Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No comment anchors detected #219

Open
Alexey-B opened this issue Jan 25, 2024 · 12 comments
Open

No comment anchors detected #219

Alexey-B opened this issue Jan 25, 2024 · 12 comments

Comments

@Alexey-B
Copy link

Describe the bug
After some kind of update in 2024, all the anchors disappeared (there were enough of them according to the project).
The new ones don't applied either.

To Reproduce
No idea

Expected behavior
The anchors is appeared.

NoAnchors

@Zodsmar
Copy link
Contributor

Zodsmar commented Jan 27, 2024

Describe the bug After some kind of update in 2024, all the anchors disappeared (there were enough of them according to the project). The new ones don't applied either.

To Reproduce No idea

Expected behavior The anchors is appeared.

NoAnchors

Have you changed your config file in any way? Have you tried comment anchors on other projects as well?

Try uninstalling and reinstalling the plugin as well

@Alexey-B
Copy link
Author

Alexey-B commented Jan 29, 2024

I didn't change config file and I tried deleting and reinstalling this extension. No success.
I even created a new workspace and disabled all extensions except Comment Anchors.
The comments are still not picked up.
Again - in 2023 everything worked with the same settings.

@Alexey-B
Copy link
Author

Alexey-B commented Feb 1, 2024

I checked on Windows 8.1, everything works there. Looks like a problem in Windows 11.

@Alexey-B
Copy link
Author

Alexey-B commented Feb 8, 2024

It’s also interesting that autofill suggests, but again doesn’t see anything.
123
456

@Zodsmar
Copy link
Contributor

Zodsmar commented Feb 17, 2024

I checked on Windows 8.1, everything works there. Looks like a problem in Windows 11.

I've run some tests on my end and I can't seem to reproduce the issue at all. I've tried different environments and different languages everything seems to work.

image

I am running Windows 11 as well. Is there any other information you can provide?
Can you show your settings.json and also if you made any modifications delete them and try just the default settings. (Deleting the plugin doesn't remove any settings.json that you added so if something is incorrect there it will exist on deletion and reinstalls)

@Alexey-B
Copy link
Author

Hi @Zodsmar !
I have attached my simplest project, there is essentially nothing in it, no settings.
I checked again (Windows 11): version v.1.10.4 is still not working. But when I rolled back to version 1.10.3, everything miraculously appeared (screen).
Test1.zip
v 1 10 3

@Zodsmar
Copy link
Contributor

Zodsmar commented Feb 19, 2024

Hi @Zodsmar ! I have attached my simplest project, there is essentially nothing in it, no settings. I checked again (Windows 11): version v.1.10.4 is still not working. But when I rolled back to version 1.10.3, everything miraculously appeared (screen). Test1.zip v 1 10 3

image

Yeah I have no idea. It works perfectly for me. If anyone else has any ideas I'm all ears but if I can't reproduce it, I'm not sure how to even go about "fixing" it

@redpwilliams
Copy link

I can attest to what @Alexey-B is saying. I'm sure I'm just now noticing this issue although the update to 1.10.4 happened 2 months ago. Can confirm that downgrading to 1.10.3 solves the issue.
I hope in the near future I'll be able to fork this and work on the issue.

@Zodsmar
Copy link
Contributor

Zodsmar commented Mar 7, 2024

be able to

If you do fork it and get the issue in a dev environment please let me know cause I have tried so many things and just can't reproduce it at all

@redpwilliams
Copy link

@Zodsmar Now I'm as lost as you. I ran the extension locally at the latest version 1.14.0 and in a clean environment, this feature of the extension worked fine. Contrasted to before where I had to downgrade to 1.13.0 to have a working feature. I tried to do a git bisect to find where the bug was introduced, but in each commit from the release of 1.13.0 to 1.14.0, I saw no issues with the feature.
To make things more confusing (for me, at least), I'm running 1.14.0 in my normal environment and the extension works fine now. I don't know what changed between today and a few days ago, as my other extensions, settings, and vscode version have stayed the same. My windows machine's version has not changed since mid February.
I'd love to know if the problem has been resolved for you, @Alexey-B.

@macjuul
Copy link
Member

macjuul commented Mar 11, 2024

Really strange issue as I personally have not run into any problems either, so I'm unsure how it could be fixed. If anyone does find a cause or a possible fix I'll gladly incorporate it and release a new version of the extension

@Alexey-B
Copy link
Author

Everything is still the same for me and I still don’t understand the reason. In version 1.10.4 (something happened to the version numbering?) there are no anchors, in version 1.10.3 there are.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants