-9

I am trying to figure out why in recent times I'm suddenly facing down & close votes on a lot of my questions. If you look at my score and history, I've gotten points more for questions than answers so this is a big change.

Can someone give me guidance as to why this question has received both down & close votes?

  1. I did a Google search and couldn't find an answer.
  2. I asked Copilot and got the standard list of potential issues.
  3. I believe it is a very clear, specific, focused question.
  4. It is an issue with Blazor server, so very much on topic.

So why would people down vote or close it?

20
  • Unrelated but interesting, when I clicked submit it took me to page not found. The question above was added though so not a big issue.
    – David Thielen
    Commented Jun 25 at 21:31
  • 2
    The two glaring issues is that you're asking two questions (paraphrased; "how do I speed this thing up?" and "why is blazor loaded multiple times/how does blazor work internally?"), and you lack an MCVE.
    – Zoe - Save the data dump Mod
    Commented Jun 25 at 21:38
  • 6
    See the blue shaded box at the top of your question? See how it says "Update the question so it focuses on one problem only."? Is that somehow unclear? (I genuinely don't understand how it's possible to write "And a follow-up question - ", and then still sincerely "believe it is a very clear, specific, focused question".) Please also read How to Ask and how to create a minimal, reproducible example.
    – Karl Knechtel
    Commented Jun 25 at 21:44
  • 1
    @Karl a small quibble: that question was closed after this meta question was asked, so that box wasn't there at the time.
    – Ryan M Mod
    Commented Jun 25 at 21:47
  • 6
    Ah, ninjas again... anyway: I also don't understand how we could possibly be expected to know "why... this one call to blazor.server.js take[s] 1.5 minutes" when we haven't been shown any of the app's contents, nor any context for how or why the call was made or what the GET query parameters should mean. "I asked Copilot and got the standard list of potential issues." - okay, and what happened when you tried investigating those? (You did try, right?)
    – Karl Knechtel
    Commented Jun 25 at 21:49
  • @Zoe I added the follow-on question because I think the cause of the multiple loads of blazor.js might help me then zero in on what this specific load of blazor.js is doing. And from that, why it's taking so long. That's why I thought it was germane and helpful. But I've removed it. As to a MCVE, that would likely require days of effort so I figured ask first in case someone knows.
    – David Thielen
    Commented Jun 25 at 22:05
  • @KarlKnechtel I did not try the list because there were not an issue. The page comes up fast on my browser even under heavy load test so server load, resource limitation, network latency, bandwidth, & large static files are clearly not an issue. The whole page is complete and works in about 1/3 of a second. But this one file waiting 1.5 minutes screws up the load testing because the page is not completely loaded until that returns. It's very weird.
    – David Thielen
    Commented Jun 25 at 22:10
  • @Zoe I figured try the standard Blazor sample Visual Studio provides. Same issue. So I updated with that MCVE. That's about as simple a Blazor app as can be created. And it has a worse case of this.
    – David Thielen
    Commented Jun 25 at 22:32
  • See meta.stackoverflow.com/a/254430/6296561
    – Zoe - Save the data dump Mod
    Commented Jun 25 at 22:43
  • @Zoe That would require posting the text of 35 source files. I understand the issue of that zip file can go away (I leave the ones I place up for links up forever because of this). But I think posting all that content is a worse idea. Now if there was 20 lines of code the issue was around, then I agree with you 100%.
    – David Thielen
    Commented Jun 25 at 23:01
  • 3
    It might be better to structure the question around the process for debugging a particular class of slowness issue, rather than simply asking what the issue is. The latter is impossible to answer without seeing any information about the app or environment; in fact, all the things you suggest "are clearly not an issue" ("server load, resource limitation, network latency, bandwidth, & large static files") are entirely plausible answers to the question as originally asked.
    – Ryan M Mod
    Commented Jun 25 at 23:10
  • 3
    Don't say why you did what you did, act on feedback. If you can't then you don't have a suitable post.
    – philipxy
    Commented Jun 26 at 0:18
  • 12
    "As to a MCVE, that would likely require days of effort so I figured ask first" - guess what? That's honestly not our concern.
    – Karl Knechtel
    Commented Jun 26 at 1:54
  • 4
    It's not a matter of how long it takes. It's a matter of meeting the laid-out criteria. If that takes a long time, so be it. Sometimes it doesn't.
    – Karl Knechtel
    Commented Jun 26 at 3:06
  • 4
    "I am trying to figure out why in recent times I'm suddenly facing down & close votes on a lot of my questions." - You are not alone, I have noticed that quite some people from "the old days" are kind of waking up now and noticing that how they used the site when they just signed up doesn't work anymore (just look at your recent list of questions, mostly zero or negatively scored). It is kind of a strange phenomenon, I wouldn't be able to say what exactly changed so you would notice that now and not say 5 years ago. You should have noticed it years ago already.
    – Gimby
    Commented Jun 26 at 7:28

0

Reset to default

Browse other questions tagged .