Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backports for v3.5.4 #12767

Merged
merged 5 commits into from
Jun 28, 2023
Merged

Conversation

adrianeboyd
Copy link
Contributor

Description

Backports for v3.5.4.

Types of change

?

Checklist

  • I confirm that I have the right to submit this contribution under the project's MIT license.
  • I ran the tests, and all new and existing tests passed.
  • My changes don't require a change to the documentation, or if they do, I've added all required information.

bdura and others added 5 commits June 28, 2023 09:54
* Address upcoming numpy v1.25 deprecations in test suite

* Temporarily test most recent numpy prerelease in CI

* Revert "Temporarily test most recent numpy prerelease in CI"

This reverts commit d75a66e.
…rs (explosion#12701)

When sourcing a component, the object from the original pipeline is added to the new pipeline as the same object. This creates a situation where there are several attributes that cannot be in sync between the original pipeline and the new pipeline at the same time for this one object:

* component.name
* component.listener_map / component.listening_components for tok2vec and transformer

When running replace_listeners on a component, the config is not updated correctly if the state of the component is incorrect for the current pipeline (in particular changes that should be applied from model.attrs["replace_listener_cfg"] as used in spacy-transformers) due to the fact that:

* find_listeners relies on component.name to set the name in the listener_map
* replace_listeners relies on listener_map to determine how to modify the configs

In addition, there are several places where pipeline components are modified and the listener map and/or internal component names aren't currently updated.

In cases where there is a component shared by two pipelines that cannot be in sync, this PR chooses to prioritize the most recently modified or initialized pipeline. There is no actual solution with the current source behavior that will make both pipelines usable, so the current pipeline is updated whenever components are added/renamed/removed or the pipeline is initialized for training.
Support overriding registered functions in configs. Previously the registry name was parsed as a section name rather than as a registry name.
@adrianeboyd adrianeboyd added the v3.5 Related to v3.5 label Jun 28, 2023
@adrianeboyd
Copy link
Contributor Author

spacy-transformers test passes: https://buildkite.com/explosion-ai/spacy-transformers-gpu-test-suite/builds/27

@adrianeboyd
Copy link
Contributor Author

@explosion-bot please test_slow_gpu

@explosion-bot
Copy link
Collaborator

explosion-bot commented Jun 28, 2023

🪁 Successfully triggered build on Buildkite

URL: https://buildkite.com/explosion-ai/spacy-slow-gpu-tests/builds/196

@adrianeboyd adrianeboyd merged commit 7a2833b into explosion:v3.5.x Jun 28, 2023
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v3.5 Related to v3.5
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants