Gherkin: Remove Background from Rule in grammar

Summary
Based on conversation at Cukenfest, we will take out Background from Rules and see if valid use cases emerge
Expected Behavior
This will become a parse error:
Feature: My Feature
    Rule: My Rule
        Background: My background

Current Behavior
Currently backgrounds are inlined into the pickles created from the Scenarios

I had a crack at this (removed Background? from the Feature rule).
Because of the way Berp works, a rule with a background does not cause a parser error. It just generates a Rule AST node with description     Background:\n      Given rb.
The Berp parser will only attempt to match lines it expects. Everything else becomes a description. I think parser is unable to detect quite a lot of parse errors. /cc @gasparnagy

Hi. I came here as I was trying to understand whether Gherkin AST produces Rule objects or not. I know that it was introduced as of Gherkin 6, but the AST picture on the start page of this GitHub project does not yet mention Rule in it. So, it is supported yet?

@ttutisani It is supported, but the docs have not been updated yet, I guess, but please create a separate issue for this.

@aslakhellesoy I see. It was definitely by design like that, but we can question whether this was really a good choice (I am not sure anymore.) I think besides "Background" and maybe "Feature" all the other keywords can be used pretty much everywhere, so the impact of this behavior is not that high.
If you write "Background" after a "Rule" and start with the first "Given" step, it will anyway cause a synxtax error (if we don't allow backgrounds for rules), because at that point only "Scenario" or another "Rule" can come, so there will be no hidden error caused by that.
I would go ahead removing the Background for the Rule and maybe have another separate discussion about how the parser should treat the "other" token. We can easily change BERP (if we want) to check every other token and only accept "Other" if no other token is matching. This will not require any change in the language implementations.

That sounds like a good plan @gasparnagy - good to hear berp can be easily changed.

IIRC the rationale for not allowing Background in Rule was that it would provide too much rope for people to hang themselves with. It would be easy to create a mess that's hard to reason about, and we want to avoid that.

I would suggest to keep Background inside Rule's as it provides a very good solution for having separate/multiple Background keywords inside one feature file.

Looking at it from a structural/utility perspective:

Backgrounds are a convenience/clarity mechanism that accomplish this by allowing for less repetition of steps in scenarios.
Rules are a convenience/scoping mechanism that accomplish this by demarcating groups of scenarios into organized, related groups.

Their purposes don't seem to conflict at all and their combined effects could still flow in a straightforward and behaviorally understandable manner of  Before hook execution -> Feature level background execution -> Rule level background execution -> Scenario execution, even if doing so does increase the overall mechanical complexity of the Cucumber framework.

IIRC the rationale for not allowing Background in Rule was that it would provide too much rope for people to hang themselves with. It would be easy to create a mess that's hard to reason about, and we want to avoid that.

While I do contend that it would not be hard to reason about (at least, no more so than any other aspect of Gherkin) unless used in a very bad manner, I can't argue that such very bad usages would not be a likely outcome. That being said, as a user I do like rope and I do like having power and, if some user does end up metaphorically hanging themselves with all of that rope then that is what I would call an 'educational experience'. Call me selfish but I've never been a fan of taking toys away from everyone just because some people don't know how to play nice with them.

Call me selfish but I've never been a fan of taking toys away from everyone just because some people don't know how to play nice with them.

@enkessler I absolutely understand you and I was thinking in the same way before I got  experience with OSS projects that are used by so many people. It was a vivid discussion with many pro and con arguments. Finally we decided this way, with the comment that we might reconsider adding the background support for rules (also maybe tagging) later, once we got more experience about how people use/like the rule structure. We have also somehow realized that making such decisions is better in a live gathering... you should definitely join the next years CukenFest!

@gasparnagy Unfortunately, CukenFest tends to be either geographically or temporally distant to me and so attending such an event necessitates a non-trivial cost in travel expenses, lost work income, or both. Lacking luxuries like vacation days or company sponsorship, I try to minimize event attendance. Even with this past CukenFest being a virtual event, I was not able to attend all of it.

we might reconsider adding the background support for rules (also maybe tagging) later, once we got more experience about how people use/like the rule structure

The lack of any implementation example of Rule is the primary reason that I hadn't yet gotten around to modeling that keyword in cuke_modeler, despite its existence since Gherkin 6 or so. With the release of Cucumber 4 (Ruby), however, I can now see it in action and that is what got me to looking into finally modeling the Rule keyword and what ultimately led me to this issue thread.
At this point in time, I am able to simultaneously use backgrounds at both the feature level and the rule level and it works exactly as I expected. I plan to use this rope to make a perfectly safe tire swing until such time as a newer release comes along to take away my fun. ;)

continues to swing on his excess rope enabled tire swing while pondering the implications of having all language platforms' behavior being dictated by the lowest common denominator of language platform aggreement

I had a crack at this (removed Background? from the Rule grammar rule).
Because of the way Berp works, a rule with a background does not cause a parser error. It just generates a Rule AST node with description  Background:\n Given rb.
The Berp parser will only attempt to match lines it expects. Everything else becomes a description. I think parser is unable to detect quite a lot of parse errors. /cc @gasparnagy

I think the easiest way to implement this is to allow Background after Rule in the parser, but throw an exception in the AST builder.

Hmmm, I find it quite useful, and use it fairly regularly - if background makes sense for a feature as a whole, why could it not make sense at a rule level, when a rule has several examples associated with it?

@wakaleo There's an anti-Background sentiment in some quarters anyhow (see Seb and Gaspar's last book) so extending it to Rules could be seen as making things worse

Hmm. it's my understanding that versions of Cucumber have been released with the Rule keyword supporting Background, right? If that's the case, then isn't removing Background from Rule just as invasive as removing Background altogether?
I mean to ask: what alternative do we offer those who already invested in either Background heavily? Either because they shot themselves in the foot or because they genuinely had a good reason to use the Background abstraction?

Hmm. it's my understanding that versions of Cucumber have been released with the Rule keyword supporting Background, right? If that's the case, then isn't removing Background from Rule just as invasive as removing Background altogether?

Ok. So, I just figured out that the Rule keyword got the Background since its inception (Gherkin v6.0). Gherkin 6 was released in 2018 (or at least the merge did). I'd argue that it's simply too late to remove the background from the Rule keyword. @gasparnagy provides the perfect reason in his original comment explaining why he thinks it shouldn't have been added in the first place:

with OSS projects that are used by so many people.

We have had backgrounds in rules for a while now.
While we speak of being opinionated, we, its creators clearly thought it was not important to fix the parser. In fact, we even removed the experimental warning from the documentation! If we are opinionated, we are also wishy washy in what our opinion is!
And that is a problem. And we should probably have a discussion about how we got here in the first place.
But form a practical point of view:

Removing background rules will have significant user impact.
Backgrounds rules are hidden from the rest of Cucumber through pickles. So the complexity of keeping background rules is contained.
Removing background rules will require a deprecation process that spans two major versions of each Cucumber implementation. One to deprecate, one to remove. This will take a significant amount of time and work to coordinate.

So if given the choice between keeping things as is, breaking background rules abruptly or deprecating them I'd say that leaving things as is is the least amount of effort.

The SpecFlow team doesn't want to implement it

@gasparnagy could you elaborate on the why here. We haven't really discussed the reasons and motivations here.

There are many good arguments made here for keeping it. Another way to address this is through documentation - make it loud and clear that using backgrounds in rules is supported, but potentially a bad idea. I think removing it would be akin to adding a limit of max 1000 lines for a source file - a bit patronising.

In terms of the backwards compatibility worries, I know the parser allows them but has there been any user-facing documentation mentioning/encouraging Backgrounds in Rules? If it was never documented as working then arguably it's a bug fix :)

@ciaranmcnulty whoops https://github.com/cucumber/docs/pull/440

In terms of the backwards compatibility worries, I know the parser allows them but has there been any user-facing documentation mentioning/encouraging Backgrounds in Rules? If it was never documented as working then arguably it's a bug fix :)

I believe I mention it in BDD in Action (2nd Edition) if that counts as user-facing documentation.

The SpecFlow team doesn't want to implement it

@gasparnagy could you elaborate on the why here. We haven't really discussed the reasons and motivations here.

This is nothing that @gasparnagy said @mpkorstanje. That was me and the rest of the SpecFlow team at Tricentis.
Our motivation was the following: The support for Rules isn't complete in SpecFlow and all our tools. We want to tackle this finally. And so the topic of Background in Rules popped up for us because it is one thing that we don't support yet.
For me the decision we did 2019 (or was is 2018) that we will remove the Background of Rules is still the last decision about this topic and was validated last Thursday again.
So in our case, we also need now to do less to support Rules completely.
That was our motivation. Only do the work that is really needed.
But if we say, it is now too late to remove the Background. This is also fine for us. Then we will implement it in SpecFlow. We just didn't want to implement something, when we said we will remove it, and is afaik not been implemented in every implementation yet.
We just need now a final decision on what we do with the Background in Rules.

I share the opinion of @mpkorstanje
I think that if this is there since the beginning of rules, and it has been at some point documented - even if asked to avoid it - we can not assume that user do not have background for their rules.
And if we remove it, we will certainly have plenty of requests to get it back.

To put it into perspective, here is an example where multiple backgrounds and rules are useful (Admittedly only one use case).
I also have examples with Backgrounds at the top level and then rule/background. I think since 2018 when we were debating it and 2019 when we accepted it, I've started to find more and more use-cases where it's useful. For me it needs to stay.
If some languages don't want to implement it, I say that's ok. But iirc what @SabotageAndi is saying is true. In 2018 rules were quite new and we were struggling with implementing them. Now they're common place let's implement them wholly >??
Feature: Advice feedback

  As a ...
  I want to ....
  So that I ....

  Rule: Rule1
    Background:
      Given I am logged in
      And I am on ....

    Scenario: User can give feedback
      Then I am able to provide feedback

    Scenario: User giving positive feedback
      When I inform ...
      Then I am thanked for providing feedback

    Scenario: User giving detailed free-text negative feedback
      When I inform ....
      And I offer a typed reason for why the advice was not useful
      Then I am thanked for providing feedback

  Rule: Rule2
    Background:
      Given I am on ....

    Scenario: User can give feedback
      Then I am able to provide feedback

    Scenario: User giving positive feedback
      When I inform ...
      Then I am thanked for providing feedback

    Scenario: User giving detailed free-text negative feedback
      When I inform ....
      And I offer a typed reason for why the advice was not useful
      Then I am thanked for providing feedback

    Scenario: User giving detailed negative feedback with a specific reason
      When I inform ...
      And I select a reason that the advice was not useful
      Then I am thanked for providing feedback

    Scenario: User changing their mind about feedback
      When I inform ....
      And I change my mind about giving feedback
      Then I am able to provide feedback

Yes, it seems to be too late to have a discussion about the usefulness of this as it is already there... It is sad though that we made an agreement by considering pro and con arguments, but finally we (including myself, no blaming here) haven't taken care of applying it and finally the power of status quo have overtaken our arguments.
Now everyone thinks over the usefulness of this feature and certainly will find use cases where it is useful. But (and I am just repeating myself), the question is not whether it is useful for you, but whether the complexity and confusion it introduces is overweighted by the benefits for the thousands of the other users. I meet everyday cucumber/specflow users on my courses: 2/3 of them thinks that background executes only once before all scenarios run. These people get a feature file (the ubiquitous language) to review. They will not check the documentation of Gherkin, because they think they understand the background (a nice example of "unknown unknown").
As I said, it is too late for the rule backgrounds now (and probably not that important anyway), but I just wanted to highlight that we have to make different considerations when we change Gherkin than any other parts of cucumber. I think I could also find good use cases where I could safely use variables, loops or conditional steps in Gherkin, but that is not the point here.

During the weekly update meeting just a minute ago, we confirmed @gasparnagy 's wording followed by the decision to close this issue without further action. Use of backgrounds remains discouraged, but removal is - due to the time it has been available now - no longer an option.


WPA Enterprise fails when server sends TLS message with multiple records (IDFGH-5702)

Development Kit:      none
Module or chip used:  ESP32-WROOM-32
IDF version:	v4.3
Build System:         CMake
Compiler version: xtensa-esp32-elf-gcc.exe (crosstool-NG crosstool-ng-1.22.0-80-g6c4433a5) 5.2.0
Operating System:     Windows
Using an IDE: Eclipse with ESP plugin
Power Supply:         USB

Problem Description
When connecting to a WPA Enterprise network that authenticates using NPS running in Windows server 2016 the association fails after the ESP receives and parses the ServerHello message, the windows NPS log shows error 262 'The supplied message is incomplete. The signature was not verified.'.
I'm using PEAP/MSCHAPv2 but as far as I can tell this problem can happen in other environments/authentication methods too, since this appears to be a issue in the TLS message exchange (I found a fix that I'll describe further below).
What I found is that when the server sends a single TLS message with multiple records the ESP only process the first one.
In my case the server is sending the ServerHello and the Certificate in the same message, the ESP parses the ServeHello but fails to read the certificate and reply with a ack (The message 'application data is null, adding one byte for ack' is shown in the console) but the server ends the connection since is already sent what it was supposed to.
I narrowed the problem to the function tls_connection_handshake in .\components\wpa_supplicant\src\crypto\tls_mbedtls.c:
struct wpabuf * tls_connection_handshake(void *tls_ctx,
					 struct tls_connection *conn,
					 const struct wpabuf *in_data,
					 struct wpabuf **appl_data)
{
	tls_context_t *tls = conn->tls;
	int ret = 0;

	/* data freed by sender */
	conn->tls_io_data.out_data = NULL;
	if (wpabuf_len(in_data)) {
		conn->tls_io_data.in_data = wpabuf_dup(in_data);
	}
	ret = mbedtls_ssl_handshake_step(&tls->ssl);          <- The message with ServerHello is read from input here
	if (ret < 0) {
		wpa_printf(MSG_ERROR, "%s:%d", __func__, __LINE__);
		goto end;
	}

	/* Multiple reads */
	while (conn->tls_io_data.in_data) {                <- Upon reaching here 'conn->tls_io_data.in_data' is null, but there are still records to be processed in the last message received
		ret = mbedtls_ssl_handshake_step(&tls->ssl);
		if (ret < 0)
			break;
	}

.....

I fixed the problem by adding the condition of 'is there more records to be read?' in the while loop:
...
	/* Multiple reads */
	while (conn->tls_io_data.in_data || tls->ssl.in_msglen>tls->ssl.in_hslen) {
		ret = mbedtls_ssl_handshake_step(&tls->ssl);
		if (ret < 0)
			break;
	}

...

I don't know if this is the best solution, but it may help others while the developers check this issue (I was in a tight spot with a costumer so I spent some long hours trying to debug this, I'm no wpa supplicant specialist so may be there's more to it, but at least it's working for now).
How to reproduce
I'm using the Windows NPS as the RADIUS in a fresh installed Windows 2016 server with a self-signed certificate, my route is a simple TP-Link TL-WR940N that supports WPA Enterprise (I have the same problem with a costumer that uses a Cisco router).
To validate the setup I connected to this network using Ubuntu in a notebook.
The wpa_enterprise idf example was used, I set the SSID, ID, Username and password fields, 'validate server' is disabled.
Debug Logs
I'm attaching 2 debug logs as a reference: The first is the error I get using the idf as is, and the other connecting with success after applying the fix.
esp32 wpa error.txt
esp32 wpa success.txt

I just confirmed that https://github.com/espressif/esp-idf/commit/e8360fe0756ec592cbd5f4ff4d36946a22561d8f solved the issue.
Thanks.


Use specific image for user namespaces tests

Due to the lack of an existing /proc dir in the rootfs of the busybox image, there
seems to be a race between the mkdir prior to the mount of /proc and whether
the root dir is already readonly? May need investigation, but for now use an image
that has a /proc dir existing.
Follow-on to comments in #5216 // cc @crosbymichael
Signed-off-by: Phil Estes<EMAIL_ADDRESS>

Anyone who wants to dig deeper, you can reproduce with one or two runs of sudo make integration EXTRA_TESTFLAGS='-run TestUserNamespace' when testImage is set to the current busybox image (e.g. use tree @ f7bd43c137248eb99543f3cc37122ee933cb4868); the readonly root FS will error on and off with:
container_linux_test.go:1650: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:59: mounting "proc" to rootfs at "/proc" caused: mkdir /run/containerd-test/io.containerd.runtime.v2.task/testing/TestUserNamespaces-ReadonlyRootFS/rootfs/proc: read-only file system: unknown
--- FAIL: TestUserNamespaces (6.75s)


[core] Transition function

This PR adds the transition(…) function for returning a [snapshot, actions] tuple given the machine, state, and event.
Its main use-case is for server-side workflows and a pure way of handling state transitions for actor logic.

Just a reminder to remove commented lines before merging 💜

@Andarist Final review?

Is there any update on the status of this, as I really need this with the deprecation of starting interpreter at a state on server side machines

Is there any update on the status of this, as I really need this with the deprecation of starting interpreter at a state on server side machines

We're planning on merging it soon (cc. @Andarist )


Validate main.go:add warning

Increases the warning when the ref's use does not conform to the specification
Signed-off-by: zhouhao<EMAIL_ADDRESS>

Seems good to me.

@opencontainers/image-tools-maintainers  PTAL

LGTM

4237bf45 looks good to me.

@xiekeyang can you offer your LGTM again, I fixed an issue with PullApprove syncing the latest list of image-tools maintainers

LGTM

@caniszczyk It is OK, thanks so much.

LGTM


Revert "Restore public method"

Reverts vespa-engine/vespa#4467
And he indicates, as factory just proved, that something must be done in hosted repo...

👍 doing something then ...


Create issues

what's the format of training data

See instructions of https://github.com/sinantie/NeuralAmr for data preprocessing

Thank you very much.
But the format of generated data by https://github.com/sinantie/NeuralAmr is like this.
source:
n / need :arg0 t / they :arg1 e / explain :time a / always
a / add :arg0 h / he :arg1 ( c2 / cause :arg1 ( c / come :arg1 y / you :arg3 s2 / sky :mod t2 / too )  )  :time t / then
target:
they always need to have things explained .
then he added : so you , too , come from the sky !
But the preprocessing code of your AMR-to-text like below, is seperated by "|".
The data don't have one.
At 2020-02-15 18:31:58, "Marco Damonte"<EMAIL_ADDRESS>wrote:
See instructions of https://github.com/sinantie/NeuralAmr for data preprocessing
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I'm not sure what you mean. What is the code that separates by '|'? Can you point me to the file and line?

Thanks for your help.
At 2020-02-17 17:14:57, "Marco Damonte"<EMAIL_ADDRESS>wrote:
I'm not sure what you mean. What is the code that separates by '|'? Can you point me to the file and line?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Global linker script is not appropriate

We have a handful of linker scripts, in riscv-test-env/{p,pm,pt,v}/link.ld. These impose certain views on section naming and memory maps. These really are target platform specific details, and so should be configured on a per platform basis. Otherwise we'll be adding a new version for every platform to be tested.

@jeremybennett
What is your proposed fix?
for a physical platform - there is a real physical constraint, and in fact for ibex, you will see I did create a platform specific linker script
For simulators however, these can be any shape we wish, so there is no real restriction, just a common description for the linker memory layout and the simulation setup

I was really just suggesting they should be in the target specific directory, not centrally.

Can those environments be easily overridden?
Where is the platform specific ibex script?
Does that solution work for everyone (without breaking anything)?

This is requirement has been fixed in RISCOF. Each target provides their own linker scripts to the framework. A sample linker script is also provided by the initial setup command.

This has been fixed pre-riscof, I believe.

yes. can be closed. Open if issue still persists.


Add Server Port Const and Console.log to display server port

I think this is duplicative of #14, so let's consolidate on that PR.


404 Island component not found

I'm experiencing this issue currently.
In components/islands/MyOgImage.vue
<script setup lang="ts">
const props = defineProps({
  title: String,
})
</script>

<template>
  <div class="w-full h-full flex text-white bg-blue-500 items-center justify-center">
    <h1 :style="{ fontSize: '70px' }">
      {{ title }} 👋
    </h1>
  </div>
</template>

in app.vue
<template>
  <SeoKit />
  <OgImageStatic component="MyOgImage" />
  <NuxtPage />
</template>

<style>
html {
  font-family: $dt('font.sans');
}
</style>

Resulting in error
Vue warn]: Component <Anonymous> is missing template or render function.          12:26:18 AM
[12:26:18 AM] [nuxt] [request error] [unhandled] [404]  (404 Island component not found: undefined (/__nuxt_island/MyOgImage.........

Originally posted by @boumanb in https://github.com/harlan-zw/nuxt-og-image/issues/40#issuecomment-1550440323

Hi @boumanb, thanks for the issue.
Would it be possible prodivde a StackBlitz reproduction? It would help me out a lot :pray:

Would it be possible prodivde a StackBlitz reproduction? It would help me out a lot 🙏

https://stackblitz.com/edit/nuxt-starter-rcgvwy?file=app.vue
Images aren't being generated on Stackblitz sadly. I've spend some time trying to get them to work, without success.
The error is triggered by navigating to the OG image previewer, I manually appended __og_image__ to the url.

Hey, so I've investigated this one and the issue seems to be related to your config, specifically these lines:
components: [
    { path: 'components', global: true },
  ],

The problem is that when you set this, you're resetting how the islands folder behaves. I'd recommend that you just create a component/global folder that does the same thing.
Not sure if there's anything the module can do to resolve this so I'll close this.


BUG - Tooltip reports do not display title properly when individual tooltip reports are copied

The resulting tooltip report header when pasted looks like:
0: ${indicator}

this was fixed in the report-rewrite


[Bug]: Cyclic dependency error

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Below is link to the app where the cyclic dependency is observed.
Steps To Reproduce
Open the app from the below link in edit mode and observe the cyclic dependency error shown.
https://www.loom.com/share/b03f9f060cfb4715948b9cb109f59434
Public Sample App
http://ec2-13-235-78-161.ap-south-1.compute.amazonaws.com/app/arteviva/login-6295afd8bf665a0a95913098/edit?branch=master
Version
Latest from release branch

I noticed that the actions field for all the JS objects was an empty array, though the JSObject body had functions.
Slack thread - https://theappsmith.slack.com/archives/C02KTH6EHUG/p1653999029583849

Unassigning myself till we have more information around reproducing this issue.

Closing this if we don't have information


Add features: push.subscribe, push.unsubscribe (issue #1040)

Description

Add 2 API:

push.subscribe
push.unsubscribe

Refactoring:

Add function: getTopicPath() to normalize topic (from topic_name to topics/topic_name) , and follow DRY principle (the getTopicPath function will be re-used)

split subscribeToTopics into  subscribeToTopics and subscribeToTopic to improve reuse ability.

in iOS: failWithMessage(string msg) will be replaced by failWithMessage(callbackId, string msg) => this will improve reuse ability & reducing the error rate in the code. Because in previous code It always use callbackId from push.init(). It's not good and It could cause misleading.

Related Issue

https://github.com/phonegap/phonegap-plugin-push/issues/1040
Motivation and Context

Add more API
How Has This Been Tested?

Tested in production environment.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@hungdoan2 thanks so much for the PR. I released a 1.8.3 today and I'm going to put out a 1.9.0 with this and other API changes in a few days.

What about WNS?


Wrong optional type in setup props for prop that default value is null

Version
3.0.11
Reproduction link
https://codesandbox.io/s/wonderful-frog-2wp60?file=/src/index.ts:0-189
Steps to reproduce
follow the link
import { defineComponent } from "vue";

defineComponent({
  props: {
    notUndefined: {
      type: Number,
      defualt: null
    }
  },
  setup(props) {
    props.notUndefined;
  }
});

What is expected?
notUndefined should not be optional
What is actually happening?
notUndefined is optional

need required:true option ?

need required:true option ?

In runtime it can't be undefined or just not in the keys, so I think required: true is just a workaround.

default,your spelling is incorrect.

defualt => default
your spelling is incorrect.

Sorry for that😂


Upload not full speed

Hello,
I'm facing uploading not full speed. Normal POST upload i can get full 100Mbps per file in tab browser. If i upload with per file per tab (3 tab total) can get full 300Mbps. Should i get full 300Mbps instead 100Mbps upload speed, i have set upload-chunk 10MB. What setting to fix it? Thank you.

If you upload multiple videos in one single POST request, you will always be faster than uploading chunks of those videos in many requests.
This is because for each request, you will have the overhead of establishing the HTTP connection (this is less of an issue with HTTP/2). With HTTPS, this also includes the overhead of establishing the TLS connection for reach request (less of an issue with TLS Session Resumption).
I don't think the combined overhead explains a 3x difference, but detecting the transfer speed of multiple requests is also not that accurate.
If you want to get the same speed as a single POST upload, you can do so with the option singleFileUploads:false and not setting maxChunkSize  - but then you also get all the drawbacks of a single POST upload.

if i upload one by one with setting sequentialUploads: true, i still get max 100Mbps instead 300Mbps. so it can be related to upload-chunk ?

Yes, each chunk is one separate request and will incur an overhead cost.

so, no way to fix it? if use normal upload (without upload-chunk) with large file 10-20GB will be terrible/nightmare with move_uploaded_file. btw thank you

If your server-side supports storing incomplete uploads, you could implement resumable uploads by setting the uploadedBytes option to the number of bytes that have been uploaded successfully.
This way, you do not need to set the maxChunkSize option and can upload in one request.
See also:
https://github.com/blueimp/jQuery-File-Upload/wiki/Chunked-file-uploads#resuming-file-uploads

hello, so it will work like as upload-chunk (not function move_uploaded_file), right?

seem it upload all file, although i was set limitConcurrentUploads: 2

The sample PHP upload server does not support resuming incomplete uploads unless chunked uploads are enabled on the client-side. So you will have to find and implement a different solution.
Your screenshot looks like you have set singleFileUploads:false or limitMultiFileUploads:1.
limitConcurrentUploads is for limiting concurrent uploads and does not influence how many files are included in one request.

hello, it mistake by my fault. everything is ok now. thank you so much.

can i ask you how to edit file name directly before submit "Start upload"?

Sure, you can read how to do this here:
https://github.com/blueimp/jQuery-File-Upload/wiki/API#how-to-provide-alternative-file-names
Since your original question seems to be answered, I'll close this issue.
Please note that I don't provide any official support for this project, see also #2190.

Sorry, you mistake my mean. I mean edit file name as screenshot. If dont have, hope you can add this feature to project. thank you.


Added linux cpu check

[ x] I have read freeCodeCamp's contribution guidelines.
[ x] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[ x] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Congrats @iozevo on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Port Ensure class from Serenity BDD

Serenity BDD has a nifty alternative to make assertions that would make a nice addition to screenpy; Ensure
Java example:
sam.attemptsTo(
    Enter.theValue("40").into(AGE_FIELD).thenHit(Keys.ENTER),
    Ensure.that(AGE).text().isEqualTo("40")
)

Special consideration will need to be taken into account to allow expansion of this class since the methods which comprise of resolutions  aren't solely in the screenpy package.  For instance screenpy_selenium has IsVisibleElement which would be nice to use for the folks who use selenium but should not be part of Ensure in the base package.
Perhaps there is some magic to be had here to avoid awkward imports between packages.

In my test suite, we have a few tasks that do something to the effect of:
# tasks/ensure_status_reads:

class EnsureStatusReads:
    ...

    def perform_as(self, the_actor: Actor) -> None:
        the_actor.attempts_to(
            Click.on_the(ELEMENT_THAT_REFRESHES_STATUS),
            See.the(Text.of_the(STATUS_ELEMENT), ReadsExactly(self.status))
        )

We can then do this elsewhere:
the_actor.attempts_to(
    Eventually(EnsureStatusReads("Updated"))
)

Does this achieve what you're hoping to see from Ensure? Maybe we could just add an alias for See?

I've written those as well.  I started to call those "combo actions".   But I don't think that's the same thing.
From what I can see in the BDD library there are a bunch of convenience methods that do the equivalent of See(question(TARGET), resolution())  just in a different format.
Something like :
Ensure(TARGET).question().resolution()
In general I think this is a language driven pattern.  It feels like a very Java-esque way to write it.

Since See is an Action and should is an alias for attempts_to, there's nothing really stopping you from doing this:
Sam.attempts_to(
    Enter.the_text("40").into_the(AGE_FIELD).then_hit(Keys.ENTER),
    See.the(Text.of_the(AGE_FIELD), ReadsExactly("40")),
    DoSomeOtherStuff(),
    ...
)

We've even got Confirm as an alias for See, which is probably more "ensure"-like.

Closing this one as we do have a mechanism to mimic this behavior already in ScreenPy, and i don't like how we'd have to write new methods to handle each of the possible question/resolution pairs.
I discussed this on Discord with @bandophahita and he's cool with closing this issue, though he thinks making dynamic methods sounds like a fun challenge. :P


The extension does not show any errors anymore

I have been using this extension for a while, and did not change any ESLint configuration related.
Randomly, the extension stopped showing errors in the VSCode editor.
For example, I have this code:

As you can see, there is no "RED LINE" of an error (or yellow), but if I run ESLint against the code:

So this is a prove there is indeed an error that should be marked.
I re-installed the extension, reloaded the editor - nothing helps. My version I use is v.3.0.8 the the ESLint version is 8.57.0. I tried to upgrade to the new major 9 version but it didn't help. Nothing related to ignorePatterns or .eslintignore file affect here.

Hi @tal-rofe98, I'm having the same issue - how did you end up solving it?
I'm trying to use flat config with 3.0.8 and it's not working for me

Same problem on v3.0.8. I solve it by reinstall old version v2.4.4.

Solved for me by updating VSCode. You can debug extension errors like this: https://stackoverflow.com/a/54381900


Defining custom vertex data for the map

Hi!
First of all - great plugin!
Is it possible to define custom vertex data (CUSTOM0-3) to be passed in along with the heightmap data?
Thanks in advance for the answer.

This Terrain plugin reuse the Mesh Chunk in generated terrain. That means one terrain mesh chunk could be copied and places in multiple place.
Custom Vertex data need a unique mesh which will not work with this system
The best is to pass an terrain image to shader  and sample that in vertex shader, which is also very efficient


CPU耗费大

Phone is hot for a while(maybe after 3 minutes)？Any suggestions for this problem?

enable android:hardwareAccelerated and use DanmakuView

Why not DanmakuSurfaceView

the canvas returned by SurfaceView.lockCanvas() cannot be hardware accelerated

OK, App have too much work doing in UI thread, DanmakuView may not be a good choice.


Importing Dependencies When it shouldn't

ImplicitPackageReference is importing its dependencies into the projects that import it, when it shouldn't be, because its dependency dll's are in the build folder in the package, causing some issues on some projects that import it.

Fixed, Changed package to be truely self enclosed


WDL function length() is not handled

Currently, the WDL function length() is not translated by the convertor. (https://github.com/openwdl/wdl/blob/main/versions/1.1/SPEC.md#int-lengtharrayx)
A WDL workflow containing length() function can be found here. (https://github.com/biowdl/tasks/blob/develop/bcftools.wdl#L75)

No. Still searching through the CWL user guide. There seems to be no mention of length and I am currently looking through the Array Inputs section.

There seems to be no mention of length

Yeah, you'll need to use a CWL Expression (javascript) again: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/length
Using https://github.com/biowdl/tasks/blob/68c56c9f7cceab1658dfae39f8d130d8ee4fe71a/bcftools.wdl#L75 as an example:
The WDL Expression Placeholder
~{true="--samples" false="" length(samples) > 0}

should look something like this in CWL (untested, though)
${if (inputs.samples.length > 0) {return "--samples";} else {return "";}}

Can I get examples for when the length() function appears by itself without being associated with true and false keywords?
And how can I source for these examples myself?

Am trying to run tests for the feature I implemented but am getting an error with token recognition. Am using this workflow https://github.com/biowdl/tasks/blob/develop/bcftools.wdl#L75

Am trying to run tests for the feature I implemented but am getting an error with token recognition. Am using this workflow https://github.com/biowdl/tasks/blob/develop/bcftools.wdl#L75

Can you open a draft PR? That will be easier for me to diagnose

Could be a key error. There's no key Array[String] in the dictionary wdl_type defined at the beginning of main.py. https://github.com/common-workflow-lab/wdl-cwl-translator/blob/main/wdl2cwl/main.py#L23 Try commenting the inputs of type Array[String] in the inputs and command sections of bcftools.wdl and see whether the error still persists.

Tried commenting some all Array[String]. Now the error is
Traceback (most recent call last):   File "wdl2cwl/main.py", line 798, in <module>     main()   File "wdl2cwl/main.py", line 794, in main     result.write(str(convert(args.workflow)))   File "wdl2cwl/main.py", line 586, in convert     cwl_inputs = get_input(cwl_inputs, ast.task_inputs, ast.task_inputs_bound)   File "wdl2cwl/main.py", line 515, in get_input     input_value = int(raw_input_value) ValueError: invalid literal for int() with base 10: '1+ceil(size(inputFile,G))'

Could be a key error. There's no key Array[String] in the dictionary wdl_type defined at the beginning of main.py.
https://github.com/common-workflow-lab/wdl-cwl-translator/blob/main/wdl2cwl/main.py#L23

Why not add "Array[String]": "string[]"?

Could be a key error. There's no key Array[String] in the dictionary wdl_type defined at the beginning of main.py.
https://github.com/common-workflow-lab/wdl-cwl-translator/blob/main/wdl2cwl/main.py#L23

Why not add "Array[String]": "string[]"?

I have added that to the main.py and now am getting this error

Please let me know if there's a better way I can report errors rather than sending screenshots here.

Please let me know if there's a better way I can report errors rather than sending screenshots here.

Can you copy and paste from your terminal surrounded by triple backticks on an empty line?
Example:

```
$ test
results
```

Becomes
$ test
results

It's referencing a file that's not in the directory.

Please git pull https://github.com/common-workflow-lab/wdl-cwl-translator.git main and then make install-dep


Follow/unfollow

Not a issue but, i would like to know if there is a way in this lib to follow or unfollow a user ?

Just add at the end of the Instagram.php file, this function:
public function follow($accountId)
{
Request::post(Endpoints::getFollowUrl($accountId), $this->generateHeaders($this->userSession));
}

I thought it was there. But apparently only like/unlike, comment/uncomment.

Just add at the end of the Instagram.php file, this function:
public function follow($accountId)
{
Request::post(Endpoints::getFollowUrl($accountId), $this->generateHeaders($this->userSession));
}

it's not working for me,
has anyone tested ?


unlock_access_by_token not working - invalid token

Hi guys,
when I run User.unlock_access_by_token '1e3f9c8987aaaa28318ec853031a0072860a163cc9a577efe424b289bf0034d1' it does not unlocks the user even if the user has unlock_token equal to 1e3f9c8987aaaa28318ec853031a0072860a163cc9a577efe424b289bf0034d1
Even if I click the link in the unlock email it tells me: invalid token.
It looks like I'm doing something wrong because this functionality has been here for quiet some time.
devise (3.5.2)
rails (4.2.3)
Thanks

The tokens are encrypted. You need to use @token when sending e-mails instead of accessing the token directly.

thanks @josevalim I probably had outdated version of email template.


Added typeof for better server side compatibilty

Solves missing document variable in server side
[0] ROUTER ERROR:   ReferenceError: document is not defined
[0]
[0]   - get-vendor-prefix.js:9 getVendorPrefix
[0]     [mysite]/[react-motion-ui-pack]/lib/get-vendor-prefix.js:9:8

Also we need the issue https://github.com/souporserious/react-measure/pull/8 to be merged in order to make react-motion-ui-pack fully compatible with server side rendering.
@souporserious, I think this issue https://github.com/souporserious/react-motion-ui-pack/issues/14 didn't solve it, at least not for me.
By the way, awesome module :+1:

This was actually removed and put into its own package https://github.com/souporserious/react-motion-ui-pack/commit/22a2776a2fe5b62932ea40c7c15a67fd964773fa I'll release a new version asap with fixes for both this and react-measure. Thank you for doing that though :)

great! thanks :+1:

Fixed https://github.com/souporserious/react-motion-ui-pack/commit/991400d35dc5329ff0c74fbe3b866dc8251fecbc


Make new editables added to a form match the waiting state of the form

When adding a new item to an editable form, the waiting state of the new item needs to match the waiting state of the rest of the form.

@coreypobrien , thanks for your commitment.


AM-2611 ET WA Specific Challenged Access - extra test cases

https://tools.hmcts.net/jira/browse/AM-2611
extra tests
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Reviewed alongside #1863 (+ #1854) and current documented mappings in config; see comments against #1863.


testing on google colab

hello
thank you for implementation sharing
it seems very good and powerful tool.
how can I run a sample for test in google colab? because of limitation in disk.
appreciate for help and answer.
thank you

I tried, but max A100 in Google Colab goes with 40gb, which is not enough to load the model into the VRAM


docs(website): spanish translation #1380

Summary
Translate the following routes.

[x] /
[x] sidebar
[x] analyzer/index

Test Plan

Check if there is no missing translation in the translated files.
Check if the translations are correct and if they adhere to the grammatical rules of Spanish.

Heya @bjohansebas , thank you for your initiative.
Not sure if you read https://github.com/biomejs/biome/blob/main/website/TRANSLATIONS.md
We would appreciate it if:

you find first more contributors to help you with this endeavour. You could use the Discord server to see if there are people willing to help
you open an issue to track the work
you stick around with Biome, and decide to update the translations. Documentation changes over time, and if we don't have anyone taking care of the translations, we'd prefer to not do it. Maintaining translations is a big commitment

Heya @bjohansebas , thank you for your initiative.
Not sure if you read https://github.com/biomejs/biome/blob/main/website/TRANSLATIONS.md
We would appreciate it if:
* you find first more contributors to help you with this endeavour. You could use the Discord server to see if there are people willing to help

* you open an issue to track the work

* you stick around with Biome, and decide to update the translations. If you want to translate the pages but then decide to move to another project, then we prefer to not translate the documentation at all. Documentation changes over time, and if we don't have anyone taking care of the translations, we'd prefer to not do it. Maintaining translations is a big commitment

Thank you, I'll keep the recommendations in mind more. I've just opened a new issue to translate the page into Spanish #1380.

Thank you @bjohansebas , but it seems there isn't enough interest to help here. You might want to try discord and see if someone wants to hep.


better maskprep

remove dask
rename dataprep with maskprep , thank you @HelgeGehring  for the name
move it to gdsfactory/geometry/
rename Layout to RegionCollection, thank you @sebastian-goeldi  for the name

@tvt173
@simbilod
@HelgeGehring
@mdecea

while I like maskprep better than dataprep. i don't like having a maskprep and a maskprep_flat. it's too confusing, and not a good distinction, as you could imagine ways to add some hierarchical capabilities to the module currently called maskprep_flat. i would argue that the module currently called maskprep_flat should be called maskprep and the other one should just be something like gdsfactory.geometry.ops (similar to shapely ops)

If I see it correctly, you are using erosion/dilation for fixing space issues, right?
It's a bit aggressive imo amd can kill DRC runtime because you are essentially flattening. Unless I am wrong, we have klayout imported there already. If yes, there is a more elegant solution, i.e. pull up the polygons into the hierarchy level where the violation occurs and merge them with a fix, see:
https://github.com/gdsfactory/kfactory/blob/main/src/kfactory/utils/violations.py#L4-L20
This can still kill DRC, but should be way nicer in the average case.


macOS self-contained mode is inoperative

Godot version
4.0.rc 2 mono
System information
Mac M1
Issue description
I create an empty file called _sc_ in Godot_mono.app/Contents/MacOS/, but the godot editor doesn't create editor_data folder, it uses ~/Library/Application Support/Godot/ to save editor data.
Steps to reproduce
1.Download godot_mono 4.0 rc2 on M1
2.Create sc file in Godot_mono.app/Contents/MacOS/
3.Open editor
Minimal reproduction project
no

Duplicate of #73081

Are these two issues the same? Is it a bug or feature?

Can you list the contents of the ~/Library/Application Support/Godot/ folder? If there's more than app_userdata, then it might not be the same indeed.

~/Library/Application Support/Godot/

It's a different issue then.
Can you show the contents of your Godot_mono.app, and confirm that there's no editor_data folder created next to it?

_sc_ should be in the same folder as Godot_mono.app, not inside it. Bundle should be considered read only and not, and Contents/MacOS/ can have executable files.

But 3.5.1 version it works.

I do this with 4.0 rc2, it doesn't work either.

It works if started from terminal, but not from Finder. Seems like a result of App Translocation done by Gatekeeper.

It's incorrect to write self-contained mode data into a bundle, since it will damage the bundle signature, and in general the bundle might be in read only location.
It's impossible to get a real bundle path, since Gatekeeper can relocate it randomly (at least on macOS 13.0).

So I guess self-contained mode is no longer supported on macOS (and probably will not be supported since there's no way to do it properly), docs should be updated to indicate it.

[macOS] Re-add support for the sc inside app bundle. #73429

ok, thanks.
I'd like to make two comments as a user: support sc inside app bundle again and this feature can be switched on and off using the editor ui.

This is likely "fixed" as far as macOS allows it to be with https://github.com/godotengine/godot/pull/73429#issuecomment-1434261545.


Release Google.Cloud.SecurityCenter.Settings.V1Beta1 version 2.0.0-beta04

Changes in this release:
New features

Add IServiceCollection extension methods for client registration where an IServiceProvider is required. (commit 022fab2)

Created release for Google.Cloud.SecurityCenter.Settings.V1Beta1-2.0.0-beta04


[AutoPR postgresql/resource-manager] chore: jsonfmt postgresql

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7432

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/7713


Android SmoochManager doesn't have a logout method

iOS's SmoochManager.m file has a logout method but Android's SmoochManager.java not.

Added, thanks!


mautrix-slack: init at a9ba2f9249bdc5df69a1349122d1769e7e48c9e1

Description of changes
Add https://github.com/mautrix/slack
Signed-off-by: Sumner Evans<EMAIL_ADDRESS>
Things done
I run this package on my server, and it works fine.

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

We can bump to the release version: https://github.com/mautrix/slack/releases/tag/v0.1.0


default options object when none is provided

This solves the issue #210

More robust solution would be to use something like this:
var mergedOptions = angular.extend({}, defaultOptions, userSuppliedOptions)


Build fails with error but exit code is 0

I encounter an Unexpected token build error but enclosure still exits with a 0 status code.
This makes my IDE try to build other dependencies and the error message to be lost in void.

Wrong repo – sorry!

Wrong repo – sorry!


[gtk] x64-linux build failure

Host Environment

OS: Ubuntu 18.04 LTS
Compiler: gcc 7.5.0, cmake 3.10.2

To Reproduce
Steps to reproduce the behavior:
vcpkg install gtk
Failure logs

vcpkg error
$ vcpkg install gtk
Computing installation plan...
The following packages will be built and installed:
    gtk[core]:x64-linux
Starting package 1/1: gtk:x64-linux
Building package gtk[core]:x64-linux...
-- Using cached /.../vcpkg/downloads/gtk+-3.22.19.tar.xz
-- Using source at /.../vcpkg/buildtrees/gtk/src/gtk+-3-b723a7b846
-- Configuring x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: /.../vcpkg/downloads/tools/cmake-3.14.0-linux/cmake-3.14.0-Linux-x86_64/bin/cmake /.../vcpkg/buildtrees/gtk/src/gtk+-3-b723a7b846 -DGTK_VERSION=3.22.19 -DCMAKE_MAKE_PROGRAM=/.../vcpkg/downloads/tools/ninja-1.10.0-linux/ninja -DCMAKE_SYSTEM_NAME=Linux -DBUILD_SHARED_LIBS=OFF -DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=/.../vcpkg/scripts/toolchains/linux.cmake -DVCPKG_TARGET_TRIPLET=x64-linux -DVCPKG_SET_CHARSET_FLAG=ON -DVCPKG_PLATFORM_TOOLSET=external -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE -DCMAKE_VERBOSE_MAKEFILE=ON -DVCPKG_APPLOCAL_DEPS=OFF -DCMAKE_TOOLCHAIN_FILE=/.../vcpkg/scripts/buildsystems/vcpkg.cmake -DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON -DVCPKG_CXX_FLAGS= -DVCPKG_CXX_FLAGS_RELEASE= -DVCPKG_CXX_FLAGS_DEBUG= -DVCPKG_C_FLAGS= -DVCPKG_C_FLAGS_RELEASE= -DVCPKG_C_FLAGS_DEBUG= -DVCPKG_CRT_LINKAGE=dynamic -DVCPKG_LINKER_FLAGS= -DVCPKG_TARGET_ARCHITECTURE=x64 -DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_BINDIR:STRING=bin -DGTK_SKIP_HEADERS=ON -G Ninja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/.../vcpkg/packages/gtk_x64-linux/debug
    Working Directory: /.../vcpkg/buildtrees/gtk/x64-linux-dbg
    Error code: 1
    See logs for more information:
      /.../vcpkg/buildtrees/gtk/config-x64-linux-dbg-out.log
      /.../vcpkg/buildtrees/gtk/config-x64-linux-dbg-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:306 (vcpkg_execute_required_process)
  ports/gtk/portfile.cmake:30 (vcpkg_configure_cmake)
  scripts/ports.cmake:90 (include)

Error: Building package gtk:x64-linux failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: gtk:x64-linux
  Vcpkg version: 2020.02.04-unknownhash

Additionally, attach any relevant sections from the log files above.

config-x64-linux-dbg-out.log
-- The C compiler identification is GNU 7.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Configuring incomplete, errors occurred!
See also "/.../vcpkg/buildtrees/gtk/x64-linux-dbg/CMakeFiles/CMakeOutput.log".

config-x64-linux-dbg-err.log
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
LIBINTL_LIBRARY
    linked by target "gdk-3" in directory /.../vcpkg/buildtrees/gtk/src/gtk+-3-b723a7b846
    linked by target "gtk-3" in directory /.../vcpkg/buildtrees/gtk/src/gtk+-3-b723a7b846
    linked by target "gailutil-3" in directory /.../vcpkg/buildtrees/gtk/src/gtk+-3-b723a7b846
PANGO_WIN32_LIBRARY
    linked by target "gdk-3" in directory /.../vcpkg/buildtrees/gtk/src/gtk+-3-b723a7b846
    linked by target "gtk-3" in directory /.../vcpkg/buildtrees/gtk/src/gtk+-3-b723a7b846
    linked by target "gailutil-3" in directory /..../vcpkg/buildtrees/gtk/src/gtk+-3-b723a7b846

Additional context
LIBINTL_LIBRARY
I have the following packages installed that should give me the proper files for libintl: gettext gettext-base libgettextpo0 libgettextpo-dev libc6 libc6-dev libc6-dbg, all of which are properly updated. I tried adding message( ${LIBINTL_INCLUDE_DIR} ) after line 54 in CMakeLists.txt, which confirmed the location of libintl.h to be in /usr/include (which locate libintl.h agrees with).
Is cmake looking for a libintl.so or libintl.a somewhere for the library? (I'm still new to C/C++, so I'm not familiar with this sort of library management.) There is a /usr/lib/x86_64-linux-gnu/preloadable_libintl.so, but that's it. locate libintl.so only returns the preloadable file. Is something installed wrong? I'm clueless.
PANGO_WIN32_LIBRARY
I assumed that this was an issue because I'm running this on Linux. Should line 33 of CMakeLists.txt be wrapped with if(WIN32)? I am probably wrong on that, but I suppose someone will know what's going on.
If you need any more information (package versions, files existing or not, etc.), please let me know. I'd like to be able to use GTK headers with Visual Studio Code. I've tried quite a bit to get this working, but I unfortunately don't have enough cmake experience or GTK experience to know where the issue is.
God bless,
scoutchorton

I have a very similar error on Ubuntu 22

Same issue on Ubuntu 22

Same issue on Ubuntu 22

Certainly not the same. The original post (2020) is about port gtk, major version 3. Port gtk is at major version 4 since 2021.
A new port gtk3 was added recently (2022), with a lot of work on dependencies. It probably resolved the issues reported here for major version 3.
So please choose the desired major version, and report issues properly.


Remove special treatment of channel ID 1

What/Why?
Historically, we had to treat channel 1 on a store as special because we did not have a channel canonical domain specific to channel 1, so you had to use store-HASH-CHANNELID.mybigcommerce.com as the hostname for all non-default channels, but store-HASH.mybigcommerce.com for channel 1.
This has been normalized across the platform such that store-HASH-1.mybigcommerce.com hostnames are now available.
Therefore, this PR removes the special snowflake code that treats channel 1 differently, which means one less thing to think about when dealing with default channels.
⚠ I have also changed the behavior when the BIGCOMMERCE_CHANNEL_ID env variable is not specified; the previous code would essentially fall back to channel 1 in this case; after this change, those requests will fail. I believe this is actually desirable as users of Catalyst are not set up for success if they do not explicitly specify a channel ID on their requests.
Testing
TBD

btw... @jorgemoya was tackling this as part of https://github.com/bigcommerce/catalyst/pull/994

I think this is fine to merge if we want in the repo asap, since my changes depend on some other factors.

Closing this in favor of #994


Settings 'docker' environment for running the WebAPI in Docker

Merged #13 instead. Closing this one


Empty 'definitions'-array in swagger 2.0-spec results in JsonSerializationException

When parsing the swagger spec located at: https://api.osre.nl/services/v2/documentation/swagger.json - I just ran into this one:

Newtonsoft.Json.JsonSerializationException: Cannot deserialize the current JSON array (e.g. [1,2,3]) into type 'System.Collections.Generic.IDictionary`2[System.String,NJsonSchema.JsonSchema4]' because the type requires a JSON object (e.g. {"name":"value"}) to deserialize correctly.
To fix this error either change the JSON to a JSON object (e.g. {"name":"value"}) or change the deserialized type to an array or a type that implements a collection interface (e.g. ICollection, IList) like List<T> that can be deserialized from a JSON array. JsonArrayAttribute can also be added to the type to force it to deserialize from a JSON array.
Path 'definitions', line 507, position 18.

Runtime: Default
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EnsureArrayContract(JsonReader reader, Type objectType, JsonContract contract)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateList(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, Object existingValue, String id)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue(JsonProperty property, JsonConverter propertyConverter, JsonContainerContract containerContract, JsonProperty containerProperty, JsonReader reader, Object target)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Populate(JsonReader reader, Object target)
   at NJsonSchema.ExtensionDataDeserializationConverter.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
   at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
   at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
   at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
   at NJsonSchema.Infrastructure.JsonSchemaSerialization.<FromJsonAsync>d__9`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NSwag.SwaggerDocument.<FromJsonAsync>d__53.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NSwag.Commands.OutputCommandBase.<ReadSwaggerDocumentAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NSwag.Commands.SwaggerGeneration.FromSwaggerCommand.<RunAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NSwag.Commands.SwaggerGeneration.FromSwaggerCommand.<RunAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NSwag.Commands.NSwagDocumentBase.<GenerateSwaggerDocumentAsync>d__40.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NSwag.Commands.NSwagDocument.<ExecuteAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NSwag.Commands.Document.ExecuteDocumentCommand.<ExecuteDocumentAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NSwag.Commands.Document.ExecuteDocumentCommand.<RunAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NConsole.CommandLineProcessor.<ProcessSingleAsync>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NConsole.CommandLineProcessor.<ProcessAsync>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NConsole.CommandLineProcessor.Process(String[] args, Object input)
   at NSwag.Commands.NSwagCommandProcessor.Process(String[] args)

...when I remove the property by deleting the entire line containing "definitions": [],, the parsing of the swagger spec functions just fine.
Is this a violation of the spec schema? Or should the parser be able to deal with this properly?

@RSuter - Thanks. In that case I'll let them know.


Pub/sub subscription does not resubscribe successfully after a socket closed unexpectedly error

Description
We found when upgrading the node-redis client from version 3.1.2 to 4.7.0 it failed to recover after a socket closed unexpectedly error. We added all of the possible event listeners and we can see it attempting to reconnect, but never reach ready state:

This happens when the system is under significant load. This is affecting our ability to upgrade the node-redis client library in our production environment.
Production environment:
Node.js Version: "18.18.1"
Redis Server Version: "6.2"
Node Redis Version: "4.7.0"
Platform: AWS Elasticache
Example code to reproduce:
https://github.com/Milanote/node-redis-bug
I couldn't create a nice clean assertion, but the basic gist is this test case sends a large payload (5mb) frequently until the client-output-buffer-limit is reached. The  v3 version seems to reconnect and resubscribe correctly and I can see more messages received. The v4 test case doesn't seem to be able to resubscribe correctly, and receives fewer messages overall. I've tried debugging the client code a bit, but found it hard to pinpoint the exact issue.
It seems to hang resolving the resubscribe promise: https://github.com/redis/node-redis/blob/942de1f0b4868f0f6464b2e0702b621a3373c4ee/packages/client/lib/client/commands-queue.ts#L324

Does it hang because the timeout is reset to 0 after successful connection? (https://github.com/redis/node-redis/blob/942de1f0b4868f0f6464b2e0702b621a3373c4ee/packages/client/lib/client/socket.ts#L164)
I tried setting disableOfflineQueue to false but that didn't seem to help. Could it be because the write buffer is not cleared?

Node.js Version
18.18.1
Redis Server Version
6.2
Node Redis Version
4.7.0
Platform
Linux
Logs
No response

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

I tried running playing with your repo, and it seems like both versions are running about the same (the "happy case" works, and the 5MB case cause the connection to die reconnect, and resubsribe). Anyway, writing to the socket faster than the network/server can handle is something you should not do, and there is not much the client can do about it..


[Bug] Cannot convert undefined or null to object with study has dicom tag (0043,1097) value's element = null

Describe the Bug
Ohif viewer version: 3.9.1.
When open a study that has a dicom tag (0043,1097) value as attached, a error occurs: Cannot convert undefined or null to object.
at method: addRetrieveBulkDataNaturalized() of file: extensions\default\src\DicomWebDataSource\index.js
Steps to Reproduce
Open a MR study that has a dicom tag (0043,1097) value as attached

The current behavior
A error occurs:

The expected behavior
Can open image viewer correctly
Is it correct if I fix this by check: if (naturalized == null) return; as
      const addRetrieveBulkDataNaturalized = (naturalized, instance = naturalized) => {
        **if (naturalized == null) return;**
        for (const key of Object.keys(naturalized)) {
         ...
        }
    }

OS
Windows 11
Node version
21.7.3
Browser
Chrome

I think this is already resolved, I uploaded this to dcm4chee locally and it opens up with no problems


Remove redundant variables

This is the 2nd attempt of merging this PR https://github.com/SGA-A/c2c/pull/18.

LGTM.


Two Parquet read fixes

Hi! I did the CLA thing.
Parquet list types and Hive
Hive serializes Parquet lists in a particular way. It wraps the element field
in an optional group, to support nulls:
optional group listField (LIST) {
  repeated group bag {
    optional int array_element
  }
}

However, other sources create lists differently, without the bag group:
optional group listField (LIST) {
  repeated int listField_tuple
}

This changes PrestoReadSupport to special case that structure, and adds a
test case for it.
Read ordering with deeply nested structs
Parquet calls GroupConverter#end after each group is finished, but the
afterValue call tree (which decides when nulls are written out) was being
called at the very end. This would result in nulls being in the wrong place.
To fix this, I reordered the calls so that each LIST or STRUCT or MAP
"manages" it's own beforeValue and afterValue trees.

(The build failure seems separate from my changes: Cannot instantiate class com.facebook.presto.raptor.TestRaptorDistributedQueries)

Ya, that was fixed. Can you rebase and update your branch? (that will re-start the tests)

I just merged a change to the memory format of structs, could you rebase this?

Sure, done. It looks like your changes subsumed the ordering fix, so I removed that from the PR.

(Sorry, build is fixed now)

Hi folks - anything needed from me here? =)

Oops, accidentally hit "close and comment" >.<

Is there a spec for Parquet? I'm not familiar with the serialization format

Looks reasonable to me, but I don't know much about Parquet. Had a couple questions, so ping me when you've replied to those.
CC: @nezihyigitbasi any thoughts?

Here's an overview of the spec: https://github.com/apache/incubator-parquet-format/blob/master/README.md
And discussion of the logical types, including LIST: https://github.com/apache/incubator-parquet-format/blob/master/LogicalTypes.md#lists

Had a couple comments, let me know when you've addressed those

Hey @colinmarc just following up. Were you still working on this? I tried removing that .equals("bag") check myself, but then your test failed, and I'm not sure why

Ah, sorry, I totally lost track of this. I'll finish it up, sorry.

No worries. Let me know when it's ready for review :)

@cberner sorry about the delay! I just pushed some changes to address your comments. I changed the LIST compatibility behavior to track the spec's suggested fallback conditions exactly (and made the comment more accurate).

Merged. Thanks!


Support size-based filtering

This change adds size-based filtering by exposing "size" attribute and
adding number comparison operators (< and >).
Signed-off-by: Kazuyoshi Kato<EMAIL_ADDRESS>

Would it be possible to support human-friendly forms such as "2MB"? https://pkg.go.dev/github.com/docker/go-units#FromHumanSize

@AkihiroSuda I initially thought that user-facing components (e.g. public clouds' clients and/or local clients such as nerdctl) can handle multiple different units. However, it may ask them to parse expressions, if the clients support free-form expressions.
There are two options:

Keep this filtering minimum and let clients support size units, <= and >=.

Pros: We can keep containerd's responsibilities minimum.
Cons: High-level clients may need to support them.

Make this filtering user-friendly and support size units and <= and >=.

Pros: High-level clients don't have to do any. We can make what end-user can do consistent.
Cons: More features we will have in containerd.

Okay. Supporting size units is much simpler than I expected. If the direction is fine, I'm going to support <= and >= as well.

On second thought, supporting size units works nicely on < and > since they are newly-introduced number-only operators. But how about == and !=?
Right now, 1025 > 1KiB could be true, but 1024 == 1KiB could be false. We can parse size units on == but it will introduce a Do-What-I-Mean behavior, which I reluctant to have in daemons like containerd.

@kzys i think we can remove unit support and leave that up to clients if that will make things more robust and clear

Sounds good to me. @AkihiroSuda What do you think?

SGTM

Let me close this one. I don't want to increase its complexity if the benefits are questionable.


Update Docs on how to use CSS stylesheets

Description
Add documentation on how to use the css design-token stylesheets
Technical Details

Write docs on how to add css stylesheets to project in README.md
Import docs from README.md into storybook in install page

Acceptance Criteria

Docs can be read in github
Docs can be found from storybook

References

Implementation to document https://github.com/MetaMask/metamask-extension/pull/13657/

Done!


refactor: changes in labels

Each commit in this PR contains a change in labels to add consistency or improve the interpretation
Work in progress

This set of changes is good to go. I will open future PRs with more changes, but it will be good to do it in another iteration.


"Disable telemetry" refinements

I recently updated my master branch, and noticed some things having to with the telemetry notification:

When the notice about telemetry collection shows in VSCode, it doesn't put anything in the output log, so once dismissed it can't be easily re-read.
I initially misread the command as "run (flutter|dart) disable-telemetry" instead of the actual command "run (flutter|dart) --disable-telemetry" (at least I assume I misread it: I can't go back and see).  Could we just make disable-telemetry an actual command (either in addition to the flag, or instead of)?
When it is run, it's not clear to me what telemetry it disables, or what the scope is: for example, if I disable telemetry for the dart command, does that also disable it for the flutter command, or do I have to run it once for each? It would be good if the notifications that the telemetry has been disabled included this information (and it would be nice if the messages on both Dart and Flutter were similar: right now they are not).

cc @eliasyishak

Thank you so much for these comments about the new unified analytics implementation. I'll make sure the rest of the team sees this as well but to just quickly answer your questions, read below

That is the intention, the analytics can't be collected from the VS Code (language server) until the user has explicitly dismissed the popup message that comes up. Once dismissed, it won't come back again. Was there an issue with how visible it was the first time?
hmm that's interesting, i would imagine the message may be formatted differently based on the user's font size preferences. But as far as changing the actual command, we would need to update the privacy document if we wanted to change --disable-telemetry to be a standalone subcommand. I'll discuss this more with the rest of the implementation team
Thank you for this point, after re-reading the consent message it definitely isn't clear that when you disable telemetry it disables it for all flutter and dart related. Like you said, I think the best way to communicate this would be to let users know after opting out that they have indeed have opted out of everything flutter and dart related (issue for myself to fix this https://github.com/flutter/flutter/issues/124413)

cc @bwilkerson @jcollins-g @jacob314

Once dismissed, it won't come back again. Was there an issue with how visible it was the first time?

No, it was plenty visible, but since it's a popup notification, I dismissed it before I went to my terminal to type the command, and then didn't have any way to refer to the notification to check that the command I typed was correct (it wasn't!).  It would be nicer if the dialog just had two buttons on it "disable telemetry" and "continue with telemetry enabled" (or some such wording, preferably lawyer-approved). Then I wouldn't need to go to my terminal and remember the command and spell it correctly.

But as far as changing the actual command, we would need to update the privacy document if we wanted to change --disable-telemetry to be a standalone subcommand.

The advantage of it being a standalone command is that it can have richer help text associated with it (because you can say flutter help disable-telemetry), and it might be easier to find because of that (although it is clearly in there in the options section, that part scrolls off the top on my typical terminal size).
I also just noticed that the help text for the option:
    --disable-telemetry     Disable telemetry reporting when this command runs.

Seems to imply that it will only disable the telemetry in the command that is currently being run, not that it will disable telemetry collection in general if you run it without a command. Having a separate command (with associated clearly worded output when it does run) could let you make that an actual distinction: running with the option could disable it for a particular command, and running the command could disable it for everything from then on.

Just following up again to see if we addressed any concerns. We have updated the helper text to show the difference between the two suppress/disable commands
    --suppress-analytics    Suppress analytics reporting for the current CLI invocation.
    --disable-telemetry     Disable telemetry reporting when this command runs.

Disable telemetry reporting when this command runs.

Is this only for the current CLI invocation?  Or every time?  I think it's every time, and in that case, clearer text would be:
"Disable telemetry reporting each time a flutter or dart command runs, until it is re-enabled."

Also, is the opposite flag (to re-enable) called --no-disable-telemetry?  Maybe --suppress-telemetry would be a better name for the flag, since --no-suppress-telemetry is less of a double-negative, which are against our style guide, and also is similar to the analytics switch.
https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#avoid-double-negatives-in-apis

Created this PR (wip) to address this:

https://github.com/flutter/flutter/pull/125995

Closing since we merged in #125995


update

What's this?

Oeps, i wanted to update my fork but github put the pull request the wrong way. Sorry!

I also went to sleep immediatelly after i opened it...
so i didn't check it...

All good :)


Facing Sox error on Google cloud platform when I am deploying this code.

I have Sox installed on my pc, that's why this code is working fine.
But it is showing errors when I deploy this code on the Google cloud platform because of SoX.
I am working on the MicrophoneStream.js.
const recorder = require('node-record-lpcm16');

// Imports the Google Cloud client library
const speech = require('@google-cloud/speech');

// Creates a client
const client = new speech.SpeechClient();

/**
 * TODO(developer): Uncomment the following lines before running the sample.
 */
// const encoding = 'Encoding of the audio file, e.g. LINEAR16';
// const sampleRateHertz = 16000;
// const languageCode = 'BCP-47 language code, e.g. en-US';

const request = {
  config: {
    encoding: encoding,
    sampleRateHertz: sampleRateHertz,
    languageCode: languageCode,
  },
  interimResults: false, // If you want interim results, set this to true
};

// Create a recognize stream
const recognizeStream = client
  .streamingRecognize(request)
  .on('error', console.error)
  .on('data', data =>
    process.stdout.write(
      data.results[0] && data.results[0].alternatives[0]
        ? `Transcription: ${data.results[0].alternatives[0].transcript}\n`
        : '\n\nReached transcription time limit, press Ctrl+C\n'
    )
  );

// Start recording and send the microphone input to the Speech API.
// Ensure SoX is installed, see https://www.npmjs.com/package/node-record-lpcm16#dependencies
recorder
  .record({
    sampleRateHertz: sampleRateHertz,
    threshold: 0,
    // Other options, see https://www.npmjs.com/package/node-record-lpcm16#options
    verbose: false,
    recordProgram: 'rec', // Try also "arecord" or "sox"
    silence: '10.0',
  })
  .stream()
  .on('error', console.error)
  .pipe(recognizeStream);

console.log('Listening, press Ctrl+C to stop.');

Can you tell us what the errors are?
Also, which code / sample are you running?
I just navigated to cloud shell and ran the following commands:
git clone https://github.com/googleapis/nodejs-speech
cd nodejs-speech/samples
npm install
node quickstart.js

So I'm not sure where you're seeing the issue.

Error: spawn sox ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
    at onErrorNT (internal/child_process.js:415:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
    at onErrorNT (internal/child_process.js:415:16)
    at process._tickCallback (internal/process/next_tick.js:63:19)

I am receiving this error on Google cloud platform when I am trying to deploy.

This is the screenshot of the error I am getting.

This the content of my package.json file
{
"name": "new-express-app",
"version": "0.0.0",
"private": true,
"scripts": {
"start": "node index.js",
"dev": "nodemon index.js"
},
"dependencies": {
"@google-cloud/speech": "^3.6.0",
"actions-on-google": "^2.7.0",
"axios": "^0.19.0",
"body-parser": "~1.18.2",
"child_process": "^1.0.2",
"cors": "^2.8.4",
"dialogflow": "^0.9.0",
"dialogflow-fulfillment": "^0.6.1",
"express": "^4.17.1",
"google-oauth-jwt": "^0.2.0",
"gyp": "^0.5.0",
"in": "^0.17.0",
"line": "^0.1.8",
"moment": "^2.24.0",
"mongoose": "^5.6.8",
"node-gyp": "^6.1.0",
"node-record-lpcm16": "^1.0.1",
"nodemailer": "^6.3.0",
"nodemon": "^2.0.3",
"pm2": "^4.2.3",
"rebuild": "^0.1.2",
"yargs": "^15.3.1"

},
"main": "index.js",
"devDependencies": {},
"keywords": [],
"author": "",
"license": "ISC",
"description": ""
}

Hmm, looks like reproducing this error requires deploying something similar to GCP.

I think you forgot to include sox dependency in your package.json
  "dependencies": {
    "@google-cloud/speech": "^3.6.0",
    "chalk": "^4.0.0",
    "node-record-lpcm16": "^1.0.1",
    "sox": "^0.1.0",
....

I have tested Google Cloud Shell and it is working as intended.

Here's code snippet I used for testing

const fs = require('fs');

// Imports the Google Cloud client library
const speech = require('@google-cloud/speech');

// Creates a client
const client = new speech.SpeechClient();

/**
 * TODO(developer): Uncomment the following lines before running the sample.
 */
// const filename = 'Local path to audio file, e.g. /path/to/audio.raw';
// const encoding = 'Encoding of the audio file, e.g. LINEAR16';
// const sampleRateHertz = 16000;
// const languageCode = 'BCP-47 language code, e.g. en-US';

const request = {
  config: {
    encoding: 'LINEAR16',
    sampleRateHertz: 16000,
    languageCode: 'en-US',
  },
  interimResults: false, // If you want interim results, set this to true
};

// Stream the audio to the Google Cloud Speech API
const recognizeStream = client
  .streamingRecognize(request)
  .on('error', console.error)
  .on('data', data => {
    console.log(
      `Transcription: ${data.results[0].alternatives[0].transcript}`
    );
  });

// Stream an audio file from disk to the Speech API, e.g. "./resources/audio.raw"
fs.createReadStream('./audio.raw').pipe(recognizeStream);

@Ayushimidha28 Please let me know if this solves the problem.

Can you tell us what the errors are?
Also, which code / sample are you running?
I just navigated to cloud shell and ran the following commands:
git clone https://github.com/googleapis/nodejs-speech
cd nodejs-speech/samples
npm install
node quickstart.js

So I'm not sure where you're seeing the issue.

I am Working on MicrophoneStream.js. In quickstart.js you are taking input from an audio file. I am taking input from microphone.

@Ayushimidha28 Hmm, including MicrophoneStream in your first question could've saved a lot of time. I will test it again with MicrophoneStream

@Ayushimidha28 Hmm, including MicrophoneStream in your first question could've saved a lot of time. I will test it again with MicrophoneStream

I am extremely sorry. I have edited that now.

I was able to reproduce your error

I need more info about how you are deploying your code to google cloud?

Since your app rely on Sox, you may need to use Docker Image that contains sox depending on how you want to deploy your app.
Here are some options:

In GAE Flexible, you are always running at least 1 instance at any time. So even if your app is not getting any requests, you’re paying for that instance. Billing granularity is 1 minute.

In Cloud Run, you are only paying when you are processing requests, and the billing granularity is 0.1 second. See here for an explanation of the Cloud Run billing model.

@Ayushimidha28 Closing this issue because it is not related to nodejs speech.


Automated cherry pick of #4035: fix: 避免普通用户添加规则到系统安全组

Cherry pick of #4035 on release/2.11.
#4035: fix: 避免普通用户添加规则到系统安全组

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@2752e6f). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #4038   +/-   ##
==============================================
  Coverage                ?   7.13%
==============================================
  Files                   ?     480
  Lines                   ?   78065
  Branches                ?       0
==============================================
  Hits                    ?    5571
  Misses                  ?   72029
  Partials                ?     465

Flag
Coverage Δ

#aFlag
7.13% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/secgrouprules.go
4.34% <0%> (ø)

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 2752e6f...e5411cb. Read the comment docs.

/lgtm

/approve

/approve


fix: Composer issue with yeoman-environment

Description
This PR fixes the issue related to the yeoman-environment version when trying to create a bot from a local template.
Since all the generators use yeoman-generator v5.7.0 and this one uses yeoman-environment v3.2.0, we updated yeoman-environment to version 3.2.0 in Composer.
Task Item
#minor
Screenshots
This screenshot shows a bot created from the generator-bot-empty working.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
19676

Relevant Lines:
31699

💛  - Coveralls

We could add a reference to the PR in components, so if someone sees these changes, know they are related.

All the changes in the yarn.lock file are necessary, right?

I ran yarn and yarn build in /Composer locally and the yarn-berry.lock was updated as in the pipeline. I can try leaving only changes related to yeoman.

All the changes in the yarn.lock file are necessary, right?

I ran yarn and yarn build in /Composer locally and the yarn-berry.lock was updated as in the pipeline. I can try leaving only changes related to yeoman.

No, it's ok, I just checked and it looks good. Thanks!

We could add a reference to the PR in components, so if someone sees these changes, know they are related.

Solved. Thanks!

/promoted 9539


Use alpine:3 in dev setup

At this step, it is not important which exact version of
Alpine is used. To avoid old versions, the last version
of the Alpine 3 series can always be used at this point
Signed-off-by: Christian Berendt<EMAIL_ADDRESS>

Thank you @berendt for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.


Adding recovery information to Emergency response plan

Describe the issue
We have Emergency response plan build till incident investigation. We want to add the next step on how to recover the  system and re-enable the services.
Additional context
Add any other context, attachments or screenshots
Definition of done

Add more information after investigation step because we didn't have a lot there yet
The new step will be called "Recovering after an Incident" or something similar.
The step will contain clear, concise and generic information on recovering after the incident took place.
Review with PO

No longer relevant, covered by other work


MatterBridge didn't reconnect to home Assistant matter server after restart

Hello, I actually don't really know if this issue should goes here or I have to create it in python matter server repository.
Given:
Home Assistant 2024.5
Python matter server 6.0.1
Yeelight matter hub
Moes matter hub
MatterBridge  1.2.17
MatterBridge zigbee2mqtt plugin 2.0.14
When I power-off / power-on yeelight or moes matter hubs then they reconnect to HA matter server without any problem
When I restart MatterBridge, then MatterBridge and provided devices becomes unavailable until I manually restart HA Matter Server.
After HA Matter Server restart devices are back and works fine until MatterBridge restart, I've tested they are worked without any issues for at least a weak

Hi thank you for your message.
HA is my controller for test so I use it a lot.
As I wrote in the help page for the plugin:
Home Assistant issues (Matter Server for HA is still in Beta)
If HA doesn't show all devices just reload the HA Matter Server
Considering it is a beta is acceptable I guess.
Btw I didn't notice that issue since after the last Matter server / core update.
Check if you have to update it maybe.

Just one more thing.
If you look at the log you can see when the controller connects again.
That is a starting point to understand the issue.

Hello, I actually don't really know if this issue should goes here or I have to create it in python matter server repository.
Given: Home Assistant 2024.5 Python matter server 6.0.1 Yeelight matter hub Moes matter hub MatterBridge 1.2.17 MatterBridge zigbee2mqtt plugin 2.0.14
When I power-off / power-on yeelight or moes matter hubs then they reconnect to HA matter server without any problem
When I restart MatterBridge, then MatterBridge and provided devices becomes unavailable until I manually restart HA Matter Server.
After HA Matter Server restart devices are back and works fine until MatterBridge restart, I've tested they are worked without any issues for at least a weak

kindly update to latest matterbridge and give your feedback if you face any issue

Hello, sorry for long delay, was busy with testing different setups (on bare metal, in kubernetes, in HA as addon) 😅
Btw, as of now it seems to be stable enough with latest versions of HA, Matter server and MatterBridge
btw if you're interested, I've wrapped MatterBridge in HomeAssistant addon with zigbee2mqtt onboard
https://github.com/L2jLiga/ha-addons
https://github.com/L2jLiga/ha-addons-built

Hi,
I'm very interested.
Can we move this to a discussion?
So it remains open and available for everyone and you can update the info?

Hi, I'm very interested. Can we move this to a discussion? So it remains open and available for everyone and you can update the info?
#49

Sure


remove orphan

Waiting for redirect before merging: https://www.mulesoft.org/jira/browse/DOCS-5144
I did a local build of all versions of the doc and then searched for the string  sync-api-apisync to find links but nothing was returned.

The redirect is ready to go at: https://github.com/mulesoft/docs-site-antora/pull/368
Let me know if the edits are already addressed here, and I'll merge both the redirect and the removal.

Closing this branch and creating a new doc PR after I've done all the other link changes for this file. Avoids unnecessary merging.


move config file to <path.conf>/analysis-ik

config files stay with plugin is not friendly for upgrade elasticsearch or this plugin.
In official example, the plugin read config file from path.conf, (at least from v2.0.0 )
When I upgrade plugin analysis-ik, I don't want re-configure the dict, the xml.
We should put config out of plugin dir, and put it in folder named with plugin name.

@RobberPhex
Thanks for bring this pull request, please make sure the plugin will auto-detect the config path, which means the user can use the es's config path or just use the plugin's config path.

@medcl When new config file is not exist, the plugin will load from plugin dir.
I add a deprecated warn for "load config file from plugin dir"

@RobberPhex
java.io.FileNotFoundException: /xxx/xxx/config/analysis-ik/IKAnalyzer.cfg.xml (No such file or directory)

@medcl
Hi, the new config loading try to load xml from /etc/elasticsearch/analysis-ik/IKAnalyzer.cfg.xml, if not exist, try /usr/share/elasticsearch/plugins/analysis-ik/config/ik/IKAnalyzer.cfg.xml, if still failed, throw a Exception:
java.io.FileNotFoundException: /etc/elasticsearch/analysis-ik/IKAnalyzer.cfg.xml (No such file or directory)

So, user will add xml to /etc/elasticsearch/analysis-ik/IKAnalyzer.cfg.xml, which is standard config dir.
So, I think there is no inappropriate. Wait for you reply.

@RobberPhex please don't assume the plugin folder name is analysis-ik, there is no such guarantee

Hi, @medcl
When install the plugin, es will move config dir to /etc/elasticsearch and named with plugin name( from zip file), so put IKAnalyzer.cfg.xml to /etc/elasticsearch/analysis-ik/IKAnalyzer.cfg.xml is good.
If we use another name, it will confuse user by finding xml file.
For plugin name's hard code, Sorry for that, I just edit code, we can get plugin name from AnalysisIkPlugin (from everywhere).

@RobberPhex what if we don't use plugin install command, that will be cause failure, the basic install method(drop and unzip),we should also support it  :)

@medcl
this PR is too complex to support load from plugin dir, so I rewrite the patch. see #197