The Dictionary used to cache the authenticated logins was made
thread-safe in revision 2653791227 ("Use thread-safe collection in
SynologyAuthenticationHandler").
The previous implementation returned false for null or empty or
whitespace values, and true for unparsable values. A default value of
false seems more appropriate for these cases.
The previous implementation returned true for null, empty or whitespace,
or unparsable values. A default value of false seems more appropriate
for this setting.
Since the ServerSettings constructor initializes the m_values Dictionary
with keys from the CONST class, we can assume that the
SERVER_PORT_CHANGED key exists.
The previous implementation returned true for null, empty or whitespace,
or unparsable values. A default value of false seems more appropriate
for these settings. In particular, if no warning or error has occurred
yet (e.g., upon first installation), these properties should return
false.
This addresses issue #3126.
The previous implementation:
1. Assumes that the relevant key exists in the Dictionary.
2. Returns true if the value is null, empty or whitespace, or
unparsable. Otherwise, it returns the parsed value.
This simplifies the code while capturing the same logic.
The previous implementation:
1. Assumes that the relevant key exists in the Dictionary.
2. Returns true if the value is null, empty or whitespace, or
unparsable. Otherwise, it returns the parsed value.
This simplifies the code while capturing the same logic.
This is to address a few issues with the state display bar including an issue that makes it difficult to see the current status due to the length of the backup name as backup names lengths are not limited.
This will:
1) Truncate the length of the name (in the state bar) to keep the state fully visible
2) Show the full name (as a title) if user hovers over name
This addresses issue: #3106
and implementation was discussed here:
https://forum.duplicati.com/t/proposal-for-a-modification-to-the-state-display-bar-green-info-bar-at-the-top/3133/6
Added support for the new keystone v3 API, the old v2.0 APIs are still
available, the v3 can be selected with a version option.
Only password login is implemented here for API v3, so token login is
still missing.
The progress bar in the restore screen appears offset from the top. This fix corrects that issue.
Changes made to LESS file and need to be compiled into CSS file.
Screenshot of problem: https://i.imgur.com/nmcHFTH.png
Screenshot of solution: https://i.imgur.com/H0tbPmP.png
Extend the GUI with a small progress bar within the backup job "details":
- add current action
- change the icon of the active job (paused, running)
- show / hide the GUI-extension (progress bar, filename, action) only if page-event contains a current filename
Extend the GUI with a small progress bar within the backup job "details":
- add current action
- change the icon of the active job (paused, running)
- show / hide the GUI-extension (progress bar, filename, action) only if page-event contains a current filename
Extend the GUI with a small progress bar within the backup job "details":
- add current action
- change the icon of the active job (paused, running)
- show / hide the GUI-extension (progress bar, filename, action) only if page-event contains a current filename
verhoek
