bootgrid: limit maintaining scroll position to inplace=true, continuation of 75e60e8
This shouldn't be the default behavior, as a "refresh" would also
maintain scrolling position.
(cherry picked from commit e67ea610853257814b6f9f543a7ed70e26d47654)
bootgrid: limit maintaining scroll position to inplace=true, continuation of 75e60e8
This shouldn't be the default behavior, as a "refresh" would also
maintain scrolling position.
[CHERI] Refine LoopIdiomRecognize handling of stable representation non-integral pointers. (#189402)
This makes two changes:
- memset can be formed from stores of null pointers, even if they are
non-integral. Null pointers are already assumed to be equivalent to the
all-zeros bit pattern, and it's not the goal of non-integral pointer
support to change that assumption.
- memcpy can be formed from copies of non-integral pointers. We assume
if the environment provides a memcpy implementation for a non-integral
pointer address space, then that memcpy is non-integral pointer aware.
These changes are not applied to pointers with unstable representation.
[libc] Implement connect(2) on linux (#189668)
I'm using the new syscall wrapper framework, and enabling the entry
point for x86_64, aarch64 and riscv. The associated test currently only
checks for the error code. Once we have listen&accept (which I'm
probably going to tackle next), we can test that the two can talk to
each other.
[flang] Fix stack-arrays pass moving alloca across stackrestore scope (#184727)
When a operand is shared between two fir.allocmem ops in different
stacksave/stackrestore scopes, findAllocaInsertionPoint() placed both
allocas at the operand definition site inside the first scope. The first
stackrestore then reclaimed both, leaving the second call with a
dangling pointer.
Add a check for intervening stackrestore ops between the last operand
and the allocmem. If one is found, fall back to the allocmem's own
location, matching the existing bail-out for cross-block operands.
Fixes: https://github.com/llvm/llvm-project/issues/178812
bootgrid: maintain scrolling position for both datatree and command actions. Closes https://github.com/opnsense/core/issues/9151
The usage of scrollToRow has been considered, but this contains
too much magic causing all kinds of jumps in scroll position,
causing a user to lose track of the changes they made. The only
downside to this is that when a datatree is expanded at the bottom
of a grid, the associated rows aren't immediately visible until
manually scrolled to.
(cherry picked from commit 75e60e85194e7f2bf7e20e3891743ce801e05820)
dashboard:gauge improvements (#10063)
Closes: #8356
*Makes the disk widget become table/bars from grid 2 size onwards
*Adds disk free/used size on the gauge
*Removes parentheses from the memory widget
---------
Co-authored-by: Fabian Rodriguez <317514+MagicFab at users.noreply.github.com>
(cherry picked from commit 7f3bcf5b787145b7cf185854758c3cddefdf1971)
[OFFLOAD][L0] Remove dependence from level zero headers for dlopen build (#189120)
Adds the subset of the Level Zero headers necessary to compile the
plugin when built with dlopen support.
Disclaimer: The headers were mostly generated by Claude.
Scripts: widgets without endpoint access exist now
(Likely the right fix: just print as informational message)
(cherry picked from commit 4d3601d5ca9bf56ac852ad6cd9e120ee6f52fbd3)
bootgrid: set visibility hidden for base_bootgrid_table
Since the structure is used to initialize the bootgrid, we shouldn't render
the original structure possibly causing a flash of content.
(cherry picked from commit 9861da22a25bed9dedb5d577bc38d9bc7ed381a4)
unbound: limit duckdb to a single thread in write mode to reduce logger memory usage
After some testing, it seems the duckdb python API has a tendency to
leak (up to a cap), which seems to be mitigated when we limit to a single thread.
Further testing shows that the single logger.py process doesn't
use parallelization when appending dataframes to the db instance
and as such multiple threads are useless to begin with. The heavier
actions are the read actions, which are separate short-lived processes
and do not suffer from the same issue and likely do require duckdb
parallelism to perform properly, so apply the single thread only to
writers.
(cherry picked from commit 5e781d8321e7b10b0b627bd1e2917cd23a343830)
firmware: repeat the update after pkg reinstall
It appears that the package manager lost a number of tricks
over the years so now we add more manual labor to do what
we expect of it.
(cherry picked from commit c0d5331e1fe7d974a8a153b9d67239b4c3d251a0)
mvc: BaseField: add setValues() for generic use
A small follow-up to make setValues() work like getValues()
including stripping empty values. Works from everywhere now
and adds a few tests in order to make sure it will keep working.
(cherry picked from commit aefe80cdd8168f26401ab85456c6632c6a259830)
(cherry picked from commit 0f092c3d7d558fdae0925bc36fea616473277369)
