example.sh reports 'Error generating session token" erroneously
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- bash
- Domain
- api, authentication
Research direction
Start with examples/bash/authentication/example.sh at line 43 and inspect the session-token check described in the issue. Correct the check so valid session tokens are not reported as errors, then verify the authentication example no longer prints the failure message for a valid response.
Written by the indexing model from the issue text.
Description
This tests for the presence of a dash in the returned sessiontoken, but since sessiontokens don't have dashes, all valid requests for sessiontokens are reported as "failed"
- Dominant language
- No language data
- Stars
- 49
- Forks
- 47
- Avg merge
- 31m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Tripletex/tripletex-api2
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Tripletex/tripletex-api2#135 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Tripletex/tripletex-api2#133 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Tripletex/tripletex-api2#130 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Tripletex/tripletex-api2#127 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Tripletex/tripletex-api2#126 · 1 reaction ·
All issues in Tripletex/tripletex-api2
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Marker-Inc-Korea/AutoRAG#1801 ·
Maintainers usually reply within 1 day
-
reef remote discovery needs a GitHub token for public releases, and its error names `<provider>`Openarea:ecosystem bug cli
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Chelis-Lang/chelis#3313 ·
Maintainers usually reply within 1 day
-
Clock.MakeTime fails to validate hour, minute, and second ranges due to inert Calendar.set try-catchOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mit-cml/appinventor-sources#4139 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
qdrant/qdrant#11002 · 1 comment ·
Maintainers usually reply within 1 day