Support dry run

This PR supports the function of dry run fuzz target, that is, only execute the empty seed once. Our insight is that the generated fuzz driver should not crash in any form when executing the empty seed in theory. Our idea is build => dry run with asan => short-term fuzz with asan. Failure of dry run is regarded as run failure, and the premise of entering short-term fuzz is that dry run is successful. The sanitizer used by dry run is ASAN. In addition, we have enabled the two ASAN options check_initialization_order and detect_stack_use_after_return (whenever dry run or fuzz). We created a dry_run folder under the logs folder. Currently, all dry run crash would be label with FP_NEAR_INIT_CRASH in _parse_libfuzzer_logs. For the time being, we do not support dry run of CloudBuilderRunner because this will involve modifications to OSS-Fuzz.

Thanks for the contribution! We've actually found several legitimate bugs in various projects when an empty input is passed.
e.g. cases where a function does not properly take into account zero length strings might look something like:
void func(char *str) {
  if (str[strlen(str) - 1] == '\n') {
     ...
   }
}

Is there some better way to filter out fuzz targets in a way that accounts for this?

Thanks for the contribution! We've actually found several legitimate bugs in various projects when an empty input is passed.
e.g. cases where a function does not properly take into account zero length strings might look something like:
void func(char *str) {
  if (str[strlen(str) - 1] == '\n') {
     ...
   }
}

Is there some better way to filter out fuzz targets in a way that accounts for this?

Thank you for your review. After discussing with @DonggeLiu , we think that the result of "executing empty seed (dry run)" can be used as feedback information to the agent to assist it in generating a better driver, rather than as a criterion for judging whether there is a crash or a problem with the driver. I will add the dry run part after the crash analyzer agent. The crash analyzer agent is being developed intensively and a PR will be submitted soon.

I will temporarily close this pr.


SCORING_DATASTORE_STORAGE_NAME, SCORING_DATASTORE_ACCESS_KEY are described as optional, but never covered

In /docs/getting_started.md, the variables are listed as optional, but never covered in the doc re: when/how you'd use them.
I added them thinking it would be covered later and it caused an error the "Set up the Release Deployment and/or Batch Scoring pipelines".

+1 having the exact same issue... I want to setup batching scoring, so I:

created a new storage account
added the storage account name/key to the appropriate variables in the variable group (as outlined in the "getting started" guide
even ensured the service principal used for my AzDO -> AML service connection is set as Contributor for the new storage account (the whole resource group, actually)

I get the same error in the same place as @cmayomsft

It appears something is mis-configured and causing fallback to interactive Azure CLI authentication, which of course does not work very well in a CI build. :-)
What's odd is that the training pipeline seems to work fine... its unclear why.

There definitely needs to be more documentation about those environment variables.
Will try to repro the issue.

@jitghosh have you ran into this issue before? can you take a look?


parentheses after catch

missing (ex) after catch clause causing errors

@P0lip Can you take a look at this?

@P0lip Can you take a look at this?

Hey!
My apologies for dropping a ball.
Is there any reason we need parentheses?
The syntax currently used is valid (optional catch binding).
Are you experiencing syntax errors?

Hey!
My apologies for dropping a ball.
Is there any reason we need parentheses?
The syntax currently used is valid (optional catch binding).
Are you experiencing syntax errors?

No worries! Thanks.
I don't have any errors when I run locally, but then when the code is run via Bitbucket pipelines it causes an error. I haven't run it recently so I don't have the error right now but I can get it and provide more details if that would be helpful.
It also looks like most of the other instances where catch is used it's followed by (ex) so this is the only line causing that error for me.

No worries! Thanks.
I don't have any errors when I run locally, but then when the code is run via Bitbucket pipelines it causes an error. I haven't run it recently so I don't have the error right now but I can get it and provide more details if that would be helpful.
It also looks like most of the other instances where catch is used it's followed by (ex) so this is the only line causing that error for me.

I am also seeing an issue with this same area when running in a Bamboo pipeline. Locally it works fine when running a spectral lint commend, unfortunately on the build agent it doesn’t work. The script I’m running it from is a simple Powershell script with: ‘spectral lint FILENAME -r RULESET’ and it tells me there is an error with the catch in a nimma file. Don’t have it directly in front of me. But I’ve been fighting with the issue all day.

Could you tell me which Node.js version are you using?

Just ran the pipeline and it reports back the node version is v8.11.3

Was able to select a build agent that had a v10.23.0 version of NodeJS and it got passed the nimma file error. Granted, now I’m getting a ‘ts-node/register’ couldn’t be found, but sprectal did start the lint.

My build agent is using v8.11.3.
I just installed that locally and it does look like that's the reason for the error. I'll see if I'm able to update the version...
Is there a reason we can't add the (ex) after the catch clause?

I looks like anything above v10.0.0 avoids the error

Is there a reason we can't add the (ex) after the catch clause?

We totally can, but what I'm trying to say is that your version of Node is not supported anyway.
I cannot guarantee you won't face any other errors using Spectral, as we don't support v8 anymore.
In fact, the minimum required version Spectral supports is Node 10.18, as can be seen in https://github.com/stoplightio/spectral/blob/develop/package.json#L33.
v8 is EOL. v10 enters EOL in April 2021, and the next version of Spectral will drop support for it.
https://nodejs.org/en/about/releases/

Each Spectral release comes with binaries. Perhaps that's something you might be interested in?
https://github.com/stoplightio/spectral/releases/tag/v5.8.0
We also offer a simple script that automates the whole process https://github.com/stoplightio/spectral/blob/develop/scripts/install.sh -> curl -L https://raw.githack.com/stoplightio/spectral/master/scripts/install.sh | sh

Thanks! I didn't realize how old a version I was using. Should have caught that. I was able to update it without issues so now it's working for me. Thanks for those resources! I appreciate you taking the time to respond! I'll close out this issue.


fix: on-demand release again

Coverage remained the same at 100.0% when pulling 4d0a2295e05c443404be77e38680431b3f12ba33 on fix-on-demand into 6aac43b8ca1fd216ce79c2097b763d08d0762a94 on main.

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


[CELEBORN-224][FOLLOWUP] Add missing license files.

What changes were proposed in this pull request?
This is a follow-up of Celeborn-224
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?

Ping @WillemJiang. How about this pull request to restore the license files?

We need to put the third-party licenses files links into the LICENSE-binary files.

We need to put the third-party licenses files links into the LICENSE-binary files.

Thanks for your review. Links are added please check again.

LGTM.

Thanks @WillemJiang for reviewing!


drt: fix check for second layer

Signed-off-by: Eder Monteiro<EMAIL_ADDRESS>

@habibayassin do you see any issue here?

no it seems okay


Reply Button on comment containers

(Unless I'm missing it) it would be nice to be able to click reply on someone's comment opposed to having to type @username in the reply input. A lot of space in the lower right-hand side of the container to the right of the voting UI to fit it in without cluttering it. Even the standard reply arrow would be sufficient to keep it minimal.

Thanks, will add that in next release


player_chat, player_join and player_leave don't update unless /ce reload

None of those events work properly unless done /ce reload after a server restart.
https://pastebin.com/pvi8NvL2

Running Paper 1.20.4

How are you restarting your server?

Normal server restart, not /reload

I will fix this in the next update


Season Notation (XXYY vs XX/YY)

Is the season notation written as XXYY or XX/YY?
For example, would Velocity Vortex be noted as 1617 or "16/17"?
In either case, it should be made sure across the site it's unified in usage.

I vote for XXYY (1617), that way it would match the API.

This is also something that will be finalized more when we rename the DBs.

This has been solved in APIv2


Improvements to configuration structure

Summary of changes:

Condensed "AMQP" section into "Comms"
Renamed "IP" property to "Host" where appropriate
Added database name option for both DB and TSDB. Only
the TSDB package uses this option currently. (This resolves https://github.com/Mierdin/todd/issues/19)
Removed configurations specific to Interop 2016

lgtm 👍

Like this? https://github.com/Mierdin/todd/pull/25/commits/155a964b2b00819a81db12fbef322e63b8958b5f

I was thinking of a method, but I think your approach makes more sense as the URL doesn't change after initial creation of the rabbitMQComms struct.

Okay cool. Thanks! Merging.


Error importing Sass: base and animations files

I followed the usage instructions found at delicious-hamburgers @npmjs, but I was unable to resolve some imports without editing some files. Since I have not used Sass on any projects, I am unfamiliar with it, so do let me know how best to resolve the imports.
I tried

Plain CSS (i.e. download the stylesheet and include it in my .html file inside <head>), which worked
Install the npm package and import Sass. The package installed smoothly, but importing the Sass files base and the specific animation file brought up errors.

Instead of the original instructions, which said to import the following:
@import "~delicious-hamburgers/scss/base";
@import "~delicious-hamburgers/scss/animations/criss-cross";

I had to specify the path (and replaced @import with @use which Sass prefers)
@use "./node_modules/delicious-hamburgers/scss/base";

to resolve the error
Error: Can't find stylesheet to import.
@use "~/node_modules/delicious-hamburgers/scss/base";

Then, I had to add the line @import '../base'; (which defines hamburger-bar()) to the files in /node_modules/delicious-hamburgers/scss/animation (like _criss-cross.scss) to resolve the error
Error: Undefined mixin.
@include hamburger-bar();

If I import hamburger.scss which includes all the animations I'm sure the files compile all fine.
Lastly, would one be able to resize the button?
Thanks so much for creating an awesome set of pure CSS animated hamburger menu buttons!

Are you using Parcel as a bundler? The tilde (~) notation (@import "~delicious-hamburgers/...") doesn't seem to work (issue). For parcel using something like @import "./node_modules/delicious-hamburgers/..." seems to work fine.
Thanks for pointing out that @use will be the preferred method in the future, but @use and @import work differently when overriding default values. Here the documentation notes:
Members (variables, functions, and mixins) loaded with @use are only visible in the stylesheet that loads them.

That's why you get the undefined mixin error because hamburger-bar() is scoped and not visible from the second imported file.
So for now: with this package you'll have to use @import, I'd recommend that over editing the plugin files, or importing all animations. I'll have to update this package sometime before 2022 it seems. As a bonus this also means I will be able to make it simpler by using @use in the animation files and you won't have to import the base file anymore. Using the plugin would then look something like (please note this is not supported yet):
@use "~delicious-hamburgers/scss/animations/criss-cross" with (
     $hamburger-size: 100px,
     // etc...
);

For your second question: Resizing is done by setting the $hamburger-size before you import the scss files, the default is 50px. Check out all the possible variables here. Maybe you tried it already with the @use keyword but that unfortunately won't work, because the internal default variable would be scoped to the file and therefore not overridden.
Closing this issue for now but feel free to open it back up if I'm missing anything!


Fix saga multiple injection problem(#2314)

purpose
According to the issue #2314,
using componentDidMount and Promise to prevent saga multiple injection problem.

componentWillMount has the render ordering problem (comment).
Cuz of React v16, componentWillMount is unsafe and we should not use it.

Using this modification, we can assure that the order sagas are injected is correct
order before fix

Page A(1)'s componentWillMount
switch language (to make Page A re-Mount)
Page A(2)'s componentWillMount
Page A(1)'s componentWillUnMount

oder after fix

Page A(1)'s componentDidMount
switch language (to make Page A re-Mount)
Page A(1)'s componentWillUnMount
Page A(2)'s componentDidMount

Coverage remained the same at 100.0% when pulling 3c630f5b723d954e87d1d138f252be18ee689145 on tonyex52:dev into 75dd475bd67c1595d7b7c63bcfb493cef17df457 on react-boilerplate:dev.

@julienben I tried to use constructor instead of componentDidMount, but I found that the store in context would be undefined

here is my code
constructor(props) {
  super(props);
  this.injectors = getInjectors(this.context.store);
  const { injectSaga } = this.injectors;
  injectSaga(key, { saga, mode }, this.props);
}


Add DO NOT EDIT. comment to generated files

Description
Adds the DO NOT EDIT. comment to generated files which lets linters like golint exclude them automatically.
As discussed in https://github.com/golang/go/issues/13560.
Checklist

[x] Code compiles correctly
[x] Created tests which fail without the change (if possible)
[x] All tests passing
[x] Extended the README.md / documentation, if necessary
[x] Added myself / the copyright holder to the CONTRIBUTORS file

Thank you.


Are we no longer emitting scaling events

I can't see any in production.

They seem to get emitted.


WIP: Python doc gen

#13340
#16894

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,649      Total (=)      2,015,649

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,192      Total (=)     11,116,192

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,649      Total (=)      2,015,649

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,198      Total (>)     11,116,194

 No significant differences in binary sizes

Corrupt JSON data (indicates timeout or crash):
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.new: 10
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.old: 10

[microbenchmarks] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,649      Total (=)      2,015,649

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,196      Total (<)     11,116,200

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,649      Total (=)      2,015,649

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,194      Total (>)     11,116,189

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,578      Total (=)      2,015,578

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,199      Total (>)     11,116,194

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,578      Total (=)      2,015,578

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,192      Total (=)     11,116,192

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,578      Total (=)      2,015,578

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,201      Total (>)     11,116,193

 No significant differences in binary sizes

Prerequisite:

Sphinx 1.8.1

To generate documentation run:
python setup.py doc

Here are some points different from current version:

The new documentation generated from a templates folder ./doc/python/sphinx to ./doc/build.
The new API reference split into sections to help users jumping between the long list of APIs
The grpc_* modules are included now (though the description is insufficient...)
If there are warnings or errors in the docstring, it will throw an exception
A new theme: Alabaster

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,578      Total (=)      2,015,578

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,197      Total (>)     11,116,196

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,578      Total (=)      2,015,578

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,194      Total (>)     11,116,191

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,578      Total (=)      2,015,578

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,195      Total (=)     11,116,195

 No significant differences in binary sizes

The doc string format reference -> link

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,578      Total (=)      2,015,578

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,196      Total (>)     11,116,192

 No significant differences in binary sizes

Hi @nathanielmanistaatgoogle , about the new documentation generator, I am planning to finish it in two PR, one is fixing the generation procedure and generate a slightly better documentation, another one is actually adding more documentation. I think this PR is ready to be reviewed.

Great; will try to take a look at it this evening.

@nathanielmanistaatgoogle Can you take a look at new API documentation grouping?

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,020,616      Total (=)      2,020,616

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,941      Total (<)     11,180,942

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,020,616      Total (=)      2,020,616

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,946      Total (<)     11,180,947

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,020,616      Total (=)      2,020,616

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,950      Total (>)     11,180,947

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,020,616      Total (=)      2,020,616

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,946      Total (>)     11,180,938

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,020,616      Total (=)      2,020,616

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,936      Total (<)     11,180,944

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,019,390      Total (=)      2,019,390

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,032      Total (>)     11,180,029

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,019,390      Total (=)      2,019,390

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,031      Total (<)     11,180,037

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,019,390      Total (=)      2,019,390

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,037      Total (>)     11,180,035

 No significant differences in binary sizes


Pillar encoder cluster center calculation logic

Hi folks, recently looking into pillar encoding logic and just found this section a bit counter intuitive. Specifically, the denominator is taking valid number of points per-pillar into account, yet the numerator is not a masked sum. Checked the original impl, and seems this is consistent. I'd imagine the distance to cluster center would be quite over-valued if there is only a few valid points within the voxel.

Suppose we set a voxel that can contain up to 5 points, if we have 3 points for a voxel, then the other 2 point features should be padded with zeros. So the masked sum is equal to the direct sum of all the point features. I am not sure whether this is what you want to ask?


Move UMD tests after build artifact

Ticket
NA
Problem description
UMD Tests were running independent of the rest of all post commit.
Many times I've seen UMD tests running, even if the global build of the project fails.
UMD Tests were getting built in the existing workflow on VMs that aren't really fast for building, and no ccache.
By putting UMD Tests after build-artifact we might be able to save on test machine usage.
**  UMD TESTS CURRENTLY FAILING DUE TO MISSING FILE??? **
What's changed
UMD tests moved after build-artifact
Checklist
https://github.com/tenstorrent/tt-metal/actions/runs/11864188038

[ ] Post commit CI passes
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] Device performance regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

Blocking Problem

Invalid path may be embedded in test executable

I am having some problem with UMD tests.
If UMD is built on machine A. (Highly parallel builder machine with no Tenstorrent cards).
And I run tests on machine B. (build products transferred to arbitrary directory on machine B from machine A).
I end up hitting this error:
unknown file: Failure
C++ exception with description "Error: device descriptor file /home/ubuntu/actions-runner-2/_work/tt-metal/tt-metal/tt_metal/third_party/umd/tests/soc_descs/grayskull_10x12.yaml does not exist!" thrown in the test body.
The absolute path from the builder machine is baked into the test case! I don't have this path on machine B.
Running tests from the build tree is usually a problem like this, this is why there is the concept of installing tests, libraries, meta data files. Artifacts in an install tree are usually relocatable. i.e. they can be in /usr/lib or /opt/tenstorrent or what have you, and everything still works.
How can we make this better?
ENV that points to the yaml?
Embed the yaml info into the library?
Start running tests from the install tree?

still draft?

If we ever want to optimize this (use build artifacts for UMD tests), a fix will be required first on UMD side.
I'm not going to prioritize this. For now, we'll just keep building on the VM.

note that we've UMD tests on post-commit since UMD now has their own CI


Added mail section with example in admin guides

@TheReal1604 thanks for adding this.  :)  Can you rebase?

@geekgonecrazy Rebased my repo and pushed it. Sry, have to work the first time with git.

@TheReal1604 all good!  Thanks again for the contributions :)


Allow operator logging to be configured

... in a similar fashion to other pods.
Depends on #1180.
Signed-off-by: Stephen Kitt<EMAIL_ADDRESS>

oh sorry about merging to wrong target :/


internal transaction missing

https://tracker.icon.community/address/hxfc56203484921c3b7a4dee9579d8614d8c8daaf5#internaltransactions
https://tracker.icon.foundation/address/hxfc56203484921c3b7a4dee9579d8614d8c8daaf5#internaltransactions

Transactions service passes this transactions locally. This issue can be resolved with a resync/backfill

Internal transaction exists in block#37,897,465. Not present in kafka, needs to be injected through ETL @shinyfoil

37897465 should be fetched now


Add google cloud storage bucket

Fix #231

Sample output:
 google_storage_bucket.my_storage_bucket
  ├─ Data storage                                                                                150  GB-months   0.0001        3e-05        0.0200
  ├─ Data retrieval                                                                                500  GB          0.0200       0.0137       10.0000
  ├─ Network egress
  │  ├─ Data transfer in same continent                                                                  550  GB          0.0100       0.0075        5.5000
  │  ├─ Data transfer to worldwide destinations (excluding Asia & Australia) (0-1 TB)                  1,024  GB          0.1200       0.1683      122.8800
  │  ├─ Data transfer to worldwide destinations (excluding Asia & Australia) (1-10 TB)                 9,216  GB          0.1100       1.3887    1,013.7600
  │  ├─ Data transfer to worldwide destinations (excluding Asia & Australia) (10+ TB)                  2,260  GB          0.0800       0.2477      180.8000
  │  ├─ Data transfer to Asia Destinations (excluding China, but including Hong Kong) (0-1 TB)         1,024  GB          0.1200       0.1683      122.8800
  │  ├─ Data transfer to Asia Destinations (excluding China, but including Hong Kong) (1-10 TB)          476  GB          0.1100       0.0717       52.3600
  │  ├─ Data transfer to China Destinations (excluding Hong Kong) (0-1 TB)                                50  GB          0.2300       0.0158       11.5000
  │  └─ Data transfer to Australia Destinations (0-1 TB)                                                 250  GB          0.1900       0.0651       47.5000
  └─ Operations
     ├─ Class A                                                                                40,000  operations   1e-05       0.0005        0.4000
     └─ Class B                                                                                20,000  operations   5e-06       0.0001        0.1000
  Total                                                                                2.1475    1,567.7000

@alikhajeh1 Any suggestions regarding the naming?

Sample output:
 google_storage_bucket.my_storage_bucket
  ├─ Data storage                                                                                150  GB-months   0.0001        3e-05        0.0200
  ├─ Data retrieval                                                                                500  GB          0.0200       0.0137       10.0000
  ├─ Network egress
  │  ├─ Data transfer in same continent                                                                  550  GB          0.0100       0.0075        5.5000
  │  ├─ Data transfer to worldwide destinations (excluding Asia & Australia) (0-1 TB)                  1,024  GB          0.1200       0.1683      122.8800
  │  ├─ Data transfer to worldwide destinations (excluding Asia & Australia) (1-10 TB)                 9,216  GB          0.1100       1.3887    1,013.7600
  │  ├─ Data transfer to worldwide destinations (excluding Asia & Australia) (10+ TB)                  2,260  GB          0.0800       0.2477      180.8000
  │  ├─ Data transfer to Asia Destinations (excluding China, but including Hong Kong) (0-1 TB)         1,024  GB          0.1200       0.1683      122.8800
  │  ├─ Data transfer to Asia Destinations (excluding China, but including Hong Kong) (1-10 TB)          476  GB          0.1100       0.0717       52.3600
  │  ├─ Data transfer to China Destinations (excluding Hong Kong) (0-1 TB)                                50  GB          0.2300       0.0158       11.5000
  │  └─ Data transfer to Australia Destinations (0-1 TB)                                                 250  GB          0.1900       0.0651       47.5000
  └─ Operations
     ├─ Class A                                                                                40,000  operations   1e-05       0.0005        0.4000
     └─ Class B                                                                                20,000  operations   5e-06       0.0001        0.1000
  Total                                                                                2.1475    1,567.7000

@alikhajeh1 Any suggestions regarding the naming?

@sinabakh first of all, wow 🤩!

The network egress costs look like the same as the standard GCP egress costs (https://cloud.google.com/vpc/network-pricing#premium-tier). I think we should move these into these into a global resource called google_network_egress that should act similar to the aws_data_transfer resource. What do you think @sinabakh and @alikhajeh1? If you both agree, I think this should be moved to a separate PR.

I would also flatten the operations to:
Class A operations / monthly_class_a_operations
Class B operations / monthly_class_b_operations

We need to add better contributing docs about when to use the hierarchy, but my initial thoughts is we should do it when the resource is a nested resource (block) in Terraform. But there's going to be exceptions to this, like CloudFront where without nesting it would be unreadable. @alikhajeh1 what do you think about this?

monthly_storage_gb -> storage_gb since the storage is continuous (number 5 here: https://github.com/infracost/infracost/blob/master/CONTRIBUTING.md#usage-file-notes)

@sinabakh first of all, wow 🤩!

The network egress costs look like the same as the standard GCP egress costs (https://cloud.google.com/vpc/network-pricing#premium-tier). I think we should move these into these into a global resource called google_network_egress that should act similar to the aws_data_transfer resource. What do you think @sinabakh and @alikhajeh1? If you both agree, I think this should be moved to a separate PR.

I would also flatten the operations to:
Class A operations / monthly_class_a_operations
Class B operations / monthly_class_b_operations

We need to add better contributing docs about when to use the hierarchy, but my initial thoughts is we should do it when the resource is a nested resource (block) in Terraform. But there's going to be exceptions to this, like CloudFront where without nesting it would be unreadable. @alikhajeh1 what do you think about this?

monthly_storage_gb -> storage_gb since the storage is continuous (number 5 here: https://github.com/infracost/infracost/blob/master/CONTRIBUTING.md#usage-file-notes)

@aliscott Your welcome. I will add my comments in reverse order since the first one is the most complicated one.

You are right, I'm not yet fully on-boarded on the new naming convention.

I modeled how the pricing page groups them. but the other way also seems completely ok. So it's a matter of taste. I will leave the decision to you and @alikhajeh1

Regarding the first comment, I think it depends on how users expect from terraform. I personally want to get the cost of my storage bucket as a whole, so its network transfer is also part of the same component. Aggregating all the egress (the ones that have a direct relation with the resources) will make things a little complicated. Let's say I make a caching mechanism in my app, it won't change the egress cost but will lower the costs of buckets network data. I personally prefer this approach. However, since you interact more with users, what do you think about the user's expectations?

@aliscott Your welcome. I will add my comments in reverse order since the first one is the most complicated one.

You are right, I'm not yet fully on-boarded on the new naming convention.

I modeled how the pricing page groups them. but the other way also seems completely ok. So it's a matter of taste. I will leave the decision to you and @alikhajeh1

Regarding the first comment, I think it depends on how users expect from terraform. I personally want to get the cost of my storage bucket as a whole, so its network transfer is also part of the same component. Aggregating all the egress (the ones that have a direct relation with the resources) will make things a little complicated. Let's say I make a caching mechanism in my app, it won't change the egress cost but will lower the costs of buckets network data. I personally prefer this approach. However, since you interact more with users, what do you think about the user's expectations?

The final output:
  google_storage_bucket.my_storage_bucket
  ├─ Data storage                                                                           150  GB-months   0.0001        3e-05        0.0200
  ├─ Data retrieval                                                                         500  GB          0.0200       0.0137       10.0000
  ├─ Network egress
  │  ├─ Data transfer in same continent                                                     550  GB          0.0100       0.0075        5.5000
  │  ├─ Data transfer to worldwide excluding Asia, Australia (first 1TB)                  1,024  GB          0.1200       0.1683      122.8800
  │  ├─ Data transfer to worldwide excluding Asia, Australia (next 9TB)                   9,216  GB          0.1100       1.3887    1,013.7600
  │  ├─ Data transfer to worldwide excluding Asia, Australia (over 10TB)                  2,260  GB          0.0800       0.2477      180.8000
  │  ├─ Data transfer to Asia excluding China, but including Hong Kong (first 1TB)        1,024  GB          0.1200       0.1683      122.8800
  │  ├─ Data transfer to Asia excluding China, but including Hong Kong (next 9TB)           476  GB          0.1100       0.0717       52.3600
  │  ├─ Data transfer to China excluding Hong Kong (first 1TB)                               50  GB          0.2300       0.0158       11.5000
  │  └─ Data transfer to Australia (first 1TB)                                              250  GB          0.1900       0.0651       47.5000
  └─ Operations
     ├─ Class A                                                                          40,000  operations   1e-05       0.0005        0.4000
     └─ Class B                                                                          20,000  operations   5e-06       0.0001        0.1000
  Total                                                                                2.1475    1,567.7000

The final output:
  google_storage_bucket.my_storage_bucket
  ├─ Data storage                                                                           150  GB-months   0.0001        3e-05        0.0200
  ├─ Data retrieval                                                                         500  GB          0.0200       0.0137       10.0000
  ├─ Network egress
  │  ├─ Data transfer in same continent                                                     550  GB          0.0100       0.0075        5.5000
  │  ├─ Data transfer to worldwide excluding Asia, Australia (first 1TB)                  1,024  GB          0.1200       0.1683      122.8800
  │  ├─ Data transfer to worldwide excluding Asia, Australia (next 9TB)                   9,216  GB          0.1100       1.3887    1,013.7600
  │  ├─ Data transfer to worldwide excluding Asia, Australia (over 10TB)                  2,260  GB          0.0800       0.2477      180.8000
  │  ├─ Data transfer to Asia excluding China, but including Hong Kong (first 1TB)        1,024  GB          0.1200       0.1683      122.8800
  │  ├─ Data transfer to Asia excluding China, but including Hong Kong (next 9TB)           476  GB          0.1100       0.0717       52.3600
  │  ├─ Data transfer to China excluding Hong Kong (first 1TB)                               50  GB          0.2300       0.0158       11.5000
  │  └─ Data transfer to Australia (first 1TB)                                              250  GB          0.1900       0.0651       47.5000
  └─ Operations
     ├─ Class A                                                                          40,000  operations   1e-05       0.0005        0.4000
     └─ Class B                                                                          20,000  operations   5e-06       0.0001        0.1000
  Total                                                                                2.1475    1,567.7000

It will probably take some time to extract the egress and make it a separate resource. I will work on it ASAP.

It will probably take some time to extract the egress and make it a separate resource. I will work on it ASAP.

Thanks @sinabakh! I tweaked a few things and commented-out the network stuff until we're ready for that, here's the output:
  google_storage_bucket.my_storage_bucket
  ├─ Storage (coldline)                                              150  GB-months       0.0070       0.0014        1.0500
  ├─ Data retrieval                                                  500  GB              0.0200       0.0137       10.0000
  ├─ Object adds, bucket/object list (class A)                         4  10k operations  0.1000       0.0005        0.4000
  └─ Object gets, retrieve bucket/object metadata (class B)            2  10k operations  0.0500       0.0001        0.1000
  Total                                                                                0.0158       11.5500

I added the storage class in brackets, and renamed the operations to use the same wording as the GCP prices do for their examples. The operations are also changed to use 10K unitMultiplier per the pricing page. Plz lmk if this looks ok and I'll merge it, I'll create a separate ticket for data transfer.

Thanks @sinabakh! I tweaked a few things and commented-out the network stuff until we're ready for that, here's the output:
  google_storage_bucket.my_storage_bucket
  ├─ Storage (coldline)                                              150  GB-months       0.0070       0.0014        1.0500
  ├─ Data retrieval                                                  500  GB              0.0200       0.0137       10.0000
  ├─ Object adds, bucket/object list (class A)                         4  10k operations  0.1000       0.0005        0.4000
  └─ Object gets, retrieve bucket/object metadata (class B)            2  10k operations  0.0500       0.0001        0.1000
  Total                                                                                0.0158       11.5500

I added the storage class in brackets, and renamed the operations to use the same wording as the GCP prices do for their examples. The operations are also changed to use 10K unitMultiplier per the pricing page. Plz lmk if this looks ok and I'll merge it, I'll create a separate ticket for data transfer.

@alikhajeh1 Thanks for the changes 👍🏼 They all look good to me. Regarding the free resources, yes that was the reason but I'm not sure if it's the right decision or not.

@alikhajeh1 Thanks for the changes 👍🏼 They all look good to me. Regarding the free resources, yes that was the reason but I'm not sure if it's the right decision or not.


New ban policy, is this safe?

This looks amazing, I want to try it out but I don't know if you are aware of the recent new bans.
If you are have you been using it? Did you get the warning?
This is completely of the radar. I can't find this(veera/orchees) on google search, or google search on 4chan boards, obviously not Reddit and not both discords(gaijin/gbfint).

No third party tool is truly "safe". All of them are against ToS and you could be banned if they so feel like.
Apparently they've even said using bookmarks (or "bookmark managers"?) is disallowed.
That said, Veera doesn't inject or change anything so it does not trigger the warning (not that this is a foolproof indication of safety) and works mostly transparently. They have been very lenient on these and I think the risk is still very low, but obviously the topic is in focus right now. No telling where we will end up. Use at your own risk.
As an aside, I'm taking a break until things calm down a bit. I'll likely implement a few qol features from other extensions afterwards once I figure out how to best do so.

Another ban wave just came out, it seems that the real issue is really just about UI modifications. A lot of reports on continuing to use Viramate with disabled functions and not getting suspended. I'm still using a few of my own scripts and Veera is still installed throughout all this, didn't get anything.


Make head of department lockers use EntityTables

About the PR

EntityTables allow for proper parenting of locker fills sort of, now we can reduce a lot of awful copy pasta.
Why / Balance

Fixes https://github.com/space-wizards/space-station-14/issues/24762
Technical details

Create a table containing all the non-hardsuit locker contents, use this to fill non-hardsuit lockers
Create a table containing all the hardsuit contents, use this to fill suit storage
Combine them together into another table, use this to fill hardsuit lockers
Repeat

Minor details:

Contents are alphabetically sorted for sanity.
Every hardsuit fill now contains a mask and oxygen. Many of the previous ones did not, for some reason.
The captain's jetpack was moved to the hardsuit fill, meaning the jetpack shows up in their suit storage instead of their locker. I don't know why the captain's jetpack wasn't stored with the hardsuit before since that's how the CE has theirs set up. It's not like you're going to be using the jetpack without the hardsuit anyways.
The CMO's cloak and beret were for some reason part of their hardsuit fill. I moved that to the non-hardsuit fill.

Media

Non-hardsuit locker + Hardsuit fill = Combined locker fill

Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

no in-game changes that should be noticed

Update for #30856

GUHHH


The chart is missing recommended Kubernetes labels

Currently, the Kubernetes objects in this chart are not using the recommended Kubernetes labels. For example, there is an app label (see e.g. daemonset.yaml:7) but no app.kubernetes.io/name. This makes it harder to filter for pods and other objects in a consistent manner. One of my primary use-cases for this is to group log items by app in Splunk Log Observer, but this is not possible when applications use non-standard labels.
I propose that we introduce as many of the recommended labels as possible. We should not add them mindlessly, but wherever is applicable.
I think the current labels can be mapped like this:

Old label
New label
Example value

app
app.kubernetes.io/name
splunk-otel-collector

release
app.kubernetes.io/instance
opentelemetry-collector

-
app.kubernetes.io/version
0.36.2

component
app.kubernetes.io/component
otel-k8s-cluster-receiver

heritage
app.kubernetes.io/part-of

-
app.kubernetes.io/managed-by
Helm

-
app.kubernetes.io/created-by

-
helm.sh/chart
splunk-otel-collector

This should be possible to do as a non-breaking change, since there's no conflict in letting the legacy app label stay while also introducing app.kubernetes.io/name.

Sorry, I didn't see that issue when posting!

I'm not sure how we can make it not as a breaking change. We will have to remove the old labels at some point anyway.

You are exactly on point here: removing the old labels will be breaking. However, I see no reason to do that yet. We can start by adding the new labels, have them around for a while, and next time there's a more pressing breaking change coming up we'll take that opportunity and remove the old labels. That way, we get the benefit of the new labels early while minimizing the number of breaking changes introduced. :)

@lindhe sounds good to me. Let's add all of them first, mark old ones as deprecated (as a comment right in the yaml?). Later we can just remove the deprecated labels

app.kubernetes.io/version
I think this field should reflect the version number of the component, not the chart version. Do we agree?

Yes, I agree. I think we should use .Chart.AppVersion as recommended by helm, and it needs to be defined according to the splunk-otel-collector image version.

It's so good to discuss! I had completely missed the fact that it's recommended to be .Chart.AppVersion. I thought it said .Chart.Version which i thought was a bad standard. I'll include it then, using .Chart.AppVersion!

app.kubernetes.io/part-of
Semantically, I think part-of is similar to heritage. But currently, heritage is set to Helm (or more precisely {{ .Release.Service }}) which does not make sense to me. On the other hand, managed-by should definitely be set to {{ .Release.Service }} since that's actually who's managing the release. How should we handle this?

It doesn't look like app.kubernetes.io/part-of is applicable to this chart according to its definition in https://helm.sh/docs/chart_best_practices/labels/. So let's keep app.kubernetes.io/managed-by set to {{ .Release.Service }} and omit app.kubernetes.io/part-of?

Sounds good to me.


Surprising values returned for the restful "state"

https://github.com/crc-org/vfkit/blob/main/doc/usage.md#restful-service

Get VM state
Used to obtain the state of the virtual machine that is being run by vfkit.
GET /vm/state Response: { "state": string, "canStart": bool, "canPause": bool, "canResume": bool, "canStop": bool, "canHardStop": bool

It doesn't show the possible values of "string", but it doesn't match the POST:
{
  "canHardStop": true,
  "canPause": true,
  "canResume": false,
  "canStart": false,
  "canStop": true,
  "state": "VirtualMachineStateRunning"
}

It should probably be documented? I think the values come straight from vz.

They are indeed coming from https://github.com/Code-Hex/vz/blob/c3198942b1b797ac424b673e06769f45bef0d275/virtualmachinestate_string.go#L22C1-L23C93
I agree it would make more sense to strip the VirtualMachineState, I don't think there are many users of this API right now (I'll have to check) so we can probably just do it.
And yes, documenting the possible values would be useful, a list is available there: https://github.com/Code-Hex/vz/blob/c3198942b1b797ac424b673e06769f45bef0d275/virtualization.go#L25-L67

I used both types of values
(both "enum" and string), but it did raise some eyebrows during code review...

Documenting them might be easiest

Documenting them might be easiest

Yes, it seems it is too late to be changing them, podman is parsing the VirtualMachineState* values, krunkit exposes a REST API with these values https://github.com/containers/krunkit/blob/main/docs/usage.md#restful-service , ...
Better to add documentation as you suggested.

https://en.wikipedia.org/wiki/Hyrum's_Law

If/when we make a breaking v2 API, we can fix these suboptimal names.


vue3 tsx can not find global component when use camel case.

🧐 Problem Description
PageContainer is register in global, when use componnet with tsx, camel case not find, but kebab-case work fine, why?  If i import it in file, camel case also work.

💻 Sample code
import { defineComponent } from "vue";

//  This can not find
export default defineComponent({
  name: 'FormList',
  setup () {
    return () => (
      <PageContainer>
        <template>
        </template>
      </PageContainer>
    );
  }
});

import { defineComponent } from "vue";

//  This work fine
export default defineComponent({
  name: 'FormList',
  setup () {
    return () => (
      <page-container>
        <template>
        </template>
      </page-container>
    );
  }
});

import { defineComponent } from "vue";
import PageContainer from '@common/components/Page/PageContainer';

//  This also work fine
export default defineComponent({
  name: 'FormList',
  setup () {
    return () => (
      <PageContainer>
        <template>
        </template>
      </PageContainer>
    );
  }
});

🚑 Other information

@WormGirl, unfortunately as I know you cannot use global component with jsx.

@WormGirl, unfortunately as I know you cannot use global component with jsx, because you work with pure js/ts (wihtout vue`s templates).

But i import the component in file  an use with  camel case, this work fine.

@WormGirl, unfortunately as I know you cannot use global component with jsx, because you work with pure js/ts (wihtout vue`s templates).

But i import the component in file and use with camel case, this work fine.

On your pic I see no other imports but only "vue". And yes of course it will work if you import component and use it inside other component.

I believe that using a global component/components in your application is always bad, whether you use vue with a template or jsx/tsx.

If it is certain that PageContainer has already been registered as a global component, you can utilize the resolveComponent function provided by vue to resolve it into a vue component instance first and then use it as you wish:
const PageContainer = resolveComponent("page-container")
return () => (
    <PageContainer>
        <template></template>
    </PageContainer>
)

ts的规范，大写开头的都是函数组件，没引入就找不到吧，ts里面应该需要配置一下

It's not relate to Vue JSX plugin. Try to add global components to dts file.
declare module '@vue/runtime-core' {
  export interface GlobalComponents {
  }
}


bug: helm inspect values chart > values.yaml adds fetched output

Using Helm v2.0.0, when I run helm fetch values chart > values.yaml, I see this on the header:
><> helm inspect values stable/jenkins | head -n 1
Fetched stable/jenkins to jenkins-0.1.0.tgz

I expected that to be displayed on stderr so that piping it would give me a 1:1 representation of the values.yaml file in the repo

Yeah, that should be fixed.


数据集问题

能否开源出微调的数据集？

Thanks for your interest! The paper is currently under review, and the fine-tuning data will be released afterwards.


Documentation url not found.

Bug report
Documentation url not found.
Domain https://www.ledokku.com/docs is not available.

Looks like they've lost the domain

You can access the markdown documentation
https://github.com/ledokku/ledokku/tree/master/website/docs

It's worse than not found, it links to a crappy ad page which looks like it links to spam/virus stuff ... The fact this is still in the README after being reported 17 months ago has just made me move on and look elsewhere for a dokku web UI ...


Create Json file from DCOMDIR file/DICOM folder

How to create a JSON file from DCOMDIR file/DICOM folder, like this:
{
"studies": [
{
"StudyInstanceUID": "1.2.840.1136<IP_ADDRESS>2583153.215519.978957063.78",
"StudyDescription": "BRAIN SELLA",
"StudyDate": "20010108",
"StudyTime": "120022",
"PatientName": "MISTER^MR",
"PatientId": "832040",
"series": [
{
"SeriesDescription": "SAG T-1",
"SeriesInstanceUID": "1.2.840.1136<IP_ADDRESS>2583153.215519.978957063.121",
"SeriesNumber": 2,
"SeriesDate": "20010108",
"SeriesTime": "120318",
"Modality": "MR",
"instances": [
{
"metadata": {
"Columns": 512,
"Rows": 512,
"InstanceNumber": 3,
"AcquisitionNumber": 0,
"PhotometricInterpretation": "MONOCHROME2",
"BitsAllocated": 16,
"BitsStored": 16,
"PixelRepresentation": 1,
"SamplesPerPixel": 1,
"PixelSpacing": [0.390625, 0.390625],
"HighBit": 15,
"ImageOrientationPatient": [0,1,0,0,0,-1],
"ImagePositionPatient": [11.600000,-92.500000, 98.099998],
"FrameOfReferenceUID": "1.2.840.1136<IP_ADDRESS>2583153.223134.978956938.470",
"ImageType": ["ORIGINAL","PRIMARY","OTHER"],
"Modality": "MR",
"SOPInstanceUID": "1.2.840.1136<IP_ADDRESS>2583153.215519.978957063.124",
"SeriesInstanceUID": "1.2.840.1136<IP_ADDRESS>2583153.215519.978957063.121",
"StudyInstanceUID": "1.2.840.1136<IP_ADDRESS>2583153.215519.978957063.78"
},
"url": "dicomweb://s3.amazonaws.com/lury/MRStudy/1.2.840.1136<IP_ADDRESS>2583153.215519.978957063.124.dcm"
}
]
}
]
}
]
}

Hey, you can take a look into dcmjs library, more specifically dcmjs and node.js script here
https://github.com/dcmjs-org/dcmjs/wiki/dcmjs-with-nodejs
You can read the dicom files, populate the study object, series object and instances based on the naturalized dataset that you can get from dcmjs


How did you get the Ground Truth in 3D pose?

How do you obtain the Ground Truth for 3D pose estimation? Is it derived from the model's detection results using 2D Ground Truth for training, or is it the original annotated 3D Ground Truth?
Additionally, I noticed that the Human3.6M dataset consists of individual images, while the code you provided is designed for 3D pose estimation regression on videos. Could you please advise on how to handle this situation? I look forward to your response if you have the time.

 How do you obtain the Ground Truth for 3D pose estimation? Is it derived from the model's detection results using 2D Ground Truth for training, or is it the original annotated 3D Ground Truth? Additionally, I noticed that the Human3.6M dataset consists of individual images, while the code you provided is designed for 3D pose estimation regression on videos. Could you please advise on how to handle this situation? I look forward to your response if you have the time.
I also encountered the same issue. Have you resolved it?


Camp Harmony: Campership calculation issues

You can click the "down" arrow and get a negative number in campership box -- number shouldn't go lower than zero.
If you enter a number that's too high and delete it, error message says "Campership request is a required property." Can we change this message to "Please enter a number between 0-$300"
Campership discount is 50% of the early bird economy rate. Maximum campership discount is $300.  If I choose semi-private full camp, it's $960.  I can request $480 campership and get it.   Total should be $660 due to the $300 limit.
If I sign up for 1 day early-bird Semi-private ($197) and ask for $98.50 (or more) campership, the total shown is $98.50. But it should be $126 because 1/2 the one-day economy rate is $71.

In the future, please put these as three separate issues.

sub issue 1: I can't change that, but it does indicate an error if you try to use that number
sub issue 2: I can't change these error messages right now, I will add this as a future feature to add
sub issue 3: This will be fixed in the next test cycle
sub issue 4: this will be fixed in the next test cycle, I missed the "economy rate" part of the formula (this camp is complicated)

got it. Ok to all.


Models move a bit when a student looks at the assessment they got and select elements

Describe the bug
Models move a bit when a student looks at the assessment they got and select elements.
Note: I tested this both on production 4.6.0 and on #2168.
To Reproduce

Submit modelling exercise submission
Grade submission as TA/Instructor
View Result as Student again, move mouse over submission and select and deselect elements.
The diagram should move a tiny bit around sometimes.

Expected behavior
The diagram should not move when moving the mouse over it and selecting elements.
Screenshots

(This also works with other diagram types)
Environment

 - OS: Win 10
 - Browser Vivaldi (Chromium)

Tested the issue with different modelling exercise types on both Chrome and Firefox and wasn't able to reproduce the issue. Therefore, I close the bug. We can reopen it if it occurs again.


Enhancement: Footer in the table

Hi, on the tables, by example, the table monitors, could it be possible to select the number of rows to display ?
And also, show the number of pages of this table !
view image attached

Thanks in advance

Yes, click on a button between next and previous buttons.

Made it simpler and added this icon:


graduation: Versionize the documents for every SDKs

Currently, the documentation is only for the latest, which could cause confusion for the end users.

Tasks

[ ] Find ways to versionize the documents for every SDKs, maybe via https://nightlies.apache.org/

I plan to take a snapshot of the website and deploy it on nightlies whenever we make a release.
It will be the place where we distribute historical documents. Also for the latest stable version.
Whereas our website defaults to displaying documents up to the unstable version, it means documents on the main branch are published directly to opendal.apache.org after each commit.

I plan to take a snapshot of the website and deploy it on nightlies whenever we make a release.

So it will be something like https://nightlies.apache.org/flink/flink-docs-release-1.19/?
Potential issues include the need to add a header redirecting users to our most recent documents, and providing links to previous versions of these documents. Do you have a strategy for addressing these concerns?

So it will be something like https://nightlies.apache.org/flink/flink-docs-release-1.19/?

Yes.

Potential issues include the need to add a header redirecting users to our most recent documents, and providing links to previous versions of these documents. Do you have a strategy for addressing these concerns?

It's easy to do this. Docusaurus has provided a convenient way to add the banner. We can also provide links or a page of documents' link list to past versions of the documentation.

Great, would you like to take over this issue?

Great, would you like to take over this issue?

Yep.

Over the past two days, I have been attempting to manually deploy the build of the website to the nightlies.
However, I encountered several strange issues, and I believe that manual deployment is not feasible.
Therefore, I plan to deploy the previous versions of our docs once the secrets are configured, using a temporary workflow.

Therefore, I plan to deploy the previous versions of our docs once the secrets are configured, using a temporary workflow.

We can start deploying since our next release. No bother to build the previous version.

We can start deploying since our next release. No bother to build the previous version.

Thank you. However, I will still consider this option.
I plan to deploy two copies for each version when we do release.
One will be named release-${version}, which will remain unchanged after deployment.
The other one will be named stable, and it will be overwritten when we do release. We need a place where users can quickly access our latest documentation version.

I plan to deploy two copies for each version when we do release.
One will be named release-${version}, which will remain unchanged after deployment.
The other one will be named stable, and it will be overwritten when we do release. We need a place where users can quickly access our latest documentation version.

Simple.
We can run the same deploy twice: one for tagged version, one for stable.

The UI/UX work could be moved to other thread.


buildImage not copying over directory contents

My Dockerfile looks like.
FROM node:5.8.0

COPY . /my-project

WORKDIR /my-project

RUN npm install

CMD ["node", "server.js"]

No modules are installed. And then errors about how package.json does not exist.
var Docker = require('dockerode');
var docker = new Docker();

docker.buildImage('Dockerfile.tar', {t: 'myproject'}, function(err, stream) {
  if(err) return;

  stream.pipe(process.stdout, {end: true});

  stream.on('end', function() {
    done();
  });
});

When I run in my terminal from inside the directory like so
docker build .
It builds perfectly fine and then I can run and access my container locally.

human error.  tar should include all the things.


JSON post loader

Bug report
Currently, I can't create a post loader for JSON files.
Related question

What is the current behavior?
I've created a custom loader, which reads JSON files and returns a react component. With my understanding, the "enforce" property for a rule should make the loader run after normal loaders are run, when set to "post". Therefore, it should be possible to return a react component instead of JSON.
But somehow this doesn't work and I get an invalid JSON error, because the integrated JSON loader still tries to load JSON even though this shouldn't happen after a post loader, or should it?

What is the expected behavior?
I'd like to "extend" the JSON loader with my own loader for specific files like *.xyz.json, but I can't see how this is currently possible, because it always runs as the last loader.

Other relevant information:
webpack version:  4.39.0

Hey @josias-r,
You'll have to set the type of the rule using your loader to something else than json if you don't want its output to go through the default JSON parser: https://webpack.js.org/configuration/module/#ruletype
Currently a loader can't do it itself without using some internal properties (see https://github.com/webpack/webpack/issues/7057)

Answer above use https://webpack.js.org/configuration/module/#ruletype, you can setup loader too, like
module.exports = {
  //...
  module: {
    rules: [
      //...
      {
        test: /\.json$/,
        type: 'javascript/auto',
        loader: 'custom-json-loader'
      }
    ]
  }
};

🤯thank you very much! I was searching for this for so long, I don't know why I couldn't find it.


YJIT-Metrics CI Benchmarking: Benchmark at 2021-12-05-071025 is significantly slower than the one before (2021-12-04-191004)!

Error running benchmark CI job on Linux ip-172-31-8-3 5.8.0-1038-aws #40~20.04.1-Ubuntu SMP Thu Jun 17 13:25:28 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux:

Latest failing benchmark: blog_speed_details_2021-12-05-071025.tripwires.json
Compared to previous benchmark: blog_speed_details_2021-12-04-191004.tripwires.json

Failing benchmark names: ["binarytrees"]

Failure details:

[
  {
    "benchmark": "binarytrees",
    "current_mean":<PHONE_NUMBER>169715,
    "second_current_mean":<PHONE_NUMBER>8941815,
    "current_stddev": 1.7151415055247814,
    "current_rsd_pct": 0.49761540306271135,
    "second_current_stddev": 0.23210866915086542,
    "second_current_rsd_pct": 0.08152752969957613
  }
]

This was transient and it's now fine.


Add README.md for each packages

It closes #87
This PR contains

meta tags for homepages
README.md for each packages
Revise badges and descriptions in README
Fix typo broswer-crypto => browser-crypto

@cre8 I updated some changes. :)


Support for rocketchat import with filesystem storage

I'm trying to import data from our rocketchat instance, and it seems zulip script awaits data dump in different format. I've tried to make mongodump as stated in import manual, but after I've tried to convert it results in:
Converting Data ...
Traceback (most recent call last):
  File "/home/zulip/deployments/2024-03-05-08-36-11/./manage.py", line 151, in <module>
    execute_from_command_line(sys.argv)
  File "/home/zulip/deployments/2024-03-05-08-36-11/./manage.py", line 116, in execute_from_command_line
    utility.execute()
  File "/srv/zulip-venv-cache/f87f01ad8099e2ca6e45fada8fb7f7e811577881/zulip-py3-venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 436, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/srv/zulip-venv-cache/f87f01ad8099e2ca6e45fada8fb7f7e811577881/zulip-py3-venv/lib/python3.10/site-packages/django/core/management/base.py", line 412, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/srv/zulip-venv-cache/f87f01ad8099e2ca6e45fada8fb7f7e811577881/zulip-py3-venv/lib/python3.10/site-packages/django/core/management/base.py", line 458, in execute
    output = self.handle(*args, **options)
  File "/home/zulip/deployments/2024-03-05-08-36-11/zerver/management/commands/convert_rocketchat_data.py", line 48, in handle
    do_convert_data(rocketchat_data_dir=data_dir, output_dir=output_dir)
  File "/home/zulip/deployments/2024-03-05-08-36-11/zerver/data_import/rocketchat.py", line 1055, in do_convert_data
    rocketchat_data = rocketchat_data_to_dict(rocketchat_data_dir)
  File "/home/zulip/deployments/2024-03-05-08-36-11/zerver/data_import/rocketchat.py", line 1006, in rocketchat_data_to_dict
    with open(
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/backup/rocketchat/rocketchat_avatars.files.bson'

We have rocketchat configured to store data in fs storage. There is https://github.com/RocketChat/filestore-migrator  but I dont know what type of storage I have to convert to to use zulip import scripts.

@mateuszmandera @rht any idea what the issue could be here?

If it is not .bson, what is the file format that you observed in the mongodump output?

If it is not .bson, what is the file format that you observed in the mongodump output?

it is json and bson like:
assets.chunks.bson
assets.chunks.metadata.json
assets.files.bson
assets.files.metadata.json
instances.bson
instances.metadata.json
meteor_accounts_loginServiceConfiguration.bson
meteor_accounts_loginServiceConfiguration.metadata.json
meteor_oauth_pendingCredentials.bson
meteor_oauth_pendingCredentials.metadata.json
meteor_oauth_pendingRequestTokens.bson
meteor_oauth_pendingRequestTokens.metadata.json
migrations.bson
migrations.metadata.json
omnichannel_auto_close_on_hold_scheduler.bson
omnichannel_auto_close_on_hold_scheduler.metadata.json
omnichannel_queue_inactivity_monitor.bson
omnichannel_queue_inactivity_monitor.metadata.json
omnichannel_scheduler.bson
omnichannel_scheduler.metadata.json
pbx_events.bson
pbx_events.metadata.json
_queue.bson
_queue.metadata.json
_raix_push_app_tokens.bson
_raix_push_app_tokens.metadata.json

but there is no *.files.bson files in dump, since all uploads and avatars is stored as plain files.

for example for avatars I only have this in mongo dump
ls -1 /tmp/backup/rocketchat/rocketchat_avatars*
/tmp/backup/rocketchat/rocketchat_avatars.bson
/tmp/backup/rocketchat/rocketchat_avatars.metadata.json

The mongodump output might have changed since the test fixture was last created (https://github.com/zulip/zulip/tree/main/zerver/tests/fixtures/rocketchat_fixtures) on July 28 2021.
Not to mention that there might have been several DB schema migrations.

@HighwayStar If you rename /tmp/backup/rocketchat/rocketchat_avatars.bson to /tmp/backup/rocketchat/rocketchat_avatars.files.bson, you should be able to get to the next missing file, which you might have to add the .files in the name. And so on.
But this approach might not work if there has been schema changes since 2021.


Difficulties in Running Sample Code in README.md

Hi,
I am new to elastic search and am looking to load in a large number of xml files. I was excited to find your plugin but am experiencing difficulties.Following successful install of your plug and restating of ES I attempted to execute the sample code in README.md with the following errors. Perhaps I am doing something incorrect
Code starting: curl '0:9200/_search?pretty'
Error: >       "_score" : 1.0, "_source" : {"@context":{"p":"http://dummy.org"},"p:foo":"bar"}

} ]

-bash: syntax error near unexpected token `]'
Code starting: curl -H 'Accept: application/xml'  '0:9200/_search?pretty'
Error: There appears to be no quoting of the xml and when I attempt this I get parse exception errors.
As I am new to this I assume that there is something simple I am doing incorrectly and I was hoping that you could guide me.
Kind regards,
Alex

In the README, I was sloppy while formatting the demonstration. Please consider only the lines beginning with curl as commands that should be entered. The lines after curl are the output of the command for documentation.
The plugin is not considered to work with existing XML files. It assumes special XML that match the conventions of Elasticsearch to the JSON transformation is straightforward. In general, it does not save you from preprocessing existing XML.

Thanks for taking the time to deal with my newbie query :) I should have definitely spotted that.
The standard commands to interact with elasticsearch node are giving the expected responses but when I am attempting to use your extension the node is returning an error. I am guessing it is another newbie mistake so if you can point me in the right direction to further reading etc to resolve this issue I would be very grateful :)
Command : curl -H 'Accept: application/xml'  '0:9200/_search?pretty'
Error
2016-08-23 11:16:49,219][ERROR][org.xbib.elasticsearch.rest.xml.XmlFilter] Not implemented
java.lang.UnsupportedOperationException: Not implemented
at org.codehaus.stax2.ri.Stax2WriterAdapter.writeRaw(Stax2WriterAdapter.java:380)
at org.codehaus.stax2.ri.Stax2WriterAdapter.writeRaw(Stax2WriterAdapter.java:373)
at com.fasterxml.jackson.dataformat.xml.util.DefaultXmlPrettyPrinter$Lf2SpacesIndenter.writeIndentation(DefaultXmlPrettyPrinter.java:511)
at com.fasterxml.jackson.dataformat.xml.util.DefaultXmlPrettyPrinter.writeLeafElement(DefaultXmlPrettyPrinter.java:321)
at com.fasterxml.jackson.dataformat.xml.ser.ToXmlGenerator.writeNumber(ToXmlGenerator.java:814)
at org.xbib.elasticsearch.common.xcontent.xml.XmlXContentGenerator.writeNumber(XmlXContentGenerator.java:173)
at org.xbib.elasticsearch.common.xcontent.xml.XmlXContentGenerator.copyCurrentEvent(XmlXContentGenerator.java:409)
at org.xbib.elasticsearch.common.xcontent.xml.XmlXContentGenerator.copyCurrentStructure(XmlXContentGenerator.java:378)
at org.xbib.elasticsearch.common.xcontent.xml.XmlXContentGenerator.copyCurrentStructure(XmlXContentGenerator.java:373)
at org.xbib.elasticsearch.common.xcontent.xml.XmlXContentGenerator.copyCurrentStructure(XmlXContentGenerator.java:348)
at org.xbib.elasticsearch.common.xcontent.XmlXContentBuilder.copyCurrentStructure(XmlXContentBuilder.java:1005)
at org.xbib.elasticsearch.rest.xml.XmlFilter$XmlChannel.sendResponse(XmlFilter.java:166)
at org.elasticsearch.rest.action.support.RestResponseListener.processResponse(RestResponseListener.java:43)
at org.elasticsearch.rest.action.support.RestActionListener.onResponse(RestActionListener.java:49)
at org.elasticsearch.action.support.TransportAction$1.onResponse(TransportAction.java:89)
at org.elasticsearch.action.support.TransportAction$1.onResponse(TransportAction.java:85)
at org.elasticsearch.action.search.SearchQueryThenFetchAsyncAction$2.doRun(SearchQueryThenFetchAsyncAction.java:138)
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Command:  curl -H 'Accept: application/xml' '0:9200/a/c/2?pretty'
Response: Not implemented
Command: url -H 'Accept: application/xml' '0:9200/a/c/2?pretty'

OK, I noticed the build is wrong, A jar is missing in the plugin zip. Please put the woodstox 5.0.2 jar into the "plugins/xml' folder, from the URL
http://search.maven.org/remotecontent?filepath=com/fasterxml/woodstox/woodstox-core/5.0.2/woodstox-core-5.0.2.jar
Maybe this is sufficient to make it work again. The jar will be included in the next release.

Hi Jorg,
I have attempted the solution proposed but I am still getting the error below. If you have any additional advice I would be grateful. I am looking forward to using your plugin in relation to dataset management for some phd research I am doing in deep learning related to handwriting recognition :)
2016-08-23 23:12:31,819][ERROR][org.xbib.elasticsearch.rest.xml.XmlFilter] Not implemented
java.lang.UnsupportedOperationException: Not implemented
at org.codehaus.stax2.ri.Stax2WriterAdapter.writeRaw(Stax2WriterAdapter.java:380)
at org.codehaus.stax2.ri.Stax2WriterAdapter.writeRaw(Stax2WriterAdapter.java:373)
at com.fasterxml.jackson.dataformat.xml.util.DefaultXmlPrettyPrinter$Lf2SpacesIndenter.writeIndentation(DefaultXmlPrettyPrinter.java:511)
at com.fasterxml.jackson.dataformat.xml.util.DefaultXmlPrettyPrinter.writeLeafElement(DefaultXmlPrettyPrinter.java:321)
at com.fasterxml.jackson.dataformat.xml.ser.ToXmlGenerator.writeNumber(ToXmlGenerator.java:814)
at org.xbib.elasticsearch.common.xcontent.xml.XmlXContentGenerator.writeNumber(XmlXContentGenerator.java:173)
at org.xbib.elasticsearch.common.xcontent.xml.XmlXContentGenerator.copyCurrentEvent(XmlXContentGenerator.java:409)
at org.xbib.elasticsearch.common.xcontent.xml.XmlXContentGenerator.copyCurrentStructure(XmlXContentGenerator.java:378)
at org.xbib.elasticsearch.common.xcontent.xml.XmlXContentGenerator.copyCurrentStructure(XmlXContentGenerator.java:373)
at org.xbib.elasticsearch.common.xcontent.xml.XmlXContentGenerator.copyCurrentStructure(XmlXContentGenerator.java:348)
at org.xbib.elasticsearch.common.xcontent.XmlXContentBuilder.copyCurrentStructure(XmlXContentBuilder.java:1005)
at org.xbib.elasticsearch.rest.xml.XmlFilter$XmlChannel.sendResponse(XmlFilter.java:166)
at org.elasticsearch.rest.action.support.RestResponseListener.processResponse(RestResponseListener.java:43)
at org.elasticsearch.rest.action.support.RestActionListener.onResponse(RestActionListener.java:49)
at org.elasticsearch.action.support.TransportAction$1.onResponse(TransportAction.java:89)
at org.elasticsearch.action.support.TransportAction$1.onResponse(TransportAction.java:85)
at org.elasticsearch.action.search.SearchQueryThenFetchAsyncAction$2.doRun(SearchQueryThenFetchAsyncAction.java:138)
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

I released plugin version <IP_ADDRESS> with a fix.
Thanks for reporting.

Hi Jörg, tested on my local install and it is working great, look forward to exploring it more over the next few days: ) Thanks for all your hard work!


Bug:  Can't pickle local object during save

Can't save model
Somehow, I remember successfuly saving it once before, but it no longer works.
I've tried to play with the home_dir parameter in the config, cleaning it, and using a tempfile.TemporaryDirectory but can no longer save my models.
Version: 0.1.14

Tried from pip and from master

System: OSX
Reproduce:
from deeptables.models import deeptable
from sklearn.datasets import load_iris

data = load_iris()
X = data['data']
y = data['target']
conf = deeptable.ModelConfig(
        nets=['dnn_nets'],
        metrics=['AUC'],
        optimizer=keras.optimizers.RMSprop(),
    )
dt = deeptable.DeepTable(config=conf)
dt.fit(X, y)
dt.save('model')

Error:
Load model from disk:models/dt/dnn_nets.h5.
Traceback (most recent call last):
  File ".../python3.7/site-packages/IPython/core/interactiveshell.py", line 3437, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-19-5a45263f9c71>", line 1, in <module>
    dt.save('model')
  File ".../python3.7/site-packages/deeptables/models/deeptable.py", line 723, in save
    pickle.dump(self, output, protocol=2)
AttributeError: Can't pickle local object 'make_gradient_clipnorm_fn.<locals>.<lambda>'

I might have found the issue.
It is the same as this phygnn issue and they fixed it.
I verified that when I downgraded to TF 2.3.0, I managed to save again.

@xdssio Thanks for your report.
The model is saved including model config (class deeptable.ModelConfig), and the optimizer you set optimizer=keras.optimizers.RMSprop() in model config cannot be pickled at TF version 2.4.0(in my machine);
You can try to set optimizer='RMSprop' if need to use TF 2.4  :
from deeptables.models import deeptable
from sklearn.datasets import load_iris

data = load_iris()
X = data['data']
y = data['target']
conf = deeptable.ModelConfig(
        nets=['dnn_nets'],
        metrics=['AUC'],
	# optimizer=keras.optimizers.RMSprop(),
        optimizer='RMSprop',
    )
dt = deeptable.DeepTable(config=conf)
dt.fit(X, y)
dt.save('model')


Add spawnOnOnce and related functions.

Description
Added spawnOnOnce, spawnNOnOnce and spawnAndDoOnce to XMonad.Util.SpawnOnce.
These functions combine the functionality of spawnOnce with spawnOn. That is they allow an application to be spawned and shifted to a particular workspace and also prevents the applications from being launched again by xmonad --restart.
spawnNOnOnce spawns an application n number of times on the given workspace. For example, my startup hook creates four terminal windows on my "xterms" workspace.
spawnAndDoOnce takes a ManageHook that is applied to the application after it starts. This is useful for combing multiple actions, for example, shift to a particular workspace and move the window down in the window stack.
Also, I'm a Haskell noob so if there is a better to accomplish this please me know.
Checklist

[X] I've read CONTRIBUTING.md

[X] I tested my changes with xmonad-testing
- Sort of, I had to hack run-in-xephyr.sh to get it to work.

[X] I updated the CHANGES.md file

Looks good to me, thanks!


wasm build failure for primitives crate

We're building a module for a custom substrate node that uses elements from core/primitives. When we add our new module to the runtime, as specified in the custom Substrate chain tutorial, we get a failure from the build.sh script. This failure originates with the ring dependency, which is used by the ed25519 API inside core/primitives.
Steps to reproduce:

Make sure you have substrate checked out and build dependencies installed.
Navigate to core/primitives.
Run cargo +nightly build --target=wasm32-unknown-unknown --release.

What should our next steps be?

Are you adding the core/primitives with default-features = false?

Adding default-features = false to our module fixed the WASM build, thanks.


how we are working

@h1alexbel thank you for reporting this. I'll assign someone to take care of it soon.

@h1alexbel I couldn't find any assignee for this task. This is either because there are no contributors with role DEV available or because the project does not have enough funds.
Please, make sure there is at least one available contributor with the required role and the project can afford to pay them.

@h1alexbel this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-09-20T16:09:01.577378.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@h1alexbel thank you for resolving this ticket. I've just added it to your active invoice. You can always check all your invoices and more on the Contributor Dashboard.


Save game from FICS

Add option to save a game to the game database or to a pgn file.

implemented.  please close.


[WFLY-18406] Upgrade ironjacamar to 3.0.5.Final

https://issues.redhat.com/browse/WFLY-18406
Upgrade because of refactor in IronJacamar which removes usage on jboss-threads blocking API

/retest

@bstansberry ok, I will make some notes about it in my docs

@tadamski It looks like it was the GH actions that were affected by the artifact not being available when they ran. It looks like  the TeamCity jobs had lots of ordinary test failures.

/retest


When workload cluster deployed with Avi, kubeconfig get throws error - can't assign requested address

Bug Report
When a TKG workload cluster is deployed on vSphere using kube-vip but without Identity Management (no pinniped), users are shown a reasonable error when they attempt to retrieve the kubeconfig information:
$ tanzu cluster kubeconfig get tkg-workload-1
Error: failed to get pinniped-info from management cluster: failed to get pinniped-info from the cluster
Usage:
  tanzu cluster kubeconfig get CLUSTER_NAME [flags]

When a TKG workload cluster is deployed on vSphere using NSX ALB (Avi) but again without Identity Management , users are shown a very odd error when they attempt to retrieve the kubeconfig information:
% tanzu cluster kubeconfig get workload
Error: failed to get cluster-info from cluster: failed to get cluster-info from the end-point: Get "https://:0/api/v1/namespaces/kube-public/configmaps/cluster-info": dial tcp :0: connect: can't assign requested address
Usage:
  tanzu cluster kubeconfig get CLUSTER_NAME [flags]

Adding --admin to the command works in both cases, so it is just the error that is different.
% tanzu cluster kubeconfig get workload --admin
Credentials of cluster 'workload' have been saved

Expected Behavior

I would expect that there is a common error in both cases. While even the Pinniped error itself is not ideal - see  #847 - the error thrown when the NSX ALB is present is very poor, can lead to customers spinning there wheels determining what the issue is, and can lead to a poor UX overall. This needs to show the same error as the case without NSX ALB at the very least.
Steps to Reproduce the Bug

Deploy TKG management cluster on vSphere with NSX ALB, and then deploy workload cluster on same vSphere cluster using same NSX ALB.
Environment Details

Build version (tanzu version):
version: v1.4.0-pre-alpha-2
buildDate: 2021-08-19
sha: 75cfa0e
Operating System (client):
macOS (Big Sur) 11.5.2, deploying to vSphere 7.0U2c (build 18356314)

Hi Cormac - this is something that tanzu-framework will need to prioritize. I've created the following issue:

[ ] https://github.com/vmware-tanzu/tanzu-framework/issues/837


Input left to right

feature request please?
an option to do left to right or (right to left, your default)

@chitgoks Thank you for using.
This is for currency inputs so right to left only.
If you want to left to right. You can use Regexp instead.


Reconcile DB models based on alembic autogenerate

Changed a few SQLAlchemy column definitions to solve differences shown by alembic autogenerate.
Bump version to 2.7.0rc2

Created follow-up for SubscriptionSearch https://github.com/workfloworchestrator/orchestrator-core/issues/724


Migrate from being a CommonJS module to a ECMAScript module

ECMAScript modules is the new standard for javascript modules and the NPM ecosystem has started the process of transition. This has started to become a pain point as some of our dependencies have performed a hard transition with no CJS exports available. ESM modules cannot be loaded from CJS, but CJS can be loaded from ESM. We need to make the necessary project changes to be ESM.
Acceptance Criteria:

Development dependency configurations updated to support ESM and function properly

typescript (see: https://www.typescriptlang.org/docs/handbook/esm-node.html)
jest
cypress
package.json (ex: type and exports properties)
babel
prettier
eslint (rules for eslint and prettier may have to be changed depending on ESM support)

RS source files fixed to support ESM (ex: relative imports must have file extension)

This was finally accomplished with the jest -> vitest migration.


[Features] Delta Green by ArcDream V2.05+

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[ ] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[x] I have authorization from the game's publisher to make this an official sheet on Roll20 with their name attached.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

[Style] Added Polaroid Effect to sheet
[Style] New Preview image showcasing the redesign in the CSE format
[Feature] Scrollable textarea
Modified sheet.json to remove the old feature list and add a link to the instruction wiki

Character Sheet Info Roll20 Internal Use only.

Is there a way to know what the failure check is? I removed 2 images that I was only used as mocking of feature to implement and were not used in the sheet nor submitted is the previous version.

Is there a way to know what the failure check is? I removed 2 images that I was only used as mocking of feature to implement and were not used in the sheet nor submitted is the previous version.

[ ] The pull request makes changes to files in only one sub-folder.
Should that box be checked?

implement

Ok my bad, I changed the json file, it was the point of this commit :D


new version issue

when i update this new version i found 1 error if you delete some file while it is not completly upload then after this file no file will be deleted but if u delete file that is uploaded then noting will be worng as well as no file will be deleted in example no 2 after the first one just ask to del but noting to do.in previous version none of these type of errors are occured

what?

when i update this new version i found 1 error
if you delete some file while it is not completly upload then after this file no any other file will be deleted but if u delete file that is completely uploaded then noting will be worng
as well as
No file will be deleted in example no 2 after the deletet the one after this just ask to del but noting to do.
In previous version none of these type of errors are occured

you have an awsome work plz check thses error and solve we are waiting for this

sorry but i have no time now. I will make this in September.

I think ur first version is more stable than this in which the only issu is that the files will not remove after completely upload
Sent from my HTC
----- Reply message -----
From: "CreativeDream"<EMAIL_ADDRESS>To: "CreativeDream/jquery.filer"<EMAIL_ADDRESS>Cc: "shaheer-javaid"<EMAIL_ADDRESS>Subject: [jquery.filer] new version issue (#21)
Date: Fri, Aug 7, 2015 6:16 pm
sorry but i have no time now. I will make this in September.

Reply to this email directly or view it on GitHub:
https://github.com/CreativeDream/jquery.filer/issues/21#issuecomment-128696503

I think ur first version is more stable than this in which the only issu is that the files will not remove after completely upload

if u give me a favour add onRemove function in version 1 to del files after upload
----- Reply message -----
From: "CreativeDream"<EMAIL_ADDRESS>To: "CreativeDream/jquery.filer"<EMAIL_ADDRESS>Cc: "shaheer-javaid"<EMAIL_ADDRESS>Subject: [jquery.filer] new version issue (#21)
Date: Fri, Aug 7, 2015 6:16 pm
sorry but i have no time now. I will make this in September.

Reply to this email directly or view it on GitHub:
https://github.com/CreativeDream/jquery.filer/issues/21#issuecomment-128696503

If it is possible for your self

hey, on the line 688 change "if(input.size() == 0)" to "if(input.size() <= 1)". I thin it will solve the file exclusion problem on your new version

okay i will check thanks in advance
----- Reply message -----
From: "erickstryck"<EMAIL_ADDRESS>To: "CreativeDream/jquery.filer"<EMAIL_ADDRESS>Cc: "shaheer-javaid"<EMAIL_ADDRESS>Subject: [jquery.filer] new version issue (#21)
Date: Tue, Aug 18, 2015 10:14 pm
hey, on the line 688 change "if(input.size() == 0)" to "if(input.size() <= 1)". I thin it will solve the file exclusion problem on your new version

Reply to this email directly or view it on GitHub:
https://github.com/CreativeDream/jquery.filer/issues/21#issuecomment-132283273

thanks a lot erikstryck this one is resolve but del file issue is remaining if you have some idea how to resolve it then plz share it

Fixed in v.1.0.3. Update it.

Creative Dream i want one more things when the files is fully uploads thenif if i delete some one it also delete from data base(uploads folder)


Custom Theme for Different Modes

It would be visually appealing and informative to have distinct backgrounds and icons for break and focus modes. This enhancement would improve the overall aesthetic and usability of the application.

This is a good suggestion. If you'd like to work on this, you're more than welcome.
Changing the icon should be straightforward, you can pick another freely licensed icon from flaticon.com, then it's a matter of changing the html element from tiktock.js file based on the mode.
For changing the background, I don't have much experience changing css from the javascript file but I assume it'll be a similar process to changing the icon.
When choosing new colors and icons, please keep in mind the current aesthetic of our program.

Check pull request #15, there's similar kind of change.


feat: Add Balance column on Tokens Page

Description
resolves #34
Demo

Checklist:

[x] I have read and followed the Contributing Guide
[x] display total supply

I finished the task, but I am not sure about it's purposes. Depends on what we want to show
The problem is that in the listing https://mainnet.aeternity.io/mdw/v2/aex9?limit=10 there is a event_supply that often is 0.
I think we want to show the total supply. So it we show the same value in listing as well as in detail.
This total supply value can be obtained from node through the SDK. Which mean the value is glued to the result per every row. It's a bit heavyweight solution but it works. Pls let me know @michele-franchi

Reopened here https://github.com/aeternity/aescan/pull/607


Service Call Hangup

I'd like to preface this with I am not quite sure yet if this is an rmw_zenoh issue or an eclipse zenoh/zenoh-c issue.
Some basic system information :
Platform: Ubuntu 24.04
Rustc: 1.75.0
GCC: 9.5.0
ROS2 packages: latest rolling as of 03/27/2024, built from source (will try to reproduce w/ latest and greatest today)
The issue:
It seems that when making service calls to a ROS2 node that the service call will hangup and not return (or even just segfault as I have seen, but that was only reproducible w/ custom debug builds), however this has only been observed to occur under some specific circumstances. Firstly, the server node in this case must be logging via the RCLCPP_* calls (we use RCLCPP_INFO for example). Secondly, there should be a publisher node that the server is subscribed to. We are publishing ~245 KiB at a rate of  50 Hz, so about 12 MiB/s. The second step isn't strictly necessary, but it seems to help trigger the issue. In my debug builds I didn't need to run the publisher node.
Through my own debugging it seems that an indefinite wait occurs here (https://github.com/eclipse-zenoh/zenoh/blob/05b9cb459f77693bbf7c89d67265ba1519959814/zenoh/src/net/routing/dispatcher/pubsub.rs#L435) waiting for the writer to release its hold of the RwLock. I have been unsuccessful in determining where that writer lock is being acquired, if that is in fact what is going on here, however as acquiring said lock is done via an RwLockWriteGuard object, whenever that object is dropped/goes out of scope, ownership should at that point be relinquished and the reader free to acquire the lock. I've also inspected the call stacks of other threads and did not observe any lingering RwLockWriteGuard's still on the stack.
This problem occurs in both normal operation and shared_memory mode.
An interesting note too is that directly publishing to /rosout is not sufficient to trigger the bug -- logging MUST be via the RCLCPP_* interface.
I will update this issue as I make more debugging progress.
To reproduce:
Build and run the Docker container located here: https://github.com/jackg0/ros2_simple_tests
Launch the zenoh router via ros2 run rmw_zenoh_cpp rmw_zenohd
Launch both the simple server and the simple publisher
Trigger the issue via making service calls to the server with ros2 service call /simple_server/trigger std_srvs/srv/Trigger
I hope that this information can provide some insight and as I said above I will be actively debugging this myself and providing updates as they come.

For sanity check, does the system work as expected with rmw_fastrtps_cpp and rmw_cyclonedds_cpp?

I ran the test files in a Iron setup (not in Docker) with rmw_cyclonedds_cpp and rmw_zenoh_cpp (both rolling and https://github.com/ros2/rmw_zenoh/pull/146 branches).
The ros2 service call /simple_server/trigger std_srvs/srv/Trigger  was always successful.
Could it be a temporary issue with rclcpp in Rolling or with your Dockerized environment ?

Apologies for not getting back to you for so long.
I've done some more testing and have confirmed on both Rolling and Jazzy that the issue is still present and can be triggered by the same steps as described in the issue. I will say that it may take a fair bit of service calls to trigger the hang up, so I would recommend doing something like:
while true; do
ros2 service call /simple_server/trigger std_srvs/srv/Trigger;
done

Also it does not appear to occur w/ other RMW's.
I don't have any other updates on this issue, but just wanted to get back to you guys on this.

@bagelbytes61 thanks for following up. Could I confirm that you tested after https://github.com/ros2/rmw_zenoh/pull/134 was merged? (You'll need to do a clean build and also ensure you kill the daemon with ros2 daemon stop before that)

@bagelbytes61 I'm unable to reproduce the issue with the latest rolling branch in rmw_zenoh.
I've been continuously making the service call for over 15mins now and am able to get a successful response each time. See video below for a snippet from this test (the warning can be ignored as it is a known issue and caused by something else).
https://github.com/ros2/rmw_zenoh/assets/13482049/b50593e5-eba2-4e81-a26c-ad0fa5d04802

Hmm. Interesting. Could I ask which version of rustc you are using to compile zenoh-c? I have been using 1.75.0, though I just tried 1.78.0 and experienced the same behavior. Also could I ask about your environment? I am using a fresh Ubuntu 24.04 virtual machine that I apt install'd ros-rolling-desktop onto and built the rmw_zenoh_cpp package with GCC 13.2.0 and rustc 1.75/1.78.

I'm compiling with 1.75.0 rustc.
Clean Ubuntu 24.04 but I have ROS 2 Rolling built from source. I don't see the problem with Iron binaries on 22.04 either.
I do have everything built in Release mode.
When you start continuously making service calls, do you see the problem immediately or after several minutes? I could try running my test for longer...

Okay I was able to reproduce it after running for a longer time.

@bagelbytes61 I opened PR https://github.com/jackg0/ros2_simple_tests/pull/3 to add a script that creates a node which makes the service calls indefinitely. I've had this script running for over 2 hours now without any hangup issues.
There is one big difference between between this script and running ros2 service call ... within a bash while loop. In the former, the ROS context and hence zenoh session is created once and then service calls are made indefinitely. In the latter, the context and session is created each time the ros2 service call command is run and more importantly destructed each time. There are some known issues related to shutting down the zenoh session eg. https://github.com/ros2/rmw_zenoh/issues/170 and when handling SIGINT signal in rclpy which I suspect may be the root cause.

We refactored a lot of this earlier this year, so I believe that this issue is fixed.  Because of that, I'm going to close this out.  If that is not the case, please feel free to reopen and we can debug some more.


fix: Update demos and documentation

Some demo configurations (MinIO service name and Druid Middlemanager resources), commands (Kafka probing and SQL queries) and product UIs were outdated / defective. This PR fixes them. Also fixes minor typos and adds consistency between the two nifi-kafka-druid demos.
Extending this PR to other demos and their documentation as well. Similar tasks of updating screenshots, typos etc.

Some of the images are smaller than before. Just check what that looks like in the rendered site.

Thanks for the idea! Tried it with local rendering and it looked fine to me. If someone else wants to try it and has some feedback though, I can update the screenshots as well.

I'm ok with the images sizes, though some of the text is on the smaller side.
We will add some tips for doing this in the new issue templates for the release process: https://github.com/stackabletech/issues/pull/602