chore(relayer): migrate relayer to fhevm (#914)#2184
Merged
mergify[bot] merged 1735 commits intomainfrom Mar 26, 2026
Merged
Conversation
- See comments for explanation.
chore(relayer): removing cron from ci
chore(ci): increasing pg max connections for test ci chore(relayer): applying changes for err_reason chore(ci): increasing max connection for ci chore(ci): increasing ulimit of rust tests
- still to apply: durations
Correctly handle ext_job_id from db: - Add tests to ensure consecutive duplicate requests are failing in case of v2 (since an unassigned ext_job_id is returned to the user). v1 does not have this issue, as the ext_job_id is not used. - The tests only assert if job ids are valid by making GET query. - Then fix the bug by handling the ext_job_id returned from db correctly and then returning it to the user for user decrypt and public decrypt. UNIQUE constraint in DB: - Previously the ext_job_id was unique only when status is not failed or timed out. So, when a new request has to be made, it can have same ext_job_id. But we want it to always be unique. - So, add missing UNIQUE constraints on ext_job_id to enforce the uniqueness at DB level.
- Previosly, doing these two updates in separate transaction could lead to race condition where a request can be timed out by the cron between these two transactions. - To remove this possibility, ensure both the operations are done atomically in a single transaction.
- Add GatewayBlockNumber model, to make this repo consistent with others and update the query to use it. - Include tx hash in UserDecryptShare model. Also, create a model for user decrypt share since it has many parameters.
- Previously, the retry after was in body for 202 responses. - Now, to align 429 response (which returns the retry-after in header) move it to header and hence remove the field in response. - Also, update tests to assert this.
chore(relayer): metrics doc for statuses
chore(relayer): metrics on active and idle connection and acquire
chore(relayer): metrics documentation for http legacy and v2
- update scope
zmalatrax
approved these changes
Mar 26, 2026
eudelins-zama
approved these changes
Mar 26, 2026
Contributor
Author
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 2 hours 42 minutes 4 seconds in the queue, including 1 hour 53 minutes 10 seconds running CI. Required conditions to merge
|
This was referenced Mar 26, 2026
This was referenced Mar 26, 2026
This was referenced Mar 26, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
migrate relayer codebase