User Details
- User Since
- Apr 12 2019, 4:27 PM (351 w, 5 d)
Yesterday
Tue, Jan 6
Mon, Jan 5
This is due to a hardcoded limit on the size of the underlying unionfs file in vyatta-cfg: as the value was set rather arbitrarily, we will increase the limit from 2^18 to 2^20. Note that limit is encountered irrespective of the use of the http api.
Fri, Jan 2
Tue, Dec 23
Sun, Dec 21
Fri, Dec 19
Thu, Dec 18
Tue, Dec 16
Mon, Dec 15
Dec 5 2025
Dec 4 2025
Dec 3 2025
Dec 2 2025
Nov 27 2025
Nov 26 2025
Nov 24 2025
Nov 21 2025
Nov 20 2025
A related issue is here: https://vyos.dev/T8000.
Nov 19 2025
Nov 18 2025
Nov 17 2025
Nov 14 2025
Nov 13 2025
Nov 12 2025
Nov 11 2025
Based on the comments above, I am moving this to 'wishlist' for consideration after the legacy backend is retired. My expectation is that we will not want to drop the invariant as such, however, we will be in a position to consider refinements of the model, radical or conservative, once freed from the legacy constraints.
Nov 6 2025
Nov 5 2025
Nov 4 2025
Nov 3 2025
Nov 2 2025
Nov 1 2025
Oct 29 2025
Oct 28 2025
Oct 26 2025
The assumption stated in the description is true, as discussed with @c-po at the time. The following invariant is fundamental to the operation of the commit algorithm (legacy and modern) and the config daemons: during a commit, the active and proposed configs are fixed --- no updates during the commit are reflected in any script's config dict, including those called by config dependencies. Evolution of this model will require a refinement of config dependencies, which is not possible until the legacy backend is retired.