Closed pavanvidem closed 2 months ago
hi @pcm32 this is a tiny fix that will have a big impact on the cell annotation tutorial from @hexhowells.
Thanks @pavanvidem !
I wonder why I need to be constantly authorising the tests...
@pavanvidem please feel free to ping me on elements/matrix whenever things are not advancing here. In the era of notification flooding, I mostly tend to give attention first to people actually talking to me 😂 . Emails from github might get lost in the flood.
...weird, file seems to be there.... maybe try an asserts instead of comparing against the file? More future proof. You can check the existing file for it.
Indeed, some files are missing. I will add them (rds files) later and also add asserts for text files.
I'm happy to remove the check file sizes check, as we delete anyways test files before uploading to the toolshed. However, it doesn't allow me to edit this in your branch.
how to disable that?
@pcm32 if you give a thumbs up I can merge it.
@pavanvidem could you please set this line https://github.com/pavanvidem/container-galaxy-sc-tertiary/blob/patch-1/.github/workflows/pr.yaml#L20 to 10M in your branch, then that should allow the tests to pass.
If you could also please set the value here https://github.com/pavanvidem/container-galaxy-sc-tertiary/blob/patch-1/.github/workflows/pr.yaml#L400 to 1 MB (so remove one zero) and change the print out in the following line to say 1 MB instead of 10 MB, that should avoid us from uploading heavy test files to the Galaxy toolshed. Then we can merge if tests continue to pass. Thanks!
It should be deployed to the toolshed in the next 10 to 20 minutes @pavanvidem. Thanks again for this.
On toolshed already. Thanks @pcm32
Description
The toolshed deployment failed because of inccrect type for
threshold
parameter. Changing it to float should fix it.Fixes # (issue)
Type of change
Checklist
@TOOL_VERSION@
), then I have reset all 'build' values to 0 (e.g.@TOOL_VERSION@+galaxy0
)@TOOL_VERSION@+galaxy0
@TOOL_VERSION@+galaxy1
). It is acceptable to do this as well when the cli version changed but not the underlying tool (to avoid issues in the coming point).@TOOL_VERSION@
part of the version does not contain any+
symbols within, otherwise this will break tool ordering on the interface and the default tool being picked. Tool version should always conform to PEP440 to avoid this issue. The only+
should be the one precedinggalaxy<build>
(unless that all the versions from that tool previously followed a different pattern).