FreeBSD: Error reading the .llvm_bc section of ELF file

I'm using gllvm to compile FreeBSD libc and libc++ into LLVM bitcode.
When running get-bc on resulting shared libraries, I get:

Error reading the .llvm_bc section of ELF file

Extracting from .a library partially works - some .o files gets extracted, but others fail with the same error.
Is there any debugging switch in gllvm or maybe any other idea how to fix that?

So first thing to check, are some of the files assembly (almost certainly true with libc and libc++). In which case you will
never be getting bitcode for them. There is no magic switch, you can manipulate the logging level, and output it to a file.
That can help. I once played around with musl libc, and you can find some observations about that over here, but that's all I got.

To be explicit: not having a .llvm_bc segment means the object file was not compiled in the normal way. There are various reasons why this can happen, but the most common is that the source file is ASM.

Sorry pressed the wrong button.

If you flick logging on to debug, you will see why we are skipping generating the bitcode
in the logs from this.

To be explicit: not having a .llvm_bc segment means the object file was not compiled in the normal way. There are various reasons why this can happen, but the most common is that the source file is ASM.

I doubt libc++ has any assembler inside. At the same time, libc does have assembler object files, but get-bc still partially works on the static library.
I believe the problem is somewhere in ELF parsing for dynamic library case.

If you flick logging on to debug,

How do I do that? I have 0 experience with Go.

Quoting from the README.md:
export WLLVM_OUTPUT_LEVEL=DEBUG
export WLLVM_OUTPUT_FILE=/tmp/gllvm.log

The file will be big, but you want to grep for skipping

Ouch, sorry for missing this obvious info.

The file will be big,

Does the log file gets recreated on each gllvm invocation? I'm running the compilation via make CC=gllvm, but the log file is only 150 lines long and contains bits related to linking phase.

No it should append if it already exists. Maybe you need to start a new fresh build?

No it should append if it already exists. Maybe you need to start a new fresh build?

Sigh.
All right, I got the log. Here is a sample log for compiling a file:
DEBUG:Calling execCmd(clang++80, [-fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -nostdlib -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.optional.pico -MToptional.pico -fstack-protector-str
DEBUG:execCmd: clang++80 [-fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.optional.pico -MToptional.pico -fstack-protector-strong -Wno-empty-bod
DEBUG:execCmd: clang++80 [-fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -nostdlib -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.optional.pico -MToptional.pico -fstack-protector-strong -Wno
INFO:Calling [/usr/local/bin/gclang++ -fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -nostdlib -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.optional.pico -MToptional.pico -fstack-protector
INFO:Entering [/usr/local/bin/gclang++ -fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -nostdlib -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.random.pico -MTrandom.pico -fstack-protector-st
WARNING:Did not recognize the compiler flag: -MF.depend.random.pico
WARNING:Did not recognize the compiler flag: -MTrandom.pico
DEBUG:Compile using parsed arguments:
InputList:         [-fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -nostdlib -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.random.pico -MTrandom.pico -fstack-protector-strong -Wno-empty-bod
InputFiles:        [/usr/src/contrib/libc++/src/random.cpp]
ObjectFiles:       []
OutputFilename:    random.pico
CompileArgs:       [-fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.random.pico -MTrandom.pico -fstack-protector-strong -Wno-empty-body -Wno-str
LinkArgs:          [-nostdlib]
ForbiddenFlags:    []
IsVerbose:         false
IsDependencyOnly:  true
IsPreprocessOnly:  false
IsAssembleOnly:    false
IsAssembly:        false
IsCompileOnly:     true
IsEmitLLVM:        false
IsLTO:             false
IsPrintOnly:       false

The IsEmitLLVM:        false line looks suspicious. Does this give any useful info?

No that looks perfectly normal.  You need to figure out:

What files are missing their .llvm_bc segments, then

Figure out how they are being produced.

Here's the last part of the log corresponding to linking stage
DEBUG:Calling execCmd(clang++80, [-fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -nostdlib -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.filesystem_operations.pico -MTfilesystem/operations.
DEBUG:execCmd: clang++80 [-fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.filesystem_operations.pico -MTfilesystem/operations.pico -fstack-prote
DEBUG:execCmd: clang++80 [-fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -nostdlib -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.filesystem_operations.pico -MTfilesystem/operations.pico -fs
INFO:Calling [/usr/local/bin/gclang++ -fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -nostdlib -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.filesystem_operations.pico -MTfilesystem/operati
INFO:Entering CC [-fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o libc++.so.1.full -Wl,-soname,libc++.so.1 filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstream.pico shared_mutex
WARNING:Did not recognize the compiler flag: filesystem/int128_builtins.pico
WARNING:Did not recognize the compiler flag: variant.pico
...
DEBUG:Compile using parsed arguments:
InputList:         [-fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o libc++.so.1.full -Wl,-soname,libc++.so.1 filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstream.pico shared_mut
InputFiles:        []
ObjectFiles:       [-Wl,-soname,libc++.so.1]
OutputFilename:    libc++.so.1.full
CompileArgs:       [-fstack-protector-strong filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstream.pico shared_mutex.pico regex.pico random.pico optional.pico iostream.pico functional.pico debug.pico chrono.pico charconv
LinkArgs:          [-shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -Wl,-soname,libc++.so.1 -L/wrkdirs/usr/ports/devel/libcxx-bitcode/work/usr/src/amd64.amd64/lib/libcxxrt -lcxxrt]
ForbiddenFlags:    []
IsVerbose:         false
IsDependencyOnly:  false
IsPreprocessOnly:  false
IsAssembleOnly:    false
IsAssembly:        false
IsCompileOnly:     false
IsEmitLLVM:        false
IsLTO:             false
IsPrintOnly:       false

DEBUG: We are skipping bitcode generation because we did not see any input files.
DEBUG:Calling execCmd(clang80, [-fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o libc++.so.1.full -Wl,-soname,libc++.so.1 filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstream.pic
DEBUG:execCmd: clang80 [-fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o libc++.so.1.full -Wl,-soname,libc++.so.1 filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstream.pico shared
DEBUG:Calling [/usr/local/bin/gclang -fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o libc++.so.1.full -Wl,-soname,libc++.so.1 filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstrea

Files named xxx.pico are actually inputs, but it seems that gllvm treats them as unknown flags. Could it be the source of the error?

Yes. Can you do, say,
file filesystem/int128_builtins.pico

and show me what it says?  By the way are you building on linux or BSD?

So the google tells me:
The .So extension clashes with the .so extension used for shared libraries on file systems that are case-insensitive. Change to .pico instead. This matches what NetBSD uses. A full buildworld and buildkernel (default options) succeeds over NFS onto a case-sensitive file system.

# file /wrkdirs/usr/ports/devel/libcxx-bitcode/work/usr/src/amd64.amd64/lib/libc++/filesystem/int128_builtins.pico
/wrkdirs/usr/ports/devel/libcxx-bitcode/work/usr/src/amd64.amd64/lib/libc++/filesystem/int128_builtins.pico: ELF 64-bit LSB relocatable, x86-64, version 1 (FreeBSD), with debug_info, not stripped

As you see, I'm building on FreeBSD.

OK so that might explain your problems. I can try and fix things, but you will have to help me by testing.
Deal?

Absolutely! Thanks for helping me.

If you need it, I can give you all commands required to reproduce this problem on a fresh FreeBSD system.

Lets see if I can just tweak it for you first.  So I pushed a fixed.  The CI is still chugging away, but
you could try and update your gllvm ... (let me know if you need help here).

Hmm. Warnings are gone, but InputFiles is still empty:
DEBUG:Calling execCmd(clang++80, [-fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -nostdlib -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.filesystem_operations.pico -MTfilesystem/operations.
DEBUG:execCmd: clang++80 [-fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -fstack-protector-strong -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-v
DEBUG:execCmd: clang++80 [-fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -nostdlib -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.filesystem_operations.pico -MTfilesystem/operations.pico -fs
INFO:Calling [/usr/local/bin/gclang++ -fpic -DPIC -O2 -pipe -isystem /usr/src/contrib/libc++/include -isystem /usr/src/contrib/libcxxrt -nostdinc++ -nostdlib -D_LIBCPP_BUILDING_LIBRARY -DLIBCXXRT -g -MD -MF.depend.filesystem_operations.pico -MTfilesystem/operati
INFO:Entering CC [-fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o libc++.so.1.full -Wl,-soname,libc++.so.1 filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstream.pico shared_mutex
DEBUG:Compile using parsed arguments:
InputList:         [-fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o libc++.so.1.full -Wl,-soname,libc++.so.1 filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstream.pico shared_mut
InputFiles:        []
ObjectFiles:       [-Wl,-soname,libc++.so.1 filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstream.pico shared_mutex.pico regex.pico random.pico optional.pico iostream.pico functional.pico debug.pico chrono.pico charconv.
OutputFilename:    libc++.so.1.full
CompileArgs:       [-fstack-protector-strong]
LinkArgs:          [-shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -Wl,-soname,libc++.so.1 filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstream.pico shared_mutex.pico regex.pico random.pico optional.pico
ForbiddenFlags:    []
IsVerbose:         false
IsDependencyOnly:  false
IsPreprocessOnly:  false
IsAssembleOnly:    false
IsAssembly:        false
IsCompileOnly:     false
IsEmitLLVM:        false
IsLTO:             false
IsPrintOnly:       false

DEBUG: We are skipping bitcode generation because we did not see any input files.
DEBUG:Calling execCmd(clang80, [-fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o libc++.so.1.full -Wl,-soname,libc++.so.1 filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstream.pic
DEBUG:execCmd: clang80 [-fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o libc++.so.1.full -Wl,-soname,libc++.so.1 filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstream.pico shared
DEBUG:Calling [/usr/local/bin/gclang -fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o libc++.so.1.full -Wl,-soname,libc++.so.1 filesystem/int128_builtins.pico variant.pico valarray.pico utility.pico typeinfo.pico strstrea

Right, because it is a linking step,  the object files are there now.

The big question is are we injecting our segment into the pico files.

elfdump -c /wrkdirs/usr/ports/devel/libcxx-bitcode/work/usr/src/amd64.amd64/lib/libc++/hash.pico | grep llvm_bc
returns nothing. I guess, the answer is "no".

 The value for this property doesn't seem right too.

They look wrong, but they might not matter, since this is a compile only step.
I don't see a skipping the bitcode generation, but this snippet might be too small.
It may be that I will have to debug this on my laptop.
So can you  guide me through that for FreeBSD.
I will be using a vagrant box, so what FreeBSD should I be looking for?

Use freebsd/FreeBSD-12.1-RELEASE box.
Inside the VM:
# ee /etc/pkg/FreeBSD.conf
<replace "quarterly" with "latest">
ESC, Enter, Enter

# pkg install git llvm80 binutils go
# git clone https://github.com/SRI-CSL/gllvm
# git clone https://github.com/arrowd/freebsd-ports
# cd freebsd-ports
# git checkout -t origin/libcxx
# make -C devel/libcxx-bitcode

After the last command finished, you'll have /tmp/gllvm.log and building directory is freebsd-ports/devel/libcxx-bitcode/work/.
Make sure you have system sources in /usr/src. If not:
# git clone https://github.com/freebsd/freebsd /usr/src
# cd /usr/src
# git checkout -t origin/releng/12.1

Feel free to ping me, if you get stuck on something.

OK I'm on it.

Oh, right, you'll have to build gllvm from source and add it to the PATH. Otherwise, running make will cause the latest release to be built.

How much memory do I need to do this? I haven't been able to clone either:
https://github.com/freebsd/freebsd
or
https://github.com/arrowd/freebsd-ports

Sorry I gave up, I rebuilt a box with 8G but it too failed to clone them.
Maybe if you send me the complete log of a clean build, and I can go from there.

Are you talking about RAM or HDD space? It shouldn't take much of RAM unless you didn't install llvm80 package. Otherwise it'd try to build it from source, which indeed takes a lot of space in both memory and disk.

As I said, it was cloning those two repos. Therefore HDD. llvm80 gave me no issues. log file?

My vagrant file:
# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure(2) do |config|

  config.vm.box = "freebsd/FreeBSD-12.1-RELEASE"
  config.vm.box_version = "2019.11.01"

  #config.vm.provision :shell, path: "bootstrap.sh"

  config.vm.provider "virtualbox" do |vb|
    vb.memory = "8192"
    vb.customize ["modifyvm", :id, "--ioapic", "on"]
    vb.customize ["modifyvm", :id, "--memory", "8192"]
    vb.customize ["modifyvm", :id, "--cpus", "4"]
   end

end

Got anything better?

The vb.memory variable sets the amount of RAM. To change the disk size, you may try Vagrant's experimental feature: https://www.vagrantup.com/docs/disks/usage#resizing-your-primary-disk
However, you'll also need to do some magic inside VM to grow the FS:
First drop to single user mode
# shutdown now
Then edit partitions:
# gpart restore      - fix GPT layout after resizing
# gpart resize <somepartition>
# gpart resize <somepartition> -i <slice number>       - if the FS is located on something like ada0s1

Finally, grow the FS
# growfs /
If you don't want to mess with this, here are log files you are requested:
http://arrowd.name/libcxx-bitcode-8.0.1.log - the build log, relevant parts start from line 250.
http://arrowd.name/gllvm.log - the log generated by gllvm.
If nothing helps, I can arrange a dedicated VM and provide a SSH access for you.

Oh and another thing to try is to do git clone with --depth 1 flag. You don't really need all the history for both repos.

Let me look at the log today, then if I work up the strength I will retry my hand at the vagrant thing.
I can't get the log: 403 forbidden.

Oops, sorry. Fixed the permission issue.

Bare with me, thinking out loud here.
So I see a lot of bitcode being created and recorded in the appropriate segments.
Lappy-Lazuli:Desktop iam$ grep objcopy gllvm.log
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm045671925 algorithm.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm360882816 any.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm116872692 bind.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm569727752 charconv.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm193861116 chrono.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm347713002 condition_variable.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm085267199 debug.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm978663549 exception.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm608946246 functional.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm722216971 future.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm450924629 hash.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm673198777 ios.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm513516590 iostream.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm898813387 locale.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm777174427 memory.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm867464108 mutex.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm109315981 new.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm923515664 optional.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm695370454 random.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm951643032 regex.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm171382266 shared_mutex.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm041921119 stdexcept.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm137503613 string.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm115190840 strstream.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm188472713 system_error.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm751714174 thread.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm244052351 typeinfo.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm702490275 utility.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm058881785 valarray.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm843285114 variant.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm525768038 vector.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm094403254 filesystem/directory_iterator.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm627709679 filesystem/int128_builtins.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm996783811 filesystem/operations.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm817004737 cxxrt_auxhelper.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm606716400 cxxrt_dynamic_cast.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm002580882 cxxrt_exception.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm078754804 cxxrt_guard.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm818403649 cxxrt_libelftc_dem_gnu3.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm779735102 cxxrt_memory.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm939495859 cxxrt_stdexcept.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm774280433 cxxrt_terminate.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm213847705 cxxrt_typeinfo.o] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm589775019 algorithm.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm115183528 any.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm768723137 bind.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm406407266 charconv.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm751741359 chrono.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm825165895 condition_variable.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm407579840 debug.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm446640394 exception.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm252841317 functional.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm497706563 future.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm440936662 hash.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm076112414 ios.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm419304695 iostream.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm405146249 locale.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm133362624 memory.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm500449035 mutex.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm428590949 new.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm890848812 optional.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm453665488 random.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm284651352 regex.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm125016605 shared_mutex.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm415676394 stdexcept.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm761481876 string.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm721205669 strstream.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm307796242 system_error.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm083092210 thread.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm458368777 typeinfo.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm521821896 utility.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm445256692 valarray.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm233581924 variant.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm504165765 vector.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm763083055 filesystem/directory_iterator.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm939504743 filesystem/int128_builtins.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm864680565 filesystem/operations.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm446076328 cxxrt_auxhelper.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm895406526 cxxrt_dynamic_cast.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm118291291 cxxrt_exception.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm030397606 cxxrt_guard.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm166375861 cxxrt_libelftc_dem_gnu3.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm000053716 cxxrt_memory.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm215917310 cxxrt_stdexcept.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm102737621 cxxrt_terminate.po] had exitCode 0
DEBUG:execCmd: /usr/local/bin/objcopy [--add-section .llvm_bc=/tmp/gllvm624764228 cxxrt_typeinfo.po] had exitCode 0

But not in the position independent ones, the .pico, which are the ones being linked at the end.
I also see the bitcode being generated for the .pico files.
 So today I will try and figure out why.

Great! Thank you for working on this.

Probably a hard coded extension check somewhere.

Thats for later, first gotta walk my beach at dawn.

As I suspected. A hardcoded notion of what constitutes an object file.
I just pushed a quick fix, wanna try it?
I will look at some of the other weirdness while I am at it...

All warnings are gone, but in the end still a error:
/usr/local/bin/get-bc -a llvm-ar80 -l llvm-link80 -r /usr/local/bin/ar /wrkdirs/usr/ports/devel/libcxx-bitcode/work/usr/src/amd64.amd64/lib/libc++/libc++.so.1
ERROR:Error reading the .llvm_bc section of ELF file /wrkdirs/usr/ports/devel/libcxx-bitcode/work/usr/src/amd64.amd64/lib/libc++/libc++.so.1.

New log is here http://arrowd.name/gllvm2.log

Not clear that you are using the latest.
Let me put in some logging instrumentation so we can be sure we are on the same page.
I am also fixing the dependency flag parsing, so they don't end up in the wrong place.
I will ping you when I have pushed.
CI seems very slow this morning, the last push still hasn't commenced.

I manually pull the patches to our devel/gllvm port and then build it. It'd be great if you give me exact commands to build it from source.

I just cd into the src directory and do make install (go uses git to download source):
vagrant@ubuntu-focal:/vagrant$ echo $GOPATH
/vagrant/go
vagrant@ubuntu-focal:/vagrant$ cd $GOPATH/src/github.com/SRI-CSL/gllvm
vagrant@ubuntu-focal:/vagrant/go/src/github.com/SRI-CSL/gllvm$ git pull
Already up to date.
vagrant@ubuntu-focal:/vagrant/go/src/github.com/SRI-CSL/gllvm$ make install
go install github.com/SRI-CSL/gllvm/cmd/...
# github.com/SRI-CSL/gllvm/shared
shared/compiler.go:211:7: syntax error: unexpected default, expecting expression
make: *** [Makefile:20: develop] Error 2
vagrant@ubuntu-focal:/vagrant/go/src/github.com/SRI-CSL/gllvm$

the installed failed because I am in the middle of the instrumenting ...

Hum. This is my try:
root@rel121-git:~/gllvm # make install
go install github.com/SRI-CSL/gllvm/cmd/...
go: warning: "github.com/SRI-CSL/gllvm/cmd/..." matched no packages

OK I pushed some dependency file switch fixes, plus some instrumentation.
I already think I know why there is no code on libc++.so.1 and it is the same problem (the .1)
but lets look at the log file first.

Hmmmm. Not sure about freebsd.
Can you install it via
go get github.com/SRI-CSL/gllvm/cmd/...

Give me a second and I will update the version number, so we can check on the cmd line...

OK I pushed again. Easy way to check:
 >gsanity-check

Version info: gsanity-check version 1.2.9
Released: October 30 13 2020

...

Okay, seems fine
# ~/go/bin/gsanity-check

Version info: gsanity-check version 1.2.9
Released: October 30 13 2020

Let me know when I can peek at the log file.

Woohoo, with the gllvm from master I got
Bitcode file extracted to: /wrkdirs/usr/ports/devel/libcxx-bitcode/work/usr/src/amd64.amd64/lib/libc++/libc++.so.1.bc.

And judging from its size, it should be generated correctly:
# file /wrkdirs/usr/ports/devel/libcxx-bitcode/work/usr/src/amd64.amd64/lib/libc++/libc++.so.1.bc
/wrkdirs/usr/ports/devel/libcxx-bitcode/work/usr/src/amd64.amd64/lib/libc++/libc++.so.1.bc: LLVM IR bitcode
# du -h /wrkdirs/usr/ports/devel/libcxx-bitcode/work/usr/src/amd64.amd64/lib/libc++/libc++.so.1.bc
6.9M    /wrkdirs/usr/ports/devel/libcxx-bitcode/work/usr/src/amd64.amd64/lib/libc++/libc++.so.1.bc

Awesome! Let me try this version with another port I was having problems with.

Great!  I am looking into doing this in a more robust way. I have to jump on a zoom call so will be busy
for a while...

OK, problems with another port seem to arise due to some object files being compiled from assembly, so this is fine.

Great! I am looking into doing this in a more robust way.

I'll happily test your code after refactoring. Thanks again for working on this.

OK great! So can I have the latest logs for libc and also libc++ so I can look for issues.

Logs for this project are very large. Here's compressed gllvm.log: http://arrowd.name/gllvm.tar.xz
The build log itself is enormous, but I can attach it too, if you insist.

Thanks, no I am just interested in the gllvm logs. That's great. I got it. You can delete them now.

Bingo! Found another one:
WARNING:attachBitcodePathToObject ignoring unrecognized extension: .nossppico

The google tells me:
".nossppico" denotes a position-independent relocatable object without
+stack smashing protection.

FYI
Lappy-Lazuli:Desktop iam$ grep WARNING gllvm_latest.log | grep nossppico | wc
     866    4330   67548
Lappy-Lazuli:Desktop iam$ grep WARNING gllvm_latest.log | grep assembly | wc
    1684   23576  159980

I pushed a fix for the nose picking.

This is a good news.
Just a thought - how about treating every command line argument that doesn't start with - symbol as file argument? And maybe additionaly do a check if such file is really exists. This should allow gllvm to get rid of explicit extensions enumeration.

A bit slow me thinks. I am thinking more of a fall back.

But yes rather than give up, try and figure out what the thing is.  So it is not just whether the
file exists but what format it is. I can use the file utility, but sometimes that isn't installed (klee docker image for example), so I have been looking into the go packages debug/elf and debug/macho

So @arrowd  I pushed some fixes. We no longer fail if we don't recognize the extension. I have onlt tested it on linux. Will try it out later on darwin. If you want to try it out that would be great.
make check

in the source would do it.
Thanks for the feedback on the tool. It is always good to improve it when it is getting stressed.
You can close this issue whenever you want.
I wouldn't mind hearing a bit about this "project" you are working on.....

Oh and will publish a new version when you close this ticket.
Cheers, Ian.

I have onlt tested it on linux. Will try it out later on darwin. If you want to try it out that would be great.

After setting correct environment variables, the test suite passes. I have to use GNU objcopy due to bug in our objcopy, but this should already be fixed in upcoming FreeBSD release.

Thanks for the feedback on the tool. It is always good to improve it when it is getting stressed.

And thank you for working through this issue!

I wouldn't mind hearing a bit about this "project" you are working on.....

You actually already named it - KLEE symbolic virtual machine. My final goal is to make it able to use native FreeBSD libc compiled to LLVM IR, because uclibc contains too much Linux-specific stuff and doesn't build there.
Waiting for a new release to update our port!

@arrowd    The new version 1.2.9 is live.

Pushed to FreeBSD Ports tree. Thanks for cooperation.


Wifi config page does not work on android phones.

VER 1.7.1
In ap config wifi mode .the page does not work on android phones.
It stucked after display the title "Homespan setup".
It works fine on iphone.

A temporary solution, I use another config wifi page code myself . It works fine on both  phone.

Sorry, android phones are not directly supported by HomeSpan (since you need an iPhone to pair HomeKit devices).

Sorry, android phones are not directly supported by HomeSpan (since you need an iPhone to pair HomeKit devices).

Thanks for reply。
And....android user can use homekit device bridged by HASS（Home Assistant）。 (such as my friend )

Thanks for the info.  Once you configure WiFi, are you able to pair the HomeSpan device and get it working with HASS?

Thanks for the info. Once you configure WiFi, are you able to pair the HomeSpan device and get it working with HASS?

Yes ,It working fine .
In fact ,many diyer use HASS as a smart home center .
HASS is compatible  with homekit ,xiaomi...and some other api.
This is the lib   https://github.com/home-assistant/home-assistant.io

Hass isn’t fully compatible. Only simple switches, fans and lights…

Unfortunately, I don't have an android phone so won't readily be able to address this.

https://www.home-assistant.io/integrations/homekit_controller/


Makdown for community

Added the tab for a community to display a possible static markdown. The implementation is a clone from the one from projects.
I also added a skeleton of a markdown for a community, to community OEBC013.

The commits included in this PR were not the right ones.


Relative auto-import path when dependency package.json "name" is not specified

This is fairly niche, but I found that in module: nodenext, when we're using a package with no name field, we generate a bad completion list entry.
import { indexFoo } from "../node_modules/dependency/lib/index.js";

for the following test case:

//// @filename: ./node_modules/dependency/package.json
//// {
////     "type": "module",
////     "exports": {
////         ".": {
////             "types": "./lib/index.d.ts",
////         }
////     }
//// }

//// @filename: ./node_modules/dependency/lib/index.d.ts
//// export function fooFromIndex(): void;

//// @filename: ./package.json
////{
////    "type": "module",
////    "dependencies": {
////        "dependency": "^1.0.0"
////    }
////}

//// @filename: ./src/foo.ts
//// import fooFrom/**/

@DanielRosenwasser Should the expected result be the same as for module: esnext?
import { fooFromIndex } from "../node_modules/foo/lib/index";

Daniel’s expected behavior is import { indexFoo } from "dependency"; but we need to double check that this actually works in Node.

Backlogging this since this is not a valid packument


Filtering scantasks by name doesn't work

Gives me empty results:

Seems to be working for me on staging -- could this be an auth issue or something?

Yeah, it's working for me again -- could be an auth issue.


Want upgrade http to websocket but always got warning WriteHeader

Is this a BUG REPORT or FEATURE REQUEST?:
/kind support
What happened:
I am use gorilla/websocket to upgrade websocket, but always got warning:
2019/04/16 10:48:44 http: response.WriteHeader on hijacked connection from github.com/caicloud/nirvana/service.(*response).WriteHeader (context.go:199)

What you expected to happen:
Provide a way to disable WriteHeader calling.

https://github.com/caicloud/nirvana/blob/32ebf1fc87109bcda0a109951a427d7ac82b5b58/service/context.go#L212-L218
May be set c.statusCode = 200 in Hijack which will prevent WriteHeader to calling.


failed to compile with mingw

The problem is unrelated to msys2 as previously thought https://github.com/dictu-lang/Dictu/issues/568. Using cmake with ninja generator and a standalone MinGW distro (winlibs.com in my case), it failed to compile with the same error.

I'm building on standalone mingw with -DDISABLE_HTTP=1, it's easier to setup dependencies with msys2 and I think if the issue regarding msys2 mingw resolved then the issue with standalone mingw will be resolved too. I will close this redundant issue.


Fix compiler error for lambda parameter with non-letter

Fix a generated code error when lambda parameter contains a character
that is not part of a valid Java identifier.
Fixes https://github.com/prestosql/presto/issues/5085

CI failed -- https://github.com/prestosql/presto/issues/4568

CI failed -- https://github.com/prestosql/presto/issues/4973


Datasets to add

We are still missing a few datasets. I believe these can fill out the ranks and cover most use-cases for Scandinavian languages.

[ ] NordJylland News , SNS
[ ] (potentially dataset from MUNI)
[ ] (potentially sundhed.dk)
[ ] VG_summarization, clustering and SNS
[ ] SNL, clustering and SNS
[ ] NorQUAD, retrieval
[ ] da-hashtag-twitterhjerne, retrieval
[ ] Add norwegian bitext (already added to mteb)
[ ] Add #54
[ ] run models on SwednSTS

We notably need

bitext for Swedish
clustering for Danish

(before running model we should probably consider implementing #18)

@x-tabdeveloping I believe these datesets mostly cover what we want in SEB? Let me know if there is anything specifically that we are missing.

I'm sure we can get some Bitext mining task for Swedish from OPUS like swedish-norwegian or swedish-danish, I can do that if need be.

Could we perchance use (aka. scrape or find) DBA entries and categories for Danish clustering?

Could we perchance use (aka. scrape or find) DBA entries and categories for Danish clustering?

We could, I am unsure if we could share the dataset though.

A simpler solution might be to simply use dagw domains.

I have split up all the datasets to add into issues for now. Unless we specifically want to add some new dataset I believe we can close this issue.

Ah there might be a review sentiment dataset available here: https://github.com/esbenkc/Emma

There is also this intent classification dataset from Certainly.io: https://github.com/certainlyio/corona_dataset/blob/master/danish.csv

jolly, let's close this


Prevent divergent migrations from being merged by concurrent, not-rebased PRs

Problem

See https://github.com/WordPress/openverse-api/pull/810 and the description for the issue.
Description

We need some way to prevent this.
Here are some suggestions I left in this comment, copied below: https://github.com/WordPress/openverse-api/pull/810#issuecomment-1191503799

How can we prevent this? Is there any way we can ensure PRs with migrations are always rebased before merging? Could we run an action triggered by pushes that introduce new migrations using https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#running-your-workflow-only-when-a-push-affects-specific-files and the iterate through all open, non-draft PRs and request changes on them if there is a migration in them?
We'd also need a similar job in the CI + CD workflow to check for migration conflicts against main any time the PR is pushed to.

Marked as high due to the risk it introduces.
Implementation

[ ] 🙋 I would be interested in implementing this feature.

Referencing #812 (duplicate) as an alternative way to phrase the issue.

Can I add something to the discussion?
Can we say that in an ideal migration tree, there should be only one leaf node?
If yes, we should think of running automated tests which detect this. Wring a custom Django command can be one way to achieve this.
A Django command which checks for the state of migration graph. If the command finds more than one leaf node, it exits with a certain exit code. This command can be integrated in CI steps as well.

That's correct. I think our existing CI checks will do that already, save for the fact that they need to be run against a rebased version of the branch for them to detect the fact that a branch will merge in a second branch of migations. This happens when two people open branches that independently add migrations with the same number and then merge them sequentially without rebasing the second branch after the first is merged.
@dhruvkb and I were chatting in DMs about this and we think that the pull_request_target: [synchronize] workflow trigger would be the right one to use to rebase the branch against main and then run the CI check. We can skip this for now for branches that don't introduce migrations, that way we don't run the risk of eating up a ton of our GitHub worker allowances. We could also skip it for PRs that are otherwise unmergeable (not enough approvals, not checks not passing), but then we'd need to make sure we also run the rebase check whenever those things are covered.

Adding more context, GitHub has a built-in feature to ensure branches are up-to-date before they can be merged (it's a checkbox called "Require branches to be up to date before merging" under branch protection rules) but it's either all-in (which can be annoying for safe branches) or switched off (which brings us to this issue).

The require branches to be up-to-date before merging is useful but it is kind of annoying and a bit of a kludge in that it enforces that universally. Even if you just update a markdown document, you'd have to rebase your branch if main changed and wait for CI to run all over again :confused: Of course, we could also optimize CI to only change when certain files change, but that's yet another issue.
I think the synchronize event is the right time to do it. It's proactive, we can make the action required for PRs and it will block. Waiting for when the person hits the merge button is annoying and frustrating if it fails when we could have caught the issue proactively anyway.

The synchronize event is only fired when commits are pushed to a PR. It's also the default activity type for workflows running on PRs (see first "Note" in this section). It might not be the right event to watch for (as that's where we are right now).

That's the pull_request event. I'm suggesting using the pull_request_target event which runs when the PR's target or base branch is updated, unless I've misunderstood that event trigger.

Unassigning myself here. The PR linked above adds a warning, but I think we can do better to prevent this by running actual automated checks for migration conflicts. I won't have time to work on this before I go on holiday.

Lowering the priority to medium, this is important but is an internal improvement that shouldn't block other development.


Bloom filter

Any support or plan to support of bloom filter for unique constraint, equal join and IN & LIKE operators on both native and foreign storages? (ref: https://github.com/apache/parquet-cpp/blob/642da055adf009652689b20e68a198cffb857651/src/parquet/bloom_filter.cc)

Hi,
AFAIK we don't use any probabilistic index right now. We do use a bit vector for certain types of operators with IN, but it's deterministic.
Regards,
Candido

Deterministic index is awesome.
When is the index built? Is it available for skipping fragments on storage?

When is the index built? Is it available for skipping fragments on storage?

We  build a bitmap for IN operations, so in a query like this
select col1,col2,avg(col5) from tab1 where col3 in (select col1 from tab2 where col2 between 1 and 50)
a bitmap index with the range on min/max of col1 after the col2 filter on table tab2 is built as first step of the query, and the tab1 will be filtered testing the col3 values against the bitmap index.
To skip fragments on storage we are using the min/max value of the column that we store for each chunk; here probably the bloom filter would be a nice idea on equality cheks, but I am not sure how much would be effective, given the increased maintenance costs of the metadata
the part of the code that skip the fragment is here
https://github.com/omnisci/omniscidb/blob/d2f719934ebfd421c00d3bce83a2b0cda0ef802f/QueryEngine/Execute.cpp#L3771


What similar tools have accomplished the same motive that we pursue and what sets this project apart.

Its undeniable that we stand on the shoulder of giants. Therefore its wise to consider the current solutions out there and make a case study of each noting its pros and cons as well as drawing inspiration from previous successful projects. This is not to be a competition but rather give developers a different experience when dealing with color in frontend development.

Gregor Aisch has an online color scale tool that makes generating color blind safe palettes easy.
Coolors is also a source of design inspiration for the webapp implementation

Also drew inspiration from the Gradient generator on  Tailwind Components
The color picking layout is so simplified and more intuitive than the traditional colour picker. Makes it easier to pick compatible color values.


advice on models without tf2 pretrained checkpoints

Your code uses models with tf2 pre-trained checkpoints. However, tf2 checkpoints are only available in a few bert models: https://github.com/tensorflow/models/tree/master/official/nlp/bert
What about languages that are only available in tf1 bert checkpoints? Do you have any advice?
If i use the tf1 checkpoints, I would receive errors when loading the model.
init_checkpoint='the pretrained model checkpoint path.'
model=tf.keras.Model() # Bert pre-trained model as feature extractor.
checkpoint = tf.train.Checkpoint(model=model)
checkpoint.restore(init_checkpoint)

I later figured it out: google released some models in nlp/modeling, others in tf.hub.
What the above lines were trying to do is to load the tf2 model in nlp/modeling. If your desired model is not in nlp/modeling but is available in tf.hub, you can load the model through tf.hub.


xml attr

Feature Requested
https://github.com/whatyouhide/vim-textobj-xmlattr
Relevant Screenshot
No response
Checklist

[X] The feature would be useful to more users than just me.

Could you please describe how what exactly delimits such an xmlattr text object, since I am not familiar with XML?

参考链接为 https://github.com/whatyouhide/vim-textobj-xmlattr

yes, I already saw the link the first time. However, as someone not familiar with XML, the link does not provide sufficient information for me to understand what an XML attribute is, I need some more information what counts as a xml attribute and what not

ah, those are just html attributes, I see. Added them just now, however, I implemented the difference between inner and outer slightly differently, ax targets the whole attribute, and ix only the value inside the quotes, hope that makes sense

Thank you so I can fully migrate to this plugin


Read webhooks api Giving Permission error

{
"Code": 403,
"Message": "Unauthorized access;User doesn't have enough permissions;"
}

@MARZOOQUE this is fixed. Please try again!


Prevent double release of mach ports

Summary:
When a MIG routine returns KERN_FAILURE, the demux function will release any OOL resources like ports. In this case, task_port and thread_port will be released twice, potentially resulting in use after free of the ports.
I don't think we can test this in any useful way
rdar://problem/37331387
Reviewers: jasonmolenda
Subscribers: lldb-commits
Differential Revision: https://reviews.llvm.org/D45011
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@328761 91177308-0d34-0410-b5e6-96231b3b80d8
(cherry picked from commit 8f022f17fe6a1579c1ec53c0f3f369fdcbd1a71b)

@swift-ci please test and merge


Editing so that fruit is in game

Thanks for your change. As indicated by @michaeldejong the Fruit class has quite a bit of pellet left overs.
Concerning fruits, the pacman rules are a bit more involved -- fruits appear after a certain number of pellets have been eaten. Also different fruits (you have now just picked an apple) exhibit different behavior.
Your changes are quite in line with the current setup of JPacman, so I intend to mix them (and fix the pellet references).

Thanks, this change is quite large and I am postponing it for now.


Reorganize content into new sections

Stylistic update and layout suggestion
Proposed fix:
This site is full of precious content, but some of it is hard to find. I am proposing a reorganization of the entire site into more intuitive groups:

What to expect

It is here
Yes; this is bad
This is not a normal flu
[government] policies

Guidance

Things you should do

...

Things you should NOT do

...

More resources
About us
Contribute

This is a big reorganization, but I think it is important. I am happy to tackle this work myself, but no one should spend time on this before we get an endorsement from the maintainers that this is actually something they want.

Done and deployed!

Woot!!

On Mar 18, 2020, at 6:23 PM, nditada<EMAIL_ADDRESS>wrote:

Done and deployed!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


[（live．free™！）] Formula 1 São Paulo Grand Prix 2024 Live Streams Free On Tv Channel 03 NOV 2024

Lando Norris’ bid to win his maiden F1 world championship was dealt a seismic boost in Interlagos after he took a brilliant pole position for the Brazilian Grand Prix, with rival Max Verstappen a shock 17th.
Verstappen was eliminated from a chaotic rain-hit qualifying on Sunday morning, carried over a day after Saturday’s running was abandoned due to bad weather.
FOLLOW LIVE: F1 Brazilian GP race updates in Interlagos
The triple world champion had been on course to improve his time in the wet conditions but Lance Stroll’s crash resulted in the third of an astonishing five red flags, and Q2 did not resume.
It left a furious Verstappen in 12th and, with the Dutchman to serve a five-place engine penalty, he will be way down the order for the 71-lap race later on Sunday.
Due to weather disruptions, the schedule for the Brazilian GP has been updated. Qualifying has been moved to Sunday morning, while the race will take place earlier than previously announced to avoid heavy rain that is forecast later in the day.
Updated: What time does the Brazilian Grand Prix start?
The Brazilian GP will begin at 12:30pm local time (-3 GMT) at at Autodromo Jose Carlos Pace (Interlagos Circuit). The start time has been brought forward by 90 minutes due to weather.


AVC 444 mode

What are the plans to update FreeRDP to implement the changes announced my MSFT for RDP 10?
The main challenge to use AVC/H.264 as the one and only Codec in Remote Desktop scenarios is that text shows a halo effect with typical implementations of AVC/H.264. This is caused by the color conversion process that happens as part of the compression which throws away some of the
https://blogs.technet.microsoft.com/enterprisemobility/2016/01/11/remote-desktop-protocol-rdp-10-avch-264-improvements-in-windows-10-and-windows-server-2016-technical-preview/

@puneet101, FreeRDP actually supports AVC444. The /gfx:AVC444 command line option should enable it. However, there are several issues with AVC444 support on the server-side.

Can you describe the several issues you allude to above?
How do you decide the default option and what do you think is the default coming in the MSFT mstsc client?
Thanks!

First of all, for some reason some Windows 10 systems refuse to use AVC444 unless Prioritize H.264/AVC 444 GPO is set. Apparently this has been fixed with some latest update and now systems behave as described in that blog post. Then we've seen servers to send malformed AVC444 data to the client which breaks the encoder after some time, like 5 to 30 minutes.
mstsc.exe client from Windows 10 supports AVC444 and has it enabled by default. I am not aware of any way to disable it.

Thanks! AVC444 is pretty standard now. Should be enabled by default.
Has this been tested only on Win client or other platforms also?

I believe all FreeRDP clients should support it with software GDI enabled (/gdi:sw). X11 client has also 'hardware' support.

AVC444 server side support for FreeRDP is not there yet, but client side is working as @ilammy pointed out. As for Win10 not defaulting to it, we can't do much about it ;)


Implement accept

Is your feature request related to a problem? Please describe.
I would like to filter the types of files the user can upload, e.g. accept=".txt,text/plain"
Describe the solution you'd like
Pass the accept prop to the file input
https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/accept
Describe alternatives you've considered
N/A
Additional context
N/A

Hey !
You can achieve that by using the inputProps property :
<MuiFileInput
  placeholder="Choisir un fichier"
  inputProps={{
    accept: 'video/*'
  }}
/>

@viclafouch can you please document it in the API reference? Multiple people (including me) thought it wasn't possible before stumbling onto this issue.

Got it !

Here the documentation : https://viclafouch.github.io/mui-file-input/docs/api-reference/#inputprops--accept


Pr/71

Fixed Lemma.json

@mcelaney Please use this PR to bring in my changes to the meta-update.

Closing this pull request. It is now out of date with recent changes. Will create a new pull request.


feat: plugin hidden field

migrate some change and suggestion from #13

should tag 0.5.1 after the pr merged.


Restore upgrade params with toml

@daniel-thom Had a conversation with Sherin yesterday, and decide to revert the toml back as the source of sample upgrade parameter values. Now the default toml file only contain the required params, and the optional ones are listed on doc page, the user decides which ones to be added.


[WIP]: Multi-journal as issues

Like Podcast <> Episodes, but Journal <> Issues.

It was a good idea ! :)

@just1602 I closed this PR because I'm going a different way in another PR:
https://github.com/crimethinc/website/pull/1200


Unity plugin

Add Unity DI plugin

Hi @diseks,
Thanks for your contribution. All looks good to me.
Before I am able to merge, can you please amend your commit message to include the sign off line?
More info here.

Hi, Tomasz.
Thanks for your reply. I added sign-off line in last commit. Please check it.


bot Not buying

{"name":"binance-api","version":"0.0.12","hostname":"5771f48662d2","pid":18,"job":"simpleStopChaser","uuid":"f0fca491-05a2-4546-a723-fa520a25a391","symbol":"BTCUSDT","symbolUuid":"ce0fba82-60dc-4bd3-8c0b-73603670cedf","level":50,"quantity":0,"msg":"Order quantity is less or equal than minimum quantity - 0.00000100.","time":"2021-01-18T15:34:45.412Z","v":0}

my balance in binance is 53USDT

my balance in binance is 53USDT

Hey @abuvanth
I suggest you read the code and make sure you understand how it works.
I won't support your case nor provide any tips as this is simply testing my code.
It is your responsibility to use it as it's your money.
Sorry for not being helpful.

Hey @abuvanth
I suggest you read the code and make sure you understand how it works.
I won't support your case nor provide any tips as this is simply testing my code.
It is your responsibility to use it as it's your money.
Sorry for not being helpful.

Guys, join the Telegram group to solve problems with each other ..
https://t.me/joinchat/z3cKyYFcx0NiOTA8


[web] flutter_service_worker.js should be generated from template file

Currently flutter_service_worker.js is automatically generated when running 'flutter build web' from a string template that is in the flutter_tools source code.
It should be possible to generate the service worker from a template file in the project directory. This would allow the developer to customize the service worker's behavior, giving the option to implement different caching strategies.

@kevmoo made service_worker for this although unfortunately it doesn't work out of the box with flutter. One reason is that the flutter build process does not put the compiled service worker into a separate file.
Just to add my use case here, I would like to attach headers to http requests in the just_audio plugin.

@kevmoo made service_worker for this although unfortunately it doesn't work out of the box with flutter. One reason is that the flutter build process does not put the compiled service worker into a separate file.
Just to add my use case here, I would like to attach headers to http requests in the just_audio plugin.

@ryanheise – I did?

@ryanheise – I did?

Apologies if I had the details wrong as I was browsing from my phone which isn't ideal. Although, you are listed as a project contributor and uploader, and yours is the only name that pops up when I browse the commit history for the past two years.
At the very least it seems that the project is unmaintained and you have stepped in at some point to continue maintaining it. I know nothing admittedly but it seems like functionally you might be someone who might be able to comment on this feature request and whether service_worker could satisfy that feature request.

Apologies if I had the details wrong as I was browsing from my phone which isn't ideal. Although, you are listed as a project contributor and uploader, and yours is the only name that pops up when I browse the commit history for the past two years.
At the very least it seems that the project is unmaintained and you have stepped in at some point to continue maintaining it. I know nothing admittedly but it seems like functionally you might be someone who might be able to comment on this feature request and whether service_worker could satisfy that feature request.

Hi @ryanheise
My feature request is for the option to provide my own service worker implementation when I run flutter build web.
There is currently the --pwa-strategy argument that you can pass with the options of none and offline-first. I would like a third option, lets call it custom that would look for a flutter-service-worker.js file under the project_path/web folder, update the RESOURCES map with the correct hashes and output that to the service worker file under project_path/build/web.
How the service worker is implemented should be up to the project developer. The service_worker package might be a good option or you can just use javascript.

Hi @ryanheise
My feature request is for the option to provide my own service worker implementation when I run flutter build web.
There is currently the --pwa-strategy argument that you can pass with the options of none and offline-first. I would like a third option, lets call it custom that would look for a flutter-service-worker.js file under the project_path/web folder, update the RESOURCES map with the correct hashes and output that to the service worker file under project_path/build/web.
How the service worker is implemented should be up to the project developer. The service_worker package might be a good option or you can just use javascript.

Ah I see. I was thinking of a more general framework for generating custom service workers via dart2js and tying that into the flutter build process. Maybe Dart files could have an annotation or comment at the top to indicate to the compiler that this file should be output into its own .js file, and then perhaps your use case would also be solved by naming your file to overwrite/override flutter_service_worker.js.

Ah I see. I was thinking of a more general framework for generating custom service workers via dart2js and tying that into the flutter build process. Maybe Dart files could have an annotation or comment at the top to indicate to the compiler that this file should be output into its own .js file, and then perhaps your use case would also be solved by naming your file to overwrite/override flutter_service_worker.js.

I have another use case on this issue.  My application has 2000+ asset files, and needs to download them automatically on service worker activation (or perhaps on request) so the application can run offline.  This is too many files for Cache.addAll() so I wrote an alternative to the downloadOffline routine in flutter_service_worker.js to fetch the files sequentially.  Then after the build I replace the code in flutter_service_worker.js with my own.  Would be nice if the build could accept my custom code.

We have our own custom service_worker.js file which we hack around in our build process.
Here's the code for it in our GitHub actions file
    - name: Inject custom turtle_service_worker.js
      run: |
        sed -i -e '1h;2,$H;$!d;g' -e "s/self\..*//" ./build/web/flutter_service_worker.js
        cat ./web/turtle_service_worker.js >> ./build/web/flutter_service_worker.js

We search for self. because we want to use the generated manifest in our own service worker.

Hello,
Sorry if this is not the place, but how can I compile service worker code from dart? Is there a way or the only way is to write js files directly?
Thanks!

any update? I need custom self.addEventListener("fetch") for my cached file.

I want to implement PWA Push Notifications in my flutter web app, my understanding is that this requires adding self.addEventListener('push', myPushCallback) to the service worker. Does this issue mean that's currently impossible?

There seems to be a lack of documentation around the flutter_service_worker.js in general. For example no where can I find anything about 'downloadOffline()'
We need to add additional resources to the cache that are not in the pubspec assets.  I think editing the template could solve this problem

Looks like a workaround might be simply editing the generated flutter_service_worker.js after running flutter build web. I initially didn't like the idea, as it only covers flutter build and not flutter run, but then I learned that flutter run doesn't support service workers at all, so I'm not losing anything.
For my use case of registering a Push event listener, it should be sufficient to append some extra code to the generated file. I'll give that a try.

Looks like a workaround might be simply editing the generated flutter_service_worker.js after running flutter build web. I initially didn't like the idea, as it only covers flutter build and not flutter run, but then I learned that flutter run doesn't support service workers at all, so I'm not losing anything.

@mrwonko.  You can check that with the Chrome Dev Tools, using the Application tab.
The only funny thing is that customizing the flutter_service_worker.js file found in the Flutter SDK 'devtools' folder has no effect in run/debug mode. Such a file is located here:
flutter\bin\cache\dart-sdk\bin\resources\devtools\flutter_service_worker.js

Since this is part of the 'cache' folder, it is probably generated from downloaded files when Flutter is initially installed (?).
On the contrary, customizing the file used by the file generators that are used when flutter build web is invoked is possible and works (I checked). This file is located here:
flutter\packages\flutter_tools\lib\src\web\file_generators\js\flutter_service_worker.js

I have the same problem, and I need to insert the logic into self.addEventListener("fetch") every time


[Security] alternative install to "https://dotenvx.sh/"

The docker guide indicates that this should be installed from https://dotenvx.sh/. This is a very high risk for supply chain attack, and is actually entirely disallowed in some orgs due to this known risk.
How else can we use this within docker without exposing this risk?

can you elaborate why this is a very high risk - are you referring to if we would lose control over our own domain dotenvx.sh?
there are install instructions here if you prefer to install from github releases: https://dotenvx.com/docs/install#git-hub-releases

are you referring to if we would lose control over our own domain

Yep, that's exactly it. Either you lose control, or poor security posture causes control to be lost either knowingly or unknowingly. Making installs from your site a malware delivery method.
These are common attacks on developer tools, 3rd party sites for popular tools being popular targets since they usually don't have automated monitoring & alerting , or are intentionally designed to avoid delivering malware with external checksum validation.
The docs should probably highlight this risk, and even avoid it by pointing the install script to the github repo instead.

To be clear, I'm not attacking you or anything. I'm just concerned.
This is something running in automated pipelines inside internal networks, and inside docker containers that have will have access, in many cases, to organizational secrets, user data....etc
Automatically executing a script retrieved from a 3rd party website with an unknown security posture is a lot of risk. And is a juicy target for data exfiltration.

security is a spectrum - even trusted CDNs have supply chain risk.
regarding the domain it is very hard to lose one with our current setup:

unique password for our domain registrar
mult-factor auth setup
multiple credit cards on file in case one fails purchase
auto-renewal turned on
trusted registrar that is 16 years old, profitable, and not VC-funded
whois privacy
dedicated domain ONLY for serving up the binary and installer. no other code runs on that domain/server.

that said, we did think about what you are discussing but my conclusion is the opposite of yours. the control of serving over your own domain has MORE strength than serving over a 3rd party CDN.
if we served over a 3rd party CDN, an attacker would only need to gain access to our credentials of that CDN to execute a supply chain attack - there are many many historical examples of this happening in the real world.
if we serve over our own domain, they need to somehow determine where our service is hosted, and then gain access to the server - which requires a combination of an ssh key, password, and a multi-factor step. there are comparatively few historical examples of this happening in the real world.
we also publish the code for dotenvx.sh publicly - for audit reasons, and for others to try and find potential security risks - at https://github.com/dotenvx/dotenvx.sh. it's readable and infinitely less complex than the code running CDNs. (there is a good argument to be made that CDNs are MORE exploitable because their code is private, always/often changing, and they have many more features/complexity. complexity = security risk.)
in general, i disagree with the assumed premise that centralized is safer.
all that said, executing an installer.sh script is not for everyone and I applaud those who instead install themselves, but as long as we are discussing along those lines we should be discussing installing and building directly from source code you've personally audited yourself. in other words, there is a spectrum here that is useful to different teams. we've tried to serve that spectrum well. an enterprise is going to put older proven stable versions of dotenvx behind their own artifactory (or the like). hobbyists and small teams are going to run curl/brew/npm. and someone extra security minded like yourself is going to download from our releases and unpack the lib yourself. also, keep in mind our current target are hobbyists/small teams. they are willing to experiment with new improvements to software far ahead of enterprises.
i do need to get the checksum file added back into our publishing process. will do so soon.
also, i did feel your post was too alarmist. please keep in mind, i've personally maintained a library with huge supply chain attack risk for the past ten years - https://www.npmjs.com/package/dotenv. ultimately, a lot of this boils down to trust, which is earned only after time and action - something i intend to earn from the community as i did with dotenv.


[BUG] binding=False disallows modifying __qualname__

Describe the bug
# cython: binding=False
def f():
    def g():
        pass
    def h():
        pass
    g.__qualname__=h.__qualname__
    print(g.__qualname__)
f()

This used to run well in previous cython versions, but not latest master.
Code to reproduce the behaviour:
No response
Expected behaviour
No response
OS
Linux
Python version
3.11.10
Cython version
latest master
Additional context
For a more practical situation, this happens in function decorators.
# cython: binding=False
from functools import wraps
def f(h):
    @wraps(h)
    def g():
        pass
    return g
@f
def h():
    pass

Will suggest the change to SageMath then.


What is DB?

Sorry for the dumb question, but what is DB in the code examples?
E.g.:
DB.ack_event(MyListener, stream_name, event_number)
Is this part of elixir? I'm still learning it.

https://github.com/exponentially/extreme/blob/master/test/listener_test.exs#L9 DB is wrapper module around some persistence. For testing purposes we are using Agent but in production you can use whatever suites you the best (dets, Postgrex, ...)

Right, got it.
Thanks.


[ConstraintSystem] Enforce TVO_CanBindToPack, and diagnose pack references outside of pack expansion expressions.

This changes catches the mistake of referencing a value pack without any keywords or with each outside of a pack expansion expression:
func packOutsideExpansion<each T>(_ t: repeat each T) {
  _ = t // error: pack reference 'T' can only appear in pack expansion
  _ = each t // error: pack reference 'T' can only appear in pack expansion
}

This is done by enforcing TVO_CanBindToPack when binding a type variable to a fixed type. If the binding is a PackType or a PackArchetypeType, solving the constraint will either fail, or apply a constraint fix in diagnostic mode for the invalid pack reference. During CSGen, type variables for decl refs and unresolved dot refs will be marked as TVO_CanBindToPack if there is an enclosing pack expansion expression.
This subsumes https://github.com/apple/swift/pull/61777

@swift-ci please smoke test

@swift-ci please smoke test macOS


Keeping a log file

First of all thanks for your incredible tool for downloading bbb sessions I personally prefer to have videos offline.
I was downloading 9  bbb sessions simultaneously separately in 9 different Terminals (I know, I should have used the batch downloading option). I ran them  and went to sleep and it seems when I was sleeping there was a power outage.
So now I don't know which one of them is finished successfully and which ones are not. A log file to keep track of them would be appreciated.

Thank you very much :)
First of all, I would recommend you using bbb-dl-batch. Because it already logs failures and successfully downlaoded sessions. And bbb-dl itself is already highly parallelized, so running multiple bbb-dl at the same time will not improve speed much, or could even slow down the process.
Yes, we could add a log option, and finally move to python standard logging. (I do not know why I did not do it already).
But for now you could use piping, that your terminal already provids.
like running bbd-dl like:
bbb-dl options > path_to_log_file.txt
or if you are on linux you could log to both, the terminal and a log file like this:
bbb-dl options | tee path_to_log_file.txt
you can use this till we add a logging option


only one service in discover mode

Describe the bug
I use knife4j-gateway-spring-boot-starter on gateway project, In the discover mode, only one of multiple services is discovered, probably because the order values of these services are the same.
maven&version
<dependency>
    <groupId>com.github.xiaoymin</groupId>
    <artifactId>knife4j-gateway-spring-boot-starter</artifactId>
    <version>4.2.0</version>
</dependency>

<spring-boot.version>2.6.13</spring-boot.version>
<spring-cloud.version>2021.0.5</spring-cloud.version>

test

code

suggestions
order by service-name

新版本已修复,>4.2.0即可,此issue关闭


[Docs] Migrate to docker

Environment: gitea 1.7.5, linux, sqlite.
I want to migrate to docker.
I couldn't find instructions, so I just copied all the files to the relevant places. The container starts, but won't serve data. Something about a "corrupted content error". So obviously I made some mistakes.
I'm sure many people like me started using gogs/gitea the normal way, and then want to "dockerise". Are there instructions for this anywhere, or any tips to follow?

This script is the procedure I used for converting from the debian package to docker (you should run it as root):
#!/bin/sh
set -e -x

USER_UID=${USER_UID:-1000}
USER_GID=${USER_GID:-1000}

# Build initool for automatically updating config
# You need `mlton` installed (package mlton in Debian/Fedora variants)
if [ ! -x initool-0.10.0/initool ]; then
	if ! command -v mlton >/dev/null 2>&1; then
		echo "Missing dependency: mlton" >&2
		echo "Available on Debian and Fedora as the mlton package" >&2
		exit 1
	fi
	wget -O- https://github.com/dbohdan/initool/archive/v0.10.0.tar.gz | tar -zxf - && make -C initool-0.10.0
fi
initool=$(realpath initool-0.10.0/initool)

# Helpers for modifying app.ini
iniset() {
	section=${1%.*}; key=${1##*.}
	"$initool" s gitea/conf/app.ini "$section" "$key" "$2" > app.ini && \
		mv app.ini gitea/conf/app.ini
}

iniunset() {
	section=${1%.*}; key=${1##*.}
	"$initool" d gitea/conf/app.ini "$section" "$key" > app.ini && \
		mv app.ini gitea/conf/app.ini
}

# Copy existing gitea config
# conf, templates, and public are symlinks to the default data (already handled by the docker container)
# indexers can be excluded, they'll be regenerated at first run
rsync -aL --no-l --progress --exclude /gitea/conf --exclude /gitea/public --exclude /gitea/templates --exclude /gitea/indexers --exclude /gitea/data/indexers /var/lib/gitea gitea/

# Restructure to match docker's default layout
cd gitea

mv gitea/repositories git
mv gitea/.ssh git
mv gitea/data/* gitea/custom/* gitea
rmdir gitea/data gitea/custom

# These settings need updating to the correct paths
iniset repository.ROOT /data/git
iniset repository.local.LOCAL_COPY_PATH /data/gitea/tmp/local-repo
iniset repository.upload.TEMP_PATH /data/gitea/uploads
iniset server.APP_DATA_PATH /data/gitea
iniset server.LFS_CONTENT_PATH /data/git/lfs
iniset indexer.ISSUE_INDEXER_PATH /data/gitea/indexers/issues.bleve
iniset database.PATH /data/gitea/gitea.db
iniset session.PROVIDER_CONFIG /data/gitea/sessions
iniset picture.AVATAR_UPLOAD_PATH /data/gitea/avatars
iniset picture.REPOSITORY_AVATAR_UPLOAD_PATH /data/gitea/repo-avatars
iniset attachment.PATH /data/gitea/attachments
iniset log.ROOT_PATH /data/gitea/log

# These settings need to be removed
iniunset server.STATIC_ROOT_PATH

# Fix permissions
chown -R "${USER_UID}:${USER_GID}" .

# If you're using a named volume instead of a host folder
# You'll need to copy the data into the volume
#docker run --rm -v "gitea:/gitea-new" -v "$PWD:/gitea-old" alpine:latest cp -a --progress /gitea-old/* /gitea-new/

The resulting restructured data will be in located in the current working directory, named "gitea"
If you're using sqlite, you should be able to just run using the docker-compose.yml in the install docs
If you're using an external database, you'll likely need to modify the database settings in gitea/gitea/conf/app.ini

@NHellFire Thanks. I've since moved to docker the hard way (recreating everything from scratch).
So I didn't test your script, but hope it will help others. And it should be in the docs.

@NHellFire do you like to create a pull to add this into the docs?

It differs a lot for different package systems. The general method is copying database, copying data directory, copying and editing app.ini.


Xcode 7.3 issue

ERROR ITMS-90596: "Invalid Bundle. The asset catalog at 'Payload/MagicBricks.app/Frameworks/Applozic.framework/Assets.car' can't be read. Try rebuilding the app with a non-beta version of Xcode and submit it again.

2 ways either build new fw in older version
or integrate in older version so that it will build according to xcode version

ERROR ITMS-90689: "Invalid Info.plist key. The key 'UIRequiredDeviceCapabilities' in bundle MagicBricks.app/Frameworks/Applozic.framework is invalid for frameworks" : 	651f225


Standard indentation and grammar correction

Codecov Report
Patch coverage: 95.00% and project coverage change: -4.15 :warning:

Comparison is base (e560bbb) 96.68% compared to head (0b6765e) 92.54%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #105      +/-   ##
==========================================
- Coverage   96.68%   92.54%   -4.15%
==========================================
  Files          12       12
  Lines         694      684      -10
  Branches       96       92       -4
==========================================
- Hits          671      633      -38
- Misses         19       45      +26
- Partials        4        6       +2

Flag
Coverage Δ

acceptance
79.38% <85.00%> (-4.34%)
:arrow_down:

unit
90.05% <95.00%> (-3.17%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

Mainframe3270/keywords/assertions.py
100.00% <ø> (ø)

Mainframe3270/keywords/screenshot.py
100.00% <ø> (ø)

Mainframe3270/keywords/wait_and_timeout.py
100.00% <ø> (ø)

Mainframe3270/librarycomponent.py
100.00% <ø> (ø)

Mainframe3270/utils.py
100.00% <ø> (ø)

Mainframe3270/py3270.py
82.39% <66.66%> (-9.46%)
:arrow_down:

Mainframe3270/keywords/commands.py
100.00% <100.00%> (ø)

Mainframe3270/keywords/connection.py
95.12% <100.00%> (-3.63%)
:arrow_down:

Mainframe3270/keywords/read_write.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Volslicer asset is too Thin

Hedwig UI:
https://goat.niaid.nih.gov:7333/sessions/U2Vzc2lvbjoyNTE1/samples
Sample name: SARsCov2_B
Pipeline run:
http://<IP_ADDRESS>:8080/default/flow-run/25ce4b87-b686-4f1b-a371-15554a41fb58
File Path:
\ai-fas12\RMLEMHedwigDev\Assets\RTB\darrellh\filipgranitn2-2022-1117-BRT_Testing\Cryo-TEM-Tomo-2022-1117-Nov_BRT_testing\SARsCov2_B\SARsCoV2_1
Review by Bryan on 11/17/2022
VolSlicer volume  looks too thin, doesn't look like even binned down that it's the thickness that you supplied (800)

Tested after the fix:
Rerun SARsCov2_B
Pipeline run: http://<IP_ADDRESS>:8080/default/flow-run/4b73a453-4e50-44d2-8887-3e71c4b10900
Both runs successfully completed, and the assets VolSlicer and Reconstructed Movie were correct.
Hedwig UI:
https://goat.niaid.nih.gov:7333/sessions/U2Vzc2lvbjoyNTE1/samples
https://goat.niaid.nih.gov:7333/volslicer/UmVjb3JkOjE3NDE5Mg==
https://goat.niaid.nih.gov:7333/recmovie/UmVjb3JkOjE3NDE5Mg==
https://goat.niaid.nih.gov:7333/tiltmovie/UmVjb3JkOjE3NDE5Mg==
See Hansen , Bryan, Feedback:
The reconstructed movie is correct now. VolSlicer looks correct now too
The issue is fixed

fixed in https://github.com/niaid/image_portal_workflows/tree/fix_recon_movie


Fix the index to start with 0

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

Comparison is base (a2b06fc) 37.81% compared to head (c4b9cd3) 37.81%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #506   +/-   ##
=======================================
  Coverage   37.81%   37.81%
=======================================
  Files          50       50
  Lines        3184     3184
=======================================
  Hits         1204     1204
  Misses       1851     1851
  Partials      129      129

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


Add datadog provider in https://github.com/GoogleCloudPlatform/terraformer?

https://github.com/GoogleCloudPlatform/terraformer
Terraformer new cli tool for export all configuration to tf and tfstate files.
It's very generic and work with many providers. Used provides binary for get all schema.
Maybe you want add datadog provider instead write/maintain other project?

@sergeylanzman
Thanks for notification.
I try to add datadog provider to GoogleCloudPlatform/terraformer

@sergeylanzman
Would you mind  resolved this issue?

yes Thank you!


Importing @sanity/nuxt-loader creates a "Package import specifier" error

Describe the bug
A "Package import specifier" error appears when viewing a page with @sanity/nuxt-loader:
Package import specifier "#build/app.config.mjs" is not defined in package /home/projects/github-orsmgg/node_modules/nuxt/package.json imported from /home/projects/github-orsmgg/node_modules/nuxt/dist/app/config.js
To Reproduce
See Stackblitz reproduction: https://stackblitz.com/edit/github-orsmgg?file=package.json,app.vue
Steps to reproduce the behavior:

Create a fresh site using a Nuxt starter
Install nuxt-loader:
npm install @sanity/nuxt-loader
Import the nuxt-loader package:
import { createQueryStore, useEncodeDataAttribute } from '@sanity/nuxt-loader';
See error:

Expected behavior
I wouldn't expect an error to appear for simply importing the package. If you remove the import, the error disappears.
Which versions of Sanity are you using?
@sanity/cli (global) 3.25.0 (up to date)
@sanity/nuxt-loader 1.7.4 (up to date)
@sanity/overlays 2.3.6 (up to date)
What operating system are you using?
The error appears on the StackBlitz reproduction, but it also appears on a local project using Windows 10.
Which versions of Node.js / npm are you running?
npm: 10.2.3
Node: v18.18.0
Additional context
There is a weird interaction I've noticed where it only seems to break on a hard refresh of the page that has the import, or if you navigate to that page using <a>, rather than <NuxtLink>.
If you navigate to the page that has the import using <NuxtLink>, the error doesn't appear.
I've created a second reproduction to show this:
https://stackblitz.com/edit/github-16x3sm?file=package.json,app.vue,pages%2Findex.vue,pages%2Ftest.vue
I'm new to Sanity and wanted to try out the visual editing feature.

I have the same issue. It is caused by the useAsyncData import here. As far as I know Nuxt imports should use #imports and I see other libs do that (such as this one). However, I tried changing the import locally and it did not work for me. Instead, it resulted in another error:
Package import specifier "#imports" is not defined in package<EMAIL_ADDRESS>imported from<EMAIL_ADDRESS>

As @blowsie suggested, please migrate to @nuxtjs/sanity!


Fix broken test which relied on DNS resolution #1962

Switched to testing by way of the static_configs rather than dns_sd_config parameter.  Verified that the revised test both passes without network access, and also still catches the bug it's supposed to cover.

Awesome! Thank you for the quick fix.


Modify Contributing.md and using it in a different project

Hi all,
I need to create contributing guidelines for the hIPPYlib project of which I am the main developer.
I was wondering if I can use a opportunely modified version of the MFEM Contributing.md file in my project.
If so, how would you like me to give credits to the authors of the Contributing.md file and to the MFEM project for using such resource?
Thank you!
Umberto

Hi Umberto,
I think it is fine to base your CONTRIBUTING.md on the one from MFEM. You can mention something like "Adopted from MFEM", but you don't have to IMHO.
Glad to see the progress on hIPPYlib :).
Tzanio


Have CustomRedirectResult use IAuthorizationParametersMessageStore

Fixes 4963
At this point we cannot accept PRs for new features, only bugfixes. Thanks!
What issue does this PR address?
Does this PR introduce a breaking change?
Please check if the PR fulfills these requirements

[ ] The commit follows our guidelines
[ ] Unit Tests for the changes have been added (for bug fixes / features)

Other information:

Ok, I caught this one before it auto closed! We will review it, I promise!


Headset Adjustment

Overview
I recently came back to this and wanted to use the Headset Adjustment scene. The scene and the screen space/camera canvas modes both don't work.
Expected Behavior
HeadsetAdjustment should show a border on the camera on startup and load the next level on command.
Actual Behavior
The scene shows nothing except the cursor (whyever there is even a cursor object in there). There is no border image in the entire project as far as I can see. Trying to use my own image with a screen space or camera space canvas doesn't work, as it is invisible for the hololenscamera. Also I cannot put any camera inside the camera field of the canvas. It just silently fails to do it and the field stays empty.
Steps to reproduce
just start the HeadsetAdjustment scene and try.
Unity Editor Version
2017.3.p3
Mixed Reality Toolkit Release Version
2<IP_ADDRESS> (But this scene doesn't seem to have changed since then?)

tried again with the latest mrtk hotfix version. Now at least the camera assignment to a canvas seems to work.

it appears that this scene lost it's display canvas sometime late 2017. I'll add a prefab that can be added to the camera (where it was in the earlier version of the scene).

This was released in the 2<IP_ADDRESS> release candidate