QasimWani / LeetHub

Automatically sync your leetcode solutions to your github account - top 5 trending GitHub repository
https://chrome.google.com/webstore/detail/leethub/aciombdipochlnkbpcbgdpjffcfdbggi
MIT License
3.95k stars 1.39k forks source link

Code not pushed to github on solving #578

Open Tanmay-901 opened 1 year ago

Tanmay-901 commented 1 year ago

Please review previous closed issues before filling out a new one! Duplicate issues will be closed without comment.

Describe the bug I've installed the extension recently and created a repo using it, but the code is not getting pushed.

To Reproduce Steps to reproduce the behavior:

  1. Go to any problem
  2. Click on submit solution
  3. Extension shows 0 problem solved after successful submission

Expected behavior Should've showed the problem solved in extension and github repo

Screenshots image

saumy007 commented 1 year ago

facing same problem

nik-1207 commented 1 year ago

I am also facing the same problem

devhindo commented 1 year ago

you need to revert to leetcode old theme

Tanmay-901 commented 1 year ago

@devhindo There's no option for the old theme on the study plans, for example, I can't find the old theme option for this one- https://leetcode.com/studyplan/top-interview-150/

Sandeep0306 commented 1 year ago

facing same Issue

lokeshs333 commented 1 year ago

same issue

theopn commented 1 year ago

@Tanmay-901 Click a question in the study set, and when the editor opens, you should be able to click your profile picture and switch back to the old version.

Tanmay-901 commented 1 year ago

Hi @devhindo @theopn, Thanks for sharing about reverting to the old theme option. However, if at all possible, is there any work in progress for supporting the new UI since it'd be much easier to use?

sidrakshe28 commented 1 year ago

facing the same issue. After reverting to the old UI, its working fine.

https://leetcode.com/discuss/general-discussion/181563/Switch-back-to-old-UI

theopn commented 1 year ago

@Tanmay-901 It unfortunately looks like the maintainer went inactive. There are several PRs for fixing the new UI issues, including the oldest one #464 which even got the maintainer's discussion participation in January. However, he went inactive without merging the PR, so our best bet is either using the old theme or using one of the fork that fixed this issue.

I personally work on problems using the new UI (new UI's Vim mode is drastically better than the old one) and once i pass all the test cases, I revert back to old version and make a submission. It's tedious, but it's works best for me.