Vyxal

user

00:43

@lyxal Do you want me to try setting up the basic framework for a debugger for v3? (after I'm done with finals, that is)

lyxal

if you want :+1:

user

I know I've done literally nothing for Vyxal recently but I'll have more time in the summer

pog

emanresu A

00:58

Header buttons are broken on firefox

lyxal

01:10

github.com/FortAwesome/Font-Awesome/issues/17402

@emanresuA it's a fontawesome problem

kit.fontawesome.com/646af2e33b.js

errors

also not loading in duckduckgo native app

also not loading in edge

status-not-our-problem

Dannyu NDos

Is it just me, or is "Vyxal" actually cool in pronunciation?

lyxal

as intended :p

but seriously, sounding cool is 100% intended

Dannyu NDos

01:26

As a South Korean, I pronounce it [vik.sal], and the [sal] sounds like it's gonna kill something.

Kill old paradigms? Idk

lyxal

[vaɪk.sal] is how I pronounce it

Seggan

i do vaijk sal

lyxal

@lyxal 3 years ago I sat thinking about the name, and I thought "my username already sounds pretty cool might as well just slap a v at the front instead of an L"

that's literally it

it's not egocentric nor is it intended to be an ownership thing

it just sounds cool

Seggan

right i just did the dumbest thing imaginable

i put my se password on github

lyxal

sounds like you better change the password then

Seggan

01:35

yeah

emanresu A

Or nuke the repo

Seggan

already did

emanresu A

docs.github.com/en/authentication/…

Seggan

ty

Seggan

02:01

public again

ive squashed the bad commits

Razetime

04:54

github.com/advisories/GHSA-h3qr-39j9-4r5v/…

seems there's some vulnerability on myxal.

The Thonnu

09:13

@lyxal ready to merge?

lyxal

10:11

@TheThonnu depends if the system exit thing is going to work on all 3 platforms

Where's @user when you need user :p

Ginger

11:25

whelp, I guess Vyxal Bot's gonna be down for a while

sorry yall

lyxal

11:37

wasn't that a rydwolf problem?

Ginger

yes

~~again~~

lyxal

how easy is it to switch to a new provider? like a new host server?

Ginger

nontrivial, especially because the all-important config file is only on Rydwolf's server

lyxal

:+1: I'll see if hyper can host the bot again

would you consider sticking with hyper hosting?

Ginger

look, this is just a temporary issue

it'll be fixed in a few days, I think

no need to panic

lyxal

11:40

well just know that hyper hosting could always be an option

Ginger

right

lyxal

it'd mean we'd be fully reliant on vyxal members for our own stuff again

and while there's nothing wrong with rydwolf hosting, self sufficiency can be nice :p

Ginger

it'd just be moving from one server to another

if hyper's house gets struck by lightning I'm no better off

lyxal

that's not what I meant

I more mean no 3rd party dependencies :p

Ginger

I know what you meant, my point is that there'd be no difference and therefore it is not worth the effort

lyxal

11:43

~~no difference to you~~

Ginger

the only difference between Rydwolf's and hyper's servers is who owns them

and that is not an important difference to me

lyxal

as I said

no difference to you

somewhat of a non-trivial difference to me

Ginger

you think hyper's more reliable than rydwolf???

lyxal

hyper is one of us

rydwolf isn't

just a small pedantic thing really

Ginger

there is no "one of us", lyxal

rydwolf is my friend, I trust him to host this bot

lyxal

11:47

it's not a trust thing

it's more of a "there was originally a bit of bad history that I've 99.9% gotten over"

Ginger

I was not aware of that?

what exactly are you talking about

lyxal

rydwolf used to be our greatest critic

emphasis on used

Ginger

huh, really?

lyxal

and as I said, I've 99.9% dealt with that, but every now and again it just feels a little bad still

Ginger

~~link or it didn't happen~~

lyxal

11:49

@Ginger 2021 was wild times

@Ginger one second

Ginger

well, I guess that's understandable

but I doubt that Rydwolf'll kill VB just because of a bit of bad history

lyxal

in The Nineteenth Byte, Sep 1, 2021 at 2:27, by Browncat Programs

@BrowncatPrograms I do have a mild case of "vyxal bad" syndrome :p

@Ginger oh no it's not a trust thing at all

I know for a fact he won't

it's just a slight bit of residual hurt from that period of time

Ginger

hm

well, I'm going to continue hosting with Rydwolf

but I understand where you're coming from now

lyxal

:+1:

I don't have a problem with where's it hosted at all. There's just a very tiny bit of me that would prefer hyper for that reason. Which is like 0.00001% of me

(it's not a grudge or any hard feelings at all. I like rydwolf and enjoy chatting with him. It's just a small feeling that hasn't seemed to have gone away)

@user now is that cross-platform or is JS and Native gonna throw a yikes about it?

because you know how fussy those two versions can be about jvm stuff :p

heh? Did I manage to forget to add Q?

how tf did I manage that?

mustn't have saved it

Referring to non-existent method static java.lang.System.exit(int)void
[error]   called from private vyxal.impls.Elements$Impls$.$init$$$anonfun$13(vyxal.Context)void
[error]   called from private vyxal.impls.Elements$Impls$.$init$$$anonfun$adapted$5(vyxal.Context)java.lang.Object
[error]   called from constructor vyxal.impls.Elements$Impls$.<init>()void
[error]   called from constructor vyxal.impls.Elements$.<init>()void
[error]   called from vyxal.Interpreter$.execute(vyxal.AST,vyxal.Context)void

And there we have it

System.exit only works on JVM

user

19:45

Yeah JS doesn't really have a nice way to exit

You can throw '' in JS apparently but that sucks

Might I suggest making a VyxalQuit exception or something and then catching that?

By catching it, you can still do some extra handling afterwards if necessary

Oh wait you're alread;y throwing nvm

Transcript for