String error code, but data can't be decoded as bytes: DecodingError(InvalidData)

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (f2d0d83 2023-03-24T21:51:43.362828Z)
What command(s) is the bug in?
forge test
Operating System
macOS (Intel)
Describe the bug

check out this PR
run RUST_BACKTRACE=full forge test --match test_mint_unsortedAddresses_reverts

[⠑] Compiling...
No files changed, compilation skipped
The application panicked (crashed).
Message:  String error code, but data can't be decoded as bytes: DecodingError(InvalidData)
Location: evm/src/executor/inspector/cheatcodes/expect.rs:109

This is a bug. Consider reporting it at https://github.com/foundry-rs/foundry

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
                                ⋮ 13 frames hidden ⋮
  14: core::result::Result<T,E>::expect::he0b104188fb8671c
      at <unknown source file>:<unknown line>
  15: foundry_evm::executor::inspector::cheatcodes::expect::handle_expect_revert::h73027d1adb592e06
      at <unknown source file>:<unknown line>
  16: <foundry_evm::executor::inspector::cheatcodes::Cheatcodes as revm::inspector::Inspector<DB>>::call_end::hf186f4a256a342d4
      at <unknown source file>:<unknown line>
  17: foundry_evm::executor::inspector::stack::InspectorStack::do_call_end::h15bfd140512ef3d7
      at <unknown source file>:<unknown line>
  18: <foundry_evm::executor::inspector::stack::InspectorStack as revm::inspector::Inspector<DB>>::call_end::h6d6901286c524721
      at <unknown source file>:<unknown line>
  19: <&mut T as revm::inspector::Inspector<DB>>::call_end::h74d310490befec71
      at <unknown source file>:<unknown line>
  20: revm::evm_impl::EVMImpl<GSPEC,DB,_>::call_inner::hd2102ee76bbbc6dc
      at <unknown source file>:<unknown line>
  21: <revm::evm_impl::EVMImpl<GSPEC,DB,_> as revm::evm_impl::Host>::call::hcfe0bc223ec24dee
      at <unknown source file>:<unknown line>
  22: revm::instructions::host::call::h136062a069100499
      at <unknown source file>:<unknown line>
  23: revm::interpreter::Interpreter::run::hf7e76a195ee2b66a
      at <unknown source file>:<unknown line>
  24: revm::evm_impl::EVMImpl<GSPEC,DB,_>::call_inner::hd2102ee76bbbc6dc
      at <unknown source file>:<unknown line>
  25: <revm::evm_impl::EVMImpl<GSPEC,DB,_> as revm::evm_impl::Transact>::transact::h39826c4106b59cf0
      at <unknown source file>:<unknown line>
  26: foundry_evm::executor::backend::Backend::inspect_ref::h62e2984a5c3ed75e
      at <unknown source file>:<unknown line>
  27: foundry_evm::executor::Executor::call_raw_with_env::hb06d350f509b242a
      at <unknown source file>:<unknown line>
  28: foundry_evm::executor::Executor::execute_test::hf60ee3720f84031c
      at <unknown source file>:<unknown line>
  29: forge::runner::ContractRunner::run_test::h5e30ad8643c270f8
      at <unknown source file>:<unknown line>
  30: forge::runner::ContractRunner::run_tests::{{closure}}::he653a45d3b624e77
      at <unknown source file>:<unknown line>
  31: <rayon::iter::flat_map::FlatMapFolder<C,F,<C as rayon::iter::plumbing::Consumer<<U as rayon::iter::IntoParallelIterator>::Item>>::Result> as rayon::iter::plumbing::Folder<T>>::consume::hf1457544cd605ae5
      at <unknown source file>:<unknown line>
  32: rayon::iter::plumbing::Folder::consume_iter::h998b7777e2c837f2
      at <unknown source file>:<unknown line>
  33: rayon::iter::plumbing::Producer::fold_with::h012078c8a93867bd
      at <unknown source file>:<unknown line>
  34: rayon::iter::plumbing::bridge_producer_consumer::helper::hd4c12c77142d004e
      at <unknown source file>:<unknown line>
  35: rayon::iter::plumbing::bridge_producer_consumer::h1a237239bc772cc8
      at <unknown source file>:<unknown line>
  36: <rayon::iter::plumbing::bridge::Callback<C> as rayon::iter::plumbing::ProducerCallback<I>>::callback::h6b7fa77f150b5f83
      at <unknown source file>:<unknown line>
  37: <rayon::slice::Iter<T> as rayon::iter::IndexedParallelIterator>::with_producer::h3a58b0bb92b30864
      at <unknown source file>:<unknown line>
  38: rayon::iter::plumbing::bridge::h17124ca9abb1677d
      at <unknown source file>:<unknown line>
  39: <rayon::slice::Iter<T> as rayon::iter::ParallelIterator>::drive_unindexed::hac83f564a3bb2b1e
      at <unknown source file>:<unknown line>
  40: <rayon::iter::flat_map::FlatMap<I,F> as rayon::iter::ParallelIterator>::drive_unindexed::hcb65ab3c6d3b294c
      at <unknown source file>:<unknown line>
  41: <rayon::iter::map::Map<I,F> as rayon::iter::ParallelIterator>::drive_unindexed::haf89c89ff121058c
      at <unknown source file>:<unknown line>
  42: <rayon::iter::while_some::WhileSome<I> as rayon::iter::ParallelIterator>::drive_unindexed::hf88c22edea9c203c
      at <unknown source file>:<unknown line>
  43: rayon::iter::extend::<impl rayon::iter::ParallelExtend<(K,V)> for alloc::collections::btree::map::BTreeMap<K,V>>::par_extend::h2bb80b52a7ec3ae4
      at <unknown source file>:<unknown line>
  44: rayon::iter::from_par_iter::collect_extended::h627b76907304c439
      at <unknown source file>:<unknown line>
  45: rayon::iter::from_par_iter::<impl rayon::iter::FromParallelIterator<(K,V)> for alloc::collections::btree::map::BTreeMap<K,V>>::from_par_iter::h988837292e97c2fd
      at <unknown source file>:<unknown line>
  46: rayon::iter::ParallelIterator::collect::h417a380fb0759719
      at <unknown source file>:<unknown line>
  47: rayon::result::<impl rayon::iter::FromParallelIterator<core::result::Result<T,E>> for core::result::Result<C,E>>::from_par_iter::h8fb9e0c7f2058e98
      at <unknown source file>:<unknown line>
  48: rayon::iter::ParallelIterator::collect::hb128446a6464bec0
      at <unknown source file>:<unknown line>
  49: forge::runner::ContractRunner::run_tests::ha1b23c17143fee32
      at <unknown source file>:<unknown line>
  50: forge::multi_runner::MultiContractRunner::run_tests::{{closure}}::hab76a5fc20e431ba
      at <unknown source file>:<unknown line>
  51: forge::multi_runner::MultiContractRunner::run_tests::hf928b959e3dfa158
      at <unknown source file>:<unknown line>
  52: forge::multi_runner::MultiContractRunner::test::{{closure}}::ha705ca9691bea13c
      at <unknown source file>:<unknown line>
  53: <rayon::iter::map::MapFolder<C,F> as rayon::iter::plumbing::Folder<T>>::consume::h2a596980f696ce92
      at <unknown source file>:<unknown line>
  54: <rayon::iter::filter::FilterFolder<C,P> as rayon::iter::plumbing::Folder<T>>::consume::hecf95d92fdec7578
      at <unknown source file>:<unknown line>
  55: <rayon::iter::filter::FilterFolder<C,P> as rayon::iter::plumbing::Folder<T>>::consume::hb541229134f21446
      at <unknown source file>:<unknown line>
  56: rayon::iter::plumbing::Folder::consume_iter::hf6e047e1b128a868
      at <unknown source file>:<unknown line>
  57: rayon::iter::plumbing::Producer::fold_with::h7363dfa2b5e8b540
      at <unknown source file>:<unknown line>
  58: rayon::iter::plumbing::bridge_producer_consumer::helper::h9bf2e4ae19aabea5
      at <unknown source file>:<unknown line>
  59: rayon::iter::plumbing::bridge_producer_consumer::helper::{{closure}}::h60dc295483a9f666
      at <unknown source file>:<unknown line>
  60: rayon_core::join::join_context::call_b::{{closure}}::hd26361c63f717b7b
      at <unknown source file>:<unknown line>
  61: rayon_core::job::JobResult<T>::call::{{closure}}::hd2e21c220e0b34d5
      at <unknown source file>:<unknown line>
  62: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::h6ec60c858a647c02
      at <unknown source file>:<unknown line>
  63: std::panicking::try::do_call::h732bf7a0bb3e06d8
      at <unknown source file>:<unknown line>
  64: ___rust_try<unknown>
      at <unknown source file>:<unknown line>
  65: std::panicking::try::he82310d669777b32
      at <unknown source file>:<unknown line>
  66: std::panic::catch_unwind::h3df9122675f751f7
      at <unknown source file>:<unknown line>
  67: rayon_core::unwind::halt_unwinding::h6824ab42aa737905
      at <unknown source file>:<unknown line>
  68: rayon_core::job::JobResult<T>::call::hcb04c134aa8911e8
      at <unknown source file>:<unknown line>
  69: <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute::h8a8f8eab29ffd628
      at <unknown source file>:<unknown line>
  70: rayon_core::job::JobRef::execute::h0a01d90e9e32fcd2
      at <unknown source file>:<unknown line>
  71: rayon_core::registry::WorkerThread::execute::he4df08e38a4ae524
      at <unknown source file>:<unknown line>
  72: rayon_core::registry::WorkerThread::wait_until_cold::hdf5f6fb72b023d60
      at <unknown source file>:<unknown line>
  73: rayon_core::registry::WorkerThread::wait_until::ha034ddba973ea065
      at <unknown source file>:<unknown line>
  74: rayon_core::registry::main_loop::ha7ef7640fdb13deb
      at <unknown source file>:<unknown line>
  75: rayon_core::registry::ThreadBuilder::run::hc3f8469d117c4811
      at <unknown source file>:<unknown line>
  76: <rayon_core::registry::DefaultSpawn as rayon_core::registry::ThreadSpawn>::spawn::{{closure}}::h76e8ad2cebb612b4
      at <unknown source file>:<unknown line>
  77: std::sys_common::backtrace::__rust_begin_short_backtrace::h7d47433eacd28c20
      at <unknown source file>:<unknown line>
  78: std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}::h81c7c026d0cdca25
      at <unknown source file>:<unknown line>
  79: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once::hb2b3cd4825b35d3e
      at <unknown source file>:<unknown line>
  80: std::panicking::try::do_call::hb7fd42016faa3ce1
      at <unknown source file>:<unknown line>
  81: ___rust_try<unknown>
      at <unknown source file>:<unknown line>
  82: std::panicking::try::h3d43ecc650c553ef
      at <unknown source file>:<unknown line>
  83: std::panic::catch_unwind::h60dc47297ac1ce45
      at <unknown source file>:<unknown line>
  84: std::thread::Builder::spawn_unchecked_::{{closure}}::h8cadb59f535f64e8
      at <unknown source file>:<unknown line>
  85: core::ops::function::FnOnce::call_once{{vtable.shim}}::h95b2bd5647f3491b
      at <unknown source file>:<unknown line>
  86: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h29c40c4b4d757fec
      at /rustc/900c3540378c8422b8087ffa3db60fa6c8abfcad/library/alloc/src/boxed.rs:1987
  87: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::hb8c24afeaacfe6bd
      at /rustc/900c3540378c8422b8087ffa3db60fa6c8abfcad/library/alloc/src/boxed.rs:1987
  88: std::sys::unix::thread::Thread::new::thread_start::habe434f21f22795f
      at /rustc/900c3540378c8422b8087ffa3db60fa6c8abfcad/library/std/src/sys/unix/thread.rs:108
  89: __pthread_start<unknown>
      at <unknown source file>:<unknown line>

Probably fixed.

Seems fixed indeed, I get the expected trace from a recent forge:
[PASS] test_mint_unsortedAddresses_reverts() (gas: 54335)
Traces:
  [54335] SS2ERC721Specifics::test_mint_unsortedAddresses_reverts()
    ├─ [8236] → new stdError@0x2e234DAe75C793f67A35089C9d99245E1C58470b
    │   └─ ← 41 bytes of code
    ├─ [0] VM::expectRevert(ADDRESSES_NOT_SORTED)
    │   └─ ← ()
    ├─ [4971] BasicSS2ERC721::mint(stdError: [0x2e234DAe75C793f67A35089C9d99245E1C58470b])
    │   ├─ emit Transfer(from: 0x0000000000000000000000000000000000000000, to: 0x0000000000000000000000000000000000000002, id: 1)
    │   └─ ← revert: ADDRESSES_NOT_SORTED
    └─ ← ()


Horizontal images get converted to vertical images

Describe the Bug
Some images with horizontal format get reformatted to vertical images during upload. The final image is then blurred on the right and left side (instead of eventually upper ans lower side).
Steps to Reproduce

Go to documents list display
Edit a document
Add a new image to that document (e.g. the attached image)
See error

Expected Behavior
Horizontal images keeps its original format adapted to the size ratio defined in the settings
Actual Behavior
Image is displayed vertically.

Still relevant?


Extending ALVR to support alternative VR runtimes and HW encoding options

First off - my deepest respect and appreciation for the ALVR team. Fantastic work. ALVR is the best hope for owners of standalone HMDs to work with Linux.
While ALVR is great for playing Steam games, I would love to see it become the defacto connector / driver for work related applications as well.
XRDesktop promises to deliver a drop-in extension to traditional Linux desktops by allowing users to manipulate desktop windows directly in VR.
It can utilise both SteamVR and Monado as its VR runtime environment, with Monado being preferable (in my opinion) as it supports non-x86 platforms (ARM, RISC-V) apart from it making more sense to have a general purpose VR runtime running in work environments rather than the temptations of a gaming environment.
The option to have Monado as a VR runtime will also make it easier for users to run other / future applications, open source games (i.e. Quake 3, Doom 3, Jedi Knight) and emulators independently of SteamVR on non-x86 or performance constrained platforms.
Would the ALVR team consider adding the following two features to their roadmap:

Choice of runtime; specifically Monado. (Having ALVR optionally work with and autostart Monado instead of SteamVR)
Custom HW encoding acceleration options; i.e. h264_v4l2m2m on Raspberry Pi (arm64) and others; by allowing users to specify / customise FFMPEG encoding configuration

Adding these two features would make ALVR the ultimate solution for owners of standalone headsets working, playing and entertaining with Linux.
Thank you for reading and hopefully taking this request into consideration.

Choice of runtime; specifically Monado. (Having ALVR optionally work with and autostart Monado instead of SteamVR)
Custom HW encoding acceleration options; i.e. h264_v4l2m2m on Raspberry Pi (arm64) and others; by allowing users to specify / customise FFMPEG encoding configuration

Both are planned but no ETA.

@zarik5 Thank you that is great news. I fully understand and appreciate that it will take considerable time and effort to implement, but it's on the roadmap at least. Thanks for reading and replying as well as all your efforts in bringing ALVR to the Linux community :)

(I'd specify that I'm not the author of contributions targeting Linux, but yeah the community has been amazing!)

Well I've seen your activity all over the project and the discussions (i.e. this one since taking over ALVR from the original developer, so the compliment and appreciation to both yourself and the community are more than deserved :) Thanks to yourself and the ALVR community Linux users have a real chance to break the last chains tethering them to dual boot Windows and Linux. In my case VR is truly the last remaining reason to have Windows installed at all.


Updated the build status badge to point to travis-ci.com

Updated the README file.
Build status badge is now pointing to 'travis-ci.com' instead of 'travis-ci.org'
JIRA: https://openedx.atlassian.net/browse/BOM-2089

Thanks for the pull request, @Jawayria! I've created OSPR-5189 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
This is currently a draft pull request. When it is ready for our review and all tests are green, click "Ready for Review", or remove "WIP" from the title, as appropriate.

:warning: We can't start reviewing your pull request until you've submitted a     signed contributor agreement     or indicated your institutional affiliation. Please see the CONTRIBUTING     file for more information.

@Jawayria you should close this PR, now that we've moved to Github Actions.

@Jawayria Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future.


Reduce columns for stat display

Describe your changes
Since the comparison UI were still scaled before we had % comparison, the increase in content due to comparison is pushing content off the grid.
Issue or discord link

Resolves https://github.com/frzyc/genshin-optimizer/issues/1683

Testing/validation

Checklist before requesting a review (leave this PR as draft if any part of this list is not done.)

[ ] I have commented my code in hard-to understand areas.
[ ] I have made corresponding changes to README or wiki.
[ ] For front-end changes, I have updated the corresponding English translations.
[ ] I have run yarn run mini-ci locally to validate format and lint.
[ ] If I have added a new library or app, I have updated the deployment scripts to ignore changes as needed

The single stats column makes it suuuuper long. Could we try reducing the width of the character card/edit button instead? They really don't need to take up like 40% of the width

I think with the character card shrinkage, we can still have 2-column smallest breakpoint for stats

I think with the character card shrinkage, we can still have 2-column smallest breakpoint for stats

There is no way 2 columns can fit on the smallest breakpoint. it is smaller than 600px, with a reasonable support of 360px.


background image and hero form component

implement a hero component which can display the content for the login, signup, and reset password pages which also has a background image off to the side

finished in PR #27


update_project_code_signing

ended up tracking this down: File.write(path, p.gsub(/PROVISIONING_PROFILE = ".*";/, "PROVISIONING_PROFILE = \"#{udid}\";"))
If no profile is selected this line won't exist
Thoughts on improving this?

I agree, that's why this feature is not listed and documented anywhere yet. I haven't had time to work on a better, cleaner solution yet.

I'll close this issue for now, as it's not officially supported right now.


Timeline for provider

We tried yesterday your terraform module for a standard postgres database. The approach seems to be promising
for us, however, we would be more interested in the implementation of the flexible postgres database.
Do you have any timeline for this project?

Hi @dressedfez
Thanks for your interest.
The module is in development and is mostly done. To be fully transparent, we need to reintegrate the Terraform provider used in the "standard" module for user creation implemented a few weeks ago and a peer review to release it.
Unfortunately, I'm not able to provide a ETA since we mostly focus on our customer delivery but it shouldn't be that long.

@BzSpi thanks for the fast feedback. I will watch your project. If possible (needs to be clarified internally) we could help you in a testing phase.

Hello @dressedfez !
The module is just released in v5.0.0 ! :tada:
Feel free to test it and open issues / PRs if needed.
Have a good day !


Sys.config File question

Hi There, my name is Thiago Esteves and I'm working on an application that should execute 2 main tasks:

Handle deployments for another Elixir app, monitoring, restarting or updating when needed
Handle hot upgrades for the monitored Elixir app

For the hot upgrade, I'm using part of the distillery code to generate the .appup files and for the upgrade release functions, the deployer app is connecting via OTP distribution and executing pretty much the steps in this script (but using Elixir syntax). So far I can execute the hot upgrades with no problems, the last issue is related to the config. While looking at your repo, I found the part I was missing which was the sys.config (Thanks!!!)
The idea I have now is to load the sys.config and save the original file, and using the OTP distribution, The deployer app can then run the config providers and generate a sys.config with all needed configurations and save it in the release folder. The next step is to execute the hot upgrade, and later on move the original file to sys.config to avoid having secrets in files.
Sorry for the long explanation, but the question is why you created another file boot.config for the configuration and didn't use the original sys.config?
Thanks in advance

Hi Thiago, so when castle system boots, it brings a preboot instance of the vm up first. The purpose of this instance is only to generate the sys.config for the 'real' system boot, after which it shuts down.
Hot-code upgrades to systems that get their boot config from files other than sys.config leads to misconfiguration after upgrade.


CUDA error: an illegal memory access was encountered

I run the code in server with a rtx A6000 48GB.But i met a error.So i debug the code.I found when run the line in corr.py and get that error.Can someone help me?Thanks!

do you still see that error?

do you still see that error?

I still have this error,and I don't know how to sloved it.I try to run code in A6000(48G memory) server and 3090(24G memory),have the same problem.And I found your image used in code is resolution of 680x1200(Replica),i resize the image with the resolution of 480x1600.And i got another error:NANs in L_inv!! #18

It is the error information.It happens in the begin of the code.I use the A6000 server run your code.Thanks for your help!
ic| os.environ['CUDA_VISIBLE_DEVICES']: '0' 10:14:17 SUCCESS  NGP Device set to: 0 10:14:17 INFO     Loading network config from: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/configs/nerf/base.json 10:14:17 INFO     GridEncoding:  Nmin=16 b=1.51572 F=2 T=2^19 L=16 10:14:17 INFO     Density model: 3--[HashGrid]-->32--[FullyFusedMLP(neurons=64,layers=3)]-->1 10:14:17 INFO     Color model:   3--[Composite]-->16+16--[FullyFusedMLP(neurons=64,layers=4)]-->3 10:14:17 INFO       total_encoding_params=13074912 total_network_params=10240 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 0 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 0 viz_index is empty, nothing to visualize Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 1 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 1 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 1 viz_index is empty, nothing to visualize Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 2 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 2 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 2 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 2 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 2 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 2 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 2 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 2 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 2 viz_index is empty, nothing to visualize Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 3 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 3 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 3 viz_index is empty, nothing to visualize Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 4 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 4 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 4 viz_index is empty, nothing to visualize Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 5 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 5 viz_index is empty, nothing to visualize Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 6 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 6 viz_index is empty, nothing to visualize Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 7 Fusion packet from SLAM module is None... RaftVisualFrontend.forward ic| self.last_kf_idx: 7 Traceback (most recent call last):   File "/home/wjt/code/NeRF-SLAM/./examples/slam_demo.py", line 200, in <module>     run(args)   File "/home/wjt/code/NeRF-SLAM/./examples/slam_demo.py", line 179, in run     and (not slam or slam_module.spin()) \   File "/home/wjt/code/NeRF-SLAM/./examples/../pipeline/pipeline_module.py", line 101, in spin     output = self.spin_once(input);   File "/home/wjt/code/NeRF-SLAM/./examples/../slam/slam_module.py", line 11, in spin_once     output = self.slam(input)   File "/home/wjt/software/anaconda3/envs/nerfslam/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/home/wjt/code/NeRF-SLAM/./examples/../slam/meta_slam.py", line 30, in forward     output = self._frontend(batch["data"], self.state, self.delta)   File "/home/wjt/code/NeRF-SLAM/./examples/../slam/vio_slam.py", line 114, in _frontend     x0_visual, visual_factors, viz_out = self.visual_frontend(batch)  # TODO: currently also calls BA, and global BA   File "/home/wjt/software/anaconda3/envs/nerfslam/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/home/wjt/code/NeRF-SLAM/./examples/../slam/visual_frontends/visual_frontend.py", line 326, in forward     self.__initialize()   File "/home/wjt/code/NeRF-SLAM/./examples/../slam/visual_frontends/visual_frontend.py", line 647, in __initialize     self.add_neighborhood_factors(kf0=0, kf1=self.kf_idx, radius=3)   File "/home/wjt/code/NeRF-SLAM/./examples/../slam/visual_frontends/visual_frontend.py", line 708, in add_neighborhood_factors     self.add_factors(ii[keep], jj[keep])   File "/home/wjt/software/anaconda3/envs/nerfslam/lib/python3.9/site-packages/torch/amp/autocast_mode.py", line 12, in decorate_autocast     return func(*args, **kwargs)   File "/home/wjt/code/NeRF-SLAM/./examples/../slam/visual_frontends/visual_frontend.py", line 857, in add_factors     target, _, _ = self.reproject(ii, jj)   File "/home/wjt/code/NeRF-SLAM/./examples/../slam/visual_frontends/visual_frontend.py", line 916, in reproject     pops.projective_transform(Gs, self.cam0_idepths[None], self.cam0_intrinsics[None], ii, jj, cam_T_body=cam_T_body, jacobian=jacobian)   File "/home/wjt/code/NeRF-SLAM/./examples/../networks/geom/projective_ops.py", line 105, in projective_transform     X0, Jz = iproj(depths[:,ii], intrinsics[:,ii], jacobian=jacobian)   File "/home/wjt/code/NeRF-SLAM/./examples/../networks/geom/projective_ops.py", line 26, in iproj     torch.arange(ht).to(disps.device).float(), RuntimeError: CUDA error: an illegal memory access was encountered CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect. For debugging consider passing CUDA_LAUNCH_BLOCKING=1. Calling frontend dtor... Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered Could not free memory: /home/wjt/code/NeRF-SLAM/thirdparty/instant-ngp/dependencies/tiny-cuda-nn/include/tiny-cuda-nn/gpu_memory.h:141 cudaFree(rawptr) failed with error an illegal memory access was encountered


chore(client): Isolate FPVM-specific constructs

Overview
Isolates the FPVM-specific constructs in the kona-client library, only exporting items that are re-usable for different backends.

#435  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @clabby and the rest of your teammates on  Graphite

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.0%. Comparing base (8454c3e) to head (e7605ed).

Additional details and impacted files

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


MB-16237: Convert to aws-sdk-go-v2

Jira ticket
Summary
The new API does not contain the same hardcoded list of valid services and partitions, so there is some validation that cannot be done without actually trying to connect to the service.
The AWS docs for migrating provides some helpful overview.
I tested that I could log in and do basic operations. We might need/want to test more scenarios, but it seems likely that if things were completely broken, we'd know it ASAP.
Verification Steps for the Author

[ ] Tested in the Loadtest environment (for changes to containers, app startup, or connection to data stores)

Messages

:book:
:link: MB-16237

  Generated by :no_entry_sign: dangerJS against 8bbac5b5311fd1711bd28413eedaa83395046c50


AUFS warns in dmesg

[ 2839.857265] aufs au_opts_verify:1597:docker[3105]: dirperm1 breaks the protection by the permission bits on the lower branch

Continuing #30

I think the problem through from docker-machine
https://github.com/docker/machine/issues/2119

Seems to be fixed, closing for now


Allow user to alter the input field class name on the Searchable Legend

We have a default input style in our app.  By putting an unconfigurable class name on the input I can't easily use both the default css from react-vis and the default input style from our app.

@mrawdon concerns regarding overriding are justified since I don't see myself writing properties I don't want to force using the css defaults.
I think the idea itself is good, but implementing it only on this form input doesn't make sense to me. But that's apparently not what @mcnuttandrew is thinking, so maybe you can expand why you are reluctant to implement full style overriding?
I was thinking of adding either a top level wrapper making using of context (yeah I know I know) or adding a classPrefix property on each of the components using a className that would result in things looking like .yolo-search-wrapper__form__input.
This way people wanting to override completely every component class could do it if they wanted to (although I think it might be quite some work), or do it only at the component level.

I think a change like what @Apercu is suggesting, is more in line with the issue #534 since its a larger change to how react-vis styles components.
I think using @mcnuttandrew suggestion is probably the easiest and most in line with how things currently work in react-vis
className={`rv-search-wrapper__form__input ${inputClassName}`}

If that makes sense, I'll update my pull request accordingly

I ended up using my own input field separate from the component here.  So I'm going to close this


Create a Helm Chart for WSO2 Open Banking Solution Deployment Pattern 1

Description:
Create resources for a Helm Chart which performs a single node deployment of the Open Banking Solution.
Sub Tasks:

[x] Define deployment definitions for the product profiles (refer https://github.com/wso2/kubernetes-open-banking/issues/2 and https://github.com/wso2/kubernetes-open-banking/issues/3)
[x] Define service definitions to expose the product profile services within the cluster (refer https://github.com/wso2/kubernetes-open-banking/issues/9 and https://github.com/wso2/kubernetes-open-banking/issues/8)
[x] Expose the necessary product profile services to outside of the cluster (refer https://github.com/wso2/kubernetes-open-banking/issues/5 and https://github.com/wso2/kubernetes-open-banking/issues/4)
[x] Add Persistent volume support for the setup (refer https://github.com/wso2/kubernetes-open-banking/issues/17)
[x] Add a README (refer https://github.com/wso2/kubernetes-open-banking/issues/14)
[x] Code/Peer review

The relevant issues have been fixed with the PRs https://github.com/wso2/kubernetes-open-banking/pull/23 , https://github.com/wso2/kubernetes-open-banking/pull/22 and https://github.com/wso2/kubernetes-open-banking/pull/13


Job add Feature

I have implemented a feature to add Jobs to the project.

Improvised Mapping for updating Job Posts


[CROSSDATA-92] [Mongo Datasource] Fix datatypes

Correct output types and add another wich we didn't support.

LGTM

+1


Add random string to end of bucket name

Add random string to end of bucket name to help with S3 bucket attribution.

This was added in release 1.3.1: https://github.com/awslabs/assisted-log-enabler-for-aws/releases/tag/v1.3.1


issues twitter

Gleam.helper Error: Failed to unfollow Twitter usser : ...
Gleam.helper Error: Failed to delete Retweet
how to solve it?

Happening to me as well for several days now. Twitter issues have arisen again it seems.
cc: @Citrinate

This issue should be fixed in v2.0.0
With v2.0 I've merged this script together with a similar script for another site (marvelousga).
If you happened to have both scripts installed, you'll now have 2 copies of "Giveaway Helper" installed, which will create a doubling effect.  You can fix this by uninstalling one of the "Giveaway Helper"s.


Address checker issues.

Coverage remained the same at 81.777% when pulling<PHONE_NUMBER>dac853db3fcafd1d5ee4b5e9fc1de3 on tswhison/checkers into 85d01de9b0b5fa4067567e42dbff94f423cfa32e on master.


github-actions: bump all official actions

@joaquimrocha  I could add dependabot support for actions in a follow up PR. What do you think?


fixed scrolling for connection viewlet

Fixes https://github.com/Microsoft/azuredatastudio/issues/4048

I think we need some PM/Design @yualan input here. Typically everywhere else we have tree in viewlets (every viewlet) the trees don't have a horizontal scroll, they just have ellipse if the content goes over.

@anthonydresser @abist can we at least fix the regression with the vertical scrollbar discussed in https://github.com/Microsoft/azuredatastudio/issues/4048?  You can work on what to do about horizontal scrolling separately if desired.

@yualan We can perhaps open a new issue to track "horizontal scrolling"

https://github.com/Microsoft/azuredatastudio/issues/4106 done


Dev

[ ] The justification for this PR is:  bumping version after doc corrections done as part of 1.13 release

wrong target, closing

Coverage remained the same at 83.074% when pulling 574b291fec34846ba5a98b9b2701b80ab872b8b1 on sjsrey:dev into e52c74a004862d0ec3f70a8c41c6096e959a3878 on pysal:master.


Treat expressions as statements (#3959)

Pull request opened by the merge tool on behalf of #3959

Merged into branches iso5 in b06c0f751235f8828f35277fe53424bd6f48f5ef


Refactoring docs to make each template have it's own README

Could you have a quick look at how the docs are structured on this branch?
https://github.com/equinor/ioc-shared-infrastructure/tree/docs
I'm thinking that this might be a good approach to make each template "own" it's own dos + assets.

Fixed a typo and pointing the tests to new path.


pty.js problem

After trying to build, following the instructions exactly it fails.
root@Blue-Analyph:/mnt/c/Users/[removed]/Documents/winner/wetty# npm install

<EMAIL_ADDRESS>install /mnt/c/Users/[removed]/Documents/winner/wetty/node_modules/pty.js
node-gyp rebuild

make: Entering directory '/mnt/c/Users/[removed]/Documents/winner/wetty/node_modules/pty.js/build'
CXX(target) Release/obj.target/pty/src/unix/pty.o
In file included from ../../nan/nan.h:190:0,
from ../src/unix/pty.cc:20:
../../nan/nan_maybe_43_inl.h: In function ‘Nan::Maybe Nan::ForceSet(v8::Localv8::Object, v8::Localv8::Value, v8::Localv8::Value, v8::PropertyAttribute)’:
../../nan/nan_maybe_43_inl.h:88:15: error: ‘class v8::Object’ has no member named ‘ForceSet’
return obj->ForceSet(GetCurrentContext(), key, value, attribs);
^
In file included from ../src/unix/pty.cc:20:0:
../../nan/nan.h: In function ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, v8::Localv8::Function, int, v8::Localv8::Value)’:
../../nan/nan.h:817:60: warning: ‘v8::Localv8::Value node::MakeCallback(v8::Isolate, v8::Localv8::Object, v8::Localv8::Function, int, v8::Localv8::Value)’ is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
v8::Isolate::GetCurrent(), target, func, argc, argv);
^
In file included from ../../nan/nan.h:47:0,
from ../src/unix/pty.cc:20:
/home/[removed]/.node-gyp/10.1.0/include/node/node.h:172:50: note: declared here
NODE_EXTERN v8::Localv8::Value MakeCallback(
^
/home/[removed]/.node-gyp/10.1.0/include/node/node.h:88:42: note: in definition of macro ‘NODE_DEPRECATED’
attribute((deprecated(message))) declarator
^
In file included from ../src/unix/pty.cc:20:0:
../../nan/nan.h: In function ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, v8::Localv8::String, int, v8::Localv8::Value)’:
../../nan/nan.h:831:62: warning: ‘v8::Localv8::Value node::MakeCallback(v8::Isolate*, v8::Localv8::Object, v8::Localv8::String, int, v8::Localv8::Value)’ is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
v8::Isolate::GetCurrent(), target, symbol, argc, argv);
^
In file included from ../../nan/nan.h:47:0,
from ../src/unix/pty.cc:20:
/home/[removed]/.node-gyp/10.1.0/include/node/node.h:165:50: note: declared here
NODE_EXTERN v8::Localv8::Value MakeCallback(
^
/home/[removed]/.node-gyp/10.1.0/include/node/node.h:88:42: note: in definition of macro ‘NODE_DEPRECATED’
attribute((deprecated(message))) declarator
^
In file included from ../src/unix/pty.cc:20:0:
../../nan/nan.h: In function ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, const char, int, v8::Localv8::Value)’:
../../nan/nan.h:845:62: warning: ‘v8::Localv8::Value node::MakeCallback(v8::Isolate, v8::Localv8::Object, const char*, int, v8::Localv8::Value)’ is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
v8::Isolate::GetCurrent(), target, method, argc, argv);
^
In file included from ../../nan/nan.h:47:0,
from ../src/unix/pty.cc:20:
/home/[removed]/.node-gyp/10.1.0/include/node/node.h:158:50: note: declared here
NODE_EXTERN v8::Localv8::Value MakeCallback(
^
/home/[removed]/.node-gyp/10.1.0/include/node/node.h:88:42: note: in definition of macro ‘NODE_DEPRECATED’
attribute((deprecated(message))) declarator
^
In file included from ../src/unix/pty.cc:20:0:
../../nan/nan.h: In member function ‘v8::Localv8::Value Nan::Callback::Call_(v8::Isolate, v8::Localv8::Object, int, v8::Localv8::Value) const’:
../../nan/nan.h:1463:5: warning: ‘v8::Localv8::Value node::MakeCallback(v8::Isolate, v8::Localv8::Object, v8::Localv8::Function, int, v8::Localv8::Value)’ is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
));
^
In file included from ../../nan/nan.h:47:0,
from ../src/unix/pty.cc:20:
/home/[removed]/.node-gyp/10.1.0/include/node/node.h:172:50: note: declared here
NODE_EXTERN v8::Localv8::Value MakeCallback(
^
/home/[removed]/.node-gyp/10.1.0/include/node/node.h:88:42: note: in definition of macro ‘NODE_DEPRECATED’
attribute((deprecated(message))) declarator
^
../src/unix/pty.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE PtyFork(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/unix/pty.cc:164:45: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Localv8::Value)’ is deprecated: Use Isolate version [-Wdeprecated-declarations]
String::Utf8Value file(info[0]->ToString());
^
In file included from /home/[removed]/.node-gyp/10.1.0/include/node/v8.h:26:0,
from /home/[removed]/.node-gyp/10.1.0/include/node/node.h:63,
from ../../nan/nan.h:47,
from ../src/unix/pty.cc:20:
/home/[removed]/.node-gyp/10.1.0/include/node/v8.h:2822:28: note: declared here
explicit Utf8Value(Localv8::Value obj));
^
/home/[removed]/.node-gyp/10.1.0/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
../src/unix/pty.cc:175:71: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Localv8::Value)’ is deprecated: Use Isolate version [-Wdeprecated-declarations]
String::Utf8Value arg(argv_->Get(Nan::New(i))->ToString());
^
In file included from /home/[removed]/.node-gyp/10.1.0/include/node/v8.h:26:0,
from /home/[removed]/.node-gyp/10.1.0/include/node/node.h:63,
from ../../nan/nan.h:47,
from ../src/unix/pty.cc:20:
/home/[removed]/.node-gyp/10.1.0/include/node/v8.h:2822:28: note: declared here
explicit Utf8Value(Localv8::Value obj));
^
/home/[removed]/.node-gyp/10.1.0/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
../src/unix/pty.cc:186:71: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Localv8::Value)’ is deprecated: Use Isolate version [-Wdeprecated-declarations]
String::Utf8Value pair(env_->Get(Nan::New(i))->ToString());
^
In file included from /home/[removed]/.node-gyp/10.1.0/include/node/v8.h:26:0,
from /home/[removed]/.node-gyp/10.1.0/include/node/node.h:63,
from ../../nan/nan.h:47,
from ../src/unix/pty.cc:20:
/home/[removed]/.node-gyp/10.1.0/include/node/v8.h:2822:28: note: declared here
explicit Utf8Value(Localv8::Value obj));
^
/home/[removed]/.node-gyp/10.1.0/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
../src/unix/pty.cc:191:45: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Localv8::Value)’ is deprecated: Use Isolate version [-Wdeprecated-declarations]
String::Utf8Value cwd_(info[3]->ToString());
^
In file included from /home/[removed]/.node-gyp/10.1.0/include/node/v8.h:26:0,
from /home/[removed]/.node-gyp/10.1.0/include/node/node.h:63,
from ../../nan/nan.h:47,
from ../src/unix/pty.cc:20:
/home/[removed]/.node-gyp/10.1.0/include/node/v8.h:2822:28: note: declared here
explicit Utf8Value(Localv8::Value obj));
^
/home/[removed]/.node-gyp/10.1.0/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
../src/unix/pty.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE PtyGetProc(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/unix/pty.cc:371:45: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Localv8::Value)’ is deprecated: Use Isolate version [-Wdeprecated-declarations]
String::Utf8Value tty_(info[1]->ToString());
^
In file included from /home/[removed]/.node-gyp/10.1.0/include/node/v8.h:26:0,
from /home/[removed]/.node-gyp/10.1.0/include/node/node.h:63,
from ../../nan/nan.h:47,
from ../src/unix/pty.cc:20:
/home/[removed]/.node-gyp/10.1.0/include/node/v8.h:2822:28: note: declared here
explicit Utf8Value(Localv8::Value obj));
^
/home/[removed]/.node-gyp/10.1.0/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
../src/unix/pty.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE PtyFork(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/unix/pty.cc:222:34: warning: ignoring return value of ‘int chdir(const char)’, declared with attribute warn_unused_result [-Wunused-result]
if (strlen(cwd)) chdir(cwd);
^
pty.target.mk:95: recipe for target 'Release/obj.target/pty/src/unix/pty.o' failed
make: *** [Release/obj.target/pty/src/unix/pty.o] Error 1
make: Leaving directory '/mnt/c/Users/[removed]/Documents/winner/wetty/node_modules/pty.js/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:235:12)
gyp ERR! System Linux 4.4.0-43-Microsoft
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /mnt/c/Users/[removed]/Documents/winner/wetty/node_modules/pty.js
gyp ERR! node -v v10.1.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/[removed]/.npm/_logs/2018-05-24T02_42_23_981Z-debug.log

Another error along the same lines...
~/Public/socioprophet-master/wetty /// node app.js -p 3000                                                                                (05/28 22:49:58)
internal/modules/cjs/loader.js:573
throw err;
^
Error: Cannot find module '../build/Release/pty.node'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:571:15)
at Function.Module._load (internal/modules/cjs/loader.js:497:25)
at Module.require (internal/modules/cjs/loader.js:626:17)
at require (internal/modules/cjs/helpers.js:20:18)
at Object. (/Users/michaelheller/Public/socioprophet-master/wetty/node_modules/pty.js/lib/pty.js:9:11)
at Module._compile (internal/modules/cjs/loader.js:678:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:689:10)
at Module.load (internal/modules/cjs/loader.js:589:32)
at tryModuleLoad (internal/modules/cjs/loader.js:528:12)
at Function.Module._load (internal/modules/cjs/loader.js:520:3)

wetty depends on pty.js which depends on a deprecated version of nan.
I have worked around the problem using nvm and installing node 8.11.2.

I am trying with nvm-windows and node 8.11.2 but I am not having any luck with python 3.6

This hasn't moved along much @krishnasrinivas can we set up some time to walk through this and push a solution to the community? I can ask a few geeks to join us on the call / webex / skype or whatever it takes; but, I'd like to try to work with you to solve this issue. I love this project and it's really a great piece of software for the global geek community. I'd like to see this project succeed and I'd like to help make sure it's a reliable app. Please let me know how we can work together to come to a worthwhile and documentable solution to these issues. I am willing to put in the time with you, and I am willing to ask other geeks to help if necessary. What is the best next step to working through this?

It seems to me that pty.js is no longer really maintained  ... but node-pty seems to be an actively maninatned fork ... maybe just switch to node-pty?!

I will push the changes to my fork

Thx for this. I'm really having issues installing node-pty. Can someone point me in the right directions pls?
Vissie

OK, if anyone wants to know how to, I eventually figured this out.....
update wetty source to use node-pty as per issue 119#124.
clone https://github.com/Microsoft/node-pty into wetty/node_modules
sudo npm install
That worked for me.
Vissie

wetty has been upgraded


Remove labels from metadata graphs

Why?

Because now we have double labels in one graph.
Greetings from Texel :D
José de Kruif
Op 1 aug. 2016 om 10:07 heeft Julian Gonggrijp <notifications<EMAIL_ADDRESS>het volgende geschreven:
Why?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/UUDigitalHumanitieslab/texcavator/issues/131#issuecomment-236515454, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGvfBK-OGZqw0Za42JDaJXi9YwOnV4eaks5qbalWgaJpZM4JXBWh.


Update index.html    .... Issue #95

Line 33 and 312  was "Index.html" Changed It To "#hero".Since ,It Works Faster{Hash Page Linking} And Retains Animation Of Page Flow
Some Textual Changes In Design

Issue #95 ... Pull Request.....

Merged! 👍

Okh....


"Path too long," error when installing QT, even with VCPKG installed in "C:/" and using "--x-buildtrees-root"

Describe the bug
When installing QT, it errors out telling me the path is too long however, I literally can't make it any shorter since it's already using C:\vcpkcg\. Even when passing --x-buildtress-root and providing either the VCPKG or buildtrees directory it still produces the same error.
Environment

OS: Windows 10
Compiler: MSVC 10.0.40219 (not sure if that's the correct version number though, latest VS community is installed).

To Reproduce
Steps to reproduce the behavior:

./vcpkg install qt or ./vcpkg install qtwebengine
See error

Expected behavior
qt or qtwebengine to be installed
Failure logs
CMake Warning at ports/qtwebengine/portfile.cmake:83 (message):
  Buildtree path 'C:/vcpkg/buildtrees/qtwebengine' is too long.

  Consider passing --x-buildtrees-root=<shortpath> to vcpkg!`

--x-buildtress-root=C:\b doesn't work? Try using subst b: c:\vcpkg\buildtrees and --x-buildtress-root=b:\ (saves one character).
Please note that it's not an error but a warning.

I tried --x-buildtress-root="C:\vcpkg" again and it worked for some reason this time, so I'm going to go ahead and close it. Thanks for your reply though.

Buildtree path 'C:/vcpkg/buildtrees/qtwebengine' is too long.

I've do like you but stucking in building debug, how to solve it ?


Adopting "convenience" APIs for often-needed/used commands

Forgive me if this has been discussed elsewhere, but being a beginner Docker dev, I am noticing there is a lot API UX improvement to be had with commonly-used commands.
Example: Me: "Hm. how do I do X? [Googles. Ends up on StackOverflow, where an answer has been upvoted by a few hundred other people] To me, this represents an opportunity to improve the CLI/API.
docker rmi -f $(docker images -q -a -f dangling=true)
Why not docker rm --dangling or something a little more guessable?
Another example:
 docker inspect --format '{{ .NetworkSettings.IPAddress }}' {$CID}
Why not docker ip $CONTAINER_NAME?
Does that make sense? Is this overlooking something obvious and non-trivial?

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Found some more here as well.
http://viget.com/extend/how-to-use-docker-on-os-x-the-missing-guide
Are there people on the docker team specifically focused on CLI UX?

@kevinSuttle the hard part is trying to find a balance between being flexible and user-friendly.  Your example of docker ip $CONTAINER_NAME is a good one.  That would certainly be more user-friendly but then it would probably mean a new top-level command for each possible property of interest on a container - which may in fact make the UX worse in the long run.
Instead, I wonder if it wouldn't be better to define some short-cuts. For example:
docker rmi @dangling

so that we're not totally changing what's there today, but instead just offering some short-cuts, or aliases, where the user is asking docker to do the "calculation" of what the short-cut means.
Just a thought.
I'm going to close this, not because its not worth considering, but rather because its not concrete enough to take action on. If you can think of specific new top-level commands to be added, or want to pursue something else (like that alias thing) then it would be best to open up a new issues with the specific proposed change so that the discussion is more concrete/targeted.
Thanks!

so that we're not totally changing what's there today, but instead just offering some short-cuts, or aliases, where the user is asking docker to do the "calculation" of what the short-cut means.

Agreed, I think most cases can be addressed by using aliases. Determining what are "frequently used" commands is hard to do, because that's something that will differ from user to user.


Argument '_node' is incompatible with the required type.

After building with axbuild, I get this error and I can't figure out how to fix it:
Error \Classes\GTXPendingVCSObjects\process 53 12 Argument '_node' is incompatible with the required type.
Any ideas?

Yeah just ignore it for the time being it hasnt been implemented
On Mar 4, 2015 7:22 AM, "BTXAndy"<EMAIL_ADDRESS>wrote:

After building with axbuild, I get this error and I can't figure out how
to fix it:
Error \Classes\GTXPendingVCSObjects\process 53 12 Argument '_node' is
incompatible with the required type.
Any ideas?
—
Reply to this email directly or view it on GitHub
https://github.com/fraga/gitax/issues/47.

Could I comment this out for the time being? I'm trying to get a clean compile.
if(versionControl.allowCreate(controlable))
{
//do something if it isn't in version control
info(strfmt("%1\t%2",pNode.treeNodeType(), pNode.treeNodeName()));
}

Yep go ahead and comment :)
On Mar 4, 2015 7:32 AM, "BTXAndy"<EMAIL_ADDRESS>wrote:

Could I comment this out for the time being? I'm trying to get a clean
compile.
if(versionControl.allowCreate(controlable))
{
//do something if it isn't in version control
info(strfmt("%1\t%2",pNode.treeNodeType(), pNode.treeNodeName()));
}
—
Reply to this email directly or view it on GitHub
https://github.com/fraga/gitax/issues/47#issuecomment-77149828.


how to deno run a fresh project published to deno.land/x ?

I was thinking to have a fresh project that you could easily run with deno run.
Here's what I tried so far:
deno run -A<EMAIL_ADDRESS>
error: Relative import path "$fresh/plugins/twind.ts" not prefixed with / or ./ or ../

deno run -A<EMAIL_ADDRESS><EMAIL_ADDRESS>error: Uncaught (in promise) TypeError: Must be a file URL.
    throw new TypeError("Must be a file URL.");
          ^
    at fromFileUrl (https://deno.land/std@0.150.0/path/posix.ts:492:11)
    at Function.fromManifest (https://deno.land/x/fresh@1.1.0/src/server/context.ts:253:42)
    at start (https://deno.land/x/fresh@1.1.0/src/server/mod.ts:64:35)
    at https://deno.land/x/git_goggles@0.0.2/main.ts:13:7

I'm wondering if there is some combination of cli flags to set import map + compiler options to match what is in deno.json?
Or if there is a better way to approach this?
The idea is to have something similar to Github Desktop instead of an electron app it could be a simple fresh app that could open a tab in your preferred browser.

It looks like the code uses toFileUrl and fromFileUrl all over the place. Unless I'm reading this wrong, it looks like it'd be a major refactor.

Running Fresh projects straight from deno.land/x is not possible. That's one of the downsides of import maps that they only take effect in the root project. If a dependency relies on a path being remapped that's not in the root import map then it will not work. It's one of the reasons we built https://jsr.io/ .


Outline Cli and server's connectivity

I've just installed Outline Cli and it does work on Debian 10. But there's a problem. After I run:
outline-cli -transport "ss://....?outline=1"

The server becomes inaccessible over the network.
I have Debian 10 with Ethernet interface called ens192 with public IP x.x.x.x. My gateway is x.x.x.1. Whenever i start outline new interface appears: outline233 with IP <IP_ADDRESS>. Nothing changes is routes, them are same before and after connection:
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
<IP_ADDRESS>         x.x.x.1     <IP_ADDRESS>         UG    0      0        0 ens192
x.x.x.0     <IP_ADDRESS>         <IP_ADDRESS>   U     0      0        0 ens192

Nothing changes is iptables - no new rules or smth. But after connecting with outline I can have outgoing traffic from server but can't connect or even ping the server itself via x.x.x.x.
How can I avoid this?

Well, seems like we intentionally blocking everything here https://github.com/Jigsaw-Code/outline-sdk/blob/6f0c166a4c9ac9b79224d85e01b6f4abbc53e458/x/examples/outline-cli/routing_linux.go#L106
Adding return nil as first line of setupIpRule fixes the problem. But is it safe? Why we block everything in the first place?

Hi @phpony , we are not blocking everything in the first place. You should still be able to access the internet. Here is how Outline CLI works:

We added a new routing table 233 (we won't touch the default routing table, because there might be a chance that we won't be able to recover it). You can list all routing rule for all routing tables in the system by ip route show table all (look for table 233 in the response).
Then we routed all traffic to table 233 to our tun device (i.e. outline233), Outline CLI will listen on this tun device and forward traffic to the target shadowsocks server. You can list the routing rule by ip route show table 233.
Finally, we must use the default routing table/network interface to forward the traffic to the target shadowsocks server  (otherwise there will be a dead loop). ip rule list will show 23333:	not from all to <ss-server-ip> lookup 233, meaning all traffic to the <ss-server-ip> won't go through the routing table 233.

I hope this could help you understand our routing strategy better, and give you more details to troubleshoot. Adding return nil to the code above basically means skipping step 3; and depending on the network interface and routing table configuration on the system, it might or might not work.
As the comment mentions, using fwmark would be better, but it requires a lot more effort. Therefore as a tradeoff, we used this simpler but still effective implementation.


Barco EventMaster User Key Implementation

Describe the feature
The ability to apply a user key to the currently selected layer in EM.
Is this platform dependent (windows, mac, ..)?
No
If documentation is required to implement, do you know where to find it?
I don't think there is documentation for this.
Usecases
In the current Companion implementation, a button can be programmed to apply a user key to a specific layer on a specific destination.  I would like the ability to have a button apply a specified user key to the currently selected layer within EM.  This would make for much speedier programming.  One could select a layer in EM then press the appropriate SD button to apply the user key.  I don't know if this is possible, but it would be fantastic!

Closing this, option to add custom XML is in a separate module.


Dependabot alerts and dependency graph support for pnpm

Summary
The dependency graph will add support for pnpm manifest files. This will allow developers to view their pnpm dependencies in the dependency graph and receive Dependabot alerts for any known vulnerabilities.
Intended Outcome
Adding pnpm support gives developers building pnpm projects the supply chain coverage needed to identify and remediate vulnerabilities within GitHub.
How will it work?
Dependency graph will parse and ingest pnpm package.json and pnpm-lock.yaml files automatically, and the included dependencies will appear in the dependency graph. Dependabot alerts will work for pnpm dependencies.

🚢 This has shipped: https://github.blog/changelog/2023-08-02-pnpm-support-for-dependency-graph-dependabot-alerts-and-dependabot-security-updates/
Leaving open to track GHES release!

This shipped with GHES 3.11<EMAIL_ADDRESS>


[Question] Is it possible to create a "multiloader" compatible modpack

Background
I making mods using a multiloader template which can be found here. This means that my mods work on fabric, quilt, and forge.
Question
Is there a way to design the pack format that would include a "forge" export and a "fabric" export (additionally at some point a "neo-forge" one as well) that I can individually export to curseforge/fabric using github actions?

I'm not entirely sure what you're asking for - packwiz isn't for publishing individual mods. Do you mean making a modpack of several of your mods for each platform?
It might be possible to implement this with a script that runs the packwiz <mr/cf> add commands every time you release, and just having 2 separate modpacks. I think implementing multi-loader modpacks into the pack format would be a bit too complex.

That is reasonable.
It is really just adding the ability to have a modpack you desire to release and being able to export a "forge" and a "fabric" version of the pack.
I think there are other solutions that could also get people there but yeah thank you


Add support for 'region' in the .aws/credentials file

The AWS 'region' value is not pulled from the .aws/credentials file. This patch adds support and suppresses the warning if it is not appropriate.

@mattray We rewrote this whole project to use the aws-sdk which brings in a lot of this sort of thing for free. I'm going to close this out at this point. It might just work for you, but if not this PR will need to be reworked for the new API.


Update ETL_vital to Obsclin_transformation.sql

commet

@vasanthi014
I updated my codes but it seems need approval to be updated


Image Block: image left/right size S is larger in view (compared to edit)

as admin
go to http://localhost:3000
create a new page
add a new image block (align: left, size: m)
save page
go to page view
-> image block shows up as size L

Edit Mode:

View Mode:

Note: set max-width in view to 25 %

Another problem with the size M. This is how a M size image aliged to the center looks like in the view:


Reference markers, formulas and other irrelevant numbers

This is related to issue #22.
I have a file (1404.4640.training.tei.xml) where there are a few reference markers, for example:

lower than those derived by Vaubaillon et al. (2014) and Moorhead et al. (2014)
computing the corresponding impact probabilities (Milani et al. 2005)

There are also figure/table titles, and other numbers who don't quantify anything, for example:

Figure 1 shows the residuals of C/2013 A1's observations
[Figure 1 about here.]
Table 1 contains the orbital elements of the computed solution.
our new orbit solution (JPL solution 46)

There are also some inline formulas, like:

a minimum point of ∆v 2 = |∆v| 2 under the constraint that the particle reaches Mars, i.e., (ξ, ζ)(r, β, ∆v) = (0, 0).

None of these numbers are annotated.
(+addToDoc)

We only annotated expressions of quantities, which can use numbers or alphabetical words.
Numbers are used for other stuff like markers, call-out, section number, identifiers, index, reference expressions, formula parameters, etc. and we must ignore all these cases.


RequestShutdown: fix shutdown if registration never succeeded

Extracted from https://github.com/oasisprotocol/oasis-core/pull/4571 and added an explicit e2e test.

Needs backport ;_;


How are the knowledge-v*.json files generated?

Hi there! Really great paper.
I wanted to understand how config/knowledge-5.12.json and config/knowledge-6.1.json are generated. How would I make new knowledge files if I wanted to port to other kernel versions? Are these automatically generated or manually written?
Any pointers would be greatly appreciated!

Hi,
Those files currently are generated manually.
In most case, the knowledge is not changed. For example, 5.12 works for most 5.x versions.
You can test the knowledge file first on your target version. If it does not work well, some manually efforts are needed.
If you are working on latest Linux kernel and find the knowledge can not work well, you can open a issue for that and I can help when I am available.
In fact, I was trying to develop a tool to automatically update those files but I have not finished the tool.

Cool! Thanks for the reply. Currently, I am using a combination of grep on the .ll file (disassembled llvm) and weggli on the C source to check if anything is different with my target. Currently, I have found some slight differences in offsets, but more automation would be very helpful! Happy to help out and test if needed :)

Btw,

You can test the knowledge file first on your target version. If it does not work well, some manually efforts are needed.

How do you "test" this? Do you just look out the output syscall descriptors and check if they look reasonable?

How do you "test" this? Do you just look out the output syscall descriptors and check if they look reasonable?

Yes.


[Provider Namespacing] Ensure that workers require runners

If workers do not require_dependency their runners, the const_defined?(:Runner, false) call in corresponding_runner will fail to find the appropriate runner class when starting up the worker.
This results in finding the "legacy" runner.  For example, after the namespacing of OpenStack CloudManager, the event catcher worker is ManageIQ::Providers::Openstack::CloudManager::EventCatcher and the corresponding runner is ManageIQ::Providers::Openstack::CloudManager::EventCatcher::Runner.  However, the legacy MiqEventCatcherOpenstack, the corresponding runner used to be 'workers/event_catcher_openstack'.
When corresponding_runner fails to find the appropriately namespaced runner class, it throws errors like:

(LoadError) cannot load such file -- workers/event_catcher_openstack on adding
openstack provider

Additionally, Openstack's EventCatcherMixin had the wrong module name.  Even though the class was located at manageiq/providers/openstack/event_catcher_mixin.rb, the full class and module name was ManageIQ::Providers::Openstack::CloudManager::EventCatcherMixin.  Removed the CloudManager so the class could be loaded correctly.
(Upstream only)
https://bugzilla.redhat.com/show_bug.cgi?id=1253134

@Fryguy / @matthewd, please review

D'oh, I think I can actually add a spec for this

Good thing I decided to add a spec for this.  I actually missed one, it seems.
ManageIQ::Providers::Openstack::CloudManager::MetricsCollectorWorker

Gonna wip this for now until I get a legacy worker test in place .. shouldn't be too hard.

Looks good...very minor comments... @matthewd Can you review too?

:+1:

Bump ... I believe this is ready to merge


fix cannot read parquet file from remote hdfs server

Fixes #2170

Hm, raises the question of why this worked previously. HDFS is the only case where we give server/port, but we do optionally supply username/password to s3fs in the URL, and this has been tested to work.

I find Dask 0.14.1 cannot read multiply parquet files from a folder.
 path = "hdfs://<IP_ADDRESS>:8020/data_set/alluxiotest"   df = dd.read_parquet(path)

The newer changes seem to break the tests

I am looking into this now. I suspect that your solution breaks s3, so it will take a little investigation.
For now, a workaround would be to pass your extra parameters as arguments instead of as part of the URL:
df = dd.read_parquet('/data_set/alluxiotest', storage_options={'host': '<IP_ADDRESS>', 'port': 8020})

I try to use your workaround to read data, unfortunately, I still cannot read parquet file from hadoop remotely.
Do I need to update fastparquet or dask?

Certainly update them, since both change regularly.
But your error looks as though hdfs3 was talking OK with HDFS, but found no files. Can you ensure that /data_set/GV/basic_information_treat/ contains a _metadata and some data files (.parq or .parquet, normally), and that you have access? You could check this directly with hdfs3:
import hdfs3
hdfs = hdfs3.HDFileSystem( ... )
hdfs.ls('/data_set/GV/basic_information_treat/')


Attest to keys, not certificates

On https://github.com/jlmucb/cloudproxy/blob/master/go/tao/auth/ast.go#L110 it is stated that Key might be a DER-encoded X.509 certificate. Why not just a DER-encoded SubjectPublicKeyInfo?

This is allowed; maybe we should clarify the comment. The types of key values named there are merely the ones that the Tao happens to use. There's certainly no reason to not use SubjectPublicKeyInfo; at the moment, we use a custom protobuf-wrapped key out of convenience.
I was going to say that you could simply write a function like tao.FromPrincipal in tao/keys.go, but you can't, since the attestation code is hardcoded to expect a CryptoKey protobuf, and the internals of tao.Verifier are not exported.
For the moment, this isn't high priority for us to fix, but I'll leave this open; at the very least, I could export the internal ec element of Verifier and Signer so external code could create them out of auth.Prin with other types.

Currently there is nothing in the encoded version to indicate what kind of thing is serialized as a key. This means a third party verifying a statement can only guess at what is in there, which is not very cryptographically sound.

John suggested that too a while ago. I agree with the comment from an engineering point of view, and I think I'll probably add it in the future. However, I don't follow the claim about cryptographic soundness. Can you provide an example of this that doesn't involve breaking the crypto algorithm used to generate the signature?
Given that a key-based auth.Prin represents the name of a principal, it is only ever going to be a public key. So, consider the actions of a receiver of an auth.Prin:
A receiver is going to deserialize the format in some way that it decides is right (and this is clearly an engineering problem for the current version). Either the deserialization succeeds or not. If not, then verification fails. If deserialization succeeds, then the receiver has a key. If it's the wrong key, then either verification fails correctly or the signature scheme is broken (with overwhelming probability). If verification succeeds correctly, then that's the right behavior.
Also, remember that this auth principal is not always getting signed, so the type of the key would be at most a hint to the receiver.

I see, you're right about that. I still see two issues:

The innermost key (the one which was specified as the actual parameter to the "Attest" call) might not be immediately used to verify an accompanying signature. That might leave room to fool whatever process this key was going to be used for.
Trying to deserialize random data in various ways is generally prone to memory safety bugs, but I understand if you claim that's "not my problem".

I think these are both good points from a security engineering perspective, and I don't think it's too hard to fix this, so I'll look into it.


Volume provisioning give btrfs subvolume of size 0

I did a provisioning of volume of 5GiB, then when I wanted to write some file into my volume I immediately got an quota exceeded error

@LeeSmet can you point where this is handled in the code ?

It's a bad size conversion, the Provision module expects module in GiB while storage expects a size in Bytes.


PhpUnitMockShortWillReturnFixer - Introduction

Replaces https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/3278 - no update from @kingmad since April.

@SpacePossum done, you can remove WIP label and review ;)
Do want to include https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/4160 and rename the fixer?

Not sure about one fixer for all mockery-will-fixing... its sounds like a good idea to me to be honest but lets see what others think.
In the meantime, please add a PHP7.3 test case with something like
$someMock->method("someMethod")->will($this->returnValue( 10  ,  ));

@kubawerlos can you rebase and squash for me? :)

Thank you @kubawerlos.


Update haskell.nix

nix build .#hydraJobs.linux.windows.cardano-cli
> ln: failed to create symbolic link '/nix/store/mir50rd7lhavh0322wanzwdd1g7mximm-cardano-cli-exe-cardano-cli-x86_64-w64-mingw32-1.34.1/bin/libsodium-23.dll': File exists

Merge to master with (at least) #3315


Redis instance size

Hi, we're interested in using this software for our server but I'm not sure how bug the redis instance should be. Do you maybe know how much memory is used for every request / ip?
Thanks

It shouldn't have a large resource requirement, as it's storing a small amount of data, and this adapter expires those keys after the data isn't relevant anymore. I'd say around 256MB of ram should be sufficient?


Delete unnecessary spaces

When copying from the web page, there is an unnecessary space after the code.

@changeworld : Thanks for your contribution! The author, @tylerfox, has been notified to review your proposed change.

#sign-off


ARROW-17830: [C++][Gandiva] Disable Gandiva build on Appveyor

Temporarily disable Gandiva on Appveyor due to a bug in Conda's packaging of LLVM.

Sent a report to conda llvm: https://github.com/conda-forge/llvmdev-feedstock/issues/175

@lidavidm Appveyor is green now.

How about pinning LLVM to old version instead?
diff --git a/ci/conda_env_gandiva_win.txt b/ci/conda_env_gandiva_win.txt
index 621b6f5a99..138b9bd200 100644
--- a/ci/conda_env_gandiva_win.txt
+++ b/ci/conda_env_gandiva_win.txt
@@ -15,5 +15,6 @@
 # specific language governing permissions and limitations
 # under the License.

-clangdev
-llvmdev
+# ARROW-17830: Conda's packaging of LLVM 15 have a bug
+clangdev<15
+llvmdev<15

How about pinning LLVM to old version instead?
diff --git a/ci/conda_env_gandiva_win.txt b/ci/conda_env_gandiva_win.txt
index 621b6f5a99..138b9bd200 100644
--- a/ci/conda_env_gandiva_win.txt
+++ b/ci/conda_env_gandiva_win.txt
@@ -15,5 +15,6 @@
 # specific language governing permissions and limitations
 # under the License.

-clangdev
-llvmdev
+# ARROW-17830: Conda's packaging of LLVM 15 have a bug
+clangdev<15
+llvmdev<15

@kou Done.


window scroll is getting change when press the enter in textarea

normally its working perfectly.
and when text area grow and scroll bar is appear beacause of that.
then text area's bottom will be near to bottom of the brower.
after that
when typing page is moving to bit up and when press the enter button page is moving bit down.
It's really anoying :(

I'm not familiar with this issue, so there's a chance it's a bug that's not related to this library.
Can you upload a reproduction? It would be greatly appreciated.


Remove unneeded brackets and add bash syntax highlighting

Remove unneeded brackets around shell code
Add bash syntax highlighting in the markdown code blocks

If you feel this falls under If you are considering a minor copy edit for tone, grammar, or simple inconsistent whitespace, consider the tradeoff between maintainer time and community benefit before investing too much of your time. ,  feel free to close this MR :-)

Closing this, as a duplicate of https://github.com/kelseyhightower/kubernetes-the-hard-way/pull/456


Improve UI flow for adding cross references

Feedback by eLife: Overall, there seems to be a lot of double actions required - e.g. adding a citation of a reference does not open a list of the available references, but inserts a placeholder citation that then needs to be clicked to select the right reference. This could get quite frustrating if writing/editing a long article.

@Integral I think we'd need to change InsertXrefCommand or InsertInlineNodeCommand to select the newly inserted inline node. then the dialog should pop up immediately and we don't need an extra click.


Got some errors when install the CUDA version from source.

Hi, When I run "python setup.py install --headless --with-cuda --cmake  " I always got the below error :
running install
running bdist_egg
running egg_info
writing habitat_sim.egg-info/PKG-INFO
writing dependency_links to habitat_sim.egg-info/dependency_links.txt
writing requirements to habitat_sim.egg-info/requires.txt
writing top-level names to habitat_sim.egg-info/top_level.txt
reading manifest file 'habitat_sim.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE'
writing manifest file 'habitat_sim.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
running build_ext
-- The CUDA compiler identification is unknown
-- Detecting CUDA compiler ABI info
-- Detecting CUDA compiler ABI info - failed
-- Check for working CUDA compiler: /usr/local/cuda
-- Check for working CUDA compiler: /usr/local/cuda - broken
CMake Error at /data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/site-packages/cmake/data/share/cmake-3.18/Module
s/CMakeTestCUDACompiler.cmake:52 (message):
The CUDA compiler
"/usr/local/cuda"

is not able to compile a simple test program.
It fails with the following output:
Change Dir: /data/leuven/333/vsc33366/projects/habitat-sim/build/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/gmake cmTC_e7ae4/fast && /usr/bin/gmake  -f CMakeFiles/cmTC_e7ae4.dir/build.make CMakeFil

es/cmTC_e7ae4.dir/build
gmake[1]: Entering directory /vsc-hard-mounts/leuven-data/333/vsc33366/projects/habitat-sim/build/CMakeFiles/CMakeTmp'     Building CUDA object CMakeFiles/cmTC_e7ae4.dir/main.cu.o                                                                    /usr/local/cuda      -c /data/leuven/333/vsc33366/projects/habitat-sim/build/CMakeFiles/CMakeTmp/main.cu -o CMakeFiles/ cmTC_e7ae4.dir/main.cu.o                                                                                gmake[1]: execvp: /usr/local/cuda: Permission denied                                                                        gmake[1]: *** [CMakeFiles/cmTC_e7ae4.dir/main.cu.o] Error 127     gmake[1]: Leaving directory /vsc-hard-mounts/leuven-data/333/vsc33366/projects/habitat-sim/build/CMakeFiles/CMakeTmp'
gmake: *** [cmTC_e7ae4/fast] Error 2
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:12 (project)
Call Stack (most recent call first):
CMakeLists.txt:12 (project)
-- Configuring incomplete, errors occurred!
See also "/data/leuven/333/vsc33366/projects/habitat-sim/build/CMakeFiles/CMakeOutput.log".
See also "/data/leuven/333/vsc33366/projects/habitat-sim/build/CMakeFiles/CMakeError.log".
Traceback (most recent call last):
File "setup.py", line 390, in
include_package_data=True,
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/site-packages/setuptools/init.py", line 153, in setup
return distutils.core.setup(**attrs)
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/distutils/core.py", line 148, in setup
dist.run_commands()
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/site-packages/setuptools/command/install.py", line 67,
in run
self.do_egg_install()
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/site-packages/setuptools/command/install.py", line 109,
in do_egg_install
self.run_command('bdist_egg')
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/site-packages/setuptools/command/bdist_egg.py", line 16
4, in run
cmd = self.call_command('install_lib', warn_dir=0)
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/site-packages/setuptools/command/bdist_egg.py", line 15
0, in call_command
self.run_command(cmdname)
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/site-packages/setuptools/command/install_lib.py", line
11, in run
self.build()
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/distutils/command/install_lib.py", line 107, in build
self.run_command('build_ext')
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "setup.py", line 204, in run
self.build_extension(ext)
File "setup.py", line 273, in build_extension
env=env,
File "/data/leuven/333/vsc33366/miniconda3/envs/nav/lib/python3.7/subprocess.py", line 363, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '-H/vsc-hard-mounts/leuven-data/333/vsc33366/projects/habitat-sim/src', '
-Bbuild', '-DBUILD_PYTHON_BINDINGS=ON', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/vsc-hard-mounts/leuven-data/333/vsc33366/project
s/habitat-sim/build/lib.linux-x86_64-3.7/habitat_sim/_ext', '-DPYTHON_EXECUTABLE=/data/leuven/333/vsc33366/miniconda3/envs/
nav/bin/python', '-DCMAKE_EXPORT_COMPILE_COMMANDS=ON', '-DCMAKE_BUILD_TYPE=RelWithDebInfo', '-DBUILD_GUI_VIEWERS=OFF', '-DT
ARGET_HEADLESS=ON', '-DBUILD_TEST=OFF', '-DBUILD_WITH_BULLET=OFF', '-DBUILD_DATATOOL=OFF', '-DBUILD_WITH_CUDA=ON']' returne
d non-zero exit status 1.
My system is CentOS Linux release 7.9.2009 (Core), the nvcc version is 10.0, and python 3.7.  I tried to install the habitat-sim v.0.1.7 version.  Could some kindly inform me how to solve this problem ? Many thanks in advance.

Hey, @Mingxiao-Li
Looks like an issue with your system cuda install.
You may want to search the repo issue history for similar issues and possible solutions.
@erikwijmans any quick thoughts here?

Yep, the install is failing when cmake checks to see if it can compile a simple cuda program with the cuda compiler. This indicates an issue with your cuda install.

Thanks for the reply, but my cuda works fine when I use PyTorch. By the way, is there a way to install the cuda version from Conda ?


Update SwiftApplication.plist.gpg for GoogleSignIn support

Update to support GoogleSignIn logins from the sample app
And cherry-pick in clang-format fixes for CI
#no-changelog

Merging now. I'll address any comments in a subsequent PR


[DO NOT MERGE] Port patch

Patch of
https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/1481 and https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/1452 for v0.7.1
/hold

The patches are in v0.8.0. Closing...


feat: reconciliation rule blocking timed out/failed futures

If a future has previously timed out or failed (not just failed at simulation). Then the user must wipe the future with the wipe command before rerunning.
We enforce this with a reconciliation check. This check comes after the future level reconciliation checks (a design decision we may revisit - could it just be a standard rule?).
Resolves #412.

I say we merge this here, and then think a bit more about the UX implications of this being part of reconciliation vs an ad-hoc check. The latter may allow us to give better error messages.

Agreed. I will merge.
I initially had it as a post-reconciliation check. But I then needed to answer the question, "what is the return result?". I picked validation, then changed my mind and went with reconciliation. At that point though it seemed odd to have a post reconciliation check that returned a reconciliation failure, rather than an additional rule in reconciliation.
Happy to shift it out and improve the message, we just need to consider whether it should count as an additional phase and hence get a new return type.


[Test] simplify .wat code for finalize-exports-issue-8261 test

To fix @xtuc comment in previous PR: https://github.com/webpack/webpack/pull/8266/files/035ceb6b1b9b14fe7c3c0da2738cd5d5e2ecf24b#diff-373fad072502d91acb95b26d85c95b7e

What kind of change does this PR introduce?
minor readability improvement

Did you add tests for your changes?
It's test itself

Does this PR introduce a breaking change?
No

What needs to be documented once your changes are merged?
Nothing

Thanks


Table Selected Rows Ordering

table.selectedRows are in the order they have been selected  (say you selected row 4, then 1, then 3 it will be 4,1,3)
Sometimes one need to get them in the order they are selected (1,3,4 in above example)

Just curious: what's the use case?

In mean time I convinced them to go about with this another way (not so great UX decision made by users)
The user would select multiple records which needed to be sent to the server for processing.  But they would have selected in a certain order, and it needed to be processed in that order.

That is because Table.selectedRows is implemented as a computed property that filters over all rows:
  /**
   * @property selectedRows
   * @type {Ember.Array}
   */
  selectedRows: computed.filterBy('rows', 'selected', true).readOnly()

In theory, we could invert this and make all rows' selected  properties depend on the Table.selectedRows array and then upon clicking add or remove that row from that array.
In essence, this ...
  /**
   * Whether the row is selected.
   *
   * CSS Classes:
   *  - `is-selected`
   *
   * @property selected
   * @type {Boolean}
   * @default false
   */
  selected: false

... would become this:
  /**
   * Whether the row is selected.
   *
   * CSS Classes:
   *  - `is-selected`
   *
   * @property selected
   * @type {Boolean}
   * @default false
   */
  selected: computed('table.rows.[]', {
    get() {
      return get(this, 'rows').includes(this);
    },
    set(key, isSelected) {
      if (isSelected) {
         // makes sure the object is only added, if it's not already present.
         // https://www.emberjs.com/api/classes/Ember.MutableEnumerable.html#method_addObject
        get(this, 'rows').addObject(this);
      } else {
        get(this, 'rows').removeObject(this);
      }
      return isSelected;
    }
  })

However, that would cause quite a few performance issues as effectively every rows needs to iterate over the Table.selectedRows array to determine its selected state, whenever Table.selectedRows is mutated.
But to solve your problem: why not pass a custom onRowClick action and do it yourself? 😜

Something like this should work.
{{#light-table table as |t|}}
  {{t.head}}
  {{t.body
    canSelect=false
    onRowClick=(action "toggleRowSelectionState")
  }}
{{/light-table}}

const {
  A,
  computed,
  get
} = Ember;

export default Component.extend({
  // ...

  selectedRows: computed(function() { return A(); }),

  actions: {
    toggleRowSelectionState(row) {
      if (get(row, 'selected')) {
        get(this, 'selectedRows').removeObject(row);
        set(row, 'selected', false);
      } else {
        get(this, 'selectedRows').addObject(row);
        set(row, 'selected', false);
    }
  }
});

Thanks so much buschtoens.  I'm pretty new to light table (actually ember as well), so did not think that far.

 We also have a very supportive Ember Community Slack. :hugs:

That is because Table.selectedRows is implemented as a computed property that filters over all rows:

@buschtoens I think a better solution would be to start out with an empty Table.selectedRows and as a user selects a row, manually add the row to that array and remove it when the row is unselected. Assuming we clean up this array when done with it. Doing this would avoid the performance hit you mentioned.

@mkay581 Actually, scratch my comment about performance. I somehow was under the impression, that users would be allowed to manipulate the Table.selectedRows array directly. That's why the [] part in the table.rows.[] dependent key was needed.
However, users can't (or shouldn't manipulate) Table.selectedRows anyways. So, if we were to remove the [] part, we should experience no performance hit.

@mkay581 @buschtoens IMHO A better solution would be to add another action that would trigger on row(s) being selected and pass those row(s) up. This provides a lot more flexibility to the developer as well which can use actions instead of observers on the selectedRows array to do specific things.

@offirgolan even better! Observers can impede performance.

@offirgolan how would group selections (shift click) invoke that action? Always top to bottom or maybe depending on the order of clicks?
What about deselection? We should an action for that as well.

@buschtoens take a look at #193. It was never finished 😞
Pretty much we can pass these into onRowClick
onRowClick(row = Row, selected = [], deselected = [], e)

Or we can have another action:
onSelectionChange(selected = [], deselected = [])

The name for that one should change but I think you can get what I mean.


OverloadedError: Model is overloaded

I am using the meta-llama/Llama-2-70b-chat-hf model on a data frame with 3000 rows, each including a 500-token text. But after 10 rows is processed, I get the following error
` in call_llama2_api(self, messages)
79     def call_llama2_api(self, messages):
80         huggingface.prompt_builder = "llama2"
---> 81         response = huggingface.ChatCompletion.create(
82             model="meta-llama/Llama-2-70b-chat-hf",
83             messages=messages,
/usr/local/lib/python3.10/dist-packages/easyllm/clients/huggingface.py in create(messages, model, temperature, top_p, top_k, n, max_tokens, stop, stream, frequency_penalty, debug)
205             generated_tokens = 0
206             for _i in range(request.n):
--> 207                 res = client.text_generation(
208                     prompt,
209                     details=True,
/usr/local/lib/python3.10/dist-packages/huggingface_hub/inference/_client.py in text_generation(self, prompt, details, stream, model, do_sample, max_new_tokens, best_of, repetition_penalty, return_full_text, seed, stop_sequences, temperature, top_k, top_p, truncate, typical_p, watermark, decoder_input_details)
1063                     decoder_input_details=decoder_input_details,
1064                 )
-> 1065             raise_text_generation_error(e)
1066
1067         # Parse output
/usr/local/lib/python3.10/dist-packages/huggingface_hub/inference/_text_generation.py in raise_text_generation_error(http_error)
472             raise IncompleteGenerationError(message) from http_error
473         if error_type == "overloaded":
--> 474             raise OverloadedError(message) from http_error
475         if error_type == "validation":
476             raise ValidationError(message) from http_error
OverloadedError: Model is overloaded`
Is there any solution to fix this problem, like increasing the rate limit?

What happens if you give it 3000 rows with 250 max token? Is it the same thing?
This might be out of memory (oom) or endpoint problem. I think it would be helpful if you put in your ram&vram for spec&usage of your system.


application choser dialog opens multiple times for tell a friend and restore project

@opticod @croozeus
In settings fragment there are two problems:
1 . If the user by mistake clicks "Tell a friend" or "Restore Project" twice.The choser dialog for selecting the application opens twice.This makes the user to close both the dialogs if he doesn't want to choose anything

2 . The author name length must be limited .Otherwise if the author name  or template name or combination of both of them is large,the emulator doesn't show author name and template name.
If we proceed further the emulator crashes.There is also UI distortion in navigation drawer

After proceeding further in emulator ,it crashes.
I will send a PR for this ASAP

Thanks.. @nikhilchowdary

Closed via #406


chore: no default invoice memo

what value does it give? then all the entries say lightning invoice and it can only be a lightning invoice

I see, this is especially wrong for keysend payments.


--strict mode

Before releasing v1, I am thinking about making lynt's rules a lot more relaxed and to truly only check for errors (this would be using @suchipi's eslint-config-unobtrusive which I had initially rejected in #1). This would mean that rules like no-var, eqeqeq, prefer-const, curly etc which aren't really checking for errors but rather check for "best practices" would be turned off. The idea is that any JS/TS codebase should be able to use lynt's default config, regardless of a person's coding style and whether they are using an ES6 codebase or not.
With the --strict flag enabled, only then are these "best practices" rules turned on. Curious to hear thoughts on this.

Hm. That separation sounds good, yea.


[Fixes] Fixed param example for ContainerGroup

Description
Changes default param value to prevent deployment issues when using the default set.
This was already correct in the .test example param file
Type of Change
Please delete options that are not relevant.

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings
[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (readme)
[x] I did format my code

Yet again, thanks for the contribution :)


HTTP/2.0 support with Got v11

Are there any plans to bump the Got dependency and gain HTTP/2.0 support (sadly good proxy support for h2 connections in the latest Got seems non-obvious)?

Got updated in #36


Feature Request: Federation

Is there any plan to support GraphQL federation?
If federation is supported, would be a very great idea since working with microservices will become very handy with this package

No plans, I think the core lib should be focused on the core spec. But you can probably build this on top of it