Add OP_MSG checksum support

The 4.2 version of the mongo shell sets an optional checksum on OP_MSG wire messages. Per this section of the OP_MSG spec, a message will have the checksumPresent flag set and the last four bytes will be a uint32 checksum. This PR adds support to detect and parse these checksums so we can use a 4.2 shell to connect to mongobetween.

I'm looking into adding a test for this. Integration tests are likely not possible because drivers don't currently add checksums, but I might be able to add a unit test.

Looks good 👍
For the unit test, we could add the flag / checksum to the opmsg here? https://github.com/coinbase/mongobetween/blob/b72171f27d65d79dc77db06f4561978c2cb13d64/mongo/operations_test.go#L71-L80

@mdehoog Added a test in my most recent commit.


GH-1401: SMLC: Fix setConcurrency bug

Fix https://github.com/spring-projects/spring-amqp/issues/1401

@zysaaa Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@zysaaa Thank you for signing the Contributor License Agreement!

Thanks; merged as 07443ceb77272c165c12dc8154cac22da41dd10b after adding a test.


"Enquire now" form: 3 new fields, spinner after submit, inquire→enquire

This addresses  OC-3890 [PEAR-47] [PEAR-48] [PEAR-49] .
To test this:

Use the sandbox, e.g. https://pearson-test.sandbox.stage.opencraft.hosting/contact#00N61000002EYUJ=Some other course&retURL=https%3A//pearson-test.sandbox.stage.opencraft.hosting/courses/course-v1%3Atesting1%2Bother2%2B2018_02/about%23contacted , where I already enabled this theme
Note that in the HTML, I replaced (but not commited to git) the Pearson code, it says nononononono… instead of their original. In this way you can submit the form to SalesForce many times without affecting their data
Check in the HTML that 3 new fields appear: content, medium, term
Check that the button says „enquire“, not „inquire“
The most important: the button. Half-fill the form, the button is still disabled. Click the checkbox, it should be enabled. Click the button, it should warn you of errors and still be clickable.
Correctly fill the form and click the button, it should be temporarily disabled while it's sending. Try clicking it faster, it won't work.
You should also see a circle spinning inside the button while the form is sending.
Try it in slow motion. To do this, go to your /etc/resolv.conf and change your DNS to a non-existant IP (<IP_ADDRESS>). Restart the browser if it uses caché.  Then, submit the form. The DNS resolution of the SalesForce domain will take very long, and you will the button disabled, unclickable, and the spinner spinning

Note that I changed the way the „I agree“ checkbox works: before, it just toggled the button on→off→on→off→…. Now, because the button can be toggled due to other reasons, I made it follow the logic „if the user doesn't agree, the button is disabled“.

+1:  Everything is present, and works as expected.
Note: An easier way to test the spinner (in Firefox), is:

Open the debugger (Ctrl+Shift+S, or press F12 then navigate to the Debugger tab)
Under Sources > pearson-test.sandbox..., select contact,
Set a breakpoint at line 874, if (!errors) {
Fill out the form completely and click the button.
Step through the following lines of code (F10 for each step), and see that the checkbox is disabled at line 879, the button is disabled at line 883, and a spinner appears at line 887.
Verify that those effects persist until the next page loads.

@jcdyer Ah yes, that way to test it is easier and always works, thanks. I would still additionally test it in another way which doesn't involve the debugger, to simulate the real conditions.


Move deps to peer deps

Hi, thanks for package!
I see, that there are packages, that could be moved to peer dependencies, because every nest app already use it:
"@nestjs/common": "6.3.1",
"reflect-metadata": "^0.1.12",
"rxjs": "^6.2.2",

Would you mind if I'll create PR to fix this?

Also if you want I can help with configuring ci/cd for testing and package deploying

OK，thank you


refactor(UI): version page changes

Describe your changes:
Fixes partially #11221
Version page changes and improvements for pages:

[x] Table

https://github.com/open-metadata/OpenMetadata/assets/51777795/bb076b2e-3e45-41fb-ac89-4cf62fc29faa

[x] Topic

https://github.com/open-metadata/OpenMetadata/assets/51777795/4ffb655d-930a-4877-b9b4-5e4d2041522f

[x] Dashboards

https://github.com/open-metadata/OpenMetadata/assets/51777795/19436255-b264-48a5-9f2f-217cec637ce3

[x] Pipeline

https://github.com/open-metadata/OpenMetadata/assets/51777795/c3e5ca56-11cd-44df-bc14-19359fa1445b

[x] mlModel

https://github.com/open-metadata/OpenMetadata/assets/51777795/9fd08dff-2251-4884-bcf6-2c579559160a

[x] Container

https://github.com/open-metadata/OpenMetadata/assets/51777795/d30a4b4e-25e5-49e9-8320-0c6fa19153c5

[x] Glossary

https://github.com/open-metadata/OpenMetadata/assets/51777795/42400e16-bfac-4ce0-9548-551f95a4502d

[x] DataModel

https://github.com/open-metadata/OpenMetadata/assets/51777795/173c9294-4c9b-4697-b9ae-82eca3177c68
Following are the remaining pages with missing version pages which will be added in a different PR:

[ ] Service
[ ] Database
[ ] Database Schema

I worked on updating version pages for different data assets with newly implemented data and bug fixes

Type of change:

[x] Bug fix
[x] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@aniketkatkar97 request description/tags / terms are visible in the Version page
We should hide all the actions on the Version page. It should be a read-only experience for the user


Compiltatio problem with esphome 2023.4.0

There is a problem when i try to compil.
THNKS

INFO Reading configuration /config/esphome/d1_mini_2.yaml...
WARNING 'd1_mini_2': Using the '_' (underscore) character in the hostname is discouraged as it can cause problems with some DHCP and local name services. For more information, see https://esphome.io/guides/faq.html#why-shouldn-t-i-use-underscores-in-my-device-name
INFO Generating C++ source...
Traceback (most recent call last):
File "/usr/local/bin/esphome", line 33, in
sys.exit(load_entry_point('esphome', 'console_scripts', 'esphome')())
File "/esphome/esphome/main.py", line 965, in main
return run_esphome(sys.argv)
File "/esphome/esphome/main.py", line 952, in run_esphome
rc = POST_CONFIG_ACTIONS[args.command](args, config)
File "/esphome/esphome/main.py", line 397, in command_run
exit_code = write_cpp(config)
File "/esphome/esphome/main.py", line 178, in write_cpp
generate_cpp_contents(config)
File "/esphome/esphome/main.py", line 190, in generate_cpp_contents
CORE.flush_tasks()
File "/esphome/esphome/core/init.py", line 622, in flush_tasks
self.event_loop.flush_tasks()
File "/esphome/esphome/coroutine.py", line 246, in flush_tasks
next(task.iterator)
File "/esphome/esphome/main.py", line 170, in wrapped
await coro(conf)
File "/config/esphome/.esphome/external_components/d4d3a138/components/opentherm/number.py", line 34, in to_code
keys = await generate.component_to_code(
File "/config/esphome/.esphome/external_components/d4d3a138/components/opentherm/generate.py", line 107, in component_to_code
entity = await create(conf, key, hub)
File "/config/esphome/.esphome/external_components/d4d3a138/components/opentherm/number.py", line 18, in new_openthermnumber
await number.register_number(var, config, min_value = config[input.CONF_min_value], max_value = config[input.CONF_max_value])
TypeError: register_number() missing 1 required keyword-only argument: 'step'

how compile?

Fix for this is available under #15 .
Before it is merged you can use temporary @ov1d1u repository:
external_components:
  source: github://ov1d1u/esphome-opentherm@main


docs: fix dead links

add npm version badge + update sponsors
appropriating language used in docs

@kiaking could you review the sponsors and let me know if there are any incorrectly displayed or missing?

Thanks for the huge fix! Sponsors looks perfect 👍 LGTM.
If there's nothing you want to add more to the PR, please go ahead and merge it 🎉


feat: update meson to 1.4.0

high-productivity build system
Issue: https://github.com/deepin-community/sig-deepin-sysdev-team/issues/545
Log: update repo

/testall

/test all


[Bug] Point display filtering not working

Was testing out the new release and found that the point option for display filtering doesn't seem to be working at all. It seems to just be using whatever the default is.

You're right, I must have broken it with one of the recent changes before release. I also forgot to document that downscaling was changed to use convolution for all existing filters too, which means it would apply a box filter for the "point" option.
Well, luckily this isn't the most important filter, but I'll try to fix it.

Well, luckily this isn't the most important filter, but I'll try to fix it.

I would argue otherwise, but that's ultimately up to you.

It seems to have been a simple issue, here's a quick fix until the next release:
ddraw.zip (diff.txt compared to v0.5.0)

Fixed in v0.5.1.


Unable to get Hystrix timeouts working

Using the tracer library I am unable to get Hystrix timeouts working.
Description
In case a Command times out it looks like the tracer library is preventing Hystrix from propagating this information. My application gets stuck.
What is going on here?
FYI the test is green if we uncomment plugins.registerConcurrencyStrategy(new TracerConcurrencyStrategy(tracer, delegate)); of setup()

See https://github.com/Netflix/Hystrix/issues/351 - related?

Also https://github.com/Netflix/Hystrix/issues/1767.
Apparently was already bisected to https://github.com/Netflix/Hystrix/commit/951c6f9daa6dc469911b2e29a77fd85d90b4ab1e

FYI the test is green if we uncomment plugins.registerConcurrencyStrategy(new TracerConcurrencyStrategy(tracer, delegate)); of setup()

The test is green when we use tryPreserve instead of preserve in the TracerConcurrencyStrategy. I'm not 100% sure whether this is the correct fix or just a quirk that happens to work.

I'm not 100% sure whether this is the correct fix or just a quirk that happens to work.

Looks as if the current hystrix docs suggest to it like that: https://github.com/mattrjacobs/Hystrix/blob/master/hystrix-core/src/main/java/com/netflix/hystrix/strategy/concurrency/HystrixConcurrencyStrategy.java#L43

Looks as if the current hystrix docs suggest to it like that

After thinking about it, I'm not so sure anymore. tryPreserve is not idempotent. It just has a fallback in case we call it on the wrong thread (by starting a new trace, which is the wrong behaviour).
I guess Netflix/Hystrix#1767 needs to be fixed properly.

Alternatively, could we make use of Hystrix request variables to keep the state?

https://github.com/Netflix/Hystrix/issues/1767#issuecomment-434790114 Looks like there is a workaround that we could implement. Not 100% whether it works in previous versions of hystrix as well.


Rec

Hi AngusJohnson:
I can't understand this function in the struct Rect.Why is not "pt.y<top&&pt.y>bottom"?
	 bool Contains(const Point<T> pt) {     return pt.x > left && pt.x < right&& pt.y > top && pt.y < bottom; }
Thank you!

Why is not "pt.y<top&&pt.y>bottom"?

Firstly, because that would never return true since pt can't be both above and below Rect<T>.
But also, Rect<T>.Contains() should only return true with pt is INSIDE.

Thanks,I udnerstand.
My coordinate system direction is wrong.
The Y-axis direction of the coordinate system is downward.


python 3 support?

Hello. It seems that mljar is python2-compatible but not python3-compatible (e.g. some print ... calls without parentheses, the from mljar import Mljar call in mljar.__init__).
Any plan on releasing a python3-compatible version?

Done! Code should run run with python 2.7 or 3.6


[JenkinsCoverage] Update Jenkins Code Coverage API for new plugin version

Recently, the Jenkins Code Coverage API plugin re-added its external API, but changed the format. This updates the Jenkins service to accommodate the new API.
Unfortunately, this breaks the current test case and I can't find any public instances that have updated to the new plugin version. I've replaced it with my own instance that is up to date, but it's not hosted on a particularly reliable server. I imagine the server jenkins.library.illinois.edu which used to be used will update at some point, so in the future the URL could probably be reverted to what it was before commit 1f104b2.

Unfortunately, this breaks the current test case and I can't find any public instances that have updated to the new plugin

More importantly than just the test cases: From what you're saying there are going to be people out there using this whose badges will break if we deploy this change because they have not updated to the same version of jenkins you are using yet. i.e: if I deploy this change tomorrow, we fix the badge for you (and some other users) but also break it for a bunch of other people.
I think given that, we need to be able to maintain compatibility with both versions.
I think my preferred way to do this would be to define 2 schemas: One for each version. Then we allow the response to match either using Joi.alternatives() and make the badge logic conditional on the response shape. I don't know if v1 and v2 is the right terminology, but we'd do something like
const v1Schema = Joi.object({
  results: Joi.object({
    elements: Joi.array()
      .items(
        Joi.object({
          name: Joi.string().required(),
          ratio: Joi.number().min(0).max(100).required(),
        })
      )
      .has(Joi.object({ name: 'Line' }))
      .min(1)
      .required(),
  }).required(),
}).required()

const v2Schema = Joi.object({
  projectStatistics: Joi.object({
    line: Joi.string()
      .pattern(/\d+\.\d+%/)
      .required(),
  }).required(),
}).required()

...
api: {
  schema: Joi.alternatives.try(v1Schema, v2Schema),

  transform: function(json) {
    if ('results' in json) {
      // do this thing
    }
    if ('projectStatistics' in json) {
      // do that thing
    }
  }
}

I've not tested that code, but hopefully the idea makes sense.

The "determine based on response" approach won't work since the URL changed between versions. I think using an extra query parameter if we want to support the old version of the plugin would work though.
The situation with the plugin is this:

the first version of the plugin had a remote API that the current badge uses
since the 2.0 release (around Oct 2021) it's been nonfunctional
the recent 4.0 release re-added it with the new URL/schema that this PR uses

so I'm not sure whether or not the badge should default to using the new version. Maybe the query param should default to the old plugin if not provided but the frontend builder should default to the new one? (although I haven't looked at how the frontend works so I'm not sure if that's easily done)

OK thanks.
In general, we prioritise backwards-compatibility for existing users so I think the current behaviour should remain the default for  badges using the existing route.
Some possible options:

Make the new route /apiv4, so the format choices become /jacoco, /cobertura, /api (which is the v1 format) and /apiv4 (the new one)
Make the new one /apiv4, rename the old one to /apiv1 and provide a redirect from /api to /apiv1, so the documented format choices are /jacoco, /cobertura, /apiv1, /apiv4 but existing badges using /api redirect to /apiv1. This is basically the same as 1 but it makes it a bit clearer what's going on in the frontend
Leave the format choices as /jacoco, /cobertura, /api but add a ?version= query param, which defaults to 1 if not supplied (again for backwards-compatibility)
Leave the route as /api. Try requesting /coverage/result and /coverage in parallel and roll with whichever one returns a 200, validating against the appropriate schema.

I think 2 is probably the least-worst of those IMO.

Alright, I've had a go at implementing the "expose as apiv1/apiv4 and redirect old badges". It looks like the previous test case for the V1 api has mysteriously stopped working, so I've had to remove that test case. Should it be mocked instead?

Nice work. I've had a look over this and it looks in good shape. If you could replace the v1 test with a mocked test, that would be great. There are lots of examples of service tests using mocks https://github.com/search?q=repo%3Abadges%2Fshields .intercept(nock&type=code I don't know of any public instances we can use.
side note: For centralised services, it is good to have tests that call the live service (even if they can be a bit flaky in some cases) because it means if something changes upstream (e.g: a package registry make a change to their API, or an endpoint gets deprecated, or whatever) then we know about it because our tests start failing. With services like Jenkins which are self-host only and there is no central service, I wonder if it would make more sense to get rid of the live tests and just test against mocks because we don't really get the payoff we normally exchange for the live tests being flaky.
Anyway, that isn't something we need to change in this PR. Lets just mock the apiv1 test and then I'll get this merged. Thanks

Ok I've added a mock based on data from an older build from the previously used test instance.

Thanks. I've pushed one more commit to this before merging, just to change the formatting.
We can pass nock a js object rather than a JSON string for the response, which allows us to lay it out in amore readable way.
Cheers

It does not seem to work?
For example, my Jenkins build here use Code Coverage API Plugin and returns 94%
http://load-balancer-jenkins-master-1462245991.ap-northeast-1.elb.amazonaws.com:8080/job/PRs - CI Build/job/babar/3/
However, when I try https://shields.io/badges/jenkins-coverage with apiv4 nothing shows :/
Is there an update to do to support this coverage plugin?

The current version of the badge expects coverage results to be published with the id coverage, so it'll probably work if you change that in your Jenkinsfile. There should probably be an issue for adding an extra parameter for this though.

Thank you @mincrmatt12  you were right the issue was not a lack of support of the new API. The specificity of the id value was key, my badge now works. Thanks!


i18n(ru): update components.mdx

Update ru/guides/components.mdx

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ru
guides/components.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Config files housekeeping

Series of commits that aim to do a bit of housekeeping of the node configs:

align comments between nctl and production chainspec files
align auction_delay to 1 in configs and nctl scripts
update chainspec values that were out of date or missmatched
remove unused config files

Fixes: https://github.com/casper-network/casper-node/issues/3495

bors try

bors r+


Was #623: Allow suppression of Lock release errors

A bot closed #623.  It's still an issue:
I've run into a problem using the redis-py backend with some caching libraries in Python.  First using dogpile-cache, but all alternatives have the same issue.
The problem is caused by a lock that times out in Redis:
00s Lock is created (redis.py)
05s Lock is timed out (in Redis)
06.0s Value returns (redis.py)
06.1s release() called; LockError is raised due to non-existent lock or it having a different value (from another process)
If I were calling Redis myself, I would just wrap everything in a try block and catch the exception.  Problem solved.
Unfortunately, most libraries operate with Redis support via a plugin that is integrated in a pattern like this:
try:
    plugin.lock_create()
    plugin.get_data()
except:
    plugin.lock_release()
return data

When this pattern is used, there isn't a clean way to handle this error in the caching package, and it can't be handled in the application code because the data isn't returned.
I was hoping you would consider a configuration argument to Lock.init that would allow for a lock_release errors to be suppressed.  That would be much easier for plugins to integrate.
I'd be willing to generate the PR.  The general idea would be adding a LockReleaseError(LockError) to exceptions.py, and then conditionally not raising that based on a config argument -- and instead returning an instance of a LockReleaseError class.

The snippet above is flawed. First, plugin.lock_release() only gets called if some other error was raised. In the (hopefully) typical case of things working correctly, the lock would not get released at all. I'm not sure if that's how the caching library has actually implemented this or of it's an over simplification in your code snippet.
I don't see the point in (optionally) suppressing an error here. If I'm using a lock, I'm probably doing so for good reasons. It's really critical for me to know when my expected behavior has failed.

I don't see a reason to allow lock errors to be suppressed. In the above case, this is something that the plugin can do if it really needs such a thing. It seems to me that knowing an error happened is critical. Please re-open and provide more info if I'm missing something.

I will do. thanks. Sorry I haven't posted a SSCEE yet, I'm still catching up on a lot of open source projects.


change db name

Your merge request is backward. You probably want to merge from my repo to yours. Instead, this request attempts to merge your content into my repo.


Files in file manager need "Move" option on context menu or second folders column

Right now if you have a file on a second page of your file manager, you can't move it into a folder, since you won't see your folders on that page.  So you're only able to move files from the first page into folders.  This can be resolved in two ways:

Add a context menu on files called "Move" that allows you to choose a folder from the tree.
Restructure the file manager so the tree is always on the left, and the paginated files (including search results) are on the right and can be dragged onto tree nodes in the other column.

Approach 1 seems better unless other folder functionality is needed, like being able to drag and drop entire folders.

Yeah, Number 1 would be good.

I think #1 is a good short-term solution, but having utilized folders for a little bit now, a (possibly collapsable?) sidebar would be a really nice improvement.


GitHub action does not find database table

Hi, I'm not sure where to ask for help about this. It may not be a rusqlite problem, maybe an SQLite or even Linux one. Or it's just related to GitHub Actions. I don't really know. But here we go:
I have written a command-line tool that unzips and accesses a bundled SQLite database which was created with rusqlite. On my local machine, everything works fine. However, in the GitHub Actions pipeline, one of the integration tests which access the database always fails on the latest Ubuntu. It's not always the same test, sometimes they take turns.
In the same GitHub action step, the bundled database is unzipped in memory, written do disk and then accessed by the integration test. Could it be that two separate threads are trying to access the database at the same time while the access is not thread-safe?
This is the stacktrace (the bottom is probably more interesting than the top):
command=`"/home/runner/work/chr/chr/target/x86_64-unknown-linux-musl/debug/chr" "--no-paging" "\xc3\x84" "@" "$" "\xc3\x9f" "!"`
code=101
stdout=Preparing Unicode character database, please wait a moment...
Database is ready

stderr=thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value:
SqliteFailure(Error { code: Unknown, extended_code: 1 }, Some("no such table: UnicodeData"))', src/main.rs:175:48
stack backtrace:

0: 0x77ce50 - std::backtrace_rs::backtrace::libunwind::trace::hbf39669e8eecfe2e
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/../../backtrace/src/backtrace/libunwind.rs:96

1: 0x77ce50 - std::backtrace_rs::backtrace::trace_unsynchronized::h6536955678967bbe
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/../../backtrace/src/backtrace/mod.rs:66

2: 0x77ce50 - std::sys_common::backtrace::_print_fmt::h0a8adae8fc4ef9e6
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:79

3: 0x77ce50 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hcce50b82ca571d0c
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:58

4: 0x7b3a6c - core::fmt::write::h7410fe2c9751fa7d
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/fmt/mod.rs:1080

5: 0x7793b2 - std::io::Write::write_fmt::h4c0dae1f7b98e3de
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/io/mod.rs:1516

6: 0x77f06d - std::sys_common::backtrace::_print::hbe0941286da8faf6
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:61

7: 0x77f06d - std::sys_common::backtrace::print::haeefde137ed8b41c
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:48

8: 0x77f06d - std::panicking::default_hook::{{closure}}::hc7652abb91610a87
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:208

9: 0x77ed18 - std::panicking::default_hook::hbbf715ca996ff6f0
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:227

10: 0x77f751 - std::panicking::rust_panic_with_hook::ha99d6ba4510ede21
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:577

11: 0x77f2f9 - std::panicking::begin_panic_handler::{{closure}}::ha0a3abfa52be3c7e
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:484

12: 0x77d2dc - std::sys_common::backtrace::__rust_end_short_backtrace::h928c9a243067ad58
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:153

13: 0x77f2b9 - rust_begin_unwind
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:483

14: 0x7b2d81 - core::panicking::panic_fmt::h8da5cc7278cbda07
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/panicking.rs:85

15: 0x7b2ba3 - core::option::expect_none_failed::hf9a8bfb1faa70e27
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/option.rs:1234

16: 0x402349 - core::result::Result<T,E>::unwrap::h7deec3210076545b
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/result.rs:973

17: 0x406ee8 - chr::retrieve_results::h443b311e393e8b95
at /home/runner/work/chr/chr/src/main.rs:175

18: 0x41c36a - chr::search_database::h7155194fb2b2f02c
at /home/runner/work/chr/chr/src/main.rs:163

19: 0x41b6ac - chr::main::h36b386a029e7d44e
at /home/runner/work/chr/chr/src/main.rs:98

20: 0x41845b - core::ops::function::FnOnce::call_once::hc0b2e9cc194095c0
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227

21: 0x40787e - std::sys_common::backtrace::__rust_begin_short_backtrace::h5a8f00dd7040fab4
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:137

22: 0x407851 - std::rt::lang_start::{{closure}}::h163fbbb0aba62381
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/rt.rs:66

23: 0x77fad9 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::hd103a7da4f5f3e68
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:259

24: 0x77fad9 - std::panicking::try::do_call::h57ffdb711764a297
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:381

25: 0x77fad9 - std::panicking::try::h3e0e9184725a0283
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:345

26: 0x77fad9 - std::panic::catch_unwind::hfc94089ba6b2ab6d
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panic.rs:382

27: 0x77fad9 - std::rt::lang_start_internal::h0d4e7f90d4e375f7
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/rt.rs:51

28: 0x407827 - std::rt::lang_start::h1cd54642b1db321b
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/rt.rs:65

29: 0x41ea4a - main

', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/assert_cmd-1.0.2/src/assert.rs:158:13
stack backtrace:
0: 0x4803d0 - std::backtrace_rs::backtrace::libunwind::trace::hbf39669e8eecfe2e
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/../../backtrace/src/backtrace/libunwind.rs:96

1: 0x4803d0 - std::backtrace_rs::backtrace::trace_unsynchronized::h6536955678967bbe
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/../../backtrace/src/backtrace/mod.rs:66

2: 0x4803d0 - std::sys_common::backtrace::_print_fmt::h0a8adae8fc4ef9e6
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:79

3: 0x4803d0 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hcce50b82ca571d0c
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:58

4: 0x4b856c - core::fmt::write::h7410fe2c9751fa7d
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/fmt/mod.rs:1080

5: 0x408c16 - std::io::Write::write_fmt::h4b74cd0e6d4677ae
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/io/mod.rs:1516

6: 0x47a3cd - std::io::impls::<impl std::io::Write for alloc::boxed::Box<W>>::write_fmt::h62df4730827dad76
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/io/impls.rs:179

7: 0x4828ed - std::sys_common::backtrace::_print::hbe0941286da8faf6
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:61

8: 0x4828ed - std::sys_common::backtrace::print::haeefde137ed8b41c
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:48

9: 0x4828ed - std::panicking::default_hook::{{closure}}::hc7652abb91610a87
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:208

10: 0x482542 - std::panicking::default_hook::hbbf715ca996ff6f0
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:224

11: 0x482fd1 - std::panicking::rust_panic_with_hook::ha99d6ba4510ede21
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:577

12: 0x482b79 - std::panicking::begin_panic_handler::{{closure}}::ha0a3abfa52be3c7e
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:484

13: 0x48085c - std::sys_common::backtrace::__rust_end_short_backtrace::h928c9a243067ad58
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:153

14: 0x482b39 - rust_begin_unwind
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:483

15: 0x482aeb - std::panicking::begin_panic_fmt::haf20a47748297afe
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:437

16: 0x444101 - assert_cmd::assert::Assert::success::hf1892b8c39f248b6
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/assert_cmd-1.0.2/src/assert.rs:158

17: 0x400322 - cli_integration_tests::succeeds_with_character_search_option::h633f2542490b5217
at /home/runner/work/chr/chr/tests/cli_integration_tests.rs:26

18: 0x40465a - cli_integration_tests::succeeds_with_character_search_option::{{closure}}::h25ad6156d25b080e
at /home/runner/work/chr/chr/tests/cli_integration_tests.rs:23

19: 0x4053fe - core::ops::function::FnOnce::call_once::h7efdcbfceb83d8eb
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227

20: 0x42fa93 - core::ops::function::FnOnce::call_once::h3dd146acb242d097
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227

21: 0x42fa93 - test::__rust_begin_short_backtrace::h4c0d2970ff877aed
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/test/src/lib.rs:516

22: 0x42df88 - <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once::he7f1b58b7fbfd1db
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/alloc/src/boxed.rs:1042

23: 0x42df88 - <std::panic::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::h51eb65f8ae7d43b1
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panic.rs:308

24: 0x42df88 - std::panicking::try::do_call::hf7c85dd7d38e9c15
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:381

25: 0x42df88 - std::panicking::try::hd91171643a91eb6b
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:345

26: 0x42df88 - std::panic::catch_unwind::h4a189bce13b36bfc
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panic.rs:382

27: 0x42df88 - test::run_test_in_process::h850ea7006e95a086
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/test/src/lib.rs:543

28: 0x42df88 - test::run_test::run_test_inner::{{closure}}::h3dcf7fd11719467b
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/test/src/lib.rs:449

29: 0x407f96 - std::sys_common::backtrace::__rust_begin_short_backtrace::he0745ea92d7c373a
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys_common/backtrace.rs:137

30: 0x40d0a5 - std::thread::Builder::spawn_unchecked::{{closure}}::{{closure}}::hd099acd06f3aa18a
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/thread/mod.rs:464

31: 0x40d0a5 - <std::panic::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::hb9d08264c93d16c6
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panic.rs:308

32: 0x40d0a5 - std::panicking::try::do_call::h707e5d7c0b6143b8
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:381

33: 0x40d0a5 - std::panicking::try::h5a771d0c48e892af
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:345

34: 0x40d0a5 - std::panic::catch_unwind::h870c012436fa44df
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panic.rs:382

35: 0x40d0a5 - std::thread::Builder::spawn_unchecked::{{closure}}::hdecd407cff650c45
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/thread/mod.rs:463

36: 0x40d0a5 - core::ops::function::FnOnce::call_once{{vtable.shim}}::he37b03a8f6aa1fa6
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/core/src/ops/function.rs:227

37: 0x488e6a - <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once::h1c9450ee681771f3
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/alloc/src/boxed.rs:1042

38: 0x488e6a - <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once::h81e5fd666e5c1445
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/alloc/src/boxed.rs:1042

39: 0x488e6a - std::sys::unix::thread::Thread::new::thread_start::h7ee40607fb4ce1b5
at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/sys/unix/thread.rs:87

"no such table: UnicodeData" suggests that SQLite uses an valid but empty database file.
http://sqlite.org/c3ref/db_filename.html may help you.
At least to make sure you are using the right path.
But currently, this method is not available in rusqlite public API.
However, temporarily, you can use Connection::handle and copy this code.
Another way is to remove the SQLITE_OPEN_CREATE flag where you expect to open an already existing database.

"no such table: UnicodeData" suggests that SQLite uses an valid but empty database file.
http://sqlite.org/c3ref/db_filename.html may help you.
At least to make sure you are using the right path.
But currently, this method is not available in rusqlite public API.
However, temporarily, you can use Connection::handle and copy this code.
Another way is to remove the SQLITE_OPEN_CREATE flag where you expect to open an already existing database.

Thanks for your quick response, @gwenn.
The path should definitely be correct as it is dynamically determined by the dirs crate. It works on macOS and Windows but not on Ubuntu. I think it's a problem with how different threads in the GitHub actions pipeline try to access the database in the integration test step. I will investigate whether switching the flag while opening the database can solve this problem.

Thanks for your quick response, @gwenn.
The path should definitely be correct as it is dynamically determined by the dirs crate. It works on macOS and Windows but not on Ubuntu. I think it's a problem with how different threads in the GitHub actions pipeline try to access the database in the integration test step. I will investigate whether switching the flag while opening the database can solve this problem.

The problem still exists when settings the flag SQLITE_OPEN_READ_ONLY.
The executable path is: /home/runner/work/chr/chr/target/x86_64-unknown-linux-musl/debug/chr
The database path is: /home/runner/.chr/chr_1_0_0.db
Could it be that the home directory is somehow not readable by the action worker on Ubuntu?

The problem still exists when settings the flag SQLITE_OPEN_READ_ONLY.
The executable path is: /home/runner/work/chr/chr/target/x86_64-unknown-linux-musl/debug/chr
The database path is: /home/runner/.chr/chr_1_0_0.db
Could it be that the home directory is somehow not readable by the action worker on Ubuntu?

Check the size of /home/runner/.chr/chr_1_0_0.db.
Because SQLite will happily open an empty file:
touch empty.db
sqlite3 -readonly empty.db

Also you can do a PRAGMA quick_check; after uncompressing the database to make sure all is fine.

Check the size of /home/runner/.chr/chr_1_0_0.db.
Because SQLite will happily open an empty file:
touch empty.db
sqlite3 -readonly empty.db

Also you can do a PRAGMA quick_check; after uncompressing the database to make sure all is fine.

Thanks @gwenn but I'm not convinced that the problem is caused by the database itself. Why should it be empty on Ubuntu while it is working well on macOS and Windows? That doesn't make sense except for a possible bug in rusqlite.
I've opened an issue for the people dealing with the virtual environments for GitHub actions. Perhaps they have an idea what's going on. I will leave this issue here open until a solution is found.

Thanks @gwenn but I'm not convinced that the problem is caused by the database itself. Why should it be empty on Ubuntu while it is working well on macOS and Windows? That doesn't make sense except for a possible bug in rusqlite.
I've opened an issue for the people dealing with the virtual environments for GitHub actions. Perhaps they have an idea what's going on. I will leave this issue here open until a solution is found.

A solution was found in the meantime. It was the way how Ubuntu handles threads in combination with cargo's multi-threaded execution of unit tests. If you switch the test execution to single-threaded mode, the database is not blocked anymore and can be accessed by all tests.
So, this issue here can be closed. Nevertheless, thanks a lot again @gwenn.

A solution was found in the meantime. It was the way how Ubuntu handles threads in combination with cargo's multi-threaded execution of unit tests. If you switch the test execution to single-threaded mode, the database is not blocked anymore and can be accessed by all tests.
So, this issue here can be closed. Nevertheless, thanks a lot again @gwenn.


[nghttp2] update to 1.39.2

Library name: nghttp2
New version number: 1.39.2
This is a security update that fixes DoS issues discovered by Netflix: https://github.com/nghttp2/nghttp2/releases/tag/v1.39.2

Now, nghttp2 updated to the new version. Please close this issue.

Thanks!


[Access] Add start/end height to EventsResponse

Description
Add start and end heights to the response from GetEventsForHeightRange. This allows clients to identify when the last available height on the Access node is lower than the end_height provided in the request

ref https://github.com/onflow/flow-go/issues/4019


Modular subroutes

The way subroutes work currently seems to be anti-modular. It would make more sense to have a way to define them inside the component, or any other way to lazily load them together with the component. Or am I missing something?

Duplicate of #298


More tests for indexing

Codecov Report

Merging #34 (e979f43) into master (9b23b77) will increase coverage by 0.31%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #34      +/-   ##
==========================================
+ Coverage   86.50%   86.81%   +0.31%
==========================================
  Files           9        9
  Lines         363      364       +1
==========================================
+ Hits          314      316       +2
+ Misses         49       48       -1

Impacted Files
Coverage Δ

src/indexing.jl
87.50% <100.00%> (+0.83%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9b23b77...e979f43. Read the comment docs.

Codecov Report

Merging #34 (e979f43) into master (9b23b77) will increase coverage by 0.31%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #34      +/-   ##
==========================================
+ Coverage   86.50%   86.81%   +0.31%
==========================================
  Files           9        9
  Lines         363      364       +1
==========================================
+ Hits          314      316       +2
+ Misses         49       48       -1

Impacted Files
Coverage Δ

src/indexing.jl
87.50% <100.00%> (+0.83%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9b23b77...e979f43. Read the comment docs.

@simonbyrne I've added a test for the code you've patched in #33 and there was a bug, sorry for that. It's fixed in this PR.

@simonbyrne I've added a test for the code you've patched in #33 and there was a bug, sorry for that. It's fixed in this PR.

Thanks!

Thanks!


Undefined behavior in all classes with getMembers method

Required information
Nearly all classes with the method getMembers() have undefined behavior after move since the move constructor and assignment operator have default specifiers which do not invalidate the underlying data pointer.
(Maybe incomplete list) of all affected classes

InterfacePort
ServerPortUser
PublisherPortUser
PublisherPortRoudi
ServerPortRoudi
ApplicationPort
SubscriberPortUser
ClientPortUser
ClientPortRoudi
BasePort
ChunkQueuePopper
ChunkSender
ChunkQueuePusher
ChunkReceiver
ConditionListener
ConditionNotifier
ChunkDistributor

Solution

For every class an explicit move constructor and move assignment operator has to be implemented which invalidates the pointer to the members.
But please pay attention to call the parent move constructor/assignment operator first when there is inheritance involved!

Parent::operator=(std::move(*this));

getMembers must return a reference/const reference to the underlying members since the members should be never nullptr.

Maybe we should think of using something like the std::reference_wrapper instead of implementing all the move constructors and assignment operators in the classes itself. The only problem is that the classes are not memcopyable anymore. Not sure if they are now or if it's important.


Fix for node build on ventura

I don't know if we actually need this but you can build the server on ventura right now but you can't build the node client. Most people don't need to be able to build the server or the node client but if we support one we should support the other?
On the other hand, running more stuff through shell scripts means more to undo when supporting windows/powershell?
Pre-merge checklist

[x] I am very sure this PR could not affect performance.

@eatonphil looks like the mac benchmark is broken?

@kprotty @cb22 I dropped the benchmark.sh fix for now so we can get the build.sh in since there was an issue in benchmark.sh I didn't have time to look at.


Add deploy script

So, this script doesn't work yet. PS crashes with:
Error Loading Teambuilder.json Error: ENOENT: no such file or directory, open '/Users/zarel/Workspace/digimon-showdown/pokemon-showdown/config/chat-plugins/teambuilder.json'
    at Object.openSync (fs.js:457:3)
    at Object.readFileSync (fs.js:359:35)
    at FSPath.readSync (/Users/zarel/Workspace/digimon-showdown/pokemon-showdown/.lib-dist/fs.js:66:13)
    at Object.<anonymous> (/Users/zarel/Workspace/digimon-showdown/pokemon-showdown/server/chat-plugins/teambuilder.js:369:66)
    at Module._compile (internal/modules/cjs/loader.js:1158:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
    at Module.load (internal/modules/cjs/loader.js:1002:32)
    at Function.Module._load (internal/modules/cjs/loader.js:901:14)
    at Module.require (internal/modules/cjs/loader.js:1044:19)
    at require (internal/modules/cjs/helpers.js:77:18)

This repository seems to be missing teambuilder.json.

This repository seems to be missing teambuilder.json.

Should be resolved with #52

Yep, it works now.
Now all you need to do to run Digimon Showdown is


feat: Add console logging support for Frame Processors

What
Until now you could not log something to the Metro JS console. The only way to log something was through the native HostFunction _log, which only logged to Xcode Logs/Android Logcat.
This PR changes this and adds support for using console to log messages to the Metro console. (e.g. console.log, console.debug, etc)
When trying to add support for this, I noticed that there were a few threading issues with the way Frame Processors are currently implemented - mainly that they use the reanimated UI Thread Scheduler for scheduling stuff, which (afaik) should only be a problem when you passed a function to a FP Plugin. But this PR fixes this by implementing a custom Scheduler.

Adds console support to the VisionCamera Frame Processor runtime so you can use console.log inside of useFrameProcessor
Creates a new Scheduler for the VisionCamera FP Thread instead of the REA UI Thread
Android: Fixes accessing the VisionCamera FP Runtime on the wrong Thread (JS Thread instead of VisionCamera FP Thread)

Changes

Tested on

iPhone 11 Pro
Android Simulator

Related issues

Waiting for https://github.com/software-mansion/react-native-reanimated/pull/2219

Possibly also waiting for https://github.com/software-mansion/react-native-reanimated/pull/2220


Arabic Translation Progress

Maintainer List

@asantarissy
@iRayan7
@aladin002dz
@Fcmam5
@mohshbool
@3imed-jaberi
@splimter

For New Translators
To translate a page:

Check that no one else has claimed your page in the checklist and comments below.
Comment below with the name of the page you would like to translate. Please take only one page at a time.
Clone this repo, translate your page, and submit a pull request!

Before contributing, read the glossary and style guide to understand how to translate various technical and React-specific terms.
Please be prompt with your translations! If you find that you can't commit any more, let the maintainers know so they can assign the page to someone else.
PS: Please use Hsoub's wiki as your reference but keep in your mind we need to keep the tech. terms in the English and Arabic language.
eg: unit testing (وحدات الاختبار), javascript (جافاسكريبت),...etc.
For Maintainers
When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:

[x] Home Page (@tesseralis) #1

When PRs are merged, make sure to mark that page as completed!

[x] RTL Support (@asantarissy) #8

Core Pages
To do before releasing as an "official" translation. Please translate these pages first.

[x] Home Page (@fkanout) #36, #37, #38 & #39
[x] Tutorial (@3imed-jaberi) #135

Basics

[x] Hello World (@maskeddeveloper) #125
[x] Introducing JSX (@asantarissy) #9
[x] Rendering Elements (@omar-dulaimi) #10
[x] Components and Props (@asantarissy) #11
[x] State and Lifecycle (@3imed-jaberi) #115
[x] Handling Events (@aladin002dz) #21
[x] Conditional Rendering (@AdhamMoussa) #22
[x] Lists and Keys (@splimter) #53
[x] Forms (@aladin002dz) #17
[x] Lifting State Up (@aladin002dz) #25
[x] Composition vs Inheritance (@a-deeb) #29
[x] Thinking in React (@ahmedfarag36) #31

API Reference

[x] React (@hgareeballa) #32
[x] React.Component (@splimter) #40
[x] ReactDOM (@splimter) #43
[x] ReactDOMServer (@splimter) #71
[x] DOM Elements (@splimter) #44
[x] SyntheticEvent (@splimter) #45
[x] Test Utilities (@splimter) #46
[x] Shallow Renderer (@splimter) #47
[x] Test Renderer (@splimter) #48
[x] JS Environment Requirements (@splimter) #49
[x] Glossary (@splimter) #51

Navigation
These are the navigation links that appears in the sidebar. Possibly wait until
the corresponding sections are translated to do these.

[x] tutorial/nav.yml (@3imed-jaberi ) #136
[x] docs/nav.yml (@3imed-jaberi ) #97

Next Steps
These are the next most important translations, ordered by importance:
Installation

[x] Getting Started (@mhmdAljefri) #54
[x] Add React to a Website (@mhmdAljefri) #55
[x] Create a New React App (@mhmdAljefri) #56
[x] CDN Links (@mohshbool) #70
[x] Release Channels (@mohamedsgap) #205

Hooks
Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.

[x] Introducing Hooks (@splimter) #57
[x] Hooks at a Glance (@splimter) #58
[x] Using the State Hook (@splimter) #59
[x] Using the Effect Hook (@aladin002dz) #60
[x] Rules of Hooks (@splimter) #61
[x] Building Your Own Hooks (@splimter) #63
[x] Hooks API Reference (@splimter) #68
[x] Hooks FAQ (@splimter) #69

Testing

[x] Testing Overview (@mohdule) #195
[x] Testing Recipes (@mohamedsgap) #198
[x] Testing Environments (@mohamedsgap) #202

Concurrent Mode ( New )

[ ] Introducing Concurrent Mode (@Fcmam5) #207
[x] Suspense for Data Fetching (@mohamedsgap) #208
[ ] Concurrent UI Patterns
[x] Adopting Concurrent Mode (@mohamedsgap) #218
[x] Concurrent Mode API Reference (@mohamedsgap) #225  (@3imed-jaberi) #243

Warnings
These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.

[x] dont-call-proptypes (@mohshbool) #121
[x] invalid-aria-prop (@mohshbool) #123
[x] invalid-hook-call-warning (@mohshbool) #126
[x] legacy-factories (@mohshbool) #145
[x] refs-must-have-owner (@mohshbool) #134
[x] special-props (@mohshbool) #141
[x] unknown-prop (@mohshbool) #132

Advanced Guides

[x] Accessibility (@splimter) #64
[x] Code-Splitting (@splimter) #65
[x] Context (@splimter) #66
[x] Error Boundaries (@aminebenkeroum) #67
[x] Forwarding Refs (@mohshbool) #91
[x] Fragments (@splimter) #74
[x] Higher-Order Components (@aladin002dz) #119
[x] Integrating with Other Libraries (@3imed-jaberi) #102
[x] JSX In Depth (@3imed-jaberi) #103
[x] Optimizing Performance (@fcmam5) #96
[x] Portals (@3imed-jaberi) #101
[x] Profiler API (@ahmed-abdulhuy) #395
[x] React Without ES6 (@aladin002dz) #93
[x] React Without JSX (@m1m6) #78
[x] Reconciliation (@Fcmam5) #99
[x] Refs and the DOM (@mohshbool) #108
[x] Render Props (@Fcmam5) #105
[x] Static Type Checking (@3imed-jaberi) #89
[x] Strict Mode (@3imed-jaberi) #92
[x] Typechecking With PropTypes (@AbdelkhalekESI) #80
[x] Uncontrolled Components (@3imed-jaberi) #95
[x] Web Components (@3imed-jaberi) #94
[x] Web Components  (@3imed-jaberi) #215

FAQ

[x] APIs and AJAX (@maskeddeveloper) #83
[x] Babel, JSX, and Build Steps (@3imed-jaberi) #138
[x] Passing Functions to Components (@3imed-jaberi) #139
[x] Component State (@maskeddeveloper) #85
[x] Styling and CSS (@maskeddeveloper) #86
[x] File Structure (@maskeddeveloper) #88
[x] Versioning Policy (@maskeddeveloper) #116
[ ] Versioning Policy #minors-versus-patches
[x] Virtual DOM and Internals (@3imed-jaberi ) #114

Contributing
Priority: Low

[x] How to Contribute (@Fcmam5) #120
[ ] How to Contribute (@ahmed-abdulhuy) #branch-organization & #feature-flags #394
[x] Codebase Overview (@ahmedkrmn) #131
[ ] Implementation Notes (@mriiad) #372
[ ] Design Principles

Components
Components in src/components that have some text in them.

[x] CodeEditor (@Fcmam5) #110
[x] CodeExample (@Fcmam5) #110
[x] ErrorDecoder (@Fcmam5) #110
[x] LayoutFooter (@Fcmam5) #110
[x] LayoutHeader (@Fcmam5) #110
[x] MarkdownPage (@Fcmam5) #110

Additional Translations
These are not the primary translation targets.

[ ] Blog
[x] Community #117
[x] Community - Meetups (@3imed-jaberi) #221
[ ] Community - Team

@22mahmoud, @SaifAsad, @Emmanuel-Melon, @iRayan7 how's it going? Do you have any questions or need any help getting started?

I would love to help! i see no pages are currently taken so i will start by the home page.

@22mahmoud, @SaifAsad, @Emmanuel-Melon, @iRayan7 how's it going? Do you have any questions or need any help getting started?

Yes, I do. Which repository should I clone and push changes to? Is it https://github.com/reactjs/ar.reactjs.org or https://github.com/reactjs/reactjs.org?

@Emmanuel-Melon This one.

@Emmanuel-Melon This one.

Thanks, I have just cloned it. BTW, have you started working on the home page?

No, but willing to start today.

No, but willing to start today.

Make a pull request so I could attach your name to the page you're editing.

@tesseralis i think we will need some help as well to transform the website to RTL

@fawzisf I'll look into it! For now, maybe looking at what the Persian translation is doing might be useful: https://github.com/reactjs/fa.reactjs.org/pull/7/files

Hey,
I'm interested to contribute to this, I'll do the Hello world page.

Can I join you guys please?
BTW "unit testing" = "اختبار الوحدات"

Hey @IsraaMoqbel , Please open a PR, So I could assign you to this page

Can I join you guys please?
BTW "unit testing" = "اختبار الوحدات"

Thanks @omar-dulaimi, please read The Contribution Guidelines, pick a page to translate and open a PR so I can assign you to it. enjoy!
الله حيو النشمي 😄

Can I join you guys please?
BTW "unit testing" = "اختبار الوحدات"

Thanks @omar-dulaimi, please read The Contribution Guidelines, pick a page to translate and open a PR so I can assign you to it. enjoy!
الله حيو النشمي 😄

Thanks man @tesseralis , I have read them all just a while ago. I'm going to pick 'rendering elements' if I may.
الله يحييك  😁

Can I join you guys please?
BTW "unit testing" = "اختبار الوحدات"

Thanks @omar-dulaimi, please read The Contribution Guidelines, pick a page to translate and open a PR so I can assign you to it. enjoy!
الله حيو النشمي 😄

Thanks man @asantarissy , I have read them all just a while ago. I'm going to pick 'rendering elements' if I may.
الله يحييك 😁

That's great @omar-dulaimi, please create a PR so I can assign you to this page.

Can I join you guys please?
BTW "unit testing" = "اختبار الوحدات"

Thanks @omar-dulaimi, please read The Contribution Guidelines, pick a page to translate and open a PR so I can assign you to it. enjoy!
الله حيو النشمي 😄

Thanks man @asantarissy , I have read them all just a while ago. I'm going to pick 'rendering elements' if I may.
الله يحييك 😁

That's great @omar-dulaimi, please create a PR so I can assign you to this page.

I just did @asantarissy Thank you.

Salam, Hello everyone,
I think we need to create a facebook group for all participants, for discussions, collaborations and sharing tips and experiences, and lead the project to a brilliant result.
Cheers,
Mahfoudh Arous

@fawzisf I'll look into it! For now, maybe looking at what the Persian translation is doing might be useful: https://github.com/reactjs/fa.reactjs.org/pull/7/files
indeed, I found some useful markdown tags in the project like these:

@fawzisf I'll look into it! For now, maybe looking at what the Persian translation is doing might be useful: https://github.com/reactjs/fa.reactjs.org/pull/7/files

indeed, I found some useful markdown tags in the project like these:

...

Salam, Hello everyone,
I think we need to create a facebook group for all participants, for discussions, collaborations and sharing tips and experiences, and lead the project to a brilliant result.
Cheers,
Mahfoudh Arous

Thanks @aladin002dz, I sent you a link on messenger to join us on slack.
Also, please check this #8 merged PR for the RTL implementation.
Enjoy.

i'll take Basics Lists and Keys

i'll take Basics Lists and Keys

That's great @splimter, please create a PR so others won't work on the same page.
Enjoy!

Hey guys, can I help translate the  \repos\ar.reactjs.org\content\docs\Composition-vs-Inheritance page?

Hello good enthusiastic people;
This idea of improving the Arabic content never left my head so I am so happy to help,
I have been learning react for a while and read many of docs pages.
Ready to translate the tutorial or thinking in react 👍

Hey guys, can I help translate the \ar.reactjs.org\content\docs\Composition-vs-Inheritance page?

Sure @a-deeb, please do the following:

[ ] Read this issue
[ ] Check our Glossary and Style Guide
[ ] Pick a page to translate
[ ] Create a PR
[ ] And enjoy! 😄

Hello good enthusiastic people;
This idea of improving the Arabic content never left my head so I am so happy to help,
I have been learning react for a while and read many of docs pages.
Ready to translate:

the tutorial or
thinking in react 👍.

@ahmedfarag36 and we would be more than happy to have you on board.
Read this issue and check our Glossary and Style Guide, the tutorial page is already taken, maybe you can start on Thinking in React page.
Please create a PR so I can add you here.
Cheers!

Hey 👋,
Am gonna take the Introducing Hooks page.

Hey @asantarissy, I don't think Hooks word needs to be translated, since it have other definistions in arabic, So I'll keep it as it is in English without not confusing to the reader, so they'll know it's a name of a feature added to react and doesn't have a meaning in arabic.

Hey @asantarissy, I don't think Hooks word needs to be translated, since it have other definistions in arabic, So I'll keep it as it is in English without no confusing to the reader, so they'll know it's a name of a feature added to react and doesn't have a meaning in arabic.

Yes I agree with you, and this is what the team suggested.
Great then, enjoy.

Hi
i want to contribute, can someone assign a section to me !?
or i get to chose !?
THanks

Hi
i want to contribute, can someone assign a section to me !?
or i get to chose !?
THanks

Welcome @hgareeballa, you can pick a page, please create a PR so I can assign you to it, also don't forget to check our Glossary and Style Guide
Enjoy

@asantarissy
i will take //
API Reference
React
React.Component
Thanks

@asantarissy
i will take //
API Reference
React
React.Component
Thanks

Great @hgareeballa, please create a "work in progress" PR for this (steps) and use Hsoub as reference for this.

Hi everyone, I would like to contribute ... well, I've already submitted my PR before seeing this issue 🤷🏼♂ Could you mention this issue in the contribution guide, so no one could miss it?

Hello everyone! 👋
I am gonna take Hooks at a Glance

Hello maintainers where are you?
I have started to translate the glossary however there is another pull request but I didn't notice since it is available here in the check list.

Hello maintainers where are you?
I have started to translate the glossary however there is another pull request but I didn't notice since it is available here in the check list.

@asantarissy is our moderator, please ping him on the dedicated slack channel

Hi everyone, I would like to contribute ... well, I've already submitted my PR before seeing this issue 🤷🏼♂ Could you mention this issue in the contribution guide, so no one could miss it?

Thank you @fkanout, your PRs are in review, great job 💪🏼
Feel free to pick another page so I can assign it to you in this issue.

Hello maintainers where are you?
I have started to translate the glossary however there is another pull request but I didn't notice since it is available here in the check list.

Sorry @ahmedfarag36 my bad 🙂
Please Pick another page so I can assign you to it here.

Hi everyone, I would like to contribute ... well, I've already submitted my PR before seeing this issue 🤷🏼♂ Could you mention this issue in the contribution guide, so no one could miss it?

Thank you @fkanout and done thanks to @iRayan7, your PRs are in review, great job 💪🏼
Feel free to pick another page so I can assign it to you in this issue.

@asantarissy that's great, thank you and @iRayan7 👌🏻

Hey I wanna help here. I will take Get Started page @tesseralis

Hey I wanna help here. I will take Get Started page @tesseralis

That's great @mhmdAljefri, please create a work-in-progress PR so I can assign the page to you, don't forget to check our Glossary, Contribution and Style Guides

Hello everyone, I wanna start helping here and I am gonna start working on "State and Lifecycle"

Hello everyone, I wanna start helping here and I am gonna start working on "State and Lifecycle"

Great @ZolfekarAskarieh, please create a work-in-progress pull request so I can assign the page to you, also please go through our Glossary, Contribution and Style Guides

I will take the Error Boundaries page!

I will take the Error Boundaries page!

That's great @aminebenkeroum, I'll assign the page to you, don't forget to go through our Glossary, Contribution and Style Guides

CodeEditor

CodeEditor

Thanks @iron2017, page assigned 🎉
Please open a work-in-progress PR and check our Glossary, Contribution and Style Guides

Hello friends, why @splimter is taking too many pages?
If we translate them in parallel it would be more efficient and more convenient for him.
Thanks

@ahmedfarag36 i had time for it, i want to contribute before i get busy with univ stuff.
you can at anytime translate other section :)

Ok @splimter, I appreciate you efforts and now I got the point happy translating :smiley:

@ahmedfarag36 btw am not doing the hard part, thanks to our maintainers <3.

I would like to help in the translation to Arabic,
I found that no one has been assigned to FAQ so is it possible for me to help translating ?
I can start with APIs and AJAX and proceed sequentially on each FAQ page :)

I would like to help in the translation to Arabic,
I found that no one has been assigned to FAQ so is it possible for me to help translating ?
I can start with APIs and AJAX and proceed sequentially on each FAQ page :)

Sure!
Thanks, @maskeddeveloper! AJAX and APIs page is assigned to you 🎉
Please create a "work in progress" PR for this. Check the contribution steps and use Hsoub as reference.

Hey Guys,
I'd like to contribute, and would like to start with react-without-jsx

Hey Guys,
I'd like to contribute, and would like to start with react-without-jsx

Hey @m1m6! just assigned react-without-jsx to you 🎉
Please create a "work in progress" PR for this. Check the contribution steps. Thanks.

Hello everybody,
I will take higher order components
Is it ok @iRayan7

Hello everybody,
I will take higher order components
Is it ok @iRayan7

Hi @ahmedfarag36, Higher-Order Components is assigned to you 🎉
Please create a "work in progress" PR for this. Check the contribution steps. Thanks.

Hey Guys,
I'd like to contribute, and would like to start with Typechecking With PropTypes

Hi,
I have done with the translation of typechecking-with-proptypes.md
PR :  #80

Hi Guys ,
So i'd like to contribute more and more in this translation so i will work this time on FAQ Section

Babel, JSX, and Build Steps
Passing Functions to Components
I know that you recommend translate just one page but the first one is short .
Thanks

Hi Guys ,
So i'd like to contribute more and more in this translation so i will work this time on FAQ Section

Babel, JSX, and Build Steps
Passing Functions to Components
I know that you recommend translate just one page but the first one is short .
Thanks

Great @AbdelkhalekESI!
Please make a pull request for each. Thanks.

Hello , I've done the faq-ajax,
can i proceed to :

Component State
Styling and CSS

Many Thanx

Hello , I've done the faq-ajax,
can i proceed to :

Component State
Styling and CSS

Many Thanx

Assigned to you 👍
Please create a draft PR for each one. Thanks.

@iRayan7 i've done the 2 pages, please check it , could you please assign me the rest of the FAQ pages :

File Structure
Versioning Policy
Virtual DOM and Internals

Many Thanx

@iRayan7 i've done the 2 pages, please check it , could you please assign me the rest of the FAQ pages :

File Structure
Versioning Policy
Virtual DOM and Internals

Many Thanx

Go for it! 😍
Please create a draft PR for each. Thanks.

Hello Guys,
I would like to help in the translation to Arabic,
I will start with ' Static Type Checking ' page .

Hello Guys,
I would like to help in the translation to Arabic,
I will start with ' Static Type Checking ' page .

Hey! Okay, you can fork, clone create another branch on which you change the title of the the page you booked, and then send the pull request,
please, use this translation:
https://wiki.hsoub.com/React
Happy working,

I'll take 'strict-mode' page .

Hello!
I would like to help :smile: , may I start with Optimizing Performance ?

Welcome @Fcmam5 ..
Okey , you can take this page and please , make sure you use  this translation: https://wiki.hsoub.com/React
and read the Gloassary :
https://github.com/reactjs/ar.reactjs.org/wiki/Glossary ..
Happy working

I'll take 'web-components' and 'uncontrolled-components' pages .

I'll take 'docs/nav.yml'.

Hello everyone,
I am finished with Optimizing Performance (#96).
Can I proceed to Reconciliation?
And how about the pages that have been assigned but they became inactive like (#4, #7, #10 ...), what can we do about it?

Hello everyone,
I am finished with Optimizing Performance (#96).
Can I proceed to Reconciliation?
And how about the pages that have been assigned but they became inactive like (#4, #7, #10 ...), what can we do about it?

Thanks, @Fcmam5!
Sure Reconciliation has been assigned to you.
For the inactive pages, we will re-assign them once we complete the other unassigned pages.

As Salam Alikum,
I finished translating Reconciliation (#99), and I'd like to continue with:

Portals
Render Props

And for sure each of them will be in a seprate PR :nerd_face:

@Fcmam5 sorry bro , i finish 'Portals' page and i sended a PR 😕 ..

@Fcmam5 sorry bro , i finish 'Portals' page and i sended a PR confused ..

No worries :) thank you for your contribution :smile: !

@Fcmam5 sorry bro , i finish 'Portals' page and i sended a PR 😕  ..

No worries :) thank you for your contribution 😄 !

Thank you too for your efforts and contribution 🤝

I'll take 'Integrating with Other Libraries' page.

I'll take 'JSX in depth' page too 🤗.

I'll take 'Refs and the DOM' page

@tesseralis  @22mahmoud  @Emmanuel-Melon  @iRayan7 @asantarissy @aladin002dz
Please make sure that the people who took the pages and didn't send PR are still contributing 🤔 ‼ ...
In case of abandonment, please update the list 😁.

I would like to work on the components section:

CodeEditor (it's not active anymore)
CodeExample
ErrorDecoder
LayoutFooter
LayoutHeader
MarkdownPage

I would like to work on the components section:

CodeEditor (it's not active anymore)
CodeExample
ErrorDecoder
LayoutFooter
LayoutHeader
MarkdownPage

Changes will only affect just a few lines in:
src/components/CodeEditor/CodeEditor.js
src/components/CodeExample/CodeExample.js
src/components/ErrorDecoder/ErrorDecoder.js
src/components/LayoutHeader/Header.js
src/components/LayoutHeader/SearchSvg.js

Should it be only in one pull request?

Bro , if you needs help i'm with you in this section.. just tell me ❤🤝🔥

Just finished refs and the dom (#108). Not sure what's left since the list above isn't, afaik, up-to-date

I would like to work on the components section:

CodeEditor (it's not active anymore)
CodeExample
ErrorDecoder
LayoutFooter
LayoutHeader
MarkdownPage

Changes will only affect just a few lines in:
src/components/CodeEditor/CodeEditor.js
src/components/CodeExample/CodeExample.js
src/components/ErrorDecoder/ErrorDecoder.js
src/components/LayoutHeader/Header.js
src/components/LayoutHeader/SearchSvg.js

Should it be only in one pull request?

Yes, please. One PR would be fine 👍

I will work on:

How to Contribute
Community

I would like to take Virtual DOM and Internals if it's not taken by @maskeddeveloper since there's a strikethrough

I'll also take Warnings. I'll be submitting each file in a pull request of its own

is there any page left, I can help with?

I would like to take Virtual DOM and Internals if it's not taken by @maskeddeveloper since there's a strikethrough

It's already been translated by @3imed-jaberi

Hey guys 👋
Please stick with the process of page assignment. You have to comment before you start working on it.
Thanks ❤

These pages are available:
Basics

[ ] Hello World

Advanced Guides

[ ] Higher-Order Components

Please comment before you start working on it 👍

@iRayan7 assign me the  Hello World Page

@iRayan7, assign me the "Higher-Order Components" page

@tesseralis @iRayan7 as discussed https://github.com/reactjs/ar.reactjs.org/pull/4,
@Emmanuel-Melon still working on the PR !

@iRayan7 assign me the Hello World Page

@iRayan7, assign me the "Higher-Order Components" page

Sure, 👍Open up a new PR, please.

@tesseralis @iRayan7 as discussed here,
@Emmanuel-Melon still working on the PR !

@atefBB, it's okay, you could work on it. Would you like to do a complete do over or pick up from where I'd left off?

@iRayan7 Hey Rayan, can I be assigned to translate these remaining warning messages:
legacy-factories, refs-must-have-owner, special-props, and unknown-prop ?

@iRayan7 Hey Rayan, can I be assigned to translate these remaining warning messages:
legacy-factories, refs-must-have-owner, special-props, and unknown-prop ?

I'm sorry Ahmed but I'm already doing them I just haven't submitted the PRs yet. How about checking the 'Contributing' section?

@iRayan7 Hey Rayan, can I be assigned to translate these remaining warning messages:
legacy-factories, refs-must-have-owner, special-props, and unknown-prop ?

I'm sorry Ahmed but I'm already doing them I just haven't submitted the PRs yet. How about checking the 'Contributing' section?

I saw you did dont-call-proptypes, invalid-aria-prop, and invalid-hook-call-warning, but those I am asking for aren't assigned to anyone!

@iRayan7 Hey Rayan, can I be assigned to translate these remaining warning messages:
legacy-factories, refs-must-have-owner, special-props, and unknown-prop ?

I'm sorry Ahmed but I'm already doing them I just haven't submitted the PRs yet. How about checking the 'Contributing' section?

I saw you did dont-call-proptypes, invalid-aria-prop, and invalid-hook-call-warning, but those I am asking for aren't assigned to anyone!

I know but I'm doing them as I said in a comment above

@mohshbool sorry Mohammad, haven't seen your comment.
@iRayan7 Can I take the Codebase Overview page?

@ahmedkrmn all is well 😅
You should be able to take "codebase overview", we would be more than happy to have you on board.
Read this issue and check our Glossary and Style Guide.
Please create a PR so I can add you here.

@ahmedkrmn all is well 😅
You should be able to take "codebase overview", we would be more than happy to have you on board.
Read this issue and check our Glossary and Style Guide.
Please create a PR so I can add you here.

Thanks. The PR is #131.

Hi !
any page available

Hi !
any page available

hey @Aissaoui-Ahmed, you might wanna check out the 'Contributing' section or perhaps the Community issue #117

thank you @mohshbool

I will take Implementation Notes

I will translate the Testing Overview page

Half of the word "مجتمع المطورين"  is hiding behind the search bar, Would like to work on that

Hello Guys, so enthusiastic to begin, Shall We refactor Todo app in the tutorial to Function components (Hooks) ?

Anyone is working on /languages page ??

@mohdule , you can take Testing Overview page.

Anyone is working on /languages page ?? Can I work on it?

Do you mean languages.yml file !!

@3imed-jaberi I mean ar.reactjs.org/languages

@3imed-jaberi I mean ar.reactjs.org/languages

🚀 ..

Alright cool @3imed-jaberi, gonna get it done by next Sat hopefully

Hi @tesseralis and @3imed-jaberi I really want to contribute and translate any of the Testing ( New ) pages, please assign to me any page and I will translate it :)

Is there  any opportunity to contribute in the translation and improve it ? @tesseralis

@mohamedsgap ,  welcome 👋 !
It's good to meet enthusiastic people like you ❤
You can start with  Testing Recipes  🚀 ..

Hey everyone, do you have plans to translate the new concurrent mode pages? I can take a stab at this!

I can help too 🌚

@forabi @cdes 👋 ..
I would like to thank you for your interest ..
We are currently working to integrate (merge) all updates to our Arabic content and soon this section will be ready ...
Now, you can start with Testing Environments or Design Principles.
You can also help @Fcmam5 in #163 ...

Can I join you guys please?
BTW "unit testing" = "اختبار الوحدة"

@Karamiq welcome 👋 ..
you can start with Testing Recipes  or  Testing Environments  🚀 ..

@Karamiq welcome 👋 ..
you can start with Testing Recipes or  Testing Environments 🚀 ..

@3imed-jaberi
I'm currently working on Testing Recipes

@Karamiq welcome 👋 ..
~you can start with Testing Recipes or  Testing Environments 🚀 ..~

@Karamiq , you can start with  Testing Environments 🚀 ..

I'm working on Design Principles

@3imed-jaberi   @Aissaoui-Ahmed  I gonna work on Testing Environments!

@3imed-jaberi  @Aissaoui-Ahmed @asantarissy  Hi guys! I finished translating Testing Environmnts, please review my pull request :)

@3imed-jaberi I'm working on Design Principles

@cdes what's the status on this? 😃

@3imed-jaberi  @Aissaoui-Ahmed  @tesseralis  @asantarissy  Hey guys :) I wonder if there ara any opporunities to contribute to more repos related to React to write a real code this time! or any available pages i noticed that Concurrent Mode ( New ) is created, one more thing how do I become one of React Community like you :)

Hey guys! @asantarissy @iRayan7 @aladin002dz @Fcmam5 @mohshbool @3imed-jaberi @splimter please assign to me any page to translate it!

Hey guys! @asantarissy @iRayan7 @aladin002dz @Fcmam5 @mohshbool @3imed-jaberi @splimter please assign to me any page to translate it!

Thanks @mohamedsgap, please pick a page/s and create a PR so I can assign you.
Enjoy 😊

Hey guys! @asantarissy @iRayan7 @aladin002dz @Fcmam5 @mohshbool @3imed-jaberi @splimter I'm going to translate Release Channels!

Hey guys! @asantarissy @iRayan7 @aladin002dz @Fcmam5 @mohshbool @3imed-jaberi @splimter I'm going to translate Release Channels!

Good luck Mohamed 🚀 !

I will take "Introducing Concurrent Mode"

I gonna work on ''Suspense for Data Fetching''  @asantarissy @iRayan7 @aladin002dz @Fcmam5 @mohshbool @3imed-jaberi @splimter  @Aissaoui-Ahmed

@3imed-jaberi I'm working on Design Principles

@cdes what's the status on this? 😃

I'm unable to work on it. Sorry.

I've just finished translated the most challenging page I've ever translated "Suspense for data fetching", I need your review, guys! :)
@asantarissy @iRayan7 @aladin002dz @Fcmam5 @mohshbool @3imed-jaberi @splimter @Aissaoui-Ahmed

I'm working on " Concurrent UI Patterns" documentation. ⌨

@HassanMuhamad great choice, Hassan! keep going and I will follow you up with  'Adopting Concurrent Mode' after my current PR's been merged!

The line above: Concurrent UI Patterns (@hassan Muhamad) incorrectly tags me; can the author correct? Sorry, I don't speak Arabic 😞

The line above: Concurrent UI Patterns (@hassan Muhamad) incorrectly tags me; can the author correct? Sorry, I don't speak Arabic 😞

Thanks @hassan for the heads-up 😊

I will take "Implementation Notes" and "Design Principles"

I will take "Implementation Notes"

Welcome to @all newcomers!

Hi guys, I would like to translate "Concurrent UI Patterns" page

Hi guys, I would like to translate "Concurrent UI Patterns" page

Thank you for joining the team @YassinHussein, please go ahead I'll assign the page to you.

[ ] Read this issue
[ ] Check our Glossary and Style Guide
[x] Pick a page to translate
[ ] Create a PR
[ ] And enjoy! 😄

I would love to take a page please assign me whatever is available   Versioning Policy || profiler API

Welcome @maqalaqil 👋🏻, it's yours.

Thank you :D

Hey all, would love to help you guys with this. Can you assign Implementation Notes & Design Principles to me?

Hi guys,
I would like to translate 'Implementation Notes' page, would it be possible to assign it to me please ?
@3imed-jaberi @Aissaoui-Ahmed, @aladin002dz, @asantarissy, @Fcmam5
Thank you!

Hello @mriiad, Sure you can take it. You need to submit a PR.

Hello @tech-chieftain @maqalaqil @YassinHussein,
Are there any updates about the pages you took?

Hello @mriiad, Sure you can take it. You need to submit a PR.

Hello again @3imed-jaberi
Thanks for the quick reply, here's the PR associated to this task https://github.com/reactjs/ar.reactjs.org/pull/372
Could you just add all the suitable labels and assign yourself as a reviewer please ?
Thank you!

Hey @3imed-jaberi, as Implementation Notes was assigned to @mriiad I can still work on Design Principles. Can you please assign it to me so others can focus on other pages? It will be ready in the next couple of days. Thanks

Hey @3imed-jaberi ill have the PR ready today.

Hi guys,
I would like to translate the 'how to contribute' #branch-organization & #feature-flags page would it be possible to assign it to me, please?
Thank you!

@ahmed-abdulhuy you can open PR
Thank you for your contribution

I would like to translate the 'Profiler API'  page would it be possible to assign it to me, please?
Thank you!

@tech-chieftain @maqalaqil, if you take any page please open a draft pr to help me to assign it to you!

b1-2283a18c-b2a2-4dd2-ac5c-d4563dd8ce46

Hey, I would like to translate "Design Principles" in Contributing section
Which is not assigned to anyone as i can see in the list

Hi, I will take Concurrent UI Patterns - thanks

Hi, I will take Concurrent UI Patterns - thanks

also I did an initial start and translate the head of concurrent-mode-patterns.md file in this draft https://github.com/reactjs/ar.reactjs.org/pull/454

Hello guys, first let's say RAMADHAN MOUBAREK ☪❤.
I would say, in the coming days, we will start the translation for the new website version.
For that, I will create a new progress-tracking issue, and in the meanwhile, the missing pages here are still available for translation.

I created https://github.com/reactjs/ar.react.dev/issues/464 for the new translation. Let's coordinate there!


Show "(at block xxxxx)" in the status bar behind "NIS is synchronized!", not behind balance

I think the information about the current height makes more sense in the status bar.
As long as NIS is synchronized, the block height is not interesting for average joe, so that shouldn't be visible behind the balance.
If NIS is not synchronized, there should be a warning at the balance. Something like "might be inacruate, NIS not synchronized" or whatever.

@Jaguar0625 I think we still show current height SOMEWHERE

as i said -> status bar? :D

@fyahfox you mean the one on top, hmm it's bit small, but could do the trick

its pretty wide i think :D no need for a second line...
Example:
NIS is synchronized! (current block height: 53058)

@gimer agree to show height somewhere


Added a minor command to help find the serivce.

Codecov Report

Merging #1377 (4eedb7c) into main (79562b1) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1377      +/-   ##
==========================================
- Coverage   65.42%   65.40%   -0.02%
==========================================
  Files         119      119
  Lines       12866    12866
==========================================
- Hits         8417     8415       -2
- Misses       3774     3775       +1
- Partials      675      676       +1

Impacted Files
Coverage Δ

internal/core/rtsp_source.go
49.09% <0.00%> (-1.82%)
:arrow_down:

internal/core/webrtc_conn.go
54.56% <0.00%> (-0.34%)
:arrow_down:

internal/core/rtmp_source.go
67.80% <0.00%> (+2.05%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

merged, thanks


Add option to allow linting of files without a TypeScript extension

Fixes #515

talked offline, decided we don't need to tackle this feature right now


Add page titles to all pages

I just wanted to try out gatsbyjs looks awesome, thanks!
I noticed the titles in the starter set did not work. This should fix it.
DocumentTitle is used but somehow not completely implemented. As in the other starters I set the titles to be set in the wrappers. In the pages that are not using wrappers, I set it up in the according JS file. Not sure if it is ideal.
I not much into react so please look over it :)

Oh this is great! Yeah, I didn't add <DocumentTitle> for some reason to the default starter.


Fix sqlite appveyor

Recent changes to cargo mean that cargo test won't look for dlls in paths outside of the target dir even if a build script tries to add them - the path/dylib path must be manually updated outside of cargo.

Added a commit to generate an import library to fix the msvc tests also.

I have experience in dealing with appveyor or sqlite on windows, but this looks good… and green! So, 👍 from me. Anyone else want to have a look? @sgrif?

It should be there as long as the AppVeyor build machine doesn't change radically. It's the version from Visual Studio 2013, but any of the 10-odd tool chains on the image would be fine. I somewhat arbitrarily chose the version from VS2103 since mysql also requires VS2013 at this point (although I have an incoming PR that allows 2015 and 2017 to work with mysql also.)
The other alternative I was able to think of was to put the VS tools in the path, but that is a global change that will indirectly affect rustc and this way will not.


Wrangler is broken

Describe the bug
Wrangler is broken on version 3.0.1
Steps To Reproduce
nix shell nixpkgs#wrangler (latest flake)
wrangler dev
--> Error: spawn /nix/store/d70h3plhhzpx0wrn20dpyghi3nrp28wx-wrangler-3.0.1/lib/node_modules/wrangler/node_modules/@cloudflare/workerd-linux-64/bin/workerd ENOENT
Expected behavior
wrangler dev should start the server
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 6.3.1-zen1, NixOS, 23.11 (Tapir), 23.11.20230529.5e871d8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - channels(chebuya): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

greetings !
I am not familiar enough with wrangler, but maybe the issue has been fixed ?
 nix shell nixpkgs#wrangler

[kirillvr@tsutenkaku:~]$ wrangler dev
 ⛅ wrangler 3.1.0
------------------
wrangler dev now uses local mode by default, powered by 🔥 Miniflare and 👷 workerd.
To run an edge preview session for your Worker, use wrangler dev --remote

✘ [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. `wrangler dev path/to/script`) or the `main` config field.

If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose

Still broken on 3.1.0.
The issue is with workerd, included binary which is not fixed for nixos.
zsh: no such file or directory: /nix/store/0bd0rqri60r80yq5r5icq5lc191xi55k-wrangler-3.1.0/lib/node_modules/wrangler/node_modules/@cloudflare/workerd-linux-64/bin/workerd

@Chebuya @tinybeachthor if you are able to test this https://github.com/NixOS/nixpkgs/pull/238886

@kirillrdy #238886 fixes it, thanks!
(There is a typo in the PR name, wranger instead of wrangler.)

@tinybeachthor thanks for picking up typo !

Yeah, it works. tried it too.
chebuya@laptop ~/d/ircworker> wrangler dev
 ⛅ wrangler 3.1.0 (update available 3.1.1)
-----------------------------------------------------
wrangler dev now uses local mode by default, powered by 🔥 Miniflare and 👷 workerd.
To run an edge preview session for your Worker, use wrangler dev --remote
⎔ Starting local server...
[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-05-18",
but you've requested "2023-06-01". Falling back to "2023-05-18"...
[mf:inf] Ready on http://<IP_ADDRESS>:8787/


Convert Ben's Python Examples

Files under
https://github.com/InstituteforDiseaseModeling/emodpy-snt/tree/main/examples/ben/example

[x] run_1960-2004.py
[x] run_2005-2022.py

Implemented and tested.


Development setup with devenv failed:

PHP Version
8.2
Shopware Version
6.6.2
Expected behaviour
git clone git@github.com:shopware/shopware.git
cd shopware
devenv up

Then I created a .env file with the database url
DATABASE_URL="mysql://shopware:shopware@<IP_ADDRESS>:3306/shopware?sslmode=disable&charset=utf8mb4"

in new terminal:
devenv shell
bin/console system:install --basic-setup --create-database --force

Shopware should be installed and accessible under localhost:8000
Actual behaviour
Outputs:
Warning: require_once(/Users/lanzelotmoll/workspace/shopware-dev/shopware/bin/../vendor/autoload_runtime.php): Failed to open stream: No such file or directory in /Users/lanzelotmoll/workspace/shopware-dev/shopware/bin/shopware on line 16

Fatal error: Uncaught Error: Failed opening required '/Users/lanzelotmoll/workspace/shopware-dev/shopware/bin/../vendor/autoload_runtime.php' (include_path='.:/nix/store/sxld48dayip79w4mf684rc6hz5201jv9-php-8.2.18/lib/php') in /Users/lanzelotmoll/workspace/shopware-dev/shopware/bin/shopware:16
Stack trace:
#0 {main}
  thrown in /Users/lanzelotmoll/workspace/shopware-dev/shopware/bin/shopware on line 16

Tried to fix by running
composer install

then the installation works but shopware is rendering dom only and admin does not appear

With the production template everything works fine
did I misunderstand something in the docs?
How to reproduce
see above

shopware/shopware has an little different setup than other setups. For shopware/shopware you need to run once composer run setup and then everything should be fine.
When you want to uses Shopware, please create a flex project. Using shopware/shopware is only intended for contribution to Shopware

Building extensions it's fine to use shopware/shopware, but for projects you want shopware as an dependency so you see on diffs only your changes and not whole shopware
In the shopware/core and so the assets are prebuild, and not with shopware/shopware so you need to rebuilt the storefront and admin to have css/js :)

Thank you so much! I will dive a bit deeper into that.