feat(connector-indy): add indy plugin implementation

Summary
Develop a Cactus Indy connector plugin + test infrastructure (container images, container manager class, etc.) from scratch (container images only need to be created from scratch if there is no existing one available that fits the purpose).
Include end to end test cases powered by Jest and the said testing infrastructure that prove that the connector is working as intended with a locally simulated Indy network.
You will be creating a new package in the Cactus monorepo from scratch under the packages/cactus-plugin-ledger-connector-indy/ path.
Acceptance Criteria

Indy All-In-One image is created or discovered and used as-is. If needed to create from scratch, place it under tools/docker/indy-all-in-one/Dockerfile which also has a README.md next to it explaining the building and running of the image and it's containers (tools/docker/indy-all-in-one/README.md)
1.1 Container health checks must be be operational and reliable for the image meaning that the HEALTHCHECK keyword needs to be used within the Dockerfile to define when the container has finished launching (e.g. it must only pass once the ledger is up and running, ready to accept transactions)
The AIO image mentioned above is published to the official GitHub Container Registry under the fully qualified image tag of ghcr.io/hyperledger/cactus-indy-all-in-one:2022-MM-DD-$GIT_SHORT_HASH for example ghcr.io/hyperledger/cactus-indy-all-in-one:2021-01-08-7a055c3 (do not use the exact example tag of course)
A packages/cactus-test-tooling/src/main/typescript/indy/indy-test-ledger.ts code file is added with a IndyTestLedger class in it that is responsible for providing a start() method that takes care of launching
A packages/cactus-plugin-ledger-connector-indy/src/main/typescript/plugin-ledger-connector-indy.ts file is added with a PluginLedgerConnectorIndy class in it. This class uses the indy-sdk npm package under the hood to implement the connector's usual methods: https://github.com/hyperledger/indy-sdk/blob/master/wrappers/nodejs/README.md
The functionality of the connector is covered by the end to end tests mentioned earlier. The tests must be using the AIO image to simulate a production Indy ledger with reasonable accuracy (so not really an actual production ready deployment, but as similar as possible with minimal resource usage so that it works on an "average" developer machine).
Web services are implemented so that the connector's functionality can be exposed via the network when the plugin is loaded into the Cactus API server.
Tests are also covering (e.g. using) the generated API client class (for which you'll need to define the necessary request and response types and endpoints in a file at packages/cactus-plugin-ledger-connector-indy/src/main/json/openapi.json file.

Links, Tips, Useful Information

Most important tip: You should study the code of other - already working - connector plugins to see how they implement web services for example. A lot of the code is just boilerplate around the actual logic that translates Cactus API requests into indy-sdk calls to the Indy ledger.

The indy-sdk seems to have some native code (C++ compiled binaries) dependencies, so watch out for these and try to avoid having to change the default Cactus build if possible (sometimes it's not possible, but an attempt has to be made to keep it simpler rather than to complicate it further potentially needlessly)
Start with the connector plugin package's implementation by simply copy pasting one of the existing connectors and then find & replace the ledger name within that folder accordingly ($COPIED_LEDGER_NAME => indy)
Double check that in packages/cactus-plugin-ledger-connector-indy/package.json the dependency versions to other Cactus packages are up to date and that the name of the package itself is also up to date.
There is already some working code for Indy ledger integration, but that is written in Python which we cannot use (without additional complexity) so a Typescript based solution is still needed.

Stone

@petermetz @stonechen1995 @jscode017 Are you guys working on this issue?

@outSH Not me, sorry for not keeping this up to date from my part!

@outSH Not me, sorry for not keeping this up to date from my part!

Not me too, sorry for not updating my status. @petermetz can you unassign me? I can not find the self-unassigned button on my computer, thanks.

@outSH Not me, sorry for not keeping this up to date from my part!

Not me too, sorry for not updating my status. @petermetz can you unassign me? I can not find the self-unassigned button on my computer, thanks.

@jscode017 No worries! It is currently unassigned so it's all good.

Not me either. Thanks for notifying us. On Oct 26, 2023, at 3:15 PM, Peter Somogyvari @.***> wrote:
@outSH Not me, sorry for not keeping this up to date from my part!
Not me too, sorry for not updating my status. @petermetz can you unassign me? I can not find the self-unassigned button on my computer, thanks.
@jscode017 No worries! It is currently unassigned so it's all good.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Restore error message when not installing IPYKernel or Jupyter Dependencies

The error message displayed when users cancel the prompt to install ipykernel has changed (the new error is as per screenshot).
Previously we'd display a message indicating the fact that the cell could not be run as ipykernle is not installed.
Yes, the user hit cancel here, but they don't know what ipykernle prompt is, and we chose to display the detailed error message in the output as well (asking with instructions to unblock themselves)
I think we should bring back the old error message.

Same applies when Jupyter packages are missing (ie. we are no longer displaying messages on how to install jupyter notebook packages)

This should simply be a matter of not throwing an error when canceled. Instead just rethrow the original error.

Not sure if we need to show the user they canceled or not. I can see it both ways. Interactive window shows the state of the error after it's done. The ipykernel error is true, but they not remember they canceled the install.


Add a Makefile

Simplify execution of go commands with a Makefile.
Possible Makefile targets:

make build
make run
make test
make unit_test
make integration_test
make lint
make dep

Other ideas:

support cross compile?
use the commands to execute e.g. the tests in the github actions?

After adding a Makefile the TODO list in README.md should be updated.

Makfile added


About Healing Aura ritual's Patchouli guidebook visualization misleading

General Information
Describe the bug:

Even though all blocks shown by The Druidic Arts are placed at there respective correct positions,
and ritual is started normally, there is still a progress bar shows "6/16".
To Reproduce:

Use The Druidic Arts to show Healing Aura ritual's visualization.
Place Pyre, Birch logs and leaves, Runic Stones according to the visualization.
You will find that progress bar shows "6/16".
Put all items needed for starting the ritual, and kindle the Pyre.
You will find that though ritual is started successfully, the progress above is still shows "6/16".

Expected behavior:

The visualization should show "Finish" instead of showing what I described above.
Environment Versions

Mystic Mods Versions

MysticalLib: mysticallib-1.12.2-1.6.0
mysticalworld-1.12.2-1.7.1
Roots-1.12.2-3.0.24

Other Versions:

Conflicting mod (if regarding mod integration):
Other mods you think could cause issues:
Forge: <IP_ADDRESS>47
Minecraft: 1.12.2

Additional Information
Screenshots (if available):

Additional context (optional):
I have found that, those 10 missing blocks is Birch leaves.
Ritual can be started without those leaves, so the altar is finished when it is still showing 6/16.
But I think this may be misleading, and that progress bar is quite annoying.
Would you like to change this?
Maybe this post is a suggestion instead of bug report?
Thanks for your consistently warm-hearted help!
Look forward to your reply!

If you go back into the Patchouli guide and click the "eye" again, it will "unvisualise" and remove the progress bar. (It's a bit unclear in Patchouli itself)


AdEMA NaN when loading from state_dict

System Info
Running a standard training loop where I save the optimizer state_dict using opt.state_dict().
Upon loading using opt.load_state_dict() to resume, the model immediately NaNs after the first backprop step.
This only occurs using the AdEMA optimizer:
bnb.optim.AdEMAMix8bit(model.parameters(),                             lr=lr,                             t_alpha=T,                             t_beta3=T)
AdamW and others load state dict perfectly fine. Any ideas?
Reproduction
`
opt = bnb.optim.AdEMAMix8bit(model.parameters())
#run training loop
torch.save(opt.state_dict(), "dt.pt")
#try resuming opt from state_dict later
opt.load_state_dict("dt.pt")
#run training loop again
`
Expected behavior
Optimizer should resume training without NaNning

Update: thought that the issue might have been that the value T was not loaded properly at the start of resuming training; therefore leading to exploding gradient. However even setting T = 0 does not enable resuming from AdEMA state_dict.
When not loading from AdEMA state_dict (ie resetting the optimizer), the optimization works fine (but not ideal because the whole point of AdEMA is that we can keep a moving average of gradients over many thousands of steps)


Add jazzy arc linter

https://github.com/google/arc-jazzy-linter
This will give us documentation linter warnings for undocumented APIs.

🎊 My diff is ready for review at http://codereview.cc/D1138


Feat/max growth study

included scripts for simulating ecYeast under various C/N substrates + data + a plotting function

@IVANDOMENZAIN note that I changed the title of the folder from /ecYeastGEM/figures/yeast8 to /ecYeastGEM/studies/yeast8, to keep it more generic. Would be good if you can adapt your branch as well (or if you want I can do it for you and merge it to master)

@BenjaSanchez  I already changed the folder file, but I'm going to remove all FVA related scripts from this repo and call them from GECKO (will be internally cloned) since they're already part of utilities


Docs: add tutorial for limits

Class limits has its own public header, and appears to be part of the library's interface. But the docs never say what it is for and when and how users are expected to use it.
It looks like in the safe usages users would use its constants to determine the sizes of their buffers. I think the docs should show such real life example.

Added in https://github.com/cppalliance/charconv/pull/127.


Added string specifier in Ex 06

std.fmt.format does not take strings without a string specifier since
zig 0.8.0.

I don't know if the behavior of std.fmt.format actually changed or if it is just a temporary regression, since 0.8.0 is still in development. I tested my assumption with a small program:
$ cat print.zig
const std = @import("std");

pub fn main() !void {
    std.debug.print("{}\n", .{"test"});
}

$ zig version
0.7.1

$ zig run print.zig
test

$ zig-master version
0.8.0-dev.1128+1480c4280

$ zig-master run print.zig
/mnt/d/dev/repos/zig/zig/lib/std/fmt.zig:525:25: error: cannot format array ref without a specifier (i.e. {s} or {*})
                        @compileError("cannot format array ref without a specifier (i.e. {s} or {*})");
                        ^
/mnt/d/dev/repos/zig/zig/lib/std/fmt.zig:358:23: note: called from here
        try formatType(
                      ^
/mnt/d/dev/repos/zig/zig/lib/std/io/writer.zig:33:34: note: called from here
            return std.fmt.format(self, format, args);
                                 ^
/mnt/d/dev/repos/zig/zig/lib/std/debug.zig:65:27: note: called from here
    nosuspend stderr.print(fmt, args) catch return;
                          ^
./print.zig:4:20: note: called from here
    std.debug.print("{}\n", .{"test"});
                   ^
./print.zig:3:21: note: called from here
pub fn main() !void {
                    ^

I opened another PR that adds a version check for the zig compiler.

Exercises 7, 8, and 43 also need to be updated for this change.

Thanks @SpexGuy.
I guess I won't update the commit before it is clear what zig version to write against. (asked this in my other PR)

@Joefish and @SpexGuy Thanks!  I'm running out of time today, but this makes total sense and...it looks like I need to update my current version of Zig!  I'll review this ASAP.

I changed my mind. This is really important because it would be very frustrating for new learners.  Merging now!

@SpexGuy I've also updated Ex. 7 and 8. 43 already had {s}. Did I miss a print() or was it a different exercise? Thanks!


[PE-D][Tester C] Reward points has an integer overflow

Steps to reproduce:

Run the following command: addpts n/Irfan Ibrahim p/2147483647
Run the following command: addpts n/Irfan Ibrahim p/1

Expected behaviour: the program does not allow the user to increment points past a certain level.
Actual behaviour: the second command ceases to work and there is no output from the application, neither an error nor a success message.

Suggestion: check if incrementing the value is going to go beyond the INT_MAX limits!

Labels: severity.Medium type.FunctionalityBug
original: kailashgautham/ped#12

set the max to 2,000,000,000 points for Reward Points and Membership Points


New Ansible example for Powerflex

Added Ansible example for PowerFlex storage provisioning for VMware workload.

Will do Florian.
Get Outlook for iOShttps://aka.ms/o0ukef
Internal Use - Confidential

From: coulof @.>
Sent: Friday, March 15, 2024 8:43:10 PM
To: dell/iac-storage-automation @.>
Cc: Kodati, Parasar @.>; Author @.>
Subject: Re: [dell/iac-storage-automation] New Ansible example for Powerflex (PR #15)
[EXTERNAL EMAIL]
@coulof approved this pull request.
Add or update a README.md later on
—
Reply to this email directly, view it on GitHub [github.com]https://urldefense.com/v3/__https://github.com/dell/iac-storage-automation/pull/15*pullrequestreview-1939208391__;Iw!!LpKI!l4iA0YLyuVndG5m-o3jXiDgU_hu2PjcdnT7puGbgfB62xxNWLviX8cRjiekspt2M6qlduwwckuYC90uZJlbjgWSuI_Q$, or unsubscribe [github.com]https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BCGIHWYLJCKQ3YY6XVXEX5DYYMFYNAVCNFSM6AAAAABEYFXAW6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSMZZGIYDQMZZGE__;!!LpKI!l4iA0YLyuVndG5m-o3jXiDgU_hu2PjcdnT7puGbgfB62xxNWLviX8cRjiekspt2M6qlduwwckuYC90uZJlbj4ZBqK0o$.
You are receiving this because you authored the thread.Message ID: @.***>


[Bug]: When entering a song, game loads the wrong difficulty

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
planckcons#0002
Version Info
Latest available release
What operating system are you seeing the problem on?
Windows
Bug Behavior
The selected difficulty shown while in the musicwheel is different than the one that is loaded when entering the song.
For example: In the musicwheel the selected difficulty is "IN" and the one that starts playing is "HD"
Attached is video showing:

Exiting the previous song
Selecting next song (the selected difficulty is shown as IN)
The loaded chart is the HD difficulty

https://user-images.githubusercontent.com/12530148/145721794-6f9a86b0-b97c-44da-bc2a-5f941341a6df.mp4
.
Expected Behavior
If the musicwheel shows for example the IN difficulty it is expected that when entering the song, the loaded difficulty will be IN.
Reproduction Steps
I could not find a way to consistently reproduce the bug.

It can happen when the song is the first in the session
It can happen after playing song with multiple or single difficulty
The difficulty (IN, HD, ...) of the previous song doesn't seem to affect the chance
I couldn't reproduce it with every song I tried, but it can happen with at least "Happy H. Christmas" in stepping stones 4
If the song has 3 difficulties both of the 2 non-selected difficulties can be the one that starts.

Anything else?
No response

Do you mash the keys that you have bound to MenuUp and MenuDown before starting the chart? If so, try not doing that, as that stopped this behavior for me when I was having this same issue.

Okay I tested it and that was the cause. After pressing enter when entering a song there is a small window where you can still change the difficulty.

fixed 9877c2a2eb1a788809ec76438996f725a224dcf6


models (folder)

Model represents the shape of the data: responsible for handing database related changes
Files inside the models folder:

[x] index.js (controlling page for our models)

[x] Add login functionality for Artist

[x] Add login functionality for Art_Lover

[x] Art_Lover.js
[x] Artist.js
[x] Liked_Artist.js
[x] Registry.js
[x] Art_Piece.js
[x] Collection.js
[x] Art_type.js

Models are done and ready to be seeded...we are two steps ahead. on target for being done tomorrow...yeah!!!


Improve main page SEO

Things added/changed:

Improve main page SEO.

LGTM. Thanks for your contribution.


Allow UTF8 encoded server names and description, dedicated cmd window now titles the server name.

Directly reading from the server cfg file directly to get server name and server description. This made server names and descriptions with Chinese characters work correctly. Demo:

Clients don't need changes for this, as UTF8 decoding works just fine clientside.
I like to have server names displayed on the cmd title for better identification between multiple servers, so it works like that now. Demo:

This fork contains code from the NorthstarCN fork, which has to work with some master server modifications so I commented them off in this pr.

I'll close this here as the main fork already broke too much


Blurred background support

Support blurred background on all platforms.

[ ] OS/X
[x] Windows (Acrylic backdrop)
[x] Linux: KDE window manager (kwin)

Blur Topics

https://learnopengl.com/Advanced-Lighting/Bloom

References:

https://gist.github.com/ethanhs/0e157e4003812e99bf5bc7cb6f73459f
https://github.com/riverar/sample-win32-acrylicblur/blob/master/MainWindow.xaml.cs
https://stackoverflow.com/questions/44000217/mimicking-acrylic-in-a-win32-app

[ ] Linux: Gnome's Blur my Shell!

https://github.com/aunetx/blur-my-shell#application-blurring

[ ] Linux: Gnome's Blur my Shell!

https://github.com/aunetx/blur-my-shell#application-blurring

Nice. Thanks!

@Summertime I've merged it to master, but we need to wait for https://github.com/aunetx/blur-my-shell/issues/300 to be addressed. That may not be instant, and you may need to just add contour's WM_CLASS to explicitly enable it until the referenced ticket is fixed, but it should hopefully only be a matter of time. And thx for the info on blur-my-shell ;-)


Create ID

how do you return the ID of the new row inserted by the create() method?

$db->create('table', ['field' => $value])->id()

see https://github.com/adriengibrat/Simple-Database-PHP-Class#various-methods
;)


TW Jquery Upgrade v3.5.1 replace .size() with .length (deprecated method)

TW recently upgraded it's jquery version to a much higher version than before and it broke some scripts. Updated sangu so it works again.

Hey Thanks a bunch for the PR!
I'll have a look into merging & deploying it this weekend

Hey Thanks a bunch for the PR!
I'll have a look into merging & deploying it this weekend

It's available on sangu.be and should arrive in the Chrome web store once reviewed by Google.

It's available on sangu.be and should arrive in the Chrome web store once reviewed by Google.


Jyutping Improvement

I don't know how you farm those jyutping,
https://words.hk/faiman/analysis/wordslist.json
https://words.hk/faiman/analysis/charlist.json
but anyway, if you haven't included this method, I think you can try.
Just so if you wanna update the dictionary, you can parse all the words from there, for the tokenizer, we can use jieba
https://github.com/hockyy/jieba-cantonese
I've made a script to auto generate jieba user dict to tokenize, so querying jyutping per token can be better, if the result don't exist, fall back to per character jyutping

let me know if you need any help.
I'm currently developing this project https://github.com/hockyy/miteiru

@graphemecluster 據我所知粵典數據係一早就已經用咗嘅？而家嘅更新主要係用咗 Jon 嘅字型數據？

而家淨係用 Jon 嘅數據，但都肯定準過結巴分詞
@chaaklau 你覺得你粵典個 word list 標粵拼有冇用？

@hockyy The accuracy should reach more than 99% since our latest updates (JS/TS version 2.0.0 / Python version 0.3.0) a few days ago.

ack ack okk thank you info

btw 呢個import唔到

我聽日debug啊好眼瞓😪


Add AppLifecycleTests to Helix

The github pipeline runs as a built-in Administrator account thus it always runs tasks as Elevated.
Dynamic Dependencies doesn't support elevation (today)
Thus AppLifecycle's tests can't be run directly by the github pipeline
But Helix is now up for test execution
Add the AppLifecycleTests to the Helix test environment
https://task.ms/34107070

Close this issue as the internal task is cut.


Not able to integrate xmpp swift messenger in my iOS app

Hi
I have a create an empty xcode project in xcode7.1.1 with swift 2. I wrote pod 'xmpp-messenger-ios' in my pod file. After installing all the dependencies when I build the project it show errors as "include of non-module header inside framework module" as shown in attached screen shot. This error is not letting me proceed. please help?

I have the same problem

Change #includes "Something/something2.h" with @include Something

I change:
#import "CocoaAsyncSocket/GCDAsyncSocket.h" to @import CocoaAsyncSocket;
#import "CocoaLumberJack/DDLog.h" to @import CocoaLumberjack; (ps why "j" not capitalized?)
and try to build.
After that same problem in the file JSQSystemSoundPlayer+JSQMessages.h
change too:
#import <JSQSystemSoundPlayer/JSQSystemSoundPlayer.h> to @import JSQSystemSoundPlayer;
and it is succesfully builded. What the magic? I didn't understand...
@include or @import is the best choice in this situation?

please, search in closed issues too, before opening a new issue. Here you can find the solution: https://github.com/processone/xmpp-messenger-ios/issues/15

Thanks @orkhanalizade, closing this now


Update event tests for strapi v4

Update tests and correct search for contact mail discovered when adding the tests

Thanks.


[STORM-3706] Add Cluster.needsSchedulingRas() to tests

What is the purpose of the change
Prior to refactoring of Resource Aware Scheduler, Cluster.needsSchedulingRas() would always return true. Call this method in tests to ensure that the correct value (true/false as appropriate) is returned.
How was the change tested
Run unit tests, especially TestResourceAwareScheduler and TestBackwardCompatibility

License problem is back. Closing and reopening for recompile.


Player IDs of DeathPenalty bags not rewritten

If you transfer players from coop to dedicated server, DeathPenalty bags are still belongs to old player and can not be pick up, because the bag owns a other guild.
Workaround: Set bCanPickupOtherGuildDeathPenaltyDrop=true

Thank you for this. Good find.


[FEATURE 💡] Element Changing Positions

[FEATURE 💡] Element Changing Positions  #<140> 📐

I Bikalpa Paudel have worked for #<140>

Guidelines 🔐
I accept the fact that I have followed the guidelines and have not copied the codes from around the internet

[x] Contribution Guidelines
[x] Code of Conduct

Issue to be closed 🛅

My pull request closes #<#140>

Screenshots 📷
Here are the pictures of changes that I have made 🔽

I am really sorry. I mistakenly closed it. I want to link PR here in this issue but I don't know how.
I don't know much about all these features. I am so sorry.
Please do something about this


Added Sparkplug B component using Eclipse Tahu library

Description

Created a Sparkplug B component wrapping the Eclipse Tahu library.
The Sparkplug B concepts of Edge Nodes and Devices are implemented as Camel Producers. Host Applications are Camel Consumers.
Producer testing uses the Sparkplug B TCK tests with a HiveMQ CE Testcontainers service embedding the TCK extension into the broker. This does NOT mean this Camel Component is Sparkplug B-spec compliant or provides any guarantees of compliance. This Component can be used to create spec-compliant Edge Node and Device behavior, given compliant configuration and Route payloads.
Consumer functionality is minimal at this point but can be fleshed out in later releases.
Target

[X] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[X] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[X] I checked that each commit in the pull request has a meaningful subject line and body.

[X] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

@orpiske Thank you for your feedback!
Most of these should be no problem at all to incorporate.
We may need to come up with an alternative approach to the HiveMQ Testcontainers broker embedding the Sparkplug B TCK extension library. The only reason I didn't include this code in the test-infra services is because it is so specialized. Maybe a generic HiveMQ CE test service for straight MQTT with the Tahu component adding the TCK extension? I'm absolutely open to suggestions.

@ryan-highley have you worked on all the tips/issues from Otavio? I wonder if this PR is getting closer to be ready for merge.

@orpiske Thank you for your feedback!
Most of these should be no problem at all to incorporate.
We may need to come up with an alternative approach to the HiveMQ Testcontainers broker embedding the Sparkplug B TCK extension library. The only reason I didn't include this code in the test-infra services is because it is so specialized. Maybe a generic HiveMQ CE test service for straight MQTT with the Tahu component adding the TCK extension? I'm absolutely open to suggestions.

I think we have a few options here:

Create a custom container w/ for the HiveMQ. For instance, we do that for the SMB component, where we have a Dockerfile and we then we build the container using it.
Alternatively ... using the official container, and then mounting the location for the extension as a volume ... I think that could work.

@ryan-highley have you worked on all the tips/issues from Otavio? I wonder if this PR is getting closer to be ready for merge.

@davsclaus Working through them yesterday and today. Getting closer but still need to simplify the testing approach. Depending on my client workload, we should have this knocked out today or tomorrow.

@orpiske
Thanks for your continued support!
I've been putting together the documentation today and should have that ready shortly. The Converter is shaping up as well and I have a plan for testing it I need to implement.
Should be pushing another update late this afternoon.

@orpiske
Both the documentation and the payload converter have been pushed and are ready for review.
The Host Application testing is still thinner than I'd like but automating it may be tricky for a few scenarios. At least it passes the Session Establishment TCK case.

Yes the syntax in @UriEndpoint must have all its options defined via @UriPath so the syntax can be understood by camel -catalog.

Thanks @ryan-highley let us know when you have the tests fixed and that this PR is complete.

DSL generation is failing. I'll have it fixed and repush shortly.

Updated the DSL generated files.
Assuming the build completes successfully now, I'm happy with this PR.
@davsclaus @orpiske @oscerd
Thanks for all your help and reviews!


[DOC] Securing your webhooks doc doesn't contain expected claim

Hello there,
I'm going through a documentation that described how to secure the Azure Marketplace SaaS Webhook.
Regarding to the doc:
"appid": "this is the resource id you use when you create publisher authorization token to call SaaS fulfillment APIs"

I've implemented a secure webhook as shown in the [documentation](https://microsoft.github.io/Mastering-the-Marketplace/saas/pdfs/10.3-simple-webhook-dotnet-securing.pdf). I didn't see the claim with the appid type.
Below I attached claims keys that were received from a webhook request header:
aud
iss
iat
exp
aio
azp
azpacr
oid
rh
sub
tid
uti
ver

I don't see appid there. Seems that has been changed to aud, right?

Hi @PFYasu - For this I recommend raising a support ticket on our partner center please.

Hi @santhoshb-msft. I wasn't sure where to raise this issue.
Thanks for your recommendation. I'll create a support ticket on the partner center, as you suggested.


Invalid image ref link in D3D12EnhancedBarriers.md

Asymmetric Aliasing is Even More Expensive

Looks like this was resolved in https://github.com/microsoft/DirectX-Specs/commit/a47d4f8bb3b1dc8639fce31a98345bc947c45632


feat: expose GlobalKey in StatefulLocation

Description
Partial fix for #11 , so we can access the GlobalKey used in a StatefulLocation's DuckShell when wanting to override this in the pageBuilder property.
Related Issues
#11
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Two questions:

Could you substantiate a little more in which cases someone would want to override this?
Since this member is now public, could you add some documentation?

Thanks!

Certainly!
One of the cases is shown in my example project, where I wanted to create a StatefulLocation with a custom animation. We need to override the pageBuilder for this, and make sure to add the DuckShell in its implementation.

I see what's up. You want to wrap stateful location in a Page, but it only supports wrapping in a Widget. So what you do is you grab the pageBuilder all the way on the core Location. It basically means you need to re-implement StatefulLocation all over again, but now _key is private.
Are you able to do the following?
  @override
  LocationPageBuilder? get pageBuilder => (context) => ModalPage(
        name: path,
        child: builder(context),
      );

It's complex, but now you've got a Page wrapping the "normal" stateful location builder, including key, and then you've got a childBuilder with your wrapping page as well as all the child locations.

Yes this works, thank you! Looks a lot nicer than before as well, not having to know the intrinsics of the StatefulLocation. I'll close this one.


Fix "disabled bans" so that trust scores are still logged

The recent hotfix to turn off bans made changing trust scores a no-op. We should use the proper mechanism that still tracks the trust scores.

The old -no-bans flag and implementation were removed in 0b698ce92e771bc8fe9ad79302a10690d1fedee1.
We could undo that change to turn off banning that still tracks and logs the trust scores.


Add documentation for data-value-key

Documentation for data-value-key attribute that would have saved me about an hour...

Also would have avoided this issue: https://github.com/sergeyt/meteor-typeahead/issues/60

@vsivsi thanks for PR!


DWM1001 upload problem (JTAG interface not configured)

Step 1: What do you want?

Need help

Step 2: Describe your environment

Arduino IDE version or Toolchain: 1.85
dw1000 Library version: 0.50
Arduino device: Arduino Uno
External power supply for DWM module (3.3V)
Used adapter board: No
Using DWM1001 module

Step 3: Describe the problem
The boards available to me after installing required nRF52 library:

This is the wiring diagram I used, although I used an Arduino Uno and a DWM1001 module with the Ready pin on the DWM1001 treated as the IRQ pin on the dwm1000. I am using a logic converter for the CSn, CLK and other SPI pins (MOSI and MISO) only. The other pins are directly connected. As mentioned above, I am using an external power supply to power the DWM1001 module (3.3V source).

Affected file(s) or example(s):

BasicConnectivityTest.ino

Steps to reproduce:

Connect the wires as indicated in the diagram above.
Select the Arduino Primo board in Arduino IDE
Attempt a flash with the code from the BasicConnectivityTest example

Observed Results:
Sketch uses 35224 bytes (9%) of program storage space. Maximum is 385024 bytes.
Open On-Chip Debugger 0.10.0-00004-g0e78f263 (2017-02-20-13:07)
Licensed under GNU GPL v2
For bug reports, read
  http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
cortex_m reset_config sysresetreq
adapter speed: 5000 kHz
Error: unable to find CMSIS-DAP device
Error: No Valid JTAG Interface Configured.
Error: No Valid JTAG Interface Configured.

Expected Results:

That it would successfully flash and start outputting.

Relevant Code:
#include <SPI.h>
#include <DW1000.h>

// connection pins
const uint8_t PIN_RST = 4; // reset pin
const uint8_t PIN_IRQ = 2; // irq pin
const uint8_t PIN_SS = SS; // spi select pin

void setup() {
  // DEBUG monitoring
  Serial.begin(9600);
  // initialize the driver
  DW1000.begin(PIN_IRQ, PIN_RST);
  DW1000.select(PIN_SS);
  Serial.println(F("DW1000 initialized ..."));
  // general configuration
  DW1000.newConfiguration();
  DW1000.setDeviceAddress(5);
  DW1000.setNetworkId(10);
  DW1000.commitConfiguration();
  Serial.println(F("Committed configuration ..."));
  // wait a bit
  delay(1000);
}

void loop() {
  // DEBUG chip info and registers pretty printed
  char msg[128];
  DW1000.getPrintableDeviceIdentifier(msg);
  Serial.print("Device ID: "); Serial.println(msg);
  DW1000.getPrintableExtendedUniqueIdentifier(msg);
  Serial.print("Unique ID: "); Serial.println(msg);
  DW1000.getPrintableNetworkIdAndShortAddress(msg);
  Serial.print("Network ID & Device Address: "); Serial.println(msg);
  DW1000.getPrintableDeviceMode(msg);
  Serial.print("Device mode: "); Serial.println(msg);
  // wait a bit
  delay(10000);
}

Error: No Valid JTAG Interface Configured.

Seems you have not configured a interface to flash the software. This is not a problem of the library.

It's more of a question than a problem with the library. Just wanted to know if someone can help.


Todo: Follow link redirects

Proxy it!

Giving the current scam message situation, this issue is now high priority

Covered by 23a298da5eb7727ce1d200a6f72d6a753d3fd7c9


Fix System.ValueTuple on net 4.7.1   ---- issue 3896

This fixes #3896
What was happening is that on net471 the F# compiler was not fiunding any metadata describing the System.ValueTuple type because.  It was loading the System.ValueTuple from mscorlib.dll.
This change ensures that the compiler will load the type from the System.ValueTuple dll, that is provided either as a command line reference or by loading the System.ValueTuple.dll from all of the places we normally magically look.
It looks like the FCS doesn't require a deployed valuetuple dll, and so we disable default reference for it.
In general that won't be a problem because the standard F# templates reference the System.ValueTuple package anyway and so they are not reliant on this default reference specification.

@dotnet-bot Windows_NT Release_ci_part2 Build please

@dotnet-bot test Windows_NT Release_ci_part2 Build please

@dotnet-bot test Ubuntu14.04 Release_fcs Build please

@dotnet-bot test Windows_NT Release_ci_part2 Build please

@dotnet-bot test this please

@dotnet-bot test this

@dotnet-bot test this please

@dotnet-bot test this please

@mmitche do you know why it's not triggering the tests?
Thanks
Kevin

@KevinRansom The servers are moving, there was an outage notification sent a few times over the last week or so.  Did you get it?

Oh... I never noticed it.  That makes sense.  When are they back on line?

@KevinRansom I am hoping in a couple hours.

Sweet, thanks mate

@dotnet-bot test this please

@dotnet-bot test this please

@dotnet-bot test this please

@mmitche is there some reason that our Ubuntu ci tasks aren't triggering?

@mmitche  is there some reason that our Ubuntu ci tasks aren't triggering?


Design for desktop & mobile view and  content for Dashboard

Create desktop & mobile view designs & content for Dashboard

Figma Link to task CLICK THIS TO FIGMA


changing receive messages to long poll by default

implements long polling by default for ReceiveMessagesAsync calls
can still short poll by setting waitTimeSeconds to 0
closes #245

Codecov Report

Merging #246 (6a4383b) into master (76d7978) will increase coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #246      +/-   ##
==========================================
+ Coverage   92.81%   92.90%   +0.09%
==========================================
  Files           2        2
  Lines         153      155       +2
  Branches       24       25       +1
==========================================
+ Hits          142      144       +2
  Misses          8        8
  Partials        3        3

Impacted Files
Coverage Δ

src/helper.ts
92.19% <100.00%> (+0.11%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 76d7978...6a4383b. Read the comment docs.


[GHSA-gvhx-gj42-m28v] Cross-site scripting (XSS) vulnerability in Wiki content...

Updates

Affected products
References
Summary

Comments
Trying to add it to ruby-advisory-db repo so I decide to add the data here too.
Unclear about source code location.
Initial advisory (in Japanese) was: https://web.archive.org/web/20090501134922/http://www2a.biglobe.ne.jp/~seki/ruby/rwiki.html

Why was this PR deleted?

Here is the advisory in ruby-advisory-db repo: https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rwiki/CVE-2006-2581.yml


A bug of thermostat

Hi everyone,there is my problem
When I said to siri “turn off the thermostat”,
it will switch to auto mode.
The Voice control will send 3 to TargetHeatingCoolingState。

Have have the same issue with a project developed also. Just did a "work around" for it, but not idle.

I had the same problem. This is actually a bug in Chinese Siri. If you say thermostat 「空調」 instead of 「冷氣」, it will turn off successfully.
To address this without workaround, just use newer HeaterCooler service which is introduced in iOS 11 to replace old Thermostat service.

Hi @Fonger
Thank you for your answer.I will try it.
Best Regrads
songzh


CI friendly fast mode for try state checks

Reviving https://github.com/paritytech/substrate/pull/13286
Should resolve https://github.com/paritytech/substrate/issues/13114
Adds a new fast mode to TryStateSelect which skips slow running state checks.
Adds two new options [fast-all | fast-try-state] to on-runtime-upgrade --checks.

Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2386987

Updates here?

Updates here?

Repeat 😁

I am working on refreshing this PR.

@liamaharon Thanks for raising those points. Its still all open to discussion but I will write how I was thinking about this.

This is a cool idea, but I'd like to raise the possibility that it may be better to completely turn off try-state checks in the CI than to have them run partially.

Currently the try-state checks are disabled on CI (it only runs pre- and post-upgrade checks). So in a way what you are suggesting is what is happening currently.

Run partially, the green CI check loses its meaning. It no longer would signify that try-state hooks are passing, rather just that they may be passing. To be sure they're actually passing, they would need to be run again somewhere else anyway, so there seems to be little value in running them in the CI.

Another way to think about it is, this would allow every pallet to write very thorough try state tests. Some of these tests may take really long time (probably hours) and it would be great to run all of them on CI but we also don't want CI to be stuck for hours. The pallet developer still believes other tests would ensure 99.9% scenarios are covered and this slow running test is something they run occasionally outside CI to ensure all storage items are consistent to the expectations.
To give a more concrete example (which is actually the reason why we wanted to introduce the fast mode) we can look at this try-state check in staking pallet. It iterates over all nominators (~ 44k) and then for each nominator, it fetches all active validators (~ 300), gets their exposure, iterates over all of its stakers (could be upto 512) and checks if the nominator (in the first loop) is only present once in a validator's exposure. This is cubic time complexity and takes more than 2 hours to run currently.
Also, most of the times, a failing try-state checks may not be introduced by the current PR but through a sneaky bug that  we only found out about later. I think we might even want to keep these tests to allow_failure and these are just indications to investigate and not blockers to a PR.
To summarise, I think what this PR is trying to do is find a middle ground where we can run try state checks in the CI that would cover most of the inconsistent state scenario but still enable pallet developer write some more thorough but expensive tests that they can run outside CI if they want to. Its also important to emphasise try-state check should only be our 3rd or 4th line of defence.

At most, they could alert the dev to some failing hooks. But, the dev would still need to run the full set of try-state hooks somewhere else anyway.
The green check may provide a false sense of security to devs who're unaware that the full set of hooks are not run in the CI.
The feature comes with a cost: it adds extra configuration to the cli, and introduces cognitive overhead for developers working on the try-state hooks needing to decide whether a check should be 'fast mode' or not.

I agree we should look to improve this, make it more intuitive and better documented. By default every test should be marked as fast test unless we notice they are taking really long to run in the CI. I do think though that running 99% of the try state checks on CI and ignoring one is better alternative than not running anything on CI. If there are complex changes to a pallet logic, a developer should always run full suite (may be we can have a bot command that runs the full suite on demand) and even possibly add more state checks.

bot rebase

Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions.

Yes, will be reworking on this.


Revert "Do not use $this to call static method"

Reverts yiisoft/yii2#18614 because method primaryKey not exists in BaseActiveRecord. We must define abstract static public function primaryKey(); in class BaseActiveRecord because ActiveRecord defined it as static to keep BC.

https://github.com/yiisoft/yii2/blob/master/framework/db/ActiveRecordInterface.php#L30

@bizley ok, but it's still wrong because method defined as static

https://github.com/yiisoft/yii2/pull/18614#issuecomment-826293939


run upstream velero ci against downstream

seeing if running upstream ci against our downstream copy is valuable. /hold for now.

oops.  git commit -m "looks like we need make update before make ci`" -s

@kaovilai there is a squash and merge option.. why not just use that?

I'm ok with that usually. I'm concerned here that the commits in this PR include commits you did not author. Double check that you're using the right branch for this PR to merge into.

dymurray and others added 5 commits last month

@kaovilai ya. it just needed to be rebased and squashed..

/remove-lifecycle rotten


UpdateRepositoryEnabledStatus not working

If I do execute the above mentioned cmdlet I do get back a response saying "The required anti-forgery cookie "__RequestVerificationToken" is not present."
Any idea if we can or how to set repo settings without that token? I'm sure the REST API is not exposing an endpoint to do this, but I was hoping in a working undocumented endpoint.

Sorry, wrong cmdlet

Thanks for the report. I'll take a look at it ASAP. My guess is that some
change in the service side may have broken my hack.
Can you confirm whether you're using Azure DevOps Services or Server? If
Server, what version?
Em qua., 26 de jun. de 2024, 17:44, Mario Majcica @ AAB <
@.***> escreveu:

Sorry, wrong cmdlet
—
Reply to this email directly, view it on GitHub
https://github.com/igoravl/TfsCmdlets/issues/221#issuecomment-2192596647,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFRGJIZSIZPJR5JK7SENW3ZJMRZZAVCNFSM6AAAAABJ6TM4ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJSGU4TMNRUG4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Sorry it is working as expected, it was an issue on my side.

Thanks for the follow-up!
Em qua., 26 de jun. de 2024, 17:51, Mario Majcica @ AAB <
@.***> escreveu:

Sorry it is working as expected, it was an issue on my side.
—
Reply to this email directly, view it on GitHub
https://github.com/igoravl/TfsCmdlets/issues/221#issuecomment-2192607225,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFRGJOHZYHK4X2DWBFIRRLZJMSWVAVCNFSM6AAAAABJ6TM4ZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJSGYYDOMRSGU
.
You are receiving this because you commented.Message ID:
@.***>


Shuffle the hosts when connecting to the broker

Currently the first successful broker is used when multiple hosts are specified.

Perhaps the distribution of hosts could be somewhat configurable?
For example: to test only intra-broker publishing on a 1-1 topology (publishers and subscribers on the same node), each matching client would need to connect to the same node.  To force all messages to be forwarded inter-brokers, they'd have to be placed on different servers.

Fixed by #16


Wrong Errormessage if confirming with Enter on Login

If you type in all 3 fields and confirm with Enter while in "Account name", you get an error message saying something like "you have to enter an account name". Clicking the button works of course.

This is due to a rather annoying limitation in WPF, I'll see if I can find a workaround for the next release.

This should be fixed with the new version, since account name is no longer required.


build failed actually but Travis CI still green

This build  failed actually, but Travis CI gave me green still.

Fix at https://github.com/Azure/azure-cli-extensions/pull/1075


Allow option to adjust url encoding by path-to-regex

What problem does this feature solve?
If you need to use a permalink system, where your API routes need to use a path to get the response. An example of this is using Vue as a frontend for Wordpress, but allowing wordpress to dictate the url structure.
So for example
would have a route that looks like:
{
      name: 'post',
      path: '/:permalink([0-9] [/][0-9] [/][\\S] )',
      component: StandardArticle
}

and a page would have a route that looks like:
{
     name: 'page',
     path: '/:permalink*',
     component: StandardPage
}

This would mean a post url would look like
/2018/04/some-post
and a page would look like
/some-page
The regular expressions work but when you actually try to use them it would look like
/2018%2F04%2Fsome-post
for the post route, page route would look fine since it does not have a / normally
I see this is an option in path-to-regex but the option is not forwarded to vue-router. This means that if a path would have a / it would be urlencoded by path-to-regex and makes it seemingly impossible to get around (at least I have not found a way around it).
This would have additional benefits of, for instance being able to not urlencode but instead change / with _ or even encode it to base64 or something.
What does the proposed API look like?
It would just be passing the second parameter of path to regexp's compile function to the route.
{
     name: 'post',
     path: '/:permalink([0-9] [/][0-9] [/][\\S] )',
     compile: {
         encode: (value, token) => value
     },
     component: StandardArticle
},

https://github.com/pillarjs/path-to-regexp#compile-reverse-path-to-regexp
https://github.com/vuejs/vue-router/blob/dev/src/util/params.js
on line 20 is where it would need to be passed in some way, { pretty: true } is where the encoding can be changed.

The url has the slashes url encoded through right?
so the url would be http://example.com/2018%2F04%2Fsome-post
If you use the post route,and create a link to it, it will route using urlencode. This comes from the default encoding function from path-to-regex, you need to override it to prevent it through the second parameter of path-to-regex compile return function.
So to reproduce create a router with
{
     name: 'post',
     path: '/:permalink([0-9]+[/|%2f|%2F][0-9]+[/|%2f|%2F][\\S]+)',
     component: StandardArticle
},

Then for the link
<router-link tag="h4" :to="{ name: 'post', params: { permalink: permalink } }">Test</router-link>

In the component
data() {
   permalink: '2018/04/some-post'
}

I tested with the urls you provided so please, provide a repro in a jsfiddle

https://jsfiddle.net/vzeLrjo0/6/
Clicking on the link to go to the "Foo" component will show the current url the browser sees.

Ah, now I see what you mean.
By the way, you can get around that by using a string value instead of an object (it will actually be the same link from vue-router perspective): <router-link :to="'/' +permalink">{{ permalink }}</router-link>

That is interesting, I will try it (works in the jsfiddle witch is cool). I had always liked to be explicit so I never thought it would handle them differently.
I think them being handled differently is a slight concern, but there is a workaround so for me its no longer a complete wall on the project I am working on, so thank you for pointing that out, I would of likely never have thought that.
For this feature request though, I still think its fairly valid, having optional access to the encoder would be good.

Although the solution to use a path instead of an object works, when matching the regular expressions it will sometimes urlencode the string, and sometimes not before matching.

+1 on having control of the escape process
My use case is about arbitrary trees so no tricks would work except to control the escape process
The manual path is not a solution either cause I'm going to have several routes and would be not nice to use them manually

+1 This would be very handy.
Did someone manage to make it work at this time? To have control on the escape process of that route/named param?

After investing quite a lot of time in understanding encoding and providing a solution that works out of the box in different browsers in v4, I don't think it is a good idea to allow people to customize the encoding. In the specific problem exposed, one should use a path with multiple parameters and can put them together with the props option:
{
  path: '/:year(\\d{4})/:month(\\d{2})/:slug',
  props: to => ({ permalink: `${to.params.year}/${to.params.month}/${to.params.slug}` })
}

This is to be able to use the slash characters in parameters (since they need to be escaped) without being considered as separators, as by default, a param regex excludes the slash: [^/]+.
If there are other use cases that make customizing character encoding a must, they should be discussed using the RFC proccess


Make setting the default cci org also set it as default for sfdx

In order to facilitate using the VS Code integration with sfdx, I'd like the command
cci org default foo
to run the command
sfdx force:config:set<EMAIL_ADDRESS>Both commands are project specific. This would allow my scratch org to follow along in VS Code without typing an extra sfdx command every time I switch orgs.

Hi @cdcarter, I definitely second this enhancement - I made a quick patch that works for me here. I figure there is some larger refactoring that will go into 2.3 but if this suffices happy to make a pr.

@njjc added in cumulusci 2.5.0


Enh/pipeline function for scanning probe

I am sorry, but we will not compromise API consistency because of the amount of work it appears to be.
I suggest that we write a decorator that turns a function such as the one in this PR into a proper pipeline function. It will then be zero additional work to write actual pipelines.
The pipeline will be of particular importance once we have time-dependence in the code.

Ok makes sense. Can we temproarily merge this and open an issue for that ?
It is holding back a pull request in SurfaceTopography.

No, we merge when this is fixed. I can do that, but probably not today.

Sorry, I just saw your comment: Why does SurfaceTopography as a upstream project depend on ContactMechanics? This should not happen. That creates weird interdependencies.

Important detail: the dependency is only in the testing suite.
We agreed on this dependency.
I agree that a dependency of the package itself would be bad and I would avoid it.
I first used it to test the elastic energy for full contact.
I now use it to test scans with tip artefacts.

No, we merge when this is fixed. I can do that, but probably not today.

Ok we can wait a few days.

Important detail: the dependency is only in the testing suite. We agreed on this dependency. I agree that a dependency of the package itself would be bad and I would avoid it.
I first used it to test the elastic energy for full contact.
I now use it to test scans with tip artefacts.

Yes, we talked about this but in retrospective it is bad to have this even in testing. Imagine you need to restrict the surfacetopography version in contactmechanics <= some version, then the whole thing breaks.
If you need to the tip artefacts in surfacetopography, maybe the code should be there not here.

Happy to move the tip artefact simulation there.
Concerning the test of computation of the elastic energy against ContactMechanics,
it is not too bad if I do these specific tests in the ContactMechanics test suite.
I have other tests that should break if the computation of the energy gets wrong

I've created a decorator that turns a function into a pipeline function with lazy evaluation, see here: https://github.com/ContactEngineering/SurfaceTopography/pull/298

MNT is a Microsoft Composite Document File (https://en.wikipedia.org/wiki/Compound_File_Binary_Format) that contains the four entries ImagePreview, ScopedContents, ScopedResults and XmlHeader.

ImagePreview is a JPG with an overview page of measurement and properties
XmlHeader is a UTF-16 encoded XML with administrative metadata such as version information

The other two entries are binary and I presently do not know how to decode them.

I will remove all the scanning probe stuff but will keep some fixes to the API I additionally did in the branch

Thanks I will implement that. Note that we need to finish the PR in SurfaceTopography before we can merge this one

Thanks I will implement that. Note that we need to finish the PR in SurfaceTopography before we can merge this one

Did you open a PR? I don't see it.

https://github.com/ContactEngineering/SurfaceTopography/pull/216


Feature Request : Allow scripts to generate YAML instead of limiting to templates.

Current installation mechanism
The installation of a chart follows these steps:

Use values and templates to generate YAML specific for that installation.
Pass the generated YAML to kubectl.

To generate the YAML, Go templates are used. Personally, I think, a package management tool, such as Helm, should focus on the management of installation/uninstallation, dependency management, package repository management, hooks to billing systems for proprietary packages, etc. The mechanism of generating the YAML should be kept as 'wide' as possible. One option of generating the YAML would be to use a high level language such as Python, etc. Indeed, one may use Kubernetes clients in written in different languages to generate the YAML!
Proposed installation mechanism
I propose a new directory structure for packaging and a new installation flow as described below.
Directory structure
awesome/
  Chart.yaml            # A YAML file containing information about the chart
  LICENSE               # OPTIONAL: A plain text file containing the license for the chart
  README.md             # OPTIONAL: A human-readable README file
  values.yaml         # The default configuration values for this chart
  values.schema.json  # OPTIONAL: A JSON Schema for imposing a structure on the values.yaml file
  charts/               # A directory containing any charts upon which this chart depends.
  scripts/              # A directory containing scripts that will generate YAML for installation.
    shell/              #   A directory of shell scripts.
      ${OS}/            #     A directory corresponding to the platform where helm will be run.
        install.sh      #       The entry-point to installation.
        ...             #       Other supporting files for install.sh
    python/             #   A directory of Python scripts.
      ${OS}/            #     A directory corresponding to the platform where helm will be run.
        install.py      #       The entry-point to installation.
        ...             #       Other supporting files for install.py
    go/                 #   A directory of Go scripts.
      ${OS}/            #     A directory corresponding to the platform where helm will be run.
        install.go      #       The entry-point to installation.
        ...             #       Other suporting files for install.go
  generated/            # A directory containing the generated YAML files. It should be empty when packaging.

Notes on directory structure

The values.yaml will be read by an install script - see 5 below.
The installation script will live inside a directory corresponding to the language of the script in the scripts directory.
The languages could be shell (e.g. bash), Python, Go or any other language that can be supported.
Only one language directory should be present in scripts directory.
Inside the language directory, there should be a install script (e.g. install.sh in bash, install.py in python, etc.)
Inside the language directory, there may be additional folders for different OS, if any OS specific actions exist.
The install script will write the generated YAML in the generated directory.

Installation
The command to install helm install ... would not change. However, the flow will change as follows.

Launch scripts/${language}/${install_script}. For example, if the installation script language is shell script, then scripts/shell/install.sh would be launched, etc.
The launched script will write YAML, ready for installation, to the generated directory. Those YAML are passed on to helm for installation.

Keen to hear feedback!

If I'm understanding correctly, this basically sidesteps all of Helm's template logic in favour of shell scripts. This sounds like a completely different model than what users have been asking for: new alternative template engines, or new ways to tie pre-render and post-render steps into the rendering process.
How do we protect against remote shell execution? If a user fetches the chart from a remote repository, they're effectively granting the chart author remote shell execution access. In the current model, Helm is intentionally sandboxed to prevent cases where a malicious chart author would be granted shell access.
Have you looked at alternative proposals such as https://github.com/helm/helm/pull/7259 yet?

If I'm understanding correctly, this basically sidesteps all of Helm's template logic in favour of shell scripts.
'sidesteps'....I think, I will use the word 'adds on'. :)

Shell scripts, high level languages are options. I could have an API end-point that takes in a payload and returns a YAML. The option of API end-point can also handle payment related requirements too.

How do we protect against remote shell execution?
Would this be considered remote shell execution too? curl https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash

Have you looked at alternative proposals such as #7259 yet?
Browsing now.

I read through the proposal #7260 (referred to in #7259).
That proposal refers to a Helm template as an input.

Helm will then render the charts using the standard Go template language and the
specified user values. Once this is done, but before parsing the manifests into
Kubernetes objects, helm will execute the binary and pass the charts on STDIN.
It will expect a 0 exit code with valid Kubernetes manifests on STDOUT.

My request is about to generating YAML through options other than templates e.g. shell scripts, high level languages, API end-points, etc.

Well ?

@thomastaylor312 You might have some input on this?

@chainhead So I think #7260 would solve this use case if I am understanding correctly. Using post render, you could actually have 0 go templating in your chart and then add/generate additional YAML in your post-render steps to your heart's desire. However, I don't know if you can have a completely empty manifest and then generate it completely out of band.
The other option here is this sounds like an advanced use case that may be a good candidate to use the Go SDK for. You could generate your YAML by calling an API, pull back that buffer and then use it to set the Manifest in the release. Then you could get the benefits of having Helm manage your releases, but generate the YAML out of band


Update README.md

remove duplicate line

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Final additions and tweaks

Minor stuff here.

Not much change really, good to see two tests added.


Short cuts cause crash

Describe the bug
Crashes server when using regular chest / inv shortcuts
To Reproduce

Use regular chest shortcuts such as:
Shift click or Shift double click while holding item to move all of one type.

Expected behavior
The server will freeze - a single tick took greater than 60 seconds - shutting down
Device Info(please complete the following information):

OS: Linux (Debian 10)
Minecraft Version: 1.16.5
Version 1.4.0

Additional context
Works fine if you don't use shortcuts

Thats... weird. I can reproduce it though, should be able to fix. In the mean time, don't do that

Fixed in 1.4.1

Sweet! Thanks for the quick fix!


Remove dependency links

This is a deprecated feature in pip, so let's not rely upon it.

May I suggest loosening the version constraint somewhat? According to your versioning strategy, >= 0.2.0 and < 1 should be compatible.

LGTM


TINKERPOP3-850: Reduce Graph.addVertex overload ambiguity (v2)

https://issues.apache.org/jira/browse/TINKERPOP3-850
Replaces #102 after removing fix for TINKERPOP3-867

I have compiled and run all tests successfully against that version of tinkerpop3. Thumbs up from my side.
Here's the changes I made:
https://github.com/mpollmeier/gremlin-scala/compare/3.1.0-SNAPSHOT

Great, thanks @mpollmeier.
Next step, should we have a DISCUSS since this is a breaking change for implementers?

TODO: Update the "Upgrade" docs when they are merged to master.

VOTE +1.
NOTES: I don't like how many addVertex() methods we have now. I don't want our core APIs to be dumping grounds for method permutations (even with default) as I would prefer these APIs stay clean and minimalistic (and ultimately, simple for the provider to implement). However, if this is required by Scala, then we can add it. If its just a nicety for Scala we shouldn't (I leave it up to @mhfrantz to decide). As there will always be a "pretty please" down the line from some other language... We shouldn't cater if the language has a workaround (e.g. how did Gremlin-Scala work prior to this moment?).

Since it has been clarified why the addVertex(Object[] args) is needed...
Vote: +1

This is a bit unfair as I only committed the change yesterday and we hadn't discussed procedure completely yet, but this is a breaking change for Graph System Providers and therefore should have appropriate documentation in our new "release docs":
https://github.com/apache/incubator-tinkerpop/blob/master/docs/src/upgrade-release-3.1.x-incubating.asciidoc
I think that PRs should be inclusive of all documentation so that as reviewers we can examine a change in full.  I assume that makes sense to everyone.
@mhfrantz Do you mind amending this PR to include that change?  also, feel free to branch and PR from the apache repo in the future.  no need to do so from a fork since you have commit access.

@spmallette I had intended to update the docs after they had been merged, as the TODO earlier in this PR states.  I should be able to get to that today.  Please hold off on merging until then.
Regarding branching from the apache repo, I have been using the fork that my colleagues share so that our project's HipChat notifications show up.

oops - sorry @mhfrantz - didn't notice your NOTE up there. and as for the fork - that's cool too. just wanted to be clear that you were free to just do all that in Apache.

@mhfrantz -- Can you delete this PR and tell the Gremlin-Scala team our findings? (or am I missing something that we agreed to?)

Issue closed as "WON'T FIX", with explanation in the JIRA ticket.


⚠ Samsung has degraded performance

In 9c5abfc, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2512 ms

Resolved: Samsung performance has improved in ad9aa11.


Added safe stringifying for circular JSON

When passing a callback to suite.capture, the data being sent becomes circular (i.e. there is a reference to itself within the JSON).
// Works
suite.capture('plain');

// Errors out
suite.capture('plain', function (actions) {
  action.setWindowSize(1024, 768);
});

Unfortunately, this was a hard bug to track down as gemini-gui would silently exit rather than give me a stack trace =/
After adding a console.log to here, I found the error and patched it with json-stringify-safe:
https://github.com/gemini-testing/gemini/blob/6499b54110bc197f3262d26e9be0c90fec6dc94e/lib/runner.js#L72-L75
In this PR:

Added fix for circular JSON by using json-stringify-safe
Added regression test to prevent the issue from recurring

Thanks!

Published in 0.2.3


Cannot find the assembly 'Facebook, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'

I have update the FacebookClientPlugin to version 1.4.0. And now android app is building fine but iOS App build is getting fail with below message
MTOUCH : warning MT0136: Cannot find the assembly 'Facebook, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' referenced from '/Users/…./packages/Plugin.FacebookClient.1.4.0/lib/Xamarin.iOS10/Plugin.FacebookClient.dll'.
MTOUCH : error MT2001: Could not link assemblies. Reason: Error while processing references of 'xxxx.iOS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'
Done building target "_CompileToNative" in project “xxxx.iOS.csproj" -- FAILED.

Version Number of Plugin:1.4.0
Version of VS: 7.8.2
Version of Xamarin: 3.1

I´m having the same issue, have you solved it yet?

Can't reproduce this issue but if still having it please test:
https://www.nuget.org/packages/Plugin.FacebookClient/2.0.1-beta
If not fixed in this version please re-open.


docs: Fix badge link to Code of Conduct

Change Type

[ ] Feature
[x] Chore
[ ] Bug Fix

Change Level

[ ] major
[ ] minor
[x] patch

Further Information (screenshots, bug report links, etc.)
I noticed that the badge link to the Code of Conduct was broken. This PR fixes it.
Checklist

[ ] Added tests / did not decrease code coverage
[ ] Tested in supported environments (common browsers or current Node)

Duplicate of #231


Restore the old look of the fixed nav while allowing it to scroll

What "old look" here means is that the gray nav used to only occupy the height required for the nav items, and since #2749 the nav takes 100% of the height.
I personally think it would be better if we could leave the nav at 100% height and occupy 100% height in the white article side of the page.


Move generate_signed_url to standalone function in credentials.

This was very out of place as a method on Connection in storage.

Coverage remained the same at 100.0% when pulling 0d70e9c5617eaea6071316f6e5d161ff2df37da5 on dhermes:move-signed-url-to-credentials into d858ff041192657c483e24fb904aade41996bf09 on GoogleCloudPlatform:master.

I can hardly object:  this is basically the same as my #356, which was aimed at #57.

I should have trusted your "this feels out of place" instincts.
This also brings up the question: How do GAE / GCE service accounts hope to sign a URL?

Also @tseaver is your endorsement above a LGTM or are you still reviewing?

LGTM


Understanding Glassmorphism in UI Design

Be sure to visit our Resources Page for tools, resources, and example articles to go over.
NOTE: We tend to stray away or tend not to publish reviews/comparisons of commercial product offerings.
Proposed title of article
Understanding Glassmorphism in UI Design
Introduction paragraph(s):
Glassmorphism is an emerging trend in user interface design. It is a modern technique of styling web-pages while providing 3D experiences and glass effects. Web designers are using this technique to improve user experience and the attractiveness of web applications.
This article provides an understanding of this concept and explains how it has been applied in the UI industry.
Key takeaways:

What is glassmorphism?
Why is glassmorphism popular?
Key features of glassmorphism in UI design
How glassmorphism has been applied in the UI industry
The future of glassmorphism

References:
N/A.

Thank you for the topic suggestion @artmuth, however this is outside of our preferred topic areas. We lean more heavily towards programming-centric topics as opposed to design-centric topics. Please feel free to suggest an alternate topic area to explore.


Add fn for rust agent to await new session

When IML installs Lustre on a storage server it may potentially restart the server, depending on whether a different kernel version is needed.
When this occurs, a new session is established between the agent and manager. We need to ensure we wait for new session establishment in these cases to avoid sending data with an old session.

Fixed by #1357.


chore: Subsample by top 5 countries in interactive plot docs

Thank you so much for contributing to Datapane, please help us by filing out this PR template and ensure you have read the CONTRIBUTING.md.
It may take a few days to review your PR and merge it - please bear with us!
Thanks!
Prerequsites

[x] Has been tested locally
[ ] If a bugfix, have included a breaking test if possible

Proposed Changes
Subsampling the COVID dataset used in the samples by only taking the first 5 countries. Reduces the output report size by around 14 MB each.

Excellent. We can increase it if you want with the minification, though we'll want to be looking into how to host larger datasets soon anyway


Disabling MAC filter deletes the filters in wireless file. No chance to enable the filters again

Once you define MAC filters for wireless (and that may be a lot), they are stored in the file "wireless" like
...
list maclist '00:01:02:03:04:05'
list maclist '06:07:08:09:AA:AB'
list maclist 'AC:AD:AE:AF:B0:B2'
...
Once you hit the option "disable" at "MAC Address filters" those entries in wireless are deleted.
So there is no chance to get them back, once you hit "enable".
You have to edit all the entries anew.
This is not only an error but max. annoying.
BR
Ralf

I downloaded  form.js and replaced  mine.
That does not solve the error.
When I now want to enable the former mac list again, all I get is a combo box with mac adresses,
Now I still have to manually add every single one again.
That is not conveniant.
What I expect , is that I can manage a list of MAC addresses and could disable/enable the whole list with one click.
BR
Ralf

You need to update wireless.js as well.

Which one?
modules/luci-mod-status/htdocs/luci-static/resources/view/status/wireless.js
or
modules/luci-mod-network/htdocs/luci-static/resources/view/network/wireless.js  ?
BR Ralf

The latter, see commit https://github.com/openwrt/luci/commit/c534f0671d9a7d0f12d38ece20fcfb3bc19509b2 which closed this issue.

I changed file /www/luci-static/resources/view/network/wireless.js with the one you linked abovec and  rebooted the device.
Unfortunatelly that did not change the bevaviour:

I added a list of MAC adresses; then I saved them.
After that I disabled MAC Filtering, saved again.
Then I enabled MAC-Filtering again, and the list was gone.
All that is  left is a combobox where I can choose from 30 or more MAC addresses.

That's the only change from the initial behaviour, where I had an empty combobox.
But I (probably nobody) do not want to create the MAC-list from scratch, once I disabled it.
The combox with the MAC Adresses does not really help.
In this case it's more practical to do a backup from /etc/config/wireless instead of adding all those MAC addresse manually.
BR
Ralf

Maybe you didn't properly clear your browser cache, it works as expected here now. Disabling and reenabling the list (by changing from disabled to whitelist or disabled to blacklist) will restore all previous items.

The video shows exactly what I'm expecting.
Maybe I changed the wrong files?
What I did:

I replaced  /www/luci-static/resources/form.js  with the on from GIT   https://github.com/openwrt/luci/blob/f5fbecf132b6c18141896b093935fb4c035ab33d/modules/luci-base/htdocs/luci-static/resources/form.js
There is another form.js in /rom/www/luci-static/resources which seems to be identical but I cannot change it.
So currently only  /www/luci-static/resources/form.js is updated
Then I searched for wireless.js and found it on four locations
/www/luci-static/resources/view/status
/www/luci-static/resources/view/network
/rom/www/luci-static/resources/view/status
/rom/www/luci-static/resources/view/network
/overlay/upper/www/luci-static/resources/view/network
I used the file from here and replaced /www/luci-static/resources/view/network/wireless.js
/overlay/upper/www/luci-static/resources/view/network/wireless seems to be the same.
*I did not change wireless.js in  /www/luci-static/resources/view/status and  /rom/www/luci-static/resources/view/status
Maybe I made an mistake somewhere...
I am not a specialist, so help for dummies would be appreciated.

BR
Ralf

You need to force clearing your browser cache, otherwise it will continue using the old cached class files.

That means I died everything right?
I just tried this, and now it works:

Thanks very much.
BR
Ralf

I update now to OpenWrt 21.02.3.
Once I view the wireless file there is no more list of MAC addresses in there. Nevertheless LUCI shows me the MAC addresses. Are they in a different file now? Where?
BR Ralf


Implement zO

Would be great to have zO to open everything under the current fold.

I'd like to be assigned this. And also given some direction on where to start looking.

As stated in the README, this package is no longer maintained and is deprecated. We recommend that people use the vim-mode-plus package instead. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!


"AttributeError: 'PseudoInputFile' object has no attribute 'buffer'" while attempting to export to CGI.

Traceback (most recent call last):
File "C:\path-to-my-app\webapp.py", line 18, in
app.run(server='cgi')
File "C:...\Scripts\bottle.py", line 755, in run
run(self, **kwargs)
File "C:...\Scripts\bottle.py", line 3127, in run
server.run(app)
File "C:...\Scripts\bottle.py", line 2750, in run
CGIHandler().run(fixed_environ)
File "C:...\lib\wsgiref\handlers.py", line 519, in init
self, sys.stdin.buffer, sys.stdout.buffer, sys.stderr,
AttributeError: 'PseudoInputFile' object has no attribute 'buffer'`

Looks like you are trying to run this script in an IDLE shell, but IDLE does not provide a real shell. The wsgiref.CGIHandler breaks because PseudoInputFile does not provide an attribute a normal file object would.
So, this is either a bug/shortcoming of IDLE or wsgiref. We cannot fix this in bottle. Your best change is to test your CGI script outside of IDLE (or not use CGI, if that is an option. CGI is slow, old and not recommended).


Added onScaleStart and onScaleEnd VoidCallbacks

Solution for https://github.com/Mayb3Nots/zoom_pinch_overlay/issues/10

Thanks for the PR @ramtinq!

Thanks for your useful package.


Convex Hull support

Provides a more robust alternative to Trimesh shapes.
THREE.js QuickHull implementation
Also: http://www.bennolan.com/2014/07/24/physics,-hulls-and-cannon.js.html

Also, THREE.ConvexGeometry in the examples/js/geometries.
They both seem a bit fragile, however. https://github.com/mrdoob/three.js/issues/8416

 *  Num Vertices  Time(ms)
 *
 *     10           1
 *     20           3
 *     30           19
 *     40           48
 *     50           107

.... nope O(n^2) isn't going to cut it in this case, THREE.ConvexGeometry is out.

Example:
<a-entity obj-model="obj: url(...); mtl: url(...)" static-body="shape: hull"></a-entity>

Performance seems OK for static bodies, but complex objects as dynamic bodies seems very costly. Using a bounding box (or compound shape, when that's added) would definitely be preferred.


Where is the tag for 1.2.8?

Hi, I see that a version 1.2.8 is listed on npm but I cannot find the tag here. Could you push it by chance? Thanks.

That would have to be 4fc9dafeefa53ba4b81d4bca12b8ffef346bcdcb, as that's the only commit between v1.2.7 and when I started contributing towards v2.0.0 - but I'll leave it to @andrew to confirm that.

I have no idea 😂

I’d recommend using 2.0.0

I have no idea 😂

oh, heh.

I’d recommend using 2.X

Yep, but our test suite fails when upgrading from 1.2.8 to 2.0.0 (using the legacy API). It seem an invalid data to decode does not throw any error anymore and we get NaN instead. I am not sure though.

Maybe it's worth changing the title of the issue to report that bug instead?

@willdurand as I mentioned before, I don't know where to put that tag as it was a long time ago.

@andrew: I've just checked against the contents of the npm package and I'm fairly certain that the commit I'd identified above was in fact v1.2.8 - do you mind if I create that tag retroactively?

@FND sure

Done: https://github.com/andrew/base62.js/commits/v1.2.8
Hope that helps, @willdurand.


[XEN] Unable to inject GSX IRQ

Hello Team,
I am facing below IRQ issue with GSX driver.
(XEN) [   20.059538] Failed to inject GSX IRQ
(XEN) [   20.276373] common/grant_table.c:1882:d2v1 Expanding d2 grant table from 1 to 2 frames
(XEN) [   20.284888] common/grant_table.c:1882:d2v1 Expanding d2 grant table from 2 to 3 frames
(XEN) [   20.293334] common/grant_table.c:1882:d2v1 Expanding d2 grant table from 3 to 4 frames
(XEN) [   20.301751] common/grant_table.c:1882:d2v1 Expanding d2 grant table from 4 to 5 frames
(XEN) [   20.496305] gnttab_mark_dirty not implemented yet
(XEN) [   22.554993] Failed to inject GSX IRQ
(XEN) [   22.570198] Failed to inject GSX IRQ
Xen is unable to inject GSX IRQ.  I have enabled below options for GSX in configuration file,.
dt_passthrough_nodes = [
"/gsx_opp_table0",
"/gsx_opp_table1",
"/gsx_opp_table2",
"/gsx_opp_table3",
"/gsx_opp_table4",
"/gsx_opp_table5",
"/gsx_opp_table6",
"/gsx_opp_table7",
]
dt_dev = [
"/soc/gsx_pv0_domd",
"/soc/gsx_pv1_domd",
"/soc/gsx_pv2_domd",
"/soc/gsx_pv3_domd",
]
irqs = [
gsx@fd000000
151,

]
iomem = [
#gsx@fd000000
"fd000,40",
]
could you please help me on how to resolve this issue??

I have also added "pvrsrvkm.DriverMode=0" in domd bootargs

Hi @naveenc-93, are you using our default config?  Also, what machine do use?
I am asking because it should work out of the box without any changes.

@otyshchenko1, may I ask you to take a quick look? I just don't remember what is the correct configuration for GSX.

Yes, I am using the same config but machine is our custom board which is based on H3 starter kit.

Ah, I see. Well, I am not sure that problem is with DomD. Looking at your logs, you already booted up DomU, so maybe Xen can't inject IRQs there? Sadly, it is unclear into which domain it can't inject IRQs. Are you seeing those messages before domain with ID=2 created?

Yes, Even it is unclear for which domain Xen is unable to inject IRQ but I observe these messages during when a graphics application is being run in domd

I also got this dump where error says "interrupts were not received in domd"
[   12.533951] PVR_K:(Error):   522: RGXUpdateHealthStatus: LISR has not received the last 3 interrupts [5760]
[   12.534037] PVR_K:(Error):   522:  Device experienced error 15 [105]
[   12.534069] PVR_K:(Error):   522: DevicesWatchdogThread: Device status not OK!!! [499]
[   12.534107] PVR_K:  522: ------------[ PVR DBG: START (High) ]------------
[   12.534138] PVR_K:  522: OS kernel info: Linux 5.10.41-yocto-standard #1 SMP PREEMPT Wed May 10 06:26:40 UTC 2023 aarch64
[   12.534181] PVR_K:  522: DDK info: Rogue_DDK_Linux rogueddk 1.15@6052913 (release) r8a7795_linux
[   12.534218] PVR_K:  522: Time now: 12534215us
[   12.534242] PVR_K:  522: Services State: OK
[   12.534263] PVR_K:  522: Server Errors: 3
[   12.534292] PVR_K:  522: Connections Device ID:0(128) P800-V800-T800-agl-compositor, P804-V804-T804-launcher, P803-V803-T803-homescreen
[   12.534342] PVR_K:  522: ------[ Driver Info ]------
[   12.534370] PVR_K:  522: Comparison of UM/KM components: MATCHING
[   12.534398] PVR_K:  522: KM Arch: 64 Bit
[   12.534418] PVR_K:  522: UM Connected Clients: 64 Bit
[   12.534444] PVR_K:  522: UM info: 1.15 @  6052913 (release) build options: 0x80000810
[   12.534481] PVR_K:  522: KM info: 1.15 @  6052913 (release) build options: 0x00000810
[   12.534514] PVR_K:  522: Window system: nullws_drm
[   12.534546] PVR_K:  522: ------[ RGX Device ID:0 Start ]------
[   12.534575] PVR_K:  522: ------[ RGX Info ]------
[   12.534613] PVR_K:  522: Device Node (Info): 00000000c86ec4a1 (000000008c71d9bd)
[   12.534649] PVR_K:  522: RGX BVNC: <IP_ADDRESS> (rogue)
[   12.534675] PVR_K:  522: RGX Device State: Active
[   12.534699] PVR_K:  522: RGX Power State: ON
[   12.534726] PVR_K:  522: FW info: 1.15 @  6052913 (release) build options: 0x80000810
[   12.534764] PVR_K:  522: BIF0 - OK
[   12.534785] PVR_K:  522: BIF1 - OK
[   12.534806] PVR_K:  522: TEXAS_BIF - OK
[   12.534827] PVR_K:  522: TEXAS_BIF - OK
[   12.534849] PVR_K:  522: RGX Virtualisation firmware connection state: UP (Fw=active; OS=active)
[   12.534891] PVR_K:  522: RGX FW State: NOT RESPONDING - Missing interrupts (HWRState 0x00000001: HWR OK;)
[   12.534939] PVR_K:  522: RGX FW Power State: RGXFWIF_POW_IDLE (APM disabled: 0 ok, 0 denied, 0 non-idle, 0 retry, 0 other, 0 total. Latency: 100 ms)
[   12.534996] PVR_K:  522: RGX DVFS: 0 frequency changes. Current frequency: 599.997 MHz (sampled at<PHONE_NUMBER> ns). FW frequency: 600.000 MHz.
[   12.535061] PVR_K:  522: RGX FW OS 0 - State: active; Freelists: Ok; Priority: 0; MTS on;
[   12.535111] Unable to handle kernel paging request at virtual address ffff8000122b502c
[   12.535143] Mem abort info:
[   12.535158]   ESR = 0x96000021
[   12.535179]   EC = 0x25: DABT (current EL), IL = 32 bits
[   12.535204]   SET = 0, FnV = 0
[   12.535223]   EA = 0, S1PTW = 0
[   12.535241] Data abort info:
[   12.535260]   ISV = 0, ISS = 0x00000021
[   12.535281]   CM = 0, WnR = 0
[   12.535301] swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000415db000
[   12.535329] [ffff8000122b502c] pgd=00000000bffff003, p4d=00000000bffff003, pud=00000000bfffe003, pmd=000000004332e003, pte=006800004792e713
[   12.535393] Internal error: Oops: 96000021 [#1] PREEMPT SMP
[   12.535419] Modules linked in: xt_MASQUERADE iptable_filter can_raw can iptable_nat xt_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_tcpudp bridge stp llc cfg80211 rfkill pvrsrvkm(O) crct10dif_ce dw_hdmi_cec smsc95xx usbnet renesas_rpc_if rcar_can can_dev renesas_usb3 ccree authenc libdes vspm_if(O) vsp2(O) vspm(O) uio_pdrv_genirq sllin(O) mmngrbuf(O) mmngr(O) fuse ip_tables x_tables ipv6
[   12.535644] CPU: 2 PID: 522 Comm: pvr_device_wdg Tainted: G        W  O      5.10.41-yocto-standard #1
[   12.535683] Hardware name: XENVM-4.18 (DT)
[   12.535706] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--)
[   12.535832] pc : RGXDumpRGXDebugSummary+0x2a8/0xf60 [pvrsrvkm]
[   12.535918] lr : RGXDumpRGXDebugSummary+0x82c/0xf60 [pvrsrvkm]
[   12.535947] sp : ffff8000230037a0
[   12.535967] x29: ffff8000230037c0 x28:<PHONE_NUMBER>000000
[   12.535994] x27:<PHONE_NUMBER>000001 x26: ffff800009179838
[   12.536022] x25: ffff800009198d88 x24:<PHONE_NUMBER>000000
[   12.536050] x23: ffff8000122a5600 x22: ffff8000122b5000
[   12.536077] x21: ffff000008a9a800 x20:<PHONE_NUMBER>000000
[   12.536104] x19:<PHONE_NUMBER>000000 x18: ffffffffffffffff
[   12.536132] x17:<PHONE_NUMBER>0012c0 x16: 00000000deadbeef
[   12.536159] x15: ffff8000a30033e7 x14: 3020534f20574620
[   12.536186] x13: ffff8000119cb6e8 x12:<PHONE_NUMBER>00064b
[   12.536214] x11: ffff800009199088 x10: ffff8000119cb6e8
[   12.536240] x9 :<PHONE_NUMBER>000001 x8 : 00000000ffffefff
[   12.536268] x7 : ffff800011a236e8 x6 : ffff800011a236e8
[   12.536295] x5 : ffff00007fb67930 x4 :<PHONE_NUMBER>000000
[   12.536322] x3 :<PHONE_NUMBER>000000 x2 :<PHONE_NUMBER>00508a
[   12.536350] x1 :<PHONE_NUMBER>000001 x0 : ffff8000122b5004
[   12.536377] Call trace:
[   12.536453]  RGXDumpRGXDebugSummary+0x2a8/0xf60 [pvrsrvkm]
[   12.536530]  RGXDebugRequestProcess+0x690/0x124c [pvrsrvkm]
[   12.536600]  RGXDebugRequestNotify+0x38/0x44 [pvrsrvkm]
[   12.536671]  PVRSRVDebugRequest+0x28c/0x620 [pvrsrvkm]
[   12.536743]  DevicesWatchdogThread_ForEachVaCb+0x134/0x150 [pvrsrvkm]
[   12.536816]  List_PVRSRV_DEVICE_NODE_ForEach_va+0x74/0xb0 [pvrsrvkm]
[   12.536888]  DevicesWatchdogThread+0x140/0x21c [pvrsrvkm]
[   12.536960]  OSThreadRun+0x24/0x60 [pvrsrvkm]
[   12.536993]  kthread+0x158/0x160
[   12.537018]  ret_from_fork+0x10/0x30
[   12.537042] Code: 8b1b0ac0 2a1b03e1 f94006a2 52800029 (f9401418)
[   12.537074] ---[ end trace ce321bd72b372c53 ]---

I also checked "cat /proc/interrupts" to check interrupts recieved by pvrsrm module. it shows 0.

Well, this is interesting issue.
Could you please confirm that you are seeing "Added GSX ..." message domain DomD creation?

Hello @naveenc-93, in addition to what @lorc has said, could you please clarify whether the graphic DDK

Hello @naveenc-93, in addition to what @lorc has said, could you please clarify whether the graphic DDK (both pvrum and pvrkm) you use is built with the per-OSID irq counters feature? The "Failed to inject GSX IRQ" means that GSX IRQ was received, but Xen couldn't recognize the origin of that IRQ (to what domain this IRQ needs to be injected).

Hello @otyshchenkod1, We are using GSX drivers provided by Renesas.
I could see ""IRQ_PER_OS" is enabled in "gaszFeaturesNoValuesNames". Also, I see below values
#define	RGX_FEATURE_IRQ_PER_OS_POS                                  	(14U)
#define	RGX_FEATURE_IRQ_PER_OS_BIT_MASK                             	(IMG_UINT64_C(0x0000000000004000))
Is this info correct?

Just to clarify - you need a special build with virtualization feature enabled. If you have access to source code, you can use our recipes to build it. But if Renesas provided you binaries only - you need to check if they were built with the correct options.

Hello @naveenc-93,  both pvrkm and pvrum should be built with the following option.
RGX_FW_IRQ_OS_COUNTERS := 1
RGX_IRQ_HYPERV_HANDLER := 1
Could you please re-check this is the case.
Could you please clarify whether you see "Added GSX d1 (OSID 0)" message during DomD creation or not? Unfortunately
it is not clear from the discussion.
Also could you please post the whole system log from the very beginning (Xen + Dom0, DomD dmesg and journalctl)?

Hello @otyshchenko1 ,
I could see below logs from xen,
(XEN) [    0.242316] Initialized GSX IRQ
(XEN) [   11.083917] Added GSX d1 (OSID 0)
(XEN) [   22.622507] Failed to inject GSX IRQ
xen_hyp.log

Hello @naveenc-93, thanks for the log and confirmation.
Both pvrkm and pvrum should be built with the following options:
RGX_FW_IRQ_OS_COUNTERS := 1
RGX_IRQ_HYPERV_HANDLER := 1
These options should be set in the Makefile for your machine (build/linux/r8a7795_linux/Makefile).
If you don't set them in your Makefile, then yes, they are in default state (disabled).
The former is to save per-OSID IRQ counters in HW registers and the latter is to
let the hypervisor read and clear the IRQ status register.
It is also possible to look at the build options.
from your log:
[   12.534444] PVR_K:  522: UM info: 1.15 @  6052913 (release) build options: 0x80000810
[   12.534481] PVR_K:  522: KM info: 1.15 @  6052913 (release) build options: 0x00000810
from my log:
[  138.565566] PVR_K:  565: UM info: 1.15 @  6052913 (release) build options: 0x80004810
[  138.565595] PVR_K:  565: KM info: 1.15 @  6052913 (release) build options: 0x00004810
In my case the bit 14 which indicates the RGX_FW_IRQ_OS_COUNTERS usage is set, in your case is not,
which clarifies why actually Xen continuously complains "Failed to inject GSX IRQ".
Also I didn't spot the following string from your log (but my log contains it):
[  138.565895] PVR_K:  565: RGX Virtualisation type: Hypervisor-assisted with dynamic Fw heap allocation
As @lorc has already said, you would need a special build with virtualization feature enabled.

Hello @otyshchenko1,
Thank you for the detailed information. If I understood correctly, I need to prepare a new build with the above flags enabled.
I also figured out PVR number of OSes supported variable should also be set to 8 which in my case is set to 1.
If we change/add these variable values in Makefile and then prepare a new build would be suffice right.
I will update my observation after testing these changes.
Thanks and Regards,
Naveen C

Hi @naveenc-93,
@otyshchenko1 may correct me, but looks like you are right.
Also, I want to say that we provide means of automatic building of PVR UM and PVR KM:
https://github.com/xen-troops/meta-xt-rcar/tree/master/meta-xt-rcar-proprietary
which is automatically enabled  if you are calling moulin with --PREBUILT_DDK=no option.
But you will need to provide URL for your copy of DDK (see https://github.com/xen-troops/meta-xt-rcar/blob/master/meta-xt-rcar-proprietary/recipes-graphics/gles-module/gles-um-compile.bb#L8C2-L8C2)

Hello @otyshchenko1,
Renesas has provided us only sources for PVR KM and only binaries for OpenGL libraries.
Can I perform a fresh build with these options ?

Hello @naveenc-93, this is unfortunate. You need a specific PVK UM ( EGL libs, firmware, tools, etc) build.

Hello @lorc
Renesas has shared PVK UM binaries and in the kernel module, I had enabled below flags in the Makefile and built it.
RGX_FW_IRQ_OS_COUNTERS := 1
RGX_IRQ_HYPERV_HANDLER := 1
Now, I face build options mismatch error.
[ 15.025143] PVR_K: 447: (FAIL) RGXDevInitCompatCheck: Mismatch in Firmware and KM driver build options; extra options present in the KM driver: (0x4000). Please check rgx_options.h
[ 15.025472] PVR_K: 447: Connections: No Devices: No active connections
[ 15.025501] PVR_K: 447: -----[ Driver Info ]-----
[ 15.025525] PVR_K: 447: Comparison of UM/KM components: MATCHING
[ 15.025552] PVR_K: 447: KM Arch: 32 Bit
[ 15.025574] PVR_K: 447: UM info: 0.0 @ 0 (debug) build options: 0x00000000
[ 15.025614] PVR_K: 447: KM info: 0.0 @ 0 (debug) build options: 0x00000000

Hi @naveenc-93,
As you can see, there is mismatch between KM and UM:
[ 15.025143] PVR_K: 447: (FAIL) RGXDevInitCompatCheck: Mismatch in Firmware and KM driver build options; extra options present in the KM driver: (0x4000). Please check rgx_options.h

Looks like you are using files from different packages.

Hello Team,
I have received updated gfx  binaries of both user module and kernel module.
I have built the image with new gfx binaries with virtualization support and as well as above flags enabled.
After flashing the image, I am unable to detect the drm device. weston log always outputs as:
[17:42:45.471] Output repaint window is 7 ms maximum.
[17:42:45.472] Loading module '/usr/lib/libweston-10/drm-backend.so'
[17:42:45.479] initializing drm backend
[17:42:45.479] Trying logind launcher...
[17:42:45.499] logind: session control granted
[17:42:45.503] no drm device found

I have also attached full log with xen startup and domd logs.
Please help me in resolving the issue.
Thanks and Regards,
Naveen C
full_log.txt

Hello Team,
Could you please help me in resolving this issue?
I get below two error logs from two different set of gsx drivers.
pvr driver codeset 1:
[    5.064492] [drm] Initialized pvr 1.15.6052913 20170530 for fd000000.gsx on minor 1
pvr driver codeset 2:
[    4.121890] [drm] Initialized pvr 1.15.6052913 20170530 for fd000000.gsx on minor 0
pvr driver codeset 1 works fine and outputs HMI on hdmi display but not driver codeset 2.
configuration everything looks same and the only difference observed is "minor" value.
What could be the problem? does it impact ?
Thanks and Regards,
Naveen C

Hello, it is not entirely clear what is the difference in both set of gfx drivers itself (codeset 1 and codeset 2)?
Could you please clarify? And please provide full system logs for both cases.
The "minor" value shows DRM minor number for device nodes in /dev. The pvr is also acts the DRM device,
but it also adds a render node.
So the there are two DRM devices in the system, first is rcar-du for feb00000.display, the second is pvr
for fd000000.gsx.
For example, logs from working environment:
[    1.211252] [drm] Initialized rcar-du 1.0.0 20130110 for feb00000.display on minor 0
[    1.211286] [drm] Device feb00000.display probed
[    1.272942] rcar-du feb00000.display: [drm] fb0: rcar-dudrmfb frame buffer device
...
[    8.100033] [drm] Initialized pvr 1.15.6052913 20170530 for fd000000.gsx on minor 1
And the corresponding nodes in /dev:
root@salvator-x-domd:~# ls -l /dev/dri/
total 0
drwxr-xr-x 2 root root        100 Nov 28 20:39 by-path
crw-rw---- 1 root video  226,   0 Nov 28 20:39 card0
crw-rw---- 1 root video  226,   1 Nov 28 20:39 card1
crw-rw-rw- 1 root render 226, 128 Nov 28 20:39 renderD128
root@salvator-x-domd:~# ls -l /dev/dri/by-path/platform-feb00000.display-card
lrwxrwxrwx 1 root root 8 Nov 28 20:39 /dev/dri/by-path/platform-feb00000.display-card -> ../card0
root@salvator-x-domd:~# ls -l /dev/dri/by-path/platform-fd000000.gsx-card
lrwxrwxrwx 1 root root 8 Nov 28 20:39 /dev/dri/by-path/platform-fd000000.gsx-card -> ../card1
root@salvator-x-domd:~# ls -l /dev/dri/by-path/platform-fd000000.gsx-render
lrwxrwxrwx 1 root root 13 Nov 28 20:39 /dev/dri/by-path/platform-fd000000.gsx-render -> ../renderD128
The log from codeset 1 (... on minor 1) is correct, while log from codeset 0 (... on minor 0) suggests that
something went wrong and rcar-du (main DRM) didn't initialized (yet?).

Hello Oleksandr,
Thank you for your reply.
Both codesets are built and based on Renesas Yocto v5.9.0 BSP.
codeset 1: These are the gfx km and um binaries built without these two flags enabled.
RGX_FW_IRQ_OS_COUNTERS := 1
RGX_IRQ_HYPERV_HANDLER := 1
Codeset 2: These are the gfx km and um binaries build with above flags enabled.
Please find the system logs of both scenarios.
log_codeset1.log
log_codeset2.log

Hello Oleksandr,
Thank you for your reply. Both codesets are built and based on Renesas Yocto v5.9.0 BSP. codeset 1: These are the gfx km and um binaries built without these two flags enabled. RGX_FW_IRQ_OS_COUNTERS := 1 RGX_IRQ_HYPERV_HANDLER := 1 Codeset 2: These are the gfx km and um binaries build with above flags enabled.
Please find the system logs of both scenarios. log_codeset1.log log_codeset2.log
could you please help us in identifying why codeset2 binaries are initializing on minor 0 and not on minor1? I am using the same xentroops recipes for both the scenarios.

Hello, could you please the full system logs for both codesets. Saying full I mean the log starting from Xen including dom0 and domd logs (also journal output from the domd). Looks like rcar-du drm is not initialized in codeset2 scenario somehow.

Hello Oleksandr,
Unfortunately, I couldn't get the full system log from codeset1 (working scenario) case.
But, I have attached the full system log from codeset2 (non working) case.
Please check and help us why drm driver is getting failed
log_codeset2_nw_dec1_23.log

Hello Oleksandr,
Did you find any issue in the above log? Could you please help ?


Update 'UserGuide' : Add more details to user guide

Codecov Report

Merging #257 (fa3c7a4) into master (f4987ef) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #257   +/-   ##
=========================================
  Coverage     57.59%   57.59%
  Complexity      832      832
=========================================
  Files           169      169
  Lines          3139     3139
  Branches        314      314
=========================================
  Hits           1808     1808
  Misses         1206     1206
  Partials        125      125

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f4987ef...fa3c7a4. Read the comment docs.


the pagination have br (brick line)  how to disable it?

https://i.imgur.com/JQSKU4W.png?1

There's no actual  tag. It's an  tag. Target it and modify with css.