Axoloti release 1.0.11

electronicbattle · 2016-08-29 14:16:09 UTC

(edit - sorry lokki, meant to post it to Technobear or the list in general)

I've the same problem (Linux mint 18 based on Ubuntu 16.04, Mate edition).

Sync (checkout) FAILED : factory (1.0.11,anon)
Current factory library does not match correct version, upgrading master -> 1.0.11
Changes stashed successfully: factory (1.0.11,anon)
upgrade (fetch) FAILED : factory (1.0.11,anon)

My Java info is

$ java -showversion
openjdk version "1.8.0_91"
OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-3ubuntu1~16.04.1-b14)
OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)

Whenever I start Axoloti I'm told I have a user version mismatch and do I want to upgrade? Answering yes or no results in the same behaviour next time I start (I get the same error box and option to upgrade or not).

I saw that ~/axoloti-factory or contribs were empty so I copied old versions in but I still get a long list of Java errors (and numerous things to do with duplicates which is presumably related to this unmanaged lib copying):

Original name: wave/play fn
Duplicate UUID! ~/axoloti/objects/wave/play fn.axo
Path: ~/axoloti/axoloti-factory/objects/wave/play fn.axo

I hope that is of some use to someone!

thetechnobear · 2016-08-29 14:31:55 UTC

you can do the upgrade, but it wont work!

ok for now, to get the libraries, and you are familiar with the command line you can do it manually

$ cd ~/axoloti
$ rm -rf axoloti-contrib axoloti-factory
$ git clone https://github.com/axoloti/axoloti-factory.git 
$ git clone https://github.com/axoloti/axoloti-contrib.git

however, this is not a solution... since as soon as you try to sync the libraries the issue will come back, as the certificate used for authentication is for some reason missing now.

Im still trying to work out why we are even in this position... its not a code change, it something to do with the build, which also has not changed. it seems something has 'changed under out feet' since 1.0.10 (which still works)

personally, Id suggest you go back to 1.0.10 for now, which gives me more time to sort it out.

Im also a bit 'limited' with time today, as I just picked up two 7 week old puppies, so they are taking a bit of my focus/attention

lokki · 2016-08-29 14:54:41 UTC

cool, will do this asap

lokki · 2016-08-29 15:28:17 UTC

ok, i can confirm this works perfectly well. thanks @thetechnobear !!!

mrdrbobo · 2016-08-29 20:52:37 UTC

After installing 1.0.11 I get file error message after connecting Axo (below in bold):
And the fw-version says 1.0.0.1 is that correct?

Axoloti version : 1.0.11-0-g4ffd432 build time : 28/08/2016 19:54:34 CEST
Link to firmware CRC 50A29AA2
Status: factory (1.0.11,anon) : OK ( 1.0.11,clean )
Status : home : OK
Status: community (1.0.11,anon) : OK ( 1.0.11,clean )
USB device found
connected
Authentic Axoloti Core
search path : C:\Users\XXX\Documents\axoloti\axoloti-factory\objects
file error: FR_NO_FILE, filename:"/start.bin"
Firmware version: 1.0.0.1, crc=0x50A29AA2, entrypoint=0x20011000
search path : C:\Users\XXX\Documents\axoloti\objects
search path : C:\Users\XXX\Documents\axoloti\axoloti-contrib\objects
finished loading objects

thetechnobear · 2016-08-29 20:55:56 UTC

The error isn't really an error, just saying you don't have a auto start patch on the Sdcard

So your fine

Note: for those upgrading that have a start.bin you will see a similar error saying start.bin is incompatible with firmware i.e. You need to re upload start patch with 1.0.11

philoop · 2016-08-29 21:01:24 UTC

The Console changed its font type, i liked it better as it was before.....

is there a way to change font type in prefs ?

johannes · 2016-08-29 22:17:10 UTC

The motivation for the console font change is to use a monospaced font.
If it looks especially ugly, which platform (Win, Mac, Linux) are you using?
Is this really a significant issue?

There is currently no way to change the font in preferences currently, only a custom build can.

jaffasplaffa · 2016-08-30 05:28:55 UTC

I noticed it had changed too, but to me it doesnt mean anything. Looks fine on Mac

hellcore · 2016-08-30 13:31:27 UTC

Please keep the monospaced font, logs/debugs in variable width fonts are evil.

thetechnobear · 2016-09-01 17:15:22 UTC

If anyone has issues with this release, can I please ask you consider keeping 1.0.11 installed, so we can work with you on the issue and get console logs etc. you can run your 'old' version alongside , see this post

lokki · 2016-09-01 18:59:38 UTC

i have the following issues:

subpatches with parameter on parent sometimes get their names reset to default names, so for example, if i have a dial named "bass gain" that name sometimes gets lost when i work on the subpatch. sometimes as soon as i open the subpatch from the mainpatch, sometimes when i close it.

second issue is that sometimes subpatches are not found anymore, and i get missing objects on the mainpatch. i can then replace the object and just search it again and it creates without problems...

both issues have no pattern that i could determine so far.

electronicbattle · 2016-09-01 19:23:51 UTC

Hello

How ought I to get rid of all of these duplicate UUIDs? I have deleted and git cloned the axoloti and "axoloti-factory" directories but I still see many of these:

search path : /home/user/axoloti/objects
Duplicate UUID! /home/user/axoloti/objects/audio/in left.axo
Original name: audio/in left
Path: /home/user/axoloti/axoloti-factory/objects/audio/in left.axo
Duplicate UUID! /home/user/axoloti/objects/audio/in right.axo
Original name: audio/in right

(full list at http://pastebin.com/u96fed0x for a month)

thetechnobear · 2016-09-01 19:40:05 UTC

this looks like you have a copy of the factory objects in ~/axoloti/objects/
if you have not developed any objects, then I suggest you delete ~/axoloti/objects....

electronicbattle · 2016-09-01 22:06:14 UTC

Perfect - thanks for your help and your patience. I should have spotted that myself. Time for some new spectacles!

spinus · 2016-09-04 05:49:37 UTC

I'm getting a problem somewhat similar to Lokki - on my mac (10.11.5), after upgrading to 1.0.11. Similar popup as described above, then:

Axoloti version : 1.0.11-0-gc534986 build time : 28/08/2016 23:11:40 UTC
Link to firmware CRC 50A29AA2
Current user library does not match correct version master -> 1.0.11
Stash (stash) FAILED : community (1.0.11,anon)
org.eclipse.jgit.api.errors.NoHeadException: HEAD required to stash local changes
org.eclipse.jgit.api.errors.NoHeadException: HEAD required to stash local changes
at org.eclipse.jgit.api.StashCreateCommand.getHead(StashCreateCommand.java:225)
at org.eclipse.jgit.api.StashCreateCommand.call(StashCreateCommand.java:242)
at axoloti.utils.AxoGitLibrary.createStash(AxoGitLibrary.java:247)
at axoloti.utils.AxoGitLibrary.upgrade(AxoGitLibrary.java:199)
at axoloti.MainFrame$2.run(MainFrame.java:285)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

Current factory library does not match correct version, upgrading master -> 1.0.11
Stash (stash) FAILED : factory (1.0.11,anon)
org.eclipse.jgit.api.errors.NoHeadException: HEAD required to stash local changes
org.eclipse.jgit.api.errors.NoHeadException: HEAD required to stash local changes
at org.eclipse.jgit.api.StashCreateCommand.getHead(StashCreateCommand.java:225)
at org.eclipse.jgit.api.StashCreateCommand.call(StashCreateCommand.java:242)
at axoloti.utils.AxoGitLibrary.createStash(AxoGitLibrary.java:247)
at axoloti.utils.AxoGitLibrary.upgrade(AxoGitLibrary.java:199)
at axoloti.MainFrame$2.run(MainFrame.java:297)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

Status: factory (1.0.11,anon) : OK ( master,dirty )
Changes for: factory (1.0.11,anon)
untracked: objects/math/half.axo
untracked: objects/disp/ibar 64.axo
(and so forth... the rest of the .axo/.axh/.h files)

Is this also a certificate issue?

Sputnki · 2016-09-04 13:00:53 UTC

I had some issues with the firmware installation, not sure why: when flashing with the new firmware the leds did not stop blinking (i left the board connected for several minutes actually). I had to disconnect the cable and rescue the board with zadig.

The second flash went fine and now i have the correct firmware on the board. No errors were shown. I used the same cable and the same usb port in both occasions.

thetechnobear · 2016-09-04 16:38:53 UTC

no its not a certificate issue...

it looks like you were going from 1.0.9?
but also then... you were on the master branch for factory, which is not correct for 1.0.9 either.
what version had you used before?

Im a bit confused why you were not at HEAD.

did you have outstanding changes in the community library?
had you changed any of the factory objects?

were you using a 'developer build version?'
IF so did you follow my instructions about removing sub-modules?

had you done any manual git operations?

can I see the earlier part of the console...

as I say, your setup looks like it was in a inconsistent state, to what I would expect axoloti to put you in....

I will say, I think i can make some changes so the upgrade process will use a bit more 'brute force' if users have an 'inconsistent state'.
(e.g. it looks like you don't have contribution details, so therefore I could have just trashed the community and factory folders, and re-downloaded them)

jaffasplaffa · 2016-09-05 15:24:05 UTC

Just noticed that you can now drag and drop patches as well as subpatches to a patch.

Great

thetechnobear · 2016-09-11 11:27:17 UTC

3 posts were merged into an existing topic: Includes in embedded patch/object