coppy

📝 Description
Please include a summary of the change and which issue is fixed.
🔧 Fixes #(issue)

📷 Provide related Screenshot/Gifs if any.

[ ] I have performed a self-review of my own code.
[ ] I'm a contributor in Hacktoberfest'21.

coppy


[engsys] remove dependency fs-extra and @types/fs-extra

PR to remove dependency: Removing "fs-extra" from the repository #9402

Close #19161 and #19183 once this is finished.

Closing this in favor of the bot created #19183 and #19161


Handle all path types

Currently only the :abs_path returned by :erlang.decode_packet/3 are handled.
This adds support for the other types by extracting the path component of the HttpUri returned by decode_packet/3.
Because of the URL construction here, the path must start with a slash, otherwise that will fail, therefore a slash is added to the start of the path if it is not present.
I am not sure if this is the correct or best way to handle the paths, so feedback would be appreciated!

Are such requests specifically allowed by RFC? I'm old enough to remember the days when Apache had all manner of security issues caused by relative URI parsing and it's not a can of worms that I'm keen to open up unless we have to.

RFC9112 should be the current one, but the allowed paths are the same.
RFC9110 also states:

For CONNECT (Section 9.3.6), the request target is the host name and port number of the tunnel destination, separated by a colon.
For OPTIONS (Section 9.3.7), the request target can be a single asterisk ("*").

See the respective method definitions for details. These forms MUST NOT be used with other methods.

To summarize, I think we should have the following behaviour?:

if the request line is an absolute path /path/to/a/thing?a=b, then

path: /path/to/a/thing
query string: a=b
host as defined in Host header

if the request line is an absolute URI http://example.com:8080/path/to/a/thing?a=b, then

path: /path/to/a/thing
query string: a=b
host is example.com (RFC2616§5.2.3 says to ignore Host)

if the request line is *, then:

path: *
host as defined in Host header
Should we return a 400 if method is not OPTIONS (I don't think so, since the specs are loose on this)
host as defined in Host header

If the request line is authority example.com:8080, then

path: ????
host is example.com
Port is required per RFC9110§9.3.6

I don't think we should support relative URIs at all. I don't think any spec references them and it feels like a Pandora's box.

WDYT?

The RFC9112 states:

The "asterisk-form" of request-target is only used for a server-wide OPTIONS request (Section 9.3.7 of [HTTP]).

Returning 400 would be okay in that case.
For the other cases I'm okay with your proposed behaviour.
I'll update PR accordingly.

Yeah but it's never actually called out in screaming case MUST, which is notable (there are also places in 2616 where the language is even looser). My vote would be to push this down to the implementing plug and keep the policy out of bandit.

@mtrudel I think you edited their comment instead of replying ^

So I did! I was on mobile at the time, I guess that's my excuse LOL.
@moogle19 tagging you in case you did t get notified for the 'reply' above

@mtrudel
Updated the PR.
I decided return an error on :scheme / authority paths (I am a bit confused by the erlang naming, since for path like example.com:8080, example.com would be the scheme and 80 the path).
As it seems to be only used by CONNECT requests and we don't support tunneling, I think we can ignore it.

Pushed up a couple of small cleanup changes:

renamed 'path' to 'request_target' for cleaner semantics
tidied up a couple of (unrelated) function calls to keep formatted code sane
tidied up :* use in tests to avoid having to special case it

LMK if the changes look good to you then I think we can merge!

Looks good! 👍


#3070 - add support for exporting to sdf file format

How the feature works? / How did you fix the issue?
closes #3070
Check list

[ ] unit-tests written
[x] e2e-tests written
[x] documentation updated
[x] PR name follows the pattern #1234 – issue name
[x] branch name doesn't contain '#'
[x] PR is linked with the issue
[x] base branch (master or release/xx) is correct
[x] task status changed to "Code review"

Failing test passes locally:


ALVR hangs for 6 seconds every 29 seconds when streaming

Apple Vision Pro
Windows 11
NVIDIA GeForce RTX 4090
ALVR VisionOS (this repo) commit 9d99df0c0848b816bc43dd5ebc49151367389935
ALVR v21.0.0-dev00+nightly.2024.02.25

When actively in SteamVR, every 29 seconds the view in the headset freezes (but stays in view just moves with head movement), ALVR UI freezes on PC, and sound changes back to the PC, it stays glitched for exactly 6 seconds, then everything returns to normal.  29 seconds later, same happens.  These timings are very consistent - I ran a stopwatch on it for several cycles. Of course my reaction time could be off.  Perhaps 30 and 5 or such, but its for sure a 35 second cycle.
I have attempted several changes to settings.  Quality, bitrate, and encoder does not seem to affect this behavior.
I'm thinking the headset is psuedo disconnecting and reconnecting or something of the sort.  The exact timing tells me its not an encoding or network issue, but something in AVP, alvr-visionos, or ALVR having a blip.
Perhaps this is a general ALVR issue and not AVP specific and belongs in the main repo - I'm not sure.
This is a screenshot of the stats chart after a 6 second freeze:

It could be that the AWDL bug changed how it manifests I guess, does it change if you change your 5GHz WiFi to channel 149?

It could be that the AWDL bug changed how it manifests I guess, does it change if you change your 5GHz WiFi to channel 149?

You pointed out the root cause. I was on a 2.4ghz network. Switched to the 5ghz, all is good now!  Flight simulator in 4K VR. Love it.
Very strange behavior though. If anyone understands and cares to explain I’d love to hear. I’m a 35 years exp software engineer so you can use big words. ;)
Finally - can I tip the authors somewhere?

The 2.4GHz stutter could just be the periodic IDR NALs (fullly encoded frames and not differential ones) the encoder sends out, it's supposed to send them every 100ms but I think like most H264+ encoders, every setting is a suggestion apparently lol. And I've found even on 5GHz, network bandwidth-related lag tends to cause weird feedback issues with the timing/Mbps prediction.
For 5GHz the devil is AWDL, which is some fancy Apple feature they use to do Airplay/Air-whatever file sending. They do it using broadcast packets on channel 149, which means if your AP is on anything except 149, you get these random stutters once a second, for several frames, and sometimes it's there and aometimes it's not.


Need to expire traces based on in-memory storage component in zipkin

When I use the open source version of Zipkin I am able to set the max number of spans and expire them accordingly as below.
I am using the latest version of Zipkin for  which this in-memory storage component was added from Zipkin 1.28.
java -Dzipkin.storage.mem.max-spans=5 -jar  zipkin-server-2.0.1-exec.jar
But, when I add the below dependencies and create/build a Spring Boot based zipkin service as below.
<dependencies>
	<dependency>
			<groupId>io.zipkin.java</groupId>
			<artifactId>zipkin-server</artifactId>
		</dependency>
		<dependency>
			<groupId>io.zipkin.java</groupId>
			<artifactId>zipkin-autoconfigure-ui</artifactId>
			<scope>runtime</scope>
		</dependency>
</dependencies>

<dependencyManagement>
		<dependencies>
			<dependency>
				<groupId>org.springframework.cloud</groupId>
				<artifactId>spring-cloud-dependencies</artifactId>
				<version>Dalston.SR1</version>
				<type>pom</type>
				<scope>import</scope>
			</dependency>
		</dependencies>
	</dependencyManagement>

I do not see the spans expiring accordingly.
I have added the property -Dzipkin.storage.mem.max-spans=5 while starting the service.
I even tried adding zipkin.storage.mem.max-spans=5 application configuration application.yml.
What version of Zipkin are the maven dependencies are based.
Should I need to do add anything other than those.

I think you should file this issue in the https://github.com/openzipkin/zipkin project.

I do not understand. The open source version of Zipkin works fine. I only want to know why it does not work with spring cloud.  If I use spring cloud sleuth and zipkin dependencies and create my own Zipkin service it does not work. So, how would the issue be with openzipkin?

I would do mvn dependency:tree and make sure you are running the same
zipkin.jar version as you think you are! Declare explicit dependency if
needed.

Did you find any solution to this issue? If yes could you please post the solution/

With Spring boot Dalston.SR3 (which uses open zipkin 1.28) you can achieve this by setting property zipkin.storage.mem.max-spans=xxxx This will limit the number of spans and discard old ones.


Use block scoping for source programs

Features

Bumped js-slang version

Pull Request Test Coverage Report for Build 770

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

Totals

Change from base Build 753:
0.0%

Covered Lines:
887

Relevant Lines:
2893

💛  - Coveralls


Add dnsPolicy option

This commit adds the possibility of specifying
the dnsPolicy.

Could you also add the "dnsConfig" property? This is useful for those, who set "dnsPolicy: none"
(https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-dns-config)

I just commited the first bunch of Helm unittests.
Could you also add some unittests for your change?

Thanks a lot, and one remark: If you want to see your commit messages in the CHANGELOG.md, please use Conventional Commits (https://www.conventionalcommits.org/en/v1.0.0/)

@pmoscode Sorry for the delay, I was busy with other things. It was actually the first time for me to write helm unit tests. I hope you're satisfied with the tests I have added, otherwise, let me know your improvement proposals.

And, if you add this test case:
 - it: should render dnsConfig only once
    template: templates/deployment.yaml
    set:
      dnsPolicy: "None"
      dnsConfig.nameservers[0]: "<IP_ADDRESS>"
    asserts:
      - lengthEqual:
          path: spec.template.spec.dnsConfig
          count: 1

it will fail, because it will try to render dnsConfig twice, which is even not possible in yaml.

So, the conditions in the deployment.yaml are incomplete.
Beside that, the tests look great. :)

@darox At line 39 in the test you say "it: should render dnsConfig if dnsPolicy key is set to None and dnsConfig is set".
But "dnsPolicy" is not set to "none" in the "set" property of the test, am I right? Only "nameservers" and "searches" are set.
This is what I tried to demonstrate here: https://github.com/pmoscode-helm/jdownloader2/pull/2#issuecomment-1568100645


Fix excludeDependencies handling

@fommil That should fix the problem with the excludeDependencies you were seeing in ensime-sbt when bumping sbt-sensible.

Awesome!


Suggest accounts instead of selecting

Maybe use a machine learning algorithm and

train the model with existing transactions and postings
use a input

transaction year, month, day
transaction title
posting absolute value
posting value sign
posting comment
posting position ?

get as output : the account name

CNN, RRN, Naive Bayes classifier ?


Potential memory leak of DiagnosticListener

Creating a separate issue per suggestion from #1678
Describe your environment. Describe any aspect of your environment relevant to the problem:

SDK version: 2.14.0
.NET runtime version (.NET or .NET Core, TargetFramework in the .csproj file): netcoreapp3.1
Hosting Info (IIS/Azure WebApps/etc): Azure AppService
Platform and OS version: Windows

What is the expected behavior?
GC able to reclaim memory
What is the actual behavior?
Number of DiagnosticSubscriptions grows in time without decreases.
Additional context.
After updating to 2.14 from 2.13.1 situation became better, but still DiagnosticSubscriptions count grows constantly. Included output from dotnet-gcdump is for approximately 12 hour period.
dumps.zip

@forik I reviewed the trace and could see a possible leak. Could you please help with the following data.

Execute below query at following time interval

First-time: process start time and the time when 1.gcdump was collected
Second-time: between the time 1.gcdump and 2.gcdump

dependencies
| summarize count() by type

Based on my initial research, Azure based back-end call may be contributing to this issue and wanted to understand from the data.
It would also help if you have a repro for this issue so that I could recreate an issue and collect data.

Below are data not from the exact timings.
This one after one hour work after deploy:

This one after two hours after previous query:

Regarding to repro, it is not an easy task though, but I'll try to do my best.

@forik I created a sample project to send/retrieve data from service bus. But I could not recreate this issue. In my scenario IndividualDiagnosticSourceListener object count always stays at 1.
Below snapshot is the growth of objects for your app from the GC dump.

@rajkumar-rangaraj could you please share the project so I could add the patterns we use with service bus? Probably we are doing something wrong

Please sync and make sure both are testing the same version of ServiceBus SDK, and DIagnosticSource nuget version as well.
@forik can you temporarily disable every dependency except service bus, and see if the issue occurs. this helps us atleast narrow down to service bus dependency collection.

@cijothomas @rajkumar-rangaraj I'm using Microsoft.Azure.ServiceBus 4.1.3 and I don't explicit dependency on System.Diagnostics.DiagnosticSource, so I guess it comes as a transitive dependency

Any update on this issue ? We encounter the same issue in .Net Core 3.1(.8) ..

We encounter the same issue.
PerfView shows the following from a memory dump:

@peterbomers Hi Peter,
We just found out the issue. We had an issue about our instances number of "BlobContainerClient".
We instanciated it every time we had to get or delete a blob..
Maybe you just need to check your code for some similar issue.
PS : BlobContainerClient is not marked as IDisposable or something, so we just created one each time we needed it ... Now I just saved it in a singleton for all my use cases.
Hope it can help you ..

@peterbomers Hi Peter,
We just found out the issue. We had an issue about our instances number of "BlobContainerClient".
We instanciated it every time we had to get or delete a blob..
Maybe you just need to check your code for some similar issue.
PS : BlobContainerClient is not marked as IDisposable or something, so we just created one each time we needed it ... Now I just saved it in a singleton for all my use cases.
Hope it can help you ..

@Rayzbam thank you for the information.
We're not using a BlobContainerClient but maybe a different Azure client. I will check it!

@Rayzbam
Your suggestion did point us in the right way.
It's not only the BlobContainerClient leaking the memory, also other Azure service suffer from this problem.
Our health endpoint constructed a CertificateClient and a SecretClient to verify the connection to KeyVault.
Each request created 2 new instances and both kept a reference to the AzureSdkDiagnosticListenerSubscriber in memory. (see the picture)
We also fixed it with a singleton instance but now I'm a little bit concerned about all other Azure services.
We use a lot transient Azure services :(

@peterbomers I'm glad it helped you !
I checked the source code of Azure and you can find many DiagnosticListener instanciated in some internal stuff.
It seems pretty hard to find out which Azure service keeps a reference on one or many instances of this..
I can only advice you to do some load tests on your app(s) and analyze the result dump in a first place..
I think BlobContainerCient or CertificateClient want to be used as Singleton, but can't find any documentation about it.. I think we just have to discover it by ourself..
This issue happened on a "small" app and it was pretty quick to replace all transient actually, i guess it's not the case of everyone in this situation.
TL;DR : Before using an Azure service, just be sure you know how to use it..

any updates? have the same with DataLake

any updates? have the same with DataLake

This is indeed a bug, we do recommend keeping clients as singletons (https://devblogs.microsoft.com/azure-sdk/lifetime-management-and-thread-safety-guarantees-of-azure-sdk-net-clients/) but for some instances, it's impractical (e.g. BlobClient). https://github.com/Azure/azure-sdk-for-net/issues/18199 is tracking the work to fix the bug.
Because this component is shared between Azure SDKs as a source every individual SDK would need to update to get a fix. I suspect for most of them it would happen at the beginning of February.

This is indeed a bug, we do recommend keeping clients as singletons (https://devblogs.microsoft.com/azure-sdk/lifetime-management-and-thread-safety-guarantees-of-azure-sdk-net-clients/) but for some instances, it's impractical (e.g. BlobClient). https://github.com/Azure/azure-sdk-for-net/issues/18199 is tracking the work to fix the bug.
Because this component is shared between Azure SDKs as a source every individual SDK would need to update to get a fix. I suspect for most of them it would happen at the beginning of February.


Suggestion: Add ability to Find/Replace in selection

VSCode Version: Code - Insiders 1.3.0-insider (a1293f5056e79c3f0e2cd3e24909f41ff4eef472, 2016-07-05T13:09:46.271Z)
OS Version: Windows_NT ia32 10.0.10586

Steps to Reproduce:

Select some text
Use Ctrl+F or Ctrl+H
Observe that there is no way to find matches and replace all occurrences within the selection.

Side note: would also be nice if there was some way to indicate to "Change All Occurrences (Ctrl+F2)" a range in which to create the cursors.

We actually already support this - try out the 'Find in selection' button in the find widget

Ah thanks. I didn't even notice that button. Maybe it would make sense to make that selected by default when a text selection is made at the time the find widget is opened?

I believe that might have been the previous behavior but we have reverted that due to some reason - I can not remember why.

Is there a way to do this without using the mouse?

@tbfleming yes my pressing ctrl + f and the tab key and lot of times and then a space. I know this is not the best so please file a feature request to create a global workbench command to enable find in selection


prometheus-dmarc-exporter: don't use poetry2nix

Motivation for this change
~https://github.com/NixOS/nixpkgs/pull/174629#issuecomment-1138426280 and it currently downloads some wheels from PyPI~

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

The evaluation error in https://github.com/NixOS/nixpkgs/pull/174629#issuecomment-1138426280 was caused by a legitimate incompatibility where upstream had marked the package as incompatible with 3.10+.
Additionally there are no wheels downloaded from PyPi for this package.

Additionally there are no wheels downloaded from PyPi for this package.

So how are https://pypi.org/project/dataclasses-serialization/ and https://pypi.org/project/more-properties/ installed?

Additionally there are no wheels downloaded from PyPi for this package.

So how are https://pypi.org/project/dataclasses-serialization/ and https://pypi.org/project/more-properties/ installed?

Oh I see they are overriden manually.

I think it should at least be up to the maintainer @Ma27 to decide whether to use poetry2nix.
However I'd argue that we should strive to avoid poetry2nix in Nixpkgs because it

creates more load for Hydra and uses more disk space
delays security updates
negates the intermediate step of distro maintainers vetting software

creates more load for Hydra and uses more disk space

Marginally so, but sure.
I do wonder how much extra Hydra load and disk space the regular python nixpkgs development workflow adds though. I'd wager a whole lot more.

delays security updates

How does this delay security updates exactly?

negates the intermediate step of distro maintainers vetting software

I would argue that this is already not happening and therefore a moot argument.
But I think the biggest argument in favour of keeping such approaches around is developer time and correctness.
With these types of overrides https://github.com/NixOS/nixpkgs/pull/174804/files#diff-33ee5643df27fb56c964dcde0e3b5a50ce360c14eaae09efa1c9f62e9247a7fcR24-R28 you're sacrificing correctness in a very hacky and questionable manner.

I do wonder how much extra Hydra load and disk space the regular python nixpkgs development workflow adds though. I'd wager a whole lot more.

A lot. But we get a properly tested package set.

How does this delay security updates exactly?

Say a security update of dataclasses-serialization is released. The maintainer of dmarc-metrics-exporter takes a few days to update the version of dataclasses-serialization in poetry.lock (if they even hear about the security update). The Nixpkgs maintainer takes a few days to update dmarc-metrics-exporter.
It gets even worse with more indirection and packages needlessly pinning their dependencies' versions.
I think it's much better to ignore pins and properly test instead so that updates reach all reverse dependencies as soon as the Nixpkgs maintainer or @r-ryantm notices.

I would argue that this is already not happening and therefore a moot argument.

I agree.

But I think the biggest argument in favour of keeping such approaches around is developer time and correctness. With these types of overrides https://github.com/NixOS/nixpkgs/pull/174804/files#diff-33ee5643df27fb56c964dcde0e3b5a50ce360c14eaae09efa1c9f62e9247a7fcR24-R28 you're sacrificing correctness in a very hacky and questionable manner.

That particular override is "endorsed" by upstream: https://github.com/jgosmann/bite-parser/blob/main/pyproject.toml#L12
But in general I think that for the reasons above ignoring pins and running as many tests as possible is the better choice. Why else would you use a distro and not just pip install directly?

How does this delay security updates exactly?

Lets be realistic here: If upstream is not releasing as often as hypothesis is then a python lock file gets updated eventually and is released with the next update and that could be quite a while or in some cases never.
Also we do not want to land in the pitty Go and Rust are already in where you need to check every single package for security related updates which looks like https://github.com/NixOS/nixpkgs/issues/141368

With these types of overrides #174804 (files) you're sacrificing correctness in a very hacky and questionable manner.

Widening version constraints is something that is constantly done and required in pythonPackages. Otherwise we couldn't deliver some software at all due to the state of the python ecosystem. Generally all core python maintainers treat version constraints a bit lightly. If there are tests for the package more often than not a version constraint is removed.
Also that particular version constraint should be a noop and could probably be dropped.

Why else would you use a distro and not just pip install directly?

Because pip is not very correct at all. It happily changes install order of packages which also can effect version constraints and up until recently pip sometimes choose the wrong wheels on alpine. It also can't track which packages you installed and which ones are dependencies, ignores version constraints on future operations and if you supply it with an impossible version constraint scenario you can end up downloading and trying to build every version of every dependency in your entire dependency chain.

Why else would you use a distro and not just pip install directly?

Because pip is not very correct at all.

I should have said poetry install, not pip install.

Back when I packaged it, I considered packaging each dependency to be too much of a pain, so I went down the poetry2nix route (which seemed like an OK choice given that it was already used in nixpkgs).
Given that the Python maintainers seem to prefer to use python packages and all dependencies are packaged now, it seems OK to me.
Also, LGTM implementation-wise.

The evaluation error in #174629 (comment) was caused by a legitimate incompatibility where upstream had marked the package as incompatible with 3.10+.

It's not uncommon for poetry2nix to break eval: https://github.com/NixOS/nixpkgs/pull/139480#issuecomment-1108053393
I think that's a design flaw.

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

1 package blacklisted:

nixos-install-tools

11 packages built:

dmarc-metrics-exporter
python310Packages.bite-parser
python310Packages.dataclasses-serialization
python310Packages.docformatter
python310Packages.more-properties
python310Packages.xsdata
python39Packages.bite-parser
python39Packages.dataclasses-serialization
python39Packages.docformatter
python39Packages.more-properties
python39Packages.xsdata


Jenkinsfile: Switch GIT_URL to linux-stable

Signed-off-by: Gianpaolo Macario<EMAIL_ADDRESS>

LGTM, merging


Keep sending heartbeat while processing a message

Is your feature request related to a problem? Please describe.
We encountered the same problem as https://github.com/tulios/kafkajs/issues/130
Kafka kept removing our consumer and re-sending the messages, on consumer side we had the logs : "Response Heartbeat(key: 12, version: 1) The coordinator is not aware of this member". On kafka side we had the logs "Member [...] in group [...] has failed, removing it from the group (kafka.coordinator.group.GroupCoordinator)"
It turned out that one of our message handlers was doing a http request to a domain that did not respond, so it was waiting for the timeout and during this time, kafkajs stopped sending heartbeats, causing kafka to remove the consumer.
When the consumer reconnected, kafka re-sent the same message that took too much time so we were stuck.
Describe the solution you'd like
When a message takes time to be processed, kafkajs should keep sending heartbeats: the process is still alive and working.

This is why we provide the heartbeat function to eachMessage/eachBatch. We can't know from "the outside" if your consumer is still working or if it should be considered unhealthy, so if we just regularly keep heartbeating even if the promise returned from your eachMessage/eachBatch never resolves, we will have invalidated the purpose of the heartbeat mechanism, because it's no longer detecting if the consumer is healthy or not.
If your case, I would suggest configuring the sessionTimeout  so that it is longer than your maximum allowed message processing time, or that you devise some mechanism by which you heartbeat from within your eachMessage/eachBatch as long as you still consider the consumer to be healthy.

That is a very good point @Nevon. Thanks for the reply. I guess the heartbeat on error would need to be on a case by case basis but a generic one on any error I agree might not be the best idea.

Had this problem as well recently.
Personally I disagree with @Nevon and think that this is a missed opportunity to use setInterval() and clearInterval() to ensure that a long-running consumer does not get booted out of the consumer group regularly.
The implementation for us is as follows but I really think this should be part of the core library:
    // 3) Handle messages
    await consumer.run({
      eachMessage: async ({ topic, partition, message, heartbeat }) => {
        const intervalId = setInterval(heartbeat, config.heartbeatInterval || 3000); // keep a steady heartbeat
        const timeoutId = setTimeout(() => clearInterval(intervalId), config.sessionTimeout || 60000); // stop if it takes too long
        try {
          async doTheThing();
        } catch (err) {
          logger.error('[KAFKA] (eachMessage) Error processing message:', { topic, partition, offset, err});
        } finally {
          // remove all timers
          clearTimeout(timeoutId);
          clearInterval(intervalId);
        }
      },
    });

@sdesalas I think you meant
          const intervalId = setInterval(() => {
            heartbeat().catch(err => {})
          },config.heartbeatInterval || 3000);

because for this code:
const intervalId = setInterval(heartbeat.catch(err => {}), config.heartbeatInterval || 3000);
I kept getting: heartbeat.catch is not a function  and then heartbeat is a function


deploy

Hi @cretueusebiu !
I appreciate your work, but I´m a question about deploy. Have I publish in web server everything in laravel-vue-spa folder ?

Yes, just deploy it as any other Laravel project. Just make sure to run npm run prod and set the env to production.

To clarify, for best practice, do you 'npm run prod' then upload or upload then 'npm run prod' on the production server? It seems like the latter, with the @if (app()->isLocal()) loading only app.js and loading manifest, vendor and app in production..

Normally what I do is I always push to my production server the production version.

On the server it's only git pull and that's it.

That's what I was doing on other projects but with this package I believe the best practice must be to npm run dev on the local and npm run prod on the production server - I think this because the index.blade.php has app()->isLocal() mix app.js, else mix manifest, vendor, app and the gitignore excludes /public/js and /public/css, so clearly these are intended to compiled on the production server. If you want to compile on your dev then git the files to production, you'd have to make some adjustments to the gitignore.

I did it that way in the past and I try to do it even now, so that I can avoid any javascript issues on the server.
Then using multiple branches, and the master was always production ready, and have other branches for testing, staging, development, all this stuff.
If you don't have issues it's perfectly fine even that way, I don't see an issue if finally webpack and all the javascript dependency hell is more stable so you can compile them with no issues everytime.
My issue was that if something went wrong during compiling on the production server, the entire production app was down since it was a JS app. Big risk. If I checkout from git everything ready to go, I don't have that risk at all.


BrowserMob Proxy extremely slow when recording HAR file

Whenever i enabled HAR File Recording all pages requested through the proxy started to load very slow. I traced the problem back to the BrowserMobHttpClient (line 411).
UserAgentInfo uai = p.parse(userAgent);
This took about 5 seconds for each request, and then throwing an IOException.
I don't know if this is relevant but I have to use an upstream proxy to access the internet. The problem happened with all pages I tried (e.g. google.com, facebook.com, ...) both if i use the proxy via the REST API or start it from Java directly (in a selenium test). As I didn't need the browser I just removed the parsing of the UA string and it works fine and speedy again.

Is there a workaround for Mac?


When using the withModuleFederationPlugin and registering shared mappings, the path alias configuration in tsconfig.json

When using the withModuleFederationPlugin and registering shared mappings, the path alias configuration in tsconfig.json as "@/": ["src/"] is not working. However, specifying the full path like "@/utils": ["src/utils/utils.ts"] does work. I'm currently using version 15.0.3.
Why is the wildcard "*" alias not effective in shared mappings with withModuleFederationPlugin? Could it be a version issue or is it intended to work this way?
Thank you in advance for your help.

I had the same issue when evaluating v16. I have not tested since then. Hopefully this will be addressed in the future. We have not migrated to native-federation yet, but if/when we do, I would prefer not to have to start the project with changing several thousand imports.


Run integration tests with ASan

We should tweak our Makefile to run our unittests with ASan at some point, to detect various C memory issues that can happen.

This is addressed by #196 indeed. I also wonder if we it's possible to run the test vectors + bindings with ASan. Would be really useful (along with getting some coverage info from the bindings).


Rotation with rotated crop rect not working.

I want to set rotation of the image and also the crop rect. with fixed X&Y ratio. but whenever I try setting the rect it doesn't  show properly.
cropView.setImageBitmap(bitmap);
cropView.setCropRect(initCropRect);
cropView.setAspectRatio(xRatio,yRatio);
cropView.setRotatedDegrees(rotationAngle);
If I remove the aspectRatio constrain then it show the rect. but only on first load.

its similar to #570


fix(web): Add padding for the  to let date tabs cov…

Fixes #213
What this PR solves / how to test:

Livestream card's border would exceed date tabs since they are sharing the same container without padding
Add padding for livestream cards to solve this issue
Test:

Different width devices to check border does not exceed while scrolling
Check both left and right side of date tabs

However, dealing with negative values like margin: 0 -2px might be a bit tricky, don't you think?

Yeah, initially I was considering to apply css code on TabBox but I was worried whether the negative margin was good practice or not. However, since you mentioned, I have done some research and it looks like negative margin is not bad practice.
Therefore, I will change the margin setting due to the TabBox might be proper place that we want to solve this issue and do not modify other component.
Thanks for the advice!
Update on commit 66e50905e133790823f6ade19f282a6443a0b4ba. Please have a look!


Themes

This commit implements themes, discussed in issue #56.
It brings the parser created aside in the repository
HipyCas/theme-parser and
adapts it to the project.
Themes are passed using the --theme flag followed by the name or path.
For more information, read the README.md of the themes
module
or for theme file syntax the formal
specification.
Features
With this addition, three new features where added.
The feature that enables themes is themes, that at the same time depend on other features.
The pairs that get parsed in the theme file depend at the same time on which other
features are enabled (color and icons).
Other two features added which are only for internal use, in which themes depends, are home (adds
function to get home directory) and index_flags (enables indexing of
lsfp::core::args::Flags).
Named themes
lsfp can load a theme by its name or by path. To load a specific path
make sure that it exists and includes either a dot or a forward or
backward slash.
When loading a theme by name, lsfp looks for a file named like the
passed name under ~/.lsfp-themes.

For more info about the specific file syntax and implementation look at SPEC.md and README.md, respectively.


Log when granting permission to the datasource and dataconnection

Description

Logging support for granting Datasource and Data connection permissions.
Related Issue :

#1603
How Has This Been Tested?

1-1. Go to 'Management' > 'Data Storage' > 'Datasource' Menu
1-2. Select any datasource and go to detail view
1-3. Click 'edit' button in the 'Publish' tab
1-4. Grant or revoke to any workspace
Finally, Check server logging
[Activity] Block(or Accept) workspace (workspace id) from datasource (datasource id)
And you can check from activity_stream table in the database
SELECT * FROM activity_stream;
related columns are as follow,

activity_action : type of action
: ACCEPT (granted permission) or BLOCK (revoke premission)

activity_actor : who acted this action

activity_object_id : source's id (datasource or data connection)

activity_object_type : sources' type
: DATASOURCE or DATACONNECTION

activity_target_id : target's id (now only support workspace)

activity_target_type : target's type
: WORKSPACE

Go to 'Management' > 'Data Storage' > 'Data connection' Menu
and repeat the above for data connections.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Additional Context

run build
deploy to 2

run build
deploy to 2

run build
deploy to 2

run build
deploy to 2


feat: notification policy for stack failure origins

Description of the change

Adds a new notification policy to track + notify the origins of a Spacelift Stack failure, aka the author. If someone's PR merge introduced the failure of a stack, it will write a comment on that PR and notify them on Slack.
This is useful when you have a couple of people working on a project with a lot of stacks, so there's lots of activity and there's fails here and there. This makes it easier to trace and keep all stacks green.
Add corresponding tests.
This is what it looks like:

Checklist
Please make sure that the proposed change checks all the boxes below before requesting a review:

[x] Each new policy has corresponding tests.
[x] All the tests pass.
[x] The pull request is opened against the main branch.
[x] The pull request is no longer marked as a draft.
[x] You agree to license your contribution under the MIT license to Spacelift (not required for Spacelift employees).

If the proposed change is ready to be merged, please request a review from @spacelift-io/solutions-engineering. Someone will review and merge the pull request.
Spacelift employees should request reviews from the relevant engineers and are allowed to merge pull requests after they got at least one approval.
Thank you for your contribution! 🙇

@spacelift-io/solutions-engineering appreciate the review on this!


Allow puppetlabs/inifile 3.x

puppetlabs/inifile 3.0.0 was recently released.  It was a major version bump as they dropped support for puppet 4.

@raphink Would you be ok with me creating a release PR for 2.4.0?

Sure

Sure

Great! https://github.com/camptocamp/puppet-systemd/pull/102


Updating TableDiskUsage utility to extend KeywordExecutable (#2807)

This will allow this utility to be executed from the accumulo command

After looking at this change, I think this makes more sense for this Utility to not be a keyword executable. It is currently called from the Shell as part of the du command. This makes more sense to me as it can be run from a table context and requires a table as an argument.

Ah ok, I tried to search and find commands that were not already exposed but must have missed this one. I can go ahead and just close this one out. That's why I created these all as separate PRs.

Created https://github.com/apache/accumulo/issues/2820 for possible follow on to capture my comments after the issue closed.


Us03 manter switches

Multiple merge commits were due to a merging issue, should be fixed now.

Coverage increased (+1.4%) to 15.261% when pulling 21bfa885cb307498fa1630a6a1a80920c27c91be on US03-Manter_Switches into 9a76dbae8870ea6e0efc876e53d96e1fe38a2a85 on master.


fix export toConstDateTime().

Sorry, I forgot to export the file. 😅

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

Project coverage is 93.02%. Comparing base (b351d58) to head (c43367f).
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #15      +/-   ##
==========================================
+ Coverage   90.00%   93.02%   +3.02%
==========================================
  Files           1        2       +1
  Lines          80       86       +6
==========================================
+ Hits           72       80       +8
+ Misses          8        6       -2

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

Published!


Appstudio update test-component-pac-rfab

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-rfab-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
33 seconds
build-container

✅ Succeeded
18 seconds
inspect-image

✅ Succeeded
18 seconds
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
21 seconds
sbom-json-check

✅ Succeeded
9 seconds
optional-label-check

✅ Succeeded
9 seconds
label-check

✅ Succeeded
20 seconds
show-summary

✅ Succeeded
11 seconds
show-sbom

Pipelines as Code CI/test-component-pac-rfab-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
33 seconds
build-container

✅ Succeeded
18 seconds
deprecated-base-image-check

✅ Succeeded
18 seconds
inspect-image

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
21 seconds
sbom-json-check

✅ Succeeded
9 seconds
label-check

✅ Succeeded
9 seconds
optional-label-check

✅ Succeeded
11 seconds
show-sbom

✅ Succeeded
20 seconds
show-summary

Pipelines as Code CI/test-component-pac-rfab-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
18 seconds
init

✅ Succeeded
20 seconds
clone-repository

✅ Succeeded
33 seconds
build-container

✅ Succeeded
17 seconds
inspect-image

✅ Succeeded
16 seconds
deprecated-base-image-check

✅ Succeeded
9 seconds
clair-scan

✅ Succeeded
33 seconds
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
19 seconds
label-check

✅ Succeeded
18 seconds
optional-label-check

✅ Succeeded
7 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-rfab-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
18 seconds
init

✅ Succeeded
20 seconds
clone-repository

✅ Succeeded
33 seconds
build-container

✅ Succeeded
17 seconds
inspect-image

✅ Succeeded
16 seconds
deprecated-base-image-check

✅ Succeeded
9 seconds
clair-scan

✅ Succeeded
33 seconds
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
19 seconds
label-check

✅ Succeeded
18 seconds
optional-label-check

✅ Succeeded
7 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary


Line: change event tests to inRange tests

This PR remove events test cases with inRange method tests.

Coverage decreased (-1.08%) to 95.274%

Looks ok, but I don't really like that we have to be one pixel inside the element before the tests work. Also should test different borderWidths of the line (1 for the other edge case, or should it actually be 0.1?). Also without label.

Without 1 inRange return false. I need to go in deep and debug it. I have the feeling it's related to intersect function and the epsilon. Let me debug it and I'll come back with the result.

Coverage decreased (-1.08%) to 95.274%

It's correct because the events part has been removed but it's present in the other PR.

Looks ok, but I don't really like that we have to be one pixel inside the element before the tests work. Also should test different borderWidths of the line (1 for the other edge case, or should it actually be 0.1?). Also without label.

Without 1 inRange return false. I need to go in deep and debug it. I have the feeling it's related to intersect function and the epsilon. Let me debug it and I'll come back with the result.

I think it would be fine if the test passes with borderWidth: 1. If it does not, then I think its worth taking a closer look.

Looks ok, but I don't really like that we have to be one pixel inside the element before the tests work. Also should test different borderWidths of the line (1 for the other edge case, or should it actually be 0.1?). Also without label.

Without 1 inRange return false. I need to go in deep and debug it. I have the feeling it's related to intersect function and the epsilon. Let me debug it and I'll come back with the result.

I think it would be fine if the test passes with borderWidth: 1. If it does not, then I think its worth taking a closer look.

I found the bug in intersect... Let me test again (with borderWidth: 1 and others)

Ok the bug was here:
https://github.com/chartjs/chartjs-plugin-annotation/blob/c04e02ef2ff171cd878a308a34154c19632c00af/src/types/line.js#L66
It must be:
return (sqr(x - xx) + sqr(y - yy)) <= epsilon;

I'm committing the changes and then I'll rebase it.

I think after this we are good to go with 1.3.0?
So the version bump would be next. The we could give it a week or 2 before starting to merge v2 things.
The week or 2 so there is room to fix any new bugs found in 1.3 without creating any additional branches and stuff.

I think after this we are good to go with 1.3.0?
So the version bump would be next. The we could give it a week or 2 before starting to merge v2 things. The week or 2 so there is room to fix any new bugs found in 1.3 without creating any additional branches and stuff.

Completely agree with you!


setNetworkTimeout checks for SQLPermission before proceeding

as be mentioned by @mrotteveel as well on this page, setNetworkTimeout method needs to check for permission.

Codecov Report

Merging #255 into dev will decrease coverage by 0.03%.
The diff coverage is 11.11%.

@@             Coverage Diff              @@
##                dev     #255      +/-   ##
============================================
- Coverage     33.77%   33.74%   -0.04%
- Complexity     1522     1523       +1
============================================
  Files           101      101
  Lines         23600    23609       +9
  Branches       3876     3877       +1
============================================
- Hits           7972     7967       -5
- Misses        14061    14073      +12
- Partials       1567     1569       +2

Flag
Coverage Δ
Complexity Δ

#JDBC41
33.56% <11.11%> (-0.09%)
1507 <0> (-4)

#JDBC42
33.7% <11.11%> (+0.1%)
1522 <0> (+3)
:arrow_up:

Impacted Files
Coverage Δ
Complexity Δ

.../microsoft/sqlserver/jdbc/SQLServerConnection.java
41.16% <11.11%> (-0.12%)
228 <0> (ø)

src/main/java/microsoft/sql/DateTimeOffset.java
37.14% <0%> (-2.86%)
8% <0%> (-2%)

...om/microsoft/sqlserver/jdbc/ReaderInputStream.java
44.94% <0%> (-1.13%)
16% <0%> (-1%)

...n/java/com/microsoft/sqlserver/jdbc/Parameter.java
30.47% <0%> (-0.86%)
37% <0%> (ø)

...rc/main/java/com/microsoft/sqlserver/jdbc/DDC.java
27.45% <0%> (-0.67%)
49% <0%> (ø)

...oft/sqlserver/jdbc/SQLServerPreparedStatement.java
29.92% <0%> (-0.27%)
85% <0%> (ø)

...om/microsoft/sqlserver/jdbc/SQLServerBulkCopy.java
44.84% <0%> (-0.15%)
182% <0%> (-1%)

...in/java/com/microsoft/sqlserver/jdbc/IOBuffer.java
37.84% <0%> (-0.11%)
0% <0%> (ø)

...m/microsoft/sqlserver/jdbc/SQLServerResultSet.java
25.59% <0%> (+0.5%)
183% <0%> (+5%)
:arrow_up:

Continue to review full report at Codecov.

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

Looks good to me.


ringo/term inserting " " (whitespace) after control sequence

Current behaviour of term.write is that it inserts " " (whitespace) after each
argument which is just an ANSI control sequence. e.g.:
>> term.writeln("Hello", term.RED, "World");
Hello World

I can see why this is convenient for simple output but it's very annoying when
outputting cursor movement sequences since those get offset by x+1.
Should we change this and break a lot of existing code? Or should we leave
it and just say that anything more then colors is out of scope for ringo/term?
I was able to work around ringo/term behaviour by wrapping term.write and concatenating all arguments into one string:
>> term.writeln("Hello" + term.RED + "World");
HelloWorld

term.write follows the console convention. So I would not change this and use the workaround proposed by @oberhamsi
Philipps-MacBook-Pro:~ philipp$ node
> console.log("foo", "bar");
foo bar


Add files via upload

@tomvanderauwermeulen Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


osrm-backend: 5.21.0 -> 5.22.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/osrm-backend/versions.
meta.description for osrm-backend is: '"Open Source Routing Machine computes shortest paths in a graph. It was designed to run well with map data from the Openstreetmap Project"'.
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
Warning: no invocation of /nix/store/r1941bqkvsld0r973hgl9s9w3s46nc76-osrm-backend-5.22.0/bin/osrm-components had a zero exit code or showed the expected version
/nix/store/r1941bqkvsld0r973hgl9s9w3s46nc76-osrm-backend-5.22.0/bin/osrm-extract passed the binary check.
/nix/store/r1941bqkvsld0r973hgl9s9w3s46nc76-osrm-backend-5.22.0/bin/osrm-partition passed the binary check.
/nix/store/r1941bqkvsld0r973hgl9s9w3s46nc76-osrm-backend-5.22.0/bin/osrm-customize passed the binary check.
/nix/store/r1941bqkvsld0r973hgl9s9w3s46nc76-osrm-backend-5.22.0/bin/osrm-contract passed the binary check.
/nix/store/r1941bqkvsld0r973hgl9s9w3s46nc76-osrm-backend-5.22.0/bin/osrm-datastore passed the binary check.
/nix/store/r1941bqkvsld0r973hgl9s9w3s46nc76-osrm-backend-5.22.0/bin/osrm-routed passed the binary check.
6 of 7 passed binary check by having a zero exit code.
6 of 7 passed binary check by having the new version present in output.
found 5.22.0 with grep in /nix/store/r1941bqkvsld0r973hgl9s9w3s46nc76-osrm-backend-5.22.0
directory tree listing: https://gist.github.com/9fc0090a591bdd5db8366d0b3753c459
du listing: https://gist.github.com/c747b5422c7f571aefe22bd85a71bd76

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
osrm-backend

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r1941bqkvsld0r973hgl9s9w3s46nc76-osrm-backend-5.22.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A osrm-backend https://github.com/r-ryantm/nixpkgs/archive/9f056c9a7d19b3524430a150b218ba1fe895afc5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r1941bqkvsld0r973hgl9s9w3s46nc76-osrm-backend-5.22.0
ls -la /nix/store/r1941bqkvsld0r973hgl9s9w3s46nc76-osrm-backend-5.22.0/bin

cc @erictapen for testing.

:+1: from me, as the test from #43442 passes. Btw, could the person merging this also merge #43442?

@erictapen Is it okay to merge this without merging #43442 ? I am comfortable merging this but not that.

@r-ryantm Sure. It is not necessary, just makes testing easier in the future.

Oh no, I just recognized, that I referenced the wrong issue. I meant #53442. m(


fix(designer): Fix invoker connection toggle behavior

Before:
By default the invoker connection toggle was on:

After the fix:
By default the "Use Invoker's Connection" toggle is off:

You are missing changes in core/actions/bjsworkflow/setting.ts to remove the connectorId check from isInvokerConnectionSupported method.

You are missing changes in core/actions/bjsworkflow/setting.ts to remove the connectorId check from isInvokerConnectionSupported method.

Removed and updated branch with required settings

You are missing changes to remove the connectorId constant -
INVOKER_CONNECTION: {
DATAVERSE_CUD_TRIGGER: 'When_a_row_is_added,_modified_or_deleted',
DATAVERSE_CONNECTOR_ID: '/providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps',
},
Also, we should never reupdate the connectionReferences sent to designer from host. Please remove the method - addInvokerSupport from connectionslice.
No where in the code you will find any host doing it, host should be modifying the connection reference if needed before sending it to the designer.
manage connection references in the portal code before sending it to designer, in logic apps portal we also do that.

connectorId removal is still pending

Removed


This site can’t be reached

Problem encountered on https://dotnet.microsoft.com/learn/web/aspnet-hello-world-tutorial/run
Operating System: windows
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Do you mean localhost? In that case it is likely firewall problem on your side.
Try another machine/VM, or check your network settings.

Maybe occur from "https://localhost:5000" that types in tutorial  try to change it to http://localhost:5000/ instead. Cut s from https:

There was a mistake in the instructions on this one (as @grenadin pointed out). Issue is now fixed.


Naming of training images

Hello,
How should the images under ./kitti_format/data/kitti/image be named? Left images are named like 000000.png ... 007480.png. Are the right ones should 007481.png ... 014961.png?
Thank you for your consideration.

Yes you are right. In total you should have 14962 images in that folder.


Hidden tabs mount

Is it normal that all hidden tabs mount when TabNavigator screen is active?

Found lazyLoad option in TabNavigatorConfig


Multiple databases and multiple language support?

Is it possible to provide support for multiple databases and multiple language libraries from the cli based on this prisma.schema, developers operate crud like a database.  specify the database with @@ in model, and specify language with multple generator,  look like:
//  prisma.schema file:
datasource db_A {
  provider = "mysql"
  url = "db_A address"
}
datasource db_B {
  provider = "mysql"
  url = "db_B address"
}
generator  js {
  provider      = "js"
  output        ="js_path"
}
generator  go  {
  provider      = "go"
  output        ="go_path"
}
model User {
  @@database(db_A)   // like this
  id               String     @id @default(cuid())
  name         String
}
model Post {
  @@database(db_B)  // like this
  id           String     @id @default(cuid())
  user       User
}

Yes, we have designed the schema to keep this feature in mind. But the scope of this feature is very vast and it would take us quite some time to support this.
You can watch @mavilein's talk on how Prisma works under the hood and how we are going to achieve this in future: https://www.youtube.com/watch?v=RAoXdyI_PH4
We are focusing on the stability of the current feature set right now.
Closing this as a duplicate of #265


adns: 1.5.1 -> 1.5.2

Motivation for this change
Security update which fixes various CVEs:
CVE-2017-9103
CVE-2017-9104
CVE-2017-9109
CVE-2017-9105
CVE-2017-9106
CVE-2017-9107
CVE-2017-9108
Closes #91310
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions (Ubuntu)

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

merge conflict

Superseded by f5f485e23156a06941cad9ad0481b06025fbd0d3


Change some pet emoji

this PR was formerly known as #170 but stale bot closed it because stale bot doesn't know what a draft is
Reasons for each change:
🐈->🐆 and 🐱->🐈⬛ switch to a colored cat that more closely reflects the in-game head
🐇->🐰 and 🐒->🐵 switch to face variant because the pet is a head in-game
🐑->🐏 switch to a ram because the sheep pet has horns in-game
🐛->🪳 switch from a caterpillar to a cockroach to more closely approximate a silverfish
🐴->🦓 use zebra for skeleton horse because the stripes look like bones
🐛->🐜 switch from a caterpillar to an ant to more closely approximate an endermite
🗿->🪨 use new rock emoji for rock pet

wtf is a draft

wtf is a draft

It's a PR wich isn't finished yet and cannot be merged untill the author sets it to not be a draft
I'm this case I have set it to a draft because it shouldn't be merged untill major OSs add support for new Unicode fetures

i probably should've added /j or /s in there

Android 11 and iOS 14 fully smart unicode 13 however Windows is still on Unicode 12 but the latest insider builds of Windows support Unicode 13 so as soon as those stable we can merge this thing https://blogs.windows.com/windows-insider/2020/12/10/announcing-windows-10-insider-preview-build-21277/

I am making this a full PR instead of a draft but be warned if this PR is merged in its current state the following pet emoji will not be displayed correctly on windows:
black cat: 🐈⬛
silverfish: 🪳
rock: 🪳
will look like this on windows:

Honestly it's just a temporary windows issue that will be solved soon™, and it only affects a few specific pets only in discord embeds (or other embeds) so I think we can just merge it now.

I am making this a full PR instead of a draft but be warned if this PR is merged in its current state the following pet emoji will not be displayed correctly on windows:
black cat: 🐈⬛
silverfish: 🪳
rock: 🪨
will look like this on windows:

On Android 10 it looks about the same as the Windows picture

On Android 10 it looks about the same as the Windows picture

Also iOS 13

I would merge anyway, it's not a big deal anyway


Add support for running wasm-snip

See also https://github.com/xtuc/rust-plugin/issues/1 and #153
Basically there are four main options:

Should we snip the std::panicking code? yes/no

Should we snip the std::fmt code? yes/no

Here are some specific functions to snip. (list of zero or more strings)

Here are some regex patterns of functions to snip. (list of zero or more strings)

following up on this feature request- do we still want to do this? how do we want to prioritize this?

do we still want to do this?

Yes, I believe so.

how do we want to prioritize this?

Not super high, in my opinion. I think the existing RFCs, wasm-opt support, and serve/watch are probably all higher priority.


Get logged in username by another plugin

I develop a Kibana plugin. And I need to know currently logged in username.
Is there a method/property available to get this information?

This has been answered on Google Groups already:
https://groups.google.com/forum/#!topic/search-guard/QDFthgZti0U
Please use GitHub Issues for reporting bugs only.


alignment cleanup

removed comment references to proposition which is currently out of scope.
rename subjectClassification to classification since it is a statement-level field not specific to subject
remove unnecessary extra classification field left over from prior commit.

re:

rename subjectClassification to classification since it is a statement-level field not specific to subject.

I'll push back here. This attribute holds a single term that classifies the subject concept. It's description clearly states that it is about a category this subject (a variant in our case) belongs to:

A single term or phrase summarizing the outcome of direction and strength
assessments of a Statement, in terms of a classification of the Statement's
subject. Permissible values for this attribute are typically selected to be
succinct and familiar in the target community of practice. e.g. 'likely pathogenic'
in the domain of variant pathogenicity classification.

I suggested the name subjectClassification to makes this clear - as calling it classification raises the question "classification of what".  Why not answer this question in the name of the property, so the user doesn't misinterpret, or need to go find the schema to understand what this means?
This is not necessary of course. But as I's said, my preference is to name properties to be as informative/explicit as pragmatically reasonable. And I also really want to lean into the subject / predicate / object paradigm here - use these wherever possible if it helps make the meaning of the data less ambiguous.  If we are going to use SPOQ naming conventions, then let's use them to their maximum potential - not say we'll use it but then strip it out from places it provides value.

re:

stripping all reference to propositions from the model:

IMO the concept of a proposition is central to the VA-SEPIO model, and key to conveying important nuance around what Statements are, and what they assess to be true or false based on a specific level of confidence or evidence.  Even if we do not include the Proposition class in this version of the core-im (which I don’t prefer but would concede to), I think we should continue to reference the notion of a 'proposition' in the descriptions of the classes and properties (which you removed in this PR).
Below I lay out how I would prefer to define the classes and properties where you removed reference to propositions, and explain how/why I think these definitions are clear and useful.
Statement class definition:
In defining the Statement class, we should make it clear that SPOQ attributes hold the 'Proposition' (possible fact) that a Statement either puts forth as true, or describes the state of evidence/confidence using strength and direction attributes. This is the paradigm we are selling and should commit to in our definitions.  The following definition does this:
"A claim of purported truth as made by a particular agent, on a particular occasion.
Statements may be used to simply put forth a proposition (i.e. a possible fact) as true,
or to provide an assessment of the level of confidence or evidence surrounding such a proposition."

We can supplement this definition with a comment and/or guidance in our docs that provides more info/examples:
"The subject, predicate, object and qualifier fields express the core "proposition" of a Statement.
A Statement object can simply put forth this proposition as true (e.g. assert that "BRCA2 c.8023A>G
is pathogenic for Breast Cancer").  If desired, the 'direction' and 'strength'  attributes can be used to
report a more nuanced assessment of this proposition - that describe the overall state of evidence
or confidence surrounding a proposition that may or may not be true. For example, that "there is minimal
evidence supporting the proposition that "BRCA2 c.8023A>G is pathogenic for Breast Cancer", or that "we
have very high confidence that the proposition "BRCA2 c.8023A>G is pathogenic for Breast Cancer" is false)."

Then, having established for users what a proposition is in the context of a Statement  - we can use it to more clearly and accurately define other Statement attributes.    (Note @larrybabb  that by removing references to propositions in these attribute descriptions, you unintentionally changed their meaning to be ambiguous or incorrect).
For example:
In the Statement.classification property definition:
"A single term or phrase summarizing the outcome of direction and strength"
assessments of a Statement, in terms of a classification of the Statement's
subject. Permissible values for this attribute are typically selected to be
succinct and familiar in the target community of practice. e.g. 'likely pathogenic'
in the domain of variant pathogenicity classification'.

Removing mention of 'proposition' as Larry did in #174 makes the definition of this attribute inaccurate.  Statements are not assessed in a Statement object.  The SPO proposition is assessed, and assigned strength and direction attributes which are part of the Statement.
In the Statement.hasEvidenceOfType definition:
A term describing a type of evidence used to assess the validity of Statement's proposition"

Again, removing mention of 'proposition' as Larry did in #174 makes the definition of this attribute inaccurate  . . .  evidence is used to assess the SPO proposition of a statement, not the Statement itself - as  the Statement includes the outcome of the evidence assessment (in its 'strength' and 'direction' fields)
In the Statement.hasEvidenceLine:
"A discrete, independent argument relevant to the validity of the proposition (possible fact) assessed or put forth in the Statement. This argument is based on the interpretation of one or more  pieces of information as evidence."

@LarryBabb I would like to make a PR to add these defs back into the yaml file.
In my mind, the only argument against this is that we want to wait until next release to introduce this level of nuance. As none of the current implementations really take advantage of it.  But I think it is still worth including now, as a selling point for the model, and to paint a more complete picture of what Statements actually are, and can do for you.

re:

rename subjectClassification to classification since it is a statement-level field not specific to subject.

I'll push back here. This attribute holds a single term that classifies the subject concept. It's description clearly states that it is about a category this subject (a variant in our case) belongs to:

@mbrush I might need some clarification on how you are describing this because it appears to me that the 'classification' is about the subject in the context of the disease based on the predicate relationship and it doesn't seem to be just about the subject. But let's discuss at our next sync up.

Removing mention of 'proposition' as Larry did in #174 makes the definition of this attribute inaccurate. Statements are not assessed in a Statement object. The SPO proposition is assessed, and assigned strength and direction attributes which are part of the Statement.

@mbrush I see your point, but wouldn't this mean that the classification is really the propositionClassification versus a subjectClassification? I see you point in keeping the definition of a Proposition in play to help be specific about when items are related to the Proposition versus component parts of it.


IMPRO-1814. Add sig phase mask

IMPRO-1814
Updates SnowFraction plugin to handle masked input data as divide-by-zero gives a different behaviour (returns masked-True rather than np.nan).
Adds SignificantPhaseMask plugin and CLI (phase-mask) to convert a snow-fraction field into a mask for one of rain, sleet or snow.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 3

Complexity increasing per file
==============================
- improver_tests/acceptance/test_phase_mask.py  2
- improver_tests/snow_fraction/test_SnowFraction.py  4
- improver/cli/phase_mask.py  1
- improver/psychrometric_calculations/significant_phase_mask.py  6
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6

Clones added
============
- improver_tests/snow_fraction/test_SnowFraction.py  6

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/snow_fraction/test_SnowFraction.py  4
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6
- improver/psychrometric_calculations/significant_phase_mask.py  6
- improver_tests/acceptance/test_phase_mask.py  2
- improver/cli/phase_mask.py  1

Clones added
============
- improver_tests/snow_fraction/test_SnowFraction.py  6

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6
- improver_tests/snow_fraction/test_SnowFraction.py  6
- improver_tests/acceptance/test_phase_mask.py  2
- improver/psychrometric_calculations/significant_phase_mask.py  6
- improver/cli/phase_mask.py  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver/cli/phase_mask.py  1
- improver_tests/acceptance/test_phase_mask.py  2
- improver_tests/snow_fraction/test_SnowFraction.py  6
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6
- improver/psychrometric_calculations/significant_phase_mask.py  6

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/snow_fraction/test_SnowFraction.py  6
- improver_tests/acceptance/test_phase_mask.py  2
- improver/cli/phase_mask.py  1
- improver/psychrometric_calculations/significant_phase_mask.py  6
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver/psychrometric_calculations/significant_phase_mask.py  6
- improver_tests/acceptance/test_phase_mask.py  2
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6
- improver_tests/snow_fraction/test_SnowFraction.py  6
- improver/cli/phase_mask.py  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/acceptance/test_phase_mask.py  2
- improver/cli/phase_mask.py  1
- improver_tests/snow_fraction/test_SnowFraction.py  6
- improver/psychrometric_calculations/significant_phase_mask.py  6
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver/cli/phase_mask.py  1
- improver_tests/snow_fraction/test_SnowFraction.py  3
- improver/psychrometric_calculations/significant_phase_mask.py  5
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6
- improver_tests/acceptance/test_phase_mask.py  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver/cli/phase_mask.py  1
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6
- improver_tests/acceptance/test_phase_mask.py  2
- improver_tests/snow_fraction/test_SnowFraction.py  4
- improver/psychrometric_calculations/significant_phase_mask.py  5

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/acceptance/test_phase_mask.py  2
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6
- improver/cli/phase_mask.py  1
- improver_tests/snow_fraction/test_SnowFraction.py  4
- improver/psychrometric_calculations/significant_phase_mask.py  5

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/acceptance/test_phase_mask.py  2
- improver_tests/snow_fraction/test_SnowFraction.py  4
- improver/psychrometric_calculations/significant_phase_mask.py  5
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6
- improver/cli/phase_mask.py  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/acceptance/test_phase_mask.py  2
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6
- improver_tests/snow_fraction/test_SnowFraction.py  4
- improver/cli/phase_mask.py  1
- improver/psychrometric_calculations/significant_phase_mask.py  5

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/acceptance/test_phase_mask.py  2
- improver/cli/phase_mask.py  1
- improver/psychrometric_calculations/significant_phase_mask.py  5
- improver_tests/snow_fraction/test_SnowFraction.py  4
- improver_tests/psychrometric_calculations/test_significant_phase_mask/test_SignificantPhaseMask.py  6

See the complete overview on Codacy


Dev

Description
GitHub Issues

Coverage decreased (-10.4%) to 80.174% when pulling 48ed02427db0e2d04ce7b0af79b90dff3338f830 on dev into daf41c6df926bcea38fac3d1f90a5d525544630b on revert-145-master.

I did this manually, but thank you for reminding me.

Coverage decreased (-12.4%) to 78.223% when pulling bee26014a30883b949b8e532726a0a8f42ee59bc on dev into daf41c6df926bcea38fac3d1f90a5d525544630b on revert-145-master.


Add missing support for C++ exceptions

Specifying -fexceptions for the compiler is not enough.

add necessary zero padding after .eh_frame section
link .gcc_except_table_table in a way flash script does not complain
call __registrer_frame_info before global constructors

Kudos jcmvbkbc for the necessary help.
This (partially) solves #459

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

Cherry-picked as f698a1b2, thanks! Toolchain update coming up.


trying a demo pr

Please check the following:

[ ] Do the tests still pass?[^1]
[ ] Does the code comply with the style guide?

[ ] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Thanks @yashasbharadwaj1 I'll close this for now - let us know if you need help with anything specific.


Request bookmarklet only handles trac ticket numbers

In pushmanager/templates/create_request_bookmarklet.js, bug numbers from reviewboard are parsed as:
 var ticketNumberToURL = function(bug) {
        return 'https://' + Settings['trac']['servername'] + '/ticket/' + bug.match(/\d+/)[0];
    };

This should either be more general to handle multiple types of issue ids or point to a separate service that can redirect to the correct place. Internally, we have separate redirect service.

This is already fixed: d7706df2fdf4630ce7f34ec3ecf389a32fca1d5c


Scroll Bar using WinAppDriver

Hi Team,
I am having vertical scroll bar in my windows application of class ScrollBar and I see the properties "RangeValue.Minimum" and "RangeValue.Maximum" are exposed. Also from inspect tool action menu, I can set the value for "RangeValue.SetValue" and on executing I see the scroll bar is moved accordingly.
Can someone suggest how do we call this method "RangeValue.SetValue" from WinAppDriver?
Looking forward for the support and thanks in advance.
Thanks
Karthik

Looking forward for some support from the community.
Thanks in advance

I'm not actually sure this is possible to set a value this way via the JSON Wire Protocol. I know you can get values like that via this command
/session/:sessionId/element/:id/attribute/:name
So instead of sending a value I suppose you could keep sending Keys.PAGE_DOWN or something and then keep checking the RangeValue.Value. Would be really nice to be able to set values that way though


Do I need to re-run process_tasks every time I make changes to my codes?

Hey guys,
Let's say I have process_tasks  running in the background. Now I go into my project and add a new function with background decorator:
@background(schedule=8)
def dummy_task():
    bot().send_message("This is a message from tasks.")

And then I register it normally from command line, do I need to stop process_tasks and then rerun it?
It looks like I have to, because when I register the task, I can see that it's registered into database. But it's not run. The moment I rerun process_tasks, it sends out the message.
Is that so?
The reason of this question is that in my server, I run process_tasks --duration 3600 which stop after 1 hour. Then we have a task scheduler to run this command every hour. It looks like whenever we make changes to the code, we'll have to wait till the next run for the new tasks to be executed?
***UPDATE: when I tried using python manage.py process_tasks --dev then this works. However it's not recommended to use in production, may I know why?

Hi @philippeowagner ,
May I know if this project is still being maintained?

We still use it in production, but we are all busy so open source development and community work falls a bit behind.
Yes, you have to restart. It's like the runserver thingy...

Thanks Philip!


netease-cloud-music-gtk: 1.2.2 -> 2.0.1

Description of changes
fixes https://github.com/NixOS/nixpkgs/issues/185428

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build netease-cloud-music-gtk


[cocoon] linux machines are not reporting the ip address

After the migration from ubuntu to debian and new hardware, linux
machines are not reporting the ip address anymore.

This is fixed


How To Send Multiple Data from cluster.queue to cluster.task

Just one question. How can i do this?
I have these data :
url : http://example.com
and 2 string data, example : firstName and lastName
The url is still the same in every browser, but, firstName and lastName will be changed every browser (firstName1 lastName1 for browser1, firstName2 lastName2 for browser2 and so on)
How I can pass these data from cluster.queue to cluster.task?

Please answer on stackoverflow. Here is the link :
https://stackoverflow.com/questions/71347869/how-to-send-multiple-data-from-cluster-queue-to-cluster-task


[Question] example test that launches the browser on standalone and does a search

Hi I have seen that a test can be created by using record and playback on the standalone but I would like to know if it is possible to programmatically write a js test that launches the safari browser on a device and types in a google search. The documentation does not indicate that this is possible,  a simple test would be appreciated

For this particular scenario we would recommend making use of our openUrl functionality to launch Google with a specific search term in the default browser of the device e.g.
test('test Appetize.io Google search', async ({ session }) => {
      const query = "Appetize.io";
      await session.openUrl(`https://www.google.com/search?q=${query}`);
      ... // validate search occurred
});

Alternatively, we also support opening an application via launchApp(appId), after which you could interact with elements on the screen via our various touch interactions.  For more test samples please have a look at our documentation here.

Thanks @dageforce but as the page launches in incognito mode, I am met with Googles accept cookies popup. Since there is no scrollIntoview function to scroll down to click on the accept cookies button, I will have to tap the "meer lezen" button 3 times to get to the accept cookies button. I could not find a way to tap multiple times in the docs.

@craitose the dialog in question is an EU requirement, so you could consider using the US region if this is something you would want to avoid.  Note: It is best to avoid setting this property unless absolutely necessary. Our system automatically directs requests to the closest servers for optimal performance. Using this property could lead to longer queues in busy regions.
Alternatively you can accomplish both those scenarios by making use of our swipe and findElement functions. We are working on introducing more helper functions to our SDK to help with these scenarios in the future.
I will close this issue as it's not related to our GitHub Actions but feel free to raise a Support Request for any other Appetize specific issues.


docs: add meta-comment about comment in pr template

Description
I saw this "meta-comment" in another repository recently and I thought I would add it here. So let contributors know, that they do not have to remove all the comments before creating PRs.
Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] Documentation content changes
[ ] Other (please describe):

Checklist

[ ] I have read the contributor guide.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

yes, this can be helpful

Can I merge, if I have two approvals?

Yes, go for it! I would say the general policy is that the person who cretes the PR merges, after approval.

Alright, thank you. That sounds reasonable.
Maybe we document that policy somewhere?


Fix exception handling in testcases

Exception handling in test cases have to be improved. Currently the method signatures of some of the testcases has clause throws Exception.

fixed in #14


Do you have some sort of community hub?

Hi there, I was wondering if you guys needed any help with the website or graphics in general. I think it's a pretty cool project and I thought I could maybe help out. I didn't see any way of getting in contact with you, and I saw there is no community hub anywhere, no Discord server or Matrix group. Maybe we could make one?
Cheers.

I'd welcome your contribution.
I've made a Discord server for discussions.


Failed calling webhook "mutation.azure-workload-identity.io", context deadline exceeded on GKE

Describe the bug
Installing Azure-Workload-Identity helm chart on GKE succeeded, but service accounts with the relevant label failed, and therefore their pods failed to launch.
Steps To Reproduce

Connect to GKE cluster, with default configurations.
Helm install Azure-Workload-Identity:
helm upgrade --install workload-identity-webhook azure-workload-identity/workload-identity-webhook --namespace azure-workload-identity-system --set azureTenantID=TENANT_ID --wait --version 1.0.0
Helm install a pod with a label:
azure.workload.identity/use: "true"

Expected behavior
The pod should get the relevant info injected using the Azure-Workload-Identity Mutating Admission Webhook. That action fails and the pod never launches.
Logs
Logs taken from the K8s events:
36s         Warning   FailedCreate        replicaset/pod-7c749d6c8f   Error creating: Internal error occurred: failed calling webhook "mutation.azure-workload-identity.io": failed to call webhook: Post "https://azure-wi-webhook-webhook-service.azure-workload-identity-system.svc:443/mutate-v1-pod?timeout=10s": dial tcp <IP_ADDRESS>:9443: i/o timeout
6s          Warning   FailedCreate        replicaset/pod-7c749d6c8f   Error creating: Internal error occurred: failed calling webhook "mutation.azure-workload-identity.io": failed to call webhook: Post "https://azure-wi-webhook-webhook-service.azure-workload-identity-system.svc:443/mutate-v1-pod?timeout=10s": context deadline exceeded
Environment
GKE 1.24.10-gke.2300, running on Linux.
Google Image type: Container-Optimized OS with containerd (cos_containerd)

36s Warning FailedCreate replicaset/pod-7c749d6c8f Error creating: Internal error occurred: failed calling webhook "mutation.azure-workload-identity.io": failed to call webhook: Post "https://azure-wi-webhook-webhook-service.azure-workload-identity-system.svc:443/mutate-v1-pod?timeout=10s": dial tcp <IP_ADDRESS>:9443: i/o timeout

@dotsuber Have you checked if the mutating webhook (mwh) pods are running and ready?

@dotsuber Any updates on the above?

The solution was to open port 9443 on GKE master firewall.


Signal.State.prototype.update to update values using callbacks

When using signals, often the value of a signal is not known, but a change needs to be made based on the current value. This pattern can be found in Svelte's stores, Solid's Signals, and React's useState, to name a few. This pattern leads to cleaner code with less clutter. Since using a callback in Signal.State.prototype.set is too ambiguous (setting the value to a function might be the preferred operation), it seems reasonable to add Signal.State.prototype.update. Here's some examples of how the update function would work:
let count = new Signal.State(0);
function increment() {
    count.update(c => c + 1);
}
function createCountdown(start, duration) {
    let countdown = new Signal.State(start);
    let interval = setInterval(()=>{
        countdown.update(c=> c - 1);
        if (countdown.get() === 0) clearInterval(interval);
    }, duration/start);
    return countdown;
}

function createTypewriter(text) {
    let typewriter = new Signal.State("");
    let chars = text.split('');

    function type(char) {
        return function() {
            typewriter.update(t => t + char);
        }
    };
    for (let index = 0; index < chars.length; index++) {
        setTimeout(type(chars[index]), 200 + index * 200);
    }
    return typewriter;
}

can you describe the situation in which the value can't be known? I don't understand
let known = count.get()

can you describe the situation in which the value can't be known? I don't understand
let known = count.get()

By known, I mean a case where the developer can't just do this:
count.set(42); //or any other constant value

...because the value could be acquired through user input, fetching, etc.
The update function is primarily a cleaner way to do:
let updater = c => c+1;
count.set(updater(count.get()));

...because the value could be acquired through user input, fetching, etc.

sorry I still don't understand this

is primarily a cleaner way to do

this I understand -- but I'd like to know what " user input, fetching, etc." patterns need the updater.
I feel like I'm missing something :\
sorry im dense!

this I understand (and am ok with, tbh) -- but I'd like to know what " user input, fetching, etc." patterns need the updater. I feel like I'm missing something :\
sorry im dense!

I meant like something where you'd have to use count.get() instead of a constant value, apologies for the bad explanation.
Example:
count.set(42); //constant ("known") value
count.set(count.get() + 1); //not "known" value


add Engine Six

SteamDB app page links to a few games using this

Alpha Zylon
Calvin Tucker's Farm Animal Racing
F1 Chequered Flag
FlatOut 3: Chaos & Destruction
Glacier 3: The Meltdown
Hyper Fighters
Monster Jam Battlegrounds
Pacific Liberation Force
Super Sonic Racer

Brief explanation of the change
a reworked rule from my old repo

After running changed rules in this pull request (this bot only tests rules.ini changes):
Changed technologies: Engine.Engine_Six
These apps now match: (9)<PHONE_NUMBER>40<PHONE_NUMBER>90<PHONE_NUMBER>50<PHONE_NUMBER>90 809900
Please confirm that all these changed apps are correct.


[BUG] Show me complete black screen in first time and in second time it's working fine.

Show me this error in the console when I am open the chat screen

W/libc    (26879): Access denied finding property "net.dns1"
W/libc    (26879): Access denied finding property "net.dns2"
W/libc    (26879): Access denied finding property "net.dns3"
W/libc    (26879): Access denied finding property "net.dns4"

When I move one video chat to another chat I have to get another error message

[ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: PlatformException(17, request to join channel is rejected, null, null)
E/flutter (28102): #0      StandardMethodCodec.decodeEnvelope
package:flutter/…/services/message_codecs.dart:607
E/flutter (28102): #1      MethodChannel._invokeMethod
package:flutter/…/services/platform_channel.dart:177
E/flutter (28102): <asynchronous suspension>
E/flutter (28102): #2      SessionController.joinVideoChannel
package:agora_uikit/controllers/session_controller.dart:404
E/flutter (28102): <asynchronous suspension>
E/flutter (28102): #3      AgoraClient.initialize
package:agora_uikit/src/agora_client.dart:69
E/flutter (28102): <asynchronous suspension>
E/flutter (28102): #4      _LiveMatchScreenState.initAgora
package:timemarks/…/live_screens/live_match.dart:49
E/flutter (28102): <asynchronous suspension>

Show me this error when I am exit from the video call

════════ Exception caught by widgets library ═══════════════════════════════════
The following assertion was thrown while finalizing the widget tree:
A SessionController was used after being disposed.

Once you have called dispose() on a SessionController, it can no longer be used.
When the exception was thrown, this was the stack
#0      ChangeNotifier._debugAssertNotDisposed.<anonymous closure>
package:flutter/…/foundation/change_notifier.dart:114
#1      ChangeNotifier._debugAssertNotDisposed
package:flutter/…/foundation/change_notifier.dart:120
#2      ChangeNotifier.removeListener
package:flutter/…/foundation/change_notifier.dart:233
#3      _ValueListenableBuilderState.dispose
package:flutter/…/widgets/value_listenable_builder.dart:177
#4      StatefulElement.unmount
package:flutter/…/widgets/framework.dart:4983
#5      _InactiveElements._unmount
package:flutter/…/widgets/framework.dart:1926

I have the same issue, except it does not work at all.

@lkrjangid1 Error code 17 can be because - you either joined a channel but didn't leave it successfully or you are trying to join channel with an incorrect or expired token.

Closing this issue for now. If you're still facing this issue please feel free to reopen this issue.


CONTRIBUTING.md: mention that the meta.license and meta.maintainers attributes must be set

Motivation for this change
So I've been reviewing a few PRs recently and I found that it's actually fairly common for these attributes to be left out (for PRs adding new packages). I know that CONTRIBUTING.md already has a link to the nixpkgs manual which mentions these attributes, but I felt that maybe these two lines could be added to CONTRIBUTING.md directly as well, seeing as though people seem to omit them from time to time?
The manual does say that a maintainer must be set, but I don't think the manual explicitly mentions that a license attribute must be set. However, even if the manual doesn't say a license must be set, I believe it's good form to require it for all packages (hence the line about meta.license), thoughts? For example, even if a package does not have a license, it can just be assumed to be nonfree (because I believe that's legally the case in basically all parts of the world?), and therefore have a license attribute stdenv.lib.licenses.unfree.
Just to clarify, obviously meta attributes are optional, but I'm talking about when a package is to be added to this nixpkgs repository.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

cc @edolstra since it's probably your choice as to whether meta.license should be mandatory (if it already isn't).
Build failure seems unrelated.


Add libopenblas.so without suffix

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
~[ ] Reset the build number to 0 (if the version changed)~
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

@conda-forge-admin please rerender

This is not correct. The .so should go in the openblas output and not libopenblas output

I'm trying to run smithy but I get the following error:
~/repos/openblas-feedstock/recipe add_so 49s
(openmeeg-feedstock-test) ❯ conda update conda-smithy -c conda-forge
Collecting package metadata (current_repodata.json): done
Solving environment: done

# All requested packages already installed.

~/repos/openblas-feedstock/recipe add_so
(openmeeg-feedstock-test) ❯ conda smithy recipe-lint .
Traceback (most recent call last):
  File "/home/sik/miniconda3/envs/openmeeg-feedstock-test/bin/conda-smithy", line 10, in <module>
    sys.exit(main())
  File "/home/sik/miniconda3/envs/openmeeg-feedstock-test/lib/python3.7/site-packages/conda_smithy/cli.py", line 477, in main
    args.subcommand_func(args)
  File "/home/sik/miniconda3/envs/openmeeg-feedstock-test/lib/python3.7/site-packages/conda_smithy/cli.py", line 372, in __call__
    return_hints=True,
  File "/home/sik/miniconda3/envs/openmeeg-feedstock-test/lib/python3.7/site-packages/conda_smithy/lint_recipe.py", line 574, in main
    results, hints = lintify(meta, recipe_dir, conda_forge)
  File "/home/sik/miniconda3/envs/openmeeg-feedstock-test/lib/python3.7/site-packages/conda_smithy/lint_recipe.py", line 392, in lintify
    for requirement in requirements:
TypeError: 'NoneType' object is not iterable

@massich, https://github.com/conda-forge/conda-smithy/pull/1175

@isuruf do you know how to patch it without the help of smithy?

Edit /home/sik/miniconda3/envs/openmeeg-feedstock-test/lib/python3.7/site-packages/conda_smithy/lint_recipe.py ?

any idea why conda-forge-linter is complaining? it passes with conda-smithy (master) passes
~/repos/openblas-feedstock/recipe add_so
(openmeeg-feedstock-test) ❯ conda smithy recipe-lint .
. is in fine form

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Add on to many mapping

This PR was still open in the old virtual-coach-server repository, see https://github.com/PerfectFit-project/virtual-coach-issues/pull/154 for remaining comments.
After merging this PR ask @svenvanderburg to remove all code from https://github.com/PerfectFit-project/virtual-coach-issues

Looks good now!