SoundKloud

[qlob]

Originally Posted by twobob

side issue affecting testing. will test again in AM

Ah okay. I did some testing, and it seems that the .sh script isn't even being called by the kindlet...

[twobob]

sounds like permissions? Back later : )

[qlob]

Removed your master password, but it still unfortunately lingers in that commit... AFAIK there's no way to remove it... Sorry....

[qlob]

Maybe we should have a seperate public soundkloud repo that sanitized releases and what not can reside in?

[twobob]

I fully agree with that.

Also I think the issues may have been line ending related.

opening mainmenu.sh with nano revealed DOS line endings for example...

Duh? Why? probably WinScp "getting in the way" again. Silly thing.

I have enclosed a dos2unix to fix this (and any future foofs) natively.

Ooops

[qlob]

I'll run all the fils through that and try again...

[twobob]

Originally Posted by qlob

Removed your master password, but it still unfortunately lingers in that commit... AFAIK there's no way to remove it... Sorry....

http://stackoverflow.com/questions/4...mmit-on-github

First, remove the commit on your local repository. You can do this using git rebase -i. For example, if it's your last commit, you can do git rebase -i HEAD~2 and delete the second line within the editor window that pops up.

Then, force push to github by using git push origin +master.

See http://www-cs-students.stanford.edu/..._and_then_some for more information (i.e. if you want to remove older commits).

but either way

[twobob]

you have nano right? just open the two .sh in there and see what it says. (it will warn you the files are DOS ended)

: )

In other news.... Retroweaver and the job of byte-mangling other peoples code

What joy.

Is there like a "Retroweaver Hotwo Guide" "Guide".

That would be great.

[twobob]

Spoiler:

me@dev /opt/eclipse/Workspace-java/HelloWorld $ ./makekindlet
Buildfile: /opt/eclipse/Workspace-java/HelloWorld/build.xml

build-subprojects:

init:

build-project:
[echo] HelloWorld: /opt/eclipse/Workspace-java/HelloWorld/build.xml

build:

weave:
[unzip] Expanding: /opt/eclipse/Workspace-java/HelloWorld/lib/asm-3.1.jar into /opt/eclipse/Workspace-java/HelloWorld/bin
[unzip] Expanding: /opt/eclipse/Workspace-java/HelloWorld/lib/retroweaver-rt-2.0.7.jar into /opt/eclipse/Workspace-java/HelloWorld/bin
[unzip] Expanding: /opt/eclipse/Workspace-java/HelloWorld/lib/java-api-wrapper-1.2.1-SNAPSHOT.jar into /opt/eclipse/Workspace-java/HelloWorld/bin
[unzip] Expanding: /opt/eclipse/Workspace-java/HelloWorld/lib/apache-mime4j-0.6.jar into /opt/eclipse/Workspace-java/HelloWorld/bin
[unzip] Expanding: /opt/eclipse/Workspace-java/HelloWorld/lib/commons-codec-1.3.jar into /opt/eclipse/Workspace-java/HelloWorld/bin
[unzip] Expanding: /opt/eclipse/Workspace-java/HelloWorld/lib/commons-logging-1.1.1.jar into /opt/eclipse/Workspace-java/HelloWorld/bin
[unzip] Expanding: /opt/eclipse/Workspace-java/HelloWorld/lib/httpclient-4.0.jar into /opt/eclipse/Workspace-java/HelloWorld/bin
[unzip] Expanding: /opt/eclipse/Workspace-java/HelloWorld/lib/httpcore-4.0.1.jar into /opt/eclipse/Workspace-java/HelloWorld/bin
[unzip] Expanding: /opt/eclipse/Workspace-java/HelloWorld/lib/httpmime-4.0.jar into /opt/eclipse/Workspace-java/HelloWorld/bin
[unzip] Expanding: /opt/eclipse/Workspace-java/HelloWorld/lib/org.json.jar into /opt/eclipse/Workspace-java/HelloWorld/bin
[unzip] Expanding: /opt/eclipse/Workspace-java/HelloWorld/lib/signpost-commonshttp4-1.2.1.1.jar into /opt/eclipse/Workspace-java/HelloWorld/bin

[retroweaver] Processing 880 classes
[retroweaver] 547 classes weaved.

jar:
[jar] Building jar: /opt/eclipse/Workspace-java/HelloWorld/HelloWorld.jar

BUILD SUCCESSFUL
Total time: 2 seconds

YAY

Spoiler:

now we have a native Java soundcloud API that runs on 1.2 onwards... (I think)

but that actually loaded and ran a
api.login(username,passord) without crying - far as I can tell. (err need to actually add some logging now, err and output... heh)

testing continues... but that is a win


EDIT:

Hemm maybe not:

[12/10/12 4:57 AM] Hello, world! (v. 1)

com.cowlark.eventbus.UmbrellaException: One or more exceptions caught, see full set in UmbrellaException#getCauses
at com.cowlark.eventbus.SimpleEventBus.doFire(SimpleE ventBus.java:232)
at com.cowlark.eventbus.SimpleEventBus.access$0(Simpl eEventBus.java:205)
at com.cowlark.eventbus.SimpleEventBus$1.run(SimpleEv entBus.java:109)
at java.awt.event.InvocationEvent.dispatch(Compiled Method)(InvocationEvent.java:152)
at java.awt.EventQueue.dispatchEvent(Compiled Method)(EventQueue.java:369)
at java.awt.EventQueueProxy.dispatchEvent(Compiled Method)(EventDispatchThread.java:351)
at java.awt.EventDispatchThread.pumpOneEvent(Compiled Method)(EventDispatchThread.java:164)
at java.awt.EventDispatchThread.pumpEvents(Compiled Method)(EventDispatchThread.java:154)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:134)
at java.lang.Thread.startup(Compiled Method)(Thread.java:1065)
Caused by: java.lang.NoClassDefFoundError: java.util.concurrent.locks.Lock

now what might be causing that... hmm

http://bugs.sun.com/bugdatabase/view...bug_id=4764778 this? maybe?

[twobob]

^ this - in many different forms lol. sigh

[qlob]

Hope you can figure it out....

[twobob]

okay pursuant to our IRC last night... I tracked down the inotify thing on the kindle 3

[root@kindle root]# finder inotify

/proc/sys/fs/inotify

[root@kindle root]# cat /proc/sys/fs/inotify/max_user_watches

8192

JNotify Linux support

Spoiler:

JNotify Linux API is a thin wrapper around Linux INotify API.
Since Linux INotify API does not support recursive listening on a directory, JNotify add this functionality by createing an INotify watch on every sub directory under the watched directory (transparently). this process takes a time which is linear to the number of directories in the tree being recursively watched, and require system resources, namely - INotify watches, which are limited, by default to 8192 watches per processes.
if you get an exception like :
net.contentobjects.jnotify.linux.JNotifyException_ linux: Error watching /home/omry/file : No space left on device
it means the native inotify watch limit per process has been reached. the solution is to change the limit with a command like this (only root can do it):
echo 32000 > /proc/sys/fs/inotify/max_user_watches
which will set the maximum number of watches per process to 32000
Users of JNotify need to give up some of the functionality of the underlying system, for example, linux supports IN_CLOSE_NOWRITE event, and windows does not, it means JNotify will not support it. JNotify only support events on basic operations. it is, however, possible to use net.contentobjects.jnotify.linux.JNotify_linux class direclty, if you do not care about code portablity. this, however, means you will also no benefit from the clean API of JNotify and not from the recursive listening support.

so I will have a dig into that.

see if we can't tidy up this horrible asynchronous menu issue.

[NiLuJe]

@twobob: Fair warning about inotify: if you intend to use it to watch something on the userstore and expect it to survive past a short time window (meaning through a usb plug/unplug and/or framework restart), prepare to be disappointed .

It's what I had to resort to for the screensavers cover mode on the legacy devices, and I had to pile up a crazy amount of ugly hacks to workaround stuff, because of a wide range of different issues, depending on the device.

* Don't watch on top of fsp, it does crazy things (meaning watch base-us, not us).
* Don't expect it to survive an USBMS switch
* Don't expect it to survive a framework restart
* Don't expect it to survive a suspend

[geekmaster]

inotify also cannot see writes by the framework to the framebuffer. I had to resort to polling for changes by comparing to a framebuffer copy...

[twobob]

ah. great. : ) Thanks then. sigh...