Help talk:Cloud Services communication
Is this talk page a Toolforge support forum?
I hope that it can serve that purpose, and you won't slap a {{Not a support forum}} template on it. Because I have a question to ask about this page. Wbm1058 (talk) 04:37, 12 September 2023 (UTC)
- It is not. As per the subject page, the support forums are IRC and the mailing list. Discussing the page itself here is fine. — JJMC89 (T·C) 06:56, 12 September 2023 (UTC)
How to report ERROR: Please report this issue to the Toolforge admins: https://w.wiki/6Zuu errors
On a couple of occasions, I've seen this message at the end of a lengthy list of other error messages when trying to execute a Toolforge command from my PuTTY console.
That strange-looking link sends me to here, the Help:Cloud Services communication page.
This page gives four options to "reach out with questions and join the conversation", but I'm not here to ask a question nor to join a discussion. I'm not here to read stories or blog posts. I'm here to report a system error because the system told me to come here and report a system error.
My first instinct is to cut and paste the lengthy list of error messages from my console so that you can see them. Is that necessary? Or are the same messages also reported to the system administrators? I'm guessing not (why not is a good question) because if they were automatically reported to the system administrators then the system wouldn't be asking me to report them.
I view IRC and Telegram chat as rather clunky mobile phone tools that aren't suited to the purpose of dumping console error logs.
I suppose I could email them. The Cloud list doesn't seem particularly active, and seems to just be used for making top-down announcements. I don't see any history of Toolforge issue reports from users on that list.
Phabricator is for tracking work tasks and software bugs. It's not clear to me that that's the best forum either. "Temporary failure in name resolution" doesn't seem like a bug to me. A hardware failure is not a bug, a disk going full is not a bug, and I'm assuming these are the kind of things happening when I get these console error messages out of the blue when I'm just doing the same things I've been doing for a long time.
So that's why I posted my report here. I come here, and hit a dead end, being presented with no good option for proceeding to submit my console log. -- Wbm1058 (talk) 04:37, 12 September 2023 (UTC)
- Error reports should be raised on Phabricator, and they should include the traceback. T340829 is a good example because it shows the command run as well as the error with traceback. In the case of something that may be temporary, I usually wait a bit to see if the issue persists before reporting though. Ideally, the error message would link directly to Phabricator instead of here. — JJMC89 (T·C) 06:56, 12 September 2023 (UTC)
- Thanks. That's the first time I've seen that form. It says, "Before submitting a bug report, use the search box (top right) to see if your bug has already been reported." That makes sense to me, as it seems hardly efficient for 2 or 3 users to submit phabs reporting the same error within minutes of each other if the system problem is impacting multiple users. A good reason for submitting the report on a village pump where others can see that someone else reported the same error five minutes ago. Searching for "ERROR: Please report this issue to the Toolforge admins", the response is:
- Query Errors
- Unknown search function "ERROR". Supported functions are: all, body, comment, core, title. (To search for a term containing a colon, surround the term in double quotes.)
- After surrounding the colon in quotes, I got this list.
- T340829: "stewardbot k8s pod fails to restart due to an internal server error" did show up as the third item on that list. I guess that's the only phab that's reported such errors to date? -- Wbm1058 (talk) 13:15, 12 September 2023 (UTC)
- Thanks. That's the first time I've seen that form. It says, "Before submitting a bug report, use the search box (top right) to see if your bug has already been reported." That makes sense to me, as it seems hardly efficient for 2 or 3 users to submit phabs reporting the same error within minutes of each other if the system problem is impacting multiple users. A good reason for submitting the report on a village pump where others can see that someone else reported the same error five minutes ago. Searching for "ERROR: Please report this issue to the Toolforge admins", the response is:
I guess English Wikipedia village pump is still the de facto Toolforge support forum
- XTools not working
geohack.toolforge.org not working
- Thursday
Looks like toolforge just crashed.