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

fix: treat invalid jwt as 401 #444

Merged
merged 1 commit into from
Oct 8, 2024
Merged

Conversation

Panaetius
Copy link
Member

closes #353

/deploy

@Panaetius
Copy link
Member Author

This change is part of the following stack:

Change managed by git-spice.

@RenkuBot
Copy link
Contributor

RenkuBot commented Oct 7, 2024

You can access the deployment of this PR at https://renku-ci-ds-444.dev.renku.ch

@coveralls
Copy link

Pull Request Test Coverage Report for Build 11215659061

Details

  • 6 of 7 (85.71%) changed or added relevant lines in 2 files are covered.
  • 7 unchanged lines in 5 files lost coverage.
  • Overall coverage decreased (-0.04%) to 90.488%

Changes Missing Coverage Covered Lines Changed/Added Lines %
components/renku_data_services/base_api/error_handler.py 2 3 66.67%
Files with Coverage Reduction New Missed Lines %
components/renku_data_services/base_api/error_handler.py 1 90.12%
components/renku_data_services/base_models/core.py 1 85.85%
components/renku_data_services/crc/blueprints.py 1 93.19%
components/renku_data_services/crc/db.py 2 87.81%
components/renku_data_services/storage/blueprints.py 2 94.29%
Totals Coverage Status
Change from base Build 11214540828: -0.04%
Covered Lines: 9551
Relevant Lines: 10555

💛 - Coveralls

@Panaetius Panaetius merged commit ce2f53c into main Oct 8, 2024
16 of 17 checks passed
@Panaetius Panaetius deleted the fix/353-handle-invalid-jwt branch October 8, 2024 08:36
@RenkuBot
Copy link
Contributor

RenkuBot commented Oct 8, 2024

Tearing down the temporary RenkuLab deplyoment for this PR.

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.

Sending an invalid bearer token causes a 500 error
4 participants