Update bitvec dependency to  0.17.4

cargo update is giving me an error about bitvec.
cargo update
    Updating crates.io index
error: failed to select a version for the requirement `bitvec = "^0.15.2"`
  candidate versions found which didn't match: 0.17.4
  location searched: crates.io index
required by package `wagyu-ethereum v0.6.2`
    ... which is depended on by `myproject v0.1.0 (/home/ski/code/myproject)`

Importantly, 0.17.2's changelog says "This crash is considered a severe bug, as it indicates memory unsafety. Users are strongly encouraged to update to 0.17.2 immediately."
I haven't tested this yet, but I will soon.

There needs to be some changes to the code, too.
$ cargo check
...

warning: use of deprecated item 'bitvec::cursor::BigEndian': This type was renamed to `order::Msb0`, and will be removed in the next release.
  --> ethereum/src/mnemonic.rs:11:5
   |
11 | use bitvec::cursor::BigEndian;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(deprecated)]` on by default

warning: use of deprecated item 'bitvec::cursor::BigEndian': This type was renamed to `order::Msb0`, and will be removed in the next release.
  --> ethereum/src/mnemonic.rs:84:33
   |
84 |         let mut entropy: BitVec<BigEndian> = BitVec::new();
   |                                 ^^^^^^^^^

warning: use of deprecated item 'bitvec::cursor::BigEndian': This type was renamed to `order::Msb0`, and will be removed in the next release.
  --> ethereum/src/mnemonic.rs:91:42
   |
91 |             entropy.append(&mut BitVec::<BigEndian, u8>::from_bitslice(index_slice));
   |                                          ^^^^^^^^^

warning: use of deprecated item 'bitvec::cursor::BigEndian': This type was renamed to `order::Msb0`, and will be removed in the next release.
   --> ethereum/src/mnemonic.rs:123:47
    |
123 |         let checksum = &hash[0].as_bitslice::<BigEndian>()[..length.div(3) as usize];
    |                                               ^^^^^^^^^

warning: use of deprecated item 'bitvec::cursor::BigEndian': This type was renamed to `order::Msb0`, and will be removed in the next release.
   --> ethereum/src/mnemonic.rs:126:37
    |
126 |         let mut encoding = BitVec::<BigEndian, u8>::from_vec(self.entropy.clone());
    |                                     ^^^^^^^^^

error[E0308]: mismatched types
  --> ethereum/src/mnemonic.rs:95:22
   |
95 |             entropy: entropy[..length].as_slice().to_vec(),
   |                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `u8`, found `usize`
   |
   = note: expected struct `std::vec::Vec<u8>`
              found struct `std::vec::Vec<usize>`

error[E0599]: no method named `as_bitslice` found for type `u8` in the current scope
   --> ethereum/src/mnemonic.rs:123:33
    |
123 |         let checksum = &hash[0].as_bitslice::<BigEndian>()[..length.div(3) as usize];
    |                                 ^^^^^^^^^^^ method not found in `u8`

error[E0606]: casting `&bool` as `u16` is invalid
   --> ethereum/src/mnemonic.rs:138:37
    |
138 |                     .map(|(i, bit)| (bit as u16) * 2u16.pow(10 - i as u32))
    |                                     ^^^^^^^^^^^^
    |
    = help: cast through a raw pointer first

error: aborting due to 3 previous errors

Some errors have detailed explanations: E0308, E0599, E0606.
For more information about an error, try `rustc --explain E0308`.
error: could not compile `wagyu-ethereum`.
warning: build failed, waiting for other jobs to finish...
error: build failed

#177

Thank you! Closing in favor of #177


Some IPv6 addresses in AAAA printed using IPv4 syntax

Example on live Internet:
echo ns1.exporterapp.com  | zdns NS -trace -iterative

Broken fragment of output:
        {
            "cached": false,
            "class": 1,
            "depth": 3,
            "layer": "exporterapp.com",
            "name": "ns1.exporterapp.com",
            "name_server": "<IP_ADDRESS>:53",
            "results": {
                "additionals": [
                    {
                        "answer": "<IP_ADDRESS>",
                        "class": "IN",
                        "name": "ns1.exporterapp.com",
                        "ttl": 14400,
                        "type": "A"
                    },
                    {
                        "answer": "<IP_ADDRESS>",
                        "class": "IN",
                        "name": "ns1.exporterapp.com",
                        "ttl": 14400,
                        "type": "AAAA"
                    },

As far as I can see in Wireshark the server is answering correctly, it looks like problem in output formating.

Until this line ZDNS has the actual net.IP object available which contains the full 16 bytes (held in aaaa.AAAA).
https://github.com/zmap/zdns/blob/65842efdad0dfbc8284a472e0f1ad7b5a6024ffc/modules/miekg/miekg.go#L157
If the result of aaaa.AAAA.To4() is not nil, the given address is an actual v4, so the prefix could be added at this point.

[1] RFC 5156, sec 2.2


Include statement

Have you considered adding an include statement field to divide content from toolkits between multiple organisms? Otherwise, these files could get pretty big.
I'm thinking something simple like includes: ["x", "y", "z"]

Could you give a specific example based off of the current schema?

yup - if we look at the pichia file in my fork, it reads
pAOX1:
    ...
pGAP:
    ...

and so on in the promoter section. I would like to have a file called plasmids at collections/pichia and instead put includes: ["pichia/plasmids"] to keep things more organized.

Oh, so lemme get this straight:
collections.yaml, rather than just having something like file: collections/pichia.yaml, you have includes: ["pichia/plasmids/promoter.yaml"] , right?

Not exactly. You'd still have file: collections/pichia.yaml, but in pichia.yaml I could put includes: ["pichia/plasmids/promoter.yaml"]

Fair enough - that makes sense!


Glitch Image has no output

The make.glitch.image node and example is just a black output for me on MBP with NVIDIA GeForce GT 750M 2 GB

In macOS 10.12, Apple changed the OpenGL driver behavior such that that glitch technique no longer works.  It should still work on Mac OS 10.11 and earlier.  I'm not aware of a workaround.  I added a note to README.md (520aa53).

Thanks Steve,
Gotta say it's one of the more ridiculous software issues to report, that it can't glitch, lol.
Sent from my Samsung Galaxy smartphone.
-------- Original message --------
From: Steve Mokris<EMAIL_ADDRESS>Date: 8/6/18 00:39 (GMT+10:00)
To: smokris/vuo-nodes<EMAIL_ADDRESS>Cc: jimbobhunter<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [smokris/vuo-nodes] Glitch Image has no output (#1)
In macOS 10.12, Apple changed the OpenGL driver<EMAIL_ADDRESS>such that that glitch technique no longer works. It should still work on Mac OS 10.11 and earlier. I'm not aware of a workaround. I added a note to README.md (520aa53https://github.com/smokris/vuo-nodes/commit/520aa5327eeb32f20799f24a77c99ac61cb3a605).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/smokris/vuo-nodes/issues/1#issuecomment-395445172, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AkxDmekIs-KQ5gxd5qjd_RMpYMpXCt5hks5t6TslgaJpZM4UdsBv.


CHECK failed: file != nullptr

Click to expand!
Issue Type
Build/Install
Source
source
Tensorflow Version
2.6.0
Custom Code
No
OS Platform and Distribution
MacOS Monterey Version 12.0.1 (21A559)
Mobile device
No response
Python version
3.8.9
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Building and running a docker container (file provided below) on several machines with the same dockerfile and python version. Works on various Ubuntu installations, a MacOS Monterey Version 12.5 installation, but not the MacOS Monterey Version 12.0.1 (21A559) installation on a machine with an Apple M1 Pro chip. On that one, the log output below happens.

Standalone code to reproduce the issue
FROM tensorflow/serving:2.6.0
#RUN mkdir /models
#WORKDIR /models
#COPY ./ /models
EXPOSE 8080
ENTRYPOINT tensorflow_model_server --rest_api_port=8080 --model_name=MyModel #--model_base_path=/models/

Relevant log output
[libprotobuf FATAL external/com_google_protobuf/src/google/protobuf/generated_message_reflection.cc:2345] CHECK failed: file != nullptr:
terminate called after throwing an instance of 'google::protobuf::FatalException'
  what():  CHECK failed: file != nullptr:
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted

@sabrinakall-imtf,
Could you please confirm if you are using X86 wheel without AVX. In that case we have already an open ticket, so it is better to add a comment there instead of having a new ticket:
#19584
If instead you want to have AVX TCG support in QEMU e.g. on M1 there is already an open ticket at:
https://gitlab.com/qemu-project/qemu/-/issues/164.
Also please take a look at this issue1 and issue2 with the similar error. Thank you!


Cannot deserialize multiple instances when using AxonServer with Jackson Serializer

I'm trying to return a list using the query gateway over axon server, however the response type does not match the desired response type.
return queryGateway.query(GetAllUserDetailsQuery(), multipleInstancesOf(UserDetails.class))

However, instead of returning a List<UserDetails>, it returns a List<LinkedHashMap>... Which leads to an exception when we try to cast it:
   2019-02-02T08:11:29.86-0500 [APP/PROC/WEB/0] OUT com.coxautodev.graphql.tools.ResolverError: Expected source object to be an instance of 'com.example.user.UserDetails' but instead got 'java.util.LinkedHashMap'

Hi @wleroux,
the issue is caused by Jackson being unable to "detect" the type of objects represented in the return value. That is, because the List (which is the outer container) does not specify the form of its contents.
To overcome this, you can ask Jackson to add type information to the serialized form of your messages, in case it is ambiguous.
For example: @JsonTypeInfo(use=Id.CLASS, include=As.PROPERTY, property="class")
Check out the javadoc on @JsonTypeInfo annotation for more details.

Hrm... I'm not a fan of using a discriminator field for this. It adds significant boilerplate code in the query models. Additionally, the framework already has all the information to deserialize the list.
List<UserDetails> userDetails = mapper.readValue(jsonInput, new TypeReference<List<UserDetails>>(){});

This approach doesn't require the discriminator field if we already know the type of list it is.

Not sure if the above supports generics, but here's another approach that does.
public static <T> List<T> parseJsonArray(String json,
                                         Class<T> classOnWhichArrayIsDefined)
                                         throws IOException, ClassNotFoundException {
   ObjectMapper mapper = new ObjectMapper();
   Class<T[]> arrayClass = (Class<T[]>) Class.forName("[L" + classOnWhichArrayIsDefined.getName() + ";");
   T[] objects = mapper.readValue(json, arrayClass);
   return Arrays.asList(objects);
}

Hi Wayne,
the multipleInstancesOf(type) information is not available at the moment serialization is performed. It is merely a construct to make sure only compatible query handler methods are invoked.
For example, you could expect instanceof(A), but if B extends A, a handler that returns B may also be invoked, as each instance of B is also an instance of A. Yet, that doesn't make the serialized type of the response an A; it's still a B.
Note that serializing using XStream should not be a problem, as XStream encloses information about the structure of objects in its serialized format.
Another workaround, which involves much less "boilerplate", is to configure the ObjectMapper to include type information in all ambiguous cases:
https://github.com/FasterXML/jackson-docs/wiki/JacksonPolymorphicDeserialization#1-usage
Do note the security warning though, if you expect messages from untrusted sources.

The type information is available in AxonServerQueryBus#query via QueryMessage#getResponseType. You could pass it to the GrpcBackedResponseMessage via the AxonServer's Serializer class. However, it would not resolve the typing issue you mentioned (e.g.: I asked for type A and I received type C extends type A.)... Although maybe subtyping information would be useful in these cases.
Anyways... I will only be using Axon Framework from trusted sources; the global configuration option works for me. For reference to others, I've added this spring boot configuration:
    @Bean("defaultAxonObjectMapper")
    @Qualifier("defaultAxonObjectMapper")
    fun defaultAxonObjectMapper(): ObjectMapper = ObjectMapper()
            .enableDefaultTyping()
            .setDefaultTyping(ObjectMapper.DefaultTypeResolverBuilder(ObjectMapper.DefaultTyping.OBJECT_AND_NON_CONCRETE).apply {
                inclusion(JsonTypeInfo.As.PROPERTY)
                init(JsonTypeInfo.Id.CLASS, ClassNameIdResolver(TypeFactory.unknownType(), TypeFactory.defaultInstance()))
            })

We discussed within the team whether there is something we could do on the framework level. The conclusion is that the effort vs benefit is not worth it. The "workaround" suggested above should suffice in most cases.


Generate Input types corresponds to Object types

to close #12

Pull Request Test Coverage Report for Build 433960792

19 of 19 (100.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 93.543%

Totals

Change from base Build 433589667:
0.08%

Covered Lines:
375

Relevant Lines:
388

💛  - Coveralls


Trace database can contain paths beginning with two slashes

Found this on the monetdb example:
//etc/ld.so.conf
//home/vagrant/monetdb_hg/holindex/build/clients/mapilib/.libs/libmapi.so.6
//home/vagrant/monetdb_hg/holindex/build/common/stream/.libs/libstream.so.3
//lib/x86_64-linux-gnu/libdl.so.2
//lib/x86_64-linux-gnu/liblzma.so.5
...

It is unclear where these might have come from.

Handled by cf9256c8.


Rustfmt deletes polarity of negative impl

As of current master branch (fd9e7d3e932986a49254de3a7da857a29978d3cc):

$ echo 'impl!Trait{}' | CFG_RELEASE_CHANNEL=dev CFG_RELEASE=1.48.0 cargo +nightly run --bin rustfmt --features rustfmt

Expected:
impl !Trait {}

Actual:
impl Trait {}

This syntax is accepted syntactically by rustc since 1.25.0. Playground: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=a0af137c2df7c45fe1571573ec6a8ad3

That's an odd miss considering rustfmt wasn't "officially" released til 1.31.0 :thinking:
I'm a bit behind on rustfmt PRs and issues but will try to take a look at this after work today

Ah I see, this only occurs in the absence of a trait_ref (compare with impl ! Trait for Foo{}) as rustfmt has an internal assumption that there wouldn't be a negative polarity if there wasn't a trait_ref present.
While I'm not sure what the use case is for a negative impl without a for type (in fairness I'm very unfamiliar with negative impls), it's nevertheless valid syntax and there's no reason rustfmt should drop a negative polarity on an impl item.
Going to mark this as a good-first-issue in case others want to work on it, but please let me know if this is a blocker/higher urgency for you and I'll go ahead and resolve myself.
For anyone interested in working on this, you'll want to take a look at the format_impl_ref_and_type function in items.rs (src/formatting/items.rs).
Things are already taken care of when there is a trait ref:
https://github.com/rust-lang/rustfmt/blob/fd9e7d3e932986a49254de3a7da857a29978d3cc/src/formatting/items.rs#L967-L976
But in cases where there isn't then rustfmt is silently tossing the polarity string. In order to resolve this, we should probably incorporate a new check that looks for the combination of a negative polarity and the absence of a trait ref, and if true then ensure the polarity string (!) is included immediately preceding the type string.
Be sure to include the extra character in the budget computations to prevent any off-by-one issues with edgier cases that run up around the max_width limit, and then incorporate the check both for the case where the type string can fit on one line:
https://github.com/rust-lang/rustfmt/blob/fd9e7d3e932986a49254de3a7da857a29978d3cc/src/formatting/items.rs#L991-L1004
and the case where it has to be multilined
https://github.com/rust-lang/rustfmt/blob/fd9e7d3e932986a49254de3a7da857a29978d3cc/src/formatting/items.rs#L1006-L1019


Adjust to camel 3.8 change in shutdown strategy

[ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #.
[ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough.
[ ] Phrases like Fix # or Fixes # will auto-close the named issue upon merging the pull request. Using them is typically a good idea.
[ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request.
[ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html

I manually merged this to the camel-master branch.

I manually merged this to the camel-master branch.


Update for Log4Shell (CVE-2021-44228)

Add a landing blog post following style of the 2015 "java-issue"
Add a 2021-SV4 for loci_tools.jar
List both on the advisories index
Activate the banner

Doh, I missed during the migration, @sbesson, the fact that we needed to add .html (https://github.com/ome/www.openmicroscopy.org/pull/555/commits/9fa269fb0d8e0fef1abb8de85b935b7be01fd0a9)

Failures are now related to:
http://www.openmicroscopy.org/Schemas/.*

Doh, I missed during the migration, @sbesson, the fact that we needed to add .html (9fa269f)

Yes, as part of the migration, we decided to treat the blog content like posts, with blog becoming a category. Unfortunately, we had a split horizon in terms of permalinks between the old OME blog and the website which means this changed the blog permalinks to use the .html suffix - https://github.com/ome/www.openmicroscopy.org/blob/master/_config.yml#L29
I also prefer the .html-less version and we did something similar for advisories on the past - https://github.com/ome/www.openmicroscopy.org/pull/115. This would require updating the permalink either for all posts or just a category, adding redirect_from for backwards-compatibilty. Should we capture as a RFE?

Pushed a fix, @sbesson. We can make a decision after the formats meeting, but if we can't be more definitive today, I'd suggest we get this released ASAP. (Note: bfmatlab.zip ships logback)


How do I hide Visual/Normal indicator at the top right of the page?

I can't seem to find a way for hiding this

It feels quite intrusive, maybe you could change Normal to just N & Visual to just V.
And since we are already notified of the change, I don't think it's necessary for it to be there all the time.
It would be great if you could add an option to hide this indicator.

It's there already.

@vipzhicheng That setting works just for the session when I uncheck it. After restarting Logseq, the indicator appears again even when it's not enabled in the settings.
See the screenshot where I'm showing a journal page & the settings in another window:

I released a patch, please have a test.

Thanks! It's working.


Container for non-sidenav-layouts

For layouts not using the <md-sidenav-layout>, dark themes can not be used, as the background does not change. Due to that, the text gets invisible and form items look bad.
To understand, what I mean, check out the plunkr. Basically I took your template and changed the theme: http://plnkr.co/edit/w4v95im2irvNm4dAzQ5k
I was looking for some container class or element, but wasn't lucky in finding any.

Layout component it's not even started yet. Does not have an issue tracking the status either.

If this is covered by the layout components, then this issue should be closed.
BTW, found a workaround by wrapping everything within a <md-sidenav-layout>.

We should have something for this, but as a workaround you can simply create a css class that uses the appropriate color, e.g.
.my-background {
  background-color: md-color($background-palette, background);
}


Status bar and padding on Expo

When using expo with a translucent status bar, top padding is correct.
But when setting the status bar to Hidden or not Translucent (with app.json or with StatusBar class), padding top is not correct anymore. Seems like padding calculations still use the status bar height when it should be 0.

Yes, I confirm this problem.
The problem is that this module treats Expo always use translucent header and react-native init always not.
https://github.com/benevbright/react-navigation-collapsible/blob/7b6825d34004cc17f365761c9a0c9c88c23bc440/src/utils.ts#L36
The status header height should be calculated according to the user option.
related with #116

Hi @benevbright, do you think it will be fix soon ?
Thanks

Not sure if it's related, but I have a specific height for my header which is 60.
I can notice when I use the createCollapsibleStack, a small part (on top) of my component goes behind the header.

Hi, @ozerty
There was a problem when using custom headerStyle.height. https://github.com/benevbright/react-navigation-collapsible/pull/130 This PR fixed it.
I will fix the status problem soon and release them together.

@Keplyx Please check this PR, https://github.com/benevbright/react-navigation-collapsible/pull/131.
It's not a smart solution but you can prevent the status height from being calculated.

v5.6.0 includes #130 and #131.


Support upscaled textures.

Create class to search for upscale textures and return the found textures.
godbolt

Did some work in openviii_cpp_wip to make it easier to find extracted files. and to override the coo. Still more work to do.


Make usage of BNN in DKL optional

Codecov Report
Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (8e97fb8) 95.59% compared to head (62b972b) 95.53%.

Files
Patch %
Lines

gpax/models/vidkl.py
72.72%
3 Missing :warning:

gpax/models/vi_mtdkl.py
80.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #78      +/-   ##
==========================================
- Coverage   95.59%   95.53%   -0.07%
==========================================
  Files          51       51
  Lines        3930     3938       +8
==========================================
+ Hits         3757     3762       +5
- Misses        173      176       +3

Flag
Coverage Δ

unittests
95.53% <75.00%> (-0.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


HTTP issuer being published instead of HTTPS in .well-known/openid-configuration

[x] I read and understood how to enable logging

Issue / Steps to reproduce the problem
N/A
Hello there,
I have IdSrv set up and I have only a HTTPS binding on it in IIS. However, when I browse to .well-known/openid-configuration I see that all the urls are HTTP instead of HTTPS.
{"issuer":"http://xxx.com","jwks_uri":"http://xxx.com/.well-known/openid-configuration/jwks","authorization_endpoint":"http://xxx.com/connect/authorize","token_endpoint"....

The exact same code works just fine in my testing environments and the discovery endpoint correct exposes the issuer. What could I be doing wrong?

You probably need to setup the forwarded header config / IIS integration
https://github.com/aspnet/Docs/issues/2384


Trouble with time.h while building on Macbook

I tried building this project and was able to build the libs, but when I try to make the main program it gives me an error centered around time.h. I have provided a link to pastebin with the entire build output.
Here.

Do you have clang installed?

According to this you can use "any nonzero integer value" which should be fine since the time measurement is relative. Try putting anything else greater than zero in there instead of TIME_UTC.

I do have clang installed
$ clang --version Apple LLVM version 9.0.0 (clang-9<IP_ADDRESS>) Target: x86_64-apple-darwin16.7.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin
I changed the time value to 1 and now its complaining memcopy. pastebin: here


Getting error "Missing argument 'thread_id'" on invoking edit-document API

I'm trying to edit a quip sheet using the edit-document API but I'm getting  'missing argument: thread_id' error even though I'm passing a valid thread id.
Request: {"thread_id":"gEAoATdxc4wa", "content":"Hello there", "section_id":"s:cVeACA8SOuG_cVeACApWRuh"}
Response: {"error":"application_error", "error_code":400, "error_description":"Missing argument 'thread_id'"}

Is there anything obvious I'm missing in my request?

You may be missing company_id. Refer to this doc for admin. I had the same problem but this helped me.
https://quip.com/dev/admin/documentation#edit-a-document

You may be missing company_id. Refer to this doc for admin. I had the same problem but this helped me.
https://quip.com/dev/admin/documentation#edit-a-document

Hi, did you resolve this as I'm having the same issue.
I'm passing in a valid thread_id in the body and have the company_id set in the URL. If I copy the body that I'm sending from Salesforce directly into Postman it works fine. This is being done in a SF sandbox.
13:04:45:283 USER_DEBUG [326]|DEBUG|System.HttpRequest[Endpoint=https://platform.quip.com/1/admin/threads/add-members?company_id=JKVIMy, Method=POST]
13:04:45:723 USER_DEBUG [331]|DEBUG|Body request = {"thread_id":"eNiVAbyDICco","member_ids":"KP*NRW"}
13:04:45:723 USER_DEBUG [330]|DEBUG|Body response= {"error":"application_error","error_code":400,"error_description":"Missing argument 'thread_id'"}


Rename Main Package

Currently the name of our main package is src, but in order to make the program more user friendly we should change it to the name of the acutal program.
The DS_store is in a bad place in the code, we should either place it in a user-level git-ignore or project-level git-ignore

Main package and folder have been updated and changed in the main file repository. This issue was fixed on January 31st, 2022.


Upgrade TypeScript to v4.9.5

While working on #4065, I wished for the satisifies operator, which was added in TypeScript v4.9. This upgrades TypeScript to v4.9.5.
Full release notes at https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-9.html.
Because Yarn patches TypeScript to make it work with Plug 'n' Play, upgrading TS also required upgrading Yarn.

Notes for next time:
yarn upgrade-interactive
yarn set version <version>
yarn dlx '@yarnpkg/sdks'

rm -rf node_modules/.cache


module "QZXing" is not installed in qml @ pelagicore/meta-pelux

Hello @TM9412 and thanks for your contribution. Could you give a bit more context on what are you trying to include in the target image. Is it the barcode processing library QZXing (https://github.com/ftylitak/qzxing)? Can you explain what modifications did you make to produce the error?

Hey Hi, @GordanM
I am trying to include QR-code feature in this meta-pelux so for that i added this library QZxing and when i run my project it is showing
warning  : QML Image: Invalid image provider: image://qzxing/encode/
and i am not get the qrcode so i added import QZXing 2.3 but i get this error in run time
error : module "QZXing" is not installed

@TM9412 the "QZxing" library has to be installed on the target image if you would like to use. Have you done this modification to the target image?
This would usually include creating a Yocto recipe that compiles/includes this QML module to the target image.

Hi @GordanM
I have done this modification
How to installed "QZxing" library on the target image  ?

@TM9412 you would need to create a Yocto recipe that installs the required libraries to the system and include the component in the target image. Do you have experience with Yocto/OpenEmbedded?
I've found a really old example of a Yocto recipe for "QZxing": https://github.com/nickdademo/meta-nickdademo/blob/master/qzxing/qzxing_1.3.bb. Maybe you could create a new recipe based on it? Our platform currently doesn't have an intention in being the holding layer of that component as we are not using it currently. But you could always add another layer to our base platform and use it just in your project.
I would recommend to ask the maintainer of the "QZxing" library to provide you with some support in creating the Yocto recipe, as he would be the best person to ask about "how to" and "where to" install the component on the target image. It might be possible that she/he has done it before as well.

@TM9412 if you need more information on how to use and extend PELUX you can always refer to the documentation in the Software Factory (http://pelux.io/software-factory/master/). It should give you a nice starting point and explanation on how to use the base platform and extend it with your components.
For example, here is an extract how to add your new layer to the project: http://pelux.io/software-factory/master/swf-blueprint/docs/articles/baseplatform/creating-a-new-layer.html
and here is an example how to structure and create a Yocto recipe using the template C++ service as a base: http://pelux.io/software-factory/master/swf-blueprint/docs/articles/templates/index.html

Closing this issue as it is outside of the context. Feel free to open another issue when you get more progress, we'd be happy to help then.


filter out POST /api/graphql spam from sndev logs

Description
Since a Next.js update, the dev environment has started logging HTTP requests, which has caused the logs to become cluttered with logs of POST /api/graphql requests. This is an actual issue of  Next.js, see the related discussion here: https://github.com/vercel/next.js/discussions/65992.
This PR adds a workaround to filter out these logs by using grep in the sndev logs command.
Screenshots
before / after

Yes, that's intentional. I don't want to make the filter too broad to avoid the risk of filtering out legitimate logs. I'm focusing on filtering the graphql calls, as they are the primary source of pollution.
I've changed the command to not use -P, can you try it now?


“python multiview.py --input ./data/Original_img --output ./data --gray --binary --blocksize 41 --C 5 --skeletonize”

What is wrong with using command “python multiview.py --input ./data/Original_img --output ./data --gray --binary --blocksize 41 --C 5 --skeletonize” without response?

What is wrong with using command “python multiview.py --input ./data/Original_img --output ./data --gray --binary --blocksize 41 --C 5 --skeletonize” without response?

Thanks for your question.
I have just successfully re-run this command “python multiview.py --input ./data/Original_img --output ./data --gray --binary --blocksize 41 --C 5 --skeletonize”.
During the successful running of the code, it will immediately provide the information of the image currently being processed by “multiview.py”, and after the operation is completed, two new folders will be obtained under the "data" folder, namely "gray" and "skeleton".
Could you please describe “without response” in more detail?

I solved this problem by reconfiguring the runtime environment, but I encountered a new problem when using the train.py file: File "Fossil-ID-Multiview-Deep-Ensembles- main/train.py", line 39, in
from timm.scheduler import create_scheduler_v2, scheduler_kwargs
ImportError: cannot import name 'create_scheduler_v2' from 'timm.scheduler'.
I think this may be a problem with the version of timm, what is the version of your timm?

Thanks for your reply.
I solved this problem by reconfiguring the runtime environment, but I encountered a new problem when using the train.py file: File "Fossil-ID-Multiview-Deep-Ensembles- main/train.py", line 39, in
from timm.scheduler import create_scheduler_v2, scheduler_kwargs
ImportError: cannot import name 'create_scheduler_v2' from 'timm.scheduler'.
I think this may be a problem with the version of timm, what is the version of your timm?

Thanks for your reply.I solved this problem by reconfiguring the runtime environment.


Support multiple databases

Checklist

[X] There are no similar issues or pull requests for this yet.

Is your feature related to a problem? Please describe.
Sometimes we need multiple databases for a project,
but in this application I haven't found how to do that.
Describe the solution you would like.
One possible solution could be to pass the sessionmaker factory instead of the engine.
SQLAlchemy documentation page about routing:
https://docs.sqlalchemy.org/en/20/orm/persistence_techniques.html#session-partitioning
Describe alternatives you considered
Multiple instance of Admin()???
Additional context
I found a PR with sessionmaker:
https://github.com/aminalaee/sqladmin/pull/542

Hello - thanks in advance for an awesome open sourced repo! I'm also interested in how we can support a connection to multiple databases. On thing I've tried is to have multiple Admin view associated with a single FastAPI app.
admins = [
    Admin(app, create_engine(database_dsn), base_url=f"/{customer_name}", title=customer_name)
    for customer_name, database_dsn in multiple_databases
]
for admin in admins:
    admin.add_view(MyView)

This builds correctly but when we then dig into each admin app, the links point to the wrong Admin app for the customer. For example, if I'm looking at models for customer B (url=mysite.com/customer-b), all the links in the app will point to customer A (url=mysite.com/customer-a/item). I've traced the issue to to this spot https://github.com/aminalaee/sqladmin/blob/main/sqladmin/application.py#L406 where we are mounting the app.
Happy to contribute to solve for the multi-database use case but wanted to see if anyone had any ideas


Add Lucene version to UploadedSegmentMetadata

Description
This PR associates the Lucene version with each uploaded segment file metadata entry that is maintained in remote store.

For the segment files that house the segment data (.cfe, .cfs, etc.), we track the Lucene version as captured in the respective SegmentInfo instance.

For the segment_N files that house the information on segments, we track the Lucene version used for the commit as captured in the respective SegmentInfos instance.

Related Issues
Resolves #7722

Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Some integration tests are failing, looking into those

Summary of failing tests:

org.opensearch.remotestore.RemoteStoreRefreshListenerIT.testRemoteRefreshRetryOnFailure - https://github.com/opensearch-project/OpenSearch/issues/7703
org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testDeleteOperations - Checking if related to https://github.com/opensearch-project/OpenSearch/issues/7643
org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testUpdateOperations - Checking if related to https://github.com/opensearch-project/OpenSearch/issues/7643
org.opensearch.search.backpressure.SearchBackpressureIT.testSearchTaskCancellationWithHighCpu - https://github.com/opensearch-project/OpenSearch/issues/7972
org.opensearch.snapshots.DedicatedClusterSnapshotRestoreIT.testIndexDeletionDuringSnapshotCreationInQueue - https://github.com/opensearch-project/OpenSearch/issues/5031
org.opensearch.index.shard.RemoteStoreRefreshListenerTests.testRefreshSuccessAfterFailureInFirstAttemptAfterSnapshotAndMetadataUpload - Need to check
org.opensearch.index.shard.RemoteStoreRefreshListenerTests.classMethod - Need to check
Multiple org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test { ... } tests - Need to check

Summary of new failures
Build https://build.ci.opensearch.org/job/gradle-check/17753/
N/A
Build https://build.ci.opensearch.org/job/gradle-check/17752/#showFailuresLink

org.opensearch.cluster.service.MasterServiceTests.testThrottlingForMultipleTaskTypes, org.opensearch.cluster.service.MasterServiceTests.classMethod - https://github.com/opensearch-project/OpenSearch/issues/5958

Build https://build.ci.opensearch.org/job/gradle-check/17754/#showFailuresLink

Flaky tests (covered in previous comment)

Build https://build.ci.opensearch.org/job/gradle-check/17877/

org.opensearch.indices.replication.SegmentReplicationTargetServiceTests.testStartReplicationListenerSuccess - opened a new issue https://github.com/opensearch-project/OpenSearch/issues/8136

LGTM

For the failing test org.opensearch.index.store.RemoteSegmentStoreDirectoryTests.testUploadMetadataNonEmpty, it appears that there is a deviation in the segmentInfos used ...
https://github.com/opensearch-project/OpenSearch/blob/68c1c86897a59fcffa77bfecc06641326e5e5199/server/src/test/java/org/opensearch/index/store/RemoteSegmentStoreDirectoryTests.java#L79-L82
... vs. the segmentFiles used for the tests, leading to the CorruptIndexException:
https://github.com/opensearch-project/OpenSearch/blob/68c1c86897a59fcffa77bfecc06641326e5e5199/server/src/test/java/org/opensearch/index/store/RemoteSegmentStoreDirectoryTests.java#L625-L626
In local repro I see 0 segments in the segmentInfos.
Updating the segmentInfos to be correct might require updates in multiple tests. Can this be tracked as a separate issue?

Updating the segmentInfos to be correct might require updates in multiple tests. Can this be tracked as a separate issue?

No, if the test is failing due to changes in current PR, we need to fix the test or code. We won't be able to merge with failed build.

Build https://build.ci.opensearch.org/job/gradle-check/18927/ :

org.opensearch.cluster.allocation.AwarenessAllocationIT.testThreeZoneOneReplicaWithForceZoneValueAndLoadAwareness => https://github.com/opensearch-project/OpenSearch/issues/3603
org.opensearch.indices.replication.SegmentReplicationIT.testScrollCreatedOnReplica => https://github.com/opensearch-project/OpenSearch/issues/7556
org.opensearch.remotestore.SegmentReplicationRemoteStoreIT.classMethod => Need to check
org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testStartReplicaAfterPrimaryIndexesDocs => Previously reported in https://github.com/opensearch-project/OpenSearch/issues/5669, new issue created: <>
org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testReplicationAfterForceMerge => https://github.com/opensearch-project/OpenSearch/issues/8279
org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testNodeDropWithOngoingReplication => https://github.com/opensearch-project/OpenSearch/issues/8279
org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testDeleteOperations => https://github.com/opensearch-project/OpenSearch/issues/7643
org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testUpdateOperations => https://github.com/opensearch-project/OpenSearch/issues/7643
org.opensearch.snapshots.RestoreSnapshotIT.testRestoreInSameRemoteStoreEnabledIndex => https://github.com/opensearch-project/OpenSearch/issues/8352
org.opensearch.snapshots.RestoreSnapshotIT.classMethod => Need to check

Build https://build.ci.opensearch.org/job/gradle-check/18924/ : same as above

Build https://build.ci.opensearch.org/job/gradle-check/18926/ : same as above

@mch2 @dreamer-89

org.opensearch.indices.replication.SegmentReplicationAllocationIT.testSingleIndexShardAllocation is likely flaky, as per https://github.com/opensearch-project/OpenSearch/issues/8279


Fix growMargin() not returning modified Rect2/Rect2i in Mono

Changed growMargin() in both Rect2.cs and Rect2i.cs to return the modifications made to the passed value, in Mono.
This fixes #38217 .

Cherry-picked for 3.2.2.


[enhancement] Add support for ArcGIS for Desktop 10.2

Hello.
Is there a chance to create a version that works in ArcGIS 10.2?

Yes, I will work on this here and post it when it is done

There is a 10.2 version

Would you be so kind as to upload the compiled version of the project site: http://www.chrisstayte.com/Applications/ArcmapToGoogleEarth/?

I'll add it the website here when I get home.Thanks

Thank you. It's working :)


revert(plugin): restore service integration SDKv2 files

About this change—what it does
Reverts ServiceIntegration resource/datasource.

tests.


Generate with project and tests targets in command line

Is it possible to set custom project and test target in command line for gen command?
Is it possible to copy tests inside module folder "Tests"?

Hi, @marko1503!

Is it possible to set custom project and test target in command line for gen command?

Check the documentation for the generamba gen command: https://github.com/rambler-ios/Generamba/wiki/Available-Commands#module-generation

Is it possible to copy tests inside module folder "Tests"?

I haven't tried it, but I don't think anything may stop you.


Calculate Position on Tag side

Step 1: What do you want?

Improve code (and need help).

Step 2: Describe your environment

Arduino IDE version or Toolchain: Arduino IDE 1.8.13
dw1000ng Library version: latest
Arduino device: Teensy 4.1
Used adapter board: Zhonglian brekaout

Step 3: Describe the problem

Affected file(s) or example(s):

I al currently working with several Tags and 3 Anchors. I would like to perform the calculations to get the tag location on the tag side (instead of doing it by the main anchor). Do you think it's possible ?

Steps to reproduce (for bugs only):

For the moment I have switched several functions (example: DW1000NgRTLS:transmitRangingInitiation is done in the tag side and DW1000NgRTLS::tagTwrLocalize is done in the anchor's side)

Observed Results:

What happened?  This could be a description, log output, etc.

Expected Results:

What did you expect to happen?

Relevant Code:
  // TODO(you): code here to reproduce the problem

Hi @CarlosAguilar1986, yes it's possible. You have to modify the DW1000NgRTLS files (this implementation is just an example of extraction) to not return the range result to the anchors or make your own workflow taking it as an example.
DW1000NgRTLS files are a simple implementation of the RTLS standard ISO/IEC 24730-62, take a look at it.
There are probably other closed issues with a similar questions.

Ok, thanks I will try that :)

I don't remember well about the flow. You should transform anchor main's code like anchor B/C and all Anchors are supposed to send the range to the Tag. The Tag should be like Anchor main. It's harder than I say to you.

Ok thanks, yes for the moment I am doing something quite similar. In my case The three anchors send Blinks (instead of having one BLINKI have BLINK_1, BLINK_2 and BLINK_3) and the Tag does the transmitRangingInitiation with each anchor but I have weird results sometimes (maybe some interferences I guess ?).
Then I read in the official decawave documentation (APS013 APPLICATION NOTE, The implementation of two-way ranging with the DW1000, Page 5 at the bottom) :
"In the case where it is necessary for the tag to be aware of the range, the anchor may optionally send an immediate message to the tag with the calculated TOF"
So I was wondering if your library had this option implemented already since I wanted some better/cleaner solution than what I had.

In our case, the "optional message" would be Range-confirm(Anchor A and B) or activity-finished(Anchor C). In your case, you could modify one of the last steps of the flow (transmitRangingConfirm or transmitActivityFinished) and send back the range in one of two optional final params.
This is an example of a final step payload of an optional message in the RTLS standard:

Obviously, if you don't want to respect the standard you could refactor the entire DWM1000RTLS class personalizing the payloads. Decawave in their examples does not respect perfectly the standard.

Yes, I see now, thanks again for your time :)


How can I use this library to write automated integration test?

I would like to know if possible how I can use this tool to perform some integration testing for a visual studio extension. I will need to write end to end tests from the time a user starts interacting with the visual studio extension, including UI tests. I have checked for any documentation online with no success.

@sailro may be able to help you out, but this library is no longer maintained.
The broken links to examples in PTVS can be fixed by replacing "master" with "v3.2.1", but that branch is nearly five years old, which is about when we stopped using it. But the examples and code wrapping DTE and Windows Automation commands may be helpful still.
The basic functionality is included in Microsoft.VSSDK.TestHostFramework.dll (in PublicAssemblies in your install), which should let you annotate tests to launch VS and give you the DTE object. I think the rest of the framework used at Microsoft is still internal-only.

Hello @paulodero, I'm going to try to add a minimal sample soon to this repo.

@paulodero I would highly recommend using https://github.com/josetr/VsixTesting for this.


feat(filename): Support non json file extensions

This would fix https://github.com/Belphemur/node-json-db/issues/123

Coverage increased (+0.02%) to 94.853% when pulling e2191246c50d9477a43c038975589a9d1da5a58d on Drarig29:extension into 8ebd600407a8475b247723d66f476b644f84e524 on Belphemur:develop.

Hello,
Thank you for this.
Can you update the readme to document this feature ?

Great first PR :)
Thank you

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


The app redirects the user to the landing page.

Redirect it to the dashboard page instead https://rake.now.sh/#/dashboard/labelled-images @bapspatil

Done.

On picker screen, it'll redirect to Dashboard.
On image labeling screen, it'll redirect to Dashboard/Labelled-Images.

ok 👍


Fast Sync Metrics - Add block accumulator metrics

Retrospective ticket for adding block accumulator metrics.
Related PR #3407

Ticket closed by PR #3407


The ability for the client to reconnect itself

Summary
Client should reconnect itself when it disconnects from the websocket
What is the feature request for?
The core library
The Problem
I have a systemd user service that starts up my bot on system startup, as follows:
[Unit]
Description=linaSTK
After=multi-user.target
After=network-online.target
Wants=network-online.target

[Service]
WorkingDirectory=%h/Bots/lina
ExecStart=/usr/bin/python %h/Bots/lina/src/main.py
Type=idle
Restart=on-failure
RestartSec=15

[Install]
WantedBy=default.target

The problem is that if the websocket disconnects (which can happen randomly, sometimes after a few hours), it will treat it as if it exited successfully (because it exits with signal 0 if it disconnects) and will not restart the service. If I then the Restart property to always, it would then making shutting down the bot using commands not possible as the init system will restart it afterwards.
The Ideal Solution
There should be a logic in the client where if the websocket was to disconnect, it will attempt to re-establish a connection to the websocket, just like discord.py.
The Current Solution
No response
Additional Context
No response

While I do plan to look into this in the future, it's probably going to have to wait until a proper rewrite. As a temporary solution however, you could try to wrap the bot starting code in a loop. If a disconnect also returns some specific error you can try to catch that in the loop and only restart then to reduce "scuff"

If a disconnect also returns some specific error

Well, it does not give an error if it disconnects, it just exits immediately as if nothing happened

If a disconnect also returns some specific error

Well, it does not give an error if it disconnects, it just exits immediately as if nothing happened

You could just throw it into a loop for now.


Update NewtonRaphsonMethod.html

update

Please pull the main branch so that conflicts may not arise when you prepare the next pull request


Pastanaga Editor: No indication of links in the edit mode

Go to volto.kitconcept.com
Login admin:admin
Create a new page
Add some text tile
Select a term and add a link
-> The text will not show an underline to indicate it is a link
-> If you hit the save button the link will show up though

@nileshgulia1 that shouldn't be too hard to fix. Could you please have a look at it on Monday?

Well, actually it is a difficult one to deal, and maybe need to learn more about draft-js internals.

I did something similar already for another project. I will take a look

@tisto I cannot reproduce this issue anymore... already fixed?

@jackahl did you kit the save button?

Fixed long time ago.

Fixed long time ago.


No warning about it taking several hours for the subscriptions to become visible after moving

Please add a warning that movement might take several hours and remind them to check the filters for the moved subscription, as well!

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

ID: da261ee4-3348-b520-a27c-98f9d9ef40cc
Version Independent ID: 13d12189-ee46-8058-dd99-058adc69f1c5
Content: Add an existing Azure subscription to your tenant - Azure Active Directory
Content Source: articles/active-directory/fundamentals/active-directory-how-subscriptions-associated-directory.md
Service: active-directory
Sub-service: fundamentals
GitHub Login: @eross-msft
Microsoft Alias: lizross

@Suzuko123 Thank you for your feedback . We will investigate and update further.

Assigning your feedback to the content author, @eross-msft , for review.

@Suzuko123  I updated the article to include, "It can take several hours for everything to show up properly. If it seems to be taking too long, make sure you check the Global subscription filter for the moved subscription, to make sure it's not simply hidden." If you feel like more needs to be said, please open a new issue.
@MarileeTurscak-MSFT  #please-close

Closing as per author comment.


User and PRIMARY/User login treat as two users at the store

Description:
We can login to primary domain using both username and PRIMARY/username with the same password. But at the store, they will be shown as two users. Applications created at username login will not be listed at PRIMARY/username login. User logged in shown (session user at login) at the store is username and PRIMARY/username respectively.
But for the secondary domain, both login using sec-user and DOMAIN/sec-user treat as the same user. Applications created at either login will appear in the application list for both logins. And, the session user at login will always be DOMAIN/sec-user for both logins.
Issue is with the session user at primary domain login. It works fine for secondary domain.
Suggested Labels:

Suggested Assignees:

Affected Product Version:
APIM 2.1.0
OS, DB, other environment details and versions:
Steps to reproduce:

Create a user for the primary domain (user1)
Login to store as user1 and create an application.
Then, login to store as PRIMARY/user1 with the same password. Created application is not come under the application list.

Related Issues:

I’m closing this issue because it has been inactive for more than two years. Please reopen if you still encounter this issue with the latest version.


Multi-JSF-Installer broken for MyFaces

Commit 9738ff27a0d0ee8e2cf8d8cd3cd2827507042b7e missed to change weld-core-jsf to weld-jsf in wildfly/jsf/multi-jsf-installer/src/main/resources/myfaces-injection-module.xml.

Moved the issue to JBoss Issue Tracker: https://issues.jboss.org/browse/WFLY-10096


Parallel Container Layer Unpacking

What is the problem you're trying to solve
The current ContainerD fetches layers in parallel, but unpacks them in a single thread layer by layer sequentially.
Describe the solution you'd like
Proposal:
We propose a config below in ContainerD (/etc/containerd/config.toml) to support unpacking images in parallel.
[plugins."io.containerd.grpc.v1.cri".containerd.overlayfs]
  unpacking_mode = "parallel"

Key Changes:  ContainerD Handlers + Content
This option reuses the existing FetchHandler and Content to support pre-decompression during the fetch phase of each layer. The actual decompression happens directly following the fetch process as the graph below. Then the unpack or snapshot handling becomes a light operation by just renaming the pre-decompression folder to the desired overlay path.

Fetch

When ContainerD config (/etc/containerd/config.toml) unpacking_mode = "parallel" is set, replace FetchHandler in pull.go with FetchUnzipHandler created below.
Create a new FetchUnzipHandler similar to FetchHandler, which enables the unzip option in Fetch.
Add unzip option to Fetch function; Update Content to support pre-decompress buckets as part of its content.Store APIs for content lifecycle management, i.e., A fetched gzip file and corresponding pre-decompressed fs folder will have the identical lifecycle, for example, create and delete.

Unpack and Snapshot processing

Update apply function to support an option to apply with the pre-decompression folder.
Update s.store.ReaderAt implementation, the content store knows if there is a pre-decompress bucket for a layer, if yes, it will return a list of file paths as byte[]. Alternatively, maybe we will add a new method s.store.FolderAt to Provider.

Additional context
Who should enable this feature?

Those who use disks with high in-parallel IO support. For example, PD or LocalSSD is designed for a deeper IO queue to get better throughput by in-parallel IO operations.
Those who use large containers and are sensitive to slow pod cold start. For example, containers with GPU libraries and frameworks (> 4GB). All GPU workloads can be put into this category. In contrast, previously top containers without using GPU were significantly smaller (< 500MB).

Who should NOT enable this feature?
HDD with high seek time for random read and write.
Potential Benefit
If user can improve disk performance, the image pull latency by this proposal can be reduced significantly. For example, Tao was able to achieve 3X faster image pull (120 seconds -> 40 seconds) for pulling a popular container: gcr.io/deeplearning-platform-release/base-cu113:m106 (5.4 GB) with a common setup of a deep learning node (2500 GB PD-SSD, 32 vCPUs).

/cc @elfinhe
/cc @bobbypage
/cc @qiutongs
/cc @samuelkarp

/assign @ike-ma

I'm not quite back from leave, but some context here:
The sequential layer unpack is a consequence of snapshot creation requiring a committed parent, and an individual snapshot not being committed until all of its content has been written.  For the overlay snapshotter, the backing filesystem does not have a concept of a "committed" lowerdir, and containerd unpacks without an active overlay mount anyway (opting to write whiteout markers explicitly).  Because the overlay filesystem does not have a dependency on a committed parent-child relationship, we can implement a further optimization of writing out the actual snapshot in parallel.  For some storage devices (such as the PD-SSD device tested above), there are performance gains from concurrent IO over sequential IO and this approach leads to faster overall image pull times.

Thanks @dmcgowan for the comment. I have prepared a draft PR: https://github.com/containerd/containerd/pull/9138
Wonder if you have any high level comments for the first version, where the uncompressed layers are consumed directly during Apply with some basic config wiring.


Fix SonarQube violations

This PR fixes the violations for the following SonarQube rules:
https://rules.sonarsource.com/java/RSPEC-4973
If you do no want to receive automated PRs for SonarQube warnings, reply to this PR with 'STOP'

Reproduction:

clone project
mvn verify


Use new URL to fix Windows descriptor location

Trying to fix the Windows issue with the path. see https://github.com/scaffold-eth/scaffold-eth-2/pull/413#issuecomment-1645295102
@Pabl0cks could you check?

@Pabl0cks could you check?

Thx @carletex for working on this bug 🙌. Just tried the fix but I'm still getting error.
Added a console.log('templateUrl: '+templateUrl.href); after const templateUrl = new URL(`file://${templateFileDescriptor.path}`);, here is the error msg and console logs:
[23:36:23] 📁 Create project directory E:\GitHub\scaffold-eth-2-readme-scaffold-config\test6 [started]
[23:36:23] 📁 Create project directory E:\GitHub\scaffold-eth-2-readme-scaffold-config\test6 [completed]
[23:36:23] 🚀 Creating a new Scaffold-ETH 2 app in test6 [started]
templateUrl: file:///E:/GitHub/scaffold-eth-2-readme-scaffold-config/templates/base/.gitignore.template.mjs
templateUrl: file:///E:/GitHub/scaffold-eth-2-readme-scaffold-config/templates/base/packages/nextjs/.gitignore.template.mjs
templateUrl: file:///E:/GitHub/scaffold-eth-2-readme-scaffold-config/templates/extensions/hardhat/packages/hardhat/.gitignore.template.mjs
[23:36:23] 🚀 Creating a new Scaffold-ETH 2 app in test6 [failed]
[23:36:23] → Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'e:'
ERROR Error occurred Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'e:'
    at new NodeError (node:internal/errors:399:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/resolve:1059:11)
    at defaultResolve (node:internal/modules/esm/resolve:1135:3)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ESMLoader.import (node:internal/modules/esm/loader:525:22)
    at importModuleDynamically (node:internal/modules/esm/translators:110:35)
    at importModuleDynamicallyCallback (node:internal/process/esm_loader:35:14)
    at file:///E:/GitHub/scaffold-eth-2-readme-scaffold-config/dist/cli.js:207:82 {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME',
  context: [Object: null prototype] {}
}
Uh oh! 😕 Sorry about that! Exiting...

The templateUrls look good!

Just tried the fix but I'm still getting error.

But is it in the same place? You mentioned it was throwing (exiting) here const template = (await import(templateUrl.href)).default;
Could you test if now the program runs below that line? If the error now is here....
const targetPath = path.join(
    targetDir,
    templateFileDescriptor.relativePath.split(templateTargetName)[0],
    templateTargetName
  );

we might have solved the issue :) (it'll be a matter of doing the new URL() to the template descriptor)
@Pabl0cks

@carletex thanks for the investigation and initial bugfix! 🙌
I made some changes:

Use fileURL for both the dynamic imports
Add fileURL straight into the descriptor
Update the descriptor type to hold the fileURL as well
Use the static method url.pathToFileURL instead of creating an instance and interpolating a string with the protocol

@Pabl0cks can you give it a go? I'm guessing the previous error might be related with the string interpolation which is not happening anymore.

I was applying @carletex fix to argsFilePath after realizing my new error was there and not in templateUrl, and found your commit @dgrcode !! :)
Tried it and it's working great, thanks to both of you 🙌

Thanks for the clean fix @dgrcode and all the testing @Pabl0cks !!
Merging this and will publish to npm in a bit.


Create a Pull Request Template for this repo

Add a pull request template, so that when someone raises a pull request, they can view a checklist before raising the PR

working on it


Fix error of invalid keyPath when bind property

Fix problem of crash when skin changed.
Object key path binding is missing KVO unbinding function KVO called when object released.


Fix modal Blueprint components not closing correctly

UI/UX: Fix modal Blueprint components not closing correctly
Summary: Fixes issue #1147 introduced by PR #874, by introducing a better fix for the original issue addressed in PR #863 that led to PR #874. This PR breaks compatibility with Internet Explorer 11.
Description
WIP
Changelog

Remove unnecessary props from the Blueprint Dialog component
Reverts the hotfixes applied in PRs #863, #874

This fixes modal Blueprint components not closing when the user clicks outside of the overlay element

Applies a new CSS fix to the Overlay and Dialog components to allow the user to scroll long dialogs with the browser scrollbar and the mouse

This does not affect the user's ability to scroll the dialog with the arrow keys or Page Up/Page Down keys

Verification instructions
WIP
Last updated 28 May 2020, 11:45PM

Pull Request Test Coverage Report for Build 5066

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

Totals

Change from base Build 5058:
0.0%

Covered Lines:
3177

Relevant Lines:
7464

💛  - Coveralls

Kudos!


[Travis] also test against newly released Python 3.5.0

Python 3.5.0 was released a few days ago, and Travis already added support for it.
Let's see if it works...

it works!


feat: theme

just curious: are there perf measurements on enabling and disabling theme?

No I didn't make any performance measurements as this worked right away and it is the way other plugins and even telescope.nvim apply themes for pickers


Size of license definition popover is different for every license

Description
The size of license definition popover changes and it depends on the content placed inside. This variation feels odd and a fixed width, like the one defined in mockups, looks more balanced.
Reproduction

Search for anything.
Open the filter sidebar.
Click on the question mark of CC BY-NC license to see its definition.
Now click on the question mark of CC BY-ND license.
Compare the popover size difference.

Screenshots

CC BY-NC
CC BY-ND

Resolution

[ ] 🙋 I would be interested in resolving this bug.

I looked into the issue. Adding w-60 class on div with popoverRef should fix this. But style rule for w-60 class seems to be missing in our version of Tailwind. The next best I can use is w-64. This works perfectly.
Here is how it looks with w-64

@ritesh-pandey if you'd like to make a PR with that change, go for it! That looks pretty good based on the screenshot.

Git pre-commit hook is failing for me with following message:
test/playwright/utils/navigation.ts:15:25 - error TS2307: Cannot find module '~/locales/ar.json' or its corresponding type declarations.

15 import rtlMessages from '~/locales/ar.json'
                           ~~~~~~~~~~~~~~~~~~~

Found 1 error in test/playwright/utils/navigation.ts:15

 ELIFECYCLE  Command failed with exit code 2.
husky - pre-commit hook exited with code 1 (error)

Is there any problem in my setup?

@ritesh-pandey that's a bug we're fixing (see https://github.com/WordPress/openverse-frontend/issues/1598).
In the meantime if you run pnpm build once you'll have the necessary locale files on your machine. It's a good temporary fix to the problem.


Add Word Error Rate evaluator

A WER evaluator would be a nice addition to Cadmium IMO.
I can work on a PR if you're ok with it.
More evaluators can be implemented so I'm planning to create a Cadmium::Evaluators module.

Very interesting. I'd definitely be open to a PR for that.

Great !


feat: add jwt-header auth method

Reference: https://github.com/filebrowser/filebrowser/pull/2474

It fails to lint the backend, but this is the fault of origin's coding habits and should not be fixed by this PR.
Changes that do not fit the PR outline will not be done because they will increase the number of differences.


Always upload artifacts

What this PR does / why we need it:
Which issue(s) this PR fixes

Fixes #

Special notes for your reviewer:
Release note:
release-note

Confirmed with failure that upload still worked. Merging after removing failing test.


Shard Distribution value of /_admin/metrics was incorrect

My Environment

ArangoDB Version:        3.7.10
Storage Engine:              RocksDB
Deployment Mode:       Cluster
Deployment Strategy:   ArangoDB Starter
Configuration:                 defaults
Infrastructure:               own
Operating System:        centos 7.7
Used Package:             RedHat .rpm

Hi, when i use the api /_admin/metrics to collect values of arangodb shards，the resault of "arangodb_shards_total_count" was incorrect and very unstable:

I can get the count of all shards number use debug-tools，and resault is correct:

How can i get the correct value of shard numbers with metrics?
Thank you ~

@reetahuang : this is indeed a bug. I think due to some internal changes made in 3.7.5, the value of this metric will only include the number of shards from databases that recently changed. That is also the reason why the values are so volatile and can even go down. Can't make a prediction about a bugfix though, just wanted to share the finding here.

@jsteemann
Thanks for your reply, looking forward to a release to fix this.


Prometheus stops firing but alerts stay active

This issue was reported by Jack and Julius here:

When the metrics behind my test alerts go back to normal, Prometheus stops firing, but the alert stays active in AM.  The PagerDuty incident is not resolved.  Yikes.

Can confirm. A simple "up == 0" alert sticks around in Alertmanager (current master) after it gets resolved in Prometheus, and also doesn't disappear after 5 minutes (the resolve timeout). It stays in the UI and it keeps sending "firing" webhook notifications.

Prometheus built from current master:
./prometheus -alertmanager.url=http://localhost:9093/
INFO[0000] Starting prometheus (version=1.6.2, branch=master, revision=5405a4724fbc7307786a65c176168a8948c0cbbf)  source="main.go:88"
INFO[0000] Build context (go=go1.8, user=julius@julius-samsung, date=20170523-13:45:49)  source="main.go:89"

Alertmanager built from current master:
./alertmanager
INFO[0000] Starting alertmanager (version=0.7.0-rc.0, branch=master, revision=6be3fbcb68af2ceb4d6bf77049a3390a1d6ad32f)  source="main.go:109"
INFO[0000] Build context (go=go1.8, user=julius@julius-samsung, date=20170523-13:47:45)  source="main.go:110"

Prometheus config:
global:
  scrape_interval: 5s

rule_files:
  - "prometheus.rules"

scrape_configs:
  - job_name: 'prometheus'
    static_configs:
      - targets: ['localhost:9090']
  - job_name: 'node'
    static_configs:
      - targets: ['localhost:9100']

prometheus.rules file:
ALERT SomethingIsDown IF up == 0

Alertmanager config:
route:
  group_by: ['alertname']
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 3h

  receiver: webhook

receivers:
- name: 'webhook'
  webhook_configs:
    - url: 'http://localhost:12345/'

Start Prometheus without node exporter running
Wait for alert to fire - it appears on AM and notifications to the webhook (listener started with netcat) are sent
Bring up node exporter

After the last step, the alert clears in Prometheus, but stays visible on the Alertmanager UI even after 20 minutes. The webhook notification keeps getting sent never-endingly repeating, but with a resolved status now...
POST / HTTP/1.1
Host: localhost:12345
User-Agent: Go-http-client/1.1
Content-Length: 602
Content-Type: application/json
Accept-Encoding: gzip

{"receiver":"webhook","status":"resolved","alerts":[{"status":"resolved","labels":{"alertname":"SomethingIsDown","instance":"localhost:9100","job":"node"},"annotations":{},"startsAt":"2017-05-23T15:53:37.804+02:00","endsAt":"2017-05-23T16:00:37.809+02:00","generatorURL":"http://julius-samsung:9090/graph?g0.expr=up+%3D%3D+0\u0026g0.tab=0"}],"groupLabels":{"alertname":"SomethingIsDown"},"commonLabels":{"alertname":"SomethingIsDown","instance":"localhost:9100","job":"node"},"commonAnnotations":{},"externalURL":"http://julius-samsung:9093","version":"4","groupKey":"{}:{alertname=\"SomethingIsDown\"}"}

The display issue is theoretically unrelated as we simply forgot to filter resolved alerts in the new API endpoint. So they remain visible until they are garbage collected.
The re-sending might be related to the fixes we made for 0.6 already. If it's only occurring in 0.7 I'd be surprised. Any chance you can verify that?

@juliusv @mxinden any further insights on this?

Checking again now with 0.6.

So actually part of the weird behavior I got earlier from master was that I used curl to receive webhook requests, but that doesn't respond with a HTTP status response, so those requests just timed out and were retried for that reason probably.
Now I'm using a small Go web server that just responds with 200, and I'm still seeing weird (but different) behavior.
This is from current master:

when the alert starts firing in Prometheus, it appears in AM
30 seconds later (group_wait: 30s), a firing webhook request gets sent out by the AM
when I resolve the alert in Prometheus, it remains visible in the AM UI, and only exactly 5 minutes after the firing notification got sent, does a resolved notification get sent out (I assume that is even intentional because group_interval: 5m also applies when all alerts in a group are resolved?)

So in current master the only thing that's clearly a bug is the UI! And in 0.6.2, that is also the only behavioral difference - in 0.6.2, the alert disappears from the UI immediately after being resolved in Prometheus.

(I assume that is even intentional because group_interval: 5m also applies when all alerts in a group are resolved?)

That's correct, otherwise we'd spam users as each individual resolution came in. Resolved notifications need to obey group_interval.

Okay, what you describe is the expected behavior. Curious about cases now
though where people report resolved being spammed endlessly into Slack.
For the UI, there's already a fixing PR open.
On Fri, May 26, 2017 at 3:20 PM Brian Brazil<EMAIL_ADDRESS>wrote:

(I assume that is even intentional because group_interval: 5m also applies
when all alerts in a group are resolved?)
That's correct, otherwise we'd spam users as each individual resolution
came in. Resolved notifications need to obey group_interval.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/alertmanager/issues/815#issuecomment-304280680,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEuA8oLH_-tEA3LvuoKrJegfGq6d7Nlpks5r9tGdgaJpZM4NiCej
.

We did have a bugs fixed in 0.6 around resolved notifications, so it could be those.

https://github.com/prometheus/alertmanager/pull/820 indeed fixes the UI issues for me. So from my side, I cannot reproduce this issue anymore. Should we close it and see if someone else reports similar issues again?

Fine with me.
On Fri, May 26, 2017 at 3:39 PM Julius Volz<EMAIL_ADDRESS>wrote:

#820 https://github.com/prometheus/alertmanager/pull/820 indeed fixes
the UI issues for me. So from my side, I cannot reproduce this issue
anymore. Should we close it and see if someone else reports similar issues
again?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/alertmanager/issues/815#issuecomment-304284796,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEuA8tiJQv0FP8qvMkZqHGh9GMf0MoEeks5r9tX5gaJpZM4NiCej
.

@juliusv I'm seeing the repeating "resolved" alert firing into Slack right now, with two different Prometheus installations. What information can I give you to try and nail this down?

I've just tried with an alertmanager built from master and observe the same behaviour. The offending alert, once resolved, notifies "resolved" every repeat_interval.
Route and Receivers config:
route:
  group_by: ['account', 'region', 'environment', 'alertname']
  group_wait: 30s
  group_interval: 1m
  repeat_interval: 2m
  receiver: infra

receivers:
- name: 'infra'
  slack_configs:
  - send_resolved: true
    channel: "channel"

I want to know when kubernetes pod was down get alert in slack or email.

@bala0409 Thanks for your interest. It looks as if this is actually a question about usage and not development
To make your question, and all replies, easier to find, we suggest you move this over to our user mailing list, which you can also search. If you prefer more interactive help, join or our IRC channel, #prometheus on irc.freenode.net. Please be aware that our IRC channel has no logs, is not searchable, and that people might not answer quickly if they are busy or asleep. If in doubt, you should choose the mailing list.
If you think this is not purely a support question, feel free to comment in here or take the underlying issues to our developer mailing list.
Once your questions have been answered, please add a short line pointing to relevant replies in case anyone stumbles here via a search engine in the future.


Sets that fail with an "out of memory" leave the proxy in an inconsistent state

The blast.go test has uncovered a rare case where memcached will respond with an "out of memory" error. After this, the next request causes memcached to reject, saying the command has an invalid magic byte at the beginning of the header. The set error recovery logic is probably not completely cleaning up, or possibly the buffered IO to and from memcached is causing the problem. I believe that #10 will be part of the solution to this problem.

#10 was not a solution, it's something else. I'm inspecting the error handling cases to see what is going wrong. After implementing the non-chunked handler, I'm not getting any errors in that while still getting errors in the chunked version. I'm focusing my attention there.

This was solved over several commits, and should no longer be an issue.


fix: Fix ediiting the extension

Description
Changes proposed in this pull request:

Fix editing the extensions

Related issue(s)
https://github.com/kyma-project/busola/issues/2986

/retest

/retest


ListItem legend may be a node as well

Currently it works, but produces a warning by react typechecking

@javivelasco please review this, I have this pain of seeng lots of warnings from React typechiecking but everuthing else works. Thanks!

Anything stops from merging this?

Thanks!

Sorry, personal issues are pushing me away from dedicating time to the project.


Draw functions should work on an interface

In Python they could operate on PIL images, while when used from jython they could be used on adapters of awt images.

I think this has been done


Not Working

Sorry to have to keep writing these, but my bot has seemed to stop working. I has stopped gathering xp and farming pokemon. I have no clue why it is doing this. Thanks
Mac osx

I don't know if its just my account or what, but a different account works fine.

does your accounthave two step auth ?

?

I get the "Session Stale message"

@iiCe89 now it just shows me this

Is it still an issue?

@Outpox No not anymore but my bot sometimes gets stuck on the "walking sign"


Update enter-ccupdate.md

Made changes to the description

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

Did you only mean to change the metadata description? The same content repeats on line 18

Did you only mean to change the metadata description? The same content repeats on line 18

I wasnt able to add a new comit So created another PR https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/pull/2352#issuecomment-497571688

@CarolynRowe Changes look correct. Could you please review and merge? Thanks!


Makefile: misleading example about enabling verbose mode

In Makefile there is an example of running tests in verbose mode:
# Build and run tests.
#
# Args:
#   WHAT: Directory names to test.  All *_test.go files under these
#     directories will be run.  If not specified, "everything" will be tested.
#   TESTS: Same as WHAT.
#   GOFLAGS: Extra flags to pass to 'go' when building.
#
# Example:
#   make check
#   make test
#   make check WHAT=pkg/build GOFLAGS=-v
check test: verify
        STI_COVER="-cover -covermode=atomic" STI_RACE="-race" hack/test-go.sh $(WHAT) $(TESTS)
.PHONY: check test

But when I'm trying to run command make check WHAT=pkg/tar GOFLAGS=-v it doesn't enable verbose mode and works as usual.
I suggest to: remove this comment or fix the scripts to make it work.
Known workaround: ./hack/test-go.sh pkg/tar -v

CC @soltysh

I'll take care of than along with fixing/aligning s2i Makefile to origin.


Remove run-dev-queue-processors

As of #367, tools/run-dev-queue-processors has evolved into nothing more than an unnecessarily elaborate wrapper around manage.py process_queue --all. Remove it (mostly to make it marginally easier to Tab-complete tools/run-dev.py, if I’m being honest).
Testing Plan: Ran run-dev.py.

Nice, merged, thanks @andersk!  That sort of tab-completion thing matters, so definitely worth fixing :)


Crash on new song

Application crashes when you try to play a song that you've just added to the directory.

Yes, you speak true.^^
I fixed it and it will be part of the next release. I think I will release one this weekend.
Thanks


Update bzlmod example to be able to use toolchain

While playing around with this bazel module.
I was looking at this issue https://github.com/bufbuild/rules_buf/issues/38
And when using the module example I wasn't able to use the bazel run cmd.
So this PR just aim to fix that.

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


background-image with linear gradient not outputting with chosen

I'm using with bourbon with Rails along with the chosen-rails gem, there seems to be some incompatibility, bourbon's background-image mixin doesn't work when chosen is present.
Anyone experienced this?
Do you think this a bourbon or chosen-rails issue?
Edit: chosen relies on some compass mixins, i'm guessing that's where the problem lies.

Hi @raldred,
It looks like chosen-rails is using Compass, which is probably what is causing the trouble. Compass uses some mixins with the same name as Bourbon and it's probably not a good idea to use both.
Of course I favor using Bourbon, so you might try giving one of the other gems a try, or as a last resort just adding Chosen into vendor/assets/ (I know, I don't like having to do that either).

@raldred Any update?

Heya yeh sorry, you're correct this the fault of chosen-rails.
I'm current in the process of patching to remove the Compass requirement, it's not necessary anyway because it should be built from the chosen source. Happy to close as nothing to do with bourbon really. :+1:


fixFillUpMissingSlots rule didn't process standalone having clause correctly

Proposed changes
Issue Number: close #xxx

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...

run buildall


ConcurrentPriorityQueue ToArray() bug

ToArray() calling CopyTo() making EnterReadLock() called twice.
The exception message is "Recursive read lock acquisitions not allowed in this mode."
Thank you!

Thanks. ToArray should call base.CopyTo() to avoid double lock entry.
I don't have IDE at hand right now. Do you think you could submit a pull request with a fix and cover it with unit tests?

I am new to both github and programming. I just tried to add pull requests and hope I did it correctly.


How to add my own standard command? (v1.0.2h)

Hello everyone,
I want to add a new standard command to the openssl utility, based on s_client and s_server. So far I haven't had success and don't understand what I'm doing wrong. Any help would be greatly appreciated :).

I discovered the progs.h file and added the following code manually (I did not run the auto generate perl script):
extern int s_proxy_main(int argc, char *argv[]);
...
#if !defined(OPENSSL_NO_SOCK)
    {FUNC_TYPE_GENERAL, "s_proxy", s_proxy_main},
#endif

Correspondingly, in a new source file (apps/s_proxy.c), I defined:
...
#undef PROG
...
#define PROG s_proxy_main
...

But when I compile and install my fork, I still cannot see or use my new command:
$ ./openssl s_proxy --help
openssl:Error: 's_proxy' is an invalid command.

Standard commands
asn1parse         ca                ciphers           cms
crl               crl2pkcs7         dgst              dh
dhparam           dsa               dsaparam          ec
ecparam           enc               engine            errstr
gendh             gendsa            genpkey           genrsa
nseq              ocsp              passwd            pkcs12
pkcs7             pkcs8             pkey              pkeyparam
pkeyutl           prime             rand              req
rsa               rsautl            s_client          s_server
s_time            sess_id           smime             speed
spkac             ts                verify            version
x509

As you can see, s_proxy is not even listed, despite the static LHASH_OF(FUNCTION) *prog_init(void) function in apps/openssl.c is supposed to take it from the functions array in progs.h (which I modified manually). I don't understand :(.
What is the correct way to add custom standard commands?
EDIT: I should also note that I did modify the Makefile according to the existing s_client and s_proxy handling. So perhaps compilation regenerated progs.h in which it was identical to when I edited it manually.

Looks like the problem was my usage of make: I installed using make --silent install_sw and that doesn't renew the binary tool (openssl). Executing make --silent install instead fixed the issue of missing s_proxy command in the openssl utility.


ci: Fix release automation

Now that we include two directories in our artifact (both dist/ and test/) we can no longer extract the artifact to the dist/ subdirectory, since that creates a dist/dist/*.tar.gz. We need to instead extract to the current directory, which means we need to upload the wheels in a dist/ subdirectory.

Codecov Report
Patch coverage has no change and project coverage change: -0.09 :warning:

Comparison is base (baa932c) 85.21% compared to head (6e45b3f) 85.12%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #407      +/-   ##
==========================================
- Coverage   85.21%   85.12%   -0.09%
==========================================
  Files          29       29
  Lines        3631     3631
==========================================
- Hits         3094     3091       -3
- Misses        537      540       +3

Flag
Coverage Δ

cpp
85.12% <ø> (-0.09%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Does this work with Melonloader 0.5.3?

https://github.com/LavaGang/MelonLoader/releases/tag/v0.5.3 #

0.5.3 crashes for me so I can't create a new signature for it.
Creating a new signature shouldn't be too hard for anyone that has used a debugger like x64dbg

@xKiraiChan guide me through it, i'll create signatures for 0.5.3 and 0.5.4

Attach to the game a debugger such as x64dbg
Double click bootstrap.dll (in the symbols tab)
Right-click then search the current module for string references ("invalid assembly")
There will be 2 results, only 1 of them matters
Find the code that raises the exception, it'll look something like this
Select the bytes in that area such that there is no collision, then calculate the offset to the target byte
Then you can create a signature and test if it works.

I've gone ahead and given this a shot. I'm able to load Munchen correctly, just getting a few people to test. If this works, I'll submit a PR shortly.

It working with Munchen is a bit odd (unless @killerbigpoint make it compatible or only the loader is obfuscated), make sure you check that it still makes integrity checking (knah's) mods work as well

I'm currently running Munchen, with UIX, VRTK, etc, no problems.

20778a4


Nesting beyond max width makes rustfmt do nothing

When expanding tokio::select with cargo expand, rustfmt gives up formatting. The whole block stays on one line.
Full expanded code: playground.
After deleting some stuff i found out that it probably is caused by nesting going nearly beyond the max width.
The shortest example i came up with: playground.

Removing the following code in the first playground
{ :: core :: panicking :: panic_fmt (:: core :: fmt :: Arguments :: new_v1 (& ["internal error: entered unreachable code: "] , & match (& "reaching this means there probably is an off by one bug" ,) { (arg0 ,) => [:: core :: fmt :: ArgumentV1 :: new (arg0 , :: core :: fmt :: Display :: fmt)] , })) }

allows formatting to happen.

Closing as duplicate of various other issues, all being tracked in #3863 now.
You're hypothesis is indeed generally correct. It was decided long ago to have rustfmt bail in cases where it's impossible to reformat the code to fit within the max_width. There's not really anything to be done about this in the interim since it's not handwritten code, but you increasing max_width to a sufficiently high point will provide something that's formatted, and you may occasionally get lucky by enabling format_strings

Thanks for the info, sorry for the duplicate.
Would it work to make two passes, first with a big max_width value and a second one with the default value?
So almost all lines would be formatted correctly.


Add SubQueryStep to distinguish whether the vectorSelector was wrapped in a SubQuery

The Select() of Querier interface supports the unexpandedSeriesSet for VectorSelector. The step in SelectHints is a global parameter, and it can't adapt to the VectorSelector which is embedded in a subquery, for example, query: max_over_time(metric[6m:10s])、step: 20s.
For the inner VectorSelector, it should choose 10s not 20s as the step parameter. So, I suggest adding the SubQueryStep parameter in SelectHints.
Currently, the latest version has already reset the interval, i.e.,
func (ng *Engine) populateSeries(querier storage.Querier, s *parser.EvalStmt) {
	var evalRange time.Duration
	parser.Inspect(s.Expr, func(node parser.Node, path []parser.Node) error {
		switch n := node.(type) {
		case *parser.VectorSelector:
			start, end := ng.getTimeRangesForSelector(s, n, path, evalRange)
			interval := ng.getLastSubqueryInterval(path)
			if interval == 0 {
				interval = s.Interval // the interval has been reset
			}
.............
.............

Now, I need to distinguish whether the vectorSelector was wrapped in a subQuery by SubQueryStep, then I can optimize the Select() process of vectorSelector.

In the process of Select(), my service will pull the timeSeries from the remote storage.
There is an optimization point, that is, Select() method just returns the timeSeries which will be visited. In other words, we can push down the range and lookbackDelta to the remote storage.
However, the optimization can'd adjust to the SubQuery. So, I suggest adding SubQueryStep to check current vectorSelector in Select().

For the inner VectorSelector, it should choose 10s not 20s as the step parameter. So, I suggest adding the SubQueryStep parameter in SelectHints.

It already does that, doesn't it?

For the inner VectorSelector, it should choose 10s not 20s as the step parameter. So, I suggest adding the SubQueryStep parameter in SelectHints.

It already does that, doesn't it?

It just reset the interval, but we can't distinguish whether the vectorSelector was wrapped in a subquery in Select() according to the step field.
func (ng *Engine) populateSeries(querier storage.Querier, s *parser.EvalStmt) {
	var evalRange time.Duration
	parser.Inspect(s.Expr, func(node parser.Node, path []parser.Node) error {
		switch n := node.(type) {
		case *parser.VectorSelector:
			start, end := ng.getTimeRangesForSelector(s, n, path, evalRange)
			interval := ng.getLastSubqueryInterval(path)
			if interval == 0 {
				interval = s.Interval  // the interval has been reset .......
			}
.............
.............

There is an optimizable point that we can improve. In the Select() of Querier, we can push down the logic about lookbackDelta and range into remote storage. However, the optimization logic of subquery  is different, and the  SubQueryStep field can help us to differ from other scenes.

Any doubts else? @codesome

How does distinguishing subquery and not a subquery help? Do you have a use case where you will actually use it or is it just a "nice to have"?

How does distinguishing subquery and not a subquery help? Do you have a use case where you will actually use it or is it just a "nice to have"?

The Select() of Querier  will pull all timeSeries from remote storage.
// Querier provides querying access over time series data of a fixed time range.
type Querier interface {
	LabelQuerier

	// Select returns a set of series that matches the given label matchers.
	// Caller can specify if it requires returned series to be sorted. Prefer not requiring sorting for better performance.
	// It allows passing hints that can help in optimising select, but it's up to implementation how this is used if used at all.
	Select(sortSeries bool, hints *SelectHints, matchers ...*labels.Matcher) SeriesSet
}

We can push down the logic of "lookBackDelta" and "range" to the remote storage, and it just needs to pull the required data. The following case will help you understand the optimization.
PromQL: max(irate(metric[2m]))
query range: 7 days
step: 15min

For the calculation of each step, it just needs the data of [current - 2min, current], and the data of the other 13 minutes is useless. It can reduce the data from the remote storage and improve the performance sharply.
However, if the VectorSelector is wrapped in a Subquery, we can't apply such optimization. Subquery will align the "step" to the start / end / original step in the eval, and the  align step is different from the original step. Therefore, we need to distinguish subquery and normal query.

It seems to me we could have the request say which data it wants - "2 minutes every 15 minutes aligned to X start time" - and not have it need to understand PromQL, subqueries, etc.
(Nitpick: you used irate in your example, which only looks at the last two samples regardless of the size of the window. But I think that makes my point - we shouldn't need to have the storage provider understand all this.)
The point of putting the aggregation in the hints was if you already downsampled max, say, you can return that.

The calculation startTime of subquery is completely different from the startTime of a normal query. You can check the original code.
case 1:
PromQL: rate(metric[2m])
query range: 7 days
step: 15min

For each step calculation, the data of 13 minutes are useless.

case2:
PromQL: metric
query range: 7 days
step: 15min
lookbackDelta: 5min

For each step calculation, the data of 10 minutes are useless.

You shouldn't focus on the specific functions or aggregators, and the lookbackdelta、range and step are the key points.

Are you saying it is impossible for the caller to say what data are required, but always possible for the callee to figure it out?

callee

Sorry, I want to confirm whether you have understood this optimization point.
In my case, the callee is the remote storage. For the normal query, the caller and callee both can figure out what data are required. For the subquery, callee can't figure out that, because the caller will do step alignment in the calculation process. And the alignment is not visitable for the remote storage(i.e., callee), so I need the interval parameter of subquery and process the "step alignment" in the remote storage.

Yes, I think I understand your point.
I am proposing something I feel is better, because it is less complicated and less coupled to specific implementation details of PromQL.
I’ll try to say it differently: the protocol should allow the caller to ask for specific data, in terms of samples or time periods. All requirements of alignment would be specified directly, e.g. “every 15 minutes starting at 10:03:21”.

Yes, I think I understand your point. I am proposing something I feel is better, because it is less complicated and less coupled to specific implementation details of PromQL.
I’ll try to say it differently: the protocol should allow the caller to ask for specific data, in terms of samples or time periods. All requirements of alignment would be specified directly, e.g. “every 15 minutes starting at 10:03:21”.

So, your suggestion is to identify the step from client request parameters , not from the vectorSelector.  But I also need the specific interval of subquery and do step alignment in remote storage.
Moreover, the suggesting solution can't adapts the following case,
promql:  metric_1 + rate(metric_2[2m:10s])
query range: 7 days
step: 15min
lookbackDelta: 5min

In this case, the step of metric_1 is 15min, while the step of metric_2 is 10s. Therefore, I must get the step/interval from the specific vectorSelector.

Yes the two requests have different steps and different alignment. Why is that impossible to state as such?  Why is it essential to reference the word “subquery” in the protocol?

Yes the two requests have different steps and different alignment. Why is that impossible to state as such? Why is it essential to reference the word “subquery” in the protocol?

There are two VectorSelector in such case, not two requests. As you say, for the vectorSelector of metric_1, the step value in the protocol is  15min. The value of metric_2 is 10s.
However, the alignment process of normal query and subquery  is completely different, so I need a field to differs subquery from other scenes and execute different alignments.


WIP/stdlib: port the test harness to Windows

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test

CC: @xwu @moiseev

Build failed
Swift Test OS X Platform
Git Sha - 7d5672fbb906a48b1c13ff2f760f926f39e41dd0

@swift-ci please test

@swift-ci please test

CC: @moiseev

CC: @lorentey


One test failure on s390x

With pyRiemann 0.3 on the s390x architecture, one test fails:
=================================== FAILURES ===================================
____________ test_distance_func_separability[distance_wasserstein] _____________
dist = <function distance_wasserstein at 0x3fd8b4d4b80>
get_covmats = <function get_covmats.<locals>._gen_cov at 0x3fd7748d940>
    @pytest.mark.parametrize("dist", get_dist_func())
    def test_distance_func_separability(dist, get_covmats):
        n_matrices, n_channels = 1, 6
        covmats = get_covmats(n_matrices, n_channels)
>       assert dist(covmats[0], covmats[0]) == approx(0, abs=1e-7)
E       assert 1.2467205919833117e-07 == 0 ± 1.0e-07
E         comparison failed
E         Obtained: 1.2467205919833117e-07
E         Expected: 0 ± 1.0e-07
tests/test_utils_distance.py:99: AssertionError

It looks like the tolerance is slightly too tight to allow for floating-point implementation differences across architectures. I will follow up with a PR to loosen the 1e-7 in the assertion to at least 1.25e-7—perhaps 2e-7 as a nice round number.

Thanks @musicinmybrain for reporting it and for the PR.


python3Packages.mkdocs-swagger-ui-tag: version bump (0.5.1)

Updated the mkdocs plugin mkdocs-swagger-ui-tag: 0.4.3 -> 0.5.1.
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Already bumped via #218614. Closing this PR.


Revisiting transliterations

I wanted to bring this topic up a while ago but forgot about it.
The core function for creating handles uses transliterations. Transliterations can be
overwritten per language by extensions.
If I'm not mistaken, what transliterations are used to create a handle always depends on what language your backend currently uses.
Is this correct?
I think that's a problem for multilingual websites and in cases where the backend language doesn't match the frontend language.
Symphony usually doesn't assume anything regarding your frontend, so this seems a bit weird.
Any ideas?

Should be added to the 3.0.0 milestone.

+1 :)