-
Notifications
You must be signed in to change notification settings - Fork 32
🎨 Changed confusing wording #7365
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
🎨 Changed confusing wording #7365
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #7365 +/- ##
==========================================
+ Coverage 86.68% 87.05% +0.37%
==========================================
Files 1711 1340 -371
Lines 66347 55909 -10438
Branches 1124 578 -546
==========================================
- Hits 57511 48673 -8838
+ Misses 8516 7051 -1465
+ Partials 320 185 -135
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
packages/service-library/src/servicelib/aiohttp/rest_middlewares.py
Outdated
Show resolved
Hide resolved
...ctor-v2/src/simcore_service_director_v2/modules/dynamic_sidecar/scheduler/_core/_observer.py
Outdated
Show resolved
Hide resolved
|
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at dcef4b4 |
|
Co-authored-by: Andrei Neagu <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>



What do these changes do?
Previously the user would see something like this

We recently had a user reporting an issue and form his message he was getting the feeling that we were already tackling the issue.
I have reworded the error displayed from the backend. I think this version is accurate and gives proper indication on what action the user should take.
Related issue/s
How to test
Dev-ops checklist