Skip to main content
  • EN

Hi Team, 


In version 1.3.15 (accessed via edge, Safari, or chrome) there is a bug with the compress setting. When set to 0% the repository size is 0.0TB. It works when left at 50% (I believe) but changing it down or up produces incorrect results. 

Example:

123TB FET
3% Change
50% Compress by
7 Day 
= 176.1TB

However, using the same numbers and only changing compression to 30% (worse compression) the end product is 105.6TB. It should be more, not less. 

It feels to me like the logic is flipped. 99% compression is actually 1% compression. 1% compression is 99% compression. 

Any idea when this will be fixed? It was fine early last week.

Thanks,

 

Yes, I can see what you’re seeing. I suspect a backend change may have reintroduced a regression. I will have a look.

Yes, I can see what you’re seeing. I suspect a backend change may have reintroduced a regression. I will have a look.

Thanks David. Anyway I could get my hands on last week’s version? 

Unfortunately, there’s no previous version maintenance. Fwiw, no changes were pushed last week; last backend change was May 14, so it’s been like this since then.

draper as i mentioned in another topic

is working, but not exactly like you need, instead of set 0, just click on none button and will count with zero compression

draper as i mentioned in another topic

is working, but not exactly like you need, instead of set 0, just click on none button and will count with zero compression

None also reproduces 0.0TB in this release. 

i have tested 1.3.14 and latest 1.3.15 and you are right, now is not working

What are the timelines on these sort of fixes? 

This is now fixed. :)

Comment


Terms & Conditions