Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

@fhembroff
Copy link
Contributor

@fhembroff fhembroff commented Jan 12, 2023

Description
The CLI requires the use of the ToilCompatibleTest class. However, ToilCompatibleTest class was recently removed from dockstore/dockstore in this PR. Meaning that the CLI cannot run off the current dockstore/dockstore repo. This PR adds the ToilCompatibleTest to the CLI.

Review Instructions
To review this ticket, you should

  • Verify that the CLI builds correctly with the current dockstore/dockstore repo

Security
If there are any concerns that require extra attention from the security team, highlight them here.

Please make sure that you've checked the following before submitting your pull request. Thanks!

  • Check that you pass the basic style checks and unit tests by running ./mvnw clean install
  • If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

\

@fhembroff fhembroff changed the title Remove Remove unhelpful stack traces in yaml validate by default Jan 12, 2023
@fhembroff
Copy link
Contributor Author

fhembroff commented Jan 12, 2023

I do not have any reason to believe that this PR would cause bitbucket tests to fail.

@fhembroff fhembroff marked this pull request as ready for review January 12, 2023 21:04
if (!DEBUG.get() && !INFO.get()) {
// Switching log off if DEBUG or INFO is not set
// yamlClient will generate unnecessary error logs
root.setLevel(Level.OFF);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kinda wonder if you can set the log level for a particular package or lower in the tree. Probably not too important since this only affects this specific command

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't know this until looking at this PR, but there's already code above starting around line 677 that invokes root.setLevel() based on the command line switches, and it feels weird to me to set it to Level.OFF only for this particular path.

I'd suggest one of these:

  1. Doing root.setLevel(Level.OFF) up above instead.
  2. Don't use LOG.error for errors, use LOG.info
  3. Do a pattern something like this:
if (LOG.isDebugEnabled()) { 
   LOG.error("the error message", theException);
}

I dislike 2.

I lean towards 3 -- it seems a little counter-intuitive, but the nice thing about it is that it won't log by default, but if it does log, it's logging at the ERROR level, so it will stand out for developers. 1 seems a little severe, it's also possible.

Also, see dockstore/dockstore#5223, which relates to this one -- ideally the solution would work for both.

Copy link
Contributor

@coverbeck coverbeck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a comment.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@codecov
Copy link

codecov bot commented Jan 16, 2023

Codecov Report

Base: 69.27% // Head: 69.04% // Decreases project coverage by -0.23% ⚠️

Coverage data is based on head (a476716) compared to base (67bc34a).
Patch has no changes to coverable lines.

Additional details and impacted files
@@              Coverage Diff              @@
##             develop     #215      +/-   ##
=============================================
- Coverage      69.27%   69.04%   -0.24%     
+ Complexity      1041     1026      -15     
=============================================
  Files             46       46              
  Lines           5940     5940              
  Branches         776      776              
=============================================
- Hits            4115     4101      -14     
  Misses          1503     1503              
- Partials         322      336      +14     
Flag Coverage Δ
bitbuckettests 10.01% <ø> (ø)
confidentialtooltests 53.40% <ø> (-0.36%) ⬇️
confidentialworkflowtests 28.35% <ø> (-0.04%) ⬇️
nonconfidentialtests 32.86% <ø> (-0.04%) ⬇️
singularitytests 16.90% <ø> (ø)
unittests 8.03% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...sted/notificationsclients/NotificationsClient.java 78.43% <0.00%> (-3.93%) ⬇️
...io/dockstore/client/cli/nested/WorkflowClient.java 72.78% <0.00%> (-0.77%) ⬇️
...ckstore/client/cli/nested/AbstractEntryClient.java 73.40% <0.00%> (-0.50%) ⬇️
.../src/main/java/io/dockstore/client/cli/Client.java 48.14% <0.00%> (-0.25%) ⬇️
...ava/io/dockstore/client/cli/nested/ToolClient.java 72.12% <0.00%> (-0.14%) ⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

Copy link
Member

@denis-yuen denis-yuen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😆
not much here now

Copy link
Contributor

@coverbeck coverbeck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While this change is good, the PR title nor linked issue seem applicable. Could you please either fold into your other PR, or update the title/description of this PR?

@fhembroff fhembroff changed the title Remove unhelpful stack traces in yaml validate by default Added a ToilCompatibleTest class to CLI Jan 17, 2023
@fhembroff
Copy link
Contributor Author

While this change is good, the PR title nor linked issue seem applicable. Could you please either fold into your other PR, or update the title/description of this PR?

I have updated the title and description.

@fhembroff fhembroff requested a review from coverbeck January 17, 2023 20:32
@fhembroff fhembroff merged commit 9cb5ebb into develop Jan 17, 2023
@fhembroff fhembroff deleted the feature/DOCK-2268/remove-default-stack-trace branch January 17, 2023 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.