Unable to initalize AM

is there anyway you can make it compatible with sky3ds? also it says "unable to initialize AM" what does that mean?

also it says "unable to initalize AM" what does that mean? thanks again.

"AM" stands for Application Management. If I can't gain access to the AM service, then FBI cannot work.


Problems of Community

feedback on bug and issues

Added the mod in the existing world in 1.21, located it with commands, but upon teleporting or approaching to the location and its surroundings, the game kicks me out of the single player world and disappeared, only to solved by removing the current level.dat and replacing it with level.dat old. Creating a new world with the mod only to stuck at loading screen with 100% and unable to take a single glance of the world.

Is there a video of this happening?

I have a few screenshots of the error and other mods I've installed with the mod.
The Error :

Mods installed with your mod :


Upgrade to SF3.4

Remove this warning:
Using Symfony\Component\Config\Definition\Builder\ArrayNodeDefinition::cannotBeEmpty() at path "nelmio_js_logger.allowed_levels" has no effect, consider requiresAtLeastOneElement() instead. In 4.0 both methods will behave the same.

Just to be sure: have you considered using requiresAtLeastOneElement() instead? Or isn't that necessary?

@stephanvierkant  i think it is not necessary, since there is a default value.

I'm not so sure if the default value is enough, what if you define the value but as an empty array? like allowed_levels: [], then the validation wouldn't catch the problem. I think requiresAtLeastOneElement should be used.


feat: returning non-nullified messages only

Fixes #3976

#5390  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @benesjan and the rest of your teammates on  Graphite

Docs Preview
Hey there! 👋 You can check your preview at https://65fdd662fb849b5026c1255b--aztec-docs-dev.netlify.app

Benchmark results
Metrics with a significant change:

note_trial_decrypting_time_in_ms (64): 99.0 (+108%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 4c565367 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
676
676
676

l1_rollup_calldata_gas
6,412
6,412
6,424

l1_rollup_execution_gas
585,745
585,745
585,757

l2_block_processing_time_in_ms
1,283
4,658
9,022

note_successful_decrypting_time_in_ms
194 (+10%)
522 (+7%)
970 (-5%)

note_trial_decrypting_time_in_ms
101 (+26%)
39.5 (-63%)
:warning: 99.0 (+108%)

l2_block_building_time_in_ms
17,234
64,867
128,998

l2_block_rollup_simulation_time_in_ms
7,908
27,981 (-1%)
55,529

l2_block_public_tx_process_time_in_ms
9,301
36,832 (+1%)
73,368

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
14,345 (+1%)
26,077 (-1%)

note_history_successful_decrypting_time_in_ms
1,218 (-4%)
2,541 (+4%)

note_history_trial_decrypting_time_in_ms
61.7 (-40%)
140 (-10%)

node_database_size_in_bytes
18,612,304
35,094,608

pxe_database_size_in_bytes
29,859
59,414

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
242
44,377
28,214

private-kernel-ordering
214
52,880
14,296

base-parity
4,451 (-4%)
128
311

root-parity
1,620 (-3%)
1,244
311

base-rollup
17,976
165,760
861

root-rollup
51.1 (+3%)
4,359
725

private-kernel-inner
602
73,794
28,214

public-kernel-app-logic
399 (-1%)
35,251
28,217

public-kernel-tail
174
40,928
28,217

merge-rollup
8.19 (-8%)
2,568
861

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.1 (+1%)
16.1 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.586 (+1%)
0.498 (+1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
45.7
71.8 (-1%)
236 (+3%)
446 (+1%)
861
1,709
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
96.0
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.470
0.444 (-1%)
0.431 (+3%)
0.417 (+1%)
0.411
0.410
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
55.6 (+4%)
106 (-1%)
334
660 (+1%)
1,284 (-1%)
2,598
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
104
207
691
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.496 (+4%)
0.479
0.456
0.455 (+1%)
0.446 (-1%)
0.453
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
61.0

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
109

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.535

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes

tx_size_in_bytes
22,024

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes

tx_pxe_processing_time_ms
3,152 (-1%)
1,663

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
10.7 (-2%)
1,149


Refactor schemas

With this PR:

update status codes and returned response objects for POST and DELETE operations (#42, #43, #51)
suggest which properties to be required among the established entities (#45)
reformat examples to be at the object-level rather than property level (#46)
add new *CreateRequest schemas for POST operations (#44)

With respect to the examples, I looked into whether the schemas should use examples at the property- or object-level, as well as in an external file. I didn't like the property-level examples as it made maintaining a little more tedious (especially if the schema has numerous properties that would need updating); using the object-level approach made it so that all of the example values was in one general area of the schema, which is preferable to me. As for object-level vs externalValue, because the example values can be specified in YAML format, I ultimately did not go for the latter option to keep things more simplistic. I can see an argument for external examples however, so happy to discuss more.
As for the *CreateRequest schemas, I had only created them for the Challenge, Grant, and Person entities; I did not see a purpose for Organization* or Tag* (since the user will be creating the ID). I also did not rename the original entities to *CreateResponse as I prefer the former. In my opinion, Challenge is more descriptive than ChallengeCreateReponse.
Note: to be merged after #52

@tschaffter ready for review! I have made the following changes to the refactor:

move parameter "schemas", e.g. ChallengeId.yaml, TagId.yaml, to a new parameters/ folder, much like what is done in nlpsandbox
create new response schemas for the POST operations; now, a JSON object containing the entity ID is returned rather than a string
update the $ref paths in the relative schemas/ and paths/ YAML files

For update # 2 (new response schemas), I debated between two directory structures:

having them in the schemas/ folder where the names are *CreateResponse.yaml
having them in the responses/ folder where the names are *Response.yaml

I went with the second approach, because I figured all the response schemas can be in one place. I don't care too much about the naming conventions -- I just went with the one that saved me some typing :-) But happy to go with *CreateResponse.yaml to keep things consistent with the *CreateRequest schemas!

@tschaffter ready for review! I have made the following changes to the refactor:

move parameter "schemas", e.g. ChallengeId.yaml, TagId.yaml, to a new parameters/ folder, much like what is done in nlpsandbox
create new response schemas for the POST operations; now, a JSON object containing the entity ID is returned rather than a string
update the $ref paths in the relative schemas/ and paths/ YAML files

For update # 2 (new response schemas), I debated between two directory structures:

having them in the schemas/ folder where the names are *CreateResponse.yaml
having them in the responses/ folder where the names are *Response.yaml

I went with the second approach, because I figured all the response schemas can be in one place. I don't care too much about the naming conventions -- I just went with the one that saved me some typing :-) But happy to go with *CreateResponse.yaml to keep things consistent with the *CreateRequest schemas!

@tschaffter Okay, NOW officially ready for review :laughing:
As mentioned, #52 is closed as changes there are also found here (so no need to review the other). Main description of the PR has been updated, but for convenience, updates implemented are:

update status codes and response objects for POST and DELETE operations, e.g. JSON object containing just the entity ID and empty JSON object, respectively
suggest which properties to be required among the established entities
reformat examples to be at the object-level rather than property level
add new *CreateRequest and *CreateResponse schemas for POST operations (to tackle the readOnly issue experienced with the openapi generator)

Also for convenience, updates to the docs page are as expected:

@tschaffter Okay, NOW officially ready for review :laughing:
As mentioned, #52 is closed as changes there are also found here (so no need to review the other). Main description of the PR has been updated, but for convenience, updates implemented are:

update status codes and response objects for POST and DELETE operations, e.g. JSON object containing just the entity ID and empty JSON object, respectively
suggest which properties to be required among the established entities
reformat examples to be at the object-level rather than property level
add new *CreateRequest and *CreateResponse schemas for POST operations (to tackle the readOnly issue experienced with the openapi generator)

Also for convenience, updates to the docs page are as expected:

As for the CreateRequest schemas, I had only created them for the Challenge, Grant, and Person entities; I did not see a purpose for Organization or Tag* (since the user will be creating the ID).

I think that consistency is more important here than not returning a piece of information because the client has passed it as input. This consistency calls for returning 201, which means that we return a reference to the created entity, whether this reference has been passed by the client itself or has been generated by the service.

I also did not rename the original entities to *CreateResponse as I prefer the former. In my opinion, Challenge is more descriptive than ChallengeCreateReponse.

The idea is not to rename the original entities. For example, Challenge and ChallengeCreateResponse are meant to be different:

Challenge: the entire challenge object as returned by getChallenge and listChallenges
ChallengeCreateResponse: used on to return the POST response, which is an object with a single property that is the reference to the created entity.

As for the CreateRequest schemas, I had only created them for the Challenge, Grant, and Person entities; I did not see a purpose for Organization or Tag* (since the user will be creating the ID).

I think that consistency is more important here than not returning a piece of information because the client has passed it as input. This consistency calls for returning 201, which means that we return a reference to the created entity, whether this reference has been passed by the client itself or has been generated by the service.

I also did not rename the original entities to *CreateResponse as I prefer the former. In my opinion, Challenge is more descriptive than ChallengeCreateReponse.

The idea is not to rename the original entities. For example, Challenge and ChallengeCreateResponse are meant to be different:

Challenge: the entire challenge object as returned by getChallenge and listChallenges
ChallengeCreateResponse: used on to return the POST response, which is an object with a single property that is the reference to the created entity.

I went with the second approach, because I figured all the response schemas can be in one place.

For future references, Verena and I have decided to keep the folder components/responses/ for true OpenAPI response objects. Schema objects <resource>CreateRequest and <resource>CreateResponse are placed in components/schemas. For now we don't use sub-folders because components/schemas/responses/ may be ill defined. Sub-folders have definitively their place in the future, but a naming convention should be adopted first.

I went with the second approach, because I figured all the response schemas can be in one place.

For future references, Verena and I have decided to keep the folder components/responses/ for true OpenAPI response objects. Schema objects <resource>CreateRequest and <resource>CreateResponse are placed in components/schemas. For now we don't use sub-folders because components/schemas/responses/ may be ill defined. Sub-folders have definitively their place in the future, but a naming convention should be adopted first.

The idea is not to rename the original entities. For example, Challenge and ChallengeCreateResponse are meant to be different
Sorry, I should've updated my comments.  After working with the schemas a bit, I understood the purpose of all the various schemas per entity, e.g. Challenge vs ChallengeCreateResponse vs ChallengeCreateRequest

The idea is not to rename the original entities. For example, Challenge and ChallengeCreateResponse are meant to be different
Sorry, I should've updated my comments.  After working with the schemas a bit, I understood the purpose of all the various schemas per entity, e.g. Challenge vs ChallengeCreateResponse vs ChallengeCreateRequest

I think that consistency is more important here than not returning a piece of information because the client has passed it as input. This consistency calls for returning 201, which means that we return a reference to the created entity...

Just wanted to clarify --
Organization and Tag do have a corresponding *CreateResponse object (what is being returned with 201)... I didn't, however, create a corresponding *CreateRequest object, as I found it redundant with the original schema.

I think that consistency is more important here than not returning a piece of information because the client has passed it as input. This consistency calls for returning 201, which means that we return a reference to the created entity...

Just wanted to clarify --
Organization and Tag do have a corresponding *CreateResponse object (what is being returned with 201)... I didn't, however, create a corresponding *CreateRequest object, as I found it redundant with the original schema.

Organization and Tag do have a corresponding *CreateResponse object (what is being returned with 201). I didn't, however, create a corresponding *CreateRequest object for them

The schemas Challenge and ChallengeCreateRequest would indeed be similar but still different: Challenge has an ID while ChallengeCreateRequest don't. The OpenAPI way to solve this is to use readOnly for the ID property, but OpenAPI currently does not support readOnly with $ref properties. This will change in the next OpenAPI release. Meanwhile, the solution proposed is to have Challenge and ChallengeCreateRequest. The duplication of code is not ideal but this brings two benefits:

The documentation is more clear as the request body schema does not include the ID property included in the schema Challenge
Defining systematically <resource>CreateRequest and <resource>CreateResspone for POST requests increases the consistency of our APIs

We will revise this design once OpenAPI supports readOnly with $ref.

Organization and Tag do have a corresponding *CreateResponse object (what is being returned with 201). I didn't, however, create a corresponding *CreateRequest object for them

The schemas Challenge and ChallengeCreateRequest would indeed be similar but still different: Challenge has an ID while ChallengeCreateRequest don't. The OpenAPI way to solve this is to use readOnly for the ID property, but OpenAPI currently does not support readOnly with $ref properties. This will change in the next OpenAPI release. Meanwhile, the solution proposed is to have Challenge and ChallengeCreateRequest. The duplication of code is not ideal but this brings two benefits:

The documentation is more clear as the request body schema does not include the ID property included in the schema Challenge
Defining systematically <resource>CreateRequest and <resource>CreateResspone for POST requests increases the consistency of our APIs

We will revise this design once OpenAPI supports readOnly with $ref.

We will revise this design once OpenAPI supports readOnly with $ref. Meanwhile, I recommend preferring documentation clarity to limited code duplication.

By support, do you mean that the generator will also generate flask files that will take into account the read-only (and write-only) property? Because if not, then we will probably continue having the same issue as we do now (so not sure if it'd be worth exploring).
Case in point:
Last week, I explored to see whether we could add readOnly to the parameter schemas and if it'll work all the way through to the server-side. (I know we wouldn't move forward with this plan, since we don't want the actual parameter to be read-only, just the reference to it in the schema). From the docs side, everything is working as expected, e.g. *ID does not show up in the request body for POST:

But when generating the server files, we hit the same problem as before, where *ID is shown as expected in the request body example.  At least it does return a "read only" error if the user just submits the example as-is :grimacing: :

The schemas Challenge and ChallengeCreateRequest would indeed be similar but still different: Challenge has an ID while ChallengeCreateRequest don't.

Yes, I understand this. But with Organization and Tag, users are creating the IDs for these entities, not the database.  If consistency is the key (as in, OrganizationCreateRequest and TagCreateRequest should be created so that their POST request bodies are the same as Challenge, Grant, and Person), couldn't we also argue that the paths should follow the same structure, e.g.

current Challenge request URL: /api/v1/challenges
current Tag request URL: /api/v1/tags?tagId=awesome-tag

I guess we'll just have to decide which of the things we want to keep consistent? The request bodies or the paths.

We will revise this design once OpenAPI supports readOnly with $ref. Meanwhile, I recommend preferring documentation clarity to limited code duplication.

By support, do you mean that the generator will also generate flask files that will take into account the read-only (and write-only) property? Because if not, then we will probably continue having the same issue as we do now (so not sure if it'd be worth exploring).
Case in point:
Last week, I explored to see whether we could add readOnly to the parameter schemas and if it'll work all the way through to the server-side. (I know we wouldn't move forward with this plan, since we don't want the actual parameter to be read-only, just the reference to it in the schema). From the docs side, everything is working as expected, e.g. *ID does not show up in the request body for POST:

But when generating the server files, we hit the same problem as before, where *ID is shown as expected in the request body example.  At least it does return a "read only" error if the user just submits the example as-is :grimacing: :

The schemas Challenge and ChallengeCreateRequest would indeed be similar but still different: Challenge has an ID while ChallengeCreateRequest don't.

Yes, I understand this. But with Organization and Tag, users are creating the IDs for these entities, not the database.  If consistency is the key (as in, OrganizationCreateRequest and TagCreateRequest should be created so that their POST request bodies are the same as Challenge, Grant, and Person), couldn't we also argue that the paths should follow the same structure, e.g.

current Challenge request URL: /api/v1/challenges
current Tag request URL: /api/v1/tags?tagId=awesome-tag

I guess we'll just have to decide which of the things we want to keep consistent? The request bodies or the paths.

^^^ That all being said, I think I would prefer having consistent request bodies after all :sweat_smile:

^^^ That all being said, I think I would prefer having consistent request bodies after all :sweat_smile:

By support, do you mean that the generator will also generate flask files that will take into account the read-only (and write-only) property? Because if not, then we will probably continue having the same issue as we do now (so not sure if it'd be worth exploring).

You're right.

From the docs side, everything is working as expected, e.g. *ID does not show up in the request body for POST:

Yes, the redocli HTML documentation is usually right on spot and show what we expect.

But when generating the server files, we hit the same problem as before, where *ID is shown as expected in the request body example. At least it does return a "read only" error if the user just submits the example as-is 😬 :

One of the current main aim is for the user to be able to POST the example request body without getting on error from the backend (user friendliness +1). As a reminder, there are two components to this issue:

The documentation UI ignores readOnly when generating the example request body. This makes the documentation confusing.
The connexion package used to run the server throws a 400 error when specifying a property that is marked as readOnly. This behavior is being discussed in this connexion ticket. According to the author of the ticket, this is not compliant with the OpenAPI spec that says (ref):

Relevant only for Schema "properties" definitions. Declares the property as "read only". This means that it MAY be sent as part of a response but SHOULD NOT be sent as part of the request. If the property is marked as readOnly being true and is in the required list, the required will take effect on the response only. A property MUST NOT be marked as both readOnly and writeOnly being true. Default value is false.

Note the "SHOULD NOT" (=> should be warning/ignore) and not "MUST NOT" (ground for error).
The issue we could face could be solved by either 1) fixing the generation of the example request body or 2) having connexion not throwing an error when readOnly properties are specified.
@vpchung I'm wondering if we have enough control aver the examples to fix 1). For example, most of my tests have been made when I specified the example at the level of the schema property. Do you know if specifying the example at the schema level can solve 1), i.e. by not including in the example value for readOnly property? Actually, this would bring another issue because the example would not be correct for response payload that do need to show an example for readOnly value. An alternative could be to specify different examples in different files, and important the example at the path level. This may work but may be more trouble than it's worth.
That was basically my reasoning to go to the current design with different schemas for POST requests and responses.

By support, do you mean that the generator will also generate flask files that will take into account the read-only (and write-only) property? Because if not, then we will probably continue having the same issue as we do now (so not sure if it'd be worth exploring).

You're right.

From the docs side, everything is working as expected, e.g. *ID does not show up in the request body for POST:

Yes, the redocli HTML documentation is usually right on spot and show what we expect.

But when generating the server files, we hit the same problem as before, where *ID is shown as expected in the request body example. At least it does return a "read only" error if the user just submits the example as-is 😬 :

One of the current main aim is for the user to be able to POST the example request body without getting on error from the backend (user friendliness +1). As a reminder, there are two components to this issue:

The documentation UI ignores readOnly when generating the example request body. This makes the documentation confusing.
The connexion package used to run the server throws a 400 error when specifying a property that is marked as readOnly. This behavior is being discussed in this connexion ticket. According to the author of the ticket, this is not compliant with the OpenAPI spec that says (ref):

Relevant only for Schema "properties" definitions. Declares the property as "read only". This means that it MAY be sent as part of a response but SHOULD NOT be sent as part of the request. If the property is marked as readOnly being true and is in the required list, the required will take effect on the response only. A property MUST NOT be marked as both readOnly and writeOnly being true. Default value is false.

Note the "SHOULD NOT" (=> should be warning/ignore) and not "MUST NOT" (ground for error).
The issue we could face could be solved by either 1) fixing the generation of the example request body or 2) having connexion not throwing an error when readOnly properties are specified.
@vpchung I'm wondering if we have enough control aver the examples to fix 1). For example, most of my tests have been made when I specified the example at the level of the schema property. Do you know if specifying the example at the schema level can solve 1), i.e. by not including in the example value for readOnly property? Actually, this would bring another issue because the example would not be correct for response payload that do need to show an example for readOnly value. An alternative could be to specify different examples in different files, and important the example at the path level. This may work but may be more trouble than it's worth.
That was basically my reasoning to go to the current design with different schemas for POST requests and responses.

That was basically my reasoning to go to the current design with different schemas for POST requests and responses.

Oh, I'm not at all saying that I'm against this approach of having multiple schemas per entity, e.g. Challenge, ChallengeCreateRequest, and ChallengeCreateResponse. For our current situation, they completely make sense and definitely work as intended. When testing on the server side, it all looks good:

My original comment here:
As for the *CreateRequest schemas, I had only created them for the Challenge, Grant, and Person entities; I did not see a purpose for OrganizationCreateRequest or TagCreateRequest
...was just to elucidate why I did not create the *CreateRequest schemas for those two entities (since I thought it'd be redundant), not that I was against making them.

That was basically my reasoning to go to the current design with different schemas for POST requests and responses.

Oh, I'm not at all saying that I'm against this approach of having multiple schemas per entity, e.g. Challenge, ChallengeCreateRequest, and ChallengeCreateResponse. For our current situation, they completely make sense and definitely work as intended. When testing on the server side, it all looks good:

My original comment here:
As for the *CreateRequest schemas, I had only created them for the Challenge, Grant, and Person entities; I did not see a purpose for OrganizationCreateRequest or TagCreateRequest
...was just to elucidate why I did not create the *CreateRequest schemas for those two entities (since I thought it'd be redundant), not that I was against making them.

@tschaffter two final schemas added -- now the PR is officially ready for the review... officially

:-)

@tschaffter two final schemas added -- now the PR is officially ready for the review... officially

:-)


use steamlink instead of linux-steamlink due to differences

this goes together with bgfx changes

It's intentionally "linux-steamlink"... Changes are minimal, and I want to be able to use linux-* instead specifying steamlink everywhere.


[Community Post]:  Baserow and Appsmith integration using JWT

Is there an existing issue for this?

[X] I have searched the existing issues

Engineering Ticket Link
NA
Release Date
NA
Release Number
NA
First Draft
No response
Loom video
No response
Discord/slack/intercom Link if needed
No response
PRD
No response
Test plan/cases
No response
Use cases or user requests
No response

Published


ffmpeg issues on raspberry

I have successfully installed dizquetv on the raspberry. Unfortunately the playback in VLC does not start. I have already tried 3 different ffmpeg versions. Only with one did the VLC show the dizque channel logo followed by an error message. On the Raspberry it shows ffmpeg error 1.
How can I get it to work? Which ffmpeg version do I need? (Raspberry Pi 4)

Did you try the tutorial in the wiki?

https://github.com/vexorian/dizquetv/wiki/Raspberry-guide

No, I have not seen that. I will try that now. Thanks

Followed it completely and now get this error:
Error getting ffmpeg version Error: Command failed: "/usr/bin/ffmpeg" -version
/bin/sh: 1: /usr/bin/ffmpeg: not found

I followed this guide and have the same issue (This stream is facing technical issues. Try again later."

Stream starting. Channel: 1 (Channel 1)
=========================================================
! Start playback
! Channel: Channel 1 (1)
! Title: Unknown
! From : 0 to: 40
=========================================================
About to play loading stream

Video and Audio are being transcoded by ffmpeg
Client Closed
Stream FFMPEG exited normally.
! Start playback
! Channel: Channel 1 (1)
! Title: ARD Ratgeber Technik, ca 1997
! From : 405410 to: 580960
About to play plex stream
Plex transcoder initiated
Debug logging enabled
Getting stream
deinterlace:     true
streamPath:      plex
Setting transcoding parameters
Recieved transcode decision:
{
MediaContainer: {
size: 1,
allowSync: '1',
directPlayDecisionCode: 3000,
directPlayDecisionText: 'App cannot direct play this item. Direct play is disabled.',
generalDecisionCode: 1001,
generalDecisionText: 'Direct play not available; Conversion OK.',
identifier: 'com.plexapp.plugins.library',
librarySectionID: '3',
librarySectionTitle: 'Retro',
librarySectionUUID: 'f25e245a-fcad-4698-a8c5-12a2290fe924',
mediaTagPrefix: '/system/bundle/media/flags/',
mediaTagVersion: '1634922505',
transcodeDecisionCode: 1001,
transcodeDecisionText: 'Direct play not available; Conversion OK.',
Metadata: [ [Object] ]
}
}
Current video stats:
{
duration: 580960,
anamorphic: false,
pixelP: 1,
pixelQ: 1,
videoCodec: 'h264',
videoWidth: 1920,
videoHeight: 1080,
videoFramerate: 25,
videoDecision: 'copy',
audioChannels: 2,
audioCodec: 'aac',
audioDecision: 'copy'
}
Current video stats:
{
duration: 580960,
anamorphic: false,
pixelP: 1,
pixelQ: 1,
videoCodec: 'h264',
videoWidth: 1920,
videoHeight: 1080,
videoFramerate: 25,
videoDecision: 'copy',
audioChannels: 2,
audioCodec: 'aac',
audioDecision: 'copy'
}
Direct play forced or native paths enabled
Recieved transcode decision:
{
MediaContainer: {
size: 1,
allowSync: '1',
identifier: 'com.plexapp.plugins.library',
librarySectionID: '3',
librarySectionTitle: 'Retro',
librarySectionUUID: 'f25e245a-fcad-4698-a8c5-12a2290fe924',
mdeDecisionCode: 1000,
mdeDecisionText: 'Direct play OK.',
mediaTagPrefix: '/system/bundle/media/flags/',
mediaTagVersion: '1634922505',
Metadata: [ [Object] ]
}
}
Current video stats:
{
duration: 580960,
anamorphic: false,
pixelP: 1,
pixelQ: 1,
videoCodec: 'h264',
videoWidth: 1920,
videoHeight: 1080,
videoFramerate: 25,
videoDecision: 'copy',
audioChannels: 2,
audioCodec: 'aac',
audioDecision: 'copy'
}
{
MediaContainer: {
size: 1,
allowSync: true,
identifier: 'com.plexapp.plugins.library',
librarySectionID: 3,
librarySectionTitle: 'Retro',
librarySectionUUID: 'f25e245a-fcad-4698-a8c5-12a2290fe924',
mediaTagPrefix: '/system/bundle/media/flags/',
mediaTagVersion:<PHONE_NUMBER>,
Metadata: [ [Object] ]
}
}
Found audio index: 1
{
directPlay: true,
streamUrl: 'https://94-134-58-173.0e19c8ae1ebe4ddebad9864dca8aa821.plex.direct:54791/library/parts/10638/1615493428/file.mp4?X-Plex-Token=VPTmmsy5bPGxVVXr3xzz',
streamStats: {
duration: 580960,
anamorphic: false,
pixelP: 1,
pixelQ: 1,
videoCodec: 'h264',
videoWidth: 1920,
videoHeight: 1080,
videoFramerate: 25,
videoDecision: 'copy',
audioChannels: 2,
audioCodec: 'aac',
audioDecision: 'copy',
audioIndex: 1
}
}
Video and Audio are being transcoded by ffmpeg
Stream FFMPEG exited with code 1.
Replacing failed stream with error streram
Video and Audio are being transcoded by ffmpeg

https protocol not found, recompile FFmpeg with openssl, gnutls or securetransport enabled.
https://94-134-58-173.0e19c8ae1ebe4ddebad9864dca8aa821.plex.direct:54791/library/parts/10550/1575071924/file.mp4?X-Plex-Token=VPTmmsy5bPGxVVXr3xzz: Protocol not found
Did you mean file:https://94-134-58-173.0e19c8ae1ebe4ddebad9864dca8aa821.plex.direct:54791/library/parts/10550/1575071924/file.mp4?X-Plex-Token=VPTmmsy5bPGxVVXr3xzz?
Stream FFMPEG exited with code 1.


Typo in Projection.LonLat.js doc.

In Projection.LonLat.js documentation, says it is used in EPSG:3395, while it is really used in EPSG:4326. It appears also in leaflet reference webpage.

Thanks for noticing this!


Created separate folder for Leetcode questions and DSA questions

Hi @kishanrajput23 ,
I have created a separate folder for DSA and Leetcode questions and added two solutions as well for Dijkastra and Binary Search.
Thanks!


Handle x nullable for enums

I've noticed that enums don't work very well with x-nullable=True. I had to include null/None as an enum value for the validation to pass, but that combo of x-nullable and enum value does not work with swagger-ui.
So I suggest this change.

Hi
Could I get some feedback on this? It would be much appreciated
Thank you

I'm hesitant to add this, at least as a feature that's enabled by default.
My reasoning is that IIUC x-nullable is not part of the core spec, and is more of a convention.  Assuming that is correct, it strikes me that this feature should require explicit opt-in using something like an environment variable or configuration flag.
Thoughts?

From a user perspective I think that if I specify both x-nullable=True and enum=[x, y, z], I'm pretty explicit about null being an expected value. This does not add unexpected behaviour to an enum field, but makes the x-nullable extension apply correctly to enums (In my opinion)
However: I see your point about it not being in the core spec and you are the one who will have do deal with questions from users about this behaviour. So if you still think it should be disabled by default I suggest an environment variable X_NULLABLE_ENUMS or similar.

Good feedback :) Thanks!


Can't pickle fuction objects ray error

System information

Ubuntu 18
0.11.2
3.7.1
Code we can use to reproduce:

Python 3.7.1 (default, Oct 26 2021, 13:26:12)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import modin.pandas  as pd
>>> import os
>>> os.environ['MODIN_ENGINE'] = 'ray'
>>> pd.read_csv('tests/googleplaystore.csv')
UserWarning: Ray execution environment not yet initialized. Initializing...
To remove this warning, run the following python code before doing dataframe operations:

    import ray
    ray.init()

UserWarning: The size of /dev/shm is too small<PHONE_NUMBER> bytes). The required size at least half of RAM<PHONE_NUMBER> bytes). Please, delete files in /dev/shm or increase size of /dev/shm with --shm-size in Docker. Also, you can set the required memory size for each Ray worker in bytes to MODIN_MEMORY environment variable.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/boris/.pyenv/versions/3.7.1/lib/python3.7/site-packages/modin/pandas/io.py", line 135, in read_csv
    return _read(**kwargs)
 ...
  File "/home/boris/.pyenv/versions/3.7.1/lib/python3.7/site-packages/ray/pickle5_files/pickle5/pickle.py", line 576, in save
    rv = reduce(self.proto)
TypeError: can't pickle function objects
>>>

Describe the problem
When using the ray engine, an attempt to read a file from disk causes errors. This does not happen on dask.
 Would you be able to tell @rkooo567 more about your execution environment in order for he could reproduce the error to fix it in Ray?

I created an issue in Ray github:
https://github.com/ray-project/ray/issues/19938

Closing this issue since we have the issue in Ray github to track the problem. Feel free to reopen it if something goes wrong on Modin side.


How do I remove the shadow of the click

How do I remove the shadow of the click. I don't want this effect


"Child already has a owner, it must be removed first. "  How to remove owner?

Report

[ ] I have searched Child already has a owner, it must be removed first and this is not a duplicate

Issues and Steps to Reproduce
1 . create view1 and subview1
2. hold subview1 with viewcontroller
3. add subview1 to view1 and config layout
4. delay some time
5. create view2
6. add subview1 to view2 and config layout
Expected Behavior
show me Child already has a owner, it must be removed first
Can i remove subview1's owner

You can use removeChildAt
and then addChildAt APIs on YogaNode object if you are using Java APIs
Calling removeChildAt on view1 will remove the owner of subview1 and then it can be added to any other view.

Closing this.

I get the same issue on Swift version.
For now, Yoga (wrapped by swift) don't provide any way to remove owner (no way to removeChildAt or addChildAt)
Thank you very much.

Same issue.

Not sure the api is exactly the same, but in the standalone js version you can remove the child from the parent with getParent and then removeChild (given that you have a reference to the child node). See https://github.com/facebook/yoga/blob/64e245942786227b2f97ccfa5c30ce5c4fd62d79/javascript/sources/entry-common.js#L123

Swift +1
so how to remove owner?

In swift, I think this error happens if you remove a view from superview and add the view to another. To remove the owner use this:
        let superview = theView.superview
        theView.removeFromSuperview()
        superview?.yoga.applyLayout(preservingOrigin: false)


Missing proj ID on Get results in unauthorized

From another ticket:
Fetching a rule with a missing rule ID gets a nice validation error
[42][default:/src:0]# curl -kH "api-token: $TOK" https://a2-dev.test/apis/iam/v2/projects/neato/rules/ | jq
{
  "error": "a rule id is required and must contain at least one non-whitespace character",
  "code": 3,
  "message": "a rule id is required and must contain at least one non-whitespace character",
  "details": []
}

But fetching a project with a missing ID gets this error that's a bit of a red herring:
[47][default:/src:0]# curl -kH "api-token: $TOK" https://a2-dev.test/apis/iam/v2/projects/ | jq
{
  "error": "error authorizing action \"iam:projects:get\" on resource \"iam:projects:\" filtered by projects [] for members [\"token:admin-token-1586543035\"]: rpc error: code = InvalidArgument desc = invalid ProjectsAuthorizedReq.Resource: value does not match regex pattern \"^[a-z][^:*]*(?::[^:*]+)*$\"",
  "code": 7,
  "message": "error authorizing action \"iam:projects:get\" on resource \"iam:projects:\" filtered by projects [] for members [\"token:admin-token-1586543035\"]: rpc error: code = InvalidArgument desc = invalid ProjectsAuthorizedReq.Resource: value does not match regex pattern \"^[a-z][^:*]*(?::[^:*]+)*$\"",
  "details": []
}

This is getting at a core design issue in the gateway middleware: any field that is needed to create the resource and action pair for the IsAuthorized call must be enforced as required at the proto validation level. Without any required validation, IsAuthorized does catch the error, but it provides a misleading message.
The problem is there is no easy required validator we can use. The closest approximate min_length = 1 results in a weird error message about "runes". We could use a regex validator but that seems excessive for something like a Get request.
One solution would be to use the min_length validator (or maybe some other combo of validators) and wrap the error in our own message before sending it back to the user.
Ideally this solution should be implemented across our APIs.

Some alternatives to fix this, I think, are

Creating out own PGV-compatible message validation in the gateway. I.e. for CreatePolicyRequest, we'd define func (r *CreatePolicyRequest) Validate() error, and opporunistically call that from the gateway middleware.
We'd control the error messages. The validation wouldn't be proto-driven.

Since only the fields required for the authorization check matter in the gateway (architectural concerns aside!), we could enhance the generated code that does the lookup of those fields. When it encounters "", it could return an error instead of constructing what ends up being an invalid resource identifier.

I think both of these are similarly low-effort.

this work has been deprioritized.


Synapse on kubernetes : other installation methods ?

Until now we are using the following helm chart to install synapse on kubernetes :
https://gitlab.com/ananace/charts/-/tree/master/charts/matrix-synapse
Other solutions exists :

a fork of this chart, made by gematik : https://gitlab.opencode.de/bwi/bundesmessenger/backend/helm-chart
another chart made by Matthias Goerens : https://github.com/mgoerens/matrix-chart
an operator (alpha stade) made by Matthias Goerens : https://operatorhub.io/operator/synapse-operator / https://github.com/opdev/synapse-operator

It may be interesting to study this other solutions and see if they are more relevant than the one we use.
What about the scaling of a worker ?

Matrix just released their own Matrix operator  : https://github.com/vector-im/ess-starter-edition-core


⚠ AZ-Launcher has degraded performance

In 3175d2d, AZ-Launcher (https://az-launcher.nz/) experienced degraded performance:

HTTP code: 200
Response time: 2154 ms

Resolved: AZ-Launcher performance has improved in 7e5ed84 after 2 hours, 45 minutes.


Update changelog along with dependency

Hi,
thanks for a extremely useful service. It could be even better, though :) I would love for scala steward to automatically make a note about what it did into changelog. The idea is you could configure file in a repo and inside it put a line with some place holder values like {scala-steward-original-version} and {scala-steward-updated-version} and when SS creates PR, it not just updates build.sbt, but also copies this line and into one of those copies puts actual values.
What do you think?
Thanks!

Thanks for the suggestion, @tomasherman! I feel that tools that are specialized for creating release notes or changelogs from issues or PRs like gren or release-drafter are better suited to do this task. I'm reluctant to include features that are somewhat orthogonal to what Scala Steward does or which are not Scala specific.

ok, fair enough ;)


GitHub Description

Try to change the description of this GitHub repository.

I changed the description

Ugh... there was a little pencil on my end!


Upgrade to nextjs 13's new app router

Is your feature request related to a problem? Please describe.
There's currently a lot of duplicated code for different types of page layouts. It would be nice to take advantage of the new and shiny features in Nextjs 13.2 (App router and react server components).
Describe the solution you'd like
Migrate the whole code to the new app router, so it can also implement server components.

Hi there @karlhorky, I spent some time working on this and I'd say it's almost done rn. The thing I need to verify is the static pregeneration generation. I remember this wasn't working 100%.
But I can look at it later today. But this shouldn't be a problem as the live site is hosted here.
Do you need this rn?

No rush on it, definitely!
Thanks for your continued hard work here! ❤

No problems @karlhorky, glad it was useful to you ♥

@vickonrails Oh great, is the migration to the App Router complete now that PR #19 was merged? 🙌  I'll give it a shot!


Update developer guide with borrow command implementation

Coverage remained the same at 92.202% when pulling 8915f880503dbcfcd60f4383d0e44a990f875574 on jelneo:update_developer_guide into 563ab0bef3107fcac61a4e2f7a2455da1d4b4cde on CS2103AUG2017-T17-B1:master.

Coverage increased (+0.07%) to 92.269% when pulling 84ab97dea382decbeced1f4daa6e1bb782c76ad8 on jelneo:update_developer_guide into 563ab0bef3107fcac61a4e2f7a2455da1d4b4cde on CS2103AUG2017-T17-B1:master.

Coverage increased (+0.07%) to 92.269% when pulling 6a2bb1abc0a420b30483ef0da0be837b0a2d09e9 on jelneo:update_developer_guide into 563ab0bef3107fcac61a4e2f7a2455da1d4b4cde on CS2103AUG2017-T17-B1:master.

Coverage decreased (-0.2%) to 92.033% when pulling b498b1f99169de506b2d4bb4e661444371d78a87 on jelneo:update_developer_guide into 563ab0bef3107fcac61a4e2f7a2455da1d4b4cde on CS2103AUG2017-T17-B1:master.


How to replace key and value using Request Transfromer?

Summary
If at body request have code:12345 than will transform to cnl:QUERY/19, id:01, name:jhon
and if te body havevalue code:67890 than will transfrom to cnl:QUERY/20, id:02, name:jenny
before I created it using the add body it's works but it is static only for code:12345. Is it possible to make it dynamacally?
Tried to search over documents but I can't found about replace example for Request Transformer plugin
Steps To Reproduce

Add replace on body in the request-transformer plugin

For example:
Request body :
{
    "code": 12345
}

will transform to:
{
	"cnl": QUERY/19,
	"id": 01,
	"name": jhon
}

And if request body:
{
    "code": 67890
}

will transform to:
{
	"cnl": QUERY/20,
	"id": 02,
	"name": jenny
}

Additional Details & Logs

Kong version ($ kong version)
Kong debug-level startup logs ($ kong start --vv)
Kong error logs (<KONG_PREFIX>/logs/error.log)
Kong configuration (the output of a GET request to Kong's Admin port - see
https://docs.konghq.com/latest/admin-api/#retrieve-node-information)
Operating system

Thanks,

tried using config.replace.body but still no luck

Solved!


GPU out of memory error

Hi,
I just ran the docker for feature extractor on COCO, but I hit an error saying out of memory:
/opt/butd//tools/../lib/rpn/proposal_layer.py:27: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.   layer_params = yaml.load(self.param_str)   0%|          | 0/82783 [00:00<?, ?it/s]WARNING: Logging before InitGoogleLogging() is written to STDERR F0829 23:53:49.776543   146 syncedmem.cpp:71] Check failed: error == cudaSuccess (2 vs. 0)  out of memory *** Check failure stack trace: *** Aborted root@eb7c95126dbc:/workspace/features#
It's weird because I'm watching my GPU and it only uses  ~ 2GB (out of 8GB). But it still throws me an out-of-memory error. It even happens when I set BATCH_SIZE to 2 in the config file. Any thought?

Hi,
Short Answer:
Please add these first two lines to faster_rcnn_end2end_resnet.yml under TEST:
TEST:
  SCALES: [300,]
  MAX_SIZE: 400
  HAS_RPN: True
  HAS_ATTRIBUTES: True
  HAS_RELATIONS: False
  SOFT_NMS: 0

Long Answer:
Faster R-CNN is single batched when testing, thus the batch size would not affect the memory usage. And it uses a large size of image (i.e., short edge >= 600, long edge <= 1000 instead of (224, 224) in ResNet) in order to capture small objects.
To save memory, the current solution I came up with is to reduce the size of the image. The first two lines are for this purpose.
More descriptions of the config file are here.
Hope it helps!

I tested it on NLVR2. It works with a little bit drop in the result.


Update 2016_02_10_181651_create_roles_tables.php

Fixes the migration issue #228. Rollback and refresh now work.

Great work thank you


make the project cmake-able, change is based on https://github.com/lo…

…gcabin/logcabin/pull/227

verified works locally.

wrong target repo


No more grid menus in all tutorials after last commit

Check any tutorial and no headers have their menus and sort indicators any longer

Duplicate of #3165.  The issue is that the fonts are broken.  This looks to be a build process issue, the same code built locally works fine.


Orphaned flows display blank instead on none

Changed line 27. Looking at flows in an environment in PPAC, orphaned flows seem to have blank in the owners column instead of none. This is for both enabled and disabled flows.

Learn Build status updates of commit 20b4a2d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

support/power-platform/power-automate/manage-orphan-flow-when-owner-leaves-org.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@tonglingchen, Hi Tom, can you help review the change request from @anttipajunen? Thanks a lot!

Learn Build status updates of commit e69fe4a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

support/power-platform/power-automate/manage-orphan-flow-when-owner-leaves-org.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

After research, according to the screenshot in the article https://powerusers.microsoft.com/t5/Building-Flows/How-to-identify-and-manage-flows-without-owners/td-p/732442, this minor change is OK to merge.


Update index-portalfx-extension-development.md

This is a case sensitive value, the link is broken if you don't match.

Link is fixed in the docs https://github.com/Azure/portaldocs/blob/master/portal-sdk/generated/index-portalfx-extension-development.md


Add requireHttps-Option

An automatic redirect to https with config-option was needed.
The option and the conditional redirect is implemented.

Thanks for contributing. Much appreciated!


WriteValue by handle

Hello.
TinyB library support write value by UUID.
But in my case one UUID hava many handle and value.
[CC:78:AB:6C:97:00][LE]> char-read-uuid  00002902-0000-1000-8000-00805f
handle: 0x001f   value: 00 00
handle: 0x0025   value: 00 00
handle: 0x002f   value: 00 00
handle: 0x003a   value: 00 00
handle: 0x004b   value: 00 00
So I can't send someting like
BluetoothGattService Service = sensor.find("Service UUID");
BluetoothGattCharacteristic config=Service.find("Characteristic UUID");
config.writeValue((byte)0x01);
so the tinyB library can send byte by handle ??
Like BluetoothGattCharacteristic config=Service.find("Handle");
Thankyou.

Not entirely sure how this works. I think you might need to write that value at an offset inside the array. This is currently not supported but not difficult to add. Best would be to ask the BlueZ maintainers about this. http://www.bluez.org/contact/


Feature/ada redeem

This PR introduces the ada redeem page where users that pre-purchased ada can upload their certificate and provide the token to redeem their ada into a selected wallet.

@darko-mijic this PR is now ready for final review!


Removal from list

Hey,
Sites forenom.com and forenom.fi don't send plain text passwords via email anymore when users reset their password. Instead the users are sent a link that can be used to change the password within a time limit.

Hello! I'm a developer at Subito.it and we would like to be moved to reformed offenders since we do not expose any kind of plaintext secret since many years. Thank You!

https://github.com/plaintextoffenders/plaintextoffenders/issues/18#issuecomment-966661445

@andreaciri, you should create a PR.


Documentation tool does not add escapes to code and codeblocks unnecessarily

Instead of adding the escapes to all * and _ the tool now excludes
the characters inside [code] and [codeblock].
Resolves: #15156

Thanks! I tried it locally and it works great.

What does the cherrypick label mean?

That it will be cherry-picked (backported) to the 3.0 branch.


Add ability to use 'replace' SQL operator in CM_Model_StorageAdapter_Database

We need for mechanism of atomic db changes to prevent race condition errors.
So we decided to implement one for Mysql adapter only yet, add new $options param to create() method and one available option will be 'useReplace'
As far as I understand create is used only from commit() method, so there are two options

To pass '$useReplace' param directly to commit()
To create whole model with this additional param (e.g pass to constructor).

@tomaszdurka , @njam  WDYT ?

How about adding $options also to commit() and passing it down to create()?
Then we can still override commit() in a specific model:
public function commit(array $options) {
 $options['replace'] = true;
 parent::commit($options);
}

sgtm

It's ready. I had to adjust some tests to add testing for replace operator.
@njam please review

@tomaszdurka could you review this?

Concept generally looks ok.
One thing though :) I am totally against passing arrays like this especially 2 levels down.
So either I would:

validate array and recreate it while passing to create method or
pass boolean replace

Additionally what about:

Adding interface for replace method
Implement that interface on database storage adapter
Read replace flag and check if storage adapter implements replace interface (throw otherwise)

@fvovan @njam wdyt?

I opt for validating array. Otherwise it would have few 'null' params when we decide to add more params.
But may be we will never add it...
And why we need to recreate it? If we validate array, we can assume it's safe.
Interface sounds good, maybe it is a bit overkill as well as $options array, because this interface will have only 1 implementation.
What should I extract for save()? i see that only $this->getType can be extracted there.

btw, should we throw during validation or just silently omit  $createOptions?

added Replaceable Interface and params validation
@tomaszdurka , @njam please review

If we keep replace as one of this bloody :) options array we need to validate it also inside create method. Otherwise you can pass there random things. If we keep current approach it's probably wise to move logic (validation, interface check) down into adapter... maybe. But then we end up with params not validated on abstract level. We could move it to abstract adapter.
What about keeping it super-simple for now with replace as flag? I know having options might be easier for adding extra options later on - as there will be no need to convert boolean usages into arrays. But all these options will be mostly for different things and most-likely never used in combination.
It will simplify code so much:

no need for validation
no array accessors (riddle for ide)
no mystical options bag
simple boolean and interface

@fvovan what are advantages of options?

@tomaszdurka advantages are obvious , much more convenient usage later without passing " null, null, true ".
I don't see a problem passing 'random things'. Anyway it will be just ignored and moreover create() now is used only from Model's commit
Actually I  don't mind to implement any of these options, and even go java way and create new class for createParams and encapsulate all validations there.

now It's with single boolean param,
@tomaszdurka , @njam wdyt ?

I wouldn't say they are obvious. After having some experience with frameworks based on arrays of arrays I can tell signature with less arguments is not really simpler. It seems like that on beginning but once code grows and you pass those options down it becomes nightmare. I would rather go "java way" than keeping the array. It's also hard to document associative array parameters in php.
Passing random things doesn't mean they won't do hard, but imagine having some parameter which influences how the application works. Once you'll remove it feature you won't see any kind of exception that there is in invalid (not-affecting) param passed.

Regarding the code:

Currently you've added interface for replace functionality, but replace is actually parameter for create method, even for those adapters which does not implement replace (mongodb). Let's make it on top of Adapter class not tangled into it.
Let's use interface for methods, implement replace on Replaceable interface.
Keep create as simple as is.

Like this?
if ($useReplace) {
  if (!$persistence instanceof CM_Model_StorageAdapter_ReplaceableInterface) {
    throw new CM_Exception_NotImplemented('Param `useReplace` is not allowed for this adapter');
  }
  $idRaw = $persistence->replace($type, $this->_getSchemaData());
} else {
  $idRaw = $persistence->create($type, $this->_getSchemaData());
}
$this->_id = self::_castIdRaw($idRaw);

@tomaszdurka , it is ready

@tomaszdurka, could you review it?
I merged some changes related to model validation

Looks good, just one note. We have convention to use only null for default values for parameters.
Can you change $replace to  = null? Thanks


[question] the same auth_token, but auth error, any others settings?

dolphinscheduler verion: 3.1.4
apapche-dolphinscheduler: 4.0.0
in api server config file application.yaml, the token is set:

in client（win11）, the auth_token is set the same:

but the result is : auth error
client log
E:\python_env\mysql\lib\site-packages\pydolphinscheduler\java_gateway.py:316: UserWarning: Using unmatched version of pydolphinscheduler (version 4.0.0) and Java gateway (version unknown) may cause errors. We strongly recommend you to find the matched version (check: https://pypi.org/project/apache-dolphinscheduler)
  gateway = GatewayEntryPoint()
Traceback (most recent call last):
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 982, in _get_connection
    connection = self.deque.pop()
IndexError: pop from an empty deque

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "e:\program\shell\test.py", line 11, in <module>
    task_parent = Shell(name="task_parent", command="echo hello pydolphinscheduler")
  File "E:\python_env\mysql\lib\site-packages\pydolphinscheduler\tasks\shell.py", line 58, in __init__
    super().__init__(name, TaskType.SHELL, *args, **kwargs)
  File "E:\python_env\mysql\lib\site-packages\pydolphinscheduler\java_gateway.py", line 139, in get_code_and_version
    return self.gateway.entry_point.getCodeAndVersion(
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 1321, in __call__
    answer = self.gateway_client.send_command(command)
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 1036, in send_command
    connection = self._get_connection()
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 984, in _get_connection
    connection = self._create_connection()
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 990, in _create_connection
    connection.start()
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 1136, in start
    self._authenticate_connection()
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 1158, in _authenticate_connection
    raise Py4JAuthenticationError(
py4j.protocol.Py4JAuthenticationError: Failed to authenticate with gateway server.

api-server log:
[INFO] 2023-04-21 11:07:22.636 +0800 py4j.GatewayConnection:[227] - Gateway Connection ready to receive messages
[INFO] 2023-04-21 11:07:22.636 +0800 py4j.GatewayServer:[519] - Connection Started
[ERROR] 2023-04-21 11:07:22.637 +0800 py4j.GatewayConnection:[251] - Authentication error.
py4j.Py4JAuthenticationException: Client authentication unsuccessful.
	at py4j.commands.AuthCommand.execute(AuthCommand.java:79)
	at py4j.GatewayConnection.run(GatewayConnection.java:236)
	at java.lang.Thread.run(Thread.java:748)
[INFO] 2023-04-21 11:07:22.637 +0800 py4j.GatewayConnection:[164] - Connection Stopped
[INFO] 2023-04-21 11:07:22.662 +0800 py4j.GatewayServer:[519] - Connection Started
[INFO] 2023-04-21 11:07:22.662 +0800 py4j.GatewayConnection:[227] - Gateway Connection ready to receive messages
[ERROR] 2023-04-21 11:07:22.662 +0800 py4j.GatewayConnection:[251] - Authentication error.
py4j.Py4JAuthenticationException: Client authentication unsuccessful.
	at py4j.commands.AuthCommand.execute(AuthCommand.java:79)
	at py4j.GatewayConnection.run(GatewayConnection.java:236)
	at java.lang.Thread.run(Thread.java:748)
[INFO] 2023-04-21 11:07:22.663 +0800 py4j.GatewayConnection:[164] - Connection Stopped

No need for other configs anymore, please try not change the token default value and check wether it work or not.

No need for other configs anymore, please try not change the token default value and check wether it work or not.

this is not the answer.
the client command list
(mysql) PS E:\Machinelearning> pydolphinscheduler config --init
E:\python_env\mysql\lib\site-packages\pydolphinscheduler\java_gateway.py:316: UserWarning: Using unmatched version of pydolphinscheduler (version 4.0.0) and Java gateway (version unknown) may cause errors. We strongly recommend you to find the matched version (check: https://pypi.org/project/apache-dolphinscheduler)
  gateway = GatewayEntryPoint()
(mysql) PS E:\Machinelearning> pydolphinscheduler config --set java_gateway.address <IP_ADDRESS>
E:\python_env\mysql\lib\site-packages\pydolphinscheduler\java_gateway.py:316: UserWarning: Using unmatched version of pydolphinscheduler (version 4.0.0) and Java gateway (version unknown) may cause errors. We strongly recommend you to find the matched version (check: https://pypi.org/project/apache-dolphinscheduler)
  gateway = GatewayEntryPoint()
Set configuration done.
(mysql) PS E:\Machinelearning> pydolphinscheduler config --get java_gateway
E:\python_env\mysql\lib\site-packages\pydolphinscheduler\java_gateway.py:316: UserWarning: Using unmatched version of pydolphinscheduler (version 4.0.0) and Java gateway (version unknown) may cause errors. We strongly recommend you to find the matched version (check: https://pypi.org/project/apache-dolphinscheduler)
  gateway = GatewayEntryPoint()
The configuration query as below:

java_gateway = ordereddict([('auth_token', 'jwUDzpLsNKEFER4*a8gruBH_GsAurNxU7A@Xc'), ('address', '<IP_ADDRESS>'), ('port', 25333), ('auto_convert', True)])
(mysql) PS E:\Machinelearning> python E:\program\shell\test.py
E:\python_env\mysql\lib\site-packages\pydolphinscheduler\java_gateway.py:316: UserWarning: Using unmatched version of pydolphinscheduler (version 4.0.0) and Java gateway (version unknown) may cause errors. We strongly recommend you to find the matched version (check: https://pypi.org/project/apache-dolphinscheduler)
  gateway = GatewayEntryPoint()
Traceback (most recent call last):
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 982, in _get_connection
    connection = self.deque.pop()
IndexError: pop from an empty deque

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "E:\program\shell\test.py", line 11, in <module>
    task_parent = Shell(name="task_parent", command="echo hello pydolphinscheduler")
  File "E:\python_env\mysql\lib\site-packages\pydolphinscheduler\tasks\shell.py", line 58, in __init__
    super().__init__(name, TaskType.SHELL, *args, **kwargs)
  File "E:\python_env\mysql\lib\site-packages\pydolphinscheduler\core\task.py", line 172, in __init__
    self.code, self.version = self.gen_code_and_version()
  File "E:\python_env\mysql\lib\site-packages\pydolphinscheduler\core\task.py", line 391, in gen_code_and_version
    result = gateway.get_code_and_version(
  File "E:\python_env\mysql\lib\site-packages\pydolphinscheduler\java_gateway.py", line 139, in get_code_and_version
    return self.gateway.entry_point.getCodeAndVersion(
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 1321, in __call__
    answer = self.gateway_client.send_command(command)
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 1036, in send_command
    connection = self._get_connection()
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 984, in _get_connection
    connection = self._create_connection()
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 990, in _create_connection
    connection.start()
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 1136, in start
    self._authenticate_connection()
  File "E:\python_env\mysql\lib\site-packages\py4j\java_gateway.py", line 1158, in _authenticate_connection
    raise Py4JAuthenticationError(
py4j.protocol.Py4JAuthenticationError: Failed to authenticate with gateway server.
(mysql) PS E:\Machinelearning>

the api-server command list
[dolphinscheduler@hadoop002 dolphinscheduler-3.1.4]$ bin/dolphinscheduler-daemon.sh stop api-server
Begin stop api-server......
stopping api-server
End stop api-server.
[dolphinscheduler@hadoop002 dolphinscheduler-3.1.4]$ bin/dolphinscheduler-daemon.sh start api-server
Begin start api-server......
starting api-server, logging to /opt/module/dolphinscheduler-3.1.4/api-server/logs
Overwrite api-server/conf/dolphinscheduler_env.sh using bin/env/dolphinscheduler_env.sh.
End start api-server.
[dolphinscheduler@hadoop002 dolphinscheduler-3.1.4]$ grep -A 10 token  api-server/conf/application.yaml
  # Authentication token for connection from python api to python gateway server. Should be changed the default v alue
  # when you deploy in public network.
  auth-token: jwUDzpLsNKEFER4*a8gruBH_GsAurNxU7A@Xc
  # auth-token: bb65ea96-dfea-11ed-90cd-047f0e130e0b
  # The address of Python gateway server start. Set its value to `<IP_ADDRESS>` if your Python API run in different
  # between Python gateway server. It could be be specific to other address like `<IP_ADDRESS>` or `localhost`
  gateway-server-address: <IP_ADDRESS>
  # The port of Python gateway server start. Define which port you could connect to Python gateway server from
  # Python API side.
  gateway-server-port: 25333
  # The address of Python callback client.
  python-address: <IP_ADDRESS>
  # The port of Python callback client.
  python-port: 25334

the api-server logs
[ERROR] 2023-04-21 13:15:52.221 +0800 py4j.GatewayConnection:[251] - Authentication error.
py4j.Py4JAuthenticationException: Client authentication unsuccessful.
        at py4j.commands.AuthCommand.execute(AuthCommand.java:79)
        at py4j.GatewayConnection.run(GatewayConnection.java:236)
        at java.lang.Thread.run(Thread.java:748)
[INFO] 2023-04-21 13:15:52.222 +0800 py4j.GatewayConnection:[164] - Connection Stopped
[INFO] 2023-04-21 13:15:57.970 +0800 py4j.GatewayConnection:[227] - Gateway Connection ready to receive messages
[INFO] 2023-04-21 13:15:57.970 +0800 py4j.GatewayServer:[519] - Connection Started
[ERROR] 2023-04-21 13:15:57.971 +0800 py4j.GatewayConnection:[251] - Authentication error.
py4j.Py4JAuthenticationException: Client authentication unsuccessful.
        at py4j.commands.AuthCommand.execute(AuthCommand.java:79)
        at py4j.GatewayConnection.run(GatewayConnection.java:236)
        at java.lang.Thread.run(Thread.java:748)
[INFO] 2023-04-21 13:15:57.971 +0800 py4j.GatewayConnection:[164] - Connection Stopped
[INFO] 2023-04-21 13:16:04.409 +0800 py4j.GatewayServer:[519] - Connection Started
[INFO] 2023-04-21 13:16:04.409 +0800 py4j.GatewayConnection:[227] - Gateway Connection ready to receive messages
[ERROR] 2023-04-21 13:16:04.410 +0800 py4j.GatewayConnection:[251] - Authentication error.
py4j.Py4JAuthenticationException: Client authentication unsuccessful.
        at py4j.commands.AuthCommand.execute(AuthCommand.java:79)
        at py4j.GatewayConnection.run(GatewayConnection.java:236)
        at java.lang.Thread.run(Thread.java:748)
[INFO] 2023-04-21 13:16:04.410 +0800 py4j.GatewayConnection:[164] - Connection Stopped
[INFO] 2023-04-21 13:16:04.433 +0800 py4j.GatewayServer:[519] - Connection Started
[INFO] 2023-04-21 13:16:04.433 +0800 py4j.GatewayConnection:[227] - Gateway Connection ready to receive messages
[ERROR] 2023-04-21 13:16:04.434 +0800 py4j.GatewayConnection:[251] - Authentication error.
py4j.Py4JAuthenticationException: Client authentication unsuccessful.
        at py4j.commands.AuthCommand.execute(AuthCommand.java:79)
        at py4j.GatewayConnection.run(GatewayConnection.java:236)
        at java.lang.Thread.run(Thread.java:748)
[INFO] 2023-04-21 13:16:04.435 +0800 py4j.GatewayConnection:[164] - Connection Stopped

it is odd, it should be work, did you change any source code of dolphinscheduler or pydolphinscheudler?

it is odd, it should be work, did you change any source code of dolphinscheduler or pydolphinscheudler?

no change。
in the api-server log, why log type is [ERROR].  [ERROR] is means the code run error?  and what is the requirements of  the dependments which in the api-server's auth algo?

it is odd, it should be work, did you change any source code of dolphinscheduler or pydolphinscheudler?

no change。
in the api-server log, why log type is [ERROR]. [ERROR] is means the code run error? and what is the requirements of the dependments which in the api-server's auth algo?

I mean your auth token is not correct

Could you try to instead both apache dolphinscheduler and pydolphinscheduler and try again? it seems others do not have this issue.


wip: update(cmake,scripts): bumped falcoctl to v0.8.0-rc1.

What type of PR is this?
/kind release
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
TODO:

[x] update rpm/deb installation scripts
[ ] update docker images entrypoints

Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

This is still wip :D

Refs #3165

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[Concurrency] Audit diagnostics for Swift 6.

This patch makes a few function changes to strict concurrency diagnostics:

@preconcurrency warnings should only come back when the imported module has enabled Swift 6. Warnings when the client enables Swift 6 are not useful because that's not the point when the library API has been audited.
Sendable diagnostics are errors in Swift 6.

This change also adds a new .limitBehaviorUntilSwiftVersion API on InFlightDiagnostic and uses it for all concurrency diagnostics that are suppressed or downgraded until Swift 6. There are a few benefits to using a UntilSwiftVersion diagnostic engine API, including the diagnostic wrapping to communicate that the mistake will be an error in Swift 6, and to include the mistake in the frontend statistic for Swift 6 errors.

@swift-ci please smoke test

@swift-ci please smoke test Linux


Barback should load multiple transformers with the same class from the same isolate

Not only would this be more efficient, it would handle the following edge-case behavior correctly:
    // package1 pubspec
    transformers:
    - package2
      some: configuration
    // package2 pubspec
    transformers:
    - package2
      different: configuration
The version of package2's transformer that package1 sees should have the same code as the version loaded by package2, but currently it will have the post-transformation code instead.

This issue has been moved to dart-lang/barback#51.


Missing definition of sig_atomic_t in posix/signal.h

This pull-request adds the definition of sig_atomic_t to the posix/signal.h file.
The definition was copied from the file modules/lib/picolibc/newlib/libc/include/signal.h. The problem of the missing definition arose when I tried to compile a lua module for the 3.3.0 version of zephyr (and the current main).
A simple minimal test example can be found in this hello_world_lua project, now updated for this solution.
I consulted the Zephyr->toolchain discord channel and the agreed upon solution was for me to make this pull-request. You can follow the discussion here.
Thank you all for your work.

The errors marked as Compliance Checks mainly refer to the format of the commit message. How should I proceed now? Should I amend the commit message in my fork and file a new pull-request? Or can I edit the commit message somehow? Sorry for making this simple questions but it is the first time for me requesting a merge to an open source project.

@tenllado - yes, exactly

Can you change the first line in your commit message to

include: posix: signal: add sig_atomic_t type

Amend the commit message to include a signed-off-by line (git commit --amend -s)
Add a blank line and at least one sentence to the commit body describing the reason for the change.

Thanks!
Incidentally, I think this should unblock the lua module :-)


Add Dependabot configuration to keep dependencies up to date

Closing this PR as there has been no response from the owner of this project for quite some time.


https://docs.docker.com/engine/userguide/containers/dockervolumes/#mount-a-shared-storage-volume-as-a-data-volume

Problem description

Problem location

I saw a problem on the following URL:

I couldn't find the information I wanted. I expected to find it near the following URL:

Other:

Project version(s) affected

Suggestions for a fix

Thank you for your feedback. There doesn't seem to be enough details in the issue for us to work on. If this really is a documentation issue and I have misunderstood, please reopen it with more information.


Fix data corruption in remote write if max_sample_age is applied

/fixes #13979
The PR https://github.com/prometheus/prometheus/pull/13002  added the option to drop old samples in remote write.
Unfortunatelly we bumped into a bug causing data to be corrupted (metrics withlabels getting merged with other metrics labels was the most obvious) reported here https://github.com/prometheus/prometheus/issues/13979
after trying to repproduce the issue it showed up it is strictly connected to situations, when retries does happen and the filter in buildTimeSeries is applied.
We did investigate and it appears that the issue is in the newly added  buildTimeSeries function which does modify the timeSeries argument  causing the corruption.
The suggested change, which avoids modification of the original timeSeries seems to fix the issue, but is naive and not sure how optimal.

Unfortunately, I had no luck with writing a test that would cover the case yet
Yet, it is possible to reproduce the bug with 100% "success"
Run locally Prometheus with following config
global:
  scrape_interval: 5s
  external_labels:
    __replica__: prometheus-local-test-0
    cluster: local-test
    mimir_cluster_id: monitoring.scif.cz/local-test

remote_write:
  - url: http://foo.bar // URL of some remote write endpoint with known IP si it can be blocked
    queue_config:
      max_shards: 1
      min_shards: 1
      batch_send_deadline: 5s
      capacity: 100
      sample_age_limit: 30s
    metadata_config:
      send: true
      send_interval: 1m
      max_samples_per_send: 100

scrape_configs:
  - job_name: prometheus
    static_configs:
      - targets:
          - localhost:9090

  - job_name: node-exporter // running with default configuration
    static_configs:
      - targets:
          - localhost:9100

When it is running, block the communication to the remote write endpoint IP using sudo iptables -I OUTPUT -d <ip> -j DROP
Wait until you see a context deadline exceeded, log in the Prometheus and enable the traffic again sudo iptables -F OUTPUT
At this point the issue happens. If you run with debugger inspecting the pendingData variable in the runShard function, you can find for example up metrics with duplicated labels like job, mimir_cluster_id etc

Mentioning @marctc and @tpaschalis as you were authors of the original code and have most context, hope you don't mind.

Sorry, but for a bug that sounds as bad as what you're describing we need a test case to ensure we've fixed the problem/this doesn't happen again. I think because of the number of functions at play here and the fact that some of them are closures within other functions that is obscuring the underlying problem and also making it hard to test things here.
My suggestion would be to add a test that uses a version of the test client that can fail and enforce a retry since you're saying this only happens when we need to retry sending an existing write request.
Beyond that, we likely need to refactor some of the code path here so that it's easier to test and less likely to break again.

Hi @cstyan, thanks for answer.
Yes, I agree. We used this bug fix successfully in our production, since we needed it asap,
but I'm planning to look into writing the test, so I can verify it's really not happening anymore (it's hard to find the corrupted data).
I'll ping you once I manage to reproduce it, if you don't mind.

I've pinged Paschalis and Marc internally as well, they're aware of the problem and are looking into it.

We used this bug fix successfully in our production, since we needed it asap

That's good to know, if it becomes pressing we can just move forward with your PR as is. Having a test is still ideal, some part of me feels like while the fix here works it might not be the correct fix because it seems like what's happening is we're modifying the underlying slice of buffered data but not returning a reference to the proper range for the modified slice.

I'll ping you once I manage to reproduce it, if you don't mind.

:+1:

@tpaschalis yes, this seemed to fix the issue using the above described way to reproduce.
I'm trying to reproduce it in a test case, but with no luck yet.
Here is a text case I'm working on right now https://github.com/prometheus/prometheus/pull/14157

I rebased this over https://github.com/prometheus/prometheus/pull/14157 which adds a test case which reproduces the bug reported in https://github.com/prometheus/prometheus/issues/13979.

@cstyan @tpaschalis would you take a look?
As @david-vavra noted above (we are from the same company) we managed to reproduce the issue in https://github.com/prometheus/prometheus/pull/14157 and the fix from this PR resolves it (not saying it should be accepted this way even though we run it in production without any significant memory impact observed)
We still do not exactly know where the actual corruption happens, just that avoiding reusing the []prompb.TimeSeries slice does solve the issue.

I believe I got into the bottom of this.
In case when just a part of a single batch gets dropped (because samples hit maxSampleAge during retrying), timeSeries []prompb.TimeSeries is rewritten so that timeseries which are to be kept are copied to the beginning of the slice so that it can be cut to a number of kept timeseries - see queue_manager.go:buildTimeSeries.
The problem shows itself when a new batch is getting filled into []prompb.TimeSeries (which is reused across batches) and those positions which refer to the same prompb.TimeSeries share the same data for underlying slices ([]Labels, []Samples,...). This leads to mixing/corruption of labels and samples.
I propose fix which would swap data within []prompb.TimeSeries instead of copying them. Other options may be more readable, but I wanted to keep the number of changes to a minimum and to avoid changes to "happy-path" (samples do not age-out during retrying).

@FUSAKLA @david-vavra sorry for the delayed response, I had a noisy on-call shift followed by an in person team offsite.
The main thing I still want to see is a test that reproduces the issue we see. From @david-vavra's comment it sounds like we know the specific case in which the labels 'corruption ' can occur, so a test should be our next step.
That being said, I'm still not sure how the corruption can happen as you're describing it. In populateTimeSeries we're explicitly writing the new data into the reused []prompb.TimeSeries slice starting from index 0, and then returning the count for how many things we wrote into the slice. Am I missing something here?
I do agree that the issue is likely in the modifying of the elements in the slice and the reference indexes.
In the meantime I've opened this PR: https://github.com/prometheus/prometheus/pull/14318

@FUSAKLA @david-vavra My mistake, I pressed the update branch since it looked locally I saw the test still failing and thought that there was some code changes in main that you guys were missing, which would show in a CI failure here. I must have missed something last night when trying the test locally.
It passes! Fails without the change to queue_manager.go but passes with the change, which is good news. Feel free to pull main locally, rebase, and force push over my merge commit. My final ask would be to cherry pick the benchmark from here: https://github.com/prometheus/prometheus/commit/5609bd7b1c08968f2bd58ec79c8d990e651775e8
And then lets merge :+1:

I rebased and cherry-picked the benchmark mentioned in by https://github.com/prometheus/prometheus/pull/14078#issuecomment-2181746353.
Benchmark result:
Without fix (benchmark cherry-picked to current main:
goos: linux
goarch: amd64
pkg: github.com/prometheus/prometheus/storage/remote
cpu: AMD Ryzen 7 7840HS with Radeon 780M Graphics
BenchmarkBuildTimeSeries-16    	     738	   1531949 ns/op	 2650813 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     757	   1543058 ns/op	 2650798 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     741	   1557946 ns/op	 2650801 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     751	   1544889 ns/op	 2650809 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     732	   1546391 ns/op	 2650812 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     730	   1530907 ns/op	 2650807 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     733	   1532309 ns/op	 2650811 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     739	   1539659 ns/op	 2650808 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     741	   1546674 ns/op	 2650816 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     739	   1538725 ns/op	 2650810 B/op	   39748 allocs/op
PASS
ok  	github.com/prometheus/prometheus/storage/remote	13.073s

With fix:
goos: linux
goarch: amd64
pkg: github.com/prometheus/prometheus/storage/remote
cpu: AMD Ryzen 7 7840HS with Radeon 780M Graphics
BenchmarkBuildTimeSeries-16    	     721	   1572745 ns/op	 2650812 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     733	   1583777 ns/op	 2650815 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     746	   1563748 ns/op	 2650818 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     726	   1563117 ns/op	 2650818 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     728	   1572327 ns/op	 2650805 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     724	   1556734 ns/op	 2650817 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     740	   1574076 ns/op	 2650809 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     722	   1571599 ns/op	 2650806 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     706	   1565431 ns/op	 2650812 B/op	   39748 allocs/op
BenchmarkBuildTimeSeries-16    	     709	   1590074 ns/op	 2650795 B/op	   39748 allocs/op
PASS
ok  	github.com/prometheus/prometheus/storage/remote	13.101s


Create a command-line argument for skipping the video download

Ideally, the command to run the example could look like the following:
python3 youtube_chapters_demo.py pvkTC2xIbeY --skip-video-download

Fixed.


Was developing application for windows

Steps to reproduce
Was working on application for windows
Expected results
Got this issue
Unable to parse JSON message:
The document is empty.
════════ Exception caught by services library ══════════════════════════════════
A KeyDownEvent is dispatched, but the state shows that the physical key is already pressed. If this occurs in real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event model as documented in HardwareKeyboard. This was the event: KeyDownEvent#abd6c(physicalKey: PhysicalKeyboardKey#ea6e1(usbHidUsage: "0x000700e0", debugName: "Control Left"), logicalKey: LogicalKeyboardKey#d0ba2(keyId: "0x200000100", keyLabel: "Control Left", debugName: "Control Left"), character: null, timeStamp: 174:10:06.606536)
'package:flutter/src/services/hardware_keyboard.dart':
Failed assertion: line 467 pos 16: '!_pressedKeys.containsKey(event.physicalKey)'
Actual results
Please can you reposnd back
this my project github url which got this issue
https://github.com/Vaibhav77e/bar_management.git
Code sample
import 'package:bar_management_system/screens/DashBoard/DashBoardScreen.dart';
import 'package:bar_management_system/screens/Orders/OrdersScreen.dart';
import 'package:bar_management_system/screens/Payments/PaymentsScreen.dart';
import 'package:bar_management_system/screens/Reports/ReportsScreen.dart';
import 'package:bar_management_system/screens/Staffs/CreateNewStaffs.dart';
import 'package:bar_management_system/utils/MediaqueryHelper.dart';
import 'package:flutter/material.dart';
import '../Inventory/AddProductsToInventory.dart';
import '../Inventory/EditInventoryProducts.dart';
import '../Staffs/EditStaffs.dart';
class HomeScreenPage extends StatefulWidget {
@override
_HomeScreenPageState createState() => _HomeScreenPageState();
}
class _HomeScreenPageState extends State {
Widget _currentWidget = DashBoardScreen();
void _changeContent(Widget newContent) {
setState(() {
_currentWidget = newContent;
});
}
@override
Widget build(BuildContext context) {
MediaQueryHelper mediaQueryHelper = MediaQueryHelper(context);
return Scaffold(
body: Row(
children: [
SizedBox(
width: 200, // Width of the locked sidebar
child: Drawer(
child: ListView(
padding: EdgeInsets.zero,
children: [
ListTile(
leading: SizedBox(
height: mediaQueryHelper.getHeightPercentage(5),
child: Image.asset('assets/images/dashboard.png',)),
title: Text('Dashboard'),
onTap: () {
_changeContent(DashBoardScreen());
},
),
ExpansionTile(
leading: SizedBox(
height: mediaQueryHelper.getHeightPercentage(5),
child: Image.asset('assets/images/inventory-management.png')),
title: Text('Inventory'),
children:[
ListTile(
leading: Icon(Icons.add),
title: Text('Add Products'),
onTap: () {
_changeContent(AddProductsToInventory());
},
),
ListTile(
leading: Icon(Icons.edit),
title: Text('Edit Products'),
onTap: () {
_changeContent(EditInventoryProducts());
},
),
]
),
ListTile(
leading:SizedBox(
height: mediaQueryHelper.getHeightPercentage(5),
child: Image.asset('assets/images/order.png')) ,
title: Text('Orders'),
onTap: () {
_changeContent(OrdersScreen());
},
),
ListTile(
leading:SizedBox(
height: mediaQueryHelper.getHeightPercentage(5),
child: Image.asset('assets/images/payment-method.png')) ,
title: Text('Payments'),
onTap: () {
_changeContent(PaymentsScreen());
},
),
              ExpansionTile(
                leading: Image.asset('assets/images/staff.png'),
                title: Text('Staffs'),
                children: <Widget>[
                  ListTile(
                    leading: Icon(Icons.add),
                    title: Text('Add Staffs'),
                    onTap: () {
                      _changeContent(CreateNewStaffs());
                    },
                  ),
                  ListTile(
                    leading: Icon(Icons.edit),
                    title: Text('Edit Staffs'),
                    onTap: () {
                      _changeContent(EditStaffs());
                    },
                  ),
                ],
              ),
              ListTile(
                leading:SizedBox(
                  height: mediaQueryHelper.getHeightPercentage(5),
                  child: Image.asset('assets/images/report.png')) ,
                    title: Text('Reports'),
                    onTap: () {
                      _changeContent(ReportScreen());
                    },
                  ),
            ],
          ),
        ),
      ),
      Expanded(
        child: AnimatedSwitcher(
          duration: Duration(milliseconds: 500),
          child: _currentWidget,
        ),
      ),
    ],
  ),
);

}
}
In this when i click on orders am getting this issue
Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[√] Flutter (Channel stable, 3.16.9, on Microsoft Windows [Version 10.0.22621.3155], locale en-IN)
    • Flutter version 3.16.9 on channel stable at D:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 41456452f2 (6 weeks ago), 2024-01-25 10:06:23 -0800
    • Engine revision f40e976bed
    • Dart version 3.2.6
    • DevTools version 2.28.5

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\shree\AppData\Local\Android\sdk
    • Platform android-34, build-tools 30.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop Windows apps (Visual Studio Build Tools 2019 16.11.5)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
    • Visual Studio Build Tools 2019 version 16.11.31729.503
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2021.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[√] VS Code (version 1.87.0)
    • VS Code at C:\Users\shree\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.34.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22621.3155]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 122.0.6261.95
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 122.0.2365.66

[√] Network resources
    • All expected network resources are available.

Closing this as a duplicate of https://github.com/flutter/flutter/issues/107972


Check component wording

Steven Newhouse pointed out that in
https://github.com/sa-tre/satre-specification/blob/ec826879e45a397408323871dd3f107c62dd8ce9/docs/source/pillars/information_governance.md?plain=1#L122C1-L122C123
the requirement should be on the project not the TRE operator. There may be other places where we need to check the wording.

IG has been rewritten in https://github.com/sa-tre/satre-specification/pull/164 (copied from Tim's WP3 doc)

I would say this issue can be closed? we addressed the phrasing of this requirement?