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
rahul|q42 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
harish has quit [Ping timeout: 255 seconds]
xet7 has quit [Quit: Leaving]
wolcen has joined #sandstorm
<bfrog> dwrensha: appreciate the explanation, it was just a bit weird to look at and see that, not what I expected as a first time capnp-rpc user, but that makes a lot more sense given the idea of directly read/writting to buffers
M-hrjet has quit [*.net *.split]
davidar has quit [*.net *.split]
kineticrootkit[m has quit [*.net *.split]
kineticrootkit[m has joined #sandstorm
M-hrjet has joined #sandstorm
davidar has joined #sandstorm
jemc has quit [Ping timeout: 258 seconds]
harish has joined #sandstorm
harish has quit [Ping timeout: 255 seconds]
indiebio has quit [Quit: No Ping reply in 180 seconds.]
Triplefox has quit [Write error: Broken pipe]
Triplefox has joined #sandstorm
indiebio has joined #sandstorm
<ocdtrekkie> I am now chasing this Sandstorm package (Scrumblr) down the rabbit hole. I decided to take in code from a PR that the Scrumblr upstream has not merged.
<ocdtrekkie> However, that feature had an issue inside Sandstorm. In order to fix it, I had to take the library in it, and patch in code from a PR that the library upstream had also not merged.
<ocdtrekkie> I have written no code, but definitely now have a special snowflake version of the app running a special snowflake version of a library. That works.
<ocdtrekkie> I think it was... BlueNinja who cared about this app?
<ocdtrekkie> Scrumblr 0.5 is in the experimental list, adds markdown support: https://apps.sandstorm.io/app/w544a46cjwtje73rfearjvszwa3nhjtxjanu5s83qkdutx6k0nz0?experimental=true
<TimMc> chase that yak
<ocdtrekkie> Sidebar: If you intend to purge a grain to your recycle bin, press delete on the top bar, not delete on the Davros bar. I still now have the grain in my recycle bin, but now I have nothing in the grain too. :D
<ocdtrekkie> I am 99.9% sure I didn't need the contents, but now I definitely don't have them anyways. :D
wolcen has quit [Quit: Leaving]
harish has joined #sandstorm
<TimMc> eep
<kentonv> ocdtrekkie: scrumblr update approved.
wolcen has joined #sandstorm
<ocdtrekkie> \o/
<kentonv> I didn't really test it myself because I figure you're the kind of person who would have tested thoroughly. :)
<ocdtrekkie> I am going to do more, probably. But I feel like I accomplished something not breaking the code today with one feature, and I figured I should package and push that while I'm ahead.
<ocdtrekkie> kentonv: It is helpfully a really simple app with a very small number of things to test.
harish has quit [Ping timeout: 256 seconds]
<ocdtrekkie> I found a bug!
<kentonv> but it has SO MANY PIXELS to test
<ocdtrekkie> It isn't new to 0.5 though.
<ocdtrekkie> I had a friend join me on it, and I found a bug in the user display.
<ocdtrekkie> It converts my user ID whatever to display name, but shows like the first few characters of my friend's ID that appears in the log, instead of his display name. I will try to fix this for the next update.
<kentonv> fwiw I'm playing with it now and I can't figure out how to apply colors to the index cards, but this isn't a new problem
<kentonv> oh
<kentonv> drag and drop?
<kentonv> but it only puts a little dot on there
<ocdtrekkie> Mhmm
<kentonv> can the index cards change color at all?
<kentonv> or are they all teal?
<ocdtrekkie> I think the index card colors are randomly chosen.
<ocdtrekkie> There are like three or four colors of index card.
<kentonv> oh, apparently I got three teal cards in a row and assumed that was the only color
<ocdtrekkie> Going to share a grain with you, if you can join it quick.
<ocdtrekkie> Trying to find out if this is specific to my friend, or just "additional people"
<kentonv> it's awkward that I need to type two newlines in order to get one line break in the final output. But that was a bug before, too.
<ocdtrekkie> Yeah, it looks like everyone but the initial person's display name is botched, and just the first few characters of their ID from the log is shown instead.
<kentonv> the names all look correct to me
<ocdtrekkie> ...Because you're last, perhaps.
<ocdtrekkie> This is interesting.
<ocdtrekkie> If I close the grain and reopen it, the names are there correctly.
<kentonv> ah, so the problem is with new names that are added on the fly
<ocdtrekkie> Exactly
rahul|q42 has joined #sandstorm
jemc has joined #sandstorm
<ocdtrekkie> I may have found a Wekan issue. I updated to the latest Wekan. And my comments written in the old version are still there, but do not appear in card view. They appear in the history of the grain, and still show the 1 comment icon on the card. But don't appear when I click on the card. @dwrensha
<ocdtrekkie> Wait, they appeared. After I like... hover or click on the Activity area of the card.
mattl has quit []
<kentonv> what browser?
NwS has quit [Ping timeout: 240 seconds]
<ocdtrekkie> Edge, as the usual oddball. :D It seems I have to hover over the "Write a comment" box before it checks for comments.
<kentonv> long ago I reported a bug with comments not appearing in IE11, so maybe this is related
<ocdtrekkie> Seems likely.
<kentonv> perhaps this issue needs to be re-reported against wefork?
<ocdtrekkie> Possibly, I will update with my experience on this issue, and maybe ask xet7 if it should be refiled.
wolcen has quit [Remote host closed the connection]
<ocdtrekkie> I have been making a point to encourage PR authors to PR against wefork so they can be merged, but I believe wefork contributors all do get notifications for wekan issues, so I am not sure the value in re-reporting issues from the main repo.
wolcen has joined #sandstorm
<ocdtrekkie> Next feature I want to add to Scrumblr is the import/export PR made by the same person who made the markdown PR.
rahul|q42 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
wolcen has quit [Quit: Leaving]
wolcen has joined #sandstorm
rahul|q42 has joined #sandstorm
rahul|q42 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
BlueNinja has quit [Read error: Connection reset by peer]
rahul|q42 has joined #sandstorm
wolcen has quit [Remote host closed the connection]
wolcen has joined #sandstorm
wolcen has quit [Remote host closed the connection]
harish has joined #sandstorm
digitalcircuit has quit [Quit: Signing off from Quassel - see ya!]
digitalcircuit has joined #sandstorm
wolcen has joined #sandstorm
wolcen_ has joined #sandstorm
wolcen has quit [Remote host closed the connection]
wolcen_ is now known as wolcen
harish has quit [Ping timeout: 260 seconds]
jemc has quit [Ping timeout: 240 seconds]
afuentes has joined #sandstorm
NwS has joined #sandstorm
harish has joined #sandstorm
rahul|q42 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
harish has quit [Ping timeout: 260 seconds]
harish has joined #sandstorm
dwrensha has quit [Quit: leaving]
dwrensha has joined #sandstorm
<dwrensha> ocdtrekkie: which version of edge?
guido has quit [Ping timeout: 240 seconds]
guido_ has joined #sandstorm
<dwrensha> ocdtrekkie: I though had fixed that problem in https://github.com/wefork/wekan/pull/30
<dwrensha> testing it now...
<dwrensha> it works for me in Edge, but does not in IE 11
wew has joined #sandstorm
ThePurgingPanda has quit [Ping timeout: 252 seconds]
ThePurgingPanda has joined #sandstorm
wew has quit [Ping timeout: 276 seconds]
wew has joined #sandstorm
ThePurgingPanda has quit [Ping timeout: 248 seconds]
<dwrensha> pulling in this patch makes it work for me on both IE11 and Edge: https://github.com/wekan/wekan/pull/646
<dwrensha> ocdtrekkie: when you're around, could I send you a link to a wekan board that has the above fix, to see if that fixes things for you?
ThePurgingPanda has joined #sandstorm
wew has quit [Ping timeout: 256 seconds]
wew has joined #sandstorm
ThePurgingPanda has quit [Ping timeout: 255 seconds]
ThePurgingPanda has joined #sandstorm
wew has quit [Ping timeout: 258 seconds]
Triplefox has quit [Write error: Broken pipe]
Triplefox has joined #sandstorm
prettyvanilla_ has quit [Remote host closed the connection]
prettyvanilla_ has joined #sandstorm
guido has joined #sandstorm
guido_ has quit [Remote host closed the connection]
Zertrin[m] has quit [*.net *.split]
HalfEatenPie has quit [*.net *.split]
CaptainCalliope_ has quit [*.net *.split]
Zertrin has quit [*.net *.split]
derf- has quit [*.net *.split]
liam has quit [*.net *.split]
mokomull has quit [*.net *.split]
Lord has quit [*.net *.split]
CcxWrk has quit [*.net *.split]
cstrahan has quit [*.net *.split]
mokomull has joined #sandstorm
Lord has joined #sandstorm
liam has joined #sandstorm
derf- has joined #sandstorm
Zertrin[m] has joined #sandstorm
Zertrin has joined #sandstorm
CcxWrk has joined #sandstorm
CaptainCalliope_ has joined #sandstorm
HalfEatenPie has joined #sandstorm
cstrahan has joined #sandstorm
TML-prv has joined #sandstorm
<TML-prv> Is there a way to control the creation of a Wekan board in Sandstorm so that I can move an existing board into my sandstorm instance?
<dwrensha> TML-prv: I don't think so.
<dwrensha> here's a Github issue about it: https://github.com/wefork/wekan/issues/51
<TML-prv> dwrensha: Thanks
jemc has joined #sandstorm
<TML-prv> dwrensha: hah - that just got pinged back to you :)
bfrog has quit [Quit: WeeChat 1.6]
ocdtr_web has joined #sandstorm
<ocdtr_web> dwrensha: Yeah, inbox (at) jacobweisz.com anything you want me to test. I have Edge on the Windows 10 Anniversary Update.
ocdtr_web has quit [Quit: Page closed]
<dwrensha> ocdtrekkie: OK, I've sent you an invite.
bodisiw has joined #sandstorm
wew_ has joined #sandstorm
ThePurgingPanda has quit [Ping timeout: 258 seconds]
isd has joined #sandstorm
ThePurgingPanda has joined #sandstorm
wew_ has quit [Ping timeout: 256 seconds]
ocdtr_web has joined #sandstorm
<ocdtr_web> dwrensha: Your version is superior. It not only loads comments, but doesn't cause the tab to flash a blank screen when I open a card.
<dwrensha> ocdtr_web: I just shared another board with you. Could you try that one too?
<dwrensha> (I shared it to your g+ identity on Oasis)
<ocdtr_web> I didn't even think I had a G+ identity on Oasis.
<ocdtr_web> It is accidental if I did.
<dwrensha> ok, I just tried sharing it to your github identity
<ocdtr_web> There it is
<ocdtr_web> Getting the screen flash thing
<dwrensha> what about the comments loading?
<ocdtr_web> Comments appear to be loading
<dwrensha> you don't need to hover over the card to make them load?
<dwrensha> that's not what I expected
<dwrensha> this board does *not* have the above-linked patch applied
<dwrensha> so there's something weird going on
<dwrensha> possibly the comment-loading problem only manifests in certain situations
<dwrensha> and you were seeing it earlier because your boards fall into those situations
<dwrensha> ocdtr_web: I'd like to be able to reproduce the problems you're seeing
<dwrensha> ocdtr_web: can you make the comment-loading problem happen on Oasis on a new grain?
<dwrensha> ocdtr_web: (if you give me some steps to reliably reproduce, then I can try them out next time I boot into Windows)
<dwrensha> I suppose it's also possible that we have a bug in our "update app version on grains" logic
<dwrensha> such that you thought you were using the latest version, but were actually using some earlier version
<dwrensha> it's true that for some number of weeks the Sandstorm Wekan package had the comment loading bug for *all* browsers
wew has joined #sandstorm
ThePurgingPanda has quit [Ping timeout: 245 seconds]
<ocdtr_web> dwrensha: Would it be useful to share a grain with you that has the issue?
<dwrensha> ocdtr_web: yeah, that would help
<ocdtr_web> Sent. I shared it with Asheesh before, so it's not exactly :secret squirrel:
<dwrensha> interesting!
<dwrensha> I'm seeing the comment-loading problem on that grain from Firefox in MacOS
<dwrensha> which supports my hypothesis that the grain is somehow on an old version of the SPK
<dwrensha> my theory is that you held this grain at an old version while multiple releases went out
<dwrensha> and then when you finally clicked "upgrade grains", it only upgraded once, i.e. not to the newest version
<dwrensha> ocdtr_web: is this theory ^ consistent with your observations?
<dwrensha> if it's true, I think you should be able to go to the app market and manually install the latest Wekan release and get everything updated
<dwrensha> might require "uninstalling" Wekan first
<dwrensha> don't worry -- uninstalling does not delete any grains, it just removes the action
<jemc> does anyone have an example of an open source meteor 1.3 app that works with vagrant-spk?
<jemc> I understnad vagrant-spk doesn't yet work with meteor 1.4, but I took the meteor todo app source code (which uses meteor 1.0) and upgraded it to meteor 1.3, and it doesn't seem to work
<dwrensha> jemc: hm. that ought to work
<dwrensha> jemc: what goes wrong?
<jemc> it was working with meteor 1.0, then I did `meteor update --release 1.3.5.1` and ran `vagrant-spk dev` again, and got that output
<jemc> seems that the vm is missing some build dependencies?
<jemc> does it matter that I ran `vagrant-spk vm up` before I did the meteor upgrade?
harish has quit [Ping timeout: 240 seconds]
<ocdtr_web> dwrensha: It is possible, I definitely held off updating Wekan for a long time, because I don't have a good way to test if the upgrade will negatively impact my grains.
<ocdtr_web> When I DID upgrade, I did not use the notification, I manually installed from app market, and then clicked "Upgrade Grains" on the app page.
<ocdtr_web> I just uninstalled and reinstalled and the Upgrade Grains button returned.
rahul|q42 has joined #sandstorm
<ocdtr_web> Okay, the screen flash is annoying still, but the comments do now load. As a note, it looks like you were connected to that grain when I upgraded, and when I tried to load the grain after upgrading, I just got a spinning circle until I forced the grain to restart.
<ocdtr_web> That was kinda odd.
<kentonv> distributed systems are hard
<ocdtr_web> As a continued note, this problem would've been much easier to diagnose, test, and fix if we could individually control updates to individual grains.
<ocdtr_web> Which I still feel is ultimately a need.
<ocdtr_web> kentonv: Though nothing has been completely broken any time in this process, which is, on fairness, pretty darn good.
ocdtr_web has quit [Quit: Page closed]
rahul|q42 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<dwrensha> ocdtrekkie: I'm not seeing the flashing behavior that you've described
rahul|q42 has joined #sandstorm
<dwrensha> ocdtrekkie: do you have a way to reliably reproduce it?
bodisiw has quit [Quit: Leaving]
ThePurgingPanda has joined #sandstorm
wew has quit [Ping timeout: 255 seconds]
rahul|q42 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ocdtr_web has joined #sandstorm
<ocdtr_web> dwrensha: I can reliably reproduce it in that it occurs for me regularly. ;)
<ocdtr_web> Sometimes it is when opening a card detail view (though never when switching from one card detail view to another). And sometimes when I click on the Write comment... box.
<ocdtr_web> And I can absolutely see the behavior on a brand new grain on Oasis.
<dwrensha> ocdtr_web: does the browser console show any error when it happens?
<ocdtr_web> No :/ I looked.
rahul|q42 has joined #sandstorm
rahul|q42 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
cstrahan has quit [*.net *.split]
CaptainCalliope_ has quit [*.net *.split]
M-hrjet has quit [*.net *.split]
davidar has quit [*.net *.split]
M-hrjet has joined #sandstorm
davidar has joined #sandstorm
CaptainCalliope_ has joined #sandstorm
cstrahan has joined #sandstorm
cstrahan has quit [Max SendQ exceeded]
ocdtr_web has quit [Quit: Page closed]
cstrahan has joined #sandstorm