jquery.visible vs jquery-visible

We had a bower entry for "jquery.visible": "1.1.0" which used to point to this repository. Now it seems to be pointing to this other repository which clearly doesn't do the same behavior.
The fix was pretty easy, change "jquery.visible": "1.1.0" to "jquery-visible": "1.1.0", however we want to see if this is a result of a hijacked package, bower inferring dots (.) as dashes (-), or something else.

This is an issue with Bower/GitHub. We migrated our account from teamdf to customd— our original testing showed that stuff was automatically redirected to the new account, but GitHub seem to have made our old handle available since.


Request for step interpolation in TSI window

Request to update the TSI app and connecting Unreal functionality.
Graphs to be able to display data in steps as well as curved mode.
Would be useful when displaying Boolean data, for example occupancy or lights in the sample project.
This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [X] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Feature has been added and merged to main branch.


[SharedModel] Make requirements case insensitive

Related Issue
Fixes #3420
Description
Makes the shared model's (Android, iOS and UWP) requirement comparisson for element rendering work with case insensitive requirements, this means that "AdaptiveCards" and "adaptivecards" are the same requirement making it easier for users to correctly render their cards even if they got a small mistake when authoring their cards
How Verified
The RequiresCustomFeatureTest test was modified to check that two requirements written with mismatching capitalization were being matched correctly
Microsoft Reviewers: Open in CodeFlow

/azp run


[Framework] Define the rooch chain id on the Ethereum network

Rooch supports Ethereum RPC, so we need to define a chain id for the Ethereum RPC and Ethereum Wallet.
#604
@baichuan3 @yubing744 @wow-sven

Finished on #680  and #693


Blocking 11 mirror sites

These IPs are mirroring charities, entertainment sites, etc.

Thanks @Morty-Feldman — you da best!


[Docs]: Dynamic Menu Items - Menu Button Widget

Is there an existing issue for this?

[X] I have searched the existing issues

Engineering Ticket Link
https://github.com/appsmithorg/appsmith/pull/17652
Release Date
Merged into release on 1 Dec, 2022
First Draft
PR Here
Loom video
Here's an Unlisted YouTube Video
PRD
https://github.com/appsmithorg/appsmith/issues/12362#issuecomment-1202023433
Use cases or user requests
A popular use case is documented here in the issue description.

This is a WIP. I'll update here once it's ready to review.

Have raised a PR #649 for this. Have also attached the first draft and video links in the issue description above.
cc: @dilippitchika @somangshu

@dhruvikn can you fix the review items?

Yes @jnikhila

@cokoghenun - Tagging you here as we need a new video for Menu Button Widget.


Create CPU ring buffer allocator

Implement CPU allocator using ring buffer strategy. Be sure to unit test creation, allocation, and deallocation

Unit tests passing - d4a852d500082d7101fd18a016bafcf7fcf6503e


Woodpecker CI cannot connect to Gitea anymore

Description
I'm having trouble connecting my Woodpecker CI instance (v0.15.6) to Gitea (v1.18.5). This used to work some time ago (it definitely worked in the Gitea 1.17.3 days and potentially even later, but I can't easily downgrade that far back), but is suddenly failing now and I'm having a hard time figure out why.
I've tried redoing the OAuth configuration, but am still hitting the same error on the Woodpecker CI side:

Error while authenticating against OAuth provider

The Woodpecker CI server logs contain this:
{"level":"error","time":"2023-03-02T09:00:24+02:00","caller":"/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/api/login.go:59","message":"cannot authenticate user. Unknown API Error: 401\nRequest: '/api/v1/version' with 'GET' method 'map[Authorization:[token eyJhbG.....]]' header and '401 Unauthorized\n' body"}

Trying to use this JWT token against Gitea (curl -H 'Authorization: token eyJhbG...' https://gitea.DOMAIN) does indeed show a 401 Unauthorized error.

I've tried doing the OAuth exchange manually as well.

curl -H 'cookie: COOKIES_HERE' 'https://gitea.DOMAIN/login/oauth/authorize?client_id=$CLIENT_ID&redirect_uri=https%3A%2F%2Fwoodpecker.DOMAIN%2Fauthorize&response_type=code&state=woodpecker'
Get the code from the operation above. Example: gta_xldifg.......
Exchange the code for an access token: curl -XPOST --data client_id=$CLIENT_ID&client_secret=$CLIENT_SECRET&code=$CODE&grant_type=authorization_code https://gitea.DOMAIN/login/oauth/access_token
Get the access_token code from the JSON response

Then, hitting the Gitea API like this: curl -H 'Authorization: token $ACCESS_TOKEN' https://gitea.DOMAIN/api/v1/version
.. gives me a 401 Unauthorized error.

I've tried enabling debug logging on both the Woodpecker CI side and on Gitea's side, but I don't see anything interesting in the logs.
Looks like Gitea does issue an access token (confirmed by going through the flow manually), but then it won't accept the token for some reason. Am I doing something wrong? Is there some mismatch somewhere?
Gitea Version
1.18.5
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Rocky Linux 8.7
How are you running Gitea?
Gitea runs using the rootless version of the official container image (currently docker.io/gitea/gitea:1.18.5-rootless).
My installation is powered by the gitea-docker-ansible-deploy Ansible playbook.
Database
PostgreSQL

I have figured it out.
It turns out that I had enabled the Traefik Dashboard on the Gitea domain. This has the side-effect of capturing /dashboard and /api requests and forwarding them to Traefik.
This explains why trying to call /api/v1/version (or anything else like this) with a Gitea access token was giving me 401 Unauthorized responses.. My requests were going to Traefik and its API, not to Gitea.
The solution is to avoid enabling the Traefik Dashboard on the same hostname as Gitea, as there's definitely a conflict with regard to the /api routes.
Sorry for the bogus bug report! Hopefully this will be useful to someone else in the future.


fix: update release to run build

What This MR Does
Adds a yarn build before publishing so the dist folder is created before we publish

:tada: This PR is included in version 1.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add an RPC deleteAllPendingTransactions()

@joojis I added.

@junha1 I think you need to update the docker tag here too.


[Fix] setup.py install_requires dependencies housekeeping

Same as storehouse PR #6
Generated and upgraded requirements/*

thanks for reviewing, Italo


jobs.maxquest.all permission

*Detailed description of the issue:
the permissions
jobs.maxquest.[jobName].[number]
jobs.maxquest.all.[number]
This permission does not work at all, how can I make it work?
Even if I set higher or lower value in the jobs folder it does not add more jobs to the player with the permission.
Jobs version: <IP_ADDRESS>
Server Type (Spigot/Paper/etc): Paper
Server Version (using /ver): 1.17, 1.18, 1.19

0964e5b32b6f535f7271080078e1620ff7807bae

I don't know what to do with a commit

i have seen the update in spigot and it includes this, thanks


General preprocessing

creates function to process all of stems folder and apply dataset specific preprocessing when needed
creates function where user can go back and provide their own parameters if they are not satisfied with automatically set up json file

closing this because the general preprocessing is already implemented in #1


PowerShell Gating Script Issue

Hello,
Regarding the PowerShell gating script, it works well but there seems to be some sort of quirk with this for the dependency scanning.
We are using the script for pull request builds as well so that we can fix any dependency alerts that were flagged when the build last ran on master or if any new dependency issues are introduced in the updated code (pull request).
If we update a dependency that has been flagged when the build was last run on master in a pull request, the alert does not seem to clear even though a full dependency scan is being run, meaning the same results are returned all the time from when the build last run on maste*. So, we cannot actually see if what we have fixed is actually fixed and resolved. Only once the code is merged to master and the build is run and the dependency scanning happens then we see that the alert is cleared.
This does not seem right. If during a pull request build the dependency scanning is happening and if a previous dependency scan alert that has been flagged is now fixed in the pull request the alert results should be updated as well.
I wanted to ask if you are aware of any limitations when the dependency scanning happens for a pull request build? If it does not work for a pull request build meaning that only the dependency scan alerts for master build are shown and not for pull request branches via the API then I believe this should not work or maybe should be excluded from pull request build as it is not accurate.
Thank you.

Hey there,
We actually have a separate script that is intended to be run in a PR, check out this one: https://github.com/microsoft/GHAzDO-Resources/tree/main/src/pr-gating
It runs a diff comparing the default branch alerts against what is newly discovered on a scan against a PR merge branch and shows annotations comments and allows to get the PR.

Hi,
Thank you very much for that.
We have implemented our own variations of the script to suit our needs. It works well.
Cheers.


test: 补充 action 单测

Checklist

迟到的单测

[ ] npm test passes
[x] tests and/or benchmarks are included
[x] commit message follows commit guidelines

Description of change

Pull Request Test Coverage Report for Build 547436922

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 93.518%

Files with Coverage Reduction
New Missed Lines
%

src/interaction/grammar-interaction.ts
1
97.37%

Totals

Change from base Build 547428257:
-0.02%

Covered Lines:
10847

Relevant Lines:
11252

💛  - Coveralls


Disable fail-fast for nightly integration tests

When the nightly integration tests run if one of the sail operator / istioctl fails the other test in the matrix is cancelled due to fail-fast: true. Setting to false so we run both integration tests no matter the outcome of the first to complete.
See latest nightly here where the integration test for sail cancelled the integration test for istioctl:
https://github.com/Kuadrant/kuadrant-operator/actions/runs/7634245121

At the moment it doesn't affect PR's as only one of the matrix options is run (istioctl). In my opinion even if we reintroduce the integration tests on sail operator for PR's I think it makes more sense for both to run in case a change breaks integration in one and not the other?


Feature: Don't use all CPU threads when compressing and decompressing

What feature or improvement do you think would benefit Files?
7zip allow users to chose how many threads are used, while Files uses all of them. This makes compression/decompression faster but also lags out other programs especially when there playing audio.
Requirements

Set Files to leave 2 to 4 logical processor threads free

Alternate give user control on how many threads are used in settings

Files Version
<IP_ADDRESS>
Windows Version
10.0.22621.3737
Comments
No response

Does 7zip have this option when extracting archives?

It doesn't, I thought it used the same value as the create archive in 7zip interface but Files seem to be matching 7zip. This can be added for making an archive only


vstest hides problems when runtime libraries are broken

When vstest is used on dotnet/runtime and underlying implementation has broken networking implementation vstest fails with no details about the problem.
The error message issued is
Failed to negotiate protocol, waiting for response timed out after 90 seconds. This may occur due to machine slowness, please set environment variable VSTEST_CONNECTION_TIMEOUT to increase timeout.
Test Run Aborted.

The only detail in the verbose log is
TpTrace Error: 0 : 70249, 4, 2020/11/03, 14:16:15.080,<PHONE_NUMBER>333184, vstest.console.dll, ProxyExecutionManager.StartTestRun: Failed to start test run: Microsoft.VisualStudio.TestPlatform.ObjectModel.TestPlatformException: Failed to negotiate protocol, waiting for response timed out after 90 seconds. This may occur due to machine slowness, please set environment variable VSTEST_CONNECTION_TIMEOUT to increase timeout.
   at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TestRequestSender.CheckVersionWithTestHost()
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.SetupChannel(IEnumerable`1 sources, String runSettings)
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyExecutionManager.StartTestRun(TestRunCriteria testRunCriteria, ITestRunEventsHandler eventHandler)

@jkotas

cc @ViktorHofer

thanks for the ping. Marek and I talked about this offline and I asked him to file the issue. cc @nohwnd

If connection dies immediately, it incorrectly reports timeout, there is some bug in event completion which triggers the timeout message, rather than reporting the actual exception.

We assume that the networking works in vstest, for more flexible solution that can be made to run without network stack please go see Testing.Platform instead. https://aka.ms/testingplatform


Crash on filter validating

isRuleValid crashes with empty string

Marshaling error - "" marhals as NULL, not IntPtr to (char[]){0}

duplicate of https://github.com/AdguardTeam/CoreLibs/issues/815


How to use section index titles for UITableView? It is not showing up on the UI at all.

Checklist

[ ] Reviewed the README and documents.
[ ] Searched existing issues for ensure not duplicated.

Expected Behavior
Index section titles should show up.
Current Behavior
Index section titles are not showing up. I even inherited the TableViewDataSource<String,Int> and defined the section index title functions but they are not getting triggered.
Detailed Description (Include Screenshots)

Environment

version:
Swift version:
Swift 5.0
iOS version:
iOS 13.6
Xcode version:
11.3.1
Devices/Simulators:
Any
CocoaPods/Carthage version:
1.9

https://github.com/ra1028/DiffableDataSources/pull/29/commits/7e96a251d7007abc4bf68b4339d953703cae5ba4
This pull request solves the above issue. Please merge this into master branch.
@ra1028


Add ukrainian translation of K&R "The C Programming Language" book

I'm pretty sure the original is not free.


[DNM] raftstore: async apply

This moves all apply related logic to apply worker, so apply won't block raftstore thread.
Ref #1442.

Rest LGTM


[1383] Fix content status in decorator

Context
Course content status
Changes proposed in this pull request

Typo in how content_tag_unpublished was being added to content_status_badge
Remove   as i'm unsure of its purpose...

Guidance to review
After

 Extract some view logic into draper decorators [timebox: 1/2 day]


Kulfy: Watch sujetexa.com

Kulfy requests the watch of the watch_keyword sujetexa\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

sujetexa\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Appeared in https://metasmoke.erwaysoftware.com/post/249077, which at least does not satisfy the policy about disclosing affiliation. The comment above doesn't show any true positives because the report hadn't yet received feedback.

Approved by Eliah Kagan in Charcoal HQ


Define gamedata API, flow and structure

As the team
we need clearly defined interfaces, datatypes and ports when moving the gamedata between the subteams
Because it enables us to independently work on the different parts of the system without having to communicate back and forth.
Acceptance Criteria:

[x] Design document exists
[x] Design document describes the scope of how we intend to visualize the gamedata (live / replay / tickspeed and all that stuff)
[x] Design document contains description of what data is moved, in what way through which ports to enable visualizing games in the frontend.
[x] Architecture diagram is extended to include the flow of the gamedata

Architecture diagram will be extended, in the process of implementation


Mario jitters back and forth when beside/inside a fence.

gif framerate is low, in reality its much faster. sorry!
this happens when mario jumps towards a fence. he will get stuck inside of it (he can escape by jumping out of it)

Duplicate of https://github.com/Retro64Mod/Retro64Mod.github.io/issues/21


Added rule to resize emoji's within labels.

This pull request fixes issue #27548 where an emoji within a label causes the element height to change and be inconsistent.
The changes are what I proposed in the above issue, along with a comment for future contributors to understand why the definitions are in place.

I am little bit skiptical to accept this change as silvermind said, fixing size will not work.

It should have been fixed in 1.22 (or 1.23)?

Feel free to re-open if there is still a problem


Allow other opinions on which instance types are filtered

Tell us about your request
It seems that many instances types (i3* in particular) are disallowed by the opinionated filter at:
https://github.com/aws/karpenter/blob/2ea8ed43fb96fe02e027aac9b135e7cbd839dd68/pkg/cloudprovider/aws/instancetypes.go#L165
Is that something that can be relaxed? Either by including i3 in the filters above, or by allowing some sort of customization of the filter? (e.g., don't filter out any instance types explicitly specified in the provisioner's node.kubernetes.io/instance-type requirements?)
Thanks!
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
We have been running i3 instances (i3.2xlarge, i3en.3xlarge etc.) in our kubernetes cluster successfully, using the locally attached NVMes in our kubernetes jobs/statefulsets.
However, it seems that the filter alluded to above makes karpenter unsuitable for provisioning such nodes, which makes the just-in-time provisioning experience much less smooth than it could be if karpenter did support them.
Are you currently working around this issue?
Working around this for now by using the kubernetes cluster autoscaler to initiate scale ups/downs of the node group and/or manually messing with the autoscaling group / managed node group settings.

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

We wanted to reduce the scope to known families to avoid any surprises with new instances types that weren't compatible on release. I want to get @bwagner5's go ahead on this, but I'm supportive of allowing the i3 prefix.

I like the idea of ignoring the instanceType filtering if there's an explicit ask to use a particular type via node.kubernetes.io/instance-type.
The only issue I see is that for new instanceTypes, we may not choose the right AMI to go with it. For example, g5g's are ARM + GPU and there's no EKS-optimized AMI to use with that. Similar issues with g5s too. So maybe we make the check a little more stringent where if it's an instanceType unknown to Karpenter, tell us what AMI to use and only then does Karpenter accept it (i.e you have to use launch templates until we inline more launch template fields like the AMI).

Apologies, I missed this issue!  I think allow i3's are fine in the hardcoded filters. I also agree that if the user specifies an instance type in the provisioner we shouldn't filter it out.


add convenient function to "prepare" emptyroom raw file for maxwell_filter

this is the type of code that we currently need to write to process correctly emtpyroom file the same way as a subject raw file.
raw_er = mne.io.read_raw_fif('.../emptyroom.fif', allow_maxshield="yes")
raw_er.info["bads"] = bads
raw_er.info["dev_head_t"] = raw.info["dev_head_t"]
raw_er.set_montage(raw.get_montage())
raw_er = mne.preprocessing.maxwell_filter(
    raw_er, origin="auto", calibration=cal_fname, cross_talk=ct_fname,
)

the proposal is to simplify this to:
raw_er = mne.io.read_raw_fif('.../emptyroom.fif', allow_maxshield="yes")
raw_er = mne.preprocessing.prepare_maxwell_filter_emptyroom(raw_er, raw)
raw_er = mne.preprocessing.maxwell_filter(
    raw_er, origin="auto", calibration=cal_fname, cross_talk=ct_fname,
)

or maybe
raw_er = mne.preprocessing.maxwell_filter_prepare_emptyroom(raw_er, raw)

discussed with @larsoner and @hoechenberger

How do we deal with existing bads in the empty-room? If the raw_er contains bads that are not present in the raw, raw_er should probably get the union of raw.info['bads'] and raw_er.info['bads']. But then we'd again have a mismatch between raw and raw_er, unless we modify raw.info['bads'] too (also put the union of bads there).

But then we'd again have a mismatch between raw and raw_er, unless we modify raw.info['bads'] too (also put the union of bads there).

I would warn if the raw_erm has bads that raw does not

I would warn if the raw_erm has bads that raw does not

In the PR (#10537) I've added a parameter to the function, allowing the user to explicitly specify what should happen to the bads
Doing "nothing" and warning  is currently not implemented, but I could add this!


Add include and exclude to terms aggregation

Add include and exclude parameters to terms aggregation: https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-terms-aggregation.html#_filtering_values_4

There is no rush whatsoever!

@dean-shaff cool, so make sure to rebase on latest first and then submit the change if possible. There were some breaking changes in Rust 1.73.0 that required updating the code. Otherwise, CI tests would fail.

@dean-shaff sorry, I've been away and could only come back to this now. Could you split this PR into two? One for collapse, the other one for includes/excludes in terms aggregation?

Closing, implemented in two separate PRs.


[incubator/jaeger]Option to provide sampling strategies file

What this PR does / why we need it:
Allows users to pass along a sampling strategies file as per https://www.jaegertracing.io/docs/1.15/sampling/#collector-sampling-configuration
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @pavelnikolov

/lgtm

Needs another /lgtm @pavelnikolov, thanks!

/lgtm
Sent from my phone

On 2 Dec 2019, at 02:42, Naseem<EMAIL_ADDRESS>wrote:

Needs another /lgtm @pavelnikolov, thanks!
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.


bug: canceling swipe back animation causes white screen on android devices

Bug Report
Ionic version:

[x] 5.x
Current behavior:

Using swipe gestures to navigate back on Android devices leaves the screen completly white if the gesture is canceled mid-way.

Expected behavior:

Swipte back gesture should show the previous screen.
Steps to reproduce:

Push a new page in the view stack with navigateForward
Start the swipe back gesture (finger on left device side and move to the right)
... while holding the finger down, move back to the left side (to cancel the swipe animation)
==> Screen stays white

You can perform the gesture in a few milliseconds or take your time and do it very slowly. It is 100% reproducible.
Related code:
Enable the following in the app.module.ts
IonicModule.forRoot({
     swipeBackEnabled: true
}),

https://github.com/capc0/ion-android-swipe-gesture-white-screen
Other information:

Ionic info:

Ionic:

   Ionic CLI                     : 5.4.9 (C:\Users\Simon\AppData\Roaming\npm\node_modules\ionic)
   Ionic Framework               : @ionic/angular 5.0.7
   @angular-devkit/build-angular : 0.803.26
   @angular-devkit/schematics    : 8.3.26
   @angular/cli                  : 8.3.26
   @ionic/angular-toolkit        : 2.2.0

Cordova:

   Cordova CLI       : 9.0.0<EMAIL_ADDRESS>   Cordova Platforms : android 8.1.0
   Cordova Plugins   : cordova-plugin-ionic-keyboard 2.2.0, cordova-plugin-ionic-webview 4.2.0, (and 4 other plugins)

Utility:

   cordova-res : 0.6.0 (update available: 0.12.0)
   native-run  : 0.2.8 (update available: 1.0.0)

System:

   NodeJS : v10.16.0 (C:\Program Files\nodejs\node.exe)
   npm    : 6.13.7
   OS     : Windows 10

Thanks for the issue. This has been resolved via https://github.com/ionic-team/ionic/pull/21058 and a fix will be available in an upcoming release of Ionic Framework.

@liamdebeasi can you check if this is included in the actual 5.1.0 build? The issue is still present in that version for me. If it is, the solutions is not working :/

The problem seems to be that the ``display: none``` style does not get removed when canceling the animation

Issue is also present for me! Please fix!

All fixed. Here is a dev build if you would like to test: 5.2.0-dev.202005081341.bb62023.

LGTM. thanks for the quick response.

I think I found a similar issue to this one.
If you navigate forward and quickly swipe back while 'forward animation' is still in progress, it will go to previous screen and that screen will be blank because 'ion-page-hidden' class is not removed in that case.


3.2.x query relationship null

OGM 3.2.x returns null instead of RelationshipModel for relationship query.
Works in OGM 3.1.16
Using blank spring boot 2.2.2 as test project with
<dependency>
	<groupId>org.springframework.boot</groupId>
	<artifactId>spring-boot-starter-data-neo4j</artifactId>
</dependency>

and
<properties>
	<java.version>1.8</java.version>
	<neo4j-ogm.version>3.2.4</neo4j-ogm.version>
</properties>

Created 2 nodes and 1 relation in fresh neo4j 3.4.5 db.
docker run     --publish=7474:7474 --publish=7687:7687     --volume=$HOME/neo4j/data:/data     neo4j:3.4.5

CREATE (Raul)-[r:PLAYER_OF]->(It)

demo code:
@SpringBootApplication
public class TestApplication {

	public static void main(String[] args) {
		SpringApplication.run(TestApplication.class, args);
	}

	@Bean
	public CommandLineRunner run(Neo4jTransactionManager transactionManager) {
		return args -> {
			final SessionFactory sessionFactory = transactionManager.getSessionFactory();

			final Result result = sessionFactory
					.openSession()
					.query("MATCH (n)-[r]-(m) WHERE ID(n)=0 and ID(m)=1 RETURN r", Collections.emptyMap());

			System.out.println("results " + result.queryResults());

			StreamSupport.stream(result.queryResults().spliterator(), false)
					.flatMap(s -> s.values().stream())
					.forEach(s -> {
						System.out.println("is null? " + Objects.isNull(s));
						if(s != null) {
							System.out.println("class is " + s.getClass());
						}
					});
		};
	}
}

Reproduces with neo4j (4.0.0) as well.
Expected Behavior
Output of demo code
results [{r=(0)-[PLAYER_OF]->(1)}]
is null? false
class is class org.neo4j.ogm.response.model.RelationshipModel

this can be achieved by using 3.1.x ogm
	<properties>
		<java.version>1.8</java.version>
		<neo4j-ogm.version>3.1.16</neo4j-ogm.version>
	</properties>

Current Behavior
Output of demo code
results [{r=null}]
is null? true

That seems indeed a bug. As a workaround, you can modify your query
MATCH (n)-[r]-(m) WHERE ID(n)=0 and ID(m)=1 RETURN * or MATCH (n)-[r]-(m) WHERE ID(n)=0 and ID(m)=1 RETURN n, r, m, the the relationship get's mapped.
We work on a fix.

Would you mind sharing your domain model? Especially PlayerOf. Thanks

there are no models defined. PLAYER_OF is just a generic relationship label created in neo4j by cypher query "CREATE (Raul)-[r:PLAYER_OF]->(It)"

Thanks, I thought so. Than my workaround probably doesn't apply. See the tests that I have added in the above commit. In any case, that is fixed and will be released with 3.2.5. Thanks for reporting.


[Pythagorean Triplet] Clarifies instructions

Adds clarity to what max_factor is and that you must return a triplet up

This discussion is available for background.


Errors on the Token Grabber

File "C:\Users#####\Desktop\Tools\AstraaTool\Additional_File\6_TokenGrab\tokengrabber.py", line 19, in tokengrabber
print(f"""[{w}+]{w} Enter the name you want to give to the final file: """)
NameError: name 'w' is not defined

Don't run the token grabber script directly but run the file "AstraaHome" and choose the option "Token Grabber". Normally you won't have any problem. :)


Add functionality to set custom headers when calling RulesLoader.loadFromUrl

Add functionality to set custom headers when calling RulesLoader.loadFromUrl

Description

Related Issue
https://github.com/adobe/aepsdk-core-android/issues/248

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
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)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] 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 read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Closing this as we no longer need this API


CodeAnalysis Build Failure - Unused Variable

The build is failing with the below error due to unused variable.

"D:\12-Git\NuGetGallery\build.msbuild" (default target) (1) ->
"D:\12-Git\NuGetGallery\packages\NuGet.Services.Build.3.0.6\tools\NuGet.Services.FullBuild.msbuild" (default target) (2) ->
"D:\12-Git\NuGetGallery\NuGetGallery.sln" (Build target) (3) ->
"D:\12-Git\NuGetGallery\src\NuGetGallery\NuGetGallery.csproj" (default target) (4) ->
(RunCodeAnalysis target) ->
d:\12-Git\NuGetGallery\src\NuGetGallery\DataServices\V2Feed.svc.cs(78): error CA1804: Microsoft.Performance : 'V2Feed.Search(string, string, bool)' declares a variable, 'result', of type 'List', which is never used or is only assigned to. Use this variable or remove it. [D:\12-Git\NuGetGallery\src\NuGetGallery\NuGetGallery.csproj]
MSBUILD : error : Code Analysis detected errors.  See Code Analysis results window or log file for details. [D:\12-Git\NuGetGallery\src\NuGetGallery\NuGetGallery.csproj]

@RanjiniM I fixed this one last week, feel free to close the issue.


Adding a underscore character to valid characters ignores underscore

Describe the bug
Adding a special character (an underscore) to valid_chars_for_string does not exclude results which do not have the character in the string, until two misses.
To Reproduce
Initialized with
_valid_chars = '_' + string.ascii_lowercase
words = {'i_love_code': {'count': 5}, 'island': {'count': 2}, 'ironman': {'count': 2}, 'i_love_coding': {'count': 2}, 'i_love_machine_learning': {'count': 3}}
autocomplete = AutoComplete(words=words, synonyms={}, valid_chars_for_string=_valid_chars)
autocomplete.search(word=search_string, max_cost=1, size=10)

Formatted output with simulated input:
Valid Characers: _abcdefghijklmnopqrstuvwxyz
Search Input 'i' : i_love_code, i_love_machine_learning, island, ironman, i_love_coding
Search Input 'ir' : ironman
Search Input 'iro' : ironman
Search Input 'iron' : ironman
Search Input 'iron_' : ironman
Search Input 'iron_m' : ironman
Search Input 'iron_ma' :
Search Input 'iron_mai' :
Search Input 'iron_maid' :
Search Input 'iron_maide' :
Search Input 'iron_maiden' :

Search Input 'i' : i_love_code, i_love_machine_learning, island, ironman, i_love_coding, iron_maiden

Expected behavior
Much like the input 'ir' excludes 'i_love_code' I would expect 'iron_' to exclude 'ironman' and so forth. From this output, it looks like it only begins to exclude 'ironman' when the input reaches 'iron_ma'.
OS, DeepDiff version and Python version (please complete the following information):

OS: Ubuntu 21.04 + pyenv
Python 3.9.7

Additional context
This seems to have something to do with the max_cost parameter. If I raise it > 2 it matches even more then the unexpected results.

Hi @lazzarello
The fuzzy matching logic still sees enough similarities between them to include it in the results. You are right that the underscore character is treated differently. That's because internally we convert all spaces into underscores. Maybe internally we should switch from using underscore for that purpose to a Unicode character that is barely used.


Recording SQL statements in traces for X-Ray

Hi again,
I've been reading that X-Ray has a dedicated set of annotation fields for tracing SQL:
https://docs.aws.amazon.com/xray/latest/devguide/xray-api-segmentdocuments.html#api-segmentdocuments-sql
I'm connecting a PHP app to an RDS Aurora (MySQL) database and I'd like to trace the SQL calls, and ideally see RDS as a node in the service map.
I currently have my SQL statements added as standard annotations, however ideallyI could use the x-ray sql segment fields, and ideally that would show RDS as a node in X-Ray.
I'm currently just doing this:
$span->setAttributes(['sql' => $query, 'params' => $params]);

It works, but I don't get any sort of visibility into DB usage, load, etc.
Not sure if this is a supported feature I've missed, or a feature request for future.
Thanks, Scott

The document you linked is a reference to our X-Ray docs, which document behavior supported by the X-Ray API and SDKs. We don't currently support PHP in the X-Ray SDKs, only in opentelemetry-php. X-Ray support for PHP is still in it's early stages, and recording the metadata that you mentioned first requires the upstream instrumentation to also be recording it.
So yes, you are correct about this being a feature request! We'll definitely keep this on the roadmap

No problems @carolabadeer, and thanks for replying.
I know the project is relatively new and I'm well aware PHP is not officially supported ;-)
Can I ask one followup though? I understand from the docs that the Go Lambda collector/exporter layer supports tracing SQL now, so is it that OpenTelemetry doesn't support SQL tracing, or that aws-otel-php doesn't yet support it?


Facing issue to set environment variable to reference a kubernetes secret

For our project, we are using Azure Key Vault to encrypt password for mosquitto exporter container, the secret already exists in Key Vault. I am following this way - https://azure.github.io/secrets-store-csi-driver-provider-azure/docs/configurations/set-env-var/  created a Kubernetes secret and reference it by setting an environment variable for the password. However, the container is not created after I deploy the chart, error message shows Error: secret "keyvaultsecret" not found. In our case, secret already exists in Key Vault, then what value should we use for the secretName in the secretObjects? Here is the output of my  helm install --debug --dry-run

secret-provider-class.yaml
# Source: mosquitto/templates/secret-provider-class.yaml
apiVersion: secrets-store.csi.x-k8s.io/v1
kind: SecretProviderClass
metadata:
  name: "dms-eg-kv-0-mosquitto"
  labels:
    app.kubernetes.io/name: mosquitto
    app.kubernetes.io/instance: goodly-guppy
    app.kubernetes.io/managed-by: Helm
    helm.sh/chart: mosquitto-1.0.23-users-qianwenyan-dev-update.104
  annotations:
    app.kubernetes.io/app-version: 2.0.14
    app.kubernetes.io/chart-version: 1.0.23-users-qianwenyan-dev-update.104
spec:
  provider: azure
  secretObjects:
  - secretName: keyvaultsecret
    type: Opaque
    data:
      - key: BmsMqtt--Password
        objectName: BmsMqtt--Password
  parameters:
    usePodIdentity: "false"
    keyvaultName: dms-eg-kv-0
    objects:  |
      array:
        - |
          objectName: mqttpasswordmosquitto
          objectType: secret
          objectVersion: ""
        - |
          objectName: BmsMqtt--Password
          objectType: secret
          objectVersion: ""
    tenantId: 72f988bf-86f1-41af-91ab-2d7cd011db47

stateful-set.yaml
# Source: mosquitto/templates/stateful-set.yaml
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: mqttbroker
  labels:
    app.kubernetes.io/name: mosquitto
    app.kubernetes.io/instance: goodly-guppy
    app.kubernetes.io/managed-by: Helm
    helm.sh/chart: mosquitto-1.0.23-users-qianwenyan-dev-update.104
  annotations:
    app.kubernetes.io/app-version: 2.0.14
    app.kubernetes.io/chart-version: 1.0.23-users-qianwenyan-dev-update.104
spec:
  replicas: 1
  serviceName: mqttbroker
  selector:
    matchLabels:
      app.kubernetes.io/name: mosquitto
      app.kubernetes.io/instance: goodly-guppy
  template:
    metadata:
      labels:
        app.kubernetes.io/name: mosquitto
        app.kubernetes.io/instance: goodly-guppy
      annotations:
        checksum/config: 27076bf29b9be07f644e30a7b25424597931a50e280fb692cbbfb00a70bc0ab
        checksum/secret: e4444bca2b66f0babfc6555a342196d34db23389732ab51d75782b55563821f
        prometheus.io/path: /metrics
        prometheus.io/port: "9234"
        prometheus.io/scheme: http
        prometheus.io/scrape: "true"
    spec:
      imagePullSecrets:
        - name: edgegateway-acr-secret
      containers:
        - name: mosquittoexporter
          image: "dmsacr0.azurecr.io/mosquittoexporter:0.8.0"
          resources:
            limits:
              cpu: 50m
              memory: 128Mi
            requests:
              cpu: 50m
              memory: 64Mi
          env:
            - name: MQTT_USER
              value: edgegatewayuser
            - name: MQTT_PASS
              valueFrom:
                secretKeyRef:
                  name: keyVaultSecret
                  key: BmsMqtt--Password
            - name: MQTT_CERT
              value:
            - name: MQTT_KEY
              value:
            - name: MQTT_CLIENT_ID
              value: mosquitto-exporter
            - name: BROKER_ENDPOINT
              value: mqttbroker:1883
        - name: mosquitto
          image: "dmsacr0.azurecr.io/mosquitto:2.0.14"
          imagePullPolicy: IfNotPresent
          ports:
            - name: mqtt
              containerPort: 1883
              protocol: TCP
            - name: websocket
              containerPort: 9090
              protocol: TCP
          livenessProbe:
            tcpSocket:
              port: websocket
            initialDelaySeconds: 5
            periodSeconds: 1
          readinessProbe:
            tcpSocket:
              port: websocket
            initialDelaySeconds: 3
            periodSeconds: 3
          resources:
            limits:
              cpu: 100m
              memory: 1024Mi
            requests:
              cpu: 50m
              memory: 512Mi
          volumeMounts:
            - name: config
              mountPath: /mosquitto/config/mosquitto.conf
              subPath: mosquitto.conf
            - name: data
              mountPath: /mosquitto/data
              subPath: "qianwen-ring0/mosquitto"
            - name: dms-eg-kv-0
              mountPath: /etc/keyvault
              readOnly: true
      volumes:
        - name: config
          configMap:
            name: mqttbroker
        - name: dms-eg-kv-0
          csi:
            driver: secrets-store.csi.k8s.io
            readOnly: true
            volumeAttributes:
              secretProviderClass: "dms-eg-kv-0-mosquitto"
            nodePublishSecretRef:
              name: "edgegateway-keyvault-secret"
  volumeClaimTemplates:
  - metadata:
      name: data
    spec:
      accessModes:
        - ReadWriteOnce
      resources:
        requests:
          storage: 1Gi

@irisvivian1993 In SecretProviderClass the secret name you're requesting for sync with the driver is keyvaultsecret but in the statefulset pod spec the secret ref name is keyVaultSecret. The second one is using camel case and doesn't match the secret name provided in SecretProviderClass

Sorry, forgot to update the latest version of stateful-set.yaml in the post. Attached updated version at here, both of them use keyvaultsecret but got error secret "keyvaultsecret" not found.
# Source: mosquitto/templates/stateful-set.yaml
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: mqttbroker
  labels:
    app.kubernetes.io/name: mosquitto
    app.kubernetes.io/instance: goodly-guppy
    app.kubernetes.io/managed-by: Helm
    helm.sh/chart: mosquitto-1.0.23-users-qianwenyan-dev-update.111
  annotations:
    app.kubernetes.io/app-version: 2.0.14
    app.kubernetes.io/chart-version: 1.0.23-users-qianwenyan-dev-update.111
spec:
  replicas: 1
  serviceName: mqttbroker
  selector:
    matchLabels:
      app.kubernetes.io/name: mosquitto
      app.kubernetes.io/instance: goodly-guppy
  template:
    metadata:
      labels:
        app.kubernetes.io/name: mosquitto
        app.kubernetes.io/instance: goodly-guppy
      annotations:
        checksum/config: d2733eafd6239ef5334c694df799b60cc1849ac8386b7997294f8ad7641cae6
        checksum/secret: bb28ae3f9177b94b542293f250da3bd58566bae5f6bb638a3731db41adef0d9
        prometheus.io/path: /metrics
        prometheus.io/port: "9234"
        prometheus.io/scheme: http
        prometheus.io/scrape: "true"
    spec:
      imagePullSecrets:
        - name: edgegateway-acr-secret
      containers:
        - name: mosquittoexporter
          image: "dmsacr0.azurecr.io/mosquittoexporter:0.8.0"
          resources:
            limits:
              cpu: 50m
              memory: 128Mi
            requests:
              cpu: 50m
              memory: 64Mi
          env:
            - name: MQTT_USER
              value: edgegatewayuser
            - name: MQTT_PASS
              valueFrom:
                secretKeyRef:
                  name: keyvaultsecret
                  key: BmsMqtt--Password
            - name: MQTT_CERT
              value:
            - name: MQTT_KEY
              value:
            - name: MQTT_CLIENT_ID
              value: mosquitto-exporter
            - name: BROKER_ENDPOINT
              value: mqttbroker:1883
        - name: mosquitto
          image: "dmsacr0.azurecr.io/mosquitto:2.0.14"
          imagePullPolicy: IfNotPresent
          ports:
            - name: mqtt
              containerPort: 1883
              protocol: TCP
            - name: websocket
              containerPort: 9090
              protocol: TCP
          livenessProbe:
            tcpSocket:
              port: websocket
            initialDelaySeconds: 5
            periodSeconds: 1
          readinessProbe:
            tcpSocket:
              port: websocket
            initialDelaySeconds: 3
            periodSeconds: 3
          resources:
            limits:
              cpu: 100m
              memory: 1024Mi
            requests:
              cpu: 50m
              memory: 512Mi
          volumeMounts:
            - name: config
              mountPath: /mosquitto/config/mosquitto.conf
              subPath: mosquitto.conf
            - name: data
              mountPath: /mosquitto/data
              subPath: "qianwen-ring0/mosquitto"
            - name: dms-eg-kv-0
              mountPath: /etc/keyvault
              readOnly: true
      volumes:
        - name: config
          configMap:
            name: mqttbroker
        - name: dms-eg-kv-0
          csi:
            driver: secrets-store.csi.k8s.io
            readOnly: true
            volumeAttributes:
              secretProviderClass: "dms-eg-kv-0-mosquitto"
            nodePublishSecretRef:
              name: "edgegateway-keyvault-secret"
  volumeClaimTemplates:
  - metadata:
      name: data
    spec:
      accessModes:
        - ReadWriteOnce
      resources:
        requests:
          storage: 1Gi

You can check the driver and provider logs to see why it's failing to create the secret. Here is the troubleshooting guide: https://azure.github.io/secrets-store-csi-driver-provider-azure/docs/troubleshooting/

Got error when I run kubectl get pods -l app=csi-secrets-store-provider-azure -o wide
No resources found in default namespace.
    + CategoryInfo          : NotSpecified: (No resources found in default namespace.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

Got error when I run kubectl get pods -l app=csi-secrets-store-provider-azure -o wide
No resources found in default namespace.
    + CategoryInfo          : NotSpecified: (No resources found in default namespace.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

@irisvivian1993 Which namespace do you have the driver and pods deployed in with the helm charts? You'll need to get the driver and provider pod log from the node in which your workload is running.

I tried that as well, but it shows no resources found. As the helm deployment failed due to the secret not found error, the pod is not up. When I run the kubectl get pods, the pod I am looking for is not in the list then how can I check the logs. We need to specify the pod name in the get logs command, right?
[BP1KF33.microsoftdatabox.com]: PS>kubectl get pods -l app=csi-secrets-store-provider-azure -o wide -n "bmsedgegateway-ring-0"
No resources found in bmsedgegateway-ring-0 namespace.
    + CategoryInfo          : NotSpecified: (No resources fo...ng-0 namespace.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

[BP1KF33.microsoftdatabox.com]: PS>kubectl get pods -l app=secrets-store-csi-driver -o wide -n "bmsedgegateway-ring-0"
No resources found in bmsedgegateway-ring-0 namespace.
    + CategoryInfo          : NotSpecified: (No resources fo...ng-0 namespace.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

[BP1KF33.microsoftdatabox.com]: PS>kubectl get pods -l app=secrets-store-csi-driver -n "bmsedgegateway-ring-0"
No resources found in bmsedgegateway-ring-0 namespace.
    + CategoryInfo          : NotSpecified: (No resources fo...ng-0 namespace.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

As the helm deployment failed due to the secret not found error, the pod is not up.

Did the helm install for the driver and provider fail? If the driver and provider are not running, then it will not be able to mount. Did you install following the steps from here? If you did, you can find the driver and provider pods in the node with issue and get the logs for it.

Thanks for your reply. I found the pods for driver and provider and pasted my found below.
[BP1KF33.microsoftdatabox.com]: PS>kubectl get pods -l app=csi-secrets-store-provider-azure -o wide -n "kube-system"
NAME                                                        READY   STATUS    RESTARTS   AGE   IP              NODE                    NOMINATED NODE   READINESS GATES
akvsecretsprovider-csi-secrets-store-provider-azure-vtt7h   1/1     Running   0          38d   <IP_ADDRESS>   k8s-bp1kf33cl-bp1kf33   <none>           <none>
[BP1KF33.microsoftdatabox.com]: PS>kubectl logs akvsecretsprovider-csi-secrets-store-provider-azure-vt -n "kube-system" --timestamps
Error from server (NotFound): pods "akvsecretsprovider-csi-secrets-store-provider-azure-vt" not found
    + CategoryInfo          : NotSpecified: (Error from serv...e-vt" not found:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

I found the pod for provider but didn't find any logs for it.
[BP1KF33.microsoftdatabox.com]: PS>kubectl logs secrets-store-csi-driver-btmrr -n "kube-system" --timestamps --since=1h | Select-String "failed"

2022-11-03T20:57:49.639347930Z {"ts":1667509069639.025,"caller":"cache/reflector.go:324","msg":"pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: failed to list *v1.Secret: secrets is forbidden:
User \"system:serviceaccount:kube-system:secrets-store-csi-driver\" cannot list resource \"secrets\" in API group \"\" at the cluster scope\n","v":0}
2022-11-03T20:57:49.639383732Z {"ts":1667509069639.0808,"caller":"cache/reflector.go:138","msg":"pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list
*v1.Secret: secrets is forbidden: User \"system:serviceaccount:kube-system:secrets-store-csi-driver\" cannot list resource \"secrets\" in API group \"\" at the cluster scope\n"}
2022-11-03T20:58:45.911253753Z {"ts":1667509125911.0796,"caller":"cache/reflector.go:324","msg":"pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: failed to list *v1.Secret: secrets is
forbidden: User \"system:serviceaccount:kube-system:secrets-store-csi-driver\" cannot list resource \"secrets\" in API group \"\" at the cluster scope\n","v":0}
2022-11-03T20:58:45.911284757Z {"ts":1667509125911.1592,"caller":"cache/reflector.go:138","msg":"pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list
*v1.Secret: secrets is forbidden: User \"system:serviceaccount:kube-system:secrets-store-csi-driver\" cannot list resource \"secrets\" in API group \"\" at the cluster scope\n"}
2022-11-03T20:59:33.445314683Z {"ts":1667509173445.167,"caller":"cache/reflector.go:324","msg":"pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: failed to list *v1.Secret: secrets is forbidden:
User \"system:serviceaccount:kube-system:secrets-store-csi-driver\" cannot list resource \"secrets\" in API group \"\" at the cluster scope\n","v":0}
2022-11-03T20:59:33.445355387Z {"ts":1667509173445.2231,"caller":"cache/reflector.go:138","msg":"pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list
*v1.Secret: secrets is forbidden: User \"system:serviceaccount:kube-system:secrets-store-csi-driver\" cannot list resource \"secrets\" in API group \"\" at the cluster scope\n"}
2022-11-03T21:00:07.459720541Z {"ts":1667509207459.5479,"caller":"cache/reflector.go:324","msg":"pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: failed to list *v1.Secret: secrets is
forbidden: User \"system:serviceaccount:kube-system:secrets-store-csi-driver\" cannot list resource \"secrets\" in API group \"\" at the cluster scope\n","v":0}
2022-11-03T21:00:07.459755544Z {"ts":1667509207459.6035,"caller":"cache/reflector.go:138","msg":"pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list
*v1.Secret: secrets is forbidden: User \"system:serviceaccount:kube-system:secrets-store-csi-driver\" cannot list resource \"secrets\" in API group \"\" at the cluster scope\n"}
2022-11-03T21:00:53.489074666Z {"ts":1667509253488.8835,"caller":"cache/reflector.go:324","msg":"pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: failed to list *v1.Secret: secrets is
forbidden: User \"system:serviceaccount:kube-system:secrets-store-csi-driver\" cannot list resource \"secrets\" in API group \"\" at the cluster scope\n","v":0}
2022-11-03T21:00:53.489124670Z {"ts":1667509253488.9514,"caller":"cache/reflector.go:138","msg":"pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list
*v1.Secret: secrets is forbidden: User \"system:serviceaccount:kube-system:secrets-store-csi-driver\" cannot list resource \"secrets\" in API group \"\" at the cluster scope\n"}
2022-11-03T21:01:38.331119282Z {"ts":1667509298330.9268,"caller":"cache/reflector.go:324","msg":"pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: failed to list *v1.Secret: secrets is
forbidden: User \"system:serviceaccount:kube-system:secrets-store-csi-driver\" cannot list resource \"secrets\" in API group \"\" at the cluster scope\n","v":0}

I didn't find any log contains "error" or "keyvaultsecret", only found above logs repeat showing up.

@irisvivian1993 This is part of our troubleshooting guide: https://azure.github.io/secrets-store-csi-driver-provider-azure/docs/troubleshooting/#failed-to-create-kubernetes-secret-errsecrets-is-forbidden-user-systemserviceaccountdefaultsecrets-store-csi-driver-cannot-create-resource-secrets-in-api-group--in-the-namespace-default. If you're using the driver to sync as Kubernetes secret, you'll need to enable the feature so required roles and rolebindings are deployed.

but we have set syncSecret to true in our code.
{
        "name": "akvsecretsprovider",
        "type": "Microsoft.AzureKeyVaultSecretsProvider",
        "arguments": "--configuration-settings secrets-store-csi-driver.enableSecretRotation=true secrets-store-csi-driver.rotationPollInterval=3m secrets-store-csi-driver.syncSecret.enabled=true",
        "version": ""
      }

[BP1KF33.microsoftdatabox.com]: PS>kubectl get clusterrole/secretprovidersyncing-role
Error from server (NotFound): clusterroles.rbac.authorization.k8s.io "secretprovidersyncing-role" not found
    + CategoryInfo          : NotSpecified: (Error from serv...role" not found:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

[BP1KF33.microsoftdatabox.com]: PS>kubectl get clusterrolebinding/secretprovidersyncing-rolebinding
Error from server (NotFound): clusterrolebindings.rbac.authorization.k8s.io "secretprovidersyncing-rolebinding" not found
    + CategoryInfo          : NotSpecified: (Error from serv...ding" not found:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

@irisvivian1993 Are you using the azure-arc extension? If you're using arc extension the config flags are different: https://learn.microsoft.com/en-us/azure/azure-arc/kubernetes/tutorial-akv-secrets-provider#additional-configuration-options. Please provide the command you use to install the driver and provider.

The driver and provider were installed by someone else, but I think we are using the azure-arc extension as I can find the extension under extensions of Kubernetes - Azure Arc.

And previously the SecretProviderClass works fine with mosquitto container which uses azure key vault. Then I added a new container - mosquittoexporter and use environment variable to reference a kubernetes secret for it, then the issue happens.

Hello, any update on this issue? We are using azure-arc extension and we added configuration-settings change as mentioned in above doc alone with the changes in SecretProviderClass. Somehow, the helm deployment failed because of the secret not found error and also the configuration change is not getting pick up. Does it require to make the configuration change first before we make any other changes in SecretProviderClass?

@nilekhc they are using the arc-extension and it looks like the ClusterRole for sync secret is missing even with secrets-store-csi-driver.syncSecret.enabled=true?

Hello, any update on this issue? We are using azure-arc extension and we added configuration-settings change as mentioned in above doc alone with the changes in SecretProviderClass. Somehow, the helm deployment failed because of the secret not found error and also the configuration change is not getting pick up. Does it require to make the configuration change first before we make any other changes in SecretProviderClass?

Hi @irisvivian1993 Could you provide the output of the following?
az k8s-extension show --cluster-type connectedClusters --cluster-name $CLUSTER_NAME --resource-group $RESOURCE_GROUP --name akvsecretsprovider

This issue is actual now.


fix leap year script init error

was getting the following error when trying to run the script:

/home/we/dust/code/tokei/tokei.lua:114: attempt to perform arithmetic on a boolean value
stack traceback:
	/home/we/norns/lua/core/norns.lua:146: in metamethod '__add'
	/home/we/dust/code/tokei/tokei.lua:114: in global 'frame'
	/home/we/dust/code/tokei/tokei.lua:54: in global 'init'
	/home/we/norns/lua/core/script.lua:137: in function 'core/script.init'
	[C]: in function 'xpcall'
	/home/we/norns/lua/core/norns.lua:147: in field 'try'
	/home/we/norns/lua/core/engine.lua:91: in function </home/we/norns/lua/core/engine.lua:89>
norns.script.load("code/tokei/tokei.lua")

if i changed the year to a non leap year, it would run.
tried to edit the existing leap year expression, but had to re-write it to be a little easier to follow.

thanks.
I had forgotten about the existence of leap years...


Remove direct psycopg2 dependency and let user decide which to use

The psycopg2 dependency has gotten complicated due to a compatibility issue resulting in segfaults when using the binary-packaged version in some configurations.  They removed the pre-compiled version from the default psycopg2 package, which had the side effect of making more difficult for the average end-user to install without having development libraries and a compiler installed.
There's a full explanation here: https://github.com/psycopg/psycopg2/issues/674
Other dependent packages seem to be removing the transitive dependency and let the users decide which to use  - e.g., sqlalchemy-redshift here: https://github.com/fizyk/sqlalchemy-redshift/commit/1781ff8d9dd8642c39ab8aefed61e9b08058e6e1
I have a package here that I'd like to use sqlalchemy-postgres-copy in (https://github.com/bluelabsio/records-mover), and I'd prefer not to vendor it in or add a psycopg2 dependency because of this, so I thought I'd send a PR your way.  Let me know if it sounds right to you.
Fixes #12 but not in the same way proposed.

Hi @jmcarp!  Let me know if you have any thoughts on this one.

As a user of the pg8000 driver for PostgreSQL-via-sqlalchemy, this change would help me too.


Bump Version to 1.6.8 to include all bugfixes since 1.6.7

Describe the solution you'd like
Create new 1.6.8 Tag
So we have a tag to import in go modules, which includes the new features and fixes

List of commits since last release:
https://github.com/swaggo/swag/compare/v1.6.7...master

v1.6.8 is released now.


Add a new hook for using underlays that will prevent default so that …

…firefox doesn't start text selection
Closes
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

Closed in favor of #1469


Update Composer dependencies (2024-02-17-00-11)

Visual regression test passed!
View the visual regression test report


Isolate @nestjs/testing dependency

Extracts TestAppProvider to a different file (under src/__tests__)
This change removes the direct reference from app.provider.ts (used in production code) to @nestjs/testing

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

9 of 11 (81.82%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 82.496%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/tests/test-app.provider.ts
8
10
80.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
502

Relevant Lines:
607

💛  - Coveralls


update infrastructure TF with latest changes

Clusters created using this updated TF pass most OPCT tests. Main areas of improvement are better etcd latency and no more request timeouts/client connection lost.

Increased default master boot volume size from 500 -> 1024 and VPUs from 60 -> 90 to help with Disk I/O (etcd)
Increased default worker node count from 3 -> 4 and their VPUs from 20 -> 30
Removed NLB and replaced with 2 ALBs each set to have min/max bandwidth from 10 MB/s - 500 MB/s

Private internal load balancer that listens on ports 6443, 22623, 22624 and directs traffic to master nodes. DNS A
record for api-int is always pointing at the internal load balancer IP
Public external load balancer that listens on ports 80, 443, 6443. Traffic on ports 80 and 443 are directed to worker nodes, 6443 is directed to master nodes. DNS A records for api and *.apps are pointing here.

Remove BIOS as an option for the image capability schema so customers can’t change it from UEFI_64
Move policy for master_nodes to compartment instead of tenancy

Looks good to me


kafka integration: replace SASL authentication with Kafkarator provided TLS credentials

Fasit needs to be moved from default to a team namespace for Kafkarator integration to work.

kafka integration: replace SASL authentication with Kafkarator provided TLS credentials


Label not linked to input

Labels as generated by JSONEditor have no "for" attribute linking them to the input they describe. This way, when clicking the label text, the browser will not set the cursor to the input element associated with the label. In addition, screen readers would not pick up the label for a certain input field.
Implementing something like this would require the ability to create unique 'id' attributes on input elements. As an example of how this could be achieved / what is necessary, I have extended a theme as such:
JSONEditor.defaults.themes.labelGeneratingTheme = JSONEditor.AbstractTheme.extend({
	getFormControl: function(label, input, description) {
		if (undefined === JSONEditor._inputCounter) {
			JSONEditor._inputCounter = 0;
		}
		if ( ! input.id) {
			JSONEditor._inputCounter++;
			input.id = 'json-editor-' + JSONEditor._inputCounter;
		}
		label.setAttribute('for', input.id);
		return this._super(label, input, description);
	}
});

This code, unfortunately, is not very clean as it creates a global counter in an attribute on JSONEditor. If you would accept a similar patch, I'm happy to hear suggestions, improve it and send a pull request.

@jdorn, ping

@jdorn: ping? It seems there is a solution in this thread, is there a reason you are not accepting it?


[Bug] area_enclosed 2D gradient in functional.c

Describe the bug
The 2D area_enclosed gradient, not numerical gradient, is wrong.
To Reproduce
The area_enclosed gradient function is defined in functional.c
Expected behavior
The gradient should have cases like the 3D case.
Screenshots
n/a
Additional context
n/a

Can you provide a minimal example, @ancaandrei? This would really help us understand the bug.


SatSearchError: message: Forbidden

Pangeo maintains a Landsat 8 tutorial as part of the pangeo-tutorial notebooks. I've been going through and doing some updating and cleaning but not changing the overall tutorial content. I was pretty surprised yesterday because there was a cell that went from working normally to giving me a 403 error. Here is the cell:
properties =  ["landsat:tier=T1"]
bbox = (gfa.bounds.minx[0], gfa.bounds.miny[0], gfa.bounds.maxx[0], gfa.bounds.maxy[0]) #(west, south, east, north)
results = satsearch.Search.search(collection='landsat-8-l1',
                        bbox=bbox,
                        sort=['<datetime'], #earliest scene first
                        property=properties)
print('%s items' % results.found())
items = results.items()
items.save('set.geojson')

And here is the error:
SatSearchError                            Traceback (most recent call last)
<ipython-input-5-774276f8fe53> in <module>
      5                         sort=['<datetime'], #earliest scene first
      6                         property=properties)
----> 7 print('%s items' % results.found())
      8 items = results.items()
      9 items.save('set.geojson')

/srv/conda/envs/notebook/lib/python3.7/site-packages/satsearch/search.py in found(self)
     73         }
     74         kwargs.update(self.kwargs)
---> 75         results = self.query(**kwargs)
     76         return results['meta']['found']
     77

/srv/conda/envs/notebook/lib/python3.7/site-packages/satsearch/search.py in query(cls, url, **kwargs)
     83         # API error
     84         if response.status_code != 200:
---> 85             raise SatSearchError(response.text)
     86         return response.json()
     87

SatSearchError: {"message":"Forbidden"}

This code worked previously, so I'm unsure how to troubleshoot this. Any thoughts?

Hey, I had a similar problem refer the below link it had a solution as well.
https://github.com/sat-utils/sat-search/issues/94

Hi @salvis2 , sorry about that, as @chaitanya2ivvala pointed out the solution is in #94 - add an environment variable with the actual URL.
I'll be adding Landsat into the new catalog, at which point the tutorials can be updated to use the new sat-search and new catalog, there's only a couple modifications that are needed.

Gotcha. Thank you @chaitanya2ivvala , I forgot to check the closed issues before posting.
@matthewhanson , do you know if you are going to release a new version of sat-search soon? My current use-case is a tutorial being run by binder. I think I'm pinned to v0.2.2 whenever that was put into the Docker image, so I the fix isn't working for me probably because the os.getenv call isn't in my sat-search.

@salvis2 I posted in the above issue, but the fix for now is to pin sat-search to 0.2.3.
When the new earth search has Landsat in it we can update the notebook to use that with the new 0.3.x sat-search


AgentPopulation Refactor

Replaces AgentPopulation with new classes AgentVector, AgentVector::Agent & AgentInstance.
Both C and Py interfaces have full test suites.
Closes #246
TODO:

[x] Update all C tests (aside from explicit AgentPopulation/AgentInstance tests)
[x] Update SWIG to generate python for the new interface
[x] Update all Py tests (aside from explicit AgentPopulation/AgentInstance tests)
[x] Update py example(s)
[x] Remove AgentPopulation/AgentInstance throughout.
[x] Rename AgentElement to AgentInstance?
[x] Update and extend C AgentPopulation/AgentInstance tests to cover new classes.
[x] Update and extend SWIG AgentPopulation/AgentInstance tests to cover new classes.
[x] Tweak AgentView internally to hold a weak_ptr to the data map, so it knows if it's AgentVector has gone out of scope. It currently has a reference, this will just allow a more explicit exception.
[x] Convert AgentView so it is a nested classtypedef of AgentVector called AgentVector::Agent (SWIG wasn't happy with template functions of a nested class)

SWIG version of AgentVector doesn't have an AgentVector::erase() equivalent. The proper equivalent would be pythons pop() function but that returns the erased item Which in this case would be an AgentElement.
This same issue applies to RunPlanVec (they use the same SWIG hack for making it usable like a python list). Although I haven't checked how RunPlanVec handles deletion of items in C.

todo rename AgentView to AgentVector::View

SWIG version of AgentVector doesn't have an AgentVector::erase() equivalent. The proper equivalent would be pythons pop() function but that returns the erased item Which in this case would be an AgentElement.

I just gave swig a copy of C insert/erase which take size_type rather than iterator, and have no return value (rather than returning an iterator).


ZinChanManga

Source information
1.4.33
Source language
English
Source new URL
https://zinchanmanga.net/
Other details
The old link (zinchanmanga.com) not dead yet but the content had many skipped chapters and some title is not been updated.
The new link had a whole chapters and more updated titles.
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] I will fill out all of the requested information in this form.

Sorry, the bot tripped on the "not been updated" keyword.


License?

Is there an intention for the authors to add a license to this repo? It would be nice to know if the intention is for this code to be Open Sourced or not

I recently added a MIT license file, so open-source it is...


Failed to activate the punchclock package

[Enter steps to reproduce below:]

... Install punchclock
...reload atom

Error: [Enter steps to reproduce below:]

...
...

Atom Version: 0.188.0
System: linux 3.13.0-46-generic
Thrown From: Atom Core
Stack Trace
Failed to activate the punchclock package
At undefined

- Timekeeper is active & functional only with a valid project open

Commands

Config
{
  "core": {
    "themes": [
      "one-dark-ui",
      "one-dark-syntax"
    ],
    "followSymlinks": true
  },
  "editor": {
    "invisibles": {}
  }
}

Installed Packages
# User
color-picker, v1.5.0
linter, v0.12.0
linter-php, v0.0.11
minimap, v4.6.0
punchclock, v0.5.0
wakatime, v4.0.1

# Dev
No dev packages

Atom Version: 0.188.0
System: linux 3.13.0-46-generic
Thrown From: Atom Core
Stack Trace
Failed to activate the punchclock package
At undefined

- Timekeeper is active

You need to re-open this issue on the punclock repo.

The offending line is https://github.com/queenp/punchclock/blob/master/lib/timer.coffee#L79, which is not properly handled in the initialize function in punchclock.coffee.

Nevermind, I see you've already opened an issue there, so I'm closing this.


Avoid duplicate code of adding item to cart logic

Should avoid duplicate code for actions like adding item to cart. Especially in Explore and Shop screen

I could not find HOME Fragment on your project . Could you please elaborate?

@NiranjanNlc Hi. I updated the description. It is the shop fragment

Please asighn it to me

There you go @NiranjanNlc . Happy coding!

Hey , i found the duplication while assighning adpater in SHopFragment.
I have made a pull request .
Please have a look


Microsoft bought GitHub

Microsoft bought GitHub I wonder want might happen to this rdpwrap Project?

Not an issue


esbuild plugin support

🚀 Feature Proposal
Have plugin support for esbuild, in comparison to @loadable/babel-plugin.
Motivation
There are other more performant build tools rather than webpack & babel, this could be the opportunity for loadable components to support react ported to non-js solutions such as esbuild (golang).
Pitch
Basically since both esbuild supports jsx & tsx, and people are starting to adopt it into their react application.
This feature is especially aimed to SSR react app as replacement for @loadable/babel-plugin for esbuild.
Other than using for SSR, this plugin might not be necessary.

There are code splitting solutions which are bundler independent, but there is no one which works out of the box without at least babel.
Technically speaking babel can be replaced by eslint and required code change might be generated in a little more explicit way, not behind the scenes as usual.
That would propably work with esbuild as well.

There are code splitting solutions which are bundler independent, but there is no one which works out of the box without at least babel.
Technically speaking babel can be replaced by eslint and required code change might be generated in a little more explicit way, not behind the scenes as usual.
That would propably work with esbuild as well.

Hmm this is currently stated in esbuild plugins:

This API does not intend to cover all use cases. It's not possible to hook into every part of the bundling process. For example, it's not currently possible to modify the AST directly. This restriction exists to preserve the excellent performance characteristics of esbuild as well as to avoid exposing too much API surface which would be a maintenance burden and would prevent improvements that involve changing the AST.

I agree about your statement above though, I'll try to figure it out later without using babel somehow.
To conclude, apparently for now we can just setup a babel transform that runns only to the files that are using @loadable/components, during the build process. Although it defeats the meaning of using esbuild in the first place.

In 100k lines project, not counting roughly the same amount from node_modules, which uses code-splitting literally for everything, I have less than 10 files with dynamic imports.
applying babel transformation as a separate build step will still be very efficient from "esbuild goal" point of view. The question is how to maintain the correct dev experience.

No understanding of the road, sorry.
In the meantime, I will pursue eslint based solutions, but no promises.


2024-04-17 - CI failed in ruby-head(3.4.0dev d6debba817)

https://github.com/kachick/irb-power_assert/actions/runs/8715154811/job/23908035670
/home/runner/work/irb-power_assert/irb-power_assert/vendor/bundle/ruby/3.4.0+0/gems/warning-1.3.0/lib/warning.rb:260:in 'Warning::Processor#warn': /home/runner/.rubies/ruby-head/lib/ruby/3.4.0+0/reline/line_editor.rb:1747: warning: assigned but unused variable - history (RuntimeError)
	from /home/runner/.rubies/ruby-head/lib/ruby/3.4.0+0/bundled_gems.rb:7[8](https://github.com/kachick/irb-power_assert/actions/runs/8715154811/job/23908035670#step:4:9):in 'Kernel.require'
	from /home/runner/.rubies/ruby-head/lib/ruby/3.4.0+0/bundled_gems.rb:78:in 'block (2 levels) in Kernel#replace_require'
	from /home/runner/.rubies/ruby-head/lib/ruby/3.4.0+0/reline.rb:7:in '<top (required)>'
	from /home/runner/.rubies/ruby-head/lib/ruby/3.4.0+0/bundled_gems.rb:78:in 'Kernel.require'
	from /home/runner/.rubies/ruby-head/lib/ruby/3.4.0+0/bundled_gems.rb:78:in 'block (2 levels) in Kernel#replace_require'
	from /home/runner/.rubies/ruby-head/lib/ruby/3.4.0+0/irb.rb:[9](https://github.com/kachick/irb-power_assert/actions/runs/8715154811/job/23908035670#step:4:10):in '<top (required)>'
	from /home/runner/.rubies/ruby-head/lib/ruby/3.4.0+0/bundled_gems.rb:78:in 'Kernel.require'
	from /home/runner/.rubies/ruby-head/lib/ruby/3.4.0+0/bundled_gems.rb:78:in 'block (2 levels) in Kernel#replace_require'
	from /home/runner/work/irb-power_assert/irb-power_assert/lib/irb/power_assert.rb:5:in '<top (required)>'
	from /home/runner/work/irb-power_assert/irb-power_assert/lib/irb-power_assert.rb:5:in 'Kernel#require_relative'
	from /home/runner/work/irb-power_assert/irb-power_assert/lib/irb-power_assert.rb:5:in '<top (required)>'
	from /home/runner/work/irb-power_assert/irb-power_assert/test/helper.rb:26:in 'Kernel#require_relative'
	from /home/runner/work/irb-power_assert/irb-power_assert/test/helper.rb:26:in '<top (required)>'
	from /home/runner/work/irb-power_assert/irb-power_assert/test/test_irb_power_assert.rb:4:in 'Kernel#require_relative'
	from /home/runner/work/irb-power_assert/irb-power_assert/test/test_irb_power_assert.rb:4:in '<top (required)>'
	from /home/runner/.rubies/ruby-head/lib/ruby/3.4.0+0/bundled_gems.rb:78:in 'Kernel.require'
	from /home/runner/.rubies/ruby-head/lib/ruby/3.4.0+0/bundled_gems.rb:78:in 'block (2 levels) in Kernel#replace_require'
	from /home/runner/work/irb-power_assert/irb-power_assert/vendor/bundle/ruby/3.4.0+0/gems/rake-[13](https://github.com/kachick/irb-power_assert/actions/runs/8715154811/job/23908035670#step:4:14).2.1/lib/rake/rake_test_loader.rb:21:in 'block in <main>'
	from /home/runner/work/irb-power_assert/irb-power_assert/vendor/bundle/ruby/3.4.0+0/gems/rake-13.2.1/lib/rake/rake_test_loader.rb:6:in 'Array#select'
	from /home/runner/work/irb-power_assert/irb-power_assert/vendor/bundle/ruby/3.4.0+0/gems/rake-13.2.1/lib/rake/rake_test_loader.rb:6:in '<main>'
rake aborted!
Command failed with status (1)
/home/runner/work/irb-power_assert/irb-power_assert/vendor/bundle/ruby/3.4.0+0/gems/rake-13.2.1/exe/rake:27:in '<top (required)>'
/home/runner/.rubies/ruby-head/bin/bundle:25:in 'Kernel#load'
/home/runner/.rubies/ruby-head/bin/bundle:25:in '<main>'

https://github.com/ruby/reline/pull/684

Fixed in https://github.com/ruby/ruby/commit/a3b7a7bc21d91d384a915bcaa1fd49909061d78d
https://github.com/kachick/irb-power_assert/actions/runs/8747297379


Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

.github/workflows/main.yaml (github-actions)
package.json (npm)
requirements.txt (pip_requirements)

What to Expect
With your current configuration, Renovate will create 10 Pull Requests:

chore(dependencies): Update dependency jest to v29.6.1

Schedule: ["at any time"]
Branch name: dependency-update/jest-29.x-lockfile
Merge into: main
Upgrade jest to 29.6.1
Upgrade @types/jest to 29.5.3

chore(dependencies): Update dependency @types/node to v20.4.1

Schedule: ["at any time"]
Branch name: dependency-update/node-20.x-lockfile
Merge into: main
Upgrade @types/node to 20.4.1

chore(dependencies): Update dependency @typescript-eslint/eslint-plugin to v5.62.0

Schedule: ["at any time"]
Branch name: dependency-update/typescript-eslint-eslint-plugin-5.x-lockfile
Merge into: main
Upgrade @typescript-eslint/eslint-plugin to 5.62.0

chore(dependencies): Update dependency @typescript-eslint/parser to v5.62.0

Schedule: ["at any time"]
Branch name: dependency-update/typescript-eslint-parser-5.x-lockfile
Merge into: main
Upgrade @typescript-eslint/parser to 5.62.0

chore(dependencies): Update dependency winston to v3.10.0

Schedule: ["at any time"]
Branch name: dependency-update/winston-3.x-lockfile
Merge into: main
Upgrade winston to 3.10.0

chore(dependencies): Update dependency @typescript-eslint/eslint-plugin to v6

Schedule: ["at any time"]
Branch name: dependency-update/typescript-eslint-eslint-plugin-6.x
Merge into: main
Upgrade @typescript-eslint/eslint-plugin to ^6.0.0

chore(dependencies): Update dependency @typescript-eslint/parser to v6

Schedule: ["at any time"]
Branch name: dependency-update/typescript-eslint-parser-6.x
Merge into: main
Upgrade @typescript-eslint/parser to ^6.0.0

chore(dependencies): Update dependency chalk to v5

Schedule: ["at any time"]
Branch name: dependency-update/chalk-5.x
Merge into: main
Upgrade chalk to ^5.0.0

chore(dependencies): Update dependency eslint-plugin-prettier to v5

Schedule: ["at any time"]
Branch name: dependency-update/eslint-plugin-prettier-5.x
Merge into: main
Upgrade eslint-plugin-prettier to ^5.0.0

chore(dependencies): Update dependency prettier to v3

Schedule: ["at any time"]
Branch name: dependency-update/prettier-3.x
Merge into: main
Upgrade prettier to ^3.0.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


1.7

Whats the duplicate label for?

We’ve already gone through all the reviewing/approving process for these changes. I am simply merging branches again, this time into master.

aight


Allow configuring which UI columns to show from cli

I have a lot of template variables and want to always hide certain variables.

and in which order IMO

How do I use this feature? the documentation do not mention it. Thank you


Bug: Pre-release versions not considered matching

This test fails:
diff --git a/tests/regression.rs b/tests/regression.rs
index a47a777..041bd7c 100644
--- a/tests/regression.rs
+++ b/tests/regression.rs
@@ -28,3 +28,22 @@ fn test_regressions() {
         }
     }
 }
+
+// See https://github.com/RustSec/cargo-audit/issues/17
+#[test]
+fn test_suffix() {
+    let req = semver::VersionReq::parse(">= 0.10.2").unwrap();
+    let version = semver::Version::parse("0.12.0-pre.0").unwrap();
+
+    // Test parsing
+    assert_eq!(version.major, 0);
+    assert_eq!(version.minor, 12);
+    assert_eq!(version.patch, 0);
+    assert_eq!(version.pre, vec![
+        semver::Identifier::AlphaNumeric("pre".into()),
+        semver::Identifier::Numeric(0),
+    ]);
+
+    // Test matching
+    assert!(req.matches(&version));
+}

It matches the req if I remove the "-pre.0" suffix though.
This causes cargo-audit to report wrong vulnerabilities.
I assume this is a bug, and does not follow the spec, right?

Hm, I just found this comment in the code:
    // https://docs.npmjs.com/misc/semver#prerelease-tags
    fn pre_tag_is_compatible(&self, ver: &Version) -> bool {
        // If a version has a prerelease tag (for example, 1.2.3-alpha.3) then it will
        // only be
        // allowed to satisfy comparator sets if at least one comparator with the same
        // [major,
        // minor, patch] tuple also has a prerelease tag.
        !ver.is_prerelease() ||
            (self.major == ver.major && self.minor == Some(ver.minor) &&
                 self.patch == Some(ver.patch) && !self.pre.is_empty())
    }

That may be correct for version resolution, but not for a case like vulnerability checking.
Maybe the matches method should accept a flag indicating whether to allow prereleases or not?

Yes, it's not what we want for resolution, for sure. That being said, if it doesn't make it for resolution, how would it make it into a vulnerability? Wouldn't you want those checks to follow resolution?

No, it's the other way around. If a program has 0.12.0-pre.0 in its lockfile, then cargo-audit checks whether it matches >= 0.10.2 (which should return true since 0.12.0-pre.0 contains the fix).
I'm not sure how checking is done for libraries without a lockfile, maybe @tarcieri knows more.

cargo audit presently requires a lock file, as it relies on cargo to do the dependency resolution

News is basically, "I have no time to prioritize work on SemVer right now, I hope to get back to it soon, the lack of 1.0 is really bugging me, but I'm also only human."

That said, I am also still not 100% sure what this issue is saying; I haven't dug into the exact details, but not matching pre-releases is a feature, not a bug.

I understand about the workload, that's no problem. If it's clear what needs to be done I might even be able to come up with a pull request.
But regarding bug vs feature: Independently from package managers, why would a query for 0.12.0-pre.1 >= 0.10.2 be false? I understand that package managers won't want to offer pre-releases as candidates, but the logical statement is clearly true.

It sounds like the simplest option is to explicitly enumerate the prereleases that contain the fix.
I can also see how it's entirely possible there'd be prereleases which don't contain a security fix despite there being a fix in the final release.

@steveklabnik I think we're still not talking about the same thing :slightly_smiling_face:
The concrete use case I mentioned above:

My crate pins hyper to 0.12.0-pre.1
There was a patch that fixed this for versions >= 0.10.2 (this is how the vulnerability db registers fixes)
I am using 0.12.0-pre.1
I want to know if the version I'm using is inside the range that contains the fix

In this case, since the patch is in >= 0.10.2, the version I am using right now is not affected by the vulnerability.

You’re not expecting someone who puts >= 0.10.2 in their Cargo.toml to get the fix?

According to @tarcieri:

cargo audit presently requires a lock file, as it relies on cargo to do the dependency resolution

This means that we're always dealing with a pinned, concrete version from Cargo.lock, not with version ranges. For example, the question could be: "Is version 0.12.0-pre.1 (installed by the user) in the range >= 0.10.2 (patched range)". I'd argue, that for simple semver version checking, not in the context of a package manager, the answer should be "yes".

Okay, we're finally on the same page. Whew. Thanks :)
What do you think about

I can also see how it's entirely possible there'd be prereleases which don't contain a security fix despite there being a fix in the final release.

If there were a mode where prereleases were in lexographic order between the release versions, you could do e.g. patched_versions = [">= 0.11.0-pre.2"], which could signal all 0.11 releases are fixed and all prereleases except 0.11.0-pre.1

@steveklabnik do you think this is something semver should handle, or should we add special logic for this case in the rustsec vulnerability checker?

Here's the current logic we're using to select vulnerable crates, for what it's worth:
https://github.com/RustSec/rustsec-client/blob/13968fb1e198593b791af7c98bd9427a9dd65d40/src/db.rs#L111
        self.find_by_crate(crate_name)
            .iter()
            .filter(|advisory| {
                !advisory
                    .patched_versions
                    .iter()
                    .any(|req| req.matches(version))
            })
            .map(|a| *a)
            .collect()

@tarcieri I think rustsec should not be using VersionReq for this, it should simply store the Version when a fix was applied: the existing PartialOrd implementation on Version behaves the way you want.
Maybe you need something more complicated to handle regressions, eg. Vec<(Version, Option<Version>)> in case you want to handle regressions, but this is already more flexible than using VersionReq.

I ended up ripping out the vendored code from semver in this PR:
https://github.com/RustSec/rustsec-crate/issues/218
We've managed to upgrade to semver v0.10, but it'd be great to figure out a more minimal/upgrade-friendly solution than https://github.com/RustSec/rustsec-crate/pull/69, or ideally something implemented upstream in the semver crate which provides similar logic.
(Sidebar: in general I've found the way prereleases are handled by this crate somewhat confusing)

I still think VersionReq is the wrong type for this: it's a version requirement whereas what rustsec needs is a version range.
Of your examples, all can be represented by a Vec<Range<Version>>, and the existing PartialEq implementation on Version works fine:
let patched_versions: Vec<Range<Version>> = ...;

patched_versions.iter().any(|range| range.contains(locked_version))

I still think VersionReq is the wrong type for this: it's a version requirement whereas what rustsec needs is a version range.

patched_versions is a full-blown version requirement which can contain multiple comma-delimited version ranges. It's not just a range: it's a set of ranges, any of which satisfy the "patched" requirement.
As it were, it seems some of the requirements we have no longer parse with semver v0.11:
Error { kind: Parse, msg: "the given version requirement is invalid for key `versions.patched` at line 17 column 12" }

patched_versions is a full-blown version requirement which can contain multiple comma-delimited version ranges. It's not just a range: it's a set of ranges, any of which satisfy the "patched" requirement.

Right, that's why I modelled it as a Vec<Range<Version>>. My point was that it's semantically different from a version requirement. You just happen to have borrowed the same syntax for defining them, since they are quite similar.

Can you state concretely what you think the difference is?

Sure: version requirements are about compatibility and stability of the API. I would expect 1.0.0-pre to already have the majority of breaking changes that are going to be part of the 1.0 release, and therefore it makes more sense to group pre-releases with the releases that follow them (so that 0.9.0 and 1.0.0-pre can coexist, but 1.0.0 and 1.0.0-pre cannot coexist).
A version range is about the development timeline. It makes perfect sense to say that versions >0.1.2, <0.1.8 are patched, but that would not make a whole lot of sense as a version requirement, since 0.1.9 is supposed to be compatible with all patch versions before it.

A major notable drawback of a 1.0.0-pre prerelease matching 1.0.0 is it means someone using a 1.0.0-pre may experience a breakage if a 1.0.0 release includes any semver breaking changes. Personally I would consider prereleases the last time to make breaking changes prior to a final release.

Sure: version requirements are about compatibility and stability of the API.

Note that we also leverage version requirements as part of cargo audit fix. That command quite literally needs to select a VersionReq that goes into Cargo.toml.
We can consider implementing our own version requirement type which differs from the one in this crate (again, the previous one was largely copy paste from semver v0.9.0), but IMO we are very much looking for a "version requirement" which satisfies a set of constraints. Semantically "version requirement" seems correct to me, even if the precise semantics of what RustSec needs and what SemVer ordinarily needs differ.

Node.js's security working group also use VersionReq as vulnerable_versions and vulnerable_versions in their data files. For example: https://github.com/nodejs/security-wg/blob/master/vuln/npm/104.json

I just noticed something else impacted by this issue: https://deps.rs thinks prerelease dependencies are out-of-date

I'll go ahead and close this because I believe this matching behavior is intentional as described by section 5 of https://github.com/semver/semver/blob/efcff2c838c9945f79bfd21c1df0073271bcc29c/ranges.md.
As of 1.0.0 though, the VersionReq's operators/comparators are publicly exposed and so it's possible to implement "nontraditional" matching logic downstream. https://docs.rs/semver/1.0.0-rc.1/semver/struct.VersionReq.html

For reasons unrelated to this issue, we'll be migrating away from VersionReqs, so this no longer concerns me, but honestly this seems like a "bug" in the spec. I agree that this behavior does appear to match the spec as written, however.
The rationale for the criteria in the spec all center around something which does make sense: making sure that prereleases don't match as a sort of boundary condition in a "less than" expression. As it were, I opened a separate issue related to that: #236.
But this leads to this rather confusing behavior for anything other than that particular edge case...
For the match expression >= 2.0.0, here's the output of VersionReq::matches for the following versions:

2.0.0-rc.0: false
2.0.0: true
3.0.0-rc.0: false
3.0.0: true
4.0.0-rc.0: false
4.0.0: true

Of the prereleases returning false, I'd argue only the first one makes sense. I don't think it makes sense for prereleases to cease to match after a major version bump, but again, I'd agree this is the "correct" behavior per the spec as written.

Locking because this is not the right/productive place to rant about the spec, especially not about deliberate and sensible features of the spec.


Cleanup google share model

All down to base group

This is done
@charise @Billflorio all scripts since github should now live here: The link is publicly viewable, but we have to grant access as needed to edit scripts:
https://drive.google.com/drive/folders/1t1tC_EtsjUdLMO2YE-O4w_-oV8-xsbeh?usp=sharing
all the old script structure kept in sync by me w/ the process are in the archive folder and mostly unviewable/uneditable, except docs owned by original writer. We should maybe copy those logged in as NPSP Vid, so that is the final owner, just in case an original writer/owner deletes (or goes rogue ;p)

The template model maybe isn't enough-- can we automate this some way via a slack WF tied to a sheet or just straight to git

add their user to the git repo?
assign them to a sprint subfolder in the main docs flder or the main docs folder


urlscan: Feature - Add get screenshot action

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[x] Testing of all the changes has been performed (for bug fixes / features)
[x] The manual_readme_content.md has been reviewed and added / updated if needed (for bug fixes / features)
[x] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[x] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[ ] Verify all checks are passing.
[x] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[x] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

[ ] New App
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Security Considerations (REQUIRED)

[ ] If you are exposing any endpoints using a REST handler,
please document them in the manual_readme_content.md.
[x] If this is a new connector or you are adding new actions

[x] Please document in the manual_readme_content.md all methods (eg, OAuth) used to authenticate
with the service that the connector is integrating with.
[x] If any actions are unable to run on SOAR Cloud, please document this in the manual_readme_content.md.

[ ] Are you introducing any new cryptography modules? If yes, please elaborate their purpose:
[x] Are you are accessing the file system? If yes, please verify that you are only accessing paths returned through
the Vault API.
[ ] Are you are marking code to be ignored by Semgrep with nosemgrep?
If yes, please provide justification in an additional comment next to the ignored code.

Release Notes (REQUIRED)

adding get screenshot action which adds screenshot of website to files given uuid

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

Hello @jaimepark1023,
Is there any specific use case for creating a separate get screenshot action?
In case we create a new action, we first need to obtain a UUID from the detonate url action and then pass it to get screenshot action.
Rather than creating a new action we can incorporate the same functionality in the existing detonate url  action. That will just require a new checkbox parameter to save the screenshot in the vault.

What you suggest does seem easier, but wouldn't adding get screenshot to detonate url be making 2 api calls for a single action?
Would it be possible to add the checkbox parameter but still keep the actions separate?

What you suggest does seem easier, but wouldn't adding get screenshot to detonate url be making 2 api calls for a single action?
Would it be possible to add the checkbox parameter but still keep the actions separate?

I agree that just an optional "save to vault" checkbox for detonate url makes more sense. The additional construction step for getting the UUID and then executing the next action is additional complexity not necessarily needed. An additional API call within the action should not be an issue; we have many actions in different apps that perform a save to the vault after execution as a norm.

What you suggest does seem easier, but wouldn't adding get screenshot to detonate url be making 2 api calls for a single action?
Would it be possible to add the checkbox parameter but still keep the actions separate?

I agree that just an optional "save to vault" checkbox for detonate url makes more sense. The additional construction step for getting the UUID and then executing the next action is additional complexity not necessarily needed. An additional API call within the action should not be an issue; we have many actions in different apps that perform a save to the vault after execution as a norm.

Just so this doesn't sit any longer, is this something you are going to implement or you would like us to implement?

What you suggest does seem easier, but wouldn't adding get screenshot to detonate url be making 2 api calls for a single action?
Would it be possible to add the checkbox parameter but still keep the actions separate?

I agree that just an optional "save to vault" checkbox for detonate url makes more sense. The additional construction step for getting the UUID and then executing the next action is additional complexity not necessarily needed. An additional API call within the action should not be an issue; we have many actions in different apps that perform a save to the vault after execution as a norm.

Just so this doesn't sit any longer, is this something you are going to implement or you would like us to implement?

Thanks for your comment. May I ask if you are connected to the original MR submitter? If so, yes if you and the original creator could make the necessary updates, and we'd be glad to help if needed. If you’re not connected to the original poster and there’s no update from them, we will to take on the duties ourselves.

I'm the original submitter. I'll work on the updates.


Incompatible with MoreCulling

When using https://github.com/fxmorin/moreculling the items in invisible item frames are still offset

I'll try and have a look into if I can fix this, once I have time. Thanks for the report!

Ok, after way too long I've finally had a chance to look at the code and unfortunately More culling just overwrites the original method as a whole. To my understanding that means I cannot make our mods compatible with one another unless the author changes their code.

you can disable more culling's item frame changes in their config to fix


GPU usage increasing continually while profile_serving benchmark

with A GPU-card, concurrency from 1 to 16.
model: internlm-7b
infer mode: turbo.
branch: master

fp16 weight requires 16G, and each concurrency requires 1GB to save kv_cache. As the concurrency increases, a total of 30+ GB is normal.
Try int8 quantization to save memory.

https://github.com/InternLM/lmdeploy/blob/main/docs/en/quantization.md


Prefer jacoco over cobertura

Coverage decreased (-7.8%) to 69.989% when pulling 9151e0700b55f871817b74b895ebea9603b64ac7 on jacoco into f3b69c5b9181847724f2aba4999702a3734a430d on master.

Okay, excludes are not yet working correctly.