-
-
Notifications
You must be signed in to change notification settings - Fork 874
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
Update client.py #1005
Update client.py #1005
Conversation
Chance made to solve error: c.a.p.r.c.security.jersey.XsrfResourceFilter] Use of the 'nocheck' value for X-Atlassian-Token has been deprecated since rest 3.0.0. Please use a value of 'no-check' instead.
looks like the maintainers want to have the ci system back up and running before agreeing to any new merges. if you want to contribute to get yr pr through have a look here => #896 |
@EdgeSync please make sure latest master changes are in your branch so the CI system can run again. |
Was hoping to see the CI triggered. Now I'm wondering if it was the close reopen which triggered it properly... |
@ssbarnea seems like a valid change ready to merge |
Chance made to solve error: c.a.p.r.c.security.jersey.XsrfResourceFilter] Use of the 'nocheck' value for X-Atlassian-Token has been deprecated since rest 3.0.0. Please use a value of 'no-check' instead.
Change made to solve warning in JIRA when adding an attachment.
Error:
2021-03-10 17:18:20,564+0000 https-jsse-nio-8443-exec-98 WARN ***REDACTED*** 1038x776292x1 1pqrv0m 16.85.88.14 /rest/api/2/issue/GIA-3259/attachments [c.a.p.r.c.security.jersey.XsrfResourceFilter] Use of the 'nocheck' value for X-Atlassian-Token has been deprecated since rest 3.0.0. Please use a value of 'no-check' instead.
Solution:
Edit client.py and change both instances of nocheck to no-check