C#•9mo ago

Blazor WASM project has logic error involving data fetching

Hello there! I'm developing a web app/educational game that is meant to teach migrant workers about labor related bureaucracy in a manner they themselves would encounter it in real life. This basically is a full stack project and it seems I'm having considerable issues with getting the app to work, which is related to the api connectivity. The app connects to an API that works as an intermediary component between the web app and translation service, as well as a database of past queries since it's bit wasteful to re-translate same stuff to same languages every time. This API works as intended when it is tested with curl and Swagger. The issue comes with the web app, which, when I try to feed it with the translation query, has an unexpected error. Basically, what happens is that the used thread for the async method is busy when the app tries to fire it, since, for some weird reason, it is processed twice, with the second runaround leading to the error and thusly instead of getting translated query, the app gives me an error and asks me to reload the page. As you can see from the image, apparently there's some sort of "Memory Out of Bounds" issue going on. I have attached screenshot of the console printout, the .razor file and dev server printout to this message.

Index.razor

dev_server_printout....

42 Replies

Unknown User•9mo ago

Message Not Public

Blizzie the Mare•9mo ago

I mean it is in use because that's where the web app runs. Isn't that how it's supposed to work?

Unknown User•9mo ago

Message Not Public

Blizzie the Mare•9mo ago

I see. How this can be fixed then? I'm genuenly curious since I think changing the address from launch options, which is the most obvious solution, would just result this issue happening again on that new address

Unknown User•9mo ago

Message Not Public

Blizzie the Mare•9mo ago

I'm not sure what could cause it but I'll take look at the launch settings. It's still pretty confusing tough. If what you say is true then that would mean that rider starts 2 instances of the app when I debug or otherwise run it

MODiX•9mo ago

TeBeCo

netstat -ano | findstr 7264

Quoted by

<@689473681302224947> from #Blazor WASM project has logic error involving data fetching (click here)

React with ❌ to remove this embed.

Blizzie the Mare•9mo ago

I'm sorry but uh, this is honestly more confusing than helpful.

Angius•9mo ago

Execute this command in the terminal to see which application takes up port 7264

Blizzie the Mare•8mo ago

Ah. I see. I'll do that tomorrow! Thank you for the clarification Here's the results I get when I run the web app withouth debugging on the machine

user@computer:~$ netstat -ano | grep 7264
tcp        0      0 127.0.0.1:7264          0.0.0.0:*               LISTEN      off (0.00/0/0)
tcp        0      0 127.0.0.1:36152         127.0.0.1:7264          ESTABLISHED off (0.00/0/0)
tcp        0      0 127.0.0.1:7264          127.0.0.1:36152         ESTABLISHED off (0.00/0/0)
tcp6       0      0 ::1:7264                :::*                    LISTEN      off (0.00/0/0)
tcp6       0      0 127.0.0.1:36140         127.0.0.1:7264          TIME_WAIT   timewait (50,38/0/0)

user@computer:~$ netstat -ano | grep 7264
tcp        0      0 127.0.0.1:7264          0.0.0.0:*               LISTEN      off (0.00/0/0)
tcp        0      0 127.0.0.1:36152         127.0.0.1:7264          ESTABLISHED off (0.00/0/0)
tcp        0      0 127.0.0.1:7264          127.0.0.1:36152         ESTABLISHED off (0.00/0/0)
tcp6       0      0 ::1:7264                :::*                    LISTEN      off (0.00/0/0)
tcp6       0      0 127.0.0.1:36140         127.0.0.1:7264          TIME_WAIT   timewait (50,38/0/0)

Unknown User•8mo ago

Message Not Public

Blizzie the Mare•8mo ago

Ah, no problem, it's easy mistake to make because a lot of .NET development happens in Windows ^^

Unknown User•8mo ago

Message Not Public

Blizzie the Mare•8mo ago

Fair enough. At least I know what to do if I have to work on windows machine

Unknown User•8mo ago

Message Not Public

Gaming

Programming

Blazor WASM project has logic error involving data fetching