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

Hyper-optimized telemetry: Provide clear explanation for unexpected value of prefix byte #2163

Conversation

vlabensky-sana
Copy link
Contributor

@vlabensky-sana vlabensky-sana commented Aug 9, 2023

As discussed in #2160 here's a small change that hopefully makes the last sentence in instructions for the "Hyper-optimized telemetry" exercise a bit more clear.

@github-actions
Copy link
Contributor

github-actions bot commented Aug 9, 2023

Hello. Thanks for opening a PR on Exercism. We are currently in a phase of our journey where we have paused community contributions to allow us to take a breather and redesign our community model. You can learn more in this blog post. As such, all issues and PRs in this repository are being automatically closed.

That doesn't mean we're not interested in your ideas, or that if you're stuck on something we don't want to help. The best place to discuss things is with our community on the Exercism Community Forum. You can use this link to copy this into a new topic there.


Note: If this PR has been pre-approved, please link back to this PR on the forum thread and a maintainer or staff member will reopen it.

@github-actions github-actions bot closed this Aug 9, 2023
@vlabensky-sana vlabensky-sana changed the title Provide clear explanation for unexpected value of prefix byte Hyper-optimized telemetry: Provide clear explanation for unexpected value of prefix byte Aug 9, 2023
@ErikSchierboom ErikSchierboom reopened this Aug 9, 2023
@ErikSchierboom ErikSchierboom merged commit c9d0559 into exercism:main Aug 9, 2023
4 checks passed
@ErikSchierboom
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants