Added new server option ALLOW_UNESCAPED_CHARACTERS_IN_URL

related issue: https://github.com/networknt/light-4j/issues/412
Added new server option allowUnescapedCharactersInUrl to support new feature of undertow. It can be configured just like other server options (ioThread, workerThread...). The default value of it is true. The documentation will be updated later.

I think we should default this to false right? At least that's what undertow does..

@NicholasAzar Hey! The old version of light-4j supports non-ascii character in Url. This feature disappears due to the update of undertow. Perhaps for backward compatibility, we need to keep the same performance as the previous version, so the default value of this flag maybe needs to be true. If we use the default value of undertow, it may cause some incompatibility, although I don't think anyone will use some rare symbols in the URL. for example: Ã¥... What do you think?

For the 1.6.* branch, i would keep it as false to match undertow. If we want to change this to match how it was working previously, maybe we should just do it for people using the 1.5.* branch?

@NicholasAzar I agree! Will change it 👍

Codecov Report

Merging #462 into master will increase coverage by 0.07%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #462      +/-   ##
============================================
+ Coverage     49.85%   49.92%   +0.07%
- Complexity     1761     1768       +7
============================================
  Files           251      251
  Lines         10854    10862       +8
  Branches       1548     1549       +1
============================================
+ Hits           5411     5423      +12
+ Misses         4798     4797       -1
+ Partials        645      642       -3

Impacted Files
Coverage Δ
Complexity Δ

...ver/src/main/java/com/networknt/server/Server.java
28.96% <100%> (+0.24%)
16 <0> (ø)
:arrow_down:

...c/main/java/com/networknt/server/ServerOption.java
93.75% <100%> (+0.56%)
26 <0> (+2)
:arrow_up:

...c/main/java/com/networknt/server/ServerConfig.java
71.76% <100%> (+1.03%)
37 <2> (+2)
:arrow_up:

...n/java/com/networknt/client/oauth/OauthHelper.java
41.13% <0%> (+0.66%)
25% <0%> (+2%)
:arrow_up:

.../src/main/java/com/networknt/utility/HashUtil.java
63.33% <0%> (+3.33%)
11% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

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


suite model potentially wrong

Tests should not present a dependency to a suite.
Suite model is potentially wrong. A suite should look like:
.....
scenario:
given: >
....
then: >
....
when: >
....
tests:
   - ref: "name"
      version: "x.x"
      pottential overriding fields (must respect test model)

Please change the entity parsing logic to refer tests inside suites not the other way around

Fixed in #31


Podspec

I used your framework and it's app target as Example project in the pull-request CocoaPods/CocoaPods#2835, which will bring Swift support to CocoaPods. See here. I hope this okay for you. I'd love to see it published in the master spec repo.

@kylef Sounds good. Thanks, @mrackwitz for the PR. I'm really happy to do what I can to help drive CocoaPods adoption for Swift. This is going to be a huge improvement to how folks get started with Alamofire; I can't thank y'all enough for all of your hard work to make this possible.

The merged podspec seems out of date, particularly,
s.version = '1.1.0' -> '1.1.3'
s.source = { :git => 'https://github.com/Alamofire/Alamofire.git', :tag => '1.1.0' } -> '1.1.3'
s.ios.deployment_target = '8.0' -> '7.0'
Thanks in advance for the update above.

Hum... Something is weird.
when I add Alamofire my Bridging header breaks. Older dependencies which where Objective-C bridged to Swift can't be imported anymore.
I'm using 0.36.0.beta.1

@mattt do you have a timeline on submitting the spec to trunk?

@thedamfr after upgrading to Cocoapods 0.36.0.beta.1, adding pod 'Alamofire', '~> 1.1.3' to my existing pod file that contains:
target 'MyApp', :exclusive => true do
  pod 'AFNetworking', '~> 2.5'
  pod 'ProtocolBuffers', '1.9.3'
  pod 'KSDeferred', '~> 0.2'
  pod 'Rollbar', '~> 0.1.2'
  pod 'Alamofire', '~> 1.1.3'
end

I receive the error failed to import bridging header and an error of 'AFNetworking.h' file not found' on the line #import "AFNetworking.h" in the bridging header.

@JustinDSN try changing that to either @import AFNetworking;" or #import <AFNetworking/AFNetworking.h>`.

@JustinDSN just remove the bridging header.
and user import AFNetworking in you swift file.
It's the way it works.


Two depth maps output?

Looks like the newest version is producing two identical depth maps. Is the second one necessary?

Investigating further....one is a jpeg and the other a png file. Both are duplicates.

There is a setting in WebUI that automatically creates downscaled and compressed jpg-s from every png that is saved. Sometimes this is a useful feature, but not in this case. It can be disabled thankfully.


Many Unable to parse log line: show each load (Windows .exe version)

Describe the bug
In the cmd window I'm getting many Unable to parse log line:
2022.11.04 19:35:44 - [console] - Unable to parse log line:
0       4/11/2022 7:33:35.017 PM        FrontDoor               AI: [Objects] person:90% [90,228 429,570] 261ms
2022.11.04 19:36:14 - [console] - Unable to parse log line:
0       4/11/2022 7:34:31.104 PM        NVR-SIDE2-MASK          AI: Alert cancelled [nothing found] 371ms
2022.11.04 19:36:14 - [console] - Unable to parse log line:

Attached is

Todays BI Log
Output from v1.0.4 windows .exe with the errors showing

blueiris_exporter-amd64 v1.0.4 cmd log.txt
blue_iris_log.txt
To Reproduce
Steps to reproduce the behavior:

With the attached BI Log run blueiris_exporter
Wait a few seconds after load, cmd window will then show all the Unable to parse log line:  lines

Expected behavior
All log items in the BI log can be parsed without error.
Screenshots

Desktop:

OS: Window 10
Blue Iris Version: Blue Iris <IP_ADDRESS> x64 (25/10/2022)
blueiris_exporter Version 1.0.4 windows cmd

Additional context
N/A

Thank you @BananaHammock743! Found another small issue. Will push up a fix for it now!

Okay, this should fix it! Sorry about that!
https://github.com/wymangr/blueiris_exporter/releases/tag/v1.0.5

Nice. I now only get 3 warnings.
C:\Users\Admin\Downloads>blueiris_exporter-amd64.exe
2022.11.05 08:38:07 - [info] - starting Blue Iris Exporter with the following:
                Log Path: C:\BlueIris\log\
                Metric Path: /metrics
                Port: :2112
2022.11.05 08:38:14 - [console] - Unable to parse log line:
1       4/11/2022 6:05:06.255 AM        NVR-SIDE2               AI: not responding
2022.11.05 08:38:14 - [console] - Unable to parse log line:
1       4/11/2022 8:02:19.281 AM        Gate                    AI: not responding
2022.11.05 08:38:14 - [console] - Unable to parse log line:
1       4/11/2022 8:02:20.641 AM        GATE-MASK               AI: not responding

Let me know if the log file would be helpful and I can post.

@BananaHammock743 awesome, thanks for the update! Luckily, I'm not doing anything with those, so (other then filling up the terminal), you aren't loosing any metrics. Unfortunately I couldn't find a list of every possible log entry that Blue Iris will log about 😞.
I will push up an update to ignore that one as well and if you run into any more, please let me know!

@BananaHammock743 I have a new release that should fix your warnings as well as add a couple more metrics.
https://github.com/wymangr/blueiris_exporter/releases/tag/v1.1.0

Going to close this out. @BananaHammock743 Feel free to open it back up or create another issue if you have any other problems.


Increase PIL limit for images size

See https://huggingface.co/datasets/datadrivenscience/ship-detection/discussions/4#6489674ff4d5239fac762f2a
PIL has a limit for the image size (178,956,970 pixels). When the datasets library tries to get the value for the big image, it raises DecompressionBombError
https://github.com/huggingface/datasets-server/blob/7b4b78f04473d8f00e7c2226381982a9a84ab48c/services/worker/src/worker/utils.py#L341
I'm not sure if we could handle this better (ie: ignoring the error just for these images, replacing with a placeholder?)

[ ] increase the limit
[ ] catch the exception and return a proper advice for the user

wdyt @huggingface/datasets?

I think we can just increase the limit. The idea is just not to OOM

Duplicate of #1192 (but we will keep this one)

Copying references found by @albertvillanova
https://pillow.readthedocs.io/en/stable/reference/Image.html#PIL.Image.open

If the number of pixels is greater than twice MAX_IMAGE_PIXELS, then a DecompressionBombError will be raised instead.

This threshold can be changed by setting MAX_IMAGE_PIXELS. It can be disabled by setting Image.MAX_IMAGE_PIXELS = None.

The default value for MAX_IMAGE_PIXELS is 0.25GB, which allows opening images up to 0.5GB (twice the value)


chore(webpack): add flow to webpack

Description

Add the flow plugin to webpack config so that we can get flow errors in our terminals.
https://github.com/happylynx/flow-webpack-plugin
https://www.npmjs.com/package/flow-webpack-plugin
Motivation and context

I'm using Emacs for development which doesn't have it's own special flow server like Atom does. I think this makes our DX more inclusive.
How to test

cd mineral-ui && npm start
make a flow error
see the errors in the terminal

Types of changes

Other (provide details below)

this is a chore probably
Checklist

[x] Renders and functions properly in all supported browsers - [n/a]
[x] Automated tests written and passing - [n/a]
[x] Accessibility and inclusivity considered - [n/a]
[x] Rendering performance (initial load time & 60fps) and perceived performance considered - [n/a]
[x] Documentation created or updated - [n/a]
[x] Tested in sandbox if new component or breaking change - [n/a]

How does this PR make you feel?

I'm closing this issue as Mike is looking for a more localized solution that does not affect build times.


Added link to latest PnP webcast.

Trivial change but up-to-date webcast needs a link ;-)

Hi @SPDoctor, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Good catch. Thx Bill.


kernel/test/metadata_test is skipped when $use_sdk

This status line was added in 7890aeef81a070648aa7ff0250f751bc1f4df693 / ac2cd687089d8d41ae6898dc7db21c0a97051716 and incorrectly categorized as front-end issue #28629.

This test seems to pass in this configuration.  I'll re-enable it.


Create a Rust unity client

Is your feature request related to a problem? Please describe.
Unity catalog is useful for a multitude of engines and application in various languages. It would be great to provide client implementations accessible to as many environments as possible.
Describe the solution you would like
A rust client is a great starting point for bindings into many languages due to its great "embeddability". As such, creating a rust unity client seems like a good idea to spread unity across ecosystems.
Additional context
cc: @dennyglee @abrassel

@roeap - it's a wonderful idea, what do you think about the unitycatalog-rs project?


.babelrc files in src/

Problem
Placing a .babelrc file in the same directory as source files does not respect the nested configuration.
References

Babel will look for a .babelrc in the current directory of the file being transpiled. If one does not exist, it will travel up the directory tree until it finds either a .babelrc, or a package.json with a "babel": {} hash within.

https://babeljs.io/docs/usage/babelrc/#lookup-behavior

Before Babel will actually compile your code, it needs to be configured. Create a new file, src/.babelrc:
{
  "presets": ["es2015-rollup"]
}

http://rollupjs.org/guide/#using-rollup-with-babel
Thoughts
I suspect that the source files are being copied to a temporary location, before babel is invoked, without copying the .babelrc file(s).

The readme for this repo and the "Using Rollup with Babel" section of the rollup guide might need to be updated. They seem to reference old versions of the libraries first with notes and caveats for the latest versions. It would be nice if the documentation for the current version was the default, and support for older versions was secondary.

Can you provide a repro? It's using Babel's builtin lookup behaviour, so should work correctly (and it's worked correctly for me in the past).

They seem to reference old versions of the libraries first with notes and caveats for the latest versions.

Can you show us where? Thanks

After building a minimal repro I realized the issue was that /src had a .babelrc file, but /lib did not, so nothing in /lib was being transpiled, just rolled up. The issue seems to be caused by my lack of understanding of the order of operations. Sorry for the confusion.

I think my documentation gripe was rooted in thinking the "Configuring Babel" preamble implied the es2015-rollup preset was no longer supported. It sounds like I can go back to using es2015-rollup instead of manually configuring .babelrc.
Again, sorry for the confusion.


guide: revisit Checkpoints guide(s?)

Per task in https://github.com/iterative/dvc.org/issues/2548

Trying to make it broader (more general) yet shorter, and cover all the usage details (extract from cmd ref) in a structured way.

[x] General text/story review - https://github.com/iterative/dvc.org/pull/2910
[x] Add info from https://github.com/iterative/dvc.org/pull/2672 to the checkpoints page.
[ ] Incorporate/merge material from https://github.com/iterative/dvc.org/pull/2753/files
[ ] Should close https://github.com/iterative/dvc.org/issues/2432
[ ] Should close https://github.com/iterative/dvc.org/issues/2568
[x] Remove deep details from https://dvc.org/doc/command-reference/exp/run#checkpoints
[ ] Sharing checkpoints with dvc exp push (here or in the Sharing Exps guide)
(See https://github.com/iterative/dvc.org/issues/2769#issuecomment-912478244)

Decide on these:

[ ] Keep a separate guide but have some basics in a Checkpoints section in each Exps guide (Running, Sharing, etc.)
[ ] Maybe https://github.com/iterative/dvc.org/issues/2742
[ ] Maybe https://github.com/iterative/dvc.org/issues/2568
[ ] Maybe https://github.com/iterative/dvc.org/issues/2509
[ ] Maybe https://github.com/iterative/dvc.org/issues/2741

It might be worth adding a mention about how to properly Share Checkpoints with dvc exp push.
The current content finishes without sharing the checkpoints and the last section Adding checkpoints to git will squash the checkpoint commits making them not usable later.
We kind of already have the Sharing Experiments guide but it doesn't mention Checkpoints at all.

I think that deserves a dedicated issue @daavoo .

As new Checkpoint specific issues appear (https://github.com/iterative/dvc.org/issues/2797) I think it would make more sense to have a dedicated Checkpoints section on each individual Experiment guide (Running, Sharing, etc.), like https://dvc.org/doc/user-guide/experiment-management/running-experiments#checkpoint-experiments .

I think that's a good idea.

deserves a dedicated issue

Oops I saw that issue and collapsed back into here 😅 just noticed your comment.
Should be OK as a task here? We have so many issues already... Hard to keep track.

more sense to have a dedicated Checkpoints section on each individual Experiment guide (Running, Sharing, etc.)

Would probably need both its own guide and a small Checkpoints section in each Exps guide.

Should we merge this issue with https://github.com/iterative/dvc.org/issues/2432?

@daavoo want to repurpose this to include checkpoint charing info for now? Per https://github.com/iterative/dvc.org/issues/2769#issuecomment-912478244
Otherwise this looks stale (per https://github.com/iterative/dvc.org/issues/2432#issuecomment-1171675345 and https://github.com/iterative/dvc.org/issues/2568#issuecomment-1171673641) and could be closed.


support C++17 compilers

The codebase was using a language construct (designated initializers) from C99 that is not currently in any C++ standard, but is proposed for C++20. The main point of this change is to get the new C++ implementation to be compatible with VS2017 (and clang 3.x) so Yoga can continue to be consumed on Windows/Xamarin platforms.

This makes things a lot harder to read, especially the default values structs. Can we change the way to do default values at the same time to make this a non-issue? I'm thinking of something like using normal C++ constructors for setting default values.

@priteshrnandgaonkar - is that something you'd be able to fix? It's a MAJOR issue that we can't get the latest builds of Yoga for react-native-windows.

Or, @priteshrnandgaonkar, what if we just commented out the designated initializer part, e.g.:
     YGValue value = {
         .value = paramName,
         .unit = YGFloatIsUndefined(paramName) ? YGUnitUndefined : YGUnitPoint,
     };

To:
     YGValue value = {
         /* .value = */ paramName,
         /* .unit = */ YGFloatIsUndefined(paramName) ? YGUnitUndefined : YGUnitPoint,
     };

@woehrl01 - if it's possible to have macros within macros, then not a problem. I'm going to put up a PR for the comments for now though.

I feel having a macro would be a great soultion.

@priteshrnandgaonkar - there is no trivial change that would allow us to switch to a macro because of how deeply nested the designated initializers are. The comment approach provides readability and is the minimum viable approach to get us compiling for Windows. I'd really like to get that merged first, and then follow up with the macro approach.

We can use constructors instead of Macros and commenting out the code. @rozele @woehrl01

MSVC errors out with a bunch of problems on this code, which I think is in line with this issue.
static YGConfig gYGConfigDefaults = {
    .experimentalFeatures =
        {
            [YGExperimentalFeatureWebFlexBasis] = false,
        },
    .useWebDefaults = false,
    .useLegacyStretchBehaviour = false,
    .shouldDiffLayoutWithoutLegacyStretchBehaviour = false,
    .pointScaleFactor = 1.0f,
#ifdef ANDROID
    .logger = &YGAndroidLog,
#else
    .logger = &YGDefaultLog,
#endif
    .cloneNodeCallback = nullptr,
    .context = nullptr,
};


Had to call SqlitePCL.Batteries.Init() to Fix missing e_sqlite3 error.  Am I doing this correctly?

I was getting an intermittent error when I run my application saying "Unable to load DLL 'e_sqlite3' followed by module not found.  I looked all over the place and couldn't find a solution that sounded like it applied to my environment.
I noticed in the description of Nuget pkg "SQLitePCLRaw.bundle_green", it says "Call SQLitePCL.Batteries.Init()"
So I added that to the entry point of my application and the problem seems to have been fixed.  But that doesn't seem correct to me.  Sqlite-net should already be making this same call shouldn't it?
Could be related to this issue:
https://github.com/praeclarum/sqlite-net/issues/643
EDIT: Crap.. Because the issue is intermittent, it had only "seemed" to fix the issue.  Now I'm getting the load DLL error on the batteries.Init() line I added. LOL
Why could this be intermittent anyway?  Sometimes my app runs fine and sometimes it halts with this error.
NOTE: I should add a lot of people are citing this problem on Windows 8.  I'm on Windows 10 with VS 2017. My project is .NET Framework 4.7.2

I haven't seen this before, at least not an intermittent version of this.
Who are "a lot of people"? Do you have evidence that others are seeing intermittent failures of this kind?
Diagnostic questions:
What version of SQLitePCL.raw are you using?
Does the behavior change if you clean your tree completely and do a full rebuild?
Is there any chance another e_sqlite3.dll exists somewhere?
The you linked is a unit test project.  Is yours?

Who are "a lot of people"? Do you have evidence that others are seeing intermittent failures of this kind?

I wasn't clear. I just meant that when I searched for the ""Unable to load DLL 'e_sqlite3'", I find a lot of issues on github and stackoverflow where people discuss that general error on Windows 8.1 or android or iOS.  I'm not targetting any of those.  I just have a WPF application on Windows 10.

What version of SQLitePCL.raw are you using?

v1.1.11 according to Nuget package manager.

Is there any chance another e_sqlite3.dll exists somewhere?

Not sure how to answer this question simply.  See further down in this post. I apparently broke things even worse by trying to uninstall the nuget packages an reinstall them.

The you linked is a unit test project. Is yours?

Negative.  Its just a issue I read when I was desperately seeking answers before posting for help.
New Status (Condition: Worse )

I uninstalled all of the SqlitePCLRaw references and sqlite-net-pcl itself.
I reinstalled sqlite-net-pcl and let it bring in all the dependencies
I did a build and got this error:
Found conflicts between different versions of "SQLitePCLRaw.batteries_v2" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed. C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets	2110

That came along with similar errors about "SQLitePCLRaw.Core" and "SQLitePCLRaw.provider.e_sqlite3"

I uninstalled all of the nuget packages again
I searched the entire project folder for any files containing "sqlite".  I deleted every one of them, except for one that appeared to be Visual Studio's own file for managing projects (am I mistaken that such a file exists?). I didn't want to break VS so I left that one alone.
I reinstalled sqlite-net-pcl with nuget and let it bring in dependencies.
I did a build and got the same errors as above.

I've never had to deal with conflicts like this before.  Deleting all of the files in the project folder was my best guess at a solution.  Do I need to delete old references in some config files or something?

This looks like you've got leftovers somewhere.
You're on .NET Framework with WPF, so I assume your project might be using packages.config.  So for example, when you uninstall all those nuget packages, I wonder if all trace of them is gone from csproj and packages.config.  Perhaps take a look at those files in a text editor and see if anything looks weird.

Ok.  I used Sublime Find-in-Files.  Sure enough, there were various sqlite references in App.config of some of my projects for my solution.  After removing all that and using Nuget to add sqllite-net-pcl again, the errors about "Conflicting versions" are gone.  yay \o/
Unfortunately, I'm back to my original problem with this error:
Exception thrown: 'System.DllNotFoundException' in SQLitePCLRaw.provider.e_sqlite3.dll
Unable to load DLL 'e_sqlite3': The specified module could not be found. (Exception from HRESULT: 0x8007007E)

But now that I've relaxed and got a better handle on things, I think I may know what problem pertains to.  I will have to explain a lot more detail about my overall environment/solutions.
I have 2 solutions.
Solution 1) Contains a project called SqliteNetHelper.DLL which is my own wrapper for sqlite-net. I also have a SqliteNetHelper.Test project that executes tests on a dummy database file using sqlitenethelper.dll.  This solution is working perfectly.   I installed the Nuget package for sqlite-net-pcl for those two projects in this solution and never had any issues.
Solution 2) This is my WPF application.  It contains four projects.  Three projects are DLLs and one is the WPF app.  I'm not actually using sqlite in the WPF app itself.  I've abstracted all my logic into the DLLs.  Each DLL has its own internal database and corresponding disk file.  As such, each DLL needs a reference to my own SqliteNetHelper.DLL and also the Nuget Packages for Sqlite-net-pcl.
Since Solution 1) Unit Tests work fine, but Solution 2) throws this sqlite3.dll error, I've begun wondering if somehow the conflict is due to the fact that I've got dependencies on my own wrapper DLL which also depends on sqlite-net-pcl.  I verified that all Nuget package installations are using the same version and files through the Visual Studio Nuget GUI.  I don't see any problems here.
  Unfortunately, I can't easily remove it and stick to the dependencies on Sqlite-net-PCL, because the wrapper is what my actual code uses.
I think I'm going to try this:

Create brand new solution with a DLL and a WPF app
Install Nuget sqlite-net-pcl in the DLL.  Call some methods for sqlite-net
reference the DLL into WPF and call an entry point
Run it and see if it works
if it works, then tie in my own wrapper into the dll and see if that causes things to break.

Not sure what else to do.  Any other ideas?
If it proves to be the case that somehow my wrapper dll's dependency on sqlite-net is somehow conflicting with my primary dlls depending on sqlite-net, I'll probably have to just abandon sqlite-net and roll my own ORM.  I've done that in the past for full server relational databases with great success.  I picked sqlite-net because I thought it would get me off the ground with sqlite quicker (never having used sqlite), but now I'm beginning to wonder if there are too many moving parts.

I don't think you should have to abandon sqlite-net and write your own ORM just because of a quirky tooling problem.  This can get worked out.
My current guess is that the problem is caused by having two solutions.  When the stuff in solution 2 references SqliteNetHelper.dll, exactly HOW does it do that?  Is the SqliteNetHelper project a member of both solutions?  Does building solution 2 cause a build of SqliteNetHelper?
I wonder what would happen if you have one solution instead of two.
Also, do the DLLs in solution 2 reference sqlite-net stuff directly, or do they only call stuff in SqliteNetHelper.  In other words, why do they need references to the sqlite-net package?  Oh, wait.  As I said earlier, you're probably still using packages.config (instead of PackageReference in csproj), so transitive dependencies work the old way.
Another thing to consider:
In some scenarios, it is easier to structure the sqlite-net and SQLitePCL.raw references differently, along these lines:
In library projects, instead of using the sqlite-net-pcl package, use the one called sqlite-net-base.  Same maintainer, same code.  The only difference is that sqlite-net-base takes its dependency on the core SQLitePCLRaw.core library instead of on the SQLitePCLRaw.bundle_green.
In the top-level (executable, app, etc) projects, add a dependency on SQLitePCLRaw.bundle_green, and add a call to SQLitePCL.Batteries.Init() in the app startup.
The thing about dealing with SQLite in the .NET world is that SQLite is a native library written in C.  And the build issues around such things can be complicated.  But a library project doesn't need to know about any of that, so it only needs to depend on the SQLitePCLRaw.core library.  It is only when building an executable for a given platform that the dependencies on the native SQLite library need to come into play.

My current guess is that the problem is caused by having two solutions. When the stuff in solution 2 references SqliteNetHelper.dll, exactly HOW does it do that? Is the SqliteNetHelper project a member of both solutions? Does building solution 2 cause a build of SqliteNetHelper?

Because I was trying to keep my primary solution (2) lightweight and sanitized, I've been copying the release build of the SqliteNetHelper.DLL into my primary solution directory and adding it as a direct reference to any other DLLs that need it.  The project from solution 1 isn't referenced at all.  It's just a plain-old copy-and-paste DLL setup.

Also, do the DLLs in solution 2 reference sqlite-net stuff directly, or do they only call stuff in SqliteNetHelper. In other words, why do they need references to the sqlite-net package? Oh, wait. As I said earlier, you're probably still using packages.config (instead of PackageReference in csproj), so transitive dependencies work the old way.

Not familiar with any of these concepts.  I didn't know about an "old way" and a "new way".  But as far as method calls, my DLLs only call methods in SqliteNetHelper.  They don't directly call anything in Sqlite-Net.  If its possible to completely get rid of the sqlite-net and sqlitePCLRaw references, that might fix the problems.  Does this "old way" and "new way" difference afford me a way to do only reference sqlitenethelper and nothing else?

In some scenarios, it is easier to structure the sqlite-net and SQLitePCL.raw references differently, along these lines:

Your explanation is thorough and tremendously helpful.  I didn't know about the EXE vs DLL reference variation when using a native library.  I'll try the setup you described using sqlite-net-base and only add sqlitePCLraw.bundle_green to the exe app.

Oh dear.  :-(
The 0.9.x versions of those packages (the ones with names of the form SQLitePCL.*) are all deprecated.
Only use the ones with >1.x version numbers, with names of the form SQLitePCLRaw.*
Er, sorry for the confusion.  Maybe it's time to remove all those old packages from nuget.  :-(

HALLELUAH! \O/
I uninstalled that package and found the correct one and installed it.  And now everything works!!!!
By the way, per your comment about library method references, I checked and realized that the Wrapper wasn't 100% hiding sqlite-net because one method was being allowed to return a sqlite-net specific object.  I abstracted this away, and was able to completely remove all nuget packages having anything to do with sqlite from my libraries.  All I have to do is reference my own sqlitenetwrapper in my libraries now.  I'm such a newbie for not having set this up right. :)
Your suggestion of only referencing bundle_green in the EXE works perfectly.  Cleaned up all my references beautifully.  Unless you think it's counter-recommended, I'd like to write a wiki page devoted to common configuration scenarios and explain the difference between sqlite-net-pcl and sqlite-net-base.  It's the least I can do to try to give back... and hopefully help someone else in the future.
Thank you so much for your help!  Now I can finally get back to building my application!
Conclusion:

SqlitenetWrapper referenced in my library projects
SQLitePCLRaw.bundle_green referenced in my EXE
SQLitePCL.Batteries.Init(); at my application entry point

Works perfectly.

Glad it's working for you!
As for the wiki page idea, if you're talking about here in this repo, that's up to @praeclarum .  This is his repo.  I just try to help with support issues here and there.  :-)


Remove success logs in Testerina

Purpose
This PR removes success logs in Testerina.

Codecov Report

Merging #13851 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #13851      +/-   ##
============================================
+ Coverage     64.47%   64.48%   +0.01%
  Complexity      426      426
============================================
  Files          2154     2154
  Lines         95396    95391       -5
  Branches      12706    12704       -2
============================================
+ Hits          61504    61511       +7
+ Misses        28872    28861      -11
+ Partials       5020     5019       -1

Impacted Files
Coverage Δ
Complexity Δ

...inalang/testerina/core/entity/TesterinaReport.java
83.33% <ø> (-1.58%)
0 <0> (ø)

...rinalang/runtime/threadpool/ThreadPoolFactory.java
61.9% <0%> (-4.77%)
0% <0%> (ø)

...ain/java/org/ballerinalang/net/websub/hub/Hub.java
69.53% <0%> (-1.57%)
0% <0%> (ø)

...a/org/ballerinalang/bre/bvm/GlobalMemoryBlock.java
78.43% <0%> (-0.99%)
0% <0%> (ø)

...e/src/main/java/org/ballerinalang/bre/bvm/BVM.java
81.84% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...et/http/actions/httpclient/AbstractHTTPAction.java
79.14% <0%> (+0.85%)
0% <0%> (ø)
:arrow_down:

...llerinalang/stdlib/socket/tcp/SelectorManager.java
71.79% <0%> (+1.7%)
0% <0%> (ø)
:arrow_down:

...org/ballerinalang/bre/bvm/WaitCallbackHandler.java
82.88% <0%> (+1.8%)
0% <0%> (ø)
:arrow_down:

...n/java/org/ballerinalang/bre/bvm/BVMScheduler.java
45% <0%> (+2%)
0% <0%> (ø)
:arrow_down:

...va/org/ballerinalang/channels/ChannelRegistry.java
97.29% <0%> (+2.7%)
0% <0%> (ø)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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


Reduce child process frequency of checking whether parent has stopped or not

Probably not mission-critical to check it every iteration on the child process, 1 per sec should be fine?

Probably won't touch it for now, benchmarking suggests it's not a bottleneck (at least on Windows)
from timeit import timeit
import psutil

iter = 10000
timeit('psutil.pid_exists(100)', globals=globals(), number=iter)/iter


Sandbox ID exported to analytics, monitoring and with envd logs does not contain client ID

There is no good way to fix this right now because we won't know the client ID until the sandbox is placed.


The tauri fetch method takes a long time to download large files

Describe the bug
I have a 30MB file, downloaded with tauri fetch method and axios method respectively, tauri takes 40+s, axios only takes 4+s, I don't know why, please help me。
Reproduction
https://github.com/wkl007/tauri-download-example
import { useCallback } from 'react'
import { fetch, ResponseType } from '@tauri-apps/api/http'
import axios from 'axios'
import './App.css'

// 30MB file
const url = 'https://cache-1256738511.cos.ap-chengdu.myqcloud.com/files/pdf/download-file.pdf'

function App () {
  const tauriDownload = useCallback(async () => {
    try {
      console.time('tauri fetch download')
      const res = await fetch(url, { method: 'get', responseType: ResponseType.Binary })
      console.log(res)
      console.timeEnd('tauri fetch download')
    } catch (e) {
      console.error(e)
    }
  }, [])

  const axiosDownload = useCallback(async () => {
    try {
      console.time('axios download')
      const res = await axios(url, { method: 'get', responseType: 'arraybuffer' })
      console.log(res)
      console.timeEnd('axios download')
    } catch (e) {
      console.error(e)
    }
  }, [])

  return (

        <button onClick={tauriDownload}>Tauri fetch download</button>
        <button style={{ marginLeft: '20px' }} onClick={axiosDownload}>axios download</button>

  )
}

export default App

Expected behavior
No response
Platform and versions
PS E:\Work\github\tauri-download-example> npm run tauri info

><EMAIL_ADDRESS>tauri
> tauri

Environment
  › OS: Windows 10.0.22621 X64
  › Webview2: 105.0.1343.53
  › MSVC:
      - Visual Studio Community 2022
      - Visual Studio ���ɹ��� 2022
  › Node.js: 16.17.0
  › npm: 8.15.0
  › pnpm: 7.12.1
  › yarn: 1.22.19
  › rustup: 1.25.1
  › rustc: 1.62.1
  › cargo: 1.62.1
  › Rust toolchain: stable-x86_64-pc-windows-msvc

Packages
  › @tauri-apps/cli [NPM]: 1.1.1
  › @tauri-apps/api [NPM]: 1.1.0
  › tauri [RUST]: 1.1.1,
  › tauri-build [RUST]: 1.1.1,
  › tao [RUST]: 0.14.0,
  › wry [RUST]: 0.21.1,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../dist
  › devPath: http://localhost:1420/
  › framework: React

App directory structure
  ├─ .git
  ├─ .idea
  ├─ .vscode
  ├─ node_modules
  ├─ public
  ├─ src
  └─ src-tauri

Stack trace
No response
Additional context
No response

This is a known limitation of v1's IPC mechanism. The webview's message channel forces us to serialize the payload to a json string, which really slows things down...
While still being really slow, it's much faster in release mode (tauri build and tauri dev --release).
Related: #1817
p.s. we try our best to find an alternative implementation for v2 🙏

@FabianLars  Release mode is faster, but there is still a gap compared to axios

Yes we know, and tbh that is better performance than i expected 😅
But as i said, we're trying to find a good work around (and already have promising stuff), the changes will be too big for a 1.X release tho...

Thank you very much


ScreenToGif Translator is not working in Windows10

Hi all,
as my native language is Czech and it is not available in ScreenToGif I decided to create a translation. However, it is not possible to start the translator application under my Windows10.
Can you please make Translator app compatible with Windows 10?
Have a nice day.
Svatopluk
Prague, Czech Republic

It works alright on my Windows 10 machine.
Is there any error message?
The translator needs to create a folder (and download some files) at the same folder where it's located, maybe could be related to that.

the original message was, that Win10 can not start the app without any special error message. I created new special folder and from this moment this app is working. So you were right with the folder creation as it was not possible to create a new one. Now it is working.
Thanks for quick reply. I will provide the translation.

Great, I'll add a warning on the wiki about this issue.


Problem with editing after warnings/errors occur in specific circumstance

The problem occurs when in nested components tutorial I write <Nested/> at the last line (before doing anything else). Then editing is blocked there (just write this, wait for warning/squigglies to appear and you will see).

in situation presented in the scrrenshot writing/backspacing with cursor in the squigglies doesn't do anything
The easiest way I found to fix the code now is to move cursor back a bit (before squigglies) and use delete button to delete what is ahead.
With this error on screen, similar problem occurs after writing something after closing brace of css rules.

The problem becomes worse, as even the trick with delete key doesn't work. Trying to write/backspace around "a" (or anywhere below the line, which makes sense when looking at the error below) results in error like this in the console:
Uncaught (in promise) RangeError: Position 159 is out of range for changeset of length 155
at Xe.mapPos (5.06ffdf3b.js:4:5476)
at El.map (5.06ffdf3b.js:5:2559)
at se.map (5.06ffdf3b.js:5:4381)
at Me.update [as updateF] (5.06ffdf3b.js:11:42592)
at Object.update (5.06ffdf3b.js:4:16950)
at te.computeSlot (5.06ffdf3b.js:4:25555)
at Pn (5.06ffdf3b.js:4:19757)
at new te (5.06ffdf3b.js:4:24801)
at te.applyTransaction (5.06ffdf3b.js:4:25511)
at get state [as state] (5.06ffdf3b.js:4:21217)
Reloading (using reload icon) results in the following in the console, and the above error after that:
[HMR][Svelte] Unrecoverable HMR error in : next update will trigger a full reload
logError @ proxy.js?v=4843b549:15
Proxy @ proxy.js?v=4843b549:380
create_fragment @ +page.svelte:2
init @ chunk-3ICDZIIQ.js?v=4843b549:2167
Page @ +page.svelte:2
createProxiedComponent @ svelte-hooks.js?v=4843b549:341
ProxyComponent @ proxy.js?v=4843b549:242
Proxy<+page> @ proxy.js?v=4843b549:349
construct_svelte_component_dev @ chunk-3ICDZIIQ.js?v=4843b549:2586
create_default_slot @ root.svelte:42
create_slot @ chunk-3ICDZIIQ.js?v=4843b549:84
create_fragment @ layout.svelte?v=4843b549:22
init @ chunk-3ICDZIIQ.js?v=4843b549:2167
Layout @ layout.svelte?v=4843b549:98
createProxiedComponent @ svelte-hooks.js?v=4843b549:341
ProxyComponent @ proxy.js?v=4843b549:242
Proxy @ proxy.js?v=4843b549:349
construct_svelte_component_dev @ chunk-3ICDZIIQ.js?v=4843b549:2586
create_if_block_2 @ root.svelte:41
create_fragment @ root.svelte:40
init @ chunk-3ICDZIIQ.js?v=4843b549:2167
Root @ root.svelte:20
createProxiedComponent @ svelte-hooks.js?v=4843b549:341
ProxyComponent @ proxy.js?v=4843b549:242
Proxy @ proxy.js?v=4843b549:349
initialize @ client.js?v=4843b549:285
navigate @ client.js?v=4843b549:1098
await in navigate (async)
goto @ client.js?v=4843b549:227
goto @ client.js?v=4843b549:1353
start @ start.js:24
(anonymous) @ ?theme=dark:272
Promise.then (async)
(anonymous) @ ?theme=dark:271
Show 4 more frames
App.svelte?t=1689491672994:35 Uncaught (in promise) ReferenceError: Nested is not defined
at create_fragment (App.svelte?t=1689491672994:35:2)
at init (chunk-3ICDZIIQ.js?v=4843b549:2167:35)
at new App (App.svelte:1:27)
at createProxiedComponent (svelte-hooks.js?v=4843b549:341:9)
at new ProxyComponent (proxy.js?v=4843b549:242:7)
at new Proxy (proxy.js?v=4843b549:349:11)
at create_fragment (+page.svelte:2:35)
at init (chunk-3ICDZIIQ.js?v=4843b549:2167:35)
at new Page (+page.svelte:2:35)
at createProxiedComponent (svelte-hooks.js?v=4843b549:341:9)
The 'console' tab in embedded IDE doesn't offer anything I should present here.

Writing  not on the last line doesn't cause the bug to appear


bug(COMPONENT): Horizontal List Orientation under an RTL element does not work properly

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
When I add direction:rtl; style to HTML (or any parent element) drop behavior does not work properly, it moves the item but in the wrong index.

I use a simple trick to handled it. But still, I thought it might need to be reported. And maybe we can use a simple way to handle the problem.
In my case I just change the drop function like this:
drop(event: CdkDragDrop<string[]>): void {
  let totalLists = this.myLists.length - 1;
  let previousIndex = totalLists - event.previousIndex;
  let currentIndex = totalLists - event.currentIndex;
  moveItemInArray(this.myLists, previousIndex, currentIndex);
}

I guess it must be a bit complex to find if an oriented list is truly right to left or left to right, but a very simple way is to use a flag for reverse calculation.
Reproduction
Steps to reproduce:

For demonstration we can use an example by the documentation.
material.angular.io/#horizontal-sorting
stackbliz
Just add RTL direction to html or body in style.css
body { direction: rtl; }

Expected Behavior
Drop to the correct Index
Actual Behavior
The items are dropped in reverse order.
Environment

Angular: 12.1.4
CDK/Material: 12.1.4
Browser(s): chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows

We don't support setting a direction through CSS, because there's no efficient way for us to detect it in JS. You should set the direction in your markup using the dir attribute.

Thanks @crisbeto 🙏


Bug: QWidget error Resolve 18 (Failed to create)

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior:
I can't create shots in Resolve 18.1
Expected Behavior:
Setting naming convention to match kitsu entities using OpenPype create, before publishing them as shots assets.
Version
3.16.3
What platform you are running OpenPype on?
MacOS
Steps To Reproduce:

followed instructions here:
https://github.com/ynput/OpenPype/tree/develop/openpype/hosts/resolve

installing PyQt 5 + install OpenTimelineIO using pip install

select shots then Resolve/EditTab/Menu/Workspace/Scripts/Comp/OpenPype_Menu
Create then create from instance creator
I get this error:

Failed to create Subset: "clipMain" Family: "clip" in Asset: "Sc002_Sh0010"

Error: 'QWidget' object has no attribute 'addRow'

Traceback (most recent call last):
  File "/Applications/OpenPype 3.16.3.app/Contents/MacOS/openpype/tools/creator/window.py", line 431, in _on_create
    legacy_create(
  File "/Applications/OpenPype 3.16.3.app/Contents/MacOS/openpype/pipeline/create/legacy_create.py", line 202, in legacy_create
    instance = plugin.process()
  File "/Applications/OpenPype 3.16.3.app/Contents/MacOS/openpype/hosts/resolve/plugins/create/create_shot_clip.py", line 223, in process
    widget = self.widget(self.gui_name, self.gui_info, self.gui_inputs)
  File "/Applications/OpenPype 3.16.3.app/Contents/MacOS/openpype/hosts/resolve/api/plugin.py", line 64, in __init__
    self.items = self.populate_widgets(ui_inputs)
  File "/Applications/OpenPype 3.16.3.app/Contents/MacOS/openpype/hosts/resolve/api/plugin.py", line 248, in populate_widgets
    data[k]["value"] = self.populate_widgets(
  File "/Applications/OpenPype 3.16.3.app/Contents/MacOS/openpype/hosts/resolve/api/plugin.py", line 252, in populate_widgets
    data[k]["value"] = self.create_row(
  File "/Applications/OpenPype 3.16.3.app/Contents/MacOS/openpype/hosts/resolve/api/plugin.py", line 166, in create_row
    layout.addRow(label, item)
AttributeError: 'QWidget' object has no attribute 'addRow'

Are there any labels you wish to add?

[X] I have added the relevant labels to the bug report.

Relevant log output:
Resolve console output:

>>> [ openpype.hosts.resolve installed ]
>>> [ Registering DaVinci Resovle plug-ins.. ]
>>> [ Assigning resolve module to `pype.hosts.resolve.api.bmdvr`: Resolve (0x0x11831e340) [App: 'Resolve' on <IP_ADDRESS>, UUID: d4adaf10-3293-48d3-afc4-dbab144a44a3] ]
>>> [ Assigning resolve module to `pype.hosts.resolve.api.bmdvf`: FusionUI (0x0x230ed7040) [App: 'Resolve' on <IP_ADDRESS>, UUID: d4adaf10-3293-48d3-afc4-dbab144a44a3] ]
Clicked Create
Using existing QApplication..
Registered font families: Noto Sans, Noto Sans, Noto Sans, Noto Sans, Noto Sans Mono, Noto Sans Mono, Noto Sans Mono, Noto Sans Mono, Noto Sans Mono, Noto Sans Mono, Noto Sans Mono, Noto Sans Mono, Noto Sans Mono
Running <create_shot_clip.CreateShotClip object at 0x7f7b3322beb0> with maintained selection

### Additional context:

_No response_

after a some reviewing I decided to replace "layout" parameter with a "layout" variable to be:
        # add to layout
        QFormLayout().addRow(label, item)

instead of:
        # add to layout
        layout.addRow(label, item)

Then I tied to create and finaly I got no errors but the Shot Creator window got corrupted

This has been resolved on discord. It's a bit hard to pinpoint what the exact issue was but it seemed the codebase of @aramadan0096 did an import from PyQt5 instead of qtpy or QtPy and thus had code changes that were never present in OpenPype for the relevant files. However, debugging on discord also showed that PyQt5 was used in resolve.
After removing PyQt5 and installing PySide2 and reinstalling OpenPype (to remove @aramadan0096's local changes) the UI worked fine.
Whether the UI breaks in PyQt5 or whether the issue was just local changes by @aramadan0096 is still unclear. But since apparently it's solved with PySide2 + a fresh install I'll close this issue.


docs: add 'twitter:image:alt' and 'og:image:alt' metadata

Description
This PR adds a metadata in Starlight documentation to improve the accessibility of Twitter cards when this documentation is shared on this platform, or other cards on different social media platforms.
Feel free to drop this PR if this is a topic that has already been discussed, or if you think this is not necessary. In this case, don't spend too much time on my PR :)
Twitter/X platform
Let's consider this page: https://astro.build/blog/astro-4120/.
It contains the following metadata:
<meta name="twitter:image" content="https://astro.build/_astro/og_image_4_12.DvriEbIV.webp">
<meta name="twitter:image:alt" content="Astro 4.12: Server Islands">

When shared on Twitter (see https://x.com/astrodotbuild/status/1813994888427684008), if you inspect the Twitter card, you'll see that the image has an alternative text, which is good for a11y:

Let's consider our own Starlight documentation at https://starlight.astro.build/ja/getting-started/ (for instance).
It contains the following metadata:
<meta property="twitter:image" content="https://starlight.astro.build/og.jpg?v=1">

The image is the following:

But there's no twitter:image:alt.
When shared on Twitter (see https://x.com/NewGyu/status/1814669986096685126), if you inspect the Twitter card, you'll see that the image doesn't have any alternative text:

It's probably debatable whether a Twitter card image is decorative or not, and should have an alt text or not. However, our Starlight documentation image contains text that, if important, should be accessible to everyone, so via a screen reader too, as it is an information.
This is the reason why I'm suggesting this enhancement.
Other social media platforms
For other social media platforms, they mostly use Open Graph, and it also supports the alternative text for images with og:image:alt. So this is basically the same explanation for the same concept
Translate or not translate?
I've forced the following English text: "Make your docs shine with Starlight".
The reason is that I'd say we should have the exact same information as in the thumbnail (which is not translated).
But that's debatable. Maybe we can translate it for screen readers users only, for once, they would have the most precise information :)

As an aside: I’m honestly not sure what on earth Twitter is doing with any of this. Looking at the astro.build example, the markup looks something like this:
Two aria-labels, an unnecessary role, an alt, and then actual text…

Yeah, and they improved it, apparently. I stumbled upon a post where it was mentioned that the alt text was inside an HTML element with an aria-hidden=true before 🙃

One question: do you happen to know if both the twitter:image:alt and og:image:alt variants are required? Or would Twitter use the og: one if available?

There are apparently fallback rules (that I haven't tested) here: https://developer.x.com/en/docs/twitter-for-websites/cards/overview/markup

Property
OpenGraph

twitter:image
og:image

twitter:image:alt
og:image:alt

We could rely on the og:* fallback as it seems to work. If we do that, for consistency, maybe we should drop twitter:image, twitter:title, etc. On one hand, it would reduce the size of the pages.
But my own personal feeling would be to keep them both, as we would never know in the future if things change, if the fallback works differently, etc.
What do you think?

#2137 coincidentally removes most of the existing twitter:* tags, so I think I’m OK with removing them. Apart from the twitter:card one, they all seem to map back to the more standard og:* ones, so I think I’d only use the twitter:* ones if for some reason I wanted more control for different tags on Twitter from elsewhere.

Oh, I didn't notice https://github.com/withastro/starlight/pull/2137, funny coincidence. I can understand the logic behind getting rid of twitter:* (except twitter:card that is important). The Astro/Starlight community is big, so if there's an update, we can trust it to create some PRs to put it back if necessary.


A PyTorch version of TCLP

Hello author,
Thank you for the release of the code of your paper:) I really love your work.
I really wanna run your code in our pipeline, but the code of TCLP is based on Tensorflow 2.0.
If you don't mind, could you provide PyTorch version?
Thank you in advance ^_^

There is no plan for PyTorch. Except the source code related to model, plateau model and label propgation is based on Python only.


Add user/group filtering to cybr safes list

Is your feature request related to a problem? Please describe.
The cybr safes list command currently just lists all safes the logged in user has access to.
Describe the solution you'd like
A filter added to cybr safes list that allows filtering based on user/group membership.
For example, cybr safes list -f jgarcia would return all safes the current logged in user can see that has jgarcia user as a member.  Or, cybr safes list -f CyberArkVaultAdmins would return all safes the current logged in user can see that has CyberArkVaultAdmins Active Directory security group as a member.
Describe alternatives you've considered
None.
Additional context
None.

Rather than adding a filter to cybr safes list, the query parameters available for cybr safes list-members should be added.  This will support filter=memberType%20eq%20user or filter=memberType%20eq%20group as well as search=<user/group name>.
By doing something like cybr safes list-members --user -s jgarcia or cybr safes list-members --group -s CyberArkVaultAdmins the same end result can be achieved and still fall in line with what the PAM REST API provides natively.

Actually, upon further thought, it won't be the same experience since it has to target a specific safe for safe members. However, the previous comment's functionality has to be added in order to support the original issue's request.

Rather than adding a filter to cybr safes list, the query parameters available for cybr safes list-members should be added. This will support filter=memberType%20eq%20user or filter=memberType%20eq%20group as well as search=<user/group name>.
By doing something like cybr safes list-members --user -s jgarcia or cybr safes list-members --group -s CyberArkVaultAdmins the same end result can be achieved and still fall in line with what the PAM REST API provides natively.

This is now supported on branch 143-add-usergroup-filtering-to-cybr-safes-list.


fix issue #41

Thank you! I just edited content_script.js with your change and the extension works!


Video Embed Possible?

Hi, is it possible to get video's embedded as links or something similar into the generated HTML report?
Thanks

Currently no, because we cant add context per suite/spec file.
Related issues: https://github.com/adamgruber/mochawesome-report-generator/issues/124 https://github.com/adamgruber/mochawesome-report-generator/issues/150

Hi @LironEr
Instead of waiting for the context for suite. I thought of adding a test entry (provided below) in tests array, after cypress execution just like enhanceReport function updating the context, here I'm adding a test entry.
When using file name I'm able to see the video in the HTML file, but I had to share the video along with the html report.
Could you please suggest a way to add the video in the embedded format. I tried some ways they didn't worked.
      suitesMap.forEach((suiteEntry) => {         suiteEntry.tests.push({           title: "Execution Video",           fullTitle: "Test Execution Video",           timedOut: null,           duration: 1,           state: "passed",           speed: "fast",           pass: true,           fail: false,           pending: false,           context: JSON.stringify({             title: "Execution video",             value: videoDetails.embeddings.data           }),           code: "",           err: {},           uuid: "f4c9b97d-f7cc-45e3-a383-852df0eec2d2",           parentUUID: "b43632da-b240-4fe7-a130-c29065bd5f87",           isHook: false,           skipped: false         })       })

hi @LironEr , any progress in this?

Currently no, because we cant add context per suite/spec file. Related issues: adamgruber/mochawesome-report-generator#124 adamgruber/mochawesome-report-generator#150

@mudit94 unfortunately no

So it seems that Bahmutov embeds the video file for the whole suite to the test(s) that fail.
:thumbsdown: Same videofile might be embedded on several failed tests
:thumbsdown: Videofile for failed tests will contain alot more tests than the one you are looking for
:thumbsup: Embedded videofile 👏🏼

This feels like were making some progress at last!

Gave it a try with #137 , give it a look and let me know what you think 😸

@joakim-sch Great work!
Released in v3.4.0


[SR-13753][Diagnostics] Downgrade l-value unused diagnostics to warning

When expression type checks to a l-value no is produced missing return because lvalue unused is currently being diagnosed as an error and failing early on type checking, therefore not even getting into SIL dataflow diagnostics where missing return diagnostic would be produced.
We can see this exactly on those two cases:

let _ : () -> Int = {
  let x : Int = 0 // x is a let so x would be an r-value, unused would be just a warning and correct SIL dataflow diagnostics would be produced.
  var a : Int = 0

  x // error: missing return
}

let _ : () -> Int = {
  var x : Int = 0 // x is a var x result will typecheck as an l-value therefore fail early on typechecking
  var a : Int = 0

  x // error: expression resolves to an unused variable
}

This just downgrades l-value to a warning and defer the proper diagnose errors in SIL.

Resolves SR-13753.

@swift-ci Please smoke test

I think this is correct, I don't see any reason why this should be an error and not a warning.
Not related to this PR but, I think the wording "expression resolves to an unused variable" seems unnecessarily jargon-heavy, there is no need to use the word "resolved". We may want to simplify the wording...

I think this is correct, I don't see any reason why this should be an error and not a warning.
Not related to this PR but, I think the wording "expression resolves to an unused variable" seems unnecessarily jargon-heavy, there is no need to use the word "resolved". We may want to simplify the wording...

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci Please smoke test macOS platform

I think the wording "expression resolves to an unused variable" seems unnecessarily jargon-heavy, there is no need to use the word "resolved". We may want to simplify the wording...

I agree, maybe just simply "result of expression is unused"? WDYT, I can put a follow-up ... or maybe we can create a starter bug on JIRA :)

@swift-ci Please smoke test macOS platform

@swift-ci Please smoke test macOS platform

@swift-ci Please smoke test macOS platform

@swift-ci Please smoke test macOS platform

Creating a starter bug sounds good. 👍🏼

Creating a starter bug sounds good. 👍🏼

Creating a starter bug sounds good. 👍🏼

Awesome!

For the suggested wording "result of expression is unused" -- I think it's a bit tricky, on one hand, I can understand what it is saying, but it's kind of funky because function application has a result, and expression evaluation has a result, but I'm not sure if the phrase might be confusing without the word "evaluation"... on the other hand, the word "evaluation" is again a bit of jargon...

I see ... so what about "result produced from expression is unused" or "result value produced from expression is unused" or "result value of the expression is unused"(I like this one)

Creating a starter bug sounds good. 👍🏼

Awesome!

For the suggested wording "result of expression is unused" -- I think it's a bit tricky, on one hand, I can understand what it is saying, but it's kind of funky because function application has a result, and expression evaluation has a result, but I'm not sure if the phrase might be confusing without the word "evaluation"... on the other hand, the word "evaluation" is again a bit of jargon...

I see ... so what about "result produced from expression is unused" or "result value produced from expression is unused" or "result value of the expression is unused"(I like this one)


Use files, and add rimraf

@EvanHahn
Not sure if I'll be able to do this for all the packages here, but rm -rf isn't cross-platform and rimraf is already in devDependencies anyway.
So this actually fixes things on Windows.

@EvanHahn: I also made the engines change because it's really fine.
Now, I see that you don't test on Node.js 4 on Travis. It's bad doing so IMO. Something not tested will break without anyone noticing.
You know your versions support better, just sort this out later by either testing on 4.0 too or dropping support for 4.0 later.

=4.0.0 is equal to >=4

the same as with .npmignore

No, sorry, I don't have the time to split this. It's simple changes.

BTW, you always pull the branch locally to see the output of npm pack --dry.

Because I don't intend to merge this (it needs to be split up into smaller PRs), I'm going to close this.
Feel free to open issues for each of these things and we can address them individually.

Nah, all good.


werkzeug.FileStorage().save() saves an empty file

If we have
file_storage = werkzeug.FileStorage()
file_storage.save()
it will save an empty file. There is no solution anywhere online that I could find. Finally, after hours of debugging, I found a workaround:
file_storage.stream.seek(0)
file_storage.save()

Duplicate of #748
Duplicate of #207
This matches the behavior of Python in general. If you read from a file, you need to reset before you can read again. Additionally, some IO cannot be seeked, so this is not done automatically.

Thank you this worked for me!!


Version bump to v3.6.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
7081

Relevant Lines:
8415

💛  - Coveralls


[Code review: Contract Bugs]: The '_distributeFees' function's gas fees issue

Describe the bug
The swapWSTONforTON function's gas fees will continue to increase as the number of lpAddresses increases.
It seems unreasonable to make the user pay the gas fee for the fee distribution to lpAddresses.
https://github.com/tokamak-network/gem-nft-contract/blob/306b8fd7de7163e11cfcef0ec7c1dd7e12f6f088/src/L2/WstonSwapPool.sol#L104
https://github.com/tokamak-network/gem-nft-contract/blob/306b8fd7de7163e11cfcef0ec7c1dd7e12f6f088/src/L2/WstonSwapPool.sol#L159-L179
Impact
No response
Exploit Scenario
No response
Recommendation
The fee distribution to lpAddresses should be run when lpAddresses are changed, or let them run and pay the gas fee themselves.

Thanks @Zena-park . I implemented a Pull Over Push Model:
Instead of distributing fees immediately during the swap, we accumulate the fees in a pool and allow liquidity providers to claim their share of the fees at their convenience. This shifts the gas cost to the liquidity providers who can decide when to claim their rewards. Here is the code update
I have created the following storage:
uint256 public tonFeeBalance;
uint256 public wstonFeeBalance;

Then I have created the claimFees function:
 /**
 * @notice Distributes accumulated TON and WSTON fees to liquidity providers based on their share.
 * @dev This function iterates over all liquidity providers and distributes fees proportionally.
 *      It resets the fee balances before distribution to prevent reentrancy attacks.
 *      Ensure that the function is called when there are fees to distribute to avoid unnecessary gas costs.
 * @dev Emits a {FeesDistributed} event.
 * @dev Uses the nonReentrant modifier to prevent reentrancy attacks.
 */
function distributeFees() external nonReentrant {
    uint256 tonFees = tonFeeBalance;
    uint256 wstonFees = wstonFeeBalance;
    require(tonFees > 0 || wstonFees > 0, "No fees to claim");

    // reset storage variables before transferring
    tonFeeBalance = 0;
    wstonFeeBalance = 0;

    if (totalShares == 0) return;

    for (uint256 i = 0; i < lpAddresses.length; ++i) {
        address lp = lpAddresses[i];
        uint256 share = lpShares[lp];
        if (share > 0) {
            uint256 tonReward = (tonFees * share) / totalShares;
            uint256 wstonReward = (wstonFees * share) / totalShares;

            if (tonReward > 0) {
                _safeTransfer(IERC20(ton), lp, tonReward);
            }
            if (wstonReward > 0) {
                _safeTransfer(IERC20(wston), lp, wstonReward);
            }
        }
    }

    emit FeesDistributed(tonFees, wstonFees);
}

Finally I have updated swapWSTONtoTON and swapTONforWSTON function by replacing
_distributeFees(0, fee);

to
tonFeeBalance += fee;

and
_distributeFees(fee, 0);

to
wstonFeeBalance += fee;

code update

Actually the contract is still vulnerable to DoS with an attacker depositing a small amount thousands of time to fill in the lpAddresses array until LPs can't collect fees anymore. I will implement a new way of managing address duplicates in addLiquidity/removeLiquidty functions

I confirmed. Thank you.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_f45waygna_/clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_f45waygna_/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_f45waygna_/clone/recipe/meta.yaml:38: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_f45waygna_/clone/recipe/meta.yaml:38: missing_license_family: The recipe is missing the about/license_family key.
ERROR: /tmp/abs_f45waygna_/clone/recipe/meta.yaml:38: missing_dev_url: The recipe is missing a dev_url
WARNING: /tmp/abs_f45waygna_/clone/recipe/meta.yaml:38: missing_description: The recipe is missing a description
Errors were found


From for AssetPath does not work with labels.

Bevy version
0.14.1
What you did
AssetServer::load(asset_server, PathBuf::from("Spaceship.glb#Scene0");

What went wrong
Error Message:
ERROR bevy_asset::server: Path not found: C:\Users\<path to working dir>\assets\Spaceship.glb#Scene0

Additional information
The Path does include a label, but in the conversion from PathBuf, it is simply not taken into account.
This leads to unexpected behaviour.
I'd expect to get an error use AssetPath! not PathBuf or i'd expect the label to get stripped from the last component.

@DasLixou hm, sorry, that's totally my bad for not rtfm
I do wonder if a # in the filename is actually the more common case
Or if an associated Method on AssetPath to use the path as-is would be more clear.
The Documentation definetely could not be any clearer, so this is definetely not an issue, and probably not worth discussing either.

@kartonrad No problem. FYI you dont need to create the Path, you can just use a string in the load function, where it then parses the label correctly. See any example that loads an asset.
Could I ask why you came to the conclusion you would need a Path?


different package versions for different python versions

My application can work under either python2 or python3, but some requirements have different versions. (For example, ipython >=6 for python3, < 6 for python2.)
If I specify ipython="*", pipenv lock will pick ipython==6.3.1
I tried specifying
ipython = {version = ">=6.3", markers="python_version >= '3'"}
ipython = {version = "<6", markers="python_version < '3'"}

but pipenv complains about re-using the identifier.
I'm not sure if this is possible; if so I could not find it in the documentation (and maybe that case should be made explicit in the documentation.) If it is not possible and is not intended to be, maybe that should also be said explicitly.
Regards

This is possible (not with this syntax, of course, because TOML does not allow duplicate keys), but I don’t think it’s a good idea overall. It is better to wrap the package (IPython in this example) in a custom setup.py, and specify the conditional dependency there.
Something like:
# ipython-select/setup.py
from setuptools import setup
setup(
    name='ipython-select',
    version='1.0',
    installs_requires=[
        'ipython>=6.3; python_version>="3"',
        'ipython<6; python_version<"3"',
    ],
)

# Pipfile
[packages]
ipython-select = {path = "./ipython-select"}

Thank you, that is helpful.

Could a similar approach be included in the Pipfile syntax directly?
e.g.
[packages]
ipython-select = [{version=">=6.3", markers="python_version>='3'"}, {version="<6", markers="python_version<'3'"}]

or anything like that, not sure if that' TOML compatible either.

Adding onto this - other markers are of interest as well, and more difficult to incorporate into a setup.py
For my use case, I would like to install from different wheels on Windows depending on the platform, and from PyPI on Linux; i.e.:
python-ldap = {path = ".\\wheel\\python_ldap-3.1.0-cp36-cp36m-win_amd64.whl", markers="python_version == '3.6' and sys_platform == 'win32' and '64' in platform_machine"}
python-ldap = {path = ".\\wheel\\python_ldap-3.1.0-cp36-cp36m-win32.whl", markers="python_version == '3.6' and sys_platform == 'win32' and '64' not in platform_machine"}
python-ldap = {version  = "==3.1.0", sys_platform = "!= 'win32"}

I would encourage people to persue the wrapper package solution. Also, if you wish to provide a solution, please provide one that is actually doable, i.e. at least propose solution in legal TOML syntax. Thanks.

How would I solve my problem (install from local wheels on Windows, install from pypi on non-Windows) using a wrapper package?

@uranusjr can I know why this encouragement?
It seems to me that a wrapper solution defeat the purpose of a Pipfile itself.
Why should someone who subscribe to the idea behind pipfile and pipenv to then choose to use code to describe dependancy as a preferred/encouraged approach?
Let's do "that" until is possible otherwise: yes. But encouraging it, seems opposite to the purpose of the project.
Am I missing your point?
I agree on the "if propose, at least propose doable"
Although, use cases collection can be done with meta code, and doesn't really change anything, while enriching the discussion.

The reasoning is a practical one—the feature is highly unlikely to land now, or even in short-term future. While a spec change is indeed worth persueing, it is by nature quite involved, and require a lot of discussion. Assuming you already need the feature right now, it is more preferrable (for us maintainers, at least) to adopt Pipenv now with a workaround, than to put off adapting it altogether until the feature is solidified and land in the far, far future.
My recommendation is also not a discouragement to spec discussion. The spec modification is still the ultimate goal, and I would love to see proposals (if doable), as mentioned above. In the meantime, however, we still need to work on our real-world tasks, and I feel it is the best to solve the problem at hand with a workaround, instead of going directly for the theoratically best, purest solution (which, from my experience, tends to result in hast discussion and bad design decisions).

@axnsan12 now, Did you have resolution for your problem

Nope, I gave up and went back to pip

@axnsan12  i want to use  a custom setup.py to solution this problem , do you know  in setup.py how to
serarch specified wheel file in setup.py's folder ?

For the record: after a few experiments, I also decided against using this workaround and went to a pip-tool based solution. I specify python_version in the requirements.in file and generate separate requirements[2,3].txt files. I'm afraid that the need for wrappers will be an obstacle to pipenv adoption. Best of luck.

Hey, nobody is stopping you if you want to actually do something about it.

I unfortunately had to go back to pip as well for a project. Understandable this requires some effort and is in low priority. Hopefully some hero steps in and tries to push a MR.

@uranusjr This seems like a very reasonable request. Do you mind providing us with a status update?
I fail to reason that this would be hard to implement. Although, I'm currently busy with other projects at the moment. If I ever get unbusy, maybe I'll send a PR for it.

@pro-src you may not see why it would be hard to implement, but it touches our dependency resolver which inherently makes it hard to implement. It also requires specification changes to Pipfile which adds complexity.  Put another way, if it were easy, it would already have been done.
I did have a chance to chat with @ncoghlan about this and he suggested simply adding the version tag to the lockfile as an extension, we could then modify the lockfile search function to look for lockfiles with extensions first, and, during resolution, if we are resolving with python 2 for instance, we can simply create Pipfile.py27.lock instead of Pipfile.lock.  This solution seems pretty elegant to me, albeit a little similar to the current situation with requirements.txt files.

Hi @techalchemy,
Thanks for taking the time to respond.
I read the PEEPS, I get it.
I read over the resolver and it doesn't appear to be easy but the code is well organized and very readable.
I gotta say... I'm not really intimidated by it. Saying it's not hard isn't fair though. So I'll concede to say that it's not extremely difficult. :smiley:
Still, I haven't the insight of the core maintainers from a mere overview alone so please excuse my opinion if misguided. It isn't my intention to appear as arrogant or suggest that there isn't a very real burden on the maintainers here. I very much appreciate Pipenv and the hard work that's been done.
If anything, please take my opinion as a complement of the excellent code that exists in this repository.
I'll try to get around to contributing and proving myself wrong as a way to say thank you.

no worries, definitely happy to accept a PR and glad you are willing to tackle it :D also glad to know you are looking at the code and not struggling too much, been putting some work into cleaning things up a bit
first step is definitely going to be coming to some agreement about the implementation though, I think that just means at the end of the day that @ncoghlan, @uranusjr and myself should be on the same page and then we should get a markdown document together describing the behavior.  Once we get that far it's all just implementation

@techalchemy Would that approach solve situations like reported here, where you want to check which sys_platform is being run?
E.g.
[packages]
bsddb3 = {version = "==6.2.6", sys_platform = "!= 'win32'"}
bsddb3 = {file = "https://download.lfd.uci.edu/pythonlibs/l8ulg3xw/bsddb3-6.2.6-cp36-cp36m-win_amd64.whl", sys_platform = "== 'win32'", platform_machine = "== 'AMD64'"}

@thernstig Unfortunately duplicate keys are not acceptable in a TOML document, however, you can always modify one entry to another name, where the package name here doesn't matter if you have specified the installation link or file path.

I’ve been wondering whether it would be a good idea to detach entry keys from package names:
[packages]
bsddb3 = { version = "==6.2.6", sys_platform = "!= 'win32'" }
bsddb3-1- = { name = "bsddb3",  file = "https://download.lfd.uci.edu/pythonlibs/l8ulg3xw/bsddb3-6.2.6-cp36-cp36m-win_amd64.whl", sys_platform = "== 'win32'", platform_machine = "== 'AMD64'"}
# The trailing dash is intentional to prevent conflicts when there actually is a package named "bsddb3-1"

@frostming, but as my previous comment slightly above, you are allowed to do this:
ipython = [ {version = ">=6.3", markers="python_version >= '3'"},
            {version = "<6", markers="python_version < '3'"} ]

@uranusjr Seems cool as well.

I quite like the idea of allowing the package requirement to be a list, with the behaviour being that when it's a list, the requirements for all applicable environments are applied. The no-list case is then just a simplification that allows the square brackets to be omitted in the single element list case (i.e. [{...}]).
That way it's crystal clear that the requirements all relate to the same package, there are just platform-specific considerations as to exactly which versions you can and can't use. As another practical example, consider the situation where a particular release of a dependency is known to have issues on Windows, but works fine elsewhere, and later versions were fixed to work again on Windows:
example_dependency = [ {version = ">=7.2""},
                                         {version = "!=7.3.0", sys_platform = "== 'win32'" } ]

If multiple options in the list end up being applicable, that's fine, but if they generate a conflict, then the dependency resolution will fail, just as it would if the conflicting dependencies had come from different projects.

it took me seven centuries to find this issue. just wanted to say that, unfortunately, this issue holds me from moving from pip to pipenv. I would appreciate any workaround or any kind of implementation.

@frostming, but as my previous comment slightly above, you are allowed to do this:
bsddb3 = [ {version = "==6.2.6", sys_platform = "!= 'win32'"},
           {file = "https://download.lfd.uci.edu/pythonlibs/l8ulg3xw/bsddb3-6.2.6-cp36-cp36m-win_amd64.whl", sys_platform = "== 'win32'", platform_machine = "== 'AMD64'"} ]

Or to make it more clear with another case:
bsddb3 = [ { version = "==7.2.6", sys_platform = "!= 'win32'" },
           { version = "==6.2.6", sys_platform = "== 'win32'" } ]

@uranusjr Seems cool as well.

My programmer intuition pointed me to the same solution. To my suprise it lead to an error:
ipfile.lock (44462f) out of date, updating to (c9fed2)...
Traceback (most recent call last):
  File "/usr/bin/pipenv", line 33, in <module>
    sys.exit(load_entry_point('pipenv==2021.5.29', 'console_scripts', 'pipenv')())
  File "/usr/lib/python3.9/site-packages/pipenv/vendor/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python3.9/site-packages/pipenv/vendor/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3.9/site-packages/pipenv/vendor/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3.9/site-packages/pipenv/vendor/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3.9/site-packages/pipenv/vendor/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/lib/python3.9/site-packages/pipenv/vendor/click/decorators.py", line 73, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
  File "/usr/lib/python3.9/site-packages/pipenv/vendor/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/lib/python3.9/site-packages/pipenv/vendor/click/decorators.py", line 21, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/lib/python3.9/site-packages/pipenv/cli/command.py", line 233, in install
    retcode = do_install(
  File "/usr/lib/python3.9/site-packages/pipenv/core.py", line 2052, in do_install
    do_init(
  File "/usr/lib/python3.9/site-packages/pipenv/core.py", line 1274, in do_init
    do_lock(
  File "/usr/lib/python3.9/site-packages/pipenv/core.py", line 1081, in do_lock
    dev_packages = overwrite_dev(project.packages, dev_packages)
  File "/usr/lib/python3.9/site-packages/pipenv/project.py", line 717, in packages
    return self._build_package_list("packages")
  File "/usr/lib/python3.9/site-packages/pipenv/project.py", line 222, in _build_package_list
    or any(is_valid_url(i) for i in [k, v])
  File "/usr/lib/python3.9/site-packages/pipenv/project.py", line 222, in <genexpr>
    or any(is_valid_url(i) for i in [k, v])
  File "/usr/lib/python3.9/site-packages/pipenv/utils.py", line 1745, in is_valid_url
    pieces = urlparse(url)
  File "/usr/lib/python3.9/urllib/parse.py", line 392, in urlparse
    url, scheme, _coerce_result = _coerce_args(url, scheme)
  File "/usr/lib/python3.9/urllib/parse.py", line 128, in _coerce_args
    return _decode_args(args) + (_encode_result,)
  File "/usr/lib/python3.9/urllib/parse.py", line 112, in _decode_args
    return tuple(x.decode(encoding, errors) if x else '' for x in args)
  File "/usr/lib/python3.9/urllib/parse.py", line 112, in <genexpr>
    return tuple(x.decode(encoding, errors) if x else '' for x in args)
AttributeError: 'Array' object has no attribute 'decode'

[packages]
tables = [{version = "*", sys_platform = "!= 'win32'"},{path = "./vendor/tables-3.6.1-cp39-cp39-win_amd64.whl", sys_platform = "== 'win32'"}]

I wonder if the array syntax is just a suggestion to new syntax or an actual solution.

I believe we are still waiting for someone to actually implement the array syntax.

Same issue. Python 3.7 includes the package contexvars, but Python3.6 does not. I want to install contexvars in setup.py when using Python3.6, but not in Python3.7. How do I make it happen？

Named categories could perhaps solve this problem too #4745
you could have your default group that is common to all systems, and then an ldap-win ldap-linux for example -- it does mean needing to know which package group you want to install ahead of time for that platform, but it feels like a reasonable workaround.

you have reached the end of the internet.

@matteius no chance this could be re-opended and reconsidered, as this https://github.com/pypa/pipenv/issues/2171#issuecomment-493098208 seems like a nicer solution than https://github.com/pypa/pipenv/issues/4745.
It would bring some extra, nice power.


Update outdated features in Readme

Feel free to change the wording. Just realized that those two points where no longer up-to-date ;-)


Move sscanf

@Graur , please review
I copied sscanf according to #9

@yegor256 look please

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 4min)

@levBagryansky Thanks!


Cannot provide a value for property in Blazor Component

If you believe you have an issue that affects the security of the platform please do NOT create an issue and instead email your issue details to<EMAIL_ADDRESS>Your report may be eligible for our bug bounty but ONLY if it is reported through email.
Describe the bug
When i  open Blazor Component that's doesn't render and return exception:
To Reproduce
Steps to reproduce the behavior:

Using this version of ASP.NET Core '3.0.0'
Run this code
Adding service in DI

 services.AddSingleton<IUserService, UserService>();
and go to page with
' @using Sensica.BLL.Contracts;
@inject UserService service'

with interfaces i'm trying do that's too.
3. With these arguments '....'
4. See error
InvalidOperationException: Cannot provide a value for property 'service' on type 'Sensica.AdminPanel.Pages.Users.Index'. There is no registered service of type 'Sensica.BLL.Contracts.IUserService'.
Expected behavior
That must render page and return collection of user

@UltWolf thanks for contacting us.
You need to inject IUserService not UserService.
Hope that helps.

Sorry, but i`m writing :

with interfaces i'm trying do that's too.

@UltWolf Can you clarify what you are trying to accomplish and what is not working according to your expectations?

@javiercn
I want just get my complete UserService from DI  and inject him into my BlazorComponent,  for creating entities without work with api,  but when im trying thats, that`s return error.


Skip slow tests (resolves #1826).

If TOIL_TEST_QUICK=True, all tests with the 'slow' decorator will be skipped. Quick, in this case, is 15 minutes on my laptop.
Any critical tests that are not too long could be added back in.

Jenkins has a list which is sortable by total runtime:
http://jenkins.cgcloud.info/job/toil-pull-requests/3098/testReport/
The fileStore tests (caching, non-caching, etc) are the longest by far, with all the jobStores a distant second.

The file diff for this PR is a list of those tests marked slow. As @joelarmstrong mentioned, look at a passing Jenkins run to see timings. I used that list initially. I marked as slow anything that took longer than 25-30 seconds.

Okay, good. I'd probably choose to keep the single machine sort tests, and all the basic single machine tests in general - as they test core toil.
For this PR to go in, I think you need some documentation in the PR on how to run with this.

jenkins, test this please

Jenkins, test this please.


Flutter Azure Hub Notification - device installation not updated

I think might be some update at Flutter and the return of String at some methods are now "dynamic", as the image below shows:

I replace the String at the "<>" and worked fine, but I think the documentation should be updated

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

ID: 94b0eeab-4627-9795-8d11-16187ea82d6c
Version Independent ID: 963a4858-9631-c1a7-b4ef-e74f74bf95e6
Content: Send push notifications to Flutter apps using Azure Notification Hubs via a backend service
Content Source: articles/mobile-apps/notification-hubs-backend-service-flutter.md
Service: mobile-services
GitHub Login: @mikeparker104
Microsoft Alias: miparker

Closing this issue due to staleness. We apologize for the delayed response. If you are still encountering the problem you've described, please re-open the issue within 2 weeks and we'll take a look. Thanks!
#label:"UUF-Stale-Not Planned"


Implement factory methods to return HttpProxyHandlerFactory instances or not based on system default proxies

The code has been structured to allow doing the same for SOCKS proxies in the same way, hence the new package-protected helper class.

This PR can be manually tested by setting the system properties

https.proxyHost
https.proxyPort
and for bonus points you can test varying by host with
http.nonProxyHosts
(note http not https prefix)

This has been tested in Apache Karaf by modifying etc/system.properties to set them.
The code as written should be easy to copy and paste for SOCKS versions but I have nothing to run them against.

The build failure is in different tests to the ones I added. I thought my tests had reset the global state they modify (the default proxy config) so I don't know what's happening there.

Actually, a Proxy is just a wrapper around a SocketAddress and a Proxy.Type; the helper could just return the SocketAddress or null, saving the caller having to unwrap it. I'll fiddle with the patch ...

Further commit added to have the proxy locator just return the appropriate SocketAddress. Either works, so which you would take (if any) is down to style choice really.

My apologies, I believe I was premature here. I wrote this one blind as we are deploying to a customer behind an HTTP proxy. I watched their code startup and say that the factory had initialised as I had expected. However, it appears that Netty's proxy handler is HTTP/1 only so with Pushy now using HTTP/2 this does not work. We only got to test with the customer recently - I should have waited for a positive end to end test before submitting this PR.

However, it appears that Netty's proxy handler is HTTP/1 only so with Pushy now using HTTP/2 this does not work.

So, let me begin by being clear that I am a total proxy n00b. When we first added proxy support, my thought was that a conventional "HTTP proxy" wouldn't work for this case precisely because APNs uses HTTP/2 (and prior iterations of APNs used a proprietary, non-HTTP protocol). Another user insisted that it would work because HTTP proxies can handle arbitrary traffic. Now that I'm looking at it in more detail, though, I can't find any evidence to support that claim.
If that's true (and I'll want to dig a little deeper before committing), it probably makes sense to remove the HttpProxyHandlerFactory entirely.

I'm embarrassing myself in public as I also learn about HTTP proxies and HTTP/2!
My above comment was wrong; you can have an HTTP/1 proxy work with an HTTP/2 client as the proxy just creates a tunnel. HTTP/1 is used to talk to the proxy with a CONNECT message and then you send HTTP/2 which will be transparently forwarded down the tunnel. I have tested that here this morning using a Privoxy container.
The actual bug I was having was due to address returned from the locator not being resolved, which caused the proxy setup code to fail with what seemed to be a mysterious "unresolved host" exception. I have updated the branch with a fix for that.
Sorry for not writing this up already - I was waiting for a positive test at the customer site before I wrote anything else that I'd regret! I hope that should be done in a few hours. While I have proven the fix here, I don't yet know for sure that is the only problem the customer were having.

No worries at all; we're in the same boat ;)
I'll look forward to the test results!


route context example

Why? What?
This approach solves next issues https://github.com/rendrjs/rendr/issues/274, https://github.com/rendrjs/rendr/issues/351

Sorry it took so long to get to this PR! I was just told there were a couple on rendr-examples, i mainly focus on reviewing things for rendr itself. :frowning:


Review new feature description with tech writer

[x] This contribution adheres to CONTRIBUTING.md.

TODO: Check the above box with an 'x' indicating you've read and followed CONTRIBUTING.md.
What does this Pull Request accomplish?
This PR edits the label, description and tip strip of the feature that appends TDMS waveform properties to channels
Why should this Pull Request be merged?
I reviewed the information we're providing to users with our technical writer to ensure it makes sense for customers
What testing has been done?
No functional changes

We decided against "Append TDMS Waveform Properties" because the tech writer asked me: "and your customers know what those are, or what that is?", and I was like... "ehhh.... no". Hence, we prefer to document the effects of the checkbox, rather to the technicality behind it. However, I did leave the technical details in the Control's description to ensure we still expose those somewhere :)


When I run Full Calculate or Schedule Full Calculate, nothing happens. I receive no error, the job just doesn't run and the summary logs are blank. This is in Sandbox. Install has not taken place in Production.

IMPORTANT NOTE The Chatter Community Group can be found here. If it is an issue that you need help on configuring the tool or have an unexpected error its really worth seeing if the community can help first before raising a GitHub issue. Most users hangout in the Chatter Community Group. Otherwise if prefer you can post here and still link in the Chatter Community Group.

@crystalmregan, if this is still an issue I'd encourage you to bring this to the Trailhead community, https://trailhead.salesforce.com/trailblazer-community/groups/0F9300000009O5pCAE.
Have you looked in the Apex Jobs setup page to see if anything executed? Is that what you mean by "job just doesn't run?"


Renovate uses the JSON api by default

If a source ends in "/simple/" renovate uses the simple API we have currently implemented.
If not it uses the JSON API for some metadata.

https://wiki.python.org/moin/PyPIJSON
https://github.com/renovatebot/renovate/issues/2970

Redirecting <>/simple/ to <> might work here.

Renovate relies on the deprecated releases in the JSON API: https://github.com/renovatebot/renovate/blob/76ba220d99ee9b426f9a0b5fcf7a7341c6df1221/lib/modules/datasource/pypi/index.ts#L170
spec: https://warehouse.pypa.io/api-reference/json.html
Although it uses very little info from it: https://github.com/renovatebot/renovate/blob/main/lib/modules/datasource/pypi/types.ts#L1
This might work and would prevent querying for every package version when listing the package since this info is available in the TagsList:
{
  "info": {
    "name": "package_name",
  },
  "releases": [
    "0.0.1": [],
    "0.0.2": []
  ]
}


Download data as a file

Could you add this feature in this package? I think, it will be very usefull for all.

Ok, I will add export example soon.

Hi,Bhavesh,  i cant find this feature in documentation, did you add to github?

Still not added, i will inform you once added exports examples.

Hi ruslanubaydullayev,
I have added export example, you can find from the below link:
https://vue3-datatable-document.vercel.app/export


[SPARK-14193][SQL] Skip unnecessary sorts if input data have been already ordered in InMemoryRelation

What changes were proposed in this pull request?
This pr is to skip unnecessary sorts if input data have been already ordered in InMemoryRelation.
Let's say we have a cached table with column 'a' sorted;
val df1 = Seq((1, 0), (3, 0), (2, 0), (1, 0)).toDF("a", "b")
val df2 = df1.sort("a").cache
df2.show // just cache data

If you say df2.sort("a"), the current spark generates a plan like;
== Physical Plan ==
Sort [a#13 ASC], true, 0
+- InMemoryColumnarTableScan [a#13,b#14], InMemoryRelation [a#13,b#14], true, 10000, StorageLevel(true, true, false, true, 1), Sort [a#13 ASC], true, 0, None

This pr removes this unnecessary sort.
How was this patch tested?
Add tests to check this kind of sort operators is removed in an optimizer.

Test build #54309 has started for PR 11997 at commit a035564.

Test build #54309 has finished for PR 11997 at commit a035564.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54309/
Test FAILed.

I found we could't check a global sort of all partitions from SprakPlan#outputOrdering, so I'll fix this soon.

Test build #54502 has started for PR 11997 at commit ccaf5f5.

Test build #54503 has started for PR 11997 at commit 18a2e93.

Test build #54502 has finished for PR 11997 at commit ccaf5f5.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SortOrder(child: Expression, direction: SortDirection, global: Boolean = false)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54502/
Test PASSed.

Merged build finished. Test PASSed.

Test build #54503 has finished for PR 11997 at commit 18a2e93.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SortOrder(child: Expression, direction: SortDirection, global: Boolean = false)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54503/
Test PASSed.

Merged build finished. Test PASSed.

Close this for now, and if needed, I'll reopen this.


[Long-Term] Hardware Rendering.

As in using DirectX or OpenGL (Or Vulkan) to drastically speed up rendering.
Obviously this a very long term goal, but could be very beneficial.
Preferably this could be changed at runtime (So if an editor was made then it would be easier to change the Renderer).
If you like I could start working on this, but it may take ages...

In this kind of situation I would much prefer OpenGL over DirectX. I think this is a good goal to work towards long term, but I don't intend to actively work on this right now. I do know of a good C# wrapper for OpenGL: OpenTK so maybe we can use this when we finally rewrite.

Thats good as I have a lot more experience with OpenGL.
OpenTK is the framework that I have worked with in the past and is more C#'y (Object Orientated etc..).
I think it also has support for embedding in Forms so could be used in an editor.

I have used it embedded in Forms before and its a super painless process. I also know of a syntax highlighted textbox, if your interested in an editor. Should be fairly simple to whip up

I've created a new repo (neon2d/neonGL) for this project. My goal is to recreate all current functionality with a different renderer, then we can see about combining them.


use DOTNET_ var in test

Why do you think this is a valid change? Do you have any documentation to support it?

Got it, thanks!


Need to save the settings to see the correct output example language

If i hover the mouse over the Full format is doesn't matter what i set the Locale language to, it will still show the output example in the language it was when i first opened the page.

I changed the language from Afrikaans to English (you can't see that because it is behind the example dialog), but as you can see it will not change language. To see the output example i'm forced to save the page and reopen it to see the selected language.
Btw, i have no idea why it is set to Afrikaans, but it will show the correct date on the dashboard.

Dashboard

Webmin 19.70
Authentic theme 19.70
Firefox 84

Update: It seems that i need to press on the page before the output example language will change.
Another thing i noticed was that I need to press twice on the language dropdown menu for it to expand.

Update: It seems that i need to press on the page before the output example language will change.
Another thing i noticed was that I need to press twice on the language dropdown menu for it to expand.

@iliarostovtsev this looks like part of the UI that the theme controls?

@iliarostovtsev this looks like part of the UI that the theme controls?

@iliarostovtsev this looks like part of the UI that the theme controls?

Yes, Jamie.

Update: It seems that i need to press on the page before the output example language will change.

Yes, at the moment but this will be fixed for 19.71. I have just improved it -- you can install latest development version of the theme to give it a try now. I hope you'll like it.
Thanks for reporting such little things, as I also believe that those little things make overall UX great.

@iliarostovtsev this looks like part of the UI that the theme controls?

Yes, Jamie.

Update: It seems that i need to press on the page before the output example language will change.

Yes, at the moment but this will be fixed for 19.71. I have just improved it -- you can install latest development version of the theme to give it a try now. I hope you'll like it.
Thanks for reporting such little things, as I also believe that those little things make overall UX great.


merging new package features into master

moving weather API to core
new audio visualizer (not optimized yet but functional)
bare bones of socket communication between python and Unity C#
removed tflite package from submodule and use it as a git package instead
removed barracuda (for now)

Weather API script kinda useless but thx for moving it to core. :)