nixpkgs: added k9copy

Could you please also define meta.platforms ? (e.g. platforms = platforms.linux)

Could you please also define meta.platforms?

sure

Sometimes I have the same problem. I don't know if a application also works on other platforms (like Darwin). Maybe we should introduce a new tag? Something like needs-testing in combination with darwin (or a different platform)

Please rename commit as it said in CONTIBUTING.md.

Did you try this before merging? It doesn't even evaluate:
error: undefined variable ‘scope’ at "/home/user/nixpkgs/pkgs/applications/video/k9copy/default.nix":38:5

yes, there seems to be a change since 3113d31070f0a0d4a1cdbad2336e32c2a2312031 but I didn't find the right place :-
@ttuegel might help us?
However, I fixit it  with these changes: https://github.com/flosse/nixpkgs/commit/86dbc9b5e2f11de545a64cd17afd5d76e34081ac (I'll create a PR as soon as the compiling on my local machine is done)

seems to work: https://github.com/NixOS/nixpkgs/pull/8517

Yes, the KDE Frameworks expressions no longer export implementation details; it is safe to just to add whatever packages you need to the buildInputs.


How to deploy to vercel？

I followed the tutorial https://grammy.dev/zh/hosting/vercel, but why the robot cannot run.
The log records on vercel feedback the following 2 information
[POST] /api/bot status=500
TypeError: req.json is not a function
at stdHttp (/var/task/node_modules/grammy/out/convenience/frameworks.js:254:21)
at /var/task/node_modules/grammy/out/convenience/webhook.js:23:79
at Server. (/opt/rust/nodejs.js:1:10660)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Server. (/opt/rust/nodejs.js:8:4429)
I'm very anxious. Can you help me?

i use CommonJS specification

If you need help with a programming problem, you need to share the code you wrote.
Also, there are are several examples for vercel here: https://github.com/grammyjs/examples/tree/main/setups

If you need help with a programming problem, you need to share the code you wrote.
Also, there are are several examples for vercel here: https://github.com/grammyjs/examples/tree/main/setups

3q


Suggestion: Remove  {topicName} -" prefix from schema key/value tree item

Code of Conduct

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

On what operating system are you seeing the problem?
macOS (Apple/arm64)
VS Code version
Version: 1.93.1 (Universal)
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.6.0
Version of Confluent extension
v0.16.3
To Reproduce

Install, signin to CC, and navigate to a topic with schema(s).
Expand the chevron of said topic
Observe child tree items

Current vs. Expected behavior
Expected: See two child items, "key" and "value"
Actual: See two child items, "{topicName} - key" and "{topicName} - value"
Since the topic name is immediately available on the parent node, the extra duplication here make it more difficult to read and navigate, suggest remove topic name as prefix.

Relevant log output
No response
Which area(s) are affected? (Select all that apply)
Schemas
Additional context
No response

Hey @derek1ee -- this is not a bug, but intended behavior since we group schema subjects associated with topics based on the TopicNameStrategy, similar to CCloud.
Under each subject item will be all versions of the schema, in descending order:

We're also pulling these {topic}-key/{topic}-value subject values directly from the Schema Registry REST proxy, so attempting to alter them could result in confusion for developers working with those schemas. In the future, if we start supporting more than the TopicNameStrategy, we may be able to adjust the hierarchy and labeling here, but that will require some coordination with the Schema Registry API and CCloud developers.


fix: add unicode 3.0 license to list of allowed licenses

This is causing our CI dependency audit to fail
For details, you can run cargo-deny check licenses locally. The following deps currently use the Unicode-3.0 license:
icu_collections
icu_locid
icu_locid_transform
icu_locid_transform_data
icu_normalizer
icu_normalizer_data
icu_properties
icu_properties_data
icu_provider
icu_provider_macros
litemap
tinystr
writeable
yoke
yoke-derive
zerofrom
zerofrom-derive
zerovec
zerovec-derive

I'm not familiar with the Unicode 3.0 license. Are there any implications for allowing code with this license?

I read the license and it seems fine to me but another pair of eyes would be good. I dug more into where all of these deps came from, and the culprit is #5444 - specifically bumping url from v2.5.0 to v2.5.1 since that bumps its version of idna from v0.5.0 to v1.0.0 which introduces icu_normalizer and icu_properties which is where the unicode license cascade starts. We could just revert url back to v2.5.0.

The Unicode License is a permissive open source license approved by the Open Source Initiative (OSI).


NATIVE-96: Add errors to state

Not sure if this is the right approach. Please take a brief look and tell me what you think. Also, I don't know where to put errors occurring in fetchResources, maybe the cityContent state would be the right place for this, but then we had to check three places for errors all the time. Maybe I'm also doing this way to complicated... ^^
https://flow.org/en/docs/types/unions/#toc-disjoint-unions-with-exact-types

@maxammann The description of the wip label is DO NOT REVIEW YET, but I would like reviews.

You attached needs-review label 3 days ago

Thats my review/feedback

@Schedulaar your opinion on this?


Upstream prematurely closed connection while reading response header from upstream

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
2.8.3
Current Behavior
After we upgraded kong from 2.0.3 to 2.8.3 we started seeing increase in 502 errors from Kong with log Upstream prematurely closed connection while reading response header from upstream. Because of this about 1 request fails every 2 seconds during peak traffic.
Number of 502 increase as the number of requests increase, we are seeing increased nginx timer delay and increased number of connections in waiting state.

This issue is observed only with a upstream that is a PHP backend and behind Apache server, this upstream is serving high traffic.
We have tried tweaking upstream keepalive setting but no luck.
Previous Config

KONG_NGINX_UPSTREAM_KEEPALIVE : 3600
KONG_NGINX_UPSTREAM_KEEPALIVE_REQUESTS: 1000

New config ( as part of tweaking )

KONG_UPSTREAM_KEEPALIVE_POOL_SIZE: 100
KONG_UPSTREAM_KEEPALIVE_MAX_REQUESTS: 1000
Removed both previous configs

Also after upgrading we started seeing increased latency to other services from Kong, like redis and other http calls to microservices, because of this lot of these requests are timing out or p99 is very high comparatively. Both of the issues can be related but not sure
Expected Behavior
No 502 errors at Kong due to this error
Steps To Reproduce

Upgrade the Kong from 2.0.3 to 2.8.3 with same configurations as before

Anything else?
No response

Hi @shettyh! Thanks for your report.
Do you see any [error] level log messages when this issue happens? Can you share them?
Some plugins can block Nginx workers for long periods and that can cause requests to fail. What plugins are you using, even on unrelated routes? Are there any custom plugins?

@locao thanks for the response. Other than this error log below, not seeing any other error log
[error] 1122#0: *58876376 upstream prematurely closed connection while reading response header from upstream, client:

Some plugins can block Nginx workers for long periods and that can cause requests to fail. What plugins are you using, even on unrelated routes? Are there any custom plugins?

Nothing new we are using with 2.8.3, all are same as before (2.0.3). Is there any specific changes in new version that can cause this ?.
There is only one custom plugin that uses timer other than zipkin plugin, custom plugin is just doing http call on specified interval using timers

Using timer is not a problem in this case. The issue exists when Nginx is blocked in a non-yielding code for long time. In Kong 2.8.3 this has been seen with Prometheus plugin, but only in special cases.
You may want to take a look at #3785, it might be the same case.

@locao thanks for the reply. We were able to fix this issue by following below steps

Disable new upstream keep-alive by setting KONG_UPSTREAM_KEEPALIVE_POOL_SIZE to 0
Enabled Nginx keep-alive by setting KONG_NGINX_UPSTREAM_KEEPALIVE

Any inputs on what could be wrong ?

This problem is because apache closed the connection earlier than kong.
You can view this document: https://httpd.apache.org/docs/2.4/mod/core.html#keepalivetimeout, the keepalivetimeout of apache is default 5s，kong is 60s. You can set apache keepalivetimeout to 65s to ensure that kong closes the connection earlier than apache

Closing considering the issue is sufficiently resolved, please reopen if needed.

I met the same errors in the kong log,but the upstream did not received the request from kong


bug: [Ionic 4.6.x] ion-input isn't work expected in @capacitor/ios

Bug Report
Ionic version:
[x] 4.6.x
Current behavior:
in @capacitor/ios, ion-input is enter duplicate characters.
input abc is changed to aababc.
This is animation gif.
https://gyazo.com/7728140ec47948396e6bc341c15d8ff8
Expected behavior:
input abc is abc.
Steps to reproduce:

Related code:
  <form #f="ngForm" >
    <ion-list>
      <ion-item>
        <ion-label position="floating">メールアドレス</ion-label>
        <ion-input required type="text" [(ngModel)]="email" name="login.email"></ion-input>
      </ion-item>
    </ion-list>
  </form>

Other information:

<EMAIL_ADDRESS>don't have this behavior.
@ionic/angular@dev(4.7.0-dev.201907111702.67c0d82) have this bug.
There is no problem with keyboards other than iOS default flick input.

Ionic info:
Ionic:

   Ionic CLI                     : 5.2.0 (/usr/local/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.6.2
   @angular-devkit/build-angular : 0.13.9
   @angular-devkit/schematics    : 7.3.9
   @angular/cli                  : 7.3.9
   @ionic/angular-toolkit        : 1.5.1

Capacitor:

   Capacitor CLI   : 1.1.0
   @capacitor/core : 1.1.0

Utility:

   cordova-res : not installed
   native-run  : not installed

System:

   NodeJS : v10.16.0 (/usr/local/bin/node)
   npm    : 6.9.0
   OS     : macOS Mojave

Thanks for the issue. This appears to be the same issue as https://github.com/ionic-team/ionic/issues/18770, so I am going to close this issue in favor of that one. You can follow the linked issue for updates regarding this issue.
Thanks!


Add Bounds Padding

Currently it isn't easy to automatically offset the map/markers (for when you have a control that sits over the map)
Google have updated their API to handle this but it isn't supported in this library yet: https://developers.google.com/maps/documentation/javascript/reference/map#Map.fitBounds
https://stackoverflow.com/a/53565456
Here are old issues about adding the feature: https://github.com/SebastianM/angular-google-maps/issues/716 https://github.com/SebastianM/angular-google-maps/issues/1471
And here is a pull request that implemented it but was never released: https://github.com/SebastianM/angular-google-maps/pull/1478

Just released it to NPM https://www.npmjs.com/package/@ng-maps/core


coldcard now does show zpubs

Thanks @mmikeww! I could see a future where there is a universal standard here (might even be xpub instead of zpub), but for now giving both options (verify a receive address and also the xpubs themselves) is probably a goon call.

Thanks @mmikeww! I could see a future where there is a universal standard here (might even be xpub instead of zpub), but for now giving both options (verify a receive address and also the xpubs themselves) is probably a goon call.

Electrum devs seem to think the standard is to use Zpubs for newer segwit addresses and xpub for legacy addresses:
https://github.com/spesmilo/electrum/issues/6946#event-4214846105

Electrum devs seem to think the standard is to use Zpubs for newer segwit addresses and xpub for legacy addresses:
https://github.com/spesmilo/electrum/issues/6946#event-4214846105

Ya, I think this is probably a poor choice on their part. For now, all the hardware wallets support it so no reason to make changes. I can see a world where new hardware wallets never adopt SLIP132 and it becomes "officially" deprecated, in which case the guide should probably recommend dropping it as well.

Ya, I think this is probably a poor choice on their part. For now, all the hardware wallets support it so no reason to make changes. I can see a world where new hardware wallets never adopt SLIP132 and it becomes "officially" deprecated, in which case the guide should probably recommend dropping it as well.

Well if Zpubs become deprecated, then there will be no way to generate bc1 segwit addresses in Electrum, unless they also change their software to offer the option to choose address type. For now, I think the guide will be relevant as-is for quite some time.

Well if Zpubs become deprecated, then there will be no way to generate bc1 segwit addresses in Electrum, unless they also change their software to offer the option to choose address type. For now, I think the guide will be relevant as-is for quite some time.

Electrum unfortunately has a history of digging in on standards long after others have won out. They still have Limited BIP39 Support :(

Electrum has limited support for BIP39 and is openly considering dropping it altogether. Users cannot create BIP39 seeds, and importing them is difficult; it requires knowing to toggle hidden checkboxes and ignoring scary user prompts with inaccurate security warnings. This is confusing for hardware wallet users, as BIP39 is the universal standard that almost all hardware wallets use.

https://btcguide.github.io/known-issues/software/electrum

Electrum unfortunately has a history of digging in on standards long after others have won out. They still have Limited BIP39 Support :(

Electrum has limited support for BIP39 and is openly considering dropping it altogether. Users cannot create BIP39 seeds, and importing them is difficult; it requires knowing to toggle hidden checkboxes and ignoring scary user prompts with inaccurate security warnings. This is confusing for hardware wallet users, as BIP39 is the universal standard that almost all hardware wallets use.

https://btcguide.github.io/known-issues/software/electrum


fix(german): fix and improve german translation

Summary of changes

fixed encoding to UTF-8
fixed typos

Checklist

[x] New functions have typespecs, changed functions were updated
[x] Same for documentation, including moduledocs
[x] Tests were added or updated to cover changes
[x] Commits were squashed into a single coherent commit

Coverage decreased (-0.04%) to 70.433% when pulling b605d23b7ad5616cd9858d61477da035c1430f84 on schurig:german into 725d91e3acfd0d24192337b8a4eb1ab928b30378 on bitwalker:master.

Thanks!


Implementing JDK 7 autocloseable feature for OdfPackage and document classes

I found a cosmetic change that might be still become quite helpful for our upcoming release:
The implementation of the JDK 7 autocloseable feature, see
https://examples.javacodegeeks.com/core-java/java-autocloseable-interface-example/
https://docs.oracle.com/javase/8/docs/api/java/lang/AutoCloseable.html
Please review, if I have overseen anything important :-)
Thanks in advance,
Svante

Here is another site with information: https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html


Adds Mediatr notifications for API responses and Cosmos DB operations

Description
These changes update the service to emit Mediator notifications containing information about API responses, as well as Cosmos DB responses.
Related issues
Addresses [issue #].
Testing
Describe how this change was tested.

Can you please add some comments clarifying the intent and purpose of this new functionality, especially for people who will be looking at this code from outside of Microsoft? These events are emitted but are not consumed anywhere.

Please see FhirDocumentClient, where we have a subset of this logic for returning the full RU consumption of a call in a response header. We should have a consistent approach to this sort of thing.


1989 guessing of namedplaces [do NOT merge]

There's a PoC for the namedplaces guessing, without taking into account countries and going straight to DB through the SQL API to query for the number of matches.
I would NOT merge it yet because:

this does not seem to scale well
it is time to refactor at least the georeferencer (a lot of copy/paste code)
lack of tests

cc/ @Kartones

Frontend tests were OK :+1: (details)

why "this does not seem to scale well" ? what do you mean?

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

:+1: Nice tests!


Road to test coverage

This PR improves test coverage for actions:

Also discovered a bug in application logic regarding new RFC emails. Currently user will only get 1 email regardless of how many RFC's have been created because hasGottenEmail() only checks for mail type, not if they received email for this new RFC. I have created a failing test for this case.
public function hasGottenMail(Mailable $mailable): bool
{
    return $this->mails()->where('mail_type', $mailable::class)->exists();
}

Love this! I can fix that bug 👍

Wrote down an issue for it, because I can probably only fix it tomorrow :)
https://github.com/brendt/rfc-vote/issues/217


supabase-cli not working in an environment with SELinux

Bug report
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Go to '…'
Click on '…'
Scroll down to '…'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information

OS: [e.g. macOS, Windows]
Browser (if applies) [e.g. chrome, safari]
Version of supabase-js: [e.g. 6.0.2]
Version of Node.js: [e.g. 10.10.0]

Additional context
Add any other context about the problem here.

Apologies, I accidentally hit the enter key before writing things out. Closing this in favor of a new submission!


Improve unit test coverage: BuildCDEvent::buildPipelineRunStartedModel

This issue reserved for Fidelity Open Source Workshop
We would like to increase our unit test coverage, to ensure our methods are returning sensible objects. In this case, we want to ensure BuildCDEvent::buildPipelineRunStartedModel returns a CloudEvent object, specifically one with a "type" field indicative of the Pipeline Run Started event, and the "pipelinename" extension accurately reflecting the getFullDisplayName() return value of Run getParent() result.
To limit the amount of mocking/stubbing, we recommend Mockito to create mocks for the Run / Job / TaskListener objects normally created by Jenkins. You may also used MockedStatic to mock static dependencies outside of the BuildCDEvent class (such as ModelBuilder).
To get started:

Create BuildCDEventTest.java in src/test/java/io/jenkins/plugins/cdevents
Add the Mockito extension to the test class with @ExtendWith(MockitoExtension.class)
Set up your mocks objects for the hudson.model.Run, hudson.model.Job and hudson.model.TaskListener objects we will be passing in to the method under test. (Tip: use Mockito's RETURNS_DEEP_STUBS feature)
In your test method, wrap the test in a try-with-resources block that sets up a MockedStatic instance of ModelBuilder. When ModelBuilder.buildJobModel(...) is called, you may return a new empty JobModel object.
Review the code for buildPipelineRunStartedModel in BuildCDEvent, and set the appropriate when(...).thenReturn(...) behavior needed for your test.
Call BuildCDEvent.buildPipelineRunStartedModel(...). Assert that .getType() and .getExtension("pipelinename") have the correct values.

I would like to address this issue


fails when current_path doesn't exist

title says all...

Thanks, when does current_path not exist, on the first deploy ever I guess?

Exactly.


Make uploads work with tus and through gateway

This PR makes uploads work with tus and uploads and downloads through the reva data gateway. Reva also provides the option to configure storage mount paths, which is now also handled.
With the default ocmd-server-1.toml config,
WOPI_STORAGE=cs3 python3 test_storageiface.py
...........
----------------------------------------------------------------------
Ran 11 tests in 0.389s

OK

There was one bug with both tus and gateway enabled, which will be fixed by this.

Very nice, thanks for this. I'd suggest a minor addition: add to the reference config file https://github.com/cs3org/wopiserver/blob/master/wopiserver.conf this extra parameter with a one-line comment about it.
And a more general question: what is the relation between the multiple Reva mount points and the storage ids?

@glpatcern thanks for the review! Added the reference in the config file.
Mount paths in reva can be used to restrict access to a set of resources for different users. For example, we usually have two storage providers running in reva. One can be mounted at /home and the other at /reva. All requests with paths starting with /home would be redirected to the logged-in user's namespace. If the user wants to access a file shared with him by another user, this won't be possible through this as the file won't be present in the current user's namespace. So such requests would be identified internally and redirected to the other storage provider which would have access to all the resources. Since both the storage providers point to the same root directory, they share the storage ids

And it was decided some time back that the home storage provider should always be mounted at /home https://github.com/cs3org/reva/issues/601. I've also updated the same in the ocmd toml file.

Thanks for the details and the reference, good to know.
So we can assume that /home will always be present, and possibly others too depending on the deployment, right? In that case, we should probably make the option uncommented with its default value /home. At the same time, the question is whether this should rather be a per-request parameter rather than a configuration option (or maybe I missed something). What do you think?

Yes, ideally requests can indeed go to different mounts. Requests to shared resources would be mounted on /home only (e.g. /home/Shares/shared_file.md), but we can have mounts such as /eos/home and /eos/project. It depends on what wopi knows about the reva mount paths. If we can assume that requests from wopi would always have either of these supported prefixes then we can get rid of this config in the first place. If not, we would need these for each mount.

For the record, we agreed to remove revamountpath from the production config, given that Reva will dispatch according to its configuration. Nevertheless, the test suite has been extended to support this concept (with /home as value); this is similar to how the xrootiface.py layer used to work (and still has code for that, though it's not used in production any longer).
That said, tests pass, therefore I'm merging this.


[FEATURE] create Saved Searches component

Display user's Saved Searches in a data table. Should be able to edit the search collection and view the results of each search.

included in #151


game over lua gone

Describe your problem here.
the Lua file download for changing the game over screen is gone
i use the precompiled version of psych engine
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

I found the script somewhere else but still


[FEATURE]: Notification exports

Scope
Developer API
Feature Description
Add exports for the notification system that is used for errors (Shown below)

Use Case
Utilise this feature in scripts, for example: Simple notifications for players getting cash
Proposed Solution
Add NUIMessages in client side and then add them into exports with several properties, I would have to check out the original source for the notification system: https://github.com/iamhosseindhv/notistack for the properties available.
Additional Info
I think there are already made functions in the source, so could just use that, not sure how tho...

Hi @JajarGaming
This would be a possible candidate for the txAdmin export API, it would be better to congregate thoughts and suggestions under #442.
I will say though, that having exports available for these internal notifications seems outside of scope for inclusion in a public API. txAdmin isn't a notification script, and users shouldn't be relying on txAdmin for that purpose.


Kernel able to access variables which are not passed to the kernel launch

I have observed that a variable which is defined outside the kernel and not passed to it either, is accessible by name within the kernel. Please check the code below
import warp as wp
import numpy as np
wp.init()
@wp.kernel
def calculations(J : int):
i = wp.tid()
wp.printf('\n p val is %d', p)
p= 10
J = 5
wp.launch(calculations, dim=1, inputs=[J])
Variable p is not being passed onto the kernel but when I run the code, the print statement gives the value of p that I have defined.
Is this an expected behavior or a bug?

Hi @nithinsomu, it is expected - this is mostly to support the case where you have some numeric constants in global scope that you would like to access in the kernel. Typically these should be declared with value = wp.constant(3.141) syntax (which will ensure that kernel caching etc works correctly).
Cheers,
Miles


Add Docker Sponsoring to website

I'm waiting for the docker legal team with a set of logos we can use.


[PE-D] Accept Invalid name

Add command allow name to have number
Input: add n/101<EMAIL_ADDRESS>m/CS2103T T12 p/91238456 h/@BenIsHere r/Overseas
Expectation: Reject with error message
Actual:

Labels: severity.Medium type.FunctionalityBug
original: jeromewjj/ped#8

Should we allow names to have numbers?


Garlic or Onion or Bulb emoji

Onions, garlic and some flowers, e.g. tulips, grow characteristic and similar-looking bulbs, which may look different inside: onions have layers, garlic has cloves. Spring onions are possibly covered reasonably well by the Herb emoji 🌿 U+1F33F.
Petitions

change.org: Garlic
change.org: Onion

https://github.com/clinty/emojiproposals/blob/master/garlic.markdown

Onion and Garlic are Candidates for Emoji 12.0 (2019).


[ZEPPELIN-4063] Don't include noteId for constructing Interpreter GroupId when under isolated per user mode

What is this PR for?
It is a straightforward fix to correct the groupId in different isolated mode.
What type of PR is it?
[Bug Fix ]
Todos

[ ] - Task

What is the Jira issue?

https://jira.apache.org/jira/browse/ZEPPELIN-4063

How should this be tested?

CI pass

Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Will merge if no more comment


Automatically exclude Mill transitive depedencies from build classpath

Plugins should add Mill dependencies as provided, but sometimes they don't and Mill breaks when you update Mill to a newer version which adds new fields to traits.
Mill could solve the problem by automatically add exclusion rules for mill-scalalib and its other artifacts when adding dependencies to the build via import $ivy..

This was already fixed in https://github.com/com-lihaoyi/mill/pull/3189.
I just triggered a new snapshot release for it.

I tried with the latest snapshot but it doesn't seem to be solved.
Reproduction:
// build.sc
import $ivy.`com.disneystreaming.smithy4s::smithy4s-mill-codegen-plugin::0.18.22`

import mill._
import mill.scalalib._

object root extends RootModule with ScalaModule {
  def scalaVersion = "3.4.2"
}

.mill-version
0.11.7-118-56323c

Errors with:
java.lang.AbstractMethodError: Receiver class millbuild.build$root$ does not define or inherit an implementation of the resolved method 'abstract mill.define.ModuleRef mill$scalalib$JavaModule$$super$zincWorker()' of interface mill.scalalib.JavaModule.
    mill.scalalib.JavaModule.zincWorker(JavaModule.scala:38)
    mill.scalalib.JavaModule.zincWorker$(JavaModule.scala:38)
    millbuild.build$root$.zincWorker(build.sc:27)
    mill.scalalib.ScalaModule.$anonfun$compile$1(ScalaModule.scala:287)
    scala.collection.mutable.HashMap.getOrElseUpdate(HashMap.scala:469)
    mill.moduledefs.Cacher.cachedTarget(Cacher.scala:10)
    mill.moduledefs.Cacher.cachedTarget$(Cacher.scala:9)
    mill.define.Module$BaseClass.cachedTarget(Module.scala:58)
    mill.scalalib.ScalaModule.compile(ScalaModule.scala:280)
    mill.scalalib.ScalaModule.compile$(ScalaModule.scala:280)
    millbuild.build$root$.compile(build.sc:27)
    java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    java.base/java.lang.reflect.Method.invoke(Method.java:566)
    mill.resolve.Resolve$.$anonfun$instantiateTarget$2(Resolve.scala:96)

I guess to understand this issue better, we should draft an integration test for reproduction. Then we can try to fix this on Mill's side.

This seems related to https://github.com/com-lihaoyi/mill/issues/2985

This seems related to #2985

I don't think so. #2985 is explicitly bumping a dependency, which is supposed to be provided by Mill. This is different from resolving a transitive dependency.

The issue is, the exclusion filter introduced in #3189 contains less mill modules and transitive dependencies then I thought, hence the filtering in incomplete.


How to Properly Change Different Wind Directions

Hi everyone,
Recently I wanted to test the turbine's response to different wind directions. In the "5MW_OC4Semi_WSt_WavesWN" case, the default wind propagation direction is 0° (aligned with the positive X-axis, PropagationDir = 0°), and the turbine rotor and nacelle are directly facing the incoming wind (NacYaw = 0°, aligned with the negative X-axis).
I generated a turbulent wind field using TurbSim and changed the wind propagation direction in InflowWind to 90° (PropagationDir = 90°). Then I encountered some issues: Do I need to adjust other parameters? Should I set NacYaw to 90° in ElastoDyn to ensure the turbine faces the wind directly?
I tried this approach, but the program failed to run due to aerodynamic errors (see the first figure below). However, if I keep NacYaw = 0°, the program runs but still shows some warnings (see the second figure below). What adjustments should I make?

Thanks in advance.

Dear @axxyyyyyyyy378,
To minimize yaw error/misalignment, you should change the yaw angle when you change the wind direction.
However, PropagationDir in InflowWind uses meteorological convention (positive PropagationDir is clockwise when viewed from above) whereas the yaw angle in OpenFAST uses right-hand rule convention (positive NacYaw is counterclockwise when viewed from above).  Thus, to minimize yaw error/misalignment, you should set NacYaw = -PropagationDir.
Note that if you change NacYaw and the nacelle-yaw degree of freedom of ElastoDyn is enabled (YawDOF = TRUE), you should also set YawNeut in the ServoDyn module equal to NacYaw or the nacelle will quickly snap from NacYaw back to YawNeut due to the nacelle-yaw spring in ServoDyn.
Best regards,

Dear @jjonkman,
Thank you for your professional response. My issue has been resolved.
Best regards,


EXO DNS Tests do not support cross platform

Currently the tests added in #271 do not support cross-platform use given a dependency on Resolve-DnsName.
A check for -not $IsWindows and then use of a cross-platform library will be necessary, such as https://github.com/rmbolger/DnsClient-PS.
Search Refs:
Test-MtCisaSpfRestriction	MS.EXO.2.1v1
Test-MtCisaSpfDirective	MS.EXO.2.2v1
Test-MtCisaDkim	MS.EXO.3.1v1
Test-MtCisaDmarcRecordExist	MS.EXO.4.1v1
Test-MtCisaDmarcRecordReject	MS.EXO.4.2v1
Test-MtCisaDmarcAggregateCisa	MS.EXO.4.3v1
Test-MtCisaDmarcReport	MS.EXO.4.4v1

With #322 this is now supported.


Can no longer train custom models with the newer version of trl

So in the previous versions, I was able to train some custom models (not pure transformers model) by wrapping the model as follows:
class WrappedModel(torch.nn.Module):
	def __init__(self, model):
		super().__init__()
		self.model = model

	def forward(self, *args, **kwargs):
		return self.model.forward(*args, **kwargs)

	def train(self):
		return self.model.train()

	def eval(self):
		return self.model.eval()

	def parameters(self):
		return self.model.parameters()

Then I was just using SFTTrainer and calling model=WrappedModel(model) and it was working fine.
Now it complains about:

ValueError: Unable to create tensor, you should probably activate truncation and/or padding with 'padding=True' 'truncation=True' to have batched tensors with the same length. Perhaps your features (text in this case) have excessive nesting (inputs type list where type int is expected).

and if I remove remove_unused_columns=False it complains about the index of the data:

IndexError: Invalid key: 1088 is out of bounds for size 0

The same code with a transformers model works.
I am not sure why would it complain about the data/tokenization. Is there something I need to add in my wrapped model after the latest updates?
Thank you in advance!

Hi @mobicham ! 👋
Great to see you here !
Do you have a simple reproducer snippet using SFTTrainer & a small dataset, let's say imdb - do you also have an idea on from when it started failing for you?

Hi @younesbelkada ! Thank you for your reply!
So it was working fine about a month ago. You can find an example here: https://github.com/mobiusml/hqq/blob/master/examples/lora/train_hqq_lora_example.py . This should produce:

ValueError: Unable to create tensor, you should probably activate truncation and/or padding with 'padding=True' 'truncation=True' to have batched tensors with the same length. Perhaps your features (text in this case) have excessive nesting (inputs type list where type int is expected).

The only reason I wrap the model is because it complains it can't use the function parameters() , but it is already there. The wrapping fixed that issue at that time.


Use class MRO to determine field origin

Description
When generating StrawberryFields for a dataclass, use the classes MRO to decide the origin. This fixes errors that can occur if a name used type annotation in a base class (from a different module) is not available in the module of the child class.
Types of Changes

[ ] Core
[x] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[ ] Documentation

Issues Fixed or Closed by This PR
None
Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Hi, thanks for contributing to Strawberry 🍓!
We noticed that this PR is missing a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!
So as soon as this PR is merged, a release will be made 🚀.
Here's an example of RELEASE.md:
Release type: patch

Description of the changes, ideally with some examples, if adding a new feature.

Release type can be one of patch, minor or major. We use semver, so make sure to pick the appropriate type. If in doubt feel free to ask :)

That's interesting, @dbowring can you add a test showing the issue? 😊

@patrick91 Updated with a test.


Reusing engines from different threads

My observation is that passing an engine connected to an in-memory duckdb database to a different thread doesn't work.
I'm wondering if that's expected or if it would be considered a bug / missing feature?
Example:
import anyio
import sqlalchemy as sa
from sqlalchemy.orm import (
    DeclarativeBase,
    Mapped,
    Session,
    mapped_column,
)

class Base(DeclarativeBase):
    pass

seq = sa.Sequence("user_id")

class User(Base):
    __tablename__ = "Users"
    id: Mapped[int] = mapped_column(
        seq,
        server_default=seq.next_value(),
        primary_key=True,
    )
    name: Mapped[str] = mapped_column(sa.String(30))

engine = sa.create_engine("duckdb:///:memory:")
Base.metadata.create_all(bind=engine)

with Session(engine) as session:
    spongebob = User(name="spongebob")
    sandy = User(name="sandy")
    patrick = User(name="patrick")
    session.add_all([spongebob, sandy, patrick])
    session.commit()

def run_query(engine: sa.Engine):
    with engine.connect() as conn:
        return conn.execute(sa.text("select * from Users")).fetchall()

Running the run_query function works as expected:
>>> run_query(engine)
[(1, 'spongebob'), (2, 'sandy'), (3, 'patrick')]

...but if I run it in a background thread I get a Catalog Error: Table with name Users does not exist! exception 😔
My assumption is that the engine loses it's connection to the in-memory database in the main thread and creates a new in-memory database where that table doesn't exist?

>>> await anyio.to_thread.run_sync(run_query, engine)
---------------------------------------------------------------------------
CatalogException                          Traceback (most recent call last)
File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/sqlalchemy/engine/base.py:1967, in Connection._exec_single_context(self, dialect, context, statement, parameters)
   1966     if not evt_handled:
-> 1967         self.dialect.do_execute(
   1968             cursor, str_statement, effective_parameters, context
   1969         )
   1971 if self._has_events or self.engine._has_events:

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/sqlalchemy/engine/default.py:941, in DefaultDialect.do_execute(self, cursor, statement, parameters, context)
    940 def do_execute(self, cursor, statement, parameters, context=None):
--> 941     cursor.execute(statement, parameters)

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/duckdb_engine/__init__.py:140, in CursorWrapper.execute(self, statement, parameters, context)
    139     else:
--> 140         self.__c.execute(statement, parameters)
    141 except RuntimeError as e:

CatalogException: Catalog Error: Table with name Users does not exist!
Did you mean "sqlite_master"?
LINE 1: select * from Users
                      ^

The above exception was the direct cause of the following exception:

ProgrammingError                          Traceback (most recent call last)
Cell In[10], line 1
----> 1 await anyio.to_thread.run_sync(run_query, engine)

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/anyio/to_thread.py:56, in run_sync(func, abandon_on_cancel, cancellable, limiter, *args)
     48     abandon_on_cancel = cancellable
     49     warn(
     50         "The `cancellable=` keyword argument to `anyio.to_thread.run_sync` is "
     51         "deprecated since AnyIO 4.1.0; use `abandon_on_cancel=` instead",
     52         DeprecationWarning,
     53         stacklevel=2,
     54     )
---> 56 return await get_async_backend().run_sync_in_worker_thread(
     57     func, args, abandon_on_cancel=abandon_on_cancel, limiter=limiter
     58 )

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/anyio/_backends/_trio.py:1060, in TrioBackend.run_sync_in_worker_thread(cls, func, args, abandon_on_cancel, limiter)
   1057         return func(*args)
   1059 token = TrioBackend.current_token()
-> 1060 return await run_sync(
   1061     wrapper,
   1062     abandon_on_cancel=abandon_on_cancel,
   1063     limiter=cast(trio.CapacityLimiter, limiter),
   1064 )

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/trio/_threads.py:437, in to_thread_run_sync(sync_fn, thread_name, abandon_on_cancel, limiter, *args)
    433 msg_from_thread: outcome.Outcome[RetT] | Run[object] | RunSync[object] = (
    434     await trio.lowlevel.wait_task_rescheduled(abort)
    435 )
    436 if isinstance(msg_from_thread, outcome.Outcome):
--> 437     return msg_from_thread.unwrap()
    438 elif isinstance(msg_from_thread, Run):
    439     await msg_from_thread.run()

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/outcome/_impl.py:213, in Error.unwrap(***failed resolving arguments***)
    211 captured_error = self.error
    212 try:
--> 213     raise captured_error
    214 finally:
    215     # We want to avoid creating a reference cycle here. Python does
    216     # collect cycles just fine, so it wouldn't be the end of the world
   (...)
    225     # methods frame, we avoid the 'captured_error' object's
    226     # __traceback__ from indirectly referencing 'captured_error'.
    227     del captured_error, self

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/trio/_threads.py:363, in to_thread_run_sync.<locals>.report_back_in_trio_thread_fn.<locals>.do_release_then_return_result()
    357 def do_release_then_return_result() -> RetT:
    358     # release_on_behalf_of is an arbitrary user-defined method, so it
    359     # might raise an error. If it does, we want that error to
    360     # replace the regular return value, and if the regular return was
    361     # already an exception then we want them to chain.
    362     try:
--> 363         return result.unwrap()
    364     finally:
    365         limiter.release_on_behalf_of(placeholder)

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/outcome/_impl.py:213, in Error.unwrap(***failed resolving arguments***)
    211 captured_error = self.error
    212 try:
--> 213     raise captured_error
    214 finally:
    215     # We want to avoid creating a reference cycle here. Python does
    216     # collect cycles just fine, so it wouldn't be the end of the world
   (...)
    225     # methods frame, we avoid the 'captured_error' object's
    226     # __traceback__ from indirectly referencing 'captured_error'.
    227     del captured_error, self

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/trio/_threads.py:382, in to_thread_run_sync.<locals>.worker_fn()
    380 PARENT_TASK_DATA.task_register = task_register
    381 try:
--> 382     ret = context.run(sync_fn, *args)
    384     if inspect.iscoroutine(ret):
    385         # Manually close coroutine to avoid RuntimeWarnings
    386         ret.close()

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/anyio/_backends/_trio.py:1057, in TrioBackend.run_sync_in_worker_thread.<locals>.wrapper()
   1055 def wrapper() -> T_Retval:
   1056     with claim_worker_thread(TrioBackend, token):
-> 1057         return func(*args)

Cell In[8], line 3, in run_query(engine)
      1 def run_query(engine: sa.Engine):
      2     with engine.connect() as conn:
----> 3         return conn.execute(sa.text("select * from Users")).fetchall()

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/sqlalchemy/engine/base.py:1418, in Connection.execute(self, statement, parameters, execution_options)
   1416     raise exc.ObjectNotExecutableError(statement) from err
   1417 else:
-> 1418     return meth(
   1419         self,
   1420         distilled_parameters,
   1421         execution_options or NO_OPTIONS,
   1422     )

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/sqlalchemy/sql/elements.py:515, in ClauseElement._execute_on_connection(self, connection, distilled_params, execution_options)
    513     if TYPE_CHECKING:
    514         assert isinstance(self, Executable)
--> 515     return connection._execute_clauseelement(
    516         self, distilled_params, execution_options
    517     )
    518 else:
    519     raise exc.ObjectNotExecutableError(self)

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/sqlalchemy/engine/base.py:1640, in Connection._execute_clauseelement(self, elem, distilled_parameters, execution_options)
   1628 compiled_cache: Optional[CompiledCacheType] = execution_options.get(
   1629     "compiled_cache", self.engine._compiled_cache
   1630 )
   1632 compiled_sql, extracted_params, cache_hit = elem._compile_w_cache(
   1633     dialect=dialect,
   1634     compiled_cache=compiled_cache,
   (...)
   1638     linting=self.dialect.compiler_linting | compiler.WARN_LINTING,
   1639 )
-> 1640 ret = self._execute_context(
   1641     dialect,
   1642     dialect.execution_ctx_cls._init_compiled,
   1643     compiled_sql,
   1644     distilled_parameters,
   1645     execution_options,
   1646     compiled_sql,
   1647     distilled_parameters,
   1648     elem,
   1649     extracted_params,
   1650     cache_hit=cache_hit,
   1651 )
   1652 if has_events:
   1653     self.dispatch.after_execute(
   1654         self,
   1655         elem,
   (...)
   1659         ret,
   1660     )

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/sqlalchemy/engine/base.py:1846, in Connection._execute_context(self, dialect, constructor, statement, parameters, execution_options, *args, **kw)
   1844     return self._exec_insertmany_context(dialect, context)
   1845 else:
-> 1846     return self._exec_single_context(
   1847         dialect, context, statement, parameters
   1848     )

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/sqlalchemy/engine/base.py:1986, in Connection._exec_single_context(self, dialect, context, statement, parameters)
   1983     result = context._setup_result_proxy()
   1985 except BaseException as e:
-> 1986     self._handle_dbapi_exception(
   1987         e, str_statement, effective_parameters, cursor, context
   1988     )
   1990 return result

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/sqlalchemy/engine/base.py:2355, in Connection._handle_dbapi_exception(self, e, statement, parameters, cursor, context, is_sub_exec)
   2353 elif should_wrap:
   2354     assert sqlalchemy_exception is not None
-> 2355     raise sqlalchemy_exception.with_traceback(exc_info[2]) from e
   2356 else:
   2357     assert exc_info[1] is not None

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/sqlalchemy/engine/base.py:1967, in Connection._exec_single_context(self, dialect, context, statement, parameters)
   1965                 break
   1966     if not evt_handled:
-> 1967         self.dialect.do_execute(
   1968             cursor, str_statement, effective_parameters, context
   1969         )
   1971 if self._has_events or self.engine._has_events:
   1972     self.dispatch.after_cursor_execute(
   1973         self,
   1974         cursor,
   (...)
   1978         context.executemany,
   1979     )

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/sqlalchemy/engine/default.py:941, in DefaultDialect.do_execute(self, cursor, statement, parameters, context)
    940 def do_execute(self, cursor, statement, parameters, context=None):
--> 941     cursor.execute(statement, parameters)

File /opt/python/envs/dev310/.pixi/envs/default/lib/python3.10/site-packages/duckdb_engine/__init__.py:140, in CursorWrapper.execute(self, statement, parameters, context)
    138         self.__c.execute(statement)
    139     else:
--> 140         self.__c.execute(statement, parameters)
    141 except RuntimeError as e:
    142     if e.args[0].startswith("Not implemented Error"):

ProgrammingError: (duckdb.duckdb.CatalogException) Catalog Error: Table with name Users does not exist!
Did you mean "sqlite_master"?
LINE 1: select * from Users
                      ^
[SQL: select * from Users]
(Background on this error at: https://sqlalche.me/e/20/f405)

IF I change the run_query function to instead accept a sa.Connection then the query works in a background thread:
>>> def run_query(conn: sa.Connection):
...     return conn.execute(sa.text("select * from Users")).fetchall()

>>> with engine.connect() as conn:
...     res = run_query(conn)

>>> res
[(1, 'spongebob'), (2, 'sandy'), (3, 'patrick')]

>>> with engine.connect() as conn:
...     res = await anyio.to_thread.run_sync(run_query, conn)

>>> res
[(1, 'spongebob'), (2, 'sandy'), (3, 'patrick')]

It would be great if it were possible to pass an engine to s separate thread to use so you could use the same code irrespective of whether you were connected to a Postgres database in production or a duckdb in-memory database in CI.

Calling back into the main-thread from the worker thread seems to work, but then it only works from the worker-thread context, so, not ideal.
def run_query(engine: sa.Engine):
    with anyio.from_thread.run_sync(engine.connect) as conn:
        return conn.execute(sa.text("select * from Users")).fetchall()


Customization of the platform to meet Code for Nepal color guidelines

hi team, we use three colors at code for nepal:
Red: #E00015
Blue: #00ADEF
White: #ffffff
for example, check out www.asknepal.info

I'll look into this.

@studenton thanks for making some changes! Could you pls also make the background white? and then pls push the update to reflect on http://<IP_ADDRESS>:8000/

@ravinepal I'll need the server details for http://<IP_ADDRESS>:8000 to push the changes.

thanks, @studenton/ @prashishh and @prerakpradhan -- grateful if you could email server details at<EMAIL_ADDRESS>and<EMAIL_ADDRESS>We will share with Cliff as well.  Thanks! (We should make some of these changes soon to avoid any copyright issue. Amit is kindly making it a priority.)


Feature: Upload image to cloudinary API and style page

In this PR I fixed my code to be much cleaner and more readable. The image is now uploading to the cloudinary API. I also styled the profile page to fit our wireframe
Trello: https://trello.com/c/tqLZJ9ny

 Component: Profile


Sorting

is it possible to configure the sorting of the links (modified, alpha, added, ...)?

Not on my side, it would require changes to the core of Shaarli. Therefore, the request has to be made on the official Shaarli repository: https://github.com/shaarli/Shaarli .


fix<EMAIL_ADDRESS>

I fixed everything as you said

I got it from your earlier PR, I will be putting this and more changes into the main branch and pushing soon. Thanks!

That is, will you bring it in with your own hands?

Consider my proposal as well.
Instead of replace | tail with the -b option.
What do you think?

I don't understand what you mean. The only | tail is in failmsg.sh line 27
log=$(${journalctlPrefix} -u "$unitName" | tail)
The -b switch for journalctl will show only since last boot and tail doesn't have a -b
What I want to happen here is only the last several lines (tail defaults to 10 lines) because these logs are sometimes very long for an email.

Well, with the tail command, you filter out only the end in the output, and at the end that the last start of the service is correct, or rather its output.


Remove duplication

I simplified the code a bit and removed the code duplication.

Wait, that was a PR to the wrong branch


Add cli version to the headers

Add the current cli version to the requests header so we know which version the request came from

Reverted because of error:
https://github.com/UffizziCloud/quickstart-k8s/actions/runs/5937219299/job/16099230100


Image upload

For production, webpack usually creates a folder(dist) with static files including photos and such.  My issue is when a user upload a photo on the website, how can webpack reload and rebuild so that it includes the photo in the dist folder?

This is more of a support question and would be better suited to something like stack overflow.
In short, what you're trying to do isn't something we recommend using webpack for. Uploaded content would typically be handled by either a separate service from your core application (e.g. a ReSTful API) or some other node script on the web server. These images would typically be stored elsewhere, not in /dist. In the vast majority of cases, /dist should be something you generate once per release.
Doing a compilation in the middle of user interaction would be extremely expensive and not very performant. You'd probably maintain a /user-images directory elsewhere on the server or on another server (e.g. an S3 bucket). Again, this question is better suited for stack overflow. You may get a more detailed answer there (although you may want to phrase it differently).


WIP PAF-213 Alter mapping names for two fields

rdaboutcontactRO
rdabout18RO
What?
Why?
How?
Testing?
Screenshots (optional)
Anything Else? (optional)

Closing as this was not the correct solution


[Win 7] Installation successful but TAP driver is not installed

I downloaded the latest installer from the site. Could reproduce this issues twice on physical machine with Windows 7 Max RU.
2016-07-01_Subutai_install_log.txt

Redistributables Installation phase skipped.


Update README.md to remove the need for specific boringSSL version

Remove the need for specific boringSSL version following https://github.com/litespeedtech/lsquic/issues/432 and test that latest boringSSL and latest lsquic compile and work properly

Should not remove it, as BoringSSL may have changes that breaks integration due to API changes. we can update the commit hash instead.

Hi,
Please note that fixating the boringSSL version exposes the library to
vulnerabilities. Since the prior version hash boringSSL had fixed to my
count 6 high and critical severity CVEs relevant to lsquic flows.
I may suggest to prefer a broken build rather than the possibility to
include vulnerabilities due to underlying libraries dependencies.
Regards,
Tzvi Katz
On Mon, Dec 19, 2022, 18:32 LiteSpeed Tech @.***> wrote:

Should not remove it, as BoringSSL may have changes that breaks
integration due to API changes. we can update the commit hash instead.
—
Reply to this email directly, view it on GitHub
https://github.com/litespeedtech/lsquic/pull/444#issuecomment-1357929396,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMTYAIJBMA5U3SL5DFAQWN3WOCE3PANCNFSM6AAAAAATDKW6AY
.
You are receiving this because you authored the thread.Message ID:
@.***>

The readme has been updated that it is OK to try the latest boringSSL.

Great, thanks!
On Thu, Jan 26, 2023 at 3:56 PM LiteSpeed Tech @.***>
wrote:

The readme has been updated that it is OK to try the latest boringSSL.
—
Reply to this email directly, view it on GitHub
https://github.com/litespeedtech/lsquic/pull/444#issuecomment-1405041200,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMTYAIJGA5K4QHPL5VFHXDLWUJ67ZANCNFSM6AAAAAATDKW6AY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Syncing upstream ipfs-service-provider

:tada: This PR is included in version 1.13.9 :tada:
Your semantic-release bot :package::rocket:


After Authentication To ABAP GIT private account, a Runtime Error is Raised

With the latest Update (21.09.2020) ,
After submitting the credentials of a Personal Github account, the dumb is being raised :

An exception has occurred in a class constructor. This exception is
assigned to class 'CX_SY_CREATE_OBJECT_ERROR'.
Since the exception was not caught in the constructor, processing was
terminated. The reason for the exception is:
An attempt was made to assign an object reference (class
"ZCL_ABAPGIT_2FA_GITHUB_AUTH", view "global")
to an interface reference (interface "ZIF_ABAPGIT_2FA_AUTHENTICATOR", view
"ZABAPGIT_FULL"). Class "ZCL_ABAPGIT_2FA_GITHUB_AUTH" does not
support interface "ZIF_ABAPGIT_2FA_AUTHENTICATOR" however.

does a global class zcl_abapgit_2fa_github_auth exist in your system? if so it must be deleted
the 2FA implementation will soon be deprecated by github, so its been removed from abapGit, https://github.com/larshp/abapGit/pull/3839

I just deleted zcl_abapgit_2fa_github_auth and it is working well.
Thank you!


Would you please explain how you calculated the scores for each organ?

Hi, Thanks for your great work, and can you give me some help regarding each multi-organ result of Aorta,Kidnely etc.? How did you estimate because I got the average results for DSC and HD95 but still struggling to understand how to get the result for each organ, which you mentioned in your Table 3.

save your model at the training stage and run test.py to get each multi-organ result.

I got it and thanks for the reply.


Can I turn off KVM acceleration?

Operating system
Ubuntu 24.04
Description
Hello
I'm trying to run this inside of a VM and no I don't have nested virtualization on my CPU.
I get this message
 ERROR: See the FAQ on how to diagnose the cause, or continue without KVM by setting KVM=N (not recommended).

So there's a way to turn this off in vdsm but is there a way I can do this using the config file?
I just commented out KVM device.
thanks
Docker compose
services:
dsm:
container_name: dsm
image: vdsm/virtual-dsm
environment:
DISK_SIZE: "256G"
devices:
- /dev/kvm
  - /dev/net/tun
cap_add:
  - NET_ADMIN
ports:
  - 5000:5000
volumes:
  - /var/dsm:/storage
stop_grace_period: 2m

Docker log
 ✔ Container dsm  Recreated                                                                              0.4s
Attaching to dsm
dsm  | ❯ Starting Virtual DSM for Docker v7.21...
dsm  | ❯ For support visit https://github.com/vdsm/virtual-dsm
dsm  | ❯ CPU: Intel Xeon E5 2620 v2 | RAM: 7/8 GB | DISK: 689 GB (ext4) | KERNEL: 6.8.0-50...
dsm  |
dsm  | ❯ ERROR: KVM acceleration not available (device file missing), this will cause a major loss of performance.
dsm  | ❯ ERROR: See the FAQ on how to diagnose the cause, or continue without KVM by setting KVM=N (not recommended).
dsm exited with code 88

Screenshots (optional)
No response

Well would you look at that :)
dsm  | [ 1230.885180] capability: warning: `nginx' uses 32-bit capabilities (legacy support in use)
dsm  |
dsm  | ❯ -----------------------------------------------------------
dsm  | ❯  You can now login to DSM at port 5000
dsm  | ❯ -----------------------------------------------------------
dsm  |

Thanks


[2.6] Azure AD - remove permissions checks and add an auth config controller

Issue: https://github.com/rancher/rancher/issues/38770
Problem and Solution
We want to allow Azure AD admins to be responsible for their own permission set they are ready to grant to an app in Azure.
That way, they can use narrower permissions (like Directory.Read.All, instead of Group.Read.All + User.Read.All, as both will work with Azure AD actions). However, admins are themselves responsible for making sure they pick those permissions that will fully work with Azure AD in Rancher.
We want to do this to avoid having to maintain a large array of permissions that we check and validate. There are a few permissions that work with all Azure AD actions that Rancher normally performs (logging in, fetching users, groups, etc.). However, customers might have different preferences as to which exact Application permissions to grant to their apps. We don't want to have complicated validating logic, so we instead allow any permissions. If customers choose insufficient permissions, then there will be a failure in Rancher at some point, which they can rectify by quickly disabling or reconfiguring the auth provider and then adjusting their permissions.
Changes proposed:

Do not check access token permissions from Microsoft Graph at all. Neither on login, nor on endpoint updates or initial provider setup. This means that any successful attempt to set up Azure AD, for example, would lead to the access token being cached in a secret.
Introduce an auth provider controller that would delete the cached access token secret, so that admins who make a mistake in choosing the necessary app permissions in Azure can easily disable the auth provider, fix their permissions, and try again without the cache holding a bad access token for up to an hour before an automatic refresh.

Testing

Engineering Testing
Manual Testing

Automated Testing

QA Testing Considerations

Regressions Considerations

QA testing
Context
There are two secrets to watch, both in the cattle-global-data namespace.

azuread-access-token - the access token for Microsoft Graph API.
azureadconfig-applicationsecret - the Application of the app in Azure.

1. Good token

In your Azure app, remove all Microsoft Graph permissions.
Add only the Application permission of type Directory.Read.All.
Run Rancher v2.7-head, set up Azure AD.
No errors.

2. Bad token

In your Azure app, remove all Microsoft Graph permissions (or simply revoke admin consent).
Youp app does not have permissions for Rancher to successfully run different actions against Azure AD.
Run Rancher v2.7-head, set up Azure AD and use your app.
There is an error, since on setup, Rancher tries to fetch the user info you logged in as.
Check both secrets, make sure they don't exist (might need to refresh).
Add Directory.Read.All permission to the app.
Try setting up Azure AD again.
No errors.
Check the secrets, make sure they exist.

Now try a different set of permissions and ensure they work as before.

Revoke consent for the Directory.Read.All permission in the app.
Add Group.Read.All and User.Read.All.
Disable Azure AD. No errors.
Check the azuread-access-token and azureadconfig-applicationsecret secrets. Make sure both have been deleted.
Try setting up Azure AD again.
No errors.
Check both secrets, make sure they exist.


CIP-0030 | deprecate signTx & add chain signing

The signTx endpoint for the dApp connector needs to change. The way we used to have a list of arguments with an optional argument makes any breaking change in the future extremely tedious. It's much better to just provide a JSON object so we can add new features to it
One of the reasons I want to do this is so that we can add the ability for dApps to request signing a chain of transactions. We can achieve this by having the dApp itself provide hints about the contents of the input for the next transaction even if they don't appear on-chain yet.
FAQ
Q: Can't wallets just keep track of pending txs so they know how to sign other transactions in the chain
A: This doesn't work in the generic sense. Here are some cases where this approach would fail:

Some of the inputs may not belong to the user (ex: the dApp may have its own transactions it needs to broadcast as part of its flow)
There is no guarantee the dApp submits transactions through the wallet's submit endpoint

@SebastienGllmt would you mind providing a quick update on that one? Is still relevant / has it been added to CIP-0030 implementations already?

This is still an important CIP that should be implemented. It just got caught up in the CIP30 governance discussion and so it stalled waiting for a decision on that front

That's good to know @SebastienGllmt but then this needs a rebase on CIP-0030 in master particularly after the changes in https://github.com/cardano-foundation/CIPs/pull/446.  I tried to resolve the merge conflict but it would have involved taking material from both sides & so would have had to ask you to proofread the result anyway.

Hey @SebastienGllmt ,
This proposal was discussed today in CIP editors call 68. Are you still interested in pursing this amendment or perhaps there has been a work around discovered? because as it stands I do not think it is advisable to continue to alter CIP-30. Rather I would strongly recommend any more alterations to CIP-30 utilize the extensibility mechanism introduced in #446. This is to avoid the past issues of versioning of CIP-30 for both dApps and wallets, see #446 for discussions.
I would suggest packaging this in with other CIP-30 amendments (such as #443 and/or maybe #206) to create a multi-functional CIP-30 extension. I mentioned this idea in this issue comment. Would you be willing to pursue something like this?

We would like to re-visit this PR. It's important now that more dApps are using transaction chaining.

We would like to re-visit this PR. It's important now that more dApps are using transaction chaining.

Agreed, this PR would benefit the whole of Cardano if it was merged

Although I agree that transaction chaining is a great feature to support, altering the CIP-30 base API would be a mistake, due to lack of versioning.
Instead, this would make a great CIP-30 extension, if someone wishes to take this forward.
Although, with the landscape of #587 this might not be needed.
Due to the age of this PR and it not fitting with the current landscape of CIP-30 extensions, I think we can move to close it cc @rphair @Crypto2099

In sympathy with https://github.com/cardano-foundation/CIPs/pull/209#issuecomment-1988228035 and the last comments from @Ryun1 I'm closing this by quorum but please @Crypto2099, @SebastienGllmt please re-open (after a proper rebase) if there's a need & someone can carry this forward.


TUI is not being redrawn

TUI is not being redrawn if you resize the terminal or change the font size (unless you press a key afterwards).

@AmmarAbouZor can you reproduce this? I'm looking at the changes since the last version but I don't know what might have caused this.


java.lang.ClassNotFoundException at spark application

Hi!
In the case of using sbt-coursier plugin or sbt 1.3.0-RC2 which uses coursier
my project fails to run with exception java.lang.ClassNotFoundException: com.google.common.collect.Maps
Minimal project: https://github.com/narma/hodor
Reproducible with: sbt run
Comment plugin in plugins.sbt resolve the issue.

I'm also suffering from similiar issue, however coursier 1.0.3 works well

@narma I can't reproduce that error with your hodor repo:
$ cat hello.txt
a
b
c
d
a
$ sbt "run hello.txt"
[info] Loading settings for project global-plugins from idea.sbt,plugins.sbt,metals.sbt ...
[info] Loading global plugins from ~/.sbt/1.0/plugins
[info] Loading settings for project hodor-build from plugins.sbt ...
[info] Loading project definition from …/hodor/project
[info] Compiling 1 Scala source to…/hodor/project/target/scala-2.12/sbt-1.0/classes ...
[info] Done compiling.
[info] Loading settings for project root from build.sbt ...
[info] Set current project to Hodor (in build file:…)
[info] Compiling 3 Scala sources to …/hodor/target/scala-2.12/classes ...
[info] Done compiling.
[info] Packaging …/hodor/target/scala-2.12/hodor_2.12-0.1.0-SNAPSHOT.jar ...
[info] Done packaging.
[info] Running (fork) hodor.Main hello.txt
2019-09-17 00:02:15.215+0200  info [Main] start job  - (Main.scala:13)
2019-09-17 00:02:15.712+0200  warn [NativeCodeLoader] Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
2019-09-17 00:02:18.495+0200  info [DataExplorer] Lines count of hello.txt: 5  - (DataExplorer.scala:15)
2019-09-17 00:02:18.496+0200  info [Main] job finished, bye bye  - (Main.scala:17)
[success] Total time: 9 s, completed 17 sept. 2019 00:02:18

Same with the latest sbt-coursier (2.0.0-RC3-5), and with sbt 1.3.0 (removing project/plugins.sbt in that case).

It can be related to this sbt bug (fixed in 1.3.1)

@narma

Yes, just rechecked it myself, run with no issues, thanks!


Unable to delete/redownload models

Not knowing where the download path of the model is, the model cannot be deleted or re-downloaded after downloading. This leads to the fact that if the download fails (especially for Mac M1/M2 series, it still shows downloaded), after testing normal uninstallation or app cleaner & uninstaller uninstallation and reinstallation, the models that show downloaded (actually unsuccessfully downloaded) are still there.
This leads to a weird circle: if the app crashes and exits while downloading a model, that model that failed to download will show up in the downloaded list and then never work, even with a fresh install!

Found the path.
Whisper model file: /Users/UserName/.cache/whisper
Faster Whisper model file: /Users/UserName/.cache/huggingface/hub

Will mark this as closed for now. Let me know if you run into any other issues.


HV-1444 Rebased/Squashed version of Marko's PR

https://github.com/hibernate/hibernate-validator/pull/878
https://hibernate.atlassian.net/browse/HV-1444

and some numbers:
with changes applied:
# Run complete. Total time: 00:01:51

Benchmark                                                                                Mode  Cnt    Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20  241.063 ±  8.683  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  613.279 ± 10.496   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  821.396 ±  9.824   ops/s

  Raw validation time:        1096ms {12342}
  Raw parsing time:              0ms {0}
  First parse and validate:      0ms {0}
  Multithreaded validation:      0ms
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.192 s - in org.apache.bval.bench.BenchTest

======================================================
current (without last commit on potentially CMD):
# Run complete. Total time: 00:01:52

Benchmark                                                                                Mode  Cnt    Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20  212.603 ± 26.591  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  592.819 ± 20.631   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  785.133 ± 13.543   ops/s

  Raw validation time:         884ms {12342}
  Raw parsing time:              0ms {0}
  First parse and validate:      0ms {0}
  Multithreaded validation:      0ms
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.143 s - in org.apache.bval.bench.BenchT

======================================================
master:

# Run complete. Total time: 00:01:53

Benchmark                                                                                Mode  Cnt    Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20  226.021 ± 37.921  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  607.903 ±  8.669   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  860.026 ± 11.842   ops/s

  Raw validation time:         903ms {12342}
  Raw parsing time:              0ms {0}
  First parse and validate:      0ms {0}
  Multithreaded validation:      0ms
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.113 s - in org.apache.bval.bench.BenchTest

Mmmh, did you mess up with the BV benchmark number or is your last version slower than everything and the current version faster than master?
it looks weird to me.

it's possible that I did ... So I've run the tests again :)
current master:
  Raw validation time:         946ms {12342}
  Raw parsing time:              0ms {0}
  First parse and validate:      0ms {0}
  Multithreaded validation:      0ms
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.263 s - in org.apache.bval.bench.BenchTest

with all changes:
  Raw validation time:        1056ms {12342}
  Raw parsing time:              0ms {0}
  First parse and validate:      0ms {0}
  Multithreaded validation:      0ms
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.126 s - in org.apache.bval.bench.BenchTest

they are pretty close, and I think that it's faster with these latest changes because in case we have NonContainerCascadingMetaData we don't call NonContainerCascadingMetaData#addRuntimeLegacyCollectionSupport anymore, which is still called in the code form master (well there is a similar call but in case of NonContainerCascadingMetaData it will just return this).

Also about that BV benchmark.... I think it's possible to convert it to JMH test. We would need to have two modules though. One to generate beans and in the other one we can write a JMH benchmark using those beans.

@marko-bekhta it's slower in your "with all changes" case. Note that the unit here is ms. So the lower the better.
I don't have anything against moving the existing code to a submodule and adding a new module with some JMH testing. It would be nice if we had the same possibilities than the existing benchmark: the ability to test the raw parsing speed and the raw validation speed (having both mixed is of no use IMHO).

Hah, yes ..... It's in ms !!! :smiley: but I did try to build a project with git today instead of mvn so I'm not surprised that I missed the units of a benchmark...
And I just took the "best" numbers from a couple of runs.
Here I've run it once more and copied 5 results for each:
master:
Raw validation time:         900ms {12342}
Raw validation time:         791ms {12342}
Raw validation time:         825ms {12342}
Raw validation time:         886ms {12342}
Raw validation time:         901ms {12342}

changes:
Raw validation time:         834ms {12342}
Raw validation time:         834ms {12342}
Raw validation time:         866ms {12342}
Raw validation time:        1005ms {12342}
Raw validation time:        1123ms {12342}

Mmmmf. I think the only conclusion we can draw is that we really need to move to JMH :).

Finally had a chance to spent some time on this. I've edited the last commit and force-pushed it.
I tried to add explanations in the comments with some examples. Hope those would make it easier to read and understand the changes.

It's not related to VE directly, just encountered one more case where annotations are not read correctly, here's an example:
@Test
public void testTypeVariableAnnotationsIssue() throws Exception {
	class Barrr {
	}
	class MapTest {
		private final Map<@Valid List<@NotBlank String>, @NotNull @Valid Barrr> container;

		MapTest(Map<List<String>, Barrr> container) {
			this.container = container;
		}
	}

	AnnotatedType[] annotatedActualTypeArguments = ( (AnnotatedParameterizedType) MapTest.class.getDeclaredFields()[0].getAnnotatedType() ).getAnnotatedActualTypeArguments();
	assertEquals( annotatedActualTypeArguments.length, 2 );
	assertEquals( annotatedActualTypeArguments[0].getAnnotations().length, 1 );
	assertEquals( annotatedActualTypeArguments[1].getAnnotations().length, 2 ); // this part fails
}

Last assert fails if the type is a local one (Barrr). If it is replaced with for example Integer - everything is ok.

@marko-bekhta might be nice to add an issue with a test case to our JDK issues milestone.

So where are we with that one? Should I do a review pass, too?

Here is the situation:

I want to make a last pass to change a few method names and get the overall thing easier to understand
Marko is working in parallel on the conversion of the BV benchmark to JMH so that we can have stable results and determine the real consequences of this patch

I'll ping you if I think an additional review is required but we should really wait for the final changes and the benchmark results.

in addition I wanted to give you some "free-time-from-Marko" during your F2F meeting :smiley: hence not much activity on this front atm.

@marko-bekhta I'm finally done with this PR. We can check that the performances are not too bad, now :).
Will you do it or should I?

@gsmet :tada: I have some time for it. I'll give it a shot and post results here.

## First run:
INFO: HV000001: Hibernate Validator 6.0.7.Final:

# Run complete. Total time: 00:02:04
Benchmark                                            Mode  Cnt    Score    Error   Units
ParsingBeansSpeedBenchmark.testCascadedValidation   thrpt   20   71.851 ±  6.902  ops/ms
RawValidationSpeedBenchmark.testCascadedValidation  thrpt   30  174.241 ± 11.016   ops/s

# Run complete. Total time: 00:01:49

Benchmark                                                                                Mode  Cnt    Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20  171.268 ± 17.361  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  443.933 ±  5.771   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  719.041 ±  8.809   ops/s

########################################################################################
INFO: HV000001: Hibernate Validator - 6.0.8-SNAPSHOT

# Run complete. Total time: 00:02:00

Benchmark                                            Mode  Cnt    Score   Error   Units
ParsingBeansSpeedBenchmark.testCascadedValidation   thrpt   20   77.417 ± 6.520  ops/ms
RawValidationSpeedBenchmark.testCascadedValidation  thrpt   30  214.495 ± 5.391   ops/s

# Run complete. Total time: 00:01:50

Benchmark                                                                                Mode  Cnt    Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20  176.687 ± 14.551  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  479.938 ±  7.135   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  648.564 ± 14.705   ops/s

and once more:
## Second run:
INFO: HV000001: Hibernate Validator 6.0.7.Final:

# Run complete. Total time: 00:02:06

Benchmark                                            Mode  Cnt    Score    Error   Units
ParsingBeansSpeedBenchmark.testCascadedValidation   thrpt   20   72.326 ± 10.849  ops/ms
RawValidationSpeedBenchmark.testCascadedValidation  thrpt   30  183.109 ±  4.638   ops/s

# Run complete. Total time: 00:01:50

Benchmark                                                                                Mode  Cnt    Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20  163.579 ±  5.531  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  455.314 ±  7.435   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  740.634 ± 17.353   ops/s

########################################################################################
INFO: HV000001: Hibernate Validator - 6.0.8-SNAPSHOT

# Run complete. Total time: 00:01:58

Benchmark                                            Mode  Cnt    Score   Error   Units
ParsingBeansSpeedBenchmark.testCascadedValidation   thrpt   20   70.965 ± 5.177  ops/ms
RawValidationSpeedBenchmark.testCascadedValidation  thrpt   30  210.119 ± 4.036   ops/s

# Run complete. Total time: 00:01:50

Benchmark                                                                                Mode  Cnt    Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20  168.120 ±  8.574  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  503.153 ±  9.834   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  716.397 ± 13.306   ops/s

Later today I'll try to run these on a different machine. I also tried some profiling on CascadedWithLotsOfItemsAndMoreConstraintsValidation, nothing unusual there:
org.hibernate.validator.internal.engine.path.PathImpl.buildHashCode() | 10.282879 | 81,893 ms (10.3%) | 81,893 ms | 81,893 ms | 81,893 ms
org.hibernate.validator.internal.engine.ValidationContext.markConstraintProcessed() | 7.529805 | 59,967 ms (7.5%) | 59,967 ms | 59,967 ms | 59,967 ms
org.hibernate.validator.internal.engine.ValidationContext.markCurrentBeanAsProcessedForCurrentPath() | 5.771458 | 45,964 ms (5.8%) | 45,964 ms | 59,804 ms | 59,804 ms
org.hibernate.validator.internal.util.CollectionHelper.newHashSet() | 5.6387296 | 44,906 ms (5.6%) | 44,906 ms | 44,906 ms | 44,906 ms

Hi @marko-bekhta ,
Thanks for the numbers.
It would probably be nice to try to understand what we do differently in CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems with the new code to make it noticeably slower.

I also think it would be beneficial to run the BV benchmark.

Hi @marko-bekhta,
As the ReflectionHelper#getValue() PR ends up being more complicated than expected, I think we should focus on trying to understand why we have a perf regression on CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems and try to get this one in (finally!).

Also some fresh numbers. (note that last commit doesn't really make any difference it's just that it can never happen and I just think that it would be easier to read without it). So the benchmarks:
single thread 1000 items:
# *Hibernate Validator 6.0.7.Final*
Benchmark                                                                                Mode  Cnt     Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20   176.892 ±  3.046  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20   877.112 ± 13.760   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  1198.482 ± 17.046   ops/s

# *Hibernate Validator 6.0.8-SNAPSHOT*
Benchmark                                                                                Mode  Cnt     Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20   194.530 ±  2.667  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20   857.824 ± 11.153   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  1177.166 ± 16.300   ops/s

single thread 2000 items (regular amount):
# *Hibernate Validator 6.0.7.Final*
Benchmark                                                                                Mode  Cnt    Score   Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20  180.171 ± 2.331  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  431.718 ± 4.602   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  593.008 ± 6.853   ops/s

# *Hibernate Validator 6.0.8-SNAPSHOT*
Benchmark                                                                                Mode  Cnt    Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20  190.509 ±  2.453  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  422.300 ±  4.079   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  581.905 ± 10.974   ops/s

10 threads 2000 items (regular amount):
# *Hibernate Validator 6.0.7.Final*
Benchmark                                                                                Mode  Cnt     Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20   179.879 ±  2.063  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  1369.362 ± 31.438   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  1845.036 ± 25.291   ops/s

# *Hibernate Validator 6.0.8-SNAPSHOT*
Benchmark                                                                                Mode  Cnt     Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20   194.068 ±  2.552  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  1641.228 ± 22.088   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  1951.470 ± 24.349   ops/s

20 threads 2000 items (regular amount):
# *Hibernate Validator 6.0.7.Final*
Benchmark                                                                                Mode  Cnt     Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20   179.347 ±  2.173  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  1344.456 ± 26.267   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  1721.242 ± 30.364   ops/s

# *Hibernate Validator 6.0.8-SNAPSHOT*
Benchmark                                                                                Mode  Cnt     Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20   192.206 ±  2.391  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  1468.377 ± 43.692   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  1753.757 ± 26.439   ops/s

40 threads 2000 items (regular amount):
# *Hibernate Validator 6.0.7.Final*
Benchmark                                                                                Mode  Cnt     Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20   179.848 ±  1.553  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  1368.312 ± 26.805   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  1638.132 ± 29.546   ops/s

# *Hibernate Validator 6.0.8-SNAPSHOT*
Benchmark                                                                                Mode  Cnt     Score    Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20   192.664 ±  1.830  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20  1255.655 ± 26.588   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  1723.268 ± 34.982   ops/s

100 threads 2000 items (regular amount):
# *Hibernate Validator 6.0.7.Final*
Benchmark                                                                                Mode  Cnt     Score     Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20   176.352 ±   1.623  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20   957.121 ±  98.533   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  1551.714 ± 107.216   ops/s

# *Hibernate Validator 6.0.8-SNAPSHOT*
Benchmark                                                                                Mode  Cnt     Score     Error   Units
CascadedValidation.testCascadedValidation                                                  thrpt   20   191.282 ±   2.465  ops/ms
CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems  thrpt   20   972.603 ±  74.376   ops/s
CascadedWithLotsOfItemsValidation.testCascadedValidationWithLotsOfItems                    thrpt   20  1520.292 ± 107.742   ops/s

for all results above  I've kept the CascadedValidation.testCascadedValidation with a single thread.

Looking at these latest benchmarks CascadedWithLotsOfItems* are both just a bit slower with these VE changes up to some number of threads. I've run each of the benchmarks a couple times and the results were consistent all the time.
I did some more debugging, staring at the code changes :) and comparing method call logs yesterday and there's nothing that showed up interesting. That's why I've started to think that maybe it's something to do with multiple threads ? Hence those benchmarks for different number of threads. Based on this could it be that this "strange" behavior of the benchmarks, that ought to behave the same, has something to do with the CHM access?  After the first run when the metadata is available we would only access the CHM just once when getting a runtime VE from the set of candidates.

@marko-bekhta I added the commit b73fe21 with a couple of micro optimizations and here are my results:
changes with the micro optimizations
Result "org.hibernate.validator.performance.cascaded.CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems":
  1373.747 ±(99.9%) 8.356 ops/s [Average]
  (min, avg, max) = (1356.278, 1373.747, 1389.036), stdev = 9.623
  CI (99.9%): [1365.391, 1382.104] (assumes normal distribution)

changes without
Result "org.hibernate.validator.performance.cascaded.CascadedWithLotsOfItemsAndMoreConstraintsValidation.testCascadedValidationWithLotsOfItems":
  1281.256 ±(99.9%) 9.410 ops/s [Average]
  (min, avg, max) = (1265.115, 1281.256, 1301.452), stdev = 10.837
  CI (99.9%): [1271.846, 1290.666] (assumes normal distribution)

So I think we are probably back on track compared to the previous behavior.
Could you take a look at the last 3 commits? I don't expect any issue there but let's be on the safe side. Once I have your go, I'll merge it.

@marko-bekhta yeah, it's not my idea. @Sanne suggested it before in a similar case, that's why I did it.

And finally merged!
@marko-bekhta thanks for your hard work on this one, glad to see it finally in.

Thanks, Marko and Guillaume!


Question

Should i close steam from the taskbar too or just the client window? And what is the chances of this vacbypass .exe getting detected?

You should exit it completely.

it won't get detected, if you get banned, its because of you getting overwatched...

It is detected because it gives red trust factor the moment you start to use it

trust factor has nothing to do with getting "detected". If you have gotten banned on different accounts, but on the same computer, your trust factor will decrease with accounts you already have and on accounts you make in the future on that computer. this is also the case when having the same ip address.
so basically either buy a new computer and new internet, or live with bad or "red" trustfactor. VAC Bypass has nothing to do with trustfactor.

so basically either buy a new computer and new internet, or live with bad/"red" trustfactor.

This doesn't make sense. You can change your HWID or reinstall the OS. Also, you can most likely use a VPN. No need to do this at all.

@TheNulledJester, true you could but just make sure you uninstall steam and reinstall steam, then use a different account, then change your HWID and use a VPN. As you trust factor for each account is saved on steams servers, and saved within your current install of steam.
Then @TheNulledJester, your way would work.
Also when uninstalling steam some file may stay behind, therfore use a 3rd party uninstaller like REVO (https://www.revouninstaller.com/). or as @TheNulledJester said, just reinstall the OS.


[bug] Why no data in CPU / Memory usage?

Describe the bug
I don't have metrics for Namespace(s) usage on total cluster CPU/Memory in % and Memory / CPU usage by Pod,
I have changed image="" with image!="" and it not resolve the issue.
sum(rate(container_cpu_usage_seconds_total{namespace=~"$namespace", image!="", pod=~"${created_by}.*", cluster="$cluster"}[$__rate_interval])) by (pod)

The same with Namespace(s) usage on total cluster CPU in %

How to reproduce?
No response
Expected behavior
I would like to have metrics of usage CPU and memory of cluster.
Additional context
No response

Hi @k-szortyka,
Do you have any series when looking at raw container_cpu_usage_seconds_total in Grafana explore ?
Can you give more information: Kubernetes distribution, Kubernetes version, deployment method/chart...

@dotdc I have any series but I can't filter by cluster or namespace which is crucial.

I use AWS EKS with the following version: 1.29 and kube-metrics 2.11.

Do you have the machine_cpu_cores metric ?
Did you install node_exporter (helm chart) ?

@dotdc Yes I have but without cluster and namespace filters.

I don't have node_exporter. I'm using kube-state-metrics and metrics-server.

@k-szortyka non-existing label shouldn't be an issue.
Can you try with node-exporter ?

@k-szortyka are you running this on minikube/docker environment?

Let me know if it doesn't work with node-exporter or if you have more data.
Closing this issue.

Hi! I was having exactly the same problem. I had the entire prometheus helm chart installed, with node-exporter and everything but no data was showging. Turns out it was the resolution, as mentioned on the Readme of the repo but that left me wondering. Why us the pre defined $__rate_interval of the datasource instead of the resolution variable on each dashboard? That way we could customize the resolution per dashboard and not have to affect the entire system


aggregateLock can't 100% prevent concurrent update

Hi @adrai
I testing the aggregate lock in our end to end integration tests and found that (maybe I'm using it wrongly) it not able to prevent concurrency happening in a multiple processes environment. (example AWS Lambda) perfectly.
Scenario:

3 or more commands (apply to the same aggregate) triggered the domain at the same time.
Each commands handled by different Lambda instance. (sharing same aggregate lock DB)
Each Instance locked the aggregate simultaneously and loaded the same version of history events (3 locks with the same aggregateId, different workId generated )
Instance 1 attempt to commit but failed due to the aggregateCheck, Then, all locks resolved and the command scheduled to be retry.
Instance 2 committed successfully as the lock being resolved by instance 1.
Instance 3 (with outdated history events) also committed successfully after the lock being resolved by instance 2.

I found the following line of code cause this scenario:
cqrs-domain/lib/defaultCommandHandler.js ln 663
if (workerIds.length === 0 || (workerIds.length === 1 && workerIds[0] === self.id)) {
        return callback(null);
}

I suggest we could tighten up the condition like following:
if (workerIds.length === 1 && workerIds[0] === self.id) {
        return callback(null);
}

and we should also allow a bigger retryOnConcurrencyTimeout value so that the retry not coming back at the same time again. Any thought?

Yes, you are right. This was coming from an older version that handled this a bit differently...
Do you want to create a PR?

@adrai  Thanks for your reply. Yes, I will submit a PR after my local end to end testing. Do you agree with my suggestion or you have any better to solve this problem?

your suggestion is perfect


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1914 ms

Resolved: Bofrost.at performance has improved in 2af6cd8 after 6 minutes.


Create default admin user on startup

We should create a default user as part of the deployment of redash. Also this could potentially be added to the output of the module.
Remember to add section to README

Closing as the PR is https://github.com/fredrikhgrelland/terraform-nomad-redash/pull/23 merged.


Display issues on M3 Max

The CPU usage is incorrect (E-CPU, P-CPU Always display 100%) and memory bandwidth is not displayed, ANE Usage has always been 0, May I know when the M3 Max can be adapted?

https://github.com/tlkh/asitop

The homepage display looks like this

Uploading asitop_readme.png…

Hi! I also have the same issue.

The thing is that it doesn't really detect the chip's data, it's hardcoded (here) and as you can see there are no M2 pro/max/ultra nor M3/pro/max
And I have no idea where to find those value to help...

The thing is that it doesn't really detect the chip's data, it's hardcoded (here) and as you can see there are no M2 pro/max/ultra nor M3/pro/max And I have no idea where to find those value to help...

Taking a quick glance it seems to be a rounded value of the bandwidth in GB/sec, so it should be fairly easy to add.
https://en.wikipedia.org/wiki/Apple_M1#Variants
https://en.wikipedia.org/wiki/Apple_M2#Variants
As for the TDP, it looks like it could just be the published or independently measured TDP in watts.

Hey there! So, I’ve had this device for just a couple of days now. I’ve been running multiple Jupyter kernels and processing hundreds of gigabytes of data on it, which means I can use it for like 3-5 hours straight. However, if I process data remotely, I get around 10 hours.

@liyiyuian Using Bandwidth to test memory throughput did not reach the official advertised 400GB/s memory bandwidth.
Graphs generated by bandwidth

Same issue here. M3 Max 40GPU

+1 same issue on M3 Max

Same issue here. M3 Max 30GPU.

Just created #68

@gavi #68
This displays more accurately on the M3 Max 40GPU version ->Power Usage Monitor for Apple Silicon .

@gavi #68 This displays more accurately on the M3 Max 40GPU version ->Power Usage Monitor for Apple Silicon .

So you recommend PUMAS instead of Asitop?

So you recommend PUMAS instead of Asitop?
This is for your reference only!!!

Same issue on M3 Max 40GPU

this PR https://github.com/tlkh/asitop/pull/68 solved this issue on my end

pip install git+https://github.com/gavi/asitop.git

It works fine for my M3 Max


Added ItemAdders support.

I suggest you to update your wiki since I tested with ItemAdders.
First of all users have to do /iacustommodeldata <item>

They have to include ITEM#CUSTOMMODELDATA into config files.

Then they can test in game.

The section your editing is for direct support for ItemsAdder without the need to add #custom_model_data. We have the custom model data format in another section of the wiki which if you want to move that to below Oraxen/ItemsAdder, You can but I'd rather keep all options available.
It seems to not be working at the moment so until I can get a jar to test with from the official source preferably if LoneDev does such things for other developers as I don't own the plugin.

I'll just merge it for the time being now until I can get the jar for it.