Bump depedencies

[ndaelman-hu]

No description provided.

[ndaelman-hu]

Updated the [dev] dependencies to match nomad-lab.

[ladinesa]

can you perhaps also fix the error associated with the removal of metainfo.Environment

[ndaelman-hu]

can you perhaps also fix the error associated with the removal of metainfo.Environment

But this is on the nomad-lab side. I don't mind removing it, as long as Markus and Theodore agree.
Moreover, is there a certain protocol for a deprecation time period for people to adapt or how to announce removal?

[ladinesa]

can you perhaps also fix the error associated with the removal of metainfo.Environment

But this is on the nomad-lab side. I don't mind removing it, as long as Markus and Theodore agree. Moreover, is there a certain protocol for a deprecation time period for people to adapt or how to announce removal?

no i mean if there is still some lingering usage of Environment in the parsers, I remember removing them a few months back. I thought this is the reason for the failure in the tests, but it seems not

[ndaelman-hu]

can you perhaps also fix the error associated with the removal of metainfo.Environment

But this is on the nomad-lab side. I don't mind removing it, as long as Markus and Theodore agree. Moreover, is there a certain protocol for a deprecation time period for people to adapt or how to announce removal?

no i mean if there is still some lingering usage of Environment in the parsers, I remember removing them a few months back. I thought this is the reason for the failure in the tests, but it seems not

No, the reason for the failure is the magres parser. (Btw, we should check on which schema the standalone plugin depends.)
There seems to be mention of Environment in the cp2k parser. Will look into it.

[blueraft]

Thanks!

[coveralls]

Pull Request Test Coverage Report for Build 11839729046

Details

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.005%) to 93.067%

---

Totals
Change from base Build 11727381091:	0.005%
Covered Lines:	35815
Relevant Lines:	38483

---

💛 - Coveralls

[ndaelman-hu]

@ladinesa Should I also open an issue for deprecating

# For automatic workflows
                from nomad.search import search
                from nomad.app.v1.models import MetadataRequired

That would remove the nomad-lab[infrastructure] dependency

[ladinesa]

@ladinesa Should I also open an issue for deprecating

# For automatic workflows
                from nomad.search import search
                from nomad.app.v1.models import MetadataRequired

That would remove the nomad-lab[infrastructure] dependency

i added this in todo, we can adapt my implementation in magres parser where i did not use search

[JosePizarro3]

i added this in todo, we can adapt my implementation in magres parser where i did not use search

please, note Sathya is developing the parser in its own repo and asked to disconnect the parser in here

[ladinesa]

i added this in todo, we can adapt my implementation in magres parser where i did not use search

please, note Sathya is developing the parser in its own repo and asked to disconnect the parser in here

we should discuss how to handle external developments, since imo we should have full control over parsers that we interface with nomad

[ndaelman-hu]

i added this in todo, we can adapt my implementation in magres parser where i did not use search

please, note Sathya is developing the parser in its own repo and asked to disconnect the parser in here

we should discuss how to handle external developments, since imo we should have full control over parsers that we interface with nomad

This is a separate discussion. This PR just updates some dependencies.

Sathya just has to properly set up his nomad.yaml, that's all. We are NOT going to start stripping off parsers, just because somebody made their own. I agree that this is an example of a counter-argument against grouping parsers into a single repo, though.