Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BAR update gives unexpected filesize for Extract_Bouts_From_Tracks.py #21

Closed
glynnelson opened this issue Feb 9, 2017 · 9 comments
Closed

Comments

@glynnelson
Copy link

Adding BAR site in Fiji on a Mac I was unable to install fully, as it gave the following error:

Incorrect file size for /Applications/Fiji.app/update/plugins/Scripts/BAR/Snippets/Extract_Bouts_From_Tracks.py: 17534 (expected 18471)

@imagejan
Copy link
Contributor

imagejan commented Feb 9, 2017

It's possible that the file was corrupted during download. The latest source file on the update site (http://sites.imagej.net/Tiago/plugins/Scripts/BAR/Snippets/) does have the correct size of 18471 bytes.
Can you try updating again?

@tferr
Copy link
Owner

tferr commented Feb 9, 2017

@imagejan thanks for looking into it!

It took me a while to reproduce this, but I finally manage to reproduce it:

  1. Download Fiji from http://downloads.imagej.net/fiji/latest/
  2. Run the Updater. Restart
  3. Run the Updater. Subscribe to the BAR Update site.
  4. The following exception is triggered:
java.lang.RuntimeException: Incorrect file size for /Applications/IJ/Fiji-Virgin.app/update/plugins/Scripts/BAR/Snippets/Extract_Bouts_From_Tracks.py: 17534 (expected 18471)
	at net.imagej.updater.Installer.verify(Installer.java:293)
	at net.imagej.updater.Installer$VerifyFiles.itemDone(Installer.java:270)
	at net.imagej.updater.util.AbstractProgressable.itemDone(AbstractProgressable.java:87)
	at net.imagej.updater.util.Downloader.download(Downloader.java:138)
	at net.imagej.updater.util.Downloader.start(Downloader.java:98)
	at net.imagej.updater.Installer.start(Installer.java:154)
	at net.imagej.ui.swing.updater.UpdaterFrame.install(UpdaterFrame.java:629)
	at net.imagej.ui.swing.updater.UpdaterFrame$13.run(UpdaterFrame.java:566)

I am not so sure what is really causing it, but for now the following seems to work:
After the error is displayed, just select the problematic file in the updater, and select the Keep as-is action (screenshot below). After restart the file seems to appear properly installed and the updater no longer complains about it. @glynnelson, does it work for you?

Otherwise, I guess I could upload a newer version of the file, to see if the problem goes away.

bar-updateexceptipn

@glynnelson
Copy link
Author

I was pretty sure it wasn't the download as I tried it several times. However, you are correct @tferr , it works fine if I restart and gives no errors.

Thanks!

@imagejan
Copy link
Contributor

In fact, it might also be an inconsistent state of the db.xml.gz file on the update site (containing the status information of all the files).
My Fiji installation reports the script file as being up-to-date, but from 14 June 2016:

image

while the latest version present on the site has a time stamp from November:

Extract_Bouts_From_Tracks.py-20161124120033

I have no clue how this could have happened, maybe @ctrueden has an idea.

@glynnelson
Copy link
Author

That would make sense, as on the multiple times I tried, it was always the same sizes expected and downloaded.

@ctrueden
Copy link
Contributor

@tferr I did some surgery on the Tiago update site's db.xml.gz. I fixed the file size there to match reality on the file system. Hopefully this makes the error go away. Please double check that the actual script contents are correct.

@ctrueden
Copy link
Contributor

Actually, my surgery was wrong. We need a new checksum for the newer 20161124120033 version. The file size is correct for that version. Working on it.

@ctrueden
Copy link
Contributor

ctrueden commented Feb 13, 2017

I changed the checksum to the correct value, and all seems OK now. Please comment here if not. Otherwise, I think this issue can be closed.

P.S. Regarding why this happened... unfortunately, I have no idea. But I propose that we wait to see whether it happens again before we worry about it too much.

@tferr
Copy link
Owner

tferr commented Feb 17, 2017

@ctrueden Thanks for looking into it. I guess this is yet one more reason to have all scripts bundled in a single jar file.
Hopefully Lisbon is treating you well. And I do hope you have time to visit Porto. It is my hometown!

@tferr tferr closed this as completed Feb 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants