**** BEGIN LOGGING AT Tue Oct 25 02:59:57 2011
Oct 25 06:03:41 <rwhitby> So, who's alpha testing Tailor ?
Oct 25 06:03:47 <ka6sox> me!
Oct 25 06:04:02 <rwhitby> ok, any problems with 0.0.6 ?
Oct 25 06:04:51 <ka6sox> not that I have seen.
Oct 25 06:05:23 <ka6sox> except I can't resize the ext3fs anymore
Oct 25 06:05:50 <ka6sox> because it drops me into file resize and when I go to up the partition size it reverts.
Oct 25 06:06:39 <ka6sox> so we have lost functionality :D
Oct 25 06:08:01 <rwhitby> run me through that sequence?
Oct 25 06:08:22 <ka6sox> resizefat lower
Oct 25 06:08:31 <ka6sox> lvresize /media/internal
Oct 25 06:08:35 <ka6sox> (lower)
Oct 25 06:08:56 <ka6sox> drops me into ext3fs (already there) in filesystem resize
Oct 25 06:09:13 <rwhitby> Tailor does not do those commands yet.
Oct 25 06:09:24 <rwhitby> Are you referring to using Tailor, or something else?
Oct 25 06:09:30 <ka6sox> sorry.
Oct 25 06:09:37 <ka6sox> let me rephrase
Oct 25 06:09:46 <ka6sox> chose resize filesystem
Oct 25 06:09:54 <ka6sox> (on media/internal)
Oct 25 06:09:55 <rwhitby> I can select ext3fs, unmount, check, resize partition fine.
Oct 25 06:10:08 <ka6sox> let me try 1 more time.
Oct 25 06:10:17 <ka6sox> 2X it didn't do that.
Oct 25 06:10:43 <ka6sox> restarting
Oct 25 06:10:53 <rwhitby> don't tap in the Select Partition part between check and resize partition
Oct 25 06:11:05 <ka6sox> I didn't
Oct 25 06:11:24 <ka6sox> it dropped me into ext3fs after finishing the "resize" of media/internal
Oct 25 06:11:56 <rwhitby> run me through the sequence, using Tailor terminology this time
Oct 25 06:12:00 <ka6sox> kk...jas
Oct 25 06:12:44 <ka6sox> comes up wihth USB selected, and unmount partition
Oct 25 06:12:50 <ka6sox> unmount partition.
Oct 25 06:12:58 <ka6sox> check filesystem
Oct 25 06:13:27 <rwhitby> yep
Oct 25 06:13:36 <ka6sox> USB partition, resize FS,
Oct 25 06:13:50 <ka6sox> resize FS to 15000
Oct 25 06:13:52 <rwhitby> yep, that's the default, no need to tap anything for that
Oct 25 06:14:08 <rwhitby> yep, done
Oct 25 06:14:23 <ka6sox> now at resize partition (USB)
Oct 25 06:14:27 <rwhitby> yep
Oct 25 06:14:44 <ka6sox> 17000 resize partion
Oct 25 06:15:00 <rwhitby> yep
Oct 25 06:15:01 <ka6sox> mounted partition
Oct 25 06:15:15 <ka6sox> and...its reverted
Oct 25 06:15:19 <rwhitby> yep, mount does a refresh
Oct 25 06:15:24 <ka6sox> okay starting over
Oct 25 06:15:27 <rwhitby> always has
Oct 25 06:15:59 <rwhitby> refresh reverts any simulated values
Oct 25 06:16:31 <ka6sox> now, go to choose User(ext3)
Oct 25 06:16:42 <ka6sox> unmount
Oct 25 06:16:47 <ka6sox> checking fs
Oct 25 06:17:11 <ka6sox> and...its reverted
Oct 25 06:17:46 <rwhitby> what is reverted?
Oct 25 06:17:48 <ka6sox> so back to square 0
Oct 25 06:17:52 <ka6sox> sizes
Oct 25 06:17:56 <rwhitby> what sizes?
Oct 25 06:17:57 <ka6sox> all back to REAL.
Oct 25 06:18:06 <ka6sox> USB User, Unused
Oct 25 06:18:25 <rwhitby> right.  mount does a refresh.  refresh reverts simulated values.  always has.
Oct 25 06:18:33 <ka6sox> no mount
Oct 25 06:18:35 <ka6sox> unmount
Oct 25 06:18:38 <ka6sox> check FS
Oct 25 06:18:48 <rwhitby> you said you mounted USB
Oct 25 06:18:59 <ka6sox> this time I didn't
Oct 25 06:19:11 <ka6sox> left it unmounted
Oct 25 06:19:17 <rwhitby> ok, start the sequence again, from the top.
Oct 25 06:19:30 <rwhitby> single run, no deviations or this times.
Oct 25 06:19:41 <ka6sox> start:
Oct 25 06:20:02 <ka6sox> 1) USB Partition is selected by default
Oct 25 06:20:10 <ka6sox> 2) unmount partition
Oct 25 06:20:17 <ka6sox> 3) check filesystem
Oct 25 06:20:27 <ka6sox> 4) resize filesystem (lower)
Oct 25 06:20:36 <ka6sox> 5) resize partition
Oct 25 06:20:46 <ka6sox> 6) select User(ext3)
Oct 25 06:20:54 <ka6sox> 7)unmount
Oct 25 06:21:02 <ka6sox> 8) check filesystem
Oct 25 06:21:07 <ka6sox> *reverts*
Oct 25 06:21:24 <rwhitby> not here
Oct 25 06:21:33 <ka6sox> 4X now its done it
Oct 25 06:21:47 <ka6sox> do you have a ext3fs on that box?
Oct 25 06:21:54 <ka6sox> or are you starting fresh?
Oct 25 06:21:55 <rwhitby> yes
Oct 25 06:22:03 <rwhitby> yes, starting with appmenu->refresh
Oct 25 06:22:29 <rwhitby> my ext3fs is not mounted, so I skip #7
Oct 25 06:22:44 <ka6sox> okay let me try this
Oct 25 06:22:54 <ka6sox> start off by unmounting everything
Oct 25 06:22:59 <ka6sox> then go thru it again.
Oct 25 06:23:19 <ka6sox> since I am not sure which is doing what I am seeing.
Oct 25 06:24:18 <rwhitby> no mounts, select usb, check usb, resize usb fs 1500, resize usb part 1700, select ext3, check ext3.
Oct 25 06:24:40 <ka6sox> okay your flow doesn't do that
Oct 25 06:24:51 <ka6sox> it does what I showed you.
Oct 25 06:25:03 <ka6sox> 6,7,8
Oct 25 06:25:14 <rwhitby> I just did: "no mounts, select usb, check usb, resize usb fs 1500, resize usb part 1700, select ext3, check ext3"
Oct 25 06:25:49 <rwhitby> at that point, I can select usb or ext3 and space and sizes are simulated correctly
Oct 25 06:25:58 <ka6sox> okay 1 more time.
Oct 25 06:26:09 <ka6sox> this time I will unmount everything first.
Oct 25 06:26:24 <ka6sox> (however that is not the flow of the app)
Oct 25 06:28:08 <ka6sox> okay, that works as you said.
Oct 25 06:28:20 <ka6sox> I am following what the UI flow prompts are doing
Oct 25 06:28:38 <ka6sox> and that fails as I described it.
Oct 25 06:30:03 <ka6sox> okay your method does work as advertised
Oct 25 06:30:12 <ka6sox> however that is not the flow of the app.
Oct 25 06:30:27 <rwhitby> mount and unmount refresh
Oct 25 06:30:35 <rwhitby> refresh resets simulation
Oct 25 06:30:49 <ka6sox> right, but you were asking me to check the flow of the app....
Oct 25 06:30:58 <ka6sox> so I was following the flow.
Oct 25 06:31:00 <ka6sox> :D
Oct 25 06:31:08 <rwhitby> yes, and the results are as expected
Oct 25 06:31:22 <ka6sox> then we are off to the next thing.
Oct 25 06:31:42 <rwhitby> "because it drops me into file resize and when I go to up the partition size it reverts." is very different from "sizes are refreshed on a mount or remount"
Oct 25 06:32:00 <ka6sox> yes, I am wrong about this.
Oct 25 06:32:17 <rwhitby> so, next is resizefat
Oct 25 06:32:24 <ka6sox> wait one please?
Oct 25 06:32:33 <ka6sox> I added a 3rd partition
Oct 25 06:32:35 <ka6sox> android
Oct 25 06:32:49 <ka6sox> and it failed fscheck..expected?
Oct 25 06:33:53 <rwhitby> is it a real partition, or a simulated one?
Oct 25 06:33:58 <ka6sox> sim
Oct 25 06:34:03 <ka6sox> of courese\\
Oct 25 06:34:05 <ka6sox> duh
Oct 25 06:34:06 <ka6sox> nm
Oct 25 06:34:08 <rwhitby> can't check simulated partition
Oct 25 06:34:15 <ka6sox> right, but its stuck now.
Oct 25 06:34:16 <ka6sox> oaky
Oct 25 06:34:29 <ka6sox> sim issues...moving on.
Oct 25 06:35:11 <ka6sox> resizefat
Oct 25 06:35:24 <ka6sox> are you concerned about no feedback?
Oct 25 06:35:48 <ka6sox> when I do it manually using the script it provides feedback.
Oct 25 06:35:53 <ka6sox> console feedback.
Oct 25 06:35:54 <rwhitby> well, I'm hoping the % complete numbers come through to the UI
Oct 25 06:36:02 <ka6sox> they should]
Oct 25 06:36:29 <ka6sox> I would check for a missing termination character that node is looking for.
Oct 25 06:36:48 <ka6sox> ie maybe LF only not CR/
Oct 25 06:36:50 <ka6sox> LF
Oct 25 06:37:26 <ka6sox> so when the app quits it sends the term character.
Oct 25 06:37:58 <ka6sox> or may be CR and no LF.
Oct 25 06:42:13 <ka6sox> want me to get a capture of the output and look?
Oct 25 06:44:21 <rwhitby> it seems the node_fork_server is exiting, and cannot fork a new copy cause /media/internal is unmounted
Oct 25 06:44:58 <ka6sox> makes sense
Oct 25 06:45:08 <ka6sox> suggestion?
Oct 25 06:45:30 <rwhitby> dunno why it's exiting
Oct 25 06:45:48 <ka6sox> when cryptofs is offline all bets are off.
Oct 25 06:46:05 <rwhitby> if it didn't exit, all would be fine
Oct 25 06:46:14 <ka6sox> unless we run it out of a ramfs.
Oct 25 06:46:24 <ka6sox> (which is what most resizers do)
Oct 25 06:51:54 * rwhitby bbl
Oct 25 15:46:42 <dtzWill> hmm how hard would it be to throw together a webos app that wrapped upstart?
Oct 25 15:46:55 <dtzWill> more clearly that listed the various services and let you restart them?
Oct 25 15:47:11 <dtzWill> (or start/stop/issue custom events as makes sense)
Oct 25 15:47:28 <dtzWill> seems like something impostah should do :P but maybe not
Oct 25 16:28:15 <ka6sox> dtzWill, not hard, we can use the same method as save restore uses to call via a C-Service or learn node.js enough to use that.
Oct 25 16:28:47 <ka6sox> the hard bits for me are the mojo/enyo front end stuff.
Oct 25 16:32:42 <dtzWill> yeah, if nothing else xecutah has the pieces to start/stop misc jobs
Oct 25 16:32:55 <dtzWill> just need to enumerate them and throw up some buttons like in save/restore
Oct 25 16:34:34 <ka6sox> ya, okay so we would have a whitelist like xecutah too?
Oct 25 16:34:46 <ka6sox> so it can't randomly start/stop stuff.
Oct 25 16:35:29 <ka6sox> just don't call it Upstartah :P
Oct 25 16:56:31 <dtzWill> oh
Oct 25 16:56:31 <dtzWill> well
Oct 25 16:57:08 <dtzWill> xecutah needs that beause it's expected to be used by misc users
Oct 25 16:59:25 <ka6sox> you mean add that functionality to xecutah?
Oct 25 17:00:05 <dtzWill> no, i'm just saying the security model of whitelisting makes sense for software that is aimed at users
Oct 25 17:00:16 <dtzWill> a "i know what i'm doing tool" that stays simple and just lets you bounce upstart jobs
Oct 25 17:00:31 <dtzWill> meh, like i said maybe it belongs in impostah, shrug
Oct 25 17:02:04 <ka6sox> ya,
Oct 25 20:03:15 <ka6sox> dtzWill, I'm sure that rwhitby will know where it belongs :D
Oct 25 20:06:59 <dtzWill> hehe yep
Oct 26 02:02:53 <rwhitby> ka6sox: seems that a node.js spawn of a process that returns false will cause the node_fork_server to exit the existing node process (which we are so carefully trying to keep running) and try to start a new one
Oct 26 02:03:13 <rwhitby> I replaced the fatresize call with a call to "false" and get the same bad behaviour
Oct 26 02:08:05 <ka6sox> rwhitby, I seem to remember that things would run along till you forked or tried to spawn a child process.
Oct 26 02:08:35 <ka6sox> when cryptofs is offline (like when we had optware in a loop in cryptofs)
Oct 26 02:09:17 <ka6sox> ie: an established ssh session would remain, but trying to connect a second time would fail.
Oct 26 02:10:03 <rwhitby> the spawn seems to occur correctly. it's the return false which causes the issue it seems.
Oct 26 02:10:16 <rwhitby> let me test that with a "sleep 10 && false" command
Oct 26 02:10:21 <ka6sox> kk
Oct 26 02:11:57 <rwhitby> hmm - looks like you're right.  the spawn fails immediately, not after 10 seconds
Oct 26 02:12:45 <ka6sox> that is what was happening to ssh
Oct 26 02:12:55 <rwhitby> except I just ran this with cryptofs still mounted
Oct 26 02:13:04 <rwhitby> so it's not a cryptofs or media unmounted issue
Oct 26 02:13:26 <ka6sox> hmmm....
Oct 26 02:13:29 <ka6sox> scratch that then.
Oct 26 02:13:55 <ka6sox> you are using a node call to that?
Oct 26 02:14:31 <rwhitby> scratch that, the test was invalid
Oct 26 02:14:35 <ka6sox> kk
Oct 26 02:15:09 <rwhitby> ok, valid test, waits 10 seconds before failing
Oct 26 02:15:38 <ka6sox> the return code is false?
Oct 26 02:15:42 <rwhitby> change to "sleep 10 && true" to test opposite case
Oct 26 02:16:53 <rwhitby> hmm - that fails too
Oct 26 02:18:07 <rwhitby> just "bin/true" fails too
Oct 26 02:18:40 <ka6sox> is cryptofs disconnnected?
Oct 26 02:18:44 <ka6sox> or still working?
Oct 26 02:19:52 <rwhitby> cryptofs is still connected and working
Oct 26 02:20:42 <ka6sox> and the call is from the node service?
Oct 26 02:21:12 <rwhitby> ok, was missing the "subscribe":true from my command line testing luna-send calls
Oct 26 02:21:16 <rwhitby> restarting testing
Oct 26 02:24:48 <rwhitby> and it seems that's the error in my app too :)
Oct 26 02:25:54 <ka6sox> well..thats a better fix than something else.
Oct 26 02:27:54 <rwhitby> awesome, got to test the filesystem check with an actual filesystem error
Oct 26 02:28:14 <rwhitby> will need to change that to do a reboot required thingo
Oct 26 02:28:51 <ka6sox> so this will be like preware in that you can reboot or....I guess exit.
Oct 26 02:29:10 <rwhitby> well, you can do stuff with other partitions still
Oct 26 02:29:29 <rwhitby> but I might not allow that anyway
Oct 26 02:29:34 <rwhitby> if you have filesystem errors, you should reboot
Oct 26 02:29:42 <ka6sox> or fix
Oct 26 02:29:53 <ka6sox> well...we can't
Oct 26 02:29:53 <rwhitby> interestingly, a reboot didn't fix it
Oct 26 02:30:00 <ka6sox> which partition?
Oct 26 02:30:04 <rwhitby> usb
Oct 26 02:30:11 <ka6sox> hmmm
Oct 26 02:30:19 <ka6sox> are we going to allow fixes?
Oct 26 02:30:35 <ka6sox> or a button that says "attempt to fix?"
Oct 26 02:38:03 <rwhitby> I wouldn't
Oct 26 02:39:24 <ka6sox> okay, then we should tell them to fix it by mounting it on a windows machine and fixing it there?
Oct 26 02:39:43 <ka6sox> I was kind of hoping we could have a repair tool.
Oct 26 02:39:51 <ka6sox> (maybe thats yet another app?)
Oct 26 02:40:47 <rwhitby> maybe Tailor will repair
Oct 26 02:53:52 <rwhitby> now, what's the easiest way to induce filesystem errors to test this ...
Oct 26 02:54:29 <ka6sox> the repair?
Oct 26 02:54:51 <rwhitby> yep
Oct 26 02:54:54 <ka6sox> connect to your mac, and pull the plug with a file open
Oct 26 02:54:55 <rwhitby> I just added it
**** ENDING LOGGING AT Wed Oct 26 02:59:57 2011