feat: add initial implementation for DIM wallet stub

Description

Initial contribution for SSI DIM wallet stub application

Spring boot application
README and other documentation
GitHub Workflows
GitHub action
AUTHORS.md updated
Basic and working helm charts. No config added for Keycloak dependency

Why

Issue Link
Refs: 788
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines

[ ] I have performed IP checks for added or updated 3rd party libraries

[x] I have added copyright and license headers, footers (for .md files) or files (for images) //open source requirement

[x] I have performed a self-review of my own code

[x] I have successfully tested my changes locally

[x] I have added tests and updated existing tests that prove my changes work

[x] I have checked that new and existing tests pass locally with my changes

[x] I have commented my code, particularly in hard-to-understand areas

All secret alerts are false positives. These values are used as a sample request in API doc

IP ticket for wiremock lib: https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/15839

@nitin-vavdiya I'm providing already some information for the review of the project content, which should only be started once you're sure that this PR remains as is / unchanged, so only once https://github.com/eclipse-tractusx/ssi-dim-wallet-stub/pull/2#pullrequestreview-2233172056 is solved.
Relevant section in the Eclipse Foundation Handbook: https://www.eclipse.org/projects/handbook/#ip-project-content
As this PR represents the initial contribution and contains changes which were authored - not just by you (committer) but -also by contributors (see Authors), it needs to undergo a review of Project Content at the  Eclipse Foundation, for which you (as committer) need to open an issue in Gitlab using the the according issue template, see https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/wikis/Requesting-a-Review.
Besides the Basic Information, please also provide additional information about why this review of Project Content is needed (like that this is an code initial contribution).
Here an example of a recent review of Project content, merely as example https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/15836.
There it was also mentioned that it's a good idea to upload the state of the feature branch of the pull request (which isn't changed again) in a zip file to the IP issue in Gitlab, see https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/15836#note_2617332, you can download a zip file by using the according GH feature:

I also noticed that the following lib is still marked as restricted in the DEPENDENCIES file:
maven/mavencentral/org.wiremock/wiremock-standalone/3.9.1, (Apache-2.0 AND EPL-2.0) OR (Apache-2.0 AND GPL-2.0-only AND NOASSERTION), restricted, clearlydefined

Did you create an IP issue? If so, could you link it?
I think you should only open the IP issue for the project content / initial contribution once also the all 3rd party libs are vetted.

Thanks for pointing this out.
I already create IP check for the restricted lib: IP issue
Further, this is used for testing only, I refactor tests and removed this dependency. Ref: https://github.com/eclipse-tractusx/ssi-dim-wallet-stub/pull/2/commits/8a041c3b4be3f2595da9e8aa42bf69e4e9108358
I closed this IP check issue for WireMock.
Now there is no any restricted lib in the code.

could you please make sure that your pr title aligns better with conventional commit messages? for instance feat: add initial implementation for DIM wallet stub Also, please take care of the GitGuardian findings: you mentioned that they were false positives, with you committer rights you are enabled to mark them accordingly

PR title changed
I cannot see this repository in the GitGuardian app. maybe someone needs to give access.

@nitin-vavdiya I'm providing already some information for the review of the project content, which should only be started once you're sure that this PR remains as is / unchanged, so only once #2 (review) is solved.
Relevant section in the Eclipse Foundation Handbook: https://www.eclipse.org/projects/handbook/#ip-project-content
As this PR represents the initial contribution and contains changes which were authored - not just by you (committer) but -also by contributors (see Authors), it needs to undergo a review of Project Content at the Eclipse Foundation, for which you (as committer) need to open an issue in Gitlab using the the according issue template, see https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/wikis/Requesting-a-Review.
Besides the Basic Information, please also provide additional information about why this review of Project Content is needed (like that this is an code initial contribution).
Here an example of a recent review of Project content, merely as example https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/15836. There it was also mentioned that it's a good idea to upload the state of the feature branch of the pull request (which isn't changed again) in a zip file to the IP issue in Gitlab, see https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/15836#note_2617332, you can download a zip file by using the according GH feature:

Thank you for the information.
IP check ticket is created: https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/15838

As a source code ZIP file is uploaded in IP check,
Additional changes will be made in separate pull requests, unless the changes are mandatory.

could you please make sure that your pr title aligns better with conventional commit messages? for instance feat: add initial implementation for DIM wallet stub Also, please take care of the GitGuardian findings: you mentioned that they were false positives, with you committer rights you are enabled to mark them accordingly

@nitin-vavdiya I'd find it odd if you couldn't manage the secret findings by GitGuardian with your committer rights.. don't you have the option to Skip when going to the Details of the check?

could you please make sure that your pr title aligns better with conventional commit messages? for instance feat: add initial implementation for DIM wallet stub Also, please take care of the GitGuardian findings: you mentioned that they were false positives, with you committer rights you are enabled to mark them accordingly

@nitin-vavdiya I'd find it odd if you couldn't manage the secret findings by GitGuardian with your committer rights.. don't you have the option to Skip when going to the Details of the check?

Done, I was looking for resolve issue like button, so it will not rise the same issue again (Same as sonarQube maybe)
Thanks

Merging this PR based on this comment


Well-Architecture Review answers not being saved

Yesterday I was able to complete an architecture review assessment, however, today I wasn't able to see the last answers that I made. I tried to create a new one with the same answers but with no results.

After completing all assessment pages, all answers were cleared:

Luckily I was able to save it as CSV before I finished, however, It did erased some days of work.


REOPEN NOW! @deepak1556 it not is question, it is new feature in web version.

          @deepak1556 it not is question, it is new feature in web version.

Originally posted by @ilixindri in https://github.com/microsoft/vscode/issues/187007#issuecomment-1666475406

Sorry, notifications system is complete in github,


feat: [custom widget] support SCSS syntax

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description

Add a TL;DR when description is extra long (helps content team)
Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation
and context. List any dependencies that are required for this change
Links to Notion, Figma or any other documents that might be relevant to the PR

PR fixes following issue(s)
Fixes # (issue number)

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

Summary by CodeRabbit

New Features

Added SCSS syntax support and CSS variables usage in tooltips.
Introduced styled components for better styling consistency across the app.
Enhanced the Custom Widget Builder with improved error message styling and tooltip content rendering.

Bug Fixes

Refined warning message conditions to reduce unnecessary warnings.
Ensured the selectedTab is always valid in the Custom Widget Builder's TabLayout.

Refactor

Updated function and component names for clarity and consistency (e.g., CSSEditor to StyleEditor, getBabelError to getError).
Restructured CSS styles for better layout and presentation in the Custom Widget Builder.

Chores

Removed unused CSS class definitions and adjusted existing ones for optimization.

/build-deploy-preview skipTests=true

/build-deploy-preview skipTests=true

/ok-to-test<EMAIL_ADDRESS>

@somangshu Yeah. Will be updating the documentation as well.


Kelvinamoaba/menu bar

Description
Implemented the common page Header.
Testing

Reviewers
@wsedor , please review

it seems that the changes in the other PRs was also added in here https://github.com/nsmq-ai/nsmqai/pull/15
please check and ensure this PR only has the change pertaining to the menu bar


istio ingress elb provisioning - aws private subnet

Bug description
We are trying to provision complete kubernetes cluster in AWS private subnet for the security reasons. Using KOPS for provisioning the K8S cluster and using istio for the mesh and the traffic routing (ingress, egress, etc).
Normally when we tried provisioning the Dev env (AWS public subnet) - istio provisioned elb on the public subnet and we were able to access the cluster using the ingress ELB. While we define private subnet for the cluster creation, istio is not provisioned the elb on the private subnet.
The status of the service see as "pending" with the kubectl output. ELB has NOT created in AWS -
istio-ingressgateway        LoadBalancer   <IP_ADDRESS>        15020:32419/TCP,80:31607/TCP,443:31426/TCP,31400:31097/TCP,15443:31829/TCP   3d18h
[ X] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
ISTIO ingress ELB to be provisioned in private subnet.
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
istioctl version
client version: 1.6.1
control plane version: 1.6.1
data plane version: 1.6.1 (15 proxies)
kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.10",
How was Istio installed?
$ curl -L https://istio.io/downloadIstio | sh -
$ istioctl install --set profile=demo
Environment where bug was observed (cloud vendor, OS, etc)
Cloud - AWS

This is not configured by Istio. We simple create Service of type=LoadBalancer, the rest is up to the Kubernetes install. Please refer to upstream Kubernetes or AWS documentation on how to configure this. Thanks!


Fastboot cannot find devices.

I am following the dev-board installation manual and I am not able to see the device in fastboot devices. I have tried with five different USB C cables, with various versions of fastboot (now I have 30.0.5). I have two Coral dev-board boards and it only happens to me on one. What can I do?

@jolloqui Which operating system are you working with and which version ?

On the host I have Ubuntu 20.04.

@jolloqui Could you try reflashing the board again using the sdcard method?
https://coral.ai/docs/dev-board/reflash/#flash-from-u-boot-on-an-sd-card

Yes, I have tried it, but when launching "fastboot devices" it still comes out empty.

@jolloqui humm
Can you share the outputs of lsusb on the dev board?

Hi, sorry about the delay but I haven't been able to try before.
I don't know how to run "lsusb" in u-boot since it is the only way I can connect to the dev-board.
From the host computer with the serial connected the output is:
usuario@HP:~$ lsusb
Bus 002 Device 004: ID 10c4:ea70 Silicon Labs CP2105 Dual UART Bridge
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
From the host computer with the data port connected the output is:
usuario@HP:~$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
As you can see it does not recognize any data USB.
I am not able to execute any "mdt" command since it cannot find the devices.
Thanks a lot

@jolloqui sorry, I mean over serial, not u-boot:
$ screen /dev/ttyUSB{id}

Then turn on the dev board and it should boot & ask you for a username/password, which will both be "mendel".
Then you can run:
$ sudo apt install usbutils
$ lsusb

I suspect that somehow the board's usb port is having issues which is causing your host to not being able to see it as a fastboot device. Here is what a normal lsusb should looks like:
mendel@red-finch:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Hi @Namburger,
As you have indicated, I have started from the serial port with screem but when I start I get these characters. I do not know if it's normal.

Once I have installed "usbutils" I get the following lines with "lsusb". Everything seems fine:

thank you!

Sorry I was wrong, I have tried with the dev-board that the installation worked for me and it already has mendel.
With the one that I don't have installed mendel doesn't start me on the serial port. I get a series of strange characters but there is no login.

I feel the mistake

@jolloqui
Sorry, the reason why you are getting garbage characters is because screen doesn't know what bitrate is being transferred, I forgot to mentioned:
screen /dev/ttyUSB{id} 115200

@Namburger
Excuse my ignorance, I didn't know what the bitrate number was for.
I have a question, can a board on which a linux mendel has never been installed can show a mendel login from the screem console?
In which I managed to install it, I login without problem but in the other one u-boot it always runs.
There seems to be a problem with the USB but I don't know how to check it.
Thank you very much

@jolloqui actually, I think I mis-understood the problem from the beginning, I thought you were trying to reflash a board without success, but it looks like one of the board just doesn't go into fastboot mode at all (and I suspect that is due to a faulty usb-c port).
To answer your question, if mendel haven't been installed,  you wouldn't be able to get a login screen, since u-boot is the only thing installed. Sorry for all of the confusion. The fact that you had one of the board flashed correctly and the second one just doesn't works tells me that there may be a HW issue. Could you shoot us an email to<EMAIL_ADDRESS>we can issue you a replacement, sorry again for this

Don't worry, I don't think I have explained myself very well either.
I really appreciate your work.
I will write to the support email.
A greeting.

@usbguru for awareness, expect an email from @jolloqui!


AUT-1210 add validate challenge method

@stevenclouston i've added the ruby key to the main env you can set the environment here
Using an env allows us to add approval rules etc
From my understanding of this github action, it does the tagging of the release as well automatically into github, which looks good


upgrade to 6.2.2

Hi,
Thank you on this PR, did you check that its works?
I checked out your branch and I get error
"Cannot read property 'onExpand' of undefined"

Hi, its my mistake I did the merge.
thanks


Creating a custom Viseme animation to get result of 2D SVG output like "redlips_front"

I'm looking to create custom viseme animations for lip syncing in my project.
Am I understanding the process correctly for creating an SVG with a custom 2D avatar?
To create my own viseme animation similar to 'redlips_front' - FE: 'bluelips_front', I'll likely need to follow these general steps:

Do I need to design the visemes - the specific lip shapes or visemes for the phonemes (all 22 visemes in our case)?

Do I need to design animations of visemes - create a sequence of frames or keyframes that animate the lips transitioning between the different visemes smoothly?

Next step is exporting the animation... Do I need to directly use my previously created animations with the Azure response.json? And Iterate one by one...
json from actual Azure API:

[
  {
    "offset": 50.0,
    "id": 0
  },
  ....

3.2. I couldn't find where to submit (FE: to Azure API to pass/create new type: 'bluelips_front')? Is it possible?
P.S. In the end, I want to get an SVG animated output (just like with "redlips_front" now).
Please advise on how I can create an avatar (using visemes + design)

@yulin-li @yinhew Please check and comment.

@yulin-li @yinhew
I've UPDATED the previous question.
Thank you in advance 👍

Hi @azatech thanks for your feedback.
The Azure TTS service doesn't support custom SVG for now. I will forward your feedback to our PM for future planning.


core: Tweak default AF options; AfMode now defaults typically to CAF

AF Mode now defaults to the highest supported mode (typically CAF) unless an explicit lens position or af_on_capture was requested. Speed and Range now default to "normal" rather than unset.
Signed-off-by: Nick Hollinghurst<EMAIL_ADDRESS>

LGTM


Fix go vet warnings

These were noticed using Go 1.7. Earlier versions may not have had all
of these issues.

https.go:376: assignment copies lock value to config:
crypto/tls.Config contains sync.Once contains sync.Mutex
examples/goproxy-yui-minify/yui.go:79: io.LimitedReader composite
literal uses unkeyed fields
proxy_test.go:508: unreachable code
transport/transport.go:308: unreachable code
transport/transport.go:658: unreachable code

Hi!
Did you see my comment?
Am I correct?

I think using this should address it, once Go 1.8 is out.

Can you please update the PR to clone the tls.Config?
Thanks
On Thu, Dec 8, 2016 at 10:16 AM, James Abley<EMAIL_ADDRESS>wrote:

I think using this should address it
https://go.googlesource.com/go/+/d24f446a90ea94b8, once Go 1.8 is out.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/elazarl/goproxy/pull/181#issuecomment-265679941, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAP4okAarzBtHLIsY2Hezjal-m5Cfw0Dks5rF7zXgaJpZM4JoRit
.

Will do, once Go 1.8 is out in January 2017.

Fixed in https://github.com/elazarl/goproxy/pull/595


Add horizontal Swipe gesture to change tabs

Is your feature request related to a problem? Please describe.
Add a horizontal Swipe Gesture to change the tabs, This should be configurable with a swippable parameter, We should also investigate if this does not interfere when the UI contains a horizontal scrollable or a draggable widget
Additional context
Add any other context or screenshots about the feature request here.

Have you implemented this feature?

Have you implemented this feature?
Can you give me a summary of some other PR and Issues are still active? Please sent me here or via work email. I wanna work on them but there are a lot, both fixed and not fixed yet. Thank you 😅.

@bebaoboy All the issues are upto date, if they are open they are not yet implemented. You are welcome to send PR.

Hi, do you think there is any drawback when using PageView to implement this?

I think PageView is a great choice to solve it, We just need to check if using PageView would hinder horizontal list inside the PageView.

I believe we cannot use PageView  (horizontal direction) and some other horizontal Scrollables without problems (aka the PageView would just block the inner scrollable).
So I think using CustomScrollView with Sliver stuff is better. But instead of doing all the hassles, maybe check this library out: nested_scroll_views.

Thanks for checking that out, But I don't think this package should depend on external libraries for such core features, It can be difficult to maintain in the long run and could add a severe code debt. I would go trying some proof of concept with CustomScrollView or PageView.

Alright I understand about the code debt and potential maintenance issue. Thanks for telling me.  I'll just use it as a case study and maybe try to play around it a lil bit. Have a good day! 😁


Re-arm the fail-safe for a longer period to deal with CASE retries

There are several retry mechanisms in CASE session setup at this point:

There is a certain amount of retrying during DNS-SD resolution.  This can take tens of seconds.
Once we have a resolution result, there are retries across the multiple IPs we got back.  Each one can take at least 9 seconds, and possibly longer depending on the advertised MRP parameters.
Once we run out of IPs, there are the retries we do to handle devices that are somewhat slow to connect to the operational network.  This can repeat all of the above a few times, with some backoff.

Looks like CHIP_DEVICE_CONFIG_FAILSAFE_EXPIRY_LENGTH_SEC defaults to 60 and I suspect no one is changing it in practice, and 60 seconds is just not going to be enough to go through that (plus the rest of commissioning)
Some possible options here:

AutoCommissioner could automatically extend the fail-safe by some amount before trying operational discovery.  It already does this if you pass in a value for SetCASEFailsafeTimerSeconds on the commissioning parameters, but we could have it default to some nonzero value.  A concern there would be overriding a longer fail-safe that someone else set up before triggering the AutoCommissioner.  And there is no way I see to read back the current fail-safe value from the server so we don't override it with a shorter one.
We could change things so that failures in CASE establishment trigger an extension of the fail-safe.  Again, how long is a good question, since we don't want to make the fail-safe shorter.  This would also make OperationalSessionSetup a little bigger, since it would now need a callback for "going to retry".
We could leave the existing setup and punt the problem to API consumers who would need to call SetCASEFailsafeTimerSeconds on the commissioning parameters.  This solves the "we're shortening their fail-safe" problem, but leaves the problem of them having to guess how long to extend for without knowing ahead of time how many times CASE will actually be tried.  That said, they could set this to something that corresponds to their "if we have not commissioned by then, we give up" timeout.
We could do something where we pipe through the "going to retry" notification all the way to the commissioning client, so they can decide what to do.  This obviously takes a bit more surgery.
What else?

https://github.com/project-chip/connectedhomeip/pull/25595 implements option 2.  I figured if we extend by "how long will a retry take" plus some overhead for actually doing the CASE handshake and sending the CommissioningComplete command, that would be pretty good as a start.

assuming this would be needed in espmatter too , should be updated there


add knip to ci-checks

Resolves #4982

CI failure 🔍

I needed to add preconstruct.entrypoints files as entry files in .knip.jsonc so it would pick up standalone entrypoint files.

This should be good to go 🤞


Transpiler hangs if trying to go to a basis with just 'ecr' and not 'cx'

Information

Qiskit Terra version: latest
Python version:
Operating system:

What is the current behavior?
The following hangs in what appears to be an infinite loop with ecr appearing never to be solved so it keeps looping.  Since a cx gate uses a cross-resonance gate on IBM systems, it should be possible to decompose it.

qc = QuantumCircuit(2)
qc.h(0)
qc.cx(0, 1)
qc.measure_all()

new_qc = transpile(qc, system, basis_gates=['rz', 'sx', 'x', 'ecr'])
new_qc.draw()

Steps to reproduce the problem
What is the expected behavior?
Suggested solutions

Update: It does not hang but takes forever to fail.

It is actually a bit odd because the QASM def of ecr is:
'gate ecr q0, q1 { U(3*pi/2, pi, pi) q0; U(pi/2, pi/2, 3*pi/2) q1; CX q0, q1; }'

which is in terms of other basis gates.  This is different from other basis gates in which their definition is itself:
gate cx c,t { CX c,t; }

My understanding was that this definition is not even being used by the Transpiler? The OpenQASM2 specification defines U and CX as special gates to be used to inform the respective compiler of the unitary representation of the derived gate. See page 5 https://arxiv.org/pdf/1707.03429.pdf.

So I can not actually use ecr gates then?  They are not defined in Qiskit anywhere and I cannot transpile to them although they are a valid basis gate per the device. Note that cx gates on ibm devices are defined in terms of cr gates so this definition seems circular.

CX is not circular. It has a special meaning in OpenQASM2 as a unitary representation, please see my comment above.
Something like
import qiskit
qc = QuantumCircuit(2, 2)
qc = qc.append(qiskit.circuit.Gate('ecr', 2, []), (0, 1))
qc_transpiled = qiskit.transpile(qc, backend=backend, basis_gates=['ecr'])

will work.

Confusing but will close as this is the expected behavior


Improved response handling none json error payload

Hi we are a happy user of your pagerduty client, but I didn't like the verbose exceptions in the log when someone uses a wrong pd key. So I hope you agree to parse json payload only when it returns json. with OK, ACCEPT or CREATED.
Sorry for not knowing your preferred code formatter

@dikhan Are you still maintaining this project ?


Start adding a CODEOWNERS file.

I suggest this after a comment from jni, as well as  pr-4932 and 4962
that I might have merged a bit overzealously without waiting for a core
napari contributor review.
I think that having assigned reviewers for part of the codebase,
and enforcing that they review/approve given changes might make ti a bit
clearer who is responsible about what.
Note that this can be made a bit easier with teams. We could have a core
team, doc team, plugins team that could be responsible for the
corresponding folders.
Current this just added Juan to review all PNGs, but that's of course
just an example.
You can find the documentation about CODEOWNERS here for more details.
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

Does this simply sned review requests, or also enforce that without those reviews the PR cannot be merged?

Does this simply send review requests, or also enforce that without those reviews the PR cannot be merged?

It depends what is checked in napari repo's settings and what is decided by the core team.

Current this just added Juan to review all PNGs

🤣🤣🤣🤣

In the spirit of assigning a group of owners instead of a single person, should we change the png owner from Juan to the steering council group before we merge?

There is a ned for some pr that will contain png. Any idea?

In the spirit of assigning a group of owners instead of a single person, should we change the png owner from Juan to the steering council group before we merge?

Updated to @napari/core-devs, and added gif, webm and jpg.

Updated to @napari/core-devs, and added gif, webm and jpg.

but this includes all persons, so it does not change anything from the current state?

but this includes all persons, so it does not change anything from the current state?

No it includes only these 15 persons, I for example am not part of it, but have commit right

In addition it will request review from the team, which it did not before, but we'll need an owner to go in the setting and enable mandatory review from codewoners for protected branches.

It seems we have a consensus to merge in this to kickstart the process and iterate on it. Going to merge tomorrow if no objection


Pull hackage-mirror-tool from source and drop patch

/stackage-builder/hackage-mirror-tool-lts-15.6.patch

Do you want help upstreaming this?
We are using it in production?

As a matter of fact, the patch isn't used anymore, so this ticket is slightly out of date.
However.
I switched to using https://github.com/chreekat/hackage-mirror-tool/ , which was based on hvr's original repo and incorporated changes present in snoyberg's fork. That creates two problems.

https://github.com/commercialhaskell/hackage-mirror-tool/ exists now. We should use that as the canonical upstream now. (It didn't exist at the time -- it was under snoyberg's namespace originally.)
There is still a divergence between chreekat/hackage-mirror-tool and commercialhaskell/hackage-mirror-tool

NB the original upstream, haskell-hvr/hackage-mirror-tool, has had no activity in 6 years

I'll rewrite the ticket.

And yes, help would be appreciated. :D


[KVM Forum] My [not accepted] Proposals

KVM Forum 2021
Cloud PMU: Building performance monitoring infrastructure in a hybrid model
After the impressive vPMU overhead reductions we made in 2019,  there are a growing number of PMU end users who want more native advanced profiling features in their guests. However, cloud administrators may characterize their guest's resource footprint to help dynamically make more globally optimal decisions (e.g., NUMA, NVDIMM, or live migration).
In this presentation, we will give a quick report on the profiling features we already have on x86 and present some critical issues when PMU is used for both host and guests (named "hybrid model"). We’ll focus on the general framework that needs to be done and propose some hw/sw approaches to make the hybrid model more easier to implement.
Based on the future of hybrid profiling, we will show several interesting use cases that may be specific to virtualization scenarios.

KVM Forum 2023
Confidential PMU for Confidential Computing: x86 status and gaps
On most private or trusted clouds, a large number of developers are already actively using vPMU to optimize their business and underlying software performance. With the popularity and adoption of confidential computing technologies, public clouds will become private clouds in some sense, but there is no performance monitoring support in the publicly available software implementation of x86 confidential technologies. In this case, the legacy virtualized PMU capability on regular VMs, which supports the simultaneous use of PMU by external control planes and internal guest agents, will disappear for confidential VMs.
This presentation will introduce a confidential PMU proposal based on AMD SEV-SNP and Intel TDX, which is aimed at availability and accuracy, by adapting the current stack to take full advantage of exist hardware and firmware support, allowing various PMU capabilities to remain isolated and operate properly within different security boundaries (e.g. legacy host, SEAM VMX root, SEAM VMX non-root). Furthermore we explore how to aggregate profiling data across address space boundaries in debug mode to facilitate the identification of performance bottlenecks throughout the confidential computing stack.
Notes
Driving the use of PMU in regular and confidential guests can spawn a wealth of technical innovations that improve software efficiency and reduce cloud computing costs, which is pretty valuable to the software ecosystem. Developers want to continue using various PMU features in confidential VMs, but support for confidential PMU is currently missing. As an active KVM contributor in this direction, the speaker has many ideas and practices he would like to share. Please consider accepting this proposal.


Release Schedule?

We should probably release a new version? Last release was ~Feb; It's not just good practise; it helps keep interested parties following the project/progress via "Watch Releases" :)

I agree!
I'm currently waiting for a review to get #201 merged. I think then we are ready for a new release.

Sounds good :D

Any thoughts on what a realistic release schedule you can maintain?

Any thoughts on what a realistic release schedule you can maintain?

No. This is currently a side-project and even tho we love to work on Gaia we also have other stuff going on (real job, familiy, kids etc.). I would like to release quarterly but that is simply not realistic because of the reasons mentioned above.
Our current approach is to release when we think it is worth to release a new version.

I totally understand! I have often been in the same situation (still am!) with the burden of release management and feeling like it takes too much time to do too often. I recently came across an excellent tool however that helps with a lot of this; goreleaser it might help you too :)

We are already using it. Goreleaser is awesome!

@prologic Release has been dooone! :))) hopefully we'll have a much frequent release process now. :)
Please reopen if necessary.


[BEAM-1222] Chunk size should be FS dependent

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @chamikaramj PTAL

Coverage increased (+0.006%) to 70.182% when pulling 48bb983aa3d216356abc60f5919f5e7b914e58b5 on sb2nov:BEAM-1222-rename-batch-consistency into 836e8e4aab239dd41f81de2f1553850b3fd3d716 on apache:master.

LGTM

Thanks


Type for money (decimal)

Now connexion cast number to float, but for money parameters needed decimal type

@worldmind please take a look at http://connexion.readthedocs.io/en/latest/cookbook.html#custom-type-format . Let me know if it does not help.

If i understood right is only part of solution - it is only about validation, but user shoud be manually convert goted string to decimal type for using it.
I think it framework job - it must return value with right type.

I think if we would do this in Connexion we would need to carry out all the responsibility to handle precision, etc. Not sure how we would tackle this issue.

Also OpenAPI spec does not provide the decimal type.

Due to no support for decimals in the OpenAPI spec, I think this issue should be closed. You can support decimal in your API, but you need to implement yourself the conversion.

Create https://github.com/OAI/OpenAPI-Specification/issues/889

As I understood they think that frameworks must create decimal values from type: number, format: decimal and some people do it https://github.com/OAI/OpenAPI-Specification/issues/607#issuecomment-200267864
They move formats from specification to separate registry in https://github.com/OAI/OpenAPI-Specification/issues/845 and add format decimal in https://github.com/OAI/OpenAPI-Specification/issues/607
I think that will be not bad if connexion will support format decimal and convert type: number, format: decimal to Decimal type.


Feature Request - Region Block in Bicep file

Discussed in https://github.com/Azure/bicep/discussions/8661

Originally posted by aavdberg October 13, 2022
Would love to see a Region Block in Bicep like we have in PowerShell Scripts, this makes scrolling thought the Bicep file a better overview.

wohooo

Is this the same as #46?

Is this the same as #46?

Looks like it is a dupe. @aavdberg is the solution discussed in #46 what you are looking for?

Closing due to lack of response. We'll assume it's the same #46 unless we here something different.

Yes that is what i am looking for


Keyboard Translator

replace the broken design of InputDecoder with a simpler KeyboardTranslator.

There is a list of documentation error you need to fix before merging this PullRequest :

Sparkle/src/input/spk_keyboard_translator.hpp:10
Compound spk::input::KeyboardTranslator is not documented.

Sparkle/src/input/spk_keyboard_translator.hpp:13
Member KeyboardTranslator(Keyboard *p_keyboard) (function) of class spk::input::KeyboardTranslator is not documented.

Sparkle/src/input/spk_keyboard_translator.hpp:20
Member setMappings(const std::unordered_map< TInputType, Keyboard::Key > p_mappings) (function) of class spk::input::KeyboardTranslator is not documented.

Sparkle/src/input/spk_keyboard_translator.hpp:25
Member setMapping(TInputType p_input, Keyboard::Key p_key) (function) of class spk::input::KeyboardTranslator is not documented.

Sparkle/src/input/spk_keyboard_translator.hpp:30
Member clear() (function) of class spk::input::KeyboardTranslator is not documented.

Sparkle/src/input/spk_keyboard_translator.hpp:35
Member erase(TInputType p_input) (function) of class spk::input::KeyboardTranslator is not documented.

Sparkle/src/input/spk_keyboard_translator.hpp:40
Member getInput(TInputType input) (function) of class spk::input::KeyboardTranslator is not documented.

Delayed later on


UI - Change Contact Email Address

Issue:

https://github.com/bcgov/entity/issues/23083

Description of changes:
Fixed/corrected contact email
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun

Temporary Url for review: https://strr-ui-dev--pr-164-rp31l2qs.web.app

/gcbrun


errors on creating VHDX

I keep getting fatal errors on the creating VHDX and I cannot pinpoint the cause of it. Hyper-V is installed, and I can create and run VMs with no problem.
My command line is:
.\BuildFFUVM.ps1 -make 'Dell' -model '3440' -WindowsSKU 'Pro' -FFUDevelopmentPath "C:\FFUDevelopment" -VMLocation "D:\HyperV\VMs" -Installapps $false -InstallOffice $false -InstallDrivers $true -VMSwitchName 'External' -VMHostIPAddress '<IP_ADDRESS>' -CreateDeploymentMedia $true -CreateCaptureMedia $true -BuildUSBDrive $true -UpdateLatestCU $true -UpdateLatestNet $true -UpdateLatestDefender $true -UpdateEdge $true -UpdateOneDrive $true -RemoveFFU $true -WindowsRelease 11 -WindowsLang 'nl-nl' -Verbose
Part of the log highlighting the errors:

VERBOSE: Download succeeded
VERBOSE: Cleanup cab and xml file
VERBOSE: Cleanup done
VERBOSE: Creating new Scratch VHDX...
Initialize-Disk : Access denied
Activity ID: {a96c9121-2497-0001-f4b6-6ca99724db01}
At D:\FFU-main\FFUDevelopment\BuildFFUVM.ps1:2625 char:50

... | Mount-VHD -Passthru | Initialize-Disk -PassThru -PartitionStyle GPT

                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : PermissionDenied: (StorageWMI:ROOT/Microsoft/Windows/Storage/MSFT_Disk) [Initialize-Disk], CimException
FullyQualifiedErrorId : StorageWMI 40001,Initialize-Disk

Creating VHDX Failed
VERBOSE: Creating VHDX Failed with error Cannot validate argument on parameter 'DiskNumber'. The argument is null. Provide a valid value for the argument, and then try running the command again.
VERBOSE: Dismounting D:\HyperV\VMs_FFU-1101724783_FFU-1101724783.vhdx
VERBOSE: Dismounting scratch VHDX...
VERBOSE: Done.
VERBOSE: Removing D:\HyperV\VMs_FFU-1101724783
VERBOSE: Removal complete
VERBOSE: Deleting ESD file
VERBOSE: ESD File deleted
New-ScratchVhdx : Cannot validate argument on parameter 'DiskNumber'. The argument is null. Provide a valid value for the argument, and then try running the command again.
At D:\FFU-main\FFUDevelopment\BuildFFUVM.ps1:4158 char:17

... $vhdxDisk = New-ScratchVhdx -VhdxPath $VHDXPath -SizeBytes $disksize  ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidData: (:) [New-ScratchVhdx], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationError,New-ScratchVhdx

This is the code you're failing on

    $newVHDX = New-VHD -Path $VhdxPath -SizeBytes $disksize -LogicalSectorSizeBytes $LogicalSectorSizeBytes -Dynamic:($Dynamic.IsPresent)
    $toReturn = $newVHDX | Mount-VHD -Passthru | Initialize-Disk -PassThru -PartitionStyle GPT

    #Remove auto-created partition so we can create the correct partition layout
    remove-partition $toreturn.DiskNumber -PartitionNumber 1 -Confirm:$False```

Initialize-Disk is throwing an Access Denied.

Are you running as Administrator? The script requires this and will fail immediately if you're running as a standard user, but if you've modified the script and removed the check, then that check wouldn't happen.

Do you have any AV/EDR/XDR software that could be putting a lock on the VHDX? We create the VHDX and then immediately initialize it, so it's possible a file lock could be happening while we try to initialize.

I also notice that you have different paths for the FFUDevelopment folder and the VMLocation. You may want to just try having everything in the FFUDevelopment folder (no need to set the VMLocation parameter).

I have moved everything into one folder. Still got the same error. I've set a breakpoint in the BuildFFUVM.ps1 script at line 2624. I can observe that the new-vhd command works, the mount-vhd also works and I receive a disk number. It seems to fail on the Initialize-Disk command. If I execute this part manually it throws the same error, but I can see in disk manager that the disk has been initialized though no partition was created.
Everything is run elevated, I have tried VScode, PowerShell ISE and normal PowerShell. Same result. I am at a loss why this fails.

That's odd. Did you also create a new VHD manually using powershell, or just debug the script and then execute the initialize disk step via the console? If not, I'd be curious if you could just create a new VHD manually as well and try to initialize it and see if that works or you see the same issue.

Tried again including disabling real time AV scanning on drives.  After some more testing it seems that the line:
Initialize-Disk $toReturn.DiskNumber -PartitionStyle GPT
will give an access denied error, but does execute the initialize disk part since it shows up in disk manager as initialized with GPT style after the error message is displayed and I set a break point there to stop execution.
So I changed the line to:
Initialize-Disk $toReturn.DiskNumber -PartitionStyle GPT -ErrorAction SilentlyContinue
and then the script continues.
Unfortunately it then fails on the line:
$systemPartitionDriveLetter = New-SystemPartition -VhdxDisk $vhdxDisk
on line number 4163 (in the #Create VHDX part). Error message:
$systemPartitionDriveLetter = New-SystemPartition -VhdxDisk $vhdxDisk
New-SystemPartition : Cannot process argument transformation on parameter 'VhdxDisk'. Cannot convert the "Microsoft.Vhd.PowerShell.VirtualHardDisk" value of type "Microsoft.Vhd
.PowerShell.VirtualHardDisk" to type "Microsoft.Management.Infrastructure.CimInstance".
At line:1 char:61
+ $systemPartitionDriveLetter = New-SystemPartition -VhdxDisk $vhdxDisk
+                                                             ~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [New-SystemPartition], ParameterBindingArgumentTransformationException
    + FullyQualifiedErrorId : ParameterArgumentTransformationError,New-SystemPartition

The line just before it
$vhdxDisk = New-ScratchVhdx -VhdxPath $VHDXPath -SizeBytes $disksize -LogicalSectorSizeBytes $LogicalSectorSizeBytes
is exectuted with no error and does create a mounted disk visible in disk manager.

Is it possible to try this on a different machine?

I have tried on another machine with similar results. The step on line 2626
Initialize-Disk $toReturn.DiskNumber -PartitionStyle GPT
now works without error, but still the script stops at line 4160
$systemPartitionDriveLetter = New-SystemPartition -VhdxDisk $vhdxDisk
Included logfile:
FFUDevelopment.log

Can you try again without running from PowerShell ISE? The log seems to indicate it's running from there. Send over the log from that run.
Thanks,
Richard

From: detox4you @.>
Sent: Tuesday, November 5, 2024 4:50:36 AM
To: rbalsleyMSFT/FFU @.>
Cc: Richard Balsley @.>; Comment @.>
Subject: Re: [rbalsleyMSFT/FFU] errors on creating VHDX (Issue #95)
I have tried on another machine with similar results. The step on line 2626
Initialize-Disk $toReturn.DiskNumber -PartitionStyle GPT
now works without error, but still the script stops at line 4160
$systemPartitionDriveLetter = New-SystemPartition -VhdxDisk $vhdxDisk
Included logfile:
FFUDevelopment.loghttps://github.com/user-attachments/files/17632643/FFUDevelopment.log
—
Reply to this email directly, view it on GitHubhttps://github.com/rbalsleyMSFT/FFU/issues/95#issuecomment-2457085083, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYE2BDLSM667DDRPRUEEWTZ7C5JZAVCNFSM6AAAAABQNOCM4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJXGA4DKMBYGM.
You are receiving this because you commented.Message ID: @.***>

Same when running outside the ISE but I might be onto something: I downloaded the ZIP with the files again, deleted everything except my calling scripts and ISO files and ran it again. It does not give errors now. Nothing else changed except downloading from the source again. Running it now and it passed the point of error I had before.

That's good news. When using VSCode with the PowerShell extension or ISE, things behave differently than directly from PowerShell. Hence the ask.
But it's good that a redownload seems to have solved things. Let me know if it has any other issues.
Thanks,
Richard

From: detox4you @.>
Sent: Tuesday, November 5, 2024 9:37:37 AM
To: rbalsleyMSFT/FFU @.>
Cc: Richard Balsley @.>; Comment @.>
Subject: Re: [rbalsleyMSFT/FFU] errors on creating VHDX (Issue #95)
Same when running outside the ISE but I might be onto something: I downloaded the ZIP with the files again, deleted everything except my calling scripts and ISO files and ran it again. It does not give errors now. Nothing else changed except downloading from the source again. Running it now and it passed the point of error I had before.
—
Reply to this email directly, view it on GitHubhttps://github.com/rbalsleyMSFT/FFU/issues/95#issuecomment-2457793019, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMYE2BBXFWBICICUYNKIAKDZ7D66DAVCNFSM6AAAAABQNOCM4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJXG44TGMBRHE.
You are receiving this because you commented.Message ID: @.***>

First part now resolved it seems.
VERBOSE: Done.
VERBOSE: Sleeping 2 minutes to prevent file handle lock
VERBOSE: Adding drivers
VERBOSE: Creating D:\FFU-main\FFUDevelopment\Mount directory
VERBOSE: Created D:\FFU-main\FFUDevelopment\Mount directory
VERBOSE: Mounting D:\FFU-main\FFUDevelopment\FFU\Win11_23H2_Pro_nov2024.ffu to D:\FFU-main\FFUDevelopment\Mount
Capturing FFU file failed
VERBOSE: Capturing FFU file failed with error Toegang geweigerd.

At D:\FFU-main\FFUDevelopment\BuildFFUVM.ps1:3102 char:9
+         Mount-WindowsImage -ImagePath $FFUFile -Index 1 -Path "$FFUDe ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Mount-WindowsImage], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.MountWindowsImageCommand

I resolved this by checking if the mount folder is created and if not create an empty one by inserting this before the command that failed (mount folder does not exist in the downloaded ZIP file of the code and it also gets deleted automatically):
        #Check if Folder exists
        If(!(Test-Path -Path "$FFUDevelopmentPath\Mount"))
        {
          #powershell create directory
          New-Item -ItemType Directory -Path "$FFUDevelopmentPath\Mount"
          Write-Host "New folder created successfully!" -f Green
        }
        Else
        {
          Write-Host "Folder already exists!" -f Yellow
        }

This now works. But I end up at an error I can't find the solution for. It now stops here:
VERBOSE: Dismount D:\FFU-main\FFUDevelopment\Mount
VERBOSE: Dismount complete
VERBOSE: Remove D:\FFU-main\FFUDevelopment\Mount folder
VERBOSE: Folder removed
VERBOSE: Optimizing FFU - This will take a few minutes, please be patient
VERBOSE: Deployment Image Servicing and Management tool
Version: 10.0.26100.1

Mounting image
[==========================100.0%==========================]

Error: 5

Toegang geweigerd.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
Script failed - D:\FFU-main\FFUDevelopment\FFUDevelopment.log for more info
Capturing FFU file failed
VERBOSE: Capturing FFU file failed with error Deployment Image Servicing and Management tool
Version: 10.0.26100.1

Mounting image
[==========================100.0%==========================]

Error: 5

Toegang geweigerd.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
VERBOSE: Cleaning up VHDX
VERBOSE: Removing D:\FFU-main\FFUDevelopment\VM\_FFU-1200674899
VERBOSE: Removal complete
VERBOSE: Remove unused mountpoints
VERBOSE: Removal complete
Deployment Image Servicing and Management tool
Version: 10.0.26100.1
Mounting image
[==========================100.0%==========================]
Error: 5
Toegang geweigerd.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
At D:\FFU-main\FFUDevelopment\BuildFFUVM.ps1:472 char:21
+                     throw $cmdOutput.Trim()
+                     ~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Deployment Imag...s\DISM\dism.log:String) [], RuntimeException
    + FullyQualifiedErrorId : Deployment Image Servicing and Management tool
Version: 10.0.26100.1
Mounting image
[==========================100.0%==========================]
Error: 5
Toegang geweigerd.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Error 5 is typically access denied. Do you have the dism.log file?

dism.zip

Your log
2024-11-06 23:58:40, Info                  DISM   DISM.EXE: Executing command line: dism  /optimize-ffu /imagefile:D:\FFU-main\FFUDevelopment\FFU\Win11_24H2_Pro_nov2024.ffu /scratchdir:D:\FFU-main\FFUDevelopment\Scratchdir
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: CFfuMiscHelpersT<class CEmptyType>::GetSignerInfoFromCatalog#998 failed with 0x80091008.
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: -------- Security Header ----------------------------------
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                     Size = 32
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                Signature = SignedImage
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:            ChunkSizeInKB = 128
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:              AlgorithmId = 32780
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:              CatalogSize = 306
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:            HashTableSize = 2012128
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: ----------- Image Header ----------------------------------
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                     Size = 24
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                Signature = ImageFlash
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:           ManifestLength = 1645
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                ChunkSize = 128
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: ----------- Store Header ----------------------------------
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:               UpdateType = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:             MajorVersion = 1
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:             MinorVersion = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:    FullFlashMajorVersion = 3
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:    FullFlashMinorVersion = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:               PlatformId =
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                BlockSize = 131072
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:     WriteDescriptorCount = 62868
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:    WriteDescriptorLength = 1257360
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:  ValidateDescriptorCount = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: ValidateDescriptorLength = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:        InitialTableIndex = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:        InitialTableCount = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:      FlashOnlyTableIndex = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:      FlashOnlyTableCount = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:          FinalTableIndex = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:          FinalTableCount = 62868
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:     CompressionAlgorithm = 3
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: CFfuMiscHelpersT<class CEmptyType>::GetSignerInfoFromCatalog#998 failed with 0x80091008.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: CFfuMiscHelpersT<class CEmptyType>::GetSignerInfoFromCatalog#998 failed with 0x80091008.
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: -------- Security Header ----------------------------------
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                     Size = 32
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                Signature = SignedImage
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:            ChunkSizeInKB = 128
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:              AlgorithmId = 32780
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:              CatalogSize = 306
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:            HashTableSize = 2012128
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: ----------- Image Header ----------------------------------
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                     Size = 24
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                Signature = ImageFlash
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:           ManifestLength = 1645
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                ChunkSize = 128
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: ----------- Store Header ----------------------------------
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:               UpdateType = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:             MajorVersion = 1
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:             MinorVersion = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:    FullFlashMajorVersion = 3
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:    FullFlashMinorVersion = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:               PlatformId =
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                BlockSize = 131072
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:     WriteDescriptorCount = 62868
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:    WriteDescriptorLength = 1257360
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:  ValidateDescriptorCount = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: ValidateDescriptorLength = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:        InitialTableIndex = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:        InitialTableCount = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:      FlashOnlyTableIndex = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:      FlashOnlyTableCount = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:          FinalTableIndex = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:          FinalTableCount = 62868
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:     CompressionAlgorithm = 3
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: Successfully created a virtual disk file at C:\Users\detou\AppData\Local\Temp\_ffumount856094852.vhd.
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: Successfully set surface cache policy.
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: Successfully attached the virtual at \\.\PhysicalDrive4.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: CFfuMiscHelpersT<class CEmptyType>::GetSignerInfoFromCatalog#998 failed with 0x80091008.
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: -------- Security Header ----------------------------------
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                     Size = 32
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                Signature = SignedImage
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:            ChunkSizeInKB = 128
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:              AlgorithmId = 32780
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:              CatalogSize = 306
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:            HashTableSize = 2012128
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: ----------- Image Header ----------------------------------
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                     Size = 24
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                Signature = ImageFlash
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:           ManifestLength = 1645
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                ChunkSize = 128
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: ----------- Store Header ----------------------------------
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:               UpdateType = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:             MajorVersion = 1
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:             MinorVersion = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:    FullFlashMajorVersion = 3
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:    FullFlashMinorVersion = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:               PlatformId =
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:                BlockSize = 131072
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:     WriteDescriptorCount = 62868
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:    WriteDescriptorLength = 1257360
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:  ValidateDescriptorCount = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: ValidateDescriptorLength = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:        InitialTableIndex = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:        InitialTableCount = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:      FlashOnlyTableIndex = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:      FlashOnlyTableCount = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:          FinalTableIndex = 0
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:          FinalTableCount = 62868
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider:     CompressionAlgorithm = 3
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: Disk size =<PHONE_NUMBER>0, Ffu disk size =<PHONE_NUMBER>0.
2024-11-06 23:58:40, Info                  DISM   DISM FFU Provider: Number of worker threads = 16
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: IOWorkerCallback#277 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: FfuApplyInternal#531 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: FfuMountInternal#242 failed with 0x80070005.
2024-11-06 23:58:40, Warning               DISM   DISM FFU Provider: Failed to delete backing VHD/X file C:\Users\detou\AppData\Local\Temp\_ffumount856094852.vhd (0x80070020).
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: FfuMountImage#206 failed with 0x80070005.
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: PID=28276 TID=1332 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffuimageinfo.cpp:347 - CFfuImageInfo::Mount(hr:0x80070005)
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: PID=28276 TID=1332 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:885 - CFfuManager::Optimize(hr:0x80070005)
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: PID=28276 TID=1332 Failed to optimize the FFU image 'D:\FFU-main\FFUDevelopment\FFU\Win11_24H2_Pro_nov2024.ffu'. - CFfuManager::InternalCmdOptimize(hr:0x80070005)
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: PID=28276 TID=1332 "Error executing command" - CFfuManager::InternalExecuteCmd(hr:0x80070005)
2024-11-06 23:58:40, Error                 DISM   DISM FFU Provider: PID=28276 TID=1332 onecore\base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:225 - CFfuManager::ExecuteCmdLine(hr:0x80070005)
2024-11-06 23:58:40, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2024-11-06 23:58:40, Info                  DISM   DISM.EXE:
2024-11-06 23:58:40, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->

Good log from my machine
2024-10-21 12:22:30, Info                  DISM   DISM.EXE: Executing command line: dism  /optimize-ffu /imagefile:C:\FFUDevelopment\FFU\Win11_24H2_Pro_Apps_Oct2024.ffu
2024-10-21 12:22:30, Error                 DISM   DISM FFU Provider: CFfuMiscHelpersT<class CEmptyType>::GetSignerInfoFromCatalog#998 failed with 0x80091008.
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: -------- Security Header ----------------------------------
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                     Size = 32
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                Signature = SignedImage
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:            ChunkSizeInKB = 128
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:              AlgorithmId = 32780
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:              CatalogSize = 306
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:            HashTableSize = 6069632
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: ----------- Image Header ----------------------------------
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                     Size = 24
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                Signature = ImageFlash
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:           ManifestLength = 1659
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                ChunkSize = 128
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: ----------- Store Header ----------------------------------
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:               UpdateType = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:             MajorVersion = 1
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:             MinorVersion = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:    FullFlashMajorVersion = 3
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:    FullFlashMinorVersion = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:               PlatformId =
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                BlockSize = 131072
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:     WriteDescriptorCount = 189646
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:    WriteDescriptorLength = 3792920
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:  ValidateDescriptorCount = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: ValidateDescriptorLength = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:        InitialTableIndex = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:        InitialTableCount = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:      FlashOnlyTableIndex = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:      FlashOnlyTableCount = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:          FinalTableIndex = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:          FinalTableCount = 189646
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:     CompressionAlgorithm = 3
2024-10-21 12:22:30, Error                 DISM   DISM FFU Provider: CFfuMiscHelpersT<class CEmptyType>::GetSignerInfoFromCatalog#998 failed with 0x80091008.
2024-10-21 12:22:30, Error                 DISM   DISM FFU Provider: CFfuMiscHelpersT<class CEmptyType>::GetSignerInfoFromCatalog#998 failed with 0x80091008.
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: -------- Security Header ----------------------------------
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                     Size = 32
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                Signature = SignedImage
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:            ChunkSizeInKB = 128
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:              AlgorithmId = 32780
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:              CatalogSize = 306
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:            HashTableSize = 6069632
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: ----------- Image Header ----------------------------------
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                     Size = 24
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                Signature = ImageFlash
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:           ManifestLength = 1659
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                ChunkSize = 128
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: ----------- Store Header ----------------------------------
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:               UpdateType = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:             MajorVersion = 1
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:             MinorVersion = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:    FullFlashMajorVersion = 3
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:    FullFlashMinorVersion = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:               PlatformId =
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                BlockSize = 131072
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:     WriteDescriptorCount = 189646
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:    WriteDescriptorLength = 3792920
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:  ValidateDescriptorCount = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: ValidateDescriptorLength = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:        InitialTableIndex = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:        InitialTableCount = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:      FlashOnlyTableIndex = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:      FlashOnlyTableCount = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:          FinalTableIndex = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:          FinalTableCount = 189646
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:     CompressionAlgorithm = 3
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: Successfully created a virtual disk file at C:\Users\admin\AppData\Local\Temp\_ffumount-6715816.vhd.
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: Successfully set surface cache policy.
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: Successfully attached the virtual at \\.\PhysicalDrive4.
2024-10-21 12:22:30, Error                 DISM   DISM FFU Provider: CFfuMiscHelpersT<class CEmptyType>::GetSignerInfoFromCatalog#998 failed with 0x80091008.
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: -------- Security Header ----------------------------------
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                     Size = 32
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                Signature = SignedImage
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:            ChunkSizeInKB = 128
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:              AlgorithmId = 32780
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:              CatalogSize = 306
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:            HashTableSize = 6069632
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: ----------- Image Header ----------------------------------
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                     Size = 24
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                Signature = ImageFlash
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:           ManifestLength = 1659
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                ChunkSize = 128
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: ----------- Store Header ----------------------------------
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:               UpdateType = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:             MajorVersion = 1
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:             MinorVersion = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:    FullFlashMajorVersion = 3
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:    FullFlashMinorVersion = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:               PlatformId =
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:                BlockSize = 131072
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:     WriteDescriptorCount = 189646
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:    WriteDescriptorLength = 3792920
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:  ValidateDescriptorCount = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: ValidateDescriptorLength = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:        InitialTableIndex = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:        InitialTableCount = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:      FlashOnlyTableIndex = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:      FlashOnlyTableCount = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:          FinalTableIndex = 0
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:          FinalTableCount = 189646
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider:     CompressionAlgorithm = 3
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: Disk size =<PHONE_NUMBER>0, Ffu disk size =<PHONE_NUMBER>0.
2024-10-21 12:22:30, Info                  DISM   DISM FFU Provider: Number of worker threads = 24
2024-10-21 12:23:15, Info                  DISM   DISM FFU Provider: Decompression time = 31009 ms, Hash time = 70718 ms, Disk I/O time = 1971964 ms, File I/O time = 43951 ms
2024-10-21 12:23:15, Info                  DISM   DISM FFU Provider: Successfully applied the FFU at \\.\PhysicalDrive4.
2024-10-21 12:23:15, Info                  DISM   DISM FFU Provider: Drive path = \\.\PhysicalDrive4
2024-10-21 12:23:15, Info                  DISM   DISM FFU Provider:   Disk size =<PHONE_NUMBER>0 Bytes (30.00 Gb)
2024-10-21 12:23:15, Info                  DISM   DISM FFU Provider: Partition Style = GPT
2024-10-21 12:23:15, Info                  DISM   DISM FFU Provider: Partition Count = 4
2024-10-21 12:23:15, Info                  DISM   DISM FFU Provider: Successfully written the session info to HKEY\SOFTWARE\Microsoft\DISM\Mounted FFUs\__?_Volume{e628e3c9-0693-4c0a-8140-ebf156cae5e9}__2124225880_1638400_1296621.
2024-10-21 12:23:15, Info                  DISM   DISM FFU Provider: Total time: 45360 ms
2024-10-21 12:23:15, Info                  DISM   DISM FFU Provider: Partition for optimization: #3
2024-10-21 12:23:15, Warning               DISM   DISM FFU Provider: Skipped \\?\Volume{16ec6031-0bc2-48c8-9c3c-9136df0d796d}\\$ntfs.log for deletion (0x80070002).
2024-10-21 12:23:15, Warning               DISM   DISM FFU Provider: Skipped \\?\Volume{16ec6031-0bc2-48c8-9c3c-9136df0d796d}\\hiberfil.sys for deletion (0x80070002).
2024-10-21 12:23:15, Info                  DISM   DISM FFU Provider: Deleted \\?\Volume{16ec6031-0bc2-48c8-9c3c-9136df0d796d}\\pagefile.sys successfully.
2024-10-21 12:23:15, Info                  DISM   DISM FFU Provider: Deleted \\?\Volume{16ec6031-0bc2-48c8-9c3c-9136df0d796d}\\swapfile.sys successfully.
2024-10-21 12:23:15, Warning               DISM   DISM FFU Provider: Skipped \\?\Volume{16ec6031-0bc2-48c8-9c3c-9136df0d796d}\\RECYCLER for deletion (0x80070003).
2024-10-21 12:23:15, Info                  DISM   DISM FFU Provider: Deleted \\?\Volume{16ec6031-0bc2-48c8-9c3c-9136df0d796d}\\$Recycle.Bin successfully.
2024-10-21 12:23:15, Warning               DISM   DISM FFU Provider: Skipped \\?\Volume{16ec6031-0bc2-48c8-9c3c-9136df0d796d}\\Windows\CSC for deletion (0x80070003).
2024-10-21 12:23:17, Info                  DISM   DISM FFU Provider: Volume can be resized anywhere between<PHONE_NUMBER>4 and<PHONE_NUMBER>6.  Reboot required=no.
2024-10-21 12:23:43, Info                  DISM   DISM.EXE:
2024-10-21 12:23:43, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->

Looks like the issue is with mounting the FFU to a VHD in order to optimize it.

Closing. Please reopen if you're still having an issue.


As a developer, I would like to Enable Bucket Logging and App-to-App access, so I can use the logs to track downloaded granules and its frequency and sunset the product.s

Collaborate with the I&A team to enable bucket logging on the SWODLR S3 bucket. This will allow us to gather metrics related to:

Downloaded granules
Granule download frequency

using programmatic approach via credential to access cloud metric

This ticket complete as we have determined approach and opened follow on ticket #64

related metric ticket is in Ingest data from CloudWatch Log Groups over to Earthdata Cloud's Metrics #94


I'd like my repo to be indexed and documented on ros.org.

Please add the following dependency to the rosdep database.
Package name:
iotbot
Package Upstream Source:
https://github.com/EduArt-Robotik/iotbot.git
Purpose of using this:
EduArt Robotik developed a new robot chassis for educational purposes. It provides a ROS interface. This is why I think it's valuable to be added to the rosdep database.
Distro packaging links:
Links to Distribution Packages

Debian: https://packages.debian.org/

https://github.com/EduArt-Robotik/iotbot.git

Ubuntu: https://packages.ubuntu.com/

https://github.com/EduArt-Robotik/iotbot.git

Fedora: https://src.fedoraproject.org/browse/projects/

not available

Arch: https://www.archlinux.org/packages/

not available

Gentoo: https://packages.gentoo.org/

not available

macOS: https://formulae.brew.sh/

not available

Alpine: https://pkgs.alpinelinux.org/packages

not available

NixOS/nixpkgs: https://search.nixos.org/packages

not available

Please Add This Package to be indexed in the rosdistro.
noetic
The source is here:
https://github.com/EduArt-Robotik/iotbot.git
Checks

[x] All packages have a declared license in the package.xml
[x] This repository has a LICENSE file
[x] This package is expected to build on the submitted rosdistro

Dear ROS maintainer,
do you miss something in my pull request? I am wondering why my demand is not considered since six days.
Best regards
Stefan May

This PR method is for binaries already available. You're providing the source (not a binary).
The method for this is described here: http://wiki.ros.org/bloom/Tutorials/FirstTimeRelease
Disclaimer: not a maintainer here, but released packages using the tutorial above.


Glutin Event Fetcher Process doesn't handle exceptions?

It looks like an exception while rendering windows terminates the Glutin Event Fetcher Process, which causes the system to become unresponsive.
The attached crash.txt shows the initial exception being logger (#asBlTktLoggingCommand not understood).  The list of processes logged by kill -USR1 doesn't include a priority 50 process with the event fetcher's normal stack.
Once this has happened the windows are greyed out (indicating that it isn't responding to X11) and it must be killed externally.
crash.txt
The issue can be reproduced by evaluating something like:
GToolkitImagesExamples new imageInSpace: 'picture.jpg'

(where picture.jpg exists).

GtWorld useGToolkitDebuggersAsDefault

currently needs to be evaluated to set the correct debugger.
I'll leave this open until it is no longer required.

This is no longer relevant, #useGToolkitDebuggersAsDefault no longer exists.


Old objects are not properly being GCed on sess.load()

This is also a bug/feature-request in the original Scala REPL:
https://issues.scala-lang.org/browse/SI-4331
This should be trivially fixed in the Ammonite REPL because sess.load() should leave the abandoned classloader un-reachable, and they should get GCed along with all defined classes. This doesn't seem to be happening though
haoyi-mbp:~ haoyi$ ~/amm
Loading...
Welcome to the Ammonite Repl 0.5.2
(Scala 2.11.7 Java 1.8.0_25)
haoyi-haoyi@ Runtime.getRuntime().totalMemory - Runtime.getRuntime().freeMemory
res0: Long = 69063536L
haoyi-haoyi@ val x = 1
x: Int = 1
haoyi-haoyi@ sess.save()

haoyi-haoyi@ Runtime.getRuntime().totalMemory - Runtime.getRuntime().freeMemory
res3: Long = 117177992L
haoyi-haoyi@ val y = new Array[Long](100000000)
y: Array[Long] = Array(
  0L,
  0L,
  0L,
  0L,
  0L,
  0L,
  0L,
  0L,
  0L,
  0L,
  0L,
...
haoyi-haoyi@ Runtime.getRuntime().totalMemory - Runtime.getRuntime().freeMemory
res5: Long = 917713368L
haoyi-haoyi@ sess.load()
res6: ammonite.repl.frontend.SessionChanged =
Removed Imports: Set('y, 'res5, 'res3, 'res2)
haoyi-haoyi@ System.gc()

haoyi-haoyi@ Runtime.getRuntime().totalMemory - Runtime.getRuntime().freeMemory
res8: Long = 928880056L

If this worked, the difference between totalMemory and freeMemory should drop back down after sess.load() and System.gc() are called, but it doesn't. JProfiler agrees with this assessment, and its telemetry graphs don't show the expected dip. Presumably something silly is keeping these classes/classloaders/statics alive and preventing them from getting GCed and this should be fixed

Seems like my classloaders are holding references to each other through the AccessControlContext and ProtectionDomains:

Not sure how to fix it. The relevant code seems to live in URLClassLoader. Maybe I need to re-implement URLClassLoader's logic from scratch only inheriting from ClassLoader?

We're probably going to do away with the whole session loading/saving thing altogether in https://github.com/lihaoyi/Ammonite/issues/437, so this would be rendered moot


Put "Coming Soon" link on download activity guides in spanish button

because they won't be ready for launch

cllosing because just checked live version and we don't have the spanish buttons


How should we attach extra data to exceptions

Can we attach extra data to our exceptions that are more helpful in understanding/debugging the issues? What's the pattern. @yishaigalatzer has some ideas - see: https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.Core/MvcRouteHandler.cs#L54

Please drive the discussion. I'd like to reach a consensus on the design and either keep what we have or remove the one place in the code that does it today.

Remove the current code, it's not adding a lot of value. When we need to throw specific exception we might create a custom exception type instead. But that will happen very sparingly, e.g. AmbiguousActionException

02f656667f8231d1be373ef523f078beeefbb23f


A11y - OU: Elements must only use supported ARIA attributes

Ensure an element's role supports its ARIA attributes. [https://dequeuniversity.com/rules/axe/4.10/aria-allowed-attr?application=AxeChrome|https://dequeuniversity.com/rules/axe/4.10/aria-allowed-attr?application=AxeChrome|smart-link]
h3. Element Location:
{noformat}input[placeholder="Search for employees"]
.js-ou-shipping-address > .form-select.multiple-selection[data-b2b-organization-unit-multiple-selection=""] > .border-0.focus-none[placeholder="Search for addresses"]
.js-ou-billing-address > .form-select.multiple-selection[data-b2b-organization-unit-multiple-selection=""] > .border-0.focus-none[placeholder="Search for addresses"]{noformat}
h3. To solve this problem, you need to fix the following:
ARIA attribute is not allowed: aria-expanded="false"
!Screen Shot 2024-11-13 at 16.05.52 PM.png|width=744,height=438,alt="Screen Shot 2024-11-13 at 16.05.52 PM.png"!
!Screen Shot 2024-11-13 at 16.06.10 PM.png|width=978,height=540,alt="Screen Shot 2024-11-13 at 16.06.10 PM.png"!
!Screen Shot 2024-11-13 at 16.06.04 PM.png|width=988,height=518,alt="Screen Shot 2024-11-13 at 16.06.04 PM.png"!

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-39567
[created from NEXT-39567, comment 512369]

[public]

FixVersion Change: <IP_ADDRESS>

This issue will be / was solved in Shopware version <IP_ADDRESS>.
[created from NEXT-39567, comment 521034]


[Question]: Cannot connect to Realtime

General info

[X] I checked the troubleshooting page for similar problems

What is your question?
Hello, sorry to still ask this question even though it has been  mentioned in the troubleshooting. This is because i dont know how to  go about it. Iam trying to connect to realtime and observe some Postgrest Action and iam having trouble with two issues.
First, the example in the documentation mentions a .subscribe()  function that can be called on an instance of a channel object, the new library version 2.0.4 seemes to have replaced the method but i was not able to figure out exactly what function replaced it. I need help on that.
Secondly, and this has been mentioned in the trouble shooting is this error that iam getting  Error while trying to connect to realtime websocket. Trying again in 7s. Engine doesn't support WebSocketCapability. The trouble shooting page suggest Not all ktor client [engines](https://ktor.io/docs/http-client-engines.html#limitations) support Websockets. If you are using Android, you can use OkHttp or CIO instead. How do i do that exactly from android studio, do i need to add an OkHttp dependency? If yes ( and i did that ) how am i supposed to use it to make my network requests. Please Help. Thanks in advance. This is the code iam trying to run;

fun realTimeChat(scope:CoroutineScope){

viewModelScope.launch {
try {

        >    val channel = client.realtime.channel("chatChannel")
         >   val dataFlow = channel.postgresChangeFlow<PostgresAction>(schema = "public").onEach {

          >  }
          >  dataFlow.onEach {

              >    is PostgresAction.Delete -> {}
                 >   is PostgresAction.Insert -> {
                    >    Log.d("realtime","data is ${it.record}")
                >        chatMessage.value = it.record.toString()
                  >  }
                  >  is PostgresAction.Select -> TODO()
                  >  is PostgresAction.Update -> TODO()
              >  }

          >  }.launchIn(scope)

          >  channel.subscribe()

           > Log.d("realtimeKibs","realtime call finished ")
     >   } catch (e:Exception){
         >   Log.d("realtimeKibs","realtime failed with ${e.message} ")
        >    handleExceptionForChat(e)
     >   }
  >  }

}

Allow me to close this one as I have since figured out and resolved my issue. Thank you.


uncaught error when '/<prompt_id>/leaderboard/<run_id>' receives an invalid run_id arg

Currently causes the server to return a 500 error when the input run_id is invalid. The endpoint should be able to catch and remove invalid runs from the response output


Add XDG basedir layer

It would be cool for applications to support the XDG basedir spec effortlessly. This can be done by:

Creating a layer to ${XDG_CONFIG_HOME:-$HOME/.config}/<application name>/<config file>.
Creating a layer for each path in ${XDG_CONFIG_DIRS:-/etc/xdg}/<application name>/<config file>

I think this can be implemented by having a utility function that does all the work (given some configuration parameters) and then returns a Vec (or an Iterator) of layers.

There's an XDG crate out there that could be used, so this crate doesn't have to concern itself with the spec: https://whitequark.github.io/rust-xdg/xdg/struct.BaseDirectories.html