<pikajude>
has anyone here ever had success creating a cookie with EditThisCookie?
eligrey has quit [Read error: Connection reset by peer]
Rurik has joined #elliottcable
Rarik has joined #elliottcable
Rurik has quit [Ping timeout: 276 seconds]
Rarik has quit [Ping timeout: 252 seconds]
Rurik has joined #elliottcable
thealphanerd has quit [Quit: farewell for now]
thealphanerd has joined #elliottcable
Sorella has quit [Quit: Connection closed for inactivity]
Sgeo__ has quit [Ping timeout: 240 seconds]
gkatsev has quit [Ping timeout: 264 seconds]
gkatsev has joined #elliottcable
gkatsev has quit [Ping timeout: 250 seconds]
gkatsev has joined #elliottcable
Rurik has quit [Ping timeout: 252 seconds]
Rurik has joined #elliottcable
aredride- has quit [Ping timeout: 258 seconds]
aredridel has joined #elliottcable
Rarik has joined #elliottcable
Rurik has quit [Ping timeout: 240 seconds]
Sorella has joined #elliottcable
<pikajude>
so uh
<pikajude>
I think node is trying to cause my stress-induced suicide
<jfhbrook>
how do you figure
<jfhbrook>
like what are you running into
<jfhbrook>
idk what EditThisCookie is, if that's what you're fighting
<pikajude>
jfhbrook: my tests have been failing for 3 days because i'm setting an environment variable and mocha is flat out ignoring it
<pikajude>
like it doesnt get set
<pikajude>
like if I set it in the test itself it doesn't get set
<jfhbrook>
I, uhh, what?
<jfhbrook>
where are you setting it?
<pikajude>
outside the test, in the first line of the test, in the line before it's printed to the user
<pikajude>
i'm pretty sure i'm going fucking nuts
<pikajude>
either i'm editing the wrong file or i accidentally put a zwnbsp in the name of the variable somewhere
<pikajude>
but i'm running `gtest foo` and then to hack on it i'm doing `vim $(which gtest)`
<pikajude>
so I don't understand how it can be happening
<pikajude>
this was happening yesterday too where I was writing a beforeRequest event handler that was being ignored
<pikajude>
but that was because in our tests we were replacing the entire fucking app object for one specific test
<pikajude>
and that can't be the case here
<jfhbrook>
it does look like process.env is mutable
<jfhbrook>
though that's kind of a weird pattern, overwriting env vars like that
<jfhbrook>
one suggestion is to refactor
<jfhbrook>
so you don't have to override process.env specifically, but instead some kind of config object
<jfhbrook>
beyond that, you're doing it outside any describe or it blocks?
<jfhbrook>
you might want to do it *inside* an if block, to ensure it gets ran before whatever uses it
<jfhbrook>
oh, also one idea is
<jfhbrook>
if you have a require that reads process.env on init, you'd have to do process.env.NODE_FOO='bar'; const thing = require('./thing') rather than the reverse
<jfhbrook>
er, might have to do
<pikajude>
well jfhbrook, this wouldn't be a problem if I could set things inside process.env
<pikajude>
because I would just set them
<pikajude>
but uh, i can't
<jfhbrook>
what do you mean
<jfhbrook>
I just checked in the repl, process.env is mutable
<jfhbrook>
I bet you're doing this.thing = process.env.THING somewhere, before you're punching process.env.THING
<pikajude>
i would totally agree. except what i'm doing is process.env['REPLAY'] = 'bloody'; console.log("Replay: " + process.env['REPLAY']);
<pikajude>
Replay: record
<jfhbrook>
show me
<jfhbrook>
or maybe don't, I have to go to the meeting from hell in a few minutes
eligrey has joined #elliottcable
eligrey has quit [Read error: Connection reset by peer]
wraithgar has joined #elliottcable
Sgeo__ has joined #elliottcable
Sgeo__ has quit [Read error: Connection reset by peer]