microsoft / DurableFunctionsMonitor

A monitoring/debugging UI tool for Azure Durable Functions

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Unable to see the subscription account in the durable section on VS code

prerna-tesser opened this issue · comments

I am unable to see the subscription account in the durable functions section of the Azure tab on VS code. Because of this, I am unable to view the test hubs created for monitoring the codes and debugging on the Durable Monitor. I can't open the Durable Monitor either. The VS code was reinstalled with the updated version and the Durable Functions Monitor extension was also installed. I am using a Mac device.
Screenshot 2021-12-28 at 3 42 33 PM

@prerna-tesser , please, check the following:

  1. That your VsCode instance is properly logged in into Azure. Use the 'Azure: Sign In' command:

    image

    VsCode might occasionally get logged out, so you might need to do this login procedure again.

  2. That your subscription is not filtered out. Use the 'Azure: Select Subscriptions' command:

    image

  3. That there're no error messages shown. Press the bell button to explicitly check that:

    image

    If there're errors, tell me what they are.

Alternatively, you can always directly connect to your Task Hub by executing the 'Durable Functions Monitor' command

image

and entering the Storage Connection String.

Does that resolve the issue?

I tried the first three steps and everything was displayed as mentioned by you. However when I directly connected to my Task Hub by executing the 'Durable Functions Monitor' command, I get this error message:

" Command 'Durable Functions Monitor' resulted in an error (command 'extension.durableFunctionsMonitor' not found)"

Screenshot 2021-12-28 at 5 21 44 PM

I have checked the extension's installation and it all seems to be fine.

Also the subscription account for the other sections seems to be opening correctly except for Durable Functions.

Then it looks very much like DfMon extension fails to be activated. And in that case VsCode should show you an error message similar to this one:
image

Can you try to restart VsCode, then try to activate DfMon (by e.g. executing the 'Durable Functions Monitor' command) and tell me what exactly this error message says?

(If you don't see any error messages, try to click on that Bell button)

It gives the same error message as the previous one. And the bell icon says no new notifications.

Could this be an issue because I am using a Mac?

Could this be an issue because I am using a Mac?

I'm not aware of any Mac-specific issues by far. We need to figure out what went wrong in your specific case.

Are you installing DfMon from the Marketplace or by any other means?

Can you please try to reinstall (uninstalll, then restart VsCode, then install again) DfMon extension and see if there're any error messages shown during this process? Once done, can you please post a screenshot of your entire VsCode window (blurring any secrets, of course)?

I am downloading it from the extensions tab available on VS code.
I followed the steps as mentioned above, however no notifications are shown during the uninstall and reinstall process.
PFA the screenshot of the same.
Screenshot 2021-12-30 at 9 25 52 AM

And when I close VScode and restart it to check for the DFMon, this error message pops up:

Screenshot 2021-12-30 at 9 26 44 AM

@prerna-tesser , I can see you have some project ('TesserAPIPYDurableFuncApps') opened.

Can you please try to close it and open some other, blank folder in your VsCode?
Does DfMon show the same error and behaves in the same way, when you do so?

My hypothesis is that there might be some files in that 'TesserAPIPYDurableFuncApps' project that DfMon tries to parse at startup and fails.

Thank you it worked when I closed the project and restarted it.
Thank you.

Great to know it eventually works.
But it would still be very interesting to learn what's so specific in this'TesserAPIPYDurableFuncApps' project that causes DfMon to fail.
Do you have a 'local.settings.json' file in it? Does that file by any chance contain any comments (// or '/**/') ?

Yes, exactly. The local.settings.json contains //

I suggest you remove those comments then (as, generally speaking, it is not a valid JSON).

But thanks for reporting this issue. Closing this one in favor of #7.