Error building binary image, LLVM ERROR

@chengchingwen
Hi Peter,
I am encountering an issue with the DoubleArrayTries.jl package when building my Julia project. Specifically, I am getting an LLVM error related to the X86ISD::PDEP instruction in the succinct.jl file.
Here are the specific error messages I am seeing:
LLVM ERROR: Cannot select: 0x858313e8: i64 = X86ISD::PDEP 0x55ee3040, 0x6dc59ef0, /root/.julia/packages/DoubleArrayTries/C3L0R/src/succinct.jl:24 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/succinct.jl:56 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/succinct.jl:22 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:59 ] ] ]
  0x55ee3040: i64 = X86ISD::CMOV 0x2efc8880, Constant:i64<0>, TargetConstant:i8<3>, 0x85942258:1, int.jl:496 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/succinct.jl:56 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/succinct.jl:22 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:59 ] ] ]
    0x2efc8880: i64 = shl nuw Constant:i64<1>, 0x85942668, int.jl:496 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/succinct.jl:56 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/succinct.jl:22 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:59 ] ] ]
      0x8593de80: i64 = Constant<1>
      0x85942668: i8 = truncate 0x85941b70, int.jl:496 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/succinct.jl:56 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/succinct.jl:22 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:59 ] ] ]
        0x85941b70: i64 = sub 0x8582d010, 0x79a262b8, int.jl:86 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:59 ]
          0x8582d010: i64,ch = CopyFromReg 0x4bfdf28, Register:i64 %16, int.jl:86 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:59 ]
            0x662076c0: i64 = Register %16
          0x79a262b8: i64,ch = CopyFromReg 0x4bfdf28, Register:i64 %10, int.jl:86 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:59 ]
            0x8593e3c8: i64 = Register %10
    0x6dc592c0: i64 = Constant<0>
    0x422037b8: i8 = TargetConstant<3>
    0x85942258: i64,i32 = X86ISD::SUB 0x85941b70, Constant:i64<64>, int.jl:496 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/succinct.jl:56 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/succinct.jl:22 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:59 ] ] ]
      0x85941b70: i64 = sub 0x8582d010, 0x79a262b8, int.jl:86 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:59 ]
        0x8582d010: i64,ch = CopyFromReg 0x4bfdf28, Register:i64 %16, int.jl:86 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:59 ]
          0x662076c0: i64 = Register %16
        0x79a262b8: i64,ch = CopyFromReg 0x4bfdf28, Register:i64 %10, int.jl:86 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:59 ]
          0x8593e3c8: i64 = Register %10
      0x3d5194d0: i64 = Constant<64>
  0x6dc59ef0: i64,ch = load<(load (s64) from %ir.82, !tbaa !26043, addrspace 13)> 0x69611ef0:1, 0x99e5f30, undef:i64, array.jl:924 @[ abstractarray.jl:1244 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:58 ] ]
    0x99e5f30: i64 = add 0x422032d8, 0x38383c88, array.jl:924 @[ abstractarray.jl:1244 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:58 ] ]
      0x422032d8: i64,ch = load<(dereferenceable load (s64) from %ir.80, !tbaa !26035, addrspace 11)> 0x69611ef0:1, 0x69611ef0, undef:i64, array.jl:924 @[ abstractarray.jl:1244 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:58 ] ]
        0x69611ef0: i64,ch = AtomicLoad<(dereferenceable load unordered (s64) from %ir.78, addrspace 11)> 0x31305d70:1, 0x31305d70, Base.jl:38 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:58 ]
          0x31305d70: i64,ch = AtomicLoad<(dereferenceable load unordered (s64) from %ir.76, addrspace 11)> 0x4bfdf28, 0x2786b408, Base.jl:38 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:58 ]
            0x2786b408: i64 = add nuw 0x22ab4450, Constant:i64<8>, Base.jl:38 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:58 ]
              0x22ab4450: i64,ch = CopyFromReg 0x4bfdf28, Register:i64 %15, Base.jl:38 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:58 ]
                0x56898f90: i64 = Register %15
              0x7ca823c8: i64 = Constant<8>
        0x65da2e50: i64 = undef
      0x38383c88: i64 = shl 0x8582a190, Constant:i8<3>, array.jl:924 @[ abstractarray.jl:1244 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:58 ] ]
        0x8582a190: i64 = or 0x65da2be0, 0x70155b90, int.jl:87 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:57 ]
          0x65da2be0: i64 = AssertZext 0x4848c7f0, ValueType:ch:i3, int.jl:87 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:57 ]
            0x4848c7f0: i64,ch = CopyFromReg 0x4bfdf28, Register:i64 %9, int.jl:87 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:57 ]
              0x85aeff50: i64 = Register %9
          0x70155b90: i64 = shl 0x85834130, Constant:i8<3>, int.jl:88 @[ int.jl:991 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:57 ] ]
            0x85834130: i64,ch = CopyFromReg 0x4bfdf28, Register:i64 %5, int.jl:88 @[ int.jl:991 @[ /root/.julia/packages/DoubleArrayTries/C3L0R/src/bvector.jl:57 ] ]
              0xb9a8338: i64 = Register %5
            0x71990e08: i8 = Constant<3>
        0x71990e08: i8 = Constant<3>
    0x65da2e50: i64 = undef
In function: julia_select_134049
signal (6): Aborted
in expression starting at none:0
gsignal at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
abort at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
_ZN4llvm18report_fatal_errorERKNS_5TwineEb at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN4llvm18report_fatal_errorERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEb at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN4llvm16SelectionDAGISel15CannotYetSelectEPNS_6SDNodeE at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN4llvm16SelectionDAGISel16SelectCodeCommonEPNS_6SDNodeEPKhj at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN12_GLOBAL__N_115X86DAGToDAGISel6SelectEPN4llvm6SDNodeE at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN4llvm16SelectionDAGISel22DoInstructionSelectionEv at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN4llvm16SelectionDAGISel17CodeGenAndEmitDAGEv at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN4llvm16SelectionDAGISel20SelectAllBasicBlocksERKNS_8FunctionE at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN4llvm16SelectionDAGISel20runOnMachineFunctionERNS_15MachineFunctionE.part.899 at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN12_GLOBAL__N_115X86DAGToDAGISel20runOnMachineFunctionERN4llvm15MachineFunctionE at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN4llvm19MachineFunctionPass13runOnFunctionERNS_8FunctionE at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN4llvm13FPPassManager13runOnFunctionERNS_8FunctionE at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN4llvm13FPPassManager11runOnModuleERNS_6ModuleE at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
_ZN4llvm6legacy15PassManagerImpl3runERNS_6ModuleE at /usr/local/julia/bin/../lib/julia/libLLVM-13jl.so (unknown line)
operator() at /cache/build/default-amdci4-2/julialang/julia-release-1-dot-8/src/aotcompile.cpp:580 [inlined]
jl_dump_native_impl at /cache/build/default-amdci4-2/julialang/julia-release-1-dot-8/src/aotcompile.cpp:592
jl_write_compiler_output at /cache/build/default-amdci4-2/julialang/julia-release-1-dot-8/src/precompile.c:94
ijl_atexit_hook at /cache/build/default-amdci4-2/julialang/julia-release-1-dot-8/src/init.c:207
jl_repl_entrypoint at /cache/build/default-amdci4-2/julialang/julia-release-1-dot-8/src/jlapi.c:720
main at /cache/build/default-amdci4-2/julialang/julia-release-1-dot-8/cli/loader_exe.c:59
__libc_start_main at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
unknown function (ip: 0x401098)
Allocations: 407042431 (Pool: 406866746; Big: 175685); GC: 137

Do you have any suggestions for how I can resolve this issue or any further troubleshooting steps I can try? I am happy to provide additional information or debug the issue further if needed.
Thank you for your help.
Sincerely,
Maxim

Hi Maxim,
I'm not sure why the error happened. It seems that LLVM does not know how to handle the pdep instruction while the cpu seems to support it. Does DoubleArrayTries.jl runs without error without PackageCompiler.jl? If it's a PackageCompiler-specific error, we should also open an issue there. I'll also see if there are any workaround I can do here.

Hi Peter,
Thank you for your response to my previous message. To provide further context, I have been experiencing issues while trying to build a binary image on AWS. I can confirm that on my local machine, the binary image is built without any issues.
DoubleArrayTries.jl runs without error without PackageCompiler.jl.

If I understand correctly, the error only happened on AWS with PackageCompiler.jl, but on local everything is fine? If so, could you check if the julia/LLVM version on AWS and your local machine are the same? Also, I would like to know if adding try block around those lines or forcing has_bmi2 return false avoiding the error. If these can be done, we can set some extra check or even a preference to turn on/off the pdep implementation.

@chengchingwen
After conducting some experiments, I found that disabling the use of LLVM for pdep leads to a successful build of the binary image. Additionally, I discovered that a try-catch condition for calling pdep via LLVM results in the same error that I described in the issue. julia/LLVM version on AWS is 11.

Can you share a minimal environment setting that could reproduce the error?

I found that disabling the use of LLVM for pdep leads to a successful build of the binary image

Did you do this by commenting out pdep implementation with llvmcall or you force the has_bmi2 return false? If it only works with commenting out pdep with LLVM, then it means we probably couldn't do anything on our side and we should report this error to PackageCompiler.jl

I am continuing my experiments. I've found out that the reason for the llvm error was connected to parameter set during calling of PackageCompiler
PackageCompiler.create_sysimage(
    project_name,
    cpu_target="generic;sandybridge,-xsaveopt,clone_all;haswell,-rdrnd,base(1)",
    sysimage_path = joinpath(sysimage_dir, "image.so"),
    precompile_execution_file = "test/runtests.jl",
)

Removing cpu_target kwarg led to successful binary image build.
As for cpu_target value, it's standard value for the x86 architecture, see here
https://github.com/JuliaLang/PackageCompiler.jl/blob/df3543443b8b5740150e28a5638f7c635c2c61eb/src/PackageCompiler.jl#L3

Can you share a minimal environment setting that could reproduce the error?
project is build in Docker on AWS t3 instance using CentOS 7.9.2009 x86_64

Did you do this by commenting out pdep implementation with llvmcall or you force the has_bmi2 return false?
It worked either by setting has_bmi2 to false or by completely commenting out llvm implementation of pdep. Adding try-catch around llvm implementation of pdep led to the error.

So, summarizing all of the above, I suppose, it's PackageCompiler issue.

Hello, looks like we have some idea what is going on.
The concern is about LLVM and a minimal processor family provided by the argument cpu_target="generic;sandybridge,-xsaveopt,clone_all;haswell,-rdrnd,base(1)". If we have a case of running LLVM with sandybridge target, definitely bmi2 is not supported. Right now we have a build agent VM with Skylake family and Intel(R) Xeon(R) Platinum 8259CL CPU. If we do not specify cpu_target, the PackageCompiler works without issues.
In the https://docs.julialang.org/en/v1/devdocs/sysimg/#Specifying-multiple-system-image-targets the only recommendation about cpu_target is present. Unfortunately even https://github.com/JuliaLang/julia/blob/0f5f62cf5a31b4a973ab0fae70988e35e2ea8da7/src/processor_x86.cpp#L196 doesn't answer how to specify haswell or broadwell as the minimal and the only required CPU family.
@KristofferC we need your help.
We cannot avoid use of cpu_target - we are using Docker images created inside an AWS VM with further deployment into an AWS cluster. Due to the use of virtual machines, we cannot guarantee a certain generation of physical CPUs. Sometimes, when we are building a Docker image, the build agent VM has a newer processor family than a Kubernetes cluster. After that, the error "unsupported processor type" appeared on deploy stage. When we have cpu_target hard restricted to the processor family, that is never happening.

https://github.com/chengchingwen/DoubleArrayTries.jl/blob/main/src/succinct.jl#L21
@static if has_bmi2()
    select_in_word(x, k) = pdep_select_in_word(x, k)
    pdep(x::UInt32, y::UInt32) = ccall("llvm.x86.bmi.pdep.32", llvmcall, UInt32, (UInt32, UInt32), x, y)
    pdep(x::UInt64, y::UInt64) = ccall("llvm.x86.bmi.pdep.64", llvmcall, UInt64, (UInt64, UInt64), x, y)
else
    select_in_word(x, k) = tabled_select_in_word(x, k)
    pdep(x::T, y::T) where {T <: Union{UInt32, UInt64}} = _pdep(x, y)
end

@MNLubov @rssdev10
Could you try using this branch and call DoubleArrayTries.set_native_pdep_support(false) to disable the pdep implementation with llvmcall and see if this work for you?

@chengchingwen
Disabling  llvm implementation of the pdep with DoubleArrayTries.set_native_pdep_support(false) works. Thank you!


Potential memory leak

With only the @google-cloud/[...] suite for traffic, google-cloud/common grew from 2.43MB to 7.30MB in the span of 2 hours, taking at first 3.21% of the heap to 8.99%. It later kept growing and never released its memory.
Environment details

OS: Ubuntu (App Engine flex)
Node.js version: 14.16.0
npm version: 6.14.13
@google-cloud/common version: 3.4.1

Heap at start:

Heap 2 hours later:

Transcript:
(anonymous<EMAIL_ADDRESS>onAuthenticated<EMAIL_ADDRESS>makeRequest<EMAIL_ADDRESS>retryRequest: /app/node_modules/retry-request/index.js
makeRequest: /app/node_modules/retry-request/index.js
(anonymous): /app/node_modules/teeny-request/build/src/index.js
teenyRequest: /app/node_modules/teeny-request/build/src/index.js
nodeFetch: ...

We are using:
@google-cloud/debug-agent: 5.1.2
@google-cloud/text-to-speech: 3.1.1
@google-cloud/trace-agent: 5.1.1
Linked to https://github.com/googleapis/cloud-debug-nodejs/issues/811

Hi @alexnault! Do you have any code we could use to reproduce?

Hi @stephenplusplus! No unfortunately since it's running closed source. But I am guessing a simple Node process with the following should trigger the issue:
require('@google-cloud/trace-agent').start();
require('@google-cloud/debug-agent').start();
require('@google-cloud/profiler').start();

// Start HTTP server or w/e...

@alexnault Thanks for the report. Few questions:

What do you do in your HTTP server?
Do you also use other Google client library?
Can you share other libraries you're using if possible?
Does it only happen with those 2 agents and the profiler enabled?

Thanks in advance

One thing to look for - there's a known leak in the debug agent:
https://github.com/googleapis/cloud-debug-nodejs/issues/811

@tmatsuo

What do you do in your HTTP server?

It's mostly a CRUD app. But as I mentioned, our server was idle with no user traffic in a staging env.

Do you also use other Google client library?

We use googleapis for its Calendar API, but again, we were not making calls in this scenario.

Can you share other libraries you're using if possible?

Without sharing the specifics, we are running a express server with redis acting as session management, sequelize as ORM and pg as database driver.

Does it only happen with those 2 agents and the profiler enabled?

Yes
@JustinBeckwith Yes, I've already linked it in my original post.

I've let the server run all weekend; onAuthenticated from google-cloud/common is now taking 103MB.

Thanks @alexnault @JustinBeckwith
There is a known memory leak in the debug agent. Is this bug considered a separate bug? Can we mark this as a duplicate?

@tmatsuo The heap snapshots make me feel like the issue is coming from google-cloud/common. But I might be wrong.
Either way, we've removed all our google-cloud/[...] dependencies and the memory leak is now gone:

@alexnault was there a specific operation we can test that consistently lead to the memory leak? Did you test any of the dependencies that rely on google-cloud/common in isolation?

Worth noting I'm testing with<EMAIL_ADDRESS>is there a chance a memory leak was patched in the interim?


[BUG] - NavBar is not working

NextUI Version
2.4.2
Describe the bug
Error: Objects are not valid as a React child (found: object with keys {$$typeof, type, key, props, _owner, _store}). If you meant to render a collection of children, use an array instead.
Your Example Website or App

const jost = Jost({ subsets: ['latin'] })

export default function RootLayout({
  children,
}: {
  children: React.ReactNode;
}) {
  return (
    <html lang="en" className={jost.className}>
      <head>
      </head>
        <body>
          <NextUiProvider>
              <Header />
          </NextUiProvider>
          <Toaster position="top-center" expand={true} />
        </body>
    </html>
  );
}

'use client';
import React from "react";
import {Navbar, NavbarBrand, NavbarContent, NavbarItem, Link, Button} from "@nextui-org/react";
// import {AcmeLogo} from "./AcmeLogo.jsx";

export default function Header() {
  return (
    <Navbar position="static">
      <NavbarContent className="hidden sm:flex gap-4" justify="center">
        <NavbarItem>
          <Link color="foreground" href="#">
            Features
          </Link>
        </NavbarItem>
        <NavbarItem isActive>
          <Link href="#" aria-current="page">
            Customers
          </Link>
        </NavbarItem>
        <NavbarItem>
          <Link color="foreground" href="#">
            Integrations
          </Link>
        </NavbarItem>
      </NavbarContent>
      <NavbarContent justify="end">
        <NavbarItem className="hidden lg:flex">
          <Link href="#">Login</Link>
        </NavbarItem>
        <NavbarItem>
          <Button as={Link} color="primary" href="#" variant="flat">
            Sign Up
          </Button>
        </NavbarItem>
      </NavbarContent>
    </Navbar>
  );
}

Steps to Reproduce the Bug or Issue
I have tried 2.4.1 and 2.4.2 but the same problem.
Also tried nexui Navbar example.
same code i have used in another project its working fine.
Expected behavior
Error: Objects are not valid as a React child (found: object with keys {$$typeof, type, key, props, _owner, _store}). If you meant to render a collection of children, use an array instead.

Screenshots or Videos
No response
Operating System Version
windows
Browser
Chrome

We don't support next.js 15.0.0-rc.0 since it is using React 19 which most of our dependencies are not supporting yet. Please use v14 instead.

same issue here, still no support for react 19?

same issue here, still no support for react 19?

Downgrade the React version, it should work.

Nope. Current version doesn't support.


Add: Capacity Reservations

Overview/Summary
Reserving compute capacity reservations should be considered with critical workloads, especially in Azure regions that are capacity constrained.

Related Issues/Work Items
AB#35813
Breaking Changes
N/A
As part of this pull request I have

[x] Read the Contribution Guide and ensured this PR is compliant with the guide
[x] Checked for duplicate Pull Requests
[x] Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Ensured PR tests are passing
[x] Performed testing and provided evidence (e.g. screenshot of output) for any changes associated to ARG queries
[ ] Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

Thank you @tksh164 for your suggestions. I've committed them to the PR.


cargo rustc --target behavior is different to rustc --target

Problem
I'm using CLion which fetches target information with this command:
cargo rustc -Z unstable-options --target /home/tmvkrpxl0/linux/scripts/target.json --print cfg

However it says it's invalid target, while running same command without cargo works.
Steps

Run RUSTC_BOOTSTRAP=1 cargo rustc -Z unstable-options --target <custom_target_json> --print cfg which fails
Run RUSTC_BOOTSTRAP=1 rustc -Z unstable-options --target <custom_target_json> --print cfg which succeed

Possible Solution(s)
No response
Notes
rustc 1.73.0 (cc66ad468 2023-10-03)
Version
cargo 1.73.0 (9c4383fb5 2023-08-26)
release: 1.73.0
commit-hash: 9c4383fb55986096b414d98125421ab87b5fd642
commit-date: 2023-08-26
host: x86_64-unknown-linux-gnu
libgit2: 1.6.4 (sys:0.17.2 vendored)
libcurl: 8.2.1-DEV (sys:0.4.65+curl-8.2.1 vendored ssl:OpenSSL/1.1.1u)
ssl: OpenSSL 1.1.1u  30 May 2023
os: Linux 22.04 (jammy) [64-bit]

@epage  I can, but setting it up will take ages, I'm building linux kernel module and you need to compile whole kernel.
https://codeberg.org/tmvkrpxl0/tefexia
Instead you can just try target.json
target.json

❯ RUSTC_BOOTSTRAP=1 cargo rustc -Z unstable-options --target /home/tmvkrpxl0/linux/scripts/target.json --print cfg
error: Error loading target specification: Could not find specification for target "target". Run `rustc --print target-list` for a list of built-in targets

error: process didn't exit successfully: `/home/tmvkrpxl0/.cargo/bin/sccache /home/tmvkrpxl0/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc -L /lib/modules/6.6.0-rc4-kindergarten+/build/rust -Zbinary_dep_depinfo=y -Cembed-bitcode=n -Zfunction-sections=n -Cforce-unwind-tables=n -Csymbol-mangling-version=v0 -Crelocation-model=static -Ctarget-feature=-sse,-sse2,-sse3,-ssse3,-sse4.1,-sse4.2,-avx,-avx2 -Ztune-cpu=generic -Cno-redzone=y -Ccode-model=kernel -Cforce-frame-pointers=y --emit=dep-info=./.tefexia.o.d --emit=obj=./tefexia.o --cfg MODULE --target target --print cfg` (exit status: 1)

Instead you can just try target.json target.json

Tried the target.json file you provided with both rustc and cargo printing cfg. Both of the commands succeeded without any error. I am not what happened to you :(
Just noticed that you have /home/tmvkrpxl0/.cargo/bin/sccache as a rustc wrapper. I don't think that would be an issue but could you try removing the setting?

Going to close due to inactivity. Feel free to reopen if you have a chance to provide more info.


feat(asset-service): regenerate asset data

Current dependencies on/for this PR:

main

PR #1188   👈

This comment was auto-generated by Graphite.


fetch-client 1.8.0 breaks my build

After upgrading aurelia-fetch-client in one of my apps from 1.7.0 to 1.8.0 the build started breaking with the following error:
../../node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(310,2): error TS2416: Property 'response' in type 'RetryInterceptor' is not assignable to the same property in base type 'Interceptor'.
  Type '(response: Response, request: Request) => Response' is not assignable to type '(response: Response, request?: Request | undefined) => Response | Promise<Response>'.
    Types of parameters 'request' and 'request' are incompatible.
      Type 'Request | undefined' is not assignable to type 'Request'.
        Type 'undefined' is not assignable to type 'Request'.
../../node_modules/aurelia-fetch-client/dist/aurelia-fetch-client.d.ts(311,2): error TS2416: Property 'responseError' in type 'RetryInterceptor' is not assignable to the same property in base type 'Interceptor'.
  Type '(error: Response, request: Request, httpClient: HttpClient) => Promise<Response>' is not assignable to type '(error: any, request?: Request | undefined, httpClient?: HttpClient | undefined) => Response | Promise<Response>'.
    Types of parameters 'request' and 'request' are incompatible.
      Type 'Request | undefined' is not assignable to type 'Request'.
        Type 'undefined' is not assignable to type 'Request'.

This PR changes RetryInterceptor so it conforms to the Interceptor interface.

LGTM @EisenbergEffect  (-:


Cluster does not startup on vagrant

When I try to start the mattermost cluster on vagrant as described in the quickstart docs, the operation will fail like this:
node-1: Wed Dec 19 12:59:16 UTC	Wait for system services to start on all nodes
node-1: Wed Dec 19 13:07:39 UTC	Operation failure: planet is not running yet: &{Degraded [{ <IP_ADDRESS> master  degraded [kube-apiserver (Get https://<IP_ADDRESS>/api/v1/componentstatuses/scheduler: dial tcp <IP_ADDRESS>:443: connect: connection refused)]}]}
node-1: Wed Dec 19 13:07:39 UTC	Installation failed in 9m35.590975162s, check /var/log/telekube-install.log for details

Any hints where to search? I've attached the logfile.

Hi @nbyl, sorry for the delay, but better late than never!
It looks like the master server couldn't connect, this could be connectivity issue between the masters nodes and the clients.  You can use gravity status to get an overview of how the cluster is working.
Wed Dec 19 13:07:39 UTC [ERROR] [node-1] Phase /wait execution failed: planet is not running yet: &{Degraded [{ <IP_ADDRESS> master  degraded [kube-apiserver (Get https://<IP_ADDRESS>/```


Sync eng/common directory with azure-sdk-tools for PR 9177

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/9177  See eng/common workflow

PR is unrelated to change. Merging manually.

/check-enforcer override


Direct resource set no longer requires test

PR Summary

Better error message when using set and no input is provided
Make dsc resource set no longer tries a test before
Rename preTest to implementsPretest to make it more clear it's the resource implementing it or not

PR Context
Some usability issues identified when @mgreenegit was writing a bash resource example

Thinking about preTest default value - existing community modules do not implement preTest in most resources - should we align to that as a majority or can we set the default in the schema for a built-in manifest that adapts to those?

In my interaction with the existing preTest, I had to use false because I had not explicitly implemented Test. So should it just be “implementsTest”?

@mgreenegit the implementsPretest is an optimization where if true (default is false) then don't even try to execute test (if implemented or synthesize it if not).  implementsPretest = true means "don't bother checking if already in desired state, call set anyways"

@SteveL-MSFT - I think I mostly agree with this, with the exception that it should be possible to indicate that I want the test operation to be carried out before set. This is important for resources that rely on DSC's synthetic testing imo, and mostly for interactive/script usage. Without this option, I have to do something like:
$Settings = @{ foo = 'bar' } | ConvertTo-Json
$Result = $Settings | dsc resource test --resource My/Resource
if (-not $Result.inDesiredState) {
  $Result = $Settings | dsc resource set --resource My/Resource
  if ($LastExitCode -ne 0) {
    # Handle error
  }
}
# Continue processing

With a --preTest flag (or whatever), I could do:
$Settings = @{ foo = 'bar' } | ConvertTo-Json
$Result = $Settings | dsc resource set --resource My/Resource --preTest
if ($LastExitCode -ne 0) {
  # Handle error
}
# Continue processing

Regarding the schema update/rename, can we mark preTest as a deprecated value that has been renamed, but still handle it in this release? I can adjust the published schemas to that effect (we can define a deprecation message in the VS Code schema to indicate they should rename the value). We might want to consider this sort of model and how we want to go about schema modifications now, while usage and impact are still low to feel out what the best practice will be in the long run.

I agree with @michaeltlombardi that it should be possible for test to run before the set, but wouldn't it also be preferred to indicate what properties that are not in desired state too from test so that can be passed into set? That way set knows what properties it actually need to set. Please correct me if that is already possible (not been able to keep up to speed with DSC v3 just yet), and it might be out of scope here. 🙂

@mgreenegit the implementsPretest is an optimization where if true (default is false) then don't even try to execute test (if implemented or synthesize it if not). implementsPretest = true means "don't bother checking if already in desired state, call set anyways"

This makes sense. My suggestion is, if the manifest does not contain a Test section, the correct value for implementsPreTest is always going to be True, but we default to False which creates a "broken by default" edge case.

@mgreenegit Set and Test are intended to be independent.  I would expect any resource that implements Test to internally use it for Set, but maybe they decided not to do that.  In this case, the logic is:

Is implementsPretest == true?  If so, DSC just calls set directly
if not set or false, then does the resource implement test, if so, call that and if it fails (not in desired state), call set
if test is not implemented, perform a get and compare to desired state input (synthetic test), if nto in desired state, call set

I don't think we can assume that because test is implemented, it means set internally does a test first.
I think adding a --pretest switch to set operation makes sense.  However, I think that should be a separate PR after this one is merged as this issue is hitting folks.

@michaeltlombardi schema changes during alpha are inevitable.  Maybe we just need to call them out in the changelog?


[TB] Component popups are not rendered correctly in dark mode

Problem/Concern
Under the components page, the dark mode switch sets the right editor container to darkmode.  This works correctly for all components except for those with popups.  For these popups, the component is added to a div on body, instead of the container that the popup was defined.
Proposed Solution

This has been fixed for popover.
It still isn't working for tooltips.


CV2-5011 refactors for making alegre dual purpose on text encoding

Description
Minor tweak identified when running text encodings.
Reference: CV2-5011
How has this been tested?
Tested locally and confirmed to work
Are there any external dependencies?
Changes no dependencies
Have you considered secure coding practices when writing this code?
Does not alter security posture.

Sorry, I'm not familiarized with this code - but, does this change in the return require any change on Alegre side?

It does not - the only thing that's happening here is basically updating vectorizers to return what is now the current specification for how responses from fingerprinters should look - this one got out of sync since we hadn't been using it for anything. Mostly just tagging you here for visibility so you can be aware of the magnitude of changes across each repo, don't worry too much about the specifics in this repo!

the only thing that's happening here is basically updating vectorizers to return what is now the current specification for how responses from fingerprinters should look - this one got out of sync since we hadn't been using it for anything.

I'm not very clear how the output changed, but it looks like it will handle caching better? Is the current specification somewhere I can check if it matches? I'm just assuming it works because you said you tested it locally

That's basically it @skyemeedan - the function calling the fingerprinting function expects a slightly different response. Once we have the fixes from @ashkankzme on the PR he's working on it should be a bit easier to highlight conceptual float like this case.


Properties missing from stringify options parameter

Describe the bug
The type of the stringify options parameter is missing properties like lineWidth as documented at https://eemeli.org/yaml/#tostring-options and also suggested at https://github.com/eemeli/yaml/issues/58#issuecomment-799334277.
To Reproduce
YAML.stringify({ abc: 'def' }, { lineWidth: 120 });

shows a TypeScript error with lineWidth does not exist in type Options.
Expected behaviour
All documented option properties are working as expected in TypeScript (I'm not sure if only the type is incorrect or the implementation as well).
Versions (please complete the following information):

Environment: Node.js 20.14
yaml: 2.6.1

Additional context
I've declared YAML as a global variable via a .d.ts file, but the error also shows up, if I import the yaml module via import YAML from 'yaml'.

Please check and confirm your yaml version, Options has not been used as a type for a while now.

To be specific, that type only showed up in exactly one prerelease version: 2.0.0-4.

Thanks @eemeli for the very fast response and for pointing me in the right direction!
I'm actually an idiot... my package.json had a resolution pointing yaml to v1.10.2. Works as expected after removing that resolution.


Add Gen2 Class Saver (JPEG)

Gen2 Class Saver (JPEG)
This example demonstrates how to run MobilenetSSD and collect images of detected objects, grouped by detection label.
After running this script, DepthAI will start MobilenetSSD, and whenever it detects objects, it will add a dataset entry
Dataset is stored under data directory, and a main dataset file is located under data.dataset.csv.
For each detected object, a new dataset entry is created, with each entry having files with a precise purpose:

timestamp uses int(time.time() * 10000) to store a timestamp of the capture. Please note that this value can be duplicated, if multiple objects are detected on a single image

label is a human-readable label of the detected object

left, top, right, top are object bounding box coordinates

raw_frame represents a path to raw RGB frame captured on DepthAI when detection occured

overlay_frame represents a path to RGB frame with detection overlays (bounding box and label)

cropped_frame represents a path to cropped RGB frame containing only ROI of the detected object

An example entries in dataset.csv are shown below
timestamp,label,left,top,right,bottom,raw_frame,overlay_frame,cropped_frame
16125187249289,bottle,0,126,79,300,data/raw/16125187249289.jpg,data/bottle/16125187249289_overlay.jpg,data/bottle/16125187249289_cropped.jpg
16125187249289,person,71,37,300,297,data/raw/16125187249289.jpg,data/person/16125187249289_overlay.jpg,data/person/16125187249289_cropped.jpg
16125187249653,bottle,0,126,79,300,data/raw/16125187249653.jpg,data/bottle/16125187249653_overlay.jpg,data/bottle/16125187249653_cropped.jpg
16125187249653,person,71,36,300,297,data/raw/16125187249653.jpg,data/person/16125187249653_overlay.jpg,data/person/16125187249653_cropped.jpg
16125187249992,bottle,0,126,80,300,data/raw/16125187249992.jpg,data/bottle/16125187249992_overlay.jpg,data/bottle/16125187249992_cropped.jpg
16125187249992,person,71,37,300,297,data/raw/16125187249992.jpg,data/person/16125187249992_overlay.jpg,data/person/16125187249992_cropped.jpg
16125187250374,person,37,38,300,299,data/raw/16125187250374.jpg,data/person/16125187250374_overlay.jpg,data/person/16125187250374_cropped.jpg
16125187250769,bottle,0,126,79,300,data/raw/16125187250769.jpg,data/bottle/16125187250769_overlay.jpg,data/bottle/16125187250769_cropped.jpg
16125187250769,person,71,36,299,297,data/raw/16125187250769.jpg,data/person/16125187250769_overlay.jpg,data/person/16125187250769_cropped.jpg
16125187251120,bottle,0,126,80,300,data/raw/16125187251120.jpg,data/bottle/16125187251120_overlay.jpg,data/bottle/16125187251120_cropped.jpg
16125187251120,person,77,37,300,298,data/raw/16125187251120.jpg,data/person/16125187251120_overlay.jpg,data/person/16125187251120_cropped.jpg
16125187251492,bottle,0,126,79,300,data/raw/16125187251492.jpg,data/bottle/16125187251492_overlay.jpg,data/bottle/16125187251492_cropped.jpg
16125187251492,person,74,38,300,297,data/raw/16125187251492.jpg,data/person/16125187251492_overlay.jpg,data/person/16125187251492_cropped.jpg

Demo

Side note:
I was wondering if I should record the demo video with a some lamps turned on, but I think this also shows that detection in fairly low-light levels is possible. Any thoughts?

Sometimes the issue is really simple, haha. Detection threshold should do the work

Thanks.  Did that fix it?

Will try it today

Great thanks!

So, I was trying the fix right now. Seems that the confidence threshold is already implemented, and it is filtering objects detected below 50% threshold

Thanks.  So maybe would it be a good idea to do one of two, or perhaps both things:

Make a system where there's a threshold of how many frames the object class has to be present consecutively for the JPEG to be saved.
Increase the min threshold to something like 75%, so that there's less chance of just little blips resulting in a saved JPEG.

Thoughts?
Thanks,
Brandon

Seems like a good idea. Will try a few of them, and let's see what's best

Great thanks!


WIP: Fix use of the macOS SDK

Changes in  this PR:

Force conda-build to use a shorter install prefix (exposes PCH relocation bugs).
Remove clangdev from the run time dependencies.
[osx] Make the shell error message clearer if CONDA_BUILD_SYSROOT isn't set.
[osx] Prevent cling from adding the macOS SDK path to libCling. (a5ef92b)
[osx] Distribute etc/allDict.cxx.pch as it can't be generated without a working compiler.
[osx] Disable prefix replacement for etc/allDict.cxx.pch as both text and binary mode fail. I think the only effect is causing error messages to the wrong paths (as in LCG).

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I should be able to start helping again tomorrow.

I've added a description of what I've changed. I've also removed the changes to SDKROOT as I think they aren't needed.
If the latest commit passes I think it's ready to merge.

Okay, looks like a good solution.

As it will take a long time to deploy and the current version is broken I'm going to merge this so there is a (hopefully) working package in the morning.


Convert timestamps from UTC?

We are showing timestamp as computed by fractal-server, that is, in UTC.
I'd say we should convert them to the browser local timezone, to avoid confusion for the user.

I actually noticed that this is in principle already covered in src/lib/components/jobs/TimestampBadge.svelte:
<script>
	export let timestamp;
</script>

<span>
	{timestamp ? new Date(timestamp).toLocaleString() : 'No timestamp'}
</span>

Maybe the glitch is due to a wrong configuration of my browser/OS timezone. I'll check further.

@tcompa I just tested this on my end and the timestamps in the project page are showing the correct local time :) Are there other time stamps that should be checked?

@tcompa I just tested this on my end and the timestamps in the project page are showing the correct local time :) Are there other time stamps that should be checked?

Thanks, then it should be a glitch on my side.
There are timestamps associated to:

Jobs (in any job-list page)
Task-collection (in the main tasks page)

Hmm, it's different for me depending on the deployment. On the FMI deployment, the correct time is shown on the job pages. For a local deployment, I get UTC time shown (both on the job page and the task collection), even though my computer is running on UTC + 2h.

toLocaleString() is not working as expected because the date returned by fractal-sever doesn't follow ISO 8601 standard, which requires to put a Z at the end of the string to represent a date in UTC. I think we should fix this on fractal-server side.
On my browser:
new Date('2023-12-20T09:49:27.914030').toLocaleString() // "12/20/2023, 9:49:27 AM"
new Date('2023-12-20T09:49:27.914030Z').toLocaleString() // "12/20/2023, 10:49:27 AM"

Does the snippet above correspond to the time strings that you are actually getting from fractal-server?

Yes, the first string included in the snippet is the actual fractal-server response.

we would expect e.g. that a GET-job endpoint response includes this sort of property:
            'start_timestamp': '2023-12-20T15:13:16.457723+00:00',

(this still has +00:00 rather than Z, but at least it is time-zone-aware)

Also this version seems to work fine:
new Date('2023-12-20T15:13:16.457723+00:00').toLocaleString() // 12/20/2023, 4:13:16 PM

Closing this issue, as it's addressed in

#400
https://github.com/fractal-analytics-platform/fractal-server/pull/1186

For the record,

Hmm, it's different for me depending on the deployment. On the FMI deployment, the correct time is shown on the job pages. For a local deployment, I get UTC time shown (both on the job page and the task collection), even though my computer is running on UTC + 2h.

The likely reason for this behavior was that the local deployment was based on sqlite (I guess). In that case, even without fully reproducing the issue, it is definitely expected that fractal-server < 1.4.3 was not providing a correct handling of timezones.

That makes sense, thanks!


Add ValueStore.ReadManyValues()

The more code can use GetMany(), the better performance gets on top of
NBS. To this end, add a call to ValueStore that allows code to read
many values concurrently. This can be used e.g. by read-ahead code
that's navigating prolly trees to increase performance.
Fixes #3019

PTAL


Added Android support

Hi Alexander,
Thanks for creating this project, It is of great help and makes it very easy to translate a react-native app. We wanted to translate Android the same way, so I decided today adding Android support.
This PR tackles #6 adding java code for bridging current locale in an Android device to javascript. Beware that Android communicates values to javascript through callbacks or events emitted, this means communication is asynchronous.
This is my first bridge for react-native and what this means is that first render might be done with default language and for the next one the local would be already read, so interface changes, sort of flickering.
There has to be a way to come around this, but I'm currently not sure if there is one without locking. I've decided to post my progress, maybe someone can shed some light.
Let me know your thoughts, thanks.
Cheers,
Miguel

hi just question how you integrate this module

Hi @Iragne I've just updated the README, totally forgot to add this section, thanks.

Hey @maraujop, thanks for contributing and sorry for the delay. Can you confirm your code works for Android devices right now?

Hi thanks ;)

Hi @AlexanderZaytsev. Are you planing to merge this pull request soon? I am very interested in using react-native-i18n for Android too. Thanks!

@andreipt I'd love to merge it, however I can't check if this PR works with Android as is right now. If someone can confirm it works, I'll merge it.

@AlexanderZaytsev, @maraujop: I just tested this PR and I can confirm it works as expected on Android.

Sorry for taking so long to answer @AlexanderZaytsev . We are currently using this as it is in a product we are developing without issues, besides the async part I mentioned in my first message, which I'm not sure if it's fixable.
Thanks, cheers
Miguel

Merged and released 0.0.7. Thanks!


Bump karma from 3.0.0 to 6.3.16 in /python/jupyter

What do these changes do?

Fix dependabot alert in npm package
Remove zookeeper dependency in analytical engine

Related issue number

Fixes

Codecov Report

Merging #1694 (b85f348) into main (10b231f) will decrease coverage by 8.90%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1694      +/-   ##
==========================================
- Coverage   44.00%   35.09%   -8.91%
==========================================
  Files          89       89
  Lines        9761     9761
==========================================
- Hits         4295     3426     -869
- Misses       5466     6335     +869

Impacted Files
Coverage Δ

...aphscope/tests/kubernetes/test_resource_builder.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...on/graphscope/tests/kubernetes/test_demo_script.py
0.00% <0.00%> (-91.75%)
:arrow_down:

python/graphscope/deploy/kubernetes/utils.py
11.90% <0.00%> (-58.58%)
:arrow_down:

python/graphscope/deploy/kubernetes/cluster.py
23.55% <0.00%> (-50.20%)
:arrow_down:

...thon/graphscope/tests/kubernetes/test_with_mars.py
0.00% <0.00%> (-44.83%)
:arrow_down:

python/graphscope/interactive/query.py
41.12% <0.00%> (-38.71%)
:arrow_down:

python/graphscope/dataset/ldbc.py
35.29% <0.00%> (-35.30%)
:arrow_down:

python/graphscope/dataset/modern_graph.py
35.29% <0.00%> (-35.30%)
:arrow_down:

python/graphscope/client/archive.py
35.84% <0.00%> (-28.31%)
:arrow_down:

...n/graphscope/deploy/kubernetes/resource_builder.py
30.59% <0.00%> (-25.95%)
:arrow_down:

... and 13 more

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 10b231f...b85f348. Read the comment docs.


Support SecurityContext for admission controller

Some clusters have strict policies on what pods can run as root, etc. Supporting security context as part of the admission controllers deployment spec would be great!

Closing as the PR has been merged.


ord_info

@Arturstrag could you install linter in your environment (flake8 preferred): https://code.visualstudio.com/docs/python/linting and make flake8 tests green (approved)? Then I will check the code.


Add tests to Function class

Codecov Report

Merging #16 into dev will increase coverage by 24.63%.
The diff coverage is 88.88%.

@@             Coverage Diff             @@
##              dev      #16       +/-   ##
===========================================
+ Coverage   48.60%   73.24%   +24.63%
===========================================
  Files          11       11
  Lines         358      370       +12
===========================================
+ Hits          174      271       +97
+ Misses        184       99       -85

Impacted Files
Coverage Δ

src/peon/project/file/function_def/function.py
94.40% <88.37%> (+75.81%)
:arrow_up:

src/peon/project/file/class_def/classes.py
97.05% <100.00%> (ø)

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 44b5ce5...ccdc266. Read the comment docs.


How to hide toolbar in the left?

Is there a command to hide toolbar?

@leaxoy What toolbar do you mean? (A screenshot would help)

#1105


[Network] Upgrade network sdk

Upgrade network sdk to fix type error.

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/jsntcy/azure-cli-extensions.git@rtv3-fix#subdirectory=src/$EXT&egg=$EXT"

add to S172


Player feet either clip through floor, or floating

When my character does not have any weapons drawn, her feet clip through the floor, sometimes all the way up to the ankles/lower calves. When she has a weapon drawn, her feet float several inches above the floor. Is there a way to fix this?

Only way to really tell is to test various areas, I know slopey areas can cause it and I have seen it myself when I was playing skyrim a couple of weeks ago some of the ground meshes wasn't working correctly it seemed.
You can enabled headbob on the various actions but it is best to turn on smooth animation transitions when you do this otherwise the camera will act snappy, there is a downside you'll get slight inertia.
What race are you using?

Imperial. I am in Clockwork Castle, which is an area added by a mod, so perhaps that has something to do with it?

Could be best bet is to teleport around various areas using the console, coc LOCATION, for example coc Riverwood.
Just make sure you hard save inside the area your at incase the game tries saving when your using the coc command.

Confirmed that it was Clockwork Castle. No issues in original Skyrim cells, or in Falskaar cells for that matter.


⚠ Bofrost.de has degraded performance

In 2b344c3, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1719 ms

Resolved: Bofrost.de performance has improved in b84fec3 after 8 minutes.


Prologue and epilogue scripts on remote machine

Is it possible to run setup/teardown scripts on the remote machine when using JobScript with SSH?
I need to source a script on the remote that sets up the LSF environment before it will let me use bsub.

There is, indirectly, but only by defining a custom backend. Basically, you would have to subclass LsfBackend and overwrite all the cmd_ methods.
For example,
class MyCustomLsfBackend(LsfBackend)

    def cmd_submit(self, jobscript):
        return 'my_bsub_wrapper.sh "%s"' % jobscript.filename

You would then put the script my_bsub_wrapper.sh somewhere in your $PATH on the cluster login node. It would contains whatever you need to do to actually submit to the scheduler (i.e., source your setup script and then call bsub). You'll have to register MyCustomLsfBackend with JobScript.register_backend before using it. Sorry I haven't gotten around to writing the section on custom backends yet, but I hope you get the idea.
Does that solve your problem?

Hi, sorry for the delay, I went on leave for a few weeks and have only just come back to this.
That's really helpful, thank you. In the end I've "simplified" things by moving my pipeline off my laptop and onto a server that can bsub in it's own right, which is probably better in the long term. It's very helpful however to have the solution available; many thanks.


videogular freezing in IE 11

When trying to play a video using videogular in IE 11, the player immediately freezes without throwing any errors.
The same videos work in Chrome, Safari, and Firefox.
UPDATE: I have narrowed it down my issue to two potential causes. First off, it's worth noting that the freezing issue only happens in a machine running Windows 7 (potentially 8.1 as well). The two issues I've narrowed it down to could be the following:

A CORS issue, as when I access the console in IE 11 I get error codes SEC7119 and SEC7118 both relating to requiring CORS, and CORS preflight.

An issue with Dash using btoa and atob declarations that break implementations of other libraries. The issue might be fixed with a dash.js update, but it has not been pushed as a stable release yet.

Dash playback won't work on the Win7 flavor of IE11 as the media source extensions feature is not provided. It's only in the Win8+ flavors.

I had to remove vg-buffering to get video to work in IE11.


add the option to play a vbr or cbr stream by default

add the option to play a vbr or cbr stream by default

There's no VBR/CBR stream in Netflix , only Main or High profile.


externpro 23.01

use externpro 23.01 release https://github.com/smanders/externpro/releases/tag/23.01

completed with commit to dev branch referenced above


Minor fixes for a working 1.0.0 release

Are you going to make the release on GitHub or should I do that?

Done! https://github.com/ritiek/spotify-downloader/tree/v1.0.0
I wasn't sure about the description though, feel free to edit. Normally we should have the latest changes and new features listed there, but that's a little too much to write for a fist real release... :wink:

Yep, let's leave it like that this release and have a changelog from every next release. Good job!


Building service with size-optimizations garbles memory

The size optimization flags -Os and -Oz flags causes aligniment errors (or something) when building the service.

Building os.a with these flags is fine, as long as the service is built without them
Building test_service.o with these flags causes crazy behavior:

TCP object is suddenly in the wrong address, causing map emplacement to take forever etc.

Thoughts:

Gnu ld doesn't play well with clang's size optimization?
I noticed that compiling with -flto causes ld to say "unrecognized file format". Related?

Was this fixed with explicit stack-realignment?

Stripped worked for me on my laptop

Can't reproduce this anymore, in any VMM with any combination of stripped and non-stripped service/kernel


drag-core.DragDropManager is undefined.

Describe the bug
I got a DragDropManager undefined error here. I thought it's maybe because I load the module twice.

DragDropContext.js?2a2f:52 Uncaught (in promise) TypeError: _dndCore.DragDropManager is not a constructor
    at createChildContext (DragDropContext.js?2a2f:52)
    at DragDropContext (DragDropContext.js?2a2f:70)
    at eval (dragFieldsIndex.js?4fd9:488)
    at Object../src/platform/bill/billView/dragFieldsIndex.js (eval at exec (index.js?635a:268), <anonymous>:389:1)
    at __webpack_require__ (eval at exec (index.js?635a:268), <anonymous>:85:30)
    at eval (conditionSettingModal.js:15)
    at Object../src/platform/bill/billView/conditionSettingModal.js (eval at exec (index.js?635a:268), <anonymous>:376:1)
    at __webpack_require__ (eval at exec (index.js?635a:268), <anonymous>:85:30)
    at eval (setting.js:18)
    at Object../src/platform/expenseclaim/billViewShowPage/setting.js (eval at exec (index.js?635a:268), <anonymous>:504:1)

Any ideas? Thanks
Desktop (please complete the following information):

OS: mac
Browser chrome latest

I know It's because some of my module dependent a<EMAIL_ADDRESS>I try to dig it out.

the<EMAIL_ADDRESS>gone after reinstall.


Use features_in_arg from cligj in fiona/fio/load.py

Addresses #311

Coverage decreased (-0.3%) to 83.71% when pulling 382285cd7745dbd97a7f4cd5a138b5b5e732cbcc on sid-kap:features_in_arg into f70b44c512076961cd52c698558028f46d7bdd1a on Toblerity:master.

Coverage decreased (-0.3%) to 83.71% when pulling 382285cd7745dbd97a7f4cd5a138b5b5e732cbcc on sid-kap:features_in_arg into f70b44c512076961cd52c698558028f46d7bdd1a on Toblerity:master.


Load weights

Hi, when I use torch.load(xxxx.pth) and model.load_state_dict(xx), I meet a warning as followed:
Weights of SLaK not initialized from pretrained model: ['stages.0.0.large_kernel.Decom1.conv.weight', 'stages.0.0.large_kernel.Decom1.bn.weight', 'stages.0.0.large_kernel.Decom1.bn.bias', 'stages.0.0.large_kernel.Decom1.bn.running_mean']
Weights from pretrained model not used in SLaK: ['stages.0.0.large_kernel.lkb_origin.conv.weight','stages.0.0.large_kernel.lkb_origin.bn.weight', 'stages.0.0.large_kernel.lkb_origin.bn.bias', 'stages.0.0.large_kernel.lkb_origin.bn.running_mean']
Do you use the re-parameter operation during the model save? thanks!

Hi, to run SLaK models, we set --Decom True so we can use two decomposed kernels instead of one big MXM lkb_origin kernel. And we do not use the re-parameter operation for inference.

Hi, to run SLaK models, we set --Decom True so we can use two decomposed kernels instead of one big MXM lkb_origin kernel. And we do not use the re-parameter operation for inference.

But keys in your pretrained weight is big MXM lkb_origin kernel instead of two decomposed kernels, what are the reasons?

There might be some mistakes. Could you please tell us which pretrained model are you testing and providing more information about this?

There might be some mistakes. Could you please tell us which pretrained model are you testing and providing more information about this?

we use SLaK-T. The codes we load model are as followed:

from slak_tr import SLaK_tiny as tmm
pm = pmm(Decom =True,width_factor =1.3)
Traceback (most recent call last):
File "", line 1, in
NameError: name 'pmm' is not defined
torch_model = tmm(Decom =True,width_factor =1.3)
import torch
static = torch.load('SLaK_tiny_checkpoint.pth')
static = torch.load('SLaK_tiny_checkpoint.pth',map_location=torch.device('cpu'))
torch_model.load_state_dict(static["model"])
Missing key(s) in state_dict: "downsample_layers.0.0.weight", "downsample_layers.0.0.bias", "downsample_layers.0.1.weight", "downsample_layers.0.1.bias", "downsample_layers.1.0.weight", "downsample_layers.1.0.bias", "downsample_layers.1.1.weight", "downsample_layers.1.1.bias", "downsample_layers.2.0.weight", "downsample_layers.2.0.bias", "downsample_layers.2.1.weight", "downsample_layers.2.1.bias", "downsample_layers.3.0.weight", "downsample_layers.3.0.bias"..........]

Unexpected key(s) in state_dict: "stages.0.0.large_kernel.lkb_origin.conv.weight", "stages.0.0.large_kernel.lkb_origin.bn.weight", "stages.0.0.large_kernel.lkb_origin.bn.bias", "stages.0.0.large_kernel.lkb_origin.bn.running_mean", "stages.0.0.large_kernel.lkb_origin.bn.running_var", "stages.0.0.large_kernel.lkb_origin.bn.num_batches_tracked", "stages.0.1.large_kernel.lkb_origin.conv.weight", "stages.0.1.large_kernel.lkb_origin.bn.weight", "stages.0.1.large_kernel.lkb_origin.bn.bias", "stages.0.1.large_kernel.lkb_origin.bn.running_mean", "stages.0.1.large_kernel.lkb_origin.bn.running_var", "stages.0.1.large_kernel.lkb_origin.bn.num_batches_tracked", "stages.0.2.large_kernel.lkb_origin.conv.weight", "stages.0.2.large_kernel.lkb_origin.bn.weight", "stages.0.2.large_kernel.lkb_origin.bn.bias", "stages.0.2.large_kernel.lkb_origin.bn.running_mean", "stages.0.2.large_kernel.lkb_origin.bn.running_var", "stages.0.2.large_kernel.lkb_origin.bn.num_batches_tracked", "stages.1.0.large_kernel.lkb_origin.conv.weight"........]

Thanks for your follow-up. I indeed have reproduced your error. We have pasted the wrong link I believe. I have fixed the link just now and the model will give you 82.482 top1 acc. Could you please try again?

Sorry, I still fail to load the pretrained weight. I meet an error as followed:
Missing key(s) in state_dict: "stages.0.0.large_kernel.Decom1.conv.weight", "stages.0.0.large_kernel.Decom1.bn.weight", "stages.0.0.large_kernel.Decom1.bn.bias", "stages.0.0.large_kernel.Decom1.bn.running_mean", "stages.0.0.large_kernel.Decom1.bn.running_var", "stages.0.0.large_kernel.Decom2.conv.weight", "stages.0.0.large_kernel.Decom2.bn.weight", "stages.0.0.large_kernel.Decom2.bn.bias", "stages.0.0.large_kernel.Decom2.bn.running_mean", "stages.0.0.large_kernel.Decom2.bn.running_var", "stages.0.1.large_kernel.Decom1.conv.weight", "stages.0.1.large_kernel.Decom1.bn.weight", "stages.0.1.large_kernel.Decom1.bn.bias"......]
Unexpected key(s) in state_dict: "stages.0.0.large_kernel.LoRA1.conv.weight", "stages.0.0.large_kernel.LoRA1.bn.weight", "stages.0.0.large_kernel.LoRA1.bn.bias", "stages.0.0.large_kernel.LoRA1.bn.running_mean", "stages.0.0.large_kernel.LoRA1.bn.running_var", "stages.0.0.large_kernel.LoRA1.bn.num_batches_tracked", "stages.0.0.large_kernel.LoRA2.conv.weight", "stages.0.0.large_kernel.LoRA2.bn.weight", "stages.0.0.large_kernel.LoRA2.bn.bias", "stages.0.0.large_kernel.LoRA2.bn.running_mean", "stages.0.0.large_kernel.LoRA2.bn.running_var", "stages.0.0.large_kernel.LoRA2.bn.num_batches_tracked", "stages.0.1.large_kernel.LoRA1.conv.weight", "stages.0.1.large_kernel.LoRA1.bn.weight", "stages.0.1.large_kernel.LoRA1.bn.bias", "stages.0.1.large_kernel.LoRA1.bn.running_mean", "stages.0.1.large_kernel.LoRA1.bn.running_var"....]
I know this error may be caused by the way I load the pretrained weight. I use following codes to load the weight and I want to ask Whether this loading weight approach is reasonable
from slak_tr import SLaK_tiny as tmm
torch_model = tmm(Decom =True,width_factor =1.3)
import torch
static = torch.load('SLaK_tiny_checkpoint.pth',map_location=torch.device('cpu'))
torch_model.load_state_dict(static["model"])

Hi, I have successfully reproduced the SLaK-T model with PaddlePaddle framework (acc_top1: 0.8240 - acc_top5: 0.9677). Thanks for your wonderful work!


SPIKE: Design Automated process for granting Lab account access

Describe the issue
Individual developers sometimes need a playground to test ideas. We can provide this by creating an automated process for developers to request a lab account for e.g. 24 hours, grant access and then after the allotted time revoke access and run aws nuke on the account.
[CRC] Olena ask for a diagram about creating a self-serve app for teams to get their project set. This request overlaps with this ticket, for this reason instead of creating a new the same ticket will be used to do the design. Both requests differs only in minor details.
Additional context
There is a quota of 10% of the existing account for using the CLI as a tool to delete accounts. There is an alternative method that is quite time intensive. Some though needs to be put into the design of the app so the CPF team will not be flooded with abandoned accounts that will incur into monthly charges.
Definition of done

Proposed technical design document created and reviewed by the team.
Create higher level diagrams
Two use cases:

Teams requesting a full project set
Teams or individual contributors asking for temporary access

Document (SelfServeApp.docx) and diagrams (diagram.drawio) created and stored in  ****


HDDS-2505. Fix logic related to SCM address calculation in HddsUtils

What changes were proposed in this pull request?

Get rid of unreachable if branches in HddsUtils methods, as reported by Sonar
Reduce duplication:

getHostNameFromConfigKeys already supports multiple keys for fallback
extract the exception about unsupported multi-SCM

Use OptionalInt instead of Optional<Integer> for ports
Move usage of config key and its default value closer
Remove unused getScmServiceRpcAddresses()
Flip assertEquals args
Avoid String.format in logging
Remove @param without description

https://issues.apache.org/jira/browse/HDDS-2505
How was this patch tested?
Unit tests (host/port lookup has good coverage).  Also ran ozone acceptance test locally.

@adoroszlai , can you please the unit test failures. They seem related.

Thanks @bshashikant for checking this.  I don't see related unit test failures.  But this can definitely wait until @elek manages to get a fully green CI run.  Then I can update this PR with those fixes to get more relevant test results.

Thanks the patch @adoroszlai and the review @xiaoyuyao I am merging it right now.
The acceptance test failure seems to be unrelated (and will be fixed by #282 )

Thanks @elek for committing it.


nextcloud27: init

Description of changes
Closes #237560.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

This is running FINE except for the memcache locking option where NC27 is saying to me "oh you are locking with database, bad!" for some reason. Did the configuration change?
I run with the following relevant fragment:
    caching = {
      redis = true;
      apcu = true;
    };
    extraOptions = {
      redis = {
        host = "/run/redis-nextcloud/redis.sock";
        port = 0;
      };
      memcache = {
        local = "\\OC\\Memcache\\Redis";
        distributed = "\\OC\\Memcache\\Redis";
        locking = "\\OC\\Memcache\\Redis";
      };
    };

@RaitoBezarius can you point me to the actual error, please?
Also, why do you have redis & apcu enabled?

This is running FINE except for the memcache locking option where NC27 is saying to me "oh you are locking with database, bad!" for some reason. Did the configuration change?
I run with the following relevant fragment:
    caching = {
      redis = true;
      apcu = true;
    };
    extraOptions = {
      redis = {
        host = "/run/redis-nextcloud/redis.sock";
        port = 0;
      };
      memcache = {
        local = "\\OC\\Memcache\\Redis";
        distributed = "\\OC\\Memcache\\Redis";
        locking = "\\OC\\Memcache\\Redis";
      };
    };

you can use enableRedis too :)

@RaitoBezarius please take a look :)

Good to go for me, modulo rebase.

@dotlambda Done!
(Sorry, upon my rebase I spotted the actual conflicts, but not the additions)

OK while I'm at it, I decided to simply add the apps I also use on my own to the list (maps is not officially ready for nc27, but master already updated - and I tested their latest release on v27 w/ php 8.2 already, so it should change soon).


Added backport workflow

Added the backport workflow to help with backports and team velocity.

Hey @neoaggelos ,
You can check the example on my fork of the repository.


Add-on crashes daily at 3:15am

Hi,
for an unknown reason, the add-on restarts every night between 2:30am and 3:30am.
The restart fails with the following error:
2022-10-04 03:15:07,181 - tydomConnector - INFO - Host Target : mediation.tydom.com
2022-10-04 03:15:07,285 - gmqtt.mqtt.handler - INFO - [SUBACK] 1 (0,)
2022-10-04 03:15:07,288 - gmqtt.mqtt.handler - INFO - [SUBACK] 2 (0,)
2022-10-04 03:15:07,416 - __main__ - INFO - Tydom Client is connected to websocket and ready !
2022-10-04 03:15:07,420 - tydomConnector - INFO - Requesting 1st data...
2022-10-04 03:15:07,423 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /info
2022-10-04 03:15:07,430 - tydomConnector - INFO - ##################################
2022-10-04 03:15:07,434 - tydomConnector - INFO - ##################################
2022-10-04 03:15:07,437 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... POST /refresh/all
2022-10-04 03:15:07,442 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /configs/file
2022-10-04 03:15:07,447 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/cmeta
2022-10-04 03:15:12,458 - tydomConnector - INFO - >>>>>>>>>> Sending to tydom client..... GET /devices/data
Traceback (most recent call last):
  File "/app/main.py", line 226, in <module>
    loop_task()
  File "/app/main.py", line 148, in loop_task
    loop.run_until_complete(listen_tydom_forever(tydom_client))
  File "/usr/local/lib/python3.10/asyncio/base_events.py", line 646, in run_until_complete
    return future.result()
  File "/app/main.py", line 162, in listen_tydom_forever
    await tydom_client.setup()
  File "/app/tydomConnector.py", line 438, in setup
    await self.get_data()
  File "/app/tydomConnector.py", line 409, in get_data
    await self.get_devices_data()
  File "/app/tydomConnector.py", line 386, in get_devices_data
    await self.send_message(method=req, msg=msg_type)
  File "/app/tydomConnector.py", line 243, in send_message
    await self.connection.send(a_bytes)
  File "/usr/local/lib/python3.10/site-packages/websockets/legacy/protocol.py", line 620, in send
    await self.ensure_open()
  File "/usr/local/lib/python3.10/site-packages/websockets/legacy/protocol.py", line 921, in ensure_open
    raise self.connection_closed_exc()
websockets.exceptions.ConnectionClosedError: received 4001 (private use) Tydom non connecté.; then sent 4001 (private use) Tydom non connecté.

After that,
Manually restarting the add-on does not fix the problem.
Rebooting the HAss virtual machine does not fix the problem.
Restarting TYDOM box does fix the problem until the next night at around 2:00am when it happens again.
There is no particular message at that moment in home-assistant.log
If you tell me how to collect more logs for mqtt2tydom, I will give you more logs (as currently I only see the restart phase in the add-on log page. I don't see the event that that triggered the restart).

Are you using the public mediation endpoint or the local ip address?

Tydom IP address: mediation.tydom.com
By the way, the Tydom is probably crashed at this stage because its light is solid orange.
So the add-on provokes an issue with the Tydom 1.0. In the last 2 years before I started experimenting with HA, it did not crash once.

I have a similar issue with my Tydom Home :
At some point (every day or so, not at a particular time) my power graphs stop updating in my home assistant, tydom2mqtt has stopped because it could not connect, and my tydom Home box lights up in orange. The tydom app doesn't connect either.
I also use mediation.tydom.com for TYDOM_IP . Is there any known issues with mediation.tydom.com ?
Did not occur to me so far that it could be a connection issue with the delta dore servers. Next time it happens, i'll try to use the local IP to connect to the tydom when it goes into "orange mode". The delta dore manual says solid orange means "local only" by the way (whatever it means).

So, my Tydom crashed again today. A few symptoms :

Solid orange light
on mediation.tydom.com : No error in the tydom2mqtt log, but no update on energy sensors
I switch to the local IP and i get this error :

2022-10-10 21:30:45,994 - tydomConnector - INFO - """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
2022-10-10 21:30:45,995 - tydomConnector - INFO - TYDOM WEBSOCKET CONNECTION INITIALISING....
2022-10-10 21:30:45,995 - tydomConnector - INFO - Building headers, getting 1st handshake and authentication....
Traceback (most recent call last):
  File "/app/main.py", line 226, in <module>
    loop_task()
  File "/app/main.py", line 148, in loop_task
    loop.run_until_complete(listen_tydom_forever(tydom_client))
  File "/usr/local/lib/python3.10/asyncio/base_events.py", line 646, in run_until_complete
    return future.result()
  File "/app/main.py", line 160, in listen_tydom_forever
    await tydom_client.connect()
  File "/app/tydomConnector.py", line 108, in connect
    conn.request(
  File "/usr/local/lib/python3.10/http/client.py", line 1282, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/local/lib/python3.10/http/client.py", line 1328, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.10/http/client.py", line 1277, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.10/http/client.py", line 1037, in _send_output
    self.send(msg)
  File "/usr/local/lib/python3.10/http/client.py", line 975, in send
    self.connect()
  File "/usr/local/lib/python3.10/http/client.py", line 1454, in connect
    self.sock = self._context.wrap_socket(self.sock,
  File "/usr/local/lib/python3.10/ssl.py", line 513, in wrap_socket
    return self.sslsocket_class._create(
  File "/usr/local/lib/python3.10/ssl.py", line 1071, in _create
    self.do_handshake()
  File "/usr/local/lib/python3.10/ssl.py", line 1342, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:997)

https://<local tydom ip> displays :

I restart the tydom : the web interface comes back, tydom2mqtt connects to the local IP, everything works

Update: I used the local IP instead of mediation.tydom.com and i had no crash since my last post.

A year later I tried again. I'm on 3.4.2 and it is not happening anymore. Closing.


Reaching ERR_REF_COUNT_LIMIT lead to a crash in ecma_ref_object

JerryScript revision
ba4e3a402fce722ea752243c60c009307438d97f
Build platform
Ubuntu 18.04 LTS
Build steps
python tools/build.py --profile=es2015-subset --lto=off --error-messages=on --strip=off --compile-flag=-fsanitize=address
Test case
function main() {
function v0() {
    const v1 = new v0();
}
const v2 = v0();
}
main();

Execution steps
build/bin/jerry testcase.js
Output
Program received signal SIGABRT, Aborted.
Backtrace
Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007ffff6e43801 in __GI_abort () at abort.c:79
#2  0x00000000005acae2 in jerry_port_fatal ()
#3  0x000000000053bedf in jerry_fatal ()
#4  0x00000000004f90d3 in ecma_ref_object ()
#5  0x00000000005042cd in ecma_copy_value ()
#6  0x000000000055cfca in vm_loop ()
#7  0x000000000055b5e6 in vm_execute ()
#8  0x000000000055b183 in vm_run ()
#9  0x000000000051f650 in ecma_op_function_call_simple ()
#10 0x000000000051fafa in ecma_op_function_construct ()
#11 0x000000000055bd22 in vm_execute ()
#12 0x000000000055b183 in vm_run ()
#13 0x000000000051f650 in ecma_op_function_call_simple ()
#14 0x000000000051fafa in ecma_op_function_construct ()
#15 0x000000000055bd22 in vm_execute ()
#16 0x000000000055b183 in vm_run ()
#17 0x000000000051f650 in ecma_op_function_call_simple ()
#18 0x000000000051fafa in ecma_op_function_construct ()
#19 0x000000000055bd22 in vm_execute ()
#20 0x000000000055b183 in vm_run ()
#21 0x000000000051f650 in ecma_op_function_call_simple ()
#22 0x000000000051fafa in ecma_op_function_construct ()
#23 0x000000000055bd22 in vm_execute ()
#24 0x000000000055b183 in vm_run ()
……

@ArayzWang Thanks for the report. I'm not sure it can be flagged as a valid bug, though. ERR_REF_COUNT_LIMIT signals that you hav reached the internal limits of the engine. Most probably because of the infinite recursion on v0.
(I'm not completely sure why this didn't cause a stack overflow instead, but perhaps simply the reference count limit was hit sooner. BTW, it could be useful if you enabled stack limit in your build. Then, infinite recursions will / should be turned into runtime exceptions.)

@akosthekiss I tried rebuild project with following arguments:python tools/build.py --profile=es2015-subset --lto=off --error-messages=on --strip=off --compile-flag=-fsanitize=address --stack-limit=3

@akosthekiss I tried rebuild with following arguments:
python tools/build.py --profile=es2015-subset --lto=off --error-messages=on --strip=off --compile-flag=-fsanitize=address --stack-limit=10
(Adding a --stack-limit=10 to enable stack limit)
The crash still reproduce, is there any other way to enable stack limit?

@ArayzWang Nah, that should be the proper way. Interesting. Someone might want to take a look at this then. @zherczeg @rerobika perhaps?

I'll take a look at it.

Since this recursive function is quite "small" and the engine is compiled in release mode the internal refcount error is still reached earlier than the 10 KB stack limit. Reducing further the stack limit to 1 KB, the expected RangeError is thrown.

IMO we can treat this issue resolved, please reopen it if needed.


Closer to the platform

Skate components should be definable via customElements.define() and skate.define() should become a syntactic sugar for anonymising components, and that's all. This piggy backs off #867 which implements #710.

This means that we will deprecated skate.define at some point and encourage the users to just pass skate components to customElements.define?

@zzarcon we'll see. I need to spike how we could do unique tag names without define().

So it turns out define() won't be deprecated. It gives you the ability to anonymise components, or use Webpack's HMR.


Add helpers for backend stores

This patch adds helpers for accessing the global and client backend stores.

We should probably use different types for the stores to avoid confusion.

This doesn't compile after rebasing on origin/main.


Merge changes to live

Docs Build status updates of commit e460dff:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

archived-reference/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Bug Report: Some sections of the Website are not responsive

Reproduction steps

scroll down to the bottom and see in the mobile view that feedback and social media links are overlapping with each other.
click on the sign up button in the navigation menu, and see that the icons of the name, email, mobile no. are hidding i.e. form is not responsive.
click on the contributors section and see that the heading and the cards of the contributors are not responsive.

Expected behavior

feedback and social media links should be seperated
sign up form should be responsive i.e all icons must be clearly visible in the mobile view
contributors cards and heading should be responsive i.e. shifted towards left

Actual Behavior

Feedback and social media links are overlapping with each other when seen in mobile view.
Icons of the name, email, mobile no. under sign up form are hidding i.e. form is not responsive.
Heading and the cards of the contributors are not responsive.

👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Please assign me this issue so that I can resolve it under GSSOC-23

@piyushkhurana2019 Go for it.
For any support join our community: https://codeincommunity.com/

Please assign me this issue so that I can resolve it under GSSOC-23


Create python branch

Hi Scott@swo and Ed @eschrom , this branch is inherited from fy_eval but with updated python files. The python file is the first version of generating vaccine uptake projections. Please leave any comments, then I can integrate in the plotting and evaluation modules in the next steps.

There are still a bunch of files that shouldn't be in this PR, like the Zone Identifier, etc.
Also, this PR both adds the Python stuff and removes the R stuff, which may or may not have been your intent

Close in favor of #13


osprepare: Fail to install bundles in clearlinux behind a proxy

osprepare is ran by the launcher to detect if there is a missing pacakge (qemu, docker, xorriso, etc)
and install the required bundle (cloud-control).
This task fails when running behind a proxy.
This is not an issue in ubuntu and fedora because you can configure the proxies in /etc/apt/apt.conf or /etc/dnf/dnf.conf

Since osprepare has code for ClearLinux, Fedora and Ubuntu, and you say the latter two are ok, this sounds like it is a ClearLinux specific issue.  I thought ClearLinux has autoproxy, or a way to configure proxies manually for a system so system software can access a network?
I'm not sure how much osprepare itself can do about this.

sudoFormatCommand() is not honoring environment variables from /etc/profile
making osprepare use env vars rom /etc/profile can fix the issue in clearlinux.

I've got a patch which I think does the right thing, but need to test.

Upon further code inspection withing golang, we're pretty sure this patch is actually unneeded.  It makes explicit grabbing the current Env, but if none was given (the state before the patch), the golang runtime pulls in the current Env.
I can only guess that the env was actually wrong (eg: maybe sudo didn't pass the user proxied env through to the root env running the ciao binary?)...in which case this bug is invalid?  But I'm guessing and assuming a lot here.  @albertomurillo if you can confirm how you're running things in more detail, eg: where is the proxy env var specified, what's the ciao command line and sudo arg's, etc., we can figure out more concretely what's gone wrong.

I think this bug is invalid too.
The reason ciao-launcher is not getting the proxy env variables is because we are not starting ciao-launcher from the command line but from a systemd unit file.
I found that the admin can create /etc/systemd/system/ciao-compute.service.d/proxy.conf file
(docker style) to make ciao-launcher start with proxy environment values.

Based on the last two comments I'm closing this as invalid, worked around in systemd standard way.


Reduce number of allocations (closures, delegates) in TaskObservableExtensions.ToTask

We use the ToTask-extension a lot in our code and found it rather expensive wrt. object allocations. Looking into the code, I found that by implementing a custom IObserver, creation of closures and delegates can be avoided. I think even without anonymous lambdas, the code is still straghtforward and easy to read.

@danielcweber this looks great! :sparkles: Introducing more of these into the Rx side to reduce allocations seems like a good idea for the next minor release.


meta-overc: fix the issue of dom0 cannot startup at the first time

The essential-autostart.service should be after overc-conftools.service
since the overc-conftools.service will setup OVS which is needed
by dom0 container.
Signed-off-by: Fupan Li<EMAIL_ADDRESS>

didn't get to test this today, will look at it tomorrow (sept 22nd)

merged


operator mode, The registrarImage cannot be specified

operator mode, The registrarImage cannot be specified,still use the default.

release 0.8 version.

The driver registrar image field mentioned(registrarImage) in the documentation was wrong. It supposed to be nodeRegistrarImage. https://github.com/intel/pmem-csi/pull/790 fixes this.

@liupeng0518 was this not caught by validation when doing kubectl create with input that contains an unknown field?

It indeed isn't caught, I tried.
@avalluri is that expected?

It indeed isn't caught, I tried.
@avalluri is that expected?

Generated CRD uses x-kubernetes-preserve-unknown-fields: true where the API server prunes the unknown fields silently without any validation errors. If we make the unknown fields as validation error we should stop setting this field.

Let's continue in https://github.com/intel/pmem-csi/issues/795


[CircleGraphCtrl] Notify selection change

This will enable notify selection change to owner.
ONE-vscode-DCO-1.0-Signed-off-by: SaeHie Park<EMAIL_ADDRESS>

for #641, from draft #647


Support server side hot module replacement

For example, to reload the Apollo Server: https://twitter.com/zachcodes/status/1129600383200813059?s=20
Once #1109 is merged, adding this to the default custom server would be a nice place for it.

@jesstelford do you still want to add this to the default server?

Yes!
This could be one approach: https://twitter.com/dan_abramov/status/1192898770842931209?s=20


#22 #20 Introduces compatibility with Strapi v4 + Permalinks + Collect assets filter

Keeps basic functionality of permalinks
Adds new filter asset_url
Described in README examples requires following collection to be setup up and with permissions findone and find for Public:

With provided PRI am able to create following site. Permalinks are working, at least  :id.
I really like new filter asset_url which collects locally remote assets.
Everything needs bit more testing. Also, this is my first Ruby code ever, but it feels similar to Python, at least a bit. If you like PR, I could maintain the project. Cheers.

Also, for populating all data: all I do is add it to the URL: https://api.example.com/api/posts?populate=*

Hi 👋 The plugin works with PR #21. You can see more chat details on discord via frontend-other.
Great work on the filter.
I would like to add this to #21. I know #21 works for certain; Daedalus and I made the smallest changes possible.

Hello @csharpee :), thank you for the feedback. Please feel free to reuse whatever you feel to :) I also added authentication in the another PR.

Also, for populating all data: all I do is add it to the URL: https://api.example.com/api/posts?populate=* via my web browser.

Regarding this, I think it has little flaw in design - pulling whole collection with all the data does not scale, which is why I introduced iterative approach.

Regarding this, I think it has little flaw in design - pulling whole collection with all the data does not scale, which is why I introduced iterative approach.

I am unsure what you mean.
On build of Jekyll site, I pull all post data from Strapi server and each post is already iterated while building Jekyll.
It would be great to have cache working for each array i.e. posts, products, etc..

check if local data
if true exit
if false download data

Hello, I am sorry but now I failed with an understanding :)
What is confusing for me - step in the browser. With approach in PR it is simplified - iteration over collection which user configured, provided complete documents for the user, and user renders/copy only what necessary. Copying locally medias from Strapi server I added since without it - my links with images were pointing to the Strapi server, and I haven't found a way to do it. Writing code was easier.
Actually I got an idea, for another optimisation patch - to specify in the collection config which fields are necessary and just use these fields :)

Due to massive changes in other PR: https://github.com/strapi/jekyll-strapi/pull/27 and much better code and docs organization in new PR - I am invalidating this one.


[Docs] Add caching topics to ROADMAP.md

@elliotcmorris @feltech I took the liberty of force-pushing.

But now I can't tell what changed :grin:

@elliotcmorris @feltech I took the liberty of force-pushing.

But now I can't tell what changed 😁

Maybe we should move to GitLab

Sorry for the delay, now you have to do a rebase. :(
RAMWR


Loading image stacks

Dear Lacie and Team,
CODEX data often comes in an image stack form (.tif) that contains all channels in one file. Would it be possible to support importing the stacks / montages?
Thanks!
Zina

Yeah, that should be possible! Would you mind sharing an example of one of these images with us? If you don't want to post it publicly, you can email it to me at<EMAIL_ADDRESS>


Response time out with client connected using unix_socket_path when using python client but not with redis-cli

Response time out with client connected using unix_socket_path when using python client but not with redis-cli.
I have a redis-server instance running locally accepting connections via unix socket.redisgraph.so was built by compiling the  RedisGraph project. redis-server was started as:
redis-server --unixsocket /tmp/redis.sock --loadmodule ./src/redisgraph.so

I create the python client as:
conn = redis.Redis(host=redis_host, port=redis_port, decode_responses=True, unix_socket_path="/tmp/redis.sock")
graph = Graph(db_name, conn)

My queries to construct the nodes and edges of the graph work fine. But when I try to to query for something from the constructed  graph, the response never returns (partial stack trace below). When I try to run the same query from redis-cli (run as redis-cli -s /tmp/redis.sock) I do get a response. Leads me to believe something in the python client is not right, maybe.
File "/Users/narayan/Documents/path/to/files/file.py", line 84, in build_frames
    result = graph.query(query["query"])
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redisgraph/graph.py", line 175, in query
    response = self.redis_con.execute_command(*command)
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/client.py", line 901, in execute_command
    return self.parse_response(conn, command_name, **options)
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/client.py", line 915, in parse_response
    response = connection.read_response()
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/connection.py", line 739, in read_response
    response = self._parser.read_response()
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/connection.py", line 363, in read_response
    response = [self.read_response() for i in xrange(length)]
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/connection.py", line 363, in <listcomp>
    response = [self.read_response() for i in xrange(length)]
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/connection.py", line 363, in read_response
    response = [self.read_response() for i in xrange(length)]
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/connection.py", line 363, in <listcomp>
    response = [self.read_response() for i in xrange(length)]
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/connection.py", line 363, in read_response
    response = [self.read_response() for i in xrange(length)]
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/connection.py", line 363, in <listcomp>
    response = [self.read_response() for i in xrange(length)]
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/connection.py", line 363, in read_response
    response = [self.read_response() for i in xrange(length)]
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/connection.py", line 363, in <listcomp>
    response = [self.read_response() for i in xrange(length)]
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/connection.py", line 324, in read_response
    raw = self._buffer.readline()
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/connection.py", line 256, in readline
    self._read_from_socket()
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/connection.py", line 198, in _read_from_socket
    data = recv(self._sock, socket_read_size)
  File "/Users/narayan/anaconda3/envs/bridge/lib/python3.8/site-packages/redis/_compat.py", line 72, in recv
    return sock.recv(*args, **kwargs)

Other Details:
OS version: macOS Monterey 12.0.1, Intel-based MBP (2019)
pip version of clients used:
$ pip list | grep redis
redis                             3.5.3
redisgraph                        2.4.0

redis-server version: Redis server v=6.2.6 sha=00000000:0 malloc=libc bits=64 build=c6f3693d1aced7d9
redisgraph.so was built from latest master branch.

Managed to isolate the instance where the above process is getting stuck. It blocks after it reads this from the buffer:
b'+\'South Korea s SK Innovation to file patent infringement lawsuit against LG Chem in U.S. South Korea\'"\'"\'s SK Innovation to file patent infringement lawsuit against LG Chem in U.S. \n'
This is the value printed in the data variable at line https://github.com/redis/redis-py/blob/master/redis/connection.py#L249
Removing the field from my query no longer blocks socket IO. Any ideas why this might be happening?
Also, let me know if I should rather move this issue to the redis-py project.

Hi @narayanacharya6 thank you for reporting! would you mind sharing a dataset with which we can reproduce this behavior?

Hey @swilly22, due to data privacy reasons I am unable to share the data/query that led to this. I will try to reproduce this issue with dummy data and report back. Meanwhile, do you mind answering a couple of questions, which I anticipate to be the culprit (but have no proof of at the moment)?

Can having \n (like above) or \r or other special characters in my response fields lead to inconsistent behavior with reading from the connection buffer? I see that these characters are used as separators while reading fields (https://github.com/redis/redis-py/blob/master/redis/connection.py#L71)

When connecting over unix sockets, are there limits to how long the requested query can be (mine is upwards of 20k string characters, UNION of many MATCH queries) or how large the response can be? If there are buffer limits and associated configs, can you point me to some documentation?

Ok, I think its because of \n in the response fields.
Minimal example to reproduce inspired by the getting started example here - https://docs.redis.com/latest/modules/redisgraph/redisgraph-quickstart/ is below. The only change I've introduced in the example is added \n to the name Valentino Rossi.

Start your redis-server with redisgraph module and unix socket.
``
For redis-cli:
a. Start redis-cli: redis-cli -s /tmp/redis.sock
b. Create graph: GRAPH.QUERY MotoGP "CREATE (:Rider {name:'Valentino Rossi\n'})-[:rides]->(:Team {name:'Yamaha'}), (:Rider {name:'Dani Pedrosa'})-[:rides]->(:Team {name:'Honda'}), (:Rider {name:'Andrea Dovizioso'})-[:rides]->(:Team {name:'Ducati'})"
c. Run query: GRAPH.QUERY MotoGP "MATCH (r:Rider)-[:rides]->(t:Team) WHERE t.name = 'Yamaha' RETURN r,t"

You will get a response:
1) 1) r
   2) t
2) 1) 1) 1) 1) "id"
            2) (integer) 0
         2) 1) "labels"
            2) 1) Rider
         3) 1) "properties"
            2) 1) 1) name
                  2) Valentino Rossi

      2) 1) 1) "id"
            2) (integer) 1
         2) 1) "labels"
            2) 1) Team
         3) 1) "properties"
            2) 1) 1) name
                  2) Yamaha
3) 1) "Cached execution: 0"
   2) "Query internal execution time: 0.526000 milliseconds"

For redis python client:

import redis
from redisgraph import Graph
redis_conn = redis.Redis(host="localhost", port=6379, decode_responses=True, unix_socket_path="/tmp/redis.sock")
graph = Graph("MotoGP", redis_conn)
graph.query("MATCH (r:Rider)-[:rides]->(t:Team) WHERE t.name = 'Yamaha' RETURN r,t")

The above never returns.

This is what I'm getting on my dev machine:
BigSur 11.6.1
Python 3.9.5
RedisGraph master branch

pip list | grep redis
hiredis                    2.0.0
redis                      3.5.3
redisgraph                 2.4.1

Test script:
import redis
from redisgraph import Graph

db_name = "MotoGP"

def query_db(connection):
    graph = Graph(db_name, connection)

    # query graph
    q = """MATCH (r:Rider)-[:rides]->(t:Team) WHERE t.name = 'Yamaha' RETURN r,t"""
    result = graph.query(q)
    result.pretty_print()

#-------------------------------------------------------------------------------
# form connections
#-------------------------------------------------------------------------------

# connect to database using TCP
tcp_conn = redis.Redis(host='localhost', port=6379, decode_responses=True)

# connect to database using unix-socket
unix_socket_conn = redis.Redis(host='localhost', port=6379, decode_responses=True, unix_socket_path="/tmp/redis.sock")

#-------------------------------------------------------------------------------
# populate graph
#-------------------------------------------------------------------------------

tcp_conn.flushall()

q = """CREATE (:Rider {name:'Valentino Rossi\n'})-[:rides]->(:Team {name:'Yamaha'})"""

#graph = Graph(db_name, tcp_conn)
graph = Graph(db_name, unix_socket_conn)
result = graph.query(q)

#-------------------------------------------------------------------------------
# query graph
#-------------------------------------------------------------------------------

query_db(tcp_conn)
query_db(unix_socket_conn)

Results:
python3 test.py
+------------------------+-----------------+
|           r            |        t        |
+------------------------+-----------------+
| {name:"Valentino Rossi | {name:"Yamaha"} |
|           "}           |                 |
+------------------------+-----------------+

Cached execution 0.0
internal execution time 0.358
+------------------------+-----------------+
|           r            |        t        |
+------------------------+-----------------+
| {name:"Valentino Rossi | {name:"Yamaha"} |
|           "}           |                 |
+------------------------+-----------------+

Cached execution 1.0
internal execution time 0.149

Both connections produce the same result-set, I'm adding @chayim to this issue maybe he'll have an idea,
@narayanacharya6 would you mind installing hiredis when this python package is available redis-py switches to it in-order to perform redis response parsing.

@swilly22 Installing hiredis makes the difference. With hiredis, I do get back responses as expected.
Keeping this issue open in case we expect the same behavior without hiredis as well.

Thank you @narayanacharya6 for validating this, we will look into the none hiredis case
Will you be running with hiredis ?

@swilly22 For now, I can continue working with hiredis installed. I haven't done rigorous testing yet - but so far seems fine.