feat(start) allow overriding inspector on start

Signed-off-by: jrwpatterson<EMAIL_ADDRESS>Hey, I just made a Pull Request!

Hey I've made a small change to allow adding changes to the inspect flag on the backend start.
We run our app out of docker-compose and it wants to listen to the debugger on ws://<IP_ADDRESS>:9229 this isn't compatible with docker compose and remote debugging. I did think about moving it to the listener but then I decided that might upset current work flows but also wouldn't allow for things like custom port listening.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

Thanks @jhaals done signed off and committed both. don't know why I didn't think of that!

@jhaals now the stars are aligned an its finally build 😆 I'm hoping we can get it in before it breaks again! 🤞


sfdx force:source:pull not recognizing that the application metadata file needs to be pulled when lightning record page assignments have changed

Summary
Lightning record page layout assignments for app, recordtype and profile are stored in the application metadata files(Application.app-meta.xml) as profileActionOverrides.
After changing the lightning record page layout assignments through lightning app builder, when you issue a force:source:pull you get changes to the profiles and the record page itself. However, the application metadata file is not updated.
You have to update something in the application(such as the description) and then issue the pull again in order to get the application metadata file to update to include the new changes.
Steps To Reproduce:
Repository to reproduce: dreamhouse-lwc
NOTE: If your issue is not reproducable by dreamhouse-lwc, i.e. requires specific metadata or files, we require a link to a simple Salesforce project repository with a script to setup a scratch org that reproduces your problem.

Create scratch org
Create application
Create record type for object
Create lightning record page for above object without assigning to a profile or app
sfdx force:source:pull
Update lightning record page to assign profile and app and record type.
sfdx force:source:pull

Expected result
Application.app-meta.xml file should be updated to include the profileActionOverrides for the recordPage, recordtype, and profile.
Actual result
Profile and recordtype files are the only ones update.
System Information
{
"cliVersion": "sfdx-cli/7.173.0",
"architecture": "darwin-x64",
"nodeVersion": "node-v16.17.1",
"pluginVersions": [
"@oclif/plugin-autocomplete 1.3.1 (core)",
"@oclif/plugin-commands 2.2.0 (core)",
"@oclif/plugin-help 5.1.14 (core)",
"@oclif/plugin-not-found 2.3.3 (core)",
"@oclif/plugin-plugins 2.1.1 (core)",
"@oclif/plugin-update 3.0.2 (core)",
"@oclif/plugin-version 1.1.2 (core)",
"@oclif/plugin-warn-if-update-available 2.0.6 (core)",
"@oclif/plugin-which 2.1.0 (core)",
"alias 2.1.5 (core)",
"apex 1.3.0 (core)",
"auth 2.2.14 (core)",
"community 2.0.7 (core)",
"config 1.4.21 (core)",
"custom-metadata 2.0.1 (core)",
"data 2.1.4 (core)",
"generator 2.0.6 (core)",
"info 2.1.10 (core)",
"limits 2.0.5 (core)",
"org 2.2.9 (core)",
"packaging 1.9.4 (core)",
"schema 2.1.10 (core)",
"signups 1.2.7 (core)",
"source 2.0.19 (core)",
"telemetry 2.0.2 (core)",
"templates 55.1.0 (core)",
"trust 2.0.4 (core)",
"user 2.1.12 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)",
"salesforce-alm 54.8.1 (core)"
],
"osVersion": "Darwin 21.6.0",
"shell": "zsh",
"rootPath": "/Users/matthew.allen/.local/share/sfdx/client/7.173.0-5858bb0"
}
Additional information
Feel free to attach a screenshot.

this is a bug on server-side source tracking (the table the CLI queries to ask what's changed).  I'm going to get it to the team that owns this type (CustomApplication).  If you have the ability to open a case, that'll help get this prioritized.


SSL related issue when pulling repo on arm64+darwin

Here is the command I'm running:
PACKAGE=rancher-monitoring/rancher-monitoring ./bin/chartsutil rebase 35bcf70c8a6f6ecb7f996021f4c1dabc736d0138

And the error (well all the output really) I'm getting:
time=2024-11-01T00:02:02.386-04:00 level=INFO msg="attempting to rebase pacakge" pkg=rancher-monitoring/rancher-monitoring from=https://github.com/prometheus-community/helm-charts.git@2ee818aaae56fd93d27652e6d878e15140636aaf/charts/kube-prometheus-stack to=https://github.com/prometheus-community/helm-charts.git@2ee818aaae56fd93d27652e6d878e15140636aaf/charts/kube-prometheus-stack incremental=false
time=2024-11-01T00:02:08.411-04:00 level=INFO msg="preparing package"
Error: failed to prepare the chart: encountered error while preparing main chart: encountered error while trying to pull upstream into charts: Get "https://github.com/prometheus-community/helm-charts.git/info/refs?service=git-upload-pack": tls: failed to verify certificate: SecPolicyCreateSSL error: 0

Second weird thing is that after the failure the ./bin dir is nuked. See:
± |util-test {2} ✓| → make pull-scripts
./scripts/pull-scripts
Downloading charts-build-scripts version<EMAIL_ADDRESS>charts-build-scripts_darwin_arm64 => ./bin/charts-build-scripts
charts-build-scripts version 1.0.0 (d59848e)

± |util-test {2} ?:1 ✗| → ls ./bin/
charts-build-scripts

± |util-test {2} ✓| → curl https://raw.githubusercontent.com/joshmeranda/chartsutil/main/hack/install.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1063  100  1063    0     0  25184      0 --:--:-- --:--:-- --:--:-- 25309
CHARTS_BUILD_SCRIPT_VERSION is not set, checking 'scripts/version'
Using charts-build-script version v1.0.0
Installing chartsutils into /Users/danpock/GitProjects/SUSE/rancher-charts/bin

± |util-test {2} ?:1 ✗| → ls ./bin/
charts-build-scripts chartsutil

Then I run the command above, and see:
[command]
Error: failed to prepare the chart: encountered error while preparing main chart: encountered error while trying to pull upstream into charts: Get "https://github.com/prometheus-community/helm-charts.git/info/refs?service=git-upload-pack": tls: failed to verify certificate: SecPolicyCreateSSL error: 0

± |util-test {2} ✓| → ls bin
ls: bin: No such file or directory

Hmm. So I'll help look into this issue further another time. I was able to get the binary working by cloning the repo and building it manually. Then I'm just running it from inside my charts repo calling it from the path it built at.
Now I can focus on learning the actual process and starting the rebase, but will still comeback to this.


Adding overloading functionality for add, sub and neg

With this PR, it will now be possible to add, subtract and calculate the opposite of a Raster object.
Here is a quick example:
import geoutils as gu
r1 = gu.Raster(gu.datasets.get_path('landsat_B4'))
r2 = gu.Raster(gu.datasets.get_path('landsat_RGB'), bands=1)
r3 = r1 + r2
r3 = -r1
r3 = r1 - r2

This also works with numpy arrays or single numbers, e.g.:
import numpy as np
r3 = r1 + np.ones(r1.data.shape)
r3 = r1 + 5

Question:
One thing I have completely ignored for now is data type. If the two rasters are 'uint8' like in the example, the output will also be of type uint8. This will lead to weird results for values > 255 (and similarly for other types with larger values).
Should a condition be added to check that the output value is within the dtype range?
Should a warning be raised? Should the output data type be set accordingly?
What do you think @erikmannerfelt @atedstone ?
To Do:
Add some tests.

For whatever reason I accidentally included the commit from my previous PR...

This is looking great!!

Regarding the dtypes, I think it should be done like numpy. I don't know how numpy does it haha but there must be somewhere in the documentation that says it.
Related to dtypes, maybe an .astype() or similar method should exist to help with these arithmetics?
Please also add a r1 / r2 operator if possible!
What happens if one raster has an incompatible amount of bands?

This is looking great!!
1. Regarding the dtypes, I think it should be done like numpy. I don't know how numpy does it haha but there must be somewhere in the documentation that says it.

Well, this is already following numpy's way. Under the hood it's simply an operation between numpy arrays so the output type of the array is set by numpy and then the Raster dtype is set from the numpy array. In my example with the numpy array for example, the output Raster has a type float64.

2. Related to dtypes, maybe an `.astype()` or similar method should exist to help with these arithmetics?

Mmmh, interesting idea! We sort of have this functionality already with the 'do-it-all' reproject function, which can convert dtype, except that right now if only the data type changes it won't do anything. So it could be a separate method yes.

3. Please also add a `r1 / r2` operator if possible!

I will! And r1 * r2.

4. What happens if one raster has an incompatible amount of bands?

If data.shape is not the same, an error is raised. So for now, both Rasters need to have the same amount of bands loaded into memory. We could also decide to use the first band by default, but it's so easy to load only a single or part of the bands with self.load that I would rather leave it as it is.

This is looking great!!
1. Regarding the dtypes, I think it should be done like numpy. I don't know how numpy does it haha but there must be somewhere in the documentation that says it.

Well, this is already following numpy's way. Under the hood it's simply an operation between numpy arrays so the output type of the array is set by numpy and then the Raster dtype is set from the numpy array. In my example with the numpy array for example, the output Raster has a type float64.

2. Related to dtypes, maybe an `.astype()` or similar method should exist to help with these arithmetics?

Mmmh, interesting idea! We sort of have this functionality already with the 'do-it-all' reproject function, which can convert dtype, except that right now if only the data type changes it won't do anything. So it could be a separate method yes.

3. Please also add a `r1 / r2` operator if possible!

I will! And r1 * r2.

4. What happens if one raster has an incompatible amount of bands?

If data.shape is not the same, an error is raised. So for now, both Rasters need to have the same amount of bands loaded into memory. We could also decide to use the first band by default, but it's so easy to load only a single or part of the bands with self.load that I would rather leave it as it is.

Sounds good with the dtype handling and band errors!
An .astype(whatever) method could just be added that runs .from_array with self._data.astype(whatever)

Actually, the question of dtypes is a problem for the subtraction...
Here's a minimal example that fails when subtracting a raster with dtypes float32 and uint8:
width = height = 5
transform = rio.transform.from_bounds(0, 0, 1, 1, width, height)
r1 = gu.Raster.from_array(np.random.randint(0, 255, (height, width)).astype('float32'), transform=transform, crs=None)
r2 = gu.Raster.from_array(np.random.randint(0, 255, (height, width), dtype='uint8'), transform=transform, crs=None)
r3 = r1 - r2
assert np.all(r3.data == r1.data - r2.data)

That's because running r1 - r2 will actually run r1 + -r2, and -r2 will be operated under the assumption of a uint8 type.

Why does it fail? Because -r2 doesn't work with a uint8 dtype? How does that work for uint8 ndarrays?

Why does it fail? Because -r2 doesn't work with a uint8 dtype? How does that work for uint8 ndarrays?

Because of this:
np.float32(10) - np.uint8(5) -> 5.0
np.float32(10) + -np.uint8(5) -> 261.0

It's actually a simple fix, I just need to make sure that the second argument has a compatible type with self, before doing the negation.

Nice!! Does * and / work or is this still in the works?

Nice!! Does * and / work or is this still in the works?

Still in the work. I'm working on the tests for the new methods right now.

@erikmannerfelt, if that version is ok, should we accept this PR and I'll create the multiplication/division in a new PR?


Truncate XS river station to 8 characters

lines 385-388 in data_model.py return the river station for a cross-section, but they are not truncated to 8 characters.  This can throw an error on line 327 of ras_run.py where the river station is used to lookup values in the rating curve database.  The river station in that database is truncated to 8 characters.
To recreate this error, run KWSE run for
collection: ble_11100303_DeepFork
source model: DEEP_FORK_CANADIAN_RIVER
sub model: 533279
Recommend updating line 388 of data_model.py to something like
return float(self.split_xs_header(1).replace("*", ""))[:8]

Another example
collection_id = "ble_12100201_UpperGuadalupe"
stac_item = "Guadalupe_River"


Mention ProcursusTeam/ldid instead of sbingner

Procursus ldid has progressed past sbingner's ldid to warrant this switch, including actual support for iOS 15.1+ missing from other ldid's

Closing this because it seems to make lots of people mad.


Agent for GBIF API calls

(as discussed)
e.g. "GBIF HP: gbif.us" (or similar)

Can you please clarify what you mean by API calls? - do we want all the way to the backend REST API or just to the GraphQL API which the hosted portals uses

The suggestion was to add the referer in the user agent, but that seems wrong. I'd rather just edit the agent to be GBIF graphql, and then forward whatever the referer is. And then let the analytics code deal with parsing that if needed.


Toggle button gets added twice upon menu creation

building a subMenu I get my toggle button added twice to the menu menu-image. "Übersicht" basically toggles the summary in the menu title on or off. The function currenciesMenuTitle is supposed to generate the current summary and return it as the menu title,
Here's the code:
const currenciesMenu = new telegrafInlineMenu(currenciesMenuTitle)

currenciesMenu
    .toggle('Übersicht', 'toggleSummary', {
        setFunc: (ctx, newVal) => {
            //currenciesMenuTitle
            showCurrenciesSummary.default = newVal
        },
        isSetFunc: () => showCurrenciesSummary.default
    })
    .selectSubmenu('selectCurrency', () => Object.keys(currencies).map(element => {
        return currencies[element].id
    }), currencySubmenu, {
        textFunc: currencyButtonText,
        columns: 2
    })

module.exports = {
    currenciesMenu
}

This gets called as a subMenu in my itemsMenu like so:
    .submenu("💰 Zaster (means money)", "showCurrenciesMenu", currenciesMenu)

After I click the either of the "Übersicht" buttons, one button dissapears and only one remains with the correct state...
I have double checked my code to be identical in structure to the example code, and fear my issue does not lie within the code above but how the menu is generate?!

I assume your isSetFunc (showCurrenciesSummary.default) is returning undefined and not false in that case?
I fixed it to accept truthy / falsy too in 1f9a8d6 which I released with v3.5.4.
But as I assumed some other things from your code this might not be the issue you experienced. Can you check if that fixed it for you?

Will do. showCurrenciesSummary is a firestore document with a boolean field "default". So this should return the state of that field. However, I can imagine it being undefined due to some code error elsewhere.


Please add basic docs and publish to Hex.

Hi, and thank you for sharing your work on making Paddle easier to integrate with Elixir apps!
Perhaps I could contribute if there was more guidance on what's missing and ways to implement.
Currently I'm looking at Plausible Analytics and Keila as examples for implementing Billiing/Subscriptions with Paddle.
However I believe the Elixir community would be more willing to contribute to such library, if you could update the Readme with a basic roadmap/todos.
Maybe also open few Issues describing how others can help?
Would you be able to add basic docs and publish to Hex.pm any time soon?

Hey @dalerka, thanks for your interest in this library!
It's been a while since I've touched this, so I'll be giving it a deeper look during the weekend.

Hey @dalerka, I've updated and published the repo.
In general, I don't know if there's too much more to add other than a module which I wasn't able to test since I didn't understand how the endpoint worked.
Other than that, I might've missed some request params in some places, or maybe there's a response shape which I'm not considering (I don't know all the shapes the api uses since it seems barely documented and irregular).
Give it a try and see if works for you, otherwise feel free to open an issue if you find an error or you wish for something to be added/modified.


Occasional crashes when streaming from iPhone to bluealsa

Problem
My setup consists of bluealsa as a sink with bluealsa-aplay for playback through speakers.
bluealsa randomly crashes with segmentation fault. Streaming is usually done from an iPhone.
Since the last update, the crashes happen daily.
Reproduction steps
bluealsa and bluealsa-aplay are run via systemd.
bluealsa -p a2dp-source -p a2dp-sink --a2dp-volume
bluealsa-aplay -Ddefault:CARD=RPiCirrus --single-audio --pcm-buffer-time=50000 --pcm-period-time=10000 --mixer-device=default:CARD=RPiCirrus "--mixer-name=Speaker Digital"

No manual ALSA configuration was done.
The iPhone is playing music via YouTube when the crash happens.
Setup

Arch Linux ARM 32 Bit on Raspberry Pi 3, updated on 2024-02-13
bluealsa --version v4.1.1 commit b6b4412 (master)

    ./configure --prefix=/usr --sysconfdir=/etc
                  --enable-aac
                  --enable-cli
                  --enable-debug
                  --enable-manpages
                  --enable-ofono
                  --enable-systemd
                  --enable-upower

bluetoothd --version 5.72
aplay --version 1.2.11

Additional context
Log before the crash:
07:31:40 D: ba-transport.c:1049: Starting transport: A2DP Sink (AAC)
07:31:40 D: ba-transport-pcm.c:286: Created BT socket duplicate: [14]: 17
07:31:40 D: ba-transport-pcm.c:365: Created new IO thread [ba-a2dp-aac]: A2DP Sink (AAC)
07:31:40 D: a2dp-aac.c:386: PCM IO loop: START: a2dp_aac_dec_thread: A2DP Sink (AAC)
07:31:40 D: a2dp-aac.c:435: Fragmented RTP packet [1]: LATM len: 42
07:31:40 D: a2dp-aac.c:435: Fragmented RTP packet [2]: LATM len: 42
07:31:40 W: a2dp-aac.c:418: Activating RTP mark bit quirk workaround
07:31:41 D: bluealsa-dbus.c:933: Setting volume: 61 [-10.57 dB] <> 61 [-10.57 dB]
07:34:13 E: a2dp-aac.c:446: AAC decode frame error: Unsupported gain control data
07:35:31 W: rtp.c:145: Missing RTP packets [9796 != 9787]: 9
07:35:31 E: a2dp-aac.c:446: AAC decode frame error: Transport sync error
07:35:31 W: rtp.c:145: Missing RTP packets [9872 != 9868]: 4
07:35:56 systemd[1]: bluealsa.service: Main process exited, code=dumped, status=11/SEGV

Backtrace:
(gdb) bt
#0  0xb6e2d4b8 in ??? () at /usr/lib/libfdk-aac.so.2
#1  0xb6e30e5c in ??? () at /usr/lib/libfdk-aac.so.2
#2  0xb6e8b6d8 in ??? () at /usr/lib/libfdk-aac.so.2
#3  0xb6e8bb24 in ??? () at /usr/lib/libfdk-aac.so.2
#4  0xb6e8c108 in ??? () at /usr/lib/libfdk-aac.so.2
#5  0xb6e8f1a0 in ??? () at /usr/lib/libfdk-aac.so.2
#6  0xb6e31c38 in aacDecoder_DecodeFrame () at /usr/lib/libfdk-aac.so.2
#7  0x0045c440 in a2dp_aac_dec_thread (t_pcm=0x0) at a2dp-aac.c:445
#8  0xb68ac140 in ??? () at /usr/lib/libc.so.6
#9  0xb692dd1c in ??? () at /usr/lib/libc.so.6

Coredump is available, in case further information is wanted.

Can you provide logs when the iPhone is just connected? I'd like to see selected A2DP configuration - log lines with A2DP peer capabilities blob: xxxx and A2DP selected configuration blob: xxxx.

peer capabilities:
15:44:23 D: bluez.c:1367: Adding new Stream End-Point: 70:F0:87:A1:71:19: SRC: SBC
15:44:23 D: dbus.c:47: Called: org.bluez.MediaEndpoint1.SelectConfiguration() on /org/bluez/hci0/A2DP/AAC/sink/1
15:44:23 D: bluez.c:452: A2DP peer capabilities blob [len=6]: 80010483e800
15:44:23 D: bluez.c:1296: Signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded(/org/bluez/hci0/dev_70_F0_87_A1_71_19/player0/NowPlaying/item184467440>
15:44:23 D: bluez.c:1296: Signal: org.freedesktop.DBus.ObjectManager.InterfacesAdded(/org/bluez/hci0/dev_70_F0_87_A1_71_19/sep3/fd10, ...)
15:44:23 D: dbus.c:47: Called: org.bluez.MediaEndpoint1.SetConfiguration() on /org/bluez/hci0/A2DP/AAC/sink/1
15:44:23 D: storage.c:123: Loading storage: /var/lib/bluealsa/70:F0:87:A1:71:19
15:44:23 D: bluez.c:593: A2DP Sink (AAC) configured for device 70:F0:87:A1:71:19
15:44:23 D: bluez.c:596: A2DP selected configuration blob [len=6]: 800104835b60
15:44:23 D: bluez.c:598: PCM configuration: channels: 2, sampling: 44100
15:44:23 D: dbus.c:47: Called: org.bluealsa.PCM1.Open() on /org/bluealsa/hci0/dev_70_F0_87_A1_71_19/a2dpsnk/source

FDK-AAC capabilities:
09:41:18 D: a2dp-aac.c:653: FDK-AAC encoder capabilities: aac=0x410b1 sbr=0x22
09:41:18 D: a2dp-aac.c:739: FDK-AAC decoder capabilities: aac=0x1a4ffff sbr=0x1bf dmx=0x7f
09:41:18 D: storage.c:90: Initializing persistent storage: /var/lib/bluealsa
09:41:18 D: main.c:632: Starting main dispatching loop

Since the last update, the crashes happen daily.

The selected configuration (and capabilities) should not interfere with recent update in bluealsa code in respect to AAC support. What kind of update you have in mind? Update of bluealsa or whole distribution? Because it is possible that the bug is in the fdk-aac library... Can you post the version of the library (on Debian you can use dpkg -s libfdk-aac2?
Also (if possible) I'd like to have the faulty stream (If the crash happens quickly after connecting the device). Then I could replay it on my side in order to preproduce the issue. Please, collect Bluetooth traffic with (start this command BEFORE you connect phone with your host):
sudo tcpdump -i bluetooth0 -w /tmp/bluealsa-aac-crash.pcap

Sorry for the unclear wording.
For a long time I was using v4.0, where the crashes also happened, but less frequently.
Recently I updated to v4.1.1 and then the mentioned commit. Both versions seem to crash more frequently now.
The libfdk-aac version is 2.0.3. Before the update it was 2.0.2.
I have to look into capturing the stream another time.

I'm getting a SIGSEGV failure in the bluealsa server when using AAC with a2dp-source profile. I'm assuming this is the same underlying fault as reported here for a2dp-sink.
git bisect reveals that the fault first occurs with commit 4495c7c "Adopt AAC encoder/decoder to A2DP spec v1.4". The previous commit 70249cf does not have this fault (@maxmitti could you try building bluealsa at commit 70249cf to see if that works for you?)

[Switching to Thread 0x7ffff623a640 (LWP 115020)]
0x00007ffff7f0ba09 in FDKsbrEnc_PSEnc_ParametricStereoProcessing (samplesBufSize=3685, sendHeader=1, qmfScale=<synthetic pointer>, sbrSynthQmf=0x7fffe0004c38, downsampledOutSignal=0x7fffe0000e60, downmixedImagQmfData=0x7fffe000efa8, downmixedRealQmfData=0x7fffe000eea8, hQmfAnalysis=0x7fffe000dae0, samples=0x7ffff6237d10, hParametricStereo=0x3dd03aa0387037a) at libSBRenc/src/ps_main.cpp:481
481	libSBRenc/src/ps_main.cpp: No such file or directory.
(gdb) bt
#0  0x00007ffff7f0ba09 in FDKsbrEnc_PSEnc_ParametricStereoProcessing(T_PARAMETRIC_STEREO*, short**, unsigned int, QMF_FILTER_BANK**, int**, int**, short*, QMF_FILTER_BANK*, signed char*, int)
    (samplesBufSize=3685, sendHeader=1, qmfScale=<synthetic pointer>, sbrSynthQmf=0x7fffe0004c38, downsampledOutSignal=0x7fffe0000e60, downmixedImagQmfData=0x7fffe000efa8, downmixedRealQmfData=0x7fffe000eea8, hQmfAnalysis=0x7fffe000dae0, samples=0x7ffff6237d10, hParametricStereo=0x3dd03aa0387037a) at libSBRenc/src/ps_main.cpp:481
#1  FDKsbrEnc_EnvEncodeFrame(SBR_ENCODER*, int, short*, unsigned int, unsigned int*, unsigned char*, int)
    (hEnvEncoder=<optimised out>, iElement=<optimised out>, samples=<optimised out>, samplesBufSize=<optimised out>, sbrDataBits=<optimised out>, sbrData=<optimised out>, clearOutput=<optimised out>)
    at libSBRenc/src/sbr_encoder.cpp:1119
#2  0x00007ffff7e9aedb in sbrEncoder_EncodeFrame (sbrData=<optimised out>, sbrDataBits=<optimised out>, samplesBufSize=3685, samples=0x7fffe0000e60, hSbrEncoder=0x7fffe0004800)
    at libSBRenc/src/sbr_encoder.cpp:2392
#3  aacEncEncode(HANDLE_AACENCODER, AACENC_BufDesc const*, AACENC_BufDesc const*, AACENC_InArgs const*, AACENC_OutArgs*)
    (hAacEncoder=<optimised out>, inBufDesc=inBufDesc@entry=0x7ffff6239a70, outBufDesc=outBufDesc@entry=0x7ffff6239aa0, inargs=inargs@entry=0x7ffff62399f8, outargs=outargs@entry=0x7ffff6239a00)
    at libAACenc/src/aacenc_lib.cpp:1934
#4  0x00005555555753b3 in a2dp_aac_enc_thread (t_pcm=0x5555555ca670) at ../../src/a2dp-aac.c:252
#5  0x00007ffff7694ac3 in start_thread (arg=<optimised out>) at ./nptl/pthread_create.c:442
#6  0x00007ffff7726850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
(gdb)

When using commit 4495c7c or later, the selected audio object type is AOT_PS ("parametric stereo"), whereas with commit 70249cf or earlier the audio object type is AOT_AAC_LC ("low complexity").
For a quick test, I checked out the current master branch head (commit 1c1e9c0) and added aot = AOT_AAC_LC; to src\a2dp-aac.c at line 126, and now AAC encoding (playback) is working fine again on master branch. So the problem appears to be with selecting or handling the  aac audio object type.
I do not know if the decoder (capture) failure is the same underlying problem, but it is possible since clearly there is some error in BlueALSA's handling of the aac audio object type.

Hmm, so I purged the Ubuntu libfdk-aac* packages, and built libfdk-aac myself from source. Now bluealsa AAC encoding works fine. Unistalled my build, re-installed the ubuntu packages, rebuilt bluealsa, Same failure as before. So it looks like my problem was caused by the Ubuntu libfdk-aac 2.0.2 packages, and maybe is not related to this issue at all.

@borine since you figured it out and it is also an encoding issue, not decoding, I will not look into this.
@arkq I was considering to record the bluetooth data, however the crashes occur less often now.
Would it still be useful if it spanned multiple days of passed time containing hours of active playback?

Would it still be useful if it spanned multiple days of passed time containing hours of active playback?

Maybe, but since borine has also reproduced the issue, I think that the dump is not required. The crash is inside AAC library after feeding in some (corrupted or not) data. That's definitely libraries fault. Encoder should not crash even after feeding it with random bytes. Otherwise, it might be a potential security vulnerability.... I suggest changing (upgrading or downgrading) fdk-aac packet.

Sorry for the late reply.
I haven’t tried anything new, but my setup changed and now it seems quite stable.
The whole setup is running on a Raspberry Pi 3.
Previously, I was using WiFi for network.
Somehow WiFi got very unstable (possibly my configuration fault), which led me to switch to wired network and seems to also have fixed the crashes.
My assumption now is, that WiFi-Bluetooth coexistence issues caused a high rate of transmission errors, which in turn caused the crashes.

My assumption now is, that WiFi-Bluetooth coexistence issues caused a high rate of transmission errors, which in turn caused the crashes.

Yes, that could be the reason. Anyway, the real cause of the crash is definitely fdk-aac decoder. Recently, I've also discovered many issues with encoder (with certain configuration) on my Debian 12 installation, which is shipped with fdk-aac v2.0.2. The solution was to bump fdk-aac to v2.0.3: https://github.com/mstorsjo/fdk-aac/releases/tag/v2.0.3
Since this issue is not directly related to BlueALSA code, I'm closing this issue.

Ok.
Just for your information, I have been using fdk-aac v2.0.3 since 2024-01-20, i.e. all the time.
Anyway, I have made a new observation. I installed kodi and while it is running crashes are happening much more often.
I therefor revised my hypothesis to the chance of crashes being related with high CPU usage.
Is it possible to disable AAC and use a different codec instead?

Is it possible to disable AAC and use a different codec instead?

Yes, you can disable AAC with command line option -c -aac, e.g.: bluealsad -p a2dp-sink -c -aac


Endpoint for deleting a 'Savings Account'

It would seem useful to have the ability to remove a 'Savings Account'.
Rename might be useful, but that could be implemented by doing a delete/add and keeping track of stored values.
Something like
/self-assessment/ni/{nino}/savings-accounts/{savingsAccountId} [DELETE]

Hi Andrew @ac000
There is no plans to add a Delete endpoint at present, but we are working on migrating all endpoints out of the SA API so I would imagine this would be reviewed at some point when we rebuild these endpoints in a new service.
I will pass your comments onto the team for review. Thanks


[utils] traverse_obj: Fix several behavioral problems

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

This PR adapts the expected results from the previous version to closer mimic what is desirable in an extractor context.
Branch prediction is removed and instead replaced by apply_key retrning a tuple of branching, results.
Changes

Values now get pruned if they are decided unhelpful (None, [] and {}).
A trailing dict key now always returns a dictionary, making **traverse_obj(None, {}) safe.
traverse_string is now correctly handled when is_user_input is False (though not branching).
is_user_input no longer supports string keys containing :.
default now always applies to the values in the last dict key (traverse_obj(None, {}, default=...) gives {})
default now applies to nested dict keys. Try to avoid this scenario.

Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[x] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Another possible enhancement - is it worth developing?
Extend key semantics to support custom key classes.
Define abstract class Traverser with methods suitable() and enumerate(). Get apply_key to handle this:
        elif isinstance(key, Traverser):
            if not key.suitable(obj):
                return
            # in yt-dlp, yield from ...
            for from_ in try_call(key.enumerate, args=(obj,)) or []:
                yield from_

and in apply_path() (actually, should check whether key.enumerate() can branch):
-            if key is Ellipsis or isinstance(key, (list, tuple)) or callable(key):
+            if key is Ellipsis or isinstance(key, (list, tuple, Traverser)) or callable(key):

Now, eg, you can implement Traversers like document.querySelectorAll(), etc, so that traverse_obj()` can be used on HTML:
class DOMTraverser(Traverser):

    @classmethod
    def suitable(cls, obj):
        return isinstance(obj, compat_str)

class ByAttribute(DOMTraverser):
    def __init__(self, attribute, value, escape_value=True):
        self._attribute = attribute
        self._value = value
        self._escape_value = escape_value

    def enumerate(self, html):
        for from_ in get_elements_by_attribute(self._attribute, self._value, html, escape_value=self._escape_value):
            yield from_

The key ByAttribute('class', 'channel-name') branches over the innerHTML of each element with class (exactly) channel-name.
    def test_dom_traversal(self):
        from youtube_dl.utils import ByAttribute
        # file is https://vid.puffyan.us/playlist?list=PL8BCB4981DD1A0108
        # with 9 videos, each with a channel link
        with open(os.path.join(os.path.dirname(os.path.abspath(__file__)), 'testdata/html/test.html'), 'rb') as f:
            webpage = f.read().decode()
            self.assertEqual(len(traverse_obj(webpage, ByAttribute('class', 'channel-name'))), 9)

The given example is not any better than len(get_elements_by_attribute('class', 'channel-name', webpage)). Do you have more complex example use-case?
Tangentially related: https://github.com/yt-dlp/yt-dlp/pull/5588

It might make sense to create an HTMLDocument class providing simple string abstractions for usage with html strings (like pathlib.Path for os.path). This would simplify development by a lot since its quite simple to use. Maybe even something like querySelector could be done (though that will be hard).
Main benefit is that now we can easily support this custom class in traverse_obj. Ideally, in the future, I would want to do something like this:
data = traverse_obj(website, [{HTMLDocument}, '#input[name="login"]', 2, {HTMLElement.get_text}])

It might also make sense to drag out traverse_obj since the current state of utils.py makes it hard to work with imo. It could live next to utils/__init__.py (old utils.py) as utils/traversal.py. If the Traverser classes get implemented that module could host them.

Do you have more complex example use-case?

That was just PoC. I think the value, for webpage parsing anyway, would come from path expressions, so that you would be able to ask for the element with attributes (or whatever) x inside the element with whatever y inside ..., within the traverse_obj() call. Like the HTMLDocument idea above, in fact.
It could be possible to generate DOMTraverser classes with a decorator-like function from the get_element...() functions.
Consider the case where some data may be available in JSON with a default in the page HTML. I would like to specify paths something like
traverse_obj((json, webpage), (0, 'path', 'in', 'json'), (1, 'path', 'in', 'html'), expected_type=whatever)
Maybe there is an XML application too.
#5588 is indeed relevant.


Unable to load kernel driver

Steps preceding reproduction:

Use SystemInformer normally.
Click Help -> Check for updates.
Update downloads, installs.
Unable to load kernel driver.
Restart computer.

Steps to reproduce:

Start System Informer (I'm admin but starting without admin privileges).
Go to main menu -> System -> Show details of all processes.
UAC dialog appears, Click YES.
"Unable to load kernel driver" message appears. More info in [1] and [2].
System Informer has limited capabilities due to not having access to its kernel driver.

Details:

System Informer version 3.0.7029 (f647fb0) x64.
Windows Server 2022 x64, 21H2, 10.0.20348.1906 (running in cloud inside QEMU).
SystemInformer.exe SHA-1 b09759778099468188434408f929d675ce289b97.
SystemInformer.sys SHA-1 ae6b8522ca5205b4cef89606ea6c7d043e81dc4f.
ntdll.dll SHA-1 4ffc26a940dffa2931923c345eb9824f76dcfca4.
ntoskrnl.exe SHA-1 ecbad74c2629f4dd516c35887b8e5d0b7032b135.

[1]
[Window Title]
System Informer

[Main Instruction]
Unable to load kernel driver

[Content]
Unable to load the kernel driver service.

The request is not supported.

Kernel version: 10.0.20348.1906
State mask: 0x00000000

[ ] Don't show this message again  [OK]

[2]

I have the same with 10.0.1941.3391 kernel.
I assume it is related to recent dyndata changes and these builds are simply not supported by driver yet.
Hopefully the support will be added soon.

could you send me your ntoskrnl.exe 10.0.19041.3391?

E-mail sent.

Thanks for getting me the build @ge0rdi - like you mentioned in the email symbols are also not yet published for 3391 yet. Once they are I'll make sure dyndata gets updated.
@MarekKnapek I added dyndata for Server 2022 here: https://github.com/winsiderss/systeminformer/commit/03f5c8c2e3a3d93102b8e4dc691be9ca9b438fbd - it'll get picked up in the next build

Microsoft released KB5029331 first as 19041.3391 and 2nd version is 19041.3393 in Release Preview/Insider version which is now also releaded to public in version 3393.

Thank you @MagicAndre1981 .
After manual Windows update check I'm on .3393 too.

ok, on 1809 LTSC 17763.4737 I also miss the ++ , so no driver is loaded for System Informer version 3.0.7029, but I dont get the messagebox

Out of curiosity: What is this dyndata thing for? I can see that it is stored into the Registry. It is definitely not a Windows thing, it is SystemInformer thing. Maybe for communication between the user-space part of SI with kernel-space part? But why is it needed? What purpose it serves? What would happen if it was not there? What are alternatives for it? Why is it needed to be Windows version specific? Sorry for bothering you with so many questions.

What is this dyndata thing for? ... Maybe for communication between the user-space part of SI with kernel-space part? But why is it needed? What purpose it serves?

They're undocumented offsets used for both protections and APIs from the client:
https://github.com/winsiderss/systeminformer/blob/4c28c8f7ba396eab1fbc13960e9731203bd60f5d/KSystemInformer/include/dyndata.h#L31-L75

What would happen if it was not there? What are alternatives for it?

The driver can't function without them. They're required for the protections to function correctly. The old driver would load without them, but it was arguably mostly useless without them. There was some functionality without them, but it was a bit non-obvious why some things would work and some wouldn't. So, during the rewrite we opted to make it a requirement. This come with the benefit that we know where we don't have support/visibility. Obviously the cost is we have to work harder to have more compatibility.

Why is it needed to be Windows version specific?

Because they're undocumented offsets that are version-specific.

I hope this helps. I am experiencing the same issue after installing KB5029351. Before this update, I only got that message once when I installed Build 3.0.7029, but now I get it every time I launch System Informer.

https://github.com/winsiderss/systeminformer/commit/137cc3a698d5960d68f63b2968a5142e25023f9c adds support for 10.0.19041.3393 and 10.0.22621.2215
Will be in next build 👍

I can confirm that with latest SI driver loads on 19041.3393.
Thank you very much.

Ok, I disabled the warning dialog in setting, when I activate the dialog, I see this for 17763.4737:

@MagicAndre1981 when I was scraping to rebuild the offsets I missed three builds:
10.0.17763.4499
10.0.17763.4644
10.0.17763.4737
I just went over them and the offsets didn't change from 10.0.17763.4337 - I updated dyndata here: https://github.com/winsiderss/systeminformer/commit/f733df42b4f20f9e938303e4231403d0fd29bd95 - will be in next build 👍

The same error happened again right after installing KB5030219 OS build 22621.2283

Thanks for letting me to @poqdavid - I'm grabbing the new versions now.

22621.2283
Should i send my ntoskrnl.exe?
ntoskrnl.zip

Symbols are not yet available for 10.0.22621.2283, I'll keep checking back - when they're available I'll update dyndata 👍

https://github.com/winsiderss/systeminformer/commit/d859dad08169721df6c66b5be580d0558fab76dc will be in next build 👍

as expected I also get the warning again for 1809:

@jxy-s out of curiosity when you guys update System Informer for newer kernels does it lose its compatibility with older kernels?
Cause I have been thinking to switch to RP channel on Windows and I was curious about how this whole thing works

you guys update System Informer for newer kernels does it lose its compatibility with older kernels

No, it doesn't break compatibility. We support older kernels. We support release builds for Win10+ x64/ARM64. The supported kernel versions are specified in https://github.com/winsiderss/systeminformer/blob/master/kphlib/kphdyn.xml

RP channel on Windows

We do not yet support preview builds. Updates to those kernels are too frequent for me to keep up with manually. I'm hoping to finish some automation eventually to support them.

Oh Windows, why must you break everything...

On latest Windows 11 stable update  (Win 11 22H2 Build 22621.2283)

I noticed I have an older SI Rev.6806 running on another Win10 17763 and here I see the ++ so driver is loaded on 17763.4851 🤔 🤷♂

I noticed I have an older SI Rev.6806 running on another Win10 17763 and here I see the ++ so driver is loaded on 17763.4851 🤔 🤷♂

See: https://github.com/winsiderss/systeminformer/issues/1823#issuecomment-1693053377
Dyndata format had to change and I went to rebuild all the offsets using some tooling. I missed a few versions. I've corrected it already, once a new build is out that kernel will be supported.

Why  process hacker displayed + and systeminformer displays ++?

the + and ++ show that both have different driver usage levels while ++ is the best

3.0.7148 fixed it on 19045.3448, but NOT for 17763.4851

@MagicAndre1981 send me your 10.0.17763.4851

@MagicAndre1981 send me your 10.0.17763.4851
I can't seem to locate that version myself. If you send it to me I can look into adding it.

ntoskrnl.zip

Thank you @MagicAndre1981, updated here: https://github.com/winsiderss/systeminformer/commit/e940474fae1300b17bf8e754ed5ade19c9e8f651

I'm on 10.0.22621.1928 but it seems to think it's a preview build.

Latest prod version is 10.0.22621.2283
Update your system.

Since windows updates kb5030183 and kb5030180, I have the same issue , "unable to load kernel driver".
Back to last restore point before installation, no error message, after re-installation   of the kbs,the message back again.
Windows Version 22H2 (build du système d'exploitation 19045.3448).
System Informer 3.0.7148 (ed40620)

@MagicAndre1981

I selfcompiled it at rev.1750 and now get this error message:

Could you try another build with the latest commits? I improved the error messaging so we can see the actual error code instead of just the localized string. My guess is you built yourself using your own signing keys outlined here. I now recognize that information is incomplete, I'll update it, but I think you may have not rebuilt the dynamic data using your signing keys (.\tools\CustomBuildTool\bin\Release\CustomBuildTool.exe -dyndata). Note that both the dynamic data, kernel driver, and the user mode binaries need rebuilt after you generate an place your developer keys.
@JJRousseau

I'm on 10.0.22621.1928 but it seems to think it's a preview build.

We have seen in the past that preview build and the kernel file version can diverge. My guess is your kernel version is actually 10.0.22621.1928 but the OS reported version is >10.0.22621. See the following, which checks the "OS reported version", that might be different than what we print as the "Kernel version":
https://github.com/winsiderss/systeminformer/blob/8d8843eebfef43334c2eef60e91125c9d19a9538/phlib/global.c#L190-L199
I've updated the message box information displayed there to include more information about the environment in which the error occurred, here: https://github.com/winsiderss/systeminformer/commit/8d8843eebfef43334c2eef60e91125c9d19a9538
@badjawe

Since windows updates kb5030183 and kb5030180, I have the same issue

Based on that error message in the window, I think you might be running an older version. I'm also not sure what HKLM\System\CurrentControlSet\Control\WMI\Security\... has to do with this?

ok, I haven't done the signing thing. So I'll wait for next official nightly

KB5030310, OS build 22621.2361, Kernel 10.0.22621.2361

10.0.22621.2361 and 10.0.19041.3516 are both on my radar, waiting for symbols to be published 👍
I'm not seeing a new build for Server 2022 yet.

Updated here: https://github.com/winsiderss/systeminformer/commit/d1a6baf440e357f1c1806554ad97df4a5972c3de 👍

7251 works now fine in 17763.4851 with full driver support (++ in title)

3.0.7254 was not offered via updater, so I extraced the zip and this is the same error I get with my self compiled version:

We're working on build pipelines. Two things here:

was not offered via updater

This is intended, deployment is disabled while we're testing.

so I extraced the zip and this is the same error

Signatures files (.sig) aren't in the zip. Use systeminformer-3.0.7254-setup.exe if you want, but probably best to wait until we're done testing. These builds will be pulled shortly.

ok, the .sig file is present in both, the zip and exe. I'll revert to the older version.

Thanks, I just noticed the issue with the pipeline that is causing the .sig not to be correct. So, that's probably what you're running into. I'm addressing that now. Thanks for your patience. In general tho, just because a build shows up on si-builds doesn't mean it's ready for consumption.

Pipeline work is complete - 3.0.7256 should be available for upgrade shortly.
I'm going to leave this issue open for a while longer. But all issues to load should already be resolved.

3.0.7256 is offered and works fine.

System Informer
Version: 3.0.7256 (121e1d2)
Many thanks for your hardworking.
🙂

So I downloaded 7256 as I have the kernel driver error on 19044,3488
Is it normal to have to reboot to replace ksi.dll? (I did shutdown system informer before trying to update).  The dll remains in use with system informer not running.

Is it normal to have to reboot to replace ksi.dll?

Yes, but generally it doesn't update. ksi.dll is a library used by the kernel driver. It can not be unloaded. The purpose of this DLL is to extend the kernel and provide functionality that would otherwise be unsafe or impossible. The updater will check the hash of the DLL to know if it needs replaced, if it does then a reboot is requested for the update to finish.

And race starts again with new updates:

and for Win11 22H2 (there is no 22H1 as shwon the messagebox) .2428:

and 1809:

@MagicAndre1981 send me 10.0.17763.4974 please. I'm looking into the others now.

@MagicAndre1981 send me 10.0.17763.4974 please. I'm looking into the others now.

ntoskrnl_17763.4974.zip

Windows Server 2022 10.0.20348.2031 x64
http://msdl.microsoft.com/download/symbols/ntoskrnl.exe/1D9F9DE41047000/ntoskrnl.exe
http://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/75F58E3898196557854FDC4B01A7AA571/ntkrnlmp.pdb

Support was added here: https://github.com/winsiderss/systeminformer/commit/d44e4d04651eafacc240e351482939f068f7c7d4
3.0.7270 is available with that commit.

.7270 works fine for 17763, 19045 and 22621 👍

Hello and thank you all,
I had the same problem as View MagicAndre1981, yesterday after the update:
Title: 2023-10 Cumulative Update for Windows 10 Version 22H2 for x64 Systems (KB5031356)
Date: 11/10/2023 16:36:56
KB Number: KB5031356
Operation: Installation
Result Code: Succeeded
HResult: 0x00000000
Update ID: 603aa2ce-9d30-473c-a175-0bdd19bd0a60
Support URL: https://support.microsoft.com/help/5031356
You have found the solution, I believe that Microsoft has chosen to annoy everyone and has been doing so for a long time.
Thanks again for your hard work.

search for new update, latest system informer update works with new Windows updates from this week.

Windows 11 23H2 is now official released with optinal Update KB5031455 (OS Builds 22621.2506 and 22631.2506) Preview

It looks like @jxy-s works on automating the dyn data in a new branch. So we'll have to wait a bit until this update race is resolved.

Updated here: https://github.com/winsiderss/systeminformer/commit/bc98048099421785ea4a37670d7b57bfb924cda5
Available in: 3.0.7310 - Help > Check for updates

works, but I had to enable driver loading again, due to your renamings. So if you see no ++ in title bar, make sure kernel driver loading is enabled.

Yep, thanks for calling that out @MagicAndre1981 - the setting names were normalized. Rather bite that bullet now then when we do a full release. Thanks.

ntoskrnl_10.0.17763.5122 .zip

Windows Server 2022
x64
10.0.20348.2113
KB5032198
ntoskrnl.exe
10.0.20348.2110
Timestamp, 0x9729528b
SizeOfImage, 0x1047000 (16.28 MB)
Guid, {53b8a0b3-6fad-7869-0204-da3ce552a05c} (b3a0b853ad6f69780204da3ce552a05c) (deterministic)
Age, 1
http://msdl.microsoft.com/download/symbols/ntoskrnl.exe/9729528B1047000/ntoskrnl.exe
http://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/53B8A0B36FAD78690204DA3CE552A05C1/ntkrnlmp.pdb

Windows 10 21H2 LTSC
x64
Kernel 10.0.19041.3693
System Informer 3.0.7310
Error kernel driver not supported on this kernel version.

Microsoft Windows [Version 10.0.22631.2715]
ntoskrnl.zip

hello everydody , same error as chrcoluk except is windows 10 22h2.
See attached file
 @

https://github.com/winsiderss/systeminformer/commit/64891545c02c8d329f358ced5a652e6d3d2a48f6 - 3.0.7313 - Help > Check for updates 👍

http://msdl.microsoft.com/download/symbols/ntoskrnl.exe/9729528B1047000/ntoskrnl.exe
http://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/53B8A0B36FAD78690204DA3CE552A05C1/ntkrnlmp.pdb

Symbols for Server 2022 are available.

https://msdl.microsoft.com/download/symbols/ntoskrnl.exe/45E0905D1047000/ntoskrnl.exe
https://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/83330EBC36016C3BD2B81C614EC8187C1/ntkrnlmp.pdb

looks like symbol are not jet uploaded

It fails to load driver after update

Looks like updater doesn't check that systeminformer process has completely finished and unlocked files.
When i open network tab it uses lots of memory and it gets swapped, delaying exit.

ntoskrnl_10.0.17763.5202.zip

https://github.com/winsiderss/systeminformer/commit/d7d0454c89d071dd5337eacce427e1d92b1c82d9 - 3.0.7310 - Help > Check for updates 👍

ok, looks like symbol for 17763 are not online, so you haven't added it

ok, looks like symbol for 17763 are not online, so you haven't added it

I'll look today 👍

ok, looks like symbol for 17763 are not online, so you haven't added it

I'll look today 👍

still missing for 17763 🤷♂
SYMSRV:  HTTPGET: /download/symbols/ntkrnlmp.pdb/AA44BDCCE47E33E9B131260A6B98E1991/ntkrnlmp.pdb
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV:  HTTPGET: /download/symbols/ntkrnlmp.pdb/AA44BDCCE47E33E9B131260A6B98E1991/ntkrnlmp.pd_
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV:  HTTPGET: /download/symbols/ntkrnlmp.pdb/AA44BDCCE47E33E9B131260A6B98E1991/file.ptr
SYMSRV:  HttpQueryInfo: 80190194 - HTTP_STATUS_NOT_FOUND
SYMSRV:  RESULT: 0x80190194
DBGHELP: ntkrnlmp.pdb - file not found

```🤷♂

Symbols for Windows Server 2k22 are now available:
http://msdl.microsoft.com/download/symbols/ntoskrnl.exe/3B845E5D1047000/ntoskrnl.exe
http://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/CEB3272F2DA918532E985797AA1099AD1/ntkrnlmp.pdb
Symbols for previous update of Server 2k22 are also available, they were not incorporated into System Informer (as of last week or so), I don't know the current situation as I already updated both Windows and SI.
http://msdl.microsoft.com/download/symbols/ntoskrnl.exe/9729528B1047000/ntoskrnl.exe
http://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/53B8A0B36FAD78690204DA3CE552A05C1/ntkrnlmp.pdb

10.0.20348.2141 and 10.0.20348.2110 already have support
10.0.17763.5202 is checked in but needs a new build, will do one when I get an opportunity to

10.0.17763.5202 - 3.0.7412 -> Help > Check for updates 👍

10.0.17763.5202 - 3.0.7412 -> Help > Check for updates 👍

works fine 👍

That's a different error. Either the ksidyn.bin or ksidyn.sig - reading the file failed (or returned a failure and didn't communicate it). I found a problem with this path that I'll correct to make the any error propagate more clearly. The handle is also leaked that might be causing an issue with the update.
If either of those files are zero length, try running the setup again (you can run it on an existing install and it will keep the settings).

I build mine from scratch with the exact settings as intended.

You need to follow the instructions here for generating your own keys for signing. The driver restricts callers unless you have the correct signatures. You can do plugin development (with restricted access), but realizing now that is somewhat broken with the new dyndata signing workflow 🤔.

10.0.17763.5202 - 3.0.7412 -> Help > Check for updates 👍

works fine 👍

ok, one 1 RS5 it it not working, telling me to do a reboot which I did but error is still the same:

After deleting the ksi.dll-old file error is gone (without any reboot).

ntoskrnl_10.0.17763.5328.zip

Symbols for Server 2k22 are available.
http://msdl.microsoft.com/download/symbols/ntoskrnl.exe/F290800D1047000/ntoskrnl.exe
http://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/B3ED6FA26A1FD6DF6A34DF3B125CAFE81/ntkrnlmp.pdb

ntoskrnl.zip

ntoskrnl_10.0.17763.5328.zip

17763 symbol is now online:
https://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/1D4090613BF97F9B9529992E20E938971/ntkrnlmp.pdb
ok, 1 day delay is now normal according to Microsoft.

3.0.7429 works on 17763, 19045 and 22631. All have ++ in title 🙌

@jxy-s can you please add a link to this issue to the messagebox that shows unsupported version to avoid the duplicates?

Yes, that's a good idea. I'm torn on if we should create a fresh issue or not. It's probably fine to just keep using this one.

Actually, I recall now that @dmex and I have had some discussions on automating the reporting of unsupported kernels. This would avoid users having to report to github themselves. I'll create a feature request on this so we can discuss there.

10.0.22621.3085, 10.0.19041.3996 - https://github.com/winsiderss/systeminformer/commit/3cc2da286e3a696c7d9fe712d792a15e7276699c
3.0.7432 - Help > Check for updates 👍

Works - loaded, however, how to use it to reduce load on the system and make my User apps work with lower latency ? Thank you.

Try to use Process Lasso
https://en.wikipedia.org/wiki/Process_Lasso

Please keep comments on this issue on-topic.

Next run. Patchday 2024-02:
KB5034763 (OS Builds 19044.4046 and 19045.4046)

KB5034768 (OS Build 17763.5458)

ntoskrnl_10.0.17763.5458.zip

KB5034765 (OS Builds 22621.3155 and 22631.3155)

Server 2022 (but I don't run this at the moment):
KB5034770 (OS Build 20348.2322)

10.0.22621.3155, 10.0.19041.4046, 10.0.20348.2322 - https://github.com/winsiderss/systeminformer/commit/220b53dcfaeb3d8c40c6c281bdfac9835f3fd288
10.0.17763.5458 - https://github.com/winsiderss/systeminformer/commit/da3d348087ae9a33aff69aa40d59d8be3442fed0
3.0.7459 - Help > Check for updates 👍

3.0.7459 - Help > Check for updates 👍

works on all reported systems

I get this error every time I try to start SystemInformer with the kernel driver enabled. This is a library PC which allows programs to run with full administrative rights; they revert any and all changes on reboot by booting to a pre-specified shadow volume copy on every boot. As such, rebooting is not an option for my use case.

I get this error every time I try to start SystemInformer with the kernel driver enabled. This is a library PC which allows programs to run with full administrative rights; they revert any and all changes on reboot by booting to a pre-specified shadow volume copy on every boot. As such, rebooting is not an option for my use case.

Probably this?:
https://github.com/winsiderss/systeminformer/blob/master/phlib%2Ferror.c#L98
Make sure the KSystemInformer service entry doesn't exist. Can't recall if there is logic to try to delete and recreate it. Otherwise...

This is a library PC which allows programs to run with full administrative rights;

Considering the error code. Ask the owner of the machine why it might be blocked?

It's probably that they are using MS's built in driver blocklist and aren't updating their fleet quickly enough to capture new certs, as they can only update by "thawing" the drive. It can be written to, but it uses snapshot logic to revert on boot. And the service entry does get made and deleted normally (minus the driver not unloading after the failed attempt to use it), but unloading it manually allows the service to disappear.
Sent from Proton Mail mobile
-------- Original Message --------
On Feb 14, 2024, 15:34, Johnny Shaw < @.***> wrote:

image.png (view on web)
I get this error every time I try to start SystemInformer with the kernel driver enabled. This is a library PC which allows programs to run with full administrative rights; they revert any and all changes on reboot by booting to a pre-specified shadow volume copy on every boot. As such, rebooting is not an option for my use case.

Probably this?:
https://github.com/winsiderss/systeminformer/blob/master/phlib%2Ferror.c#L98
Make sure the KSystemInformer service entry doesn't exist. Can't recall if there is logic to try to delete and recreate it. Otherwise...

This is a library PC which allows programs to run with full administrative rights;

Considering the error code. Ask the owner of the machine why it might be blocked?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

I don't see how this could have anything to do with MS blacklist. The KSystemInformer driver has never been on an MS blacklist. Probably some broken service key or some specific policy unique to the environment.
Regardless @Giantvince1, if you want to continue a thread on this. Please create a new issue, the error you're experiencing is unrelated to this thread. I'm going to hide the comments here to keep this one on topic.

Windows 11 23H2 (OS Build 22631.3235)
10.0.22621.3235

ntoskrnl.zip

10.0.19041.4123, 10.0.22621.3235 - https://github.com/winsiderss/systeminformer/commit/e904d245241276a6e0677d1283a53a6a6fc63d69
3.0.7474 - Help > Check for updates 👍

Came here with the same issue on 10.0.22621.3235, as I started reading was prompted by System Informer to update to 7474. @jxy-s you're a wizard...
Thanks for your work all :)

KB5035845 (OS Builds 19044.4170 and 19045.4170)

KB5035849 (OS Build 17763.5576)

exe:
https://msdl.microsoft.com/download/symbols/ntkrnlmp.exe/20575C03a6f000/ntkrnlmp.exe
Pdb: https://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/105E35CDD9BB308C18A176AB5BB37CE31/ntkrnlmp.pdb

10.0.22621.3296, 10.0.20348.2340, 10.0.19041.4170, 10.0.17763.5576 - https://github.com/winsiderss/systeminformer/commit/fe48085c0642d2acfcda3bacffaf0f285f6b9564
3.0.7479 - Help > Check for updates 👍

Mine:
[Window Title]
System Informer
[Main Instruction]
Unable to load kernel driver
[Content]
The kernel driver is not yet supported on this kernel version. Request support by submitting a GitHub issue with the Windows Kernel version.
Windows 10 22H2 10.0.19045
Windows Kernel 10.0.19041.4235
System Informer 3.0.7479 (fe48085)
[ ] Don't show this message again  [OK]

19041.4235

this is a Release Preview build which is not supported so this is expected.

Windows 11 23H2 10.0.22631
Windows Kernel 10.0.22621.3374
System Informer 3.0.7526 (863858c)
ntoskrnl.zip

Windows 10 22H2 10.0.19045
Windows Kernel 10.0.19041.4239
System Informer 3.0.7526(863858c)

Well, I shouldn't have installed the cumulative update of March.

I get this.

Updater for some reason doesn't check that Systeminformer exits completely.
Window closes, but process doesn't exit for some more time.
I have 96% of ram used.

10.0.22621.3374, 10.0.19041.4239 - https://github.com/winsiderss/systeminformer/commit/3de9d4bf4bb95e598fa4be6fb726f7ec6098ad71
3.0.7526 > Help > Check for updates - 👍

10.0.22621.3374, 10.0.19041.4239 - https://github.com/winsiderss/systeminformer/commit/3de9d4bf4bb95e598fa4be6fb726f7ec6098ad71
3.0.7546 - Help > Check for updates - 👍

KB5036892 (OS Builds 19044.4291 and 19045.4291)

ntoskrnl.zip

ntoskrnl.zip

10.0.22621.3527, 10.0.19041.4355 - https://github.com/winsiderss/systeminformer/commit/fc042be5774f278f515f32682b8f41bfd45a9b70
3.0.7579 - Help > Check for updates - 👍

10.0.26100.268
ntoskrnl.zip

Is that insider version?

26100.x will be 24H2, but they finiahd it already so that OEMs can preinstall new Devices with that version.

Just as a little tidbit of info for those who may have been on the release channel like I was, Version 3.0.7579 is on the Canary update channel so if you currently have 3.0.7578 installed and are getting this error, go to Help > Switch Update Channel > Canary and allow it to check for updates and authorize the install which will automatically download 7579. Hope this helps anyone who may have still been stuck on this. In my specific case, this applied to Windows 11 23H2 with Kernel version 10.0.22621.3527.
Hadn't seen this mentioned so I figured I'd help out for the sake of people maybe googling the issue.

KB5037768 (OS Builds 19044.4412 and 19045.4412)

Windows Server 2022 x64:
https://msdl.microsoft.com/download/symbols/ntoskrnl.exe/3A6EB0D31047000/ntoskrnl.exe
https://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/C339CA26E8E26BB7F4C9BB7B8244A46A1/ntkrnlmp.pdb

Uploading ntoskrnl.zip…

Same thing here after got cumulative update recently.

10.0.22621.3593, 10.0.20348.2461, 10.0.19041.4412, 10.0.17763.5820 - https://github.com/winsiderss/systeminformer/commit/4af54b68bdc77b144d3f7de34ba68aeaedc94584
3.0.7643 - Help > Check for updates - 👍

does not seam to quite work

latest version is 7643
you have 7548

check for update doe snot give me 7643 also not on https://systeminformer.sourceforge.io/downloads
may be its still building

change update channel to canary.

how i change the channel to canary?

and with process hacker 2?

uninstall it and install system informer.

Latest version is 3.0.7645

There is a hotfix/Out of Band Update for 1809:
KB5039705 (OS Build 17763.5830) Out-of-band
https://support.microsoft.com/en-us/topic/may-23-2024-kb5039705-os-build-17763-5830-out-of-band-2285667a-13a3-4fd9-98a0-e980eb996aac

ntoskrnl_17763.5830.zip

10.0.17763.5830 - https://github.com/winsiderss/systeminformer/commit/08de40d791fac0914267e64d6552bc195fa7943e
3.0.7660 - Help > Check for updates - 👍

3.0.7660 - Help > Check for updates - 👍

thanks, 3.0.7660 works fine

@sequencerr switch to the Canary channel.

This is the new preview update, which is not jet supported.:
May 29, 2024—KB5037853 (OS Builds 22621.3672 and 22631.3672) Preview
https://support.microsoft.com/en-us/topic/may-29-2024-kb5037853-os-builds-22621-3672-and-22631-3672-preview-dcf14fd8-84d6-4234-9d5b-784c319cd7cf
Maybe team is busy to add this build and wait for patchday next tuesday.

New patchday, new update requests:
KB5039211 (OS Builds 19044.4529 and 19045.4529)

Wired, that SI says 4522, but winver says 4529

New patchday, new update requests:
KB5039211 (OS Builds 19044.4529 and 19045.4529)

Wired, that SI says 4522, but winver says 4529

ok, ntoskrnl.exe version is 4522

KB5039217 (OS Build 17763.5936)

(here also kernel is 5933, UBR is 5936)
ntoskrnl_17763.5933.zip
KB5039212 (OS Builds 22621.3737 and 22631.3737)
KB5039227 (OS Build 20348.2527)

Huh, well... I'll gonna stick to the old version until System Informer "kernel-driver" compatible with the new build or kernel.

Support for recent kernels was added here: https://github.com/winsiderss/systeminformer/commit/2375ee344ef8f64c41e34dc9189ec4a44b736681
As some of you might be aware we're working on sorting out some issues with the updater and versioning, once that is taken are of we'll publish another build with the recent kernel support. All of this effort is in support of an official fully stable release and version 3.1.x - thank you for your patience and understanding.

Server 2022 x64
https://msdl.microsoft.com/download/symbols/ntoskrnl.exe/5E236E981047000/ntoskrnl.exe
https://msdl.microsoft.com/download/symbols/ntkrnlmp.pdb/BA02CB8F36DB1DACC5DB9F1ED97AAC961/ntkrnlmp.pdb

Latest Server 2022 was already added:
https://github.com/winsiderss/systeminformer/blob/a871402f3ee3a21e80c0314653702d4dae092157/kphlib/kphdyn.xml#L284-L285

KB5039302 (OS Builds 22621.3810 and 22631.3810) Preview

10.0.19041.4597, 10.0.22621.3810 - https://github.com/winsiderss/systeminformer/commit/ae7f4c9d4b1d6966cef4ced541f99b0d921b4343

KB5039304 (Build 26100.1000)
KB page not online jet, but released on Windows Update.
ntoskrnl_26100.1000.zip

Btw, do you also need the ntkrla57.exe which is used for systems that support Intel 5-level paging?

Eventually but now right now. The driver supports it but the dynamic data format doesn't - so YMMV on LA57. I'm hoping to eventually move all the dynamic data handling to a service which will solve this in a more elegant way.

3.1.24184.1 - Help > Check for updates - 👍

New Month, new Patchday:
KB5040427 (OS Builds 19044.4651 and 19045.4651)

Ah dang it Microsoft, again? Every Patch Tuesday got System Informer kernel mode driver suffered again! Hopefully the team will figure it out quick unlike last time on 3.1.
Sent from my iPhone 6+ lol

On 10 Jul 2024, at 01.45, MagicAndre1981 @.***> wrote:
New Month, new Patchday:
KB5040427 (OS Builds 19044.4651 and 19045.4651)
image.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

10.0.26100.1150, 10.0.22621.3880, 10.0.20348.2582, 10.0.19041.4648, 10.0.17763.6054 - https://github.com/winsiderss/systeminformer/commit/16df3a4dc5d71dba4a16b59e97c725335f6d3b9c
3.1.24192.0 - Help > Check for updates > Canary > Check - 👍

@jxy-s is my impression correct that in most cases the fix is just to allow a higher kernel version?
That is the structures don't change that often you just want to be on the safe side and only allow DynData to be used with known compatible builds.
So I wonder if it would be possible to determine on the live system if a certain DynData is still valid and then use if it that check passed.
Or leave it to the user show a notification "Current DynData is not know to be compatible, (and it looks wrong / but it looks right), do you want to use it at YOUR OWN RISK?"
And remember the user's choice for the current kernel build and DynData version so don't ask each time.
Do you think that would be a viable approach? I mean as long as its at the users own risk IMHO its fine people have the right to crash their own systems.

@jxy-s is my impression correct that in most cases the fix is just to allow a higher kernel version?
That is the structures don't change that often you just want to be on the safe side and only allow DynData to be used with known compatible builds. So I wonder if it would be possible to determine on the live system if a certain DynData is still valid and then use if it that check passed. Or leave it to the user show a notification "Current DynData is not know to be compatible, (and it looks wrong / but it looks right), do you want to use it at YOUR OWN RISK?" And remember the user's choice for the current kernel build and DynData version so don't ask each time.
Do you think that would be a viable approach? I mean as long as its at the users own risk IMHO its fine people have the right to crash their own systems.

Hmm, interesting one. So when that DynData not supported on those Tuesday Patch build every month, does it'll gonna risk Windows to crash infinite or something like that?

Hmm, interesting one. So when that DynData not supported on those Tuesday Patch build every month, does it'll gonna risk Windows to crash infinite or something like that?

Well if you try using DynData which does not match your kernel's internal structures its likely it will crash.
Although IMHO one could devise a mechanism to make this more fail safe, for example testing addresses read from the structures first with MmIsAddressValid, and alike...
To make it as safe as possible one could have this mechanisms on systems which don't run insider builds disabled by default, for the user to enable. And only on insider builds use the more risky approach.

Hmm, interesting one. So when that DynData not supported on those Tuesday Patch build every month, does it'll gonna risk Windows to crash infinite or something like that?

Well if you try using DynData which does not match your kernel's internal structures its likely it will crash. Although IMHO one could devise a mechanism to make this more fail safe, for example testing addresses read from the structures first with MmIsAddressValid, and alike...
To make it as safe as possible one could have this mechanisms on systems which don't run insider builds disabled by default, for the user to enable. And only on insider builds use the more risky approach.

@DavidXanatos Oh, I see. So this doesn't affect to Patch Tuesday build every month, right? Or could affected too?

New Preview Updates at end of month:
KB5040527 (OS Builds 22621.3958 and 22631.3958) Preview
https://support.microsoft.com/en-us/topic/july-25-2024-kb5040527-os-builds-22621-3958-and-22631-3958-preview-de3e1e24-0c07-4210-9777-8e03a1446bae
KB5040525 (OS Build 19045.4717) Preview
https://support.microsoft.com/en-us/topic/july-23-2024-kb5040525-os-build-19045-4717-preview-381f029e-b20e-4a0f-9b7e-695ee7845168
24H2 is only RP update, so you can skip that.

10.0.26100.1252, 10.0.19041.4717, 10.0.14393.7155, 10.0.10240.20708 - https://github.com/winsiderss/systeminformer/commit/d6a21858b530b101cc74faafc40e7325594aa1f9
10.0.22621.3958 - https://github.com/winsiderss/systeminformer/commit/ae1dd2f411b05a9344fdf089865a973b9b0413e0
3.1.24208.0 - Help > Check for updates > Canary > Check - 👍

24H2 is only RP update, so you can skip that.

now it is released to public as KB5040529 - 26100.1301

New Patchday, new kernel requests:
KB5041580 (OS Builds 19044.4780 and 19045.4780)

KB5041578 (OS Build 17763.6189)

ntoskrnl_17763.6189.zip

KB5041585 (OS Builds 22621.4037 and 22631.4037)
KB5041571 (OS Build 26100.1457)
KB5041160 (OS Build 20348.2655)

KB5041585 (OS Builds 22621.4037 and 22631.4037)
KB5041571 (OS Build 26100.1457)
KB5041160 (OS Build 20348.2655)

Interesting, Microsoft now likely changed the cycle of Patch Tuesday now at the middle of the month instead of first day or week in the month likely? Or maybe they forgot about it before 24H2 rolls out to public?

I think it is second tuesday of the month.
Which is today.

yes, it is always the 2nd tuesday each month

I think it is second tuesday of the month. Which is today.

@kotenok2000 Hmm I see, probably in Microsoft HQ still currently Tuesday, meanwhile in Indonesia already Wednesday.

I think it is second tuesday of the month. Which is today.

@kotenok2000 Hmm I see, probably in Microsoft HQ still currently Tuesday, meanwhile in Indonesia already Wednesday.

When Microsoft / Windows is talking about date / time, often times it means Redmond time zone. Meaning PST / PDT or UTC-8 / UTC-7. I believe Raymond Chen has article about this, because of course he has.

Could someone explain what is the deal with so many people having this error message because I have it too. I even tried SystemInformer on a fresh Win11 VM, and the same error occurs there.
(This is the error from my host OS)
Is my Windows version out of date, or is it my kernel, or system informer?

The System Informer driver accesses undocumented windows Kernel structures, these may change with any new build of the kernel in a unforeseeable way, and using outdated offsets can easily lead to a BSOD, and that is not good.
That said, these structures do not change that often, System Informer simply opts to be certain it will not cause a BSOD and only uses offsets it knows are valid for the current build.
The alternative would be to assume the last known offsets are still valid and just YOLO it hoping for the best.
The users would then come here and post that System Informer caused a BSOD instead of coming here and complaining about this error message.
So being a everyone is responsible for them selves and sure give anyone the means to shoot themselves in the foot type of person I would greatly appreciate an option to dismiss the error message and try the last known offsets, if it crashes it crashes.
So I would like this error to be turned into a dismissable warning.
That said I already had to once re install a PC after a System Informer driver related BSOD as it caused File System corruption and it was a not yet backup ed new machine, sooo..... may be being able to dismiss the Warning is not the best idea in the end LOL
I think what one could do is to try to test if the last known offsets are valid, for example testing addresses read from the structures first with MmIsAddressValid, and alike... so that the users would be offered the option to dismiss the warning only if its exceedingly likely that the offsets will still work.
I believe this would be a great usability improvement to System Informer, especially for users of insider builds.

10.0.26100.1455, 10.0.22621.4036, 10.0.20348.2652, 10.0.19041.4780, 10.0.17763.6189, 10.0.14393.7254, 10.0.10240.20747 - https://github.com/winsiderss/systeminformer/commit/390c20cdee82c49e23f034dde2239479c1574f42
3.1.24232.0 - Help > Check for updates > Canary > Check - 👍

do you have this?

Btw, is the start type supposed to be Disabled?

same for me, so looks like default behavior

New Windows Preview Update is out:
KB5041587 (OS Builds 22621.4112 and 22631.4112) Preview

New Windows Preview Update is out:
KB5041587 (OS Builds 22621.4112 and 22631.4112) Preview

this update includes AMD Performance improvements, it is likely that more people, compared to normal preview updates, will install the update and get the warning about kernel not supported.
ntoskrnl_22621.4111.zip
can you please add this a bit faster? Or do you wait for a general release of the 24H2 update, too?

Windows 10 22H2 also got a new preview update:
KB5041582 (OS Build 19045.4842) Preview

@User4716

Btw, is the start type supposed to be Disabled?

Yes. This is the correct settings. The start type is set to disabled after the driver loads because we don't want the driver using any resources unless the application is running or any issues or bugs with auto-start from crashing the system.

Windows 10 22H2 also got a new preview update:

@MagicAndre1981
We added support for CI to automate new builds but Microsoft hasn't published any metadata for those versions.

Windows 11 24H2 10.0.26100
Windows Kernel 10.0.26100.1591
System Informer 3.1.24233.0 Canary
I am not running a Release Preview Build

Could someone explain what is the deal with so many people having this error message because I have it too. I even tried SystemInformer on a fresh Win11 VM, and the same error occurs there.
(This is the error from my host OS)
Is my Windows version out of date, or is it my kernel, or system informer?

The System Informer driver accesses undocumented windows Kernel structures, these may change with any new build of the kernel in a unforeseeable way, and using outdated offsets can easily lead to a BSOD, and that is not good.
That said, these structures do not change that often, System Informer simply opts to be certain it will not cause a BSOD and only uses offsets it knows are valid for the current build. The alternative would be to assume the last known offsets are still valid and just YOLO it hoping for the best. The users would then come here and post that System Informer caused a BSOD instead of coming here and complaining about this error message.
So being a everyone is responsible for them selves and sure give anyone the means to shoot themselves in the foot type of person I would greatly appreciate an option to dismiss the error message and try the last known offsets, if it crashes it crashes. So I would like this error to be turned into a dismissable warning.
That said I already had to once re install a PC after a System Informer driver related BSOD as it caused File System corruption and it was a not yet backup ed new machine, sooo..... may be being able to dismiss the Warning is not the best idea in the end LOL
I think what one could do is to try to test if the last known offsets are valid, for example testing addresses read from the structures first with MmIsAddressValid, and alike... so that the users would be offered the option to dismiss the warning only if its exceedingly likely that the offsets will still work.
I believe this would be a great usability improvement to System Informer, especially for users of insider builds.

I would appreciate an official statement on this suggestion if implemented it would eliviate a lot of the pain of users in the insider channels.

Could someone explain what is the deal with so many people having this error message because I have it too. I even tried SystemInformer on a fresh Win11 VM, and the same error occurs there.
(This is the error from my host OS)
Is my Windows version out of date, or is it my kernel, or system informer?

The System Informer driver accesses undocumented windows Kernel structures, these may change with any new build of the kernel in a unforeseeable way, and using outdated offsets can easily lead to a BSOD, and that is not good.
That said, these structures do not change that often, System Informer simply opts to be certain it will not cause a BSOD and only uses offsets it knows are valid for the current build. The alternative would be to assume the last known offsets are still valid and just YOLO it hoping for the best. The users would then come here and post that System Informer caused a BSOD instead of coming here and complaining about this error message.
So being a everyone is responsible for them selves and sure give anyone the means to shoot themselves in the foot type of person I would greatly appreciate an option to dismiss the error message and try the last known offsets, if it crashes it crashes. So I would like this error to be turned into a dismissable warning.
That said I already had to once re install a PC after a System Informer driver related BSOD as it caused File System corruption and it was a not yet backup ed new machine, sooo..... may be being able to dismiss the Warning is not the best idea in the end LOL
I think what one could do is to try to test if the last known offsets are valid, for example testing addresses read from the structures first with MmIsAddressValid, and alike... so that the users would be offered the option to dismiss the warning only if its exceedingly likely that the offsets will still work.
I believe this would be a great usability improvement to System Informer, especially for users of insider builds.

I would appreciate an official statement on this suggestion if implemented it would eliviate a lot of the pain of users in the insider channels.

The suggestion to use MmIsAddressValid or to otherwise "try" validating internal offsets at runtime is fundamentally misguided. It reflects a misunderstanding of the problem space and demonstrates a disregard for the operating environment of the kernel. As we have communicated multiple times, the design of the System Informer driver and its dynamic data structure intentionally prevents loading or using unauthorized dynamic data with the associated kernel.
System Informer fully acknowledges the privilege of having a Microsoft-signed kernel driver, and we take every measure to uphold the architecture and security of the operating system. Allowing the bypass of this integrity check would compromise that privilege and the trust in the system.
Regarding support for preview builds, we are actively working on automating the process of generating, vetting, and signing dynamic data. At present, due to time constraints, we are unable to support all kernel builds and have chosen to limit the number of kernels we can accommodate. Once automation is in place, we aim to support a wider range of kernels. However, even with automation, there will be some delay in making data available for the latest builds, although this should be significantly reduced.
As the code is open source, you are free to modify it to bypass these checks if desired. You can build your own driver accordingly. If you cannot sign the driver, you will need to configure your operating system to load unsigned drivers. There are also instructions available for self-signing, which also requires building a new driver.
@DavidXanatos, this thread is not intended for suggesting changes, so I will mark your suggestions and comments here as off-topic. You've made suggestions on several occasions in different threads, and a more suitable place for this discussion would be issue #1963. I'm also happy to continue this conversation with you personally. Please feel free to email me or send a direct message on Discord.

We added support for CI to automate new builds but Microsoft hasn't published any metadata for those versions.

which metadata do you need?

10.0.26100.1591, 10.0.22621.4111, 10.0.19041.4842 - https://github.com/winsiderss/systeminformer/commit/c1798de12a7115f5ff11f6138ca89d0596a439c0
3.1.24244.0 - Help > Check for updates > Canary > Check - 👍

KB5043064 (OS Builds 19044.4894 and 19045.4894)
KB5043050 (OS Build 17763.6293)
ntoskrnl_17763.6292.zip
KB5043076 (OS Builds 22621.4169 and 22631.4169)
KB5043080 (OS Build 26100.1742)
KB5042881 (OS Build 20348.2700)

I would like to inform everyone involved in this thread that the next build will include significant changes to dynamic data. These changes were necessary to better support the automation of dynamic data generation. I have gone through and generated the dynamic data manifest for a large number of supported kernels.
As a result, we will be trialing support for ntkrla57 and preview builds 🎉. However, please note that for preview builds, Microsoft may not always provide the information needed to generate the dynamic data. Our long-term goal is to fully automate both the generation and validation of dynamic data, but we still have some work to do in fully vetting the current tooling.
That being said, since there are significant changes and a regeneration of dynamic data, there is a possibility that some kernels may have been missed or other issues could arise. I appreciate your patience as we work through these.
A new build will be available soon™.

Does this mean that you will be able to support Insider channels, such as Release Preview, as well?

Does this mean that you will be able to support Insider channels, such as Release Preview, as well?

Yes, as long as Microsoft provides the necessary information. There are two scenarios to consider. First, with the automated metadata we currently have access to, testing shows we achieve around 90% coverage of kernels. However, in some cases, we may need to manually retrieve the kernel binary, either through user submission or by other alternative means.

Does this mean that you will be able to support Insider channels, such as Release Preview, as well?

Yes, as long as Microsoft provides the necessary information. There are two scenarios to consider. First, with the automated metadata we currently have access to, testing shows we achieve around 90% coverage of kernels. However, in some cases, we may need to manually retrieve the kernel binary, either through user submission or by other alternative means.

Are you using the provided PDB files or also other data sources?

Does this mean that you will be able to support Insider channels, such as Release Preview, as well?

Yes, as long as Microsoft provides the necessary information. There are two scenarios to consider. First, with the automated metadata we currently have access to, testing shows we achieve around 90% coverage of kernels. However, in some cases, we may need to manually retrieve the kernel binary, either through user submission or by other alternative means.

Are you using the provided PDB files or also other data sources?

We are positioned to leverage a multiple of data sources.

I would like to inform everyone involved in this thread that the next build will include significant changes to dynamic data. These changes were necessary to better support the automation of dynamic data generation. I have gone through and generated the dynamic data manifest for a large number of supported kernels.
As a result, we will be trialing support for ntkrla57 and preview builds 🎉. However, please note that for preview builds, Microsoft may not always provide the information needed to generate the dynamic data. Our long-term goal is to fully automate both the generation and validation of dynamic data, but we still have some work to do in fully vetting the current tooling.
That being said, since there are significant changes and a regeneration of dynamic data, there is a possibility that some kernels may have been missed or other issues could arise. I appreciate your patience as we work through these.
A new build will be available soon™.

is this the "Saturday, 14th of September, 2024 Canary" build
Also a small OT request: would it be possible to link with every canary release the exact git tag it was built from? Or may be that's already the case and I just don't know where to find that info LOL

Also a small OT request: would it be possible to link with every canary release the exact git tag it was built from? Or may be that's already the case and I just don't know where to find that info LOL

In check for updates dialog you see the short git hash

I noticed that the latest DynData are not for the latest ARM64 Win11 yet:

I noticed that the latest DynData are not for the latest ARM64 Win11 yet:

Added a few more ARM64 kernels in these commits:
https://github.com/winsiderss/systeminformer/commit/f247ebc4e7e09bdaa853fadefeb1fc13e11413bf
https://github.com/winsiderss/systeminformer/commit/bf387c777ba21242fe645d84ecc5160707210578
Unsure exactly why those were not reported to me automatically, will investigate that - but they'll be available in the next build 👍.

Unsure exactly why those were not reported to me automatically, will investigate that - but they'll be available in the next build 👍.

has your logic detected the latest RP Updates for  Windows 11 23H2 (KB5043145) and 24H2(KB5043178)?

Or do you still only support retail updates?

The automation primarily depends on SystemInformer running on those builds and checking for updates at least once. According to my data, it hasn’t done so yet. However, I have alternative methods to backfill any missing information.

Or do you still only support retail updates?

We’re currently tentatively trialing support for all releases, not just retail.

Running latest Win11

Running Win11 screenshot

You're running an outdated version of System Informer: Help > Check for updates > Canary > Check

Umm, just a quick report to the latest Canary release.
Didn't wanna submit a new issue just for this, so I hope this is the right place to put it.
The 3.1.24276 Canary release(Which I just updated couple minutes ago)
Somehow made my OS froze and unresponsive, had to cold reboot my PC.
I rule out all other software down to this one, since I only just updated today.
Currently running on: Win 10 Pro 22H2(19045.4894)
Already rolled back to 3.1.24258.0 Canary, which is perfectly normal on my end.

Umm, just a quick report to the latest Canary release. Didn't wanna submit a new issue just for this, so I hope this is the right place to put it. The 3.1.24276 Canary release(Which I just updated couple minutes ago) Somehow made my OS froze and unresponsive, had to cold reboot my PC several times. I ruled out all other software down to this one, since I only just updated today. Currently running on: Win 10 Pro 22H2(19045.4894) Already rolled back to 3.1.24258.0 Canary, which runs perfectly normal on my end.

@fansteven7 would you please create a new issue for this? I'm not seeing this behavior on my end on 22H2. It might have something to do with your environment. I'll respond in the new ticket with some options to collect more information so that I can help identify the a root cause.

@fansteven7 would you please create a new issue for this? I'm not seeing this behavior on my end on 22H2. It might have something to do with your environment. I'll respond in the new issue with some options to collect more information so that I can help identify the a root cause.

Apologies, the issue reoccurred after putting my PC in idle mode for hours(Not hibernating though)
I'm gonna have to do some more testing, to see if something else is at play.
Hopefully, the "Log" feature within System Informer will be of help.
Will submit a new issue if I found any connection to it.
Thanks for your time

@dandeliondream switch to the canary channel, please - Help > Check for updates > Canary > Check

I think the kernel works now! I do have a different issue now- I assumed that having the kernel be active (sorry if I'm not using the correct terminology) would allow me to kill processes that were previously telling me "access denied," but it doesn't. My PC won't let me delete files for ReasonLabs until the processes are terminated. Are there certain settings that need to be enabled to do this?

My PC won't let me delete files for ReasonLabs until the processes are terminated. Are there certain settings that need to be enabled to do this?

ask this in discussions, but you probably need to close open handles of the files first.

Latest version canary channel updates to is 3.1.24305.0

This is Windows 11 Enterprise LTSC 2024. Latest canary producing this error as of time of writing. Let me know if you need me to send my ntoskrnl.exe file and/or where to find the PDB needed.

Thank you for the new build; my kernel is now supported by the driver too!

Windows Server 2025 (W11 based) latest build

Any suspected ETA? Any obvious obstacles for foreseeable future, postponing implementation?

switch to the canary channel via Help -> Check for updates -> Canary -> Check as this version is already supported here.

switch to the canary channel via Help -> Check for updates -> Canary -> Check as this version is already supported here.
And in a few minutes new Windows updates get released and the tool needs a new update.

ntoskrnl.zip

10.0.26100.2605 was added yesterday: https://github.com/winsiderss/systeminformer/commit/b71dc84d0bc4528fd6294958099bd1ddd758e0a9
Holding on a build, we're finishing up some other work, will have another build soon.

Recent KB Update (December 10, 2024—KB5048652) Seems to have broken kernel compatibility. Here is the error window below, looks like new compatible SI build is rolling soon, however, I thought I'd let you know in case you were not aware... Thanks!

Windows 10 21H2 10.0.19044
Windows Kernel 10.0.19041.5247
System Informer 3.1.24333.0 Canary
[ ] Don't show this message again  [OK]
Oh noes

When will it be fixed?

That would require undoing work elsewhere. @dmex is making changes to the pipelines we use for releasing. I would rather not undo his work there.
If it were only me I wouldn't put master or our pipelines in a state that prevents us from releasing. But I'm not the only maintainer. We appreciate your patience while this work gets completed.

I get a new error (0xc000000d) with latest version:
[Main Instruction]
Unable to load kernel driver

[Content]
Unable to restart.

Einem Dienst oder einer Funktion wurde ein ungültiger Parameter übergeben. (0xc000000d)

Windows 10 22H2 10.0.19045
Windows Kernel 10.0.19041.5247
System Informer 3.1.24360.0 Canary
Process State 0x000003fa

this happens under Windows 10 22H2

this happens under Windows 10 22H2 and also happens after a reboot.

Happens on Windows 11 24H2 too :(

Here's the English version of the first dialog:

I'm on the latest GE release of Win11 24H2 IoT LTSC, kernel 26100.2605. Just applied the updated build seconds ago, so I know I'm on latest Canary.

[Window Title]
System Informer
[Main Instruction]
Unable to load kernel driver
[Content]
The kernel driver is not yet supported on this kernel version. Request support by submitting a GitHub issue with the Windows Kernel version.
Windows 11 24H2 10.0.26100
Windows Kernel 10.0.26100.2605
System Informer 3.1.24298.0 Release
00-8664-4f6c47b9-0144f000
[ ] Don't show this message again  [ОК]
also
[Window Title]
System Informer
[Main Instruction]
Unable to load kernel driver
[Content]
The kernel driver is not yet supported on this kernel version. Request support by submitting a GitHub issue with the Windows Kernel version.
Windows 11 24H2 10.0.26100
Windows Kernel 10.0.26100.2605
System Informer 3.1.24318.0 Canary
00-8664-4f6c47b9-0144f000
[ ] Don't show this message again  [ОК]

[Window Title] System Informer
[Main Instruction] Unable to load kernel driver
[Content] The kernel driver is not yet supported on this kernel version. Request support by submitting a GitHub issue with the Windows Kernel version.
Windows 11 24H2 10.0.26100 Windows Kernel 10.0.26100.2605 System Informer 3.1.24298.0 Release
00-8664-4f6c47b9-0144f000
[ ] Don't show this message again [ОК]
also [Window Title] System Informer
[Main Instruction] Unable to load kernel driver
[Content] The kernel driver is not yet supported on this kernel version. Request support by submitting a GitHub issue with the Windows Kernel version.
Windows 11 24H2 10.0.26100 Windows Kernel 10.0.26100.2605 System Informer 3.1.24318.0 Canary
00-8664-4f6c47b9-0144f000
[ ] Don't show this message again [ОК]

You're not on the latest Canary build, but latest is also not working; this is a known issue as the build method is undergoing some changes (as stated in previous comments by the maintainer). Once a new Canary build surfaces with the new build method intact, we should see the kernel-mode driver functioning normally again.

3.1.24366.0 (2c03cc2b) solves the driver loding issue, but broke my UI ( see #2350 )


Build dir not initialized (when running Build the application)

When running the follwing command:
Flatpak: Build the application the following error is raised
> flatpak build --share=network --nofilesystem=host --filesystem=<project_path> --filesystem=<project_path>/.flatpak/repo --env=PATH=$PATH:/usr/lib/sdk/rust-stable/bin --env=RUSTFLAGS=--remap-path-prefix =../ --env=CARGO_HOME=/run/build/project_name/cargo --env=RUST_BACKTRACE=1<project_path>/.flatpak/repo cargo fetch --manifest-path Cargo.toml --verbose <
error: Build directory =../ not initialized, use flatpak build-init

That's interesting, do you have your project somewhere so I can give it a try locally?

Oh, remove the --remp-path-prefix from your manifest, restart vscode and try again?

The project is here: https://github.com/toger5/Spectre-gtk
(I will try your propesed changed and edit this message)

All good then, thanks for confirming it works!


Added json output option.

This adds a -json flag to the analyze-local-images tool to be able to further process the data.

If you're looking for machine readable output, why not use the API directly rather than going through the CLI tool?

I considered doing this, but there's some logic in the cli tool to extract
the image, resolve the layers from the image tag, etc, which is not present
in the API yet.
An endpoint which accepts an image tag and provides the vulnerabilities of
its layers would be great, but I guess this would be quite an effort, no?
Jimmy Zelinskie<EMAIL_ADDRESS>schrieb am Di., 24. Mai 2016
20:43:

If you're looking for machine readable output, why not use the API
https://github.com/coreos/clair/blob/master/api/v1/README.md directly
rather than going through the CLI tool?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/coreos/clair/pull/184#issuecomment-221360007

you could use github.com/wemanity-belgium/hyperclair
the command expose a 'hyperclair report - -format json /'
it will replace analyze image tool soon
Le mar. 24 mai 2016 22:06, Magnus Kulke<EMAIL_ADDRESS>a écrit :

I considered doing this, but there's some logic in the cli tool to extract
the image, resolve the layers from the image tag, etc, which is not present
in the API yet.
An endpoint which accepts an image tag and provides the vulnerabilities of
its layers would be great, but I guess this would be quite an effort, no?
Jimmy Zelinskie<EMAIL_ADDRESS>schrieb am Di., 24. Mai 2016
20:43:

If you're looking for machine readable output, why not use the API
https://github.com/coreos/clair/blob/master/api/v1/README.md directly
rather than going through the CLI tool?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/coreos/clair/pull/184#issuecomment-221360007

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/coreos/clair/pull/184#issuecomment-221378325

@jgsqware i looked at this yesterday, seems the docker-machine support was merged just now. I was wondering whether it would happen at all, since the PR was old. I'm fine with closing the PR then.


gpu memory consumption kept increasing all the time when just did executor.forward operation

I made a file recorder following the example code "example/fcn-xs/data.py/FileIter" dataiter. Gpu memory consumption kept increasing all the time till out of memory error, when  the data of dataiter is passed   into executor and only did executor.forward() operation circularly. Bellow code could reproduce the error.
import mxnet as mx
import mxlib
import model_vgg19

args = mxlib.config(root_path = "/home/gpu2/separate-reflection/dataset",
                 input_shape = (8,3,256,256),
                 flist_name = "../dataset/train_img.lst",
                 prefix='../model/sepRef',
                 save_iteration = 200,
                 load_iteration = 0,
  test_img="../test/mix/COCO_train2014_000000001764_COCO_train2014_000000078380.jpg")

dataiter = mxlib.ImageIter(args.root_path, args.flist_name, batch_size=args.input_shape[0],show_rf=True)
vgg_model = model_vgg19.get_model(args.input_shape,ctx=args.ctx)#model definition from "example/neural-style"

for e in range(args.max_num_epochs):
    dataiter.reset()
    for data in dataiter:      #data is numpy array
        vgg_model.data[:] = mx.nd.array(data["mix"],ctx=args.ctx)
        vgg_model.executor.forward()

Is there any problem in my code? If yes, please show some hints about how to solve it.
Or is this a bug needs to fixed?
Any information will be appreciated.

The code has been running well after i replaced the code vgg_model.data[:] = mx.nd.array(data["mix"],ctx=args.ctx) with vgg_model.data[:] = mx.nd.array(data["mix"]).
That means the operation, mx.nd.array(data,ctx=mx.gpu(0)) will create a new variable that occupy memory. Is this interpretation right?

Because there is no synchronization point, you are pushing too many operations into the engine. Add a executor.outputs[0].wait_to_read() before forward

Thanks for your reply @piiswrong.  The code is running successfully now.
I found another way to make code running without memory error by replacing vgg_model.data[:] = mx.nd.array(data["mix"],ctx=args.ctx) with vgg_model.data[:] = data["mix"]). But i don't know the second way is right or not.

assign from or to numpy array is always synchronization. Usually you will always want to copy data out to CPU, and that will be a synchronization and it is good to do so