fix: resolve various parser issues

set ecmaVersion acorn option to 2020 (https://github.com/esxjs/esx/issues/17)
fix function attributes parsing (https://github.com/esxjs/esx/issues/17)
fix imported components registration (fix: #2)
fix computed props
add lockfile

@irudoy I tried out this change (just directly added the code in node_modules to-esx) and still see it breaking on optional chaining.

@prograhammer can you provide stack trace of error thrown with these changes?

@irudoy there's no new errors that appear with these changes, I'm just noticing that optional chaining still breaks. See here: https://github.com/esxjs/esx/issues/17

@irudoy BTW, I'm able to get through this issue by transpiling (via babel-loader) twice. I do one pass through babel on the optional chaining, etc, then another pass with babel-plugin-esx-ssr. However now I'm facing an issue with none of the components registering from esx:
ReferenceError: ESX: FooComponent not found in registered components","stack":"ReferenceError: ESX:
FooComponent not found in registered components\n    at grow (webpack-
internal:///./node_modules/esx/lib/parse.js:116:13)\n    at parse (webpack-
internal:///./node_modules/esx/lib/parse.js:363:11)\n    at raw (webpack-internal:///./node_modules/esx/index.js:292:24)\n
at render (webpack-internal:///./node_modules/esx/index.js:350:31)\n

@irudoy Update: I think the ReferenceError: ESX: FooComponent not found in registered components error my be comiing from renderToNodeStream. I tried withrenderToString and the error went away. I still need to confirm ESX is working though.

@irudoy Now I'm transforming import/exports to commonjs (require). That get's be past the register errors, but now I'm getting ReferenceError: React is not defined.

@prograhammer first of all consider, that esx project isn't stable for now, and I'm also trying to get it to work with my codebase as well 😄 Personally, I'm not using babel-plugin-esx-ssr because it has issues, and with webpack it's more rational to use a loader to convert the whole module to esx.
Registration issues with imports should be resolved by this PR. Could you create an isolated repro? And for React is not defined too. Seems like it's related to your build tool setup.


Provided add-in package was not understood error when uploading app

Hi,
I am trying to upload the company Communicator Users app manifest and getting below error.

Hi @pmkinyua ,
Thanks for raising the query. Could you please share the manifest files of author and user zip files


Add an icon component

HTML5 is fully compatible with SVG vector map. Compared with italic markup, SVG can have more patterns, and magnification will not distort, but also can display color patterns, color patterns of ICONS to modify the color is invalid, only monochrome icon can modify the color, in other components to adapt ICONS, You also need to optimize icon styles with other components slot slots

@ulquiowu
thanks for contribute to this repo! ☕
and here are two things need to confirm

dev branch's component comes from local lib NOT from npm
please perform a PR to origin repo here

Add row and COL layout components and temporarily remove icon components before adjusting


Item number for in progress contracts

Noticed that ed and stephanie both try to search for spec numbers in their in progress contracts. When asked if spec number or item number is preferable for the in progress contracts, Ed said:

The item number was good to have when we were doing the spreadsheets. When I started sitting in on  the meetings we were having back in the day, they would always shout out spec number 1234 and they would find it on there. Bill was obviously at that point conducting the meetings, so anytime he would  shout out a spec number it was because there was an incident he need to discuss. We would have six pages of spreadsheet you would have to scour through those pages. So I asked if we could add a item number that was consecutive so it was easier to find. Going forward I don’t know if that number would be significant anymore.

So it seems like we should switch to spec number. Thoughts @shellicious @bsmithgall?

The main problem with this is that the majority of things in-progress don't actually have spec numbers. They don't get them until the County assigns them.
We could do what we are doing in the title card, which is to display the spec number of the contract if it exists, and if not, display the spec number of the parent contract.

Thoughts on this?

@bsmithgall they're just using whatever spec number they have on hand, so I think the same logic that's used in the card would work fine.

The spec number is added for new contracts by the county and only changes when rebids happen. So maybe we could do a '0000' or '9999' or some other kind of designation that indicates this is a new contract, it doesn't have a spec number yet.

@hamhands are you saying that we should get rid of the item number column? As long as there's no situation in which it is necessary, that's fine.
What number should they use to reference contracts instead? The old spec number? The new spec number / "----" if there isn't one yet?

I'm saying that the item number isn't relevant in conductor. It had relevance in a spreadsheet when they needed to scan a paper copy for a record, but in a search interface they use spec number. I haven't seen them try to look something up using the item number, but they try to look up an in progress record using the spec every single time they look up a contract.

Ditch item number in favor of spec number.
If no spec number, write "----"


Feature: Nullable reference types annotations

We are migrating to WASDK and adopt .NET 6, so we get build-in nullable reference types support.
Requirements

We should annotate our code to eliminate thousands of warnings about NRT.

This is a large one, but we can do it progressively.

Good idea, I believe we can do this one by one (e.g. update things as you notice them).

We should annotate our code to eliminate thousands of warnings about NRT.

What's the proper way to resolve these warnings? Making properties nullable solves the warnings but doesn't offer any protection.

According to stackoverflow and the Microsoft docs, the way to eliminate the warnings with "possible" is to mark the properties as nullable or to check for null values

My 2 cents: If something can be null, we should make it nullable and add null checks where they are used. If the property can never be null (for reasons that the compiler cannot know about), then disabling the warning for that property with an explanation why is the best way.

I think that's a fair solution. That being said, these warnings should be fixed as needed because otherwise, opening a pull request just to fix the warnings takes away from other review efforts.

So opening a PR just to fix these warnings is not encouraged?

I think not

So opening a PR just to fix these warnings is not encouraged?

It can also impact stability to make large changes like this without understanding the context.

Just to clarify my previous comments, opening PRs for this that are limited in scope (eg one or two classes) are fine.

Removed null-ref warnings in all Widgets classes in the widget view models introduction PR.

As this might have to be done gradually and not in Separated PRs, can’t we merge this to #4180?


Update convert-user-mailbox-to-shared-mailbox.md

Added a note about how to convert a user mailbox to a shared mailbox when it has a online archive

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/2371

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks


after upgrade, "no such file" errors in mounted volume

Output of docker version:
Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 7
 Running: 1
 Paused: 0
 Stopped: 6
Images: 46
Server Version: 1.12.0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 82
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.15-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.788 GiB
Name: moby
ID: 72HH:OBYI:OHW2:TSCQ:KI25:M6QQ:QHWJ:BNC2:KWSO:OUPF:DF5M:W4UE
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 26
 Goroutines: 45
 System Time: 2016-08-02T16:00:28.269018806Z
 EventsListeners: 1
No Proxy: *.local, 169.254/16
Registry: https://index.docker.io/v1/
Insecure Registries:
 <IP_ADDRESS>/8

Output of docker inspect on the affected container:
[
    {
        "Id": "d0c198d435b11b2fa8b696ffd631f256c3ee15433ff8f73446073c82888c9335",
        "Created": "2016-07-26T17:23:18.362402209Z",
        "Path": "/bin/bash",
        "Args": [],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 1786,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2016-08-02T15:57:37.774760796Z",
            "FinishedAt": "2016-08-02T15:57:28.172229576Z"
        },
        "Image": "sha256:1b088884749bd93867ddb48ff404d4bbff09a17af8d95bc863efa5d133f87b78",
        "ResolvConfPath": "/var/lib/docker/containers/d0c198d435b11b2fa8b696ffd631f256c3ee15433ff8f73446073c82888c9335/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/d0c198d435b11b2fa8b696ffd631f256c3ee15433ff8f73446073c82888c9335/hostname",
        "HostsPath": "/var/lib/docker/containers/d0c198d435b11b2fa8b696ffd631f256c3ee15433ff8f73446073c82888c9335/hosts",
        "LogPath": "/var/lib/docker/containers/d0c198d435b11b2fa8b696ffd631f256c3ee15433ff8f73446073c82888c9335/d0c198d435b11b2fa8b696ffd631f256c3ee15433ff8f73446073c82888c9335-json.log",
        "Name": "/debian-work",
        "RestartCount": 0,
        "Driver": "aufs",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "",
        "ExecIDs": [
            "34d88a74b051f44d12ebfab0d5fc9d54ddf36f90c17e9b1c3fadbf6f750e015a"
        ],
        "HostConfig": {
            "Binds": [
                "/Users/ranger/git/opennms-repo:/opennms-repo"
            ],
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "json-file",
                "Config": {}
            },
            "NetworkMode": "default",
            "PortBindings": {},
            "RestartPolicy": {
                "Name": "no",
                "MaximumRetryCount": 0
            },
            "AutoRemove": false,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "CapAdd": null,
            "CapDrop": null,
            "Dns": [],
            "DnsOptions": [],
            "DnsSearch": [],
            "ExtraHosts": null,
            "GroupAdd": null,
            "IpcMode": "",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": false,
            "PublishAllPorts": true,
            "ReadonlyRootfs": false,
            "SecurityOpt": null,
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "ConsoleSize": [
                0,
                0
            ],
            "Isolation": "",
            "CpuShares": 0,
            "Memory": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": null,
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": [],
            "DiskQuota": 0,
            "KernelMemory": 0,
            "MemoryReservation": 0,
            "MemorySwap": 0,
            "MemorySwappiness": -1,
            "OomKillDisable": false,
            "PidsLimit": 0,
            "Ulimits": null,
            "CpuCount": 0,
            "CpuPercent": 0,
            "IOMaximumIOps": 0,
            "IOMaximumBandwidth": 0
        },
        "GraphDriver": {
            "Name": "aufs",
            "Data": null
        },
        "Mounts": [
            {
                "Source": "/Users/ranger/git/opennms-repo",
                "Destination": "/opennms-repo",
                "Mode": "",
                "RW": true,
                "Propagation": "rprivate"
            }
        ],
        "Config": {
            "Hostname": "d0c198d435b1",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": true,
            "StdinOnce": false,
            "Env": [
                "no_proxy=*.local, 169.254/16",
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "Cmd": [
                "/bin/bash"
            ],
            "Image": "debian:latest",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": {}
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "5f2ae7588586580123f4b7a47f16066a360d4615f15725dae616a59a94ce02aa",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {},
            "SandboxKey": "/var/run/docker/netns/5f2ae7588586",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "ca96703431fd4c0e6fcb428d89820c7576278558fefb7300e9bc763a1a2135ac",
            "Gateway": "<IP_ADDRESS>",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "<IP_ADDRESS>",
            "IPPrefixLen": 16,
            "IPv6Gateway": "",
            "MacAddress": "02:42:ac:11:00:02",
            "Networks": {
                "bridge": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "b8c0e1cf2699892d710c0d35fe69f49a0859dd56c81ad715c0b630a85d793780",
                    "EndpointID": "ca96703431fd4c0e6fcb428d89820c7576278558fefb7300e9bc763a1a2135ac",
                    "Gateway": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:ac:11:00:02"
                }
            }
        }
    }
]

Additional environment details (AWS, VirtualBox, physical, etc.):
Mac OS X 10.11.6 on a MacBook Pro.
I've been working on a set of java tools for modifying Yum (RPM) repositories.  I have a large set of unit tests that all passed under the last Docker for Mac beta before the final release came out (1.12.0-rc4 maybe?  I don't recall.)  I run the unit tests in a volume that is mounted from a subdirectory in my homedir (/Users/ranger/git/opennms-repo).
Since upgrading to the final 1.12.0 release, my unit tests now fail with "FileNotFoundException".  These tests create and delete a lot of small files, running createrepo reindexing repositories, copying around RPMs, etc.  I know all through the betas there were a lot of release notes about various issues with mounted volumes and filehandles, so my first suspicion is that it's related.
Steps to reproduce the issue:

run my unit tests in a docker container

Describe the results you received:

many tests fail with file I/O errors

Describe the results you expected:

all tests pass

Additional information you deem important (e.g. issue happens only occasionally):
Note that these tests all pass just fine if I copy my /opennms-repo volume-mounted directory into another directory inside the docker VM.  They only fail when run directly in the mounted volume.

Thanks for reporting, and sorry to hear you're running into this issue.
We very recently opened a separate issue tracker for issues that are specific to Docker for Mac; could you open this issue in that issue tracker? https://github.com/docker/for-mac/issues
I'll close this issue here for housekeeping

No problem.  Done: https://github.com/docker/for-mac/issues/74


Merge branch-Sort with Master

Closes #35
Implemented sorting persons by name.
Modified some existing test cases so that they work with the new method signatures, but haven't added any new tests specific to the sorting feature.

Codecov Report
Base: 72.15% // Head: 71.77% // Decreases project coverage by -0.38% :warning:

Coverage data is based on head (f14e9c9) compared to base (01d8573).
Patch coverage: 65.62% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #53      +/-   ##
============================================
- Coverage     72.15%   71.77%   -0.39%
- Complexity      399      416      +17
============================================
  Files            70       73       +3
  Lines          1232     1293      +61
  Branches        125      131       +6
============================================
+ Hits            889      928      +39
- Misses          311      331      +20
- Partials         32       34       +2

Impacted Files
Coverage Δ

...in/java/seedu/address/logic/parser/ParserUtil.java
85.36% <0.00%> (-11.86%)
:arrow_down:

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)

src/main/java/seedu/address/model/person/Name.java
72.72% <0.00%> (-7.28%)
:arrow_down:

...ain/java/seedu/address/model/person/SortField.java
60.00% <60.00%> (ø)

.../seedu/address/logic/parser/ListCommandParser.java
66.66% <66.66%> (ø)

...java/seedu/address/logic/commands/ListCommand.java
81.81% <77.77%> (-18.19%)
:arrow_down:

.../seedu/address/logic/parser/AddressBookParser.java
100.00% <100.00%> (ø)

...ain/java/seedu/address/logic/parser/CliSyntax.java
85.71% <100.00%> (+2.38%)
:arrow_up:

src/main/java/seedu/address/model/AddressBook.java
92.59% <100.00%> (+0.92%)
:arrow_up:

...rc/main/java/seedu/address/model/ModelManager.java
100.00% <100.00%> (ø)

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Exception in label generated

Hello, I followed the training guide and trained a parlerTTS model from scratch. First I initialized a new mod using
python helpers/model_init_scripts/init_dummy_model.py ./parler-tts-untrained-dummy --text_model "google-t5/t5-small" --audio_model "parler-tts/dac_44khZ_8kbps

After that, I referred to the parameters provided in the training guide and modified the tokenizer slightly to match the model,  Specifically, this includes
--description_tokenizer_name "google-t5/t5-small" \
--prompt_tokenizer_name "google-t5/t5-small" \

At the same time I modified the batch size to initiate training.
However, there seems to be an error in generating the labels, where two of the nine channels are completely populated with 1024 (i.e. pad_token/eos_token), is this situation stemming from the model not being adequately trained?
I've attached an image showing the results generated.

Meanwhile I ran into a second problem, I'm using the officially provided training tutorial and I'm encountering error reporting when executing the forward function of the ParlerTTSSinusoidalPositionalEmbedding class.
My code will execute up to this point:
https://github.com/huggingface/parler-tts/blob/8b8c576e2dbdc29172e30be7d68fac9357cd92c5/parler_tts/modeling_parler_tts.py#L221-L222
Then the error message is
AttributeError: 'ParlerTTSSinusoidalPositionalEmbedding' object has no attribute 'offset'

How should self.offset be defined and can I take any value?

Hey @MingHui-Fang, thanks for opening the issue, this is indeed a weird error. could you send a reproducing code snippet with regards to your first error and send more details on what you exactly did ? What you did does seem correct to me.
For the offset thing, there's definitely a bug with the offset missing!
You can have a workaround either by chunking your audio to chunks less than 30s or by setting a longer context window here:https://github.com/huggingface/parler-tts/blob/8b8c576e2dbdc29172e30be7d68fac9357cd92c5/helpers/model_init_scripts/init_model_600M.py#L27

Sincerely thank you for your answer, the first problem I have solved, I found out that it is because of using wrong generation_config.json when generating.
secondly in the second problem, there may be some problem in the code to initialize tiny-model (init_dummy_model.py) as below:
https://github.com/huggingface/parler-tts/blob/8b8c576e2dbdc29172e30be7d68fac9357cd92c5/helpers/model_init_scripts/init_dummy_model.py#L27
and
https://github.com/huggingface/parler-tts/blob/8b8c576e2dbdc29172e30be7d68fac9357cd92c5/helpers/model_init_scripts/init_dummy_model.py#L60
Now, I have successfully completed the training as well as the inference process using tiny-model, although the sound quality of the generated audio is a bit poor, but I guess that's a separate issue. Thanks again for your reply and the code.


Add aliases to osx module

Include aliases for lock screen, screencapture, and system volume.
lock brings up the login screen without a full logout.
snap saves a screen shot to current dir following default OS X screen shot naming convention
mute and unmute are essentially identical to pressing the physical mute key, can be changed via any other volume altering function in OS X. I find it useful for (1) not straying too far from the home row and (2) when function keys and fn are remapped to oblivion.
PS - thanks so much for prezto. OMZ performance was killing me.

Please document your additions in the README.

Updated the README with descriptions for each

This seems like a few great additions. Is there something blocking this from being merged in?

@andruby I haven't reviewed it.


🚀 [Feature Request] - Create Blog page for grabtern

Is your feature request related to a problem ? Please describe. ✍

Needs blogs related to grabtern...
This issue can have multiple PRs of level 3.
Creating a simple blog page.
Edit and send the blogs through form.
To fetch blogs from db and json too

Describe briefly how you would implement this enhancement.
mentioned above

Additional context or screenshots
Additional context
Are you contributing for a program?
GSSoC2023
Code of Conduct

[X] I have read and agree to the Contributing Guidelines of this project.

Can you use AI to create blogs.. actually blogs purpose is to increase SEO and revert them on mentor page.

@anmode I want to work on this

Ok, so regarding blog page, Is this design fine for home page?

All blog page toh bn chuka h...bass blog detailed wala design krna h...
Medium Jaisa UI theek h i hope

All blog page toh bn chuka h...bass blog detailed wala design krna h... Medium Jaisa UI theek h i hope

Ok send I will make that, also routes kya hai pages ke woh bhi bhej do


Would you be willing to charge me a monthly fee to "host" Astro Snipcart for me?

I don't want to install Astro Snipcart because I'm neither developer, nor do I want to try to find a developer to deal with the inevitable headaches and hassles associated with ongoing maintenance. (Been there, done that).
In other words, if you want me to be your first customer for a SaaS side hustle which you might not have envisioned creating, please let me know.

Sure?

How much would you charge me per month?


Generate classes even for interfaces that don't declare methods but inherit them

The actual issue with this test is not config (which works fine) but the fact that we skipped CDI subclass generation if the interface didn't declare a method but inherited one.
This fixes the ConfigKeyForMultipleInterfacesTest and gives me the following TCK coverage - Tests run: 155, Failures: 17, Errors: 0, Skipped: 42
Second commit is just a bunch of formatting that I got when building the branch. If you find it too disruptive, I can take it out ;-)

Added a commit that cleans up TCK pom file to silence the enforcer and removes some unused commented out deps.


Failed to parse lesson pages!

I have traced the issue to this

in the upper photo result is always null , that regular expression does not exist.

I am also getting this error!


error on remount if stats plugin is registered

Hey, I don't have a repro for you here yet... but on any component with that "stats" plugin registered, like this component: https://github.com/mentat-collective/mathbox.cljs/blob/1cfdc4891157a728f1974921b0867f718afed84b/dev/mathbox/examples/math/helitorus.cljc#L126
I am getting this error on a re-mount:
Uncaught DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
    at ctor.uninstall (http://localhost:8766/js/cljs-runtime/module$node_modules$threestrap$src$extra$stats.js:3:60)
    at Bootstrap.__uninstall (http://localhost:8766/js/cljs-runtime/module$node_modules$threestrap$src$bootstrap.js:8:276)
    at http://localhost:8766/js/cljs-runtime/module$node_modules$threestrap$src$bootstrap.js:7:253
    at Array.forEach (<anonymous>)
    at Bootstrap.uninstall (http://localhost:8766/js/cljs-runtime/module$node_modules$threestrap$src$bootstrap.js:7:237)
    at Bootstrap.destroy (http://localhost:8766/js/cljs-runtime/module$node_modules$threestrap$src$bootstrap.js:5:264)
    at http://localhost:8766/js/cljs-runtime/module$node_modules$mathbox_react$build$cjs$index.js:33:366
    at safelyCallDestroy (http://localhost:8766/js/cljs-runtime/module$node_modules$react_dom$cjs$react_dom_development.js:488:496)
    at commitHookEffectListUnmount (http://localhost:8766/js/cljs-runtime/module$node_modules$react_dom$cjs$react_dom_development.js:497:424)
    at flushPassiveEffects (http://localhost:8766/js/cljs-runtime/module$node_modules$react_dom$cjs$react_dom_development.js:617:152)
(anonymous) @ react-dom.development.js:22901
callCallback @ react-dom.development.js:4122
invokeGuardedCallbackImpl @ react-dom.development.js:4224
invokeGuardedCallback @ react-dom.development.js:4475
reportUncaughtErrorInDEV @ react-dom.development.js:22898
captureCommitPhaseError @ react-dom.development.js:27152
safelyCallDestroy @ react-dom.development.js:8229
commitHookEffectListUnmount @ react-dom.development.js:23124
flushPassiveEffects @ react-dom.development.js:25084
commitRootImpl @ react-dom.development.js:26978
commitRoot @ react-dom.development.js:26706
performSyncWorkOnRoot @ react-dom.development.js:26146
flushSyncCallbacks @ react-dom.development.js:12113
(anonymous) @ react-dom.development.js:25684

Maybe it's just a Clojurescript thing, but on React 18 pressing the option key seems to remount all components??

This is with the latest rc!

Glad it's not just the newest version... BTW: I expect to be using mathbox-react a lot more in the coming weeks/months. I haven't used in hardly at all until now, but am now starting to add graphics to math3d-next.

This is the issue, of course: https://github.com/unconed/threestrap/blob/master/src/extra/stats.js#L19
I'm too tired now to think through why it's already been removed!

I think this is actually a bug in Threestrap, not a bug in mathbox-react. You'll get the same error if:

Clone https://github.com/unconed/threestrap
Open examples/element_cube
In console, call `three.destroy()

I think mathbox-react exacerbates this issue by making it easier to instantiate threestrap (via mathbox) inside a non-body element.
IMO, the fix is to switch Threestrap from calling Node.removeChild(child) on the parent to calling Element.remove() on the child itself.
removeChild seems like a strictly worse API to me, since it requires a reference to both the parent and the child. My best guess as to why Threestrap is using it is that it seems like remove was introduced in later versions of JS. E.g., ie supports removeChild but not remove... cf

https://caniuse.com/?search=remove
https://caniuse.com/mdn-api_node_removechild

I'll make a PR to threestrap in the next day or two.

@sritchie I appear not to have collaborator status on Threestrap, so I can't actually request your reviews, but PRs are up to address this. I didn't realize the tests over there were broken... I'll look into that next.
https://github.com/unconed/threestrap/pulls
Probably after the holidays I will email Steven and ask for collaborator status.

I'll make a note to ask Steven!
On Thu, Dec 22, 2022, at 9:42 PM, Chris Chudzicki wrote:

@sritchie https://github.com/sritchie I appear not to have collaborator status on Threestrap, so I can't actually request your reviews, but PRs are up to address this. I didn't realize the tests over there were broken... I'll look into that next.
https://github.com/unconed/threestrap/pulls
Probably after the holidays I will email Steven and ask for collaborator status.
—
Reply to this email directly, view it on GitHub https://github.com/ChristopherChudzicki/mathbox-react/issues/202#issuecomment-1363557669, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAARAAZURQCZCX4SF7LWMVDWOUGS5ANCNFSM6AAAAAATFDIMVY.
You are receiving this because you were mentioned.Message ID: @.***>

Closing since we've covered this in threestrap.


Fix add-event dialog console warnings

Fixes a "missing key prop" and an "invalid prop type" error by adding that key and changing the prop type.
Not sure what to do about the missing i18next keys though.
Closes #550

Not sure what to do about the missing i18next keys though.

That's a task for another issue/pull request because the i18next::translator: missingKey en-US translation <empty string> <empty string> 2 i18next.js:13:48 messages are all over the place and not limited to the add-event dialogue.


java install failed

on Ubuntu 16.04.3 LTS run following command failed
sudo apt-get install oracle-java8-installer -y java -version
result is:
apt 1.2.29 (amd64) Supported modules:  Ver: Standard .deb  Pkg:  Debian dpkg interface (Priority 30)  Pkg:  Debian APT solver interface (Priority -1000)  S.L: 'deb' Debian binary tree  S.L: 'deb-src' Debian source tree  Idx: Debian Source Index  Idx: Debian Package Index  Idx: Debian Translation Index  Idx: Debian dpkg status file  Idx: Debian deb file  Idx: Debian dsc file  Idx: Debian control file  Idx: EDSP scenario file E: Command line option 'e' [from -version] is not understood in combination with the other options.

@flyonok  is it for elastic search? It's better you run elasticsearch with docker. The current documentation is created for ubuntu 18.04
try https://hub.docker.com/_/elasticsearch

@ashwin31 ok，thanks.


bug: insert with empty payload hana, will not execute valid SQL

end with VALUES

Insert record with in-existed table, no error raised

hdb dirver throw object instead of error


Add disclaimers and restrictions to index and detail views

We need to communicate restrictions like (don't really need to cover all, but most would be good):

only works for Stripe accounts in MY
only works with X and Y currencies
only works for X currencies on Stripe accounts in X countries
only works with https
only works with specific MCC

X

X

X

X

Payment

#323

#323

ch_3KtgKtFc7yM6jura1Kl3oAhG

https://github.com/stripe-samples/accept-a-payment/issues/2#issuecomment-903539623

#1042

Duplicate of #


fix(geometry): fix error multi geometry

fix: sub geometry can't be render success.
fix: normal of planeZ

is this ready?


Clarify meaning of training parameter in XGBoosterPredict()

fixes #5601 . Pre-empts questions about the breaking API change for v1.1.0 that downstream maintainers will have.

@glycerine I simplified the explanation in the docstring. Can you review and see if it makes sense to you?

@hcho3 LGTM. Thanks for adding the clarification about custom objectives.

This way the parameter is general enough to be reused in the future instead of being a dart only parameter.

@trivialfis Can you suggest a good way to document the meaning of training for people who use the C API function? Right now, it is not clear when training parameter should be set to 1.

 * \param training Whether the prediction function is used as part of a training loop.
 *    If you are running prediction on a model that's finished training, set `training` to false.

How about this?

YAGNI applies. I would say don't document it as general-purpose until it actual is. It is already used here in R in the general sense, even when DART may not be used.
https://github.com/dmlc/xgboost/blob/master/R-package/R/utils.R#L148
Is there harm is setting to true when not under DART?

Maybe we can give dart as an example.

If you are running prediction on a model that's finished training, set training to false.

A little too sparse. I would want a little more guidance about when it is okay to set it to true.

@glycerine How about this, if the prediction result is used for calculating gradient for training, set it to true, otherwise set it to false.

Also, it's a breaking change in 1.0.0.

* \param training Whether the prediction function is used as part of a training loop.
*    1. If you are running prediction on a model that's finished training, set training=false.
*    2. When should you set training=true?
*       Normally, you don't need to use XGBoosterPredict() in your training loop, since you are
*       probably using XGBoosterUpdateOneIter(), which calls XGBoosterPredict() internally. The one
*       case you should use XGBoosterPredict() in your training loop is when you wrote a customized
*       objective. In this case, call XGBoosterPredict() with training=true and then invoke your
*       customized objective fobj(predicted_label, true_label) to obtain the gradient pairs.

I tried elaborating the design behind the training parameter.

* \param training Whether the prediction function is used as part of a training loop.
*    1. If you are running prediction on a model that's finished training, set training=false.
*    2. When should you set training=true?
*       Normally, you don't need to use XGBoosterPredict() in your training loop, since you are
*       probably using XGBoosterUpdateOneIter(), which calls XGBoosterPredict() internally. The one
*       case you should use XGBoosterPredict() in your training loop is when you wrote a customized
*       objective. In this case, call XGBoosterPredict() with training=true and then invoke your
*       customized objective fobj(predicted_label, true_label) to obtain the gradient pairs.

@hcho3 I like it. Very clear and helpful.

If you are running prediction on a model that's finished training, set training=false.

I would omit this item.  We do prediction during training to use external metrics.

I would omit this item. We do prediction during training to use external metrics.

@trivialfis That is the most important piece of guidance. Without that, we are lost.
You really must describe detail when to set it true, and when to set it false. Give examples. Be precise. Without the line above, it is far too vague, and you will get tons of questions.

* \param training Whether the prediction function is used as part of a training loop.
*    When should you set training=true? Set training=true if 1) you are writing your training loop
*    and 2) you are using a customized objective function to obtain gradient pairs.
*    Normally, you don't need to use XGBoosterPredict() in your training loop, since you are
*    probably using XGBoosterUpdateOneIter(), which calls XGBoosterPredict() internally. The one
*    case you should use XGBoosterPredict() in your training loop is when you wrote a customized
*    objective. In this case, call XGBoosterPredict() with training=true and then invoke your
*    customized objective fobj(predicted_label, true_label) to obtain the gradient pairs.

great. This is good in that it give guidance about when to use training=true.
It would also be good to add what change happens when you set training true, and that shows the intent. I'm guessing it has to do with dropout or not, as one example.

Prediction can be run in 2 scenarios:

Normal model inference, given a X, obtain the y_p from model.
Obtain the prediction for computing gradients.  For example dart booster performs dropout during training, and the prediction result will be different from the one obtained by normal inference step.

The training parameter is used to distinguish these 2 scenarios.  Set to false for the first scenario and true for the second one.

@trivialfis Excellent.


version info error

I upgraded my phpbrew to v1.0.2, but the version info is CLIFramework:
# phpbrew --version
CLIFramework - 0
cliframework core: 1.1.1

oops

fixed. ;-)


GH-34698: [C++][Acero] Add node that emits explicit ordering after asserting order

Rationale for this change
An acero node that turns an implicit ordering into an explicit ordering (rows sorted by some columns) is useful to re-use order that already exists in the data.
What changes are included in this PR?
This PR adds the AssertOrderNode that implements this logic. The Scanner employs that node to turn the implicit ordering of the ScanNode into an explicit order as defined by user code via ScanBuilder.Ordering.
Are these changes tested?
There are unit tests for the AssertOrderNode as well as for the ScanNode and ScanBuilder.
Are there any user-facing changes?
The following options has been added:

the ordering option added to ScanOptions
the Ordering option added to ScannerBuilder
the AssertNodeOptions class

GitHub Issue: #34698

@raulcd thanks, assertions adjusted


[Issue #88] feat: automatic detect payments

Description:
Solves #88. Creates #346.
Addresses are now subscribed when they are added, such that if a new transactions appears on any address, it is automatically added to the DB.
Test plan:
After building, create a paybutton with of your addresses. Then, using Electrum ABC or any other XEC wallet, transfer some small quantity to that address. After the transaction is confirmed, it should appear on  the button detail. Same thing with Bitcoin Cash.
Depends on:

[x] #342

Ok it seems to not work on particular addresses... maybe just addresses that have been used already?

Works for me.
It would be nice if there was some sort of user feedback to let a user know that its syncing. Initially I thought it didn't work but I was just being impatient


Docker-based build environment (to build checkmake binary)

In https://github.com/mrtazz/checkmake/issues/28 we learned that is maybe helpful to have a docker-based build environment available for users that are interested in a fresh checkmake binary but still want to keep the host system free from build dependencies.
This PR adds a build environment (docker-based) to the project.
BTW: i hope to see more frequent releases of binary files here: https://github.com/mrtazz/checkmake/releases.

This is interesting. Thanks for taking the time to contribute. I kinda don't like that the resulting binary has an empty BUILDER field in the version string. Would you be up for changing this Makefile line to be ?= so we can set the BUILDER env var from outside. And then update the README to reflect being able to pass the env var e.g.
docker run BUILDER=docker-builder --rm -v $(pwd):/data --workdir /data checkmake/buildenv:latest make

thanks for the contribution!


Mobile key don't appears on signing

Mobile key don't appears on signing. it was 2 of 3
https://github.com/bithyve/bitcoin-keeper/assets/107177634/bae8cd23-3536-43bb-95be-30a8c2b4d5f5

Completed


Feat: add moralis integration

This PR introduces the integration of Moralis Web3 APIs into TurboETH. The integration provides a range of API routes, React hooks, and components, leveraging the Moralis Transaction and Events APIs. It facilitates the building of Web3 apps with rich, multi-chain data.

@marthendalnunes can we add an API key for the staging environment too?

@kamescg the API key was already set for all the environments, probably you were looking at a stale preview deploy, this is the right one https://turbo-5frrmm8ob-district-labs.vercel.app/integration/moralis/transaction


BK Feedback

mission/vision phil/scarlett feedback intent

swap

portfolios for firefighting

technical advice for phone a nerd

more white space for body copy, paragraph

form: "Product Management and something long"

more photos (see roro)

About Us, under "values":
We refer to the DoD in 3 different ways (Department, DoD, etc.)
"Signal intent" isn't clear.
Our Work:
"Using design and technology to improve government services, strengthen national defense, and care for military members and their families." is not a complete sentence.
"Engagement Categories" is spelled wrong.
Should have the numbers of the Categories also bold.
The Categories are not totally accurate. Portfolios, Projects, Firefighting, Technical Advice, Discovery Sprints. I could see leaving out Discovery Sprints as it folds into either projects or technical advice, but our Firefighting should be in there. MySymptoms.mil goes in that category
The text is weird when you go to the sub-page of the Engagement Categories.
Our Team:
Missing "s" after contractors.
Media
Think you can just say "News" instead of "DDS in the news"

swap

portfolios for firefighting (fixed, but now where do we put Hack the Pentagon?? still will need to update copy in this section once I receive the deck link that was discussed on the call)
technical advice for phone a nerd (fixed)
more white space for body copy, paragraph (I think this is a Jeff thing, not a Rachel thing)

About Us, under "values":

We refer to the DoD in 3 different ways (Department, DoD, etc.) (fixed)
"Signal intent" isn't clear. (I don't know what the request/edit is here. Signal intent is listed in one of the values already.)

Our Work:

"Using design and technology to improve government services, strengthen national defense, and care for military members and their families." is not a complete sentence. (fixed)
"Engagement Categories" is spelled wrong. (fixed)
Should have the numbers of the Categories also bold. (I think this is a CMS/Jeff thing; not a Rachel thing)
The Categories are not totally accurate. Portfolios, Projects, Firefighting, Technical Advice, Discovery Sprints. I could see leaving out Discovery Sprints as it folds into either projects or technical advice, but our Firefighting should be in there. MySymptoms.mil goes in that category (fixed per the first list of items in this comment)
The text is weird when you go to the sub-page of the Engagement Categories. (Think this is a Jeff thing not Rachel thing, I don't see any major issues with the text on my end)

Our Team:

Missing "s" after contractors. (fixed)

Media

Think you can just say "News" instead of "DDS in the news" (fixed, though looks like someone did it before I got in there)

@jhackshaw-dds for all the changes to the pages under Our Work, I think we'll need to change the redirect links too (the ones that look like this: /work/portfolios). I've changed the titles via CMS copy, but are you able to manage all the updates to redirect pages, etc.? I don't want to mess that up. Should be Firefighting, Projects, and Phone A Friend.

@racheldds Let me know if it looks alright the way it is now, it's easy for me to change too. I changed to:
/work/fire-fighting
/work/phone-a-friend
/work/projects

Looks perfect, thanks @jhackshaw-dds.


Update dockerfile

Add launching of multinode server.
Add selection of server type in entrypoint.

Issue moved to bwsw/t-streams #702


Switch to web socket-based StreamingClientDAOs

This is towards performance improvements for "cold boot" of web UI.
The plan is, roughly:

Use DAOs that can stream individual entities;
Use a worker to populate IndexedDB in the background
Update Angular components make more targeted queries (for "current page") against caching DAO

Codecov Report

Merging #82 into master will increase coverage by 0.13%.
The diff coverage is 11.11%.

@@            Coverage Diff             @@
##           master      #82      +/-   ##
==========================================
+ Coverage   68.31%   68.44%   +0.13%
==========================================
  Files          30       31       +1
  Lines        1477     1477
  Branches      108      108
==========================================
+ Hits         1009     1011       +2
+ Misses        468      466       -2

Impacted Files
Coverage Δ

lib/dao_container.es6.js
100% <ø> (ø)
:arrow_up:

lib/datastore/datastore_container.es6.js
15.9% <ø> (+0.69%)
:arrow_up:

lib/client/api_service.es6.js
23.33% <0%> (ø)
:arrow_up:

lib/controller/default.es6.js
100% <100%> (ø)

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 77cb49f...41a4887. Read the comment docs.


Vista cue with decimal point does not work.

I ran into an issue this past Sunday that was new. We had a Vista cue with a decimal point, for example 1.5 and it would not work. In ProPresenter stage notes, I entered "Vista: 2, 1.5;" (for example) and Presentation Bridge Client did not pick it up. I renamed the queue to a whole number and updated stage notes and it worked. So, is there an issue with cues with decimal points? Not a huge deal. I can get around it, but wanted to report it.

Version 1.0.14 published which should allow decimal point in parameters


Trivy Parser Does Not Parse file_path Correctly

Bug description
Trivy parser does not parse the file_path appropriately, thus it will always be empty. It tries to get the "PkgPath" parameter which does not exist in trivy result. Below is the problematic code (dojo/tools/trivy/parser.py)

Steps to reproduce
Steps to reproduce the behavior:

Import a trivy scan result (with lang-pkgs vulnerabilities)
Check on the database, table dojo_finding column file_path (it is always empty)

Expected behavior
When the "Class" of the trivy result is "lang-pkgs", obtain the file_path value from "Target" parameter.
Here is a sample trivy result with "lang-pkgs" vulnerabilities
{
  "SchemaVersion": 2,
  "ArtifactName": "sbom.json",
  "ArtifactType": "cyclonedx",
  "Metadata": {
    "ImageConfig": {
      "architecture": "",
      "created": "0001-01-01T00:00:00Z",
      "os": "",
      "rootfs": {
        "type": "",
        "diff_ids": null
      },
      "config": {}
    }
  },
  "Results": [
    {
      "Target": "requirements.txt",
      "Class": "lang-pkgs",
      "Type": "pip",
      "Vulnerabilities": [
        {
          "VulnerabilityID": "CVE-2023-37920",
          "PkgName": "certifi",
          "InstalledVersion": "2<IP_ADDRESS>",
          "FixedVersion": "2023.7.22",
          "Layer": {},
          "SeveritySource": "ghsa",
          "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2023-37920",
          "Ref"<EMAIL_ADDRESS>          "DataSource": {
            "ID": "ghsa",
            "Name": "GitHub Security Advisory pip",
            "URL": "https://github.com/advisories?query=type%3Areviewed+ecosystem%3Apip"
          },
          "Title": "python-certifi: Removal of e-Tugra root certificate",
          "Description": "Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi prior to version 2023.07.22 recognizes \"e-Tugra\" root certificates. e-Tugra's root certificates were subject to an investigation prompted by reporting of security issues in their systems. Certifi 2023.07.22 removes root certificates from \"e-Tugra\" from the root store.",
          "Severity": "HIGH",
          "CweIDs": [
            "CWE-345"
          ],
          "CVSS": {
            "ghsa": {
              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
              "V3Score": 7.5
            },
            "nvd": {
              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
              "V3Score": 9.8
            },
            "redhat": {
              "V3Vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
              "V3Score": 7.5
            }
          },
          "References": [
            "https://access.redhat.com/security/cve/CVE-2023-37920",
            "https://github.com/certifi/python-certifi",
            "https://github.com/certifi/python-certifi/commit/8fb96ed81f71e7097ed11bc4d9b19afd7ea5c909",
            "https://github.com/certifi/python-certifi/security/advisories/GHSA-xqr8-7jwr-rhp7",
            "https://github.com/pypa/advisory-database/tree/main/vulns/certifi/PYSEC-2023-135.yaml",
            "https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/C-HrP1SEq1A",
<EMAIL_ADDRESS>            "https://nvd.nist.gov/vuln/detail/CVE-2023-37920",
            "https://www.cve.org/CVERecord?id=CVE-2023-37920"
          ],
          "PublishedDate": "2023-07-25T21:15:00Z",
          "LastModifiedDate": "2023-08-12T06:16:00Z"
        }
      ]
    }
  ]
}

Deployment method (select with an X)

[x] Docker Compose
[ ] Kubernetes
[ ] GoDojo

Environment information

Operating System: Ubuntu 20.04
DefectDojo version (see footer) or commit message: v. 2.24.4 ( release mode )

Done, can be closed


pkgsStatic.perl: fix build

Motivation for this change
I don't understand how this worked prior to 1dbb306 ("pkgsStatic.perl: Use `dontAddStaticConfigureFlags` instead of overriding"), but what I do know is that it's very broken now, to the point that perl-cross needs a patch.
I doubt the -Duseshrplib is actually necessary when native compiling, but removing it would be a mass rebuild, so I've left it in place for now.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages 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 (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

pkgsCross.aarch64-multiplatform.perl failed:
Running Mkbootstrap for B ()
Can't locate DynaLoader.pm in @INC (you may need to install the DynaLoader module) (@INC contains: /build/perl-5.34.0/cnf/stub /build/perl-5.34.0/cnf/cpan /build/perl-5.34.0/cpan/AutoLoader/lib /build/perl-5.34.0/dist/Exporter/lib /build/perl-5.34.0/dist/Cwd /build/perl-5.34.0/dist/Cwd/lib /build/perl-5.34.0/cpan/ExtUtils-Command/lib /build/perl-5.34.0/cpan/ExtUtils-Install/lib /build/perl-5.34.0/cpan/ExtUtils-MakeMaker/lib /build/perl-5.34.0/dist/ExtUtils-MakeMaker/lib /build/perl-5.34.0/cpan/ExtUtils-Manifest/lib /build/perl-5.34.0/cpan/File-Path/lib /build/perl-5.34.0/cpan/Pod-Simple/lib /build/perl-5.34.0/cpan/Pod-Escapes/lib /build/perl-5.34.0/ext/File-Find/lib /build/perl-5.34.0/ext/re /build/perl-5.34.0/cpan/ExtUtils-Constant/lib /build/perl-5.34.0/dist/ExtUtils-ParseXS/lib /build/perl-5.34.0/dist/constant/lib /build/perl-5.34.0/cpan/Getopt-Long/lib /build/perl-5.34.0/cpan/Text-Tabs/lib /build/perl-5.34.0/dist/Carp/lib /build/perl-5.34.0/cpan/podlators/lib /build/perl-5.34.0/cpan/parent/lib /build/perl-5.34.0/cpan/version/lib /build/perl-5.34.0/dist/Pod-Simple/lib /build/perl-5.34.0/dist/if /build/perl-5.34.0/lib ../../lib .) at /build/perl-5.34.0/cpan/ExtUtils-MakeMaker/lib/ExtUtils/Mkbootstrap.pm line 28.
make[2]: *** [Makefile:451: B.bs] Error 2
make[2]: Leaving directory '/build/perl-5.34.0/ext/B'
make[1]: *** [Makefile:235: ext/B/pm_to_blib] Error 2
make[1]: Leaving directory '/build/perl-5.34.0'
make: *** [Makefile:81: all] Error 2
builder for '/nix/store/vl4fy433w7fmnk1vdsfw2r3933dxpxda-perl-5.34.0-aarch64-unknown-linux-gnu.drv' failed with exit code 2
error: build of '/nix/store/vl4fy433w7fmnk1vdsfw2r3933dxpxda-perl-5.34.0-aarch64-unknown-linux-gnu.drv' failed

@OfBorg build pkgsStatic.perl pkgsStatic.aarch64-multiplatform.perl


/openmp:llvm - Documentation does not list all supported platforms.

The documentation says:

Currently, the /openmp:llvm option only works on the x64 architecture.

However, according the the Microsoft Blog support for x86 and arm64 platform has already been added in 2021.
I think, the documentation should be fixed to reflect the correct state of development.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 6c23f71d-4fe6-e91a-2331-900bc86f78b1
Version Independent ID: 37bcd3b7-8072-c6b7-4da1-97258dc85883
Content: /openmp (Enable OpenMP Support)
Content Source: docs/build/reference/openmp-enable-openmp-2-0-support.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

@exo-dbahadir , thank  you for catching this. I've updated the doc. It should be live tomorrow afternoon.


Can't build current commit on master

Having the following error while using nix build:
http://ix.io/3Ij2
Reverting commit 107cb2285f10a0a5daddd4995516efede96bdbe3 works fine.

I think the issue is that the current flake.lock is too old. Updating nixpkgs seems to work fine.

fixed in https://github.com/Mic92/nixpkgs-review/pull/241


The ReplyLength size documentation of FltSendMessage  is wrong

The documentation for FltSendMessage calls for the ReplyLength to be sizeof(FILTER_REPLY_HEADER) + sizeof(MY_STRUCT)
See below.
Therefore, it is recommended that you call FilterReplyMessage and FltSendMessage (leveraging the above example) by setting dwReplyBufferSize and ReplyLength both to sizeof(FILTER_REPLY_HEADER) + sizeof(MY_STRUCT) instead of sizeof(REPLY_STRUCT).
But the scanner sample sets it to sizeof(MY_STRUCT)
Refer
https://github.com/microsoft/Windows-driver-samples/blob/main/filesys/miniFilter/scanner/filter/scanner.c#L1327
I think doc is wrong.
Sri
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f6f940ae-4ddf-0e73-6607-32522f6ac5b7
Version Independent ID: 20dfb40f-9d20-2d7b-9d81-4423eb0973de
Content: FltSendMessage function (fltkernel.h) - Windows drivers
Content Source: wdk-ddi-src/content/fltkernel/nf-fltkernel-fltsendmessage.md
Product: windows-hardware
Technology: wdk-api-reference
GitHub Login: @lorihollasch
Microsoft Alias: loriwhip

Thanks for the issue, @sri-mabelsoftware. The docs actually are correct as written. Note that setting dwReplyBufferSize and ReplyLength to sizeof(FILTER_REPLY_HEADER) + sizeof(MY_STRUCT) instead of sizeof(REPLY_STRUCT) is the recommendation for robustness (and not a requirement).

You missed my noting - the size needs to be neither the sizeof(FILTER_REPLY_HEADER) + sizeof(MY_STRUCT) nor the sizeof(REPLY_STRUCT) - these two sizes could be obviously different and cause robustness issue. It should just be sizeof(MY_STRUCT) - i.e. dwReplyBufferSize does NOT need to include the header size of sizeof(FILTER_REPLY_HEADER) as per scanner sample.


Add Kaomoji.app

[x] Checked there aren’t open pull requests for the same cask.
[x] Checked there aren’t closed issues where that cask was already refused.
[x] When naming the cask, followed the token reference.
[x] Commit message includes cask’s name.
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.

Thank you for the contribution. It was merged directly as fe42bc2609edb26e7fe8566d52e583675ea3d927 to keep commit history cleaner. Your contribution is still credited to you.


[bug]the windows title bar button can not be removed or disabled, or window can not be maximized as configured.

Describe the bug

button is like above,
config like following:
"resizable": false,
"maximized":true,
"width":1024,
"height":768,
"decorations":true
when button clicked, window becomes 1024*768, click again, restore to maximized.
Reproduction
No response
Expected behavior
window should kept maximized whenever button clicked or not
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 126.0.2592.113
    ✔ MSVC:
        - Visual Studio Community 2019
        - Visual Studio Community 2022
    ✔ rustc: 1.82.0-nightly (28a58f2fa 2024-07-31)
    ✔ cargo: 1.82.0-nightly (257b72b8a 2024-07-30)
    ✔ rustup: 1.24.3 (ce5817a94 2021-05-31)
    ✔ Rust toolchain: nightly-x86_64-pc-windows-msvc (environment override by RUSTUP_TOOLCHAIN)
    - node: 18.0.0
    - npm: 9.6.6

[-] Packages
    - tauri [RUST]: 2.0.0-beta.22
    - tauri-build [RUST]: 2.0.0-beta.17
    - wry [RUST]: 0.40.1
    - tao [RUST]: 0.28.1
    - tauri-cli [RUST]: 2.0.0-beta.21
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 2.0.0-beta.21

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1422/

Stack trace
no

Additional context
No response

if you want to disable clicking on the mouse button, set maximizable: false

a

this was removed in https://github.com/tauri-apps/tao/pull/749


Bug 2211592: [release-4.12] Always update the template parameters & objects to keep it up-to-date

Previously once the template existed we were not reconciling it. This resulted in the template using very old rook-ceph images and not having the newly added parameters. We want the template to be updated to use new parameters, any new ceph commands, latest rook-ceph image, etc. Trying to update the whole template object also doesn't work. So we need to update the parameters & objects separately to keep the template up-to-date.
/hold

/bugzilla refresh

/bugzilla refresh

/unhold
/bugzilla refresh
/cc @iamniting


[PE-D][Tester E] Attendance parameter in mark command differs from UG specification

The user guide states that the Attendance parameter of mark command is case sensitive, however that is not the case.

For instance, the command
mark 1 d/20/02/2025 08:00 m/absent
works the same as
mark 1 d/20/02/2025 08:00 m/Absent

Labels: type.DocumentationBug severity.Medium
original: tanwartushar/ped#4

@izruff can you help rectify the Ug for this

Duplicate of #256


moltengamepad-git: init at 2016-05-04

@fpletz Ah, yes. That is correct. Fixed. (∩_∩)

Thanks!
Travis fail is unrelated and fixed f0f31a256f833f124d3af2433e46431e547a3fb2.

@fpletz thanks! (｡◝‿◜｡)


Updating to Swift 3.0.2

A few things missing: 1) The travis.yml file needs to be updated to 'osx_image: xcode8.2'. Then we should make sure that the xcode build on travis works and no warnings are thrown when compiling the iOS app; 2) The README should be updated accordingly, from "iOS App | Xcode 8 default (Swift 3.0.2)" to "iOS App | Xcode 8.2 default (Swift 3.0.2)".


Remove unused ProxyInput

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@804270b). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #6657   +/-   ##
=========================================
  Coverage          ?   82.99%
  Complexity        ?    13380
=========================================
  Files             ?     1524
  Lines             ?    49636
  Branches          ?     5922
=========================================
  Hits              ?    41197
  Misses            ?     5626
  Partials          ?     2813

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 804270b...6cce294. Read the comment docs.


Full Static Control (Except Invoke) Inlining & Compilation

Adds static seq, par, if, and repeat support, in addition to static enable!
Currently, it inlines each of these four different control operators into a single static group in the static-inline pass, and then the compile-static pass 1) instantiates FSMs so that these inlined static groups get turned into dynamic groups with "early-resetting" FSMs that never reach the group's done condition, and 2) creates wrapper groups for these "early reseting" groups when necessary (i.e., when they need to use a go-done interface).
For the correctness test cases, it passes the same test cases as the tdst pass did (only difference is that it doesn't infer static control yet, but we adding that support rn) . I also added another case that compiles a "static island" within dynamic control just to demonstrate that we can do that as well.
A Couple Notes:

Because of the recursive nature of the static-inlining pass, it ends up creating a bunch of unnecessary timing guards for nested control statements (e.g., %3 & %[2:4] & %[0:5], which is really just %3). I'll write up an issue on this... ideally, we want some sort of simplify-guards pass that can handle this separately.
StaticInvoke support is still a to-do (#1417).

When merged, should close #1406,. After this, we can also delete merge-static-par and static-par-conv as these passes no longer really do anything.

Great! I don't have time to review this yet but make sure that the programs take exactly the same amount of time (in number of cycles) as the tdst programs did. The "dynamic island" test is a great idea and something I wanted to do with the OG tdst pass but it couldn't support it. Great to see it become a reality.
Also, I mentioned in #1419, we should have a new alias for the compilation pipeline that uses the new static powered passes and eventually remove all the old crud.

Just changed the frontend so that latencies don't have to be explicitly given in the control. I still allow it optionally though.
You're completely right, not sure why I was doing it like that. Fixed now.
Yep. In fact, there's this one method on Guard called add_interval(self, (beg, end)) that basically just changes self -> self & (beg, end). I can probably change it to look thru self first to see if (beg, end) will be redundant, and then just not change anything if it will obviously be redundant.

Also, I'll look thru the minor reviews u made and update accordingly as well.

Making a strong argument for hashconsing the guard expressions!

Another drive-by thought: worth making sure that the following two cases work:

Loop with 1-cycle body
Doubly nested loop with 1-cycle body

I'll come by and take another look but if you're confident things work, then merge it! Once #1419 is merged, we should run the inlining pass on the Dahlia benchmarks from the evaluation repository since those are a good test case for all of this stuff. Alternatively, if you're feeling adventurous, you can change the Dahlia frontend to generate static group instead of the annotated stuff (on a branch) and see if any of the polybench benchmarks fail

Ok, I added a test case for nested loop w/ one cycle body! I think I'm gonna merge since it'll be easier for @paili0628 to make progress on some of her work if we merge sooner rather than later.


Release notes in editor not updating

My version of Atom is up to date but the release notes page is stuck on an older version and keeps showing the "restart and update" button which closes Atom but doesn't restart the editor and the button doesn't disappear.

Thanks for the report! This is a duplicate of https://github.com/atom/release-notes/39 - please subscribe there for updates.
Also, please take a look at the Contributing guide for a guide on submitting bug reports (including searching for duplicates first).

Ah, thanks, I didn't see that


import error with docker

hi,  thanks for publishing this cool packages.
But, I am having issue with CSF module not being found in the docker image of segment-lidar.
`fw@w-Crosshair-15-A11UCK:~/lidar_segmentation$ docker ps
CONTAINER ID   IMAGE                    COMMAND                  CREATED             STATUS             PORTS     NAMES
01cf113224e7   yarroudh/segment-lidar   "python -c 'while Tr…"   About an hour ago   Up About an hour             priceless_wu
w@w-Crosshair-15-A11UCK:~/lidar_segmentation$ docker exec 01cf113224e7 python segment.py
Traceback (most recent call last):
File "segment.py", line 1, in
from segment_lidar import samlidar, view
File "/opt/conda/lib/python3.8/site-packages/segment_lidar/samlidar.py", line 6, in
import CSF
ModuleNotFoundError: No module named 'CSF'
`
I also  installed CSF inside the docker, but still CSF is not found.

Hello @wendwosenbb,
Thanks for reporting this error. The docker image should be updated. I encourage you to install the package on a local environment. Once updated, I will inform you here.


Add how to troubleshoot skipped but required checks

Why:
Closes #8926

What's being changed:

This adds a troubleshooting guide as to how to handle skipped but required checks on a PR.
Check off the following:

[x] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[x] For content changes, I have completed the self-review checklist.

@thispsj Thanks so much for opening a PR! I'll get this triaged for review :zap:

https://github.com/github/docs/projects/1#card-70814394

https://github.com/github/docs/projects/1#card-70814394

ok

Replacement screenshots
Please save this as pr-required-check-skipped.png:

Please save this as pr-required-check-passed-using-generic.png:

@thispsj - Thanks for the changes.
Merging this now.

Now live: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks
🎉

Unless I'm missing something this solution seems incomplete.  Say two files change, for example: "scripts/foo" and "README.md".  Wouldn't both actions trigger and then the required check would falsely get marked successful?

Unless I'm missing something this solution seems incomplete. Say two files change, for example: "scripts/foo" and "README.md". Wouldn't both actions trigger and then the required check would falsely get marked successful?

@steve21168 a good question indeed !
It's very simple to answer that : Both the workflows will run as required when there are changes to items in the required path and also to items out of the required path.
I have also created a practical demo for you which you can see here
If you don't understand any specific thing, don't hesitate to ping me and ask it here.

Unless I'm missing something this solution seems incomplete. Say two files change, for example: "scripts/foo" and "README.md". Wouldn't both actions trigger and then the required check would falsely get marked successful?

@steve21168 a good question indeed ! It's very simple to answer that : Both the workflows will run as required when there are changes to items in the required path and also to items out of the required path.
I have also created a practical demo for you which you can see here.
If you don't understand any specific thing, don't hesitate to ping me and ask it here.

Yes so in your demo both of your "ci/build" Github actions ran - in your example you can see there are two "ci/build" checks .  What you want to happen is to only have the one real "ci" run.
The issue with both actions running is that the build which skips everything will pass very quickly and the status check will be marked a success making the PR mergable.  The real "ci/build" may still be running at this time.

Unless I'm missing something this solution seems incomplete. Say two files change, for example: "scripts/foo" and "README.md". Wouldn't both actions trigger and then the required check would falsely get marked successful?

@steve21168 a good question indeed ! It's very simple to answer that : Both the workflows will run as required when there are changes to items in the required path and also to items out of the required path.
I have also created a practical demo for you which you can see here.
If you don't understand any specific thing, don't hesitate to ping me and ask it here.

Yes so in your demo both of your "ci/build" Github actions ran - in your example you can see there are two "ci/build" checks . What you want to happen is to only have the one real "ci" run.
The issue with both actions running is that the build which skips everything will pass very quickly and the status check will be marked a success making the PR mergable. The real "ci/build" may still be running at this time.

@steve21168 you're partially correct.
It's true that the generic check will pass very quickly. But this will not make the PR mergable.
This is because both the real & generic checks run as required. You can see that in the screenshot below :

@steve21168 for your doubt I added a delay in the real build using sleep and then added a commit to the PR branch and now you can clearly see what I was trying to convey :

Also if you are still confused, why not open a PR on my repo and see it happen yourself.

@thispsj Thank you for the time an effort you put into this.  In my scenario the required check is a dependency of an earlier job.  Until the earlier job finishes I only see the one check which is the bypassing check.  See the scenario setup here: https://github.com/thispsj-lab/pr-actions/pull/16

Ya it's like that on your side. On my side it show 2 workflows awaiting approval. See :

If you're still online put a like here and I will approve the workflows to run so that you can see that live.

@steve21168 and the logic behind it showing one check is because of branch protection rules where I've define only one check but when you approve it two workflows will run.

@steve21168 also you've changed the name of job it's not the same. So it'll not show as required.

@steve21168 open another PR without changing name and you'll realise.

Yes

@steve21168 and the logic behind it showing one check is because of branch protection rules where I've define only one check but when you approve it two workflows will run.

Yes both workflows run - but the branch protection check would be falsely marked successful b/c you have a job that just goes straight to success - defeating the purpose of the branch protection.  The second workflow may eventually mark the required check as failed but there could be a long period where it is marked successful.
@thispsj Thank you for your time.

I have not changed the name they are both "ci/build" I just put a step before to show that until it gets there the build would be mergeable since the first "ci/build" was successful and the second "ci/build" has yet to appear.
Now that both jobs have caught up you can see the two required "ci/build" checks.. But until "slow-job" finished the build had one successful "ci/build" check and was therefore mergeable.

Ahh I got it when the real build job is invoked directly (i.e. without depending on another job) this fix in GitHub Docs would work perfectly because the real build job would start along with the generic one. But when real build job is dependent on another job, the PR will show as mergable till the job on which build is dependent is completed. Perfect ! Looks like you've found something new to add to this document.

@thispsj You can go for it - I'm sure the community will appreciate it.

@steve21168 Thanks !
Had a great time conversing with you. Definitely improvised my knowledge about GitHub Actions.

I have not changed the name they are both "ci/build" I just put a step before to show that until it gets there the build would be mergeable since the first "ci/build" was successful and the second "ci/build" has yet to appear.
Now that both jobs have caught up you can see the two required "ci/build" checks.. But until "slow-job" finished the build had one successful "ci/build" check and was therefore mergeable.

@steve21168 Ahh I got it when the real build job is invoked directly (i.e. without depending on another job) this fix in GitHub Docs would work perfectly because the real build job would start along with the generic one. But when real build job is dependent on another job, the PR will show as mergable till the job on which build is dependent is completed. Perfect ! Looks like you've found something new to add to this document.

I now this thread is more than one year old, but I just stumbled over the same issue and would suggest the following solution: Couldn't you just make the dummy build-job dependent on the same job as the real build-job? Then both build-jobs (dummy and real) should again start at the same time and there shouldn't be a time window where the dummy job finished successfully while the real job still didn't started and hence there shouldn't be any time window where the PR is mergable although the real build-job hasn't started yet.


ThreadLocal add initial value

Fixes #ISSUSE_ID.
Changes proposed in this pull request:

Can you resolve the conflict first?


Fix reading from config file of argparse.boolean optional action

This fix the reading from config file of argparse.boolean optional action (see #245).

Hello @bw2, what do you think about my PR? I am using this implementation in my projects and I will like to have it in the basecode. Let me. Thanks!

Thanks for the PR @ftesser !


add support for explicit NodePort on jenkins chart

Please bump the chart version.

@dannydavidson please rebase to resolve the conflicts


Metro server not reachable when integrating with existing app

Description
Following the steps in https://reactnative.dev/docs/integration-with-existing-apps to integrate React Native with existing apps doesn't work. Either it's missing steps or outdated.
Issue 1: Crash with "java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so"
Issue 2: Unable to connect to Metro server even when it is already running.
React Native version:
$ react-native info
info Fetching system and libraries information...
System:
    OS: macOS Mojave 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz
    Memory: 30.73 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 13.12.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.8.4 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3, 29.0.2
      System Images: android-29 | Google Play Intel x86 Atom
      Android NDK: 21.0.6113669
  IDEs:
    Android Studio: 3.6 AI-192.7<IP_ADDRESS>08749
    Xcode: 10.3/10G8 - /usr/bin/xcodebuild
  Languages:
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: ^0.62.1 => 0.62.1
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce

Created Android project with Empty Activity
Commit: https://github.com/oreyes598/YARNAppIssue/commit/40e003bee46e265ac347bcb1f2e3fcee554b579c

Added package.json
Commit: https://github.com/oreyes598/YARNAppIssue/commit/89d6d9f46e1c5e9fb2f1ce93b4caa621671f4380

Added react-native by running the command in the terminal

yarn add react-native

See all these warning

[1/4] 🔍  Resolving packages...
warning react-native > fbjs ><EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning react-native > create-react-class > fbjs ><EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning react-native > fbjs-scripts ><EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning react-native > metro-babel-register ><EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning react-native > @react-native-community/cli > metro-core > jest-haste-map > micromatch > snapdragon > source-map-resolve ><EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
warning react-native > @react-native-community/cli > metro-core > jest-haste-map > micromatch > snapdragon > source-map-resolve ><EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "react-native ><EMAIL_ADDRESS>has unmet peer dependency "@babel/core@*".
warning "react-native ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>

Resolved all warnings by running these commands

$ yarn add core-js@3

$ yarn add @babel/core@*

$ yarn add<EMAIL_ADDRESS>
Commit: https://github.com/oreyes598/YARNAppIssue/commit/e8a487ed5e82c4cf5936b670ded63974ba6ab5b0

Added dependencies to Android app build.gradle and repository in root build.gradle project
Commit: https://github.com/oreyes598/YARNAppIssue/commit/b8bed2b8d263da3992d8c426db7247ba490847ba

Updated AndroidManifest file to add permissions and Actvity
Commit: https://github.com/oreyes598/YARNAppIssue/commit/1eed5ba318a6ff1c14bd7f6b10d92790ccb49c43

Created ReactNative Activity in the Android project
Commit: https://github.com/oreyes598/YARNAppIssue/commit/2280efa1cde06ac5445beea04f2bc5c8d701f51c

Added a button in the MainActivity to start the MyReactActivity
Commit: https://github.com/oreyes598/YARNAppIssue/commit/9d41ac099a2b5d50bd5080c703cf23013c7d844c

Now ready to run the application. Started Metro server

yarn start

ISSUE #1: In Android Studio, ran the app and clicked the button to start the MyReactActivity but encountered this crash. Also attempted to start the app just using 'npx react-native run-android' and the same issue.

2020-04-03 14:44:55.688 3337-3438/com.yarn.appissue D/SoLoader: About to load: libhermes.so
2020-04-03 14:44:55.691 3337-3438/com.yarn.appissue D/SoLoader: libhermes.so not found on /data/data/com.yarn.appissue/lib-main
2020-04-03 14:44:55.692 3337-3438/com.yarn.appissue D/SoLoader: libhermes.so not found on /data/app/com.yarn.appissue-kDz7svHCD1g1jexnsvDB3A==/lib/x86
2020-04-03 14:44:55.709 3337-3438/com.yarn.appissue D/SoLoader: libhermes.so not found on /vendor/lib
2020-04-03 14:44:55.709 3337-3438/com.yarn.appissue D/SoLoader: libhermes.so not found on /system/lib
2020-04-03 14:44:55.722 3337-3438/com.yarn.appissue E/SoLoader: couldn't find DSO to load: libhermes.so

    --------- beginning of crash
2020-04-03 14:44:55.723 3337-3438/com.yarn.appissue E/AndroidRuntime: FATAL EXCEPTION: create_react_context
    Process: com.yarn.appissue, PID: 3337
    java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
        at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:789)
        at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:639)
        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:577)
        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:525)
        at com.facebook.hermes.reactexecutor.HermesExecutor.<clinit>(HermesExecutor.java:20)
        at com.facebook.hermes.reactexecutor.HermesExecutorFactory.create(HermesExecutorFactory.java:29)
        at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:997)
        at java.lang.Thread.run(Thread.java:919)

ISSUE #2: Updated root project gradle.build and app gradle.build to add android-jsc support and that stopped the crash above from happening but getting new crash now.
Commit: https://github.com/oreyes598/YARNAppIssue/commit/511754990215d73745915897e111c124627cee5e

2020-04-03 14:57:34.887 3986-3986/com.yarn.appissue D/ReactNative: ReactInstanceManager.createReactContextInBackground()
2020-04-03 14:57:34.887 3986-3986/com.yarn.appissue D/ReactNative: ReactInstanceManager.recreateReactContextInBackgroundInner()
2020-04-03 14:57:34.935 3986-4052/com.yarn.appissue W/unknown:ReactNative: The packager does not seem to be running as we got an IOException requesting its status: socket failed: EPERM (Operation not permitted)
2020-04-03 14:57:34.940 3986-4051/com.yarn.appissue W/unknown:InspectorPackagerConnection: Couldn't connect to packager, will silently retry
2020-04-03 14:57:34.943 3986-4050/com.yarn.appissue W/unknown:ReconnectingWebSocket: Couldn't connect to "ws://<IP_ADDRESS>:8081/message?device=Android%20SDK%20built%20for%20x86%20-%2010%20-%20API%2029&app=com.yarn.appissue&clientid=DevSupportManagerImpl", will silently retry
2020-04-03 14:57:34.948 3986-3986/com.yarn.appissue W/unknown:ReactNative: Packager connection already open, nooping.
:
2020-04-03 14:57:35.061 3986-4054/com.yarn.appissue D/ReactNative: CatalystInstanceImpl.runJSBundle()
2020-04-03 14:57:35.065 3986-4054/com.yarn.appissue E/unknown:ReactNative: Exception in native call
    java.lang.RuntimeException: Unable to load script. Make sure you're either running a Metro server (run 'react-native start') or that your bundle 'index.android.bundle' is packaged correctly for release.
        at com.facebook.react.bridge.CatalystInstanceImpl.jniLoadScriptFromAssets(Native Method)
        at com.facebook.react.bridge.CatalystInstanceImpl.loadScriptFromAssets(CatalystInstanceImpl.java:235)
        at com.facebook.react.bridge.JSBundleLoader$1.loadScript(JSBundleLoader.java:29)
        at com.facebook.react.bridge.CatalystInstanceImpl.runJSBundle(CatalystInstanceImpl.java:259)
        at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:1243)
        at com.facebook.react.ReactInstanceManager.access$1000(ReactInstanceManager.java:132)
        at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:996)
        at java.lang.Thread.run(Thread.java:919)

NOTE: Metro server is running and even accessible in browser http://localhost:8081/. Getting "React Native packager is running." message when loaded in the browser.

After several search for this issue and not able to find solution I ended up not relying on Metro server to get JavaScript code so just added it to the Android project. Ran the command below to bundle the JavaScript code to Android project.

npx react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res/

Commit: https://github.com/oreyes598/YARNAppIssue/commit/9dab535e63756ddbb1e1c236c0a4542ab71a4adb
Expected Results
Expected Result 1: Feedback whether it is really needed to add support for android-jsc and configure the project as such.
Expected Result 2: Should be able to connect to Metro server for online development of React Native application.
Snack, code example, screenshot, or link to a repository:
Sample Project: https://github.com/oreyes598/YARNAppIssue
Note: This project is working but solution/workaround added may not be the right approach so need feedback and/or maybe documentation needs updating.

same problem here

@oreyes598 Did you find any solution ?

Same here. Metro says it can not connect (typical red screen), but when I write down the exact same URL in the browser, it reaches my laptop and comes back with the code.
I am using a Motorola G7 Plus, which has an USB-C port. Connecting through WIFI shows the same results. Android 10.
Done the following from command line:
$ adb devices
# It shows my device
$ adb reverse tcp:8081 tcp:8081
$ fastlane dev # this just assembles a debug apk for local env
$ adb install -r <path-to-debug-apk>
# the app icon shows on device
$ node node_modules/react-native/local-cli/cli.js start --reset-cache
# the server loads the dependency graph

For everyone, who is facing this issue, I was able to build the project using the steps provided on https://reactnative.dev/docs/integration-with-existing-apps.
Two things which was missed earlier :

Apply the usesCleartextTraffic option to your Debug AndroidManifest.xml.

** Do not ignore this line , the usesCleartextTraffic should be added in debug folder , androidmanifest.xml file , otherwise metro bundler won't able to connect.

Be careful to use your package’s BuildConfig and not the one from the facebook package.

** Important , import the buildconfig from your project , not from facebook.
Hope it will save someone time. cheers

@uditvishnoi2 In the sample I have, I don't have debug folder so I don't have another AndroidManifest.xml there. Are you saying that adding Debug folder/variant and adding AndroidManifest.xml there helped resolve the issue?
Here's the src directory for the sample project showing it only has main, https://github.com/oreyes598/YARNAppIssue/tree/master/android/app/src

Any solution to this, i am also experiencing this right now, App crashes immediately after startup and when i check the logcat i get
    java.lang.RuntimeException: Unable to load script. Make sure you're either running a Metro server (run 'react-native start') or that your bundle 'index.android.bundle' is packaged correctly for release.
        at com.facebook.react.bridge.CatalystInstanceImpl.jniLoadScriptFromAssets(Native Method)
        at com.facebook.react.bridge.CatalystInstanceImpl.loadScriptFromAssets(CatalystInstanceImpl.java:227)
        at com.facebook.react.bridge.JSBundleLoader$1.loadScript(JSBundleLoader.java:28)

@oreyes598 It will be better to create project from scratch , using : npx react-native init AwesomeProject and copy the existing code in it. Debug folder ,is created using buck , which is located under app folder.

@oreyes598 It will be better to create project from scratch , using : npx react-native init AwesomeProject and copy the existing code in it. Debug folder ,is created using buck , which is located under app folder.

@uditvishnoi2 Thanks for the suggestion and that will most likely work for simple existing projects that's easy to move to another project. But for a big complex project I was hoping to avoid that and follow the given instructions.

I  was able to resolve this issue by removing the build import from MainActivity in Android


Progress bar displays with no network logo when internet connection is down.

Actual: Progress bar display with no network logo.

Expected: Progress bar should not be shown.

Fixed with #411


fix horizontal scroll bug (#10554)

Fixes https://github.com/microsoft/azuredatastudio/issues/10378 in release
Commit taken from https://github.com/microsoft/azuredatastudio/pull/10554

Coverage decreased (-0.03%) to 33.627% when pulling 7830c7004827f1b9bc41777f4a1778e4fa30fe90 on hotfix/scroll into 2acd37a1b1cff34b64fbb4ea2d40715d7e2accac on release/1.18.


no such file or directory on extract on run

If the extract command from the readme is used without creating the necessary directories in the assets folder, then the tool will crash with no such file or directory.
ngx-translate-extract version: 2.3.4
Full log:
E:\development\goprojects\src\github.com\zlepper\physicalStore\frontend>npm run extract

><EMAIL_ADDRESS>extract E:\development\goprojects\src\github.com\zlepper\physicalStore\frontend
> ngx-translate-extract --input ./src --output ./src/assets/i18n/*.json --clean --sort --format namespaced-json

Extracting strings...
- src/app/app.component.spec.ts
- src/app/app.component.ts
- src/app/app.module.ts
- src/app/app.routing.ts
- src/app/helpers/Queue.ts
- src/app/lists/create-new-list/create-new-list.component.spec.ts
- src/app/lists/create-new-list/create-new-list.component.ts
- src/app/lists/lists.component.spec.ts
- src/app/lists/lists.component.ts
- src/app/lists/open-list/confirm-list-delete/confirm-list-delete.component.spec.ts
- src/app/lists/open-list/confirm-list-delete/confirm-list-delete.component.ts
- src/app/lists/open-list/confirm-list-delete/ValueValidator.ts
- src/app/lists/open-list/create-new-post/create-new-post.component.spec.ts
- src/app/lists/open-list/create-new-post/create-new-post.component.ts
- src/app/lists/open-list/open-list.component.spec.ts
- src/app/lists/open-list/open-list.component.ts
- src/app/lists/open-list/post/edit-post/edit-post.component.spec.ts
- src/app/lists/open-list/post/edit-post/edit-post.component.ts
- src/app/lists/open-list/post/post-remove-confirm/post-remove-confirm.component.spec.ts
- src/app/lists/open-list/post/post-remove-confirm/post-remove-confirm.component.ts
- src/app/lists/open-list/post/post.component.spec.ts
- src/app/lists/open-list/post/post.component.ts
- src/app/lists/open-list/upload-area/upload-area.component.spec.ts
- src/app/lists/open-list/upload-area/upload-area.component.ts
- src/app/login/login.component.spec.ts
- src/app/login/login.component.ts
- src/app/models/list.ts
- src/app/models/post.ts
- src/app/operators/behaviorSubject.ts
- src/app/operators/delayAtLeast.ts
- src/app/services/auth.service.spec.ts
- src/app/services/auth.service.ts
- src/app/services/is-authenticated.guard.spec.ts
- src/app/services/is-authenticated.guard.ts
- src/app/services/lists.service.spec.ts
- src/app/services/lists.service.ts
- src/app/services/local-storage.service.spec.ts
- src/app/services/local-storage.service.ts
- src/app/services/log.pipe.spec.ts
- src/app/services/log.pipe.ts
- src/app/services/services.module.ts
- src/app/services/upload.service.spec.ts
- src/app/services/upload.service.ts
- src/app/sign-up/repeatValidator.ts
- src/app/sign-up/sign-up.component.spec.ts
- src/app/sign-up/sign-up.component.ts
- src/environments/environment.prod.ts
- src/environments/environment.ts
- src/main.ts
- src/polyfills.ts
- src/test.ts
- src/typings.d.ts
- src/app/app.component.html
- src/app/lists/create-new-list/create-new-list.component.html
- src/app/lists/lists.component.html
- src/app/lists/open-list/confirm-list-delete/confirm-list-delete.component.html
- src/app/lists/open-list/create-new-post/create-new-post.component.html
- src/app/lists/open-list/open-list.component.html
- src/app/lists/open-list/post/edit-post/edit-post.component.html
- src/app/lists/open-list/post/post-remove-confirm/post-remove-confirm.component.html
- src/app/lists/open-list/post/post.component.html
- src/app/lists/open-list/upload-area/upload-area.component.html
- src/app/login/login.component.html
- src/app/sign-up/sign-up.component.html
- src/index.html
Extracted 0 strings

Saving: E:\development\goprojects\src\github.com\zlepper\physicalStore\frontend\src\assets\i18n\*.json
- sorted strings
fs.js:652
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open 'E:\development\goprojects\src\github.com\zlepper\physicalStore\frontend\src\assets\i18n\*.json'
    at Object.fs.openSync (fs.js:652:18)
    at Object.fs.writeFileSync (fs.js:1299:33)
    at E:\development\goprojects\src\github.com\zlepper\physicalStore\frontend\node_modules\@biesbjerg\ngx-translate-extract\dist\cli\tasks\extract.task.js:93:16
    at Array.forEach (native)
    at ExtractTask._save (E:\development\goprojects\src\github.com\zlepper\physicalStore\frontend\node_modules\@biesbjerg\ngx-translate-extract\dist\cli\tasks\extract.task.js:59:22)
    at ExtractTask.execute (E:\development\goprojects\src\github.com\zlepper\physicalStore\frontend\node_modules\@biesbjerg\ngx-translate-extract\dist\cli\tasks\extract.task.js:32:14)
    at Object.<anonymous> (E:\development\goprojects\src\github.com\zlepper\physicalStore\frontend\node_modules\@biesbjerg\ngx-translate-extract\dist\cli\cli.js:111:9)
    at Module._compile (module.js:569:30)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:503:32)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>extract: `ngx-translate-extract --input ./src --output ./src/assets/i18n/*.json --clean --sort --format namespaced-json`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>extract script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\hanse\AppData\Roaming\npm-cache\_logs\2017-11-11T10_19_10_130Z-debug.log

```

Same here!

I get exactly the same problem.  Running on Windows 10

Same issue with Win10.

Same here.

Windows 10
ngx-translate-extract 2.3.4
npm 3.10.10
node 6.11.0

win 10
ngx-translate-extract 2.3.4
yarn 1.7.0
node 10.4.1
same bug, it do not understand asterix symbol
`Saving: D:\Work\ecp-cabinet\src\locale*.po

sorted strings
fs.js:145
throw err;
^

Error: ENOENT: no such file or directory, open 'D:\Work\ecp-cabinet\src\locale*.po'
at Object.fs.openSync (fs.js:579:3)
at Object.fs.writeFileSync (fs.js:1309:33)
at D:\Work\ecp-cabinet\node_modules@biesbjerg\ngx-translate-extract\dist\cli\tasks\extract.task.js:93:16
at Array.forEach ()
at ExtractTask._save (D:\Work\ecp-cabinet\node_modules@biesbjerg\ngx-translate-extract\dist\cli\tasks\extract.task.js:59:22)
at ExtractTask.execute (D:\Work\ecp-cabinet\node_modules@biesbjerg\ngx-translate-extract\dist\cli\tasks\extract.task.js:32:14)
at Object. (D:\Work\ecp-cabinet\node_modules@biesbjerg\ngx-translate-extract\dist\cli\cli.js:111:9)
at Module._compile (internal/modules/cjs/loader.js:702:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:713:10)
at Module.load (internal/modules/cjs/loader.js:612:32)
error Command failed with exit code 1.`

I'm having this issue as well on Windows 10, Angular 6.
This is what I'm trying for now - does not error:
"extract-translations": "ngx-translate-extract --input ./src --output ./src/assets/i18n/ --clean --sort --format namespaced-json --marker _"
I am new to this module so I'll let you know if it works as expected.

plugin on win 10 cant recognize asterics (*) sign. Only solution I found is to run command separately for each language. If you have few one, its no problem (borring, but work). If you have many langs, use linux.

then how do this.. change operating system ... Its not possible...

@biesbjerg will this get fixed?

i not tried yet, but i have an idea, use Ubuntu from windows store )

My friends what works for me like a charm is:
"extract-translations": "ngx-translate-extract --input ./src --output ./src/assets/i18n/en.json ./src/assets/i18n/es.json --clean --sort"
It seems that in windows it does not recognize the *.json pattern

Added a note in README about this not working on Windows.

IT is happening for me to for version 4.0.0


rebass@v2 Text fontWeight bug

<Text fontWeight="700">some text</Text> generate spacefont-weight: 700

Thanks! I think this was related to jxnblk/styled-system#288 – if you can check with the latest versions, that'd be helpful


Update Dart Basics pages to link to live example and source code

[x] overview - #1410
[x] architecture - #1807
[x] displaying-data - #1819
[x] forms - #2176
[x] user input - #2175
[x] dependency-injection
[x] template-syntax

Contributes to #1580. Also see #1508.

All done.
cc @kwalrath


ABC Improvements

#697 Extension of this PR

[X] Use a map for HATCHER_ALLOWLIST
[X] Clean up state when going from Hatch -> Open
[x] Various spell-checking fixes
[x] Allow an existing tokenfactory token - reverted
[x] Implement a circuit breaker
[x] Add a new method to donate into the reserve from comment - reverted
[x] Add transparency around initial token config - reverted
[x] Fix logic around auto-sending funding pool from comment
[x] Move curves into cw-curves package
[x] Allow hatcher allowlist by DAO membership

Running just gen will update the contract schemas and fix those schema errors.

Shoutout to @BHIIKTOR btw for noticing unnecessary packages and aliases after moving things to cw-curves package

I still want to squeeze in a couple of things.

[ ] Buy and sell quotes (how many tokens will a user receive from x amount)
[ ] MinMax contribution limit override by hatcher config

this is ready 🔥