frigginglorious has quit [Ping timeout: 260 seconds]
<ocdtrekkie>
I'm honestly curious who has kept my Wekan grain open for nearly a month now.
<ocdtrekkie>
asheesh, I have to install all this :stuff: on my Windows box to test this.
<ocdtrekkie>
And I have to :reboot: even.
<ocdtrekkie>
Note that while Vagrant puts itself in the system's PATH, VirtualBox does not, and I did that manually.
digitalcircuit has quit [Quit: Moving server across rooms, be back in under an hour unless things explode]
<ocdtrekkie>
Currently downloading crud, so reboot will have to wait a bit.
frigginglorious has joined #sandstorm
jadewang has joined #sandstorm
digitalcircuit has joined #sandstorm
AsheeshRoam has joined #sandstorm
<AsheeshRoam>
Howdy all, e.g. ocdtrekkie. I'm surprised you need to put VirtualBox on the %PATH%. Does Vagrant give you an error that motivated you to do that, or was it just that you felt it was sensible to do that in general?
<ocdtrekkie>
Your insturctions suggested I check VirtualBox --help to confirm it's installed.
<ocdtrekkie>
That command would only work if it was in my path. Or I felt like navigating to that folder. But suffice, I assumed it should be in path based on this.
<AsheeshRoam>
Oh, hah, right, OK (-:
<ocdtrekkie>
Okay, so, AsheeshRoam, VAGRANT_SPK_EXPERIMENTAL is not recognized by Windows as a valid command.
<ocdtrekkie>
Looking at that step I was fairly confident that would be the result before I ran it.
<AsheeshRoam>
Oh right
<AsheeshRoam>
You don't need it anymore anyway.
<AsheeshRoam>
Remove the VAGRANT_SPK_EXPERIMENTAL=Y from the command and try again.
<ocdtrekkie>
I'm using the version of vagrant-spk that was in your filedrop
<AsheeshRoam>
Oh, sensible, but now you can use the release build.
<AsheeshRoam>
Alternatively I can learn about Windows environment variables.
<AsheeshRoam>
Looks like SET should be involved
<AsheeshRoam>
SET VAGRANT_SPK_EXPERIMENTAL=Y
<AsheeshRoam>
in cmd. Then run vagrant-spk w/o the VAGRANT_SPK_EXPERIMENTAL=Y
<AsheeshRoam>
That idiom should embody the same meaning as my bash-centric idiom I'm using in the doc.
<AsheeshRoam>
ocdtrekkie ^ no need to install anything new.
<ocdtrekkie>
I doubt that worked, because it doesn't show in my environment variables table.
<ocdtrekkie>
But I'll add it with the System control panel.
<AsheeshRoam>
It should be local within the bash that way, fwiw.
<AsheeshRoam>
I'm +1 on us working through using SET, but if it takes us longer than 15 min, then it might be smart to switch to a strategy involving testing the most recent released installer.
<ocdtrekkie>
Does vagrant-spk update cleanly with the setup file?
<AsheeshRoam>
(which won't need the environment variable for vagrant-spk)
<AsheeshRoam>
Yeah, it's supposed to at least, although I haven't tested it extensively. But I do believe so.
<AsheeshRoam>
Others report yes, anyway.
<ocdtrekkie>
Why is local.sandstorm.io still running after I Ctrl-C out of vagrant-spk?
<AsheeshRoam>
Because VirtualBox is a system process that "vagrant-spk vm up" launches.
<AsheeshRoam>
"vagrant-spk vm halt" will stop it.
<AsheeshRoam>
I said "system process" in an attempt to sound more Windows-y than "daemon" or "forked background process", which is what I'd say on Linux.
<ocdtrekkie>
Your instructions did not tell me how to stop running it. :P
frigginglorious has quit [Ping timeout: 244 seconds]
<AsheeshRoam>
That is honestly kind of interesting.
<AsheeshRoam>
But great (-:
<ocdtrekkie>
I ran the vagrant-spk installer, and I can't tell if it updated vagrant-spk.exe or not, because the date modified is like when you compiled it. Not when I installed it.
<ocdtrekkie>
The "Details" page in Windows for vagrant-spk.exe doesn't have the version field filled in.
<AsheeshRoam>
vagrant-spk --help
<ocdtrekkie>
That's not a very Windows-y way to check. :P
<AsheeshRoam>
should now show "enter-grain" as an option, if you have the newer build
<AsheeshRoam>
Yeah, using the version field would be smart.
<ocdtrekkie>
Also, Windows SmartScreen hates your app because it isn't signed and probably because of some of the things it does.
<AsheeshRoam>
: D yeah I need to work on the signing.
<ocdtrekkie>
I have to click on a tiny "more info" and then "Run anyway" amongst scary warnings.
frigginglorious has joined #sandstorm
<ocdtrekkie>
Same error message with the new version that I sent private to you.
<AsheeshRoam>
"sweet"
<AsheeshRoam>
The one error that I thought might occur, did occur.
<AsheeshRoam>
So that's interesting. I guess \r\n <=> \n corruption is happening.
<AsheeshRoam>
Maybe I can mark the file as binary in the installer thing to avoid this.
<AsheeshRoam>
Can you find the "enter-grain" and "enter-grain.sha1" files in c:\progra~1\vagrant-spk and filedrop them?
<AsheeshRoam>
It could be that the files aren't corrupted, but my Python code is corrupting them in memory.
<AsheeshRoam>
I'm grateful that you're willing to test this so that we can run into this problem with you, rather than with someone less willing to report the issues.
<ocdtrekkie>
Do you prefer FileDrop over Davros for such things?
<AsheeshRoam>
Shrug City
<AsheeshRoam>
I'm OK with any of Davros, FileDrop, GitHub issue upload
<ocdtrekkie>
I will note, the sample data, as with Etherpad, makes the choice of Davros mildly more tedious, in fairness.
<ocdtrekkie>
But I don't have FileDrop installed.
<AsheeshRoam>
I don't fully understand your note. Explain?
<ocdtrekkie>
When I make a new Davros grain, there's two graphics and an md file in there.
<AsheeshRoam>
Oh, right.
<ocdtrekkie>
I feel compelled to delete them, and Davros doesn't have multiselect or delete from the file list yet.
<AsheeshRoam>
You can "delete the folder" within Davros and then you can reload the page to make Davros recreate its main folder.
<AsheeshRoam>
That's a bit clunky though.
<AsheeshRoam>
Also wow, kiwiirc really is pretty good.
<AsheeshRoam>
Also wow, huh, 105 users.
<ocdtrekkie>
These are in program files
<ocdtrekkie>
\vagrant-spk\helpers
<ocdtrekkie>
FWIW
<ocdtrekkie>
I was confused, I couldn't find it.
<ocdtrekkie>
Is there security concerns for the sha1 file?
<ocdtrekkie>
Files are shared with you.
<ocdtrekkie>
Oh, that's just the hash of the enter-grain file. Makes sense.
<AsheeshRoam>
No security concerns for the sha1 file; it's a checksum that is public.
<AsheeshRoam>
Yeah (-:
<AsheeshRoam>
It's too bad that this doesn't work, but I am pretty happy that it self-tested and detected the insanity rather than failing later down the process in a more incomprehensible way.
<AsheeshRoam>
...
<AsheeshRoam>
I think it actually is broken for everyone, and I didn't notice maybe.
<AsheeshRoam>
If you edit the enter_grain.sha1 file to only have the hex contents, not the " enter_grain" suffix, do things work?
<ocdtrekkie>
Got further. Slightly.
<AsheeshRoam>
"Yay"
<AsheeshRoam>
It's too bad I write code with bugs. It makes estimating the durations of projects more difficult.
<AsheeshRoam>
(-:
<AsheeshRoam>
There's a new error message?
<ocdtrekkie>
There is.
<AsheeshRoam>
oh
<ocdtrekkie>
I quoted it on Github so far.
<ocdtrekkie>
:P
frigginglorious has quit [Ping timeout: 260 seconds]
<AsheeshRoam>
How much patience do you have for me using you as a remote try-stuff-on-Windows oracle? I could alternatively go to a Windows box, but if you're OK with it, I admit I prefer telling you to try things, and learning from that.
<ocdtrekkie>
I am okay with it.
<AsheeshRoam>
Sweet.
frigginglorious has joined #sandstorm
<AsheeshRoam>
OK I made a grain and shared with you (-:
<AsheeshRoam>
ocdtrekkie: y u no run commands and give me output in the doc
<ocdtrekkie>
Working on it.
<AsheeshRoam>
yay
<ocdtrekkie>
Also, try not to hose my computer. :P
frigginglorious has quit [Ping timeout: 252 seconds]
<AsheeshRoam>
OK (-:
<ocdtrekkie>
Do you want me to run the bottom one now?
<AsheeshRoam>
Ya
<AsheeshRoam>
Aw man
<AsheeshRoam>
And are you doing the 'vagrant-spk dev' thing right now?
<AsheeshRoam>
Sure looks like you are, OK.
<ocdtrekkie>
Yeah, that's running in another cmd.
<AsheeshRoam>
Great.
<AsheeshRoam>
OK I'm going to take 5 min to try to research something here; will ping you when I have more commands for you; keep everything running for now if that's OK.
<ocdtrekkie>
k
frigginglorious has joined #sandstorm
<ocdtrekkie>
Just realized you moved your line, AsheeshRoam
<ocdtrekkie>
I need to make a ten minute errand, but I ran your newer commands.
<AsheeshRoam>
cool
<AsheeshRoam>
Interesting; I'm not really sure what is going on, butt I can try pushing a maybe-fix that minimizes the chance of some errors here.
<AsheeshRoam>
I'll have to build a new installer to have you test that.
jadewang has quit [Remote host closed the connection]
frigginglorious has quit [Quit: frigginglorious]
jemc has joined #sandstorm
AsheeshRoam has joined #sandstorm
AsheeshRoam has quit [Client Quit]
<asheesh>
ocdtrekkie: I estimate that if I am able to provide you a new binary, it'll be 1h from now. If you want to be awake then, well cool, but just so you know!
jemc has quit [Quit: WeeChat 1.4]
jemc has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 240 seconds]
frankier has joined #sandstorm
<ocdtrekkie>
I might still be awake.
jemc has quit [Ping timeout: 260 seconds]
jadewang has joined #sandstorm
<asheesh>
ocdtrekkie: I will timebox this at 15 min since I am getting tired myself!
<ocdtrekkie>
I can maybe stay awake 15 more minutes.
sydney_untangle has quit [Ping timeout: 272 seconds]
sydney_untangle has joined #sandstorm
isd has quit [Remote host closed the connection]
frankier has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 250 seconds]
gelnior54 has quit [Remote host closed the connection]
gelnior54 has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 260 seconds]
jadewang has joined #sandstorm
frankier has quit [Ping timeout: 244 seconds]
jadewang has quit [Ping timeout: 264 seconds]
mnutt_ has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 244 seconds]
rgrinberg has joined #sandstorm
frankier has joined #sandstorm
frankier has quit [Remote host closed the connection]
frankier has joined #sandstorm
dwrensha has quit [Remote host closed the connection]
<mnutt_>
anyone know what the likelihood of sandstorm servers having atime enabled is? I'm implementing thumbnail cache eviction, planning on using atime and falling back on mtime but atime is preferable
<asheesh>
I would guess 99% of servers have atime or relatime
<asheesh>
I would guess 1% or fewer have noatime
<asheesh>
There's no data behind this estimate, though, just my usual hunches about how people configure things.
<asheesh>
And the fact that Sandstorm is often the only thing on a server so it uses Linux distribution defaults.
rgrinberg has quit [Quit: WeeChat 1.5]
rgrinberg has joined #sandstorm
jadewang has joined #sandstorm
frigginglorious has joined #sandstorm
jadewang has quit [Ping timeout: 252 seconds]
jemc has joined #sandstorm
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 252 seconds]
dwrensha has joined #sandstorm
dwrensha_ has joined #sandstorm
dwrensha has quit [Ping timeout: 260 seconds]
dwrensha_ is now known as dwrensha
jemc has quit [Quit: WeeChat 1.4]
jadewang has joined #sandstorm
jadewang has quit [Ping timeout: 240 seconds]
rustyrazorblade has joined #sandstorm
jadewang has joined #sandstorm
wolcen has joined #sandstorm
wolcen_ has joined #sandstorm
wolcen has quit [Client Quit]
wolcen_ is now known as wolcen
jadewang has quit [Remote host closed the connection]
jadewang has joined #sandstorm
wolcen has quit [Ping timeout: 240 seconds]
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
rgrinberg has quit [Ping timeout: 276 seconds]
rgrinberg has joined #sandstorm
jadewang has quit [Remote host closed the connection]
mnutt_ has joined #sandstorm
rustyrazorblade has quit [Ping timeout: 244 seconds]
rustyrazorblade has joined #sandstorm
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
rgrinberg has quit [Quit: WeeChat 1.5]
rgrinberg has joined #sandstorm
wolcen has joined #sandstorm
mnutt_ has joined #sandstorm
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
wolcen has quit [Ping timeout: 272 seconds]
rgrinberg has quit [Ping timeout: 264 seconds]
rgrinberg has joined #sandstorm
amyers has joined #sandstorm
rustyrazorblade has quit [Ping timeout: 244 seconds]
rustyrazorblade has joined #sandstorm
wolcen has joined #sandstorm
jadewang has joined #sandstorm
rustyrazorblade has quit [Ping timeout: 258 seconds]
rustyrazorblade has joined #sandstorm
rustyrazorblade has quit [Ping timeout: 246 seconds]
wolcen has quit [Ping timeout: 260 seconds]
rustyrazorblade has joined #sandstorm
amyers has quit [Ping timeout: 250 seconds]
isd has joined #sandstorm
frankier has quit [Ping timeout: 240 seconds]
isd has quit [Quit: Leaving.]
mnutt_ has joined #sandstorm
rustyrazorblade has quit [Ping timeout: 260 seconds]
rustyrazorblade has joined #sandstorm
rustyrazorblade has quit [Read error: Connection reset by peer]
rgrinberg has quit [Ping timeout: 244 seconds]
rustyrazorblade has joined #sandstorm
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
decipherstatic has quit [Ping timeout: 272 seconds]
frigginglorious has quit [Quit: frigginglorious]
rustyrazorblade has quit [Read error: Connection reset by peer]
decipherstatic has joined #sandstorm
rustyrazorblade has joined #sandstorm
jadewang has quit [Remote host closed the connection]
jadewang has joined #sandstorm
jadewang has quit [Remote host closed the connection]
rustyrazorblade has quit [Read error: Connection reset by peer]
rustyrazorblade has joined #sandstorm
jadewang has joined #sandstorm
gwillen is now known as gwiIIen
gwiIIen is now known as gwilIen
gwilIen is now known as gwiIlen
gwiIlen is now known as gwillen
gwillen is now known as gwil1en
gwil1en is now known as gwi1len
gwi1len is now known as gwi11en
gwi11en is now known as gwillen
rustyrazorblade has quit [Ping timeout: 260 seconds]
gwillen is now known as gwiI1en
gwiI1en is now known as gwi1Ien
gwi1Ien is now known as gwillen
rustyrazorblade has joined #sandstorm
rustyrazorblade has quit [Ping timeout: 250 seconds]