asheesh changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Channel glossary: "i,i" means "I have no point, I just want to say". b == thumbs up. | Public logs at https://botbot.me/freenode/sandstorm/ & http://logbot.g0v.tw/channel/sandstorm/today
<abnd> @asheesh *facepalm* I wasn't forking uwsgi in the background so nginx never ran
<abnd> Thanks!
afuentes has joined #sandstorm
aeviator has joined #sandstorm
aeviator has quit [Ping timeout: 276 seconds]
<asheesh> abnd: You're very welcome! Easy mistake to make; glad you caught it! BTW what's the app, if I may ask? : )
<asheesh> I'm also one of the main authors of the docs, so if there's anything I could have done to help you solve your problem faster, please do let me know.
<asheesh> The answer isn't always "more docs" -- maybe a Sandstorm change or some logging info or something similar might have helped. Feel free to say anything that comes to mind.
<abnd> Throwing an error when the http connection to the grain was refused might have helped, although this was a silly mistake on my end
<abnd> Great job on the docs, very helpful!
<abnd> I'm just getting started on writing a todo list/task management app along with a companion Android app, that's one thing I would love to use on sandstorm
<asheesh> On connection-refused, interesting.
<asheesh> A difficulty is that connection-refused does happen on grain start, so then we don't know exactly how long to wait.
<asheesh> e.g. if a Java-based app takes 30 seconds to launch and bind its port
<asheesh> One thing I'd like to see, I think, is a configurable timeout in .sandstorm/sandstorm-pkgdef.capnp for waitThisManySecondsBeforeConnectionRefusedSeemsLikeARealProblem
<asheesh> And/or we could do something different in dev mode.
<abnd> Yeah I could be a "developer mode" only thing, if such a thing exists
<asheesh> Out of curiosity, (approx) how long did you wait for the grain to start properly?
<asheesh> And also, is there something we could have printed on the 'vagrant-spk dev' console that might have helped?
<asheesh> That's probably the easiest place to put this info, fwiw.
<abnd> I did give it multiple minutes for sure, multiple "** SANDSTORM SUPERVISOR: Grain still in use; staying up for now." were in the debug log
<digitalcircuit> asheesh: Belatedly, thanks for the compliment on that bug report :)
<abnd> Maybe the http check could go in the debug log, when sandstorm prints the "grain in use" message
isd has quit [Ping timeout: 258 seconds]
NhanH has quit [Ping timeout: 264 seconds]
cstrahan has quit [Ping timeout: 260 seconds]
daemoen has quit [Quit: No Ping reply in 180 seconds.]
daemoen has joined #sandstorm
lukexj has joined #sandstorm
cstrahan has joined #sandstorm
NhanH has joined #sandstorm
<geemili> @asheesh I installed it, but no. I'm not really using it.
<geemili> And I installed it for Ubuntu, but since it requires VirtualBox, I probably should have installed it for Windows
<asheesh> Ah hah, OK : )
<geemili> I thought that it would be easier to just develop with out it, but it's not. :(
lukexj has quit [Ping timeout: 252 seconds]
<asheesh> Yeah geemili; alas. |:
aeviator has joined #sandstorm
geemili has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
<asheesh> Hey abnd - do you have a GitHub account? I want to thank you for suggesting the debug log idea!
aeviator has quit [Ping timeout: 260 seconds]
<abnd> asheesh: https://github.com/abhinandh is me. Thanks for such a quick fix!
<asheesh> You're welcome. We'll see what kentonv thinks once he gets a chance to look at it. Moreover, do you think this specific fix would have helped you?
<asheesh> !! OK I guess all he said is "Merged" :D
<kentonv> :)
<asheesh> abnd: If you need anything else, please feel very free to ask!
<asheesh> https://twitter.com/abhinandh suggests you're maybe based in the SF Bay Area; consider joining the SF Bay Area Sandstorm meetup: http://www.meetup.com/Sandstorm-SF-Bay-Area/
gemlog has joined #sandstorm
<gemlog> just testing out rocketchat, which is great on pc. the version currently on the appstore won't connect though, complaining the server version is too old.
<gemlog> I just bounced in here to mention that in case it wasn't a known thing.
<gemlog> ...and it's late, so... cheers.
gemlog has left #sandstorm [#sandstorm]
aeviator has joined #sandstorm
eternaleye has quit [Changing host]
eternaleye has joined #sandstorm
aeviator has quit [Ping timeout: 244 seconds]
frigginglorious has joined #sandstorm
coyotebush_ has joined #sandstorm
coyotebush has quit [Ping timeout: 250 seconds]
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
frigginglorious has quit [Quit: frigginglorious]
crw has quit [Quit: leaving]
crw has joined #sandstorm
larjona_ is now known as larjona
larjona has quit [Quit: http://quassel-irc.org - Chatee cómodamente donde sea.]
larjona has joined #sandstorm
tg has quit [Quit: Leaving]
aeviator has joined #sandstorm
abnd has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
aeviator has quit [Ping timeout: 244 seconds]
tg has joined #sandstorm
tg has quit [Quit: Leaving]
tg has joined #sandstorm
<digitalcircuit> When I find really small typos, is the formal pull request process good, or should I do something else? Just making sure I don't bother or offend :)
aeviator has joined #sandstorm
aeviator has quit [Ping timeout: 264 seconds]
Aurelius_Home has quit [Ping timeout: 265 seconds]
Aurelius_Home has joined #sandstorm
aeviator has joined #sandstorm
sydney_u1tangle has quit [Ping timeout: 250 seconds]
sydney_untangle has joined #sandstorm
xet7_ has joined #sandstorm
mnutt_ has joined #sandstorm
<afuentes> I created a gitweb grain but the "You can clone this repo by running these commands:" is empty. Do you know what can be the problem?
<afuentes> both app log (the terminal icon) and sandstorm.log doesnt show anything
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<afuentes> if i create a share access link, the repo cloning field is empty as well
<afuentes> if i create a gogs grain it happens the same :s
<asheesh> afuentes: That's pretty weird. I wonder if we broke it over the weekend. Let me see. : )
<afuentes> well, oasis works fine
<asheesh> Huh. Does the Javascript console in your browser show anything interesting when it fails?
<afuentes> i guess both mine and oasis are running on the same version
<asheesh> Yeah, Oasis does work; I agree. Hmm.
<asheesh> Similarly can you provide me a sharing link to a grain on your server that demonstrates the problem?
<asheesh> That might help me diagnose it.
<afuentes> web console: "App authors: To understand the grain-frame in Sandstorm and how to find logs and perform troubleshooting, see: ...
<asheesh> digitalcircuit: When you find typos like that, yeah, pull request is good. A lot of "paperwork" for a typo, maybe, but it's the process we use for most things, so it's the easiest one for us to deal with.
<afuentes> i tried both firefox and chromium
<asheesh> afuentes: Any chance you can make a sharing link for me to try?
<asheesh> A gogs sharing link would work.
<afuentes> I just sent one to you
<afuentes> didnt you get it?
<asheesh> Oh! I didn't check PMs
<afuentes> with /msg
<afuentes> /msg usually inlines the mesage
<afuentes> instead of opening a new window like /query
<asheesh> Got it
<afuentes> I changed domains recently... but everything else seems to work fine, so I dont think thats it
<afuentes> btw, i was testing, gitlab before on oasis, and i wasnt able to push something to the repo with the shared link. Not sure if there an extra step to do, but i checked every option. With gogs for example you have to add the user to the new project for it to work. gitweb doesnt need anything
<asheesh> Hi afuentes !
<asheesh> The problem is a mismatch between WILDCARD_HOST and BASE_URL
<asheesh> The grain-frame and the WILDCARD_HOST aren't able to communicate, which results in this pause.
<asheesh> pause of execution
<afuentes> if WILDCARD_HOST and BASE_URL cant be different domains, im not sure they should be different variables x)
<afuentes> yeah, saw the patch on the github about that piece of documentation
<asheesh> Yeah, the only reason they're diff variables is that there are a few options in how to format the two variables. That's a good point, though.
<afuentes> I read that piece of docu when you pushed it a few days ago, and im reading it again, but still not sure why it cant be done after reading it x)
<afuentes> the big problem seems to be the third-party cookie blocking
<asheesh> In this case, it's about iframe cross-origin communication.
<afuentes> but thats not the case here
<afuentes> yay, so many problems to have it under https ^^
<asheesh> The grain-frame attempts to access window.parent, which is on a different domain (username.sandcats.io) than the main site.
<asheesh> It's possible we can adjust Sandstorm to work slightly better in this configuration; it's not something we've tested yet, that's for sure!
<afuentes> cerbot has stated they are not working, not intend to work on wildcard certs :(
<afuentes> this is unfortunate
<asheesh> Yeah, that is.
<afuentes> okay... well, i was using gitolite and a read-only gitweb so far... i guess i cant use these gits interfaces then ^^
<afuentes> thanks asheesh!
<asheesh> The issue might go even deeper than those; any powerbox interactions will fail, I believe, but I haven't tested them.
<asheesh> Do try the Collections app and see if that works.
<afuentes> yeah, i click on add grain, but nothing happens
<afuentes> just something to be aware of, next time something stops working :)
<asheesh> OK! Just know it's not a supported configuration. We might show big red warnings at some point to you since most people who get into this configuration should probably get out of it. :)
<asheesh> I have to head out for a bit, but will be back later!
<afuentes> yeah, and not only that is not supported (I knew this and still went on) but that some things wont work at all!
<afuentes> Its not that I dont want to get out of it... I like simplicity like everybody else :)
<afuentes> I will probably go full sandcats at some point if I really need something that i cant make work with my current setup
<afuentes> I know that im hosting everything... but without using my own domain, it might not be that clear to the people I share grains with... sharing photos for example
<afuentes> or private git repos
<afuentes> not that using your own domain implies that at all anyway, but thats the perception you get :)
<afuentes> for now ill just keep using my old gitolite setup
<afuentes> for git repos
<aeviator> Hi Everybody…i wonder if there's any heroku (third party) buildpack available for running sandstorm on heroku
<digitalcircuit> asheesh: Noted! The overhead of a pull request for typos is fine by me; I'll just use my 'very short' PR template. I'll try to get it up in the next day; I should've been sleeping by now :)
kxra has quit [Ping timeout: 265 seconds]
frigginglorious has joined #sandstorm
kxra has joined #sandstorm
aeviator has quit [Ping timeout: 244 seconds]
mnutt_ has joined #sandstorm
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mnutt_ has joined #sandstorm
eternaleye has quit [Read error: Connection reset by peer]
davidar has quit [Read error: Connection reset by peer]
M-hrjet has quit [Remote host closed the connection]
JonTheNiceGuy[m] has quit [Remote host closed the connection]
M-hrjet has joined #sandstorm
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mnutt_ has joined #sandstorm
frigginglorious has quit [Ping timeout: 258 seconds]
davidar has joined #sandstorm
eternaleye has joined #sandstorm
JonTheNiceGuy[m] has joined #sandstorm
aeviator has joined #sandstorm
<asheesh> Hi aeviator ! I don't know of any.
<asheesh> Out of curiosity, (a) have you tried it? does it work? my hunch is Heroku blocks some syscalls that we'd need, but you could find out! :) (b) Out of curiosity, what you really trying to do? e.g. why Heroku?
eternaleye has quit [Changing host]
eternaleye has joined #sandstorm
DanC_ has quit [Ping timeout: 240 seconds]
wolcen has joined #sandstorm
wolcen has quit [Ping timeout: 252 seconds]
DanC_ has joined #sandstorm
felix_rapidfactu has joined #sandstorm
wolcen has joined #sandstorm
felix_rapidfactu has quit [Client Quit]
frigginglorious has joined #sandstorm
Telesight has joined #sandstorm
sh_smith has quit [Read error: Connection reset by peer]
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
sh_smith has joined #sandstorm
mnutt_ has joined #sandstorm
frankier has joined #sandstorm
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
isd has joined #sandstorm
isd has quit [Client Quit]
garrison has left #sandstorm [#sandstorm]
<asheesh> "Morning", all!
<pdurbin> asheesh: mornin'. What's new?
<asheesh> Oh, huh. Let me think about that.
<asheesh> With me personally, one new-ish thing is I'm in Rochester, NY, visiting family.
mnutt_ has joined #sandstorm
afuentes has quit [Ping timeout: 244 seconds]
afuentes has joined #sandstorm
aeviator has quit [Ping timeout: 244 seconds]
mnutt_ has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mnutt_ has joined #sandstorm
sydney_untangle has quit [Ping timeout: 244 seconds]
frankier has quit [Ping timeout: 264 seconds]
ThePurgingPanda has joined #sandstorm
ThePurgingPanda_ has quit [Ping timeout: 252 seconds]
aeviator has joined #sandstorm
aeviator has quit [Ping timeout: 240 seconds]
sydney_untangle has joined #sandstorm
tantalum has joined #sandstorm
Telesight has quit [Quit: Leaving.]
<pdurbin> cool
tantalum has left #sandstorm [#sandstorm]
jemc has joined #sandstorm
jemc_ has joined #sandstorm
jemc has quit [Ping timeout: 260 seconds]
jemc_ has quit [Quit: WeeChat 1.4]
jemc has joined #sandstorm
frigginglorious has quit [Ping timeout: 244 seconds]
isd has joined #sandstorm
wolcen has quit [Ping timeout: 264 seconds]
afuentes has quit [Ping timeout: 260 seconds]
wolcen has joined #sandstorm
aeviator has joined #sandstorm
aeviator has quit [Ping timeout: 264 seconds]
wolcen has quit [Ping timeout: 258 seconds]
wolcen has joined #sandstorm