I cannot open the .NET tutorial 1 page

[acsgunc]

Describe the bug

RabbitMQ queues Queue for .Net example page is crashing
try to open below page, then you can reproduce this issue
https://www.rabbitmq.com/tutorials/tutorial-one-dotnet

Reproduction steps

1. go to https://www.rabbitmq.com/tutorials#queue-tutorials
2. click on C# at link at queue
3. or open this page https://www.rabbitmq.com/tutorials/tutorial-one-dotnet
   ...

Expected behavior

the page should open https://www.rabbitmq.com/tutorials/tutorial-one-dotnet without crashing

Additional context

No response

[michaelklishin]

@acsgunc it works just fine for me in Chrome, including in a private browsing window.

[acsgunc]

Please open this site https://www.rabbitmq.com/tutorials/tutorial-one-dotnet

[michaelklishin]

@acsgunc what do you think I did?

[michaelklishin]

Given that Docusaurus usually fails at build time with any serious problem that has nothing to do with cascading stylesheets, and you are the first person to report this, I highly doubt that this is a systemic issue.

More likely something in your environment blocks loading of some JS files, which Docusaurus relies on very heavily.

[acsgunc]

https://www.rabbitmq.com/tutorials/tutorial-one-dotnet opening this gives below error
Objects are not valid as a React child (found: TypeError: Failed to fetch). If you meant to render a collection of children, use an array instead.

I am getting above error.

Same time of error, when i build and open locally

but
https://www.rabbitmq.com/tutorials/tutorial-one-java
this site opens perfectly

[michaelklishin]

@acsgunc I have asked several people in different countries and no one but you can reproduce this. No one else has reported it either, despite a few millions of page views on the site, a non-trivial percentage of which is the tutorials.

[acsgunc]

       GET https://raw.githubusercontent.com/rabbitmq/rabbitmq-tutorials/main/dotnet/Send/Send.cs net::ERR_CONNECTION_RESET

apply @ t.js:1
t.fetchCode @ 18627.07b082a2.js:1
t.default @ 18627.07b082a2.js:1
hi @ main.59fa20a1.js:2
Sc @ main.59fa20a1.js:2
yd @ main.59fa20a1.js:2
gd @ main.59fa20a1.js:2
hd @ main.59fa20a1.js:2
cd @ main.59fa20a1.js:2
Ua @ main.59fa20a1.js:2
(anonymous) @ main.59fa20a1.js:2
t.js:1

       GET https://raw.githubusercontent.com/rabbitmq/rabbitmq-tutorials/main/dotnet/Receive/Receive.cs net::ERR_CONNECTION_RESET

apply @ t.js:1
t.fetchCode @ 18627.07b082a2.js:1
t.default @ 18627.07b082a2.js:1
hi @ main.59fa20a1.js:2
Sc @ main.59fa20a1.js:2
yd @ main.59fa20a1.js:2
gd @ main.59fa20a1.js:2
hd @ main.59fa20a1.js:2
cd @ main.59fa20a1.js:2
Ua @ main.59fa20a1.js:2
(anonymous) @ main.59fa20a1.js:2

main.59fa20a1.js:2 Error: Objects are not valid as a React child (found: TypeError: Failed to fetch). If you meant to render a collection of children, use an array instead.
at P (main.59fa20a1.js:2:43624)
at A (main.59fa20a1.js:2:43901)
at Object.toArray (main.59fa20a1.js:2:44636)
at 18627.07b082a2.js:1:17412
at H (18627.07b082a2.js:1:17490)
at hi (main.59fa20a1.js:2:141679)
at Es (main.59fa20a1.js:2:155730)
at Sc (main.59fa20a1.js:2:201515)
at yd (main.59fa20a1.js:2:189896)
at gd (main.59fa20a1.js:2:189824)
us @ main.59fa20a1.js:2
r.componentDidCatch.n.callback @ main.59fa20a1.js:2
Hr @ main.59fa20a1.js:2
xc @ main.59fa20a1.js:2
yc @ main.59fa20a1.js:2
vc @ main.59fa20a1.js:2
(anonymous) @ main.59fa20a1.js:2
_d @ main.59fa20a1.js:2
ad @ main.59fa20a1.js:2
w @ main.59fa20a1.js:2
A @ main.59fa20a1.js:2

this is the error in browser console

[mkuratczyk]

Our tutorial pages reference some of the code on github. Given this error:

GET https://raw.githubusercontent.com/rabbitmq/rabbitmq-tutorials/main/dotnet/Receive/Receive.cs net::ERR_CONNECTION_RESET`

it looks like there's some, probably temporary, issue when your browser tries to fetch that code from Github. There's very little context here, but perhaps this Github service disruption is related: https://www.githubstatus.com/incidents/gxf0jzns6rn2

The error is between your browser and Github, so there's not much we can do about it. We'd need to completely reorganize those tutorials (copy-paste the code or something) to avoid the risk of such problem and given it's the first time anyone reported it in ~1.5 years since we moved to Docusaurus, that sounds like a lot of work to avoid a very rare issue.