-
Notifications
You must be signed in to change notification settings - Fork 1
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
Have a mechanism to turn off shepherds & layout #25
Comments
PeterJCLaw
added a commit
to PeterJCLaw/srcomp-http
that referenced
this issue
Aug 8, 2023
This is allowed by the core srcomp library, so the HTTP API should not complain about it being missing. See also PeterJCLaw/srcomp#25
Note that while some partial shepherd/layout data combinations result in various loading errors, others appear to load ok. |
PeterJCLaw
added a commit
to sourcebots/compstate-smallpeice2023
that referenced
this issue
Aug 8, 2023
This might be something to turn into a warning and then silence via a warnings silencing mechanism? (#23) Or we might want to just drop this entirely as we're not using it any more. |
PeterJCLaw
changed the title
Have a mechanism to turn off shepherds
Have a mechanism to turn off shepherds & layout
Apr 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes we don't want to deploy shepherds, so needing to include them in the compstate isn't ideal.
While the core library seems ok with some aspects of shepherds being missing, it's inconsistent about how much is needed.
Additionally SRComp-HTTP requires that:
signal_shepherds
key is provided, though the core library does not (fixed in PeterJCLaw/srcomp-http@3ad10e8)The text was updated successfully, but these errors were encountered: