Migrate React Native website to Docusaurus V2

This PR migrates the React Native website to Docusaurus V2.
This is an effect of collaboration with @slorber and MLH Docusaurus team (@darshkpatel & @teikjun).
It is the initial import, rebased against current master in the main repository.
Refs: #2146, #2139
Fixes #2208, Fixes #2054
Preview

https://deploy-preview-2263--react-native.netlify.app

Noticeable changes for website user

SPA - reduced page load times, more fluid navigation
additional dark theme and theme toggle (dark theme Snacks too)
build in tabs sync
Snacks appears on mobile without the preview but with link to open example in Expo app
blog posts are now searchable
code blocks content can be copied by click - "Copy" button appears on hover
old versions and next page have a notice for users that they are reading old or upcoming version of the page

Noticeable changes for contributors/maintainers

announcement bar support out of the box
MDX fragments - which allows to split content and helps to maintain large pages (example: Environment Setup)
extended page customizability and theme components swizzling
improved build times
still growing set of ready to use plugins - https://v2.docusaurus.io/docs/using-plugins/
<!--truncate--> tag for blog posts to hide the details on the post list, blog posts tags

You can read more about V2 features and changes in the official documentation:

https://v2.docusaurus.io/docs/

Deploy preview for react-native failed.
Built with commit aea653ec26394355b19976ca2ba2ebdba157d0a1
https://app.netlify.com/sites/react-native/deploys/5f8f292c26a6970007f559df

Deploy preview for react-native failed.
Built with commit e567208fe6bc26569eb27f474b7eedcd9603d82b
https://app.netlify.com/sites/react-native/deploys/5f8f2a7e8e7e780008b67db1

As posted in the comment above deploy preview is available in here:

https://deploy-preview-2263--react-native.netlify.app

Feel free to report any spotted issues or problems.
This PR should NOT be merged before the V1 based archive is deployed!

The archive branch website deploy has been set up and RN Archive is available under https://archive.reactnative.dev/ URL.
In theory, having V1 archive up and running makes this PR ready to review and merge 🙂

What are the next steps for this PR? Can you make a checklist in the summary of this PR? Let me know when you need me for final review.

What are the next steps for this PR? Can you make a checklist in the summary of this PR? Let me know when you need me for final review.

@cpojer I have posted all the steps within the migration plan last week. Since V1 Archive is deployed this PR should be ready to merge. The commits that appears in this PR lately are just a small tweaks which should not affect the functionality and break the deployment in any way.
Currently we are only not sure if V2 deploy will work from master (after the merge) but there was no way to check this earlier, we are ready to hot fix issues on merge.
When the V2 deploy will be finished we need to ask Algolia to update the search index and recrawl the website. There are also several minor checks that need to be done after the deployment, for example:  if the Google Analytics events are tracked correctly.

Thanks for clarifying. I will review it tomorrow and merge it then.

@Simek I found some docs are reverted to an older version like this one https://github.com/facebook/react-native-website/commit/e622c6a43246bb354e7aa60768d7af20fb82b0fc#diff-941914e9c6da4d386c78dcde541e7cc9be34624e543dfccbad380409d8e81813L152-L162

Hi @sunnylqm, it is not clear what changes are exactly missing, remember that the tabs code has changed so the diff might be misleading.
Please check the page file in the master docs and let me know if problem occurs in there - https://github.com/facebook/react-native-website/blob/master/docs/building-for-tv.md.
In a meanwhile I will compare master with archive branch and try to find the issue.

@Simek That doc in master is incorrect (older) after the migration commit as I showed above

@sunnylqm Can you show me somehow where exactly is the issue which you are referring? Can you quote the missing paragraph or sentence on the new site?
At the first glance content on https://reactnative.dev/docs/building-for-tv and https://archive.reactnative.dev/docs/building-for-tv pages looks the same.

I think maybe it's because the master version did not build into versioned doc. For the content, it's obvious tabbarIOS and ListView are deprecated long time ago.

I think maybe it's because the master version did not build into versioned doc. For the content, it's obvious TabBarIOS  and ListView are deprecated long time ago.
So if you take the doc from versioned folder, there might be more inconsistence (not all doc changes go into version folder immediately)

Sorry, but I don't understand you.
My last idea is that you are looking for additional known issues on Android TV which were only applied to the next docs before the migration, so they are only visible in the next docs: https://reactnative.dev/docs/next/building-for-tv

@Simek See this commit https://github.com/facebook/react-native-website/commit/6677d7a8e83cfeaf17fc57045fa6f140046b24f1#diff-941914e9c6da4d386c78dcde541e7cc9be34624e543dfccbad380409d8e81813
It's reverted, isn't it?

If you take the doc from versioned folder and copied them back to master, some changes that haven't build will get lost. Do I make myself clear?

@sunnylqm You should mention #2126 at the beginning. 😉 Now I can clearly see and can confirm that this change has been somehow lost during the migration. Would you like to prepare PR to fix this?

If you take the doc from versioned folder and copied them back to master, some changes that haven't build will get lost

The versioned docs were not copied into next docs during the migration. You can check the whole process in the fork created specially for this migration: https://github.com/react-native-website-migration/react-native-website

And i noticed the edit link now changed to versioned doc(it was linked to master before), which may not be a good choice.
For a common pattern we should commit to master first then cherrypick to current release right?(either automatically or manually)

This is how Docusuaurs V2 "Edit Page" links works and there is no option to change that at this moment. We can always create PR for that, but I'm personally looking at this as an improvement.
When all links were leading to the next version potential contributors were often confused, because they want to fix something on the page they are reading, but after "Edit Page" link click they were seeing different page content or the issue they were looking for was missing on the GitHub file which was opened.

The question is that what's the cause for that lost?(I don't know what to check on that migration repo)  If it's not copied from versioned docs, the only possibility I can come up with is it's copied from a snapshot on master?
Either way I am worrying about more commits may lost.

@sunnylqm I agree with you and it's also a problem for docusaurus website.
I want to add an option so that we can configure the edit link of each version independently.
You can make the RN 0.63 (latest) target the master docs in priority for example. I'd also prefer to edit the master docs in such case because if we merge by mistake a PR that only target RN. 0.63 we end up loosing the info for RN 0.64
This is also needed because some of our users are assembling md files from external repos, git submodules etc... Also we'll explore how to handle git-based CMS tools like Forestry/Tina/NetlifyCMS, in which case the edit link may rather target the edition UI instead of the git file.
So, it's not ready today but it's something we'll definitively support soon


HDDS-1226. ozone-filesystem jar missing in hadoop classpath

hadoop-ozone-filesystem-lib-*.jar is missing in hadoop classpath.
This PR aims at having a shaded hadoop-ozone-filesystem-lib-*.jar file in ${OZONE_HOME}/share/hadoop/ozonefs/ path

@bharatviswa504 @elek @avijayanhwx @swagle

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
20
Docker mode activated.

_ Prechecks _

+1
@author
0
The patch does not contain any @author tags.

_ trunk Compile Tests _

+1
shadedclient
824
branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1
shellcheck
1
There were no new shellcheck issues.

+1
shelldocs
14
There were no new shelldocs issues.

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
795
patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1
asflicense
30
The patch does not generate ASF License warnings.

1784

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-560/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/560

Optional Tests
dupname  asflicense  shellcheck  shelldocs

uname
Linux c2280c5ecb6c 4.4.0-139-generic #165~14.04.1-Ubuntu SMP Wed Oct 31 10:55:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 945b504

maven
version: Apache Maven 3.3.9

shellcheck
v0.4.6

Max. process+thread count
340 (vs. ulimit of 5500)

modules
C: hadoop-ozone/dist U: hadoop-ozone/dist

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/1/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

LGTM

Discussed with @vivekratnavel offline:
The big question here is that how can we put the jar files to the classpath in a version independent mode.
We can use HADOOP_CLASSPATH=share/ozone/lib/hadoop-ozone-filesystem-lib-legacy* but can't use any wildcard for the normal lib as the legacy jar file also will be matched.
One possible solution is to rename the ozonefs-lib project to ozonefs-lib-current.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
24
Docker mode activated.

_ Prechecks _

0
yamllint
1
yamllint was not available.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

0
mvndep
69
Maven dependency ordering for branch

+1
mvninstall
1033
trunk passed

+1
compile
961
trunk passed

-1
mvnsite
112
hadoop-ozone in trunk failed.

+1
shadedclient
654
branch has no errors when building and testing our client artifacts.

+1
javadoc
162
trunk passed

_ Patch Compile Tests _

0
mvndep
26
Maven dependency ordering for patch

-1
mvninstall
108
hadoop-ozone in the patch failed.

-1
mvninstall
14
dist in the patch failed.

-1
mvninstall
11
ozonefs-lib in the patch failed.

+1
compile
905
the patch passed

+1
javac
905
the patch passed

-1
mvnsite
94
hadoop-ozone in the patch failed.

-1
mvnsite
30
ozonefs-lib in the patch failed.

+1
shellcheck
0
There were no new shellcheck issues.

+1
shelldocs
38
There were no new shelldocs issues.

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
4
The patch has no ill-formed XML file.

+1
shadedclient
615
patch has no errors when building and testing our client artifacts.

-1
javadoc
27
ozonefs-lib in the patch failed.

_ Other Tests _

+1
unit
33
docs in the patch passed.

-1
unit
110
hadoop-ozone in the patch failed.

+1
unit
35
dist in the patch passed.

-1
unit
28
ozonefs-lib in the patch failed.

+1
unit
32
ozonefs-lib-current in the patch passed.

+1
asflicense
46
The patch does not generate ASF License warnings.

5847

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-560/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/560

Optional Tests
dupname  asflicense  mvnsite  shellcheck  shelldocs  compile  javac  javadoc  mvninstall  unit  shadedclient  xml  yamllint

uname
Linux 320e3c4e668a 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / a55fc36

maven
version: Apache Maven 3.3.9

Default Java
1.8.0_191

mvnsite
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/2/artifact/out/branch-mvnsite-hadoop-ozone.txt

shellcheck
v0.4.6

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/2/artifact/out/patch-mvninstall-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/2/artifact/out/patch-mvninstall-hadoop-ozone_dist.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/2/artifact/out/patch-mvninstall-hadoop-ozone_ozonefs-lib.txt

mvnsite
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/2/artifact/out/patch-mvnsite-hadoop-ozone.txt

mvnsite
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/2/artifact/out/patch-mvnsite-hadoop-ozone_ozonefs-lib.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/2/artifact/out/patch-javadoc-hadoop-ozone_ozonefs-lib.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/2/artifact/out/patch-unit-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/2/artifact/out/patch-unit-hadoop-ozone_ozonefs-lib.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/2/testReport/

Max. process+thread count
469 (vs. ulimit of 5500)

modules
C: hadoop-hdds/docs hadoop-ozone hadoop-ozone/dist hadoop-ozone/ozonefs-lib hadoop-ozone/ozonefs-lib-current U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/2/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

+1. Merged it to the trunk.Thanks the contribution @vivekratnavel
As this is a small risk patch and it would be better to finalize the name earlier, I cherry-pick it to branch-0.4 to be part of the next release.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
0
Docker mode activated.

-1
patch
7
https://github.com/apache/hadoop/pull/560 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/560

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-560/3/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

The last commit (typo fix) added as an addendum commit.


ADC Support for STM32U575

Is your feature request related to a problem? Please describe.
I need to use ADC for my project. I am using nucleo_u575zi_q board. I am using samples/drivers/adc example. I looked into PR #39202 where ADC support is provided for STM32U585 board. I made necessary changes to my dts files for ADC to work.
The ADC sample code is now compiling and running as well. I have configured pc0 as adc pin. But the output I am getting is floating values irrespective of what I connect at ADC input(VCC/GND).
Results
`ADC reading:

ADC_1, channel 1: 296 = 59 mV
ADC reading:
ADC_1, channel 1: 292 = 58 mV
ADC reading:
ADC_1, channel 1: 295 = 59 mV
ADC reading:
ADC_1, channel 1: 293 = 59 mV
ADC reading:
ADC_1, channel 1: 293 = 59 mV
ADC reading:
ADC_1, channel 1: 302 = 60 mV
ADC reading:
ADC_1, channel 1: 301 = 60 mV
ADC reading:
ADC_1, channel 1: 244 = 49 mV
ADC reading:
ADC_1, channel 1: 300 = 60 mV
ADC reading:
ADC_1, channel 1: 296 = 59 mV
ADC reading:
ADC_1, channel 1: 296 = 59 mV
ADC reading:
ADC_1, channel 1: 298 = 60 mV`

Describe the solution you'd like
The output of ADC must change as per the input.
Describe alternatives you've considered
Added adc node to dts file by referring to STM32U585 board. Is there anything else needed to be done?
Additional context
Attached: DTS file, overlay file
nucleo_u575zi_q_DTS_File.txt
nucleo_u575zi_q_overlay_file.txt
.

I had a test on b_u585i_iot02a and I'm seeing same behavior. Converting to bug

@vibhor-meshram could you please check with the https://github.com/zephyrproject-rtos/zephyr/pull/48770

ADC works using above fix.


About Bandwidth Limitation

It would be nice to be able to set the bandwidth limit on the stream sending side, as it is currently not configurable.

Hello, the problem of the bandwidth is that it depends on the stream that is being transmitted: the stream has to be re-encoded in order to change the bandwidth. Since the stream is generally not re-encoded during transmission, this can't be done.
This is different with respect to WebRTC implemented in browsers, where the stream is re-encoded and the encoder is tuned accordingly to the available bandwidth.


cli: implement update command

Update command is used to update container's resources at run time.
All constraints are applied inside the VM to each container cgroup.
By now only CPU constraints are fully supported, vCPU are hot added
or removed depending of the new constraint.
fixes #189
Signed-off-by: Julio Montes<EMAIL_ADDRESS>

@kata-containers/runtime please take a look

@bergwolf changes applied, thanks

@egernst changes applied, thanks

Codes LGTM. Only a typo left s/cc-agent/hyperstart-agent/
So anyone please feel free to merge this after the typo is fixed.

@WeiZhang555 changes applied, thanks

@devimc please rebase and lets move forward to merge after...


PD Spike: plan TC command creators & data types

Overview
PD TC step has 2 modes:

TC State
TC Profile

These both will be translated to command creator "Args", then the command creator(s) will translate the "Args" to atomic commands (defined in JSON Protocol Schema v4).
Acceptance criteria

[ ] Plan TC State form data type (TC profile out of scope of this ticket)
[ ] Have a plan for the command creators (how many, what names, which atomic commands do they spit out). Include data type of command creator args for all command creators.
[ ] Code portion: define arg types in PD, as Flow types (they'll just be sitting there in form-types.js or wherever and not used yet)

Tickets in #5594


chore: arm linux should work

fixed all system check - do not export non existing attrs (no system)
made 0.8.23 default
used official rfc formatter and formatter all files
update list input as it changed its hash (bug fix in place was made by solc people - crazy)
fixed flake attribute exports warnings
make sure on recursion in overlay
ported source build to 8 23 and started templating (seems many changes wil be neede as it goes later versions)
made error to be soft landing

not tested, but do not see reason why it will not work.

Should just work:
Dzmitry Lahoda
:computer:  7 minutes ago
not sure what you mean, but with nix:
me do not care official builds, i care only official make files - if there are mention of arm - i can build it
fixes for any arms are simple if official make files support it, for example https://github.com/nix-community/ethereum.nix/pull/386/files#diff-54a35e40130461d913a507bdde67091d7b7dd0054afb3c05a066a73e71bbd6b3R25
solc see is very popular, its make MUST support arm linux (which is VM on Mac, and Docker on Mac is VM)
hence just adding solc.nix one line should work, i sent PR, person active. he will do it soon i guess
so this just should work https://github.com/hellwolf/solc.nix/pull/6
(edited)

[#6 chore: arm linux should work](https://github.com/hellwolf/solc.nix/pull/6)
<https://github.com/[hellwolf/solc.nix](https://github.com/hellwolf/solc.nix)|hellwolf/solc.nix>hellwolf/solc.nix | Today at 5:23 PM | Added by [GitHub](https://null-studios-group.slack.com/services/B05BXAGG3JB)

Dzmitry Lahoda
:computer:  [3 minutes ago](https://null-studios-group.slack.com/archives/C05QGV097CN/p1715791891008839?thread_ts=1715788406.619529&cid=C05QGV097CN)
the do arm on CI
image.png

image.png

Dzmitry Lahoda
:computer:  [3 minutes ago](https://null-studios-group.slack.com/archives/C05QGV097CN/p1715791928087489?thread_ts=1715788406.619529&cid=C05QGV097CN)
https://github.com/ethereum/solidity/blob/816b588a01e4156f64dcfad8ffbf3b4132d0281d/.circleci/osx_install_dependencies.sh#L109

[osx_install_dependencies.sh](https://github.com/ethereum/solidity/blob/816b588a01e4156f64dcfad8ffbf3b4132d0281d/.circleci/osx_install_dependencies.sh)
    # be aware that we are only building the arm version here, we don't build a universal binary.
<https://github.com/[ethereum/solidity](https://github.com/ethereum/solidity)|ethereum/solidity>ethereum/solidity | Added by [GitHub](https://null-studios-group.slack.com/services/B05BXAGG3JB)

Dzmitry Lahoda
:computer:  [3 minutes ago](https://null-studios-group.slack.com/archives/C05QGV097CN/p1715791939136529?thread_ts=1715788406.619529&cid=C05QGV097CN)
it should just work

first step to check, so  without new systems I get: so it is broken
       error: NAR hash mismatch in input 'https://binaries.soliditylang.org/macosx-amd64/list.json?narHash=sha256-akcOahJE/QR0jCPvo4aBf0loJt9P8zvP2E7oCBCRIho%3D' (/nix/store/9hw6yp4zv7vb7yq0s5yh42rxnjasf1p9-source), expected 'sha256-akcOahJE/QR0jCPvo4aBf0loJt9P8zvP2E7oCBCRIho=', got 'sha256-f5kzXsfnxgad+1FxaGOlflIUVt8RPNBGS5wkqb63DVA='
bash-5.1$

have run flake lock update input, start getting this one
         | ^
          512|

       … while calling anonymous lambda

         at /nix/store/6gxrfravwqh3mjfnqvxgrl7hqm9cf3j1-source/pkgs/build-support/fetchurl/default.nix:123:40:

          122|   hash_ =
          123|     if with lib.lists; length (filter (s: s != "") [ hash outputHash sha1 sha256 sha512 ]) > 1
             |                                        ^
          124|     then throw "multiple hashes passed to fetchurl" else

       error: attribute 'solc-macos-aarch64' missing

       at /nix/store/qbgh3r0jdysqp5x52ghhwxizwmkmm4rb-source/mk-solc-static.nix:51:16:

           50|       inherit url;
           51|       sha256 = solc_sha256.${solc-flavor};
             |                ^

@hellwolf so it works, so I did not done template, if you will have time to template - would be awesome.
templating C++ sources good examples are in poetry2nix

Thanks @dzmitry-lahoda !!
That's a lot of changes to review, give me some time.
What autoformatting did you use?  Going forward, I should setup the same.

Hi,
Thanks again for the inspiration.
I merged the change I did myself https://github.com/hellwolf/solc.nix/pull/7, which includes your changes:

[x]  fixed all system check - do not export non existing attrs (no system)
[ ] made 0.8.23 default
[x] used official rfc formatter and formatter all files
[x] update list input as it changed its hash (bug fix in place was made by solc people - crazy)
[ ] fixed flake attribute exports warnings
[ ] make sure on recursion in overlay
[ ] ported source build to 8 23 and started templating (seems many changes wil be neede as it goes later versions)
[ ] made error to be soft landing (?)

I will further incorporate your changes and additional cleanups:

More code comments to make contribution easier.
Check how to include your expression for building from source.
Fix the rest of the TODOs

Check how to include your expression for building from source.

This would be awesome. It will make ultimate solution when there is no binary, just try build it. i guess that is main point.

made error to be soft landing

this is about do not throw, but just do not generate attribute (so it will just not find attr in consumer).

make sure on recursion in overlay

I got recursion somehow with flake-parts consumer. So imho better do explicit parameters passing in instead of pkgs, look  cosmos.nix for example.

ported source build to 8 23 and started templating (seems many changes wil be neede as it goes later versions)

latest nixpkgs is 8.21, I ported it to 8.23. I see that after 8.23 there are more changes in cmake. so need some flex system for CMAKE FetchContent override. So can start from 8.21 and 8.23 difference easy.
What can I do to help making these in master sooner than later? :)

I fixed the infinite recursion issue in main directly. But I also have a different issue in my local NixOS config using it. I will be fixing it asap this week!

https://github.com/hellwolf/solc.nix/pull/9 merging:

CI to test ubuntu-latest, macos-12/13/14.
Make solc 0.8.23 default.

I also realized that a deeper refactoring to use list files from https://github.com/ethereum/solc-bin/ would be better than maintaining my own lists.

I will checkout the "ported source build" expression you made.
I am not sure I would want to maintain that in this project yet, to be honest.

I am not sure I would want to maintain that in this project yet, to be honest.

You mean source version build or solc.nix?
For first, build for existing version will not fail, so maintenance only where source is plugged as fallback for binary, which is 2  lines with // and callPackage.  Build itself is static, so it will work all the time without maintenance. Our company will migrate to new version, will PR add newer versions of source (8 25 and 8 23 could be built from source).
If second, ask if nix-community wants to maintain it and move to nix-community org. So these people I am pretty sure are on source version of things. But as you will look nixpkgs, it actually does both, source for linux and binary for mac. So you  approach is good. nix-community as org can add more reviewers than only you too (technically problems of own project is that owners of single person repo are single).

for example request for recently moved project
https://github.com/orgs/nix-community/discussions/835

@hellwolf anyway, when you decide stop, and ok with having from source fallback in place, i will send new PR for that

@hellwolf anyway, when you decide stop, and ok with having from source fallback in place, i will send new PR for that

Thanks again! I an bit slow at the moment, will look into it later this week.
I think I am leaning towards maintaining it indeed, though I wish a bit more clarity in nixpkgs community how to deal with  "core" v.s. "contrib" packages.

I am not nix community :) , so for sure never seen multiversion packages in nixpkgs. All multi version I saw were in nix-community repos (or repos of some orgs like cosmos.nix for example). Nixpkgs seems tracks latest stable release compatible with all other core pacakges in nixpkgs release.

Is " ported source build to 8 23 and started templating (seems many changes wil be neede as it goes later versions)" the remaining thing to address in a new pull request?
I am happy to get something like this merged, my 2cents:  since this project includes all versions of solidity, would it be a good idea to version the solc build expression too? For example, mk-solc-from-source-0.8.23, and perhaps 0.8.24 works the same so that the 0.8.23 will be reused over time.

thanks, will open new PR for source.

no worries, i am still target to follow up on this, so i guess to optimize, will do it when out team decides to move to next version of solc.


[FLINK-29639] Print resourceId of remote taskmanager when encounter transport exception.

What is the purpose of the change
Print resourceId of remote taskmanager when encounter transport exception.
Brief change log

Add resourceId to TransportException.
Print resourceId of remote taskmanager when encounter transport exception.

Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

@flinkbot run azure


Treasury Advisory Service Meeting -  Monday, 29th August, 2022

Attendees

[x] Andre
[x] Stephen
[x] Miro

Notes
1) F8: ABC of Governance

GitBook : https://quality-assurance-dao.gitbook.io/training-and-automation/
Project Board : https://github.com/orgs/Catalyst-Auditing/projects/5
Onboarding form - https://github.com/Catalyst-Auditing/Training-and-Automation-Coordination/issues/24
Proof of Life - n/a - because previously funded
Monthly Report - https://github.com/Catalyst-Auditing/Training-and-Automation-Coordination/issues/25
Discord setup - https://github.com/Catalyst-Auditing/Training-and-Automation-Coordination/issues/17
Obsidian costs - https://github.com/Catalyst-Auditing/Training-and-Automation-Coordination/issues/33

2) F8: Open Source Development Ecosystem - Automate, Educate, Communicate

GitHub : Decision - Stay with Catalyst Auditing & Oversight - GitHub organization
GitBook : https://quality-assurance-dao.gitbook.io/training-and-automation/
Project Board : https://github.com/orgs/Catalyst-Auditing/projects/5
https://github.com/Catalyst-Auditing/Training-and-Automation-Coordination/issues/17
https://github.com/Catalyst-Auditing/Training-and-Automation-Coordination/issues/35
https://github.com/Catalyst-Auditing/Training-and-Automation-Coordination/issues/23

Notes
F8 ABC of Governance

[ ] Amend the GitBook location
[ ] Decide where it lives ? QADAO ?
[x] July 2022 Monthly report has been completed
[x] August 2022 Monthly report will be due
[ ] Document the expenses and reason why funds were transferred - ABC of Governance Treasury GitBook reference
[ ] Where should be the project board ?

F8: Open Source Development Ecosystem - Automate, Educate, Communicate

[x] Treasury Advisory Service Project Board has been moved to Treasury Guild GitHub Org - Andre  / Stephen
[ ] Move and rename (url) GitBook to Treasury Guild GitHub Organisation (current location https://github.com/Catalyst-Auditing) - Stephen W
[x] Review Project Board issues

General
ADA DUE
Added issue to create ADA DUE GitHub Action. (https://github.com/treasuryguild/Treasury-Advisory-Service/issues/57)

This raises the question of how we should be using our ADA DUE/ADA PAID issues
How to use for reporting ?
How to use to for payments ?

Previous in series: #59

Next in series: #62


Allow channels to be closed on blocking select

This PR might deserve a bit of discussion. On the MT recent work, we focus on non-blocking select and I think there were some cases for blocking select that might have slipped.
_, r = Channel.select(ch1.receive_select_action, ch2.receive_select_action)

is equivalent to
select
when r = ch1.receive
when r = ch2.receive
end

and to
_, r = Channel.select([ch1.receive_select_action, ch2.receive_select_action], false)

And it is expected to wait for a send over any ch1 and ch2.
Then, there is a construct for non-blocking select (when an else is present):
select
when r = ch1.receive
when r = ch2.receive
else
  r = Channel::NotReady # this is to match the behaviour of the next example.
end

Or equivalent:
_, r = Channel.select([ch1.receive_select_action, ch2.receive_select_action], true)

For non-blocking select there is no change in the behaviour in this PR.
For blocking select, since closing a channel awakes the fiber, there is a need to loop and re-wait over the channels. This is what is mainly added in this PR.
A decision was made regarding what should happen on blocking select over closed channels: It will generate a runtime exception with the message "All channels are closed on a blocking select".
Additionally, we avoid waiting over already closed channels.
Related to #8231, but the opening issue will still raise since it was a blocking select over a closed channel. But it pushed the think exposed here in the specs.

As a comparison to Go,
select {
case m, e := <-c:
   // ...
}

when the channel is closed, e will inform so. There is an explicit way to know that the channel is been closed. I think in Crystal we prefer to use unions or typed messages when needed to signal that. Otherwise every Channel(T)#receive should return T | Channel::Closed.

We were discussing with @waj about the design.
Another idea is that instead of going the route of this PR, the select could remain loopless and when an awaited channel is closed the select will exit. If the select was using ch.receive then an exception will be raised when closing the channel. If the select was using ch.receive? then a distinguished value will be sent when the channel is closed.
This will be actually more similar to Go in the sense that a close event will awake the select, but will keep the simple API for when the user does not care about channel been closed.
A select with ch.receive? will allow the user to know about which channel is been closed.
Regarding the Channel#receive? there are two alternatives:
a) It returns a Nil when the channel is closed. This will be cumbersome for Channel(Nil) (and any nilable value) since there will be no way to distinguish a message from the closing
b) It returns a Channel::Closed value. So Channel(T)#receive : T and Channel(T)#receive? : T | Closed. The user will need a m = ch.receive? ;  if m.is_a?(Channel::Closed) ... which is a bit more code than if m.

I didn't see select documented anywhere, could you add documentation? (It doesn't have to be in this PR)
It would also be great to document more Channel in the API docs, and the book. People are certainly missing powerful Channel features.
I did try, but I don't know the topic well enough 🤐

@bcardiff I like the simple design: wake up the select, let receive raise and receive? return nil.
For the alternatives, the case of Channel(Nil) is independent of select; we never know whether receive? returns because the channel is closed or you got a value. One must manually check for #closed? or use another type (e.g. Int32). I don't see any benefit for passing an union.

@ysbaddaden that won't work. It is not possible to effectively use close? to check if the state of the channel when received? returned. It could change in between.
That why the alternative is to either
a) use nil as a signal of the closed channel. Which will disallow, in practice, the usage of nilable types as channel messages.
b) introduce Channel::Closed to allow nil as a kind of data.
Either way, an independent ch.receive or ch.receive? (ie: wihout a select) will be blocking.
The non-blocking behaviour is brought by the select.
So the difference between ch.receive and ch.receive? is about how to handle the closing reaction (ie: exception or explicit value)

An alternative is ch.receive { ... } which will invoke the block if the channel is closed. That way you can return any type in the block. This is similar to Hash#fetch, where we have [] (raises), []? (returns nil, not useful if values can be nil) and fetch (if values are nil you can know because the block will or won't be invoked).

I've been iterating on this. As said before

the difference between ch.receive and ch.receive? is about how to handle the closing reaction
there should be no difference whether the channel was closed or is closed while the current fiber is suspended
closing a channel that is been wait will awake the fiber

if that raises an exception or not it depends on whether receive or receive? was used

there will be no loop in the implementation of select
the implementation of blocking and non-blocking select will need to be different functions because their types need to defer.

Channel.select is considered a private API, it should have :nodoc: and its usage should be mainly from a select statement.

The current review of what types is expected can be viewed at: https://gist.github.com/bcardiff/289953a80eb3a0512a2a2f8c8dfeb1db
Closing this PR. I should submit a new one with the above implementation.


No implementation found for method getAll on channel plugins.flutter.io/shared_preferences

[✓] Flutter (Channel stable, 3.0.1, on macOS 12.3.1 21E258 darwin-arm, locale en-VN)
• Flutter version 3.0.1 at /Users/mac/fvm/versions/3.0.1
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision fb57da5f94 (5 weeks ago), 2022-05-19 15:50:29 -0700
• Engine revision caaafc5604
• Dart version 2.17.1
• DevTools version 2.12.2
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
• Android SDK at /Users/mac/Library/Android/sdk
• Platform android-32, build-tools 31.0.0
• ANDROID_HOME = /Users/mac/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 13.3.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• CocoaPods version 1.11.3
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2020.3)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
[✓] IntelliJ IDEA Community Edition (version 2021.2)
• IntelliJ at /Applications/IntelliJ IDEA CE.app
• Flutter plugin version 61.2.4
• Dart plugin version 212.4746.57
[✓] VS Code (version 1.67.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.42.0
[✓] Connected device (3 available)
• iPhone 13 Pro (mobile) • C1DC424E-7967-49E9-BFBE-1039CC14C82A • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-4
(simulator)
• macOS (desktop)        • macos                                • darwin-arm64   • macOS 12.3.1 21E258 darwin-arm
• Chrome (web)           • chrome                               • web-javascript • Google Chrome 102.0.5005.115
[✓] HTTP Host Availability
• All required HTTP hosts are available

@dev12-dgh
A similar issue was fixed here https://github.com/flutter/flutter/issues/98473 (workaround)
Can you switch to the latest master and try again?
flutter channel master
flutter upgrade

did you fix it?

you can add this line  SharedPreferences.setMockInitialValues({});
but the problem is that every time I open the app it initializes again


JBPM-3193: jBPM5 Form Builder

jBPM Form Builder is thought to allow functional users and designers to create forms for the BPMN2 processes defined in the jBPM console.
Next items in the roadmap include:

Adding new validations
Adding script helpers to add dynamic ui components on client side
Adding server interpretation of complex objects to the generated form's API
Adding template management for complex objects for the generated form's inputs
Improvement of properties edition panel to add better coverage of properties for form items
Improvement on tree and edition panel visualization
Allow switching layouts once they're filled without losing content
Adding script helpers to allow onEvent simple validations on client side
Definition of a standard page layout for a given user or role
Definition of standard UI visualization strategies for particular types of data
New translators and renderers for JSF, XUL and so on

Mariano,
Perfect! Thanks.. I'll take a look in the next couple days.
Marco


Screenshot on Failure

Would be cool if we had an option to take a screenshot on failure during a Puppeteer scenario.

Accessing build artifacts with CircleCI is as easy as:
- store_artifacts:
    path: tmp/screenshots

Makes it super quick to diagnose a failure without rerunning the pipeline.


Update to README.md - adding a link to a site

Added a link to my own site that uses this wonderful theme.

Hello!
Thank you for the PR. When I try to open your site, there's an error;

Access denied
Error code 1020
You do not have access to thomaslaneart.com.

The site owner may have set restrictions that prevent you from accessing the site.

Oh my! I will take a look, thank you.  I have it filtered to only allow US IP addresses - for standard reasons.  But that firewall can be removed.  Give it a shot now :)


Improve the API documentation

This commit fills in missing API documentation and also reorders some
of the fields to bubble the most common ones closer to the top.

/retest

/retest

/lgtm


normalize the lookup name so that it works on Windows

Hi @tylergould , our developers found some errors on running unit tests on windows. Root cause is that it can not resolve the partials correctly on windows. for example, in our handlebars template, we have a lot of code as following. as you can see path is forward slash. however in fina-partials.js all the found partias with be cached under the name with OS specific path separator which will be common\templates\detail on windows). So I create a pull request to normalize the name before lookup. could you help merge it? Thanks for your time.
<div>
    {{> common/templates/reusableTemplates}}
</div>

Thanks for the contribution @larryhe ! I'll publish a release now.

Your change is in 0.3.0. Thanks again --


Add an iptables rule for letting weaveDNS requests in

Fixes #1578

should be branched off 1.2

why do we need to insert the rule rather than appending it?

Because I think we need it before all these rules:
Chain INPUT (policy DROP 137 packets, 4384 bytes)
 pkts bytes target     prot opt in     out     source               destination
 136K   98M ufw-before-logging-input  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0
 136K   98M ufw-before-input  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0
 7237  424K ufw-after-input  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0
 1537 56400 ufw-after-logging-input  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0
 1537 56400 ufw-reject-input  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0
 1537 56400 ufw-track-input  all  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0

@rade you are right, we append it. Fixing...

It seems I'll have to close this branch as the target branch cannot be changed in a PR... :confused:

yes

Tests failing with:
>>> Test ./640_proxy_restart_reattaches_test.sh finished after 32.7 secs with error: exit status 1
Proxy restart reattaches networking to containers
d4b5c5a8baf365fca5fc9f68582c4802b8b7d9d115ff42c81b8fbd92feb49d2e
6123910fedad4ebf07e17a5211f33677e461651b929c9eced84675c4813bdc24
c2
weave
sudo: systemctl: command not found

:confused:

Tests failing

#1588

I'll wait until #1588 is fixed, then I'll close this PR and open a new one based on branch 1.2.

I'll wait until #1588 is fixed

Don't. Unless you are going to fix it yourself.


ErrorHandler 2.5-beta: More readable exceptions, smaller blob

This PR introduces new Error Handler version 2.5-beta.
Detailed changeset
See version 2.5-alpha changeset.
Additional changes

[x] Support "c+" compile option in ASM68K bundle (case-sensitivity);
[x] Error Handler: Improve readability of offsets and symbols in exception header;
[x] Error Handler: Reduce blob size below 3 KiB mark;
[x] Error Handler: Migrate the rest of tests to MDShell 2.0, implement "full exception" test;
[x] Error Handler: Introduce "External Symbol Table" bundle;
[x] MDShell: Introduce "headless" bundle.

I'm going to cut this PR as-is naming this version 2.5-beta. Further enhancements (if any) will go under 2.5-final.


Doesn't connect with xamarin forms

When I try the following

Create a new Xamarin Forms project
Update all release packages
Run Install-Package Microsoft.AspNetCore.SignalR.Client -Version 1.0.0-preview1-final on the portable project
Run the android project

I find the following error:

"Could not load assembly 'System.Threading.Tasks.Extensions' during startup registration".

I have tried installing the latest pre-release of System.Threading.Tasks.Extensions. Still no change in the error.
Update
I have found the same error on xamarin versions "<IP_ADDRESS>203", "<IP_ADDRESS>0555", "<IP_ADDRESS>7207-pre1"
I get the same error with web socket client nuget as well for "<IP_ADDRESS>0555" and "<IP_ADDRESS>7207-pre1" but NOT on "<IP_ADDRESS>203".

Are you using the latest version of Xamarin?

I too

Same here.

Closing see https://github.com/aspnet/SignalR/issues/1886


Estimate rec_prob

[ ] Add tests to check the accuracy of estimation of the recombination rate (func_test) and tests to check if the estimation of the recombination rate improves the accuracy of the peeling (accu_test)
[ ] Add descriptions of option est_rec_prob to the documentation
[ ] Add code to estimate the recombination rate and output the recombination rate

@RosCraddock please work with @XingerTang on the testing and documentation


Update Contributer.md

Have added my  name

Add some code to any folder

Have added
On Sun, 2 Oct 2022, 00:35 A M, @.***> wrote:

Add some code to any folder
—
Reply to this email directly, view it on GitHub
https://github.com/tomriddle77/Hacktober22/pull/52#issuecomment-1264455220,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWOCSUPSQFT5AYX7DC5WD5TWBCDRFANCNFSM6AAAAAAQ2RQIZE
.
You are receiving this because you authored the thread.Message ID:
@.***>


The definition of File class is truncated

Hello, I was reviewing this SDK to replace our custom implementation but got an issue with the File class. I was under the impression that some methods were missing.
Diving in the sources I found what looks like a code generation bug. Some functions are inserted in the class definition having for effect to discard the following methods definitions: https://github.com/Files-com/files-sdk-python/blob/41a7deef6cd3d77c26372edc60b8abd8cb4b2f50/files_sdk/models/file.py#L261-L324

Hi,
This should be solved now.  Please advise if you still have issues.

Hello, thanks for your answer. Sadly, the issue is still the same.

Wow, thanks for the update.  Our team took another look at this and pushed another fix, which is shipping now.  Please give this a try.

Judging by the commit's diff I'd say it's all good. Thank for the fix!


Bug: failed test output points to wrong line in code

Given

Config:
import "dotenv/config";
import environments from "./config/environments.json";
import { defineConfig, expect } from "@playwright/test";
import { defineBddConfig } from "playwright-bdd";

const validEnvironments = Object.getOwnPropertyNames(environments);
const environmentErrorMessage = `Environment name not found. Edit .env in the root directory to set GALAXY=<environment name>, using one of the following options:
${validEnvironments}`;
expect(validEnvironments, environmentErrorMessage).toContain(
  process.env.GALAXY
);
console.log(`Using environment ${process.env.GALAXY}`);

const testDir = defineBddConfig({
  features: "tests/features/**/*.feature",
  steps: "tests/**/*.ts",
});

export default defineConfig({
  testDir,
  reporter: "html",
  use: { browserName: "chromium", viewport: { width: 1280, height: 880 } },
});

Feature file:
Feature: Automatic renewal of policy

Background:
  Given I am logged in to PolicyCenter as Super user
  And I am using an existing completed account
  And I have a policy
  And the policy type is Renewing
  And the term type is Annual
  And the policy expiration date is 10 days in the future
  And the policy has a coverage of type Milk

@PC_DF_014
Scenario: Policy renewal for Buildings and Contents
  Given the policy defined in the background
  When I start the batch renew process and return to the account summary

Folders:

When

I added a line to throw an error in the steps definition file, and ran the test from the playwright test runner in VSCode, after running bddgen.

Then

The error was thrown and ended the test but the test-results reports the error in the wrong position:

But I expect

This is actually reasonably close, but in most non-artificially caused errors, it's out by 30-40 lines. Probably proportional to the line number. I expect it to point to where it actually failed. This offset also comes through in the playwright HTML report.
Isolated demo
 https://github.com/vitalets/playwright-bdd-example/pull/21
In this case, the results point to a line past where it should, to a line that doesn't even exist:

Environment

Playwright-bdd environment info:

platform: win32
node: v20.12.1
playwright-bdd: v7.4.2
@playwright/test: v1.47.2
@cucumber/cucumber: none
Playwright config file: playwright.config.ts

Interesting..
I've run your example and it shows correct location:

Possibly some Win vs OSX issue. Could you try to run pure Playwright test that throws such error?

Sure, I'll look into it further at my end.

When I open a different repo that does not use bddgen, just Playwright on its own, the error report points to the right place. So I don't think it's environmental/system, it's at the repo level. I'll carry on trying to isolate it.

I get the same result in both VSCode and IntelliJ IDEA.

Setting up a new repo via npm init playwright@latest and inserting an error reports it at the correct place.

Adding bdd-playwright to the same repo and generating a test spec file with it and adding the error points to the wrong place. Error occurs with both typescript and javascript.

I'm really at a loss now. Apart from sharing my actual system via a teams call or something, I'm not sure how to resolve this issue locally or reproduce this issue elsewhere.

Disabled WSL and Hyper-V, no change.

@UncleGus I've simplified playwright-bdd-example - kept only one step, removed cucumber reporter and added non-bdd project. Could you try to clone and run incorrect-fail-line branch? Here is the PR to see the diff.
When I run npm t I'm getting the following 2 errors:
    Error: Fail in bdd test

       at features/steps/index.ts:4

      2 |
      3 | Given("step", async ({}) => {
    > 4 |   throw new Error("Fail in bdd test");
        |         ^
      5 | });
      6 |

...
    Error: Fail in non bdd test

      2 |
      3 | test("non bdd test", async ({}) => {
    > 4 |   throw new Error("Fail in non bdd test");
        |         ^
      5 | });
      6 |

Also could you run only non-bdd-project npx playwright test --project non-bdd-project.
And if it still produce incorrect line, comment all BDD-related stuff in playwright.config.ts and run  npx playwright test --project non-bdd-project again.

Thank you for your investigation!

I'll have to get to that tomorrow, but I will say that I've added non-bdd tests to the actual project that I'm working in, and it reports errors at the correct line.

Okay, that didn't take as long as I though :P
Here's my output, and it's looking promising:
  1) [bdd-project] › .features-gen\features\homepage.feature.spec.js:6:7 › Playwright Home Page › Check title › Given step

    Error: Fail in bdd test

       at features\steps\index.ts:4

      2 |
      3 | Given("step", async ({}) => {
    > 4 |   throw new Error("Fail in bdd test");
        |         ^
      5 | });
      6 |

        at Object.<anonymous> (C:\dev\playwright-bdd-example\features\steps\index.ts:4:9)
        at C:\dev\playwright-bdd-example\.features-gen\features\homepage.feature.spec.js:7:5

  2) [non-bdd-project] › non-bdd\index.spec.ts:3:5 › non bdd test ──────────────────────────────────

    Error: Fail in non bdd test

      2 |
      3 | test("non bdd test", async ({}) => {
    > 4 |   throw new Error("Fail in non bdd test");
        |         ^
      5 | });
      6 |

        at C:\dev\playwright-bdd-example\non-bdd\index.spec.ts:4:9

  2 failed
    [bdd-project] › .features-gen\features\homepage.feature.spec.js:6:7 › Playwright Home Page › Check title
    [non-bdd-project] › non-bdd\index.spec.ts:3:5 › non bdd test ───────────────────────────────────

Running the non-bdd project on its own got the same results for that test.

A colleague cloned the repo and had the exact same issue, so whatever the cause is, it's not specific to my laptop.

A colleague cloned the repo and had the exact same issue, so whatever the cause is, it's not specific to my laptop.

I will think how to debug that deeper.
Is he also on win?


#9 MatchError: no match of right hand side value: [“Delete”]

"Delete" does not work as expected.

I added some exception handling to help recover from situations like this one where an exception was being thrown and putting the user in an odd state where Courtbot wouldn't respond. Additionally I fixed the underlying issue where 'Delete' was not being parsed correctly.


App is published but nothing from the app is visible

This bug occurs only in Azure production environment. In Sandbox environment everything works fine.
I have extension which I regularly update in Sandbox environment and user deploys it to the production environment when they are happy with update.
Today they tried to deploy the update, but nothing from the app is visible anymore.
Extension deployment status says Upload is completed but the app is not visible in list of extensions.
In search box nothing from this app is visible. Added actions are also not visible.
I created test app which has the same fields in one table extension as the main app, and when I try to publish it, it registers the collision. I guess this means the main app is really installed.
After field ID & name changes in test app it is successfully published to the Sandbox environment and test functionality is visible. In production environment Deployment is successful, but test functionality is not visible.
I've tried sign out and sign in multiple times, I've tried different user also, no luck.
Successful deployment

Extensions Task1 and Test_ext not visible

I've tried to go to the Extension Marketplace and get App test by Administrator Office 365 Dynamics 365 and installation failed 2 times.

Error details :
Unexpected error. There was an unknown error when attempting to deploy the extension. Try to deploy again.
Expected behavior
App working in Sandbox environment and successfully deployed to Production environment to be visible and usable to the user.

AL Langauge: 2.0.56865
Business Central: NL Dynamics NAV 13.2 (27167)

It seems like update/restart or something solved the issue. Next day everything is fine


Update elisp packages

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126151 at 045afcce run on x86_64-linux 1

2 packages built successfully:

cask
irony-server


Bug fix with contentView height

This will fix constraints, to correct contentView height.
Also fixes customView height and touches inside it.

Not tested yet.


Updated Unity Sample Application to Handle Multiple Root Nodes in Hierarchy

Updated the PuppetAvatar.cs script in the Unity Sample App so that we can now puppet the Rocketbox avatar library.
This will work also for any avatar that has more than one parent for the hips joint in the hierarchy, which is pretty common outside of the mixamo pipeline.
Also fixed a bug that was causing standalone apps to hang on exit.

Please Squash merge

Ok done.  Thanks,
Angus
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From<EMAIL_ADDRESS>Sent: Monday, July 13, 2020 9:12 AM
To<EMAIL_ADDRESS>Cc: Angus<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [microsoft/Azure-Kinect-Samples] Updated Unity Sample Application to Handle Multiple Root Nodes in Hierarchy (#55)
Please Squash merge
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FAzure-Kinect-Samples%2Fpull%2F55%23issuecomment-657651657&data=02|01|Angus.Antley%40microsoft.com|43b17f4b75b148ac72ae08d827477ac9|72f988bf86f141af91ab2d7cd011db47|1|0|637302535240103518&sdata=Haj%2F6YU%2B5XugEh1FeiV5aQqFjkZyFKwg9JUXKHi%2BXXU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOLH3HLOGNUO5EK3HDIOLLLR3MW5FANCNFSM4OPEMHFQ&data=02|01|Angus.Antley%40microsoft.com|43b17f4b75b148ac72ae08d827477ac9|72f988bf86f141af91ab2d7cd011db47|1|0|637302535240103518&sdata=NbAuI%2BSPzt632Efi0PBAVE43dgSqzCy8m0lS6JpXjZY%3D&reserved=0.


Allow for nuget v3 api to have an url that does not end with /index.json - third try

Reduce the check for v3 api to searching the string "/v3/" in the url
This change also helps to circumvent #3575 by using v3 api

thansk!


Allow for customizing lines scrolled

Resolves #13
This PR adjusts the default number of lines to scroll by to 3, and allows for setting a custom value with the lines-to-scroll field in inlyne.toml

Looks good to me. I think we can close https://github.com/trimental/inlyne/issues/13 now since it's up to the user, but 3 seems like a good default from testing using a mouse 👍


Adm 908 show DORA charts

Summary
...
Before
can not show DORA chart
After
can show DORA chart
Note
Null

Another question On chart page, clieck previous, existing behavior is getting back to list page, is this the wanted design? @Yufan0226

existing behavior is： getting back to metrics page.


RuntimeError: Expected is_sm80 || is_sm90 to be true, but got false.

Getting this error when trying to quantize llama3-8b-instruct in an T4 GPU.
torch version - 2.1.1

Thank you for trying AutoRound. Could you kindly attach more log?

thanks for your response.
Code i am running -
`from transformers import AutoModelForCausalLM, AutoTokenizer
import torch
model_name = "meta-llama/Meta-Llama-3-8B-Instruct"
model = AutoModelForCausalLM.from_pretrained(model_name, torch_dtype=torch.float16, trust_remote_code=True)
tokenizer = AutoTokenizer.from_pretrained(model_name, trust_remote_code=True)
from auto_round import AutoRound
bits, group_size, sym = 4, 128, False
autoround = AutoRound(model, tokenizer, bits=bits, group_size=group_size, sym=sym, device=None)
autoround.quantize()
output_dir = "4bit_autoRound"
autoround.save_quantized(output_dir) `
Error I am getting -
Loading checkpoint shards: 100%|██████████| 4/4 [00:03<00:00,  1.13it/s] Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained. 2024-06-21 05:22:46 INFO utils.py L527: Using GPU device 2024-06-21 05:22:46 INFO autoround.py L464: using torch.float16 for quantization tuning 2024-06-21 05:22:52 INFO autoround.py L851: switch to cpu to cache inputs 2024-06-21 05:23:09 INFO autoround.py L1306: quantizing 1/32, model.layers.0 Traceback (most recent call last):   File "/home/sandlogic/LINGO/LINGO_PROJECTS/ModelQuantization/Intel_AutoRound/llama3_4bit_Autoround.py", line 12, in <module>     autoround.quantize()   File "/home/sandlogic/LINGO/LINGO_ENV/ModelQuantization/lib/python3.10/site-packages/auto_round/autoround.py", line 575, in quantize     self.quant_blocks(   File "/home/sandlogic/LINGO/LINGO_ENV/ModelQuantization/lib/python3.10/site-packages/auto_round/autoround.py", line 1316, in quant_blocks     q_input, input_ids = self.quant_block(   File "/home/sandlogic/LINGO/LINGO_ENV/ModelQuantization/lib/python3.10/site-packages/auto_round/autoround.py", line 1208, in quant_block     self.scale_loss_and_backward(scaler, loss)   File "/home/sandlogic/LINGO/LINGO_ENV/ModelQuantization/lib/python3.10/site-packages/auto_round/autoround.py", line 1470, in scale_loss_and_backward     scale_loss.backward()   File "/home/sandlogic/LINGO/LINGO_ENV/ModelQuantization/lib/python3.10/site-packages/torch/_tensor.py", line 492, in backward     torch.autograd.backward(   File "/home/sandlogic/LINGO/LINGO_ENV/ModelQuantization/lib/python3.10/site-packages/torch/autograd/__init__.py", line 251, in backward     Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass RuntimeError: Expected is_sm80 || is_sm90 to be true, but got false.  (Could this error message be improved?  If so, please report an enhancement request to PyTorch.)
Cuda version - 11.8
torch version - 2.1.1

Thanks for the information.  AutoRound requires gradient backward, however, the root cause should be related torch or sdpa-attention.   please refer to https://github.com/pytorch/pytorch/issues/98140 or try other solutions online.

or https://github.com/huggingface/accelerate/issues/2799


Cmake spits error when I set -DCMAKE_INSTALL_PREFIX to install CPP SDK to my own custom path.

What platform/OS are you using?
Ubuntu 18.04 LTS (WSL)
Which version of the SDK?
1.7.162
What compiler are you using? what version?
Clang 6
What are your CMake arguments?
sudo cmake ../aws-sdk-cpp -DCMAKE_BUILD_TYPE="RelWithDebInfo" -DCMAKE_CXX_COMPILER:FILEPATH="clang++" -DCMAKE_C_COMPILER:FILEPATH="clang" -DENABLE_TESTING="OFF" -DBUILD_ONLY="dynamodb;firehose;gamelift" -DBUILD_SHARED_LIBS="OFF" -DCMAKE_INSTALL_PREFIX="../aws-sdk-cpp/install/Linux/RelWithDebInfo"
Can you provide a TRACE level log? (sanitize any sensitive information)
aws-sdk-error.log
CMakeOutput.log

This is how I run and install CPP SDK to the custom path.
sudo cmake ../aws-sdk-cpp -DCMAKE_BUILD_TYPE="RelWithDebInfo" -DCMAKE_CXX_COMPILER:FILEPATH="clang++" -DCMAKE_C_COMPILER:FILEPATH="clang" -DENABLE_TESTING="OFF" -DBUILD_ONLY="dynamodb;firehose;gamelift" -DBUILD_SHARED_LIBS="OFF"
sudo cmake ../aws-sdk-cpp -DCMAKE_BUILD_TYPE="RelWithDebInfo" -DCMAKE_CXX_COMPILER:FILEPATH="clang++" -DCMAKE_C_COMPILER:FILEPATH="clang" -DENABLE_TESTING="OFF" -DBUILD_ONLY="dynamodb;firehose;gamelift" -DBUILD_SHARED_LIBS="OFF" -DCMAKE_INSTALL_PREFIX="../aws-sdk-cpp/install/Linux/RelWithDebInfo"
sudo make && sudo make install

Hi @sunhyung ,
the first thing that comes to mind here is the sdk dependencies. If you're trying to build in a custom path, you'll have to tell the sdk where those dependencies are.
See the To build and install third party dependencies section of the README.
but basically you'll need to add :
-DCMAKE_PREFIX_PATH=deps-install-dir to your cmake arguments.

Hi @sunhyung ,
the first thing that comes to mind here is the sdk dependencies. If you're trying to build in a custom path, you'll have to tell the sdk where those dependencies are.
See the To build and install third party dependencies section of the README.
but basically you'll need to add :
-DCMAKE_PREFIX_PATH=deps-install-dir to your cmake arguments.

Looks like that is what I wanted but... complicated... running another round of cmake is way more simple.

Yea.. sadly, it is somewhat of a limitation we have since we are depending on other aws projects, but I guess if that works better for you then that's good 👍
I don't know if I can do more here so I'll be closing the issue, let me know if there are more questions and feel free to reopen it if that's the case.


feat(errors): capture error stack trace in v8 only

Error Stack Tracing only works on V8
checks for availability
though running on V8

For context, how are you running Puppeteer without V8?

@maddhruv Yeah, I'm not sure either where captureStackTrace is missing. I'll close this for now; if this is still relevant, please come back to us.


Update docker guide with Jib content

Incorporates content from #265

@cricket007 FYI

Actually, should probably keep
<jmxFlag>-XX:+UseG1GC</jmxFlag>


Server Ready

ELN1 is fun to play with others - I can imagine ELN2 will be that 2 fold.
ELN2 should include locking features for servers.
Owners of ELN blocks should be able to:

Prevent others from connecting to their power lines
Prevent others from using their equipment
Prevent the destruction of their equipment
Prevent a circuit from listening to a wireless signal that isn't made by the owner player
Prevent other players from adding Modems or placing computers next to their ELN Computer Probes [ if applicable ]
Make motion sensors pay no attention to other players
Prevent other players from accessing the inventories of their equipment or placing any kind of pipes beside their equipment
Prevent other players from coloring their wires, operating their switches / buttons, or using a wrench on their equipment
Prevent other players from configuring their locking settings
Add blacklist or whitelist exceptions for certain players

This functionality should treat Server Ops as owners of the equipment as well.
This should be disable-able in the server-side config file.
There should be a menu where a player should be able to globally set all their ELN blocks to be locked or unlocked by default, and possibly have a tool and/or keybind to lock equipment.

pls config option to disable everything like that for servers without private

Owners of ELN blocks should be able to:
* Prevent others from connecting to their power lines

* Prevent others from using their equipment

* Prevent the destruction of their equipment

* Prevent other players from adding Modems or placing computers next to their ELN Computer Probes [ if applicable ]

* Prevent other players from accessing the inventories of their equipment or placing any kind of pipes beside their equipment

* Prevent other players from coloring their wires, operating their switches / buttons, or using a wrench on their equipment

* Prevent other players from configuring their locking settings

* Add blacklist or whitelist exceptions for certain players

So that weird permission system that Thermal Expansion and co have?
This feels like it could be generalized to Cell and require Security Age for the actual features. Though a lot of this feels like a chunk protection mod should be used here instead of us implementing that feature.

* Prevent a circuit from listening to a wireless signal that isn't made by the owner player

Nope. That's not how wireless communication works. Everyone with an antenna and the right decoding hardware/software can listen in on what's being transmitted if they are close enough. You can protect the data, but not the transmission.

* Make motion sensors pay no attention to other players

Probably a Digital Age or Security Age feature, but definitely.

This functionality should treat Server Ops as owners of the equipment as well. This should be disable-able in the server-side config file.

Naturally.

There should be a menu where a player should be able to globally set all their ELN blocks to be locked or unlocked by default, and possibly have a tool and/or keybind to lock equipment.

Client-side config should be the home for this.

Also @Caeleron I didnt notice what you meant

Nope. That's not how wireless communication works. Everyone with an antenna and the right decoding hardware/software can listen in on what's being transmitted if they are close enough. You can protect the data, but not the transmission.

It seems you might've misinterpreted my message - I don't mean for other players receiving your signals i meant for you receiving other's signals. This would prevent another player's transmitters fiddling with your receivers.


Lambda: mention internals of lambdas

Have a look at http://zeroturnaround.com/rebellabs/java-8-the-first-taste-of-lambdas/
Mention variable reference and how it changes the compiled result (and performance, maybe).
This thing in particular:

Please note that in this example the lambda did not capture any of the variables and did not refer to any methods of the enclosing class. That is why the generated lambda$0 method is static. If the lambda refers to any of the enclosing context variables or methods, then a non-static method is generated. So don’t be mislead by the simple example – lambdas can capture enclosing context just fine!

Solved in 8fea5f85ca0dbd4a02311c8d9af343d6aa199ec8


Incremental Wrapper ValueError: Layer not in the HighLevelGraph's layers:

What happened**: I am getting value errors when I implement an incremental wrapper around my PyTorch model with skorch.
ValueError: Layer ('fit-cb2461b73d6a9abbf8a6eacb8d7c983d', 3) not in the HighLevelGraph's layers: ['original-array-ca0ac32624c3fb9bb23d2ca89c89e186', 'array-ca0ac32624c3fb9bb23d2ca89c89e186', 'transpose-c840e9da8930d4f38c6497326ee6e59d',<PHONE_NUMBER>09824, 'getitem-4f71595287eec8f0490287973829e6f2', 'reshape-fe8d57675329c0348f3a175d62f073d0']
What you expected to happen: I expected my neural network model to begin training with my dataset incrementally
Minimal Complete Verifiable Example:

import dask.array as da
import torch.nn as nn
from skorch import NeuralNetRegressor
import torch.optim as optim
from dask_ml.wrappers import Incremental
from dask_ml.datasets import make_regression

class GRU(nn.Module):
    def __init__(self, inputsize, outputsize):
        super(GRU, self).__init__()
        self.inputsize = inputsize
        self.outputsize = outputsize
        self.hiddenlayers = nn.GRU(self.inputsize, self.inputsize, num_layers=2, batch_first=True)
        self.outputlayer = nn.Linear(self.inputsize, self.outputsize)

    def forward(self, x):
        output, hidden = self.hiddenlayers(x)
        x = hidden[-1]
        x = self.outputlayer(x)
        return x

niceties = {
    "callbacks": False,
    "warm_start": False,
    "train_split": None,
    "max_epochs": 1,
}

model = NeuralNetRegressor(
    module=GRU,
    module__inputsize=10,
    module__outputsize=1,
    criterion=nn.L1Loss(),
    optimizer=optim.SGD,
    optimizer__lr=0.01,
    optimizer__momentum=0.9,
    batch_size=100,
    **niceties
    )

inc = Incremental(model, scoring="r2")
# Trains the model incrementally using chunked data

X, y = make_regression(n_samples=10000, n_features=10, n_targets=1, chunks=100)
# Creates data for github example

y = X[:, 1].reshape(-1, 1)
# reshapes the input for sequential model
X = da.stack([X, X, X], axis=1)

print(X.shape)
print(y.shape)

inc.fit(X, y)
print(inc.score(X, y))

Anything else we need to know?:
Environment: Anaconda 3

Dask version: 1.7.0
Python version: 3.9.7
Operating System: Pop OS 21.10
Install method (conda, pip, source): conda

Can you post the full traceback?
Does NeuralNetRegressor implement partial_fit?

Traceback (most recent call last):
  File "/coolstuff.py", line 66, in <module>
    inc.fit(X, y)
  File "/home/anaconda3/envs/Torch/lib/python3.9/site-packages/dask_ml/wrappers.py", line 493, in fit
    self._fit_for_estimator(estimator, X, y, **fit_kwargs)
  File "/home/anaconda3/envs/Torch/lib/python3.9/site-packages/dask_ml/wrappers.py", line 477, in _fit_for_estimator
    result = fit(
  File "/home/anaconda3/envs/Torch/lib/python3.9/site-packages/dask_ml/_partial.py", line 136, in fit
    value = Delayed((name, nblocks - 1), new_dsk)
  File "/home/anaconda3/envs/Torch/lib/python3.9/site-packages/dask/delayed.py", line 497, in __init__
    raise ValueError(
ValueError: Layer ('fit-3a23b2bee452186733b389b1c5a56db7', 99) not in the HighLevelGraph's layers: ['stack-a184c924722ff5ca46fb6c0ef85f0d12', 'normal-862d9ba0e2bc042085f36c63710cfe0b',<PHONE_NUMBER>23552, 'getitem-0d109ff96323bf4206bd2b008436a85a', 'reshape-84d7afd23da422ab179600d3f13f97b8']

The neural net regressors from skorch does implement partial fit

Dask-ML v1.7.0 is from Sep. 2020. Try upgrading, I think it's been fixed since then (it certainly raises an error on the main branch): https://github.com/dask/dask-ml/blob/67d28b15dfff7869e9a04def203aa129a3540b27/dask_ml/_partial.py#L96-L98

That fixed one issue that I was having. However, there is still 1 error with the incremental wrapper:
Traceback (most recent call last):
  File "/home/christopherwoolford/Documents/Research/Deep learning research with Dr. Aledhari/Gene Regulatory Elements Prediction/GRU/GRUStuff/GRU/GRUwithDask.py", line 89, in <module>
    train = inc.fit(X, y)
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/dask_ml/wrappers.py", line 579, in fit
    self._fit_for_estimator(estimator, X, y, **fit_kwargs)
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/dask_ml/wrappers.py", line 563, in _fit_for_estimator
    result = fit(
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/dask_ml/_partial.py", line 137, in fit
    return value.compute()
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/dask/base.py", line 290, in compute
    (result,) = compute(self, traverse=False, **kwargs)
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/dask/base.py", line 573, in compute
    results = schedule(dsk, keys, **kwargs)
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/dask/threaded.py", line 81, in get
    results = get_async(
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/dask/local.py", line 506, in get_async
    raise_exception(exc, tb)
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/dask/local.py", line 314, in reraise
    raise exc
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/dask/local.py", line 219, in execute_task
    result = _execute_task(task, data)
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/dask/core.py", line 119, in _execute_task
    return func(*(_execute_task(a, cache) for a in args))
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/dask_ml/_partial.py", line 20, in _partial_fit
    model.partial_fit(x, y, **kwargs)
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/skorch/net.py", line 1174, in partial_fit
    self.fit_loop(X, y, **fit_params)
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/skorch/net.py", line 1074, in fit_loop
    self.check_data(X, y)
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/skorch/regressor.py", line 69, in check_data
    if get_dim(y) == 1:
  File "/home/christopherwoolford/anaconda3/envs/Torch/lib/python3.9/site-packages/skorch/utils.py", line 193, in get_dim
    return y.dim()
AttributeError: 'tuple' object has no attribute 'dim'

There appears to be an error in the wrapper where the inserted data is not being converted into torch tensor. I modified the code and just used skorch and that was running just fine. However the incremental wrapper is not converting the input data into the necessary form for skorch


Rename securebanking-openbanking-demo to securebanking-openbanking-uk-gateway

the use of the word demo gives the wrong message. Further more it's really not descriptive. Renaming now will likely be painful, but not as painful as later. Let's do this now before it gets spread throughout the docs and customers start cloning it!

Hey team! Please add your planning poker estimate with ZenHub @andra-racovita @mariantiris


Add fake-cluster- prefix to fake cluster uid

[x] Add fake-cluster- prefix to fake cluster uid
[x] Test that it is generating the uid properly

/assign @abhinavdahiya
/cc @joelddiaz

/lgtm


feat: added Cascadia Code font

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/riccardoperra/codeimage/blob/main/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[x] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Hey @max-programming, thank you 😄
the PR is ok, CI is broken for these pr so is fine
I will do a check on local environment just to be sure everything is ok then I’ll merge it and deploy

Everything is fine 😄 thank you. Will do a deploy later

Thanks! The dev env didn't quite work for me so I just made the changes.

@max-programming just to know, what was the issue? I may have to update my CONTRIBUTORS.md file

1.0.6 release with your changes is live 🙏

Got this error when I ran pnpm i
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

.
└─┬ pnpm-bundle-workspace-package 1.0.2
  └─┬ @pnpm/find-workspace-packages 4.0.43
    └─┬ @pnpm/cli-utils 0.7.43
      └─┬ @pnpm/config 15.10.12
        └─┬ @pnpm/pnpmfile 3.0.3
          └─┬ @pnpm/core 6.0.3
            └─┬ @pnpm/hooks.read-package-hook 1.0.2
              └─┬ @yarnpkg/extensions 2.0.0-rc.6
                └── ✕ missing peer<EMAIL_ADDRESS>Peer dependencies that should be installed:
<EMAIL_ADDRESS>
packages/highlight
└─┬ rollup-plugin-dts 5.0.0
  └── ✕ unmet peer<EMAIL_ADDRESS>found 2.79.1

packages/ui
├─┬ @babel/plugin-syntax-jsx 7.18.6
│ └── ✕ missing peer<EMAIL_ADDRESS>├─┬ @rollup/plugin-babel 6.0.0
│ └── ✕ missing peer<EMAIL_ADDRESS>└─┬ acorn-jsx 5.3.2
  └── ✕ missing peer<EMAIL_ADDRESS>|| ^7.0.0 || ^8.0.0"
Peer dependencies that should be installed:
<EMAIL_ADDRESS><8.0.0"<EMAIL_ADDRESS>|| ^7.0.0 || ^8.0.0"

hint: If you want peer dependencies to be automatically installed, add "auto-install-peers=true" to an .npmrc file at the root of your project.
hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.

And this error when I ran pnpm dev
✘ [ERROR] [plugin externalize-deps] Failed to resolve entry for package "@codeimage/vanilla-extract". The package may have incorrect main/module/exports specified in its package.json.

    ../../node_modules/.pnpm/esbuild@0.15.11/node_modules/esbuild/lib/main.js:1327:27:
      1327 │         let result = await callback({
           ╵                            ^

Something might be wrong with my system. Large projects usually don't work

Ok it’s the same I got while trying to playground with CodeSandbox
basically due to “strict-peer-dependencies” pnpm install fail, then the libs:build too because there is a package about prisma models that’s failing (you need docker and the containers probably)
I will update that workflow  in order to be able to run the project correctly 😉 thank you so much


[lldb-moduleimport-test] Add a way to test getTypeFromMangledSymbolName.

The only way we had to test this path was through swift-ide-test,
which takes an input a source file, instead of a serialized module.
This is not the scenario that lldb tests, hence this patch.
rdar://problem/38323564

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 8cbf5bbff751228969ea2202cb38771c27b1cda3

@jrose-apple I'm fine either way. I find that passing a list of names (maybe comma separated) would be doable but will make the test slightly harder to read (but I don't feel strong about it).
Originally I implemented this as an option which took a string rather than a file, but I figured it would be easier to batch so you don't have to pay the price of importing every time you want to look up a name.
@adrian-prantl I thought that as well, not sure whether type reconstruction isn't powerful enough or just isn't supposed to resolve this type (maybe @slavapestov knows)
$ ./swift-demangle '$S4blah4mainyyF8PatatinoL_VMa'
$S4blah4mainyyF8PatatinoL_VMa ---> type metadata accessor for Patatino #1 in blah.main() -> ()

Please note all these AT_linkage_name(s) (including the one that's failing) are coming from the dwarfdump output of the test .dSYM, so, at least in theory, lldb could ask about them to type reconstruction.

@dcci I think the best approach is to have a file of input types, one per line, and an expected output file, and have a RUN: line that checks that the diff is empty. I'm not sure FileCheck is the best approach for this.

Cool, I'll modify this now. Thank you all for your comments

I think the best approach is to have a file of input types, one per line, and an expected output file, and have a RUN: line that checks that the diff is empty. I'm not sure FileCheck is the best approach for this.
Wouldn't it be better to have input and expected output next to each other in the same file so it's easier to edit/read?

I was thinking just -lookup-type '$SSi' -lookup-type '$SSf' or similar, but a file is fine. I just wanted to make sure you'd thought about both options and picked one.

@slavapestov updated to use the approach you suggested. Please let me know if this matches what you had in mind.
@adrian-prantl I moved the debug messages under -verbose otherwise the input/output file approach doesn't work. Hope this is fine with you.

@swift-ci please smoke test

@swift-ci please smoke test


feat: add pr title checker workflow

Issue:
This PR resolves issue #57
Description:
This pull request addresses the need for a PR title checker to ensure conformity to conventional commit prefixes. The specified prefixes include 'build', 'chore', 'docs', 'feat', 'fix', 'perf', 'refactor', 'revert', 'style', and 'test'. Consistent PR titles are essential for maintaining clarity and organization in the project's version history.
Files added

.github/pr-title-checker.json
.github/workflows/pr-title-checker.yml

Solution:

Developed a PR title checker script to validate titles against the defined prefixes.
Integrated the checker into the project's CI/CD pipeline for automatic validation.
Defined clear error messages for non-compliant PR titles, aiding contributors in adhering to guidelines.

To-Do:

[x] Develop and test the PR title checker script.
[x] Integrate the checker into the CI/CD pipeline.
[x] Define error messages for non-compliant PR titles.

This PR enhances the project's contribution guidelines by automating the validation of PR titles, ensuring adherence to conventional commit prefixes. Contributions and feedback are encouraged for continuous improvement.
@ItsRoy69 please review this PR.
Thanks

LGTM

@ItsRoy69 can you please add iwoc24 and difficulty level tag to the PR? Otherwise, my points won't count.

Sure


ROS2 Dashing + Jetson Inference

Hi guys!
I am trying to run detectnet and imagenet using ROS Dashing in a Jetson Nano 2GB with the JetPack 4.6.
Dashing seems to be working properly - I've just tested some dummy publisher and subscriber nodes.
The real issue comes when I want to integrate Jetson Inference.
The build works without an issue. However, when I try to do the launch for video_source, imagenet or detectnet.
The terminal is properly sourced for ros2 and the workspace. I have not modified a thing in the launch files.
ros2 launch ros_deep_learning detectnet.ros2.launch
I have the following error:
1704759117.6031718 [INFO] [launch]: All log files can be found below/home/puzzlebot/.ros/log/2024-01-08-18-11-56-045550-puzzlebot-desktop-32545
1704759117.6037271 [INFO] [launch]: Default logging verbosity is set to INFO
1704759117.7718298 [ERROR] [launch]: Caught exception in launch (see debug for traceback): invalid syntax (video_source.ros2.launch, line 1)
The log file contains the information I posted above.
Previously I have used the ROS2 docker images without an issue, any clue what might be the problem?
Best

invalid syntax (video_source.ros2.launch, line 1)

Hi @Rolix57, it was probably some syntax change that occurred between Dashing and Foxy, and Dashing being EOL for some time I haven't ever used it

So I figured it out!
Thank you for your response. So... you were totally right, they changed some stuff related to ROS2.
Starting Foxy you can create launches in XML, Yaml and Python. From Dashing to all the previous ones, you can only use Python for launch files.
I wrote the corresponding launch files for the ones available in the repository (video_source, video_output, video_viewer, detectnet, and imagenet), and they work well enough, they just lag a little bit. I assume it is because of the available computational power of the Jetson Nano.
Do you want me to share them with you?
Best

Thank you @Rolix57, yes sure! - for other ROS2 projects I use the Python-based launch files, but in ros_deep_learning I had previously kept it XML for pseudo-compatibility between ROS1/ROS2 (years ago at this point).  But with the waning user base of ROS1, I think it would be good to add the Python launch files 👍

Sure!
They work fine for ROS2 Dashing. However, they might need some slight changes for Foxy+ versions.
launches.zip


Publish on bower registry

This isn't really a code issue but I wasn't sure where else I could put it.
Is it possible for this package to be published on bower, as detailed here?
http://bower.io/docs/creating-packages/
Currently I am using the github URL directly, but it is the only library I am using this way.  Publishing as a bower package would give some direction as to versioning and handling breaking changes.

You put in the right place only. I'll do it and close this issue. Thanks for the suggestion

It's done!
bower install knockout-file-bindings --save

Perfect, thanks :-)


Problem about starting an orderer

Hi, I encountered an issue when I want to start an orderer after starting the proxy.
I firstly started 4 replicas, following the README instruction. Then I started a proxy. All of these commands were done without 'sudo'.
However, when I tried to start an orderer by './orderer/orderer', there is a mistake:

Also the proxy started to log like this:

If I run the proxy with 'sudo', the orderer can start normally but the proxy seems to be untouched. Once I start a timestamp client in the example, the orderer/proxy/stdout are all crashed.
Have you ever encountered this? Thanks you!

Judging from the java exception, I suspect you are using the wrong branch. Make sure you are using the "zeromq" branch at both the HLF fork and this repository.

@jcs47 What do you mean for HLF's ZeroMQ branch? Is it the repository https://github.com/jcs47/fabric?
I used this branch and the ZeroMQ branch of BFTSmart. Do these steps require the root privilege? And what is the content in /tmp folder about? Thanks for your time!

Yes, both the zeromq branch of jcs47/fabric and jcs47/hyperledger-bftsmart. Make sure to switch to that branch in both repos and re-compile the code.

Also, don't forget to install the dependencies I mentioned in the readme.

@jcs47
I changed my bftsmart branch to Zeromq and the HLF's version is your branch. The 4 replicas, proxy and order run well now.
However, when I started the broadcast_timestamp server, the orderer, deliver_stdout crashed and the timestamp server failed to start.
Orderer:

Deliver_stdout:

Timestamp server:

It seems that the system encountered a SIGSEGV signal. What happened when I started the timestamp server?

Did you made sure to re-compile the everything after switching the branch?  You are still using compiled code from the default "master" branch.  I can tell that because the orderer is using the "sendEnvToBFTProxy" method, which does not exist in the zeromq branch. Recompile the fabric code again, and make sure to also re-execute the "go build" command at each of those 3 programs, as described in the readme.

@jcs47
Thanks for your identification of this error. I did not check out the branch of your HLF repo. Now the system seems to be running!
Another question is that how I can run this BFT orderer in a real distributed environment? I got an array of nodes and hope to deploy a Hyperledger cluster with BFT.

Edit the config/host.config file with the ip address of your hosts, as well as the config/system.config file in case you are using more than 4 nodes (you need to fiddle with the parameters system.servers.num, system.servers.f and system.initial.view).
Before launching the nodes, make sure you delete the config/currentView file. Make also sure that you launch each node in numerical order (node 0, node 1, node 2, etc). The command to launch each node at each machine is:
./startReplica.sh
A sample command for each node is:
./startReplica.sh 0 10 /home/joao/gocode/src/github.com/hyperledger/fabric/msp/sampleconfig/signcerts/peer.pem /home/joao/gocode/src/github.com/hyperledger/fabric/msp/sampleconfig/keystore/key.pem 1000
./startReplica.sh 1 10 /home/joao/gocode/src/github.com/hyperledger/fabric/msp/sampleconfig/signcerts/peer.pem /home/joao/gocode/src/github.com/hyperledger/fabric/msp/sampleconfig/keystore/key.pem 1000
./startReplica.sh 2 10 /home/joao/gocode/src/github.com/hyperledger/fabric/msp/sampleconfig/signcerts/peer.pem /home/joao/gocode/src/github.com/hyperledger/fabric/msp/sampleconfig/keystore/key.pem 1000
./startReplica.sh 3 10 /home/joao/gocode/src/github.com/hyperledger/fabric/msp/sampleconfig/signcerts/peer.pem /home/joao/gocode/src/github.com/hyperledger/fabric/msp/sampleconfig/keystore/key.pem 1000
To launch the BFTproxy:
java -cp dist/BFT-Proxy.jar:dist/* bft.BFTProxy 1000 9998 9999
Keep in mind that BFTProxy needs to be in the same machine as the Go orderer, but you only need to install the zeromq dependencies in the machine that has the Go orderer and the BFTproxy.

@jcs47 I'm now trying to run the replica in an un-interactive shell by SSH. However it stopped when the first replica was started. Is it feasible for replica/proxy/orderer to run them in the background?

I know that bftsmart can run in the background, but I never tried to execute this entire ordering service that way. I'll need to check it out, but first I need to make sure the master branch is stable and that this code is compatible with the latest HLF code.

@jcs47 I've changed my way to deploy a network manually. There is 4 replicas and 1 proxy/orderer(on the same node), totally 5 nodes.I set the replica's port to 7050(the communication port is automatically set to 7051) but when I tried to test it by peer node status command the connection was reset. What's the problem? Thanks for your help!

you'll need to give out more context. I don't understand what peer node status is supposed to be.

@jcs47
The prompt of peer node status

The log of ./startReplica.sh

The peer node status should return that the node is running in normal.

Oh, you mean commands from the HLF framework. That is because the bftsmart library is not prepared to interpret anything else other than messages bftsmart clients and bftsmart replicas.

@jcs47 Do you mean that the BFTSmart library only supports messages from BFTSmart clients like the timestamp client? Does it support orderer/sample_clients/single_tx_client? I'm doing tests about this consensus mechanism so I want to find a process which can trigger the consensus process. I wonder how I can trigger a transaction.

@jcs47 Also is there a way to benchmark the cluster's throughput? I found a YCSB workload in the config folder, so I thought that a performance test was done by your group. Is it convenient for you to give me some details? I'm really appreciated for your help!

Regarding your first question, the BFT-SMaRt library is only responsible for executing the distributed protocol for atomic broadcast. Furthermore, each BFTNode is implemented on top of that library, and their funcion is only to take envelopes that have been atomicaly ordered, assembled those envelopes into blocks, sign them, and send them back to the orderer processes (that you invoke by executing orderer/orderer). Try sending those commands to the orderer instead.
As for benchmarks, that YCSB library  is actually one of the dependencies of the BFT-SMaRt library (for one of the demos that uses YCSB) but it is never used in the context of the HLF ordering service. Nonetheless, you can still trigger measurements for throughput by simply keeping sending envelopes to the BFTNodes. Eventually throughput measurements will start popping up at the BFTNodes.


[oolongswap] create strategy

Changes proposed in this pull request:

Copies Uniswap strategy and adjust values for Oolongswap on Boba

This could in practice be added to the existing Uniswap strategy but that could cause issues if Uniswap ever expands to Boba.

➜  snapshot-strategies git:(feat/oolongswap) npm run test --strategy=oolongswap

><EMAIL_ADDRESS>pretest
> npm run build

><EMAIL_ADDRESS>build
> tsc -p .

><EMAIL_ADDRESS>postbuild
> copyfiles -u 1 src/**/*.md dist/ && copyfiles -u 1 src/**/*.json dist/

><EMAIL_ADDRESS>test
> jest test/index.spec.ts --runInBand --testTimeout=120000

  console.log
    [ { '0x4f6798D42feB2A9169F4fBe0f986D005E1b76180':<PHONE_NUMBER>467143 } ]

      at Object.<anonymous> (test/index.spec.ts:48:13)

  console.log
    Resolved in 1.10 sec.

      at Object.<anonymous> (test/index.spec.ts:49:13)

  console.log
    Scores with latest snapshot [ { '0x4f6798D42feB2A9169F4fBe0f986D005E1b76180':<PHONE_NUMBER>467143 } ]

      at Object.<anonymous> (test/index.spec.ts:111:13)

  console.log
    Resolved in 1.25 sec.

      at Object.<anonymous> (test/index.spec.ts:112:13)

 PASS  test/index.spec.ts (5.924 s)

Test strategy "oolongswap"
    ✓ Strategy should run without any errors (1114 ms)
    ✓ Should return an array of object with addresses (1 ms)
    ✓ Should take less than 10 sec. to resolve
    ✓ File examples.json should include at least 1 address with a positive score
    ✓ File examples.json must use a snapshot block number in the past (701 ms)
    ✓ File examples.json must have symbol in its strategy params
    ✓ Returned addresses should be either same case as input addresses or checksum addresses (1 ms)

Test strategy "oolongswap" with latest snapshot
    ✓ Strategy should run without any errors (1755 ms)
    ✓ Should return an array of object with addresses (2 ms)

Test strategy "oolongswap" (with 500 addresses)
    ○ skipped Should work with 500 addresses
    ○ skipped Should take less than 20 sec. to resolve with 500 addresses

Others:
    ✓ Author in strategy should be a valid github username (362 ms)
    ✓ Version in strategy should be a valid string
    ○ skipped Check schema (if available) is valid with example.json
    ○ skipped Strategy should work even when strategy symbol is null

Test Suites: 1 passed, 1 total
Tests:       4 skipped, 11 passed, 15 total
Snapshots:   0 total
Time:        6.256 s
Ran all test suites matching /test\/index.spec.ts/i.


Update MariaDB default version

On the latest CentOS 7.2.x MariaDB application fails to start.
This is fixed with the latest MariaDB 5.5.53 so upgrading to it.
Longer term I think it is better if the blueprint is changed to use the yum mariadb repository and to retrieve an rpm from there.

LGTM

+1; merging now.


[5.0] [Bug] Using fill() does not work on mutated attributes

Took me a while to work out what is going on - I've got a strange bug that is causing issues.
It seems that if you have a mutator - it causes any of those mutated fields to not be updated when using fill().
Working example (with no mutator) if I change a comments and name field:
$booking->fill($request->all());
$booking->save();

gives SQL output
array:4 [▼
  0 => "update `bookings_djfunctions` set `comments` = ?, `name` = ?, `updated_at` = ? where `id` = ?"
  1 => array:4 [▼
    0 => "My comments here"
    1 => "Example"
    2 => "2015-02-21 05:57:18"
    3 => 24
  ]
  2 => 1.2
  3 => "mysql"
]

But if I add a mutator to my class:
public function setCommentsAttribute($value)
{
    return $value;
    // or something like   return "fake";
}

Then this is now the SQL output for the same update query:
array:4 [▼
  0 => "update `bookings_djfunctions` set `name` = ?, `updated_at` = ? where `id` = ?"
  1 => array:3 [▼
    0 => "ExampleAgain"
    1 => "2015-02-21 05:58:58"
    2 => 24
  ]
  2 => 1.2
  3 => "mysql"
]

Notice how the mutated field comments is not included in the SQL statement?
Let me know if you need any further info - I'm still trying to get my head around it.
Edit: removed references to relationships and changed the code - this is happening on all fill() methods.

Ok - the bug is not with fill() - it is with the getDirty() command in Eloquent.
With no mutator:
array:2 [▼
"comments" => "My comments here"
"name" => "Example"
]
with mutator
array:2 [▼
"name" => "ExampleAgain"
]

Never mind - i fail at life today


CHANGELOG.md: fix format and add sections to previous releases

We missed sections and added extra parens in issues.

bors r=@eguzki p=2


[Enhancement]: Add validate to the CLI

This is a proposal for adding validate to the CLI.
Example
dab validate config.json
Reasoning
Longer config JSON files can be difficult to read for errors. We use the CLI, but sometimes manual interaction with the file is necessary. The current (not ideal) approach is to validate a config file is to deploy or start dab to see if there are errors as a result. Using this new validate command can run the same logic already implemented in deploy and start but returns in design time.
Benefits

The developer experience is nicer because validate can include in its error message the line number.'
The devops experience is nicer because configs can be validated as a command line gate operation.

completed in #1856


OUT_OF_SERVICE的Node被莫名其妙的删除，导致重新注册为UP

Describe the bug
Please provide details of the problem, including the version of Spring Cloud that you
are using.
Sample
If possible, please provide a test case or sample application that reproduces
the problem. This makes it much easier for us to diagnose the problem and to verify that
we have fixed it.

eureka client版本1.7.2
spring cloud 版本1.4.5


Make unit-tests for CommandProcessorLib

A corner was cut when the alpha skeleton branch was merged, there exists no unit-tests for the CommandProcessorLibrary.
These should be implemented to ensure they continue to work as expected.
todo

[ ] Implement Unit tests

no longer relevant