Loading ... Compilation error. Oh! I didn't declare that variable x. corrected
Compile Now.. Loading ... Runtime error. Wtf! ... Oh! The array size is 1000 and I entered 100. corrected
Compile Loading ... Wrong Answer. In sample test case itself?!? Ohhh !! I forgot to update flag value. corrected
Compile Loading ... Sample test cases passed. Cross check with extra cases generated on your own, gives AC.
Taking a deep breath and clicking SUBMIT ... Time Limit Exceeded. Damn!
Few hours later
Taking a deep breath and clicking SUBMIT ... Wrong Answer.
"Debugging is like being the detective in a crime movie where you are also the murdurer" - Filipe Fortes
Pretty much true, isnt it?! This opencode, its not going to be like that. You won't be asked to murder and then, solve the crime. Instead we are helping this opencode. We will do the murder for you and give an oppurtunity for you to become Sherlock Holmes.
And you are rewarded points for that!!
A new issue for a unique bug will open everyday at 10 pm ! Stay tuned.
Whoever wishes to participate in this project must follow these guidelines:
- Do not make PR which is not related to any issues. You can create an issue and solve it once we approve them.
- Be polite: Be polite to other community members.
- Communicate: Whether you are working on a new correction or facing a doubt please feel free to ask us on our slack channel(specifically #competitive-coding). We will be happy to help you out.
- Each issue should be resolved by either modifying a line of code or appending a line of code. Resolving an issue by modifying/adding multiple lines will not be entertained.
- Mention the line number along with the Pull Request and further give suitable explanation.
- Each task is 6 days long. Each task will have 6 issues. Every new issue shall be uploaded everyday at 10 pm. The issues are independent of each other.
- Submission are encouraged only till 6 days from (uploaded day for each issue)/(Feb 12) and after that the issue will be automatically closed and the bug-free code will be uploaded. All files related to task 1 shall be uploaded under week 1 folder and so on.
- On the 7th day, at 10 pm, the new task and its first issue will be uploaded. And this cycle shall continue over the month. Thus, for a month i.e., 30 days, there are totally 5 tasks under "Open-De-Bug".
- Pull Request older than 2 days with no response from the contributor shall be marked closed.
Create a PR as per the format given below:
- On your local machine, go to the project folder.
- Go inside the "tasks" folder and go to the task folder in which you want to solve the issues. (for example "task_2").
- Read and understand the problem statement and the code given in the particular task folder.
- Find the bug.
- Edit, commit and push the changes.
- Create the PR according to the format mentioned in the PULL_REQUEST_TEMPLATE.md.
It is totally upon the mentors to close the issue, you can't make any pull request after the issue is closed. Once your PR has some mistake and is closed you cant make any further PRs for that particular issue. All PR's will be reviewed and merged at the end of the day. Only first correct PR for each erronous bug/issue will be considered.
Happy Debugging ! ✌️