solution for spoj-cot

[1Nigar357]

The code solution for the problem count on tree from spoj on persistent segment tree concept

Place an "x" in the corresponding checkbox if it is done or does not apply to this pull request.

• I have tested my code.
• I have added my solution according to the steps here.
• I have followed the code conventions mentioned here.
  • I understand that if it is clear that I have not attempted to follow these conventions, my PR will be closed.
  • If changes are requested, I will re-request a review after addressing them.
• I have linked this PR to any issues that it closes.

[1Nigar357]

Hi, I just submitted this pull request. Please let me know if there’s anything I need to adjust or address. Thanks!

[1Nigar357]

Could you please help me resolve the problem "Some checks were not successful"? Is the " '''cpp " causing the problem?

[TheGamingMousse]

fyi, you can test ur mdx code at usaco.guide/editor

[TheGamingMousse]

hmm, it's giving this error:

Internal solution spoj-cot isn't linked to all of its problems (see above). Did you forget to update the solution metadata of a module after adding an internal solution?

  Error:Internal solution spoj-cot isn't linked to all of its problems (see abo  ve). Did you forget to update the solution metadata of a module after adding a  n internal solution?
  
  - gatsby-node.js:1 
    /home/runner/work/usaco-guide/usaco-guide/.cache/compiled/gatsby-node.js:1:8    567
  
  - Array.forEach
  
  - gatsby-node.js:1 Object.n.createPages
    /home/runner/work/usaco-guide/usaco-guide/.cache/compiled/gatsby-node.js:1:7    973
  
  - task_queues:95 processTicksAndRejections
    node:internal/process/task_queues:95:5
  
  - api-runner-node.js:[48](https://github.com/cpinitiative/usaco-guide/actions/runs/12919237231/job/36029331675?pr=5073#step:7:49)7 runAPI
    [usaco-guide]/[gatsby]/src/utils/api-runner-node.js:487:16
  

not finished Running gatsby-plugin-sharp.IMAGE_PROCESSING jobs - 13.133s
failed createPages - 0.814s

[1Nigar357]

I changed the solution metadata kind to internal after committing this change. I think I accidentally included it in a different pull request

[TheGamingMousse]

I changed the solution metadata kind to internal after committing this change. I think I accidentally included it in a different pull request

yeah thats what it looks like, just change the solution type to internal

[1Nigar357]

I think I solved it

[TheGamingMousse]

just some misc style changes + other

for examples of how the code should roughly look, u can look at other internal solutions (here's a good example)

[1Nigar357]

Thank you for the suggestions! Is there anything else that you would suggest modifying?

[1Nigar357]

I changed the code and the explanation part

[1Nigar357]

@SansPapyrus683 The format is automatically changed by pre-commit. Therefore, the weird formatting is caused by pre-commit

[SansPapyrus683]

no yeah, to fix it you need to place the comment above the line of code as opposed to it being on the same line

[1Nigar357]

@SansPapyrus683 I moved the comments to separate lines