Hydra stops being able to build if given a jobset with a unicode character in its name
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 358
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 27
Description
I have a jobset named foo bar… (note the single ellipses character).
Every time hydra-evaluator encounters this job it fails with "specified jobset does not exist".
The evaluator is never able to progress past this jobset, and loops forever trying.
This is closely related to #343, although it would be nice if hydra could handle jobsets with any string as a name, there's certainly something fishy if it's requiring strings are in special forms. I don't know if Perl's type system is able to cope with enforcing this though.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure in hydra-evaluator with the reported jobset name foo bar…, then compare it with the behavior described in #343. Trace how the evaluator looks up jobsets and determine what successful handling of a Unicode name should look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100