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

fix(server): improved packfile encoding to support short messages and… #409

Merged
merged 5 commits into from
Feb 6, 2024

Conversation

sammoorhouse
Copy link
Contributor

@sammoorhouse sammoorhouse commented Jan 22, 2024

… unicode in errors

This change allows you to say

step.setError(`🥺 Rejecting repo ${action.repo} not in the authorisedList`);

in a step.

Also fixes a padding bug that meant fewer than 5chars of errors broke the proxy response.

Copy link

linux-foundation-easycla bot commented Jan 22, 2024

CLA Signed

The committers listed above are authorized under a signed CLA.

Copy link

netlify bot commented Jan 22, 2024

Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name Link
🔨 Latest commit d2d2c6b
🔍 Latest deploy log https://app.netlify.com/sites/endearing-brigadeiros-63f9d0/deploys/65c2513f9ecbe20008e7102c

@maoo
Copy link
Member

maoo commented Jan 23, 2024

Thanks for the PR @sammoorhouse ! Please reach out to [email protected] if you encounter any issue to sign the FINOS CLA using EasyCLA.

@JamieSlome
Copy link
Member

@sammoorhouse - thanks for the contribution 👍 I'd been wondering how to get some "prettier" messages into the CLI for the developer.

Do you think we could include a test case with this PR to demonstrate it works successfully? Perhaps to demonstrate that a message successfully returns with Unicode characters?

Happy to help if needed 🎉

@JamieSlome JamieSlome self-requested a review January 23, 2024 11:45
@JamieSlome JamieSlome added the bug Something isn't working label Jan 23, 2024
@sammoorhouse
Copy link
Contributor Author

Thanks @JamieSlome I'll have a look later today!

@sammoorhouse
Copy link
Contributor Author

I extracted 'handleMessage' in proxy/routes and wrote two tests just for that function in a second commit just now. Thanks!

src/proxy/routes/index.js Show resolved Hide resolved
@psmulovics
Copy link

Can someone kick the build again? It failed on something unrelated imho.

@coopernetes
Copy link
Contributor

Can someone kick the build again? It failed on something unrelated imho.

The failure is due to #213, we have some sort of repo permission bug in the coverage steps.

I’ll try to get a PR open soon to get it fixed then we can rebase on this one. Seems like a simple enough fix: zgosalvez/github-actions-report-lcov#150

@JamieSlome JamieSlome mentioned this pull request Jan 25, 2024
Copy link
Member

@JamieSlome JamieSlome left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🍰

Ready to go once we've addressed the code coverage permissions issue...

(cc) @coopernetes @CyberCitizen01

@JamieSlome JamieSlome merged commit edeed3d into finos:main Feb 6, 2024
10 checks passed
Psingle20 pushed a commit to Psingle20/git-proxy that referenced this pull request Nov 27, 2024
fix(server): improved packfile encoding to support short messages and…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants