SME broken by zas "update"

[D3athrow-Issues]

(WEB REPORT BY: bobthomas REMOTE: 172.93.109.202:7777)

Revision

9ef74e808f59b43bd5a9e97f02ba2477c6afc572

Description

zas "update" broke all known configurations of SME

Steps to Reproduce

try to use the SME without it blowing up

What you Expected

self explanatory

What Actually Happened

self explanatory

[PJB3005]

Challenge accepted.

[MadmanMartian]

how is this self explanatory?

what has broken?

[jknpj]

I swear to god these reports get worse every day

[PJB3005]

I want to say we peaked when somebody made 10 issues being aware of spamming but you know...

On 1 Dec 2017 17:29, "jknpj" notifications@github.com wrote:

I swear to god these reports get worse every day

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vgstation-coders/vgstation13/issues/16661#issuecomment-348540920, or mute the thread https://github.com/notifications/unsubscribe-auth/AHu1wzEHE7P31_zwCR7sHxY8BW5m71EDks5s8ClYgaJpZM4QyaPB .

[Exxion]

How in the blazing fuck did the R-UST being broken get reported before the SME? And by quite a while, too

Anyway, I can probably fix this one later tonight, but I still don't know jack shit about the R-UST

[PJB3005]

Yeah I think we can ignore this issue it's probably full of shit. I just built this on the test server.

[PJB3005]

[Exxion]

Does the test server even have the update yet? I'm not sure how far out of date out is right now. But that would explain it not getting reported yet.

[PJB3005]

@Exxion I just checked and it has Unid's Zathura vault so it's at LEAST at 6aa5e230f3bc1255d9bda36cef6395d3e820f0bf

[PJB3005]

Yeah unless somebody credible has evidence of the SME being broken I'm just closing this.