Add uproot python package

Motivation for this change
Package uproot is missing from the distribution.
Things done

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

[ ] NixOS
[x] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg build python3.pkgs.uproot

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: python3.pkgs.uproot
Partial log (click to expand)
Cannot nix-instantiate `python3.pkgs.uproot' because:
error: attribute 'uproot' in selection path 'python3.pkgs.uproot' not found

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python3.pkgs.uproot
Partial log (click to expand)
Cannot nix-instantiate `python3.pkgs.uproot' because:
error: attribute 'uproot' in selection path 'python3.pkgs.uproot' not found

I think I've addressed all the comments. Can you please check again?

The expression needs to be called from python-packages.nix.

done. This is my first real contribution, sorry for being sloppy...

@GrahamcOfBorg build python3.pkgs.uproot

Success on aarch64-linux (full log)
Attempted: python3.pkgs.uproot
Partial log (click to expand)
Installing collected packages: uproot
Successfully installed uproot-2.8.16
/build/source
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/nq9lpyzs5zzg5hy3i60v20xsn60mhr6z-python3.6-uproot-2.8.16
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/nq9lpyzs5zzg5hy3i60v20xsn60mhr6z-python3.6-uproot-2.8.16/lib
patching script interpreter paths in /nix/store/nq9lpyzs5zzg5hy3i60v20xsn60mhr6z-python3.6-uproot-2.8.16
checking for references to /build in /nix/store/nq9lpyzs5zzg5hy3i60v20xsn60mhr6z-python3.6-uproot-2.8.16...
/nix/store/nq9lpyzs5zzg5hy3i60v20xsn60mhr6z-python3.6-uproot-2.8.16

Success on x86_64-darwin (full log)
Attempted: python3.pkgs.uproot
Partial log (click to expand)
Processing ./uproot-2.8.16-py3-none-any.whl
Requirement already satisfied: numpy in /nix/store/8jcsbs0m9hklh01mmh2ydnhw1mrgsy6i-python3.6-numpy-1.14.2/lib/python3.6/site-packages (from uproot==2.8.16)
Installing collected packages: uproot
Successfully installed uproot-2.8.16
/private/tmp/nix-build-python3.6-uproot-2.8.16.drv-0/source
post-installation fixup
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/0k4xajqzgiy4rahzi5bz69dsg1mq9xv2-python3.6-uproot-2.8.16/lib
patching script interpreter paths in /nix/store/0k4xajqzgiy4rahzi5bz69dsg1mq9xv2-python3.6-uproot-2.8.16
/nix/store/0k4xajqzgiy4rahzi5bz69dsg1mq9xv2-python3.6-uproot-2.8.16

Success on x86_64-linux (full log)
Attempted: python3.pkgs.uproot
Partial log (click to expand)
Installing collected packages: uproot
Successfully installed uproot-2.8.16
/build/source
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/l7q8azscxx9y6j3x2rwmd07f3dzz4x1m-python3.6-uproot-2.8.16
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/l7q8azscxx9y6j3x2rwmd07f3dzz4x1m-python3.6-uproot-2.8.16/lib
patching script interpreter paths in /nix/store/l7q8azscxx9y6j3x2rwmd07f3dzz4x1m-python3.6-uproot-2.8.16
checking for references to /build in /nix/store/l7q8azscxx9y6j3x2rwmd07f3dzz4x1m-python3.6-uproot-2.8.16...
/nix/store/l7q8azscxx9y6j3x2rwmd07f3dzz4x1m-python3.6-uproot-2.8.16

I've done the requested changes.
@dotlambda I've tried adding lz4 and lama, however they seem not to be picked up when building. I am using an overlay with the following to test:
uproot = import ../nixpkgs/pkgs/development/python-modules/uproot {
     inherit (self) lib;
     inherit (super.python27.pkgs) fetchPypi;
     inherit (super.python27.pkgs) buildPythonPackage numpy lz4;
     inherit (super) lzma;
};

and I of course added lz4 and lzma to the propagatedBuildInputs. Am I doing something trivially wrong?

If it's Python 3, there might not be an lzma package because that's in the standard library now.

@jpivarski in my test it's python2.7. I suspect it's something nix related, actually.

By looking at the code, e.g. https://github.com/scikit-hep/uproot/blob/47b981e6ce0b5913a763d379eae1c0337a898a01/tests/test_compression.py#L34-L41, it should just work when adding the lz4 (and lzma in the case of python 2) python packages to propagatedBuildInputs.

@ktf Now what's left to do is naming your second commit (and your PR) pythonPackages.uproot: init at <version>.
@GrahamcOfBorg build python2.pkgs.uproot python3.pkgs.uproot

Success on x86_64-linux (full log)
Attempted: python2.pkgs.uproot, python3.pkgs.uproot
Partial log (click to expand)
test_issue74 (tests.test_issues.TestIssues) ... ok
test_issue76 (tests.test_issues.TestIssues) ... ok
test_issue79 (tests.test_issues.TestIssues) ... ok

----------------------------------------------------------------------
Ran 74 tests in 7.619s

OK
/nix/store/pff88w2kvarhm3ysj796g7i7m0cy2l2c-python2.7-uproot-2.8.23
/nix/store/bbf4pavmbjm0ghzsdf7311mqkgbzgyd8-python3.6-uproot-2.8.23

Success on aarch64-linux (full log)
Attempted: python2.pkgs.uproot, python3.pkgs.uproot
Partial log (click to expand)
test_irregular_array (tests.test_cache.TestCache) ... ok
test_regular_array (tests.test_cache.TestCache) ... ok
test_strings_array (tests.test_cache.TestCache) ... ok

----------------------------------------------------------------------
Ran 74 tests in 41.814s

OK
/nix/store/h8f1f3vclgm2i3773byd07im6brdw1g4-python2.7-uproot-2.8.23
/nix/store/2an977hpilsm2bh1qvwnh75lqyj1389j-python3.6-uproot-2.8.23

@dotlambda done.


update next- versions for pylint/mypy/pyright

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

@l0lawrence autorest.python is targeting pylint==3.1.0: https://github.com/Azure/autorest.python/blob/main/eng/requirements.txt#L3
Do we want to do that here for next-pylint?

if they are already, yes lets do it to keep aligned 💯  https://pylint.readthedocs.io/en/stable/whatsnew/3/3.1/index.html


Allow moving back in the process

Moving back could be done via Process Instance Modification (https://docs.camunda.io/docs/components/operate/userguide/process-instance-modification/).

advantages of PIM:

Manipulation clearly visible

disadvantages of PIM

Breaks history & heatmap
Shortest path algorithm may still be needed (as for missing messages) OR one just picks any
At least one still needs to check if the currently received message can be received by the process (would go away with message correlation feedback)
Has limitations that require process changes, e.g. multi-instance

won't implement this as of now; updated reasoning in README (see https://github.com/camunda-community-hub/message-correlator/commit/01137482bc65a55a7f83b201535c86cd531dcc37)


chd: Fix various memory and overflow bugs

As part of trying to improve the robustness of input file handling for my emulator, I have identified and fixed a number of issues in libchdr's CHD handling. Most of these were discovered through some very brief fuzzing with LibFuzzer.
The majority are straightforward - missing error checking, or assuming input was structurally valid. The only one I'm a bit iffy on is d5935ca - is a 128MB maximum hunk size and 10GB data size reasonable?
It's one of the first things that libfuzzer hit, so I had to add some basic checks, and even if the allocation will fail on most systems. Should you have a corrupted file, you don't really want them to swap out all their working sets to satisfy it, only to fail loading later.
5eb9a28 is related to #118, however it only fixes the malicious/corrupted case, I didn't have any very low-compression CHDs to check with.
I fully acknowledge that many of these would require some serious work to actually accomplish anything malicious with, and many of them are just reads, not writes, but IMO it's best to validate everything where possible, especially when there is basically no performance cost to doing so. And it saves OOM/crashing if the user does have accidental file corruption.
I've included the fuzz target in this PR as well. If that's not something you want upstream, let me know and I'll drop the commit. If anyone wants to spend more time fuzzing the library, simply enable the CMake option and use make fuzz to invoke it. You'll probably also need to set -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ as well on most systems. There are no doubt more data validation issues... :)

Yep, it is. I just tacked the last commit on there since it was straightforward, the others have been tested by DS users for a week or so.

Why is C89 a goal? Just a personal flex? C11 should be the bare minimum supported across compilers, even ones for relatively older hardware.

Why is C89 a goal? Just a personal flex? C11 should be the bare minimum supported across compilers, even ones for relatively older hardware.

FWIW I agree 100%, but that is a can of worms that is best kept closed.
Unless things have changed of course - it would be nice to see.


Fixed the problem of donation card

Issue no:- #1024
Before :-

After :-

Added pointer As cursor

Please see the conflicts highlighted. Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


Keyboard functioning in Basic Calculator

Describe a logic in Basic Calculator so that user can type the number on the calculator website using his/her PC keyboard!!

Hi @Rakesh9100 I would like to work on this issue under JWOC

For JWOC, you need to make comment after 15th Jan 12:00 AM else considered invalid comment @SoumyadevSaha

For JWOC, you need to make comment after 15th Jan 12:00 AM, else considered invalid comment @SoumyadevSaha

okay, then I need to comment once more at 12.01 on 15th right ?

Yes @SoumyadevSaha

Hello @Rakesh9100  please assign me this project under SWOC'24

Proceed @Developer-Swati

Thankyou @Rakesh9100

@Developer-Swati Status of your PR pls

@Rakesh9100  please assign it to someone else. I am busy in my semester exams. I am really sorry for that

Would like to work on it under IWOC @Rakesh9100

Go ahead @SoumyadevSaha


DOC-2380 chart path

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[x ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/DOC-2380

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Rancher server crashed when node is draining.

Rancher versions: Build from master
Setup:
DO cluster with 3 worker nodes.
Drain one of the nodes.
When the pods was still in the process of draining , rancher server container crashed and restarted.
rancher-server logs:
2018/09/13 23:05:48 [ERROR] nodeDrain: [santestworker3] in cluster [c-xkhlt] : pod/cattle-cluster-agent-5c769fdb64-jt5ld
pod/santest1-66b4cddc7f-8lckg
pod/santest1-66b4cddc7f-9hspm
pod/santest1-66b4cddc7f-mkgfl
pod/santest1-66b4cddc7f-nnwzn
pod/santest1-66b4cddc7f-q76kr
pod/santest1-66b4cddc7f-rt8hx
pod/default-http-backend-797c5bc547-ft8tb
pod/kube-dns-7588d5b5f5-bcbh6
pod/kube-dns-autoscaler-5db9bbb766-8khxm
pod/metrics-server-97bc649d5-wnfdz

 santestworker3
error: error when evicting pod "santest1-66b4cddc7f-q76kr": the server is currently unable to handle the request (post pods.policy santest1-66b4cddc7f-q76kr)
 Operation cannot be fulfilled on nodes.management.cattle.io "m-cxmhq": the object has been modified; please apply your changes to the latest version and try again
2018/09/13 23:05:50 [INFO] Handling backend connection request [c-xkhlt]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x380ab40]

goroutine 196538 [running]:
github.com/rancher/rancher/pkg/controllers/user/nodesyncer.(*NodeDrain).drain(0xc016df8090, 0x80affe0, 0xc007e1cac0, 0xc01484a800, 0xc01e328360)
	/go/src/github.com/rancher/rancher/pkg/controllers/user/nodesyncer/cordonfieldssyncer.go:128 +0x200
created by github.com/rancher/rancher/pkg/controllers/user/nodesyncer.(*NodeDrain).drainNode
	/go/src/github.com/rancher/rancher/pkg/controllers/user/nodesyncer/cordonfieldssyncer.go:79 +0x2d9

Rancher server goes into a crash loop with this exception:
2018/09/13 23:12:55 [INFO] registering podsecuritypolicy namespace handler for cluster c-xkhlt
2018/09/13 23:12:55 [INFO] registering podsecuritypolicy serviceaccount handler for cluster c-xkhlt
2018/09/13 23:12:55 [INFO] registering podsecuritypolicy template handler for cluster c-xkhlt
2018/09/13 23:12:55 [INFO] Starting cluster controllers for c-xkhlt
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x380ab40]

goroutine 16871 [running]:
github.com/rancher/rancher/pkg/controllers/user/nodesyncer.(*NodeDrain).drain(0xc0063503f0, 0x80affe0, 0xc010fca100, 0xc009e1f750, 0xc006460470)
	/go/src/github.com/rancher/rancher/pkg/controllers/user/nodesyncer/cordonfieldssyncer.go:128 +0x200
created by github.com/rancher/rancher/pkg/controllers/user/nodesyncer.(*NodeDrain).drainNode
	/go/src/github.com/rancher/rancher/pkg/controllers/user/nodesyncer/cordonfieldssyncer.go:79 +0x2d9

Tested with latest build from master.
Able to drain nodes successfully.


Monero not showing in wallet

I transferred Monero to my wallet using sideshift.ai. It has always worked 100%. Now it is not showing!
All details on the Monero transaction is available.
Help urgently needed!

This is issue 498... but yea this is like the September 11 of MyMonero.


[meta] all components should report their 2.0.x version string

In Deis v1.x each component has an ENV DEIS_RELEASE v1.x string in its Dockerfile. That was a workaround that may no longer be needed, and requires lots of clerical PRs just to update strings. In Deis v2.x it would be preferable for each component to print its version up-front, on startup.

@mboersma should the versions be 2.0.0?

In workflow we bumped the deis client to 2.0.0-dev. But that's probably not specific enough at this point--it will be more useful to have 2.0.0-beta1 or something similar that contains the pre-release version. (And maybe the git SHA?) And since printing such a version up-front will require changes to components, it's not in scope for alpha.

@mboersma I see. I opened a few PRs that I'll leave open for now, without an alpha milestone

@mboersma Can we start opening up tickets for the components that are missing and fix up the version strings as needed?

@mboersma says this isn't needed anymore


HOTA vs HOTA(0)

Hi,
For evaluation, the HOTA printed out and the HOTA(0) in the csv don't match. What does the '(0)' mean?
Thanks,

I think this means the HOTA value at Loc-IoU threshold \alpha=0. The overall HOTA value is an average over HOTA(\alpha) with \alpha from 0 to 1. See their blog. I didn't check this though, and always stick with the printed HOTA.

Got it. Thanks Zhongbao


flaky client integration test

Client tests with QUIC version TLS dev version (WIP)

  uploads a file

  /home/travis/gopath/src/github.com/lucas-clemente/quic-go/integrationtests/self/client_test.go:83

• Failure [30.090 seconds]

Client tests

/home/travis/gopath/src/github.com/lucas-clemente/quic-go/integrationtests/self/client_test.go:21

  with QUIC version TLS dev version (WIP)

  /home/travis/gopath/src/github.com/lucas-clemente/quic-go/integrationtests/self/client_test.go:45

    uploads a file [It]

    /home/travis/gopath/src/github.com/lucas-clemente/quic-go/integrationtests/self/client_test.go:83

    Expected error:

        <*url.Error | 0xc42b4a8120>: {

            Op: "Post",

            URL: "https://quic.clemente.io:59843/echo",

            Err: {

                ErrorCode: 97,

                ErrorMessage: "cannot read frame",

            },

        }

        Post https://quic.clemente.io:59843/echo: HeadersStreamDataDecompressFailure: cannot read frame

    not to have occurred

    /home/travis/gopath/src/github.com/lucas-clemente/quic-go/integrationtests/self/client_test.go:89

    Full Stack Trace

    	/home/travis/gopath/src/github.com/onsi/gomega/internal/assertion/assertion.go:69 +0x1ef

    github.com/onsi/gomega/internal/assertion.(*Assertion).ToNot(0xc42b415a40, 0xbbda00, 0xce5330, 0x0, 0x0, 0x0, 0xc42b415a40)

    	/home/travis/gopath/src/github.com/onsi/gomega/internal/assertion/assertion.go:39 +0xae

    github.com/lucas-clemente/quic-go/integrationtests/self_test.glob..func1.3.5()

    	/home/travis/gopath/src/github.com/lucas-clemente/quic-go/integrationtests/self/client_test.go:89 +0x244

    github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc423503260, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)

    	/home/travis/gopath/src/github.com/lucas-clemente/quic-go/integrationtests/self/self_suite_test.go:14 +0x64

    testing.tRunner(0xc42021a0f0, 0x95f360)

    	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/testing/testing.go:746 +0xd0

    created by testing.(*T).Run

    	/home/travis/.gimme/versions/go1.9.2.linux.amd64/src/testing/testing.go:789 +0x2de

Fixed by #1067 (apparently Github doesn't auto-close issues, when the keywords for doing so are in a comment 👎 ).


[Chainlist] [Issue-259] Hotfix update chain-list stable version

Related issue(s)

https://github.com/Koniverse/SubWallet-ChainList/issues/259

Is your feature request related to a problem(s)? Please describe.

Update stable version for chain-list

Describe the solution you'd like

Update stable version for chain-list

Describe alternatives you've considered

No

Additional context

No

🚀 Deployed on https://pr-3299--sw-web-runner.netlify.app


Can you add to the documentation how Dependabot decides on the superseded security-updates (PRs)?

A vast number of the closed security-PRs are due to that Dependabot closes the original security-PR and creates a new one with a newer version of the affected dependencies. However, given that Dependabot sends a pull request to update the affected dependency manifest with the closest non-vulnerable version [1], why would it send a newer pull request to update the dependency?
@greysteil  Could you please clarify this point here [1]:
[1] https://github.blog/2020-06-01-keep-all-your-packages-up-to-date-with-dependabot/

@greysteil :-))

I can't comment on the GitHub native version of Dependabot as I didn't write it - @infin8x or @feelepxyz may be able to provide more details. The strategy I'd expect us to be aiming for with security updates is only to supersede them if a newer version fixes additional security vulnerabilities.

A vast number of the closed security-PRs are due to that Dependabot closes the original security-PR and creates a new one with a newer version of the affected dependencies. However, given that Dependabot sends a pull request to update the affected dependency manifest with the closest non-vulnerable version [1], why would it send a newer pull request to update the dependency?

Yeah Dependabot should be targeting the lowest non-vulnerable version and only update it if there's a new vulnerability for a later version. Do you have any example public repos where you've spotted this? Can take a look and see if there's anything funky going with this logic.

A vast number of the closed security-PRs are due to that Dependabot closes the original security-PR and creates a new one with a newer version of the affected dependencies. However, given that Dependabot sends a pull request to update the affected dependency manifest with the closest non-vulnerable version [1], why would it send a newer pull request to update the dependency?

@mahmoud-alfadel Dependabot should be targeting the lowest non-vulnerable version and only update it if there's a new vulnerability for a later version. Do you have any example public repos where you've spotted this? Can take a look and see if there's anything funky going with this logic.

Thanks, @feelepxyz, for the information. Here is an example of such a case in a public repo:
https://github.com/deadlybyte/react-speedy-reader/pull/146

I looked through the chain of PR's that cascade from https://github.com/deadlybyte/react-speedy-reader/pull/146 and in all cases that I saw the next PR that superceded the previous PR had an additional vulnerability that it was fixing. So it's still going to the "lowest version that resolves all known vulnerabilities".


retry with fallback timer

Are there any examples available for managing retry schedules that could postpone the retry attempt for a few minutes? Ideally, the first retry should occur after one minute, the second retry after two minutes, and the third retry after three minutes.

Have you looked at https://github.com/geofmureithi/apalis/issues/399?


[WIP] Data Tiling for GPU

This PR is the first attempt for data tiling for GPUs. It implements materialization for the encoding.
Note that, it cannot compile any program. Because it generates tensor.pad and we don't know how to tile it yet. #10184 can be enabled to tile for tensor.pad but it results bufferization problem #11273

Closing stale PR.


First Commit! (RodDeacon)

Task to create a first commit! Probably something to CONTRIBUTING.md or README.md

Ok, a first comment from Kevin!


Add PCB

Original discussion: leodesigner/powmr_comm#3

Heh, cool! I'm currently testing an upgraded controller with PZEM-004 at the input of the inverter. Then I was planning to start designing the controller board. In that case, I will use yours as a basis. Thank you!

@davidebeatrici   By the way, are you sure there won't be any issues with ESPHome on ESP32-C3? The documentation states that it's not fully supported, and there might be problems.

Heh, cool! I'm currently testing an upgraded controller with PZEM-004 at the input of the inverter. Then I was planning to start designing the controller board. In that case, I will use yours as a basis. Thank you!

Awesome, looking forward to it!

By the way, are you sure there won't be any issues with ESPHome on ESP32-C3? The documentation states that it's not fully supported, and there might be problems.

Working flawlessly here with the following changes to the ESP32 config:
substitutions:
  device_name: "powmr-inverter"
  node_name: "PowMr Inverter"
  node_id: powmr_inverter
  tx_pin: GPIO7
  rx_pin: GPIO6

esp32:
  board: esp32-c3-devkitm-1
  framework:
    type: arduino

Home Assistant
Please note that it's night and there is no battery at the moment.


Usage of the code

Hi, really appreciate that you create this dataloader. Could you give a simple sample of how to use the code during training?
Thank you so much!

I modify some parts of the code and make it work for me. Really thank you for your framework.


OOM in production with high tenant count

OOMs have been observed in production, related slack threads:

https://neondb.slack.com/archives/C03F5SM1N02/p1676292700744839
https://neondb.slack.com/archives/C033RQ5SPDH/p1676396240193049

My understanding of the root cause is that while pageserver uses somewhat conservative amount of RAM, for each been-active tenant we have a postgres --wal-redo process, which is about 22MB RSS idle.
Possible solutions iterated in threads:

enable linux swap

tail latency++

higher oom score adj for postgres --wal-redo via choom for example
exit postgres --wal-redo on a timeout from https://github.com/neondatabase/neon/blob/7991bd3b6921ccdd13f0f38085127bbe282d4f26/pgxn/neon_walredo/walredoproc.c#L823
detect process is already exited before sending request in https://github.com/neondatabase/neon/blob/7991bd3b6921ccdd13f0f38085127bbe282d4f26/pageserver/src/walredo.rs#L265-L268

via killed via oom_score_adj, or having exited as suggested above

Increasing oom_score_adj for each postgres --wal-redo would probably have a negative effect in the case memory usage of one would spike, then it would be a very likely candidate to be killed and we would just retry.

adding relevant discussion from slack: https://neondb.slack.com/archives/C03H1K0PGKH/p1678107912052379

Because #3739 was merged, all that remains is dying on timeout on read iff we have completly handled sending page.

@koivunej any objections to close this one ? or do we have followups ? (I think this is dup of #3687)

this is dup of #3687

Well, it cannot duplicate a later issue now can it :)
This became relevant for the choom parts. Looking around, I do still see a chromium bug open about the fact so unsure if this is doable: https://bugs.chromium.org/p/chromium/issues/detail?id=333617 -- esp. given rss differences of pageserver AND walredo processes, but there might be spikes of which we do not know.

Discussed in 2023-11-06 meeting, not going to be worked in near future.

Noted #5877 in the issue description. I don't think we need the choom route at least currently, which is the only unimplemented.


Move dotenv warning to stderr

It was printed to stdout, which broke custom flask subcommands whose output was consumed by scripts (which might expect json or something else that's not just text).

This doesn't match the rest of the flask run output, which prints to stdout. Is that going to be an issue?

I thought about this too, but flask run is not something that will evr produce output which is useful when processed programmatically, while flask <something> may very much output something that's consumed by another program.


ERROR: SSL peer shut down incorrectly

hello,
what's wrong with this ?
after i download the project and build it in Android studio, but it tell me
ERROR: SSL peer shut down incorrectly
how to solve the problem ?
thx

This error is something related to build configuration.
please check SO thread https://stackoverflow.com/q/47629999


MAIN-ERROR-Failed to load image.

python3
macOS Mojave 10.14.6

what dose input_path means ? where should l download it or find it locally?

input_path means path to your image file. I appears you have used it correctly. I would verify that /Users/xuqiang/Acquisition.E01 actually exists and is valid.
This is an error with pyewf. I haven't encountered this before. Can you run the script with -l DEBUG option. This will run the script in debug mode and may offer  more info on what is going on.

l don't have /Users/xuqiang/Acquisition.E01. How can l build it or where can l download it ?

EO1 is an image file format, you can use several free tools such as
AccessData FTK Imager to create an E01 image file from a hard drive. You
can also acquire an image in .dd format, again using several free tools. If
you use a dd,  change the mac_apt image format input to dd when selecting
your image file.
On Tue, Oct 15, 2019 at 11:20 PM 徐强<EMAIL_ADDRESS>wrote:

l don't have /Users/xuqiang/Acquisition.E01. How can l build it or where
can l download it ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ydkhatri/mac_apt/issues/23?email_source=notifications&email_token=AKAEV2KMUEM6MZEO25BWF7TQO2B6ZA5CNFSM4JA3FBC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBK4RSQ#issuecomment-542492874,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKAEV2P25QJUGS65CU34CMLQO2B6ZANCNFSM4JA3FBCQ
.

l don't have /Users/xuqiang/Acquisition.E01.

I think you are trying to run this live, hence the confusion.
If you want to run this live on you mac (no image), then read this page on the wiki:
https://github.com/ydkhatri/mac_apt/wiki/Sample-Usage#run-mac_apt-live-no-image-to-get-artifacts-from-local-machine
Also this one for settings you need when running it live.
https://github.com/ydkhatri/mac_apt/wiki/Known-issues-and-Workarounds

Great! It works. Thx


Resizing comments does not adhere to snapping

Material Maker version:
0.94.stable
OS/device including version:
NA
Issue description:
Resizing comments does not adhere to snapping. When snapping is enabled I would expect comment box scaling to also snap to the grid so I can have everything adhere to the grid.
Steps to reproduce:
Enable snapping. Create a comment and drag at it's corner.

It's likely this is a Godot behavior and we don't have any control over it.

Aren't comments specific to MM? I don't see them available in normal Godot graphs.

Aren't comments specific to MM? I don't see them available in normal Godot graphs.

Comment is a flag in nodes.

This should be fixed in Godot itself, no?

Closing and opening in Godot instead.

For the record, this was fixed by https://github.com/godotengine/godot/pull/45776 in 3.2.4.


Remove unnecessary packages from the default dependency list

Also alphabetizes the dependency list.
 I'm moving countries right now, and don't have much free time...

Works for me. Tested with electron-forge init && electron-forge make && sudo gdebi out/make/*_amd64.deb with an Electron Forge instance that uses this PR. Admittedly, I already have git and python installed, so it's kind of a weird test. A "real" test would involve a clean Linux VM with a minimal X11 install.

Let's merge it then.

@unindented I know you're busy right now, but do you have some time soon to release a new version with this? That would probably cut down on the number of issues like #54 that are filed.

v0.5.0 contains your fix.

Thanks!


Gyro and accels

Hi there - fantastic work, thank you very much for doing this.  I am trying to expose/inject the gyro and accel data, between your work and dekuNukem I have a fairly good idea of the bytes I need to inject but am struggling with where to do it.
It looks like 'server' handles the queues, timing, and communications back and forth.  'Input' parses commands from the human to go to the switch, and 'responses' and 'commands' are directions from the switch back to the emulated joycon.  'Protocol' handles the packets to send to the switch and back.
As a simple test I have defined a new macro (say 'g') that would inject bytes into the z-gyro (for example) location on the packet.  I have added that to 'input', and it calls a modified 'protocol.set_imu_data' function where protocol replaces the subarray with gyro bytes.
Is that a good first test?  I see small responses on the switch but I'm not sure it's doing it correctly.  Would you recommend a different approach, perhaps through 'set_controller_input'?  Sounds like there I'd have to handle repeating the gyro injection for every packet manually, but maybe that is more direct.  Any thoughts?
Thanks again
UPDATE:  I have confirmed the new macro and set_imu_data approach works (tested on Surgeon Simulator).  I am leaning towards adding accel and gyro values as members of protocol, and set_imu_data reads from them.  The input macros then simply update the accel and gyro values as desired.  I suppose I will have to keep a copy of the default value when it wants to return to idle (or zeros I suppose).
PS - surgeon simulator only allows me to test the gyros with feedback on screen.  Does anyone have any recommendations for a switch game that tracks both position and orientation on screen (IE a vr-style interface)?    Maybe Arms?

Thanks for your interest in the project! Your descriptions for the components are definitely correct. In hindsight, I should probably add more documentation so people don't have to dig through the code to understand the underpinnings of the system.
To summarize, NXBT has two ways that input is set/parsed. The first is through use of macros where macro strings are queued up, parsed, and input accordingly. This input method has built-in timings for macros, so it's likely easier to test with, however, you'll need to define the new macro command and parsing methodology for it (which it sounds like you've done). The second method for generating input is through use of set_controller_input. This method uses a "direct input" strategy meaning that set input is immediately sent to the controller (and also supersedes macro input). The downside to this is that the user has to handle all the timing in regards to the input. Direct input is ideal for use in other applications that handle their own input (such as the web app within NXBT).
I believe adding gyro input as a macro command is the correct initial approach, since you can leave timing up to NXBT. My one thought would be in regards to setting the gyro and accel values. I think it might be best if we had set_accel and set_gyro methods that override the default gyro/accel values with specified input when run (similar to how the button presses work). This way we could avoid having to save/replace the default value. Basically, if we have gyro/accel input -> replace default, if not -> default.
It's also great to hear that you've got gyro working. If you're comfortable, I would be happy to review a fork or a PR too.
For further testing, I recall Breath of the Wild, Mario Odyssey, Splatoon 2, Superhot, and Overwatch leverage gyro in some way. I think most of those games, though, have gyro aim assist. I can't really think of any off the top of my head the specifically take into account position.

Thanks for your interest in the project! Your descriptions for the components are definitely correct. In hindsight, I should probably add more documentation so people don't have to dig through the code to understand the underpinnings of the system.
To summarize, NXBT has two ways that input is set/parsed. The first is through use of macros where macro strings are queued up, parsed, and input accordingly. This input method has built-in timings for macros, so it's likely easier to test with, however, you'll need to define the new macro command and parsing methodology for it (which it sounds like you've done). The second method for generating input is through use of set_controller_input. This method uses a "direct input" strategy meaning that set input is immediately sent to the controller (and also supersedes macro input). The downside to this is that the user has to handle all the timing in regards to the input. Direct input is ideal for use in other applications that handle their own input (such as the web app within NXBT).
I believe adding gyro input as a macro command is the correct initial approach, since you can leave timing up to NXBT. My one thought would be in regards to setting the gyro and accel values. I think it might be best if we had set_accel and set_gyro methods that override the default gyro/accel values with specified input when run (similar to how the button presses work). This way we could avoid having to save/replace the default value. Basically, if we have gyro/accel input -> replace default, if not -> default.
It's also great to hear that you've got gyro working. If you're comfortable, I would be happy to review a fork or a PR too.
For further testing, I recall Breath of the Wild, Mario Odyssey, Splatoon 2, Superhot, and Overwatch leverage gyro in some way. I think most of those games, though, have gyro aim assist. I can't really think of any off the top of my head the specifically take into account position.

Thanks.  I ended up adding accel and gyro fields to direct_input_packet in nxbt.py, which then gets submitted through the normal set_controller_input.  In input.py I added at the bottom of parse_controller_input a call to a new function in protocol.py to set_imu_variables, which are new self variables that keep persistant values of accel and gyro data in protocol.self.  Finally, in protocol.set_imu_data I write those values instead of the default ones you have.
I understand what you're saying about returning to default imu values but if a user is trying to overwrite imu values they should probably understand that they need to be returned to default after a while anyways.  I suppose you could add another layer of macros to rotate a gyro for a second or something, and in that macro it would contain the commands to return to zero.
I'm sorry but I don't really know how to do a fork or PR... I guess I could paste some of the code from what I described above and let someone else insert it, but not sure if there is enough of a demand to do that.  Still, it was very fun to do so thanks again for creating this framework, it is the best I've found after a decent amount of searching.
Also FYI, reading joycon accel and gyro info from a human with joycon-python:
https://github.com/tokoroten-lab/joycon-python
is very fun, then emulating those movements with NXBT can open up a wide range of human simulation applications.  It's also interesting just to simply see the accel and gyro values as the joycon goes through different movements.

Thanks.  I ended up adding accel and gyro fields to direct_input_packet in nxbt.py, which then gets submitted through the normal set_controller_input.  In input.py I added at the bottom of parse_controller_input a call to a new function in protocol.py to set_imu_variables, which are new self variables that keep persistant values of accel and gyro data in protocol.self.  Finally, in protocol.set_imu_data I write those values instead of the default ones you have.
I understand what you're saying about returning to default imu values but if a user is trying to overwrite imu values they should probably understand that they need to be returned to default after a while anyways.  I suppose you could add another layer of macros to rotate a gyro for a second or something, and in that macro it would contain the commands to return to zero.
I'm sorry but I don't really know how to do a fork or PR... I guess I could paste some of the code from what I described above and let someone else insert it, but not sure if there is enough of a demand to do that.  Still, it was very fun to do so thanks again for creating this framework, it is the best I've found after a decent amount of searching.
Also FYI, reading joycon accel and gyro info from a human with joycon-python:
https://github.com/tokoroten-lab/joycon-python
is very fun, then emulating those movements with NXBT can open up a wide range of human simulation applications.  It's also interesting just to simply see the accel and gyro values as the joycon goes through different movements.

I'm glad to hear you got an implementation working that you're happy with! I was originally suggesting returning to default since this is how the other inputs (buttons, sticks, etc) function on a "cycle" within nxbt. All the "set_" functions within protocol.py are writing over the defaults initialized when a report is constructed. Anyways, it's been a while since I've read up on how the controller sets the IMU values, so your approach might be the better one in this case!
Per the fork/PR, it's all good. I'm also not sure what the demand is for such a feature. This is part of the reason why I left it out of emulation in the first place. Still, if you're interested getting this added to the repo, let me know and we can work something out.
Thanks as well for the link to that project. I haven't played around much with gyro/accel stuff on the controllers so this might be an interested area to explore in the future.
I think, since you've got an implementation you seem happy with, we can close this issue?

I'm glad to hear you got an implementation working that you're happy with! I was originally suggesting returning to default since this is how the other inputs (buttons, sticks, etc) function on a "cycle" within nxbt. All the "set_" functions within protocol.py are writing over the defaults initialized when a report is constructed. Anyways, it's been a while since I've read up on how the controller sets the IMU values, so your approach might be the better one in this case!
Per the fork/PR, it's all good. I'm also not sure what the demand is for such a feature. This is part of the reason why I left it out of emulation in the first place. Still, if you're interested getting this added to the repo, let me know and we can work something out.
Thanks as well for the link to that project. I haven't played around much with gyro/accel stuff on the controllers so this might be an interested area to explore in the future.
I think, since you've got an implementation you seem happy with, we can close this issue?

Yes please close the issue thanks
On Fri, Jan 29, 2021 at 8:31 PM Reece Walsh<EMAIL_ADDRESS>wrote:

I'm glad to hear you got an implementation working that you're happy with!
I was originally suggesting returning to default since this is how the
other inputs (buttons, sticks, etc) function on a "cycle" within nxbt. All
the "set_" functions within protocol.py are writing over the defaults
initialized when a report is constructed. Anyways, it's been a while since
I've read up on how the controller sets the IMU values, so your approach
might be the better one in this case!
Per the fork/PR, it's all good. I'm also not sure what the demand is for
such a feature. This is part of the reason why I left it out of emulation
in the first place. Still, if you're interested getting this added to the
repo, let me know and we can work something out.
Thanks as well for the link to that project. I haven't played around much
with gyro/accel stuff on the controllers so this might be an interested
area to explore in the future.
I think, since you've got an implementation you seem happy with, we can
close this issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Brikwerk/nxbt/issues/10#issuecomment-770131928, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASNTR6FH2RAYMXTOZLITHMDS4NOOPANCNFSM4V7ZQVIQ
.

@DanceBot1234 could you maybe send me your code? trying to do stuff with motion controls but it's confusing me lol

Hi @DanceBot1234, I would like to get The code You modified. Thank you


Make deploy command bundle edge functions

Summary

Fixes https://github.com/netlify/pillar-runtime/issues/299

Bundles edge functions whenever ntl deploy is called without the --build flag to ensure file changes reflect.
Needs this netlify/build PR merged first: https://github.com/netlify/build/pull/4271

For us to review and ship your PR efficiently, please perform the following steps:

[ ] Open a bug/issue before writing your code 🧑💻. This ensures we can discuss the changes and get feedback from everyone that should be involved.
[ ] Read the contribution guidelines 📖. This ensures your code follows our style guide and
passes our tests.
[ ] Update or add tests (if any source code was changed or added) 🧪
[ ] Update or add documentation (if features were changed or added) 📝
[ ] Make sure the status checks below are successful ✅

A picture of a cute animal (not mandatory, but encouraged)

Failing tests will be fixed once new build package is available from PR https://github.com/netlify/build/pull/4271


Error when trying to change thumbnail

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":

Search the issues already opened: https://github.com/googleapis/google-api-php-client/issues
Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+php

If you are still having issues, please be sure to include as much information as possible:
Environment details

OS: MacOS M2
PHP version: 8.3
Package name and version: "google/apiclient": "^2.15.0"

Steps to reproduce

After following the authentication flow and get/set the bearer token, I'm trying to change a thumbnail of specific video. I'm using Laravel too.

Code example
// After flow of authentication....this is my code:
$service = new Google_Service_YouTube($this->client);

$videoId = "XG96bA9Q9OE";
$newThumbnailPath = storage_path('app/thumbs/1/test1.jpg');

$response = $service->thumbnails->set($videoId, [
    'mimeType' =>  'image/jpeg',
    'data' =>  file_get_contents($newThumbnailPath)
]);

dd($response);

Response error:
{
  "error": {
    "code": 403,
    "message": "The thumbnail can't be set for the specified video. The request might not be properly authorized.",
    "errors": [
      {
        "message": "The thumbnail can't be set for the specified video. The request might not be properly authorized.",
        "domain": "youtube.thumbnail",
        "reason": "forbidden",
        "location": "videoId",
        "locationType": "parameter"
      }
    ]
  }
}

Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!

Hi @icarojobs , thanks for raising the issue.
Please make sure your account is verified. For more info, see:

https://support.google.com/youtube/answer/72431
https://stackoverflow.com/questions/38636310/set-custom-thumbnail-via-youtubeapi-doesnt-work-can-someone-tell-me-why

Hi @icarojobs , thanks for raising the issue.
Please make sure your account is verified. For more info, see:

https://support.google.com/youtube/answer/72431
https://stackoverflow.com/questions/38636310/set-custom-thumbnail-via-youtubeapi-doesnt-work-can-someone-tell-me-why

Wow! This worked! Thank you! 🔥🚀


feat(BigOperators/Fin): Sum/product over Fin intervals

This PR adds new theorems about the sum/product of some vector over Fin intervals. One example is:
@[to_additive]
theorem prod_Iic_succ (i : Fin n) :
    ∏ j ∈ Iic i.succ, v j = (∏ j ∈ Iic i.castSucc, v j) * v i.succ

This is in preparation for reworking finSigmaFinEquiv and finProdFinEquiv in #19013.

Sorry, won't be able to review before a week or so


image picker: select an icon previously uploaded by the organization admin

fix https://github.com/CartoDB/cartodb/issues/11462
added the organization uploads tab to the image picker

I didn't cover the case of icon upload by the organization admin, as I think it fails out of the scope of the issue, but it could be extended afterwards to support this (and better resemble the "Your icons" tabs)

acceptance

add an icon as an organization admin
and use it in the map
if the user doesn't belong to an organization, it shouldn't appear at all

quite advanced on this, do we have an state for the case when the organization doesn't have any icon uploaded yet? @xavijam @javierarce

the first thing that came to my mind was not showing the tab at all, but it is after the modal is rendered that the organization icons are fetched :/

That's a good one, don't we have a 0 results state? have you seen it in the designs @javierarce?

No, I'm afraid we don't have it / I haven't seen it.

Let's go to the source of truth, design 🍡 .

I guess hiding the tab in case the user didn't have any assets would be the best solution, but that would require an extra call.

if we can afford that extra call I'm down to follow that path of thinking

Fine by me, go ahead!

now the tab would only appear if the User is an Organization user and the organization icons collection is not empty
we need to make two extra calls (the organization icons collection, and the user icons collection, which we had to extract) but further requests are cached

I encourage you how, for example, we code the add widget modal, where several requests are needed before render the view displaying a new state. For me it should work in the same way, if possible (take into account this modal will be the main modal in the future, so better to make it properly than other thing).

roger!

I tried to go full widgets implementation, but there's no model related to fetched collections to rely on, and after replicating the bodyView and that stuff I trimmed back to something quite similar
anyways, I took into account the $.when suggestion (and fixed the tests)
https://github.com/CartoDB/cartodb/pull/11492/files#diff-f6ad32d8aa3da552f4ab34d6b38853a1R114

Hey, I suggested you to not follow the same solution, just take it as an example :).
Question, if the user doesn't belong to an organization, organization icons fetch fails or it returns an empty array? I guess we don't show the error state in that case right?

no prob! my bad for trying too far. If the user doesn't belong to the organization, the array of collections to apply fetch will only containuserAssetCollection, thus no errors and only the "your uploads" tab will be shown
(solving the conflicts now to move on)

:+1:

I went ahed and included the change for the findWhere. Feel free to act on the other two comments :)

Nice one, let's go to acceptance?

A member of the organization selects an icon to style a marker.
The organization removes that particular icon from the ones it offers.

If that happens and the user goes back to the icon modal and to the organization tab, the "set button" will be enabled, but there won't be any icon selected.
There's also the issue of having a map with an icon that no longer exists (only in the cache).

About the icon removed and how the fill component will look like, it is a good question. @CartoDB/design what do you think?
Further to the last "question", it is something already discussed and there is a big and great warning in the organization side. We decided to not do it nothing else for the moment (https://github.com/CartoDB/cartodb/pull/11292#issuecomment-273751733).

@noguerol's call

Can't we just go back to a default bubble whenever a map with missing icon is loaded?

@noguerol I don't think that's an easy thing to do right now, since we'd need to store the previous size somewhere.

Acceptance
I've discovered a big issue with this PR. It seems that uploading a custom icon as a regular user, doesn't refresh the list of icons in the modal :(

d'oh, very well spotted as I think I only tested this as owner :((( move to development then andI'll take as soon as I can

Oh, don't worry, I'll fix it and ask you for help if I need it.

Back to CR! I've addressed the problems (1 and 2) found in Acceptance.
Props to @matallo for the help me debugging one of the problems.

Taking a look @javierarce 💋

OK, so if found one little issue and one thing that concerns me:
a, the issue: on the organizational settings, the copy for deleting an icon is in plural ("delete icons"), while it only deletes one icon, so is confusing as it seems it will erase them all
b. the concern: I understand the dont-break-maps policy when removing an organizational because is very difficult to know how many maps use them, but I can't find a reason to still render a map with an icon that has been deleted when its opened on Builder. On that situation I think we can afford to do it and will be better whatever the use case is.

@noguerol
a. It is not related with this PR (check description of this pull request), if you consider it is confusing, please open a new ticket.
b. we already discuss that and we took a decission. Weren't you in that thread?. What's your proposal?

Understood. Opening two new tickets, lets move this to production.

💋

merging and bumping assets in master


Blunderbuss: don't panic if less than 4 lines changed

Basically the code does:
    log := math.Log10($NUM_LINES_CHANGED)
    logPlus := log + .5
    fileWeight := int64(logPlus)

So lets assume that $NUM_LINES_CHANGED == 3.
    log        == 0.4771212547196624
    logPlus    == 0.9771212547196624
    fileWeight == 0

This means that further on weightSum (and other things) will be calculated by
a multiple by fileWeight and thus will get the value of 0. Both
100.0*float64(potentialOwners[cur])/float64(weightSum)
and
selection := rand.Int63n(weightSum)
Will cause a panic if weightSum == 0
I solve this by adding 1 to the fileWeight after it is truncated to
int64. So we can never get a value of 0.

@lavalamp since I think you wrote this part that is panic-ing....

Oops. I should add one after truncation to int.

@lavalamp ok, will fix it that way.

@lavalamp updated that way.

(although i'm panic-ing on 13901 now. debugging)

Somehow it is getting
"cluster/docker-cluster/.gitignore" fileWeight: -9223372036854775807

It must be overflowing an int64. Hm.

*fileChanges == 0 WTF?
fileWeight := int64(1)
    if file.Changes != nil {
        fileWeight = int64(*file.Changes)
}

Hm, maybe a rename?

Create cluster/baremetal/.gitignore
https://github.com/ZJU-SEL/kubernetes/commit/bf2f19bcb10e1944fd9c60c6456c841aedc858b4
Mv cluster/baremetal/.gitignore to cluster/docker-cluster/.gitignore
https://github.com/ZJU-SEL/kubernetes/commit/0c620ac8d387a3cf19e9668fe5f44b484b59291e
cluster/baremetal/.gitignore  Changes:2 Additions:2 Deletions:0
cluster/docker-cluster/.gitignore Changes:0 Additions:0 Deletions:0

Apparently log10(0) != panic()
How about we just skip any files where Changes = 0?

re-running, but this fixes the 2 I've found so far...

I had 1 clean run through the repo (with --dry-run)

LGTM

OK, I'll merge and restart this soon, then.

#88


"Current working directory is not a Cordova-based project."

Following the getting started instructions, I'm running into this error on step 3 when I try to run: ionic platform add android
My server is Ubuntu 14.04 LTS

I had the same issue, and the problem went away after I added an empty www folder. The thing is that www is in .gitignore so when you git clone a project everything is there and set up, except www. :D

mkdir www solved the problem for me, too (thanks @devakone!)
I have a different app structure than what cordova creates (and expects).


Replaced 'xcopy' Exec task with the more universal Copy task to suppo…

…rt OS's which do not have xcopy.
PR Details
Replaced 'xcopy' Exec task with the more universal Copy task to support OS's which do not have xcopy.
Description
Added a new ItemGroup called BuiltItems that includes the entire set of output in the TargetDir. Then I created a new Target called CopyFiles, which, after the PostBuildEvent, copies the set of files in BuiltItems to the appropriate deps folder.
Related Issue

Motivation and Context
xcopy is a Windows-specific tool which does not exist on Linux. To move towards a Linux build pipeline we'll need to gradually remove any such Windows-only dependencies.
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Looks good, thanks.


MF-1034 - Wrapping MQTT client

Signed-off-by: Ivan Milosevic<EMAIL_ADDRESS>What does this do?
Which issue(s) does this PR fix/relate to?
Put here Resolves #1034  to auto-close the issue that your PR fixes (if such)
List any changes that modify/break current functionality
Have you included tests for your changes?
Did you document any new/modified functionality?
Notes

Codecov Report

Merging #1318 (d991e2e) into master (3eca692) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1318   +/-   ##
=======================================
  Coverage   59.79%   59.79%
=======================================
  Files         113      113
  Lines        8797     8797
=======================================
  Hits         5260     5260
  Misses       3080     3080
  Partials      457      457

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 3eca692...d991e2e. Read the comment docs.

Codecov Report

Merging #1318 (d991e2e) into master (3eca692) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1318   +/-   ##
=======================================
  Coverage   59.79%   59.79%
=======================================
  Files         113      113
  Lines        8797     8797
=======================================
  Hits         5260     5260
  Misses       3080     3080
  Partials      457      457

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 3eca692...d991e2e. Read the comment docs.


fix tracking of multiply trimmed boundaries

Hopefully fixes #104, needs checking.

Coverage decreased (-0.0002%) to 66.148% when pulling 1539d26f77d8931b1859e5e175920768315600f8 on gertjanvanzwieten:fixtrimgroups into d0abf370e9b9e4fc42228c63ce83cf40a7e7f9a7 on nutils:master.

Coverage increased (+0.2%) to 66.3% when pulling dc7b827fc58bde792ca1c443980308ff8a48e628 on gertjanvanzwieten:fixtrimgroups into d0abf370e9b9e4fc42228c63ce83cf40a7e7f9a7 on nutils:master.


refactor: simplify working with trivia tokens in LPL

This patch removes a lot of boilerplate related to working with trivia tokens during resilient syntax tree parsing by introducing trivia-aware combinators as well as abstracting a lot of code in LPL itself. It also happens to improve TMDL parser's performance by ~9%.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

481 of 518 (92.86%)  changed or added relevant lines in 8 files are covered.
26 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.7%) to 87.302%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lpl/src/debug.rs
0
1
0.0%

lpl/src/diagnostic.rs
0
1
0.0%

tmdl/src/syntax_kind.rs
5
6
83.33%

tmdl/src/parser.rs
374
376
99.47%

lpl/src/syntax.rs
8
23
34.78%

lpl/src/parse_stream.rs
29
46
63.04%

Files with Coverage Reduction
New Missed Lines
%

lpl/src/combinators/flatten.rs
26
54.84%

Totals

Change from base Build<PHONE_NUMBER>5:
-0.7%

Covered Lines:
5576

Relevant Lines:
6387

💛  - Coveralls


ENH: constants: Add Muon Gyromagnetic ratio

Is your feature request related to a problem? Please describe.
It would be useful to have the Muon gyromagnetic ratio as a constant in scipy.constants.physical_constants. Scipy already has the the gyromagnetic ratios for a neutron and proton. See here: https://docs.scipy.org/doc/scipy/reference/constants.html
Describe the solution you'd like.
At the moment, I am needing to calculate the gyromagnetic ratio using the following code:
from scipy.constants import elementary_charge, physical_constants

MUON_GYROMAGNETIC_RATIO = physical_constants["muon g factor"][0] * - elementary_charge / (2 * physical_constants["muon mass"][0] * 1e6)  # MHz / T

but I would like to do something like
from scipy.constants import physical_constants

MUON_GYROMAGNETIC_RATIO = physical_constants["muon gyromag. ratio in MHz/T"][0]

Describe alternatives you've considered.
No response
Additional context (e.g. screenshots, GIFs)
No response

Cc @jakobjakobson13 for input/visibility.

Cc @jakobjakobson13 for input/visibility.

That's up to you. I, in my personal opinion, would only include the bare constants provided by CODATA (as it is a "higher" authority and therefore its selection of constants can be considered more "meaningful"/"correct"/"scientifically proven") in scipy.
From a practical point of view, the inclusion of a MUON_GYROMAGNETIC_RATIO is no big deal as it is one line.

Thanks for the proposal @robertapplin and for the feedback @jakobjakobson13.

I, in my personal opinion, would only include the bare constants provided by CODATA (as it is a "higher" authority and therefore its selection of constants can be considered more "meaningful"/"correct"/"scientifically proven") in scipy.

This has been our stance/policy on other feature requests for scipy.constants in the past. It hasn't come up in a few years, but I agree with your opinion here - there is no good way to draw a line otherwise. Hence I will close this issue.


docs(api): Fix description of run log payload

Overview
While working on #13709, I noticed some outdated documentation for opentrons.simulate.simulate() and opentrons.execute.execute().
The docs say you're supposed to do this:
command = ...  # get from opentrons.simulate.simulate() or opentrons.execute.execute()

run_log_text = command["payload"]["text"].format(command["payload"])

However, it's apparently been simplified to this now:
command = ... # get from opentrons.simulate.simulate() or opentrons.execute.execute()

run_log_text = command["payload"]["text"]

I'm not sure how long this has been the case. PR #9799 suggests it's at least since v5.0.2 but doesn't provide further details ("text field is not a format string anymore"). I tried some Git archeology, but I couldn't get to the bottom of it quickly.
Unfortunately, if you try to do the old .format() thing today, it's actively harmful. If the string happens to contain any { or } characters, it will confuse .format() and raise a KeyError. This happens for Thermocycler commands (see issue #9988), and of course it can happen for ProtocolContext.comment() commands.
Test Plan

Preview changes on http://sandbox.docs.opentrons.com/fix_payload_docs/v2/.

http://sandbox.docs.opentrons.com/fix_payload_docs/v2/new_protocol_api.html#opentrons.simulate.simulate
http://sandbox.docs.opentrons.com/fix_payload_docs/v2/new_protocol_api.html#opentrons.execute.execute

Changelog

Document that you should just do command["payload"]["text"].
Document that you should no longer do command["payload"]["text"].format(command["payload"]).

Review requests

Do you see any other places where we encourage the .format() thing? Anything in the Support help center? Any demo files floating around?
Does my flowery prose inspire joy in the depths of your heart?

Risk assessment
Low.

Failing tests appear to all be flaky Thermocycler integration tests.


Allow user to define ACLs for OpenStack keys

The openstack_keys structure now supports a key called acls whose value is a list of strings that one could
pass to setfacl. The ansible ACL module applies the ACLs to all openstack keys with this property.
Fixes: #1688

FAIL - luminous-ansible2.2-docker_dmcrypt_journal_collocation

Of the 18 failing tests:

13 were "vagrant: command not found"
1 was "org.kohsuke.github.HttpException: Server returned HTTP response code: -1,"
(ceph-ansible-prs-luminous-ansible2.2-docker_dmcrypt_journal_collocation)

For the four that actually ran the job I will send a new PR. Two of them uncovered a case that should have been obvious to me before I sent the PR (when acls isn't set):

https://jenkins.ceph.com/job/ceph-ansible-prs-luminous-ansible2.2-docker_cluster/186/console
https://jenkins.ceph.com/job/ceph-ansible-prs-luminous-ansible2.2-purge_docker_cluster/185/console

The other two are permissions errors and likely related to key creation and legit bugs for my PR: librados: client.bootstrap-osd authentication error (1) Operation not permitted

https://jenkins.ceph.com/job/ceph-ansible-prs-luminous-ansible2.2-bluestore_cluster/182/console
https://jenkins.ceph.com/job/ceph-ansible-prs-jewel-ansible2.2-update_cluster/778/console

jenkins test this please

jenkins test jewel-ansible2.2-xenial_cluster

jenkins test luminous-ansible2.2-centos7_cluster

jenkins test luminous-ansible2.2-bluestore_docker_cluster

jenkins test luminous-ansible2.2-xenial_cluster

jenkins test luminous-ansible2.2-xenial_cluster


[Suggestion] Turbine coil rebalancing

The turbine coils are currently very unbalanced.
One can do just copper and silver coils and get a lot of efficiency without the more expensive coils.
Based on that I wanted to suggest a rebalance to bring the coils more in line:
Silver 110% -> 95%
Gold 105% -> 100%
Magnesium 100% -> 105%
Aluminum 95% -> 110%
(Basically switch silver and aluminum, gold and magnesium coil efficiencies)

0.7.1


design docs folder seeding

Looks like one of the docs by @karlkfi is a design doc and we can move that as an example of where public design docs can go.
In addition the change to remove the internal shortcut http://cloud from an external doc.

It’s not a design doc. Design docs are written before implementation to propose a feature. This is a usage doc, describing the feature to users and maintainers.


[Wishlist] Randomize tracker order for each torrent file

Would be nice if there was a -U option to randomize the tracker list order for each torrent file in order to load balance tracker traffic. Options to randomize tracker groups (double spaced), randomize the group (single spaced), maybe a third option for both.
For example, a single spaced list randomized for each torrent, with a reasonably even random distribution, each tracker would only receive (1/totaltrackers)*amounttorrents updates at any one time.

There is a new release V1.32.0-RC.5
There is already a sort tracker list torrent option.
Now I have also added randomize tracker selection: -U7
This function is also available under update menu item.


fixed urlib3 version as per dependabot alert

Issue #, if available:
Description of changes:
fixed urlib3 version as per dependabot alert
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: 68c3667d659fdbd288d1353c633b624f7d464141
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


adobe-air-sdk: migrate to Caskroom

https://github.com/caskroom/homebrew-cask/issues/23938
Cask at https://github.com/caskroom/homebrew-cask/pull/23942
@MikeMcQuaid is this the right way to do things?

@adidalal One comment otherwise 👍

Updated

Thanks @adidalal!


test

wanna add gentleness to "yor good point" assessment!

haoa~

this is commit log

fixed with ${2f78d54}


Allow development on a freshly installed Windows 10

Remove hard-coded paths to SDK folder, and in one case, just update the list of SDKs to look for.
With this PR, the appveyor build runs on my fresh install of Windows 10/VS2015.
Fixes #561
The errors in #561 stemmed from inability to find the SDK utils, so strong-name validation was not turned off for the assemblies that are usually strong-named.

Nice ... I like it.  I will try it out shortly but it looks pretty fine.
Thank you
Kevin

Looks good

Committed, thank you for your contribution.


Return error on tail.Cleanup

Pass through the error of fsnotify/fsnotify#Watcher.Remove to check if clean up was successful.

@bahlo thanks for your contribution.


Better accessibility

Typemill needs improvements on its accessibility, can we collaborate on this?

Yes, highly welcome! I don't have a lot of time right now but let us try to improve it step by step.


Pushing DF up to PWR repo

DF changes merging upstream to PWR dev branch.

Merging pull request from Disaster Faster branch.


Again Update topdeals.js

I have added prices , ratings , discounts and brands on the flipkart clone to make it more attractive and user friendly.

plz do the same things in the updated website. ok

sir , that's what i am not able to understand what is this mean?
From where ?

It would be great sir @arghadipmanna101 , if you tell from where i have to make changes. please sir , thank you

DM me in LinkedIn .ok @kuritika098

ok sir


allowPublicClient in App Registration for Auth Code Flow

Please follow the issue template below. Failure to do so will result in a delay in answering your question.
Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Documentation location

[x] docs.microsoft.com
[x] MSAL.js Github Wiki
[ ] README file
[ ] Other (please fill in)
[ ] Documentation does not exist

Description
I am now using msal-browser 2.4.
My app registration has two redirect uris of type Spa, one for my server and one http://localhost.
My app registration has the allowPublicClient to null (or false in the UI)
Running locally (localhost), everything is OK.
Running from the server, I get the AADB2C90058 error (The provided application is not configured to allow public clients )
I found out, from a blog concerning another lib, that I need to have allowPublicClient set to true.
I did not see any mention of this neither in this repo or on Microsoft's website.
Am I doing something wrong?

@CerosDev If allowPublicClient is null, then it is assumed that your client is Confidential. msal-browser supports only PublicClientApplications with PKCE. Thanks for bringing this to our attention, we will add this to our docs.

@hamiltonha Is this something we can add to Microsoft docs?

@sameerag @hamiltonha  I'd like to also point out that according to this doc:

Do NOT select either checkbox under Implicit grant.

Which totally brake the id_hint_token invitation flow  with this error:

AADB2C90057 The provided application is not configured to allow the OAuth Implicit flow.

@nickgmicrosoft Can you update the docs/app registration experience to call out the nuances with the invite flow?

Hi all, there's currently a limitation for Azure AD B2C in which the service relies purely on the access token checkbox to enable both ID token and access token implicit requests. For Azure AD B2C, you have to check that checkbox, regardless of whether you'll use ID token/implicit flow or not.
We're exploring options to update the documentation and portal experience updates to reflect this while this is the case.

Closing this as there is no immediate work for msal team. @nickgmicrosoft please track this in the B2C portal activities as needed.

Closing this as there is no immediate work for msal team. @nickgmicrosoft please track this in the B2C portal activities as needed.


Camera underground controls

Opening this PR for early testing. There's still some work to be done, especially for panning. While I had the urge to rewrite ScreenSpaceCameraController I took the opposite approach and just modified camera behavior when underground. Above ground controls should be the mostly same, for better or for worse.
At a high level the changes include:

Added ability to zoom into the ground, like submerging below the terrain. This happens by default if enableCollisionDetection is false and minimumZoomDistance is greater than 0.0. I'm occasionally noticing large jumps which I still need to fix.
Changed zooming, rotating, and panning behavior when underground. There's a new property in ScreenSpaceCameraController called undergroundSurfaceHeight which acts as an invisible ellipsoid that's used to improve camera navigation when underground. For best results the height should be set just below the height of underground entities in the scene.
When underground, the zoom distance is now determined by the position over the mouse's cursor rather than the position at the center of the screen. This should make it a lot easier to navigate to underground datasets.
Fixed what seemed like a kludge in the camera panning code which had the side effect of panning every other frame. Basically panning felt like 30hz while other camera controls felt like 60hz. Panning feels so much smoother now.

Local sandcastle for testing

@fredj @gberaudo

Thanks for the pull request @lilleyse!

:heavy_check_mark: Signed CLA found.
:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I pretty much have the underground navigation where I want it now. Tomorrow I'll do some final testing and then bump @IanLilleyT for review.

Right click (zoom) sometimes moves in an unexpected direction, as if it's both strafing and zooming, and will sometimes fix itself mid-zoom (haven't found a consistent repro, just click different spots on the screen and zoom in and out quickly and it's bound to happen eventually).

The only time I see this is when there's inertia from a pan still happening.

At this point a lot of the remaining problems are caused by multiple actions happening simultaneously, usually because of inertia.
Fixed one pretty serious bug last night where zooming past the pan ellipsoid causes the camera to pan extremely far away. This happens in master too and could explain unexpected camera jumps.
The next set of things to look at are strafing + zooming and zooming + tilting combinations like https://github.com/CesiumGS/cesium/pull/8811#issuecomment-635004308. These also happen in master but become more noticeable when underground.

@IanLilleyT ready for another look

The recent changes made the underground camera controls more stable and even fixed a couple problems with existing above ground code, so this is good to go, thanks @lilleyse !


Added a basic REPL

It looks like your parser program doesn't actually do anything. I tested it with Text.Megaparsec.parseTest and there doesn't seem to be any output.
I've also added a readme and a license (MIT).
Feedback on how to improve my haskell would be greatly appreciated.

You're right, the parser is broken. it's not my strong point tbh.
I've made some other changes, like parameterising the AST and Form types with the type of runtime data.


Re-equipping armor multiple times causes the effects to stack

I found a bug that only works on servers for some reason (I am using ketting server 1.20.1)
I have tested this in singleplayer and it does not work, but I also tested multiplayer with no plugins but it still happens
It seems to only work when you apply gems to an item, then spam re equip it.
Video of what happens:
https://github.com/user-attachments/assets/f3e49a44-5cec-4b68-9173-b6386bf5fce2

This is probably an issue with the forge/spigot hybrid server you're using. You can see if they would like to investigate it, but I will not.


hideTabBar is broken when used in nested stacks/scenes

Version
Tell us which versions you are using:

react-native-router-flux v4.0.2 (latest master)
react-native v0.56.0 (Example App)

Expected behaviour
hideTabBar on any Scene hides TabBar when that Scene is presented (as previously)
Actual behaviour
TabBar keeps on showing
Steps to reproduce
Slightly modified the Example app, added tabs to the root Stack, and added hideTabBar to the register Scenes, I have the same structure in my app. Previously using 4.0.0-beta.28, TabBar was hidden when the Scene with hideTabBar got presented, now it isn't.
      <Stack hideNavBar tabs key="root" titleStyle={{ alignSelf: 'center' }}>
        <Scene key="echo" back clone component={EchoView} getTitle={({ navigation }) => navigation.state.key} />
        <Scene key="launch" component={Launch} title="Launch" initial />
        <Stack key="customNavBar" hideTabBar titleStyle={{ alignSelf: 'center' }}>
          <Scene key="customNavBar1" title="CustomNavBar 1" navBar={CustomNavBar} component={CustomNavBarView} back />
          <Scene key="customNavBar2" title="CustomNavBar 2" navBar={CustomNavBar} component={CustomNavBarView} back />
          <Scene key="customNavBar3" title="Another CustomNavBar" navBar={CustomNavBar2} component={CustomNavBarView} back />
          <Scene key="hiddenNavBar" title="hiddenNavBar" component={CustomNavBarView} hideNavBar={true} back />
        </Stack>
        <Stack back backTitle="Back" key="register" duration={0} navTransparent>
          <Scene key="_register" hideTabBar component={Register} title="Register" />
          <Scene key="register2" hideTabBar component={Register} title="Register2" />
          <Scene key="home" component={Home} title="Replace" type={ActionConst.REPLACE} />
        </Stack>

I had the same issue too
Version
react-native-router-flux v4.0.1
    <Drawer
      key="root"
      contentComponent={Sidebar}
      headerMode="none"
    >
      <Tabs key="myTabBar">
        <Scene key="tab_1" tabBarLabel="home">
          <Stack>
            <Scene key="home" component={Home} />
            <Scene key="blankPage" component={BlankPage} />
            <Scene key="listPage" component={ListPage} hideTabBar={true} /> // not work
          </Stack>
        </Scene>
        <Scene key="tab_2" tabBarLabel="BlankPage">
          <Stack>
            <Scene key="blankPage" component={BlankPage} />
          </Stack>
        </Scene>
      </Tabs>
    </Drawer>

That is working in the Example code with the most recent version.

Please, take a look there, and in case you found a bug, or was able to reproduce this there, reopen this ticket with the failing example.

@daviscabral I'm sorry but I don't really see the hideTabBar in your screenshot of code (Cmd+F didn't work so I can't be sure), both of us above provided broken examples, mine is straight out of the Example app. But to make it straightforward, here's the full modified Example app: https://github.com/R1ckye/rnrf-broken
Just go to the register screen, it should hide the tab bar (it has hideTabBar) but it doesn't.

Sorry - I misread the issue and the prop - I read it as hideNavBar - as the hide the navigation bar - and not the tab bar.
But I got your code here - and there is no hideTabBar in your example as well.
            <Stack back backTitle="Back" key="register" duration={0} navTransparent>
              <Scene key="_register" component={Register} title="Register" />
              <Scene key="register2" component={Register} title="Register2" />
              <Scene key="home" component={Home} title="Replace" type={ActionConst.REPLACE} />
            </Stack>

Check this out: https://github.com/aksonov/react-native-router-flux/issues/2076.

@daviscabral That issue is more than a year old, and as mentioned above by both of us, it was working exactly this way in late betas of 4.0.0, but not anymore

I pinpointed the issue, it was broken in this commit, when react-navigation was bumped from 1.5.8 to 2.8.0
https://github.com/aksonov/react-native-router-flux/commit/d61960c6bf0139150a327a161b3d9374c6d6772f
Can you please reopen, as it's clearly a valid, existing issue?

In my case, I use Actions.refresh({ hideTabBar: true }) dinamically inside of the scene.
Like when the keyboard shows up, or under an onPress Button event...
With the RF 4.0.1, this option was not working.
Downgraded to 4.0.0-beta.28 and my problem got fixed.

Yes, I belive that's because 4.0.0-beta-28 uses<EMAIL_ADDRESS>- and the final 4.0 version uses<EMAIL_ADDRESS>We will need to see what else is broken/deprecated - and maybe update the API.

confirmed that it doesn't work for me also

I got it working in the PR that is opened: [](https://gyazo.com/664563f57ca5a9b25a57e41c5d793359

I still got the problem.
I tried your solution @daviscabral but it didn't work in my case. I'll try to investigate in the next few days, starting by your updated example.
Thank you for your time :)

Great - in case you find a bug, please open an issue with as many details as possible :+1:


Do-Nothing Boundary Condition

Hi, my private Trixi-wizard suggested to report the following probably erroneous behavior: I am interested to model "open boundaries" by using the flag boundary_condition_do_nothing provided by Trixi.jl, for instance with
boundary_conditions = ( x_pos = boundary_condition_do_nothing,
                        x_neg = boundary_condition_do_nothing,
                        y_pos = BoundaryConditionDirichlet(initial_condition),
                        y_neg = BoundaryConditionDirichlet(initial_condition))

also using Dirichlet data. This leads to a crash after a few time steps.
The error can be reproduced on the example elixir_euler_blast_wave.jl where I add the boundary condition block above in line 37, and include periodicity=false in the call of TreeMesh() and boundary_conditions = boundary_conditions in the call of SemidiscretizationHyperbolic().
Funny enough, the boundary conditions work if boundary_condition_do_nothing is used only once on either x_pos or y_pos and all other sides are Dirichlet. It crashes if it used only once but on x_neg or y_neg. It also crashes with do-nothing only on the two y-sides or on all sides. All sides with Dirichlet also works fine.
Sorry, but I did not investigate the actual solutions, only checked crash/no-crash.

Thanks for the report. We should check whether it's an implementation issue or whether it's just the behavior of the numerical scheme. Our boundary_condition_do_nothing is just a crude way, computing the boundary flux purely from the inner state - without any stability guarantees in the general case.

It is most certainly an implementation issue. You can try the above example, but set the initial conditions to constants. Using the boundary flux from the inner state should be equivalent to using Dirichlet data from the initial condition. But it crashes.
I suspect the implementation of the boundary flux gets the orientation of the wall wrong.

I can confirm this. There is something fishy going on. I hope to have a fix soon. Thanks for reporting this!

Hi @torrilhon! The current main branch contains a fix so that the elixir you mentioned at least runs through without crashing. Let me please know if there are still problems.
We will release a new version of Trixi.jl soon. If you want to try it our directly, you can for example run
using Pkg; Pkg.develop("Trixi")

to get a local clone of Trixi.jl and use that to check out the current main branch.


Make C# work without visual studio.and with mono

Xunit VS runner is tied to csproj for now
Need xunit console runner
use paket? (/!\ is it ok for everyone to use console too much...)

I have add initialize script to restore package, and checkTests script to run unit tests in V2.3


Update rubocop config for rubocop 0.54.

@ab rubocop has had a few bumps in recent months: https://github.com/rubocop-hq/rubocop/releases
thoughts on dropping ruby 2.0 support for these specs?  https://www.jetbrains.com/research/devecosystem-2018/ruby/
just added #686 and some of these changes are preventing tests from running.


JsonObject.getFloat() will fail if the property appears to be an Integer

import ceylon.json {
    JsonObject,
    parse
}

shared void jsonTest() {
    value json = "{ \"x\": 10.0, \"y\": 10 }";
    value o = parse(json);
    assert (is JsonObject o );
    Float x = o.getFloat("x");
    Float y = o.getFloat("y"); // Fails here
}

In JSON (and JS) there are only numbers, and no distinction between Float and Integer, so it's a little bit of an impedance mismatch. (And one that is kind of tedious to work around.) It would be nice to have getFloat() return value.float in the case of the parsed value being an Integer.

So the options are:

Have getFloat() coerce using value.float (throws if the integer's magnitude can't be exactly represented as a float
Have getFloat() coerce using value.nearestFloat (accept loss of precision)
Add getNumber() that uses value.nearestFloat

I think 3 would be best. With 1, exceptions for large numbers would be surprising (a trailing .0 isn't meaningful in JSON AFIACT). A JSON serializer very well may leave off the .0, and in fact the "integer" value's source may be a double precision float that has no fractional part because it is so large. So in fact, the precision would already be lost.

@gavinking fixed and closed this issue while I was typing the above :)
But I think the issue of not throwing on large magnitudes should be carefully considered.

@gavinking suggested this issue could be reopened for further discussion. So...
I really think people would expect nearestFloat. By calling a parse function that returns a Float, the programmer is implicitly accepting the precision offered by Float, and that they don’t expect or require an exact integral result.
In fact, even if the string contains a ., the Float you get back may have loss of precision.
Usually, a schema is agreed upon by the producer and consumer of data. But in this case, the producer has no means to differentiate between integers and floats. There are only numbers. We must accept this to be true, as it is the very basis for this issue. Sometimes data providers leave off the .0!
Therefore, it is the consumer's job to provide the data schema. And if the consumer declares the field a Float, then in Ceylon terms, the value should have an implicit .0 if a fractional part does not already exist.

then in Ceylon terms, the value should have an implicit .0 if a fractional part does not already exist.

I guess that means that we should really defer parsing until we know what the consumer wants, so values > 2^63 can be handled.

So I guess for very large magnitudes, the difference in precision overflow is to me kind of arbitrary. At a certain number of bytes, the integer becomes too large to be turned into a Float without losing precision, but add a few more bytes in there and you get too high to represent as an Integer, too.
So I guess the question is: if the caller requests an Integer and the number is > 2^63, would we return the nearest Integer? Or would we throw an overflow exception? (Or something else?)
I think ideally we would always parse numbers as arbitrary-precision, and only do the conversion when converting to the final data type. But AFAIK Ceylon doesn't support those (yet?), and I'm not totally certain the overhead is really worth it anyways.

always parse numbers as arbitrary-precision

I think it's better to figure out what we want, and then figure out how. But I don't think arbitrary precision parsing is necessary. It may be as simple as initially parsing large magnitude values as Floats.
In fact, this issue highlights that what we currently have isn't great:
import ceylon.json { ... }

shared void run() {
    value json = "{ \"x\":<PHONE_NUMBER>854775808 }";
    assert (is JsonObject o = parse(json));
    print(o.getInteger("x"));
}

produces<PHONE_NUMBER>854778000 on JS and throws on parse on Java. Instead, it should probably parse as a Float on both platforms (since it is too large), and throw on getInteger()

I guess the real question is this: Should the user be made aware when a loss of precision would happen? If a number is too large to fit in an Integer, it's certainly too large to fit into a Float without losing precision.
Of course, if we had a number like pi that went out a few hundred decimal places, would that throw any type of exception on getFloat()?

Of course, if we had a number like pi that went out a few hundred decimal places, would that throw any type of exception on getFloat()?

Right. And IEEE floats are pretty much just approximations anyway, especially when represented in decimal form. Attempting to identify meaningful losses of precision for conversions from decimal strings is basically impossible.

I pushed a couple changes consistent with the idea that even though a JSON number doesn't include a ., we may want to treat it as a Ceylon Float. See the commit messages for more detail. If there are objections, the commits can easily be reverted.
Closing (at least for now...)


Add parser

add extra data parser and dump command

Parse

Can parse extra data, go_type, column_name, column_type. for example

  test_multitype:
    title: test multitype
    type: integer
    go_type: int
    column:
      name: test multitype
      db_type: int
      foreign_key:
        name: fk

this JSON Schema(yaml) file convert into a inter-generate go-jstmpl data structure
such that...

- ColumnName: test multitype
  ColumnType: int
  GoType: int
  Name: TestMultitype
  Type: number

this is good for writing text template, make easy

Dump

add dump command, it is required a file path, or stdout specification

Fix done!

@minodisk add!


scala.meta.tokenizers.TokenizeException

scala.meta.tokenizers.TokenizeException: jar:file:///C:/Users/partens/AppData/Local/Coursier/cache/v1/https/packages.corp.com/artifactory/maven/ai/dragonfly/slash_3/0.1/slash_3-0.1-sources.jar!/ai/dragonfly/math/Constant.scala:25: error: illegal character '\ud835'
  val 𝜑: Double = 1.46557123187676802665 // Golden

I think there is enough in that snippet (import the artefact into scala-cli) to reproduce this. I can provide more info if requred.

I think then that this is close-expected-behaviour? Thanks for looking... I've sent a PR to simplify that char out the library.

Scalameta ought to support surrogate unicode characters, since the compiler does, so I would think the ticket should remain open.


go: Remove old version 1.8

Motivation for this change
Follow up PR to https://github.com/NixOS/nixpkgs/pull/35327
According to https://golang.org/doc/devel/release.html#policy only the two latest releases are supported an 1.10 is out.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

cc go maintainers @cstrahan @orivej @wkennington
cc perkeep maintainer @cstrahan
cc cockroachdb maintainer @rushmorem

Failure on aarch64-linux (full log)
Partial log (click to expand)
Package ‘cockroach-1.1.5’ in /var/lib/gc-of-borg/nix-test-rs-1/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-1/pkgs/servers/sql/cockroachdb/default.nix:38 is not supported on ‘aarch64-linux’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-darwin (full log)
Partial log (click to expand)
github.com/cockroachdb/cockroach/pkg/sql/jobs
github.com/cockroachdb/cockroach/pkg/ts
go build github.com/cockroachdb/cockroach/pkg/server/status: invalid flag in #cgo LDFLAGS: -u_je_zone_register
github.com/cockroachdb/cockroach/pkg/sql/distsqlrun
github.com/cockroachdb/cockroach/pkg/sql/distsqlplan
make[1]: *** [Makefile:177: buildoss] Error 1
make[1]: Leaving directory '/private/tmp/nix-build-cockroach-1.1.5.drv-0/go/src/github.com/cockroachdb/cockroach/src/github.com/cockroachdb/cockroach'
make: *** [Makefile:3: buildoss] Error 2
builder for '/nix/store/ph5kbil0nxxx6p6009b9z0h5lfy3vx21-cockroach-1.1.5.drv' failed with exit code 2
error: build of '/nix/store/ph5kbil0nxxx6p6009b9z0h5lfy3vx21-cockroach-1.1.5.drv' failed

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/x65nnf9bzv8lmia0sh6arg79bipsabwr-cockroach-1.1.5-bin
shrinking /nix/store/x65nnf9bzv8lmia0sh6arg79bipsabwr-cockroach-1.1.5-bin/bin/cockroach
gzipping man pages under /nix/store/x65nnf9bzv8lmia0sh6arg79bipsabwr-cockroach-1.1.5-bin/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/x65nnf9bzv8lmia0sh6arg79bipsabwr-cockroach-1.1.5-bin/bin
patching script interpreter paths in /nix/store/x65nnf9bzv8lmia0sh6arg79bipsabwr-cockroach-1.1.5-bin
checking for references to /tmp/nix-build-cockroach-1.1.5.drv-0 in /nix/store/x65nnf9bzv8lmia0sh6arg79bipsabwr-cockroach-1.1.5-bin...
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
/nix/store/x65nnf9bzv8lmia0sh6arg79bipsabwr-cockroach-1.1.5-bin
/nix/store/p0a1pdgrdhmyrsm8rr0gxdv74ip01zq3-perkeep-20170505


[Bug Report] Weird behaviour when typing Chinese and there is a timer to update UI

Element UI version
2.3.8
OS/Browsers version
Mac OS / Chrome 66
Vue version
2.2.5
Reproduction Link
https://jsfiddle.net/bitjjj/ogszk8g2/
Steps to reproduce

slowly input Chinese in input area
sometimes you will see Chinese word will disappear automatically

What is Expected?
Input Chinese word correctly
What is actually happening?
Sometimes word will disappear automatically.
Checking different version code of ElementUI, I find this issue will happen after using composition event in Input component. This issue will not happen in Element UI version 2.0.5

I am do it

Fixed in #11235

@Leopoldthecoder 你太牛叉了

@leslieSie 没有，是之前一位社区开发者修复的。

@Leopoldthecoder 留几个bug给小弟修一修，你们的速度这么快。拼不过


ATAC crashes on request parameter deletion

Issue
I've noticed that when you try to delete a request parameter ATAC crashes due to an out of bound access on a vect.
Step to reproduce the issue

Create a collection
Create a request (I used a GET request)
Create a parameter for the request
Delete the created parameter

Solution
I have inspected the code and found that the issue is on line 58 of file src/tui/tui_logic/request/query_params.rs.
match self.delete_query_param(selection.0, selected_request_index.0, selected_request_index.1) {
Here the first parameter of the function code is the selected parameter row. But from the function definition is clear that it should be the last (3rd) parameter.
pub fn delete_query_param(&mut self, collection_index: usize, request_index: usize, row: usize) -> anyhow::Result<()> {
I have fixed it in my local repository and it solve the issue.
This is the first time I contribute to an open source project, can I simply commit it to the repository?
Hope this is useful,
Good evening

Fixed in https://github.com/Julien-cpsn/ATAC/commit/e3287f2bec54b8088df7bd55699bc4dc787c5eb9


feat: support scss compile

Description:

support scss compile
BREAKING CHANGE:

None
Related issue (if exists):

#121 should be implemented in Rust and using https://crates.io/crates/sass-embedded.


DRUM-KIT

I would like to add the sound feature using JS with interactive user interface in which user can play sounds of different instruments and play with this. I am a GSSOC'22 participant.
Code of Conduct✅

[x] I agree to follow this project's Code of Conduct.
[x] I checked the current issues for duplicate problems.
[x] I have gone through project README.

@NOiR-07 Please assign me this issue.

please please assign to me this issue i will made this quickly

I am a participant under GSSOC 2022. I would like to work on the issue. Please assign it to me and I have already done this, So I will do it quickly

@ruhirani011 This project already exists unfortunately. Feel free to work on a new issue. In case of any doubts, feel free to reach the mentors through our discord channel


Base64 image throwing 404 errors in srcset

Bit of an odd one and I am not sure if Imager specific?
I am using a practice in accordance with the lazysizes documentation and recommendation;
https://github.com/aFarkas/lazysizes#modern-transparent-srcset-pattern
So as an example my code for an image looks like this;
{% set image = entry.bannerImage.first() ?? fallbacks.bannerImage.first() %}
{% set mode = 'fit' %}
{% set imageSizes = [
    { width: 1560 },
    { width: 1200 },
    { width: 1000 },
    { width: 780 },
    { width: 600 },
] %}

{# Set Srcset Transform #}
{% set transformedImages = craft.imager.transformImage(image, imageSizes, { mode: mode, jpegQuality: 80 }) %}
{% set srcImage = transformedImages[2] %}

However, I am finding that when I do a link integrity check (using multiple applications) I am getting lots of 404 errors as it is finding the following urls where the srcset image is displayed e.g:
http://cvpal.loc/<svg xmlns='http:/www.w3.org/2000/svg' width='8736' height='5824' style='background:transparent'/>
Secondary to this when I view the actual source code (not inspector) I can see the following:
data:image/svg+xml;charset=utf-8,%3Csvg%20xmlns%3D%27http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%27%20width%3D%271000%27%20height%3D%27667%27%20style%3D%27background%3Atransparent%27%2F%3E

But it seems the browser is splitting this into two clickable elements the first part and the second part after the comma. The second part if clicked also links off to the 404 error above: http://cvpal.loc/<svg xmlns='http:/www.w3.org/2000/svg' width='8736' height='5824' style='background:transparent'/>
Not sure where to go from here? Not sure if this is because imager is actually include the protocol? or if it is a misinterpretation by the browsers and integrity tools?
Any thoughts/ideas?

Yes, at the moment it's SVG only. Should probably make more options for the Craft 3 version.