Implement non-interactive payments by including the preimage in the Sphinx e2e payload

With the current implementation there are two ways to send a payment to a remote node:

Receive an invoice from them, and fulfill that invoice using the SendPayment RPC.
Both the sender and receiver have been started with the --debug_htlc flag, and the sender sends a payment using the hard-coded "debug" preimage value within the HTLC.

A third mode is possible which is similar to the second payment route, but can be used in a "production" network as it'll properly generate a brand new preimage with each payment. This third mode is what I've been calling "sphinx send" (or "onion send", dunno). In this mode the sender generates the preimage for a targeted payment, and includes the pre-image either in the e2e payload, or the per-hop payload within the Sphinx packet embedded within the outgoing HTLC.
It is important to note, that this mode should not be used for retail or b2c payments. This is due to the fact that one is unable to properly obtain assigned proof-of-payment receipt as the sender generates the pre-image instead of the receiver int his mode. However, for paying a friend of LN, or other cases which don't require a verifiable proof-of-payment, then this mode allows for non-interactive payments. If a remote node accepts such payments (which should be denoted it it's global_features vector), then the node can simply advertise it's public key and that is all that's needed for other modes to send them payments.
Steps To Completion

[ ] Modify the logic in the routing module to accept an additional attribute to routing.LightningPayment request struct which toggles if a sphinx_send should be attempted or not. If so, then the last per-hop-payload should be modified to include a preimage generated by the sending node.

[ ] Within the peer struct's htlcManager goroutine, when an incoming HTLC arrives and we're the exit node but we can't find the preimage within the invoiceManager, then the per-hop-payload should be checked for a valid pre-image. If one matches, then that should be used to settle the HTLC, and all logic should proceed as normal.

[ ] The SendPaymentRequest struct should also be modified to add sphinx_send bool. On the server side, this bool should be passed into routing.LightningPayment request struct.

[ ] Finally, the additional argument should be added to the lncli tool.

[ ] A set of bits in the global_features should be allocated to signal knowledge of this new feature. If a user attempts to trigger a sphinx_send to a node that doesn't have these bits advertised, then the payment should fail.

A set of integration tests should be added to ensure the proper propagation and handling of sphinx_send payments within the network.

Can I take this?

I consider this issue to be of a rather low priority. It doesn't require any modifications to the spec instead, but instead should be coupled with a signaling mechanism to use the extra bytes in the payload to signal that some, or all of the remaining per-hop payloads are to be decrypted as they're a complete package.
Nevertheless, @AndrewSamokhvalov has started some preliminary work on this feature (though we forgot to comment on this issue).
It's worth nothing though, that this feature isn't incompatible with obtaining a signed receipt as the encrypted error replies can slightly abused to (using the extra payload bytes to signal) request a signed invoice for a particular amount, returning the replay over an encapsulated "error".

Adding to the description in the issue, the following change needs to be made in lightning-onion:

Rather than _discarding) the currently un-used payload when parsing a sphinx packet, the value should instead be embedded within the HopData as a new field of type []byte

To accompany this change, the htlcswitch.ForwardingInfo struct should be modified to either opaquely embed the unused per-hop data, or create a set of abstractions around the unused payload, the first of which would define the interpretation and parameters for this feature.
We have a choice here w.r.t whether to define a generic extension mechanism now that uses 2-bytes to denote the interpretation of the payload, and then extend the payload over excess hops in the sphinx packet, or just use the 8+8+4+12 bytes to encode the payment pre-image in full.

Is there a spec for this so that other implementations can receive these payments?

Hey @stevenroose ! No there is no yet, but I have implementation of it locally.

Wouldn't it make more sense to add a requestinvoice method to a spec, that would return a short-lived invoice to a requesting node?

This is a single shot. It also doesn't require changes at the core, it's
end to end.
On Jun 27, 2018 9:55 PM, "Damian Mee"<EMAIL_ADDRESS>wrote:
Wouldn't it make more sense to add a requestinvoice method to a spec, that
would return a short-lived invoice to a requesting node?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lightningnetwork/lnd/issues/132#issuecomment-400910510,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA87LmQmVv-7WUMdg6YjKhXtPdGexLulks5uBGGugaJpZM4L-Xsw
.


[Bugfix][IR][ATTRS] Fix AttrEqual for Array and StrMap, double

Use fuzzy comparison for double.
Removed the hack for BatchNormAttrs and DictAttr.

Also removed a warning from text printer printing.
cc @MarisaKirisame @zhiics @merrymercy @jroesch @spectrometerHBH

Thanks @MarisaKirisame @zhiics


Install a11y add-on and install for existing components.

 Install a11y add-on to storybook so that it runs on all components


Create uczen.txt

@rn-itsol First stage of verification passed, official domain is lo2kk.edu.pl as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@rn-itsol Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Update MEI.visual.xml

Make att.breath.vis a member of att.verticalGrp.
Similar to #1472
Closes #1379

@pe-ro I just added the final change here to #1472, so we have everything in one PR.
Closing this one.


Fix incorrect dimming and sheet position

If translation > maxSheetTranslation the sheet won't be attached to the bottom, and the dimAlpha can go beyond the max dimming value
Resolves https://github.com/Flipboard/bottomsheet/issues/91

Lgtm, but seems like the bigger issue is that max translation isn't being respected?

The main problem in #91 is that Views can resize after the show() call, and WebViews seemed to be especially prone to that. I can't reproduce it now. I wonder if WebView has updated to avoid that behavior.


Migration from openenergymonitor/emoncms image

Hello,
I'm currently running openenergymonitor/emoncms:11.3.24 on a kubernetes cluster, with separated containers for external services (like mysql).
It looks like the image I'm using is no longer supported and emoncms suggests to move to this one.
Is it something I can do just using this new docker image without changing my setup?
Thanks.
This is my conf:
# MySQL database
MYSQL_HOST=[redacted]
MYSQL_PORT=3306
MYSQL_DATABASE=emoncms
MYSQL_INITDB_SKIP_TZINFO=true
MYSQL_USER=[redacted]
MYSQL_PASSWORD=[redacted]
# Redis
REDIS_ENABLED=false
# MQTT
MQTT_ENABLED=false
# Feed
PHPFINA_DIR=/var/opt/emoncms/phpfina/
PHPTIMESERIES_DIR=/var/opt/emoncms/phptimeseries/

PRODUCTION=true

Hello
No, you have to change your setup but. I did not use the initial openenergymonitor/emoncms image, I dont know if it is complex or not.
In my mind, it is possible to migrate manually, even it is not a one-to-one replacement, as the architectures and design choices are different
One possibility would be to create a backup and to restore it within a container running the alexjunk/emoncms image
I guess you dont have the backup module working so you have to create it manually :

you have to dump your database. Connect to the database through mysql in command line and run something like that, replacing all the $ with your parameters : mysqldump -u${username} -p${password} emoncms > ${backup_location}/emoncms.sql
then make a tar.gz with inside the timeseries folders : phpfina, phptimeseries, phpfiwa plus at the root the sql file and your settings file

You will also have to adjust the way you post your datas, but if you use an external mqtt broker and want to keep it, the alexjunk/emoncms image can be configured for it, even if it ships its internal broker.... see the env vars in the dockerfile : https://github.com/Open-Building-Management/emoncms/blob/6a9beae3811e60442f0bb3698c9eb1b289f6437a/Dockerfile#L230
You can give a try without stopping your original setup.
Best

Thank you for your answer.
is there a way to run this image with a separated mysql host so I dont have to dump & restore the database?
I prefer to have it separately because it has already what is required to be backed up etc in my current setup and I prefer containers separated for each service.
My IoT device still uses HTTP requests so mqtt is not required too.
I would just to use your image for emoncms only so I can have the last version running.
Is there a way?
Thanks!

You can try to adapt the emoncms_pre.sh file, replace localhost by the address in your mysql container and also add the port, altough it may not be necessary if both containers run on the same network
Happy if you make a pr for that with the mysql adress as an env var in the dockerfile.....but it has to be tested....
https://github.com/Open-Building-Management/emoncms/blob/6a9beae3811e60442f0bb3698c9eb1b289f6437a/emoncms_pre.sh#L133

I prefer containers separated for each service.

Why ? There is nothing bad running more than one service in a container when it is correctly done, like here with s6-overlay. This image is here to simplify your life while installing and running emoncms and it sticks to the original design of emoncms, it was not the case with the openenergymonitor/emoncms image
Other users are making the jump and feedback is good :
See : https://community.openenergymonitor.org/t/up-to-date-docker-container-image/27198/6
More on s6-overlay :
https://github.com/just-containers/s6-overlay

Thank you for your help Alexandre.
While I understand the appeal of bundling services for convenience, running multiple services in one container doesn’t align well with containerization best practices, especially in Kubernetes. Keeping services isolated allows for better scalability, resilience, and easier observability, all of which are critical in production-grade setups (and I'm used to them, also in my own homelab 😊 ).
I ended up using the original openenergymonitor/emoncms image and updating it to the latest version to separate the services as needed.
I believe offering an option to disable bundled services could make your image more flexible for users in similar environments while still catering to simpler use cases.
Thank you again for the work on this image.

Of thanks for the feedback. As you updated to a new version, could you open a PR in https://github.com/emoncms/emoncms-docker/blob/master/web/Dockerfile or just tell me your changes so i can echo them on the emoncms/emoncms-docker
As you can see, the openenergymonitor image uses supervisord :
https://github.com/emoncms/emoncms-docker/blob/e143cfe6b709357cba0a9bd0a68c3ba1dd8a5e85/web/Dockerfile#L64
is it ok with the k8s best practises ?
disabling the services is not possible with s6-overlay i think. They will run in the background but you will not use...at the end, it is a lot of ressources lost because if you dont use redis, mosquitto and mysql which are embedded, it is a pity, so would be better to update the original emoncms dockerfile with the minimum vital....
I think they lack of an automatic workflow but this i can arrange....

Of thanks for the feedback. As you updated to a new version, could you open a PR in https://github.com/emoncms/emoncms-docker/blob/master/web/Dockerfile or just tell me your changes so i can echo them on the emoncms/emoncms-docker
As you can see, the openenergymonitor image uses supervisord : https://github.com/emoncms/emoncms-docker/blob/e143cfe6b709357cba0a9bd0a68c3ba1dd8a5e85/web/Dockerfile#L64 is it ok with the k8s best practises ?
disabling the services is not possible with s6-overlay i think. They will run in the background but you will not use...at the end, it is a lot of ressources lost because if you dont use redis, mosquitto and mysql which are embedded, it is a pity, so would be better to update the original emoncms dockerfile with the minimum vital.... I think they lack of an automatic workflow but this i can arrange....

Yeah it would be better to just run on pid 0 the apache service, but I didn't want to change too much because I needed that to have it working asap, compatible with last home assistant version (it requires the new UUID identifier).
Here you can find my mods:
https://github.com/emoncms/emoncms-docker/compare/master...Leen15:emoncms-docker:master


java.util.Set generation at maxDepth fails due to insufficient distinct elements being generated

Describe the bug
Assume the following

Instancio is being invoked with a maxDepth of n
there is a java.util.Set field with elements to type E at depth n-1
E consists of a single String field and overrides equals/hashCode such that two instances of E are equal if the String fields are equal
minSize for collection generation is 2

During object graph generation Instancio will will fail in org.instancio.internal.InstancioEngine#generateCollection at level n when generating the collection elements for the java.util.Set because the collection elements, instances of E, will not be populated because the maxDepth has been reached. Hence the String field in all generated elements will be null. Hence all generated collection elements will be considered equal by the equals/hashCode implementation. Hence, only one element will ever be inserted into the Set and any further attempt will be considered a failedAddition by Instancio. Hence, the minSize of 2 is never reached and Instancio will fail with an internal error.
Expected result
I'm not sure if this can actually be considered a bug. However, when this issue surfaces it is very unexpected and hard to understand.
The only sensible workaround I can think of that generally prevents this situation is to configure minSize to at most 1 for collections.
Another way of preventing this in Instancio could be to introduce a special handling for Set collections that lazily increases the maxDepth by 1 in this situation so that the Set elements get populated.
Actual result
The object generation fails with an internal error.

Java version: 17
Instancio version: 3.0.1

@Mobe91 thanks for creating this issue! I documented this briefly here: https://www.instancio.org/user-guide/#error-handling, but maybe I need to expand the documentation to include an example of max depth affects collections.
Recently I also added a more descriptive log message. If you have debug logging enabled, you should see a message: "unable to populate Collection of size 2".
Another option is run with verbose() mode enabled when troubleshooting. Then you should see a stack trace if there's an internal error.
If you prefer to propagate internal exceptions, you can enable Keys.FAIL_ON_ERROR, or add the following to instancio.properties:
fail.on.error=true

Let me know if the above works for you.

@Mobe91 I updated the error message and added a link to the Error Handling section of the user guide. Hopefully it makes the behaviour less confusing.
Sample error message for reference:

Internal error occurred creating an object.
Internal errors are suppressed by default and
can be ignored if not applicable to the current test
-> at org.external.errorhandling.ImpossibleCollectionSizeErrorMessageTest.met
Reason: unable to populate Collection of size 100: class Set (depth=0
│ Path to root:
│   <0:Set>   <-- Root
│
│ Format: <depth:class: field>
Could not generate enough elements to populate the collection.
This typically occurs with Sets when the number of potential values is
limited and the target set cannot be generated due to duplicate element
values, for example:
-> The element type is an enum
-> The element type is a POJO, but blank POJOs are being generated
because the configured maximum depth has been reached
Model properties:
-> Collection target size: 100
The size was either chosen randomly based on current settings,
or may have been specified explicitly via the API.

-> Current size settings are
Keys.COLLECTION_MIN_SIZE: 2
Keys.COLLECTION_MAX_SIZE: 6

-> Keys.MAX_DEPTH: 8
-> Model max depth: 8
Unless overridden using withMaxDepth() method,
this value should be the same as Keys.MAX_DEPTH

For more information see: https://www.instancio.org/user-guide/#error-handling


Rfm 17.1 - Sharing Provider Records with Multiaddress

This is the first draft of the report that extends RFM17 to measure if the Multiaddresses of a content provider are being shared during the retrieval process of a CID process.
It includes the study's motivation, the methodology we followed, the discussion of the results we got out of the study, and a conclusion.
All kind of feedback is appreciated, so please, go ahead to point out improvements!
Also, should I be running a more extensive set of CIDs for extended periods?
cc: @yiannisbot @guillaumemichel @dennis-tra

Thanks for the feedback @yiannisbot , I really appreciate it!

My main worry is that the claim of: "if a multiaddress is returned together with the PeerID for the TTL period (10mins or 30mins), then we can extend the TTL to the PR expiry interval" doesn't really hold. Why would we arrive to this conclusion

I will try to make it a bit more explicit in the conclusion (my bad). It's not an "it won't hold" statement. It is an "It won't have as much impact as we are expecting" statement.
As far as your network has different TTL values for Multiaddresses (like in the current network), the smallest TTL will be the one limiting negatively the final result of the DHT lookup process (at least the go-libp2p-kad-dht one). So unless the largest part of the network updates to that TTL, we will still face the same problem, and there will still be sporadic problems originated from those remaining "old" clients. (The double-hashing implementation would be a nice incentive to force a total network update)

Basically, similar to the CID Hoarder, what we need here is a PeerID Hoarder :-D This tool would get a lot of PeerIDs, record the multiaddress by which we first saw the peer and then periodically ping the peer to figure out if it changed its Multiaddress within the PR Expiry Interval.

I left you a comment as well in the #22 comment
I think that we have a few options here. The hoarder already does this indirectly (it contacts the PR Holders to the Multiaddress that we stored while storing the PRs). Also, I think that Nebula already tracks IP rotation. We could have a deeper chat about this :)
I'll iter again over your comments and suggestions, will ping you back whenever I make a commit!

I'm not sure if this functionality can easily be included in Nebula @dennis-tra ?

Sorry for the late reply! The information is already recorded by Nebula and would just need to be analyzed :)

I'll iter again over your comments and suggestions, will ping you back whenever I make a commit!

Just ping here or in Discord and I'll also have a proper read. I just skimmed it in the past 🙈

I already added some explanations and most of the changes that @yiannisbot suggested. I set up another Hoarder run with 20k CIDs for 60 hours, so the plots and some numbers might change.
If you can go through and give me some thoughts @dennis-tra , I would appreciate your feedback as well 😄

@cortze do we have any results from this experiment? I think with these results and addressing Guillaume's question, this should be ready to be merged, right?

@yiannisbot  The results of this run were not as good as I expected. To track such a large set of CIDs, I had to increase the concurrency parameters of the hoarder, and as we spotted in our last meeting (link to the Issue describing the bottleneck) the code is not that prepared to support such a high degree of concurrency.
However, I think that even with such a low number of CIDs and a lower ping-interval between pings (3 minutes), we can conclude that increasing provider Multiaddress' TTL would improve content fetching times. And the impact would be much higher if we merge it with go-libp2p-kad-dht#802.
RFM17 already proved that the IP rotation of PRHolders barely happens:

@yiannisbot I've updated the document with your suggestions and with two extra paragraphs describing:

The observed IP-churn of DHT servers in IPFS (from the RFM-17)
Contribution section, where I aggregated all the pull requests related to this RFM

I've also updated the figures. The new ones have the DHT lookup limited to 2 mins - which shows a reasonable number of peers that return the PRs as pointed out by @guillaumemichel .
The new data still faces a lower number of online PR Holders due to a problem storing the records in a part of the network. However, I consider them more than good enough to conclude that increasing the TTL of the Provider's Multiaddres would avoid the second DHT lookup to map the PeerID of the Provider with its Multiaddres.
Let me know what do you think about the update :) Cheers!


Use Pydantic instead of asdict()

We will use Pydantic later on for JSON decoding, so use it for encoding now.

What benefit do we get from using pydantic here over dataclasses?

dataclasses does not have from_dict() or anything like that, which is needed for decoding.

When would rapids-metadata ever have to go from JSON text to Python objects?

Two weeks ago we had an internal discussion on Slack where we realized that putting the data in a package that pre-commit-hooks depends on wouldn't work, because pre-commit caches the environment and wouldn't get rapids-metadata updates as they come. The solution we came up with was to check the generated JSON into source control and have pre-commit-hooks download it from raw.githubusercontent.com. This is what JSON decoding will be used for.


Missing suport for kafka 2.0.x 2.1 ?

Hi,
I see in pom.xml  <kafka.version>1.1.1</kafka.version>. Does it mean that we can't use it for kafka 2.x ?

1.1.1 client is compatible with 2.x broker. You can use latest master with 2.x broker cluster.


⚠ Fortnite has degraded performance

In c495eb1, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1336 ms

Resolved: Fortnite performance has improved in dfb8c77.


Remove questionnaireResponseItemRetriever

this api (internal api) change is fine. But what this means is that the questionnaireResponseItemRetriever is going to become a little redundant. I think in this case we should remove questionnaireResponseItemRetriever and instead implement the functionality of finding the questionnaire response item from linkId inside of the enablement package.
i'm happy for this to be done in a follow-up PR.
Originally posted by @jingtang10 in https://github.com/google/android-fhir/pull/1294#discussion_r857097359

@RaaziaTarique @jingtang10 can we rename this ticket? Something like: Extension to EnableWhen expression?

Yes, we can. @f-odhiambo CC: @jingtang10

@f-odhiambo done.
i created this ticket from a PR review comment and github does this automatically


Django 1.9 :  django.db.models.signals.post_syncdb remplaced by post_migrate

file concerned management.py

https://docs.djangoproject.com/en/1.9/releases/1.9/

https://docs.djangoproject.com/en/1.9/releases/1.7/#deprecated-features-1-7
A new makemigrations command provides an easy way to autodetect changes to your models and make migrations for them.
django.db.models.signals.pre_syncdb and django.db.models.signals.post_syncdb have been deprecated,   to be replaced by pre_migrate and post_migrate respectively. These new signals have slightly different arguments. Check the documentation for details.

Need to run:
 manage.py makemigrations django_messages

to create tables.

thanks a lot!

Hi @FabriceSalvaire,
the command "manage.py makemigrations django_messages" works without any errors. But this command didn't create the tables. Did you have any workaround? (Django Version: 1.9.1)
I tried the command "manage.py migrate django_messages" and got the following error:
site-packages/django_messages/management.py", line 1, in
from django.db.models import get_models, signals
ImportError: cannot import name get_models
Thank you for your help.
Tobias

django.db.models.get_model is deprecated
See here for sample fix:
https://github.com/wq/django-swappable-models/issues/6


Route to a new page

I was wondering if there a way to complete route to a whole new page with whole new layout.
I have a login page that is completely different to the regular views but vue-router always go the default index.html
const routes = [   { path: '/login', component: resolve => require(['./views/Login.vue'], resolve) },   { path: '/', component: resolve => require(['./views/Dashboard.vue'], resolve) },   { path: '/create-client', component: resolve => require(['./views/CreateClient.vue'], resolve) },   { path: '*', component: resolve => require(['./views/404.vue'], resolve) } ]

 //this not always work. In particular, there are `children` sub-routing. bug?
component: resolve => require(['./Foo.vue'], resolve)

try one of:
component: resolve => {
    // require.ensure is Webpack's special syntax for a code-split point.
    require.ensure(['./Foo.vue'], () => {
       resolve(require('./Foo.vue'))
    })
}

or
component: require('./Foo.vue')

or
component: Foo

hope to help you.

Please make sure to read the Issue Reporting Guidelines before opening new issues. Questions should be posted on the forum or StackOverflow. Thanks.

You should create a component for each route. There's only one index.html in an spa


update opentelemetry-collector-contrib: v0.78.0 -> v0.85.0

Description of changes

Things done

Built on platform(s)

[ ] 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.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

argh how do i get the channel check to re-run

Okay, this is ready I believe.

!ofborg check

!ofborg check

https://github.com/NixOS/ofborg#commands

I was going from memory :D

@ofborg test

Also why are you removing CGO_ENABLED = 0;? We've had issues in the past when we've not had this set and that README item still requires it to be disabled AKA what we have so I don't think that position has changed
CC: @uri-canva

nixpkgs-review didn't pass the inbuilt tests with that set, due to the gosqlite3 (I think?) package dependency requiring it.

If it's required for the tests, we can set it only for the build, and leave it unset for the check.

How?

preCheck export CGO_ENABLE=1 or skip the related tests

Yep, fixed. Is there any way to get it other than to build it and wait for the error?

ofberg internal error? O.o

For future reference, this shouldn't have been merged with 3 commits as it's against the commit conventions outlined in CONTRIBUTING.md
https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#commit-conventions
They should have been squashed into the original and become opentelemetry-collector-contrib: 0.78.0 -> 0.87.0


Reduce refresh indicator pull-down distance

Description
Reland of #44054
Thanks to @altherat
gifs to compare results:

Old Flutter
New Flutter
Native

Related Issues
#14981
Tests
@altherat added the following tests:
RefreshIndicator - just enough: Ensures a 100 pixel drag causes a refresh, which would fail with the previous pull-down distance.
Also modified an existing test (RefreshIndicator - not enough) to pass for the reduced pull-down distance.
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] All existing and new tests are passing.
[ ] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

Sorry for that, but @altherat I need you to sign this again 😭

@shihaohong Regarding the gif you mentioned in my previous pr: I don't have much knowledge in graphic design tools. Do you know any tool / easy way to create such a gif out of 2 videos?

@googlebot I consent.

I figured out a way to compare it pretty well in a more crude manner and added it to the description. This looks great! Thanks for the fix @altherat and thanks for the effort to reland this @lazylazyllama!

I reran Google testing and it appears to be a flake. I'll merge the change.


!ping command

Unlike normal ping commands. This checks the connection to the API Server and the Plugin (if active)

added

added


linux: make IDE an "option no"

When trying to build a 5.14 (rc-*), this fails to build otherwise:

error: unused option: IDE

Motivation for this change
IDE has long been deprecated, and 5.14 will finally remove it entirely. We shouldn't assert it to be just "disabled".
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase 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

[ ] Fits CONTRIBUTING.md.

Reproducer:
{ buildLinux, fetchFromGitHub, ... }:

let
  version = "5.14-rc4";
in
buildLinux {
  inherit version;

  src = fetchFromGitHub {
    owner = "torvalds";
    repo = "linux";
    rev = "v${version}";
    sha256 = "10vha8nibkgplqrq4prxiycnwav8qpzl50ifak9p42w4bspg2srg";
  };

  modDirVersion = "5.14.0-rc4";

  kernelPatches = [ ];
}

Why this vs. "whenOlder '5.14' no"? I don't really have any strong opinions, just thought it's worthwhile asking for future reference.

You're right - that works too. Updated the PR.


Remove init template command

Based on consultation with users (see ticket) it seems that nobody
argued against this change.
Fixes: #2471

Looks like some more of the related tests need to be removed. Example Travis CI failure: https://travis-ci.com/ansible/molecule/jobs/270637079


README.md

English - Chinese

Are u kidding? English comment to Chinese? You want to make project not supportable or what?

@makzimko 1、You misunderstood, sometimes machine translation language is not accurate.
2、SO, I carefully opened the dusty many years of high school English dictionary to answer your "questions"

@1xxxx documentation on Chinese is a pretty bad idea. I know that more than one billion people know Chinese, but believe me that English is more in all the world. So with documentation in Chinese other world can't support project

Compile the document ≠ code, you understand?
Just want to compile, one billion people also do not understand the English language programmers, such as me.

@makzimko Compile the document ≠ code, you understand?

Not really sure I understand, but i'm closing this


Fix inconsistency

The --add and --remove arguments' descriptions currently indicate that they are multi-valued; this contradicts the note under the table. Fix: Define the arguments as single-valued.

@chrullrich,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/install/use-command-line-parameters-to-install-visual-studio.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@tglee Please take a look.


How to access host:port service running inside code-server via WebView

Web Browser: Chrome
Local OS: OS X
Remote OS: Ubuntu
Remote Architecture: x64
code-server --version: 3.0.0

On creation of a code-server instance I have a springboot server auto-launch in the embedded terminal of VSCode, serving port 8580. This services is used by a custom extension.
In a local version of VSCode (non code-server) I can just have the extension WebView make calls to http://localhost:8580, but when using this base URL - export const SERVER_BASE_URL = "http://localhost:8580"; - through the code-server browser client, it doesn't direct to the INSTANCE/Container localhost - but rather to the USER's localhost.
Is there an easy method to have this service contained in the docker instance and accessed via a WebView in code-server?
My next step would be to expose 8580 externally and direct WebView calls to .domain.net:8580, but wondering if this is avoidable or if it can just all be contained. Thanks

code-server has a built-in proxy you could use to proxy port 8580. See https://github.com/cdr/code-server/blob/master/doc/FAQ.md#how-do-i-securely-access-web-services. That would at least let you avoid opening another port.
We have some open issues to make this easier: https://github.com/cdr/code-server/issues/1936 https://github.com/cdr/code-server/issues/1510

Yup, closing as a duplicate of #1936 and #1510


[Model Update]: Battery Pass in correspondence with Digital Product Pass

Update Reason
Update of: https://github.com/eclipse-tractusx/sldt-semantic-models/tree/main/io.catenax.battery.battery_pass
to fit with the: #183 new Digital Product Passport
MS1 Criteria

[ ] The model that should be updated exists
[ ] The referenced use case exists
[ ] The potential updates are discussed with all stakeholders
[ ] The potential update will be either

[ ] backward compatible or
[ ] a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed

Migration Strategy: Both models (and the applications, which use those models) will be actively used for a while in parallel. Further details will be developed.

@catroest what are the plans here? Will there be a model update soon?

@bs-jokri yes the work is ongoing and will be presented end of this PI


Clean up TODOs and duplicated code in client code generation

Is this a Bug or Feature request?
Enhancement that's part of #4896
Description of the problem

[ ] replace Microsoft.DotNet.Cli.CommandLine code with Microsoft.Extensions.CommandLineUtils.Sources package
[x] replace custom lookup with Internal.WebHostBuilderFactory.Sources package
[ ] perhaps, replace console writing code with Microsoft.Extensions.Logging

not positive because adding dependencies to the tool seems perilous

Version of Microsoft.AspNetCore.Mvc or Microsoft.AspNetCore.App or Microsoft.AspNetCore.All
See the features/client.code.generation branch. That work is intended for the 2.2 Preview 3 milestone.

New bullets from #10641 discussions:

remove net461 tasks assembly and stick with the netstandard2.0 one

see https://github.com/aspnet/AspNetCore/pull/10641/files#r289548486

rename GetCurrentItems to something less generic in client targets file

see https://github.com/aspnet/AspNetCore/pull/10641/files#r289549577

add an escape hatch for the properties removed when calling Web API projects: %(OpenApiProjectReference.GlobalPropertiesToRemove)

see https://github.com/aspnet/AspNetCore/pull/10641/files#r289551199

New bullet from a #10669 discussion:

[ ] add @(FileWrites) items for code and document files as well as the OpenApiFiles.cache file

see https://github.com/aspnet/AspNetCore/pull/10669/files#r289567963

Couple more bullets

[ ] avoid NU1704 build warnings and other client / server incompatibility issues
[ ] change default $(OpenApiGenerateDocuments) to false in projects using .NET Core 2.0 or earlier

not supported by dotnet-getdocument tool in the Microsoft.Extensions.ApiDescription.Server package
otherwise, users need to manually add <OpenApiGenerateDocuments>false</OpenApiGenerateDocuments> when updating the NSwag or Swashbuckle package version to one that pulls in Microsoft.Extensions.ApiDescription.Server

Part 1 in 04b1adbc2e49

e89a0519b947
8417429b9bfe


Fix empty snapshot list server errors

It looks like I didn't properly review the updateFinishedPrefix uses

@Kha I am merging this PR as-is. My system became unusable today because of the panic error messages. It was happening every time I opened Emacs and then src/Lean/Elab/Command.lean. This PR seems to fix the problem after update-stage0.


Unparses foo as #{"foo"}

Unparser unparses `foo` as `#{"foo"}` which forms a different parse tree than the original source:
`foo` == xstr { str { 'foo' } }
`#{"foo"}` == xstr { begin { str { 'foo' } } }
While the two code snippets are functionally the same in standard ruby, Opal interprets them differently, so the distinction matters. Is there any reason Unparser can't differentiate between the two to create the proper tree?

While the two code snippets are functionally the same in standard ruby,

This is (so far) a standard ruby unparser. I never intend to explicitly support opal.

Is there any reason Unparser can't differentiate between the two to create the proper tree?

Technically no. Practically yes. Elaboration: I do this library on my free time and that one is super limited.
All my OSS is driven by clients needs, if a clients project stumbles about a problem in my libs they get a patch, if not: nothing happens.
I'd accept patches for this one.

Is this really intended behavior?
irb(main):038:0> initial_ast = Unparser.parse('"My name is #{first_name} #{last_name}."')
=> s(:dstr,
  s(:str, "My name is "),
  s(:begin,
    s(:send, nil, :first_name)),
  s(:str, " "),
  s(:begin,
    s(:send, nil, :last_name)),
  s(:str, "."))

irb(main):039:0> round_trip_ast = Unparser.parse(Unparser.unparse(initial_ast))
=> s(:dstr,
  s(:begin,
    s(:str, "My name is ")),
  s(:begin,
    s(:send, nil, :first_name)),
  s(:begin,
    s(:str, " ")),
  s(:begin,
    s(:send, nil, :last_name)),
  s(:begin,
    s(:str, ".")))

irb(main):040:0> initial_ast == round_trip_ast
=> false

@hovissimo Not intended.
The #129 branch is attempting to clean it up as a side effect.

Sorry did not intend to close, was fat fingering.

Very likely this gets fixed with #148


support for Flatpak

Hi
Is there any possibility to support Flatpak for this app?

If you want to work on it, go ahead, but I cannot do it because as I said, I do not have a Linux Machine which is compatible to build and publish on Flatpak.

I heard WSL for win10/win11 is quite capable https://docs.microsoft.com/en-us/windows/wsl/about

I tried WSL earlier, doesn't work for me.


[Getting Started with Sass] Failed to load external module babel-register

How can we reproduce this bug?
Install resources as mentioned: http://foundation.zurb.com/emails/docs/sass-guide.html
Create project
Run the npm start script in that project directory:
$ npm start
Looks like babel-register was was forgotten in package.json devDependancies?

We have an update for this that was tested on Foundation-sites. It will go out with 2.2!

@kball Are you able to apply the same fix from sites to the Emails Template?

Same issue here.
$ npm i babel-register
$ $(npm bin)/gulp

And I got this error from node-sass
[15:37:57] Requiring external module babel-register
[15:37:58] Using gulpfile ~/Projects/emails/most-anticipated/gulpfile.babel.js
[15:37:58] Starting 'default'...
[15:37:58] Starting 'build'...
[15:37:58] Starting 'clean'...
[15:37:58] Finished 'clean' after 5.6 ms
[15:37:58] Starting 'pages'...
[15:37:59] Finished 'pages' after 392 ms
[15:37:59] Starting 'sass'...
[15:37:59] 'sass' errored after 65 ms
[15:37:59] Error: ENOENT: no such file or directory, scandir '/Projects/emails/most-anticipated/node_modules/node-sass/vendor'
    at Error (native)
    at Object.fs.readdirSync (fs.js:808:18)
    at Object.getInstalledBinaries (/Projects/emails/most-anticipated/node_modules/node-sass/lib/extensions.js:119:13)
    at foundBinariesList (/Projects/emails/most-anticipated/node_modules/node-sass/lib/errors.js:20:15)
    at foundBinaries (/Projects/emails/most-anticipated/node_modules/node-sass/lib/errors.js:15:5)
    at Object.module.exports.missingBinary (/Projects/emails/most-anticipated/node_modules/node-sass/lib/errors.js:45:5)
    at Object.<anonymous> (/Projects/emails/most-anticipated/node_modules/node-sass/lib/index.js:15:28)
    at Module._compile (module.js:409:26)
    at Module._extensions..js (module.js:416:10)
    at Object.require.extensions.(anonymous function) [as .js] (/Projects/emails/most-anticipated/node_modules/babel-register/lib/node.js:166:7)
[15:37:59] 'build' errored after 467 ms
[15:37:59] 'default' errored after 469 ms

1

Please, is there any workaround we can use in the meantime?

This is not an actual error and can be ingored and closed.

Closing as outdated and we did not receive any further feedback.

this is the error I'm getting when I run foundation watch:
[23:05:02] Requiring external module @babel/register
Error: Plugin/Preset files are not allowed to export objects, only functions. In /Users/slickvick/Emails/node_modules/babel-preset-es2015/lib/index.js


Added hs-koblenz.txt

Thx. I just wanted to add this too. :D
Fachhochschule Koblenz has changed its name into Hochschule Koblenz
and Domain changed from
fh-koblenz.de      to
hs-koblenz.de

I'm sorry for the delay - i'm adding the domain.


Facebook videos

@Athlon1600  Sorry to bother you! The videos on Facebook cannot be loaded on your proxy, because you did not encode/encrypt the Facebook video's URL.
Please check this site:---
https://pi.dvbris.com/public/proxy/index.php
The above-mentioned site is able to load Facebook videos because it encrypts the video's URL. Please view the below code:---

But, unfortunately, your proxy site (https://unblockvideos.com/) does not encrypt the facebook video's URL. So, please kindly fix it.
Thank you very much!

This will need a special plugin like we have for other sites like youtube:
https://github.com/Athlon1600/php-proxy-plugin-bundle/tree/master/src
This goes with other issues we have with facebook barely working at all:
https://github.com/Athlon1600/php-proxy-app/issues/88
I'll try fixing all that up within a few weeks.

Facebook plugin is on my todo list now:
https://github.com/Athlon1600/php-proxy-app#to-do-list


Make the CI script more generic and robust.

As has been noted in #1 the glazier CI has been mostly a rough port of the druid-shell CI script. Recently, mostly thanks to @waywardmonkeys, our CI scripts have received some improvements. This PR here pushes that forward some more by incorporating some druid-shell post-fork changes and also a few other lessons from running the Druid CI over the years.
Changes

The script now has a short name, CI, instead of the automatic .github/workflows/ci.yml to reduce UI noise.

Everything is more generic, which means the script has e.g. --workspace which has no practical effect for Glazier at this point in time. The goal is to have a more easily syncable generic Linebender CI with minimal required changes per repository.

Wayland no longer receives a separate job and instead gets tested using the general process.
The original reason why Wayland had its own job for druid-shell was because we had GTK, X11, and Wayland to test which meant that the Linux job ran significantly longer than others. With GTK gone that reason has withered. Now the counter argument to have a single Linux job is stronger. Most of the common dependencies are already built for X11 so the additional building needed for Wayland is small. Also this helps reduce the GitHub job cache eviction pressure by no longer saving ~430MB per Wayland test run of essentially duplicate artifacts.

Removed libx11-dev & libpango1.0-dev from the dependency setup. The former is preinstalled already, the latter is no longer required.

Updated windows-2019 to windows-latest which currently translates to windows-2022.

Run clippy with no default features, then default features, then all features. This doesn't have too much of an impact on time spent, because the follow-up stages can reuse most dependencies that were built in an earlier stage.
As for motivation, imagine a scenario where glazier depends on lib_a and optionally on lib_b. Glazier code using feat_a of lib_a works fine, because lib_b enables lib_a::feat_a. However when lib_b is no longer included, code unexpectedly breaks. This has happened in practice with Druid and so doing more granular feature testing helps avoid it. Of course in a perfect world we would test every feature combination. However for regular CI I think starting with these three options should help catch most cases.

Removed beta toolchain jobs. The original motivation for these was to catch clippy errors early before they hit stable. Now  that #76 is merged and the strategy is to explicitly update the toolchain version, there won't be any sudden breakage that these beta jobs were meant to combat. So we can just remove them.

Documentation code tests no longer have a separate job and are instead run as part of the general testing path.

Documentation itself is generated using the nightly toolchain, because that is what docs.rs uses. This is another learned lesson from Druid where docs were fine with the stable toolchain, but then after publishing the crate the online docs were broken. Best to catch that earlier.

Added back doc generation tests for Linux.

Fixes #1

It does make sense and I wanted to do it, but you either have to manually update all the references (not that bad with search/replace) or reference a special variable that has to be defined by a repo admin in the github web UI. So I left it out of this PR at least.


Role ignored for Representations with two roles

When a DASH Representation has two Role tags, we are ignoring them both.  A text Representation could legitimately have both a role=main and a role=subtitle.  The DASH parser should not assume only one Role tag.

These streams exposed the issue: https://github.com/Axinom/dash-test-vectors/issues/1#issuecomment-243039762


python312Packages.sensorpush-ble: 1.6.2 -> 1.7.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.sensorpush-ble is: Library for SensorPush BLE devices
meta.homepage for python312Packages.sensorpush-ble is: https://github.com/Bluetooth-Devices/sensorpush-ble
meta.changelog for python312Packages.sensorpush-ble is: https://github.com/Bluetooth-Devices/sensorpush-ble/releases/tag/v1.7.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.7.0 with grep in /nix/store/xmz0kjzcn1z9hpmp1xn79dmixd4q3qvd-python3.12-sensorpush-ble-1.7.0
found 1.7.0 in filename of file in /nix/store/xmz0kjzcn1z9hpmp1xn79dmixd4q3qvd-python3.12-sensorpush-ble-1.7.0

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

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

home-assistant-component-tests.sensorpush
python311Packages.sensorpush-ble
python312Packages.sensorpush-ble

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xmz0kjzcn1z9hpmp1xn79dmixd4q3qvd-python3.12-sensorpush-ble-1.7.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.sensorpush-ble https://github.com/r-ryantm/nixpkgs/archive/a7f3eef2ed74c025b17497d6d82f02c66baf0540.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a7f3eef2ed74c025b17497d6d82f02c66baf0540#python312Packages.sensorpush-ble

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xmz0kjzcn1z9hpmp1xn79dmixd4q3qvd-python3.12-sensorpush-ble-1.7.0
ls -la /nix/store/xmz0kjzcn1z9hpmp1xn79dmixd4q3qvd-python3.12-sensorpush-ble-1.7.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 5 packages built:

home-assistant-component-tests.sensorpush
python311Packages.sensorpush-ble
python311Packages.sensorpush-ble.dist
python312Packages.sensorpush-ble
python312Packages.sensorpush-ble.dist

Maintainer pings
cc @fabaff for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 350412

x86_64-linux

:white_check_mark: 5 packages built:

home-assistant-component-tests.sensorpush
python311Packages.sensorpush-ble
python311Packages.sensorpush-ble.dist
python312Packages.sensorpush-ble
python312Packages.sensorpush-ble.dist


[Bug]: sending the cd command to other tmux panes should clear the command line first

Similar Issues

[X] Before filing, I have searched for similar issues.

Description
If you already have a command typed but not yet run, it messes with the tmux integration. See gif example:

Shell + Version
fish, version 3.3.1-838-g1eb58f905

Minimal Configuration to Reproduce
ctrlg init fish | source

Additional Details
We'd need a way to clear the line before sending our command. Or simply abort if the line isn't empty.

We can send ctrl+u via tmux send-keys -t "$pane" C-u and that covers most cases. The case it doesn't cover is if the cursor isn't at the end of the line.

Maybe it can be a config option between using ctrl+u to clear the line vs ctrl+c


Link in sidebar in the examples page in website doesn't work

"Button Styles" link in sidebar in the examples page in website doesn't work when its clicked

Hi @michalismichailidis1999 thank you for opening an issue regarding this, but this is not a bug. It's because there's no page for Button Styles. It's just a header for buttons that belong to that category.


Minor editorial changes to linear-classify.md

Adds small changes and fixes typos. The image caption for the SVM vs. Softmax example has been switched to use the natural log instead of the common log (luckily, the picture itself seems to already do this).

Awesome, thank you!


Bluetooth: Audio: add missing CONFIG_BT_AUDIO_DEBUG_STREAM_DATA guards

Some places did not properly guard debug messages for sending ISO data.
Signed-off-by: Emil Gydesen<EMAIL_ADDRESS>

It would be nice have dedicated macro for this purpose, so that one would not need use guard explicitly

Can you elaborate? Are you suggesting a BT_AUDIO_STREAM_DATA_DBG macro as an alternative to BT_DBG in these situations?


jsonrpsee version upgrade

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

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

Current dependencies on/for this PR:

main

PR #698   👈

PR #699

PR #700

This comment was auto-generated by Graphite.


maybe the q_dim in the original code fusion.py may be the num_dim

Thanks for your perfect work！

Thank you for pointing it out. You are definitely right.
However, I don't think the current version would cause any error as we initialize q_dim to be the same as num_hid
https://github.com/linjieli222/VQA_ReGAT/blob/9f6fe5bcda169c268eb1c92ef00df9f61d540081/model/regat.py#L115

Dear  scholar,
I feel the third picture could not corespond with the first formation.

I think the sum signal is some confused. Because in this code the visual data wasn't injected. I think maybe when injecting the visual data , the label_biases_att could be introduced( the label num is converted to the bias term)
The below picture is from https://github.com/linjieli222/VQA_ReGAT/blob/master/model/graph_att_layer.py

I found the word westerhof has error
So could I simply erase the /x185


New Review

Added QTSP verification expanded explanation and DSS open-source library as alternative
Added reviewer information

Added manually because of conflicts with the main branch. Closing this pull request.


Metadata segments are not available. Cannot balance.

2019-05-21T06:58:55,490 WARN [DatabaseSegmentManager-Exec--0] org.apache.druid.metadata.SQLMetadataSegmentManager - No segments found in the database!
2019-05-21T06:58:55,937 INFO [DatabaseRuleManager-Exec--0] org.apache.druid.metadata.SQLMetadataRuleManager - Polled and found 1 rule(s) for 1 datasource(s)
2019-05-21T06:58:56,846 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.helper.DruidCoordinatorSegmentInfoLoader - Starting coordination. Getting available segments.
2019-05-21T06:58:56,846 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.helper.DruidCoordinatorSegmentInfoLoader - Found [0] available segments.
2019-05-21T06:58:56,847 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.ReplicationThrottler - [_default_tier]: Replicant create queue is empty.
2019-05-21T06:58:56,847 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.helper.DruidCoordinatorCleanupUnneeded - Found 0 availableSegments, skipping the cleanup of segments from historicals. This is done to prevent a race condition in which the coordinator would drop all segments if it started running cleanup before it finished polling the metadata storage for available segments for the first time.
2019-05-21T06:58:56,847 WARN [Coordinator-Exec--0] org.apache.druid.server.coordinator.helper.DruidCoordinatorBalancer - Metadata segments are not available. Cannot balance.
2019-05-21T06:58:56,847 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.helper.DruidCoordinatorLogger - Load Queues:
2019-05-21T06:58:56,847 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.helper.DruidCoordinatorLogger - Server[localhost:8083, historical, _default_tier] has 0 left to load, 0 left to drop, 0 bytes queued, 0 bytes served.
2019-05-21T06:59:01,847 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.helper.DruidCoordinatorSegmentInfoLoader - Starting coordination. Getting available segments.
2019-05-21T06:59:01,848 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.helper.DruidCoordinatorSegmentInfoLoader - Found [0] available segments.
2019-05-21T06:59:01,848 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.ReplicationThrottler - [_default_tier]: Replicant create queue is empty.
2019-05-21T06:59:01,848 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.helper.DruidCoordinatorCleanupUnneeded - Found 0 availableSegments, skipping the cleanup of segments from historicals. This is done to prevent a race condition in which the coordinator would drop all segments if it started running cleanup before it finished polling the metadata storage for available segments for the first time.
2019-05-21T06:59:01,848 WARN [Coordinator-Exec--0] org.apache.druid.server.coordinator.helper.DruidCoordinatorBalancer - Metadata segments are not available. Cannot balance.
2019-05-21T06:59:01,848 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.helper.DruidCoordinatorLogger - Load Queues:
2019-05-21T06:59:01,848 INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.helper.DruidCoordinatorLogger - Server[localhost:8083, historical, _default_tier] has 0 left to load, 0 left to drop, 0 bytes queued, 0 bytes served.
real node can't generate segments to history node，and warn logs up.
and there is no more error log to be found,what can I do for that?

the task failed,then click the failed log but it returns 500 error

few minutes gone, the data in realnode disappear

Hi wangshulun,
Facing with similar issue. Have you found any solution ?

+1

having Same Issue:
org.apache.druid.metadata.SqlSegmentsMetadataManager - No segments found in the database!
INFO [Coordinator-Exec--0] org.apache.druid.server.coordinator.duty.BalanceSegments - Metadata segments are not available. Cannot balance.
ANy solution please?

Check if metadata-storage is configured correctly on the coordinator:
https://druid.apache.org/docs/latest/dependencies/metadata-storage.html#available-metadata-stores


error: str.replace is not a function , 'content-type'  test regular expression may not correct

file: request.js, in function 'Request.prototype.json', line 1260:
    if (!/^application\/x-www-form-urlencoded\b/.test(self.getHeader('content-type'))) {
        self.body = safeStringify(self.body, self._jsonReplacer)
      } else {
        self.body = self._qs.rfc3986(self.body)
      }

when 'content-type' is  'application/x-www-form-urlencoded; charset=UTF-8', error happen.
may be '\b' should be removed ?

It's impossible to debug this without more info. Please re-submit as a new issue and use the provided issue template to collect the important information.

It's impossible to debug this without more info. Please reply with more information, using the following template:

<!---
BEFORE YOU SUBMIT please read the following:

Please search open/closed issues before submitting since someone might have asked the same thing before!

If you have a support request or question please submit them to one of this resources:

* Stack Overflow: http://stackoverflow.com/questions/tagged/request+node.js using the tags `node.js` & `request`
* Gitter community: https://gitter.im/request/request?utm_source=newissue
* Also have a look at the Readme for more information on how to get support:
  https://github.com/request/request/blob/master/README.md

Issues on GitHub are only related to problems of request itself and we cannot answer
support questions here.
-->

### Summary
<!--- Provide a general summary of the issue in the title above -->
<!--- If describing an error, provide the error message & stack trace as well. -->

### Simplest Example to Reproduce
<!--- If describing a bug, tell us what request options we can use to reproduce the same bug/behavior -->

request({
  method: 'GET',
  url: 'http://example.com', // a public URL that we can hit to reproduce, if possible
  more: { 'options': 'here' }
},

### Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->
<!--- If request is handling requests/responses incorrectly, please include a link to the spec or documentation that supports that your expected behavior is correct. -->

### Current Behavior
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
<!--- If suggesting a change/improvement, explain the difference from current behavior -->

### Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
<!--- or ideas how to implement the addition or change -->

### Context
<!--- How has this issue affected you? What are you trying to accomplish? -->
<!--- Providing context helps us come up with a solution that is most useful in the real world -->

### Your Environment
<!--- Include as many relevant details about the environment you experienced the bug in -->

| software         | version
| ---------------- | -------
| request          |
| node             |
| npm              |
| Operating System |

Summary

I use request as a proxy, receive message from frontend ,and send data to backend api.
Simplest Example to Reproduce

in html, code like this:
$('.submit_btn').click(function(){
$.ajax({
url:'/submit',
type:'POST',
data:$('#formSubmit').serialize(),
success:function(data){
alert(data);
}
}
);
});
in express router, code like this:
request.post({
url: PRIVATE_URL,
json: true,
body: req.body,
headers: req.headers
}).pipe(res);
under below is http headers:
Accept:
/
Accept-Encoding:
gzip, deflate, br
Accept-Language:
zh-CN,zh;q=0.8
Connection:
keep-alive
Content-Length:
20
Content-Type:
application/x-www-form-urlencoded; charset=UTF-8
Cookie:
Host:
<IP_ADDRESS>:4000
Origin:
http://<IP_ADDRESS>:4000
Referer:
http://<IP_ADDRESS>:4000/test
User-Agent:
Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
X-Requested-With:
XMLHttpRequest
Expected Behavior

Current Behavior

TypeError: str.replace is not a function
at Querystring.rfc3986 (D:\wt\boc-portal\node_modules\request\lib\querystring.js:44:14)
at Request.json (D:\wt\boc-portal\node_modules\request\request.js:1215:30)
at Request.init (D:\wt\boc-portal\node_modules\request\request.js:407:10)
at new Request (D:\wt\boc-portal\node_modules\request\request.js:128:8)
at request (D:\wt\boc-portal\node_modules\request\index.js:54:10)
at Function.post (D:\wt\boc-portal\node_modules\request\index.js:62:12)
at D:\wt\boc-portal\routes\shop.js:21:13
at Layer.handle [as handle_request] (D:\wt\boc-portal\node_modules\express\lib\router\layer.js:95:5)
at next (D:\wt\boc-portal\node_modules\express\lib\router\route.js:131:13)
at Route.dispatch (D:\wt\boc-portal\node_modules\express\lib\router\route.js:112:3)
at Layer.handle [as handle_request] (D:\wt\boc-portal\node_modules\express\lib\router\layer.js:95:5)
at D:\wt\boc-portal\node_modules\express\lib\router\index.js:277:22
at Function.process_params (D:\wt\boc-portal\node_modules\express\lib\router\index.js:330:12)
at next (D:\wt\boc-portal\node_modules\express\lib\router\index.js:271:10)
at Function.handle (D:\wt\boc-portal\node_modules\express\lib\router\index.js:176:3)
at router (D:\wt\boc-portal\node_modules\express\lib\router\index.js:46:12)
Possible Solution

I think when processing content-type 'application/x-www-form-urlencoded; charset=UTF-8', request has errors, maybe it  is a problem caused by regular expression  '/^application/x-www-form-urlencoded\b/',
Context

Your Environment

software
version

request
2.79.0

node
v6.9.5

npm
3.10.10

Operating System
Windows10

Hi
If your content type is application/x-www-form-urlencoded, then maybe you should not use the json: true option. Although I understand the expectation is that the library converts the JSON properly to HTTP body as required, this may still resolve your problem.
For example, to add a SAML token as the body parameter:
body: 'SAMLResponse=' + SAMLResponseBase64URLEncoded,
Hope this helps.
Serdar


[Feat] Implement new API PluginManager::nn_preload

In this PR, add new API nn_repload for PluginManager to support new C-API WasmEdge_PluginInitWASINN.

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!

@L-jasmine Could you please help review this PR? Thanks a lot!

@L-jasmine Thanks for the review!


Where are the esp_event_base_t defined? (IDFGH-2468)

Environment

Development Kit:      [SBC-NodeMCU-ESP32]
Module or chip used:  [ESP32-WROOM-32]
IDF version platformio
Build System:         [Make|CMake]
Compiler version platformio
Operating System:     [Linux]
Power Supply:         [USB]

Problem Description
//Detailed problem description goes here.
Expected Behavior
That the WIFI_EVENT define is found
Actual Behavior
lib/gate_controller/mg_wifi_sta.cpp:154:48: error: 'WIFI_EVENT' was not declared in this scope
Steps to repropduce

load the example
try to compile it

Code to reproduce this issue
https://github.com/espressif/esp-idf/blob/30372f5a4ff2c0dfdaad95f544dc36bcdda30b75/examples/wifi/fast_scan/main/fast_scan.c
On the legacy list:
https://docs.espressif.com/projects/esp-idf/en/latest/api-reference/system/esp_event_legacy.html#_CPPv417system_event_id_t
I can see all the event types, but if I want to use the esp_event.h I need to move away from esp_event_loop_init(...) and for that i need the esp_event_base_t for the wifi or ip events, I can't find them anywhere in the documentation.

It even says in the notes:

This API is part of the legacy event system. New code should use event library API in esp_event.h

but it doesn't really say what equivalent code with esp_event.h would look like.

https://github.com/espressif/esp-idf/blob/release/v3.3/components/esp_event/include/esp_event_base.h#L27
https://github.com/espressif/esp-idf/blob/release/v3.3/components/esp_event/include/esp_event.h#L145

which says what type it is, not what variables are what values.
On this line:
https://github.com/espressif/esp-idf/blob/30372f5a4ff2c0dfdaad95f544dc36bcdda30b75/examples/wifi/fast_scan/main/fast_scan.c#L94
What is supposed to go into the parameters instead of WIFI_EVENT because that is not defined.
yes i know it is of type
`typedef const char*  esp_event_base_t; /**< unique pointer to a subsystem that exposes events */```
But what ID is the ID of the WIFI_EVENT base ? What actual value is behind it?

Hi @DasVoelkel,

IDF version platformio

As you have indicated, you are using ESP-IDF installed via Platformio. If I'm not mistaken, Platformio ships ESP-IDF v3.3.
However you are attempting to compile an example from the master branch, which was added in IDF v4.x. This explains the compilation error: WIFI_EVENT did not exist in IDF v3.3 and was introduced in IDF v4.0.
You have two options:

use examples which are provided with IDF version you have installed via Platformio
use a more recent IDF version; this may require following the ESP-IDF getting started guide, and not using Platformio.

Ok, thanks!
I'll keep this open until i work up a way to switch from pio to the normal idf


feat(resolver): add peercache ttl

Codecov Report

Merging #460 into master will decrease coverage by 2.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #460      +/-   ##
==========================================
- Coverage   65.07%   63.06%   -2.02%
==========================================
  Files          69       69
  Lines        4238     3769     -469
==========================================
- Hits         2758     2377     -381
+ Misses       1254     1170      -84
+ Partials      226      222       -4

Impacted Files
Coverage Δ

pkg/resolver/peercache.go
96.55% <100.00%> (+9.05%)
:arrow_up:

pkg/resolver/resolver.go
86.98% <100.00%> (-1.39%)
:arrow_down:

pkg/network/pubsub_handler.go
33.33% <0.00%> (-9.53%)
:arrow_down:

pkg/peer/peer.go
25.00% <0.00%> (-8.34%)
:arrow_down:

pkg/object/type_hint.go
10.00% <0.00%> (-5.22%)
:arrow_down:

pkg/migration/migration.go
31.14% <0.00%> (-5.22%)
:arrow_down:

internal/nat/nat.go
17.64% <0.00%> (-4.58%)
:arrow_down:

pkg/crypto/ed25519.go
61.11% <0.00%> (-4.16%)
:arrow_down:

pkg/network/filters.go
36.84% <0.00%> (-3.90%)
:arrow_down:

pkg/object/object.go
75.37% <0.00%> (-3.55%)
:arrow_down:

... and 60 more

Continue to review full report at Codecov.

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


.NET 7.0 Update: Use hubs in ASP.NET Core SignalR: Introduce dependency injection feature.

In the 7.0 version of the topic Use hubs in ASP.NET Core SignalR:  add a new section introducing dependency injection for SignalR.
This feature added in .NET 7.0 preview 2.
This issue has a parent tracking issue: #26477
Making use of the introduction work already provided in the blog preview docs where possible:  Dependency injection for SignalR hub methods
Then follow up by providing what is needed in What's new in ASP.NET Core 7.0 to represent it, and a link back.

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

ID: 1387f556-b4b7-70f9-5bd0-f0bccc597689
Version Independent ID: fb016cdc-d281-6b5b-7466-2c718e7274b4
Content: Use hubs in ASP.NET Core SignalR
Content Source: aspnetcore/signalr/hubs.md
Product: aspnet-core
Technology: aspnetcore-signalr
GitHub Login: @bradygaster
Microsoft Alias: bradyg

Feature has already been documented: https://github.com/dotnet/AspNetCore.Docs/pull/25746


Adds mapped storage for lots of entities + a botanical belt

About the PR
Filling in the content part of #4201. Still got some work to do, just sitting on this since i'm handling it.
Gonna do most of the belts, although lack of functionality in StorageComponent and ItemCounter is causing some issues.
Screenshots

Changelog

:cl:

add: botanical belt for gardening tools
add: add mapped storage sprites for lots of belts and other stuff

Ready for review.

Failing tests due to false-positive from EntityWhitelist.


The data is not available in the repository

It would be great if the repository were self-sufficient to reproduce the analyses and plots.
For that there are two options:

The data is programmatically retrieved from the source.
The data resides in the repository.

benefit
requirements

retrieved onthe fly
- no data in the git repo  => smaller repository   => smaller repository  - clear documentation of origin  - no data duplication
The origin must be accessible:   - Network access    - The origin is still working Services and databases can go offline.

in repo
Data is always the same, even if the origin changes it.
None (the repository must support the size of the data)

The in repo data seems more beneficial for reproducibility.

The zip file from PRIDE contains files which are not necessary and quite big with > 550 MB
-rw-r--r--@ 1 eglif  staff   530M Jan  6 13:29 DIANN1.8_SingleCells_CellCycle.7z
-rw-r--r--@ 1 eglif  staff   6.0M Jan  9 15:13 GSE129447_RAW.tar
-rw-r--r--@ 1 eglif  staff   9.7M Jan 12 10:00 GSE142277_RAW.tar
-rw-r--r--@ 1 eglif  staff   7.3M Jan 12 10:10 GSM4226257_out_gene_exon_tagged.dge_exonsds_046.txt.gz
-rw-r--r--@ 1 eglif  staff   2.9M Jan 12 10:11 GSM4226257_out_gene_exon_tagged.dge_intronsds_046.txt.gz

Whereas a file containing only the required data files in the already required folder structure is 20 x smaller with only 27 M.
% ls -lh data.tar.gz
-rw-r--r--@ 1 eglif  staff    27M Jan 12 12:07 data.tar.gz

The data is now bundled data in data.tar.gz and is extracted at the beginning of the notebook execution if not already present.


Change the locals exceed maximum error to a warning

It has come to my attention that this is a "wasm-parser" issue, which is not in the purview of wasm-bindgen, so this can be ignored, thanks. :)
Motivation
We are developing a project in the Rust Leptos web framework.
When we do a development build with Rust at opt level 0, there are more than 50k local bindings created, causing wasm-bindgen to throw an error that the max limit is hit.
When we do a release compile and do an opt level of 1 or above, there are less than 50k bindings - so only the dev compilations have more than 50k variables.
We need to use opt-level 0 for fast dev build iterations. The optimized builds take much longer.
This will likely be a fairly common occurrence for anyone using a Rust web framework to make a website of any large scale.
Proposed Solution
Change the errors to warnings where it is logical.
Alternatives
Possibly a flag to override the max local variable setting and increase it from 50k? This is not as ideal, as the tooling we use would then have to all pass that flag in (Cargo Leptos, etc), and it would not really make much sense for them to think of setting it higher.
Additional Context
This is the error I'm referring to, that limits our ability to even compile an opt-level 0 build for dev iterations:
Caused by:
    0: at `/home/alex/.cargo/git/checkouts/cargo-leptos-f550c444455a3716/34dd942/src/compile/front.rs:111:10`
    1: failed getting Wasm module for 'target/front/wasm32-unknown-unknown/debug/website.wasm'
    2: failed to parse input as wasm
    3: failed to parse code section
    4: locals exceed maximum (at offset 20291387)

Duplicate of #3451.


luci-app-firewall missing "port range" / usability issue

(observed on IRC)
It is not "obvious" for new users that the
"External port" field does support multiple ports or port ranges.
possible solution:
expand field description to "External port, list of ports or port-range"
PS: the overview differentiates between "port" and "ports"

The description states Match incoming traffic directed at the given destination port or port range on this host now


Object property indented after await

Description
Since version 1.8.1, When formatting an object, a property is indented if the previous property is initialized using the await keyword.
Input
The code looked like this before beautification:
async function() {
  const obj = {
    a: 1,
    b: await fn(),
    c: 2
  };
}

Expected Output
The code should have looked like this after beautification:
async function() {
  const obj = {
    a: 1,
    b: await fn(),
    c: 2
  };
}

Actual Output
The  code actually looked like this after beautification:
async function() {
  const obj = {
    a: 1,
    b: await fn(),
      c: 2
  };
}

Settings
Default

This is also a problem in multi-variable assignment statements. E.g.:
const os = require('os');

const foo = async =>{};

const a = 1,
    b = 2,
    c = await foo(),
    d = 3,
    e = await foo(),
    f = 4,
    g = 5,
    h = await foo(),
    i = await foo(),
    j = (await foo()),
    k = (await foo()),
    l = 6,
    m = 7,
    n = await foo(),
    o = 8;

Becomes:
const os = require('os');

const foo = async =>{};

const a = 1,
    b = 2,
    c = await foo(),
        d = 3,
        e = await foo(),
            f = 4,
            g = 5,
            h = await foo(),
                i = await foo(),
                    j = (await foo()),
                    k = (await foo()),
                    l = 6,
                    m = 7,
                    n = await foo(),
                        o = 8;

Thanks for the detailed issue report. This will help craft a fix.
Docs for await
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/await

Just confirmed that the Issue wasn't present in v1.7.5.

@qguv
Please try some inputs on https://beautifier.io/ and see if they look right.

@bitwiseman Looks great! Thanks again.


[BUG] Unable to focus or search using React Production mode.

Describe the bug
Using the dev build of react, my select component works perfectly.
However, once I go to prod build, the component is unable to be focused and search no longer works.
I went through the dom and the only difference I can find is that on the dev build, the following element exists:

All of the other Chakra components works 100% fine, it's just the chakra-react-select component.
Is there any known issue with production builds or minifying?
To Reproduce
Steps to reproduce the behavior:
Can't provide reproduction since it would require a production build.
I'm using create-react-app so really there shouldn't be any weirdness.
Desktop (please complete the following information):

OS: Mac
Browser Chrome
Version 1.8.7 (but i checked older versions and the issue remains)

Additional context
I'm assuming other people aren't having issues with this, but there's no reason that only this library is affected.
The only thing I can think of is some unlisted dependency issue.
Any tips would be greatly appreciated.

Can you show me how you implemented the select component?  you can obfuscate variable names but I can't do much without seeing how it's implemented.
The only thing I could guess that it might be without seeing that is if you have custom components defined inside the body of your select component.  If so it should be something like this instead:
// Make sure this is defined outside of the component which returns your select
// or you'll run into rendering issues
const customComponents = {
  Option: ({ children, ...props }) => (
    <chakraComponents.Option {...props}>
      {props.data.icon} {children}
    </chakraComponents.Option>
  ),
};

const Example = () => (
  <Select
    name="flavors"
    options={flavorOptions}
    placeholder="Select some flavors..."
    components={customComponents}
  />
);

If that's not the case then I'd need to see more about the implementation to have any way to help.

Sure thing! Have done some more debugging and discovered its stemming from how I'm handling the ValueContainer.
Basically I want the select box to say "X items selected" once more than one option has been selected.
Seems that maybe the child.type.name value is getting changed in production but not dev.
Is there a better or easier way of handling that?
Here is the code for that:
ValueContainer: ({ children, getValue, ...props }) => {

    var values = getValue();
    var valueLabel = '';

    if (values.length === 1) valueLabel = props.selectProps.getOptionLabel(values[0]);
    if (values.length > 1) valueLabel = `${values.length} items selected`;

    // Keep standard placeholder and input from react-select
    var childsToRender = React.Children.toArray(children).filter(
      (child) => ['Input', 'DummyInput', 'Placeholder'].indexOf(child.type.name) >= 0
    );
    return (
      <chakraComponents.ValueContainer {...props}>
        <Box textOverflow="ellipsis" overflow="hidden" whiteSpace="nowrap">
          {!props.selectProps.inputValue && valueLabel}
        </Box>
        {childsToRender}
      </chakraComponents.ValueContainer>
    );
  },

Did some more ready and just went with this implementation in case anyone else encounters it!
Suppose the original issue is that the build is scrubbing the name from the children in ValueContainer. Not sure if that's expected or not, but definitely like this new implementation more.
  ValueContainer: ({ children, ...props }) => {
    const { getValue, hasValue } = props;
    const nbValues = getValue().length;
    if (!hasValue) {
      return (
        <chakraComponents.ValueContainer {...props}>{children}</chakraComponents.ValueContainer>
      );
    }
    if (nbValues === 1) {
      return (
        <chakraComponents.ValueContainer {...props}>{children}</chakraComponents.ValueContainer>
      );
    }
    // This dom element is necessary for react-select to function correctly.
    // Without it, focus is all sorts of jank.
    // It's always the second child. So if you have 10 things selected, those 10 are in the first child.
    // Ghost element is the second.
    const necessaryHiddenChild = children && children.length > 0 ? children[1] : false;
    return (
      <chakraComponents.ValueContainer {...props}>
        {`${nbValues} items selected`}
        {necessaryHiddenChild}
      </chakraComponents.ValueContainer>
    );
  },
};

Ah ok, so I don't really have any experience with the child.type.name part of your code, but if I had to guess I'd say it's probably the displayName component property.  These are only really meant for debugging purposes as they get obfuscated or removed entirely when you do a production build with create-react-app.
It sounds like you solved your issues so I'll close this but if you're still having issues with it feel free to reach out!


Workaround for custom webpack providers?

I'm afraid that the answer for this will just be "eject" but I'll ask anyways.
With an entry point like this:
// index.js
import 'jquery/dist/jquery.min.js';
import 'bootstrap/dist/css/bootstrap.css';
import 'bootstrap/dist/js/bootstrap.min.js';

You'll get the error:

For right now I have jQuery in my index.html, but believe this is fixed by providing something like the following in the webpack config:
  plugins: [
    new webpack.ProvidePlugin({
      $: "jquery",
      jQuery: "jquery"
    })
  ],

However I'd really like to avoid ejecting. Any thoughts?

For right now I have jQuery in my index.html

Is it working? Why would the webpack setup be beneficial?

Yeah placing a script tag in my html works fine. In my mind the webpack setup is just convenient. All the 'static' dependencies can be listed at the top of your entry point and the index.html can remain clean.

Yeah I believe the current API calls for just using the index.html file for these kinds of things.
Might not be relevant to your use case, but it might make sense to use something like react-bootstrap which covers features like dropdowns without the use of jQuery as jQuery can be tricky to use with React.

Yeah, I was wondering, do you only use jquery for bootstrap? I think using react-bootstrap makes much more sense in this setup.

I also need this because I want to use datatables (which is a jquery plugin). A little tricky to use with react - but I cannot find anything as good as this which is written in react (esp responsive features)
btw - I love this project. Has saved me days and days... thanks so much!

If you want to avoid ejection, the best you can do is to create your own package that combines jquery with bootstrap and uses webpack to build them together with whatever configuration you need. You can then put this package on npm and use it from CRA project.


Fix to work RECHECK_SYNC_BACKEND correctly

Close #870
Changes

Fix to work RECHECK_SYNC_BACKEND correctly

A break for switch-case is missing. It is easy mistake.

Add a test case for checking whether synckit function has been called.

Codecov Report

Merging #872 (3cd1173) into main (4c51c22) will decrease coverage by 1.70%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #872      +/-   ##
==========================================
- Coverage   99.05%   97.35%   -1.70%
==========================================
  Files          69       13      -56
  Lines        3066     1098    -1968
  Branches      537      180     -357
==========================================
- Hits         3037     1069    -1968
  Misses         29       29

Impacted Files
Coverage Δ

packages/recheck/src/main.ts
100.00% <100.00%> (ø)

... and 56 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more