fix: DIA-1935: fix JWT feature flag

[pakelley]

---

PR fulfills these requirements

• Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
• Tests for the changes have been added/updated (for bug fixes/features)
• Docs have been added/updated (for bug fixes/features)
• Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
• Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)

(check all that apply)

• Product design
• Backend (Database)
• Backend (API)
• Frontend

Describe the reason for change

(link to issue, supportive screenshots etc.)

What does this fix?

(if this is a bug fix)

What is the new behavior?

(if this is a breaking or feature change)

What is the current behavior?

(if this is a breaking or feature change)

What libraries were added/updated?

(list all with version changes)

Does this change affect performance?

(if so describe the impacts positive or negative)

Does this change affect security?

(if so describe the impacts positive or negative)

What alternative approaches were there?

(briefly list any if applicable)

What feature flags were used to cover this change?

(briefly list any if applicable)

Does this PR introduce a breaking change?

(check only one)

• Yes, and covered entirely by feature flag(s)
• Yes, and covered partially by feature flag(s)
• No
• Not sure (briefly explain the situation below)

What level of testing was included in the change?

(check all that apply)

• e2e
• integration
• unit

Which logical domain(s) does this change affect?

(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)

[netlify]

✅ Deploy Preview for heartex-docs ready!

Name	Link
🔨 Latest commit	b5f0544
🔍 Latest deploy log	https://app.netlify.com/sites/heartex-docs/deploys/67bcf1b9ff87580008ab21a1
😎 Deploy Preview	https://deploy-preview-7128--heartex-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for label-studio-docs-new-theme ready!

Name	Link
🔨 Latest commit	b5f0544
🔍 Latest deploy log	https://app.netlify.com/sites/label-studio-docs-new-theme/deploys/67bcf1b9c6a1500008f1a012
😎 Deploy Preview	https://deploy-preview-7128--label-studio-docs-new-theme.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

Attention: Patch coverage is 80.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 77.08%. Comparing base (7d086c2) to head (b5f0544).
Report is 22 commits behind head on develop.

Files with missing lines	Patch %	Lines
label_studio/jwt_auth/middleware.py	80.00%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #7128      +/-   ##
===========================================
- Coverage    77.09%   77.08%   -0.01%     
===========================================
  Files          183      183              
  Lines        14406    14401       -5     
===========================================
- Hits         11106    11101       -5     
  Misses        3300     3300              

Flag	Coverage Δ
pytests	77.08% <80.00%> (-0.01%)	⬇️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[matt-bernstein]

The logic makes sense to me, but any particular reason for removing the debug logs? There's no other indication of why the auth wouldn't work in that case

[pakelley]

The logic makes sense to me, but any particular reason for removing the debug logs? There's no other indication of why the auth wouldn't work in that case

Ah, yeah this was debug logging that was added (in a separate PR) to debug this specific issue. Nikolai requested that we remove it again after this, because it will result in lots of noise (as this is called on every request)