Why do you use two windows in L2 norm attack? I don't understand the mass moving (Fig.2)

Hi,
When I read your paper, Why do you use two windows in L2 norm attack? I don't understand your L2 norm attack and the mass moving (Fig. 2)?
Can you explain that for easy to understand?
Thank you!

Thanks for the interest in our paper!
The Linf attack is simple since for Linf-perturbations each coordinate can be changed up to eps independently of other coordinates. This independence just follows from the fact that the Linf-ball is separable over dimensions.
However, it's not the same for L2-perturbations. There we have some total L2-budget calculated over all coordinates of delta, and not over each coordinate separately. Thus, we have to make sure that when we modify one group of pixels, we do not exceed the total budget. Since on each iteration we are approximately at the boundary of the L2-ball, in order to make a new modification we first have to take some mass from one subset of entries of delta (i.e. to reduce the L2-norm of delta) in order to be able to change some other entries of delta. That's the main reason why we use two windows in the L2 attack.
Here is a toy example to illustrate what we do. Say, the L2-norm of perturbations is 2.
Here is the vector we have which has exactly L2-norm of 2:
delta_before = [1, 1, 1, 1, 0, 0, 0]
But we want to sample a new vector that would have some entries different from delta_before although still being close to it. To achieve this, we can remove some "mass" from the first 2 coordinates of delta_before -> this will lead to a vector [0, 0, 1, 1, 0, 0, 0]. Wonderful, now its L2-norm is equal to sqrt(2), thus we have some "free mass". We can use it to change, say, the last coordinate, i.e. we will get the following vector:
delta_after = [0, 0, 1, 1, 0, 0, sqrt(2)]
which now has L2-norm of 2 again. So delta_after will be the perturbation that we will use to query the black-box model on to check whether our modification of the perturbation helps to reduce the loss or not.
That's really the core idea, so it's really simple. It just gets a bit more involved when one has to write it down formally (see  Algorithm 3), but the actual idea is very intuitive.

Closing it for now, feel free to reopen if you have additional questions!

@max-andr However, the attack that uses the similar strategy with yours is the SignHunter attack (the paper of ''sign bits are all your need''), its L2 norm attack is not that complicated, it is only modify the pixel to the largest L2 norm distance.
https://github.com/ash-aldujaili/blackbox-adv-examples-signhunter/blob/master/src/attacks/blackbox/sign_attack.py#L62
The above code calls x + lr * g / norm(g)
https://github.com/ash-aldujaili/blackbox-adv-examples-signhunter/blob/master/src/utils/compute_fcts.py#L79

This approach is essentially equivalent to searching for adversarial examples in the Linf-ball embedded in the L2-ball. It is easy to implement, but it doesn't perform very well since it performs a search in a much smaller set (particularly when the input dimension is large). In particular on ImageNet, it performs worse than Bandits:

They also discuss this issue in more detail in APPENDIX I. ON THE L2-L∞ PERFORMANCE GAP in their paper. Based on my experience, I would say is that it is okay to reduce the search space only to the extreme points of the perturbation set (that's what we do in the Square Attack), but it is not okay to exclude a large portion of them (e.g. by restricting delta_i to be in {-1, 1} or in {-1, 0, 1}) which leads to suboptimal results.

I am currently working on the research to improve your Square Attack, but many attempts have been failed, your approach seems the limitation of the query-based black-box attack. Do you have any suggestion?

Do you have any suggestion?

I think one can still improve the attack in several ways boosting the results further.
For example, one idea would be that instead of changing pixels in each square to the same value, one could change it to horizontal or vertical stripes. Currently, we use stripes for initialization of the perturbation, but they also can be used in the sampling distribution to generate a new update. We did some preliminary tests, and that worked also quite well. For the best performance, one can try to adaptively decide on the type of the update (constant, horizontal stripes, vertical stripes) based on how well it works for each image separately. Moreover, one can also try to have stripes of different width (not just of width 1 as we used in the initialization).
Another aspect that probably can be improved is the schedule for the size of the square. Currently, we have a piecewise constant schedule for it, but maybe one can rather detect when the loss plateaus, and reduce the size of the square then. The advantage would be that this scheme can lead to a different adaptive schedule for every image which can be better than a single schedule for all images.

@max-andr Thank you very much! Your study is excellent, the experiment result is unbelievable!
Currently I am searching for the approach to improve random search, that is the core of your algorithm. I search a lot of literatures, but the random search seems quite remote,  I cannot find the literature of the  improvement of random search. Do you have any idea that how to improve the core of your algorithm, random search.
Also I consider your suggestions, and I will cite your paper and make it as my baseline.

Do you have any idea that how to improve the core of your algorithm, random search.

I do not see how the core idea (randomized search over the extreme points of the constraint set) can be improved substantially. But what one can certainly try to improve is the sampling distribution. That's exactly where one can easily incorporate some domain-specific prior knowledge into the problem. One example that we did was to use square-shaped updates in the sampling distribution where we change all the values in a square to the same value (at least, for Linf-perturbations). One can think about other, more advanced schemes on how to improve the sampling distribution (both for L2 and Linf).

@max-andr I conducted a L_inf attack experiment which attack 1000 images of ImageNet, the target model is Inception_v3. However, when I use the original square attack, the performance is best, the Avg. query per successful image = 254.
When I change the update window to the vertical strip with each strip value = epsilon, the Avg. query = 416, and horizontal strip of update window also leads to Avg. Query =424.
Maybe the value inside updated window should not be vertical strip with the value inside stripe = epsilon? Because it perform worse than all value constantly equal epsilon, which is original Square Attack performs best?

Well, that's why we didn't use the stripes in the update ;)
But our hypothesis was that for some images updating stripes may be better. So you can come up with some input-dependent scheme that would automatically decide which perturbation time is better for the given image. If this scheme is reasonable, then in the worst case it should be as good as the vanilla square attack, but maybe there will be some improvement (maybe a small one, one would need to benchmark it).


Additional text for FB posts

Allows to grab additional text from facebook page when post was shared from external source

So this works on the shares from external source, where it shows this text:

And on shared posts where it shows this text:

Currently doesn't work on this kind of post which I assume is just shared image:

@ZueFe Hey!
Thanks for your contribution :)
Actually I think that new field is some kind of “provider-specific”. ‘Post’ class should be as common as possible for all source providers.
I think it’s more appropriable to use concatenation for that two text fields and just use ‘text’ field (e.g. I did it in PikabuSkraper).

I split "addition text" into two strings since only one is actually displayed (first image) and second is just kinda...there...is more like first paragraph or some such, so figured concat is not the way to go.
With FB there also a possibility to have "commneted" shared post, so in "text" you'd have whatever the user wrote when sharing, and "additional text" is text from the source.
But perhaps I can create extension for Post class for FB only, otherwise if it's concated, you will just end up splitting in anyway.

@ZueFe Hey!
Thanks for your contribution :)
Actually I think that new field is some kind of “provider-specific”. ‘Post’ class should be as common as possible for all source providers.
I think it’s more appropriable to use concatenation for that two text fields and just use ‘text’ field (e.g. I did it in PikabuSkraper).

I split "addition text" into two strings since only one is actually displayed (first image) and second is just kinda...there...is more like first paragraph or some such, so figured concat is not the way to go.
With FB there also a possibility to have "commneted" shared post, so in "text" you'd have whatever the user wrote when sharing, and "additional text" is text from the source.
But perhaps I can create extension for Post class for FB only, otherwise if it's concated, you will just end up splitting in anyway.

@ZueFe Ah, I get it.
I think that the comment of the shared post should be the main source of the text field. So I suppose it's ok.
About reposted data and attached articles - It's not a simple issue at all. Facebook provides just a small preview with the first paragraph and one tiny image, but most of the other sources do not have those features at all. And adding an extension/overriding is not the option in this case because Kotlin data classes are final (Post). And I do not like that proposal because one of the main goals of this project is to "equate" format of all sources we have (like RSS, but bit different and with some features).
I've been thinking a bit about this issue and have some thoughts and options about it:

Adding field with the list of all attached links of the post.
Adding new media type - Unknown with some link.
Adding new media type - Article with some link and optional preview text and image.
Leaving as is and just use concatenation for the text field with an ellipsis at the end of it.

@SokoMishaLov
When it comes to small previews, there's a way to extract both strings and concat them together, so deffinately a possibility. They are both wrapped in div and span with human class names (as far as I remember).
A bummer aboout Post class tho :)
If I read you correctly, I think "Article" would work probably the best, similar "Video" and "Image" ones. Perhaps then video and image can have string description added to it? Not sure other pages would use it tho :/
I'll jump into making Article media class if that's ok then? We can try to figure out what to do with shared images in the meantime.

@ZueFe just realized that making "Article" a new media type is a bad idea even so. "Article" cannot be a media file at all. It's some more complex than that. Sorry for confusing you :(
We need to find out a better solution I think.

@SokoMishaLov
ah hm, well I don't really know the project structure that well, so no clue where it should go. Still with this PR I included link to original article, not the FB post, so it might help some
In all fairness, by broad definition, medium is anything that transmits and/or conveys information ^^

@ZueFe well, yeah, thank you anyway :)
I'm still thinking about the best solution to this case.
It's a good proposal about Medium, but it's not simple to implement because of the current data structure.
Medium and any other "blog" post should have ordered data. For now we just have text field and list of media, and filling it will not be good because of breaking text and media order.

@SokoMishaLov
I see hm, well lemme know if you come up with something that will work, this is a rather important feature for app I'm making, would rather have it in the repo that is being regularly updated :)

Hey just curious, was there any progress on this?

Hey, @ZueFe!
My apologies for being unavailable for such a long time.
Unfortunately, I didn't have enough time to work on this, but I still have some plans for this.
I think that the additional media type like UnknownLink would be the best way.

@SokoMishaLov no worries, thanks for the answer, I will rewrite it when I find a little time then and send update PR once the conflicts are resolved.


Add support for sources at concept level

Need to add support for sources at concept level as mentioned here -> https://github.com/geolexica/geolexica-server/issues/151#issuecomment-1689384693

And we need to add it to the concept model.

And we need to add it to the concept model.

@ronaldtse Added this ticket to make changes in concept model -> https://github.com/glossarist/concept-model/issues/31


Faiss re-index to adjust IVFx,Flat?

Hi everyone,
This faiss index has grown since it was originally created so the x in IVFx,Flat is smaller than the default 4*sqrt(n). Would it be worthwhile to reindex to get larger buckets/larger nprobe or should I see if I run into performance/result quality issues?
{
'path': './all-mpnet-base-v2',
'backend': 'faiss',
'content': True,
'dimensions': 768,
'offset': 1976772,
'build': {
'create': '2023-04-27T17:08:28Z',
'python': '3.10.6',
'settings': {'components': 'IVF1272,Flat'},
'system': 'Linux (x86_64)',
'txtai': '5.5.0'
},
'update': '2023-05-10T03:06:35Z'
}
Thanks!

Hello, thank you for writing up the question.
A rebuild in this case may be beneficial but not required unless you're seeing performance issues. It could be good to consider a recurring backup/archive/rebuild job. The backup could simply be a directory copy script or you can use embeddings.save and save the index as a .tar.gz.
If rebuild speed becomes an issue, you'll want to consider the faiss.sample parameter - https://neuml.github.io/txtai/embeddings/configuration/#faiss

Thanks for the response David and for all your work on txtai. Definitely appreciated. I'm more concerned with result quality than speed for now, so I'll play around with the nprobe parameter first during searches and see if that has an effect.
If I were to reindex, is this how it would be done?
from txtai.embeddings import Embeddings
embed = Embeddings()
embed.load("./embedding_index")
embed.reindex({"path" : "./all-mpnet-base-v2", "backend" : "faiss", "content" : True})
embed.save("./embedding_index")
embed.close()
Thanks again!

That code should do it. The backend parameter defaults to faiss so you shouldn't need to provide that. You can also try the hnsw backend for comparison purposes.

Closing due to inactivity. Re-open or create a new issue to continue the conversation.


Add API to create view controllers without registering features

This change adds a new way to create view controllers, without having to pre-register a feature with the framework. The use case for this is to more easily be able to create view controller, which decreases the learning curve to get into using the framework.
It also will make it easier to use the Hub Framework for playgrounds.
To make this happen, another convenience API is introduced to be able to create content operation factories using a concrete class that takes a block. Again, this reduces the barrier of entry for creating content operations, and the need for boilerplate.

@spotify/objc-dev

Also planning to update the "Getting Started Guide" to use this API instead, since it's so much easier to get into and doesn't require modifying the navigation stack. Will do in a subsequent PR thou :)

Awesome stuff! 🎉

Current coverage is 93.76% (diff: 100%)

Merging #62 into master will increase coverage by 0.04%

@@             master        #62   diff @@
==========================================
  Files            56         57     +1
  Lines          3824       3849    +25
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           3584       3609    +25
  Misses          240        240
  Partials          0          0

Powered by Codecov. Last update 69b9cba...d227303


Commit to the next power table in the message payload

#151 makes it difficult to validate finality certificates by introducing a power lookback. Right now, given the previous power table and a finality certificate, I can generate the "next" power table and validate it by checking the PowerTable CID in the last finalized epoch. After this change, I won't be able to do that.
One solution is to commit to the power table used to validate the next instance in the message Payload itself (and possibly remove it from the tipset list). This would be somewhat annoying at the moment because the "next" power table can change over the course of an instance as we try to find the longest common prefix. However, given a lookback of at least one instance, this value will be consistent for all participants in the instance.

Discussed in standup:

Regular light clients only need the power table used to validate the next finality certificate.
Regular GPBFT participants can always get their power tables from lotus if/when participating in voting (can't participate in an instance (except decide) unless they've synced that chain).
However, we may want GPBFT followers that follow the GPBFT chain without syncing the main chain. For these clients, having "future" power tables (the power tables as they're finalized) without having to talk to lotus could be useful.

So, I'm proposing:
type Payload struct {
	// ...
	Value Value
}

type Value struct {
	// Power table from the base tipset.
	BasePowerTable Cid
	// Power table used to validate the next instance.
	NextPowerTable Cid
	// Arbitrary commitment tree, used primarily for snark-friendly power tables. Unused for
	// now.
	Commitments [32]byte
	// The chain being finalized.
	Chain ECChain
}

The signing format will change to:
DSTPrefix || Step || Round || Instance || \
    Digest(BasePowerTable) || Digest(NextPowerTable) || \
    Commitments || \
    MerkleRoot(Chain)

I'm also proposing that we remove the power table from each tipset:
type TipSet struct {
	// The EC epoch (strictly increasing).
	Epoch int64
	// The tipset's key (canonically ordered concatenated block-header CIDs).
	Key TipSetKey
	// Keccak256 root hash of the commitments merkle tree.
	Commitments [32]byte
}

NOTE: we're including the base power table in the Value, not the head power table. Unless we involve lotus to get the head power table from the last instance, this reduces the effective lookback by 1.
Alternatively, we could use the head power table, but then we'd need to add the power tables back into the tipset objects. By excluding it from the tipset objects, we can avoid computing the CID for every power table and instead just need to compute it for the last tipset finalized in each instance.

In terms of finality certificates, we'll need to support two formats:

One that tracks the latest finalized power table.
One that tracks the power table used to validate the next instance (the next finality certificate).

Only GPBFT "followers" will use the first protocol, light clients will use the second so they don't have to understand and/or care about the power table delay (which also gives us more leeway to change it in the future).

EDIT: I split the value into data/chain for simplicity. Otherwise the refactor is going to be annoying.

Data can be trivially constructed when we start an instance and validated when we receive a message by checking for equality.
We can then ignore Data in the rest of the protocol (except when sending messages, because we need it to be signed).

In theory, we could drop it from our messages entirely and supply it when validating message signatures. But that doesn't seem worth it.

A downside of the "support both" solution is that validating finality certificate chains still requires lookback. One option is to always include the delta for validating the next finality certificate (lookback power table), and optionally include a delta for the base power table (latest power table). It's a slight waste of bandwidth, but so minimal it shouldn't be a huge issue in practice.
But including the lookback table is going to be kind of annoying regardless of what we do...

Rename NextPowerTable to NextValidationPowerTable

MVP: Put NextPowerTable (or NextValidationPowerTable) in the root.
Maybe: Remove the power table from the tipsets and add a base power table to the root.
TODO: Benchmark generating power tables per tipset. @Kubuxu pointed out that only using the base power table could help with catch-up.

Benchmark results: It's taking about 1.5s to walk the power table hot, or 4.3 when cold.
However, that's without any diffing or parallelism, both of which are options for us (we already have the diffing code courtesy lily). So I doubt this is going to be a huge performance issue.

(Catching up)

By excluding it from the tipset objects, we can avoid computing the CID for every power table and instead just need to compute it for the last tipset finalized in each instance.

I think this is what you've just benchmarked, but I would question whether computing the power table CID for each EC epoch is really much of a burden.
Your MVP proposal sounds good.
I think it's probably fine for light clients to deal with the lookback. So the deltas are for the power table just finalised, and validation requires holding on to 10 most recent computed versions. Are your changes attempting to avoid that?

I think this is what you've just benchmarked, but I would question whether computing the power table CID for each EC epoch is really much of a burden.

Yes, that's what I benchmarked. And it doesn't look like a burden except, possibly, if we're running in 'catch up' mode.

I think it's probably fine for light clients to deal with the lookback. So the deltas are for the power table just finalised, and validation requires holding on to 10 most recent computed versions. Are your changes attempting to avoid that?

My plan was to support deltas for both and let the client decide which deltas they want to request. But I'm still working out the details.
You're right that the client could handle lookback, but I'd rather not have clients care about it. It simplifies the client logic and means we can change the lookback in the protocol itself without touching the clients.

NOTE: I've tried diffing and the performance was actually worse. Not sure why yet (I'm testing on a live node so it could be other factors).

@Kubuxu I'm just calling it PowerTable as it should be pretty unambiguous now. We're explicitly agreeing on the power table used to validate the next instance (even though we should all already agree).


Cursor offset right from Unicode content

Hi,
I'm editing some files which include Myanmar text. This includes diacritic characters (meaning char + char adding a diacritic (above / below / left / right) the previous char). Atom appears to give each char equal space, meaning that I need to click right of the text to select it, and the highlight appears offset right, too. Each string makes it more difficult to highlight text appearing after it on the line.

Put the text နေပြည်တော် in the middle of a long line to see what this looks like. This problem will occur with many other scripts, for example Devanagari used widely in India and Nepal - use this text: देवनागरी. Can you use HTML5 Canvas measureText() ?

Thanks for the report -- I believe this is a duplicate of https://github.com/atom/atom/issues/1849, so I'm closing this in favor of that issue. You might also be interested in https://github.com/atom/atom/issues/6055 and https://github.com/atom/atom/pull/6083.


recast: Update to upstream version 1.6.0

Release notes:

https://github.com/recastnavigation/recastnavigation/releases/tag/v1.6.0

Cherry-picked for 4.0.4.

Cherry-picked for 3.6.


Add more errors to improve logging

Last bit of the work to improve error messages for the commands. Adds errors to:
RunCommand
StatusCommand
VerifyCommand
WidgetCommand

Merged #198 into main.


Add clear error messages when the user is not able to deploy an instance

Description
Add clear error messages when the user is not able to deploy the instance for any reason.
for example:

When there are no nodes in a specific region, there should be a clear message mentioning that this region doesn't have online nodes instead of showing Node ID is required and not being able to select a node.

Same logic should be applied if the resources are not enough in the selected region/farm.

And for every case there should be a clear error message why the user is not able to deploy the instance.

Verified on https://getmastodon.threefold.io/
a new logic was implemented in #79 where the Deploy button is active at all times but if the user clicks on it while an error is present it will focus on the field with a clear error message explaining the error.
and more error messages were added/Improved in:

https://github.com/threefoldtech/www-mastodon/issues/20
https://github.com/threefoldtech/www-mastodon/issues/75
https://github.com/threefoldtech/www-mastodon/issues/90


Thank you message after run

Thank you message to patreons at the end of the run

Not adding this for the reasons we discussed earlier.


WezTerm + Yazi on Windows does not show Image Preview

What system are you running Yazi on?
Windows
What terminal are you running Yazi in?
WezTerm
Yazi version
Yazi 0.1.4
Did you try the latest main branch to see if the problem has already been fixed?
Not tried, and I'll explain why below
Describe the bug
I'm using the latest binary.

Expected Behavior
I expect the image to show up on in the preview portion of the terminal.
To Reproduce
On a base Windows, install both WezTerm and Yazi with scoop, like:
scoop install wezterm yazi
Start WezTerm and open Yazi, find an image.
Configuration
No response
Anything else?
No response

Yazi version on Scoop is outdated. Could you please try downloading the latest version from the releases page https://github.com/sxyazi/yazi/releases
Also see this https://yazi-rs.github.io/docs/faq#why-cant-i-preview-files-on-windows

0.1.5 doesn't show images either

Have you configure your file(1) as per https://github.com/sxyazi/yazi/wiki/Windows-Installation-Guide#requirements?

Ah, bugger. WezTerm was not inheriting the environment from the calling process, so file wasn't working.
When I manually add the missing environment, it now works.
Thanks!


Cleaning of mockup repo

Here the next step necessary to clean the mockup repository and have a stable and clean basecode:

[x] Close the pull request related to the download module: https://github.com/CMCC-Foundation/bluecloud-mockup_method/pull/15
[x] Refactoring the main script

[ ]  Refactoring the main script

This is the current main script: mockup.py and it is a mess. It has too much variables or ad-hoc setting for each example provided. To think a solution to clean the code.

@mdrudi My cleaning work on the mockup has finished.
I cleaned the main of this repo, now it is a wrapper which call the specific mockup of the methods available here: mockups.
Then I also introduced a new features from Ocean Climate with a new module: modules. A README is still missing in this part to describe the pro to use on Dataminer this approach


Fix 26.6.1 version in ChangeLog

Some typo has been done in the latest ChangeLog release.

Thanks, it is fixed in the development repo, just not yet deployed.


Error building with 6.1.8 on create-react-app, works with 6.1.6

When building a React application created with create-react-app and adding eosjs 6.1.8 as a dependency, building the app (npm run build) results in the following error:
root@blockone:~/block.one# npm run build

><EMAIL_ADDRESS>build /root/block.one
> react-scripts build

Creating an optimized production build...
Failed to compile.

Failed to minify the code from this file:

 	./node_modules/eosjs/lib/write-api.js:98

Read more here: http://bit.ly/2tRViJ9

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `react-scripts build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-03-11T14_53_14_563Z-debug.log

This is happening because the compiled version of eosjs 6.1.8 (shipped via npm) still has an async keyword in the ES5 version of the code. The line in question is https://github.com/EOSIO/eosjs/blob/3dbee2426626c1ebe8c8bd3fe585eb1362457aac/src/write-api.js#L82
Forcing the build to use eosjs 6.1.6 fixes the issue.

<EMAIL_ADDRESS>


Add web.config to test sites

Follow up for https://github.com/aspnet/Mvc/pull/4433. This time, I'm also updating the tests sites. Although the functional tests will not run behind IIS, we decided to add IISIntegration so the sites themselves can be launched from Visual Studios.
cc @ryanbrandenburg @Tratcher @NTaylorMullen

:shipit: Seems good to me, looking like it's missing some wwwroot's in content, but my PR is already fixing those so no need to change it.

@ryanbrandenburg where am I missing wwwroot? I shouldn't be missing anything.

Huh, I completely mis-remembered that, I could have sworn most of the test/Website sites had wwwroot folders but they don't. Ignore me!

@ryanbrandenburg I removed the ones that had only a placeholder HelloWorld.htm since we no longer need them. Maybe that's what you were thinking of?

Probably.


add Explosion AI and AWS to sponsors

Add AWS and Explosion AI to primary sponsors.
See:

tweet thanking AWS
tweet thanking Explosion AI

For context.
@ines @spotaws please let me know if you'd like me to change this at all.
[skip change file check]

please review.

I'll give it 24hours for the sponsors to commit if they wish.

LGTM.

Thanks everyone.


Move to yarn and add a yarn workspace in the root

As far as I can see this is done, see #210, #277, and #345.


vcpkg crashes while building opencv with x86-windows-static-md

Describe the bug
Building a project with opencv causes vcpkg to crash with latest version.  This was working fine in the past but today I did a git pull on the vcpkg repo and now it fails.
Environment

OS: Windows
Compiler: Visual Studio 17.5.3

To Reproduce
Steps to reproduce the behavior:

With latest vcpkg I have project with this manifestL
{
"$schema": "https://raw.githubusercontent.com/microsoft/vcpkg/master/scripts/vcpkg.schema.json",
"name": "spaghetti-laser-show",
"builtin-baseline": "6ba505cf2c1752d8ea5abb21427e23ff89dc486f",
"version": "0.0.1",
"dependencies": [
{
"name": "opencv"
},
{
"name": "libusb"
}
],
"overrides": [
{
"name": "libusb",
"version": "1.0.23"
}
]
}
See error

The following packages will be built and installed:
8>  * libpng[core]:x86-windows-static-md -> 1.6.37#16 -- H:\vcpkg\buildtrees\versioning_\versions\libpng\b082585ac20aefc27150af5386b6a8a15473e93a
8>    opencv[core,default-features]:x86-windows-static-md -> 4.5.4#1 -- H:\vcpkg\buildtrees\versioning_\versions\opencv\c120b015f37bc79900712d64e8ca612d71be22cc
8>  * opencv4[core,default-features,dnn,jpeg,png,quirc,tiff,webp]:x86-windows-static-md -> 4.5.4#2 -- H:\vcpkg\buildtrees\versioning_\versions\opencv4\537abba5a070d173cf42510f86ff4ffe057dd77f
8>  * protobuf[core]:x64-windows -> 3.18.0#1 -- H:\vcpkg\buildtrees\versioning_\versions\protobuf\5f6aa04d94e184b89c1887946fb4684bc51c4611
8>  * protobuf[core]:x86-windows-static-md -> 3.18.0#1 -- H:\vcpkg\buildtrees\versioning_\versions\protobuf\5f6aa04d94e184b89c1887946fb4684bc51c4611
8>  * quirc[core]:x86-windows-static-md -> 1.1#2 -- H:\vcpkg\buildtrees\versioning_\versions\quirc\15bad29ef4d2466b236311ce7af075dbb9507ed9
8>Additional packages (*) will be modified to complete this operation.
8>Restored 0 package(s) from C:\Users\Gary\AppData\Local\vcpkg\archives in  274 us. Use --debug to see more details.
8>Installing 1/6 quirc:x86-windows-static-md...
8>Building quirc[core]:x86-windows-static-md...
8>H:\vcpkg\scripts\buildsystems\msbuild\vcpkg.targets(183,5): warning : warning: -- Using community triplet x86-windows-static-md. This triplet configuration is not guaranteed to succeed.
8>-- [COMMUNITY] Loading triplet configuration from: H:\vcpkg\triplets\community\x86-windows-static-md.cmake
8>-- Installing port from location: H:\vcpkg\buildtrees\versioning_\versions\quirc\15bad29ef4d2466b236311ce7af075dbb9507ed9
8>-- Using cached dlbeer-quirc-7e7ab596e4d0988faf1c12ae89c354b114181c40.tar.gz.
8>-- Cleaning sources at H:/vcpkg/buildtrees/quirc/src/b114181c40-f1e71e0d5b.clean. Use --editable to skip cleaning for the packages you specify.
8>-- Extracting source H:/vcpkg/downloads/dlbeer-quirc-7e7ab596e4d0988faf1c12ae89c354b114181c40.tar.gz
8>-- Using source at H:/vcpkg/buildtrees/quirc/src/b114181c40-f1e71e0d5b.clean
8>-- Found external ninja('1.11.0').
8>-- Configuring x86-windows-static-md
8>-- Building x86-windows-static-md-dbg
8>-- Building x86-windows-static-md-rel
8>-- Installing: H:/vcpkg/packages/quirc_x86-windows-static-md/share/quirc/copyright/LICENSE
8>-- Performing post-build validation
8>H:\vcpkg\scripts\buildsystems\msbuild\vcpkg.targets(183,5): warning : warning: copyright being a directory is deprecated.
8>H:\vcpkg\scripts\buildsystems\msbuild\vcpkg.targets(183,5): warning : warning: The software license must be available at ${CURRENT_PACKAGES_DIR}/share/quirc/copyright
8>Elapsed time to handle quirc:x86-windows-static-md: 3.1538863 s
8>vcpkg has crashed. Please create an issue at https://github.com/microsoft/vcpkg containing a brief summary of what you were trying to do and the following information.
8>
8>Version=2023-03-14-105f7f7e8a5ea10dfac9874ff9d1a6bacba5f454
8>EXCEPTION=argument not found

Expected behavior
No error
Failure logs
None
Additional context
None
I am not sure how to go about debugging this issue.  Please let me know if there is additional information needed and how to obtain it.

Glad I reproduced the problem and found the cause.
The builtin-baseline you are using is 6ba505cf2c1752d8ea5abb21427e23ff89dc486f, which was committed on 2022-01-28:
PS E:\vcpkg02> git show 6ba505cf2c1752d8ea5abb21427e23ff89dc486f
commit 6ba505cf2c1752d8ea5abb21427e23ff89dc486f
Author: autoantwort<EMAIL_ADDRESS>Date:   Fri Jan 28 20:30:49 2022 +0100

At this point, the processing of copyright in prots/quirc/portfile.cmake is as follows:
file(INSTALL ${SOURCE_PATH}/LICENSE DESTINATION ${CURRENT_PACKAGES_DIR}/share/quirc/copyright)
It will create a share/quirc/copyright/ folder, which is non-compliant, so a post-check error will be reported:
-- Performing post-build validation
warning: `copyright` being a directory is deprecated.
warning: The software license must be available at ${CURRENT_PACKAGES_DIR}/share/quirc/copyright
Elapsed time to handle quirc:x86-windows-static-md: 12.8941562 s
vcpkg has crashed. Please create an issue at https://github.com/microsoft/vcpkg containing a brief summary of what you were trying to do and the following information.

Later, we uniformly made modifications in https://github.com/microsoft/vcpkg/pull/25409:
- file(INSTALL ${SOURCE_PATH}/LICENSE DESTINATION ${CURRENT_PACKAGES_DIR}/share/quirc/copyright)
+ file(INSTALL "${SOURCE_PATH}/LICENSE" DESTINATION "${CURRENT_PACKAGES_DIR}/share/${PORT}" RENAME copyright)

There are currently two solutions:

Use the modified ID, for example: 763f6664c1858240fdfb563c55f9c9fdc5e19ac7.

Use override to overwrite other version constraints:

"overrides": [
    {
        "name": "quirc",
        "version": "1.1#3"
    }
]

Thank you.  I didn't use either of your solutions but your reply did make me notice my builtin-baseline uuid.  I don't quite understand how that value works but I updated it to the current value of vcpkg and now my application compiles without error.  Thank you for your reply and the explanation.

I don't quite understand how that value works

For a port that does not specify a version with override and version>=, it will search for the highest version specified by the current builtin-baseline by default.
For example: https://github.com/microsoft/vcpkg/commit/763f6664c1858240fdfb563c55f9c9fdc5e19ac7
PS E:\vcpkg01> git show 763f666
commit 763f6664c1858240fdfb563c55f9c9fdc5e19ac7
Author: Thomas1664<EMAIL_ADDRESS>Date: Fri Jun 24 21:50:23 2022 +0200

Your dependency opencv will find the latest version before Date: Fri Jun 24 21:50:23 2022 +0200:
PS E:\vcpkg04> git blame versions/o-/opencv.json
2f6537fa2b port_versions/o-/opencv.json (Victor Romero     2021-01-14 16:08:36 -0800   1) {
2f6537fa2b port_versions/o-/opencv.json (Victor Romero     2021-01-14 16:08:36 -0800   2)   "versions": [
2a95acc161 versions/o-/opencv.json      (Russell Greene    2023-02-24 14:02:54 -0600   3)     {
2a95acc161 versions/o-/opencv.json      (Russell Greene    2023-02-24 14:02:54 -0600   4)       "git-tree": "7c13270745cf85fc4146cd4f21ee4f71eb2ca7e1",
2a95acc161 versions/o-/opencv.json      (Russell Greene    2023-02-24 14:02:54 -0600   5)       "version": "4.7.0",
2a95acc161 versions/o-/opencv.json      (Russell Greene    2023-02-24 14:02:54 -0600   6)       "port-version": 1
2a95acc161 versions/o-/opencv.json      (Russell Greene    2023-02-24 14:02:54 -0600   7)     },
49299e0c05 versions/o-/opencv.json      (Matthew Oliver    2023-01-18 06:35:29 +1100   8)     {
49299e0c05 versions/o-/opencv.json      (Matthew Oliver    2023-01-18 06:35:29 +1100   9)       "git-tree": "562bbf3bc1027e73456d71a10020ba984eec0eb1",
49299e0c05 versions/o-/opencv.json      (Matthew Oliver    2023-01-18 06:35:29 +1100  10)       "version": "4.7.0",
49299e0c05 versions/o-/opencv.json      (Matthew Oliver    2023-01-18 06:35:29 +1100  11)       "port-version": 0
49299e0c05 versions/o-/opencv.json      (Matthew Oliver    2023-01-18 06:35:29 +1100  12)     },
acb370dd6d versions/o-/opencv.json      (Stefano Sinigardi 2022-08-05 02:21:59 +0200  13)     {
acb370dd6d versions/o-/opencv.json      (Stefano Sinigardi 2022-08-05 02:21:59 +0200  14)       "git-tree": "135db832c720c800e2ac222994aa216df7575d17",
acb370dd6d versions/o-/opencv.json      (Stefano Sinigardi 2022-08-05 02:21:59 +0200  15)       "version": "4.6.0",
acb370dd6d versions/o-/opencv.json      (Stefano Sinigardi 2022-08-05 02:21:59 +0200  16)       "port-version": 0
acb370dd6d versions/o-/opencv.json      (Stefano Sinigardi 2022-08-05 02:21:59 +0200  17)     },
bde216bf73 versions/o-/opencv.json      (LilyWangLL        2022-06-10 11:11:05 +0800  18)     {
bde216bf73 versions/o-/opencv.json      (LilyWangLL        2022-06-10 11:11:05 +0800  19)       "git-tree": "1ed18903421ae513e731348b2e5afb13c8c38d24",
bde216bf73 versions/o-/opencv.json      (LilyWangLL        2022-06-10 11:11:05 +0800  20)       "version": "4.5.5",
bde216bf73 versions/o-/opencv.json      (LilyWangLL        2022-06-10 11:11:05 +0800  21)       "port-version": 1
bde216bf73 versions/o-/opencv.json      (LilyWangLL        2022-06-10 11:11:05 +0800  22)     },
401578455f versions/o-/opencv.json      (Stefano Sinigardi 2022-02-23 20:57:13 +0100  23)     {
401578455f versions/o-/opencv.json      (Stefano Sinigardi 2022-02-23 20:57:13 +0100  24)       "git-tree": "afe6b1b5c7be14be0656724754f95e537416c763",
401578455f versions/o-/opencv.json      (Stefano Sinigardi 2022-02-23 20:57:13 +0100  25)       "version": "4.5.5",
401578455f versions/o-/opencv.json      (Stefano Sinigardi 2022-02-23 20:57:13 +0100  26)       "port-version": 0
401578455f versions/o-/opencv.json      (Stefano Sinigardi 2022-02-23 20:57:13 +0100  27)     },

It can be seen that the latest one before the Date specified by the baseline is 4.5.5#1 updated at 2022-06-10 11:11:05 +0800:
bde216bf73 versions/o-/opencv.json      (LilyWangLL        2022-06-10 11:11:05 +0800  18)     {
bde216bf73 versions/o-/opencv.json      (LilyWangLL        2022-06-10 11:11:05 +0800  19)       "git-tree": "1ed18903421ae513e731348b2e5afb13c8c38d24",
bde216bf73 versions/o-/opencv.json      (LilyWangLL        2022-06-10 11:11:05 +0800  20)       "version": "4.5.5",
bde216bf73 versions/o-/opencv.json      (LilyWangLL        2022-06-10 11:11:05 +0800  21)       "port-version": 1
bde216bf73 versions/o-/opencv.json      (LilyWangLL        2022-06-10 11:11:05 +0800  22)     },

So when you use https://github.com/microsoft/vcpkg/commit/763f6664c1858240fdfb563c55f9c9fdc5e19ac7 the dependency opencv will download version 4.5.5#1.
Usually, it is enough to set the baseline to the latest, and the latest version in vcpkg will be downloaded.

@MonicaLiu0311 Thank you explaining that.  What I actually want to do is just pin the version of libusb at 1.0.23 while everything else uses the latest available version.  In order to set override for libusb it required me to set a baseline version.  Is there a way I can just pin libusb without limiting everything else to some version?  I tried to figure this out from the documentation but I wasn't able to.

Is there a way I can just pin libusb without limiting everything else to some version?

You only need to use overrides to specify the version of libusb, and keep the baseline up to date, just like you did above:
"overrides": [
    {
        "name": "libusb",
        "version": "1.0.23"
    }
]


add example to ModuleInfo documentation

Follow-up to the 100% correct information written by Walter, reviewed by me, and merged by Razvan in https://github.com/dlang/dlang.org/pull/3464 to demonstrate to the reader how things are supposed to work.

Force pushed with more information, to show how these modules must work with any combination of -betterC thanks to the ModuleInfo generation rules. I think this is complete now, ping @RazvanN7 @maxhaton


Craco build failing on docker

When I run the build on local it works fine but on docker, it fails.
Error: Failed to launch chrome!
I am not trying to launch chrome from my docker but on docker it's failing due to this reason.
Please ignore the deprecation warning those warnings are also coming on the local build.

The craco config file that I have used.

same to me any updates regarding this issue ?

Same to me, any updates regarding this error ?

@dilanx Could anyone please share the workable for this issue?

Are you sure this is a craco issue?
Try looking at this: https://stackoverflow.com/questions/71040681/qemu-x86-64-could-not-open-lib64-ld-linux-x86-64-so-2-no-such-file-or-direc

I had tried this earlier but changing the base image did not make any difference.

Any updates regarding this issue ?

@GauravT500 did you find any solution about this issue ?

@GauravT500 This issue not related to Craco . If i remove the html-critical-webpack-plugin then the build error resolved . You can also check the details here https://www.npmjs.com/package/html-critical-webpack-plugin

@GauravT500 This issue not related to Craco . If i remove the html-critical-webpack-plugin then the build error resolved . You can also check the details here https://www.npmjs.com/package/html-critical-webpack-plugin

@snairsumith Yes, I tried this if you want to use html-critical-webpack-plugin then you need chrome/chromium installed in the docker container.

Hi @GauravT500 are you using Ubuntu ?
I am installed chromium-browser but still getting the error


Brackets sometimes slow, sometimes fast

I have used Brackets and it slowed down suddenly one day, taking 10-20 seconds each time I make a click or type. I tried reinstalling it completely, didn't change a thing. Then suddenly, Brackets started being fast for 2 days. It has now resumed being slow.
I typically edit files with 1000's of lines of code and also have many file in one folder, I know this is not the issue since Brackets was fast for 2 days once.
I do not have any extensions at all.
What could be the issue?
(PS: I have a second question as well, how do I get Brackets to connect to the server (127.000.000 live
port) on live preview and not files://stuff/morestuff/editing? It's much faster when it's connected to the live port thing.
Thanks

Please check this post : https://github.com/adobe/brackets/issues/14515
Issue confirmed, no ETA yet

@Etchedy Could you please let us know following details :

Machine configuration
Version of Windows and windows edition.
Antivirus that is running on your machine.
Do you have any brackets extension installed.

Machine configuration

OS Name	Microsoft Windows 10 Pro
Version	10.0.17134 Build 17134
Other OS Description 	Not Available
OS Manufacturer	Microsoft Corporation
System Name	DESKTOP-QVMI9SC
System Manufacturer	LENOVO
System Model	4291HA6
System Type	x64-based PC
System SKU
Processor	Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2501 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date	LENOVO 8DET50WW (1.20 ), 7/7/2011
SMBIOS Version	2.6
Embedded Controller Version	1.09
BIOS Mode	Legacy
BaseBoard Manufacturer	LENOVO
BaseBoard Model	Not Available
BaseBoard Name	Base Board
Platform Role	Mobile
Secure Boot State	Unsupported
PCR7 Configuration	Binding Not Possible
Windows Directory	C:\WINDOWS
System Directory	C:\WINDOWS\system32
Boot Device	\Device\HarddiskVolume1
Locale	United States
Hardware Abstraction Layer	Version = "10.0.17134.285"
User Name	DESKTOP-QVMI9SC\Richard Gao
Time Zone	Eastern Daylight Time
Installed Physical Memory (RAM)	16.0 GB
Total Physical Memory	15.9 GB
Available Physical Memory	12.7 GB
Total Virtual Memory	18.3 GB
Available Virtual Memory	14.8 GB
Page File Space	2.38 GB
Page File	C:\pagefile.sys
Kernel DMA Protection	Off
Virtualization-based security	Not enabled
Device Encryption Support	Reasons for failed automatic device encryption: PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions	Yes
Hyper-V - Second Level Address Translation Extensions	Yes
Hyper-V - Virtualization Enabled in Firmware	Yes
Hyper-V - Data Execution Protection	Yes

I am running windows 10 pro with a 64 bit operating system, x64 based-processor.

I have malwarebytes and 360 total security, I don't know if 360 total security runs all the time, but I know malware bytes only does a scan per day or when I tell it to.

I have no extensions installed

Thanks

@Etchedy Thanks for sharing the information.
I am running same version of windows but not seeing any slowness.
Request you to share a video of this issue.
Also, are their any other applications running in parallel along with brackets on your machine ?

Thank you
On Sun, Dec 16, 2018 at 11:19 PM Ayush Rathi<EMAIL_ADDRESS>wrote:

Hi @Etchedy https://github.com/Etchedy @XavierCrespin
https://github.com/XavierCrespin ,
We have addressed this issue and have refreshed the windows build.
The new build can be downloaded from below location :
https://github.com/adobe/brackets/releases/download/release-1.13/Brackets.Release.1.13.msi
Please let us know if you are still experiencing any performance issues
with the new build.
Thanks and Regards
Ayush Rathi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/adobe/brackets/issues/14527#issuecomment-447718198,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnqbAbSsdMs01INIGhBHGxqQ8At0OeLRks5u5xtDgaJpZM4WWpNZ
.


segfault during ngx_proxy_wasm_ctx_lookup

Running kong/kong:nightly container (SHA kong/kong@sha256:efaa8af02211956a69fc180f6cffa1fcf64f45a44297f21c192a077087030fb9 ) with the coraza-proxy-wasm filter, I am getting a consistent segfault by triggering two proxy requests: the first one fails with cannot pause in "body_filter" phase ("on_response_body" step), the second one segfaults.
I haven't tried it with the latest ngx_wasm_module code yet; I will add more info to this issue as I gather it. No detailed repro steps at the moment since my coraza-proxy-wasm testing environment is quite tweaked at the moment.
docker-compose logs:
WARNING: Found orphan containers (kong-service-provisioner-1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
Starting kong_httpbin_1 ... done
Recreating kong_kong_1  ... done
Attaching to kong_httpbin_1, kong_kong_1
httpbin_1  | time="2023-11-30T18:10:13.5321" msg="go-httpbin listening on http://<IP_ADDRESS>:8080"
kong_1     | 2023/11/30 18:10:14 [warn] 1#0: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /var/run/kong/nginx.conf:8
kong_1     | nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /var/run/kong/nginx.conf:8
kong_1     | 2023/11/30 18:10:14 [notice] 1#0: [wasm] swapping modules: "ngx_http_headers_more_filter_module" (index: 61) and "ngx_http_wasm_filter_module" (index: 90)
kong_1     | 2023/11/30 18:10:14 [notice] 1#0: [wasm] swapping modules: "ngx_http_lua_module" (index: 60) and "ngx_wasm_core_module" (index: 88)
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: using the "epoll" event method
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: openresty/<IP_ADDRESS>
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: OS: Linux 6.2.0-37-generic
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: getrlimit(RLIMIT_NOFILE): 1048576:1048576
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker processes
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1256
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1257
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1258
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1259
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1260
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1261
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1262
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1263
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1264
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1265
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1266
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1267
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1268
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1269
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1270
kong_1     | 2023/11/30 18:10:20 [notice] 1#0: start worker process 1271
kong_1     | 2023/11/30 18:10:26 [notice] 1263#0: *1 [lua] globalpatches.lua:73: sleep(): executing a blocking 'sleep' (0.001 seconds), context: init_worker_by_lua*
kong_1     | 2023/11/30 18:10:26 [notice] 1263#0: *1 [lua] globalpatches.lua:73: sleep(): executing a blocking 'sleep' (0.002 seconds), context: init_worker_by_lua*
kong_1     | 2023/11/30 18:10:26 [notice] 1265#0: *2 [lua] init.lua:259: purge(): [DB cache] purging (local) cache, context: init_worker_by_lua*
kong_1     | 2023/11/30 18:10:26 [notice] 1265#0: *2 [lua] init.lua:259: purge(): [DB cache] purging (local) cache, context: init_worker_by_lua*
kong_1     | 2023/11/30 18:10:26 [notice] 1265#0: *2 [kong] init.lua:522 declarative config loaded from /opt/kong/kong.yaml, context: init_worker_by_lua*
kong_1     | 2023/11/30 18:10:26 [notice] 1260#0: *5 [lua] globalpatches.lua:73: sleep(): executing a blocking 'sleep' (0.001 seconds), context: init_worker_by_lua*
kong_1     | 2023/11/30 18:14:32 [crit] 1256#0: *2369 [proxy-wasm]["main" #1] /%!(EXTRA T=GET, T=HTTP/1.1), client: <IP_ADDRESS>, server: kong, request: "GET / HTTP/1.1", host: "localhost:8000"
httpbin_1  | time="2023-11-30T18:14:33.5486" status=200 method="GET" uri="/" size_bytes=11133 duration_ms=0.31 user_agent="HTTPie/2.6.0" client_ip=<IP_ADDRESS>
kong_1     | 2023/11/30 18:14:33 [error] 1256#0: *2369 [proxy-wasm]["main" #1] filter 1/1 cannot pause in "body_filter" phase ("on_response_body" step) while sending to client, client: <IP_ADDRESS>, server: kong, request: "GET / HTTP/1.1", upstream: "http://<IP_ADDRESS>:8080/", host: "localhost:8000"
kong_1     | 2023/11/30 18:14:33 [warn] 1256#0: *2369 [proxy-wasm]["main" #1] filter 1/1 failed resuming "on_response_body" step in "body_filter" phase (not yieldable) while sending to client, client: <IP_ADDRESS>, server: kong, request: "GET / HTTP/1.1", upstream: "http://<IP_ADDRESS>:8080/", host: "localhost:8000"
kong_1     | <IP_ADDRESS> - - [30/Nov/2023:18:14:33 +0000] "GET / HTTP/1.1" 200 11153 "-" "HTTPie/2.6.0"
kong_1     | 2023/11/30 18:14:35 [error] 1269#0: *310 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1259#0: *1332 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1268#0: *756 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1270#0: *1482 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1266#0: *2223 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1262#0: *1791 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1267#0: *456 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1258#0: *748 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1261#0: *1770 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1271#0: *758 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1264#0: *1478 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1257#0: *752 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1260#0: *460 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1263#0: *164 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [error] 1265#0: *18 [lua] worker.lua:266: communicate(): event worker failed: failed to receive the header bytes: closed, context: ngx.timer
kong_1     | 2023/11/30 18:14:35 [notice] 1#0: signal 17 (SIGCHLD) received from 1256
kong_1     | 2023/11/30 18:14:35 [alert] 1#0: worker process 1256 exited on signal 11 (core dumped)
kong_1     | 2023/11/30 18:14:35 [notice] 1#0: start worker process 2004
kong_1     | 2023/11/30 18:14:35 [notice] 1#0: signal 29 (SIGIO) received
kong_1     | 2023/11/30 18:14:35 [warn] 2004#0: found and cleared 1 stale readers from LMDB

Backtrace from within the container:
Program terminated with signal SIGSEGV, Segmentation fault.
#0  ngx_proxy_wasm_ctx_lookup (id=2, ictx=0x56255ad16db8)
    at /home/runner/.cache/bazel/_bazel_runner/5f5cb99aeb7e2b4db19484ea5022e949/execroot/kong/external/ngx_wasm_module/src/common/proxy_wasm/ngx_proxy_wasm.c:95
95	/home/runner/.cache/bazel/_bazel_runner/5f5cb99aeb7e2b4db19484ea5022e949/execroot/kong/external/ngx_wasm_module/src/common/proxy_wasm/ngx_proxy_wasm.c: No such file or directory.
(gdb) bt
#0  ngx_proxy_wasm_ctx_lookup (id=2, ictx=0x56255ad16db8)
    at /home/runner/.cache/bazel/_bazel_runner/5f5cb99aeb7e2b4db19484ea5022e949/execroot/kong/external/ngx_wasm_module/src/common/proxy_wasm/ngx_proxy_wasm.c:95
#1  ngx_proxy_wasm_on_start (ictx=ictx@entry=0x56255ad16db8, filter=filter@entry=0x56255ad16800, start=start@entry=0)
    at /home/runner/.cache/bazel/_bazel_runner/5f5cb99aeb7e2b4db19484ea5022e949/execroot/kong/external/ngx_wasm_module/src/common/proxy_wasm/ngx_proxy_wasm.c:1507
#2  0x00007f09b78d8356 in ngx_proxy_wasm_run_step (pwexec=pwexec@entry=0x56255ad13fe8,
    ictx=ictx@entry=0x56255ad16db8, step=step@entry=NGX_PROXY_WASM_STEP_REQ_HEADERS)
    at /home/runner/.cache/bazel/_bazel_runner/5f5cb99aeb7e2b4db19484ea5022e949/execroot/kong/external/ngx_wasm_module/src/common/proxy_wasm/ngx_proxy_wasm.c:660
#3  0x00007f09b78d8a86 in ngx_proxy_wasm_resume (pwctx=0x56255b4b7500, phase=<optimized out>,
    step=NGX_PROXY_WASM_STEP_REQ_HEADERS)
    at /home/runner/.cache/bazel/_bazel_runner/5f5cb99aeb7e2b4db19484ea5022e949/execroot/kong/external/ngx_wasm_module/src/common/proxy_wasm/ngx_proxy_wasm.c:785
#4  0x00007f09b78d035b in ngx_wasm_ops_resume (ctx=0x56255b1a9448, phaseidx=<optimized out>)
    at /home/runner/.cache/bazel/_bazel_runner/5f5cb99aeb7e2b4db19484ea5022e949/execroot/kong/external/ngx_wasm_module/src/wasm/ngx_wasm_ops.c:293
#5  0x00007f09b78e1d02 in ngx_http_wasm_ffi_start (r=0x56255b763020)
    at /home/runner/.cache/bazel/_bazel_runner/5f5cb99aeb7e2b4db19484ea5022e949/execroot/kong/external/ngx_wasm_module/src/common/lua/ngx_wasm_lua_ffi.c:164
#6  0x00007f09b92d1f89 in lj_vm_ffi_call () at buildvm_x86.dasc:2704
#7  0x00007f09b931fbe4 in lj_ccall_func (L=<optimized out>, cd=<optimized out>) at lj_ccall.c:1382
#8  0x00007f09b9337435 in lj_cf_ffi_meta___call (L=0x7f09a1b69290) at lib_ffi.c:230
#9  0x00007f09b92cfb3b in lj_BC_FUNCC () at buildvm_x86.dasc:859
#10 0x0000562558276146 in ngx_http_lua_run_thread (L=L@entry=0x7f09b7597380, r=r@entry=0x56255b763020,
    ctx=ctx@entry=0x56255b763d78, nrets=<optimized out>, nrets@entry=0)
    at ../ngx_lua-0.10.25/src/ngx_http_lua_util.c:1184
#11 0x000056255827c2bb in ngx_http_lua_access_by_chunk (L=0x7f09b7597380, r=0x56255b763020)
    at ../ngx_lua-0.10.25/src/ngx_http_lua_accessby.c:337
#12 0x00005625581e08d1 in ngx_http_core_access_phase (r=0x56255b763020, ph=0x5625598bf678)
    at src/http/ngx_http_core_module.c:1110
#13 0x00005625581dbfcd in ngx_http_core_run_phases (r=0x56255b763020) at src/http/ngx_http_core_module.c:885
#14 0x00005625581e7917 in ngx_http_process_request_headers (rev=rev@entry=0x56255a8fb230)
    at src/http/ngx_http_request.c:1498
#15 0x00005625581e7d39 in ngx_http_process_request_line (rev=0x56255a8fb230) at src/http/ngx_http_request.c:1165
#16 0x00005625581cdf0f in ngx_epoll_process_events (cycle=<optimized out>, timer=<optimized out>,
    flags=<optimized out>) at src/event/modules/ngx_epoll_module.c:901
#17 0x00005625581c3d0a in ngx_process_events_and_timers (cycle=cycle@entry=0x56255895bac0)
    at src/event/ngx_event.c:257
#18 0x00005625581cbcfe in ngx_worker_process_cycle (cycle=cycle@entry=0x56255895bac0, data=data@entry=0x0)
    at src/os/unix/ngx_process_cycle.c:793
#19 0x00005625581ca08f in ngx_spawn_process (cycle=cycle@entry=0x56255895bac0,
    proc=proc@entry=0x5625581cbc80 <ngx_worker_process_cycle>, data=data@entry=0x0,
    name=name@entry=0x5625582f7d5c "worker process", respawn=respawn@entry=-3) at src/os/unix/ngx_process.c:199
#20 0x00005625581cb390 in ngx_start_worker_processes (cycle=cycle@entry=0x56255895bac0, n=16, type=type@entry=-3)
    at src/os/unix/ngx_process_cycle.c:382
#21 0x00005625581cc754 in ngx_master_process_cycle (cycle=0x56255895bac0) at src/os/unix/ngx_process_cycle.c:135
#22 0x00005625581a15ee in main (argc=<optimized out>, argv=<optimized out>) at src/core/nginx.c:386

It is highly likely this is one of the segfaults fixed by ecd78968469ed5fa40d81a26600964535d3e6b00 or 34c23c604198725fed022fa7c5db023dcee89f2c.


Can't add packages to use for custom components

Bug Description
I'm trying to make an azure ai search component but langflow doesn't come with the azure-search-documents package.
I've tried to put the following in my Dockerfile:
FROM langflowai/langflow:1.0.19
COPY ./custom_components/components langflow/components
RUN pip install azure-search-documents
CMD ["langflow", "run"]

But it still throws the error
ModuleNotFoundError: Module
                             azure.search.documents not
                             found. Please install it
                             and try again

Is this something that would be possible to do or would I need another approach?
Reproduction
Use the above dockerfile.
Expected behavior
Installed the azure-search-documents package.
Who can help?
@ogabrielluiz
Operating System
MacOS
Langflow Version
1.0.19
Python Version
3.12
Screenshot
No response
Flow File
No response

I had to install packages like this:
RUN python3 -m venv /app/.venv &&
/bin/bash -c "source /app/.venv/bin/activate && pip install -U langchain-huggingface mysql-connector-python langchain pydantic"
to ensure they were available in the venv


I have a problem with my Flutter application.

Steps to Reproduce

Execute flutter run on the code sample
...
...

Expected results:
Actual results:

Code sample

Logs

You need to actually fill out the issue template if you want folks to help you.


There is a question about the calculation of LOSS in SOT training

I found that the mask of ctr loss is a non-background area in any case. But in my opinion, if it is a neg pair, there is no need to calculate the ctr loss of the non-background area.
What do you think?

@TCBocean the area where is not in the box will be set to 0 in this line https://github.com/MegviiDetection/video_analyst/blob/4c5e03a8f8e98aeb917432f18ede706935c6ac47/videoanalyst/data/target/target_impl/utils/make_densebox_target.py#L134

@lzx1413
Yes, when creating the center label, the background area (the area outside the bounding box of the target) is set to 0, while the foreground area (the area within the bounding box of the target) will be greater than 0. When calculating the loss , Only the part of the center label that is not equal to 0 is calculated.
For the neg pair, it will also have a bounding box, so its center label will also have a part that is not equal to 0, and this part is also counted as center loss.
And I think that for the label of the center of the neg pair, there should be no response (should be all 0s) at the target, which is more in line with my understanding.
Or is there something in the code that I missed?

@TCBocean  You are right, the ctr should set to zero while in neg pairs.


[release-1.25] 16k kernel page builds to support Apple Silicon (ARM64)

Backport #7335

Closing per this comment and approval from MGMT
https://github.com/k3s-io/k3s/issues/7335#issuecomment-1529916982


Storage disk still lists capacity when empty

Hi there,
I emptied all of my 4k and 16k disks manually to move onto 64k disks. (Manually because there's no disk manipulator yet ;))
I found that the disks still show storage, but I cannot see any items in the grid. Assuming this is a bug, but I cannot break these disks down to components unless they are empty.

Maybe a hard Q to answer, but since which version do you have that storage disk approximately?

I would say the server has been running for about 3 weeks now. We use Spilled Juice mod pack from AT Launcher. We started with 0.8.5 and are now on 0.8.12.
Hope this helps!

Gonna close this as this is probably related to #227


Updated link to InfluxDB Docs to use the latest

This link was pointing to a specific version of the InfluxDB docs. This change would always point the link to the latest version of the docs.
fyi @brian-brazil

Can you add the DCO please?
You've got a stray double quote in the warning at the top of the linked doc.

I'll fix the DCO, but what do you mean re: "...stray double quote in the warning at the top of the linked doc."?

https://docs.influxdata.com/influxdb/v1.6/supported_protocols/prometheus reads
Note: The Prometheus API Stability Guarantees states that remote read and remote write endpoints are features listed as experimental or subject to change, and thus considered unstable for 2.x”. Any breaking changes will be included in the InfluxDB release notes.

ah thanks!

Thanks!


LDS Standards - Empty State

When you add the IndicatorList (CMDT) to the page, and there are no Indicator Bundles set up yet, the component should show an Empty State illustration on the lightning page and on the record page when it is displayed. Also see #44 and #81

This was split from #44

Note to future self - display an empty state image when bundle dev name is not assigned (value = null).

This should be available now.  May need some padding around the image, but the functionality is present.


v1.6 docs release endgame

v1.5 Branch - use this for reference: https://github.com/dapr/docs/pull/1925/files
@msfussell @hhunter-ms @greenie-msft
In pending PR:

[ ] Add v1.6 (latest) to nav bar
[ ] Archive notice
[ ] Update root README.md
[ ] Update URL in config.toml
[ ] Delete workflow file

Day of:

[ ] Push v1.5 PR

v1.6 Branch - use this for reference: https://github.com/dapr/docs/pull/1926/files
@msfussell @hhunter-ms @greenie-msft
In a pending PR:

[ ] Update README.md
[ ] Update version dropdown in nav bar
[ ] Supported versions section
[ ] All output logs change 1.5 to 1.6
[ ] Update URL in config.toml
[ ] Update workflow for docs.dapr.io to v1.6 branch
[ ] Update quickstart page links to the latest release branch (requires quickstarts to cut a release branch)

Day of:

[ ] Push v1.6 PR

GitHub - After release
@greenie-msft

[ ] Make v1.6 the default branch
[ ] One last upmerge

Website

[x] Create new website for v1.7, v1.8, v1.9 - @willtsai + @greenie-msft
[ ] Add DNS entry for new website - @greenie-msft  to ask CNCF to create this. Let's as for v1-7.docs, v1-8.docs, v1-9.docs.
[ ] Add custom domain & generate SSL certificate - Needs to happen after the DNS entry is created - @willtsai + @greenie-msft

v1.7 Branch
@msfussell @hhunter-ms @greenie-msft

[ ] Create v1.7 branch
[ ]  Update website workflow file
[ ]  Upmerge from release branch to preview branch

Release announcements

[ ] Release notes/blog  - @paulyuk
[ ] Tweet release announcement - @greenie-msft
[ ] Discord release announcement - @greenie-msft

Update - I've submitted a Zendesk ticket asking for creation of the new DNS entries for the next three docs releases - v1.7, v1.8, v1.9

Websites have been created and DNS configured correctly for:
https://v1-7.docs.dapr.io
https://v1-8.docs.dapr.io
https://v1-9.docs.dapr.io

v1.5 Branch - Merge day of release: https://github.com/dapr/docs/pull/2123

Resolved


Some questions about "Full-Spectrum Out-of-Distribution Detection“

Hello, I've noticed your recent publication on the paper titled "Full-Spectrum Out-of-Distribution Detection", and it has greatly inspired me.
However, I couldn't find relevant pretraining weights for COVID. Additionally, I observed that the FS-OOD detection introduced in openood v1.5 did not utilize the benchmarks proposed in the mentioned paper, but instead, it was tested on imagenet200 and imagenet-1k. I'm curious about the reasoning behind this choice.

Thank you


How does teams manage blocked users?

Would be good if the page described how people are removed from the team.  We blocked a user while they were on holiday, and they got removed from the team.  When they unblocked them today, they did not automatically get added back into the team.

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

ID: 8c674715-5bd3-7e2c-6689-7ce636be53bc
Version Independent ID: 0b3649a2-cf33-346d-86dc-c1a984c67502
Content: Create an org-wide team
Content Source: microsoft-365/business-video/org-wide-team.md
Service: o365-administration
GitHub Login: @twernermsft
Microsoft Alias: twerner

@BrianLeFlem Thank you for your feedback. Are you referring to Blocking the users on teams or on the M365 admin center?
Thanks
Sri

M365 Admin Center.  Cheers

@BrianLeFlem Thank you for the response. I tested it and don't see the users getting removed from MS teams when they are blocked.
Blocking someone prevents anyone from signing in as this user, and is a good idea when you think their password or username may have been compromised. When you block someone, it immediately stops any new sign-ins for that account, and if they’re signed in, they’ll be automatically signed out from all Microsoft services within 60 minutes.
This won't stop the account from receiving mail or remove them from Microsoft teams. However, If you find the accounts getting removed when blocked, please reach out to Microsoft support via the need help button to resolve the issue.
Hope this helps!
Thanks
Sri

@msbemba  Thank you very much for the contribution and sharing this explanation. @BrianLeFlem Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed to close it as here we are limited to documentation fixes and improvements only.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Not Checking if .config Dir Exists

Seems like warpd is not checking if the .config directory exists which leads to "flock open: No such file or directory" on running warpd without a ${HOME}/.config (relevant code seems to be  here). You may want to also consider implementing the XDG spec in warpd which would allow specifying the location of an alternative .config dir.

Thanks. I believe this should be fixed.

You are indeed correct, that was my original intention. I have fixed this in the latest commit, thanks for catching this.

Oops. Third time is the charm :P.

the lockfile should be put in XDG_RUNTIME_DIR ("standard" name could be
warpd.lock) or, if it doesn't exist, in a directory with "similar capabilities"
(/tmp/warpd/lock would be a good candidate) upon issuing a warning.

I prefer storing state in one location. XDG_RUNTIME_DIR may not be set on all systems.

I would have loved to get this boring chore off your shoulders but after trying
for half an hour succumbed to my lack of C programming skills.

<3

Also, I don't see any need to create a config path.
...
Warpd should exit, however, if HOME is not set (as do most standard tools like cd).

Creating the parent directories seems like sane default behaviour. It makes it easier for the user to discover the path. There is some precedent for this, since several programs in the wild do this (e.g kitty).

I agree with storing state in one location but looking at the most recent commit
...
Many people have special backup policies for ~/.config, (personally, I don't want to
backup any logfiles on my laptop at all),

Fair point. I hail from a time when men were men and dotfiles were dotfiles.  ~/.config/warpd began life as ~/.warpd before I cargo culted the (sporadically supported) XDG style.
I've eliminated the log file altogether (issues can still be debugged with -f) and moved the lock file to /tmp.

On the other hand, an empty directory doesn't hurt anybody (at least not that much).

+1
I'm inclined to keep this behaviour.


strip_video_id_from_url doesn't trim time delimiters

Ex: 'https://youtube.com/8qi8ixn6-Vo#t=1397' returns '8qi8ixn6-Vo#t=1397'

Ok we can split on '#', and take the first element

👍 will you do that or should I?


Download my data

An option for a user to download all data we have about him. Exposed in the settings menu. The format needs to be human readable (json for now, unless otherwise noticed later).

We will need to provide all info about the user which can be somehow linked to him (all orgs, invitations to orgs, sms logs, ...)

I don't think invitations to orgs and sms logs are part of data articulated by gdpr, as the main purpose for the download account data functionality is to enable users to pack up their data in a machine readable format and leave to use other service, so I don't see a use of sms logs, invitations, etc....

I discussed this with Pierre this morning. Since a user itself needs to be able to inspect all of its personal data, and personal data included everything which can be linked to a user, this will need to be included. We  can for example link a phone number to a user, and we can link an sms log entry to the phone number and therefore to the user

The data portability is related to only the data which the user himself/herself provided us
https://gdpr-info.eu/art-20-gdpr/
For example: if you tried to download your account from Google or Facebook, you won't be able to download the two factor authentication sms logs for example, as this isn't the kind of data meant by GDPR


[Doc] minor edits to streamLoad and modify shortDesc in exportOverview in 2.2

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

starrocks_be_unittest succeeded.

starrocks_be_unittest succeeded.


Error: x the name ... is defined multiple times

react-query-swagger generating multiple functions with the same name but different signatures. Here's one example:

node: v20.10.0
next: v13.5.6
react-query-swagger: v15.11.0 (used with /use-recommended-configuration /template:fetch args)

Resolved after adding the /operationGenerationMode:MultipleClientsFromFirstTagAndOperationId arg


Supporting eu-west-1 in the empire build

I've done the work locally to support eu-west-1 for the stacker empire build but that involved reducing the number of AZs from 4 to 3 (as eu-west-1 only has 3).
I'd like to give the updates back to you, but is there a way to add conditional logic into the conf/empire/empire.yaml file to allow 4 everywhere but in eu-west-1?

So this is a problem for multiple regions - us-west-1 in my account, for example, only has 2 subnettable zones.
The AZCount thing has always been a little hacky, which was why we ended up adding the local parameters feature: https://github.com/remind101/stacker/pull/61
Let me think about this a bit.  I have code that can figure out how many subnettable zones are available in a given region, but I really need to figure out where the right place for that would be.  Also, we probably want to leave it configurable, so people can choose less zones than the max.
I'll try to come up with something today.

Maybe a way of saying 'up to 3'? Something like "^5"?
Sent from my iPhone

On 17 Aug 2015, at 21:27, Michael Barrett<EMAIL_ADDRESS>wrote:
So this is a problem for multiple regions - us-west-1 in my account, for example, only has 2 subnettable zones.
The AZCount thing has always been a little hacky, which was why we ended up adding the local parameters feature: #61
Let me think about this a bit. I have code that can figure out how many subnettable zones are available in a given region, but I really need to figure out where the right place for that would be. Also, we probably want to leave it configurable, so people can choose less zones than the max.
I'll try to come up with something today.
—
Reply to this email directly or view it on GitHub.

So I can't think of a great way to do this 'automatically' with the way things currently are- the blueprint is where the logic happens that uses the AZCount, and the blueprint (purposefully) doesn't have access to the provider.
At this point I think it's best to make AZCount a variable inside the environment file, default it to 2, and leave a comment with detailed instructions about updating it to higher values (no more than 4, and no more than your individual region can handle).  Also probably worth saying something like "We suggest, in a production environment, that you increase this to as many as you possibly can for the most redundancy."
Does that seem like a decent enough workaround, @gileze33 ?

Sounds like a very good work around. I was tempted to submit a PR with it set to 3 but wasn't sure how you guys would react :)
Sent from my iPhone

On 19 Aug 2015, at 18:51, Michael Barrett<EMAIL_ADDRESS>wrote:
So I can't think of a great way to do this 'automatically' with the way things currently are- the blueprint is where the logic happens that uses the AZCount, and the blueprint (purposefully) doesn't have access to the provider.
At this point I think it's best to make AZCount a variable inside the environment file, default it to 2, and leave a comment with detailed instructions about updating it to higher values (no more than 4, and no more than your individual region can handle). Also probably worth saying something like "We suggest, in a production environment, that you increase this to as many as you possibly can for the most redundancy."
Does that seem like a decent enough workaround, @gileze33 ?
—
Reply to this email directly or view it on GitHub.

https://github.com/remind101/stacker/pull/82 - let me know if the wording isn't clear enough, or if you think there's something I missed.  I'm not closing this, because in order to get eu-west-1 in there we need to finish the empire_ami stuff, but I think we're getting close!

Hey @gileze33 - I've started copying the empire_ami to eu-west-1 with this update: https://github.com/remind101/empire_ami/pull/13
Was there any other work, other than the change to the # of AZs in the stacker empire config, that you needed to make empire work in eu-west-1?  If not, I'll be updating the stacker config with the eu-west-1 AMI.  Thanks!

Here's the diff from my changes:
diff --git a/conf/empire/empire.yaml b/conf/empire/empire.yaml
index b958381..65d133a 100644
--- a/conf/empire/empire.yaml
+++ b/conf/empire/empire.yaml
@@ -48,6 +48,10 @@ mappings:
NAT: ami-2dae821d
ubuntu1404: ami-f15b5dc1
empire: ami-85ede7b5

eu-west-1:

 NAT: ami-ef76e898

 ubuntu1404: ami-47a23a30

 empire: ami-984c13ef

Many stacks need these settings, or a subset of them, from the VPC -
this makes it easy to pass them around. Stacker will drop unused Parameters
@@ -76,10 +80,10 @@ stacks:
#       Also you need at least 2 AZs in order to use the DB because
#       of the fact that the DB blueprint uses MultiAZ
# Note: You will create a NAT instance PER Availability zone.

 AZCount: 4

 AZCount: 3
 # Enough subnets for 4 AZs

 PublicSubnets: <IP_ADDRESS>/24,<IP_ADDRESS>/24,<IP_ADDRESS>/24,<IP_ADDRESS>/24

 PrivateSubnets: <IP_ADDRESS>/22,<IP_ADDRESS>/22,<IP_ADDRESS>/22,<IP_ADDRESS>/22

 PublicSubnets: <IP_ADDRESS>/24,<IP_ADDRESS>/24,<IP_ADDRESS>/24

 PrivateSubnets: <IP_ADDRESS>/22,<IP_ADDRESS>/22,<IP_ADDRESS>/22
 # InstanceType used for NAT instances
 InstanceType: ${nat_instance_type}
 SshKeyName: ${ssh_key_name}

Cool - I made some updates here with the new AMI:
https://github.com/remind101/stacker/pull/116
Let me know if that looks ok to you.

OK, I think #116 should cover it - I'm going to go ahead and close this.  If you have issues with ti, let me know.


Please provide a good Api doc with good explanation

This does not provide any information on how to use the api , only few api are self explanatory (which  is dangerous - not exactly sure with it does only assumption)

please  provide the same structure as this image blow

This thread has been closed since there has not been any recent activity. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.


Build issues with 0.71 RNSha256 XCode 15.3

Description
Incompatible function pointer types sending 'unsigned char *(const void *, CC_LONG, unsigned char *)' (aka 'unsigned char *(const void *, unsigned int, unsigned char )') to parameter of type 'DIGEST_FUNCTION' (aka 'unsigned char ()(const void *, unsigned int, unsigned char *)')
Steps to reproduce
n/a
React Native Version
0.71.0
Affected Platforms
Runtime - iOS
Output of npx react-native info
info Fetching system and libraries information...
System:
    OS: macOS 14.4.1
    CPU: (12) arm64 Apple M2 Max
    Memory: 487.86 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
    Yarn: 1.22.21 - /opt/homebrew/bin/yarn
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.15.2 - /Users/eugene/.gem/ruby/2.7.6/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 23.4, iOS 17.4, macOS 14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4
    Android SDK: Not Found
  IDEs:
    Android Studio: 2023.1 AI-231.9392.1.2311.11076708
    Xcode: 15.3/15E204a - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.22 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: Not Found
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Stacktrace or Logs
n/a

Reproducer
n/a
Screenshots and Videos

@xgenem Please provide a valid reproducer

Fixed at https://github.com/itinance/react-native-sha256/issues/70


[Bug]: Slider range selection: second SliderThumb missing

Reproduction
https://stackblitz.com/edit/v9flpn?file=src%2FApp.vue
Describe the bug
Building on the the example code given for Slider, if we have an array for the model value, e.g. const modelValue = ref([12,60]) with v-model="modelValue", a range shows up, which can be dragged on both ends, but there is no SliderThumb present.

System Info
(note: I ran this on StackBlitz)

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.3 - /usr/local/bin/pnpm
  npmPackages:
    radix-vue: ^1.5.3 => 1.5.3
    shadcn-vue: latest => 0.10.2
    vue: latest => 3.4.21

Contributes

[ ] I am willing to submit a PR to fix this issue
[ ] I am willing to submit a PR with failing tests

In order to show the 2nd thumb, you need to add another SliderThumb.  https://stackblitz.com/edit/v9flpn-aotck7?file=src%2Fcomponents%2Fui%2Fslider%2FSlider.vue


Document suggested region names per cloud provider as best practice

In terms of implementing a client that understands this extension, it's great that storage:platform is an enum, but unfortunate that storage:region is any string. I agree the regions from each platform are too many and can change too frequently to encode in the JSON Schema an enum restriction, but it would be great if we could have a "Best Practices" section of the extension documentation that lists suggested string values for each platform.
For example, regions in AWS could be described either as us-west-2 or US West (Oregon), and right now there's no section that recommends the former. It would be great if we could explicitly suggest the former, with a link to a web document or CLI command with the most updated list of available names. For example in AWS that could be
> aws ec2 describe-regions --all-regions | jq '.Regions[].RegionName'
"af-south-1"
"eu-north-1"
"ap-south-1"
"eu-west-3"
"eu-west-2"
"eu-south-1"
"eu-west-1"
"ap-northeast-3"
"ap-northeast-2"
"me-south-1"
"ap-northeast-1"
"sa-east-1"
"ca-central-1"
"ap-east-1"
"ap-southeast-1"
"ap-southeast-2"
"eu-central-1"
"us-east-1"
"us-east-2"
"us-west-1"
"us-west-2"

Excellent point.  I do wish we could make it an Enum, but as you said between different regions and keeping up to date it's problematic.
I think the best approach here would be to have a Best Practices section on each Provider in the README that can state what the valid regions are (or how to get them), what to use as a URL protocol (e.g., gs for google storage, s3, etc.) and other important notes (e.g., Azure doesn't have requester pays).
This doesn't change anything in the spec so we're free to update the README anytime without having to issue a new version.

I believe we should split this extension into a generic storage extension and a couple of sub-extensions that are provider dependent and each provider can suggest a platform name and allowed values for the different generic fields. That makes it a bit simpler to manage everything, I hope.

I think we can't ever solve this issue here. Even if we add an AWS extension that is based on this extension and adds an enum for the region on top, is this really good? AWS adds regions all the time and the extension would like always be outdated once AWS changes something. So I'm tempted to close this issue. Thoughts @kylebarron ?

In #24 this could be listed per provider in the respective provider documents/best practices.