-
Notifications
You must be signed in to change notification settings - Fork 6
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
Fixes for new resolver & publish #441
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
m0ar
force-pushed
the
m0ar/new-resolver-and-publish
branch
3 times, most recently
from
August 14, 2024 10:04
232d70b
to
4637cca
Compare
m0ar
force-pushed
the
m0ar/new-resolver-and-publish
branch
from
August 19, 2024 14:32
ddc717d
to
20e3ba4
Compare
m0ar
force-pushed
the
m0ar/new-resolver-and-publish
branch
from
August 19, 2024 16:11
20e3ba4
to
cb661e3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Problem / Feature
getIndexedResearchObjects
, using the new resolver routes to find streamsssss 🐃getIndexedResearchObjects
🧑🔧redisClient.ts
(swallowed global exceptions without exiting, leaving stuff in a weird state sometimes) 🙅♂️Instructions on making this work
No special setup for backend, but both frontend and resolver need these updates to support the same queries⚠️
The new in-cluster resolver requires setting the
DPID_URL_OVERRIDE
envvar for the frontend to a local URL to resolve local dPID's