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

Merge release_23.1 into dev #17056

Merged
merged 18 commits into from
Nov 21, 2023
Merged

Merge release_23.1 into dev #17056

merged 18 commits into from
Nov 21, 2023

Conversation

mvdbeek
Copy link
Member

@mvdbeek mvdbeek commented Nov 20, 2023

(Please replace this header with a description of your pull request. Please include BOTH what you did and why you made the changes. The "why" may simply be citing a relevant Galaxy issue.)
(If fixing a bug, please add any relevant error or traceback)
(For UI components, it is recommended to include screenshots or screencasts)

How to test the changes?

(Select all options that apply)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

mvdbeek and others added 17 commits November 8, 2023 10:38
Fixes galaxyproject#16987,
though there's probably something to be done for loc files
being loaded from tools. At the minimum this is a versioning
issue, if a new version of featureCounts comes with a new
built-in reference then an old version shouldn't use it,
and vice-versa. Seems like a hard problem to solve.
…cate_log_files

[23.1] Change log level for duplicate data table entries to warning
And disable submit button when request is being handled.
[23.1] Fix duplicated tools in tool panel view section copying
Admin users get all the broadcasts notifications regardless of their "activation" status so we need to apply the filtering also in the client.

Regular users are not affected because they can only get active broadcasts.
…flow form

This is another attempt at
galaxyproject#13220, but taking into
account
galaxyproject#13220 (comment)
by limiting this to the simplified workflow form, where we can assume
input parameter optionality to have the correct meaning.

This makes it harder to submit a mandatory text parameter that can be
empty, but that is (at this point at least) a very fringe requirement.

If really needed you can make the parameter optional (and use pick_value
to fill in an empty string if null is not OK as a value).
…ast_filtering_for_admins

[23.1] Fix filtering of active broadcasts for admins
…submission_missing_input_value

[23.1] Prevent workflow submission with missing input values
@mvdbeek mvdbeek merged commit a758757 into galaxyproject:dev Nov 21, 2023
50 of 51 checks passed
@nsoranzo nsoranzo added the merge label Nov 21, 2023
@galaxyproject galaxyproject deleted a comment from github-actions bot Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants