Repository navigation
Conversation
Mayhem Automated Code Testing Report❗ 1 Defects Found
Testing details found at https://app.mayhem.security/forallsecure/mcode-action/mayhemit/63 |
src/project.ts normalizes each /-separated segment of the project name to Mayhem's slug ([a-z0-9-], everything else '-'), so the owner/name default from GITHUB_REPOSITORY keeps its separator. dist/ rebuilt with ncc. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The inline `.toLowerCase().replace(/[^a-z0-9-]/g, "-")` also turned the "/" in the owner/name default (GITHUB_REPOSITORY) into "-": SavantEnvs/SDL_sound became savantenvs-sdl_sound's slug "savantenvs-sdl-sound", and main.ts then prepended the owner again, naming savantenvs/savantenvs-sdl-sound, a project that does not exist, for every repository using the default. getConfig() now calls mayhemProjectSlug(), which normalizes each /-separated segment, and logs when the name changes. This is the source the committed dist/ was built from: a fresh build leaves dist/ unchanged. Also prettier-formats __tests__/project.test.ts (one line wrap, final newline) so `yarn format-check` stays clean. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sauliusbc
requested changes
Oct 1, 2026
sauliusbc
requested changes
Oct 1, 2026
sauliusbc
left a comment
sauliusbc
left a comment
Contributor
There was a problem hiding this comment.
Also: no need for internal issue numbers on PRs to public repos (so not to leak internal jira #)
d-dot-one
changed the title
Contributor
Author
|
Superseded by #258 (same change, history cleaned up per review). |
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
2 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.
The problem is a name mismatch between the GitHub action and Mayhem. For repos with _ or . in the name, the fuzz job asks Mayhem for a project name Mayhem doesn't use, since it uses dashes.
How a run gets its project name:
The fork's
mayhem.ymldoesn't set a project. It callsForAllSecure/mcode-action@v1with--image,--fileand--duration.mcode-actionfalls back to the GitHub repo name.src/main.ts:130sets theprojectto(getInput("project") || repo).toLowerCase(). That only lowercases, so the repo, for example,sample_repostayssample_repo. Mayhem stores project names with dashes. It keeps the project assample-repo. Its lookup API treats both spellings alike:sample_repoandsample-reporeturned identical data when I queried them.The seed test-suite entry uses the literal name. Every Mayhemfile starts its testsuite with
https://$MAYHEM_DOMAIN/$MAYHEM_PROJECT/$MAYHEM_TARGET/testsuite.tar. That expands to…/sample_repo/…, and at run creation Mayhem's access check refuses it: "You do not have access to use a test suite from the project sample_repo". Soooo, the run never starts.