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

New remote datasets are not registered inside proxy allowed hosts when GeoNode runs asynchoronously #12828

Open
giohappy opened this issue Jan 15, 2025 · 1 comment · May be fixed by #12829
Open
Assignees
Milestone

Comments

@giohappy
Copy link
Contributor

The link post save signal should register new remote datasets (3dtiles) inside the proxy allowed hosts registry.
This works fine when run sync but fails when run asynchronously. A restart of the GeoNode instance is required for the registry to pick up the new Link URLs.

Something is wrong here probably due to the async process still running.

@giohappy giohappy added this to the 4.4.2 milestone Jan 15, 2025
mattiagiupponi added a commit that referenced this issue Jan 16, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi added a commit that referenced this issue Jan 17, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi added a commit that referenced this issue Jan 17, 2025
…lowed hosts when GeoNode runs asynchoronously
@mattiagiupponi
Copy link
Contributor

After few analysis, the missing registration is due the fact that the signal is handled async: so in celery we have the hostname registered as expected:

Image

While in django is not, because celery is running in a different thread:

Image

We should have a persisted or shared cache for this information

mattiagiupponi added a commit that referenced this issue Jan 20, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi added a commit that referenced this issue Jan 20, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi added a commit that referenced this issue Jan 21, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi added a commit that referenced this issue Jan 21, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi added a commit that referenced this issue Jan 21, 2025
…lowed hosts when GeoNode runs asynchoronously
mattiagiupponi added a commit that referenced this issue Jan 24, 2025
…lowed hosts when GeoNode runs asynchoronously
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants