Skip to content

Issue a warning if primary config is missing _self_ and is overriding config values #1755

Closed

Description

@omry

Hydra 1.1 changed the default composition order and it turned out more disruptive than initially expected.
To help people migrating be aware of the change, we will issue a warning if the primary config is specifying both a Defaults List and config values and the Defaults List is not specifying `self.

This warning may be removed in Hydra 1.2.

Activity

  1. added this to the Hydra 1.1.1 milestone on Aug 4, 2021
  2. postrational commented on Mar 7, 2022

    @postrational

    Is it possible to supress this warning in the meanwhile before 1.2 comes out(assuming new app, no hydra 1.0 compatibility needed)?

  3. Jasha10 commented on Mar 7, 2022

    @Jasha10
    Contributor

    The warning is raised as a UserWarning using python's warnings.warn stdlib function. Here is the relevant code in Hydra. You should be able to suppress this by configuring the warnings filter.

  4. francois-rozet commented on Sep 13, 2024

    @francois-rozet

    We are now at Hydra 1.3.2 and this warning has not been removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions