Do you have a Radeon/ATI Graphics card? -ERROR

################################################################
Do you have a Radeon/ATI Graphics card?
################################################################
y/n: Y
jq: error (at :5): Cannot iterate over null (null)
jq: error (at :5): Cannot iterate over null (null)
[06/05/24] [-] ERROR: RadeonSensor release URL not found, is GitHub rate-limiting you?

This is a limitation of GitHub's API. I've been trying to work going around it by HTML Scraping but its taking a really long while, plus exams and stuff. Turn on a VPN or try again later.


docker compose

We discussed the docker update going from docker-compose to docker compose.
I do not remember our conclusions.
I observe on my side: (in scripts/build) if I use docker-compose it does not work at all, I have to use docker compose. Is it also the same for others?

Same for scripts/down and scripts/up

In my memory

docker compose replaces  docker-compose.
we were able to make it running with docker compose on your local copy.

If it runs on your side, also for scripts/down and scripts/up, please commit and push directly to main.

Done


Fix JSDoc Function type

Before:
@param {function} next

After:
@param {Function} next

Hello, and thank you for your pull request. As function refers to typeof result and Function refers to the class name, they are both interchangeable within JavaScript. Unless there is some specific issue the casing solves, this seems like a style-only issue, which is not something we generally accept, as it creates a lot of churn without meaningful benefits; only slowing down the process of merging between on going branches, PR conflicts, and more.
If there is something demonstrable this resolves, we can always re-open.


Delete User from store

Here's my first stab at deleting user from the store. This is implemented as part of https://github.com/solid/node-solid-server/issues/177
The test doesn't pass, and I'm not sure the test is OK, but I pushing makes it easier to discuss.

@megoth ahhh no no, sorry bout that! I dont recommend ‘del’ over ‘remove’, please feel free to use the latter. I just didn’t remember whether ‘remove’ was implemented! :)

Actually, it fails if I go with remove:
  1) UserStore (integration)
       deleteUser()
         deletes a previously saved user:
     TypeError: this.backend.remove is not a function
      at Promise.resolve.then (src/user-store.js:91:241)

  2) UserStore
       deleteUser
         should call backend.del with normalized user id:
     TypeError: [Function: del] is not a spy or a call to a spy!
      at assertCanWorkWith (node_modules/sinon-chai/lib/sinon-chai.js:53:19)
      at Proxy.<anonymous> (node_modules/sinon-chai/lib/sinon-chai.js:98:13)
      at Proxy.methodWrapper (node_modules/chai/lib/chai/utils/addMethod.js:57:25)
      at Proxy.<anonymous> (node_modules/dirty-chai/lib/dirty-chai.js:184:23)
      at Proxy.overwritingMethodWrapper (node_modules/chai/lib/chai/utils/overwriteMethod.js:78:33)
      at doAsserterAsyncAndAddThen (node_modules/chai-as-promised/lib/chai-as-promised.js:289:22)
      at Proxy.<anonymous> (node_modules/chai-as-promised/lib/chai-as-promised.js:255:20)
      at Proxy.overwritingMethodWrapper (node_modules/chai/lib/chai/utils/overwriteMethod.js:78:33)
      at store.deleteUser.then (test/unit/user-store-test.js:229:60)

So, I suppose we'll retain del?

Let us release a new patch version right after this PR is merged, as @kidehen needs it urgently.

Looks great, @kjetilk, 👍 from me!


Grid Spacing on Horizintal / X Date Axis

Hi there, thank you for the great tool :)
Using your lib for my corona tracker: https://github.com/SeidChr/COVID-19-Report-Data-Pipeline/wiki/The-Plot
Trying to set a grid spacing on the X axis to 7 days, so one can easily count the weeks, but whatever i put in the plt.Grid(xSpacing: XXX) command seems to have not effect at all.
Is there some way to achieve this?

I created a cookbook example to test this out and track progress toward fixing this issue. You're correct, plt.Grid(xSpacing: 1) is ignored when plt.Ticks(dateTimeX: true) is used.
I'll leave this open to track my progress toward fixing this issue.
In the mean time, you could define tick positions manually like this:
http://swharden.com/scottplot/cookbooks/4.0.20/#Customize_Ticks_Positions
It would also give you an opportunity to format the labels as you like.

I remembered why this is so difficult: If a user wanted to define horizontal tick spacing as 1 month, how would they do it? They can't define a certain number of days (how DateTime.ToOATime() works) because different months have different names. Working with DateTimes is very challenging...
Still working on a fix. It will probably require the user define a DateTime unit of magnitude, and the tick spacing (multiples of that magnitude) like this:
plt.Ticks(dateTimeX: true, dateTimeUnit: Config.DateTimeUnit.months, dateTimeSpacing: 1);

A high DateTime density highlights the need for #160, but fixed-unit DateTime grid spacing seems to be working now.
https://github.com/swharden/ScottPlot/blob/749c4b8ddf358fdee797ff8d884fcb0781bfdc8d/tests/Ticks/TickGeneration.cs#L70

Cool, and interface looks good.
Can't wait for the release 😊

Now that #300 is completed I think this issue is solved.
pltTest.Ticks(dateTimeX: true, xTickRotation: 45);
pltTest.Layout(xScaleHeight: 60);

Hi, what do you think, when could you make a release?

Hi, what do you think, when could you make a release?

Source code is ready to use now
https://github.com/swharden/ScottPlot/archive/master.zip
I'll fix a few more things then upload a new NuGet package tonight

Hi, what do you think, when could you make a release?

Source code is ready to use now

Inspired by this comment I added a new section to the readme:
https://github.com/swharden/ScottPlot#build-from-source
I'll post a nuget package in a few more minutes though


Revamp administration panel

Switch to ModelAdmin classes
Use a single parent class for all StripeObject models
Switch to StackedInlines instead of TabularInlines
Set more readonly_fields, raw_id_fields etc.

Closes #385

Sorry for the big commit but once I started, it was hard to leave it in a half-baked state.
There's a lot more to do in the admin, I'll follow up in a separate issue.

Huge thumbs up from me with regards to improving the administration interface.
I had also noticed that objects within the interface aren't reverse-chronologically ordered in places where they really should be (e.g. events), so we should probably either add ordering to the admin classes or add them as default ordering into the models themselves, where it makes sense to do so.
I contributed the original implementation for reprocessing the webhook events, but to be honest having used it over time there are two improvements I'd like to make soon to it:

Process the events in chronological order (the order that they arrived from Stripe).
Process the events through the callback rather than calling event.process directly.

I'm just going to leave this here :) https://github.com/kavdev/dj-stripe/pull/402

I'll have to take a look at both when I have some more time this weekend, but it'll probably come down to who can sell their PR the best lol

Heh, I didn't notice the PR but it looks like we took essentially the same approach.
I'll change mine to do some of the same fieldset stuff that #402 does. I'm -1 on making fields blank and migrating all that stuff though, I think that needs to be addressed separately, as per #452.

Agreed.

Updated with a couple more fixes and fieldset usage inspired from the other PR. I'm good landing this for now, the rest of the work is out of scope.

More little fixups. validated_message present in Event.search_fields for some reason even though it doesn't exist (yay duck typing). Now preventing adding Event objects because that never makes sense.

Imports fixed


Issue with build site: latest CU check is wrong for CU13 of 2017

Please see the following for details: https://twitter.com/_randolph_west/status/1075889399609475072

thanks niph!


Cannot DL/Update Light Novel List and Chapters

My reader cannot download updates. When I update a certain novel, it'll have an an error and I've tried to reinstall the reader, as of now, I cannot get the list of novels due to the same error

Same here get SSL error

identical with #232
use that one :smile:


Can't go-publish private dependency on Go 1.13

I'm trying to go-publish one of my dependencies to artifactory:
jfrog rt go-publish --self=false --deps=go.example.org/example:v1.0.3 go-local

This fails on the go mod graph step:
[Info] Running 'go mod graph' in /home/perj/example
verifying<EMAIL_ADDRESS><EMAIL_ADDRESS>reading<EMAIL_ADDRESS>410 Gone

This surprised me because this checksum is already in my go.sum file and go mod graph should pick it up from there rather than calling to sum.golang.org. Indeed, running go mod graph directly is not an issue.
So I checked with strace since I like to do that. Turns out jfrog is removing my go.sum just before it calls go mod graph:
[pid  5704] unlinkat(AT_FDCWD, "/home/perj/example/go.sum", 0) = 0
[pid  5704] write(2, "[Info] Running 'go mod graph' in /home/perj/example\n", 55[Info] Running 'go mod graph' in /home/perj/example

Since there's no go.sum present go falls back to the checksum database server.
I don't particulary like that, I think the local go.sum should be used if possible. I assume the jfrog cli has a good reason for removing it, perhaps related to publishing self. But if so it should be possible to still have it around when other go commands is run.
Obviously I can work around this by setting GONOSUMDB, but I'd prefer not to since checksums are a good idea.
jfrog version 1.29.1

@perj,
I created the above PR which should fix this issue.

@perj,
The latest release includes this fix.
Please let us know if the issue is resolved for you.

It works fine. Thanks a lot.

Great. Thanks @perj.


update(kubernetes): Deployment files

Updating deployment files (automatically generated by helm template). Made using the update-falco-k8s-manifests ProwJob. Do not edit this PR.\n\n/kind update\n\n/area manifests

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: poiana
To complete the pull request process, please assign zuc after the PR has been reviewed.
You can assign the PR to them by writing /assign @zuc in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: maxgio92, poiana
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [maxgio92]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Create gh-pages branch via GitHub

GH pages

What is this PR

This was a mistake. Please ignore it.
Sorry!
On Thu, Apr 7, 2016 at 9:49 AM Andre Christoga<EMAIL_ADDRESS>wrote:

What is this PR
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/gabrielecirulli/2048/pull/402#issuecomment-206913288


FoundationEssentials: correct an off-by-one error on Windows

The returned value in the success case does not account for the terminating nul character, resulting in the value being 1 less than the allocation required. This was causing a spurious failure and thus unable to compute the location of the process.

@swift-ci please test


Initial work

@koivunej
Few days ago, to learn Sandstorm and rediscover TiddlyWiki, I began a basic implementation of TiddlyWiki5 as a Sandstorm app. On TiddlyWiki GoogleGroup, @Jermolene told me that you have already started this work. It was discussed in this thread on GitHub :
https://github.com/Jermolene/TiddlyWiki5/issues/2487
Have you made any progress toward packaging TW5 ? We could compare and merge our codes.

Yeah I might have found something more interesting while waiting for my sandstorm patch to get to stable :) I have since forgotten to periodically check for this but if your version now works on latest vagrant-spk and stable sandstorm it'd seem like my patch is in the stable already.

We could compare and merge our codes.

Looking at your setup.sh which installs npm and tiddlywiki it's exactly the same solution as I had. You've gone ways beyond mine solution with app-graphics :)
The more general issues I was thinking about after I managed to get my simple PR into sandstorm was (using blockquotes for the "issues"):

If I publish the sandstorm/tiddlywiki app into sandstorm marketplace, will I be locked in as a maintainer or is there a support for transferring ownership to the team (or it's buildbot or similar) later on?

I couldn't find an answer for this. I am not too familiar with gpg or how it's used in Sandstorm marketplace so I couldn't answer this myself.

What would be the best way to integrate sandstorm marketplace app with tiddlywiki development?

I'm most likely thinking too far ahead, but seeing what has happened to for example Ghost on Sandstorm marketplace (last I checked, it had fallen way behind in update schedule).
Even with the above issues open, I'd say it's better to publish something to the marketplace and work on any issues that come up later. I'll try to test this repo of yours later today and I'll comment back on this issue with the results.

Hi Joonas
I have benefited from your patch without knowing ;) In fact, I was surprised that it works (apparently almost without too many bugs) as easily.
I agree with you, we need to maintain the application synced with the development of TW5. I don't feel very qualified to do that. My technical level is quite limited, the quality of my english is poor and I'm not familiar with gpg. However we could join our efforts.
Should be discussed with @Jermolene. The solution may lie in the proposal of Tony late last year on the Google Group TiddlyWiki:

After TiddlyWiki is packaged as an app, I think Jeremy or another TW representative developer can sign off as the upstream author as Sandstorm is open to adding additional licenses like BSD3

https://groups.google.com/d/msg/tiddlywiki/JArRJpuYWkI/SUkqBM2VBAAJ
I also agree with you, it's better to attempt publish (after tests) our app to the marketplace and work together on any issues that come up later.
regards
Thierry

Just tested the package yielding one PR and a possible issue with chromium and the svg icons.
Tested:

create, update tiddler
create, delete tiddler

No problems, all HTTP traffic seem'd to work nicely. The package is currently at least as functional as mine was once I got the patch submitted.

Like in comment for issue #2 I noted:

Sharing the grain worked, we can scratch that off as tested as well. Again I created two tiddlers, removed the first and updated the other.

To recap the testing:

[x] create tiddler
[x] update tiddler
[x] delete tiddler
[x] sharing a grain via invite (create/update/delete)

Regarding your previous comment and the Google groups discussion I do not really understand what is the issue with BSD3 or why it was brought up in:

After TiddlyWiki is packaged as an app, I think Jeremy or another TW representative developer can sign off as the upstream author as Sandstorm is open to adding additional licenses like BSD3

I can't really see it as a blocker either way?

I agree with you, we need to maintain the application synced with the development of TW5. I don't feel very qualified to do that. My technical level is quite limited, the quality of my english is poor and I'm not familiar with gpg.

Well the same goes for me with gpg. Of course to start out the syncing could be manual.

However we could join our efforts.

I'd like to help out as much as I can. Getting and keeping tiddlywiki in sandstorm appstore is something I have wanted for some time now :)
I'd like to suggest you to revive that thread you found on google groups and present this work of yours with the problems we see (gpg for one at least). Perhaps there's someone with gpg confidence already in the team/groups who could easily take on the task of publishing or guiding us? If not, I think I might be able to understand the publishing process but wouldn't keep that as a first option :)

I have copied the all sentence, I don't think the choice BSD3 is imperative. There are no reasons. Before read this proposal, I have chosen Apache3 which seems is the Sandstorm dev's choice. Ok, I will send a message on TW5 Group.


Adding a plugin for Sentinel Entities across MITRE tactics

@shivpatel-ms and @cbelwal - May I request your feedback on this and help with the PR approval.

@samikroy PR is undergoing approval process and checks once certified we wil advise

@samikroy Several adjustments are required, specifically pertaining to the clarification of the plugin's purpose. The current description suggests its alignment with Sentinel Cost capabilities, which might create confusion. It's essential to provide an accurate depiction, emphasizing that the plugin is designed to retrieve information on Mitre, rather than being directly associated with Sentinel Cost functionalities. This clarification will enhance understanding and ensure accurate expectations among users.
Description: Skills summarizes Entities from the alerts from Sentinel workspace. #Can you lookup what my Sentinel costs are for the past 7 days? #Can you provide a detailed summary of my total Sentinel costs for the past 90 days? Be sure to explain what each table is used for within Sentinel and the security value it provides. Also total up all the costs to give me an average monthly cost. Also be sure to give any cost saving recommendations based on my data ingestion.

Thank you for sharing this @KwachSean .
Please have a review, it is updated now.

Thanks for the changes and Readme additions
please note after extensively testing the plugin is failing to provide a response

Please review the query


Failure Count Incorrect observation

I’ve seen a mismatch twice now ... recheck for log with all 12 parts.
Summary of J1939-84 Tool Execution
J1939-84 Tool version 3.0.7 - 2021/04/12 08:26
Generated: 2021/04/23 12:16:23.1555
Log File Name: C:\CdriveSave\new j1939-84\v307 old ISB Link2 c.j1939-84
TEST SUMMARY REPORT
OUTCOME:
Failures:    32             // Search in word Finds FAIL: 34 times
Warnings:    25
Information: 3
Incomplete:  0
Timing:      7
Passes:      34
User Data Entry:
Engine Model Emissions Year: 2015
Number of Emissions ECUs Expected: 1
Number of CAL IDs Expected: 5
Fuel Type: Diesel vehicle
Ignition Type: Compression
Number of Trips for Fault B Implant: 1

The discrepancy between the counts is a result of duplicate outcomes being reported:
12:11:58.3765 Sending DM7 for DM30 to Engine #1 (0) for SPN 157
12:11:58.3802 18E300F9 [8] F7 9D 00 1F FF FF FF FF (TX)
12:11:58.3876 18A4F900 [48] F7 9D 00 10 82 01 00 FB FF FF FF FF F7 9D 00 12 82 01 00 FB FF FF FF FF F7 9D 00 07 82 01 86 10 BA 13 00 00 F7 9D 00 07 82 01 86 10 6C DC 86 0B
DM30 from 0: [
  SPN 157 FMI 7 (SLOT 386) Result: Test Passed. Min: -40,000, Value: 2,300, Max: 10,500 kPa
  SPN 157 FMI 7 (SLOT 386) Result: Test Passed. Min: -10,500, Value: 2,300, Max: 524,280 kPa
  SPN 157 FMI 16 (SLOT 386) Result: Test Not Complete.
  SPN 157 FMI 18 (SLOT 386) Result: Test Not Complete.
]
FAIL: <IP_ADDRESS>.a (A7.1.b) - Test result for SPN 157 FMI 7 from Engine #1 (0) does not report the test result/min test limit/max test limit initialized properly
FAIL: <IP_ADDRESS>.a (A7.1.b) - Test result for SPN 157 FMI 7 from Engine #1 (0) does not report the test result/min test limit/max test limit initialized properly
WARN: <IP_ADDRESS>.a (A7.2.b) - Engine #1 (0) returned duplicate test results for SPN 157 FMI 7

12:11:58.6732 Sending DM7 for DM30 to Engine #1 (0) for SPN 3227
12:11:58.6764 18E300F9 [8] F7 9B 0C 1F FF FF FF FF (TX)
12:11:58.6867 18A4F900 [24] F7 9B 0C 14 2D 00 00 FB FF FF FF FF F7 9B 0C 15 2D 00 00 FB FF FF FF FF
DM30 from 0: [
  SPN 3227 FMI 20 (SLOT 45) Result: Test Not Complete.
  SPN 3227 FMI 21 (SLOT 45) Result: Test Not Complete.
]
FAIL: <IP_ADDRESS>.a (A7.1.c) - #45 SLOT identifier for SPN 3227 from Engine #1 (0) is invalid
FAIL: <IP_ADDRESS>.a (A7.1.c) - #45 SLOT identifier for SPN 3227 from Engine #1 (0) is invalid

But when the total count is reported, the duplicate are removed.
I'll update the logic to not remove the duplicates.  Additionally in 6.1.12, I'll add the FMI to the message.


Documentation doesen't work

the documentation page says 401 Unauthorized

you could try my fork, https://github.com/dopry/pecans I'm also on the look out for additional maintainers.


Lucas/8685 rework file upload

Description

Uploading a static folder now uses Tika preprocessing for the text -> more file types supported.
-> I'm not keeping the file for now because handling the file name is tricky, and a refactoring is on its way to make it cleaner.

Risk

Could potentially break static file uploading

Deploy Plan
Simply deploy front

Can we remove pdfjs from the client? 😬

Not yet because I also need to modify the 'MultipleDocumentsUpload' modal (which is still using it), doing it as my immediate next step


Profile Recorder: Add bpf_d_path implementation and hook mkdir, mknod, unlink.

What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds a custom bpf_d_path implementation that can be used in eBPF hooks that are not allowlisted to actually use bpf_d_path. We then use this to hook mkdir, mknod, and unlink to create more comprehensive AppArmor profiles.
Which issue(s) this PR fixes:
None
Does this PR have test?
Yes
Special notes for your reviewer:
supersedes #2608
Does this PR introduce a user-facing change?
Profile recorder: Hook `mkdir`, `mknod`, and `unlink` for better AppArmor profiles

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 41.38%. Comparing base (11d77f4) to head (85ae693).
Report is 539 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2611      +/-   ##
==========================================
- Coverage   45.50%   41.38%   -4.12%
==========================================
  Files          79      109      +30
  Lines        7782    18239   +10457
==========================================
+ Hits         3541     7549    +4008
- Misses       4099    10191    +6092
- Partials      142      499     +357

It seems that the entire overlay filesystem is added to the profile https://github.com/kubernetes-sigs/security-profiles-operator/actions/runs/12261338471/job/34208338061?pr=2611#step:8:170.
We need to filter out all these file permissions since is not required in the apaprmor profile.

I think we need to filter out the bootstraping and init phases of the container.
As far as I know the nsenter (https://github.com/opencontainers/runc/tree/main/libcontainer/nsenter) gets executed before runc init which executes itself and then starts the container init process. I believe that we should not record the resources before container init process.
I am think maybe is possible to filter out all resource associated with runc command. There is already this filter for syscalls https://github.com/kubernetes-sigs/security-profiles-operator/blob/3cb35b9bc6c75a8452b5fbdc0c2fe8147040040d/internal/pkg/daemon/bpfrecorder/bpf/recorder.bpf.c#L124.


Add intermediate temporary folder

Temporary files should be created in a temporary folder whose name contains the pid of the process to avoid collisions when many kernels are running.

This has been implemented in last release.


VMAlertManager StatefulSet was deleted when k8s control planes down

Hello.
I experienced a strange behavior of the VictoriaMetrics operator.
Please let me know if you know anything about it.
Environment

Kubernetes v1.19.7
VictoriaMetrics operator v0.7.4

An issue I experienced

I rebooted the machines which k8s control planes (kube-apiserver etc.) run on.
Then a StatefulSet generated by a VMAlertmanager was deleted and the MV operator re-created it.

Other info
I checked the source of the VM operator, but I cannot find any logic to remove the StatefulSet.
And I don't see any setting errors.
Log
{"level":"info","ts":1613614128.1669858,"logger":"controllers.VMAlertmanager","msg":"Reconciling","vmalertmanager":"monitoring/vmalertmanager"}
{"level":"info","ts":1613614128.1908672,"logger":"factory","msg":"Creating a new sts","reconcile.VMAlertManager.sts":"vmalertmanager","ns":"monitoring","sts.Namespace":"monitoring","sts.Name":"vmalertmanager-vmalertmanager"}
{"level":"info","ts":1613614128.1990695,"logger":"factory","msg":"new sts was created for alertmanager","reconcile.VMAlertManager.sts":"vmalertmanager","ns":"monitoring"}
{"level":"info","ts":1613614128.1990888,"logger":"factory","msg":"updating vmalertmanager sts"}

vmoperator.log

Hello, thanks for reporting, seems like its the same problem with https://github.com/VictoriaMetrics/operator/issues/159
Will investigate and fix it.


feat: Add new scanning pipeline yaml

What type of PR is this?
feat: adding empty pipeline yaml so that I can start testing

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 75.969%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2627

Relevant Lines:
3458

💛  - Coveralls


Missing blazor WebAssembly tooling instructions at link

Debug instructions here where it says:

For information on installing Visual Studio Code for Blazor app development, see Tooling for ASP.NET Core Blazor.

brings you to this page, which, for mac, only says Install Visual Studio for Mac, and nothing about vs code setup

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fa3e99ba-cbe1-e8a1-6628-9b6eb39710a4
Version Independent ID: dd777362-b92d-cac6-2343-a7aaf31d0bdf
Content: Tooling for ASP.NET Core Blazor
Content Source: aspnetcore/blazor/tooling.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @rollandjb ... Management recently decided to recommend that users on Mac use VS for Mac and users on Linux to use VS Code. Follow the instructions on the Linux tab to get VS Code.
I'll fix the line in the Debug WebAssembly topic to point directly to the VS Code install page. Thanks for calling it out.


Move Cross DB Ownership Chaining into AllInstance Check

A New PR
THANK YOU - We love to get PR's and really appreciate your time and help to improve this module
Accepting a PR
Before we accept the PR - please confirm that you have run the tests locally to avoid our automated build and release process failing. You can see how to do that in our wiki
https://github.com/sqlcollaborative/dbachecks/wiki
Please confirm you have 0 failing Pester Tests
[X] There are 0 failing Pester tests
Changes this PR brings
Moving the Cross DB Ownership Chaining check into the AllInstance check to help speed up checks.
Please add below the changes that this PR covers. It doesnt need an essay just the bullet points :-)

Ok, I think I finally figured out how to do a merge.

All we need is to fix the difference between the expected message and the actual message
'Expected 0, because We expected the Cross DB Ownership Chaining to be disabled, but got 1.' to be thrown, but the message was
'Expected 0, because We expect Cross Db Ownership Chaining to be disabled, but got 1.

Closes #647


Create an Institutions Model

An "institution" model should be added to track the holding institution of a source. This will necessitate moving the "siglum" out of the source title into its own model.
This means also adding a "holding institution" field to a source.
The institution model will be based on (but not exactly) the DIAMM 'Archive" model: https://github.com/diamm/diamm/blob/main/diamm/models/data/archive.py
This will also include adding an "institution identifiers" table with several options for indicating the presence of that institution in other authorities -- DIAMM and RISM, in particular, but also probably wikidata and VIAF.

This relates to the series of issues you've created, @ahankinson, but rather than create a meta-issue or discussion, I think it's ok to just discuss this here.
Ok, so here's what I understand to be the current state of affairs and some of the problems: title (current city + current archive + shelfmark), a siglum (institution siglum + shelfmark), and a pointer to the RismSiglum model (intended to be the "RISM" -- ie. institutional -- siglum). The "RISM" sigla (quotes intentional) used in both the source's siglum and RismSiglum are not always accurate. The siglum and RismSiglum fields can be modified independently, as can the title. It's kinda a mess. There's currently no linkage between sources in CantusDB and other catalogs, etc (e.g. RISM, the institution's own record, etc.)
If I'm understanding this set of issues (1505 - 1509), the goal is to standardize and enhance source identification in the following ways:

get rid of the RismSiglum table and associated fields -- they are not accurate (and also, frankly, not really used)
create an Institution model that contains information (name, siglum, city) on the institutions that hold our sources
create an InstitutionIdentifier model that contains various ID's for the institutions in Institution. For example, for the there might be multiple records in Instititution Identifier model that point to the Bodleian (for example, both BNF cb11930727f and RISM institutions/30001627
create a SourceIdentifier model that does basically the same thing as InstitutionIdentifier but at the source-level.

Questions

Is Institution.siglum a RISM siglum or a CantusDB siglum?
Is shelfmark a SourceIdenfier? Or maybe we still store that directly on the source itself?

There is a terminology issue here that’s been known since the migration but hasn’t yet been addressed. See: https://github.com/DDMAL/CantusDB/issues/621
Basically, the word “siglum” can mean “shelfmark” in some musicological circles, but this creates confusion when talking about “RISM sigla”.
Institution.siglum is a RISM siglum: GB-Ob, D-Mbs, etc.
In an ideal world the Source “siglum” column would be renamed “shelfmark” when the institution component of that is removed and ladder in through its relationship to a holding institution. That’s how it is in DIAMM. But I didn’t want to tackle that just yet, since that’s more a project terminology question, and there’s no technical reason to change it.
Source Identifiers are like institution identifiers, where multiple places may publish a page on the source: wikidata, bnf, RISM, etc. It will operate exactly like the institution identifiers.

Institution.siglum is a RISM siglum: GB-Ob, D-Mbs, etc.

So, in cases where a source is held by an "institution" without a RISM siglum...I guess this is a place where the current source.siglum would hold some kind of identifier to a source's holding location, but that source would not point to an Institution.

That was what we were trying to figure out in the email. I think what we landed on was that sources not held by institutions with a RISM siglum would be “held” by a Cantus institution with its own RISM siglum — CDN-WAcantus or something like that. All sources should have a holding institution, and that should be the only place institution sigla are catalogued.
What the shelfmark is for such sources, however, is still TBD. It could include a geographic indicator, but I have suggested that this isn’t ideal for privacy reasons. That’s a problem for future us at the moment though.

That was what we were trying to figure out in the email.

And, just realized there's been a whole thread about this going on in an email that I never use :( Ok, reading that now and setting up forwarding lol)

That was what we were trying to figure out in the email.

And, just realized there's been a whole thread about this going on in an email that I never use :( Ok, reading that now and setting up forwarding lol)

the  double institutional email problems strike again!


[UIManager] Only handle accessibility notifications from the correct RCTAccessibilityManager

When you reload and create a new bridge, one of the things that happens during setup is that the RCTAccessibilityManager fires a notification. The old bridge would receive this notification from the new bridge's RCTAccessibilityManager, which we don't want, especially because the two are running on different shadow queues.
I believe this led to a gnarly crash in NSConcreteTextStorage because RCTMeasure in RCTShadowText.m was getting called for the old RCTText (getting destroyed) from a notification fired from the new shadow queue. The fix is for the UIManager to handle notifications only from its bridge's RCTAccessibilityManager. See #2001 for the kinds of crashes we were seeing.
Test Plan: Loaded a complex app. Crashes on reload seem to have gone away but this was non-deterministic so there may still be other issues.

Fix makes sense. Test failures seem to be unrelated.
@facebook-github-bot shipit

We see this crash in the Playground app a lot as well - couldn't figure it out. Nice one!


eliminating the need for certificates with the grpc / automating validation of certificates using a node's peer to peer pubkey

lnd creates a certificate for the grpc. We also have a node pubkey that is used for securing peer to peer transport. At a high level, this seems a bit redundant to me to have two types of public keys for one node.
There are a few things that can be done to get the grpc client to work.

With an unsigned certificate, we can copy over the public certificate from the lnd node to the client and the client can validate that way. This method I don't think works if using  macaroons for things like LSATS and subscription type services. Also, clients must be updated annually because the self signed certificate is only good for one year.
We can get a certificate signed by a CA. This is problematic because it requires the PKI, which requires us to trust every issuer that is trusted by the OS. This has never been a good design in my opinion, but it was 'the best' that could be done before a blockchain was invented. Lightning terminal has a method to use Let's Encrypt (https://github.com/lightninglabs/lightning-terminal/blob/master/doc/letsencrypt.md) to generate certificates automatically and get them automatically signed by Let's Encrypt (supported by most operating systems, browsers, etc.). This may or may not be in lnd, I don't know. However, as mentioned above, this has the problem of needing to trust every issuer, and, I believe that lightning-terminal uses the HTTP-01 challenge, which isn't really secure (see https://serverfault.com/questions/1031317/how-can-lets-encrypt-verify-the-identity-over-insecure-http).
We have another option that could be used, which isn't really implemented right now, and that is to use DNS-based Authentication of Named Entities (DANE), which is an alternative to the PKI that uses DNS and DNSSEC to store public keys in DNS records instead. DNS has it's own centralization problems, but it eliminates the need for a separate CA infrastructure.

With all this being said, why can't the grpc certificate be tied somehow to the node's public key and not fuss with the methods above? The node's public key has it's open channels affiliated with it, and those channels are sort of a way to build a weighted web of trust that may one day be able to eliminate the desire for certificate authorities. I realize that the peer to peer transport may be a widely different protocol than the grpc interface, but I'm just thinking that there could be some way to sign the grpc certificate using the peer to peer transport's public key. We also have the <pubkey>@host format that is typically used to connect to a peer. This is easy to copy and paste, put in QR codes, etc.. Seems like this approach may be better than needing to copy certificate files over if we can use it to bootstrap the security of the grpc certificate.

With all this being said, why can't the grpc certificate be tied somehow to the node's public key and not fuss with the methods above?

Totally can be, we have a new project coming out soon that implements this. The idea is just to use the node public key, and then use the same crypto handshake as we use for the LN p2p protocol over gRPC. So then this way, all you need is a new fresh public key, and everything works as normal.

Is your new gRPC protocol going to use https. or will you run http and then wrap everything in your own encryption? Just wondering how this might be compatible with existing gRPC libraries that are more general than for use with lnd.

The problem with using the node's public key as the TLS/HTTPS key is that you need to unlock the wallet to be able to use the private key to sign stuff. But the unlocking mechanism works through gRPC and you certainly don't want to submit your wallet password through unauthenticated/unencrypted gRPC. So this would only work with the auto-unlocking feature enabled that reads the wallet password from a file on startup.

With all this being said, why can't the grpc certificate be tied somehow to the node's public key and not fuss with the methods above?

Totally can be, we have a new project coming out soon that implements this. The idea is just to use the node public key, and then use the same crypto handshake as we use for the LN p2p protocol over gRPC. So then this way, all you need is a new fresh public key, and everything works as normal.

@Roasbeef , are you talking about https://lightning.engineering/posts/2021-11-30-lightning-node-connect-deep-dive/ ? Curious if you are going to release any other client implementations for Lightning Node Connect? Seems like a really cool alternative, but I have no way of using it in my applications without python libraries being available and the documentation that you've published (in non-code form) is fairly high level, so I don't know where to start to make my own Lightning Node Connect client library.


Fixed coverage testing (checks source now, instead of tests)

At the moment, coverage testing tests the coverage of the lines in the tests directory. This is of course not what we want - we want to check the coverage in the actual source directory (ifsbench). I've done two things:
Run python -m pytest instead of pytest. This automatically adds the current path to sys and will therefore use the actual source folder and not whatever we've installed to the virtual environment. If we don't do this, the coverage is always 0%.
I've replaced --cov by --cov=ifsbench so only the ifsbench dir is treated as source.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 76.40%. Comparing base (f16ae50) to head (30d37b7).

:exclamation:  There is a different number of reports uploaded between BASE (f16ae50) and HEAD (30d37b7). Click for more details.
HEAD has 6 uploads less than BASE

Flag
BASE (f16ae50)
HEAD (30d37b7)

7
1

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #9      +/-   ##
==========================================
- Coverage   83.15%   76.40%   -6.76%
==========================================
  Files          13       17       +4
  Lines         855     1776     +921
==========================================
+ Hits          711     1357     +646
- Misses        144      419     +275

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


key/shortcut remapping in keyboard manager not working at all

Microsoft PowerToys version
0.79.0
Installation method
Microsoft Store
Running as admin
None
Area(s) with issue?
General
Steps to reproduce
1 open keyboard manager
2 enable keyboard manager
3 try to open "remap a key" or "remap a shortcut"
4 nothing happens when you click them
✔ Expected Behavior
a window that allows me to remap keys/shortcuts
❌ Actual Behavior
nothing at all
Other Software
No response

/bugreport


Removing Matt from the required reviewers

TL;DR
The new-codebase has new contributors and currently Matt is not an active collaborator on the codebase. This change makes it faster to get PR's and directs it to more relevant users

Codecov Report

Merging #371 (ef77d46) into master (9f8e22e) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #371      +/-   ##
==========================================
- Coverage   96.00%   95.94%   -0.06%
==========================================
  Files           2        2
  Lines          75       74       -1
  Branches        8        8
==========================================
- Hits           72       71       -1
  Misses          1        1
  Partials        2        2

Impacted Files
Coverage Δ

tests/scripts/test_flytekit_sagemaker_runner.py
100.00% <0.00%> (ø)

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 9f8e22e...ef77d46. Read the comment docs.


Problems when using mod_md "clustered" using shared storage directory on NFS

We keep seeing problems with the renewal of certificates on our four node Apache httpd "cluster" using mod_md (with ~1000 managed domains) with a shared storage directory on NFSv3.
The node -01 is configured with
export MDRenewWindow="33%"
export MDRenewMode="auto"

so it could be called "primary".
And the other nodes are configured with
export MDRenewWindow="30%"
export MDRenewMode="manual"

I suspect that it happens when one of the secondary nodes first reloads/restarts httpd (I think maybe due to logrotate) before the primary node got a chance to and therefore it somehow gets messed up. (Or it might be that the logrotates run too simultaneously...)
From the Apache error logs regarding the domain https://crt.sh/?q=infosys.informatik.uni-mainz.de as an example:
Node -01:
/var/log/apache2/old/error.log-20220710.gz:[Sat Jul 09 17:32:50.738944 2022] [md:notice] [pid 3548953:tid<PHONE_NUMBER>47552] AH10059: The Managed Domain infosys.informatik.uni-mainz.de has been setup and changes will be activated on next (graceful) server restart.

Node -02:
/var/log/apache2/old/error.log-20220711:[Sun Jul 10 00:04:45.042386 2022] [md:error] [pid 4077496:tid<PHONE_NUMBER>14240] (17)File exists: AH10069: infosys.informatik.uni-mainz.de: error loading staged set

Now to come to the actual issue/request:
This does not show up in the monitoring page at md-status - there, all domains are listed and seem fine...
Or do you have any other ideas or shall I look for additional clues?

Looking at my code in this light again, the overall strategy is on a start/reload:

look if there is a staging/mydomain with all data needed
copy over all data to tmp/mydomain my reading (parsing) and writing
move domains/mydomain to archive/mydomain.n
move tmp/mydomain to domains/mydomain

this is all nice on a single host and survives aborted restarts quite well.
However on a cluster with a shared file system, several nodes may be working on the same tmp/mydomain and when one node moves it, it may be incomplete due to another node messing with it.
The best approach here, without some cluster-wide locking, is probably to have tmp/mydomain on a local file system. But that still may give trouble if steps 1-4 are interleaved on several cluster nodes. But at least the produced domains/mydomain directory would be complete.
The only safe way I can think of would require some cluster sync, like holding some lock while processing a staged domain. Which leads us back to MDMessageCmd with a new pre-install action.
Any ideas?

Would be nice if you could try v2.4.18 with the new MDStoreLocks directive. If that works nice in your setup, maybe we could also add such locking for renewal attempts.

@moschlar maybe this escaped your notice. Could you test if the new version addresses the restarting in your cluster?

Hey @icing,
Am Freitag, dem 29.07.2022 um 02:40 -0700 schrieb Stefan Eissing:

@moschlar maybe this escaped your notice. Could you test if the new
version addresses the restarting in your cluster?

Sorry, no, I did see it but there had been many other projects that
needed attention, especially with summer vacation time...
I explicitly left the GitHub notification open to come back at it when
I have the time.

Apache 2.4.54 only ships with v2.4.17, but would love to test MDStoreLocks this when it drops. I am assuming the approach used is compatible with NFS 4's native file locking? In that I gather flock() in newer kernel support NFS v4 file locks?
Q: From the docs I take it the MDStoreLocks time will potentially block a graceful restart such that new requests will be blocked for (up to) that time? But that only affects simultaneously restarting nodes who do not gain the lock first?
Q: Would/should nodes that were not restarting and thus did not activate the staged certificate, notice that the domains directory has a new cert that it is not using (or notice a timestamp file that is readable), and issue an MDMessageCmd to that effect? The user could then implement some variety of random back-off to locally restart the node. Or where there are only 2-3 nodes, each could just restart immediately, since one node has already finished restarting.

Apache 2.4.54 only ships with v2.4.17, but would love to test MDStoreLocks this when it drops. I am assuming the approach used is compatible with NFS 4's native file locking? In that I gather flock() in newer kernel support NFS v4 file locks?

It sounds like it, but I cannot verify.

Q: From the docs I take it the MDStoreLocks time will potentially block a graceful restart such that new requests will be blocked for (up to) that time? But that only affects simultaneously restarting nodes who do not gain the lock first?

Yes, that is how it is intended to work.

Q: Would/should nodes that were not restarting and thus did not activate the staged certificate, notice that the domains directory has a new cert that it is not using (or notice a timestamp file that is readable), and issue an MDMessageCmd to that effect? The user could then implement some variety of random back-off to locally restart the node. Or where there are only 2-3 nodes, each could just restart immediately, since one node has already finished restarting.

I do not see a nice way to make that happen. The node already has read domains and to detect that some other changed it, it would need to assess it again (but when exactly?).
If you want a way to detect that your nodes are not all using the same certificate, you might want to asses the md-status handler for each node. That can give you JSON data with information about the certificate used.

Thank you for the answers @icing! I'm hoping for a way for nodes to detect and restart themselves purely by observing the shared filesystem, without knowledge or network access to the other nodes.
I was thinking that if the node installing a new certificate also touched a world readable empty file somewhere in the shared filesystem (e.g. /etc/apache2/md/last_install) then mod_md on nodes could periodically check if the data/time of that world-readable file was newer than their own start time and if so, invoke MDMessageCmd restart-required. The command invoked could do the same as it would do for MDMessageCmd renewed, it just wouldn't know which domain(s) were renewed.
BTW, is MDMessage installed called during the MDStoreLocks locked period or only after the lock is released?

Closed as being stale.


Change background color of yes/no button row

Depending on the state of the yes/no buttons. Green for yes, grey for no.

oh it was background color of row, I thought it is only for button, kk

thanks @hanbyul-here!


[v6]  radio button input field with a boolean value not a string value not working right.

Is this intended to work right if I use an actual boolean javascript value for input radio field.
Creatd an input field radio button.
trueBool <Field name="trueBool" type="radio" value={true} component="input" />

Using redux-logger trace for actions generated by redux=form i get the following
action Object {type: "redux-form/CHANGE", meta: Object, payload: "true"}
It fails to check the radio button when clicked.
I suspect its because the payload is a string and the field is a javascript boolean
At the moment I think I may need to force my boolean fields in my view model to be strings.
Thank you for your attention and any feedback.
Cheers, Robin

In HTML, when using an input[type="radio"] its value will be a String. So it is the same in RF. If you want to change this behavior, don't use an input but a custom component. You could also use a normalizer to transformer the value before writing it into the store.

You can also add the code below to your boolean radio.
checked={myBoolValue === 'true' || myBoolValue === true}

For those interested, below is a sample of code using a normalizer to make this work.
const normalizeBoolean = value => {
    if (value === "true") {
        return true;
    }

    if (value === "false") {
        return false;
    }

    return value;
};

<Field name="active" component="input" type="radio" value={true} normalize={normalizeBoolean}/>
{' '}
Yes

<Field name="active" component="input" type="radio" value={false} normalize={normalizeBoolean}/>
{' '}
No


Added English editorial for LightOj 1428 (Melody Comparison)

Change requests are resolved now . Please check if everything is okay now .


update webstart-maven-plugin to allow for successful build with JDK 1.7. - SHIRO-403

According to this Jira issue: https://issues.apache.org/jira/browse/SHIRO-403, the patch was applied to: "the trunk and 1.2.x branch". Apologies for not circling back and closing this PR afterwards.


fix(git): use main as default branch in project creation

@pevisscher merged this pull request with Graphite.


Basic IDE integration for C++ projects

Investigate options for IDE integration and implement one such integration.

I would say this is already done with Xcode integration. For further IDE integration, I would refer to issue https://github.com/gradle/gradle-native/issues/19.

This is not done, as we never did the investigation.

The output would be a design document outlining the options we have

@adammurdoch We think this is the same thing as #19.  Would we only do the investigation for this issue?

This is the first part of #19, specifically is to evaluate what IDE integration for C++ actually means and what our options are and what the costs would be.

And to implement the highest priority option from that plan.


Update sensors.py - added SmartwareMotion Detector

Update sensors.py - added SmartwareMotion Detector (433 MHz)

I've edited with github editor and cant see the whitespaces. I cant find the commented BINARYNODE. Sorry

No worries. I've done it myself and it is already merged. Am I correct, that in Home Assistant this should be a binary sensor?

Thank you and yes, its a binary sensor. Works perfectly.


Remove warnings from state plotter

Context:
from mrmustard.lab import *
Vacuum(1)

Executing the code above triggers a long list of annoying warnings, displayed between the recap of the state and the phase-space plot.
Description of the Change:
This PR removes the cause of the warnings, without changing the way that the plot looks

Tbh, I can not reproduce the same warnings on my dev container in the branch develop.


Release 0.11.1

This is a tracker issue to synchronize issues / PRs blocking 0.11.1
Depends on https://github.com/submariner-io/submariner-operator/pull/1728
Depends on https://github.com/submariner-io/submariner-operator/pull/1729

The following PR also needs to be backported. I just pushed the cherry-pick - https://github.com/submariner-io/submariner-operator/pull/1729

Depends on submariner-io/submariner#1640

If possible, it would be nice to have the following issue included in 0.11.1 release as well:  https://github.com/submariner-io/lighthouse/issues/656

@dfarrell07 I am moving to "Verification" in the 0.12 board until we:

Test locally with subctl (just in case, to double check on top of our CI)
Merge the release notes PR (DONE)
Announce the release (Twitter, mailing-lists)

Announce the release (Twitter, mailing-lists)

Okay, I didn't think we did this for patch releases but will-do. :+1:


feat: secure folder upload Action

Part of https://github.com/slsa-framework/slsa-github-generator/issues/1864

I understand this for purposes of uploading folders between trusted VMs. What if these are also outputs? Would the outputs be a tar file, instead of a collection of files when download the artifact?

I'll create a secure download folder which will untar and extract the files. Is that OK?
I may be mis-understanding the question

I may be mis-understanding the question

If the attestation folder is uploaded using this in the SRW, so that the TRW can securely download it, should the TRW then upload the folder with the normal upload-artifact back to the caller? Otherwise the caller will get the attestations uploaded in a tar file.
I guess I'm curious whether the tar needs to be uploaded, rather than just recompute the tar from the downloaded folder and verify its sum in secure-download.

That's a good point. I was thinking that we'd make a public secure-download-attestations Action that untars. But it's not ideal you're right.
Re-tar / zip may not work unless we make sure timestamps are not recorded and other compression methods don't get in the way. So maybe we need a merkle tree of folder content.. this would still require a public Action for folks to verify but at least the caller can download using the official download-artifact.
Google tells me find /path/to/folder -type f -print0 | sort -z | xargs -0 sha1sum | sha1sum may work. I'll need to try it out. TRWs will need to use this so we'd document it.
Wdut?

TRWs will need to use this so we'd document it or create an Action for it.

I believe we can still package that line into a secure-download-folder, so TRWs may not need to know the internals (or even public users where it's less important to do this verification but they may)
Hmmm.

Google tells me find /path/to/folder -type f -print0 | sort -z | xargs -0 sha1sum | sha1sum may work. I'll need to try it out.

I think the filenames may matter here (say we download to a temp folder, then we must execute that command INSIDE the temp folder so that the prefix change wouldn't matter). That's not too bad.
I don't know @ianlewis WDYT? in my view it's nice for a user to not have to deal with the tar'd attestations, but I can't tell if introducing this complexity is too much.
The  folder of build artifacts will also need to be either securely downloaded via the checksums or verified with provenance, right? IMO secure download is easier, since we'll need to match on the many provenance files and artifacts to find the correspondence. In this case as well, we need to either tell TRW users the folder uploaded will be a tar and provide the action, or  do something like the above and hope it stays deterministic

The folder of build artifacts will also need to be either securely downloaded via the checksums or verified with provenance, right? IMO secure download is easier, since we'll need to match on the many provenance files and artifacts to find the correspondence.

BTW, the official download / upload Action cannot download / upload from / to outside the GITHUB_WORKSPACE. At least for download I tried and it cannot. To do that we'd need to call the API ourselves, maybe

In this case as well, we need to either tell TRW users the folder uploaded will be a tar and provide the action, or do something like the above and hope it stays deterministic

I'd like to avoid relying on determinism, that's likely to break sometimes. Especially since there's no guarantees that the VM use the same runner, iiuc.

BTW, the official download / upload Action cannot download / upload from / to outside the GITHUB_WORKSPACE. At least for download I tried and it cannot. To do that we'd need to call the API ourselves, maybe

Yeah, it can. It doesn't check the workspace directory explicitly. Download does fail if the file exists and it won't overwrite it. See this run which successfully uploads /usr/bin/bash but fails to overwrite it when it downloads.
https://github.com/ianlewis/actions-test/actions/runs/4506456118/jobs/7933255194
It seems that the download action also lacks permissions to write to most directories outside the workspace. I still think it's valuable for us to limit the path to the workspace dir and not rely on protections inherent to the runner's environment.

I believe we can still package that line into a secure-download-folder, so TRWs may not need to know the internals (or even public users where it's less important to do this verification but they may)

I think that if there is a secure-upload-folder and secure-download-folder action then users shouldn't need to care about how the folder was uploaded as long as the actions work together, will they? Unless they need to use secure-download-folder with a tarball they uploaded themselves for some reason?

BTW, the official download / upload Action cannot download / upload from / to outside the GITHUB_WORKSPACE. At least for download I tried and it cannot. To do that we'd need to call the API ourselves, maybe

Yeah, it can. It doesn't check the workspace directory explicitly. Download does fail if the file exists and it won't overwrite it. See this run which successfully uploads /usr/bin/bash but fails to overwrite it when it downloads. https://github.com/ianlewis/actions-test/actions/runs/4506456118/jobs/7933255194
It seems that the download action also lacks permissions to write to most directories outside the workspace. I still think it's valuable for us to limit the path to the workspace dir and not rely on protections inherent to the runner's environment.

Agreed. I can add a check to verify the destination does not exist.

I believe we can still package that line into a secure-download-folder, so TRWs may not need to know the internals (or even public users where it's less important to do this verification but they may)

I think that if there is a secure-upload-folder and secure-download-folder action then users shouldn't need to care about how the folder was uploaded as long as the actions work together, will they? Unless they need to use secure-download-folder with a tarball they uploaded themselves for some reason?

That was my reasoning too.
So the summary seems that:

Create internal secure upload / download folder by tar-ing the folder first
Check in both upload and download that it does not overwrite existing files
create a public secure-download-attestation Action that will just call the secure download folder Action

Wdut?

Create a public secure-download-attestation Action that will just call the secure download folder Action

Yes! This plan sounds good. I too would like to avoid relying on the determinism hope.

SG. I'll make these changes then. Thanks for all the feedback!

PATL at the changes.


COPII vesicle coat (GO:0030127) parentage

One of two multimeric complexes that forms a membrane vesicle coat. COPII is best characterized in S. cerevisiae, where the subunits are called Sar1p, Sec13p, Sec31p, Sec23p, and Sec24p. Vesicles with COPII coats are found associated with endoplasmic reticulum (ER) membranes at steady state.
should this have ER  parent? (has Golgi apparatus part)?

If the vesicles shuttle between ER and Golgi, then it's a bit dodgy to say the coat is part_of either ER or Golgi because part_of means always part of.

I will remove the parent from the COPII vesicle.

Seems to be coming from a bad assertion that a Golgi-associated vesicle is a Golgi part. Based on the def, this is not always true.


Graph won't display anything older than 6 hours

Hi all,
I am using the default configuration provided with the Graphite docker image. I have 3 custom metrics I have created and are sending data to successfully. Unfortunately though once I zoom out on the graph in the Graphite Browser to look at a time period older than 6 hours, all data in the graph disappears.
Here's the configuration. I am not seeing what the issue could be. Any assistance is appreciated, thank you!
/opt/graphite/storage/whisper # cat /opt/graphite/conf/storage-schemas.conf
# Schema definitions for Whisper files. Entries are scanned in order,
# and first match wins. This file is scanned for changes every 60 seconds.
#
# Definition Syntax:
#
#    [name]
#    pattern = regex
#    retentions = timePerPoint:timeToStore, timePerPoint:timeToStore, ...
#
# Remember: To support accurate aggregation from higher to lower resolution
#           archives, the precision of a longer retention archive must be
#           cleanly divisible by precision of next lower retention archive.
#
#           Valid:    60s:7d,300s:30d (300/60 = 5)
#           Invalid:  180s:7d,300s:30d (300/180 = 3.333)
#

# Carbon's internal metrics. This entry should match what is specified in
# CARBON_METRIC_PREFIX and CARBON_METRIC_INTERVAL settings
[carbon]
pattern = ^carbon\.
retentions = 10s:6h,1m:90d

[default_1min_for_1day]
pattern = .*
retentions = 10s:6h,1m:6d,10m:1800d

/opt/graphite/storage/whisper # cat /opt/graphite/conf/storage-aggregation.conf
# Aggregation methods for whisper files. Entries are scanned in order,
# and first match wins. This file is scanned for changes every 60 seconds
#
#  [name]
#  pattern = <regex>
#  xFilesFactor = <float between 0 and 1>
#  aggregationMethod = <average|sum|last|max|min>
#
#  name: Arbitrary unique name for the rule
#  pattern: Regex pattern to match against the metric name
#  xFilesFactor: Ratio of valid data points required for aggregation to the next retention to occur
#  aggregationMethod: function to apply to data points for aggregation
#
[min]
pattern = \.lower$
xFilesFactor = 0.1
aggregationMethod = min

[max]
pattern = \.upper(_\d+)?$
xFilesFactor = 0.1
aggregationMethod = max

[sum]
pattern = \.sum$
xFilesFactor = 0
aggregationMethod = sum

[count]
pattern = \.count$
xFilesFactor = 0
aggregationMethod = sum

[count_legacy]
pattern = ^stats_counts.*
xFilesFactor = 0
aggregationMethod = sum

[default_average]
pattern = .*
xFilesFactor = 0.3
aggregationMethod = average

One of the metrics:
/opt/graphite/storage/whisper # ../../bin/whisper-info.py ./LOGINS.wsp
aggregationMethod: average
maxRetention: 155520000
xFilesFactor: 0.30000001192092896
fileSize: 3240052

Archive 0
offset: 52
secondsPerPoint: 10
points: 2160
retention: 21600
size: 25920

Archive 1
offset: 25972
secondsPerPoint: 60
points: 8640
retention: 518400
size: 103680

Archive 2
offset: 129652
secondsPerPoint: 600
points: 259200
retention: 155520000
size: 3110400

You are most likely not sending points at a 10-second interval.  What that means is that when the points are rolled up into the 1-minute interval instead of seeing eg 1,2,3,4,5,6 it has 1,null,null,4,null,null (if you're sending at a 30-second interval) or 1,null,null,null,null,null (for a 60-second interval).
Because of your xFilesFactor settings, you effectively need to have at least 5 non-null points for the default_average pattern and 6 non-null points for the other patterns to get a valid rollup.

That is definitely it. I am sending the values at 2 minute intervals, not 10 seconds.
I'll fix up my configuration. Thank you!


Add a RemoteCollectBatchIterator

Codecov Report

Merging #5000 into batch-iterator will decrease coverage by -0.12%.
The diff coverage is 73.72%.

@@                 Coverage Diff                  @@
##             batch-iterator    #5000      +/-   ##
====================================================
- Coverage             82.15%   82.04%   -0.12%
+ Complexity            10899    10884      -15
====================================================
  Files                  1318     1319       +1
  Lines                 45069    45112      +43
  Branches               5692     5701       +9
====================================================
- Hits                  37028    37011      -17
- Misses                 5372     5419      +47
- Partials               2669     2682      +13

Impacted Files
Coverage Δ
Complexity Δ

dex/src/main/java/io/crate/data/BatchConsumer.java
100% <100%> (ø)
1 <1> (?)

...rate/operation/collect/RemoteCollectorFactory.java
92% <100%> (-0.31%)
5 <1> (+1)

...collect/collectors/RemoteCollectBatchIterator.java
72.56% <72.56%> (ø)
8 <8> (?)

...exceptions/GroupByOnArrayUnsupportedException.java
66.66% <0%> (-33.34%)
1% <0%> (-1%)

.../main/java/io/crate/metadata/doc/DocTableInfo.java
64.67% <0%> (-17.97%)
49% <0%> (-3%)

...crate/executor/transport/TransportShardAction.java
90% <0%> (-7.5%)
9% <0%> (-1%)

...tor/transport/distributed/SingleBucketBuilder.java
70% <0%> (-6.67%)
9% <0%> (-1%)

.../java/io/crate/blob/TransportDeleteBlobAction.java
75% <0%> (-5%)
5% <0%> (-1%)

core/src/main/java/io/crate/types/ShortType.java
88.46% <0%> (-3.85%)
18% <0%> (-1%)

...rc/main/java/io/crate/blob/BlobTransferTarget.java
84.1% <0%> (-3.32%)
25% <0%> (-1%)

... and 25 more

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 0253b7d...7a5c3ac. Read the comment docs.

Opened a alternative PR which has the BatchIterator decoupled for testing: https://github.com/crate/crate/pull/5010
But currently the BatchIteratorTester fails because .get calls on the columns proxy fail until the BatchIterator is loaded. Probably need to adapt the contract there, @dobe?

Became obsolete due to https://github.com/crate/crate/pull/5013


Decrease minsdk

Hi there!
Can you please decrease the minsdk from 14 to 9 or most least version to support more android devices. if so please do it.
I guess you can because MaterialTapTarget  a similar library has minsdk to 9.
Thank you.

The library uses things that are not available on API 9 and I do not think it's worth adding in something like nine old androids just to support 1% of devices. I also do not have devices that old to test with

ok but 1% in terms android users is not less. 1% = several thousands of devices.


Using getNameField for the DURC editing pages

The method used to populate the name in the DURC web form drop down is not tying back to the DURCModel->getNameField() function to sort out which name should display. Is this something that can be fixed? https://github.com/CareSet/DURC/blob/master/src/DURCModel.php#L308
To see the problem look at onering url /DURC/podproject/1016 and look at the project repo id field... It should be finding the repoName field but it is not...

@ftrotter is this related or a dup of #76 ?

I re-ran durc and there seems to be a bug causing those two repo fields not to get their display values, and is crashing the select2 plugin. Plan of action is to 1: Fix bug 2: refactor so all of the "select text"  comes from the getFieldName() function, rather than the controller functions.

@ftrotter I fixed the bug that was causing the select2 to not function. Now it pulls correctly from the related model using the controller code. I didn't make it look for the "local" name field from the same table. That seems weird to me from a relational DB standpoint, because if you update the project repo, then you'd also always have to update the repo name, which is already on the related model's table, so not sure why you'd even need the repo name field, or it shouldn't it be on the related model. Bug was in the mustache generator for select2, so will need to re-write views.

Did we decide that this is a dup of #76 ? If so this looks good and can be closed.

If I'm understanding this correctly, this looks like it's working as expected.


Test: First bootstrap of Kubernetes FQDN test

This new Kubernetes end-to-end test creates a new Bind container with
the cilium.test domain.
Also all kubedns and coredns services will proxy a cilium.test to the
bind service.
For simulating world, two new containers in the 192.168.9.X Docker
network will be online where applications can ping, http request without
using internet connection and avoid flakes.
Signed-off-by: Eloy Coto<EMAIL_ADDRESS>

This change is

test-me-please

test-missed-k8s

Coverage increased (+0.01%) to 43.89% when pulling 63b9c0fe56ee0968bed5e987e6980801dc827192 on eloycoto:FQDNK8s into 93c115a616671264cfd1fdc235f42c0f18047abe on cilium:master.

test-missed-k8s

test-me-please

test-me-please

test-me-please

test-me-please

test-missed-k8s

test-me-please

test-me-please

test-me-please

test-me-please


Why does windows use favicon.png instead of the icon I specified in resource.syso?

Hi,
I'm trying to make the taskbar icon look nice in windows, but no matter what kind of favicon it uses, it is coming up pixelated.  I specified an icon using syso and that looks great for the actual exe and scales perfectly using a multi res ico file, but the same file doesn't work there either.  At the end I tested the png included in the counter example to see if it looked as bad as my png was looking (it does)

Is there any solution?

favicon.svg? Bigger PNG?


The movie is marked as available even though only the 4K version is.

Description
When a movie is downloaded only in 4K, it is marked as "available" and "4K available", so we cannot request it in HD.
I haven't tested it for TV shows, but it might also be the case.
Version
1.4.1
Steps to Reproduce

4K radarr instance needed
Go on a movie
Ask for the movie in 4K
Waiting for the movie to download
The movie is marked available

Screenshots

The movie in jellyfin :

Logs
No response
Platform
desktop
Device
PC
Operating System
Windows 11
Browser
Chrome
Additional Context
My Jellyseerr instance is hosted on Docker using the 'latest' tag.
Code of Conduct

[X] I agree to follow Overseerr's Code of Conduct

This is already fixed and will be available in the next branch. If you want to try it out you can also try it using the development tag. You'll have to manually clear data of the media affected tho

I am also facing the same issue. I am using 1.5.0 version currently

I am also facing the same issue. I am using 1.5.0 version currently

You might wanna clear data and rescan. That will fix it with the new version

I have started using jellyseerr from the 1.5.0 version. Just set it up yesterday. I did the rescan now but that didn't fix the issue. (I am using the merge versions plugin in jellyfin btw)

I tested the same on shows, and it seems to work fine with the 4k-only shows. Only The 4k-only movies are experiencing this issue.

4k and 1080p movies are in separate folders in the filesystem. Still, in Jellyfin, all these folders are added to the same library, and I use the merge versions plugin in Jellyfin to combine different versions if they exist.
It is the same as above with shows too. But shows have no issues.

4k and 1080p movies are in separate folders in the filesystem. Still, in Jellyfin, all these folders are added to the same library, and I use the merge versions plugin in Jellyfin to combine different versions if they exist.
It is the same as above with shows too. But shows have no issues.

Could you try putting two test ones in two seperate libraries and see if they detect? (As so far everyone who reported before show fix and after show fix mentioned that movies were working fine. It was the shows that were borked and after the fix they mentioned shows were working as well)

I don't understand what you mean by putting 2 files in separate libraries.😅
I think I wasn't clear in explaining my issue😅.
The issue is when I have only one version of the movie (4k), jellyseerr is falsely detecting that both versions exist.(which isn't true).
This is what is happening currently in my library.
Scenario 1:
4k version exists in jellyfin
1080p version exists in jellyfin
Jellyseerr shows both as available.
Scenario 2:
4k version doesn't exist in jellyfin
1080p version exists in jellyfin
Jellyseerr shows that 1080p is available along with an option to request for 4k.
Scenario 3(the issue):
4k version exists in jellyfin
1080p version doesn't exist in jellyfin
Jellyseerr shows that both versions are available(even though 1080p actually isn't available).
What else should I test to diagnose the issue? Are there any logs I can provide?
Thanks for responding so quickly and trying to solve my issue.

@Rover1176 could you reach out on discord server so its easier to troubleshoot? I'll update here once done

This was fixed in bc9017f54d84ec24c4d74d38e1b4e24219425d41 and 3bf04f2abd96bf95a1363dd16e4de46cf621ab5d


[Android]Image resizeMode 'contain' should be converted as 'FIT_CENTER'

I'm using React Native v0.12.0.
When using Image with resizeMode specified as 'contain', There is a big difference if the png resource is smaller than the Image view size between iOS and Android.
on iOS: the image is scaled up to fill the view with ratio unchanged

on Android: the image is NOT scaled, which is not prefered

I've dig into the related source code in com.facebook.react.views.image.ImageResizeMode:

public static ScalingUtils.ScaleType toScaleType(@Nullable String resizeModeValue) {
if ("contain".equals(resizeModeValue)) {
return ScalingUtils.ScaleType.CENTER_INSIDE;
}
...
}

But I think it should be FIT_CENTER, as follows

if ("contain".equals(resizeModeValue)) {
return ScalingUtils.ScaleType.FIT_CENTER;
}

Does anyone else have also noticed this issue?

If the image failed to load, try refresh...

YES,I got this issue too;
I'm using React Native v0.14+.

I also believe FIT_CENTER would be the correct choice here...

+1

+1

Just gave this PR a try an am still getting a white screen when setting resizeMode to "contain".
Can anyone else try this out and report back? Thanks!

Any progress on this? Small png images does not fill the view when resizeMode is contain.

@bcalik It appears PR #5738 was shipped 3 days ago. I can't say for certain in which version in will land but you can follow that PR for further progress.

Glad this is getting fixed, weird to me it was setup like this.

For anyone interested in a fix for now. You can open up react-native in your node modules and edit ImageResizeMode.java located here:

Fixed via https://github.com/pglotov/react-native/commit/8dab14f06263067af0762b0c44799397ab62e181

@christopherdro contain is still not scaling up images--am I missing something?

@skleest The fix is in 0.23-rc.

@christopherdro Thanks for the response, I tried both 0.23-rc as well as changing the source code manually. Maybe a bug with Fresco?

@skleest @christopherdro same, just tried 0.23.0-rc1 and the behavior doesn't seem to have changed, images are not scaling to fit

I am on RN 0.19, and I have manually changed CENTER_INSIDE to FIT_CENTER in the source code and rebuilt the app, but contain still doesn't scale images up for me.

@veronicapowersbeardon just upgrade the version. It is not hard.

@veronicapowersbeardon you have to recompile the entire react-native module (not just your app) from source to get those changes to be picked up, much easier (and a few hours less work) to switch to 0.23-rc1 as mentioned above

Ah, I see.  Thank you!


How to hide days from previous month and future month ? see example

Hello,
How to hide days from previous month and future month ? see picture below
https://www.dropbox.com/s/o5owk36djxhl6xm/git-hub-insue.png?dl=0
thanks

@vaskolekoski
You can pass your customized template, check the monthviewDisplayEventTemplateUrl option in README.


metrics-apiserver json logs

    > I'm very sorry @JorTurFer - I was looking at logs from the `keda-operator-metrics-apiserver` deployment. It seems that only has a level setting as opposed to the operator having level, format, and timeEncoding.

Our logs for keda-operator are correctly being emitted as JSON 🤦

That said, I'd like to have the metrics-apiserver log in json format as well, primarily because all info logs are emitted to stderr and those show up as error logs in our logging system. Could this functionality please be added?
Originally posted by @naseemkullah in https://github.com/kedacore/keda/issues/3655#issuecomment-1367852952

Hi,
What KEDA version are you using?

Hi Jorge, 2.9.1

I have reviewed and you are right, all the logs are sent to stderr :( You can disable this behaviour removing the -logtostderr=true from the deployment arguments.
Maybe we should review this for the future @kedacore/keda-core-contributors , something like -stderrthreshold=ERROR could be enough

What are the accepted values for --stderrthreshold today Jorge? the default is 2 but not sure what that maps to

Hi there, this is still an issue in 2.10.1. metrics server has a different logging settings than the other two binaries, as visible in the docs of helm: https://github.com/kedacore/charts/blob/main/keda/README.md. This doesn't allow users to enable json logs or set a logging level using words (like debug or info).
Are there any plans to change this? It's hard to tell from the issue history.

AFAIK, there isn't work in progress in this direction, but if you have an idea and you are willing to contribute, you can do it :)

I have reviewed and you are right, all the logs are sent to stderr :( You can disable this behaviour removing the -logtostderr=true from the deployment arguments. Maybe we should review this in the future @kedacore/keda-core-contributors , something like -stderrthreshold=ERROR could be enough

Hi @JorTurFer , is there any plan to add this(-stderrthreshold=ERROR) deployment arguments ?
I just want to contribute .

There isn't any wip about this, so the stage is yours :smile:

Would love JSON logs so that they can be properly parsed in places like Google Cloud Logs Explorer.

same need


fix sql query to deal with multiple json_schema_keys for aspredicted schema

Purpose
fix sql query to deal with multiple json_schema_keys for aspredicted schema
Changes
Removed group by json_schema_key in retract_by_date & reg_by_date and added group by name to setup queries to get both aspredicted schemas counted a single time
QA Notes
Documentation
Side Effects
None that I know of?
Ticket
https://openscience.atlassian.net/browse/ENG-1267

Cherry-picked in as 2999f19cb628752003ea82d94a140a642a46e0a5, consider this merged ⛏


Fixed scrolling bug that skipped a day when scrolling slowly

https://www.pivotaltracker.com/story/show/95721430

:+1:


[ja] Translate tasks/debug-application-cluster/audit into Japanese

This is a Feature Request
What would you like to be added
Translate tasks/debug-application-cluster/audit  into Japanese.
Why is this needed
This page has not been translated.
Comments
/language ja
/assign

/triage accepted


Base: tx message tags handle long message names

add a margin right 16px

Closing as it's been merged with no issues.


Scrutinizer Auto-Fixes

@Yoshi2889 requested this pull request.
It consists of patches automatically generated for this project on Scrutinizer:
https://scrutinizer-ci.com/g/WildPHP/Wild-IRC-Bot/

This is to fix indentation.


[Event Request] Table 6651 - Return Shipment Line - Add IsHandled to OnInsertInvLineFromRetShptLineOnBeforePurchLineInsert (like is done for the same event in the Sales Line table)

Dear ALAppExtensions team,
Through this issue we would like to request an IsHandled parameter to be added to event OnInsertInvLineFromRetShptLineOnBeforePurchLineInsert in table 6651 Return Shipment Line, resulting in the following code in procedure InsertInvLineFromRetShptLine:
            IsHandled := false;
            OnInsertInvLineFromRetShptLineOnBeforePurchLineInsert(Rec, PurchLine, NextLineNo, IsHandled); // Add argumentIsHandled, like for Sales Line table event
            if not IsHandled then begin
                PurchLine.Insert();
                NextLineNo := NextLineNo + 10000;
            end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Skip JS tests if driver is not installed.

Coverage remained the same at 100.0% when pulling 9032dfd2351484c16cc1bfabef556e78fa5ddfd9 on skip-js into 7d76af4af777d74b8917659ad7e9d6d3db58ab83 on dev.

Coverage remained the same at 100.0% when pulling 241ca512cf66bfd702bccc1e66b4e8b6940a91ec on skip-js into ea1e650b619f5741c5a9e3d22faeb527e0b1e5a9 on dev.

It appears like this isn't working for everybody.. Trying to fix it :)

It appears like this isn't working for everybody.. Trying to fix it :)

Fixed now and ready for merge and review.

Coverage remained the same at 100.0% when pulling d4fc80ab132ea790454bf8e4860e47a431b62b17 on skip-js into ea1e650b619f5741c5a9e3d22faeb527e0b1e5a9 on dev.

Coverage remained the same at 100.0% when pulling d4fc80ab132ea790454bf8e4860e47a431b62b17 on skip-js into ea1e650b619f5741c5a9e3d22faeb527e0b1e5a9 on dev.


Beacon chain light protocol plans

We need a rough sketch of how we're doing beacon chain light protocol access.  I suggest the following.
A new sub protocol for the portal network.  I'll call this the "Beacon Chain Light Client" network.  This network will provide storage and retrieval of LightClientUpdate objects back to some reasonable historical time horizon.  The network will also provide gossip of the latest LightClientUpdate objects as they enter the network (provided by a bridge node).
This will need to be fleshed out into a full spec document.  Would anyone like to volunteer?

I started working on draft specs for the Beacon Chain Light Client network. I will push a PR for review when I have something and then we can iterate on it.


feat: Provide per test "context" that is shared with "beforeEach"

Right now beforeEach has limited utility in concurrent tests. The following won't work because both tests manipulate a shared variable and run concurrently:
var obj;

test.beforeEach(t => {
  obj = // ... some verbose setup code.
  t.end();
});

test('test1', t => {
  // tests with side-affects  on `obj`

  // sometime later
  t.end();
});

test('test2', t => {
  // tests with side-affects  on `obj`

  // sometime later
  t.end();
});

To address this, I think it would be good to provide a this reference that is shared between beforeEach and the individual test:
var globalCount = 1;

test.beforeEach(t => {
  this.count = globalCount;
  globalCount++;
  t.end();
});

test('test1', t => {
  t.plan(1);
  var self = this;
  setTimeout(() => t.is(self.count, 1));
});

test('test2', t => {
  t.plan(1);
  var self = this;
  setTimeout(() => t.is(self.count, 2));
});

The above is maybe not the best example and might fail since I doubt we are guaranteeing test instantiation order in a concurrent testing framework.
Another alternative might be to pass the context as an optional second arg:
var globalCount = 1;

test.beforeEach((t, ctx) => {
  ctx.count = globalCount;
  globalCount++;
  t.end();
});

test('test1', (t, ctx) => {
  t.plan(1);
  setTimeout(() => t.is(ctx.count, 1));
});

test('test2', (t, ctx) => {
  t.plan(1);
  setTimeout(() => t.is(ctx.count, 2));
});

This has the advantage of avoiding self reference verbosity.

I like the current approach: t.context :smile:

CRAP!
How did I miss that?!


chore: Fix various typos

Please ensure your pull request adheres to the following guidelines:

[ ] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[ ] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[ ] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Are you a user of Cilium? Please add yourself to the Users doc
[ ] Thanks for contributing!

This fixes a few typos and grammatical errors.

Thanks for the fixes, can you squash your commits and add sign off to it?

@AaronDewes Thank you for these updates! It looks like this PR needs a bit more TLC. Could you take another look?

Sorry, I missed the previous comments. I'll get back to this pr in about 30 mins.


Make xcode-install list (without --all) not only show the 7 beta

xcode-install list now only returns: 7 beta
While of course one can use --all to see the rest, it would be better if we'd see the list of versions for the latest 'stable' major as well as the bleeding edge.

Thanks so much @sirlantis


SLES 15 SP5 - support updates

Support rocAL setup on SLES 15 SP5

Test

Ubuntu 20

rocAL Dependencies Installed with rocAL-setup.py V-2.4.0 on Linux-5.15.0-113-generic-x86_64-with-glibc2.29-Ubuntu-20

Ubuntu 22

rocAL Dependencies Installed with rocAL-setup.py V-2.4.0 on Linux-6.5.0-41-generic-x86_64-with-glibc2.35-Ubuntu-22

SLES 15 SP5

rocAL Dependencies Installed with rocAL-setup.py V-2.4.0 on Linux-6.5.0-41-generic-x86_64-with-glibc2.3.4-SLES

CentOS 7

rocAL Dependencies Installed with rocAL-setup.py V-2.4.0 on Linux-5.15.0-113-generic-x86_64-with-centos-7.9.2009-Core-redhat-7

RHEL 8

rocAL Dependencies Installed with rocAL-setup.py V-2.4.0 on Linux-6.5.0-41-generic-x86_64-with-redhat-8.8-Ootpa-redhat-8


Installation command error in docs/getting-started.md

When using composer to download Yii2-user, the correct command seems to be as follows.
composer require "dektrium/yii2-user":"0.9.@dev"
The origin command on docs/getting-started.md is lacking of quotes on both sides of the colon and results in UnexpectedValueException as follows.
[UnexpectedValueException]
Could not parse version constraint <=2.: Invalid version string "2.*"

I've checked command from manual and it works. Please make sure that you're using the latest composer version and using the same command given in docs.


[Feature] Support for creating new images that contain nothing

Current Behavior
AFAICT regctl has no command that can create an empty image, eg: FROM scratch
Expected Behavior
None
Example Solution
I am proposing adding a new subcommand named regctl image create that will create an empty image and push it a registry/ocidir.
Example: regctl image create <REF> --os linux --arch arm64 --variant v8
Version
VCSTag:     v0.6.0
VCSRef:     9de7397da9f1c00dad5213519366002376b8d5ed
VCSCommit:  9de7397da9f1c00dad5213519366002376b8d5ed
VCSState:   clean
VCSDate:    2024-03-24T18:09:00Z
Platform:   darwin/arm64
GoVer:      go1.22.1
GoCompiler: gc

Environment

Running as binary or container:
Host platform:
Registry description:

Anything else

The primitive way to do this is:
config_digest=$(regctl blob put ocidir://tools/regctl/output:latest <<EOF
{
   "created": "",
   "architecture": "arm64",
   "os": "linux",
   "variant": "v8",
   "config": {},
   "history": [],
   "rootfs": {
      "type":"layers",
      "diff_ids": []
   }
}
EOF
)

regctl manifest put ocidir://tools/regctl/output:latest <<EOF
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.oci.image.manifest.v1+json",
   "config": {
      "mediaType": "application/vnd.oci.image.config.v1+json",
      "digest": "$config_digest"
   },
   "layers": []
}
EOF

Thanks for the suggestion! That would align fairly well with regctl index create. I've added it to my todo list.

This should now be supported. I have intentions to extend this with the option to include layers in the future, avoiding the need to mod the image after it is created.


run comand not work  "python .\auto3d.py --path="data/smiles.sdf" --use_gpu=False"

Looks like it's due to the path difference between different systems. For windows, the path should be --path="data\smiles.sdf"


"Făgețelu", "Bâgești", "Chilia", "Gruiu", "Isaci", "Pielcani" are listed in the drop-down men

Description:
When user writes "Făgețelu", "Bâgești", "Chilia", "Gruiu", "Isaci" and "Pielcani" the locations appear in the drop-down menu next to the comune and the county which is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Făgețelu"
Expected results
The location appears in the drop-down menu as "Sat Făgețelu, OLT (Făgețelu)"

Step 2
Press "x" button.
Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Bâgești"
Expected results
The location appears in the drop-down menu as "Sat Bâgești, OLT (Făgețelu)"

Step 4
Press "x" button.
Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Chilia"
Expected results
The location appears in the drop-down menu as "Sat Chilia, OLT (Făgețelu)"

Step 6
Press "x" button.
Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Gruiu"
Expected results
The location appears in the drop-down menu as "Sat Gruiu, OLT (Făgețelu)"

Step 9
Write in the search bar "Isaci"
Expected results
The location appears in the drop-down menu as "Sat Isaci, OLT (Făgețelu)"

Step 10
Press "x" button.
Expected results
The location was deleted from the search bar.

Step 11
Write in the search bar "Pielcani"
Expected results
The location appears in the drop-down menu as "Sat Pielcani, OLT (Făgețelu)"


pointing to the new commit to the master in django_irods

This is just an update on HydroShare to point to the new commit to the master in django_irods submodule, for fixing the unicode issue #2299

@aphelionz Can you approve this PR which just update SHA reference to point to the latest commit to the master branch in django_irods submodule for the further unicode issue fix?


python311Packages.pythonfinder: fix build

Description of changes
The build was broken as can be seen here. The Pydantic patch no longer worked because the project no longer uses pydantic.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 313119 run on x86_64-linux 1

4 packages built:

python311Packages.pythonfinder
python311Packages.pythonfinder.dist
python312Packages.pythonfinder
python312Packages.pythonfinder.dist


Magnet mode persist on new world

Whenever you start a new world after dying/deleting one that previously had advanced options on they're not available and have to be reenabled to use.
This has been the way for a good while and I think it's about time this was changed.

NEI will be completely rewritten for 1.13, this will likely be changing in that rewrite. Sorry gonna close this.

Fair enough. Will deal with the usual work around till then.


S3 Auditor Needs Source VPC Exemption

If you have an S3 policy that looks like this:
        "Effect": "Allow",
        "Action": "s3:GetObject",
        "Resource": [
          "arn:aws:s3:::some-bucket/*"
        ],
        "Condition": {
          "StringEquals": {
            "aws:sourceVpc": "vpc-01234567"
          }
        },
        "Principal": "*"
      }

The Auditor will flag this as the bucket being wide open.  The Auditor needs to check for the aws:sourceVpc condition.
Also, the Auditor thinks CloudFront ARNs are unknown cross-account access. - Will need some logic to parse out the CloudFront ARN and ignore that (or at the very least, raise an issue that is not rated 10).

Fixed in #757


Update db/initialize.sql to drop/create a cache_development db

The MO process for updating a development db snapshot will usually drop this third db, which is necessary for local caching.
Solid Queue uses tables in the main db, so that's just a migration.

coverage: 94.429%. remained the same
when pulling 3f660ffba9062368aa2dda2a0d14155e8ced4b5d on update-db-initialize-sql
into de869882727602161f602d499d47b7ec4d1f29f1 on main.


Shader Compiler(shaderc) Error:0x80004002

Like @andr3wmac, I wanted to make the shader compiler an embedded tool library. I've had success in communicating to shaderc via a C# wrapper to a modified version of shaderc.cpp.
But i'm having some issues now, the compiler is passing back error: 0x80004002. I have no idea what this means and investigating the C++ source code brings little success. Because I'm communicating to the C++ function that used to be the main function, I can pass arguments to it like I would a console command. So this is what i'm basically using as arguments;
"shaderc -f C:\\Users\\cory1\\Dropbox\\RubberTechEngine\\Build\\Debug32\\..\\Assets\\Shaders\\src\\Cubes\\vs_cubes.sc -i C:\\Users\\cory1\\Dropbox\\RubberTechEngine\\Build\\Debug32\\..\\Assets\\Shaders\\include\\ -o C:\\Users\\cory1\\Dropbox\\RubberTechEngine\\Build\\Debug32\\..\\Assets\\Shaders\\bin\\dx11\\Cubes\\vs_cubes.bin --platform windows --type vertex --profile vs_4_0 -O 3 --depends --disasm"

I'm using the cubes example for reference here.
I tried using no double back slashes, forward slashes, and relative paths(with forward and back slashes) and quotes just confuse it.
What could I be doing wrong...?
I looked at shader.mk and how the configuration process would compile them, the only differences between the two is the ordering of arguments... From what I can see.

I looked at issue [https://github.com/bkaradzic/bgfx/issues/518], my sdk's are where they should be. Reinstalled DirectX SDK June 10 to verify. Installing Windows 10's sdk to further verify this.

Changing the DXSDK_DIR to point to the correct windows SDK and including the d3dcompiler_47.dll with the exe will fix this. Problem solved.

Grab latest bx, I removed DXSDK_DIR completely.