Suggestion: clarify cookie string structure

[rsazra]

Just started using this tool and really liking it so far, but had some trouble getting the testing/submitting working.

For future users, I think it might be helpful to clarify what the cookie needs to look like. The README gives the cookie a description of "Leetcode session cookie" with an example value of "abc123def456ghi789jkl0", and I initially just set my cookie with LEETCODE_SESSION cookie. My browser shows cookie values individually, so I only realized later that I also needed to have csrftoken set, which I manually added in the config.

An example value of "csrftoken=abc123;LEETCODE_SESSION=xyz098" would've helped me get set up quicker.

Also would be nice to surface this error to the user. I was getting a 499 Client Error when I tried testing. I see the code in config_manager.py already sends a logger error for missing CSRF token, but I didn't see this error in my terminal.

Really appreciate the project!

[michal-pielka]

Thank you for your feedback! I'm very glad to hear that the project is being used and appreciated! Currently, I'm a bit pressed for time, but I plan to address the issue and implement additional features, such as the ability to check other users' solutions, in the near future. I anticipate releasing the fix within the next few days. Once again, thank you for your support, and I hope you continue to enjoy using the tool!

[jaswanth6988]

I also got the error which says like this

┌──(/_\)-[/mnt/d/KaliWsl/leetcode_cli]
└─$ leetcode test 1.two-sum.cpp
An unexpected error occurred: Submission failed: 499 Client Error:  for url: https://leetcode.com/problems/two-sum/interpret_solution/

└─$ leetcode submit 1.two-sum.cpp
An unexpected error occurred: Submission failed: 499 Client Error:  for url: https://leetcode.com/problems/two-sum/submit/

then i went through all the files and add the csrftoken humm....still doesn't work ...why ?

ran a curl of the link that cli trying to connect .......hmm works fine ...

after adding csrf error changed from 499 -> 403 got the culprit... which is forbidden connection typically rejected by leetcode reCAPTCHA bot :( the cloudflare? hmm :...)

└─$ leetcode test 2.add-two-numbers.cpp
An unexpected error occurred: Submission failed: 403 Client Error: Forbidden for url: https://leetcode.com/problems/add-two-numbers/interpret_solution/

imo the cli is not making a perfect connection with the leetcode by any reason we might have predicted ..... one of the thing i observed is i didn't get the marks or attempted bullseye symbols on the list @rsazra can confirm this? .....which made the suspicion of the same issue ... trying to find the cause..... will update if i know :)

any way thank for the share @michal-pielka really appreciate the work ... !