Vdoc problem notifications

[davidjanmassgov]

Hi,

I wanted to see if other people were getting overwhelmed by the number of "problem" notifications that pop up that are related to .vdoc files? It looks like these are supposed to be temporary files. They eventually go away, but I feel like my focus keeps going to these problems notifications and it's hard to ignore. Any solutions for handling these false positives?

Thanks!

[jennybc]

I find it rather peculiar that you're seeing these from a .vdoc file. So I feel like that is the real mystery.

The general phenonenon of seeing PROBLEMS of this nature for symbols in namespaces that have not been loaded yet is being tracked in #2649 and #2252.

[juliasilge]

I have occasionally seen this myself. Those .vdoc R files get generated by the Quarto extension for .qmd files, so Quarto can know what the executable content of the file is. I have not yet been able to figure out what set of steps kicks off Positron thinking such a file is full of PROBLEMS.

Those are temp files that get deleted pretty often, so I would try doing something like Developer: Restart Extension Host or closing and reopening Positron to clear them, as a workaround.

If you are able to notice a concrete set of steps leads you to see these in the first place, we would love to hear it!

[jennybc]

To further detail what's weird: I would expect PROBLEMS to be limited to files within the current workspace. So it makes sense that these .vdoc file exist behind the scenes, but it feels like they shouldn't be in scope for PROBLEMS reporting.

[davidjanmassgov]

I can try to keep an eye out, but I don’t really understand how vdoc files work! I have noticed that sometimes when I launch Positron and before I load libraries, it’s telling me preemptively that none of my functions will work. I have noticed a lot of times I just wait and the vdoc start disappearing. From: Jennifer (Jenny) Bryan ***@***.***> Sent: Friday, July 11, 2025 6:02 PM To: posit-dev/positron ***@***.***> Cc: Jan, David (DUA) ***@***.***>; Author ***@***.***> Subject: Re: [posit-dev/positron] Vdoc problem notifications (Discussion #8491) CAUTION: This email originated from a sender outside of the Commonwealth of Massachusetts mail system. Do not click on links or open attachments unless you recognize the sender and know the content is safe. To further detail what's weird: I would expect PROBLEMS to be limited to files within the current workspace. So it makes sense that these .vdoc file exist behind the scenes, but it feels like they shouldn't be in scope for PROBLEMS reporting. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/posit-dev/positron/discussions/8491*discussioncomment-13735920__;Iw!!CPANwP4y!XundL_MQqzA-SC1e9FBXHUOeELuar-OtzrGWHn3hF5_5xkxDSflHMT1C-Sulh8fMpHzyDgVSzwBwtNdnAJTpnat6RQ$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BAMN4WNVBTR3AV7UWNPDK3D3IAX57AVCNFSM6AAAAACBKVZ3O6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNZTGU4TEMA__;!!CPANwP4y!XundL_MQqzA-SC1e9FBXHUOeELuar-OtzrGWHn3hF5_5xkxDSflHMT1C-Sulh8fMpHzyDgVSzwBwtNdnAJR_4pEnYA$>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[davidjanmassgov]

A lot of them are either “No symbol” or “Syntax errors” also: ***@***.*** From: Jennifer (Jenny) Bryan ***@***.***> Sent: Friday, July 11, 2025 6:02 PM To: posit-dev/positron ***@***.***> Cc: Jan, David (DUA) ***@***.***>; Author ***@***.***> Subject: Re: [posit-dev/positron] Vdoc problem notifications (Discussion #8491) CAUTION: This email originated from a sender outside of the Commonwealth of Massachusetts mail system. Do not click on links or open attachments unless you recognize the sender and know the content is safe. To further detail what's weird: I would expect PROBLEMS to be limited to files within the current workspace. So it makes sense that these .vdoc file exist behind the scenes, but it feels like they shouldn't be in scope for PROBLEMS reporting. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/posit-dev/positron/discussions/8491*discussioncomment-13735920__;Iw!!CPANwP4y!XundL_MQqzA-SC1e9FBXHUOeELuar-OtzrGWHn3hF5_5xkxDSflHMT1C-Sulh8fMpHzyDgVSzwBwtNdnAJTpnat6RQ$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BAMN4WNVBTR3AV7UWNPDK3D3IAX57AVCNFSM6AAAAACBKVZ3O6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNZTGU4TEMA__;!!CPANwP4y!XundL_MQqzA-SC1e9FBXHUOeELuar-OtzrGWHn3hF5_5xkxDSflHMT1C-Sulh8fMpHzyDgVSzwBwtNdnAJR_4pEnYA$>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[davidjanmassgov]

I'm getting the sense that the "Problems" related to the Vdocs, might be related to the R styler (I think via the Air extension?). I was trying to call the styler multiple times and it kept racking up arbitrary large problem notifications in red. I didn't realize that I didn't finish my statement and that's why the styler didn't want to run. Once I fixed that statement, the problems (~200) went away. Not sure if all the problems were related to the styler, but maybe?