⚠ Bofrost.de has degraded performance

In 1512ed0, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 958 ms

Resolved: Bofrost.de performance has improved in 52d68aa.


Only print message for get_modified_time() failure when in verbose mode

This error message was often displayed for no good reason when PCK files were loaded in the editor.
Since file modification dates are secondary metadata, it's not very important if it can't be retrieved successfully anyway.
This closes https://github.com/godotengine/godot/issues/25318.

Thanks!

Cherry-picked for 3.5.

Cherry-picked for 3.4.1.


Favor HTTPS URLs - the GNU edition

Motivation for this change
GNU / Savannah / NonGNU domains always offers HTTPS and often there is even a redirect from plain http to https. So let's save a redirect to users (and Hydra) when following a link to an homepage or to a source tarball. It also updates links in the doc.
More details in the commit messages.
+ a bonus on a small number of SourceForge URLs that were left before
Related: #13809 / #50989
/cc @markuskowa @Infinisil @ryantm
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

I guess the mass rebuild is caused by changing the URLs in the some of the patches. If you want to keep that it should maybe go in to staging.

No the point is not to trigger a mass-rebuild. I'll undo the changes on patches, it's not necessary and not the important part.

There! Now we have something practical to work with.
(sorry for the noise)


Note regarding MyVaillant

Today I found https://github.com/TA2k/ioBroker.vaillant/commits/master which provides similar functionality for iobroker.
They seem to have added support for the MyVaillant API.
Of course this isn't an issue with this repo, but I thought creating an issue is one way to keep you informed.

https://github.com/signalkraft/mypyllant-component
@hvbargen I built a proof-of-concept component for myVAILLANT based on the repo you linked, as well as some reverse engineering I did on a rooted Android device. It's very alpha compared to @thomasgermain's component, but works for my particular setup. For other combinations of Vaillant components it will probably fail in exciting ways.


(Bug) standalone FV flow not working in metamask/valora in-app browser

Description
There seems to be some kind of a loop asking for browser camera permissions. even if I press allow it keeps asking for it.
Second time i've tried it asked me only twice, but then after pressing "got it" it just gets stuck trying to load the facetec UI
Steps to reproduce
ON ANDROID

open metamask
switch to non-whitelisted account
in metamask inapp browser go to gooddapp.org
press claim
sign FV
try to allow camera and to press "got it"

Edit
This is probably similar issue that unsupported browsers face with facetec.
I've used the app "webview test" from playstore and i'm able to reproduce the issue that the chinese browsers have.
I suggest that we detect "webviews" or unsupported browsers and ask users to continue on the native browser.
This is specifically important for the standalone FV.
See supported "mobile browser":
https://dev.facetec.com/compatibility#compatibility-matrix
New flow

detect webview (or iframe on desktop) on FV start screen
if on webview show modal

please copy the link and open it in your native browser.
button to copy link

important on FV standalone the link copied should be the original link including the user signature.

@patpedrosa

@patpedrosa

I don't know how they work exactly. But it might be that Chinese (or equivalent) browsers are a web view....
Yes we could and it might make more sense to do.
2a. but what do we do about users who cannot download the app or one of the 2 supported browsers?

@L03TJ3 The white screen on QA env after pressing the pass FV button
https://images.zenhubusercontent.com/166818382/93bd6c5f-8918-4b55-87c6-1b733345f6f9/c04488dc_75f8_486e_834c_e6f831de9248.mp4

fixed here: https://github.com/GoodDollar/GoodDAPP/commit/75c11ff66dd2d89aebef0f7bc36e0f0c063e72bb

@L03TJ3 didn't help, still white screens on both iOS and Android

@vldkhh and me now both verified it did work.
goodid did not release properly

verified on prod

@patpedrosa @L03TJ3
The second button should be, "try anyways" or something. because some webviews might be working.

@patpedrosa @sirpy Maybe it can be just something simple as 'Understood'

verified on prod


rustfmt output wrong path on windows

run rustfmt --write-mode=diff on windows
the correct output should be Diff in \D:\project\rust\test\src\network.rs at line 102:
but I got the following
rustfmt --write-mode=diff src\network.rs
Diff in \\?\D:\project\rust\test\src\network.rs at line 102:

     pub fn recv_message(&mut self) -> Result<String> {
         let msg = self.client.read_message()?;
-        match msg {
-        }
+        match msg {}
     }

     pub fn close(mut self) -> Result<()> {
Diff in \\?\D:\project\rust\test\src\network.rs at line 109:
         self.client.close(None)?;
-         Ok(())
+        Ok(())
     }
 }

why \\? is prefixed? \\?\D:\ is not a valid path

According to https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#maxpath, a \\? prefix is valid.

To specify an extended-length path, use the "\\?" prefix. For example, "\\?\D:\very long path".

It is strange to me, too. But it is valid...

In any case, we are just using Path::display(), so if this is a bug it is with std.

Sure, I didn't know that \? is a valid windows path. This should be not a issue. Thanks!


Update the title of the Advanced Carousel section of the Carousel demo page

The current title of this section is too long:

This title should be changed to Advanced.
The demo file name is BitCarouselDemo.razor in the Bit.BlazorUI.Demo.Client.Core project.

not relevant anymore!


Compilation error on MSVC 19.36

I'm in the process of adding proxy to Conan Center Index (https://github.com/conan-io/conan-center-index/pull/22362) and a test build of proxy v2.1.0 against a copy of the main.cpp example provided in the repo fails on MSVC 19.36.32532.0:
proxy/proxy.h(622,45): error C3546: '...': there are no parameter packs available to expand
proxy/proxy.h(624,2): message : see reference to class template instantiation 'pro::details::combined_dispatch_prototype<Ds...>' being compiled

Full log:
======== Input profiles ========
Profile host:
[settings]
arch=x86_64
build_type=Release
compiler=msvc
compiler.cppstd=20
compiler.runtime=dynamic
compiler.runtime_type=Release
compiler.version=193
os=Windows

======== Testing the package: Building ========
proxy/2.1.0 (test package): RUN: cmake -G "Visual Studio 17 2022" -DCMAKE_TOOLCHAIN_FILE="C:/J2/w/prod-v2/bsr/cci-b6f0142c/recipes/proxy/all/test_package/build/msvc-193-x86_64-20-release/generators/conan_toolchain.cmake" -DCMAKE_INSTALL_PREFIX="C:/J2/w/prod-v2/bsr/cci-b6f0142c/recipes/proxy/all/test_package" -DCMAKE_POLICY_DEFAULT_CMP0091="NEW" "C:\J2\w\prod-v2\bsr\cci-b6f0142c\recipes\proxy\all\test_package"
-- Using Conan toolchain: C:/J2/w/prod-v2/bsr/cci-b6f0142c/recipes/proxy/all/test_package/build/msvc-193-x86_64-20-release/generators/conan_toolchain.cmake
-- Conan toolchain: C++ Standard 20 with extensions OFF
-- The CXX compiler identification is MSVC 19.36.32532.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.36.32532/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Conan: Target declared 'msft_proxy'
-- Configuring done
-- Generating done
-- Build files have been written to: C:/J2/w/prod-v2/bsr/cci-b6f0142c/recipes/proxy/all/test_package/build/msvc-193-x86_64-20-release

proxy/2.1.0 (test package): Running CMake.build()
proxy/2.1.0 (test package): RUN: cmake --build "C:\J2\w\prod-v2\bsr\cci-b6f0142c\recipes\proxy\all\test_package\build\msvc-193-x86_64-20-release" --config Release
MSBuild version 17.6.3+07e294721 for .NET Framework

  Checking Build System
  Building Custom Rule C:/J2/w/prod-v2/bsr/cci-b6f0142c/recipes/proxy/all/test_package/CMakeLists.txt
  test_package.cpp
C:\J2\w\prod-v2\bsr\75336\ccfff\p\proxy5414b57492048\p\include\proxy/proxy.h(622,45): error C3546: '...': there are no parameter packs available to expand [C:\J2\w\prod-v2\bsr\cci-b6f0142c\recipes\proxy\all\test_package\build\msvc-193-x86_64-20-release\test_package.vcxproj]
C:\J2\w\prod-v2\bsr\75336\ccfff\p\proxy5414b57492048\p\include\proxy/proxy.h(624,2): message : see reference to class template instantiation 'pro::details::combined_dispatch_prototype<Ds...>' being compiled [C:\J2\w\prod-v2\bsr\cci-b6f0142c\recipes\proxy\all\test_package\build\msvc-193-x86_64-20-release\test_package.vcxproj]

GCC, Clang and AppleClang built without issues in the CI.

Thanks for the information. We have updated the implementation. Please try 2.1.1.


Respect Terrain Height?

I'm trying to create a new map with the new map editor, but the image overlay is cut off by higher terrain areas.
Is there a way to have the mod respect the map terrain, or alternatively add a setting to align the height of the overlay? Thx!

Projecting the overlay onto the terrain is planned, but is not a trivial task (and may not be able to happen due to the challenges involved).
You can change the elevation of the overlay by using the elevation change keys mentioned on the README, or by using the slider in the mod's options panel.


Basic auth no longer working with 0.7

I've just upgraded to .7, and Basic Auth seems to have stopped working.
    'auth' => [
        'basic' => function ($app) {
            return new Dingo\Api\Auth\BasicProvider($app['auth'], 'email');
        }
    ],

I've got a web page login working, using standard Laravel Auth, however all requests sent to protected routes seem to be failing.
$ curl -X POST --user my.email@gmail.com:password http://myapp.app:8000/api/components
{"message":"Invalid authentication credentials.","status_code":401}

Using the same credentials works via the 'web login', also had this working yesterday too before upgrading. Am I missing something?
Laravel 4.2 by the way.

I'm having the same issue. No matter what I try, I can not use the laravel 4.2 basic auth functionality.
I protected my route in the constructor and this is the response after making a post request with postman:
{"message":"Invalid authentication credentials.","status_code":401}
I'm using 0.8.2


Implement  a nav bar for sessions/tracks

Currently there is no navbar on sessions/tracks pages and it becomes difficult to navigate through the sessions without a navbar. We could take inspiration from eventyay navbar from the link given below, on the webapp they are datewise so there would be an option to select the date and then the navbar would display the corresponding tracks according to the selected tab on navbar.

Eventyay sessions page : https://eventyay.com/e/18252ab6/sessions/
PS: If the issue seems valid, I would like to work on this.

@CosmicCoder96 Great idea!!.

@aayusharora on smaller screens, it can be a fixed width scrollable (scrollable to right or down whichever works best ) Navbar so it doesn't cover the entire screen area. How does that sound? I'm on working on one and will give you a demo as soon as I can.

@CosmicCoder96 Sounds good. Suggestion is to post the proposed UI before coding it.

@aayusharora I have made a PR #967 , there is a live link to preview as well, you can see the UI there.


Add my name to Contributors.md

@plemomay, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added Facebook share and tweet feature to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

Honestly, I edited the file and make a pull request on a GitHub website directly (which is very easy).
So I don't have any problem making a pull request on this repo.
However, I'm so excited that you've merge my pull request! I've created many pull request and this one is the first one that is merged. Thank you for merging my pull request.
Ps. I suggested that there should be an easy step to do a pull request on GitHub website only (as I did) so the beginners might not have to install git or others before making their first pull request.


Update to heapster version v0.7.

Added the new label required for cluster addon services.
Made Grafana UI accessble via the proxy on the api-server.
Tested using the e2e test.

LGTM
This partially addresses #4620

Coverage remained the same at 53.84% when pulling e2cdcad5555103362e9509edec3e711df2c872ef on vishh:monitoring_rc into 984fb2e6754207d3803dc9c3681a507e8aec0002 on GoogleCloudPlatform:master.


update reference to conform to literature database

New PR into the correct repo! For https://agr-jira.atlassian.net/browse/SCRUM-1142

@azurebrd are you saying there should be a slot date_last_modified_in_pubmed still?

@dougli1sqrd There will eventually need to be a change from date_last_modified to date_last_modified_in_pubmed once the database and API change to match.  So, more of a heads up that it will change, but it hasn't yet.

@azurebrd - I added a few notes in the LinkML that explains how currently the date_last_modified should be renamed to date_last_modified_in_pubmed.

@gildossantos I see it, thanks Gil !


Is there a method to reduce/remove the [YAD-PLUGIN] logging information in the build log?

Hi,
I would like to know if there is a way to reduce the level of logging output in the build log itself.
I would like to remove the ..
[YAD-PLUGIN] Injecting DOCKER_CONTAINER_ID variable.
For example and only keep the build information.
Thanks.

Yes, it possible... DockerEnvironmentContributor needs change, but this information was used in test, so test need to be adjusted also...

There were change before and variables are printed only when they are enabled for Node variables insertion.


'1' is considered a branch with the mass scan supercuts

The following branches have been skipped...
1

Done in b571b0db


demos: Increase the executable permissions

Add executable permissions to the buildah-bud-demo.sh file.
Signed-off-by: Zhou Hao<EMAIL_ADDRESS>

LGTM
@TomSweeneyRedHat PTAL

LGTM, thanks for the touch up @q384566678 !

@rh-atomic-bot r+


Allow Module Augmentation of ZodiosEndpointDefinition

I want to enforce aliases on all endpoints but can't without playing fun typescript games. By converting the ZodiosEndpointDefinition type to an interface, this can now easily be done with module augmentation.
In addition to being able to modify which fields are required, additional fields could be added. This can be useful if a developer wanted to reuse the endpoint definitions for other purposes and needed additional meta data that wasn't provided by zodios out of the box.

Thanks, great idea!


Proposal: Have a UI variant app that hides the fact we're DDoSing

Hi,
This is actually a serious proposal. After trying to get a lot of my contacts to contribute, many of them had concerns for their safety, even through VPNs. If you were to make the software available as a "DEFENSE" variant, which would do the same thing, but without the user knowing, then this could serve as a legitimate counter argument. I realize this would essentially trick our users, but at the same time this would make the supplier the criminal, not the user, getting more people to use it.

Best,
turtle
PS: I really admire your work and try support you through every means I can.

In new version we removed log from GUI. Is it will be enough?

It is what it is.
User should understand the purpose and how it works.
"trick our users"

really bad idea. One lie usually causes another.


[Legacy DB] update uri for models table

old uri project_3/models/job_151_7_1.mod
add 3 new columns to support uri combining

uri_param1 (tinyint) - 151

uri_param2 (tinyint) - 7

uri_param3 (tinyint) - 1

remove old uri column

update arbimon-jobs repo to support this logic

the size of the table is 0.64 MB. it is not worth cleansing at the moment.


fix: Kafka external stream virtual columns

PR checklist:

Did you run ClangFormat ?
Did you separate headers to a different section in existing community code base ?
Did you surround proton: starts/ends for new code in existing community code base ?

Please write user-readable short description of the changes:
closes #55
refs #175
Fixed virtual columns in Kafka external streams:

_tp_time now always has a value
_tp_append_time is set only when message timestamp is an append time
all time columns has DateTime64 type
if a virtual column is explicitly defined an a pyshcial column, it should be respected

(Jove Github Bot) added it to the current sprint.

(Jove Github Bot) moved this ticket out of the GitHub project(up to 1200 tickets for one project).


NETEXP-898: Increase the waiting time before terminating the websocket

NETEXP-898: Increase the waiting time before terminating the websocket
Signed-off-by: Ammad Rehmat<EMAIL_ADDRESS>

Thanks Ammad, merged.

Thanks Ammad, merged.


Thank you for contributing to Doom!

Before you submit this PR, please make sure it is targeted at develop, not
master (unless this is a fix for a critical error). Then replace this message
with a description of your changes.

Woops! Wrong repo. Apologies.


highscore doesnt behave properly

as you can see in this vid, my highscore in week 3 is 179507, but when i enter and then exit out of the stage, it suddenly changes to 179510
https://user-images.githubusercontent.com/48515908/128623179-e066d14d-597c-44b2-bad7-09dc839359c6.mp4

update : found another way of doing this, so i scrolled to week 3, and then week 4, and then week 3 again, and the week 3 score wasnt the same as before i scrolled to week 4
https://user-images.githubusercontent.com/48515908/128665782-1463fe39-c3df-4afb-a5f8-9dd9a3e49e93.mp4

Fixed on release 0.3: https://github.com/ShadowMario/FNF-PsychEngine/commit/560b66e2f7fff01d2668138ef0e8e72340bd5b03
Thank you for reporting this issue.


[sending] Add support for 'sending'

This PR adds support to the compiler for 'sending'. It does not completely remove 'transferring' (since it may already be used). Instead what it does is:

Internally except for in the parser and the clang importer, we only represent
'sending'. This means that it will be easy to remove 'transferring' once enough
time has passed.

I included a warning that suggested to the user to change 'transferring' ->
'sending'.

I duplicated the parsing diagnostics for 'sending' so both will still get
different sets of diagnostics for parsing issues... but anywhere below parsing,
I have just changed 'transferring' to 'sending' since transferring isn't
represented at those lower levels.

Since SendingArgsAndResults is always enabled when TransferringArgsAndResults
is enabled (NOTE not vis-a-versa), we know that we can always parse sending. So
we import "transferring" as "sending". This means that even if one marks a
function with "transferring", the compiler will guard it behind a
SendingArgsAndResults -D flag and in the imported header print out sending.

rdar://128216574

@swift-ci smoke test

I think this also needs a corresponding parser change in swift-syntax.

apple/swift-syntax#2658
@swift-ci smoke test

https://github.com/apple/swift-syntax/pull/2658
@swift-ci smoke test


Trainer module

I am not able to run the file. It shows
ModuleNotFoundError: No module named 'chatterbot.trainer'
I also used this command: pip3 install chatterbot.trainer

You just left out "s" on trainer,

chatterbot.trainers

so your import would look like
from chatterbot.trainers import ListTrainer


fiona._err.CPLE_OpenFailedError: '......auxiliary_data/Elbe.shp' not recognized as a supported file format.

Describe the bug
When checking that basic examples works OK, I got the error in the title, with the extract_shape example
The context is :
 File "fiona/_shim.pyx", line 83, in fiona._shim.gdal_open_vector   File "fiona/_err.pyx", line 291, in fiona._err.exc_wrap_pointer fiona._err.CPLE_OpenFailedError: '/home/ssenesi/EVT/livrable1/recipe_extract_shape/auxiliary_data/Elbe.shp' not recognized as a supported file format.
I actually took care of downloading all shape data formats, as indicated, and put them all in the auxiliary data dir
I am using version v2.0.0b9, at commit 9f4553e
I do attach

The main_log_debug.txt file, main_log_debug.txt

Github doesn't allow to attach a yaml file, so please refer to the recipe given under link examples, above (I didn't modify it)

It looks like some problem with fiona. Could you try a fresh installation as described here (just create a completely new conda environment)? v2.0.0b9 of ESMValCore was released over a year ago.

The other possibility is that something went wrong with the download and Elbe.shp is broken. You could try to see if the file can be opened with other software, for example qgis.

@senesis Have you had any success with a more recent version of the tool? Is this still a current problem?

It's worth pointing out that the report here at the top tells us that gdal was involved in the loading. We have had and resolved a number of problems with regards to gdal and fiona recently, so I have good hopes that the issue does not exist anymore.

@senesis Have you had any success with a more recent version of the tool? Is this still a current problem?

The recipe runs successfully with V2.4.0


remove metrics container

https://github.ibm.com/IBMPrivateCloud/roadmap/issues/58304

This metrics is unexposed outside and un-used, Hence removing this to contribute to Foot-print reduction

$ oc get pods |grep mongo
ibm-mongodb-operator-5cf976cfd4-hcnrf                   1/1     Running     0          73m
icp-mongodb-0                                           1/1     Running     0          73m
Tirumalas-MBP:ibm-mongodb-operator tirumalamannaru$


Aws prw exporter

Description:
This PR introduces a new exporter that leverages the existing Prometheus Remote Write Exporter in the core collector repo, and adds AWS Sigv4 authentication logic to it.
The idea here is to add an interceptor to the http client that is used to initialize the Prometheus Remote Write Exporter struct. The interceptor handles the Sigv4 logic, and the rest of the logic is identical to the core exporter.
The way this is designed, any changes in the core exporter's config will need to be duplicated here, however any other changes in the core exporter should be fine.
This PRs size is significantly bloated by the go summary file
Link to tracking Issue:
No direct issue for this exists but it is related to vendor specific code discussion: https://github.com/open-telemetry/oteps/issues/141
Testing:
Unit tests have been added for the factory and config. Testing the authentication logic has been done manually by setting up a pipeline to communicate with AWS services.
Documentation:
A thorough README.md is included, as well as all example configuration in testdata/config.yaml

All comments have been resolved and PR has been merged upstream


Install and configure OpenTSDB

Adds configuration to pull down the OpenTSDB deb file from the Github repo and store it on the bootstrap's apt mirror
Adds a new bach_opentsdb cookbook for installing and configuring OpenTSDB

Writes out all important configuration files / init-related scripts, some are hardly modified
Manages the service and uses the already installed JDK
Configures Kerberos authentication parameters + jaas config for secure clusters - not currently flaggable using an attribute - possible future todo to make this more easily utilized by others with unsecured clusters?
Intializes HBase tables using the default table creation script - another possible future todo is to modify the script and allow custom table names other than the defaults

But does it blend? Early results say no.

Marked this one as to-backport, even though it feels like a feature to me. I can remove that tag if it's too much to backport, but OpenTSDB in its current state doesn't modify existing services other than talking to them, so it should be safe enough after reviews.

Looks good, do you want to add it to a specific role?

Noce work on the coolbook Sal; this looks really good!

Note I'll be cherry-picking this change to release-3.0 already and just mark review areas with FIXME and TODO comments.

gnuplot doesn't seem to be installed as a depency of the debian package.
nice: gnuplot: No such file or directory

Do we want to be plotting the graphs on the main OpenTSDB dashboard? Or will it be just purely for APIs?

Ok, @pu239ppy / @aespinosa / @cbaenziger - I think all review comments have been addressed. Please see the latest commit for those changes, and let me know if you see any other places I can make improvements. Thanks!


Stats-related changes in aggregation tool and health report

create separate job for each type of stats in aggregation tool
add config to specify which type of stats will be collected
tweak account/container string to avoid exceeding znode limit

Codecov Report

Merging #1135 into master will decrease coverage by 0.07%.
The diff coverage is 26.08%.

@@             Coverage Diff              @@
##             master    #1135      +/-   ##
============================================
- Coverage     68.84%   68.76%   -0.08%
+ Complexity     5085     5081       -4
============================================
  Files           397      397
  Lines         31744    31747       +3
  Branches       4058     4061       +3
============================================
- Hits          21853    21831      -22
- Misses         8822     8838      +16
- Partials       1069     1078       +9

Impacted Files
Coverage Δ
Complexity Δ

...main/java/com.github.ambry.server/AmbryServer.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ain/java/com.github.ambry/config/ServerConfig.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ry/clustermap/HelixClusterWideAggregationTool.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...main/java/com.github.ambry/server/StatsHeader.java
100% <100%> (ø)
4 <0> (ø)
:arrow_down:

...java/com.github.ambry.server/AmbryStatsReport.java
77.27% <100%> (+2.27%)
7 <2> (+1)
:arrow_up:

...in/java/com.github.ambry.store/BlobStoreStats.java
71.48% <71.42%> (ø)
106 <0> (+1)
:arrow_up:

...ain/java/com.github.ambry.server/StatsManager.java
76.22% <80%> (+0.16%)
24 <0> (ø)
:arrow_down:

.../main/java/com.github.ambry.router/EncryptJob.java
92.1% <0%> (-5.27%)
4% <0%> (-1%)

...github.ambry.rest/AsyncRequestResponseHandler.java
87.62% <0%> (-3.26%)
23% <0%> (ø)

...java/com.github.ambry.store/CompactionManager.java
86.75% <0%> (-2.65%)
19% <0%> (ø)

... and 7 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 d94ae5f...bdca5bc. Read the comment docs.


fix

Closes #102
Description of changes:
Explicitly specify tokenizer for SentenceSplitter of llamaindex
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi!
I'm trying to understand why this function as tokenizer.. could you explain?
https://github.com/aws-samples/bedrock-claude-chat/blob/7776cc8c89166407efd96714422fdb3963165b5e/backend/embedding/main.py#L114
Thanks in advance,
Best regards.

Due to llamaindex implementation. The code on L114 is equivalent to like len(text).


Spacing between rows is to big (bigger than the examples)

too much space between the rows make the car a bit clumbsy. See my card below:

However, The example shows a much smaller row space:

Hi, you need to change your cards layout to large, you can do that in the editor.


Newbie question about listeners

Hi, thank you for the script.
I'm a blind, french speaking Python coder specialized in accessibility for visually impaired musicians. I want AbletonOSC to listen to track or scene change and send back the track/scene id so I can trigget a get command.
Is there a listener I can enable that fits that purpose? Something that sends the scene and track index of the highlighted clip_slot?
Right now, I can only do it by using a loop with timeout but I don't feel it's a good (and CPU efficient) approach. I would prefer Live to send that trigger.
Thank you very much for your help.

Hi betov75,
Apologies for the delay, I am away at the moment without much internet
access. This should be possible and I would love to help; I will be back in
10 days and will reply properly then, and perhaps we could have a zoom call
to chat further. Thank you for your patience!
best wishes,
Daniel
On Mon, 8 May 2023 at 10:45, betov75 @.***> wrote:

Hi, thank you for the script.
I'm a blind, french speaking Python coder specialized in accessibility for
visually impaired musicians. I want AbletonOSC to listen to track or scene
change and send back the track/scene id so I can trigget a get command.
Is there a listener I can enable that fits that purpose? It'll help me
send text to speech output with Track and scene info each time a
scene/track change occurs.
Right now, I can only do it by using a loop with timeout but I don't feel
it's a good (and CPU efficient) approach. I would prefer Live to send that
trigger.
Is there, also, a way to listen to play/stop states?
Thank you very much for your help.
—
Reply to this email directly, view it on GitHub
https://github.com/ideoforms/AbletonOSC/issues/85, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACJZ3QDQHZ2EQKQO6ELDMDXFEPLNANCNFSM6AAAAAAX2FZSFU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Daniel Jones
web: www.erase.net
mastodon: @.***
twitter: @ideoforms https://twitter.com/ideoforms
(+44) 07855 449 735

@betov75
Back from travels now — mind dropping me a note on my email address so we can set up a call?
cheers!


Remove flowtype/require-valid-file-annotation temporarily.

Until this issue (https://github.com/gajus/eslint-plugin-flowtype/issues/165) is fixed we're disabling flowtype/require-valid-file-annotation.
(For future tracking this came out of a twitter thread: https://twitter.com/robdel12/status/866073982801502209)

Thanks!

Should be fixed in<EMAIL_ADDRESS>Please verify!


Synchronize Agent ID and container name

What's done:

Add container name to agent entity

Please support this logic in kubernetes profile too; there name and ID can simply be equal and set in KubernetesManager into agent's env

Do you mean agentIdEnv? But I don't see any suitable fields in EnvVar()

Please support this logic in kubernetes profile too; there name and ID can simply be equal and set in KubernetesManager into agent's env

We use Pod::metadata.name, but there is Pod::metadata.uid. Looks like we already put docker's analog of docker's name and kubernetes api uses Pod::metadata.name.
We can:

store Pod::metadata.name as container_id and container_name
or remove container_id at el and store docker's name only and get container by:

private fun getContainerIdByName(containerName: String): String = dockerClient
    .listContainersCmd()
    .withNameFilter(setOf(containerName))
    .exec()
    .firstOrNull()
    ?.id
    ?: throw NotFoundException("There is no container with name $containerName")

@petertrr what do you think about it?


BEP: DICOM "file-format" support

I think GitHub issues do not provide adequately powerful medium to discuss complex topics due to single threading etc. In DataLad, DANDI and other projects we adopted an idea of introducing "design documents" which take advantage from "code review" functionality of the GitHub by allowing for context-specific comments or recommended changes.
Hence I am submitting this PR to seek further discussion and improvements to the idea of such a BEP first.
Instructions for readers: click on :+1: or :-1: to express your opinion on overall idea
TODOs

[ ] Allow for period of discussion/improvement
[ ] File/mint an official BEP if the idea finds some support

This was mentioned as related in the BIDS OHBM town hall: https://github.com/ismrmrd/ismrmrd

@arokem - i believe the scope of that file format was specifically for k-space data.

A clear case of "one person's raw data is another person's product"

The idea of dropping nifti and moving over sounds appealing to me, yes. But... that would require all(/most) common neuroimaging packages that even do not support BIDS out of the box (e.g. FSL) + the existing bidsapps to switch over to DICOM. I think hell will freeze over before that happens, while in the meantime we would create more chaos/incompatibilities...


python train.py --dataset_path D:\CutPaste-main\mvtec\train\ --num_class 3

Is the raw data set format,I'm confused. What's the reason?I hope I can give you some solutions in your busy schedule.

@xaioffff check your dataset structure. You should have something like this:
mvtec
│   readme.
│   license.txt
│
└─── bottle
│   │   readme.txt
│   │   lisence.txt
│   │
│   └─── ground_truth
│   |   └─── broken_large
│   |   └─── broken_small
│   |   └─── contamination
│   |
|   └─── train
|   |     └─── good
|   |       |  000.png
|   |       | ...
│   |
|   └─── test
|   |     └─── broken_large
|   |     | |  000.png
|   |     | |  ...
|   |     └───   broken_small
|   |     | |  000.png
|   |     | |  ...
|   |     └───   contamination
|   |     | |   000.png
|   |     | |  ...
|   |     └───   good
|   |     | |  000.png
|   |     | | ...
└─── cable
| ...
└─── zipper
In the command, you should specify the path like this ./mvtec/bottle/train. It trains model for each class separately/

@xaioffff check your dataset structure. You should have something like this: mvtec │ readme. │ license.txt │ └─── bottle │ │ readme.txt │ │ lisence.txt │ │ │ └─── ground_truth │ | └─── broken_large │ | └─── broken_small │ | └─── contamination │ | | └─── train | | └─── good | | | 000.png | | | ... │ | | └─── test | | └─── broken_large | | | | 000.png | | | | ... | | └─── broken_small | | | | 000.png | | | | ... | | └─── contamination | | | | 000.png | | | | ... | | └─── good | | | | 000.png | | | | ... └─── cable | ... └─── zipper
In the command, you should specify the path like this ./mvtec/bottle/train. It trains model for each class separately/

I looked at the previous question.It has also been changed in accordance with your requirements.But it still doesn't solve the problem.Am I using python3.6, cuda10.1?I use Windows

@xaioffff check your dataset structure. You should have something like this: mvtec │ readme. │ license.txt │ └─── bottle │ │ readme.txt │ │ lisence.txt │ │ │ └─── ground_truth │ | └─── broken_large │ | └─── broken_small │ | └─── contamination │ | | └─── train | | └─── good | | | 000.png | | | ... │ | | └─── test | | └─── broken_large | | | | 000.png | | | | ... | | └─── broken_small | | | | 000.png | | | | ... | | └─── contamination | | | | 000.png | | | | ... | | └─── good | | | | 000.png | | | | ... └─── cable | ... └─── zipper
In the command, you should specify the path like this ./mvtec/bottle/train. It trains model for each class separately/

I looked at the previous question.It has also been changed in accordance with your requirements.But it still doesn't solve the problem.Am I using python3.6, cuda10.1?I use Windows

I see. The reason may be in os differences.
In dataset object we have
if self.train_images and self.mode == 'train':             self.images = glob(self.train_images + "/*")
where "/*" may not work in Windows. You can change that part, use pathlib  instead of glob , it may solve your issue

The result of the required substitution is

I really appreciate your patience。But I'm very sorry it still doesn't work


Update hw models nrf

[nrf fromlist] manifest: Update nRF HW models to latest
The nRF HW models have been updated to include the following
fixes and improvements.

PPI: add support for nrf_ppi_group_enable
BLECrypt: Widen search for crypto library
Makefile: Switch to gnu11 from c11 due to HAL
NVMC: Minor fixes in command line options descriptions

Which enable more 15.4 functionality with the nrf driver
Upstream PR: https://github.com/zephyrproject-rtos/zephyr/pull/58745

[nrf fromtree] manifest: nrf hw models: Use latest w flash
Update to the latest NRF HW models which include
models of the NVMC and UICR peripherals,
as well as some other (very) minor fixes.
(cherry picked from commit https://github.com/nrfconnect/sdk-zephyr/commit/e7d658c91d19790f03d944b5f6a4581c1ea50522)

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

nrf_hw_models
https://github.com/zephyrproject-rtos/nrf_hw_models/commit/bad9877e997b2c2a78dd74eec8978181f4655d14
https://github.com/zephyrproject-rtos/nrf_hw_models/commit/37c571ef7c4a86dad852566fc43eb36f42534e9f (master)
<EMAIL_ADDRESS>

Note: This message is automatically posted and updated by the Manifest GitHub Action.


Change plotly_express to plotly

plotly_express is deprecated; correct syntax is import plotly.express as px

Closed by 482


add bigtable support for per-operation options

Add an Options options = {} argument to the constructor of the client class(es).  Merge these options with the default options for the service, and store them as a member of the client class.
Add an Options options = {} argument to each operation within each client.  These options should then be merged with the client options from above, and installed as the prevailing options for the duration of the operation by instantiating an internal::OptionsSpan.
You could then use internal::CurrentOptions() to obtain (a const& to) the prevailing options from anywhere you might need them.  Any cleanup for call paths where Options have been passed explicitly is discretionary.
Similar support for the generated client classes was added in #7683, so you might be able to use that as an example.

Note: The options stored in the client class should now include the connection->options().  So something like ...
ServiceClient::ServiceClient(std::shared_ptr<ServiceConnection> connection, Options opts = {})
    : connection_(std::move(connection)),
      opts_(internal::MergeOptions(std::move(opts),
                                   service_internal::DefaultOptions(connection_->options()))) {
  ...
}

T ServiceClient::Operation(..., Options opts = {}) {
  internal::OptionsSpan span(internal::MergeOptions(std::move(opts), opts_));
  ...
}

Addendum: Please also ensure that the OptionsSpan instantiated during ServiceClient::Operation() is saved and then restored over any work done on behalf of the operation but after Operation() returns.  Typically this means for async, paginated, or streaming RPCs.  (These cases may already be handled via changes in the common library.)


About the PR cureve of Fig. 4 in the paper

Hello, @hogyun2 @sparolab ,-I really appreciate for your work！Congratulations :)
The PR cureve of Fig. 4  in the paper look great. Currently I want to try to implement them but I failed. Is it convenient to provide the relevant implementation code?Of course, detailed guidance would be better.
I am always looking forward to your kind response.
Best regards.

Thank you for your interest. :)
We don't provide code for PR curves. However, when ground truth exists for the dataset, if you know the number of revisited places, you can draw the precision and recall.
If you change the threshold of each cosine distance and find the precision and recall, you can depict the pr curve.

Hello, @MAX-OTW, thank you for your interest :).
Maybe, this link(https://github.com/ameya98/pr2roc/blob/master/demo.ipynb) will be helpful for your reference.
Sincerely,
Hogyun Kim


set stylus as a peer dependency

The version of stylus has to keep being updated and there is a constant mismatch between the latest and the version in this module. Currently the version in this module does not support sourcemaps, while the latest does. The second you add nib to a project your sourcemaps go out the window. This could all be solved by using peer dependencies or using a more laid back range for stylus.

that sounds like a good idea, wanna submit a PR?

+1, solves #301

+1

Seems sytlus is not yet a peer dependency because of https://github.com/tj/nib/pull/297


Adding Project Paradise - CHI Token to Solana Token List

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

So I am seeing "unsupported file modified: /Moneda_1.png b/assets/mainnet/ARg9wfeLN4qZTxgYTYeuGtGFMmYdk5zFhBuSnTfXXUvb /Moneda_1.png", is this because "First-time contributors need a maintainer to approve running workflows. Learn more." or because of the unsupported file?

Retrying.


feat!: upgrade to Capacitor v6

Just ran npx @capacitor/plugin-migration-v5-to-v6@latest
cc @BranchMetrics/saas-sdk-devs for visibility.

when are you going to complete the migration to capacitor 6?

@nsingh-branch

@tafelnl @marshall86 Hi, I appreciate the PR and patience. This is on our roadmap and I will try to look into this soon, but can't give an exact date yet.

@tafelnl @marshall86 This has been included in the latest release, 8.0.0.


PP-6368 Remove explicit correlation ID from get charge call

The x-request-id is already available to the logging context as this
uses the getCommonLoggingFields utility added during structured
logging.
This fixes an issue where correlationId is destructured into individual
characters in the logs.

👍


user12986714: Watch interteckpackaging.com

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

interteckpackaging\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Daniil in Charcoal HQ


Implement CI in GHA

Add global configuration file
Add script to install and configure Spark
Run minikube in CI
Run integration tests in CI
Bump k8s version to 1.25
Add image analysis in CI
Update doc

2 additional features to implements in this PR:

add secret for KAFKA socket
move images between CI tasks


Compilation

Not a issue, but can you tell me how to make a mod from a datapack. I know that I need to somehow use some code from git modrinth, but I don't know how. Thank you in advance

If you're asking about the mod packages on modrinth, that's something that's provided by the modrinth website. If you upload a datapack there it gives you a button to automatically package it as a mod. I have no idea how to do it otherwise though, but I'd be interested in finding out!

Thanks for the answer, I don't know anything else myself


Missing license

I came across a mention on Stack Overflow that the project is "free and open source", but that's a bit indirect and non-specific.  Can you add a license file to the repository?

This repo is clearly missing a license. Without any, it falls under no permission
https://choosealicense.com/no-permission/
This must be an oversight because the NuGet packaged is registered under MIT License

Indeed MIT licence. Missing file added.


Fix EPS32 build warning

Problem
ESP32 build fail
../third_party/connectedhomeip/src/app/reporting/Engine.cpp: In member function 'CHIP_ERROR chip::app::reporting::Engine::BuildAndSendSingleReportData(chip::app::ReadHandler*)':
../third_party/connectedhomeip/src/app/reporting/Engine.cpp:415:42: error: 'hasMoreChunks' may be used uninitialized in this function [-Werror=maybe-uninitialized]
     else if (apReadHandler->IsReadType() && !hasMoreChunks)
              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~
cc1plus: some warnings being treated as errors

Change overview
Fix build warning.
Testing
Use unit-tests

/rebase


Adding version specific deprecation options

Looks good, should we add the dependency HPX_WITH_DEPRECATION_WARNINGS=ON => HPX_WITH_DEPRECATION_WARNINGS_V1_5=ON ?

I can do that, sure. How do we handle that normally? Do we use CMake option dependencies?

Looks good, should we add the dependency HPX_WITH_DEPRECATION_WARNINGS=ON => HPX_WITH_DEPRECATION_WARNINGS_V1_5=ON ?

I can do that, sure. How do we handle that normally? Do we use CMake option dependencies?

I've added that now by just guarding the definition of the new options by if(HPX_WITH_DEPRECATION_WARNINGS). Not sure if this what you had in mind.

I'm not sure I understand the use case for this. @hkaiser would you mind summarizing how you would use this?

I'm not sure I understand the use case for this. @hkaiser would you mind summarizing how you would use this?

This allows to mark the deprated facility directly with a version, like:
HPX_REPRECATED_V1_5("foo is deprecated") using foo;

Which would produce a warning saying:
foo is deprecated (This functionality is deprecated starting HPX V1.5 and will be
removed in the future. Disable this warning by adding this to your cmake invocation:
-DHPX_WITH_DEPRECATION_WARNINGS_V1_5=Off")

This allows for controlling deprecation messages on a version-by-version bases by changing the CMake option's default values. It also adds a clear documentation to the functionality itself detailing with what version it was deprecated.

@msimberg the use case for this are the algorithm changes we're working on which I would like to become 'active' starting V1.6 (i.e. I'd like to deprecate the old APIs with V1.6). These new macros allow me to mark the old APIs right now without them generating a warning in the upcoming release. I was planning to finish the algorithm work before we release V1.6 which would allow us to claim C++20 standards conformance on that release.

@msimberg the use case for this are the algorithm changes we're working on which I would like to become 'active' starting V1.6 (i.e. I'd like to deprecate the old APIs with V1.6). These new macros allow me to mark the old APIs right now without them generating a warning in the upcoming release. I was planning to finish the algorithm work before we release V1.6 which would allow us to claim C++20 standards conformance on that release.

Thanks. This was the part I was missing. I'd have just deprecated them right away, but this makes sense as well so we can announce the standards conformance in one go, rather than spread out over multiple releases. In that case would it be enough to just have the deprecation macros, and not the CMake options (just thinking about not adding more options if not needed)? I'd even be in favor of getting rid of the module specific deprecation options and just always using the global one, but that's separate from this. Could the macro be a more generic #define HPX_DEPRECATED(major, minor, message) or will the implementation become nasty in that case?

@msimberg the use case for this are the algorithm changes we're working on which I would like to become 'active' starting V1.6 (i.e. I'd like to deprecate the old APIs with V1.6). These new macros allow me to mark the old APIs right now without them generating a warning in the upcoming release. I was planning to finish the algorithm work before we release V1.6 which would allow us to claim C++20 standards conformance on that release.

Thanks. This was the part I was missing. I'd have just deprecated them right away, but this makes sense as well so we can announce the standards conformance in one go, rather than spread out over multiple releases. In that case would it be enough to just have the deprecation macros, and not the CMake options (just thinking about not adding more options if not needed)?

I think that giving the user an option to silence the warnings temporarily would be important. There are time where one doesn't have the time to deal with upstream changes right away, but still wanting to have a clean build.

I'd even be in favor of getting rid of the module specific deprecation options and just always using the global one, but that's separate from this. Could the macro be a more generic #define HPX_DEPRECATED(major, minor, message) or will the implementation become nasty in that case?

I'll try this. I like the idea.

@msimberg better now?


Race condition under heavy load

If a client disconnects under extremely heavy load (bug was found at > 1,000,000 updates /sec) the following race condition can occur
c:\dev\deepstream.io-performance\high-troughput\node_modules\deepstream.io\src\utils\subscription-registry.js:42
this.subscriptions[ name ][ i ].send( msgString );
^
TypeError: Cannot read property 'send' of undefined
at SubscriptionRegistry.sendToSubscribers (c:\dev\deepstream.io-performance\high-troughput\node_modules\deepstream.i
o\src\utils\subscription-registry.js:42:36)
at RecordHandler.$broadcastUpdate (c:\dev\deepstream.io-performance\high-troughput\node_modules\deepstream.io\src\r
ecord\record-handler.js:264:30)
at RecordTransition._onCacheResponse (c:\dev\deepstream.io-performance\high-troughput\node_modules\deepstream.io\src
\record\record-transition.js:242:23)
at LocalCache.set (c:\dev\deepstream.io-performance\high-troughput\node_modules\deepstream.io\src\default-plugins\lo
cal-cache.js:8:2)
at RecordTransition._next (c:\dev\deepstream.io-performance\high-troughput\node_modules\deepstream.io\src\record\rec
ord-transition.js:224:22)
at RecordTransition._onRecord (c:\dev\deepstream.io-performance\high-troughput\node_modules\deepstream.io\src\record
\record-transition.js:171:8)
at RecordRequest._onCacheResponse (c:\dev\deepstream.io-performance\high-troughput\node_modules\deepstream.io\src\re
cord\record-request.js:55:8)
at LocalCache.get (c:\dev\deepstream.io-performance\high-troughput\node_modules\deepstream.io\src\default-plugins\lo
cal-cache.js:12:2)
at new RecordRequest (c:\dev\deepstream.io-performance\high-troughput\node_modules\deepstream.io\src\record\record-r
equest.js:32:22)
at RecordTransition.add (c:\dev\deepstream.io-performance\high-troughput\node_modules\deepstream.io\src\record\recor
d-transition.js:127:25)

Fixed this issue in release 0.4.1


OP_CheckSig Failing tests

The checksig opcode is currently failing tests, I think it has something to do with signatures not being in DER format, or the public_key not being compressed, I am not sure at the moment.
Test vectors were taken from neo-python
the verify signature looks like:
  # (binary, binary, binary)
  def verify(msg, sig, pub_key) do
    :crypto.verify(:ecdsa, :sha256, msg, sig, [pub_key, :secp256r1])
  end

The method in the Execution engine looks like:
  def do_execute(<<@_CHECKSIG, rest::binary>>, %{stack: [pub_key, sig, msg | stack]} = state) do
    res = NeoVM.Crypto.verify(msg, sig, pub_key)
    {rest, %{state | stack: [res | stack]}}
  end

The test that fails is:
  test "CHECKSIG" do

    sig_hex =
      "CD0CA967D11CEA78E25AD16F15DBE77672258BFEC59FF3617C95E317ACFF063A48D35F71AA5CE7D735977412186E1572507D0F4D204C5BCB6C90E03B8B857FBD"

    pub_hex = "036FBCB5E138C1CE5360E861674C03228AF735A9114A5B7FB4121B8350129F3FFE"

    msg = "abcdef"
    {:ok, sig} = Base.decode16(sig_hex)
    {:ok, pub_key} = Base.decode16(pub_hex)

    len_msg = byte_size(msg)
    len_sig = byte_size(sig)
    len_pub_key = byte_size(pub_key)

    assert %{stack: [true]} ==
             ExecutionEngine.execute(
               <<len_msg, msg::binary, len_sig, sig::binary, len_pub_key, pub_key::binary, 0xAC>>
             )
  end

Test taken from: https://github.com/CityOfZion/neo-python/blob/master/neo/VM/tests/test_execution_engine.py#L44
I have inspected the public key, message and signature before passing it to Crypto module, everything checks out. So I think that the Erlang crypto module may require it in another format. If the problem cannot be solved, then in the worse case, we could call a C function to do the verification.

{pub_key, priv_key} = :crypto.generate_key(:ecdh, :secp256r1)
sign = :crypto.sign(:ecdsa, :sha256, "abcdef", [priv_key, :secp256r1])
:crypto.verify(:ecdsa, :sha256, "abcdef", sign, [pub_key, :secp256r1])

Verify is returning true in this case, but we have a signature of 71 bytes, and a public_key of 65 bytes.
In the python example, signature is 64 bytes and public_key is 33 bytes.
Maybe we are missing this operation for the public_key: https://github.com/neo-project/neo/blob/35ff9a68010bdddc160840f222df13c3c46290f6/neo/Cryptography/Crypto.cs#L45

Ohh I did not check both of them at the same time. If 71 bytes signature bytes works with 65 bytes public key, then we need to convert signature into DER format and decompress the public key for it to verify. That explains why it was still failing, let me re-do the functions for you, and check again.


TAPO cameras failling after firmware update

One of my Tapo C310 hw v2.0 receive an update (new version is 1.3.9) and, after this, cannot be accessed anymore by WebRTC  HASS integration.
I didn't update my another C310 and still working fine. Looks like new firmware changes something in the auth process (it ends in "streams: wrong response on DESCRIBE, 401 Unauthorized"
Log:
023-11-13 19:06:51.201 DEBUG (webrtc) [custom_components.webrtc.utils] 19:06:51.201 INF go2rtc version 1.8.1 linux/arm64
2023-11-13 19:06:51.203 DEBUG (webrtc) [custom_components.webrtc.utils] 19:06:51.202 INF [api] listen addr=<IP_ADDRESS>:1984
2023-11-13 19:06:51.206 DEBUG (webrtc) [custom_components.webrtc.utils] 19:06:51.204 INF [rtsp] listen addr=<IP_ADDRESS>:8554
2023-11-13 19:06:51.206 DEBUG (webrtc) [custom_components.webrtc.utils] 19:06:51.205 INF [webrtc] listen addr=<IP_ADDRESS>:8555/tcp
2023-11-13 19:07:02.694 DEBUG (MainThread) [custom_components.webrtc] New client: {'authSig': 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJkZWEwZGJmYjU1MzY0Y2QyYjQwMDg2OTg2NTE3ZTM4ZiIsInBhdGgiOiIvYXBpL3dlYnJ0Yy93cyIsInBhcmFtcyI6W10sImlhdCI6MTY5OTkxMzIyMiwiZXhwIjoxNjk5OTEzMjUyfQ.JzOUGuwbzvfNQbLWf4GnSPOL1PGGN9CHF8B6jzasCFQ', 'url': 'rtsp://<IP_ADDRESS>:8554/c310puerta?mp4'}
2023-11-13 19:07:06.037 DEBUG (webrtc) [custom_components.webrtc.utils] 19:07:06.037 ERR github.com/AlexxIT/go2rtc/internal/mjpeg/init.go:166 > error="streams: wrong response on DESCRIBE, 401 Unauthorized"

Please, ask me for any other info i can provide to help solve this issue.
Thanks!
UPDATE: one of my C100 updates too and shows same issue. The other ones still with old firmware and working fine.

https://github.com/AlexxIT/go2rtc/issues/733


remove -K and -R flags from tmux popup: uknown flags

as per tmux 3.3a, -K and -R result in an unknown flag error on tmux popup

sure


Bind entry deletion

Hey there, thank you for the very nice tool, awesome work. :)
The README says that "To delete history entries, run mcfly search manually". Is there anything fundamentally blocking us to use mcfly entry deletion directly from fzf?
If not, is it something that you would see into mcfly-fzf? How hard would that be?

I think the main challenge with deletion in the fzf interface is handling confirmations well, so that users get a confirmation prompt before permanently deleting a history entry. Though looking at the fzf docs I think that the execute action may be able to handle confirmation.
In that case, the elements would be

Find/make a CLI one-liner that can delete a history entry with command-line confirmation (e.g. y/n prompt)
Add a key-binding to the fzf setup scripts that will call that command appropriately (likely requires writing some Rust code)

For prototyping, I'd recommend you start with 2 and make a dummy python script or something to make sure that the UI of prompt + confirm will work well, and ensure that you are able to get the relevant information passed to the CLI script.
Definitely something I'd be happy to take a pull request on if you can get it working

FWIW I don't like McFly's confirmation in the first place. What do you think of skipping the confirmation in a first iteration, disabling the shortcut by default and adding an environment variable flag, e.g. MCFLY_FZF_UNSAFE_DELETE=1? Then we could see to eventually add the confirmation and make it activated by default.

Yeah, disabled by default but no confirmation sounds good to me. I'll take a look at your pull over the next few days as I have time. I'm also a bit of a rust noob, but I've found tinkering on projects like mcfly and reedline to be a good learning experience


chore(main): release 0.16.1

:robot: I have created a release beep boop
0.16.1 (2024-05-22)
Bug Fixes

trek detail observers (e2eb686)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/GeotrekCE/Geotrek-rando-widget/releases/tag/0.16.1 :sunflower:


Video doesn't resume from the same time it was paused at, if it stays paused for a few seconds.

Bug

Platform

Which player are you experiencing the problem on:

Android (Reproducible on both the media players available for android)

Environment info

React native info output:
 System:
    OS: macOS 13.0.1
    CPU: (8) arm64 Apple M1
    Memory: 120.73 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
    Android SDK: Not Found
  IDEs:
    Android Studio: 2021.3 AI-213.7172.25.2113.9014738
    Xcode: 14.2/14C18 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.15 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.68.2 => 0.68.2
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Library version: 5.2.0
Steps To Reproduce

I have a video which is about 45 seconds long. I have created a component somewhat similar to Whatsapp stories.
When I press and hold on the screen the video pauses. But, with this particular longer video, the video seeks back/forward to some position different from the position I paused the video on if it stays paused for longer than around 5 seconds. If I release the tap the video resumes from that wrong position. If I release the tap sooner than around 5 seconds, it works as expected.

Start playing a video.
Keep it paused for longer than around 5 seconds, and the video abruptly skips to some other position, different from what it was paused on.
If the video is unpaused now, it will resume from that wrong position.
It works as expected if the video is unpaused before it has the chance to skip to a different position.
It also works as expected on smaller videos.

Expected behaviour

The video shouldn't skip to some different position if it is paused.

Reproducible sample code
Should probably work with a simple implementation with a longer video.
Here is my slightly trimmed down implementation.
<Video
    source={{uri: media_url}}
    resizeMode="contain"

    // This is toggled to true when I long press on the screen, and toggled to false when the touch is released.
    paused={pauseAutoStoryChange}

    onLoadStart={() => {
        setMediaLoading(true);
    }}
    onLoad={videoData => {
        setVideoDuration(videoData.duration * 1000);
        setMediaLoading(false);
    }}
/>

Video sample
Any video longer than 45 seconds.

6.0.0-alpha.4 fix seek behavior on android


custom.css

It might be convenient to put
<link rel="stylesheet" href="{{ $.Site.BaseURL }}css/custom.css" />
in header.html partial, so that it is easy to customize css by creating custom.css in static/css folder, without changing the theme files.

Thanks for the feedback. Yes, sounds like a convenient way to allow for more advanced customization.
I have added support for custom CSS and JS assets in commit 280d5ca .
After applying that update, you can put asset(s) such as a custom.css file in a static/css/ directory and set custom_css = ["custom.css"] in your config.toml to link it in.

Thanks!


Add tests/python_build to clang-format pre-commit hook ignore list

It had been ignored by misc/scripts/clang_format.sh since 388d35b74d8919b251faae9e24af50476f12b1a2 but not the hook; running the hook on all files yields changes in GLSL files in that directory.

cc @akien-mga, you seem to have been maintaining these :)

CI fails because of:

could not find pull request diff: HTTP 500 (https://api.github.com/repos/godotengine/godot/pulls/87000)

That's a new one...

Looks like GitHub is having server problems again

Gentle ping, @akien-mga?

Thanks!


Update lndclient branch lnd-18-4 to track lnd v0.18.4-beta release

Updating lndclient branch lnd-18-4 to point to the tagged version of lnd is a dependency for the custom channel saga and needs to be completed before merging [the mother of all PRs](link to the original PR).
To complete this task:

[ ] 1. Tag / push lnd v0.18.4-beta to https://github.com/lightningnetwork/lnd/ tagged (at least an RC tag)
[ ] 2. Update the lndclient branch lnd-18-4 to point to the tagged version of lnd

This update is a prerequisite for the litd version (to be released with custom-channels code merged into main) dependency chain.

Fixed by https://github.com/lightninglabs/lndclient/releases/tag/v0.18.4-6.


Additional properties not showing in Application Insights .NET framework

I have added Microsoft.ApplicationInsights.ServiceFabric.Native package to my stateful project .net
I have added   FabricTelemetryInitializerExtension.SetServiceCallContext(this.Context); to my RunAsync method.
I am loging to insights as follows
           TelemetryClient tclient = new TelemetryClient(new icrosoft.ApplicationInsights.Extensibility.TelemetryConfiguration("InstrumationKey"));
            tclient.TrackEvent("TEST");

However i am not seeing any of the context information in the application insight logs. I do see the TEST log.
Am i missing something i thought that these would be added when i genetered my logs?

@inkey The context are added through TelemetryIntializer, which is configured in the ApplicationInsights.config file in your case, so you need to create a telemetry client from that config so the TelemetryInitializer can take effect.
Try TelemetryClient tclient = new TelemetryClient(TelemetryConfiguration.Active). More info at here.


Can't import photos

Describe the bug
I'm not able to import photos to upload them as observations. Taking a photo with the app works fine but importing existing photos does not work.
To Reproduce
Steps to reproduce the behavior:

Tap on Green Plus at bottom and tap the photo icons that appear on the top right of the Green Plus.
Select any photo from your files, gallery, google photos, etc.
It gets stuck at a blank screen with green activity bar on top.

Expected behavior
I expected the photo to appear so it can be uploaded
Screenshots

Context (please complete the following information):

Device: Samsung Galaxy A54 5G
OS: Android version 14
App version: 0.52.0 (121)

This is probably a duplicate of #947, but since it's definitely working both online and offline, I guess we'll leave it. Both probably need the same solution.

I did see #947. That user mentioned it worked with screenshots but I can't make it work with anything, including screenshots. Also for note; I tried it with and without internet, and I tried with wifi and mobile data. Nothing


VEGA-2216 Fix loading of assets when in dev mode #minor

Checklist

[ ] I have updated the end-to-end tests to work with my changes
[ ] I have added styling for Dark Mode
[ ] I have checked that my UI changes meet accessibility standards

Looks like this also covers the doc rewrites from VEGA-2262, so that can be marked done too.


Set predefined environment variables for existing libraries in dart2js

See issue #24581.
Not clear, if we want to expose these behind the flag, or not.

Fixed with e775fa093207913f0fea911842c3840b065ead93


eq-without-hash (PLW1641) does not check for __hash__ in superclasses

i noticed this is mentioned in the rule's docs but i'm raising it because i couldn't see an issue for it

👍 Yeah this is why the rule is in the nursery -- as long as we don't support multi-file analysis, we can't implement it reliably. I'm gonna close as this is basically a known issue that will eventually be solved by multi-file analysis.

wouldn't it make sense to keep the issue open to track it if it's a known issue?

We could consider creating a central tracking issue (or a tag like @zanieb did here). I just want to avoid piling up a bunch of known issues related to multi-file analysis that can't be worked on individually and make it harder to navigate the issue tracker.

Also hit this one while enabling --preview. It's a useful rule. It found out 1 place we were missing __hash__ but then had 6 false positives due to superclasses.
Added # noqa: PLW1641  # hash implemented by superclass at the false positives for now and keeping the rule.

We could consider creating a central tracking issue

raised #7447

see #14883, it shouldn't look in superclasses


Add Search trait

Codecov Report

Merging #33 (086f809) into main (d47808b) will increase coverage by 0.03%.
The diff coverage is 87.50%.

@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
+ Coverage   95.68%   95.71%   +0.03%
==========================================
  Files          23       24       +1
  Lines        4491     4523      +32
==========================================
+ Hits         4297     4329      +32
  Misses        194      194

Impacted Files
Coverage Δ

search/src/negamax.rs
86.73% <86.73%> (ø)

search/src/alpha_beta.rs
87.93% <87.93%> (ø)

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 d47808b...086f809. Read the comment docs.


MicroPython Support

Is it possible to include support for MicroPython in the same way Ruby, Python, Python 3, etc. is?

what would be the advantage over regular python?

Availability on certain microcontrollers is the main benefit in reality. I have a variant of Tiny Core Linux (PiCore) on my Raspberry Pi, which has MicroPython installed by default as it is lightweight.
I would like to be able to use Vim on that, and be able to code for microcontrollers which use MicroPython (mainly the ESP8266/8285 at this point).

closing as not planned


Dropdown has wrong initial position

Select one ...  (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Expected behavior
Closed dropdown should not create extra space on the screen
Actual behavior
Dropdown has wrong initial position when dropdown's content is longer than trigger width. It result in unneeded scrollbars.

When the dropdown is closed, the clr-dropdown-menu element has the following styles:
position: absolute; top: 0px; bottom: auto; left: 0px; right: auto; visibility: hidden;
Its parent clr-dropdown component has CSS class .dropdown which hangs position: relative to it. When we open the dropdown for the first time, the clr-dropdown component receives style="position: static;" which fixes the problem.
As a workaround one can explicitly add style="position: sticky;" to the clr-dropdown` component.
Why do we need setting visibility: hidden instead of display: none?
Reproduction of behavior
https://plnkr.co/edit/wwBl4jNZ9zJAlVCyKPHm?p=preview
Environment details

Angular version: 4.4.6

Clarity version: 0.10.10

OS and version: Windows 10

Browser: all

@coldhamix: We recommend that you use the *clrIfOpen directive with clr-dropdown-menu. Please see this: https://plnkr.co/edit/PE4d6fLvckVn8MKvuS8D?p=preview When you use *clrIfOpen, the menu is not loaded be default and is positioned correctly.
I believe this issue is a duplicate of: https://github.com/vmware/clarity/issues/1474. Please subscribe to that issue for more updates or use the alternative that we suggested above. Closing the issue based on this.

Apologies. This is a duplicate of: https://github.com/vmware/clarity/issues/1262 Please subscribe to that issue for more updates.


Provide pre-transpiled code on npm

Thanks for this wonderful little tool!
Do you think it'd be possible to provide the npm version in ES5? Most anyone using this from within webpack likely has a setup similar to
{
  test: /\.js?$/,
  exclude: /(node_modules|bower_components)/,
  loader: 'babel?presets[]=es2015' // etc.
}

... because there is an unspoken expectation that anything inside node_modules doesn't use export from lines etc.
Not a big deal, but would be nice not to have to mess with the webpack config for just this one package.

Thanks!
So, there is a transpiled ES5 version installed in node_modules/venn.js/venn.js  . Its produced with rollup.js as detailed in this post on creating D3 plugins: https://bost.ocks.org/mike/d3-plugin/
I'm not really a JS guy though, so let me know if I'm doing anything wrong here =)

I seems I spoke too soon. It works without any problems on another machine of mine, just as you described. For some mysterious reason though the first one insists on loading index.js, and webpack complains about needing a loader (i.e. babel) to deal with export from lines.
I'll be taking another look at this; for now thanks again for a great library and sorry about the false alarm!


proposal: refactor quickstart and docs

Skeleton refactor to test new provider-specific flows.
One of the struggles I've had with the quickstart is that it has been
caught between among a task-oriented doc, platform reference and provider
agnostic. The end-result is something that isn't compelling and ends up
being particularly confusing for new visitors to the project.
This (now squashed) commit represents a deep refactor of the quickstart
documentation.
Orient the quickstart around a three step, goal-oriented process:

Tools
Infra + Workflow Install
Deploy an example app

This also pulls in specific configurations of Kubernetes for evaluation and
dev/test (kube-up.sh and GKE). We want tire-kickers to get a win and we
need to offer as much assistance through the process as possible.
Pre-install helm and deis CLIs up front.
Couching the install in provider-specific workflows gives the documentation
much needed context. For example, nuances about load balancer
configurations (or lack there-of) can be dealt with in-context. This will
simplify the language as we can back away from routing folks to more
detailed explanations or landing a barrage of caveats.
I also slimmed down the "deploy your first app" to the absolute basics.
Using the deis/example-go app lets folks get a win without having to deal
with cloning repos, etc. That stuff can go into reference documentation for
the three build types.
Click through the GKE flow, that should be complete.
Thoughts would be great! Then we can do sections for Vagrant and AWS.

/cc @mboersma @bacongobbler

Finished up all three quickstart paths, would like to start getting eyes on this one.

Updated and rebased.

manually testing this as well now :)

what's with the TODO.md?

I also cannot click on the AWS, GKE or Vagrant selections on the right-hand-side dropdown list. This is likely due to a limitation with the number of levels the table of contents can handle, so I'd put the "Boot" sections as the top level index and make those links clickable.

Regarding the busted links, the whole CSS/TOC thing is a disaster and I'll tackle that separately.

I'm happy to just LGTM this for now and start hacking away on any nitpicks I have as follow-ups. Excellent work on the quickstart docs!

I'm happy to just LGTM this for now and start hacking away on any nitpicks I have as follow-ups.

Agreed--this is a huge improvement. I'm happy to merge it and I can take a pass at reducing the first-person pronouns in a subsequent PR.

needs a rebase now that https://github.com/deis/workflow/pull/239 was merged. Sorry about that!


CI Builds against Stable, Beta, and Dev channels

Codecov Report

Merging #68 (87e0722) into master (0ed2af4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #68   +/-   ##
=======================================
  Coverage   35.16%   35.16%
=======================================
  Files           3        3
  Lines         236      236
=======================================
  Hits           83       83
  Misses        153      153

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 0ed2af4...87e0722. Read the comment docs.


Is it possible to write my own poll mechanism?

For long running operations.
cc @jhendrixMSFT

Related to https://github.com/Azure/azure-rest-api-specs/issues/1347

Futures have a Response() method, so from there, it should be easy to write a poller by hand in case it was needed.


Fix the build issue in core-lro testing

fixes https://github.com/Azure/azure-sdk-for-js/issues/29634

API change check
API changes are not detected in this pull request.


Changes in README and headless script

Install instructions for centos/rhel
Instructions to run Xvfb in node
Changes in prepareHeadless.sh to install in centos/rhel

Thanks!


Browsing the Wiki's history

[ Making it separate from #4399, as suggested.  ]
It would be great to be able to browse the wiki's Git repository, to see what changes happened when and who made them.

Duplicated to https://github.com/gogits/gogs/issues/2991?


Fix missing matrix screenshots for OnyxRadioGroup

https://teams.microsoft.com/l/message/19:3a7010e95b8749edac6271ea346a7bc4@thread.tacv2/1722925096614?tenantId=d04f4717-5a6e-4b98-b3f9-6918e0385f4c&groupId=969ca3b3-9c78-411f-8629-eb770bbfdc7b&parentMessageId=1722925096614&teamName=onyx&channelName=Developers&createdTime=1722925096614

@jannick-ux I renamed the headline property to label for the radio and checkbox group so its uniform with our other form components. Can you also rename it in Figma?


Update README.md

Improved the documentation and supported Flink1.18 version
Proposed changes
Issue Number: close #xxx
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Improved the documentation and supported Flink1.18 version


Error: I2p

[hacker@localhost ~]$ python3 my_connecter.py
Traceback (most recent call last):
File "my_connecter.py", line 5, in
sock.connect(("red.i2p", 80))
File "/usr/local/lib/python3.8/site-packages/i2p-0.1.0-py3.8.egg/i2p/socket/sam/simple.py", line 169, in check_connect
File "/usr/local/lib/python3.8/site-packages/i2p-0.1.0-py3.8.egg/i2p/socket/sam/simple.py", line 137, in check_state
File "/usr/local/lib/python3.8/site-packages/i2p-0.1.0-py3.8.egg/i2p/socket/sam/simple.py", line 147, in check_type
File "/usr/local/lib/python3.8/site-packages/i2p-0.1.0-py3.8.egg/i2p/socket/sam/simple.py", line 225, in connect
File "/usr/local/lib/python3.8/site-packages/i2p-0.1.0-py3.8.egg/i2p/socket/sam/simple.py", line 120, in _sam_cmd
BrokenPipeError: [Errno 32] Broken pipe

Decision: reinstall i2p.socket lib


Convert multi session selector for KPIs dashboard item to combobox style from checkboxs. This is needed for large numbers of sessions.

Use your best intuition as to how the UI/UX should function.
Tagging @katherineyli and @aiizhao as you two should chat to discuss how this affects @katherineyli s overhaul of the chart UI/UX.

Closing when merging #555


Query Combinations

Queries can be more expressive by performing a union along queries of the same case and an intersection across cases:

"iPhone 5" "iPhone 6" will find both iPhone 5 and iPhone 6 Simulators.
"iPhone 5" "iPhone 6" B8EEA6C4-841B-47E5-92DE-014E0ECD8139 will find iPhone 5 and 6 Simulators that match the given UDID.
booting booted "iPad 2" will find all booting or booted iPad 2 Simulators.

lgtm


[import/order] Add ability to sort groups in order of nested groups

Resolves #2685, #2683, #2682
This PR changes 2 things:

Add the ability to sort groups in the order of nested groups
Add the ability to sort types in the order of the rest of the groups array.

Both of these features are currently disabled by default and must be enabled with the intraGroupOrdering option. I've added a TODO: semver major flag to this option indicating to make this behavior the default in the next major version. We can either remove the flag after that or enable its behavior by default with the option to disable it.
Add the ability to sort groups in the order of nested groups (intraGroupOrdering = true)
Will mutate ranks of a single group based on the order of the of the group's nested groups.
If the rule is configured to alphabetize, it will alphabetize each subgroup individually and then sort the subgroups in nested groups order. That is to say, if the rule is configured as [['parent', 'sibling']], it will sort all of the parent imports alphabetically, then sort all of the sibling imports alphabetically. Then move all the alphabetized parent imports before the alphabetized sibling imports.
Ex.
Given the following code and rule options
// code
import fs from 'fs';
import { foo } from './foo';
import { bar } from './bar';
import { fooz } from '../fooz';

// options
{
  intraGroupOrdering: true,
  groups: ['builtin', ['parent', 'sibling']],
  newlines: 'always',
  alphabetize: {
    order: 'asc',
  }
}

Results in: ../fooz being before ./foo because parent is listed before sibling in the groups array
import fs from 'fs';

import { fooz } from '../fooz';
import { bar } from './bar';
import { foo } from './foo';

Add the ability to sort types in the order of the rest of the groups array (intraGroupOrdering = true)
Will mutate ranks of all type imports such that they are sorted in the flattened order of the original groups array without the types. If the rule is configured to alphabetize, it will do the same thing as how alphabetization works above.
Ex.
Given the following code and rule options
// code
import type { Dirent } from 'fs';
import type { Foo } from './foo';
import type { Bar } from './bar';
import type { Fooz } from '../fooz';

import fs from 'fs';
import { fooz } from '../fooz';
import { bar } from './bar';
import { foo } from './foo';

// options
{
  intraGroupOrdering: true,
  groups: ['type, 'builtin', ['parent', 'sibling']],
  newlines: 'always',
  alphabetize: {
    order: 'asc',
  }
}

Results in: ../fooz being before ./foo because parent is listed before sibling in the groups array
import type { Dirent } from 'fs';
import type { Fooz } from '../fooz';
import type { Foo } from './foo';
import type { Bar } from './bar';

import fs from 'fs';

import { fooz } from '../fooz';
import { bar } from './bar';
import { foo } from './foo';

Testing
I had a lot of trouble with tests. @ljharb I'm not sure if you've seen this before but I was randomly getting cases where the groups array was setting elements to undefined. I assumed the code was mutating the groups array somewhere but I couldn't find it. Please be on the lookout for that. Also, I would randomly need newlines in the output of some tests but not for others.
I decided I would rather get the PR up so that I can show progress than continue struggling with the system. I think there should be more testing for the case where both intraGroupOrdering and alphabetize is enabled. As well as tests for unknown types when this option is enabled. The tests I did add are very basic. I am open to test suggestions.

Hi @Pearce-Ropion, thank you so much for the PR. Just a little suggestion: would you mind not using the Resolves keyword? In my humble opinnion the merge of this PR does not guarantee that a lot of corner cases not covered here will be solved. Wouldn't it be good to wait for the user feedback before simply closing the issues?
Regarding tests, man I don't know what to say. In theory https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/order.md is the source of truth here, so you should add enough cases to guarantee the code complains that doc, but the test file is massive so it's really hard to tell which cases are already covered and which ones not. This is a reason to not auto close the issues.
Once this is finished I would really consider a refactor, there seem to be a lot of complexity in both the source and the test files. Having said that, I'm a mere spectator, it's up to you guys to form your own opinnion and reach your own conclussions.

The way to know it fixes the linked issues is to add those test cases here - which shouldn't interact with new options at all. @Pearce-Ropion, could we do that? (note i haven't looked at the diff yet, so maybe you already have!)

Hi @Pearce-Ropion, thank you so much for the PR. Just a little suggestion: would you mind not using the Resolves keyword? In my humble opinnion the merge of this PR does not guarantee that a lot of corner cases not covered here will be solved. Wouldn't it be good to wait for the user feedback before simply closing the issues?

I think that is the point of being able to discuss the change in the PR and add/remove test cases. Ideally a PR should resolve issues. Issues can always be re-opened if a PR does not adequately address the problems. However, in my opinion, this change does resolve all of the listed issues.
Now, I agree that there are potentially a lot of corner cases that I am not covering, but that is why I explicitly state that I think I need to add more test cases because I know I am not covering all of the edge cases. Is there a particular issue with the proposed changes that you think does not resolve the issues listed? If so, please bring it up here so that we can discuss it and potentially make changes as needed.
Also, I am not entirely sure how this repo is set up, but I am pretty sure @ljharb manually closes issues as they are resolved.

I think that is the point of being able to discuss the change in the PR and add/remove test cases.

I totally agree with you, I couldn't be happier after reading this :)

Now, I agree that there are potentially a lot of corner cases that I am not covering, but that is why I explicitly state that I think I need to add more test cases because I know I am not covering all of the edge cases. Is there a particular issue with the proposed changes that you think does not resolve the issues listed? If so, please bring it up here so that we can discuss it and potentially make changes as needed.

To be honest, understanding your changes and giving feedback on top of those seems quite challenging to me given my experience with this code base and the complexity surrounding this files. I think the library maintainers are way more capable than me. Having said that, I can take a different approach: I can give you test cases so we can see what's going on with the logic (asuming the cases are right, of course).
In order to start, what do you think about the following case? It complains the document rules but throws an error:
test({
      code: `import { beforeAll, describe, expect, it, jest } from '@jest/globals';

import { ServiceId, Tag } from '@cuaklabs/iocuak-common';
import { Binding, BindingType } from '@cuaklabs/iocuak-models';

import { TypeBindingFixtures } from '../fixtures/TypeBindingFixtures';
import { BindingService } from './BindingService';
import { BindingServiceImplementation } from './BindingServiceImplementation';
`,
      options: [{
        alphabetize: {
          order: 'asc',
          caseInsensitive: true,
        },
        groups: ['builtin', 'external'],
        'newlines-between': 'always',
        pathGroups: [
          {
            pattern: '@jest/globals',
            group: 'external',
            position: 'before',
          },
          {
            pattern: 'jest-mock',
            group: 'external',
            position: 'before',
          },
        ],
        pathGroupsExcludedImportTypes: ['@jest/globals', 'jest-mock'],
      }],
    }),

According to the output, the error is:
`../fixtures/TypeBindingFixtures` import should occur after import of `./BindingServiceImplementation`

But this error is a regression. Until eslint-plugin-import version 2.26.0, a grandparent import was before a parent import. Is there a reason to change this behavior? Is that the expected behavior? If so, should we update docs and changelog according to this behavior? This way any user would know it's not a bug but the new expected behavior.

Also, I am not entirely sure how this repo is set up, but I am pretty sure @ljharb manually closes issues as they are resolved.

If that's the repo's methodoly let's proceed that way.

Ok, I think I am started to understand your issue with using "resolves" in this PR. I think I definitely could have explained how this PR resolves the given issues better. I think the main problem with "resolving" these issues is that some of them are technically unresolvable without further intervention by @ljharb.
This PR adds an option (intraGroupOrdering) that enables user the ability to resolve these issues on their own. So in that regard, it could be perceived as a feature/enhancement rather than a bug fix. The central problem that all of the given issues revolve around is that the way that alphabetization of imports in this package has changed between v2.26 and v2.27. I think what you and those that reported these issues are calling a "bug" should probably have been listed as a breaking change in the changelog.
Essentially, #2396 changes the way that alphabetization is handled by making it so that each path segment of a given path (split on /) is sorted in alphabetical order. So this means that . is sorted before .. given the following paths: ../foo and ./foo. Before #2396 the whole path was used for alphabetization. So ../foo was sorted before ./foo.
Ultimately, there isn't a straightforward fix to make it so that ../foo is sorted before ./foo because when alphabetically sorted by path segment, the current order is correct. Also, unless your specifically tell the rule to sort parent imports before sibling imports, the rule is under no obligation to do so. Any sorting of that nature that previously occurred (in v2.26 and below) was just a happy accident. So therefore, you could potentially make the argument that the way that alphabetical sorting worked in the previous implementation (ie v2.26 and below) was actually a bug and that the way it works in newer versions (v2.27 and above) is correct.
The changes made in #2396 were not made by me and therefore is not up to me to decide whether they should be reverted or what the direction that @ljharb wants to take this library in. The problem therein being that technically this is not bug and the change probably should have been in the breaking changes list.

Ok, moving on to your example. Lets break this down and simplify it a bit. The problem you are experiencing can be attributed in its entirely to the change made in #2396 (see above). Again, this means that paths within the same group are sorted alphabetically by their path segments. Given that your configured groups array does not contain either parent or sibling, all of the parent and sibling imports are added to the unknown group and are therefore all part of the same group.
Therefore, your test case can be simplified to the following:
test({
    code: `
        import { TypeBindingFixtures } from '../fixtures/TypeBindingFixtures';
        import { BindingService } from './BindingService';
        import { BindingServiceImplementation } from './BindingServiceImplementation';
    `,
    options: [{
        alphabetize: {
            order: 'asc',
            caseInsensitive: true,
        },
        groups: ['builtin', 'external'],
        'newlines-between': 'always',
    }],
}),

According to my explanation above, the error you are receiving is not bug. Technically, when paths are sorted alphabetically by path segment, any path that starts with a single . (ie, a sibling import) will be sorted above a.. (a parent import). Since all of these parent and sibling imports are part of the unknown group, the plugin is under no obligation to sort these in the parent > sibling order.
Ok, so how do we fix this? Essentially, this PR adds and option allowing you to control the order in which imports are sorted. This would mean an eslint configuration change. Your current config would need 2 changes:

Add the intraGroupOrdering option and set it to true.
Add a nested subgroup in your groups array that places parent imports above sibling imports

Therefore your resulting configuration would look something like this:
options: [{
    alphabetize: {
        order: 'asc',
        caseInsensitive: true,
    },
    intraGroupOrdering: true,
    groups: ['builtin', 'external', ['parent', 'sibling']],
    'newlines-between': 'always',
}],

If you still want all of the potentially unknown imports to be sorted together (no newlines), you could potentially add all of those remaining import group types to the final subgroup (given that we already know what all of them are).
So something like this:
intraGroupOrdering: true,
groups: ['builtin', 'external', ['internal', 'parent', 'sibling', 'index', 'object', 'type', 'unknown']],

But this error is a regression. Until eslint-plugin-import version 2.26.0, a grandparent import was before a parent import. Is there a reason to change this behavior? Is that the expected behavior? If so, should we update docs and changelog according to this behavior? This way any user would know it's not a bug but the new expected behavior.

To answer this final part, yes this is a "change" but not necessarily a "regression". I personally believe that the method that this rule uses for alphabetization should be documented and that that change could potentially be part of this PR. I also understand that having to specify every import type in the groups array (like in the final example I gave above) to essentially have the same behavior as v2.26 and below is not ideal. But ultimately, I think most people are more likely to be update their configuration and accept that there will be import ordering changes in their files when they do.

@Pearce-Ropion Thank you so much! Ok now I got the context everything is clear to me. As soon as it's an intended change I can afford the changes on my source code.

The changes made in https://github.com/import-js/eslint-plugin-import/pull/2396 were not made by me and therefore is not up to me to decide whether they should be reverted or what the direction that @ljharb wants to take this library in. The problem therein being that technically this is not bug and the change probably should have been in the breaking changes list.

I totally respect the change, just consider documenting it as BC, for me that was the issue: from a day to another the CI tried to update the linter, which resulted complaining about tons of errors in the imports order. Then I went to the changelog and no BC was documented, it was a normal minor release.
I can understand the argument this is a fix and not a regression, but those subtelties are hard to acknoledge without coming here for help since most of us do not know the design decissions taken here in the library. For that reason maybe, as you commented, it would be more practical to warn (a BC sections feels great) about these changes, even if they are technically fixes. The hint given in the changelog was:

order: move nested imports closer to main import entry (https://github.com/import-js/eslint-plugin-import/pull/2396, thanks @pri1311)

Which maybe lacks a little bit of detail. Sorry to be picky, just doing my best to give you my honest feedback looking forward to improve things in the future. You guys are great and I really appreciate all the work you are doing! :heart:

Any chance this is going to be merged?

still stay "eslint-plugin-import": "2.26.0" wait for this pr to be merged

Looking forward to this :heart: , thanks for the PR

@Pearce-Ropion if the original change is considered breaking, then the right approach is to revert it, and instead of provide it behind an option. Can you rebase this PR and update it to achieve that?

Also looking forward to this (so as to avoid ✖ 745 problems (745 errors, 0 warnings) when upgrading from 2.26.0.
Is there anything I can do to move this forward?

recommend migrate to: https://github.com/lydell/eslint-plugin-simple-import-sort

Sorry all, I've been very busy at work and haven't had time to work on this.
At this point, I'm inclined to agree with @rgant on this one. Reverting the thing that caused this issue will likely also be a breaking change for everyone who started using this rule since v2.27 released.
I haven't tested it, but I'm fairly sure my changes will still work with or without reverting the initial issue.

I would love to stop being locked at 2.26.0. Any motion on this?

I would love to stop being locked at 2.26.0. Any motion on this?

@brendonrapp I ended up delegating the sorting part to Perfectionist so I could upgrade eslint-plugin-import while being able to define my sorting preference exhaustively. It's working well for me and might work for you:
"perfectionist/sort-imports": [
      "error",
      {
        groups: [
          ["external", "builtin"],
          ["parent", "sibling"],
        ],
        "newlines-between": "always",
      },
    ],

Ideally, I'd be able to add a new option that matches the post-2.26 behavior, and separately revert the default behavior to the pre-2.26 behavior.
that way, the breaking change is reverted, but all the users that will break have an easy fix.
My hope is that this PR can be made to do that.

Any progressing?