deal with too large...
 
Share:
Notifications
Clear all

UPDATE FROM MABULA

I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.

 

Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.

 

APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46.  Before I release it, I will make sure that everything is working properly and then I will release it.

deal with too large filenames

3 Posts
2 Users
0 Reactions
1,635 Views
(@dkamen)
Molecular Cloud
Joined: 7 years ago
Posts: 1
Topic starter  

Hi,

Last night I told APP 1.075 on Linux (ext4 filesystem) to integrate 20-odd sessions ("Integrate all"). Due to the way integrations are named, this resulted in a too large filename. Like most filesystems, ext4 has a 255 character limit. So the entire process failed after several hours, just before attempting to write the integration to disk with an error like: "filename is not supported or file is locked by another process". (unfortunately I did not take a screenshot but you probably get the idea)

I guess my feature request would be for APP to either predict that the filename will be too large before the integration starts or catch the error at the moment it occurs. The best would be for the user to be prompted for a filename much like what happens when saving an image from the Tools section, alternatively APP can simply truncate the filename into something reasonable.

Thanks,

D.

 

[edit: I had mistakenly written 0.75 instead of 1.075 as APP version]


This topic was modified 7 years ago by Dimitris Kamenopoulos

   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

Yes, I've seen this issue raised before. I'll notify Mabula about it.



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

So I asked directly and he'll fix it for the upcoming release in about a week.



   
ReplyQuote
Share: