Re: Discourse down?
Nicholas Jankowski <[email protected]> Wed, 13 Mar 2024 07:31:26 -0400
| Newsgroups | gmane.comp.gnu.octave.maintainers |
|---|---|
| Message-ID | <CALW4+bJcEGnjs_-i0y6KNf50Shke1i-dBw+RBfHEy2DFef8Ctw@mail.gmail.com> |
--===============4529517927484252152== Content-Type: multipart/alternative; boundary="00000000000028bdff0613891e8c" --00000000000028bdff0613891e8c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Looks like it=E2=80=99s operating normally now. On Wed, Mar 13, 2024 at 03:54 Markus M=C3=BCtzel <[email protected]> wr= ote: > The discourse forum is in read-only mode for me currently. Does anyone > else have the same issue? > > Markus > > Am Donnerstag, 01. Februar 2024 um 18:37 Uhr schrieb "John W. Eaton": > > > > OK, it's working again for me. I guess I was too impatient. > > > > jwe > > > > On 2/1/24 12:33, Nicholas Jankowski wrote: > > > it's up for me at the moment. just went to the main page, clicked th= e > > > help section, and clicked a topic. opened fine. > > > > > > On Thu, Feb 1, 2024 at 12:23=E2=80=AFPM John W. Eaton <[email protected] > > > <mailto:[email protected]>> wrote: > > > > > > I can access https://octave.discourse.group > > > <https://octave.discourse.group>, but if I try to view any > > > individual topic, I see an error that says "Sorry, we couldn't lo= ad > > > that > > > topic, possibly due to a connection problem. Please try again. If > the > > > problem persists, let us know." with a "Try Again" button. > > > > > > It's been happening for about 30 minutes so far. > > > > > > Is it just me? > > > > > > This issue also reminds me to ask whether we have a backup of the > > > message data posted to our discourse forum and whether it is > > > possible to > > > run our own instance if necessary? > > > > > > jwe > > > > > > > > > ---------- > > > We are transitioning to a web based forum > > > for maintainer discussions at > > > https://octave.discourse.group/c/maintainers > > > <https://octave.discourse.group/c/maintainers> > > > > > > > > > > > ---------- > > We are transitioning to a web based forum > > for maintainer discussions at > > https://octave.discourse.group/c/maintainers > > > --00000000000028bdff0613891e8c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">Looks like it=E2=80=99s operating normally now.</div><div= ><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On We= d, Mar 13, 2024 at 03:54 Markus M=C3=BCtzel <<a href=3D"mailto:markus.mu= [email protected]">[email protected]</a>> wrote:<br></div><blockquote cla= ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;= border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)= ">The discourse forum is in read-only mode for me currently. Does anyone el= se have the same issue?<br> <br> Markus<br> <br> Am Donnerstag, 01. Februar 2024 um 18:37 Uhr schrieb "John W. Eaton&qu= ot;:<br> ><br> > OK, it's working again for me.=C2=A0 I guess I was too impatient.<= br> > <br> > jwe<br> > <br> > On 2/1/24 12:33, Nicholas Jankowski wrote:<br> > > it's up for me at the moment.=C2=A0 just went to the main pag= e, clicked the <br> > > help section, and clicked=C2=A0a topic. opened fine.<br> > > <br> > > On Thu, Feb 1, 2024 at 12:23=E2=80=AFPM John W. Eaton <<a href= =3D"mailto:[email protected]" target=3D"_blank">[email protected]</a> <br> > > <mailto:<a href=3D"mailto:[email protected]" target=3D"_blank">jw= [email protected]</a>>> wrote:<br> > > <br> > >=C2=A0 =C2=A0 =C2=A0I can access <a href=3D"https://octave.discour= se.group" rel=3D"noreferrer" target=3D"_blank">https://octave.discourse.gro= up</a><br> > >=C2=A0 =C2=A0 =C2=A0<<a href=3D"https://octave.discourse.group"= rel=3D"noreferrer" target=3D"_blank">https://octave.discourse.group</a>>= ;, but if I try to view any<br> > >=C2=A0 =C2=A0 =C2=A0individual topic, I see an error that says &qu= ot;Sorry, we couldn't load<br> > >=C2=A0 =C2=A0 =C2=A0that<br> > >=C2=A0 =C2=A0 =C2=A0topic, possibly due to a connection problem. P= lease try again. If the<br> > >=C2=A0 =C2=A0 =C2=A0problem persists, let us know." with a &q= uot;Try Again" button.<br> > > <br> > >=C2=A0 =C2=A0 =C2=A0It's been happening for about 30 minutes s= o far.<br> > > <br> > >=C2=A0 =C2=A0 =C2=A0Is it just me?<br> > > <br> > >=C2=A0 =C2=A0 =C2=A0This issue also reminds me to ask whether we h= ave a backup of the<br> > >=C2=A0 =C2=A0 =C2=A0message data posted to our discourse forum and= whether it is<br> > >=C2=A0 =C2=A0 =C2=A0possible to<br> > >=C2=A0 =C2=A0 =C2=A0run our own instance if necessary?<br> > > <br> > >=C2=A0 =C2=A0 =C2=A0jwe<br> > > <br> > > <br> > >=C2=A0 =C2=A0 =C2=A0----------<br> > >=C2=A0 =C2=A0 =C2=A0We are transitioning to a web based forum<br> > >=C2=A0 =C2=A0 =C2=A0for maintainer discussions at<br> > >=C2=A0 =C2=A0 =C2=A0<a href=3D"https://octave.discourse.group/c/ma= intainers" rel=3D"noreferrer" target=3D"_blank">https://octave.discourse.gr= oup/c/maintainers</a><br> > >=C2=A0 =C2=A0 =C2=A0<<a href=3D"https://octave.discourse.group/= c/maintainers" rel=3D"noreferrer" target=3D"_blank">https://octave.discours= e.group/c/maintainers</a>><br> > > <br> > <br> > <br> > <br> > ----------<br> > We are transitioning to a web based forum<br> > for maintainer discussions at<br> > <a href=3D"https://octave.discourse.group/c/maintainers" rel=3D"norefe= rrer" target=3D"_blank">https://octave.discourse.group/c/maintainers</a><br= > ><br> </blockquote></div></div> --00000000000028bdff0613891e8c-- --===============4529517927484252152== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline Ci0tLS0tLS0tLS0KV2UgYXJlIHRyYW5zaXRpb25pbmcgdG8gYSB3ZWIgYmFzZWQgZm9ydW0KZm9y IG1haW50YWluZXIgZGlzY3Vzc2lvbnMgYXQKaHR0cHM6Ly9vY3RhdmUuZGlzY291cnNlLmdyb3Vw L2MvbWFpbnRhaW5lcnMK --===============4529517927484252152==--