[Snyk] Security upgrade Microsoft.AspNetCore.Components.Web from 6.0.1 to 6.0.25

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `nuget` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

packages/nimble-blazor/NimbleBlazor/NimbleBlazor.csproj

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

141/1000  Why? Confidentiality impact: High, Integrity impact: None, Availability impact: None, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Local, EPSS: 0.01055, Social Trends: No, Days since published: 0, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.35, Score Version: V5
Access Control Bypass SNYK-DOTNET-MICROSOFTASPNETCORECOMPONENTS-6060291
No
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Access Control Bypass

Abandoning since we want to update more of these dependencies together. We'll look at using Renovate to do this instead. Hopefully Snyk respects abandoned PRs like Renovate does.


Recursively search for alert rule files

I tried to specify a directory in the main config, which obviously isn't supported:
rule_files:
  - /etc/prometheus-alerts/

$ tree prometheus-alerts
/etc/prometheus-alerts
|-- team1/
|   `-- configmap1/
|       |-- alert1.yaml
|       `-- alert2.yaml
`-- team2/
    |-- configmap1/
    |   |-- alert1.yaml
    |   |-- alert2.yaml
    |   `-- alert3.yaml
    `-- configmap2/

rule_files is a lost of files, not directories. You can use a glob in the filename though (but not the directories).

@brian-brazil in this case I expect to be able to to specific something like:
rule_files:
  - /etc/prometheus-alerts/*/*/*.yaml

But golang's file globs doesn't support that. That's my issue, I don't know the actual list of directories that contain these files.

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

I've started thread https://groups.google.com/forum/#!topic/prometheus-users/ExJbj-pX-es .


Build failed dev.hilla.push.PushMessageHandler declares multiple scope

quarkus: 3.2.4.Final
hilla version 2.1.7
quarkus-hilla  version 2.0.1
Java SE <IP_ADDRESS>
[INFO] ------------------------------------------------------------------------
[INFO]  BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  50.019 s
[INFO] Finished at: 2023-10-04T15:32:02+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal mio.quarkus.platform:quarkus-maven-plugin:3.2.4.Final:build (default) on project [xxx-hilla:
 Failed to build quarkus application: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
[ERROR]     [error]: Build step io.quarkus.arc.deployment.ArcProcessor#registerBeans threw an exception: jakarta.enterprise.inject.spi.DefinitionException: Bean class dev.hilla.push.PushMessageHandler declares multiple scope type annotations: jakarta.enterprise.context.ApplicationScoped, jakarta.inject.Singleton
[ERROR]     at io.quarkus.arc.processor.Beans.multipleScopesFound(Beans.java:318)
[ERROR]     at io.quarkus.arc.processor.Beans$ClassBeanFactory.create(Beans.java:1277)
[ERROR]     at io.quarkus.arc.processor.Beans.createClassBean(Beans.java:52)
[ERROR]     at io.quarkus.arc.processor.BeanDeployment.findBeans(BeanDeployment.java:1161)
[ERROR]     at io.quarkus.arc.processor.BeanDeployment.registerBeans(BeanDeployment.java:271)
[ERROR]     at io.quarkus.arc.processor.BeanProcessor.registerBeans(BeanProcessor.java:141)
[ERROR]     at io.quarkus.arc.deployment.ArcProcessor.registerBeans(ArcProcessor.java:419)
[ERROR]     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR]     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
[ERROR]     at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR]     at java.base/java.lang.reflect.Method.invoke(Method.java:568)
[ERROR]     at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:864)
[ERROR]     at io.quarkus.builder.BuildContext.run(BuildContext.java:282)
[ERROR]     at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
[ERROR]     at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2513)
[ERROR]     at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1538)
[ERROR]     at java.base/java.lang.Thread.run(Thread.java:833)
[ERROR]     at org.jboss.threads.JBossThread.run(JBossThread.java:501)
[ERROR] -> [Help 1]

Hi @leotu, thanks for trying out the extension and for filling the issue.
I tried locally, downloading a new app from code.quarkus.io and also with the quarkus-hilla-starter using the versions you mentioned, but I had no build errors.
Do you have any spring related extensions in your project?
Could you share an example project that reproduces the issue?

I think the problem may arise from a conflict with the extension "quarkus-spring-data-jpa"
Download from: https://code.quarkus.io/?e=com.github.mcollovati%3Aquarkus-hilla
Import into Eclipse and pom.xml file just add
 <dependency>
   <groupId>io.quarkus</groupId>
   <artifactId>quarkus-spring-data-jpa</artifactId>
</dependency>

code-with-quarkus_build-failed.zip

Unfortunately, the error is expected because the extension is not designed to work with Spring.
But you can use Panache as a replacement for Spring Data JPA.
Here's a simple ToDo List example project using quarkus-hilla and panache to access persisted data

I tried removing "quarkus-spring-data-jpa" and adding "quarkus-spring-di"  still build failed with the same error
   <!--
   <dependency>
	  <groupId>io.quarkus</groupId>
	  <artifactId>quarkus-spring-data-jpa</artifactId>
   </dependency>
   -->
   <dependency>
          <groupId>io.quarkus</groupId>
          <artifactId>quarkus-spring-di</artifactId>
   </dependency>

The  code of Hilla Project uses a lot of @Bean @Autowired @Component, so I think this extension should be able to not affect quarkus-spring-di.
At the same time, I found that Hilla Project only PushMessageHandler.java uses @Service (excluding test code), so it seems that this extension only needs to solve
".addBeanClasses(PushEndpoint.class, PushMessageHandler.class)" will do.
https://github.com/mcollovati/quarkus-hilla/blob/3643742b590d380be236e14ffd198721320eba97/deployment/src/main/java/com/github/mcollovati/quarkus/hilla/deployment/QuarkusHillaExtensionProcessor.java#L155

Hilla Project

Quarkus-hilla

@leotu thanks for investigation!
The whole point about the extension was running Hilla in a Quarkus environment without Spring, so we did not plant to support any of the quarkus-spring-xxx extensions.
For this reason, for example we have a dependency that shades the minimum amount of Spring classes required to make the build work, but we rely on the Quarkus Dependency Injection mechanism.
There are a couple of actions we can consider addressing this issue, such as remove the @Service annotation from PushMessageHandler or register the PushMessageHandler bean only if it is not already present.
Anyway, a full support for quarkus-spring is currently not planned because out of the scope of the extension, but we may consider it for the future, if there will be interest on it.
Out of curiosity and to better understand your use case, do you mind sharing the reasons for you to use Spring with Quarkus instead of the built-in DI or other suggested extension (e.g. Panache)?


reporter: extend lifetime for cached elements

Similar to the reported issue https://github.com/open-telemetry/opentelemetry-ebpf-profiler/issues/248 around lifetime of executables, the same issue happens for frames. So keep cached frame information alive.

👋  As discussed in https://github.com/open-telemetry/opentelemetry-ebpf-profiler/issues/248, using GetAndRefreshKeys() for the frames outer cache solves the issue for UNREPORTED / UNRESOLVED frames, however, for long / forever running large executables, there is the potential of increasing the inner map (map[libpf.AddressOrLineno]sourceInfo) without limit.
I'm personally onboard with merging this first then working on the inner map size issue, just wanted to highlight the tradeoff that was raised in https://github.com/open-telemetry/opentelemetry-ebpf-profiler/issues/248#issuecomment-2488330374 !

Thanks for pointing this out. As mentioned, there is a risk of increasing the inner map (map[libpf.AddressOrLineno]sourceInfo) without limit. I do also agree, that limiting this inner map should be a dedicated issue/task.


[NF] BH Curve Extrapolation

Hello everyone,
@jgdedamas and I will start working on the BH curve extrapolation method. In particular, we would like to implement the Langevin extrapolation method.
For the coupling with FEMM, the idea would be to gave a very large number of point based on this extrapolation as the BH curve input, such that FEMM never has to extrapolate the data itself. As written in the FEMM manual:

It may also be important to note that FEMM extrapolates linearly off the end of your B-Hcurve if the program encounters flux density/field intensitylevels that are out of the range of thevalues that you have entered. This extrapolation may make the material look more permeable thanit “really” is at high flux densities.  You have to be careful toenter enough B-H values to get anaccurate solution in highly saturated structures so that the program is interpolating between your29
entered data points, rather than extrapolating.

Feedbacks welcome,
BR

Hello Raphaël,
I think if the BH curve is well defined the linear FEMM extrapolation should be sufficient. I.e. if the curve is given up to the point where the material is completely polarized, the differential permeability will be 1. So linear extrapolation will be enough.
Rather we have to check that the polarization has settled at the end of the given curve.
BTW: How does this Langevin method work? Do you have some refs?
BR

Hello @SebGue,
We have reason to think that the extrapolation method could play a significant role on magnetic force results. Thus, we would like to check that by ourselves.
Different models (including Langevin method) are described in this paper:
https://www.infona.pl/resource/bwmeta1.element.baztech-b5337e23-d5ad-4315-9872-06811fb079a1
BR

Hello,
so your actual goal is to find some good curve fitting function for the BH curve.
Then I will come back to you for some related issue ;-)
Best regards, Sebastian

The last PR enables to use analytical defined BH curves. In particular, the Langevin model is implemented. It uses two parameters "Bs" and "a". In the following example, the parameter "a" is modified:

I have also started a "fitting" algorithm: from the input BH_curve data (from the previous workflow), the user can activate a fitting process. Then, the parameters of the model (such as previous Langevin's model) are fitted in the least square sense.
This fitting process enables advanced extrapolation methods (in addition to the linear extrapolation from FEMM).


compose watch combined with depends_on can lead to failure of dependencies

I've started to use 'watch' feature for one project, but it fails every time when I change files from state A to state B and then back to state A.
Steps to reproduce:

Compose yaml (truncated):

apiserver:
  build:
    context: ./backend
    dockerfile: api.Dockerfile
  container_name: apiserver
  pull_policy: build
  restart: always
  depends_on:
    - "db"
    - "rabbit"
  expose:
    - 3000
  volumes:
    - /etc/localtime:/etc/localtime:ro
  develop:
    watch:
      - path: ./backend/
        action: rebuild

analytics:
  build:
    context: ./backend
    dockerfile: analytics.Dockerfile
  container_name: analytics
  pull_policy: build
  restart: always
  depends_on:
    - "db"
    - "rabbit"
  volumes:
    - /etc/localtime:/etc/localtime:ro
  develop:
    watch:
      - path: ./backend/
        action: rebuild

# ...
# more services here. No more "depends_on" statements.

Run watch: docker compose watch.
Edit file under ./backend folder, e.g. add new line.
Watch detects changes and rebuilds both services as expected.
Edit same file under ./backend folder bringing it to the state it was before step 3 (remove new line).
Watch starts to rebuild both services, but fails:

...
service "apiserver" successfully built
Failed to recreate service after update. Error: Error response from daemon: Conflict. The container name "/eaad56074ed9_db" is already in use by container "30b1ad6dcf9135f90dcef865d7de2bfaf1e6a2faa4b3c1ac56351d97e18cf2fa". You have to remove (or rename) that container to be able to reuse that name.
WARN[0011] Error handling changed files for service apiserver: Error response from daemon: Conflict. The container name "/eaad56074ed9_db" is already in use by container "30b1ad6dcf9135f90dcef865d7de2bfaf1e6a2faa4b3c1ac56351d97e18cf2fa". You have to remove (or rename) that container to be able to reuse that name.
Failed to recreate service after update. Error: Error response from daemon: No such container: 30b1ad6dcf9135f90dcef865d7de2bfaf1e6a2faa4b3c1ac56351d97e18cf2fa
WARN[0012] Error handling changed files for service analytics: Error response from daemon: No such container: 30b1ad6dcf9135f90dcef865d7de2bfaf1e6a2faa4b3c1ac56351d97e18cf2fa

As you can see, the error mentions container db. This container dies.
Looks like compose is trying to restart dependencies after rebuilding apiserver but somehow conflict occurs.
The problem does not occur when I run watch only for one service (docker compose watch apiserver)
This might be related to https://github.com/docker/compose/issues/9014
Versions:
# kernel:
Linux 6.8.2-arch2-1

# docker compose version
Docker Compose version 2.26.1

# docker version
Client:
 Version:           26.0.0
 API version:       1.45
 Go version:        go1.22.1
 Git commit:        2ae903e86c
 Built:             Sat Mar 23 15:27:08 2024
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          26.0.0
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.22.1
  Git commit:       8b79278316
  Built:            Sat Mar 23 15:27:08 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.14
  GitCommit:        dcf2847247e18caba8dce86522029642f60fe96b.m
 runc:
  Version:          1.1.12
  GitCommit:
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

oops, wrong repo. Sorry!


Extend CpsNotificationConfig to ignore duplicate messages

also add style
.cps-toast-message-details {
  white-space: pre-line;
}

https://github.com/AbsaOSS/cps-shared-ui/pull/342


add support for matlab

I think it is possible for matlab proxy working in vscode-jupyter environment.
The related issue is here matlab proxy unable to run on vscode-jupyter
here's what's returned when i tried to use matlab proxy on vscode-jupyter
I use vscode-jupyter to launch matlab kernal.
It returns :
Kernel needs to be started by a Jupyter Server. Please use JupyterLab or Classic Notebook while using MATLAB Kernel for Jupyter.

Thanks for filling this issue and sorry you are running into this
Please can you provide steps to replicate this issue (with instruction to setup matlab and the like)

Kernel needs to be started by a Jupyter Server. Please use JupyterLab or Classic Notebook while using MATLAB Kernel for Jupyter.

where is this displayed, please could you provide a screenshot

Closing this issue as its been over 4 weeks, since the information was requested.
We'll be happy to reopen the issue when the requested information has been provided.

I am having a similar issue.
steps to replicate:

Install matlab as per their instructions and add to PATH: https://www.mathworks.com/help/install/ug/install-products-with-internet-connection.html
install jupyter-matlab-proxy using pip to current python environment.
create a new notebook in vscode and select kernel MATLAB Kernal (my_env). This option appears in the VS code kernel select menu under "Select Another Kernel > Jupyter Kernel > MATLAB Kernel (my_env)"
try to run cell with matlab code and error message appears in output section.

log output:
05:04:42.228 [info] Handle Execution of Cells 0 for ~/Documents/Research/energy_graphs.ipynb 05:04:42.229 [debug] start the kernel, options.disableUI=false for ~/Documents/Research/energy_graphs.ipynb 05:04:42.230 [debug] Execution Request Sent to Kernel for cell 0 05:04:42.234 [debug] Start cell 0 execution @<PHONE_NUMBER>234 (clear output) 05:04:42.234 [info] Kernel acknowledged execution of cell 0 @<PHONE_NUMBER>234 05:04:42.236 [info] End cell 0 execution @<PHONE_NUMBER>236, started @<PHONE_NUMBER>234, elapsed time = 0.002s 05:04:42.236 [debug] Cell 0 executed with state Success
Note that I was able to make this work by starting jupyter notebook server with the kernel first and then connecting to the existing server in vs code instead of selecting a kernel


User help tooltips

Please test and see if the hints helpful. I'll make an option to turn them on only when needed soon. Should there be tooltips on input fields or other things as well? How long should the wait time for the tooltip to appear be?

making another pull request pointing to master...


gha: Simplify integration test job

The build.sh script was mainly for travis, which is removed a while back. Additionally, the build and precheck targets are already run in other CIs (e.g. docker build, and lint-go), hence we can just run make integration-tests directly from GHA.
The runtime is reducing by half (from ~30m to ~14m).

/ci-integration

/test

/ci-integration

/test


Add tooltips

I couldn't add tooltips to the two last tabs

Wait don't merge yet, I'll add the rest...

Ah yes, the world name text box is made of world name. What benefit does this add apart from cluttering the interface?

Ah yes, the world name text box is made of world name. What benefit does this add apart from cluttering the interface?

I'm just going to close this.


[Enhancement] Refine profile to support visualization refactor(2)

This pr is an continuation work of https://github.com/StarRocks/starrocks/pull/29063, and the main objectives of this pr are:

Remove core level profile
Change spill metrics from profile hierarchy to counter hierarchy for better analysis.
Fix the wrong calculation of output rows for Join Node in text-based profile analysis

What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE Incremental Coverage Report]
:disappointed: fail : 2 / 5 (40.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ExplainAnalyzer.java
0
2
00.00%
[827, 828]

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
2
3
66.67%
[2526]

[BE Incremental Coverage Report]
:heart_eyes: pass : 25 / 26 (96.15%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exec/pipeline/pipeline_builder.cpp
0
1
00.00%
[247]

:large_blue_circle:
src/exec/spill/spiller.cpp
25
25
100.00%
[]

[BE Incremental Coverage Report]
:heart_eyes: pass : 25 / 26 (96.15%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exec/pipeline/pipeline_builder.cpp
0
1
00.00%
[247]

:large_blue_circle:
src/exec/spill/spiller.cpp
25
25
100.00%
[]

[FE Incremental Coverage Report]
:heart_eyes: pass : 4 / 5 (80.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/SessionVariable.java
2
3
66.67%
[2550]

:large_blue_circle:
com/starrocks/sql/ExplainAnalyzer.java
2
2
100.00%
[]

[BE Incremental Coverage Report]
:heart_eyes: pass : 25 / 26 (96.15%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exec/pipeline/pipeline_builder.cpp
0
1
00.00%
[247]

:large_blue_circle:
src/exec/spill/spiller.cpp
25
25
100.00%
[]

@Mergifyio backport branch-3.1


Error on build after updating to 0.13.0 from 0.12.3

Current Behavior

Expected behavior
no build errors
Additional context
@react-google-maps/api @react-google-maps/marker-clusterer @react-google-maps/infobox packages affected, rolling back to 0.12.3
Your environment

Software
Version(s)

TSDX
0.13.0

TypeScript
3.8.3

Browser

npm/Yarn
1.22.4

Node
13.11.0

Operating System
MacOSX

ups, this is node 13.9 issue: https://github.com/babel/babel/issues/11216

https://github.com/nodejs/node/issues/32107

Ok, was gonna say I've never seen that error before and no Babel deps were updated this release 😅
Seems like this happens if you have some Node 13.x and Babel 7.8.3 because of churn on conditional exports


EL7 use python2-pip package name

It turns out that the package name has changed in the epel repository.
closes #348
Signed-off-by: David Caro<EMAIL_ADDRESS>

This certainly would do the job. I wonder though if it would not be a good idea to allow the user to pass on the package name as a parameter. This way, it may be possible to simplify the code a bit.

I agree that is a good idea, and that it would have allowed me to work around the issue, though to me that should be the last resource for the user,it should pick the good package by default.

Thank you for your contribution! Could you please add a spec test so that we can merge this change.

@schwicke The package name should definitely be a parameter, though we also want to have sane defaults for our supported platforms so that when you use the module, it does the right thing out of the box without having to specify data.

You probably missed #346 when writing this pull request. Feel free to reuse the test I wrote.
I would recommend versioncmp() over a regex on the wrong fact. You can use $::operatingsystemmajrelease instead.

Hi,
Could someone please do a functional test of the code from https://github.com/stankevich/puppet-python/pull/347 and verify that it works to solve this problem?

@david-caro Thanks for the contribution though going with PR #347 since it had spec tests. We could still use your help by verifying that the code in PR #347 works.

@ghoneycutt I did not see it, I think I searched on the issues but not the PRs. No problem 👍

@ghoneycutt fully agree, I think the  module should both provide sensible (working) defaults and the option to name the package as a parameter. That would be nice to have.


fix: update wooting rules

It should maybe be noted that this is not just adding or tweaking things, it is updating the rules to match the full current list directly provided by Wooting. Dunno if that changes anything about when/how to merge

Should we be adding extra users? Or would it make sense for me to modify the group to be wheel instead?

I think we should be trying to get users into an input or plugdev group rather as these rules are written rather than using wheel. It’s better because if someone sets up a non-admin user for gaming etc, they can still have access to the devices. On Apr 29, 2023, at 9:54 AM, Jorge O. Castro @.***> wrote:
Should we be adding extra users? Or would it make sense for me to modify the group to be wheel instead?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

If this may take a while to sort out due to important long term maintenance philosophy, could lines 59-70 be merged independently since they are for a new device doing its own thing? I had not realized this would not be a trivial addition to fix an entirely unsupported device, and I would like to be able to configure my keyboard. Does the same concern apply to the new device by adding / messing with a new group?

I was wrong that input group is missing in Silverblue... but I'm not wrong that there's something weird about it.
Thus I'm trying to understand the situation with groups on Silverblue... on my current ublue system:

systemd-sysusers is the process that creates system users/groups, this should usually happen on first boot? maybe it updates if there's additions to /usr/lib/sysusers.d

rpm-ostree has the "managed" groups in /usr/etc/group (eg, i think this get created/appended when we install packages in our Containerfile builds) ... rpm-ostree apparently merges this with /etc/group somehow (just read this, not sure what code makes it happen)

there also exists /usr/lib/group which is where, as I care about with respect to the PR above, input group resides (not in /etc/group or /usr/etc/group)

getent group will show the full, merged set of groups in a system... and genteng group | grep input shows for certain, the system can resolve input:x:104:  from /usr/lib/group so... we can at least read that...

but here's the crazy part... sudo usermod -a -G input MYUSERNAME succeeds, or at least says it does (using an obviously non-existing group fails with group does not exist)... BUT..... even after rebooting, my MYUSERNAME is NOT a member of the input group...

So... it seems like shadow utils is not working right possibly? it should probably create a masking input:x:104:MYSUSERNAME line in /etc/group when the above usermod command runs... since clearly /usr/ is read-only...
this is where i think its time to test on pure silverblue.
And... I intend to break out the group changes from this PR so that this PR will just contain the added device rules, not a change to groups... we should solve group mysteries in another issue.

Changed my mind... I've submitted a simplified PR ( #30 ) with just the new wooting rules...
We can keep this PR until the groups concern is resolved.

Let's enumerate our options.

If we add all users to input group as originally planned, it's the exact same as opening device access to everybody. So there's no security difference.

Opening device access to all users means we don't need to add users to a silly input group. So that's way cleaner. It's how Valve solved it.

Even if adding all users to read/write privilege for the keyboard devices, are there really any security implications? The user is already typing at the keyboard. They know what they're typing. And malware has more important things to do than hunting for wooting users to read the device to keylog all the cool wootbros in the world.

The last option is to just not do anything. Users who aren't in input will have to add themselves to it, and take full responsibility for that security.

For that reason, I think it makes sense to do option 2. Because option 1 sure as hell doesn't make sense since it's an identical outcome with MORE work for us.

STOP THE PRESSES!
THE MYSTERY HAS BEEN SOLVED!
TL;DR

@KyleGospo was the original contributor of 80-wooting.rules  ( see https://github.com/ublue-os/udev-rules/commit/eef7b5ae1fe46e8c5c5f376866aa0b83f3edda00  )
He explicitly chose to use wheel instead of input (which Wooting does by default) because

input is not default on Fedora
wheel meant only admins could reconfigure the keyboard

this means we have no "bug" to "fix"

My proposal: Add a comment explaining the rationale here and call it done. Future PRs for wooting should be simple.
Full story ... go read a lot of discord chat...
https://discord.com/channels/1072614816579063828/1072617059265032342/1107549060237361192


[V3] Use consistent naming for method references

Looking at the existing Ruby exercises, there are a couple of different ways methods are referred to. I've seen:

'Please implement the pass? method'
'Please implement the LogLineParser.log_level method'
'Please implement the Lasagna#remaining_minutes_in_oven method'

There are several places where methods are being referred to, but most notably they are referred to in the instructions.md files and the stub implementation files (and occasionally the hints.md files). It would be nice to use a uniform way of referring to methods.
I'm fairly sure that @iHiD wants to use <CLASS>.<METHOD> for class methods, and <CLASS>#<METHOD> for instance methods. So I'd suggest normalizing to those.

This has been normalized. Closing.


docs: polish ProdMon examples

ProdMon overview example

add imports for dependencies: tensorlfow, gradio, weave
add wanbd login and make sure to set entity != Tim
wording polish: step index, typos, clarification
TODO: currently erroring on gradio authentication? will double-check

cleaned up examples! there's a new error in the last cell of the ProductionMonitoring one that looks like gradio authentication/setup/maybe a changed api?
@tssweeney any chance you could take a look? also possible i'm not installing gradio correctly

@scottire verified ProdMon gradio works with a clean env, this should be good to go!


rework dram hash encode/decode to account for 0-width fields

This PR does two things:

fixes the L2/DRAM hashing to account for fields that may have 0-width (CCE, slice, bank, and set indices)
prevents aliasing of blocks outside the L2 capacity

The purpose of the hash function is to distribute the L2 blocks evenly across the L2 slices/banks. This algorithm distributes blocks first to CCEs, then across slices and across banks (i.e., slice 0, bank 0 - slice 1, bank 0 - slice 0, bank 1 - slice 1, bank 0, etc.).
By definition (at least for POT number of CCEs), this algorithm guarantees that if there are N total sets across all L2s, then blocks [0, N) will remap to the same range and not alias outside the the L2 capacity.
Number of CCEs can be NPOT, but number of slices, banks, and sets must be POT >= 1.

Put a comment with the buggy xsim version


Make NBT serialisation methods follow the conventions

The NBT serialisation methods are currently a mess. Most of them were mapped before the conventions were a thing, and as a result they're pretty inconsistent.
For example, the conventions say that you should use read/write for non-static methods like the ones in BlockEntity - but BlockEntity uses fromTag and toTag instead. (The names should also probably use -Nbt instead of -Tag, as that seems to be the new standard.)
Should we make a bunch of PRs fixing this, or change the conventions to adapt to current naming? (I'd prefer the former for clean mappings, but the latter is better for modders.)

I would be in favor of changing the conventions. That part was written 2 years ago anyway.
If the parameter is going to be a Tag or a CompoundTag, then keeping fromTag and toTag is better imo.
As for confusion between nm.nbt.Tag and nm.tag.Tag, I don't think you are deserializing from datapack tags anyway, and I don't think toTag returning nm.tag.Tag is supposed to happen either.

I would be in favor of changing the conventions. That part was written 2 years ago anyway.
If the parameter is going to be a Tag or a CompoundTag, then keeping fromTag and toTag is better imo.
As for confusion between nm.nbt.Tag and nm.tag.Tag, I don't think you are deserializing from datapack tags anyway, and I don't think toTag returning nm.tag.Tag is supposed to happen either.

As for confusion between nm.nbt.Tag and nm.tag.Tag, I don't think you are deserializing from datapack tags anyway, and I don't think toTag returning nm.tag.Tag is supposed to happen either.

There have been multiple times where I have had to use both classes in the same class, and I am only able to import one. They should have different names.

As for confusion between nm.nbt.Tag and nm.tag.Tag, I don't think you are deserializing from datapack tags anyway, and I don't think toTag returning nm.tag.Tag is supposed to happen either.

There have been multiple times where I have had to use both classes in the same class, and I am only able to import one. They should have different names.

If the parameter is going to be a Tag or a CompoundTag, then keeping fromTag and toTag is better imo.

The format is NBT, though. When serializing to JSON, you wouldn't call that method toObject, you would call it toJson because the format is JSON, and that is what you care about, not the arbitrary name that the format chooses to call its objects/elements/tags/nodes/properties/values/entries.

As for confusion between nm.nbt.Tag and nm.tag.Tag, I don't think you are deserializing from datapack tags anyway, and I don't think toTag returning nm.tag.Tag is supposed to happen either.

Until you work with items or entities where the phrase "get tag" could refer to either getting an NBT tag or a datapack tag. Really, the only time this isn't an issue is with blocks, because they don't store NBT.
"Tag" is not an ideal name for anything because it's so generic, but in the datapacks case it sorta works because really it is quite generic. But in the case of NBT, calling it just a "Tag" is entirely unhelpful because not only does the word "tag" not a term that entirely makes sense for what it is, it's also a generic term that is also used by the same game for a different concept and often in the same context as NBT.
It would be bad enough if NBT elements were called something unconventional like a "potato" instead of "tag". But if you also have potatoes in the game that can store NbtPotatoes, then why would you not clarify which you're referring to? Or why would you even bring up the arbitrary element name when it is not at all relevant to someone who wants to store "NBT" and will be searching for relevant methods to the name of the format.
I propose two options for class renames:

Consistency with GSON

Tag -> NbtTag (Subclasses can either remain CompoundTag or become CompoundNbtTag. Generally it's okay to drop a prefix for subclasses)

No, this is not redundant. NBT is the format name. Tag is the type. Yes, that is Named Binary Tag Tag. Named Binary Tag is the format. Tag is the type. Compare to JsonObject, which is a JavaScript Object Notation Object. JSON is the format, Object is the type.

Tag -> Nbt

Since there is no element of NBT that is not a tag, the Tag suffix is potentially unnecessary, and doesn't need to be used at all.
Subclasses are tricker here, would they become CompoundNbt if Nbt is a noun or NbtCompound if it is a compound of format NBT? For this reason, I'd prefer the first option, plus it would be consistent with GSON.

If the parameter is going to be a Tag or a CompoundTag, then keeping fromTag and toTag is better imo.

The format is NBT, though. When serializing to JSON, you wouldn't call that method toObject, you would call it toJson because the format is JSON, and that is what you care about, not the arbitrary name that the format chooses to call its objects/elements/tags/nodes/properties/values/entries.

As for confusion between nm.nbt.Tag and nm.tag.Tag, I don't think you are deserializing from datapack tags anyway, and I don't think toTag returning nm.tag.Tag is supposed to happen either.

Until you work with items or entities where the phrase "get tag" could refer to either getting an NBT tag or a datapack tag. Really, the only time this isn't an issue is with blocks, because they don't store NBT.
"Tag" is not an ideal name for anything because it's so generic, but in the datapacks case it sorta works because really it is quite generic. But in the case of NBT, calling it just a "Tag" is entirely unhelpful because not only does the word "tag" not a term that entirely makes sense for what it is, it's also a generic term that is also used by the same game for a different concept and often in the same context as NBT.
It would be bad enough if NBT elements were called something unconventional like a "potato" instead of "tag". But if you also have potatoes in the game that can store NbtPotatoes, then why would you not clarify which you're referring to? Or why would you even bring up the arbitrary element name when it is not at all relevant to someone who wants to store "NBT" and will be searching for relevant methods to the name of the format.
I propose two options for class renames:

Consistency with GSON

Tag -> NbtTag (Subclasses can either remain CompoundTag or become CompoundNbtTag. Generally it's okay to drop a prefix for subclasses)

No, this is not redundant. NBT is the format name. Tag is the type. Yes, that is Named Binary Tag Tag. Named Binary Tag is the format. Tag is the type. Compare to JsonObject, which is a JavaScript Object Notation Object. JSON is the format, Object is the type.

Tag -> Nbt

Since there is no element of NBT that is not a tag, the Tag suffix is potentially unnecessary, and doesn't need to be used at all.
Subclasses are tricker here, would they become CompoundNbt if Nbt is a noun or NbtCompound if it is a compound of format NBT? For this reason, I'd prefer the first option, plus it would be consistent with GSON.

I'd personally like to the move towards seperating the two names.
FormatType scheme feels to be more natural sounding english. Atleast how I have learned english, modifiers are applied before a word, such as an orange cat. Similarly I belive this would apply to the classes as you are presenting a type in a specific format, where the format is the modifier. e.x: JsonArray, NbtList.
Other precendent exists in support of the FormatType scheme in DataFixerUpper as mojang has chosen the JsonOps name for the DynamicOps implementation.
For the method names, I would agree with a to/fromNbt standard.

I'd personally like to the move towards seperating the two names.
FormatType scheme feels to be more natural sounding english. Atleast how I have learned english, modifiers are applied before a word, such as an orange cat. Similarly I belive this would apply to the classes as you are presenting a type in a specific format, where the format is the modifier. e.x: JsonArray, NbtList.
Other precendent exists in support of the FormatType scheme in DataFixerUpper as mojang has chosen the JsonOps name for the DynamicOps implementation.
For the method names, I would agree with a to/fromNbt standard.

For the copious amounts of discussion on this topic: see #1077, #1078, and #1275

For the copious amounts of discussion on this topic: see #1077, #1078, and #1275

Ok I see. You are right Prospector, it makes more sense to use Nbt, both for the serialization function and for the tag types. :)
We could also go for Tag -> NbtElement for even more Gson consistency, and NbtNumber, NbtCompound, ... for the subtypes.

Ok I see. You are right Prospector, it makes more sense to use Nbt, both for the serialization function and for the tag types. :)
We could also go for Tag -> NbtElement for even more Gson consistency, and NbtNumber, NbtCompound, ... for the subtypes.

Linking to #2037

Has been fixed


ONNX Operators Implementation

Please redirect me to the kernel level code (Implementation) of ONNX Operators by nnabla.
Please help me in understanding at nnabla from developer perspective.

Sorry late response.
The code involved onnx operators in placed in:
https://github.com/sony/nnabla/tree/master/python/src/nnabla/utils/converter/onnx
exporter.py: implements a mapping from nnabla to onnx operators.
importer.py: implements a mapping from onnx to nnabla operators.
utils.py some misc helper functions.

I hope you are satisfied with this answer.
Please create new github issue if you have questions.


Question: Accessing BlazorCodeMirror javascript object in javascript

Hey there,
I know that the BlazorCodeMirror is a Blazor wrapper over the underlying CodeMirror javascript objects and code.
So I want to be able to access the CodeMirror javascript object from my js code.  Is there a convention or simple means of getting a handle on the CodeMirror Editor js object in my javascript?  I want to be able to hook into the underlying CodeMirror js code to manipulate it accordingly, then use Blazor JSInterop to trigger these behaviours from user interaction.
Cheers

Hey @domingoladron, you can use the getCmInstance() export for this purpose.
First, import the method:
import { getCmInstance } from "./_content/GaelJ.BlazorCodeMirror6/index.js"

Then pass the instance's ID to getCmInstance():
var view = getCmInstance(id).view;

You'll then have access to the object. Hope that helps!

Aw, that's mint!  Cheers for the great answer and rapid turnaround.  Super helpful!

One last thing.  HOW do I get the ID of the current CodeMirror from my Blazor code so I can pass it along to the javascript?  I note the "ID" property of the CodeMirror6Wrapper has been removed in more recent versions of the library.

CodeMirror6Wrapper has a Setup property of type CodeMirrorSetup, which exposes a public string Id.

Ah, there it is!  That's great.  Thanks again.


cmake-ide on mac crashes

Having an issue which is think is similar to a other mac user issues. My packages work fine (rtags, irony etc) before i bring in cmake-ide but when i do it will load up fine and crash after i use rtags a bit. I have tried running rtags from a separate terminal and when i do a new rtags daemon is started in emacs regardless. I have the package running perfectly on linux with separate terminal rtags daemons and having emacs start one automatically in emacs so i know it's not to do with my test projects.
Here is the message i get when i load up a file.
cmake-ide [Sun Aug  5 02:58:22 2018]: Running cmake for src path /Users/gavin/Dropbox/programming/acc_cpp/unix-source/chapter07/exe/exe5/ in build path /var/folders/pj/v2sjfs5j5973950byfn0k6qm0000gn/T/cmakeYAEcv0/
cmake-ide [Sun Aug  5 02:58:25 2018]: Finished running CMake
cmake-ide [Sun Aug  5 02:58:25 2018]: Converting JSON CDB /var/folders/pj/v2sjfs5j5973950byfn0k6qm0000gn/T/cmakeYAEcv0/compile_commands.json to IDB
cmake-ide [Sun Aug  5 02:58:25 2018]: Setting flags for file /Users/gavin/Dropbox/programming/acc_cpp/unix-source/chapter07/exe/exe5/grammar.cc
cmake-ide [Sun Aug  5 02:58:25 2018]: Running rc for rtags
I know you don't have a mac so it's more just to see if anyone else has this problem and has solved it.

I tagged it with "help wanted" in case someone with a mac can help.


ImageMagick and Assim Examples

I"m developing some examples that involve ImageMagick and Assim.
However, I think the additional complexity is probably not warranted for OpenGLAda so I plan to setup a separate repository for at least these examples. My intended name is OGL_AdaExamples.
Any suggestions or recommendations are welcome.

Eventually, it may be a good idea to put all examples in an own repository. However, having them in the main repository is kinda easier as they also serve as tests.
Anyway, examples that involve additional libs should certainly be in an own repo, so I (over half a year later) approve of your actions :).


KeyError: '1; 2; 3; 4; 5; 6; 8; 10'

When i use FewShotPromptTemplate function, if the examples contain "{" and "}" characters, I get this error.
Like this: {"question": "A = {1; 2; 3; 4; 5; 6; 8; 10}; B = {1; 3; 5; 7; 9; 11}"}
How can i fix it. Thank you!!!

You can escape the braces - use "{{" and "}}".


use CVODES error string instead of numeric flag in error messages

This PR addresses #1039 by replacing flag with strings from CVODES.
Summary
The replacement happens inside the checking functions. With added cvodes_check we call the library functions that map flag to error string constant.
Tests
All CVODES  unit tests with error throw checks.
Side Effects
na
Release notes
More informative error messages for ODE solvers.
Checklist

[x] Math issue #1039.

[x] Copyright holder:  Metrum Research Group
By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

@syclik do you want to take a look of this one?

@wds15 would you like to review it? thx

This is ready for review. @SteveBronder @rok-cesnovar any of you have time for this? It's a straightforward impl.

thanks a lot @rok-cesnovar


Tooltip remains after parent element get removed

Bug, feature request, or proposal:
This plunkr example http://plnkr.co/edit/WjzlmBYs7Yf2IgAXbERf?p=preview show how removing the parent buttons containing the md-tooltip directive doesn't remove the generated tooltip element from the view.
What is the expected behavior?
As the button get removed from the view, the related md-tooltip element should be removed as well
What is the current behavior?
The tooltip remain visible on the screen
What are the steps to reproduce?

using an ngFor for dynamically generates buttons containing a tooltip
as the array of elements, linked to the ngFor, changes, the already displayed tooltip elements persist in the view.

Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd
http://plnkr.co/edit/WjzlmBYs7Yf2IgAXbERf?p=preview
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, browsers are affected?
Is there anything else we should know?

Already opened an issue about it (#1111).


Implements the functionality to customize the logging based on config file

Summary of Changes
In order to have the proper monitoring in place, based on the internal requirements it would be much easier to have a configurable configuration file for logging.
Following is the example:
[loggers]
keys=root,amundsenmetadata,werkzeug

[handlers]
keys=consoleHandler

[formatters]
keys=amundsenFormatter

[logger_root]
level=DEBUG
handlers=consoleHandler

[logger_werkzeug]
level=DEBUG
handlers=consoleHandler
qualname=werkzeug
propagate=0

[logger_amundsenmetadata]
level=DEBUG
handlers=consoleHandler
qualname=amundsenmetadata
propagate=0

[handler_consoleHandler]
class=StreamHandler
level=DEBUG
formatter=amundsenFormatter
args=(sys.stdout,)

[formatter_amundsenFormatter]
format=%(asctime)s.%(msecs)03d [%(levelname)s][%(name)s] %(module)s.%(funcName)s:%(lineno)d (%(process)d:%(threadName)s) - %(message)s
datefmt=%Y-%m-%dT%H:%M:%S%z

Tests
NA
Documentation
NA - Adds required comments
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes make test

Codecov Report

Merging #92 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #92      +/-   ##
==========================================
+ Coverage   77.67%   77.69%   +0.02%
==========================================
  Files          19       19
  Lines         954      955       +1
  Branches       91       91
==========================================
+ Hits          741      742       +1
  Misses        187      187
  Partials       26       26

Impacted Files
Coverage Δ

metadata_service/config.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@feng-tao would you mind reviewing this. We needed to format the logs a bit differently and sometimes in JSON format. So I thought would be nice to make it highly customizable. :)

lgtm, thanks @verdan , also FYI, I will be OOO for 3 weeks starting this weekend and slow to response. Feel free to tag @jinhyukchang or other folks if you have others pr.


:sparkles: Support defects in the SiDB Gate Designer

Description
This PR extends the SiDB Gate Designer to support defects.
Checklist:

[x] The pull request only contains commits that are related to it.
[x] I have added appropriate tests and documentation.
[ ] I have made sure that all CI jobs on GitHub pass.
[ ] The pull request introduces no new warnings and follows the project's style guidelines.

We still need to get the Windows CI up and running again, but besides that, this PR looks good to me.


Add type checking to CI

This setup with tox.ini should make the mypy checks run after the (unit) tests for each python/django env.

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

Project coverage is 94.46%. Comparing base (41c2366) to head (f64b63b).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #30   +/-   ##
=======================================
  Coverage   94.46%   94.46%
=======================================
  Files          17       17
  Lines         488      488
=======================================
  Hits          461      461
  Misses         27       27

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


Need connection to different container registries

Expected behavior
Kitematic allows configuration and pulling from a variety of Docker container repositories
Actual behavior
Kitematic allows configuration and pulling ONLY from DockerHub repository
Information about the Issue
We push our containers to quay.io

@Jaff We would need to build-in the authentication functionality of quay.io (or other registry)
We aim to support Docker Hub as best as we can and rely on the community to help build other registries. Feel free to write a plugin-like add-on for Kitematic to support quay.io


TypeScript doesn't see a new symlink in node_modules

TypeScript Version:  2.7.0-dev.20171029
TypeScript doesn't see a symlink inside node_modules when executed twice. The symlink is created after the first execution of typescript. It seems like some caching issue.
Code to reproduce is in this repo: https://github.com/pnpm/outdated/tree/experimenting. You have to install pnpm and run pnpm install && npm test. It will fail only the very first time. Next executions of npm test will work, even if the symlink (at node_modules/@pnpm/outdated) will be removed manually.
Fail can be seen in CI: https://travis-ci.org/pnpm/outdated/jobs/295085685#L521
I used ls node_modules/@pnpm to demonstrate that the symlink is there before tsc is executed.
For some context. I created a tool called package-preview which packs and installs locally the tested package before running tests. So unit tests are testing a real production-like version of the package.
When a project is written in typescript, package-preview will compile the project with typescript, pack it, install it in a different folder and symlink it to the project's node_modules. Then it calls typescript again, to run the tests, which import the "real thing", the pseudo-published package... (that is when typescript fails)

I see many caches in the typescript repo, is there some flag that I can use to make typescript ignore cache? Or is there a command to ignore it?

Running tsc on the command line twice shouldn't involve any caching. Are you sure that the file system content is the same both times you run it?

The node_modules content differs. The first time I run it, there is no symlink in node_modules/@pnpm/outdated. The symlink is created before it is called the second time.

tsc shouldn't perform any writes to node_modules. It sounds like some other tool is creating the link. So if you run tsc twice in a row without intervening steps you should see the same result twice.

Yes, another tool creates the symlink (the package-preview)
First time tsc is called when the package is packed. The package is then unpacked in another directory and linked into node_modules. Then tsc is called second time to run the tests. The tests are importing the package by name (because the backage is symlinked into node_module by then)

It sounds like the error doesn't have anything to do with the number of times you run tsc. The result of tsc should be determined solely by the content of the file system at the time it is run. Based on that, you should be able to get a repro for this issue that consists only of creating some files (and symlinks) and then running tsc.

Alright, I'll try to make a simpler example. Probably tomorrow.

There is no issue in TypeScript. I thought npm pack runs prepublish scripts but it doesn't. So tsc was called only once, the second time, and .d.ts. files were not there. So the error was not because typescript did not see the symlink. It was because it did not find the d.ts. file.


Support SM2 csr for cfca certificate?

cfca limit the request csr format like：

Is there any Chinese national standards indicating this format? Or this is just what CFCA does in a 'non-standard' way?

CFCA and 360 browsers can communicate using ecc-sm4-sm3. Therefore, many companies need to apply for a national double certificate from cfca. Otherwise the communication is unsuccessful and the 360 browser is limited.

or can you help me ,  This is the certificate request file I generated. How can I remove the SET and reserved printablestring? You can refer to the function X509_ATTRIBUTE_set1_data.

Well, OpenSSL can only support what national standards specify instead of following what a company does, even that company is CFCA. So I may ask some other Chinese CAs to see if it's possible to use current OpenSSL version to generate a CSR that they can proceed to sign.

or can you help me

I could help, depending on when I get adequate spare time...

Context[] is stored in the attribute field, which is equivalent to extended information, so it can be controlled by configuration parameters.

Another choice is that you can ask CFCA to use current OpenSSL version to replace their 'whatever-custom-built' CA infrastructure, and you will have no problem ;-)

I am too small.

@ygm521, anyone can ask even if it's ignored.


Return created for Integrations

We already receive lastUpdated for Integrations, which is great and is currently used in the Dashboard. It looks strange when an Integration has not been updated, as that entire column remains blank. Please add created as a property that is included as part of the Integration object.
An example of where we would use both the created and lastUpdated properties for an Integration (this is the Dashboard):

@kahboom I've added CreatedDate and LastUpdated on Connection and Integration.

Ty @KurtStam !


ICRC-25: Introduce method to query granted permissions

This PR introduces the method icrc25_granted_permissions method to query currently granted permission scopes.
It also renames icrc25_request_permission to icrc25_request_permissions so that it better reflects that multiple different permissions can be requested / granted.

LGTM, but I guess icrc25_revoke_permission should also eventually become icrc25_revoke_permissions, no?

Yes, this was simply an oversight. Thanks, fixed.


ActiveAdmin password_digest column bug

If draft:model sees that a column is named password_digest, it should permit the attribute password in ActiveAdmin's dashboard rather than password_digest.

Closing since we're no longer using active_admin.


Cleanup of Kotlin entity codegen with Schema type hierachy.

(Builds up on #5728 which adjusts the goldens to allow this change)
Unlocks  List<&Thing> in Kotlin codegen.
Instead of adding another layer of indirection to code that has been been already far too twisted and with too many layers, I instead cleaned it up but introducing a recursive type hierarchy for schema fields.
Fixes b/159856888

Yup, agreed @cromwellian. This should be moved to visitor pattern the next time we want to use this hierarchy for anything. Currently it is only used for Kotlin type generation, but it is clear that we use schema field types in a lot of places and we should lift this hierachy here and add a visitor pattern... It would also clean up the C++ code FWIW.
But well... one step at a time.


Crash when freeing Certificates

I created multiple *openssl.Ctx.  When one goes out of scope, the finalizer tries to free a bunch of stuff including the *openssl.Certificate associated with that context (https://github.com/spacemonkeygo/openssl/blob/master/cert.go#L326).  My program keeps crashing and it seems like the finalizer is being called twice.  The workaround is to never let the openssl.Ctx go out of scope.  The following is the relevant crash error:
main(97262,0xb0104000) malloc: *** error for object 0x5216a20: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
SIGABRT: abort
PC=0x7fff8da09286
signal arrived during cgo execution

goroutine 19 [syscall]:
runtime.cgocall(0x4002560, 0x46f4f10)
    /usr/local/Cellar/go/1.3.1/libexec/src/pkg/runtime/cgocall.c:143 +0xe5 fp=0x46f4ef8 sp=0x46f4eb0
github.com/spacemonkeygo/openssl._Cfunc_X509_free(0x52152d0)
    github.com/spacemonkeygo/openssl/_obj/_cgo_defun.c:1460 +0x31 fp=0x46f4f10 sp=0x46f4ef8
github.com/spacemonkeygo/openssl.func·007(0xc208085980)
    /Users/i/proj/src/github.com/spacemonkeygo/openssl/cert.go:327 +0x2a fp=0x46f4f20 sp=0x46f4f10
runtime.call16(0x446ade8, 0xc2080003d0, 0x1000000010)
    /usr/local/Cellar/go/1.3.1/libexec/src/pkg/runtime/asm_amd64.s:360 +0x32 fp=0x46f4f38 sp=0x46f4f20
runfinq()
    /usr/local/Cellar/go/1.3.1/libexec/src/pkg/runtime/mgc0.c:2682 +0x207 fp=0x46f4fa8 sp=0x46f4f38
runtime.goexit()
    /usr/local/Cellar/go/1.3.1/libexec/src/pkg/runtime/proc.c:1445 fp=0x46f4fb0 sp=0x46f4fa8
created by runtime.gc
    /usr/local/Cellar/go/1.3.1/libexec/src/pkg/runtime/mgc0.c:2268

OpenSSL is probably calling X509_free() internally on the cert, so we need to adjust our GC strategy so that doesn't happen twice.

(See https://github.com/spacemonkeygo/openssl/blob/master/ctx.go#L125)

This might be fixed by now. Closing due to inactivity.


[WIP] azp/ci: Break out bazel.yml from ci.yml

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

there is more code i would like to factor out to this template, but its a bit harder so pushing just these bits for now


fix: remove speed_unit from fabric connection module

speed_unit was deprecated in last fabric module and this change is required to pass tests in https://github.com/equinix-labs/terraform-equinix-fabric-connection-aws/pull/18

I would recommend making this change directly to the upgrade PR instead.  There are going to be other breaking changes with the upgrade, such as the lack of actions data in the Fabric v4 connection resource.


[Relationship] Edge: Network missing protocol

Current Behavior
Kubernetes Services related to Kubernetes Pods via edge network relationship.
Expected Behavior
Both port and protocol are attributes that are to be considered as mutators in this relationship.
A regression has occurred in which protocol is not being accounted for.
Screenshots/Logs
Environment

Meshery Server Version: stable-v0.7.110

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@leecalcote I can take a look at this but want to make sure I understand the issue. When I try to test this in the Playground I can create a Kubernetes Service and Kubernetes Pod and create an edge network relationship between them. If I then open the service and modify the port it works fine. If I modify the protocol then the edge network relationship is deleted.
Is that behavior the regression that this ticket is describing?

@ctcarrier, thank you, yes. What you've described is an issue that needs fixing. I suspect that we might have a couple flavors of this bug, but yes, please, the behavior that you've described is unwanted.


[Question] Executing transactions in current Thread.

First of all, many-many thanks for developing such awesome library!.
Is there any way to execute transactions by means of TransactionManager in current thread (in thread where call to TransactionManager.getInstance().save(ProcessModelInfo.withModels(models)) is made) ?

new SaveModelTransaction<>(ProcessModelInfo.withModels(models)).onExecute();
for 2.0.0 I will force you to use the classes vs. static methods on the TransactionManager, such that the statement you mentioned above becomes:

TransactionManager.getInstance().addTransaction(new SaveModelTransaction<>(ProcessModelInfo.withModels(models)));

Alright, thanks very much!


Using Twilio integration to send campaigns via sms

Hello, im not sure if this is the place to ask. I am working in the possibilities using twilio integrated with crisp, and im wondering if the twilio integration only support receiving sms message in to the crisp chat at the moment. Thank you so much

Can you go ask over chat support at https://crisp.chat/en/ ? Thank you :)


Fix readJsonStringFromJsonFile method which didn't compile when insta…

…ntiated.

Thanks for the fix!


⚠ Bofrost.at has degraded performance

In cd54e00, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1262 ms

Resolved: Bofrost.at performance has improved in 8c7eeb5 after 17 minutes.


roll over smpp seq number at<PHONE_NUMBER>

otherwise vumi will explode after 4.29 billion PDU's

Do you want to land this while you're working on moving to the redis incr based implementation?

yes
On 4 January 2012 12:54, Simon de Haan <
<EMAIL_ADDRESS>
wrote:

Do you want to land this while you're working on moving to the redis incr
based implementation?

Reply to this email directly or view it on GitHub:
https://github.com/praekelt/vumi/pull/89#issuecomment-3353108

--
David
He had read much of things as they are, and talked with too many people.
Well-meaning philosophers had taught him to look into the logical relations
of things, and analyse the processes which shaped his thoughts and fancies.
Wonder had gone away, and he had forgotten that all life is only a set of
pictures in the brain, among which there is no difference betwixt those
born of real things and those born of inward dreamings, and no cause to
value the one above the other. Custom had dinned into his ears a
superstitious reverence for that which tangibly and physically exists, and
had made him secretly ashamed to dwell in visions.

- H. P. Lovecraft (The Silver Key)


added pydocstyle to pre-commit

Fixes #284

[ ] Consistent Repeated Arguments
[ ] Docstrings Exist
[x] Consistent Style

Yes, let's open a PR for each of those items.
Concerning this PR, it is time for me to take a look into that hook.

Sorry, but what do you mean one DXYZ at a time?

D102, D103, D401, etc.

Actually, bc of the way DXYZs are selected via convention=numpy, and with tools like docformatter, I think it will be easiest to just do this all at once.


FINOS Code Scans, Checks, Validation - SDLC Code

This task can't start until https://github.com/finos/alloy/issues/235 is completed.
SDLC

[x] FINOS Security Vulnerability Check
[x] FINOS Legal/License Scans
[x] Apply FINOS Project Blueprint

First FINOS scanning done, feedback provided by email

Feedback integrated, dashboards are clean, validation is passed!


Change Uyuni to Leap 15.5

What does this PR change?
Change Uyuni Server and Proxy to openSUSE Leap 15.5, as well as the examples.
https://github.com/SUSE/spacewalk/issues/21566

let's stay in sync with @deneb-alpha on this

This could affect our test suite, although we specify every OS version for each minion in the susemanager-ci repository. So it would be good if @wweellddeerr ping the RRTG when merging this, so he/she is aware.


//internal:test is broken with Bazel's Windows native test wrapper

🐞 bug report
Affected Rule

 The issue is caused by the rule:
//internal:test, which is a jasmine_node_test from @npm_bazel_jasmine//:index.bzl
Is this a regression?

Not really, I think it's always been there.
Description
 A clear and concise description of the problem...
Bazel 0.27 will enable a feature by default: to use a new test execution mechanism on Windows. Currently (in Bazel 0.26) this features is disabled. The new feature allows faster test execution, and doesn't use Bash. See https://github.com/bazelbuild/bazel/issues/6622 for details.
The bad news is, rules_typescript breaks with this planned change 😢 I fixed it in the past (https://github.com/bazelbuild/rules_typescript/commit/e50c806efc6f8c2bb46f16118d79dc3dbbad4337), but it's broken again 😿
Currently, I'm stuck: can't figure out where I have to update what.
I think I know the problem. It looks similar to that fixed by https://github.com/bazelbuild/rules_nodejs/commit/76609c79b2db80b1dee52065e2d0a93757ecb65f
And I believe I have to update @npm_bazel_jasmine//src/jasmine_node_test.bzl to use nodejs_test_macro instead of nodejs_test.
But I can't find where to update this file, or how it's pulled in as a dependency :(
🔬 Minimal Reproduction

With Bazel 0.26.0, check out rules_typescript c160db910772b2e58a46aaa0430e9b167a77eb6c, and run:
bazel test --incompatible_windows_native_test_wrapper --test_output=errors //internal:test

It fails because the test rule tries to execute a .sh file, which is not an executable file on Windows.
🔥 Exception or Error

🌍  Your Environment
Operating System:
Windows 10
Output of bazel version:
0.26 release
Rules version (SHA):

Anything else relevant?

Bazel 0.27 will enable a feature by default

Looks like this will NOT happen :(

Next time you can just ping me to unwind the silly sync sandwich between this repo and rules_nodejs
Sounds like the right thing is for us to pair a bit to remove the need for the wrapper macro on nodejs_test and nodejs_binary?

Sure, and thanks.
I'll ping you again about this when you're not on vacation.

Ping -- sorry for the long silence, I'm just now picking this up.
The test still fails:

Windows 10

Bazel 0.28.1

PATH=c:\git\mingw64\bin;c:\msys64\usr\bin;c:\src\bazel-releases\current;c:\windows\system32

Pass: C:\src\tw-migrations\rules_typescript>bazel --ignore_all_rc_files --output_user_root=c:/b test --noincompatible_windows_native_test_wrapper --experimental_allow_incremental_repository_updates //internal:test

Fail: C:\src\tw-migrations\rules_typescript>bazel --ignore_all_rc_files --output_user_root=c:/b test --incompatible_windows_native_test_wrapper --experimental_allow_incremental_repository_updates //internal:test
INFO: From Testing //internal:test:
==================== Test output for //internal:test:
ERROR(tools/test/windows/tw.cc:1248) ERROR: src/main/native/windows/process.cc(184): CreateProcessW("C:\b\thor5vol\execroot\build_bazel_rules_typescript\bazel-out\x64_windows-fastbuild\bin\internal\test.sh"): %1 is not a valid Win32 application.

ERROR(tools/test/windows/tw.cc:1405) Failed to start test process (arg: C:\b\thor5vol\execroot\build_bazel_rules_typescript\bazel-out\x64_windows-fastbuild\bin\internal\test.sh)
================================================================================

Linking to https://github.com/bazelbuild/bazel/issues/6622, which is blocked by this

ping

dupe of https://github.com/bazelbuild/rules_nodejs/issues/947, let's fix them together

Thanks!


feat: add sm2 encrypted test case from GM/T0003.5-2012.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

https://github.com/openssl/openssl/pull/15869
this PR is the same to this one!

@mspncp

@paulidale @t8m @romen

@ymj-uos you have 2 commits in this PR and one of them is a Merge commit, which we do not allow.
You need to rebase on current master instead.

Also, as background, I did look previously into backporting this KAT to OpenSSL, but preferred not to, for 2 reasons:

there appears to be an error in the description of this KAT in GM/T0003.5-2012/GB/T 32918.5-2016 (at section C.2/page 13):

compute point 𝐶1 = [𝑘]𝐺 = (𝑥1, 𝑦1) of the elliptic curve:

coordinate 𝑥1: 04EBFC71 8E8D1798 62043226 8E77FEB6 415E2EDE 0E073C0F 4F640ECD 2E149A73
coordinate 𝑦1: E858F9D8 1E5430A5 7B36DAAB 8F950A3C 64E6EE6A 63094D99 283AFF76 7E124DF0

choose the uncompressed form of 𝐶1, convert the point to be byte string of form 𝑃𝐶 ∥ 𝑥1 ∥ 𝑦1 where 𝑃𝐶 is a single byte and 𝑃𝐶 = 04, and denoted still by 𝐶1.
… omitted steps …
compute 𝐶2 = 𝑀 ⊕ 𝑡: 21886C A989CA9C 7D580873 07CA9309 2D651EFA
… omitted steps …
compute 𝐶3 = 𝐻𝑎𝑠ℎ(𝑥2 ∥ 𝑀 ∥ 𝑦2): … :
59983C18 F809E262 923C53AE C295D303 83B54E39 D609D160 AFCB1908 D0BD8766
output the cipher-text 𝐶 = 𝐶1 ∥ 𝐶2 ∥ 𝐶3:
04EBFC71 8E8D1798 62043226 8E77FEB6 415E2EDE 0E073C0F 4F640ECD 2E149A73
E858F9D8 1E5430A5 7B36DAAB 8F950A3C 64E6EE6A 63094D99 283AFF76 7E124DF0
59983C18 F809E262 923C53AE C295D303 83B54E39 D609D160 AFCB1908 D0BD8766
21886CA9 89CA9C7D 58087307 CA93092D 651EFA

the last step shows the order of 𝐶2 and 𝐶3 is swapped
the beginning of the cipher-text 𝐶 should start with 0404 as the first two bytes, as the KAT describes the encoding of 𝐶1 to be 𝑃𝐶 ∥ 𝑥1 ∥ 𝑦1, where 𝑃𝐶 is 04 and the encoding of 𝑥1 starts with another 04. The described point encoding (analogous to the SECG format) conforms to what is described in GM/T 0003.3-2012 (and GM/T 0003.1-2012), but the 𝐶1 part in the final cipher-text 𝐶 of this KAT does not match.

GM/T0003.5-2012/GB/T 32918.5-2016 seems to be incompatible with GM/T 0009-2012 (unofficial translation), which defines the ASN.1 structure we actually use to serialize/unserialize SM2 ciphertexts.
From the latter, compare
SM2Cipher ::= SEQENCE{
  XCoordinate     INTEGER,                -- x-coordinate
  YCoordinate     INTEGER,                -- y-coordinate
  HASH            OCTET STRING SIZE(32),  -- hash value
  CipherText      OCTET STRING            -- ciphertext
}

against the GM/T0003 family which mandates a SECG like encoding for the point described by the first two INTEGERS in the sequence above:

6.1.A8 of GM/T 0003.4-2012 mandates the output ciphertext to be 𝐶1 || 𝐶2 || 𝐶3, where 𝐶1 is a elliptic curve point, defined in 6.1.A2
6.1.A2, regarding its encoding, mandates: "convert the data type of 𝐶1 to bit string as specified in Clauses 4.2.8 and 4.2.4 of GM/T 0003.1‒2012"
4.2.8 of GM/T 0003.1‒2012 (for uncompressed form & prime curve as the default SM2 curve) mandates to write 0x04 || X1 || Y1, where X1 and Y1 are 𝑙 = ⌈(log2 𝑞)/8⌉ bytes long as specified in 4.2.5
4.2.5 refers to 4.2.1, which ultimately mandates to write 𝑙 bytes, from left to right, padding with zero bits as needed.

This is incompatible with the ASN.1 structure, not only because the first byte signaling "uncompressed encoding" is missing, but also because the coordinates when defined as INTEGER cannot be padded but must take the shortest possible form.

I thought a long time, the two reason which you mentioned seem to be misunderstood.
about your 1st reason:
according to the GM/T0003.5-2012 and GB/T 32918.5-2016, "output the cipher-text" should be 𝐶 = 𝐶1 ∥ 𝐶3 ∥ 𝐶2, this is correct!
because of historial version, 𝐶 = 𝐶1 ∥ 𝐶2 ∥ 𝐶3 would be used for some time, which would be changed to 𝐶 = 𝐶1 ∥ 𝐶3 ∥ 𝐶2 later.
about C1 (PC ∥ x1 ∥ y1), this is a data-format problem. In the GM/T0003.1-2012 (at section 4.1 and 4.2/page 6),
there are 5 data formats (bit_string, byte_string, integer, Elliptic curve point, field_element),
all of them could be used to express C1. only byte_string format should add PC flag.

about your 2nd reason:
SM2Cipher ::= SEQENCE{
XCoordinate     INTEGER,                -- x-coordinate
YCoordinate     INTEGER,                -- y-coordinate
HASH            OCTET STRING SIZE(32),  -- hash value
CipherText      OCTET STRING            -- ciphertext
}
at the serialize/unserialize SM2 ciphertexts,
C1 does not use byte_string format, so we do not care about "PC". If C1 use byte_string format, we should think about the first byte signaling "uncompressed encoding"
about padding with zero bits, it is used during computing or transferring. If only communicating or saving SM2Cipher data, we should not care about padding.
section 6.1 (page 4-5) Encryption algorithm its process
Suppose the message to be sent is the bit string 𝑀 and 𝑘𝑙𝑒𝑛 represents the bit-length
of 𝑀.
To encrypt the plaintext 𝑀, encryption user A should perform the following procedures:
A1: generate a random number 𝑘 ∈ [1, 𝑛 − 1] with the random number generator.
A2: compute point 𝐶1 = [𝑘]𝐺 = (𝑥1, 𝑦1) of the elliptic curve, and convert the data type
of 𝐶1 to bit string as specified in Clauses 4.2.9 and 4.2.5 of GM/T 0003.1‒2012.
A3: compute point 𝑆 = [ℎ]𝑃𝐵 of the elliptic curve; if 𝑆 is the infinity point, report
error and exit.
A4: compute point [𝑘]𝑃𝐵 = (𝑥2, 𝑦2) of the elliptic curve, convert the data type of 𝑥2, 𝑦2
to bit string as specified in Clauses 4.2.6 and 4.2.5 of GM/T 0003.1‒2012.
A5: compute 𝑡 = 𝐾𝐷𝐹(𝑥2||𝑦2, 𝑘𝑙𝑒𝑛). If 𝑡 is an all-zero bit string, go to A1.
A6: compute 𝐶2 = 𝑀 ⊕ 𝑡.
A7: compute 𝐶3 = 𝐻𝑎𝑠ℎ(𝑥2||𝑀||𝑦2).
A8: output the ciphertext 𝐶 = 𝐶1||𝐶3||𝐶2.
Note: Examples of the process of encryption are described in Annex A (Appendix A, is the same to Annex C in GB/T32918.5-2016).
compared to the original version as below:

finally, In the GM/T 0009-2012 only asn.1 data format (C1,C2,C3) is defined. not say that the SM2 cipher must use asn.1 data format.
If someone need use asn.1 data structure (format), he could adopt the data format in the GM/T 0009-2012. if not, he could use one of 5 data formats in the GM/T0003.1-2012.
So, the code that I upload match all the sm2's standards.

GMT 0003.4-2012 SM2椭圆曲线公钥密码算法第4部分：公钥加密算法.pdf
This is the original version standard. If you want to check some detail，you can use it.

Thanks for your comments @ymj-uos , but even considering that the problem might be related to the English version of the standard (which is a problem, because that is the one we can use for our reviews), I still have some doubts:

looking at the version in Chinese you linked, I can still clearly see in the KAT that C1 is supposed to be serialized as PC || x || y with PC = 04, and this is still evident looking for example at page 9 at the expected ciphertext C under A2
even looking at the Chinese original of GM/T 0003.5-2012 (Appendix C, at page 8-9 seems to be the one about the SM2 encryption standard) C1 (and also in the expected ciphertext) is serialized using the SECG standard and prefixed with PC = 04
In the GM/T 0003.5-2012 document above I am not finding a reference to the KAT being added in this PR.

@ymj-uos I apologize, I finally managed to understand why I was seeing discrepancies, I will update my review shortly

Note for whoever will merge this, remember to squash the commits!

@paulidale

Note for whoever will merge this, remember to squash the commits!

@paulidale I plan to take care of merging this tomorrow morning (European timezones) once the 24h grace period is over.

Merged

to master with 8ba65c35ea3af347c3b2adc8e665066b541a1c35
to openssl-3.0 with 09f24c909cb717f40ebb4a6de2699aa971dcc15d

Thanks @ymj-uos for your contribution!

@paulidale This could be cherry-picked cleanly to 1.1.1, and I would propose to do so.
If you agree, could you please add the 1.1.1 label and state that you agree for the record?

(removed the ready to merge label, so we can restart the 24h grace period for 1.1.1 if @paulidale agrees)

This pull request is ready to merge

Merged also to 1.1.1: b9b45aa45873c63b8207eb527249f430288c17a0


Define translation workflow / policy

We need to answer the following questions:

What happens with translations when we update the (English) source?
When do we consider a language to be 'supported' and link to it from the PyPI footer?
What happens if a language is no longer maintained?

My 2c:
Updating English source
First, we need to reach out to the community to register maintainers for each language.
When we update the UI copy:

The change is merged as normal
The UI falls back to the original English
We notify translators via Weblate that a new translation is required

Note: In some cases (e.g. fixing typos, formatting) translators may be able to use the translation memory to reduce the maintenance burden
When do we consider a language 'supported'?
If 90% (???) of strings are translated, we should link to it from the PyPI footer.
What happens if a language is no longer maintained?
We remove it from the PyPI footer if it falls below 90% (???) coverage

Note, once this workflow is decided, we should document it in the Warehouse docs.  I have added a basic translations page in https://github.com/pypa/warehouse/pull/6681.

I'm happy with all these policy decisions @nlhkabu - @ewdurbin you have any objections?

@ewdurbin will "spend some time late this week trying to figure out the best way for us to handle building translation files from source" per conversation in IRC just now. That might include some updates to #6749 to document the process.

So I've tried out Weblate and there's one thing I see missing which is the ability to create variants of phrases depending on the number/gender for languages that use declension for this.
I suppose that the way to go is to use poEdit app locally instead and then send PRs. But how does that integrate back into the Weblate UI?
(Ref: https://twitter.com/webKnjaZ/status/1181495636946014208)

But Weblate is just gettext; in its side it does allow for plural forms according to the language.

Alright, I've seen just one string with multiple versions depending on the number there. Which means that the string source should be fixed to properly mark such places.

@webknjaz - sounds like this justifies it's own ticket.
Would you be able to open a new issue to explain the problem? Please use the 'translation' issue type.
Thanks

https://github.com/pypa/warehouse/issues/6798

I recently almost translated the entire website into French. Now this is appearing online, but I noticed that certain strings were missing. Will you add them later?
I'm thinking about elements in the footer, the Sponsors and Terms of use pages.


After you master that you can go to git commit --fixup=HEAD and git rebase -i --autosquash

@yangmillstheory for me? Squash will always result with one commit, which isn't always what I want. I prefer small amount of well crafted commits that shows my thought process and evolution of feature.

Yeah I think if you're careful with commit history it makes sense. My comments are usually unfocused and not descriptive (I don't always feel like doinggit add --patch, git commit, usually just ends up being "WIP"), so I tend to want to keep those out of master. I could rebase those WIP commits, but then it's more effort. I haven't been converted to this way of committing yet.


Build fails with RediStack 1.0.0-beta.1

Since RediStack is imported like this, on a new deployment, it updated to the latest beta version, which does not compile.
.package(url: "https://gitlab.com/mordil/RediStack.git", from: "1.0.0-alpha.8"),
Workaround:
Add to main Package.swift:
.package(url: "https://gitlab.com/mordil/RediStack.git", .exact("1.0.0-alpha.10")),

@andreigherghe Fixed with 1.0.0-beta.5.1
The Vapor/Redis package should be updated soon to drop this intermediate package and rely on RediStack directly.
Are you using RedisKit directly, or did this come up while using Vapor/Redis?
If you're using this package directly, you should switch to using RediStack directly, as this package is being deprecated.


Bridge: Replace lazy_static macro with once_cell

See also #1024
lazy_static is unmaintained, once_cell is the new hotness. This PR swaps out the one lazy_static invocation for the equivalent lazy construct from once_cell.

:star: Open source review :star:
Might not be necessary, but given that this is technically a different project, here's what I said last time:
once_cell is the new standard for lazily-initialized static values. The intent is for its API to be incorporated into the standard library. Parts of it already have been as of Rust 1.70.0.
Our existing solution lazy_static is not maintained, and urges users to move to once_cell.
once_cell is dual licensed Apache 2.0 and MIT, as are all of its dependencies.

OSS review approved!


BlockPos - Spam

Minecraft Version:

1.12.2
Forge Version: - <IP_ADDRESS>87

Advanced Rocketry Version:

AdvancedRocketry-1.12.2-1.2.6-42.jar

LibVulpes Version:

LibVulpes-1.12.2-0.2.7-24-universal.jar
is this the latest curseforge build?

We are getting a lot of spam on our Revelations server:

duplicate of #1023, fixed in build 43


refactor: cleaner types by inference for getL1Network and getL2Network

closing this as the change doesn't seem to improve the concerned code


Code doesn't compile

Using .NET Command Line Tools (1.0.0-beta-001598)
Running build.cmd
Compiling Microsoft.AspNetCore.Server.Kestrel.GeneratedCode for .NETStandardApp,Version=v1.5
C:\Users\ayende\AppData\Local\Microsoft\dotnet\cli\bin\dotnet.exe compile-csc @C:\Work\KestrelHttpServer\tools\Microsoft.AspNetCore.Server.Kestrel.GeneratedCode\obj\Debug\netstandardapp1.5\dotnet-compile.rsp returned Exit Code 1
C:\Work\KestrelHttpServer\tools\Microsoft.AspNetCore.Server.Kestrel.GeneratedCode\FrameFeatureCollection.cs(25,24): error CS0246: The type or namespace name 'IServiceProvidersFeature' could not be found (are you missing a using directive or an assembly reference?)
C:\Work\KestrelHttpServer\tools\Microsoft.AspNetCore.Server.Kestrel.GeneratedCode\FrameFeatureCollection.cs(33,24): error CS0246: The type or namespace name 'IQueryFeature' could not be found (are you missing a using directive or an assembly reference?)
C:\Work\KestrelHttpServer\tools\Microsoft.AspNetCore.Server.Kestrel.GeneratedCode\FrameFeatureCollection.cs(34,24): error CS0246: The type or namespace name 'IFormFeature' could not be found (are you missing a using directive or an assembly reference?)
C:\Work\KestrelHttpServer\tools\Microsoft.AspNetCore.Server.Kestrel.GeneratedCode\FrameFeatureCollection.cs(40,24): error CS0246: The type or namespace name 'IResponseCookiesFeature' could not be found (are you missing a using directive or an assembly reference?)
C:\Work\KestrelHttpServer\tools\Microsoft.AspNetCore.Server.Kestrel.GeneratedCode\FrameFeatureCollection.cs(41,24): error CS0246: The type or namespace name 'IItemsFeature' could not be found (are you missing a using directive or an assembly reference?)

https://github.com/aspnet/KestrelHttpServer/commit/f13c418a65db4426ebf265fa7eb34fe741b4163b
It's already been 'fixed', but we're having build issues and have not been able to update myget all week.

@ayende please reactivate/file another issue if the recent aspnetvnext packages have the same issue.


Open the calendar on pop up

Hi.
thanks for keeping this fork of the kekeh repository.
I also was using the prev version, Right now I'm migrating the app to version 14 and the old module doesn't work.
I'm trying to use this one, but I'm not sure how to open the calendar in a pop up view and also keep the user to enter the date manually.
Thanks,

Here's a basic example of an input that can accept a manual date along with a button to toggle the calendar...
import { Component, ViewChild } from "@angular/core";
import {
  AngularMyDatePickerDirective,
  IAngularMyDpOptions,
} from "@nodro7/angular-mydatepicker";

@Component({
  selector: "app-root",
  template: `
    <input
      angular-mydatepicker
      #datePicker="angular-mydatepicker"
      placeholder="placeholder"
      autocomplete="off"
      [options]="myDatePickerOptions"
    />
    <button type="button" (click)="toggleCalendar()" type="button">
      Toggle
    </button>
  `,
  styles: [],
})
export class AppComponent {
  @ViewChild("datePicker") datePicker!: AngularMyDatePickerDirective;

  myDatePickerOptions: IAngularMyDpOptions = {
    appendSelectorToBody: true,
  };

  toggleCalendar(): void {
    this.datePicker.toggleCalendar();
  }
}

No problem.
Just FYI, this repository is actually based on the newer version of Kekeh's datepicker - angular-mydatepicker not mydatepicker that you are using.


[ImageHotspots] onClick gives incorrect coordinates when parent has scrollbar

What package is this for?

[x] React
[ ] Angular

Describe the bug
Adding new hotspots by clicking will not work properly if the parent has scrollbar. This bug is visible when in the HotspotEditorModal.
To Reproduce

Resize the HotspotEditorModal to like like in the image

Add a hotspot and notice the incorrect position

Please create a reduced test case in CodeSandbox:
https://codesandbox.io/s/github/IBM/carbon-addons-iot-react/tree/master/examples/codesandbox

Expected behavior
New hotspot should appear centered exactly where the mouse click was.
Environment/versions:

OS: [e.g. MacOS, Windows]
Browser: [e.g. chrome, safari]
carbon-addons-iot-react version: [e.g. v2.60.0]

Additional context
If applicable, add screenshots to help explain your problem.
Add any other context about the problem here.
Specific timeline issues / requests
Do you want this work within a specific time period? Is it related to an
upcoming release?
NB: The core contributors will try to work with your timeline, but it's not
guaranteed. The earlier you make a request in advance of a desired delivery
date, the better!

:tada: This issue has been resolved in version 2.143.0-next.10 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.143.0-next.10 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Mark repository as abandoned

No longer actively maintained, should be archived: https://docs.github.com/en/repositories/archiving-a-github-repository/archiving-repositories

Here a valid alternative https://springdoc.org/ (disclaimer: i'm not involved in any way in that project, I'm only a developer that whants help other people to create better code, too many blogs and video tutorial suggesting to use this abandoned library)


[BUG] Azure.ResourceManager.KubernetesConfiguration using Api version '2022-11-01,2022-11-01' twice and caused the create/update failure

Library name and version
Azure.ResourceManager.KubernetesConfiguration 1.0.0 and 1.1.0
Describe the bug
Trying to create/update Microsoft.AzureKeyVaultSecretsProvider extension on a connected cluster. However, encountered this issue:
Azure.RequestFailedException
HResult=0x80131500
Message=No registered resource provider found for location 'eastasia' and API version '2022-11-01,2022-11-01' for type 'extensions'. The supported api-versions are '2020-07-01-preview, 2021-05-01-preview, 2021-09-01, 2022-03-01, 2022-04-02-preview, 2022-07-01, 2022-11-01, 2023-05-01, 2019-11-01-preview, 2020-10-01-preview, 2021-03-01'. The supported locations are 'eastus, westeurope, westcentralus, westus2, westus3, southcentralus, eastus2, northeurope, uksouth, southeastasia, australiaeast, francecentral, centralus, northcentralus, westus, koreacentral, eastasia, japaneast, canadaeast, canadacentral, norwayeast, germanywestcentral, swedencentral, switzerlandnorth, australiasoutheast, centralindia, southindia, japanwest, ukwest, francesouth, koreasouth, southafricanorth, brazilsouth, uaenorth, norwaywest, germanynorth, jioindiawest, eastus2euap, centraluseuap'.
Status: 400 (Bad Request)
ErrorCode: NoRegisteredProviderFound
Content:
{"error":{"code":"NoRegisteredProviderFound","message":"No registered resource provider found for location 'eastasia' and API version '2022-11-01,2022-11-01' for type 'extensions'. The supported api-versions are '2020-07-01-preview, 2021-05-01-preview, 2021-09-01, 2022-03-01, 2022-04-02-preview, 2022-07-01, 2022-11-01, 2023-05-01, 2019-11-01-preview, 2020-10-01-preview, 2021-03-01'. The supported locations are 'eastus, westeurope, westcentralus, westus2, westus3, southcentralus, eastus2, northeurope, uksouth, southeastasia, australiaeast, francecentral, centralus, northcentralus, westus, koreacentral, eastasia, japaneast, canadaeast, canadacentral, norwayeast, germanywestcentral, swedencentral, switzerlandnorth, australiasoutheast, centralindia, southindia, japanwest, ukwest, francesouth, koreasouth, southafricanorth, brazilsouth, uaenorth, norwaywest, germanynorth, jioindiawest, eastus2euap, centraluseuap'."}}
Headers:
Cache-Control: no-cache
Pragma: no-cache
x-ms-failure-cause: REDACTED
x-ms-request-id: c91bb804-e116-4d16-a180-c0c0243fda28
x-ms-correlation-request-id: REDACTED
x-ms-routing-request-id: REDACTED
Strict-Transport-Security: REDACTED
X-Content-Type-Options: REDACTED
Date: Tue, 05 Sep 2023 05:52:57 GMT
Content-Type: application/json; charset=utf-8
Expires: -1
Content-Length: 924
Source=Azure.ResourceManager.KubernetesConfiguration
StackTrace:
at Azure.Core.OperationInternal1.GetResponseFromState(OperationState1 state)
at Azure.Core.OperationInternal1.<UpdateStatusAsync>d__20.MoveNext()    at System.Threading.Tasks.ValueTask1.get_Result()
at Azure.Core.OperationInternalBase.d__13.MoveNext()
at System.Threading.Tasks.ValueTask1.get_Result()    at Azure.Core.OperationPoller.<WaitForCompletionAsync>d__11.MoveNext()    at System.Threading.Tasks.ValueTask1.get_Result()
at Azure.Core.OperationInternalBase.d__19.MoveNext()
at System.Threading.Tasks.ValueTask1.get_Result()    at Azure.Core.OperationInternal1.d__19.MoveNext()
at System.Threading.Tasks.ValueTask1.get_Result()    at Azure.Core.OperationInternal1.d__15.MoveNext()
at System.Threading.Tasks.ValueTask`1.get_Result()
at Azure.ResourceManager.KubernetesConfiguration.KubernetesClusterExtensionCollection.d__8.MoveNext()
at _202.ArcEnabledExtensionHelper.<CreateOrUpdate_CreateExtension>d__9.MoveNext() in D:\azurearc-samples\202\dotnet\src\ArcEnabledExtensionHelper.cs:line 114
at _202.Program.Main(String[] args) in D:\azurearc-samples\202\dotnet\src\Program.cs:line 35
Looks like the sdk is doubling the api version 2022-11-01 here.
Expected behavior
No apiversion related error
Actual behavior
api version and location related error.
The actuall api version and location is in the support list.
Reproduction Steps
I think any extension type would cause this issue.
Environment

net7.0
enable
enable

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Any update here?

Do we have any update here? It's been a month

@jsquire @ArthurMa1978 @HarveyLink
It's been more than a month and no updates has been made.
Do we have any progress here?

Hi @iwangjintian , We have repro this issue, working on a solution now.

Haven't heard from you for a while. Do we got any update on this?

Service team is still working on a fix for it. will let you know when the fix is deployed. Sorry for the slow progress. thanks.

@iwangjintian , the issue should have been fixed. Please give it a try and feel free to let us know if you have more questions. thanks.