Api server address dns not resolving about vscode-stories HOT 30 CLOSED

well, I cleared cache memory and optimized by disk space and restarted vscode and it seems to work fine now.
but if the problem arises again will surely let you know @bar9

from vscode-stories.

It looks like the same issue with dns that Vivan had. This is very strange.

@bar9 do you think Google has countries in some sort of ban? I wouldn't think so, but we have now two users with dns issues.

@mrbinary71 Can you add an entry in /etc/hosts? And try again.

from vscode-stories.

I add this entry in /etc/hosts, and It's work fine, thanks.
216.58.194.52 vscode-stories-295306.uk.r.appspot.com
@TheFern2

from vscode-stories.

My first guess is that you still have Ben's extension installed, and that would make sense since that server is offline now. You need to install the new one after the repo was transferred to @bar9 Roland.

The extension is working fine for me right now.

from vscode-stories.

@benawad @bar9 can you guys come to an agreement and unpublish 2.22.0 extension, just to avoid creating confusion in the future.

from vscode-stories.

@TheFern2 I'm aware of the fact that the whole code has been shifted to the new one and I did install the correct v2.22.1 from it
still, the same message is displayed, unable to fetch data: error occurred

from vscode-stories.

Ok, can you give us a bit more information, we can't really help just from the fact that you say is not working on your machine alone.

• Did it worked previously and now it stopped working?
• Do you have an exact date when it stopped working, if it worked previously?
• OS
• VScode version

Can you try uninstalling it, and installing it again if you haven't already tried that.

Lastly can you try the below in your browser, you should get a json response:

https://vscode-stories-295306.uk.r.appspot.com/text-stories/hot

from vscode-stories.

@bar9 are you good with me unpublishing it?

from vscode-stories.

@benawad Yeah, makes sense.
@VivanVatsa can you dm me indicating time and date when you tried loading? I can take a look in the logs, check if I see anything there

from vscode-stories.

@bar9 it might be difficult for me to recall when it actually started to show this behavior, but the problem has been persistent for like 10 days or more now
@TheFern2 I did try reinstalling / uninstalling / removing all versions and then a fair install, still no luck.

• yes it was working before and now it stopped working
• no I don't have any exact/particular info about when it stopped working, really regretting that now
• Windows 10
• vscode v1.52.1

from vscode-stories.

well, I cleared cache memory and optimized by disk space and restarted vscode and it seems to work fine now.
but if the problem arises again will surely let you know @bar9

Thanks for the info, we'll keep an eye on our windows users.

from vscode-stories.

I am experiencing the same problem once again and the time for it is right after my comment of it started working again. I dont know what's the problem, so please help.
so time would be 7 hours ago

from vscode-stories.

@bar9 do you think this is a server issue?
@VivanVatsa did you tried calling the api with previous url provided?

from vscode-stories.

yes @TheFern2 I tried that link and still, this message is displayed
it was working for a while, when I closed this issue, then within a time frame of 10 mins it again started showing the same error message!

from vscode-stories.

Yeah I'm beginning to think this issue is related to the changes @bar9 did on the api server during the last week or so.

from vscode-stories.

Just out of curiosity, both stories panels show fetch error? The sidebar panel, and the small split panel?

from vscode-stories.

can you be precise, which all panel @TheFern2 are you talking about?
their is this "s" logo where I click to see all stories, just the usual way.
that's where this message is displayed. and their is this record story (beta) that's the only 2 things displayed regarding vscode stories

from vscode-stories.

the s logo is the sidebar panel, but there is also a smaller panel on the file explorer.

from vscode-stories.

Yeah I'm beginning to think this issue is related to the changes @bar9 did on the api server during the last week or so.

But wouldn't that mean, it isn't working for anyone, tho?

from vscode-stories.

Yeah I dunno what's going on, mine works fine on Linux. I don't use it much at work where I have Windows although I did noticed a very slow fetch one time on Windows.

So it is possible that the fetch is timing out.

from vscode-stories.

@VivanVatsa I've increased memory of the database. Did that make any difference on your end? Did you get errors lately?

from vscode-stories.

no luck @bar9 still getting the same error.
accessing from the main extension and the panel. Both display the same error.
really difficult to find what is causing this problem?

from vscode-stories.

Can you do the following command in cmd prompt, and post results. Run it a few times just to see if time is really high. I have 9ms and I am seeing a long delay when loading stories which I don't think I saw this previously:

ping vscode-stories-295306.uk.r.appspot.com

Either way I am suspecting timeout on line 16 await fetch Sidebar.svelte isn't completing, and then it goes into the catch.

https://github.com/ide-stories/vscode-stories/blob/master/svelte-stuff/components/Sidebar.svelte#L16

Just a few more questions:

• Can you authenticate? ctrl + shift + p, Stories: Authenticate
• Can you upload a story?

These last two items will tell us if you have at least have connection to the api server, and loading 21 stories on the sidebar is really just timing out in which case we really need to figure out how to optimize that route.

from vscode-stories.

the ping displays:

>> ping vscode-stories-295306.uk.r.appspot.com
Ping request could not find host vscode-stories-295306.uk.r.appspot.com. Please check the name and try again.

the authentication is working fine when I authenticate it manually as you suggested
but when I try to record and upload it, this is what is displayed even when I have opened a file to record

from vscode-stories.

Ok so we have two problems here:

• The ping should definitely ping at all times. Something is wrong with either your firewall or ISP provider. This is really odd.

• If you have a file opened, and is giving you that error that's another weird issue, but let's focus on the first issue for now.

• can you ping 216.58.194.52?

• can you try to use a vpn, then try to load stories on the sidebar panel?

from vscode-stories.

did the ping with IP address
the result is this:

for the next step, will use VPN to load stories sure!

from vscode-stories.

This issue has been resolved. It looks like @VivanVatsa has some dns issues, but we've added an entry in the hosts file to get the extension working properly, but normally this would not be required if dns was resolving properly to the server address.

from vscode-stories.

@mrbinary71 can you follow the ping commands on this post. Did you get it sorted out?

from vscode-stories.

@TheFern2

from vscode-stories.

Nice, you're welcome, I really don't know why dns is not resolving, but we'll try to make a note about this once we setup docs folder in the repo.

from vscode-stories.