search

synapsecns / sanguine

Synapse Monorepo
MIT License
35 stars 25 forks source link

screener auth fix #2782

Closed golangisfun123 closed 2 weeks ago

golangisfun123 commented 2 weeks ago

Description A clear and concise description of the features you're adding in this pull request.

Additional context Add any other context about the problem you're solving.

Metadata

Summary by CodeRabbit

coderabbitai[bot] commented 2 weeks ago

Walkthrough

The recent updates focus on enhancing security and functionality. Specific improvements include renaming headers and paths, adding new testing functions, introducing a gin-based middleware for tracing requests, and creating utilities for JSON beautification in the core/ginhelper directory. Together, these changes improve the robustness and clarity of the API interactions and facilitate easier debugging and improved test coverage.

Changes

File/Path Change Summary
contrib/screener-api/client/client.go Renamed headers and updated endpoint path in the BlacklistAddress function.
contrib/screener-api/screener/screener.go Modified authMiddleware to handle new header names and improved message construction.
contrib/screener-api/screener/suite_test.go Added functions for testing blacklist operations with randomized data and status checks.
contrib/screener-api/screener/export_test.go Added import for github.com/synapsecns/sanguine/contrib/screener-api/config.
core/ginhelper/README.md Introduced gindump, a middleware for dumping request and response data in a visually appealing way.
core/ginhelper/gindump.go Added middleware and utility functions for tracing and dumping HTTP requests and responses, including a new parameter for callback functions.
core/ginhelper/gindump_test.go Added tests for handling different MIME types using the new gin dump utilities.
core/ginhelper/parse.go Added functions for beautifying JSON output and handling hidden fields in JSON structures.

Poem

In lines of code where brilliance shines,
Headers changed, the path refines,
Gin now dumps with utmost grace,
JSON’s beauty finds its place.
A screener strong, tests with zeal,
Rabbit hops, with code that’s real. 🐇✨

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
codecov[bot] commented 2 weeks ago

Codecov Report

Attention: Patch coverage is 62.83525% with 97 lines in your changes missing coverage. Please review.

Project coverage is 25.77429%. Comparing base (239a996) to head (bc7107c).

Files Patch % Lines
core/ginhelper/gindump.go 55.81395% 43 Missing and 14 partials :warning:
core/ginhelper/parse.go 70.70707% 21 Missing and 8 partials :warning:
contrib/screener-api/screener/screener.go 78.57143% 4 Missing and 2 partials :warning:
contrib/screener-api/client/client.go 0.00000% 5 Missing :warning:
Additional details and impacted files ```diff @@ Coverage Diff @@ ## master #2782 +/- ## =================================================== + Coverage 25.66686% 25.77429% +0.10743% =================================================== Files 699 759 +60 Lines 51510 54469 +2959 Branches 80 80 =================================================== + Hits 13221 14039 +818 - Misses 36939 38995 +2056 - Partials 1350 1435 +85 ``` | [Flag](https://app.codecov.io/gh/synapsecns/sanguine/pull/2782/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns) | Coverage Δ | | |---|---|---| | [cctp-relayer](https://app.codecov.io/gh/synapsecns/sanguine/pull/2782/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns) | `31.93780% <ø> (?)` | | | [core](https://app.codecov.io/gh/synapsecns/sanguine/pull/2782/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns) | `62.15933% <62.28070%> (+0.95962%)` | :arrow_up: | | [ethergo](https://app.codecov.io/gh/synapsecns/sanguine/pull/2782/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns) | `49.01600% <ø> (+0.16989%)` | :arrow_up: | | [git-changes-action](https://app.codecov.io/gh/synapsecns/sanguine/pull/2782/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns) | `23.69615% <ø> (ø)` | | | [omnirpc](https://app.codecov.io/gh/synapsecns/sanguine/pull/2782/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns) | `33.08129% <ø> (+0.04726%)` | :arrow_up: | | [opbot](https://app.codecov.io/gh/synapsecns/sanguine/pull/2782/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns) | `0.22305% <ø> (ø)` | | | [promexporter](https://app.codecov.io/gh/synapsecns/sanguine/pull/2782/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns) | `9.86717% <ø> (?)` | | | [rfq](https://app.codecov.io/gh/synapsecns/sanguine/pull/2782/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns) | `27.02332% <ø> (ø)` | | | [screener-api](https://app.codecov.io/gh/synapsecns/sanguine/pull/2782/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns) | `38.48168% <66.66667%> (-0.25351%)` | :arrow_down: | | [scribe](https://app.codecov.io/gh/synapsecns/sanguine/pull/2782/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns) | `18.11159% <ø> (ø)` | | | [tools](https://app.codecov.io/gh/synapsecns/sanguine/pull/2782/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns) | `30.55118% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=synapsecns#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

cloudflare-pages[bot] commented 2 weeks ago

Deploying sanguine-fe with  Cloudflare Pages  Cloudflare Pages

Latest commit: bc7107c
Status:🚫  Build failed.

View logs