Nightly jobs failing

[tripleee]

Nightlies have been failing since https://github.com/tripleee/sloshy/actions/runs/13557649911

I'm unable to spend time on this at the moment. Sorry.

[Peter-developer01]

It seems that it's mysteriously working again since https://github.com/tripleee/sloshy/actions/runs/13600174561

They still show up as failed because my room (146039) is now deleted, sorry about that.

[Peter-developer01]

I opened a pull request to (hopefully temporarily) remove my room from the YAML file: #117

[tripleee]

It seems that ChatExchange now unconditionally requires JavaScript on chat.stackexchange.com. For the time being, chat.stackoverflow.com seems to work with the current Sloshy client. Really not sure yet whether I should take the plunge and try to support this, or just declare StackExchange unsupported, with condolences.

[tripleee]

Additional discussion in SOBotics starting earlier but picking up speed around here: https://chat.stackoverflow.com/transcript/message/57945280#57945280

Cocomac points to /<room_id>/events as a possible quick fix.

[adeak]

For the time being, chat.stackoverflow.com seems to work with the current Sloshy client.

That's no longer true, alas. One of our chat.SO rooms has frozen. Sloshy logged about posting a message, but it didn't get through.

[adeak]

Looking at the code:

sloshy/sloshy.py

Lines 635 to 645 in 9964848

	try:
	self.notice(room)
	self.log_notice(
	'Age threshold exceeded; sending a%s thawing notice '
	'to %s' % ('' if age>maxage else 'n expedited',
	room.linked_name), cc=True)
	except ChatActionError as err:
	self.log_error(
	'%s: Age threshold exceeded, but failed to thaw: %s'
	% (room.linked_name, err))
	failures.add(room.id)

the log suggests that the notice had already been sent successfully. But then self.notice(room) -> self.send_chat_message(room, self.generate_chat_message()) -> room.send_message(message) looks fairly robust, and independent from any SO company shenanigans. So it's possible that ChatExchange itself is breaking...

Oh, yeah, reading again this comment:

It seems that ChatExchange now unconditionally requires JavaScript on chat.stackexchange.com.

Odds are this is what's been extended to chat.stackoverflow.com.