RLS panics with 0.4.0

Version of VSCode: 1.13.1
Version of the extension: 0.4.0
OS: Fedora 25
Description:
RLS panics with latest extension version. On previous version it worked well.
Output of the "Rust Language Server" channel (Rust logging is not useful in this case):
thread 'main' panicked at 'unknown action', /checkout/src/tools/rls/src/cmd.rs:90
note: Run with `RUST_BACKTRACE=1` for a backtrace.
thread '<unnamed>' panicked at 'Error reading from channel: RecvError', /checkout/src/libcore/result.rs:860
thread '<unnamed>' panicked at 'cannot access stdout during shutdown', /checkout/src/libcore/option.rs:823
[Error - 8:17:27] Connection to server got closed. Server will not be restarted.

The reason behind this is user configuration. I've removed my old one and did the initial extension config. Now everything works ok.
Unfortunately, I can't remember what was the content of my settings.json.

I had this also, same fix worked for me.
Broken settings which caused crash:
{
    "rust.rustLangSrcPath": "C:\\Users\\Daniel\\.rustup\\toolchains\\nightly-x86_64-pc-windows-gnu\\lib\\rustlib\\src\\rust\\src",
    "rust.cargoHomePath": "C:\\Users\\Daniel\\.cargo",
    "rust.rls": {
        "executable": "rustup",
        "args": [
            "run",
            "nightly",
            "rls"
        ],
        "useRustfmt": true
    },
    "rust.rustup": {
        "toolchain": "nightly-x86_64-pc-windows-gnu"
    },
    "rust.mode": "rls"
}

What I did was remove ALL of these settings, then restart VS Code and follow the prompts to choose toolchain etc. Now my settings looks like this and there is no issue:
{
    "rust.rustup": {
        "toolchain": "nightly-x86_64-pc-windows-gnu"
    },
    "rust.mode": "rls",
    "rust.rls": {
        "useRustfmt": true
    }
}

I'm sorry about that.
The reasons are the same as for #229.
Until I release new version, you shouldn't use "rust.rls.executable" and "rust.rls.args" if they point at "rustup".

@KalitaAlexey I have reset my settings, but the issue still exists.
Missing change, aborting. Found 813, expected Some(830)
[Error - 下午9:18:23] Connection to server got closed. Server will not be restarted.

My user settings:
    "rust.rustup": {
        "toolchain": "nightly-x86_64-pc-windows-msvc"
    },
    "rust.mode": "rls",
    "rust.rls": {
        "useRustfmt": true
    }

on my Windows 10
vscode-rust 0.4.0
rustc 1.20.0-nightly (622e7e648 2017-06-21)
cargo 0.21.0-nightly (d26fd6f08 2017-06-20)
rls 0.1.0-nightly (d26fd6f 2017-06-20)

@WangZishi,
It's interesting.
@nrc @jonathanturner, Have you seen something similar before?

Same thing happening to me.
{"message":"expected value, found module internals::cpu::cpu_impl","code":{"code":"E0423","explanation":"\nA structvariant name was used like a function name.\n\nErroneous code example:\n\n```compile_fail,E0423\nstruct Foo { a: bool };\n\nlet f = Foo();\n// error:Foois a struct variant name, but this expression uses\n//        it like a function name\n```\n\nPlease verify you didn't misspell the name of what you actually wanted to use\nhere. Example:\n\n```\nfn Foo() -> u32 { 0 }\n\nlet f = Foo(); // ok!\n```\n"},"level":"error","spans":[{"file_name":"src\\main.rs","byte_start":32,"byte_end":56,"line_start":4,"line_end":4,"column_start":5,"column_end":29,"is_primary":true,"text":[{"text":"    internals::cpu::cpu_impl;","highlight_start":5,"highlight_end":29}],"label":"not a value","suggested_replacement":null,"expansion":null}],"children":[],"rendered":null} Missing change, aborting. Found 2, expected Some(20) [Error - 18:21:27] Connection to server got closed. Server will not be restarted.
rustup show:
`Default host: x86_64-pc-windows-msvc
nightly-x86_64-pc-windows-msvc (default)
rustc 1.20.0-nightly (622e7e648 2017-06-21)`

@rerzer,
Post the whole Rust Logging.

@KalitaAlexey
How would I access the log? (Win 10)

Open a terminal.
export RUST_BACKTRACE=1
code path/to/your/project

And then paste what Rust Language Server says you.

I'm on Win 10, used SET RUST_BACKTRACE=1
No output in the powershell I used to start vscode, output in vscode does not seem to change after the crash.
Rust logging:
DEBUG: Rustup: updateToolchains: this.toolchains=[{"channel":"nightly","host":"x86_64-pc-windows-msvc","isDefault":true}]
DEBUG: Rustup: updateComponents(nightly-x86_64-pc-windows-msvc): components=["cargo-x86_64-pc-windows-msvc (default)","rls-x86_64-pc-windows-msvc (installed)","rust-analysis-x86_64-pc-windows-msvc (installed)","rust-docs-x86_64-pc-windows-msvc (default)","rust-src (installed)","rust-std-aarch64-apple-ios","rust-std-aarch64-linux-android","rust-std-aarch64-unknown-fuchsia","rust-std-aarch64-unknown-linux-gnu","rust-std-arm-linux-androideabi","rust-std-arm-unknown-linux-gnueabi","rust-std-arm-unknown-linux-gnueabihf","rust-std-arm-unknown-linux-musleabi","rust-std-arm-unknown-linux-musleabihf","rust-std-armv7-apple-ios","rust-std-armv7-linux-androideabi","rust-std-armv7-unknown-linux-gnueabihf","rust-std-armv7-unknown-linux-musleabihf","rust-std-armv7s-apple-ios","rust-std-asmjs-unknown-emscripten","rust-std-i386-apple-ios","rust-std-i586-pc-windows-msvc","rust-std-i586-unknown-linux-gnu","rust-std-i686-apple-darwin","rust-std-i686-linux-android","rust-std-i686-pc-windows-gnu","rust-std-i686-pc-windows-msvc","rust-std-i686-unknown-freebsd","rust-std-i686-unknown-linux-gnu","rust-std-i686-unknown-linux-musl","rust-std-mips-unknown-linux-gnu","rust-std-mips-unknown-linux-musl","rust-std-mips64-unknown-linux-gnuabi64","rust-std-mips64el-unknown-linux-gnuabi64","rust-std-mipsel-unknown-linux-gnu","rust-std-mipsel-unknown-linux-musl","rust-std-powerpc-unknown-linux-gnu","rust-std-powerpc64-unknown-linux-gnu","rust-std-powerpc64le-unknown-linux-gnu","rust-std-s390x-unknown-linux-gnu","rust-std-sparc64-unknown-linux-gnu","rust-std-wasm32-unknown-emscripten","rust-std-x86_64-apple-darwin","rust-std-x86_64-apple-ios","rust-std-x86_64-linux-android","rust-std-x86_64-pc-windows-gnu","rust-std-x86_64-pc-windows-msvc (default)","rust-std-x86_64-rumprun-netbsd","rust-std-x86_64-unknown-freebsd","rust-std-x86_64-unknown-fuchsia","rust-std-x86_64-unknown-linux-gnu","rust-std-x86_64-unknown-linux-musl","rust-std-x86_64-unknown-netbsd","rustc-x86_64-pc-windows-msvc (default)",""]
DEBUG: activate: getNightlyToolchain: There is only one nightly toolchain
DEBUG: RlsMode: start: enter
DEBUG: Rustup: isRlsInstalled: getNightlyToolchain: There is only one nightly toolchain
DEBUG: RlsMode: start: User decided to use rustfmt
DEBUG: Rustup: isRlsInstalled: getNightlyToolchain: There is only one nightly toolchain
DEBUG: RlsMode: start: rlsPath=rustup
DEBUG: RlsMode: start: env={"RUST_SRC_PATH":"C:\\Users\\rerzer\\.rustup\\toolchains\\nightly-x86_64-pc-windows-msvc\\lib\\rustlib\\src\\rust\\src"}
DEBUG: Rustup: isRlsInstalled: getNightlyToolchain: There is only one nightly toolchain
DEBUG: RlsMode: start: args=["run","nightly","rls"]
DEBUG: RlsMode: start: revealOutputChannelOn=3
DEBUG: RlsMode: start: Language Client Manager: start

RLS still only shows:
Missing change, aborting. Found 2, expected Some(21)
[Error - 21:38:15] Connection to server got closed. Server will not be restarted.

@rerzer,
I don't know and I am busy with other issues.
I would be glad if you could find it the reasons.

Gonna try on my laptop with arch to see if it's a Windows only issue.
Will update if I find something.

Backtrace after crash with RUST_BACKTRACE=1
thread '<unnamed>' panicked at 'RUST_SRC_PATH is set: NotPresent', /checkout/src/libcore/result.rs:860
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
             at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at /checkout/src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:355
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:371
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:549
   5: std::panicking::begin_panic
             at /checkout/src/libstd/panicking.rs:511
   6: std::panicking::begin_panic_fmt
             at /checkout/src/libstd/panicking.rs:495
   7: rust_begin_unwind
             at /checkout/src/libstd/panicking.rs:471
   8: core::panicking::panic_fmt
             at /checkout/src/libcore/panicking.rs:69
   9: core::result::unwrap_failed
  10: racer::nameres::get_crate_file
  11: racer::nameres::resolve_name
  12: racer::nameres::resolve_path
  13: racer::core::complete_from_file_
  14: std::panicking::try::do_call
  15: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:98
  16: rls::server::LsService::handle_message::{{closure}}

and with RUST_BACKTRACE=full
thread '<unnamed>' panicked at 'RUST_SRC_PATH is set: NotPresent', /checkout/src/libcore/result.rs:860
stack backtrace:
   0:     0x7fb2a8ae8153 - std::sys::imp::backtrace::tracing::imp::unwind_backtrace::h0c3c52ab4000a0c3
                               at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1:     0x7fb2a8ae3514 - std::sys_common::backtrace::_print::h1a2a77bbc8c86dbb
                               at /checkout/src/libstd/sys_common/backtrace.rs:71
   2:     0x7fb2a8af614a - std::panicking::default_hook::{{closure}}::h8019b68fb1d13c50
                               at /checkout/src/libstd/sys_common/backtrace.rs:60
                               at /checkout/src/libstd/panicking.rs:355
   3:     0x7fb2a8af5bff - std::panicking::default_hook::hfbf8766d5f07b890
                               at /checkout/src/libstd/panicking.rs:371
   4:     0x7fb2a8af6542 - std::panicking::rust_panic_with_hook::hc2ba7f4258940a80
                               at /checkout/src/libstd/panicking.rs:549
   5:     0x7fb2a8af63d4 - std::panicking::begin_panic::h3686babf7c1a65b5
                               at /checkout/src/libstd/panicking.rs:511
   6:     0x7fb2a8af6369 - std::panicking::begin_panic_fmt::h128cd28a87901b35
                               at /checkout/src/libstd/panicking.rs:495
   7:     0x7fb2a8af62f7 - rust_begin_unwind
                               at /checkout/src/libstd/panicking.rs:471
   8:     0x7fb2a8b335ad - core::panicking::panic_fmt::h4daceedfcb998660
                               at /checkout/src/libcore/panicking.rs:69
   9:     0x55df5c65a18b - core::result::unwrap_failed::h1582683fda57e954
  10:     0x55df5c687184 - racer::nameres::get_crate_file::h6f8986780262b8c3
  11:     0x55df5c69950d - racer::nameres::resolve_name::hf61e34d46f4700a6
  12:     0x55df5c69c4aa - racer::nameres::resolve_path::hc3e9e68db7953e3c
  13:     0x55df5c664ae4 - racer::core::complete_from_file_::h8fa86b9d9a3902fb
  14:     0x55df5c191ac2 - std::panicking::try::do_call::h3a89e201e5a81d37
  15:     0x7fb2a8aff82a - __rust_maybe_catch_panic
                               at /checkout/src/libpanic_unwind/lib.rs:98
  16:     0x55df5c24c0d3 - rls::server::LsService::handle_message::{{closure}}::h7ad702c888f5c236
  17:     0x55df5c18faf7 - std::sys_common::backtrace::__rust_begin_short_backtrace::hd08317da6bff9656
  18:     0x55df5c191927 - std::panicking::try::do_call::h33999acb13cc3e5b
  19:     0x7fb2a8aff82a - __rust_maybe_catch_panic
                               at /checkout/src/libpanic_unwind/lib.rs:98
  20:     0x55df5c1d0472 - <F as alloc::boxed::FnBox<A>>::call_box::h20d8f9e7cdf18a30
  21:     0x7fb2a8af4d85 - std::sys::imp::thread::Thread::new::thread_start::h52ac90d0416e4a80
                               at /checkout/src/liballoc/boxed.rs:660
                               at /checkout/src/libstd/sys_common/thread.rs:21
                               at /checkout/src/libstd/sys/unix/thread.rs:84
  22:     0x7fb2a8441296 - start_thread
  23:     0x7fb2a7c5925e - __clone
  24:                0x0 - <unknown>

This is on a fresh install of rust nightly on Antergos.

I'll look at it now.

Could you make rustup component add rust-src --toolchain nightly.

I did that right after I read the backtrace, it appears to have fixed the crashing on arch.
But on Windows it says info: component 'rust-src' is up to date and the RLS keeps crashing.

It shouldn't help, but try rustup component add rust-src --toolchain nightly-x86_64-pc-windows-msvc

Okay I guess that was placebo, it still crashes.

Could you try:

rustup component remove rls --toolchain nightly, rustup component remove rust-analysis --toolchain nightly, rustup component remove rust-src --toolchain nightly, rustup component add rust-src --toolchain nightly
Remove the extension and install it again

It's kind of strange problem.

I see DEBUG: RlsMode: start: env={"RUST_SRC_PATH":"C:\\Users\\rerzer\\.rustup\\toolchains\\nightly-x86_64-pc-windows-msvc\\lib\\rustlib\\src\\rust\\src"} , but thread '<unnamed>' panicked at 'RUST_SRC_PATH is set: NotPresent'. It confuses me.

I'm going sleep. Write your results. Thanks.

Managed to make it crash again on Arch.
thread '<unnamed>' panicked at 'begin <= end (16 <= 12) when slicing `fn main() {
    let a = Test {
        val: 12,
    };

    println!("{:}", a);
}

struct Test {
    val: u16,
}`', /checkout/src/libcore/str/mod.rs:2137
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
             at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at /checkout/src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:355
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:371
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:549
   5: std::panicking::begin_panic
             at /checkout/src/libstd/panicking.rs:511
   6: std::panicking::begin_panic_fmt
             at /checkout/src/libstd/panicking.rs:495
   7: rust_begin_unwind
             at /checkout/src/libstd/panicking.rs:471
   8: core::panicking::panic_fmt
             at /checkout/src/libcore/panicking.rs:69
   9: core::str::slice_error_fail
             at /checkout/src/libcore/str/mod.rs:2137
  10: racer::nameres::search_scope_headers
  11: racer::nameres::search_local_scopes
  12: racer::nameres::resolve_name
  13: racer::nameres::resolve_path
  14: racer::core::complete_from_file_
  15: std::panicking::try::do_call
  16: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:98
  17: rls::server::LsService::handle_message::{{closure}}

Gonna try your suggestions next.

I think removing the components and adding them again through the plugin might have helped. No crashes so far but I don't really have enough time to tets it right now.

Followed the same steps on Win 10, still crashing. I assume it didn't "really" work on Arch then either and I was just lucky.

It's RLS problem. I already mentioned nrc in the thread. I believe he knows better.

This is the RLS issue that discusses this problem https://github.com/rust-lang-nursery/rls/issues/372

@rerzer I got everything working by checking out and building rls from master. Then all you have to do is change the extension settings to know about your newly built version:
{
    "rust.rustup": {
        "toolchain": "nightly-x86_64-apple-darwin",
        "nightlyToolchain": "nightly-x86_64-apple-darwin"
    },
    "rust.mode": "rls",
    "rust.rls": {
        "useRustfmt": true,
        "executable": "/Users/joe/Documents/Programming/rustproj/rls/target/release/rls",
        "env": {
            "DYLD_LIBRARY_PATH": "~/.rustup/toolchains/nightly-x86_64-apple-darwin/lib"
        }
    }
}

The environment variables will be dependent on the platform that you're using.

Commenting on the previous one: building rls from master worked for me to fix the crash, but setting the DYLD_LIBRARY_PATH via env didn't. "Luckily", in OSX you can modify the rpath on a binary sigh.
So if the above doesn't work for you, this should:
$ cd rls
$ cargo build --release
$ install_name_tool -add_rpath `rustc --print sysroot` target/release/rls

verify that running target/release/rls works.


⚠ ClamAV has degraded performance

In 0882518, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in 95f2a90.


ClickHouse 23.10 support

The following test scenario fails for ClickHouse 23.10:
  Scenario: Backup table with S3 storage policy                   # tests/integration/features/backup_multiple_disks.feature:39
    Given default configuration                                   # tests/integration/steps/common.py:12
    And a working s3                                              # tests/integration/steps/s3.py:12
    And a working clickhouse on clickhouse01                      # tests/integration/steps/clickhouse.py:15
    And a working clickhouse on clickhouse02                      # tests/integration/steps/clickhouse.py:15
    Given we have executed queries on clickhouse01                # tests/integration/steps/clickhouse.py:55
      """
      CREATE DATABASE IF NOT EXISTS test_db;
      CREATE TABLE test_db.table_01 (
          CounterID UInt32,
          UserID UInt32
      )
      ENGINE = MergeTree()
      PARTITION BY CounterID % 3
      ORDER BY UserID
      SETTINGS storage_policy = 's3';

      INSERT INTO test_db.table_01 SELECT 0, number FROM system.numbers LIMIT 10;
      INSERT INTO test_db.table_01 SELECT 1, number FROM system.numbers LIMIT 10;
      """
    When we create clickhouse01 clickhouse backup                 # tests/integration/steps/ch_backup.py:26
    Then we got the following backups on clickhouse01             # tests/integration/steps/ch_backup.py:146
      | num | state   | data_count | link_count |
      | 0   | created | 2          | 0          |
    When we restore clickhouse backup #0 to clickhouse02          # tests/integration/steps/ch_backup.py:86
      """
      cloud_storage_source_bucket: 'cloud-storage-01'
      cloud_storage_source_path: 'data'
      """
      Assertion Failed: execution failed with code 1, out: "Traceback (most recent call last):
        File "/usr/local/bin/ch-backup", line 33, in <module>
          sys.exit(load_entry_point('ch-backup', 'console_scripts', 'ch-backup')())
        File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1157, in __call__
          return self.main(*args, **kwargs)
        File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1078, in main
          rv = self.invoke(ctx)
        File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1688, in invoke
          return _process_result(sub_ctx.command.invoke(sub_ctx))
        File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
          return ctx.invoke(self.callback, **ctx.params)
        File "/usr/local/lib/python3.10/site-packages/click/core.py", line 783, in invoke
          return __callback(*args, **kwargs)
        File "/usr/local/lib/python3.10/site-packages/click/decorators.py", line 33, in new_func
          return f(get_current_context(), *args, **kwargs)
        File "/var/tmp/ch-backup/ch_backup/cli.py", line 161, in wrapper
          result = ctx.invoke(f, ctx, ctx.obj["backup"], *args, **kwargs)
        File "/usr/local/lib/python3.10/site-packages/click/core.py", line 783, in invoke
          return __callback(*args, **kwargs)
        File "/var/tmp/ch-backup/ch_backup/cli.py", line 693, in restore_command
          ch_backup.restore(
        File "/var/tmp/ch-backup/ch_backup/ch_backup.py", line 291, in restore
          self._restore(
        File "/var/tmp/ch-backup/ch_backup/ch_backup.py", line 521, in _restore
          self._table_backup_manager.restore(
        File "/var/tmp/ch-backup/ch_backup/logic/table.py", line 267, in restore
          self._restore_data(
        File "/var/tmp/ch-backup/ch_backup/logic/table.py", line 607, in _restore_data
          disks.copy_part(context.backup_meta, table, part)
        File "/var/tmp/ch-backup/ch_backup/clickhouse/disks.py", line 160, in copy_part
          self._copy_dir(
        File "/var/tmp/ch-backup/ch_backup/clickhouse/disks.py", line 190, in _copy_dir
          result = _exec(
        File "/var/tmp/ch-backup/ch_backup/clickhouse/disks.py", line 222, in _exec
          raise ClickHouseDisksException(
      ch_backup.clickhouse.disks.ClickHouseDisksException: clickhouse-disks call failed with exitcode: 70

https://github.com/yandex/ch-backup/actions/runs/6737760412/job/18315952124#logs

More details:
clickhouse-disks logs:
root@clickhouse02:/# /usr/bin/clickhouse-disks --log-level TRACE copy --disk-from s3_source --disk-to s3 shadow/77970e61_7626_4fd1_8925_dec40fad4677/store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/1_2_2_0/ store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/detached/1_2_2_0/
Provider type: Unknown
API mode of the S3 client: AWS
Starting up disk s3_source
Disk s3_source started up
Provider type: Unknown
API mode of the S3 client: AWS
Starting up disk s3
Disk s3 started up
Loading filesystem cache with 1 threads
Status file /var/lib/clickhouse/disks/s3_cache/status already exists - unclean restart. Contents:
PID: 13
Started at: 2023-11-07 10:59:34
Revision: 54479

Code: 76. DB::Exception: Cannot lock file /var/lib/clickhouse/disks/s3_cache/status. Another server instance in same directory is already running. (CANNOT_OPEN_FILE), Stack trace (when copying this message, always include the lines below):

0. DB::Exception::Exception(DB::Exception::MessageMasked&&, int, bool) @ 0x000000000cdd11b7 in /usr/bin/clickhouse
1. DB::Exception::Exception<String const&>(int, FormatStringHelperImpl<std::type_identity<String const&>::type>, String const&) @ 0x00000000079a084d in /usr/bin/clickhouse
2. DB::StatusFile::StatusFile(String, std::function<void (DB::WriteBuffer&)>) @ 0x000000000cf0bdff in /usr/bin/clickhouse
3. DB::FileCache::initialize() @ 0x0000000012c14c05 in /usr/bin/clickhouse
4. DB::CachedObjectStorage::CachedObjectStorage(std::shared_ptr<DB::IObjectStorage>, std::shared_ptr<DB::FileCache>, DB::FileCacheSettings const&, String const&) @ 0x0000000011dac72e in /usr/bin/clickhouse
5.  DB::DiskFactory::create(String const&, Poco::Util::AbstractConfiguration const&, String const&, std::shared_ptr<DB::Context const>, std::map<String, std::shared_ptr<DB::IDisk>, std::less<String>, std::allocator<std::pair<String const, std::shared_ptr<DB::IDisk>>>> const&) const @ 0x0000000011d62c60 in /usr/bin/clickhouse
8. DB::DiskSelector::initialize(Poco::Util::AbstractConfiguration const&, String const&, std::shared_ptr<DB::Context const>, std::function<bool (Poco::Util::AbstractConfiguration const&, String const&)>) @ 0x0000000011f22080 in /usr/bin/clickhouse
9. DB::Context::getDiskSelector(std::lock_guard<std::mutex>&) const @ 0x0000000011ee96fd in /usr/bin/clickhouse
10. DB::Context::getDisk(String const&) const @ 0x0000000011ecbda0 in /usr/bin/clickhouse
11. DB::CommandCopy::execute(std::vector<String, std::allocator<String>> const&, std::shared_ptr<DB::Context>&, Poco::Util::LayeredConfiguration&) @ 0x000000000d0937b2 in /usr/bin/clickhouse
12. DB::DisksApp::main(std::vector<String, std::allocator<String>> const&) @ 0x000000000d08d88e in /usr/bin/clickhouse
13. Poco::Util::Application::run() @ 0x000000001659e0e6 in /usr/bin/clickhouse
14. mainEntryClickHouseDisks(int, char**) @ 0x000000000d08fff8 in /usr/bin/clickhouse
15. main @ 0x00000000073badfa in /usr/bin/clickhouse
16. ? @ 0x0000000000023d0a in /lib/x86_64-linux-gnu/libc-2.31.so
17. _start @ 0x00000000065903ae in /usr/bin/clickhouse
 (version <IP_ADDRESS>6 (official build))
DB::Exception: Cannot lock file /var/lib/clickhouse/disks/s3_cache/status. Another server instance in same directory is already running.
Shutting down named sessions
Shutting down database catalog
Shutting down system databases
Shutting down DDLWorker
Shutting down caches

After stopping clickhouse-server on the same node, copy cmd works normally:
root@clickhouse02:/# supervisorctl stop clickhouse
clickhouse: stopped
root@clickhouse02:/# /usr/bin/clickhouse-disks --log-level TRACE copy --disk-from s3_source --disk-to s3 shadow/77970e61_7626_4fd1_8925_dec40fad4677/store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/1_2_2_0/ store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/detached/1_2_2_0/
Provider type: Unknown
API mode of the S3 client: AWS
Starting up disk s3_source
Disk s3_source started up
Provider type: Unknown
API mode of the S3 client: AWS
Starting up disk s3
Disk s3 started up
Loading filesystem cache with 1 threads
Registered cached disk (`s3_cache`) with structure: DiskObjectStorage-s3(CachedObjectStorage-s3_cache(S3ObjectStorage))
Copying from s3_source (path: /var/lib/clickhouse/disks/s3_source/) shadow/77970e61_7626_4fd1_8925_dec40fad4677/store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/1_2_2_0/default_compression_codec.txt to s3 (path: /var/lib/clickhouse/disks/s3/) store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/detached/1_2_2_0/default_compression_codec.txt.
Copying from s3_source (path: /var/lib/clickhouse/disks/s3_source/) shadow/77970e61_7626_4fd1_8925_dec40fad4677/store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/1_2_2_0/partition.dat to s3 (path: /var/lib/clickhouse/disks/s3/) store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/detached/1_2_2_0/partition.dat.
Copying from s3_source (path: /var/lib/clickhouse/disks/s3_source/) shadow/77970e61_7626_4fd1_8925_dec40fad4677/store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/1_2_2_0/count.txt to s3 (path: /var/lib/clickhouse/disks/s3/) store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/detached/1_2_2_0/count.txt.
Create WriteBufferFromS3, Details: bucket cloud-storage-02, key data/oic/fiudvqoqntynsqxavaeltyemdbhoa
Copying from s3_source (path: /var/lib/clickhouse/disks/s3_source/) shadow/77970e61_7626_4fd1_8925_dec40fad4677/store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/1_2_2_0/data.bin to s3 (path: /var/lib/clickhouse/disks/s3/) store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/detached/1_2_2_0/data.bin.
Copying from s3_source (path: /var/lib/clickhouse/disks/s3_source/) shadow/77970e61_7626_4fd1_8925_dec40fad4677/store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/1_2_2_0/columns.txt to s3 (path: /var/lib/clickhouse/disks/s3/) store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/detached/1_2_2_0/columns.txt.
Copying from s3_source (path: /var/lib/clickhouse/disks/s3_source/) shadow/77970e61_7626_4fd1_8925_dec40fad4677/store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/1_2_2_0/serialization.json to s3 (path: /var/lib/clickhouse/disks/s3/) store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/detached/1_2_2_0/serialization.json.
Copying from s3_source (path: /var/lib/clickhouse/disks/s3_source/) shadow/77970e61_7626_4fd1_8925_dec40fad4677/store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/1_2_2_0/checksums.txt to s3 (path: /var/lib/clickhouse/disks/s3/) store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/detached/1_2_2_0/checksums.txt.
Copying from s3_source (path: /var/lib/clickhouse/disks/s3_source/) shadow/77970e61_7626_4fd1_8925_dec40fad4677/store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/1_2_2_0/primary.cidx to s3 (path: /var/lib/clickhouse/disks/s3/) store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/detached/1_2_2_0/primary.cidx.
Copying from s3_source (path: /var/lib/clickhouse/disks/s3_source/) shadow/77970e61_7626_4fd1_8925_dec40fad4677/store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/1_2_2_0/minmax_CounterID.idx to s3 (path: /var/lib/clickhouse/disks/s3/) store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/detached/1_2_2_0/minmax_CounterID.idx.
Copying from s3_source (path: /var/lib/clickhouse/disks/s3_source/) shadow/77970e61_7626_4fd1_8925_dec40fad4677/store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/1_2_2_0/data.cmrk3 to s3 (path: /var/lib/clickhouse/disks/s3/) store/72f/72f5d0a7-61e7-45a7-9183-62e9366a1373/detached/1_2_2_0/data.cmrk3.
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Created HTTP(S) session with minio01:9000 (<IP_ADDRESS>:9000)
Single part upload has completed. Details: bucket cloud-storage-02, key data/oic/fiudvqoqntynsqxavaeltyemdbhoa, size 10
finalizeImpl WriteBufferFromS3. Details: bucket cloud-storage-02, key data/oic/fiudvqoqntynsqxavaeltyemdbhoa.
Close WriteBufferFromS3. Details: bucket cloud-storage-02, key data/oic/fiudvqoqntynsqxavaeltyemdbhoa.
Destructing remote fs threadpool reader
Destructing local fs threadpool reader
Destructing local fs threadpool reader
Shutting down named sessions
Shutting down database catalog
Shutting down system databases
Shutting down DDLWorker
Shutting down caches

Assume that starting breaks from this pr : https://github.com/ClickHouse/ClickHouse/pull/55002


Add Windows Server 2022 images for 3.9 and 3.10-rc

Tested on a Windows Server 2022 evaluation install in a Hyper-V VM, using Mirantis Container Runtime 20.10.6 from DockerMsftProvider.
Basic tests for functionality, for both new Dockerfiles, downloaded into otherwise-empty directories:
PS C:\Users\Administrator\3.9> docker build . -t py39
Sending build context to Docker daemon  4.608kB
Step 1/11 : FROM mcr.microsoft.com/windows/servercore:ltsc2022
...
Successfully tagged py39:latest
PS C:\Users\Administrator\3.9> docker run py39 python -c "import platform; print(platform.win32_ver()); import sys; print(sys.version)"
('10', '10.0.20348', 'SP0', 'Multiprocessor Free')
3.9.6 (tags/v3.9.6:db3ff76, Jun 28 2021, 15:26:21) [MSC v.1929 64 bit (AMD64)]

PS C:\Users\Administrator\3.10-rc> docker build . -t py310rc
Sending build context to Docker daemon  4.608kB
Step 1/11 : FROM mcr.microsoft.com/windows/servercore:ltsc2022
...
Successfully tagged py310rc:latest
PS C:\Users\Administrator\3.10-rc> docker run py310rc python -c "import platform; print(platform.win32_ver()); import sys; print(sys.version)"
('10', '10.0.20348', 'SP0', 'Multiprocessor Free')
3.10.0rc1 (tags/v3.10.0rc1:cc115e5, Aug  3 2021, 15:22:01) [MSC v.1929 64 bit (AMD64)]

[x] Test the images (either CI-generated, or just run the Dockerfiles locally)
[x] Internal sign-off per Wargaming.net Open Source contribution policy (2/2 done)

CI has previously passed for Windows Server 2022, but rebasing to pull bb70f32 has put it back into the workflow-approval queue.

Looks good, thanks!


First link incomplete

Hi, the first used link in this article is not complete. It is missing the &topicid=38066 part.

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

ID: 11ec6892-6853-a52a-095c-f4cf7f8a6f49
Version Independent ID: db918e3c-7dde-0a8d-41db-7c6d6fa1ff57
Content: You must write a tooltip in the Tooltip property for all controls of type Action and Field that exist on page objects (https://styleguides.azurewebsites.net/Styleguide/Read?id=2748&topicid=38066). - Business Central
Content Source: dev-itpro/developer/analyzers/codecop-aa0218-tooltipmustbefilledonpageforfieldsandactions.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: SusanneWindfeldPedersen

Hello, this is due to a bug in the generation of the topic, but it has been fixed now. The topic will be fixed with the next refresh. Thanks!


Chrome extension focus issue

When I try to click on chrome extension like vimium, extension manager, the extension window is killed immediately and the focus moves back to the main chrome window. Similar thing happens with zoom app as well.
I am attaching the logs here. In it I tried clicking on the two extensions multiple times.
yabairc.txt
yabai.log
I tried focus_follows_mouse with autofocus as well. It had the same issue. This seems to happen only with chrome and zoom.
In zoom you cant select a meeting from the dropdown because the dropdown gets killed immediately.

Are you running 1.1.2 or current master? That's likely caused by some subrole=AXUnknown windows from Chrome and has been fixed on master for a few weeks. There just hasn't been a new release yet.

Yep sorry. I am running v1.1.2. I  will upgrade to master test again.


Update troubleshoot-bitlocker-boot-error.md

Update the powershell script for clarity

@yutopio : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@yutopio Thanks for helping to improve the document.
#sign-off


Update README.md

Add ML Security Code resources
Add Incident database, AIRISK

also please add this image

Thanks, will do

@wearetyomsmnv I added the image here, although as this list of resources grows in size maybe I will split the infographics into their own file to make the main README more readable & lean


Consider using Hugo JS bundling rather than webpack

Hugo release notes promise JS bundling with support for modules and dead tree shaking. If true, this would greatly simplify the build and installation step, and let us avoid Webpack.

Pretty sure this was closed by #49.


Add file name containing "%" and "&" to Travis

add test for avoiding a regression from
https://github.com/MediaArea/MediaConch_SourceCode/pull/373

"%" was GUI only, maybe difficult to automate.

There are also filename with:

<

'
"

https://github.com/MediaArea/MediaConch_SourceCode/pull/390


Simple grammar fix.

:shipit:
Feel free to just fix stuff minor stuff like this without a full PR.


Unable to download albums past 50 tracks

When downloading large albums, tracks past 50 will be detected as already existing and not download them. It looks like it's looping around back to the first track instead of continuing with track 51.
% ./tdl get https://listen.tidal.com/album/201482078
Getting Track Info for: [1] <Track 1 name>
Submitting Track to Download Queue: [1] <Track 1 name>
Download Complete | [1] <Track 1 name>
...
Getting Track Info for: [50] <Track 50 name>
Submitting Track to Download Queue: [50] <Track 50 name>
Download Complete | [50] <Track 50 name>
Getting Track Info for: [1] <Track name 1>
Submitting Track to Download Queue: [1] <Track name 1>
File Exists | [1] <Track name 1>
...
Getting Track Info for: [35] <Track 35 name>
Submitting Track to Download Queue: [35] <Track 35 name>
File Exists | [35] <Track 35 name>

(lines omitted/altered for brevity)
Subsequent attempts on the same albums will encounter the same error on the same tracks. This will also affect downloading by artist once it reaches the same album. Changing the number of workers/downloads does not have an affect on the issue, though I was seeing EOF while parsing a value at line 1 column 0 errors.
If one were to download all the tracks individually they will work just fine, so this is likely the workaround.
% tdl get https://listen.tidal.com/browse/track/201482079
...
% tdl get https://listen.tidal.com/browse/track/201482163

The behavior is 100% caused by a bug in this function.
I'll work on a fix and author a new version with it patched in a couple hours.

Got the fix in place (#18).
The Tidal API only lets you get up to 50 items of an album/playlist/artist as a time, and I forgot to re-calculate the offset per loop 😅.
Easy fix, Appreciate you bringing it up.
I authored v0.2.5 with this in place. The CI should have the binaries built in a few minutes.

Downloading playlists is now broken.
invalid type: null, expected a string at line 1 column 21924

That's a separate error, the Tidal API returned a null value in an
unexpected place.  There's still a few edge cases of that laying around
since there's not any formal documentation laying around. An easy fix, just
need to know where the null value showed up to update that type to be
nullable.
Can you open an issue about it? You can enable debug logging with the
RUST_LOG=debug environment variable, and include the output, which will
show the JSON of the request before the parsing error occurred.
Example Command:
RUST_LOG=debug tdl get <playlist_link>
On Sun, Aug 7, 2022 at 9:48 PM Phil Kauffman @.***>
wrote:

Downloading playlists is now broken.
invalid type: null, expected a string at line 1 column 21924
—
Reply to this email directly, view it on GitHub
https://github.com/MinisculeGirraffe/tdl/issues/17#issuecomment-1207593200,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMCLQ7C6QL4PFLYTYBJADS3VYBYQPANCNFSM553BZHQQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Hi, sorry to bring this again, but trying to get a 100 tracks album, just get 51. Should I paste debug info right here?

I just ran it with DEBUG option. It generates both download commands  (i see a JSON with the first 50 and another with the rest) but only downloads the first one (maybe Tidal limit). Is there an easy way to add the offset on the command to download?


Cannot install on windows 10 (64bit) python36

Hi,
I just download  x86_64_python3.tar.gz.
Errors message is as below:
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "", line 1, in
File "c:\users\xx\appdata\local\programs\python\python36\lib\tokenize.py", line 452, in open
buffer = _builtin_open(filename, 'rb')
FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\xx\AppData\Local\Temp\pip-229ndf1p-build\setup.py'
Command "python setup.py egg_info" failed with error code 1 in C:\Users\xxx\AppData\Local\Temp\pip-229ndf1p-build\

Hello,
I updated the release to now include *.whl distributions. You can install them with "pip install <filename>". That should solve this problem.


VS Code 1.23 insiders extension host crashing when live share extension installed

Product and Version [VS/VSCode]:1.23.0 insiders
OS Version  macos 10.13.3
Live Share Extension Version: 0.2.307
Target Platform or Language [e.g. Node.js]:
Steps to Reproduce / Scenario:

Open vs code

Bug
Extension host crashes with:
/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:2776 /Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Code - Insiders Helper.app/Contents/MacOS/Code - Insiders Helper[47246]: ../../vendor/node/src/async-wrap.cc:357:void node::SetupHooks(const FunctionCallbackInfo<v8::Value> &): Assertion `env->async_hooks_init_function().IsEmpty()' failed.
 1: node::Abort() [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 2: node::Assert(char const* const (*) [4]) [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 3: node::AsyncWrap::Initialize(v8::Local<v8::Object>, v8::Local<v8::Value>, v8::Local<v8::Context>) [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 4: v8::internal::StrDup(char const*) [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 5: v8::internal::compiler::BranchElimination::ControlPathConditions::operator==(v8::internal::compiler::BranchElimination::ControlPathConditions const&) const [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 6: v8::internal::compiler::BranchElimination::ControlPathConditions::operator==(v8::internal::compiler::BranchElimination::ControlPathConditions const&) const [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libnode.dylib]
 7: 0x2b1a64b8463d

This error goes away when we disable the live share extension

Possibly https://github.com/electron/electron/issues/10905?

@mjbvz Thanks for reporting this and the reference to the electron bug.  You could be right. We'll have to take a look.

I can reproduce, I doubt the liveshare extension can do anything. I believe this got reported in VSCode via https://github.com/Microsoft/vscode/issues/47264 so we can continue the discussion also there.

@bpasero Yeah, that looks like the same issue.  We'll leave this issue open as reference for those using Insiders for the moment, but I'll tag as external..

@Chuxel we have since released a new insiders version with the old Electron version. All of this seems to get triggered from a very old dependency to fsstream. More details in https://github.com/electron/electron/issues/10905#issuecomment-379248466

@bpasero Replied on mail as well - we don't directly use fsstream but we use the latest versions unzip which appears to have this problem.  We also use the latest fs-extra which is also referenced in the above issue which doesn't use fsstream but is also referenced in the bug above.  Thanks very much for the support and help here!
Net-net though is it sounds like everyone should update their Insiders this morning if they hit this.

@Chuxel is there an issue for the unzip module using the outdated module?

@bpasero I just checked and there is not currently  - it does have an outdated dependency. "fstream": ">= 0.1.30 < 1".  graceful-fs does appear to have an issue on node 8.3.0 though it does not use fsstream as far as I was able to see: https://github.com/isaacs/node-graceful-fs/issues/116

@Chuxel wow is that https://github.com/EvanOxfeld/node-unzip which has been changed 4 years ago for the last time? Wouldn't there be an alternative module with the same functionality that is not so outdated?

@bpasero Yeah this was done due to incompatibles of other modules with .NET Core.  We're keeping this bug open so we can address the dependencies. @davidkpiano will be starting to take a look.

@Chuxel sounds good, thanks

While the extension host crash has been resolved, we have a new issue with Insiders, where guest's receive "corrupted" contents when opening up files: https://github.com/Microsoft/vscode/issues/47363.
@Chuxel Should we update the title of this bug (or open a new one) to ensure that as users update to 1.23, they're aware that we're looking into the latest symptom? (which wouldn't be a crash)

@lostintangent Let's update the title of this one and create a new issue for the other behavior.  We still have work to do to remove the old dependencies.

Opened #184 for garbled text behavior.

@Chuxel @lostintangent we would like to move forward with the Electron update as soon as possible, would it be possible for you to make the move away from unzip library soon? Our current thinking is that we simply throw an error as soon as an extension (or any dependency like unzip) calls require("natives") to prevent the crash from happening.

It would (theoretically) - we can depend on yauzl instead of unzip.

@bpasero Adding another response since I'm not sure if David's edit would have popped up for you. :) I didn't see it.
It sounds like we can't switch because some sort of .NET Core issue - I don't know the details. @srivatsn looked at this for a while (trying a bunch of different libs) so he can fill in the details. We're trying to lock down a bit release at the moment heading towards build so we can start stabilizing is part of the challenge for looking into alternatives.

@davidkpiano @Chuxel does that last comment mean you cannot (or will not) work on this until build conference is over? I do not think that is a model that would work for us, we have to move forward with Electron before that time frame.
PS: did you try to use the unzip-stream node module which seems to be a drop-in replacement for the unzip library?
PPS: we need to run an experiment with Code Insiders on the new Electron framework starting next week. This would mean that insiders users have to switch to Stable for this time to use LiveShare, I hope that is OK.

@bpasero I'm on it - I'm checking out node-unzipper which seems to be an up-to-date fork of unzip.

Ya we tried yauzl but that fails on some of the zip files we need because those zips don't follow the zip spec apparently.

Verified that node-unzipper works (no natives dependency, and up-to-date).

It looks like an update went out to VS Code Insiders with the same version number (1.23-insiders) that blocks the use of natives and as a result Live Share now completely does not work on insiders.  This fix is caught in a set of other changes we're validating, but right now only VS Code Stable works.

@Chuxel yes, as announced and discussed. We will revert this early next week before releasing stable.

We just released v0.2.399 which should resolve this issue!


Failing inverse One-to-One relationship using a custom data type

Issue
The BasicEntityPersister, possibly loadOneToOneEntity() method, does not handle One-to-One relationships on the inverse side when using a custom data type.
I've stepped through the code and can see that getTypes() method is failing to find a mapping due to the SQL field name being passed in rather than the class field. E.g. from the example below its "t0.shipping_id" but I think should be "shipping". Unfortunately my understanding of the internals of Doctrine is not enough to spot the exact cause / place to fix.
Steps to reproduce
Create two classes with a one-to-one relationship using a custom data type. I used the Ramsey UUID library and Doctrine integration.
Create DQL that filters based on the inverse side and not that hydrated object returned has NULL for the relationship.
Filtering on owning side or using entityManager-find('Shipping', $id) both work correctly.
If I can give any more information or perform any tests please don't hesistate to ask.
Versions
doctrine/common                     v2.5.3
doctrine/dbal                       v2.5.4
doctrine/doctrine-module            1.0.0
doctrine/doctrine-orm-module        0.10.0
doctrine/orm                        v2.5.4
ramsey/uuid-doctrine                1.2.0
YAML mappings
Product:
  type: entity
  table: products
  id:
    id:
      type: uuid_binary
      generator:
        strategy: CUSTOM
      customIdGenerator:
        class: Ramsey\Uuid\Doctrine\UuidGenerator

  fields:
    name:
      type: string

  oneToOne:
      shipping:
        targetEntity: Voicesafe\Test\Shipping
        joinColumn:
          name: shipping_id
          referencedColumnName: id

Shipping:
  type: entity
  table: shipping
  id:
    id:
      type: uuid_binary
      generator:
        strategy: CUSTOM
      customIdGenerator:
        class: Ramsey\Uuid\Doctrine\UuidGenerator

  fields:
      transport:
        type: string

  oneToOne:
      product:
        targetEntity: Voicesafe\Test\Product
        mappedBy: shipping

Working Example - Owning Side
$qb = $entityManager->createQueryBuilder();

$qb->select('p')
    ->from('Product', 'p')
    ->where('p.shipping = ?1')
    ->setParameter(1, $id, 'uuid_binary');

$query  = $qb->getQuery();
$result = $query->getResult();

Debug::dump($result);

SQL Generated
SELECT p0_.id AS id_0, p0_.name AS name_1, p0_.shipping_id AS shipping_id_2 FROM products p0_ WHERE p0_.shipping_id = ')�.GF����\"'

Broken Example - Inverse side
$qb = $entityManager->createQueryBuilder();

$qb->select('s')
    ->from('Shipping', 's')
    ->where('s.id = ?1')
    ->setParameter(1, $id, 'uuid_binary');

$query  = $qb->getQuery();
$result = $query->getResult();

Debug::dump($result);

SQL Generated
SELECT s0_.id AS id_0, s0_.transport AS transport_1 FROM shipping s0_ WHERE s0_.id = ')�.GF����\"'
SELECT t0.id AS id_1, t0.name AS name_2, t0.shipping_id AS shipping_id_3 FROM products t0 WHERE t0.shipping_id = '2901d32e-1247-4615-9f13-baafec221604'

Note: shipping_id is using the string representation not database value.
Thanks a lot for any help / advice or even a suggested bug fix.
Alex

Can someone please have a look into this bug. I would look into myself but will probably end up breaking stuff!!!

I came across this bug and spent quite some time debugging and found following line:
BasicEntityPersister.php#L786
$identifier[$this->getSQLTableAlias($targetClass->name) . "." . $targetKeyColumn] =
    $sourceClass->reflFields[$sourceClass->fieldNames[$sourceKeyColumn]]->getValue($sourceEntity);

Keys of $identifier array are being used in BasicEntityPersister::getTypes but since the keys are in the form of table_alias.column_name e.g. t0_.user_id it can't find the appropriate type.
After changing previously mentioned line to:
$identifier[$targetClass->getFieldForColumn($targetKeyColumn)] =
    $sourceClass->reflFields[$sourceClass->fieldNames[$sourceKeyColumn]]->getValue($sourceEntity);

Which results in keys being in the form of mapped class field name and in BasicEntityPersister::getTypes it gets mapped correctly using target class associationMappings.
I did not test this heavily but it works for the case with which I had trouble but as I never worked with doctrine source code it would be best if someone took a look at it. I'll try creating pull request for this over the weekend but if someone wants to do it sooner feel free.

@alexb-uk can you please check if that is fixed on master since #6274 got merged?


can we train yolo on imageai

Is there any tutorial which shows how to rain on imageai as yolo ?
and I wanted to create bonding box automatic to label images to use in yolo because I have 100K images need to train but cannot do labeling manual

Please refer to #8


Compatibility

According to your read me, the most recent version of libPusher is not backwards compatible with the previous version.  Does this mean that clients using the previous version of libPusher can't send messages to clients using the most recent version of libPusher?
Thanks for the great work!

No, it just means that if you were previously using an old version of the library, you will need to make some significant changes to your code if you update to the newer version.
If you are using the old version of the library, as long as it's talking to Pusher correctly it will receive messages however they were sent.


[Demo review] MFA enabling process - Show current time (and minor fixes)

Update text changes

[ ] Update userhelp link to "Learn about MFA" so its more accessible.
[ ] Update grace period label to "Allow grace period until (Optional):"
[ ] Add help text below input: "MFA setup will be optional during grace period. Reminders to setup MFA will appear on login.

See CMS Admin turns on 2FA: https://projects.invisionapp.com/dsm/silver-stripe/silver-stripe/folder/components/5c68f96ffb26bb0018525d1a

There's a semantic difference between showing the current date and not showing anything at all. By showing the current date, you'll end up setting the grace period to expire today, which is different from not setting one at all. I think if you want to do this you might want to also have a checkbox saying "Grace period enabled" to clarify that the date you set (e.g. today) is actually enforced.

@newleeland would you be happy to skip the "show current date/time" suggestion? I'm happy with the rest of your suggestions

I'm fine with not showing the current time and just havd "dd/mm/yyyy"
I'll be updating the design to have the text label t include "(Optional)" in the end

Potential text:
Will be Required from
if date is in the future then user will be prompted registration to help them

Closing this issue as tasks are now captured in other issues.

Update userhelp link to "Learn about MFA" so its more accessible. : #142
Update grace period label to "Allow grace period until (Optional):": #144
Add help text below input: "MFA setup will be optional during grace period. Reminders to setup MFA will appear on login: #144


R2DBC API: Provide Row.get(Object identifier)

From @mp911de on June 7, 2018 15:24
When reading and mapping data into objects, it's common to have types which differ between the model and its persistent representation. We should have a method to read values and let the driver determine the data type.
Note: Ideally, we have Row.get(String identifier) and Row.get(int index) methods to tighten up the API contract and resolve ambiguities over the identifier.
Copied from original issue: r2dbc/r2dbc-client#7

I think we should break out the discussion about identifier types into a separate issue as it's larger than this.

At the moment, the PostgreSQL implementation will work as you'd expect if you did a Row.get("$1", Object.class) and that's by design (we use isAssignableFrom() as part of the conversion).  This is clearly an implementation decision and isn't contractually obligated.  Do you think that this should be an additional API (Object Row.get(Object identifier)) to codify it, or should this be an API documentation change?  If you think an additional API is required, how do you feel about a default method that makes the delegating call with Object.class?

For now, we could utilize Row.get(…, Object.class). Currently, I'm getting:
Caused by: java.lang.IllegalArgumentException: Cannot decode value of type java.lang.Object
		at io.r2dbc.postgresql.codec.DefaultCodecs.decode(DefaultCodecs.java:85)
		at io.r2dbc.postgresql.PostgresqlRow.get(PostgresqlRow.java:82)

for a numeric column. Calling Row.get(…, Integer.class). I will file a separate ticket for the exception in r2dbc-postgresql.
I think we should be good for now when stating that the type parameter allows for variance (e.g. Number, Object).  A default method Object Row.get(Object identifier) delegating to Row.get(identifier, Object.class) could also serve as documentation and we don't need to touch implementations.

Here's the ticket for the exception on Row.get(…, Object.class): https://github.com/r2dbc/r2dbc-postgresql/issues/8.


Enable operations on CloudObjectStoreObject

This commit brings support for operations on CloudObjectStoreObject. For now, only delete operation is supported. The two new columns type and name have to be there to enable appropriate async task processing.

@miq-bot add_label enhancement
@miq-bot assign @durandom
@miq-bot assign @kbrock

@miha-plesko looks like you have to update schema.yml too


HWKAPM-742 : Retrieve property values on TX change

In order to replicate, both Transactions must have the same property name (eg: fault), otherwise it will clear the selected property name and the issue won't occur.

@ammendonca Thanks!


getting photo id of a recived message

Hi
I was trying to get photoID of the message I recived using OnMessage event and messageEventArgs but couldn't find any property representing it.
can you help me find it?
thank you
NuGet Package Version: (e.g. 13.0.1)
.NET Version: (e.g. 4.7, Core RTM, Mono, etc.)
IDE: (e.g. VS2017, VS Code, etc.)
App: (e.g. Desktop, iOS, Android, etc.)

MessageEvenArgs.Photo.FileId or sth
And I find it really funny that you used the issue template but didnt fill it xD


No such file or directory: 'datasets/coco/annotations/panoptic_val2017.json'

got this when trying to follow semantic segmentation toturial, couldn't find panoptic_val2017.json anywhere

got this when trying to follow semantic segmentation toturial, couldn't find panoptic_val2017.json anywhere

you need to export the dataset path for detectron2 when using the convertion script. export DETECTRON2_DATASETS=$YOUR DATASET_PATH

I solved this issue by downloading annotation file at https://cocodataset.org/#download


How to Create an Automatic Slider in Android Studio

Be sure to visit our Resources Page for tools, resources, and example articles to go over.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
We're looking for the first 2-3 paragraphs of the article that appropriately summarize what your article will be about.
NOTE: We tend to stray away or tend not to publish reviews/comparisons of commercial product offerings.
Proposed title of the article
How to Create an Automatic Slider in Android Studio
Introduction paragraph (2-3 paragraphs):
Sliders are commonly used on cross platforms, i.e., websites, Desktop applications, and mobile applications. They are widely implemented on the home pages or application main screens to showcase major and key features.
Let's take the case of an eCommerce application. You would like to show the new items you have in your shop without interfering with the user app interaction. Slides would be a perfect way to showcase some of these major new items to your users.
This guide will walk you through how to create an automatic slider page using android studio.
What we shall look at
We will create a slider based on the following concepts.

Populate an array list of slides into a ViewPager using PagerAdapter.
Set a list of slides in a tabbed layout and a toolbar.
Set timmer that will automatically slide to the next slider after a set of milliseconds.

Prerequisites
This guide uses java in android studio. Prior knowledge of android ViewPager, PagerAdapters, and TabLayout would be helpful.
Setting Up
Start a new android studio project. I have changed the default parent theme. To do that on your android studio, go to res folder → values → style.xml and change the app theme, as shown below.
<resources
<style name="Theme.AnAutomaticAndroidSlider" parent="Theme.AppCompat.Light.DarkActionBar"></style>
</resources>

Laying out the slider components
Create an XML layout name it slider_items_layout.xml. The slides are comprised of two major views.

A text view for the slide title.
An image view for the slide hero image.

Key takeaways:

Setting up the android studio project
Laying out the slider UI components
Setting a ViewPager and TabLayout
Setting up PagerAdapte and a model class
Preparing the slider adapter
Setting up the timer
Testing the application

References:
https://developer.android.com/reference/kotlin/androidx/viewpager/widget/PagerAdapter
https://developer.android.com/reference/com/google/android/material/tabs/TabLayout
Templates to use as guides

How To Guide Template

good topic @kimkimani - approved


Uninstall

How can you uninstall nltk, after you've previously run
sudo python setup.y install
?

sudo pip uninstall nltk


Could I use this module without managed identity to get certificate from key vault?

I am in the process of setting up the CI/CD and the certificate with HSM in Key Vault, and I'd like to test that I did not mess up the certificate, and for that I thought maybe I can just sign a test script from my local machine without a managed identity... but from the error message I am not sure if this should be impossible at the moment or I am just "holding it wrong"
Get-OpenAuthenticodeAzKey: DefaultAzureCredential failed to retrieve a token from the included credentials. See the troubleshooting guide for more information. https://aka.ms/azsdk/net/identity/defaultazurecredential/troubleshoot
- EnvironmentCredential authentication unavailable. Environment variables are not fully configured. See the troubleshooting guide for more information. https://aka.ms/azsdk/net/identity/environmentcredential/troubleshoot
- ManagedIdentityCredential authentication unavailable. Multiple attempts failed to obtain a token from the managed identity endpoint.
- Visual Studio Token provider can't be accessed at C:\Users\User\AppData\Local\.IdentityService\AzureServiceAuth\tokenprovider.json
- Azure CLI not installed
- Please run 'Connect-AzAccount' to set up account.

I ran Connect-AzAccount with browser based SSO.

The code uses DefaultAzureCredential which should support various environmental settings which includes the logon from Connect-AzAccount.
https://github.com/jborean93/PowerShell-OpenAuthenticode/blob/ce28aa336b9402fd863ae9d384d6d03910dd0cd5/src/OpenAuthenticode.Module/AzureKeyVault.cs#L83
As an example I use OIDC OAuth authentication with the azlogin action to set up the environment in this module for signing https://github.com/jborean93/PowerShell-OpenAuthenticode/blob/ce28aa336b9402fd863ae9d384d6d03910dd0cd5/.github/workflows/ci.yml#L32

Isn't new(includeInteractiveCredentials: false); means what my interactive credentials are ignored?

OK, so it seems that my interactive credentials won't work, and unless I can get a managed identity - which is not interactive, I need to set up a pipeline to test.

Potentially my terminology isn't up to date but ultimately if you are setting up something in CI you are going to need some form of auth that doesn't require explicit interaction and thus need some sort of service principal to authenticate as. You have various ways to do this authentication like the env var secrets, OAuth OIDC to authorize the pipeline, etc. The connection setup by Connect-AzAccount should cache the logon for the process and should be usable by the Get-OpenAuthenticodeAzKey though, it's agnostic to it all and just uses the default logic inside DefaultAzureCredential.


kidney_donor_profile_index is “Kidney Donor Profile Index”?

See if there's some other field to pull from Jonathan's data that gives us a more meaningful value.

Fixed.


carbonmark: Fix project's page hydratation issue

Description
Fixes the hydratation issue on the /projects page when there are no query parameters
as per the documentation https://nextjs.org/docs/pages/api-reference/functions/use-router router.isReady should not be used outside of useEffect
Fixes #1959

Checklist

[x] I have run npm run build-all without errors
[x] I have formatted JS and TS files with npm run format-all

Was there a ticket for this @biwano ?

Was there a ticket for this @biwano ?

No, I just created one: https://github.com/KlimaDAO/klimadao/issues/1959

@Atmosfearful I went for rendering server side at every request.
I made a few more changes to make the best of that situation:

Use query parameters server side
Displays projects on first render
Only make a request on the client when a query parameter is changed by the user

@0xemc If you have some time to take a look too,
If that's good:

We will need a QA pass
maybe we can extract a pattern for other pages.


Uninstall

This PR solve #80, in order to uninstall only packages installed through arduino-connector during installation will create a config file listing packages already present, like network-manager, docker (images + container), and so on...
The uninstall feature is called by API /status/uninstall/post and at the end of the uninstall process it creates a script (uninstall-arduino-connector.sh) for the user that must run to finalize the uninstall process. This because is impossible to stop and remove service from within arduino-connector, that script removes also the binary.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


⚠ ClamAV has degraded performance

In bba84f7, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in 570fe6e.


Updates for Debug nugets

Fix nuspec files to include .netcoreapp.3.0
create nuspecs for Identity and Policy projs
Update CreateDebugNuget script

Obsolete


Left View of Binary Tree

💥 Proposal
(A clear and concise description of what the proposal is.)
This is to add a C++ program to find left view of a Binary Tree.
The left view of a Binary Tree contains all nodes that are first nodes in their levels.
Have you read the [Contributing Guidelines on Pull Requests]
Yes
(https://github.com/TesseractCoding/NeoAlgo/blob/master/CONTRIBUTING.md#reporting-new-issues)?
(Write your answer here.)
This program will be helpful in understanding concept of binary trees better. I will be happy contributing here under GSSoC'21.

/assign


implement multi-MPPT inverter model

[x] Closes #457
[x] I am familiar with the contributing guidelines
[x] Tests added
[x] Updates entries to docs/sphinx/source/api.rst for API changes.
[x] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[x] Pull request is nearly complete and ready for detailed review.
[x] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

An approach that leverages the existing function pvlib.inverter.sandia and the model parameters available in the SAM file. Conceptually, this is the same approach as in Pvsyst, although it appears that Pvsyst offers more options for adjusting the inverter's behavior (and Pvsyst uses an internally-developed inverter output model, which isn't fully documented in the public files).

I found these pages in the pvsyst help docs interesting:

[Power sharing](https://www.pvsyst.com/help/powersharing.htm(
Grid Inverters: main parameters] (https://www.pvsyst.com/help/inverters_general.htm)

Be careful: as in the PVsyst inverter database, there is no information about the maximum power (or current) for each individual MPPT input, it is your responsibility to check in the data sheets whether the allocated power is compatible with the manufacturer's specifications.  PVsyst puts a  general limit to the sharing ratio, which is modifiable in the Hidden parameters.

Has anyone checked the hidden parameters?

Has anyone checked the hidden parameters?

I don't have a Pvsyst license, I'd be interested to know what parameters are hidden that relate to multi-MPPT inverters.
I've read those pages and also exchanged email with Bruno at Pvsyst. I don't feel confident that I accurately understand how inverter efficiency is modeled in Pvsyst, so am not proposing a inverter.pvsyst function.
Inverter datasheets typically list limits on DC current per MPP input, but these limits appear be related to safety (e.g. fuse ratings) rather than limits on DC-AC conversion.
For this model, I had proposed a parameter 'dc_limit' which would act as a cap on DC power at each MPP input. But after some discussions, I've removed that parameter for two, related reasons:

there's no reliable source for its value (the safety limits in datasheets are not what is needed here)
it is not clear that inverters actually impose limits per MPP input.

Bumping this PR as I think it's ready for review, and is needed to move #1076 forward.

@cwhanse you can decorate that failing psm test function with @pytest.mark.xfail(strict=True, reason='github 1091')

@pvlib/pvlib-maintainer will merge on 12/2 unless there are additional reviews

@pvlib/pvlib-maintainer Will merge today if no further reviews

let's move on with it - thanks @cwhanse!

Sorry I am a bit late to the game on this.  My understanding of the multi-MPPT modeling method currently being worked on is that all arrays are operating at the same DC voltage.  The focus is address clipping per MPPT.  When I first brought up this question I was modeling a residential system with 2 arrays on different planes and of different sizes.  My solution at the time was to average the DC voltage between the 2 arrays and feed that into the inverter efficiency loss function.  Given the huge variations in insolation because of shading on a typical residential system, any accuracy loss because of the inverter efficiency was not a concern to me at the time.  No suggestion here.  I just wanted to circle back with the original use case.


It would help to have a working example

Why not set up a repository with a working example using word2vec?  I find that most documentation is badly written; so I prefer to just look through working code.

Yes, it would be great if there is a working example.

The documentation is actually pretty good; so I'm closing this.


use smithy-core package as aws dependency

Use smithy-core npm package as AWS dependency instead of copying to lib/smithy.ts
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

smithy-core package added in https://github.com/aws/aws-sdk-js-v3/pull/546

This code could also get added to @aws-sdk/smithy-client.  I don't think smithy-core would be used independently of smithy-client, so may make sense to bundle them into one package.

Approved in https://github.com/aws/aws-sdk-js-v3/pull/546 as "smithy-core"


Concern about mp4 with no sounds

can you help me? i already download youtube videos links but results is mp4 with no sounds?
### This is my Settings i dont know if correct?

Your settings are ok. Open the videos with software like VLC, the default media player in windows does not support the audio codec that youtube is using, which is why you don't hear anything when playing the videos. Get VLC from here: https://www.videolan.org/vlc/


Pre-release

Found a bug. It looks like when there isn't any actually frontmatter, spaces are being inserted anyways:

Fixed with https://github.com/stateful/runme/pull/421/commits/796a444db283c0f26fa12455c0fe6a8f099090a5


Z-Targeting: NPC Giving same response on chat

NPC Giving same response on chat.
Uploading 2022-06-29 21-09-16.mp4…

@msm0823 hey i don't think your video finished uploading


ARROW-3150: [Python] Enable Flight in Python wheels

Flight enabled in manylinux1 and Windows wheels.

Fails here with:
auditwheel: error: cannot repair "dist/pyarrow-0.13.1.dev401+g6fc91cd1c.d20190617-cp37-cp37m-linux_x86_64.whl" to "manylinux1_x86_64" ABI because of the presence of too-recent versioned symbols. You'll need to compile the wheel on an older toolchain.

@wesm @xhochy

Kind of annoying that auditwheel doesn't tell you which symbols it doesn't like
https://github.com/pypa/auditwheel/issues/36

I can't look at this today but perhaps tomorrow if no one else resolves it by then

After a lot of mystery and head-scratching I finally found the remedy: git clean -Xfd. Apparently our Docker container isn't isolated at all.

Now someone should upload an updated build image before CI builds can proceed, I think. Who has the rights to do that?

Anyone who can push to my fork or who is happy to setup a quay.io account on their own.

@xhochy I have created a quay.io account, but does that mean the script would need to be changed to point to my account? Is there a group account that we can use?

@pitrou if you'd like to push the image to https://quay.io/organization/ursa-labs I'm sure that's no problem, @kszucs can give any Arrow committer push access

That would be fine with me.

We don't really use https://quay.io/organization/ursa-labs. Either way We need to change the docker repository's url, so I suggest to use https://hub.docker.com/u/ursalab and create a user there. @pitrou sent You an invite to your python email address.

@kszucs I didn't receive the dockerhub invite, so I'll try to push to quay.io.

@kszucs I need to confirm the Windows script works on CI. How do I do that?

@ursabot crossbow --help

@ursabot crossbow package wheel

Note that the badges might be cached, until a workaround please refresh the page with wiped cache - the badges are updated after the build finishes.

@ursabot crossbow package wheel

@ursabot crossbow package wheel-win-cp37m

@ursabot crossbow package wheel wheel-win-cp37m

@ursabot crossbow package wheel

@ursabot crossbow package wheel-win-cp35m wheel-win-cp36m wheel-win-cp37m

@pitrou I've changed the interface of the crossbow command, now You can run standalone tasks too, not just groups.

@ursabot crossbow package wheel-win-cp36m

@kszucs Could you cancel the pending AppVeyor builds?

@ursabot crossbow package wheel-win-cp36m

@ursabot crossbow package wheel-win-cp36m

@ursabot crossbow package wheel-win-cp36m

@ursabot crossbow package wheel-win-cp36m

@ursabot crossbow package wheel-win-cp36m

AppVeyor wheel build still failed: https://ci.appveyor.com/project/Ursa-Labs/crossbow/builds/25365203
I think we'll have to bundle the OpenSSL DLLs.

@pitrou agreed. I recommend rebasing as I've just merged two PRs that touch the manylinux build (shared library deduping, and ORC-use-system-packages ARROW-3052)

I updated the title that this is for Linux and Windows, we can deal with macOS in a follow up PR if that sounds good

@ursabot crossbow package wheel-win-cp36m

@ursabot crossbow package wheel-win-cp36m

@ursabot crossbow package wheel-win-cp36m

Looks like it worked save for a permissioning issue
Deploying using GitHub provider
Creating "ursabot-25-wheel-win-cp36m" release for repository "ursa-labs/crossbow" tag "ursabot-25-wheel-win-cp36m" commit "c335c9db4dcffb1964473897c9261bd0f6f938f5"...Error creating GitHub release: Error reading repository 'ursa-labs/crossbow' releases: 401 - Unauthorized

No, it didn't. I disabled the failing wheel test to be able to download the wheel file.

Progress status:

manylinux done
Windows theoretically done, but importing the wheel fails on AppVeyor (on the same image that's used to build it!) even though it succeeds at home

@ursabot crossbow package wheel-win-cp36m

Joy. I would suggest merging this and tackling the Windows issue as a follow up, not sure how else to proceed =/ Someone will need to look at macOS also

@ursabot crossbow package wheel-win-cp36m

Update: this should work now. Except for the deploying part highlighted by @wesm. @kszucs can you fix that?

@ursabot crossbow package wheel-win-cp36m

@ursabot build


[BP-1.16][FLINK-32023][API / DataStream] Add config execution.buffer-…

Backports FLINK-32023 to release-1.16.

Hi @Myracle , the commit message shouldn't add the [BP-1.16]as the prefix, the commit message should be the same with master branch, could you help update the commit message?


feat: New tab ui changes

Description
Added new design of New Query/Js tab design.
Fixes #33116
Automation
/ok-to-test<EMAIL_ADDRESS>@tag.IDE"
:mag: Cypress test results

[!CAUTION]
🔴 🔴 🔴 Some tests have failed.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/9015524659
Commit: 12534deadd9aa0bdb1e92cdab57db2bb8e2f2a00
Cypress dashboard:  Click here!
The following are new failures, please fix them before merging the PR:
cypress/e2e/Regression/ClientSide/IDE/IDE_Add_Pane_Interactions_spec.ts
To know the list of identified flaky tests - Refer here

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

/build-deploy-preview skip-test=true

/build-deploy-preview skip-test=true

/build-deploy-preview skip-test=true

/build-deploy-preview skip-test=true


"Trojan:Win32/Fuery.B!cl" detection

Windows Defender is detecting a trojan in the executable

Dupe of #17


fix crash with camera permissions off. nav up when you delete a message

@keybase/react-hackers
this fixes a crash if you turn off camera permissions. there's an error which we didn't plumb through
this also fixes a crash if you delete an attachment from a popup and keep that screen up. instead of keeping it up we instead nav back up

Yeah that's what I'm looking for.  Kinda wanted to nav up to a certain parent really. Maintaining any state or props that happened to exist. We used to have a navigateUp that took a pathname param. This is fine though.


Only old versions available

When I run snap info home-assistant-snap.
It only shows versions up to 2021... and I can't install newer versions either....

Does anyone have any ideas?

Very old 🤪
As long as I'm the only maintainer I'm only pushing latest to the latest track, and the final versions for each when they have hit final (aka "stable").
However the latest is typically in the edge channel (latest/edge).

(ah, you're on armhf. We've ended support for those.  Thanks for your fast reply :)

Happy to help 😄 Hope you'll solve it!


amplify deployment of Next.js showing deployment failed without any error logs

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d1lxz7k7qngoq2
Region
eu-central-1
Amplify Console feature
Not applicable
Describe the bug
i can deploy the repository existing in the root of created group but cannot deploy from the repository which are nested inside the group in gitlab.
Expected behavior
my repository inside group should be deployed in amplify
Reproduction steps
1.firstly create a group in gitlab
2. then further create a sub group
3. and add a repository there in created sub group and deploy using amplify
Build Settings
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm install
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: .next
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Additional information
No response

I'm having the exact same issue! When I try to deploy a Gitlab repo that lives in sub-group in Gitlab (so a group under a group), deployment fails without any clear error message. When I move that repo directly to the "root" group in Gitlab, deployment works.
@zugger14 your description of this issue has been a life saver for me, because at least now I have a workaround

Has this been solved by now? It's super inconvenient to have to put all of our frontend repos in a top-level group.

this issue should be resolved, feel free to re-open if you continue to face the issue. thank you!


Find out what performance implication would be of inlining metadata

Inlining metadata with geometry would mean more I/O as part of rewriting each zoom level, but potentially less thrashing since read access would be linear instead of random. Does the reduced thrashing when memory is low compensate for the extra write time when there is lots of memory available?

A simple test with tl_2014_06001_roads (which easily fits in memory) shows a 16% performance hit by having to recopy the metadata as part of the geometry instead of just referring to it.

This seems to have been a bad idea

The other strike against it is that as large polygons get split across many tiles, the metadata will get massively duplicated.

Maybe the thing to do is to inline the metadata if it and the string pool start to get close to the size of memory and if the bounding box of the feature is small (say, a maximum of 4 tiles at maxzoom). This could fix thrashing with large data without spending too much time recopying when it's not going to thrash anyway.

Working on this again in https://github.com/mapbox/tippecanoe/pull/245. It does still have a performance hit in the normal case because of the extra copying, but ought to help with thrashing in some of the low-memory situations.

This was merged.


Adjust planning unit: support multipolygon

Substitute this line for a meaningful title for your changes
Overview
Add support for multipolygons inside the "adjust planning unit upload file"

@mbarrenechea a delay has been introduced in BE and now we have a change in status (from 'running' to 'done'). Even so, the fetch of the planning units is not carried out again after the done status appears. Not sure what is the best way to solve it.
Also I noticed when uploading smaller files layer updates.

@mbarrenechea a delay has been introduced in BE and now we have a change in status (from 'running' to 'done'). Even so, the fetch of the planning units is not carried out again after the done status appears. Not sure what is the best way to solve it.
Also I noticed when uploading smaller files layer updates.

Checking it


fix: Update flow log ARNs to use partition from aws_partition data source

… ensuring compatibility with AWS GovCloud and other partitions
Description
Update flow log ARNs to use partition from aws_partition data source, ensuring compatibility with AWS GovCloud and other partitions. This was due to the least privilege change in 5.12.0, 5.11.0 and earlier are fine. See PR #1088
Motivation and Context
Currently when deploying to GovCloud with flow logs you get the following error
MalformedPolicyDocument: Partition "aws" is not valid for resource "arn:aws:logs:us-gov-west-1:0123456789:log-group:/aws/vpc-flow-log/vpc-012345:*"

Breaking Changes
No
How Has This Been Tested?

[X] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[X] I have tested and validated these changes using one or more of the provided examples/* projects

[X] I have executed pre-commit run -a on my pull request

This PR is included in version 5.12.1 :tada:

Thank you for quick review and release


can run/debug jbang show up in the short cut menu?

would  be awesome if run/debug jbang could show up in the "run" menu/icon

@testforstephen @jdneo is there a way to contribute entries there?

Yes: https://github.com/microsoft/vscode-java-debug/blob/b26af9542ee140e10d464c3d75dbf0f6dc3a2e42/package.json#L187-L198

Thanks @jdneo, it worked:


Add Propel Data

Context: https://www.snowflake.com/blog/startup-spotlight-api-on-top-of-snowflake-propel/

Thank you @JPHaus. It seems like it's not visible on the site yet. Will it need to be deployed?


PG Replication

Let's inform users why they might like to replicate, how to set up replicas, and everything else they need to know.  Split the PR if it ends up bigger than 3 articles though!
Candidate content from the previous docs site:

Replication

[x] High availability in Aiven for PostgreSQL
[x] Setting up PostgreSQL logical replication
[x] Using PostgreSQL read-only replicas
[x] Aiven for PostgreSQL remote replica
[x] Detecting and addressing inactive or lagging PostgreSQL replication slots
Failover proxy

The failover proxy is partially covered in the /concepts/upgrade-failover article, I don't think this additional info is key for our developers

Related content is now merged.


Lock Faraday version to 0.8 branch

The pessimistic version for the Faraday gem is not tight enough in the latest release (v1.21.1) for this gem. As a result, version 0.9.x of Faraday gets installed and the gem explodes.
$ bundle exec rackup
/Users/s/.gem/ruby/2.2.2/gems/faraday-0.9.2/lib/faraday.rb:99:in `method_missing': undefined method `load_autoloaded_constants' for #<Faraday::Connection:0x007f897d802218> (NoMethodError)
	from /Users/s/.gem/ruby/2.2.2/gems/stretcher-1.21.1/lib/stretcher.rb:8:in `<top (required)>'
	from /Users/s/src/test/stretcher-1.21.1-app/config.ru:1:in `require'
	from /Users/s/src/test/stretcher-1.21.1-app/config.ru:1:in `block in <main>'
	from /Users/s/.gem/ruby/2.2.2/gems/rack-1.6.4/lib/rack/builder.rb:55:in `instance_eval'
	from /Users/s/.gem/ruby/2.2.2/gems/rack-1.6.4/lib/rack/builder.rb:55:in `initialize'
	from /Users/s/src/test/stretcher-1.21.1-app/config.ru:in `new'
	from /Users/s/src/test/stretcher-1.21.1-app/config.ru:in `<main>'
	from /Users/s/.gem/ruby/2.2.2/gems/rack-1.6.4/lib/rack/builder.rb:49:in `eval'
	from /Users/s/.gem/ruby/2.2.2/gems/rack-1.6.4/lib/rack/builder.rb:49:in `new_from_string'
	from /Users/s/.gem/ruby/2.2.2/gems/rack-1.6.4/lib/rack/builder.rb:40:in `parse_file'
	from /Users/s/.gem/ruby/2.2.2/gems/rack-1.6.4/lib/rack/server.rb:299:in `build_app_and_options_from_config'
	from /Users/s/.gem/ruby/2.2.2/gems/rack-1.6.4/lib/rack/server.rb:208:in `app'
	from /Users/s/.gem/ruby/2.2.2/gems/rack-1.6.4/lib/rack/server.rb:336:in `wrapped_app'
	from /Users/s/.gem/ruby/2.2.2/gems/rack-1.6.4/lib/rack/server.rb:272:in `start'
	from /Users/s/.gem/ruby/2.2.2/gems/rack-1.6.4/lib/rack/server.rb:147:in `start'
	from /Users/s/.gem/ruby/2.2.2/gems/rack-1.6.4/bin/rackup:4:in `<top (required)>'
	from /Users/s/.gem/ruby/2.2.2/bin/rackup:23:in `load'
	from /Users/s/.gem/ruby/2.2.2/bin/rackup:23:in `<main>'

The contents of the two files used:

Gemfile:

source "https://rubygems.org"

gem "rack"
gem "stretcher"

config.ru:

require 'stretcher'

Fixing this issue should be as simple as applying this diff:
     gem.add_runtime_dependency('json')
   end

-  gem.add_dependency('faraday', '~> 0.8')
+  gem.add_dependency('faraday', '~> 0.8.11')
   gem.add_dependency('faraday_middleware', '~> 0.9.0')
   gem.add_dependency('excon', '>= 0.16')
   gem.add_dependency('hashie', '>= 1.2.0')

and releasing the change as v1.21.2.

@andrewvc: I'd be interested in your thoughts on this if and when you have time.

:wave:


output/input types should be changed.

I notice that the MLX inputs/outputs aren't compatible with the standard items, so can't use a standard model intot he ksampler etc, so i think you should change the expected types to something like mlx_model to block people making the mistake

Hello @cchance27,
Thank you for your feedback! 🙏
You are absolutely right. I’ll make the changes early next week.
Have you tried connecting the MLX Sampler with any SDXL model or others? Let me know so I can prioritize the next feature update.

Update pushed ! New basic workflow here: https://github.com/thoddnn/ComfyUI-MLX/blob/main/workflows/basic_workflow.json


Cannot update vault with python's azure.mgmt.recoveryservices

I am trying to disable the "SoftDeleteState" and "EnhancedSecurityState" of our recovery services vault via the python azure-sdk libraries. For some reason the changes don't take affect. Running my own def below just returns a Vault object but no changes take effect and no errors. I've taken this code from the sample code in the azure-sdk docs and have fiddled with it to try and get it to work, but nothing seems to work.
Any ideas of what I may be doing wrong?
from azure.mgmt.recoveryservices import RecoveryServicesClient

def disable_soft_delete(subid, rg_name, vault_name):
    response = recovery_services_client.vaults.begin_update(
        resource_group_name=rg_name,
        vault_name=vault_name,
        vault={
            "properties": {
                "SecuritySettings": {
                    "SoftDeleteSettings": {
                        "SoftDeleteState": "Disabled",
                        "EnhancedSecurityState": "Disabled",
                    },
                },
            },
        },
    ).result()
    print(response)

Hi @arielc, please try the code below instead:
from azure.mgmt.recoveryservicesbackup import RecoveryServicesBackupClient

def disable_soft_delete(subid, rg_name, vault_name):
    response = recovery_services_client.backup_resource_vault_configs.update(
        resource_group_name=rg_name,
        vault_name=vault_name,
        parameters={
            "properties": {
                "enhancedSecurityState": "Disabled",
                "softDeleteFeatureState": "Disabled"
            }
        }
    )
    print(response.properties)

Using the RecoveryServicesBackupClient did the trick. Thanks!


Support dependent fields in internals

We need to handle cases such as:
template
class Whatever
{
T Foo;
}
class Bar
{
Whatever W;
}
In here, Foo is a dependent field. We need to represent it in Internals as an int. One of the approaches is generating a separate internal struct per template specialisation.

Dependent fields in internals are actually impossible to support. Structures with native layouts cannot be generic so we can only use separate structures per specialisation which we already do.


[Docs]Added details/guidance in README based on Issues

Fixes nothing
Changes Proposed in this pull request:

Added more details in the README based on issues people are facing

@jamesmontemagno anything else you'd like me to change in the docs here?


Quick fix to precision recall

See issue #62 .

Everything seems to be correct and making the groupby explicit is definitely needed. I have to say that I still do not see how it solves the issue about counting twice vs. counting once (as discussed in the issue, see last comment) but I trust you on it. When I have some more time I can think into it further.

If you have unique groupings now, ie one group per sample. Then there will no bidirectional vertices since you are only looking at one node. If you group by several nodes, then yes we still have the counting twice thing


CellStyleBuilder.merge(Map[] sources) performance

Merge escape statements always fail because sources.length is always 2. [null,null].length == 2.
This came up when profiling some larger sheet generation, [bx:10000]+. That sheet is causing GC overhead limit exceeded errors which I thought may be related to not using SXSSF, but maybe not.
class CellStyleBuilder {
...
Map merge(Map[] sources) {
//These guards are always false and never executed
        if (sources.length == 0) {
            return [:]
        }
        if (sources.length == 1) {
            return sources[0]
        }
//this executes for ALL THE THINGS
        (Map)sources.inject([:]) { result, source ->
            source.each { k, v ->
                result[k] = result[k] instanceof Map ? merge((Map)result[k], (Map)v) : v
            }
            result
        }
    }

Merge escape statements always fail because sources.length is always 2

This is true but I doubt that is causing you any issues. If you track down any memory issues please file a new issue


Small typo's

I noticed you used Tailwind instead of Tailwindcss. Looking at the branding of tailwindcss.com I think the brand name they want to come out with is with the CSS-part. Right? What do you think? Happy to change it back or do a replace-all.

Oh yeah, deffo. Thanks! If you find more happy to merge 'm in.

Or maybe it should be like this?


オラクルエンジンを追加

イカビール さんによる寄稿

https://oracleengine.tumblr.com/

Codecov Report

Merging #214 into master will increase coverage by 0.11%.
The diff coverage is 93.95%.

@@            Coverage Diff             @@
##           master     #214      +/-   ##
==========================================
+ Coverage   87.18%   87.29%   +0.11%
==========================================
  Files         214      215       +1
  Lines       22194    22337     +143
==========================================
+ Hits        19349    19500     +151
+ Misses       2845     2837       -8

Impacted Files
Coverage Δ

src/utils/command_parser.rb
97.01% <92.85%> (-1.20%)
:arrow_down:

src/diceBot/OracleEngine.rb
93.93% <93.93%> (ø)

src/diceBot/DiceBot.rb
94.25% <100.00%> (ø)

src/bcdiceCore.rb
73.85% <0.00%> (+0.25%)
:arrow_up:

src/test/DiceBotTestData.rb
100.00% <0.00%> (+4.00%)
:arrow_up:

src/test/DiceBotTest.rb
84.26% <0.00%> (+15.73%)
:arrow_up:

Continue to review full report at Codecov.

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

Ruby 1.8だとArray#to_sの挙動違うのか……

typo修正しました。
brakはbreakが予約語のため、意図的にその名前にしています。


Safely restart jenkins service

When we manage files on disk, we have to restart the Jenkins service if we make a change. Doing a service refresh does not take into account if any builds may be happening and will cause them to fail.
This commit adds a class which pulls the jenkins-cli.jar and issues a safe restart. Use this class to notify rather than the service itself.

Wow this is weird/cool.

I've changed this a little to use puppet-curl, and to just instigate the task as root.

Does the exec resource need a refreshonly => true set? And then notify => Exec['Restart Jenkins'] or something like that? Otherwise I'm a little worried the command might execute every Puppet run.

The notify in the File resource should only call when the file changes. I call the Class instead of an Exec to ensure that the jenkins-cli.jar exists. We could order this in a different way, perhaps with a require on the exec itself?

But I guess the exec will still execute every time because that's how it behaves, right? Unless it has an onlyif, unless or refreshonly or something like this.

@surminus For reference https://docs.puppet.com/puppet/3.8/type.html#exec-attribute-refreshonly

So does notify => Service['jenkins'], behave differently to notify => Class['Govuk_jenkins::Safe_restart'],?
That's what I don't understand, as I thought the notify would only call the class if the content changed on the File resource.

I've added refreshonly => true anyway as it doesn't hurt.

Thanks for the patience everyone (and for @deanwilson explaining), I misunderstood and got thrown by how the Service resource worked.

@deanwilson updated so that it hardcodes the home directory.


Ika Review

It appears you cannot post a review for Ika card. My username is Havvy and I believe I have the correct rights to post the review?

Hi there!
(By any chance, are you Ian Witt? I’m in the tournament group!).
I’ve tried this again today and got the following error:
Reviews
An error occured while posting your review (OK). Reload the page and try again.
I noticed there are reviews on this card now, so I suspect it might be just me?
Thanks
Ian
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: x3N1GM4x<EMAIL_ADDRESS>Sent: Monday, December 3, 2018 4:53:26 PM
To: Alsciende/netrunnerdb
Cc: Havvy86; Author
Subject: Re: [Alsciende/netrunnerdb] Ika Review (#250)
Have you been able to post reviews on other cards since you noticed this? Do you get any specific error message or behaviour you can describe (or event better, capture in screenshots) when you attempt to post the review?
I'm not able to reproduce this issue on my local instance, so we're going to need to try and gather some more information to be able to help.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Alsciende/netrunnerdb/issues/250#issuecomment-443782431, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AqfagtP7-P-XbTzDdyqeS09h0lJ03pxqks5u1VcGgaJpZM4X-Jms.

Yes, that's me, hi!
It certainly sounds like something local to your machine or account. Perhaps you could take a look at your web browser's console when you get that error to see if any further detail is being recorded there?
Details on how to do this if you're not aware will vary depending on your browser, there's a summary for the major browsers here. Alternatively, just google "[browser_name] view console" or similar.

See #252 as I assume it's the same and as there I think this is linked to #247

That looks identical with the error message.
Word count is 243 though for my review!
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: 5N00P1<EMAIL_ADDRESS>Sent: Sunday, December 23, 2018 10:10:05 AM
To: Alsciende/netrunnerdb
Cc: Havvy86; Author
Subject: Re: [Alsciende/netrunnerdb] Ika Review (#250)
See #252https://github.com/Alsciende/netrunnerdb/issues/252 as I assume it's the same and as there I think this is linked to #247https://github.com/Alsciende/netrunnerdb/issues/247
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Alsciende/netrunnerdb/issues/250#issuecomment-449626429, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AqfagvbYV4jgD1vc6Rer2qOAhuxw9ONcks5u71Z9gaJpZM4X-Jms.


Improve the generated code for  conditions

Currently pyxl uses a global stack (!) of results from if conditions
to determine whether to execute else branches.
Instead, use if-else to do it in a more natural manner.
Unfortunately, because the parser is structured in a very streaming
manner, we don't know whether an if has an else block until after
fully processing it, so we do some tasteless rewriting of the output
to handle this.
The main purpose of this is to produce better looking code so that we
can compile everything to the target python and throw away the pyxl
codec, but I suppose it also fixes a thread-safety bug and probably
makes things faster too.

Yeah, basically that.


Auto Registration from Attributes

Summary
One more extension method is required to register from attributes instead of registering from namespace.
It might looks like:
services.AddFromAttributes();

And all attribute used classes should be registered.
[RegisterAs(typeof(IMyAwesomeService), ServiceLifetime.Singleton)]
public class MyAwesomeService : ServiceBase, IMyAwesomeService
{
    //...
}

It already exists qith following usage:
services.AddServicesByAttributes();


Initialize optional query parameters with null

Pretty self explanatory, helps with calling APIs with many parameters as you don't have to specify all params.
Considered also initialising with default value but that's more like the value the server assigns when a param is missing so I don't think it's wise to pre-initialize it in the client.

[...] can I ask you to add a test [...] for a call to getSymbolsInParameterName() with no parameters?
done.

@cortinico will you follow-up with merging (and eventually releasing) this?

Let's merge this.
For the releasing part, I'd love to have this into 2.x
I'll have some time during the XMas eve to review/develop all the remaining features for 2.x