Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge dev to main #144

Merged
merged 33 commits into from
Dec 4, 2024
Merged

Merge dev to main #144

merged 33 commits into from
Dec 4, 2024

Conversation

Mr-Kanister
Copy link
Contributor

No description provided.

fhilgers and others added 30 commits December 2, 2024 23:02
This is necessary for granular builds.
Without it we are always building the client when building
`uniffi-bindgen`.

Signed-off-by: Felix Hilgers <[email protected]>
`ktfmt` is used by `uniffi-bindgen` when generating kotlin code.

- Explicitly configure openjdk 21
- Override jre to jdk to avoid duplicate dependencies

Signed-off-by: Felix Hilgers <[email protected]>
- Add configuration cache
- Add build cache
- Add parallel builds

Signed-off-by: Felix Hilgers <[email protected]>
- Everything is evaluated lazily for good performance
- Define libraries and binaries using kotlin dsl
- Automatically build and package libraries into JniLibs for Desktop and
  Android
- Automatically generate kotlin code via uniffi-bindgen

Signed-off-by: Felix Hilgers <[email protected]>
To hide ugly auto generated code from our main library and application
and to provide faster builds, all generated libs and code is put into a
separate package called `bindings`.

Signed-off-by: Felix Hilgers <[email protected]>
- Kills the running app when pressing Ctrl-c
- Launches the app in a writeable directory

Signed-off-by: Felix Hilgers <[email protected]>
There is currently no reason to have them, also the build is faster
without.

Signed-off-by: Felix Hilgers <[email protected]>
There was the wrong package name asserted.

Signed-off-by: Felix Hilgers <[email protected]>
- The autogenerated bindings are inconvenient to use
- We do not want to have to build rust code for our mocked client

Signed-off-by: Felix Hilgers <[email protected]>
Signed-off-by: Felix Hilgers <[email protected]>
This change speeds up our current CI pipeline by a lot (20min -> 2min).

We are using a self hosted S3 cache on hetzner and a single large
server, also hosted on S3.

The main reason our old CI system was slow is that we have a large
amount of toolchains that are not installed by default on the github
runners. That means that every job in the CI has to download about 10Gb
of data, just for the toolchains.

The new system is way faster, we have a single server with nix
installed. On this server there are multiple github runners. Each of
them share a single nix store. They also share the gradle caches in the
home directory.

The build artifacts are cached to S3 which is both local and cheap.

Signed-off-by: Felix Hilgers <[email protected]>
Nothing to see here, just for testing CI
…ly by pid and minor bugfix

Signed-off-by: Tom Weisshuhn <[email protected]>
Signed-off-by: Felix Hilgers <[email protected]>
chore(eBPF) set the threshold for a blocking call individually per pid
…so added tracking-per-pid for vfs_write

Signed-off-by: Tom Weisshuhn <[email protected]>
This commit refactors most of the frontend and along with it fixes a few bugs like:
- configurations being wrongly shared amogst PIDs
- metric selection only displaying global
- submit button being displayed if there are no changes
- filtering is now being applied corrently for both filter and metric options,
depending on what is actually configured

Signed-off-by: Luca Bretting <[email protected]>
…configured-based data stream to mock client

Signed-off-by: Luca Bretting <[email protected]>
[UI] fix frontend metric & config selection bugs + refactor
@fhilgers fhilgers merged commit df1b528 into main Dec 4, 2024
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants