MBACK implementation

This PR implements the Weng et al MBACK normalization algorithm.  It also modifies the recent diffkk plugin to use the new mback plugin.
Changes to the Larch manual are included (I put it in the xafs/pre-edge section).
My plugin tutorial, which refers to the mback plugin a lot, is more or less done.  There are still a few formatting issues, mostly related to the math, and one shortcoming related to larch file locations (I haven't yet looked carefully at #104.)  Anyway, it's at
http://bruceravel.gitbooks.io/larch-plugin-tutorial/
I'll leave it up to you if and how to link to it from the larch manual.

This is really great  -- Diffkk and Mback and Fluo, Oh My!
I'll add the latest XDI dll and tag all the recent changes as 0.9.25, hopefully by the end of the week.   Also, I'll add a link to your git-book to the devel docs.


Some Unity games always reset speed

Subway Surfers  https://apps.apple.com/us/app/subway-surfers/id512939461
Some games tend to revert to the original speed, seemingly resetting every frame. A temporary solution is to "freeze speed" to ensure it remains constant, though this increases CPU usage.
LuckySpeeder has not implemented this yet.

The problem is now perfectly solved, with almost no additional CPU overhead.


docs: Add a guide for adjusting airflow scheduler resources

Summary
This should help your Airflow users understand how to update scheduler resources for Airflow hosted on plural.sh
Test Plan
I'm running the provided configuration in my plural.sh Airflow and it's working great 👍
Checklist

[x]  No images hosted from dockerhub
[x]  Are dashboards present to understand the health of the application.  There must be at least 1 of these

[x]  all databases should have dashboards
[x]  ideally also have at least cpu/mem utilization dashboards for webserver tier of the app
[x]  you can use plural from-grafana to convert a grafana dashboard found via google to our CRD

[x]  Are scaling runbooks present

[x]  all databases must have scaling runbooks
[x]  you can use the charts in pluralsh/module-library to accelerate this

[x]  do you need to add config overlays?

[x]  inputing secrets
[x]  configuring autoscaling

[x]  If there’s a web-facing component to the app, we need to support OIDC authentication and setting up private networks if no authentication option is viable
[x]  All major clouds must be supported

[x]  Azure
[x]  AWS
[x]  GCP

A lot of the checklist items may not really apply since it's a simple doc, but let me know if there's anything else I can add 🍻

thanks for the contribution!


Still maintained project?

Hi guys, I see that the last commit is more than 1 year old.
Are you sill planning to continue working on this?
The lock support is not working at all - I only get status updates after restarting the adapter. Looking at the source - the lock is not even in the list of scheduled getStatus requests.
Setting a new state for the lock would be great - then you can start with some kind of automations there.
There seems to be newer API versions from Switchbot available etc.

Yes, that would be good to know.

At least I could get a script ready to give me some infos on statechanges via IFTTT iot adapter.
Not easy to set this all up... But better than setting up my own machine in the cloud to let the webhook callback and somehow push the data into my local network. Security nightmare. The iot adapter and ifttt guys did this already.


Update deep link with new URLs

Updates the deeplinking documentation for the added routes.

@whydna This is good to go?

@irace  Yep!


fix: use  instead of ':' in quick menus remaps

Quick menus remaps now work even if a user uses a ':' remap.
It solves the problem raised by @rod-stuchi in #113.

I accept


Villagers wont breed

I have tried breeding villagers with both carrots and potatoes and still not having any luck.

Do u have beds near villagers? Are there more than 2 blocks above beds?

If you can, take screenshot of your breeder

I will get a screen shot tomorrow after work. It’s currently 11:40pm here in Australia.
Yes there are beds near the villagers and 2 blocks above the beds.
The villagers just seem to look at the carrots on the ground without picking them up.
Sent from my iPhone

On 10 Oct 2022, at 10:16 pm, Tvitser @.***> wrote:

Do u have beds near villagers? Are there more than 2 blocks above beds?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

I tested breeding in a new empty world and it works fine. As long as the villagers have empty slots in their inventory and the carrots and potatoes are close enough, they should pick them up. It's possible their inventory is filled with seeds or wheat, which would mean they won't breed and won't pick things up.

Ok thanks for the update. I will sus it out later today.
Sent from my iPhone

On 11 Oct 2022, at 8:50 am, Jack Sorrell @.***> wrote:

I tested breeding in a new empty world and it works fine. As long as the villagers have empty slots in their inventory and the carrots and potatoes are close enough, they should pick them up. It's possible their inventory is filled with seeds or wheat, which would mean they won't breed and won't pick things up.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.


Build fails with unrecognized command-line option '-arch' when cross-compiling

Hi :-)
Has anyone seen anything like this before when cross-compiling on an M1 Mac?
This cross-compile configuration works successfully for a variety of other crates, however this is the first crate I'm using that uses CMake, so I'm not sure if it's a libz-sys specific problem, or with cross-compiling with CMake and this toolchain in general.
Steps to reproduce

brew install messense/macos-cross-toolchains/x86_64-unknown-linux-musl (to install this cross-compile toolchain)
brew install cmake (since libz-sys requires it)
rustup target add x86_64-unknown-linux-musl
Ensure the new toolchain can be found:export CC_x86_64_unknown_linux_musl=x86_64-unknown-linux-musl-gcc
export CXX_x86_64_unknown_linux_musl=x86_64-unknown-linux-musl-g++
export AR_x86_64_unknown_linux_musl=x86_64-unknown-linux-musl-ar
export CARGO_TARGET_X86_64_UNKNOWN_LINUX_MUSL_LINKER=x86_64-unknown-linux-musl-gcc

cargo new testcase-libz-sys-cross-compile && cd_
cargo build --target x86_64-unknown-linux-musl

Expected
The build completes successfully (like it does on this machine, when not cross-compiling).
Actual
The build fails with:
   Compiling cc v1.0.73
   Compiling pkg-config v0.3.24
   Compiling libc v0.2.121
   Compiling cmake v0.1.48
   Compiling libz-sys v1.1.5
error: failed to run custom build command for `libz-sys v1.1.5`

Caused by:
  process didn't exit successfully: `/Users/emorley/src/testcase-libz-sys-cross-compile/target/debug/build/libz-sys-720c0d8a10ea6099/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=LIBZ_SYS_STATIC
  cargo:rerun-if-changed=build.rs
  CMAKE_TOOLCHAIN_FILE_x86_64-unknown-linux-musl = None
  CMAKE_TOOLCHAIN_FILE_x86_64_unknown_linux_musl = None
  TARGET_CMAKE_TOOLCHAIN_FILE = None
  CMAKE_TOOLCHAIN_FILE = None
  CMAKE_GENERATOR_x86_64-unknown-linux-musl = None
  CMAKE_GENERATOR_x86_64_unknown_linux_musl = None
  TARGET_CMAKE_GENERATOR = None
  CMAKE_GENERATOR = None
  CMAKE_PREFIX_PATH_x86_64-unknown-linux-musl = None
  CMAKE_PREFIX_PATH_x86_64_unknown_linux_musl = None
  TARGET_CMAKE_PREFIX_PATH = None
  CMAKE_PREFIX_PATH = None
  CMAKE_x86_64-unknown-linux-musl = None
  CMAKE_x86_64_unknown_linux_musl = None
  TARGET_CMAKE = None
  CMAKE = None
  running: "cmake" "/Users/emorley/.cargo/registry/src/github.com-1ecc6299db9ec823/libz-sys-1.1.5/src/zlib-ng" "-DBUILD_SHARED_LIBS=OFF" "-DZLIB_COMPAT=ON" "-DWITH_GZFILEOP=ON" "-DCMAKE_INSTALL_PREFIX=/Users/emorley/src/testcase-libz-sys-cross-compile/target/x86_64-unknown-linux-musl/debug/build/libz-sys-2b3ea8f924a72b91/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_C_COMPILER=/opt/homebrew/bin/x86_64-unknown-linux-musl-gcc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_CXX_COMPILER=/opt/homebrew/bin/x86_64-unknown-linux-musl-g++" "-DCMAKE_ASM_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_ASM_COMPILER=/opt/homebrew/bin/x86_64-unknown-linux-musl-gcc" "-DCMAKE_BUILD_TYPE=Debug"
  -- Using CMake version 3.22.3
  -- ZLIB_HEADER_VERSION: 1.2.11
  -- ZLIBNG_HEADER_VERSION: 2.1.0.devel
  -- The C compiler identification is GNU 11.2.0
  -- Checking whether C compiler has -isysroot
  -- Checking whether C compiler has -isysroot - yes
  -- Checking whether C compiler supports OSX deployment target flag
  -- Checking whether C compiler supports OSX deployment target flag - no
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - failed
  -- Check for working C compiler: /opt/homebrew/bin/x86_64-unknown-linux-musl-gcc
  -- Check for working C compiler: /opt/homebrew/bin/x86_64-unknown-linux-musl-gcc - broken
  -- Configuring incomplete, errors occurred!
  See also "/Users/emorley/src/testcase-libz-sys-cross-compile/target/x86_64-unknown-linux-musl/debug/build/libz-sys-2b3ea8f924a72b91/out/build/CMakeFiles/CMakeOutput.log".
  See also "/Users/emorley/src/testcase-libz-sys-cross-compile/target/x86_64-unknown-linux-musl/debug/build/libz-sys-2b3ea8f924a72b91/out/build/CMakeFiles/CMakeError.log".

  --- stderr
  CMake Error at /opt/homebrew/Cellar/cmake/3.22.3/share/cmake/Modules/CMakeTestCCompiler.cmake:69 (message):
    The C compiler

      "/opt/homebrew/bin/x86_64-unknown-linux-musl-gcc"

    is not able to compile a simple test program.

    It fails with the following output:

      Change Dir: /Users/emorley/src/testcase-libz-sys-cross-compile/target/x86_64-unknown-linux-musl/debug/build/libz-sys-2b3ea8f924a72b91/out/build/CMakeFiles/CMakeTmp

      Run Build Command(s):/usr/bin/make -f Makefile cmTC_710b5/fast && /Library/Developer/CommandLineTools/usr/bin/make  -f CMakeFiles/cmTC_710b5.dir/build.make CMakeFiles/cmTC_710b5.dir/build
      Building C object CMakeFiles/cmTC_710b5.dir/testCCompiler.c.o
      /opt/homebrew/bin/x86_64-unknown-linux-musl-gcc   -ffunction-sections -fdata-sections -fPIC -m64  -arch arm64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk -std=c11 -o CMakeFiles/cmTC_710b5.dir/testCCompiler.c.o -c /Users/emorley/src/testcase-libz-sys-cross-compile/target/x86_64-unknown-linux-musl/debug/build/libz-sys-2b3ea8f924a72b91/out/build/CMakeFiles/CMakeTmp/testCCompiler.c
      x86_64-unknown-linux-musl-gcc: error: unrecognized command-line option '-arch'
      make[1]: *** [CMakeFiles/cmTC_710b5.dir/testCCompiler.c.o] Error 1
      make: *** [cmTC_710b5/fast] Error 2

    CMake will not be able to correctly generate this project.
  Call Stack (most recent call first):
    CMakeLists.txt:37 (project)

  thread 'main' panicked at '
  command did not execute successfully, got: exit status: 1

  build script failed, must exit now', /Users/emorley/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.48/src/lib.rs:975:5
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Environment

macOS 12.3 on Apple Silicon (M1 Max)
rustc 1.60.0-beta.6 (7bccde197 2022-03-22)
Crate versions at time of testing:

libz-sys: 1.1.5
cmake: 0.1.48
pkg-config: 0.3.24

The cross-compile toolchain currently uses GCC 11.2.

The CMakeError.log file mentioned contains:
Detecting C compiler ABI info failed to compile with the following output:
Change Dir: /Users/emorley/src/testcase-libz-sys-cross-compile/target/x86_64-unknown-linux-musl/debug/build/libz-sys-2b3ea8f924a72b91/out/build/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make -f Makefile cmTC_1760d/fast && /Library/Developer/CommandLineTools/usr/bin/make  -f CMakeFiles/cmTC_1760d.dir/build.make CMakeFiles/cmTC_1760d.dir/build
Building C object CMakeFiles/cmTC_1760d.dir/CMakeCCompilerABI.c.o
/opt/homebrew/bin/x86_64-unknown-linux-musl-gcc   -ffunction-sections -fdata-sections -fPIC -m64  -arch arm64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk   -v -Wl,-v -std=c11 -o CMakeFiles/cmTC_1760d.dir/CMakeCCompilerABI.c.o -c /opt/homebrew/Cellar/cmake/3.22.3/share/cmake/Modules/CMakeCCompilerABI.c
Using built-in specs.
COLLECT_GCC=/opt/homebrew/bin/x86_64-unknown-linux-musl-gcc
x86_64-unknown-linux-musl-gcc: error: unrecognized command-line option '-arch'
Target: x86_64-unknown-linux-musl
Configured with: /Volumes/build/.build/x86_64-unknown-linux-musl/src/gcc/configure --build=aarch64-build_apple-darwin21.3.0 --host=aarch64-build_apple-darwin21.3.0 --target=x86_64-unknown-linux-musl --prefix=/Volumes/tools/x86_64-unknown-linux-musl --exec_prefix=/Volumes/tools/x86_64-unknown-linux-musl --with-sysroot=/Volumes/tools/x86_64-unknown-linux-musl/x86_64-unknown-linux-musl/sysroot --enable-languages=c,c++,fortran --enable-__cxa_atexit --disable-libmudflap --disable-libgomp --disable-libssp --disable-libquadmath --disable-libquadmath-support --disable-libsanitizer --disable-libmpx --with-gmp=/Volumes/build/.build/x86_64-unknown-linux-musl/buildtools --with-mpfr=/Volumes/build/.build/x86_64-unknown-linux-musl/buildtools --with-mpc=/Volumes/build/.build/x86_64-unknown-linux-musl/buildtools --with-isl=/Volumes/build/.build/x86_64-unknown-linux-musl/buildtools --enable-lto --enable-threads=posix --enable-target-optspace --with-linker-hash-style=both --enable-plugin --enable-gold --disable-nls --disable-multilib --with-local-prefix=/Volumes/tools/x86_64-unknown-linux-musl/x86_64-unknown-linux-musl/sysroot --enable-long-long
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 11.2.0 (GCC)
make[1]: *** [CMakeFiles/cmTC_1760d.dir/CMakeCCompilerABI.c.o] Error 1
make: *** [cmTC_1760d/fast] Error 2

Determining if the C compiler works failed with the following output:
Change Dir: /Users/emorley/src/testcase-libz-sys-cross-compile/target/x86_64-unknown-linux-musl/debug/build/libz-sys-2b3ea8f924a72b91/out/build/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make -f Makefile cmTC_bd1e5/fast && /Library/Developer/CommandLineTools/usr/bin/make  -f CMakeFiles/cmTC_bd1e5.dir/build.make CMakeFiles/cmTC_bd1e5.dir/build
Building C object CMakeFiles/cmTC_bd1e5.dir/testCCompiler.c.o
/opt/homebrew/bin/x86_64-unknown-linux-musl-gcc   -ffunction-sections -fdata-sections -fPIC -m64  -arch arm64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX12.3.sdk -std=c11 -o CMakeFiles/cmTC_bd1e5.dir/testCCompiler.c.o -c /Users/emorley/src/testcase-libz-sys-cross-compile/target/x86_64-unknown-linux-musl/debug/build/libz-sys-2b3ea8f924a72b91/out/build/CMakeFiles/CMakeTmp/testCCompiler.c
x86_64-unknown-linux-musl-gcc: error: unrecognized command-line option '-arch'
make[1]: *** [CMakeFiles/cmTC_bd1e5.dir/testCCompiler.c.o] Error 1
make: *** [cmTC_bd1e5/fast] Error 2

And .../out/build/CMakeFiles/3.22.3/CMakeSystem.cmake contains:
set(CMAKE_HOST_SYSTEM "Darwin-21.4.0")
set(CMAKE_HOST_SYSTEM_NAME "Darwin")
set(CMAKE_HOST_SYSTEM_VERSION "21.4.0")
set(CMAKE_HOST_SYSTEM_PROCESSOR "arm64")

set(CMAKE_SYSTEM "Darwin-21.4.0")
set(CMAKE_SYSTEM_NAME "Darwin")
set(CMAKE_SYSTEM_VERSION "21.4.0")
set(CMAKE_SYSTEM_PROCESSOR "arm64")

set(CMAKE_CROSSCOMPILING "FALSE")

set(CMAKE_SYSTEM_LOADED 1)

Upgrading from CMake 3.22.3 to the newly released 3.23.0 (both installed via brew), doesn't help.

I don't suppose anyone has ideas of what to try next? :-)


Able to vote multiple times more cheaply if I sign each separately

I did this by accident in the TEC repo - I had intended to add 2 votes (costing 4) but clicked on the vote button twice. The tokenlog updated the count with 4 votes, but it only cost me 8 cstk. Technically it should have cost me 16 cstk, but voting twice allowed me to get more votes for cheaper.
Really only vulnerable to malicious intentional use, but does break the intended quadratic voting aspect if exploited.

Hi, thanks for reporting. I'm able to reproduce and this should indeed get fixed.
Right now, the verification is handled in the front-end and prone to these kind of vulnerabilities.
In the upcoming version, all of that logic is moved to the back-end, where additional checks are added to verify new votes.

Had this planned for the next major release, but more people experienced similar behavior.
So just implemented additional checks in the back-end. That should solve these issues.
Closing this issue.


Add Auto-Upgrade Feature for Seamless Chart Deployment and Version Management

Problem Statement:
Our team aims to streamline the deployment process by utilizing this tool to effortlessly deploy charts and seamlessly upgrade versions as soon as they are available in the Helm repository.
Proposed Solution:
Integrate a feature that enables users to auto-upgrade the chart to the latest version with the click of a button, similar to the functionality offered by flux2 (Gitops).
Alternative Solutions:
Manual version checks and upgrades can be cumbersome and prone to human error. Automating this process would significantly reduce the workload and ensure timely updates.
Implementing a notification system to alert users about new chart versions could also be beneficial, but it may not be as efficient as an automated upgrade option.
Additional Context:
By incorporating this auto-upgrade feature, users can maintain their deployments effortlessly, staying up-to-date with the latest features and fixes without manual intervention. This enhancement would greatly enhance the efficiency and usability of the tool.

Hey @aviorma, we picked this up in the past couple of days. We added a section to the Edit module page that allows you to change the version of a template or load the latest version.
In the recording below, we had a Module referencing a template on version x.x.x (the latest version). The module was created when the latest version was 0.3.0, and since then, we have added version 0.4.0. In version 0.4.0 we added an additional field (my-new-field) to show the functionality.
You can now easily load the latest version by clicking the "lock" icon in the Template section and hitting the Load button, thus bumping from 0.3.0 to 0.4.0.
https://github.com/cyclops-ui/cyclops/assets/72022639/71cf0ac3-7b5f-4799-bf93-e843f940cebe
You can try it yourself by installing the RC version we created by running the command below:
kubectl apply -f https://raw.githubusercontent.com/cyclops-ui/cyclops/v0.5.0-rc.1/install/cyclops-install.yaml &&
kubectl apply -f https://raw.githubusercontent.com/cyclops-ui/cyclops/v0.5.0-rc.1/install/demo-templates.yaml

Let me know what you think and if this would help your team

Implemented with v0.7.0


Split NV management functions to new files

In prepereation for adding recovery logic, split off the NV code from the more general variable management code.

I'm going to be adding a fair chunk of new logic, and it will all relate to the underlying OP-TEE storage mechanisms. It seemed like a good idea to split the existing OP-TEE logic into its own file before starting on that.
I've got a patch for that almost ready as well.


Errors encountered during compiling.

Hello, I meet some errors when compiling dacapo.
The first one is in the Build Hecate:

I solve this by removing this part in lib/Runtime/CMakeLists.txt:

Another error is still the Build Hecate:

How can I solve this issue?
My clang/clang++ version is 14.0.6. I appreciate your help.

Hello! First of all, I have resolved the error arising from the CMakeList.
The second error seems to be related to incorrect linking of MLIR. Please try setting 'export CC="clang"' and 'export CXX="clang++"'. Also, make sure that the MLIR_ROOT is set to the correct path.
Thank you!


Update what-is-cloud-sync.md

Updated support for group writeback

@billmath
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

This has already been updated.  Thanks
#please-close


✨ Freshen Builds

This ensures that the freshest coinstac-common and coinstac-client-core are bundled within the UI before its built. This is easier then publishing these packages every time before testing a build.

Problem: Builds rely on published packages.
Solution: Bash script ‘em to copy that source
Testing:

Check out branch
Run npm run build in packages/coinstac-ui/
Test out the build!

#!/bin/bash 👀

:)

@cdaringe Yeah, temporary script. It's faster than Node.js’s rimraf and ncp. ¯\_(ツ)_/¯


Audit: make sure service commands exist

[x] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

Review period will end on 2021-04-14 at 09:26:43 UTC.

And here we have 1 of the 2 reasons that I wanted to make the service block.

Hmm, I need to somehow make this audit require an installed formula. Any suggestions?

Hmm, I need to somehow make this audit require an installed formula. Any suggestions?

https://github.com/Homebrew/brew/blob/a4ea7fb279b581fa0e7783f2b0d76f6a7ed6372e/Library/Homebrew/formula_cellar_checks.rb#L278-L297

It seems kinda weird to add it to the Cellar checks since it checks the formula, not the cellar. But I guess that can work until someone has a better idea.

It seems kinda weird to add it to the Cellar checks since it checks the formula, not the cellar. But I guess that can work until someone has a better idea.

You can think of it as checking the Cellar that the file referenced by the service block exists.

Review period ended.

Looks good to me. One question if you don't mind: why/when/how would you specify multiple run commands?

It's multiple parts, e.g. [bin/'httpd', '-D', 'foreground']

Ah gotcha, thanks!


rr_openrover_basic: 0.6.0-1 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository rr_openrover_basic to 0.6.0-1:

upstream repository: https://github.com/RoverRobotics/rr_openrover_basic.git
release repository: https://github.com/RoverRobotics/rr_openrover_basic-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.6.9
previous version for package: 0.6.0-0

Did you mean to make a new release? It looks like this is the 0.6.0 tag repackaged from 13 days ago. If you want newer content you need to make a new tag in the upstream repository which is conveniently done with catkin_prepare_release http://wiki.ros.org/bloom/Tutorials/ReleaseCatkinPackage


Set accurate data set titles and links so that I am certain the data sources are trustworthy on Source Data table

Aiming to fix #29 , by giving proper data instead of mock

Awaiting additional data

Still waiting on final data from Supriya. Getting closer I think.


test methods are overridden when multiple TestResults folder given to generate the report

Hi
we are having around 50 sanity test methods and we have split it into 3 execute shells in Jenkins
like the below
xcodebuild test -workspace myworkspace.xcworkspace -scheme myUITests -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone X,OS=12.4' -only-testing:(1-20 test methods) -resultBundlePath Testresult1
xcodebuild test -workspace myworkspace.xcworkspace -scheme myUITests -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone X,OS=12.4' -only-testing:(21-40 test methods) -resultBundlePath Testresult2
xcodebuild test -workspace myworkspace.xcworkspace -scheme myUITests -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone X,OS=12.4' -only-testing:(41-50 test methods) -resultBundlePath Testresult3
and later we run
xchtmlreport -r TestResults1 -r TestResults2 -r TestResults3
the issue is the test methods in TestResults1 are repeated in TestResults2 and TestResults3 report

looking at the above commands, it seems that you are running all the tests on the same simulator (iPhone X) which could be why all your results are getting combined. You could create 2 clones of iPhone X and then run the tests or create separate simulators of different iPhones and that should resolve the issue for you.


get_documents

not sure if it needs a batch option, will a docket have more than 5k docs?
not currently working in sandbox, working on it

I don't think we would end up with more than 5k.
Before seeing this. I made some edits to this go get it working, but it could be cleaner without the batch argument
On thing to keep in mind: the api_key or api_keys argument cannot be used as the default in more than one place. It is ok if the top-level function defaults to api_keys = api_keys, but we can't then do that in helper functions or it gets recursive: https://stackoverflow.com/questions/4357101/promise-already-under-evaluation-recursive-default-argument-reference-or-earlie

I did get one that was a bit over 3000 documents, but have not seen 5k

I'd say we can drop the batching for now, and put it back in if it is needed.

investigate: EPA-HQ-OW-2009-0819

😳EPA-HQ-OW-2009-0819 has 7,196 documents @mzkhuzam2

This is a really weird docket. It has a Unified Agenda tab which I haven't seen before, documents have been posted from 2013-2023, and it's received 300k+ comments but only 4k have been posted.
Should we hold off on dropping batching for now?

yes, it will be more robust to odd things like this if it has the batch loop, so let's keep it.

I don't think we would end up with more than 5k.
Before seeing this. I made some edits to this go get it working, but it could be cleaner without the batch argument
On thing to keep in mind: the api_key or api_keys argument cannot be used as the default in more than one place. It is ok if the top-level function defaults to api_keys = api_keys, but we can't then do that in helper functions or it gets recursive: https://stackoverflow.com/questions/4357101/promise-already-under-evaluation-recursive-default-argument-reference-or-earlie

Okay, I think I established a system that works:
Two types of API key calls: api_keys, api_key

api_key is reserved for the make_call function because that will loop through the different keys
api_keys is in the function arguments for both the batch and higher-level functions, but it is not set with a default value anywhere. Users must set their own default value.

It seems in the StackOverflow responses, the issue arises from setting a default argument and not the naming standard across the different functions so I think this makes sense. Let me know if you run into any issues.
Note: I'm not sure where "keys" is used .... I know I saw it somewhere but I can't find it anymore. If that causes a problem let me know.

I investigated DOT-OST-2005-23307 today, and it looks like the majority of the documents are actually comments. I tried to collect the comments on all 5084 document to see what would be returned, but it kept failing and I got frustrated. I'll try again later once my API hit rate refreshes.


support Xocde 11 SPM for iOS

please update Package.swift, and BigInt version need to be 4.0.0

Yes, current version has SipHash issues. I believe its removed from newer versions of BigInt.

@phpmaple already updated in Carthage.
There is a lot of issues with Package.swift. But I will this update file too. Thanks for update 👍

I used xcode 12.0.1, add SPM but an error occurred with message "Invalid semantic version string 5.0".  After that, i change version of BigInt to 5.0.0, it work normally. Could you update your Package?

@lamnd91 will fix it now. thank you!

It seems that it's still broken. I've got same error yet.

It seems that it's still broken. I've got same error yet.

What the code version are you using ?

What the code version are you using ?

It seems to work in dev branch but no in master
El El lun, 11 ene 2021 a las 17:48, Petr Korolev<EMAIL_ADDRESS>escribió:

What the code version are you using ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/matter-labs/web3swift/issues/221#issuecomment-758080013,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFOQFEU5MOQ2FBVEDJRVXTSZMTW7ANCNFSM4IZ2RCSA
.

It seems to work in dev branch but no in master
El El lun, 11 ene 2021 a las 17:48, Petr Korolev<EMAIL_ADDRESS>escribió:

What the code version are you using ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/matter-labs/web3swift/issues/221#issuecomment-758080013,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFOQFEU5MOQ2FBVEDJRVXTSZMTW7ANCNFSM4IZ2RCSA
.


Consider enabling word wrapping by default in test failure inline diff editor

When a test fails, it might sometimes look like this:

By pressing alt+z in both editors, I can get it to look like this, which is more helpful for long strings:

It might be better to enable word wrapping by default for string comparisons.

Code pointer: https://github.com/microsoft/vscode/blob/c78811c1a7d2b2438ce69670f290008700037221/src/vs/workbench/contrib/testing/browser/testingOutputPeek.ts#L762

@alexdima @connor4312 Is this issue up for grabs? I would love to implement this 👍

Could you assign me to this issue?

No, only people in the Microsoft org can be assigned issues. You can open a PR without being assigned though 🙂


Build from repository

Just for the sake of context: I'm building a bit of a wrapper project around this that will handle auto-configuration of projects. My workflow, in general, is to

Do a clean checkout of the repo I'm currently working on
Create a branch to hold my feature/bug
Initialize the project (we use ant)
Watch for the directory for changes and rsync to a remote server (sometimes)
Do some configuration (vhosts) on that same remote server (sometimes)
Finish my work and commit, push.
Wait for testers to be done and then delete everything.

While the majority of that doesn't fit in with the philosophy of desk and is really specific to my workflow, the bit about checking out from a repository might be. I'm envisioning something like
$ desk build github.com/owner/repo [desk-name]

Where you would previously configure where you want the projects to live (like configuring where you want the deskfiles to live).
This would create some stub deskfile (desk-name.sh) and do the git clone in your project directory.
The biggest things that I'd see with this are:

Tying desk to a specific scm (git) or host (github) OR trying to generalize and really bloating the code
Requiring an additional template file that would need to live somewhere and have a reference
Requiring users to configure and create a project directory

Maybe not ideal as laid out here, but potentially could be hammered into something useful :smile: I'd like to hear your thoughts on this, @jamesob.

Yeah, I'm definitely interested in supporting something complementary at desk's layer. Thanks for the detailed write-up of your thoughts.
I've been drafting a behavior to facilitate easy sharing of project-specfic deskfiles that may dovetail with your flow. Imagine a convention where we had Deskfile (or deskfile.sh, either way) live at the root of a project's source tree. You check out the project, cd into it, then run desk import .. This would symlink the project Deskfile into your $DESK_DESKS_DIR.
Question there is: some (maybe most) deskfiles start off with a cd ~/project/dir... how do we handle that in an imported deskfile, where the path of the project's checkout is unknown?
One option would be to support some comment syntax for saying "this is a project deskfile; if it's symlinked, read the link and cd to the basedir of the source." Something like
# /tmp/checkout/spectac_proj/Deskfile
#
# Description: my spectacular project
# Name: specproj
# Root: .

alias whatever='baz'
...

So then when you desk . specproj, it reads the symlink and cds you into /tmp/checkout/spectac_proj. I'm not wild about having to specify the name, so maybe we could think of a clever way to infer that.
What do you make of the above? Would it be useful for your wrapper?

I think your instinct is right with regard to the caveats you list: at some point I'd like to be able to optionally recognize git (and other vcs) if it's easy, but I definitely don't want to take on any dependencies in doing so. It requires some more thought, but I think there's potential there.

I like this approach better for the general use-case. It doesn't really match what I'd be able to do immediately as I'm the only one evaluating desk at my company at the moment and it might be a hard sell to place another file at source root (to live with grunt, npm, composer, bower, etc). However, I could easily get my wrapper script to 'inject' the deskfile into the project after checkout and then follow the same flow you describe after that point.
I can't think of a way to infer things like the project directory or the name of the project that aren't fraught with special cases or magic. In any case, I'm not opposed to optionally specifying the name and root directory, but we'd just have to be careful to not require too much configuration right off the bat.

I also think some sort of project specific setup would be really useful.
Why not just get desk to search for the deskfile in the current directory first, then if it doesn't exist look in $DESK_DESKS_DIR?
That would resolve the cd ~/project/dir... issue because you will already be there, just open the new shell at the current directory of the old one.

@TristanBurnside: +1

Sounds good -- I'll throw together and implementation for that pretty soon.


Longest Increasing Path in a Matrix

Link to Problem: https://leetcode.com/problems/longest-increasing-path-in-a-matrix/
Problem Number 329

Please assign this to me in C++

@MuskanGupta1503 Assigned in C++

Assign this to me in JAVA

@viralkumar28 Assigned in Java 👍🏻


Building the Astrobee API with Android Studio fails because of maven dependency

The espresso-core:2.0.2 dependency in the build.gradle for the astrobee_android/guest_science  project needs to be changed to espresso-core:2.2.2 because the maven repository doesn't host 2.0.2 anymore.

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2') {
        exclude group: 'com.android.support', module: 'support-annotations'
    }
    compile 'com.android.support:appcompat-v7:26.+'
    testCompile 'junit:junit:4.12'
}

I'm a bit confused, you say it needs to be changed to 2.2.2, but if I search the repo, it's already 2.2.2:
https://github.com/search?q=repo%3Anasa%2Fastrobee_android androidTestCompile(%27com.android.support.test.espresso%3Aespresso-core%3A&type=code

I can see it on the latest commit. I am not sure how this dependency changed for me.


Sandbox Baking

Provide sandbox baking options: immediately, every # sec vs. scheduled time

Replaced by #1067

Handling in #1163


When using Appfairy, my whole page gets overwritten with the current date

This is a bit of a weird issue! But bear with me.
I have just run Appfairy on my webflow exported code, and I now have two versions, my react one, and my original webflow files.
My original webflow files work as expected (deployed from src/public_site/.appfairy)- see here.
My new Appfairy react-ified webflow loads the page, and then covers the whole thing with some kind of override that deletes all elements and replaces them with the current date - see here.
All the code for reproducing this issue is available in my repository here. The site code is contained in src/public_site.

You have a script which has a document.write(data) which I suspect was added manually I guess for SEO reasons


AMQP-678: Move BrokerRunning @Rule to junit Jar [BACKPORT]

JIRA: https://jira.spring.io/browse/AMQP-678
Clean Broker After Running Tests
Remove redundant foo queue from QueueParserIntegrationTests-context.xml
Convert BrokerRunning to use the amqp-client directly to avoid circular reference.
Also LongRunningIntegrationTest.
Polishing - PR Comments

Repushed after rebase; wait for travis.


Random user logout

✅ Prerequisites

[x] Did you perform a cursory search of open issues? Is this question already asked elsewhere?
[x] Are you reporting to the correct repository (magic-sdk)?

❓ Question
We are using magic in an Electron app and the user is sometimes randomly logged out. We are unable to replicate the error, but it keeps happening. We already checked our code, but it is possible that the error is there.
We found several things that are not clear and that may be the cause:
Re-authenticating users
In the magic documentation it is not clear how long the session lasts and when we have to re-authenticate.

Does it always expire after 7 days if no other action happens?
Is the magic.user.isLoggedIn() or magic.user.getIdToken() causing the actual re-authentication? Will this reauthentication provision a new didToken?

didToken claims
We have looked at the decoded claims from the didToken and the ext field was always only 15 minutes in the future. Even after waiting for 15 minutes the user was still logged in - magic.user.isLoggedIn() is returning true.

How does this work? Is the didToken used solely as an "access token" and you are storing the actual information authentication information used for generating these tokens in the IndexedDB?
Where can we see how long until the current user's session expires and he needs to log in again?

The Electron environment also does not seems to be the problem. The IndexedDB where you are storing the sessions are persistent in Electron and even deleting the application cache does not log out the user.
🌎 Environment

Software
Version(s)

magic-sdk
4.0.2

Browser
Electron

yarn

Operating System
macOS 11.1

How does this work? Is the didToken used solely as an "access token" and you are storing the actual information authentication information used for generating these tokens in the IndexedDB?

The DID token is not an access token; think of it as more of a self-sovereign identity token or "authentication token" to your service. DID tokens are ultimately just proof to you that the user knows their private key. Accordingly, a user's DID token does not grant further access to Magic's DKM (delegated key management) for other signing actions.

Is the magic.user.isLoggedIn() or magic.user.getIdToken() causing the actual re-authentication? Will this reauthentication provision a new didToken?

magic.user.isLoggedIn will return true if the user is able to sign DID tokens. In other words, this lets you know if the user has an active session with Magic's DKM. Unless you're building a Web3 application, it's usually better to manage your own session after authenticating the user with Magic.
A typical flow goes like this:

Client-side calls magic.auth.loginWithMagicLink() => DIDToken
Client-side calls server-side /login endpoint with DIDToken encoded in the authorization header.
Server-side validates DIDToken using the Admin SDK of your choice.
Upon successful validation of DIDToken, server-side creates an encrypted session cookie called session and attaches it to the response headers.

Now, for any endpoint that requires authenticated access (like /user for example), your server middlewares can check for the existence the session cookie, validate it, and proceed! Otherwise, raise a 401!
For a Browser / Electron / NodeJS use-case, I think you'll find our Express / React example is an easy-to-understand implementation for this idea.
Also, magic.user.getIdToken() will return a new DID token that your service can use to authenticate a user; it does not restart or refresh the user's session with Magic.

We have looked at the decoded claims from the didToken and the ext field was always only 15 minutes in the future. Even after waiting for 15 minutes the user was still logged in - magic.user.isLoggedIn() is returning true.

To reiterate, the DID token is an authentication token that represents the user's identity for your service, it's not associated to the user session with Magic's DKM. By the way, you can customize the ext timestamp by providing an integer argument to magic.user.getIdToken as seconds. 900s or 15m is the default.

How does this work? Is the didToken used solely as an "access token" and you are storing the actual information authentication information used for generating these tokens in the IndexedDB?

It's not an access token (sorry to harp on this, I just want to answer each question you asked individually).

Where can we see how long until the current user's session expires and he needs to log in again?

We don't currently surface this information, but we'd like to in the future. For a more predictable session management experience, I recommend rolling your own sessions as described above!

Thanks for an exhaustive answer! :D
I will take the time to go over everything.
The session management does sound like something that is used pretty much every time you will be using magic. We are not sending the didToken with each request - we plan to use JWT exchanged for the didToken.

we plan to use JWT exchanged for the didToken.

This is the way 😉

We did solve it by doing something similar to what you are demonstrating in the Express / React examples - by adding a refresh/access token which the client gets in exchange for the didToken.
The misconception was that we thought the didToken is used as an access token for authorized access to resources. It also looked like you "refresh" the didToken by using the client's magic SDK, which would be handling the persistence of the session.

The misconception was that we thought the didToken is used as an access token for authorized access to resources. It also looked like you "refresh" the didToken by using the client's magic SDK, which would be handling the persistence of the session.

This is good feedback for us. We are always working to improve our documentation and dev experience. Thanks for sharing.

I got same question and find this issue.
But currently Express / React example  not implemented exchange JWT.
JWT exchange implementation removed this commit.
https://github.com/magiclabs/example-react-express/commit/0abb4e8b889f38bcd53e6b9ded1142fc28a6229e
Do you know why this is removed?

Hey @terrierscript, I had removed the JWT from the guide to rely on Magic for sessions and tracking if the user is logged in primarily to simplify the example. I'll add a new guide to site ASAP specifically on Magic + JWT for session management.

@terrierscript here's the new guide for custom sessions w JWT https://magic.link/posts/magic-jwt


missing bitcoin

General Description i noticed bitcoin is missing from my wallet without any transactions showing up

How To Reproduce?

Go to '...'
Click on '...'
Scroll down to '...'
See ERROR

Screenshots

Operating System

Logs

Insert Your Logs Here

Wasabi Version

please add more info, otherwise we cannot really help you. we can only guess
if you think BTC is missing without any transaction it could be a sync issue
https://docs.wasabiwallet.io/FAQ/FAQ-UseWasabi.html#how-do-i-resync-rescan-my-wallet
would still be useful if you also add info, like which Wasabi version etc

This can be closed.


Allow running the test suite offline

Hello,
Is your feature request related to a problem? Please describe.
Yes: it doesn't currently appear possible to run the acceptance tests (cucumber) inside a minimal environment isolated from the network (internet).
Describe the solution you'd like
It'd be nice if the test suite was self contained, e.g. not needing to fetch any resource from the internet at the time the test suite is run.
Describe alternatives you've considered
N/A.
Additional context
This is as far as I've gotten, with some light patching to use gems from GEM_PATH instead of from git:
starting phase `check'
Resolving dependencies...
/gnu/store/j4z07lyi1ykk8bc68h1p4bpj1il9dn3f-ruby-2.7.4/bin/ruby -w -I/gnu/store/l3nss8vrb6laiqb1ayn9bri2vn4xnzj1-ruby-rspec-core-3.12.1/lib/ruby/vendor_ruby/gems/rspec-core-3.12.1/lib:/gnu/store/900s3ljm1d44zam9hsbxf7ckr49zrriv-ruby-rspec-support-3.12.0/lib/ruby/vendor_ruby/gems/rspec-support-3.12.0/lib /gnu/store/l3nss8vrb6laiqb1ayn9bri2vn4xnzj1-ruby-rspec-core-3.12.1/lib/ruby/vendor_ruby/gems/rspec-core-3.12.1/exe/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
/gnu/store/2cqdyxyp0dxfmjhbgk3q84dzplf2qd6a-ruby-mail-2.7.1/lib/ruby/vendor_ruby/gems/mail-2.7.1/lib/mail/parsers/address_lists_parser.rb:32454: warning: statement not reached
/gnu/store/2cqdyxyp0dxfmjhbgk3q84dzplf2qd6a-ruby-mail-2.7.1/lib/ruby/vendor_ruby/gems/mail-2.7.1/lib/mail/parsers/address_lists_parser.rb:32615: warning: statement not reached
/gnu/store/2cqdyxyp0dxfmjhbgk3q84dzplf2qd6a-ruby-mail-2.7.1/lib/ruby/vendor_ruby/gems/mail-2.7.1/lib/mail/parsers/address_lists_parser.rb:32651: warning: statement not reached
/gnu/store/2cqdyxyp0dxfmjhbgk3q84dzplf2qd6a-ruby-mail-2.7.1/lib/ruby/vendor_ruby/gems/mail-2.7.1/lib/mail/parsers/address_lists_parser.rb:32740: warning: statement not reached
/gnu/store/2cqdyxyp0dxfmjhbgk3q84dzplf2qd6a-ruby-mail-2.7.1/lib/ruby/vendor_ruby/gems/mail-2.7.1/lib/mail/parsers/address_lists_parser.rb:32756: warning: statement not reached
/gnu/store/2cqdyxyp0dxfmjhbgk3q84dzplf2qd6a-ruby-mail-2.7.1/lib/ruby/vendor_ruby/gems/mail-2.7.1/lib/mail/parsers/address_lists_parser.rb:32822: warning: statement not reached
/gnu/store/2cqdyxyp0dxfmjhbgk3q84dzplf2qd6a-ruby-mail-2.7.1/lib/ruby/vendor_ruby/gems/mail-2.7.1/lib/mail/parsers/address_lists_parser.rb:32863: warning: statement not reached
/gnu/store/2cqdyxyp0dxfmjhbgk3q84dzplf2qd6a-ruby-mail-2.7.1/lib/ruby/vendor_ruby/gems/mail-2.7.1/lib/mail/parsers/address_lists_parser.rb:32888: warning: statement not reached
/gnu/store/2cqdyxyp0dxfmjhbgk3q84dzplf2qd6a-ruby-mail-2.7.1/lib/ruby/vendor_ruby/gems/mail-2.7.1/lib/mail/parsers/address_lists_parser.rb:31984: warning: assigned but unused variable - testEof

Randomized with seed 52034
.............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................***......................................................................

Pending: (Failures listed here are expected and do not affect your suite's status)

  1) HaveEnqueuedMail matchers have_enqueued_mail when parameterized passes when mixing parameterized and non-parameterized emails
     # No reason given
     # ./spec/rspec/rails/matchers/have_enqueued_mail_spec.rb:375

  2) HaveEnqueuedMail matchers have_enqueued_mail when parameterized passes with provided argument matchers
     # No reason given
     # ./spec/rspec/rails/matchers/have_enqueued_mail_spec.rb:382

  3) HaveEnqueuedMail matchers have_enqueued_mail when parameterized passes when mailer is parameterized
     # No reason given
     # ./spec/rspec/rails/matchers/have_enqueued_mail_spec.rb:369

Finished in 2.54 seconds (files took 1.27 seconds to load)
1062 examples, 0 failures, 3 pending

Randomized with seed 52034

rm -rf tmp/example_app
rm -f /tmp/guix-build-ruby-rspec-rails-6.0.1.drv-0/source/bin/rails
bundle exec rails new ./tmp/example_app --no-rc --skip-javascript --skip-bootsnap --skip-sprockets --skip-git --skip-test-unit --skip-listen --skip-bundle --skip-spring --template=example_app_generator/generate_app.rb
      create
      create  README.md
      create  Rakefile
      create  .ruby-version
      create  config.ru
      create  Gemfile
      create  app
      create  app/assets/config/manifest.js
      create  app/assets/stylesheets/application.css
      create  app/channels/application_cable/channel.rb
      create  app/channels/application_cable/connection.rb
      create  app/controllers/application_controller.rb
      create  app/helpers/application_helper.rb
      create  app/jobs/application_job.rb
      create  app/mailers/application_mailer.rb
      create  app/models/application_record.rb
      create  app/views/layouts/application.html.erb
      create  app/views/layouts/mailer.html.erb
      create  app/views/layouts/mailer.text.erb
      create  app/assets/images
      create  app/assets/images/.keep
      create  app/controllers/concerns/.keep
      create  app/models/concerns/.keep
      create  bin
      create  bin/rails
      create  bin/rake
      create  bin/setup
      create  config
      create  config/routes.rb
      create  config/application.rb
      create  config/environment.rb
      create  config/cable.yml
      create  config/puma.rb
      create  config/storage.yml
      create  config/environments
      create  config/environments/development.rb
      create  config/environments/production.rb
      create  config/environments/test.rb
      create  config/initializers
      create  config/initializers/assets.rb
      create  config/initializers/content_security_policy.rb
      create  config/initializers/cors.rb
      create  config/initializers/filter_parameter_logging.rb
      create  config/initializers/inflections.rb
      create  config/initializers/new_framework_defaults_7_0.rb
      create  config/initializers/permissions_policy.rb
      create  config/locales
      create  config/locales/en.yml
      create  config/master.key
      create  config/boot.rb
      create  config/database.yml
      create  db
      create  db/seeds.rb
      create  lib
      create  lib/tasks
      create  lib/tasks/.keep
      create  lib/assets
      create  lib/assets/.keep
      create  log
      create  log/.keep
      create  public
      create  public/404.html
      create  public/422.html
      create  public/500.html
      create  public/apple-touch-icon-precomposed.png
      create  public/apple-touch-icon.png
      create  public/favicon.ico
      create  public/robots.txt
      create  tmp
      create  tmp/.keep
      create  tmp/pids
      create  tmp/pids/.keep
      create  tmp/cache
      create  tmp/cache/assets
      create  vendor
      create  vendor/.keep
      create  test/fixtures/files
      create  test/fixtures/files/.keep
      create  test/controllers
      create  test/controllers/.keep
      create  test/mailers
      create  test/mailers/.keep
      create  test/models
      create  test/models/.keep
      create  test/helpers
      create  test/helpers/.keep
      create  test/integration
      create  test/integration/.keep
      create  test/channels/application_cable/connection_test.rb
      create  test/test_helper.rb
      create  test/system
      create  test/system/.keep
      create  test/application_system_test_case.rb
      create  storage
      create  storage/.keep
      create  tmp/storage
      create  tmp/storage/.keep
      remove  config/initializers/cors.rb
      remove  config/initializers/new_framework_defaults_7_0.rb
       apply  /tmp/guix-build-ruby-rspec-rails-6.0.1.drv-0/source/example_app_generator/generate_app.rb
     prepend    Rakefile
        gsub    Gemfile
        gsub    Gemfile
        gsub    Gemfile
        gsub    Gemfile
        gsub    Gemfile
        gsub    Gemfile
      append    Gemfile
        gsub    Gemfile
        gsub    Gemfile
        gsub    Gemfile
      append    Gemfile
      create    maintenance-branch
      create    ci_retry_bundle_install.sh
        gsub    ci_retry_bundle_install.sh
        gsub    ci_retry_bundle_install.sh
       chmod    ci_retry_bundle_install.sh
    conflict    app/assets/config/manifest.js
<config/manifest.js? (enter "h" for help) [Ynaqdhm]
       force    app/assets/config/manifest.js
    conflict    app/assets/stylesheets/application.css
<ts/application.css? (enter "h" for help) [Ynaqdhm]
       force    app/assets/stylesheets/application.css
./ci_retry_bundle_install.sh 2>&1
Starting bundle install using shared bundle path
[DEPRECATED] The `--path` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local path '/tmp/guix-build-ruby-rspec-rails-6.0.1.drv-0/source/../bundle'`, and stop using this flag
Your Gemfile lists the gem sqlite3 (~> 1.4) more than once.
You should probably keep only one of them.
Remove any duplicate entries and specify the gem only once.
While it's not a problem now, it could cause errors if you change the version of one of them later.
`/homeless-shelter` is not a directory.
Bundler will use `/tmp/guix-build-ruby-rspec-rails-6.0.1.drv-0/bundler20230317-87-w9w31q87' as your home directory temporarily.
Could not reach host index.rubygems.org. Check your network connection and try
again.
rake aborted!
Command failed with status (17): [./ci_retry_bundle_install.sh 2>&1...]
/tmp/guix-build-ruby-rspec-rails-6.0.1.drv-0/source/Rakefile:39:in `block (3 levels) in <top (required)>'
/tmp/guix-build-ruby-rspec-rails-6.0.1.drv-0/source/Rakefile:73:in `block (2 levels) in in_example_app'
/gnu/store/r2i29lm86yj10q5f99ivgr2pc7jm9s4i-bundler-2.4.8/lib/ruby/vendor_ruby/gems/bundler-2.4.8/lib/bundler.rb:401:in `block in with_original_env'
/gnu/store/r2i29lm86yj10q5f99ivgr2pc7jm9s4i-bundler-2.4.8/lib/ruby/vendor_ruby/gems/bundler-2.4.8/lib/bundler.rb:664:in `with_env'
/gnu/store/r2i29lm86yj10q5f99ivgr2pc7jm9s4i-bundler-2.4.8/lib/ruby/vendor_ruby/gems/bundler-2.4.8/lib/bundler.rb:401:in `with_original_env'
/tmp/guix-build-ruby-rspec-rails-6.0.1.drv-0/source/Rakefile:70:in `block in in_example_app'
/tmp/guix-build-ruby-rspec-rails-6.0.1.drv-0/source/Rakefile:69:in `chdir'
/tmp/guix-build-ruby-rspec-rails-6.0.1.drv-0/source/Rakefile:69:in `in_example_app'
/tmp/guix-build-ruby-rspec-rails-6.0.1.drv-0/source/Rakefile:38:in `block (2 levels) in <top (required)>'
/gnu/store/l7a6068vvi424q2rkf9f6yn9mych39sf-ruby-rake-13.0.6/lib/ruby/vendor_ruby/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
Tasks: TOP => default => acceptance => smoke:app => generate:app
(See full trace by running task with --trace)
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "rake" arguments: ("default") exit-status: 1 term-signal: #f stop-signal: #f>
phase `check' failed after 5.0 seconds
command "rake" "default" failed with status 1
builder for `/gnu/store/11mnywjsjhycg5a4bd33npjikmak04yq-ruby-rspec-rails-6.0.1.drv' failed with exit code 1
@ build-failed /gnu/store/11mnywjsjhycg5a4bd33npjikmak04yq-ruby-rspec-rails-6.0.1.drv - 1 builder for `/gnu/store/11mnywjsjhycg5a4bd33npjikmak04yq-ruby-rspec-rails-6.0.1.drv' failed with exit code 1
derivation '/gnu/store/11mnywjsjhycg5a4bd33npjikmak04yq-ruby-rspec-rails-6.0.1.drv' offloaded to 'localhost' failed: build of `/gnu/store/11mnywjsjhycg5a4bd33npjikmak04yq-ruby-rspec-rails-6.0.1.drv' failed
build of /gnu/store/11mnywjsjhycg5a4bd33npjikmak04yq-ruby-rspec-rails-6.0.1.drv failed
View build log at '/var/log/guix/drvs/11/mnywjsjhycg5a4bd33npjikmak04yq-ruby-rspec-rails-6.0.1.drv'.
guix build: error: build of `/gnu/store/11mnywjsjhycg5a4bd33npjikmak04yq-ruby-rspec-rails-6.0.1.drv' failed

Thanks for your consideration!

The issue provided is bundler not being able to install gems, the rspec-rails test suite is dependent on being able to generate rails apps to test things insitu, but if you were able to get bundler to install from a local cache that would alleviate your difficulty.
I'm going to close this as "not planned" as its not something I feel we can dedicate the time to, but if you find something actionable for us to do to allow you to install gems from a cache of other package store (I"m assuming guix is what youre trying to use here) I'll happily review a PR.

OK; It's hard for me to suggest something because I have zero experience with Rails applications, but if I revisit the question in more depth I'll remember to do so.  Thanks!


Install 'mime-types' outside of bundle

It's needed to load rest-client in irb/automate.  For bundle, we override with local path 'mime-types-redirector'
https://bugzilla.redhat.com/show_bug.cgi?id=1518865

cc @Fryguy @ NickLaMuro

Gaprindashvili backport details:
$ git log -1
commit bb226ab0907912b62723dc4662992ba5dec0a0b5
Author: Jason Frey<EMAIL_ADDRESS>Date:   Mon Dec 4 16:39:03 2017 -0500

    Merge pull request #254 from simaishi/add_mime_types

    Install 'mime-types' outside of bundle
    (cherry picked from commit 13c4d92aa883974ec8db92cefe79639cd0935938)

    https://bugzilla.redhat.com/show_bug.cgi?id=1518865


Attribute names are not in quotation marks

I tried converting vscode's settings.json to nix and everything was fine, but I found that the property names were not in quotation marks
json:
{
  "[dart]": {
    "editor.formatOnSave": true,
    "editor.formatOnType": true,
    "editor.rulers": [90],
    "editor.selectionHighlight": false,
    "editor.suggest.snippetsPreventQuickSuggestions": false,
    "editor.suggestSelection": "first",
    "editor.tabCompletion": "onlySnippets",
    "editor.wordBasedSuggestions": "off"
  },

  "workbench.iconTheme": "catppuccin-mocha",
  "workbench.list.automaticKeyboardNavigation": false
}

nix:
{
  [dart] = {
    editor.formatOnSave = true;
    editor.formatOnType = true;
    editor.rulers = [
      90
    ];
    editor.selectionHighlight = false;
    editor.suggest.snippetsPreventQuickSuggestions = false;
    editor.suggestSelection = "first";
    editor.tabCompletion = "onlySnippets";
    editor.wordBasedSuggestions = "off";
  };
  workbench.iconTheme = "catppuccin-mocha";
  workbench.list.automaticKeyboardNavigation = false;
}

Expected is:
nix:
{
  "[dart]" = {
    "editor.formatOnSave" = true;
    "editor.formatOnType" = true;
    "editor.rulers" = [
      90
    ];
    "editor.selectionHighlight" = false;
    "editor.suggest.snippetsPreventQuickSuggestions" = false;
    "editor.suggestSelection" = "first";
    "editor.tabCompletion" = "onlySnippets";
    "editor.wordBasedSuggestions" = "off";
  };
  "workbench.iconTheme" = "catppuccin-mocha";
  "workbench.list.automaticKeyboardNavigation" = false;
}

Keys don't need to be wrapped in quotation marks unless they have certain characters right? It is a bug that [dart] isn't in quotes but the rest is expected.

I've fixed it in https://github.com/uncenter/json-to-nix/commit/232b5d5da6c2dec0f76b63a47c108d428e4e438d. Your original JSON now becomes:
{
  "[dart]" = {
    editor.formatOnSave = true;
    editor.formatOnType = true;
    editor.rulers = [
      90
    ];
    editor.selectionHighlight = false;
    editor.suggest.snippetsPreventQuickSuggestions = false;
    editor.suggestSelection = "first";
    editor.tabCompletion = "onlySnippets";
    editor.wordBasedSuggestions = "off";
  };
  workbench.iconTheme = "catppuccin-mocha";
  workbench.list.automaticKeyboardNavigation = false;
}

Only keys that have to be quoted are quoted.

Totally right! Let me make another fix, sorry!

Fixed in https://github.com/uncenter/json-to-nix/commit/6a26a4439f0d95de0fb6a83a1c6b29edb2c24386!


Enhancement: Mini-maps / Split Maps

Any chance we could get support for a minimap style setup?
I'd love to be able to have a smaller bit of my map zoomed in a bit and to be following an object, with a larger map showing an overview of the area.
I think this would likely need the sync and clonelayer plugins here: https://leafletjs.com/plugins.html#minimaps--synced-maps

or how about this one ? https://github.com/Norkart/Leaflet-MiniMap

Looks great! My key feature is the ability to control the main map and minimap independently if desired with the option to sync :)

OK - now in v 2.5

Awesome! Many thanks for the hard work!


Fix Application Process Fetch Interactions

Re-launch is a little messed up since it relies on an Application existing, the logic was a little faulty here is this meant it wasn't always possible to fetch the last-launched app process. This fixes that.

lgtm

It looks instances of Simulators are accumilating over tests which is causing notifications to be duplicated. There's probably a cycle in the Simulator infrastructure somewhere that is causing this.

So it looks like most of this was due to ordering issues with notifications with changes in shutdown and notification receiving behaviour. This has been fixed with some juggling around of the assertion methods.


[4.0] UuidVX::fromString should fail if provided string belongs to a different version

Describe the bug
Specific version factory, unlike the general one (RamsayUuid::uuidX()) should fail if provided string belongs to a different version
To Reproduce...
        $uuid4String = RamseyUuid::uuid4()->toString();
        $uuid = UuidV1::fromString($uuid4String);
        assert($uuid instanceof UuidV1);

Expected behavior
UuidV1::fromString should throw InvalidArgumentException
Screenshots or output

UuidV1::fromString returns instance of UuidV4
assert fails

Environment details

OS: Windows 10
PHP version: 7.4
ramsey/uuid version: 4.0

Good catch. This is a result of these classes extending Ramsey\Uuid\Uuid right now. Technically, they shouldn't even have the static methods, since these methods are not part of the interface. In version 5.0, Ramsey\Uuid\Uuid will be a final, static class, and these subclasses will not have these static methods, so I'm not sure whether this requires any action at this point.

Is 5.0 coming soon?

Not until PHP 8. I just released 4.0 two days ago. :-)


How about a tag

So we can finally start using this in projects that have the default minimum stability (stable) specified in Composer.

RIP @igorw. In your memory I have erected a tagged version of your repository.

and that is dead too


Demanded bits based pruning

I don't understand the implementation here, why not just reuse the existing, well-tested, and useful demanded bits from LLVM?
also this needs a few negative and a few positive test cases


Please review "Cases where composite build substitutions won’t work"

Issue type
Wrong or misleading information
Problem description
I'm not sure how much of that part is recent information.
For example I cannot remember a time when using maven-publish plugin made composite builds not usable.
Would be nice if you could review and correct or clarify that section.
Context (optional)
No response
Page with the problem
https://docs.gradle.org/current/userguide/composite_builds.html#included_build_substitution_limitations

This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

I added this to 8.12's list. We'll take a look


mainly added tests, some small fixes

Thank you ! Do you know why the codecov report can't compare to the base branch ?

Thank you ! Do you know why the codecov report can't compare to the base branch ?

I just heard that integration with codecov is still worked on, this seems to be a known issue.

Thank you ! Do you know why the codecov report can't compare to the base branch ?

The base of this branch was before the commit that introduced codecov, so we didn't have coverage for the main branch at the correct commit, it should fix itself for future PRs.


Performance problems in files which defined many functions

Try to enable git_authors and open this file:
https://github.com/neovim/neovim/blob/master/src/nvim/ex_docmd.c
It will load up your computer.

disalbe git author will solve this:
        config = {
            enable = true,
            sections = {
                git_authors = false,
            },
        },

You can also use https://github.com/LunarVim/bigfile.nvim plugin to disable it when the file is huge.

These of course could avoid the load-up. So I only report the issue in such a limited situation, which I already explained:

Try to enable git_authors and open this file:

sorry. I am missing this when  I reading.


fix(remove custom code for aws-cdk-migration)

*Issue #, if available:*537
Description of changes:
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: githubautobuild-for-cdk-v2
Commit ID: c38740e29f855ce7224b3d1425d155329871fd64
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: c38740e29f855ce7224b3d1425d155329871fd64
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: c83bfd40ba26a2a8c67d8e3869b409e4332d79d0
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: c83bfd40ba26a2a8c67d8e3869b409e4332d79d0
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: bcc674d8eb6a5d86db5bbd0d30560a67c4379008
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: bcc674d8eb6a5d86db5bbd0d30560a67c4379008
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: a9aeb4f6e044b6151d0c99f2561cdd32a3fe902b
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: a9aeb4f6e044b6151d0c99f2561cdd32a3fe902b
Result: SUCCEEDED
Build Logs (available for 30 days)

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


Bindable picker doesn't work with ObservableCollection changes

On the pickers preview on the sample app, 3 persons are added to the viewModel's list but the picker is empty (the label above does work).

Yes, i see it.
Thats because the original Xamarin cast items change get not fired. See https://github.com/xamarin/Xamarin.Forms/blob/master/Xamarin.Forms.Platform.Android/Renderers/PickerRenderer.cs#L46
In iOS i've made a custom renderer that's why work in iOS https://github.com/NaylahProject/Naylah/blob/master/Naylah.Xamarin.iOS/Renderers/PickerRenderer.cs#L75
I will fix that, while this u can easily workaround it with:
var personsList = new ObservableCollection<Person>();
personsList.Add(new Person() { Name = "Peter" });
personsList.Add(new Person() { Name = "Joana" });
personsList.Add(new Person() { Name = "Naylah" });
PersonsList = personsList;

Perfect, thanks a lot!


Allow updates to groups/users without removing/recreating them

Looking at the code (https://github.com/angely-dev/freeradius-api/blob/master/src/api.py#L9), the lack of support for updating entities is intentionally, and it's recommended to remove and re-create entities when an update is needed.
However, this is problematic for the use case where you want to update a group that already has users attached. I would like to update this group to add some more replies, but removing this isn't possible without removing the group (and links to the users). Also, since this isn't possible in one atomic operation, the users will be unlinked to a group for a brief moment.
I'm thinking on adding this functionality, but will be this be accepted in this project, or is this beyond the scope of this project?

I do get your point. We could add a PUT endpoint to fully replace the existing group in one operation. But that would mean re-sending all group fields (attributes and user belongings) so not really convenient, especially if the group has thousands and thousands of users (which is not rare).
A PATCH operation seems to be more suitable, yet trickier to implement. RFC 6902 (JSON Patch) and RFC 7386 (JSON Merge Patch) provide some guidance but we could go simpler for this specific need (and I doubt there will be another update need):

Add a GroupUpdate request model in api.py

class GroupUpdate(BaseModel):
    checks: List[AttributeOpValue] = []
    replies: List[AttributeOpValue] = []

    @model_validator(mode='after')
    def check_fields_on_init(self):
        if not (self.checks or self.replies):
            raise ValueError('Group must have at least one check or one reply attribute')
        return self

Add a PATCH endpoint:

@router.patch('/groups/{groupname}', tags=['groups'], status_code=200, response_model=Group, responses={**e404_response})
def patch_group(groupname: str, group: GroupUpdate, response: Response):
    if not group_repo.exists(groupname):
        raise HTTPException(404, 'Given group does not exist')

    group_repo.update(groupname, group.checks, group.replies)
    response.headers['Location'] = f'{API_URL}/groups/{groupname}'
    return group_repo.find_one(groupname)

Add GroupRepository.update method which overwrites checks/replies attributes (delete old ones and insert new ones)

Contributions are welcomed. Do you have another update pattern in mind?

I had already prepared a PUT request to fully replace an entity in one operation (so it's in the same transaction, fixing the split second time frame where a user is gone). I was indeed thinking on using a PATCH to update parts of the entity.
I can draft up a merge request next week.

I've added a merge request for a PUT request here: https://github.com/angely-dev/freeradius-api/pull/6
I'll look at the PATCH next to update only specified fields. This PATCH is mainly useful to update the checks of a group without specifying all the users. The difference will be something like:
For a PUT to /groups/something
{
    "replies": [
        {"attribute": "test", "op": ":=", "value": reply}
    ]
}

This will remove all users, and checks since those aren't specified.
For a PATCH to /groups/something
{
    "replies": [
        {"attribute": "test", "op": ":=", "value": reply}
    ]
}

This will only modify all replies, the users, and checks aren't touched since they are not specified.
The same can be used to update the checks of a user without having to specify the replies and groups again.
I hope this works with pydantic. I should be able to tell when a field is missing in the input, so when you specify the groups: [], it can remove all groups, but when you don't pass it, it shouldn't touch the groups.
Does this makes sense?

Okay, when implementing this, I've noticed that there is no real benefit of having a PUT, since you can just do a PATCH to /groups/something and specify an empty list for checks and replies to do the same:
Example 1
PATCH /groups/something
{
    "checks": [],
    "users": [],
    "replies": [
        {"attribute": "test", "op": ":=", "value": reply}
    ]
}

This will remove the checks and users and replace all replies.
Example 2
PATCH /groups/something
{
    "replies": [
        {"attribute": "test", "op": ":=", "value": reply}
    ]
}

This will keep the existing checks and users, but replace all replies.


Split multiple dictionaries

[ ] Add a test case that tests for duplicated keys in the input data.
[ ] Simplify code to assume a list and just loop over the list. Ensure that it behaves correctly if a key is duplicated, and that the first/last is kept.


Automatic PR from RestAPI-PR1596

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/1596

In https://github.com/Azure/azure-sdk-for-python/pull/1413


Add 2.9.0 release notes

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Caused by: java.lang.ClassNotFoundException: org.apache.hc.core5.http2.HttpVersionPolicy
»  	at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:476)
»  	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:589)
»  	at java.base/java.net.FactoryURLClassLoader.loadClass(URLClassLoader.java:904)
»  	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)

will handled by https://github.com/opensearch-project/notifications/pull/703


Get Polygon maintainer

[ ] Launch Fortune (https://github.com/humanprotocol/fortune) on Polygon
[ ] Verify the scanner on polygon is correct
[ ] Verify the location of the polygon smart contracts

HMT contract "owner"(actually, they owns Proxy) - is Polygon team. @AmrEssamSh is trying to reach them. but still no luck, they just ignore his requests, unfortunately

Verify the scanner on polygon is correct
Scanner - polygonscan.com or dashboard.humanprotocol.org?

Verify the location of the polygon smart contracts
This is already done. We deployed factory, KV store. HMT deployed by Polygon team a while ago. Maybe I missing something?


[python-package] [c++] support scipy sparse arrays

Summary
LightGBM currently has APIs to support two formats of sparse matrices:

CSC = "Compressed Sparse Column"
CSR  = "Compressed Sparse Row"

In the Python library scipy, these are represented by classes scipy.sparse.csc_matrix and scipy.sparse.csr_matrix, respectively.
Per scipy's docs (link)

This package is switching to an array interface, compatible with NumPy arrays, from the older matrix interface. We recommend that you use the array objects (bsr_array, coo_array, etc.) for all new work.

lightgbm should add support for scipy.sparse.csc_array and scipy.sparse.csr_array in all places that currently support the corresponding *_matrix classes.
Motivation
Allows continued use of scipy sparse types with lightgbm, even after future scipy releases remove those matrix types.
Description
See the discussion in #6348 for more information.
References
Created based on this comment: https://github.com/microsoft/LightGBM/pull/6348#issuecomment-1973471486
Good visual summary of these types: https://matteding.github.io/2019/04/25/sparse-matrices/#compressed-sparse-rowcolumn

Closed in favor of being in https://github.com/microsoft/LightGBM/issues/2302. We decided to keep all feature requests in one place.
Welcome to contribute this feature! Please re-open this issue (or post a comment if you are not a topic starter) if you are actively working on implementing this feature.


How to train offline prediction model in 5.0

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (Linux Ubuntu 18.04):
Apollo installed from (source):
Apollo version (5.0):

Steps to reproduce the issue:

i followed the guide here https://github.com/ApolloAuto/apollo/blob/fc11a0782bd3eb037bf3a9de99392d7f198d0970/docs/howto/how_to_train_prediction_mlp_model.md and found ** feature_extraction.sh ** is deleted in 5.0. So which file should i use to train prediction model offline?

also , i tried to copy feature_extraction.sh from v3.5 to v5.0 and update several dependency, then, play demo. i got a lot error message and an empty training_data.npy
"[prediction]  E0303 14:45:34.901347  5423 right_of_way.cc:110] [prediction] Null lane info pointer found.
[prediction]  E0303 14:45:34.901369  5423 right_of_way.cc:110] [prediction] Null lane info pointer found.
[prediction]  E0303 14:45:34.901387  5423 right_of_way.cc:110] [prediction] Null lane info pointer found."

Supporting materials (screenshots, command lines, code/script snippets):

Hi, I am also facing the same issue, any workaround/solution?

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


Slider multi-touch v2

Following on from #77 but based on dev branch.
I hope the way I merged changes is appropriate here.
Also added some comments about slider vs mouse event clash. I don't think anyone would particularly want or expect to be able to drag a single slider with both mouse and touch at the same time, so it may be worth adapting onTouchStart & mouseDown to be aware of each-other.

So I realise maybe my lack of git / PR practice may be showing here, this should probably not be requested as a merge into master with all the changes from dev along with the new salient ones... oops, my bad.

No worries, seems like it's easy enough for me to change the target branch.

Absolutely—my philosophy when it comes to lil-gui is we should limit our features to things people need now. Let's worry about making the rest of the library accommodate multi-touch when users express the need.
As for the brokenness around the touchend event you mention in #77 — I'm guessing this has to do with the fact that touchend is bound to window. Theoretically, we're checking to make sure that our touch is in changedTouches, and rejecting the event if it's not. But what if a different touch ends, and our touch is still moving? Would it still appear in the changedTouches? Then again, even if that's true, it would just end a drag prematurely and not leave it in the stuck state you're describing... 🤷🏻♂
I believe the pointerevents API is supposed to solve this problem, in that it would spare us from having to bind to window. Sadly it broke a lot of scrolling things when we tried porting it: https://github.com/mrdoob/three.js/pull/24259#issuecomment-1241295585
Thanks again and nice work—let me know if you have any luck with the stuck state, but don't go losing sleep ;)

Absolutely—my philosophy when it comes to lil-gui is we should limit our features to things people need now. Let's worry about making the rest of the library accommodate multi-touch when users express the need.

Yes, fair enough, I was mostly just trying to think of possible permutations & edge-cases etc... although think I would genuinely somewhat benefit right now if it did behave perfectly like that, it's not at all important, and it would change the scope of needed changes significantly.

As for the brokenness around the touchend event you mention in #77 — I'm guessing this has to do with the fact that touchend is bound to window. Theoretically, we're checking to make sure that our touch is in changedTouches, and rejecting the event if it's not. But what if a different touch ends, and our touch is still moving? Would it still appear in the changedTouches? Then again, even if that's true, it would just end a drag prematurely and not leave it in the stuck state you're describing... 🤷🏻♂

Yeah... I really can't find an analytical logical reason for it getting into the state that it did. It seems that changedTouches should be what you'd expect:

For the touchend event, it is a list of the touch points that have been removed from the surface (that is, the set of touch points corresponding to fingers no longer touching the surface).

I tried to come up with other scenarios where window.touchend might not happen when a touch ended - pressing the home button to close the browser, moving the finger outside the window... nothing I've found leads to getting into a bad state.
I suppose there could be a browser bug.
Still, I think my work-around should deal with it should it ever occur again.
I think for this reason we probably shouldn't bother to try to reject mouse events while touch is dragging since that's such an obscure edge-case anyway, and we couldn't check e.touches in the same way in mouseDown, so it seems like we'd have to use the old method which could get stuck.

I believe the pointerevents API is supposed to solve this problem, in that it would spare us from having to bind to window. Sadly it broke a lot of scrolling things when we tried porting it: mrdoob/three.js#24259 (comment)

Interesting, I might read up on that more at some point.

Thanks again and nice work—let me know if you have any luck with the stuck state, but don't go losing sleep ;)

Cheers! As I say, I think that this change should prevent problems with it, without doing any other harm.

Hi again, I'm going through old PR's and issues today. I appreciate your help with this—it doesn't seem like the benefits of this change justified the complexity though. Maybe it could be released as an add-on at some point in the future?
Thanks again, -g


shield.daemon.domain not used in shield-agent

I cannot find where these properties are being referenced.
It look like the logic on the post-start script has changed to expect the shield.agent.autoprovision property to be the server endpoint.

Can you remove the property from the spec file and then test it locally to ensure that it doesn't cause any regressions?

yup will do

They are used here: https://github.com/starkandwayne/shield-boshrelease/blob/master/jobs/shield-daemon/templates/config/shieldd.conf#L30


Aws::S3::Errors::InvalidArgument Error on Remote URL Upload

Here's the stack trace which should help point to the file/command causing the issue:
Aws::S3::Errors::InvalidArgument:
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/aws-sdk-core-2.0.48/lib/seahorse/client/plugins/raise_response_errors.rb:15:in `call'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/aws-sdk-core-2.0.48/lib/aws-sdk-core/plugins/s3_sse_cpk.rb:18:in `call'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/aws-sdk-core-2.0.48/lib/seahorse/client/plugins/param_conversion.rb:22:in `call'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/aws-sdk-core-2.0.48/lib/aws-sdk-core/plugins/response_paging.rb:10:in `call'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/aws-sdk-core-2.0.48/lib/seahorse/client/plugins/response_target.rb:18:in `call'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/aws-sdk-core-2.0.48/lib/seahorse/client/request.rb:70:in `send_request'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/aws-sdk-core-2.0.48/lib/seahorse/client/base.rb:216:in `block (2 levels) in define_operation_methods'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/aws-sdk-resources-2.0.48/lib/aws-sdk-resources/request.rb:24:in `call'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/aws-sdk-resources-2.0.48/lib/aws-sdk-resources/operations.rb:41:in `call'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/aws-sdk-resources-2.0.48/lib/aws-sdk-resources/operation_methods.rb:19:in `block in add_operation'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/carrierwave-aws-0.6.0/lib/carrierwave/storage/aws_file.rb:56:in `store'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/carrierwave-aws-0.6.0/lib/carrierwave/storage/aws.rb:16:in `block in store!'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/carrierwave-aws-0.6.0/lib/carrierwave/storage/aws.rb:15:in `tap'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/carrierwave-aws-0.6.0/lib/carrierwave/storage/aws.rb:15:in `store!'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/carrierwave-0.10.0/lib/carrierwave/uploader/store.rb:59:in `block in store!'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/carrierwave-0.10.0/lib/carrierwave/uploader/callbacks.rb:17:in `with_callbacks'
... 16 levels...
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/activerecord-4.2.3/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/activerecord-4.2.3/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/activerecord-4.2.3/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/activerecord-4.2.3/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/activerecord-4.2.3/lib/active_record/transactions.rb:220:in `transaction'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/activerecord-4.2.3/lib/active_record/transactions.rb:348:in `with_transaction_returning_status'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/activerecord-4.2.3/lib/active_record/transactions.rb:291:in `save!'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/activerecord-4.2.3/lib/active_record/persistence.rb:51:in `create!'
    from (irb):3
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/railties-4.2.3/lib/rails/commands/console.rb:110:in `start'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/railties-4.2.3/lib/rails/commands/console.rb:9:in `start'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:68:in `console'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/railties-4.2.3/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
    from /Users/karanjain/.rvm/gems/ruby-2.2.0@tinygive/gems/railties-4.2.3/lib/rails/commands.rb:17:in `<top (required)>'
    from bin/rails:4:in `require'
    from bin/rails:4:in `<main>'

And here's the gem versions being used:
carrierwave-aws (0.6.0)
      aws-sdk (~> 2.0.47)
      carrierwave (~> 0.7)
 aws-sdk (2.0.48)
      aws-sdk-resources (= 2.0.48)
    aws-sdk-core (2.0.48)
      builder (~> 3.0)
      jmespath (~> 1.0)
      multi_json (~> 1.0)
    aws-sdk-resources (2.0.48)
      aws-sdk-core (= 2.0.48)

@krnjn: Please take a look at https://github.com/sorentwo/carrierwave-aws/issues/57#issuecomment-117279126, I think you are running into the same issue.

@sorentwo here's my config block – I don't think its the same issue:
CarrierWave.configure do |config|
  ## FOR HEROKU
  config.root = Rails.root.join('tmp') # adding these...
  config.cache_dir = 'carrierwave' # ...two lines

  ## AWS CONFIG
  config.storage    =  :aws                  # required
  config.aws_bucket =  ENV['S3_BUCKET']      # required
  config.aws_acl    =  :public_read
  config.aws_credentials = {
    access_key_id:      ENV['S3_KEY'],       # required
    secret_access_key:  ENV['S3_SECRET'],     # required
    region:             ENV['S3_REGION']      # required
  }
end

@krnjn: Are you getting this consistently, only from uploaded files? Can you give me some more context to recreate the bug?

@sorentwo: if you use the dependencies I listed above (mainly just use carrierwave-aws 0.6.0) and attempt to save an image/attachment/file to AWS using carrierwave's remote_url method from the rails console, you'll get the error. For example, create a User model with attributes :name and :avatar mounted via Carrierwave with mount_uploader :avatar, ImageUploader, and then try:
User.create!(name: 'test name', remote_avatar_url: 'http://www.femto.it/wp-content/uploads/2014/04/default-user-avatar.png')

It will not accept the remote_avatar_url in this format and save it to S3. There may be additional cases in which it does not work, but this was my primary issue.

That's very helpful, thank you.

Im getting Aws::S3::Errors::InvalidArgument without more information after updating from 0.5.0 to 0.6.0. But im not using remote_url's.
@krnjn
According the Changelog you have to change :public_read to "public-read"

@philipgiuliani: You are absolutely correct, the :public_read vs 'public-read' difference is probably the issue here.

Oh i havent even tested if this is causing the issue for me, i also had forgotten it when i updated!
I will try to update it again tomorrow :)

@sorentwo that seemed to fix it. Thanks @philipgiuliani!

I'm adding config validation to the 1.X branch to catch these sorts of problems during startup, rather than at runtime.

This is still a problem at the end of 2019.

@mdchaney A pull request is always welcome. This issue is over four years old and quite honestly, I don't remember it at all.

If I get time next month I'll track it down.  My belief is that it's an issue when the acl on the file is set to "public" but the bucket is set to private.


BlockRules

Implementation and Testing for BlockValidation

[x] Move validate_block() to Consensus
[x] Implement all validation rules from Bitcoin Core
[x] Unit Test

With this, we have all the validation rules in floresta... This pr will now cover some unit test and ensure that all Floresta-Chain call Consensus::validate_block() to validate blocks.

Did you skip headers timestamp validation on purpose?

Yes, to make a separate pr for it, but i see thats not necessary

Could you please rebase and squash the last commits? It's kinda hard to parse the changes as is.

Suggestion: Everything looks good to me, with the exception of https://github.com/vinteumorg/Floresta/pull/198#discussion_r1739291770. I think we can keep this out of this PR and think about it a little more in a new one (but it's up to you)

Suggestion: Everything looks good to me, with the exception of #198 (comment). I think we can keep this out of this PR and think about it a little more in a new one (but it's up to you)

Suggestion: Everything looks good to me, with the exception of https://github.com/vinteumorg/Floresta/pull/198#discussion_r1739291770. I think we can keep this out of this PR and think about it a little more in a new one (but it's up to you)

If we would this out of this PR, 80% of the functionality that i added in this PR would be useless.
I cooked something in e1d1ea014983e01ef46959916eb1aea659b59518 see if you like in the review

@Davidson-Souza
Please Review this

I'll run it on mainnet and see if it syncs fine

FYI: the CI will not be green unless you rebase after #244

[2024-10-08 12:25:26 ERROR floresta_wire::p2p_wire::sync_node] Invalid block Header { block_hash: 0x00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048, version: Version(1), prev_blockhash: 0x000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, merkle_root: 0x0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e68bebb44a74b1efd512098, time:<PHONE_NUMBER>, bits: CompactTarget(486604799), nonce:<PHONE_NUMBER> } received by peer 0 reason: BlockValidation(BadBlockVersion)
[2024-10-08 12:25:27 ERROR floresta_wire::p2p_wire::sync_node] Error processing block: PeerMisbehaving
[2024-10-08 12:25:27 INFO floresta_wire::p2p_wire::node] Peer disconnected: 0
[2024-10-08 12:25:27 ERROR floresta_wire::p2p_wire::sync_node] 267:crates/floresta-wire/src/p2p_wire/sync_node.rs - NoPeersAvailable
[2024-10-08 12:25:27 WARN floresta_wire::p2p_wire::sync_node] No utreexo peers connected, trying to create a new one
[2024-10-08 12:25:27 INFO floresta_wire::p2p_wire::node] New peer id=1 version=/btcwire:0.5.0/utreexod:0.4.1/ blocks=864772 services=ServiceFlags(NETWORK|BLOOM|WITNESS|NETWORK_LIMITED|UTREEXO)
[2024-10-08 12:25:28 INFO floresta_wire::p2p_wire::running_node] starting running node...
^C[2024-10-08 12:25:37 INFO floresta_wire::p2p_wire::node] Shutting down node

Forgot to try this again after some changes, my bad ! But this error seems really strange...

FYI: the CI will not be green unless you rebase after #244

Seems like not

[2024-10-10 00:43:09 ERROR floresta_wire::p2p_wire::sync_node] Invalid block Header { block_hash: 0x00000000d1145790a8694403d4063f323d499e655c83426834d4ce2f8dd4a2ee, version: Version(1), prev_blockhash: 0x000000002a22cfee1f2c846adbd12b3e183d4f97683f85dad08a79780a84bd55, merkle_root: 0x7dac2c5666815c17a3b36427de37bb9d2e2c5ccec3f8633eb91a4205cb4c10ff, time:<PHONE_NUMBER>, bits: CompactTarget(486604799), nonce:<PHONE_NUMBER> } received by peer 4 reason: TransactionError(TransactionError { txid: 0xf4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16, error: InvalidScript(UnknownSpentOutput(OutPoint { txid: 0x0437cd7f8525ceed2324359c2d0ba26006d92d856a9c20fa0241106ee5a597c9, vout: 0 })) })

Literally the first transaction in bitcoin history 😆

[2024-10-10 00:43:09 ERROR floresta_wire::p2p_wire::sync_node] Invalid block Header { block_hash: 0x00000000d1145790a8694403d4063f323d499e655c83426834d4ce2f8dd4a2ee, version: Version(1), prev_blockhash: 0x000000002a22cfee1f2c846adbd12b3e183d4f97683f85dad08a79780a84bd55, merkle_root: 0x7dac2c5666815c17a3b36427de37bb9d2e2c5ccec3f8633eb91a4205cb4c10ff, time:<PHONE_NUMBER>, bits: CompactTarget(486604799), nonce:<PHONE_NUMBER> } received by peer 4 reason: TransactionError(TransactionError { txid: 0xf4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16, error: InvalidScript(UnknownSpentOutput(OutPoint { txid: 0x0437cd7f8525ceed2324359c2d0ba26006d92d856a9c20fa0241106ee5a597c9, vout: 0 })) })

Literally the first transaction in bitcoin history 😆

Thats why we need functional tests... LOL it was running fine yesterday... this is actually a strange bug...

@Davidson-Souza I think this is stable and wont break on a random non-standard transaction from the past.

@Davidson-Souza I think this is stable and wont break on a random non-standard transaction from the past.
I tested, but i would like to you test this build too.

I'll test, get back to you soon

It broke again :sweat_smile: .
[2024-10-19 16:39:07 ERROR floresta_wire::p2p_wire::sync_node] Invalid block Header { block_hash: 0x000000000000019c2f79d19c74d62319426b55e5e373393f75852e20b8e7cc61, version: Version(2), prev_blockhash: 0x000000000000024b89b42a942fe0d9fea3bb44ab7bd1b19115dd6a759c0808b8, merkle_root: 0x0b70ce79f0fceddbc51ccb906e317090b926689068dfc97b10df3d6c4fb182d0, time:<PHONE_NUMBER>, bits: CompactTarget(436371822), nonce:<PHONE_NUMBER> } received by peer 0 reason: BlockValidation(BadBlockVersion)

It broke again 😅 .
[2024-10-19 16:39:07 ERROR floresta_wire::p2p_wire::sync_node] Invalid block Header { block_hash: 0x000000000000019c2f79d19c74d62319426b55e5e373393f75852e20b8e7cc61, version: Version(2), prev_blockhash: 0x000000000000024b89b42a942fe0d9fea3bb44ab7bd1b19115dd6a759c0808b8, merkle_root: 0x0b70ce79f0fceddbc51ccb906e317090b926689068dfc97b10df3d6c4fb182d0, time:<PHONE_NUMBER>, bits: CompactTarget(436371822), nonce:<PHONE_NUMBER> } received by peer 0 reason: BlockValidation(BadBlockVersion)

Sorry @Davidson-Souza, couldnt replicate the bug here. Can you give some more infos ? Just by looking at the code i cant address the problem, this block is indeed valid.

Pushed the changes and looks running fine.

Oops. forgot the new things on floresta-chain/benches

Any update on this @jaoleal?

Any update on this @jaoleal?

Sorry, busy with satsconf... 😅
Ill be back soon.

Oh good luck there 🇧🇷


V3: Formulas return #ERROR if no cells are referenced

I am trying to port my application from the V2 library to V3. However the new parsing mechanism seems to require at least one cell reference in a formula to work, e.g. =SUM(1,1) returns #ERROR, whereas in V2 it would return 2. In V3, either the first or second argument has to reference a cell such as A1 or B3 for example.
Is this by design or a bug?

We are going to fix that to keep the compatibility.

It has been fixed.


ModuleInterface: Improve TypedThrows feature guards

Functions that use typed throws anywhere in their signature (including in closure types) need to be surrounded with if $TypedThrows guards in swiftinterfaces.

@swift-ci please smoke test


Add link method to contract constructor

link() is used to link libraries to contracts.
const mylib = await MyLib.new()
MyContract.link("MyLib", mylib.address)
const myContract = await myContract.new()

Truffle v4:
https://github.com/trufflesuite/truffle/blob/v4.1.17/packages/truffle-contract/contract.js#L564
Truffle v5:
https://github.com/trufflesuite/truffle/blob/981e421e771aab4a018151093c5e40d3f1ec2176/packages/contract/lib/contract/constructorMethods.js#L157

don't merge for now

Let me know if there's anything else I have to do to get this merged, thank you!

Thanks! Published as 📦
<EMAIL_ADDRESS><EMAIL_ADDRESS>


Parse multiple module-info.java files in parallel

If the project contains multiple module-info.java files, parse them in parallel using Worker API.
Depends on #22

Gradle 6.4 now has Module support built-in. It allows having one module-info per source set, as each source set can define a Java module.
Please open an issue on https://github.com/gradle/gradle if there is still a problem.