Clarify definitions of "positive" and "negative" strands

Greetings,
We are adding a field to the FHIR Sequence resource, to differentiate positive/negative (aka watson/crick) strands. The definitions we are proposing: "An absolute reference to a strand. The Watson strand is the strand whose 5'-end is on the short arm of the chromosome, and the Crick strand as the one whose 5'-end is on the long arm".
HL7 Genomics Committee members suggested that we submit a comment here, to see if it might make sense to include "watson strand" and "crick strand" into Sequence Ontology?
Thank you.

Hi @rhdolin and Terrence,
I think it makes sense to add these. What do you think of adding the terms with the following info?
name: Watson_strand
def: "An absolute reference to the   strand. When a chromosome has p and q arms, the Watson strand is the trand   whose 5'-end is on the short arm of the chromosome. Of note, the term 'plus   strand' is typically used for the Watson strand, but can be changed in   reference sequences based and is therefore not an exact synonym."   [PMID:21303550]
comment: Added as per GitHub Issue   Request #419   (https://github.com/The-Sequence-Ontology/SO-Ontologies/issues/419)
synonym: "Watson strand" EXACT   []
synonym: "Top strand" EXACT []
synonym: "Forward strand" EXACT   []
synonym: "Plus strand" BROAD []
is_a: SO:0000830 ! chromosome_part
name: Crick_strand
def: "An absolute reference to the   strand. When a chromosome has p and q arms, the Crick strand is the trand   whose 5'-end is on the long arm of the chromosome. Of note, the term 'minus   strand' is typically used for the Crick strand, but can be changed in   reference sequences based and is therefore not an exact synonym."   [PMID:21303550]
comment: Added as per GitHub Issue   Request #419   (https://github.com/The-Sequence-Ontology/SO-Ontologies/issues/419)
synonym: "Crick strand" EXACT   []
synonym: "Bottom strand" EXACT   []
synonym: "Reverse strand" EXACT   []
synonym: "Minus strand" BROAD   []
is_a: SO:0000830 ! chromosome_part
Thanks,
Dave

but can be changed in reference sequences based and

this seems like it's missing some wording?
How about:

Of note, the term "plus strand" is typically based on a reference sequence where it's preferred for the plus strand to be the Watson strand, but might not be and "plus strand" is therefore not an exact synonym." [PMID:21303550]

Thanks @davidwsant. Agree with @murphyte 's revisions, and supportive of the additions.

Hi guys,
Thanks for the help. How does this look? Also, do you agree with using BROAD synonym for "plus" and "minus"?
name: Watson_strand
def: "An absolute reference to the strand. When a chromosome has p and q arms, the Watson strand is the trand whose 5'-end is on the short arm of the chromosome. Of note, the term "plus strand" is typically based on a reference sequence where it's preferred for the plus strand to be the Watson strand, but might not be and "plus strand" is therefore not an exact synonym." [PMID:21303550]
comment: Added as per GitHub Issue Request #419 (#419)
synonym: "Watson strand" EXACT []
synonym: "Top strand" EXACT []
synonym: "Forward strand" EXACT []
synonym: "Plus strand" BROAD []
is_a: SO:0000830 ! chromosome_part
name: Crick_strand
def: "An absolute reference to the strand. When a chromosome has p and q arms, the Crick strand is the trand whose 5'-end is on the long arm of the chromosome. Of note, the term "minus strand" is typically based on a reference sequence where it's preferred for the minus strand to be the Crick strand, but might not be and "minus strand" is therefore not an exact synonym." [PMID:21303550]
comment: Added as per GitHub Issue Request #419 (#419)
synonym: "Crick strand" EXACT []
synonym: "Bottom strand" EXACT []
synonym: "Reverse strand" EXACT []
synonym: "Minus strand" BROAD []
is_a: SO:0000830 ! chromosome_part
Thanks,
Dave

one typo in both definitions:
"the Watson/Crick strand is the trand "
Otherwise that reads well.

Thank you guys for the suggestions and comments. Watson strand has been given the ID SO:0002262 and Crick strand has been given the ID SO:0002263. As usual, these should be present on the SO Browser within about 24 hours.
Thanks,
Dave


Bash script: Calling directly works, via cron has issues

Hello,
So fist, thank you for everything you guys did on this nice software. Some days ago I decided to automate the log generation processes and for that I made a bash script, to run every month, that:

Lists all vhosts under apache
For each vhosts reads every log time modified on the last 35 days
Uses grep to filter everything from the last month
Pipes everything into goaccess

If I manually run the bash script it creates my reports properly. However if I use cron the run the bash script it just outputs to the files goaccess help / the same as running without any options.
Since the script runs fine manually the issue must be with cron and the environment used there. Why is this happening? Any tips?
My cron: 00 01 1 * * /root/scripts/traffic-vhost-report.sh
Thank you!

Nevermind guys, this issue was already answered at #647. Exactly my issue.


RISCV CPU bug when booting up 24.04 disk image

Describe the bug
When using 8 RISCV ATOMIC CPUs to boot up a 24.04 ubuntu disk image created by following the riscv-fs guide, the kernel encounters CPU related bug after gem5_init.sh.
Affects version
both stable <IP_ADDRESS> and develop to commit# 2fc44a5
gem5 Modifications
None
To Reproduce

Build a disk image using the riscv-fs guide on an 24.04 ubuntu host.
Input the path to the disk image to the following script and run it with stable <IP_ADDRESS> or develop(2fc44a5) gem5

from m5.objects.DRAMInterface import DDR4_2400_16x4
from gem5.components.memory.memory import ChanneledMemory
from gem5.components.boards.riscv_board import RiscvBoard
from gem5.components.cachehierarchies.classic.no_cache import NoCache
from gem5.components.processors.simple_processor import SimpleProcessor
from gem5.isas import ISA
from gem5.components.processors.cpu_types import CPUTypes

from gem5.simulate.simulator import Simulator

from gem5.resources.resource import WorkloadResource, obtain_resource,DiskImageResource

# input the path to the disk image here
disk_image_path = ""

processor = SimpleProcessor(
    cpu_type = CPUTypes.ATOMIC,
    isa=ISA.RISCV,
    num_cores=8
)
cache = NoCache()
memory = ChanneledMemory(DDR4_2400_16x4, 1, 128, size="8GiB")
board = RiscvBoard(
    clk_freq="2GHz",
    processor=processor,
    cache_hierarchy=cache,
    memory=memory,
)

workload = WorkloadResource(
    function = "set_kernel_disk_workload",
    parameters = {
        "kernel" : obtain_resource(resource_id="riscv-linux-6.6.33-kernel"),
        "disk_image" : DiskImageResource(local_path=disk_image_path,
            root_partition="1"),
        "bootloader" : obtain_resource(resource_id="riscv-bootloader-opensbi-1.3.1")
    }
)

board.set_workload(workload)

simulator = Simulator(
    board=board
)

simulator.run()

print("all done!")

Terminal Output
board.terminal:
[    0.264981] devtmpfs: mounted
[    0.265440] Freeing unused kernel image (initmem) memory: 2200K
[    0.265460] Run /sbin/init as init process
Kernel booted, In gem5 init...
Starting systemd...
[    0.304812] systemd[1]: System time before build time, advancing clock.
[    0.311767] systemd[1]: systemd 255.4-1ubuntu8 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[    0.311804] systemd[1]: Detected architecture riscv64.

Welcome to Ubuntu 24.04 LTS!

[    0.312429] systemd[1]: Hostname set to <ubuntu>.
[    0.394446] BUG: spinlock wrong owner on CPU#6, swapper/6/0
[    0.394456]  lock: 0xffffffff81487480, .magic: dead4ead, .owner: swapper/2/0, .owner_cpu: -1
[    0.394470] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 6.6.33 #1
[    0.394481] Hardware name: riscv-virtio (DT)
[    0.394488] Call Trace:
[    0.394494] [<ffffffff80005a92>] dump_backtrace+0x1c/0x24
[    0.394506] [<ffffffff808a5362>] show_stack+0x2c/0x38
[    0.394519] [<ffffffff808b150c>] dump_stack_lvl+0x3c/0x54
[    0.394533] [<ffffffff808b1538>] dump_stack+0x14/0x1c
[    0.394546] [<ffffffff8005ea94>] spin_bug+0x80/0xb4
[    0.394560] [<ffffffff8005ecf2>] do_raw_spin_unlock+0xe4/0xfe
[    0.394574] [<ffffffff808ba80e>] _raw_spin_unlock_irqrestore+0x16/0x2e
[    0.394589] [<ffffffff80077618>] rcu_report_qs_rnp+0x86/0x100
[    0.394602] [<ffffffff8007772a>] rcu_report_qs_rdp+0x98/0xcc
[    0.394614] [<ffffffff8007b50c>] rcu_core+0x15a/0x400
[    0.394627] [<ffffffff8007b8ac>] rcu_core_si+0xc/0x14
[    0.394639] [<ffffffff800168c6>] handle_softirqs+0xfc/0x246
[    0.394654] [<ffffffff80016dda>] irq_exit_rcu+0x78/0xa2
[    0.394668] [<ffffffff808b15a4>] handle_riscv_irq+0x64/0x74
[    0.394682] [<ffffffff808b202a>] do_irq+0x56/0x7e

simerr:
src/mem/dram_interface.cc:690: warn: DRAM device capacity (32768 Mbytes) does not match the address range assigned (8192 Mbytes)
board.platform.terminal: Listening for connections on port 3458
src/arch/riscv/isa.cc:278: info: RVV enabled, VLEN = 256 bits, ELEN = 64 bits
src/base/statistics.hh:279: warn: One of the stats is a legacy stat. Legacy stat is a stat that does not belong to any statistics::Group. Legacy stat is deprecated.
src/arch/riscv/isa.cc:278: info: RVV enabled, VLEN = 256 bits, ELEN = 64 bits
src/arch/riscv/isa.cc:278: info: RVV enabled, VLEN = 256 bits, ELEN = 64 bits
src/arch/riscv/isa.cc:278: info: RVV enabled, VLEN = 256 bits, ELEN = 64 bits
src/arch/riscv/isa.cc:278: info: RVV enabled, VLEN = 256 bits, ELEN = 64 bits
src/arch/riscv/isa.cc:278: info: RVV enabled, VLEN = 256 bits, ELEN = 64 bits
src/arch/riscv/isa.cc:278: info: RVV enabled, VLEN = 256 bits, ELEN = 64 bits
src/arch/riscv/isa.cc:278: info: RVV enabled, VLEN = 256 bits, ELEN = 64 bits
board.remote_gdb: Listening for connections on port 7002
src/arch/riscv/linux/fs_workload.cc:162: info: Loaded bootloader '/home/ztpc/.cache/gem5/riscv-bootloader-opensbi-1.3.1' at 0x0
src/arch/riscv/linux/fs_workload.cc:180: info: Loaded kernel '/home/ztpc/.cache/gem5/riscv-linux-6.6.33-kernel' at 0x80200000
src/arch/riscv/linux/fs_workload.cc:199: info: Loaded DTB 'develop-m5outs/device.dtb' at 0x87e00000
src/sim/simulate.cc:199: info: Entering event queue @ 0.   Requested size: 16
src/sim/simulate.cc:199: info: Entering event queue @<PHONE_NUMBER>00.  Starting simulation...

Expected behavior
After encountering the gem5_init.sh, the CPU bug will show up in the board terminal output.
Host Operating System
Ubuntu 24.04
Host ISA
X86

It looks like you have not added the exit event handlers, this disk will throw 3 m5 exits. It looks like the simulation ended as the first exit was triggered.
For more info, check: https://github.com/orgs/gem5/discussions/1540

It looks like you have not added the exit event handlers, this disk will throw 3 m5 exits. It looks like the simulation ended as the first exit was triggered.
For more info, check: https://github.com/orgs/gem5/discussions/1540

I have a version that defined an exit event, but after taking the checkpoint, it ran into the cpu bug:
from m5.objects.DRAMInterface import DDR4_2400_16x4
from gem5.components.memory.memory import ChanneledMemory
from gem5.components.boards.riscv_board import RiscvBoard
from gem5.components.cachehierarchies.classic.no_cache import NoCache
from gem5.components.processors.simple_processor import SimpleProcessor
from gem5.isas import ISA
from gem5.components.processors.cpu_types import CPUTypes

from gem5.simulate.simulator import Simulator
from gem5.simulate.exit_event import ExitEvent

import m5
import argparse
from pathlib import Path

import sys
import os
sys.path.append(str(Path(__file__).resolve().parent.parent))
print(str(Path(__file__).resolve().parent.parent))

from workload.workload import get_workload

parser = argparse.ArgumentParser()
parser.add_argument("--checkpoint", type=str, default="m5-cpt", help="Checkpoint put here")
args = parser.parse_args()

checkpoint_output_dir = Path(args.checkpoint)
checkpoint_output_dir.mkdir(parents=True, exist_ok=True)

processor = SimpleProcessor(
    cpu_type = CPUTypes.ATOMIC,
    isa=ISA.RISCV,
    num_cores=8
)
cache = NoCache()
memory = ChanneledMemory(DDR4_2400_16x4, 1, 128, size="8GiB")
board = RiscvBoard(
    clk_freq="2GHz",
    processor=processor,
    cache_hierarchy=cache,
    memory=memory,
)
board.set_workload(get_workload())

def exit_handle():
    checkpoint_id = 0
    while True:
        print("get to exit")
        m5.checkpoint(Path(checkpoint_output_dir / f"{checkpoint_id}").as_posix())
        checkpoint_id += 1
        yield False

simulator = Simulator(
    board=board,
    on_exit_event={
        ExitEvent.EXIT:exit_handle()
    }
)

simulator.run()

print("all done!")

It took one checkpoint, then the simulation stopped due to the cpu bug.

Just an update on this bug. I was able to reproduce this issue but when I run the simulation with 1 core the simulation runs to completion. It might my a bug in the way we handle multiple cores in riscv.


include could not find load file cotire

to reproduce the error do the following Dockerfile:
from ubuntu:16.04
maintainer Nico Cesar<EMAIL_ADDRESS>
# Set the env variable DEBIAN_FRONTEND to noninteractive
ENV DEBIAN_FRONTEND noninteractive

RUN apt-get update &&  apt-get install -y git cmake python-virtualenv python-pip

RUN git clone https://github.com/lyft/envoy.git
RUN cd envoy && make
RUN cd envoy && mkdir -p build && cd build && cmake ..

and run it this way:
docker build --rm=false .
you'll get a
(...)
build succeeded.
 ---> 8bfe5ce2629a
Step 7/7 : RUN cd envoy && mkdir -p build && cd build && cmake ..
 ---> Running in 51be985c19e3
-- The CXX compiler identification is GNU 5.4.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at common.cmake:57 (include):
  include could not find load file:

    cotire
Call Stack (most recent call first):
  CMakeLists.txt:5 (include)

CMake Error at source/common/CMakeLists.txt:141 (cotire):
  Unknown CMake command "cotire".

-- Configuring incomplete, errors occurred!
See also "/envoy/build/CMakeFiles/CMakeOutput.log".
The command '/bin/sh -c cd envoy && mkdir -p build && cd build && cmake ..' returned a non-zero code: 1

You need to install cotire.

Beyond what @PiotrSikora said, the only build flows we support are the official ones in the CI directory. See the docs there. If you go outside of that we can't offer support.


Eliminate named pipe for temp WAV

In an attempt to reduce piping and possibly reduce the chance of small computer hiccups causing a drop out, the named pipe has been changed to create a .wav. Because ending recording via closing the monitoring window truncates the .wav file wrapper, a step has been added to rewrap the data into its final destination.
While not entirely elegant, this seems like a safer way of capturing the audio data.  Thoughts?

👀

@ablwr I asked your i ching app if this would work and I got
"63. Already_Fording (既濟 jì jì); After Completion; Completion"
and "01. Force (乾 qián); The Creative; Possessing Creative Power & Skill"
Does that mean I should go ahead and merge?

Think of the cast hexagram of representing the situation you are in and the transformed hexagram of the situation in which you will be, should you follow your current path as posed by your question. Yes. It furthers one to cross the great water.

I think I need an i ching bot to analyze all future pull requests for cosmic correctness


Write HA State Issues

Did a full deletion of the integration + entities.  Re-did the integration.
Serials seem different:

Things seem to be working now!
Only remaining errors are:
2021-08-08 13:43:29 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/ge_home/update_coordinator.py", line 266, in on_device_update
entity.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 457, in async_write_ha_state
raise RuntimeError(f"Attribute hass is None for {self}")
RuntimeError: Attribute hass is None for <Entity DS100880G Laundry Delay Time Remaining: >

2021-08-08 13:43:29 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/ge_home/update_coordinator.py", line 266, in on_device_update
entity.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 457, in async_write_ha_state
raise RuntimeError(f"Attribute hass is None for {self}")
RuntimeError: Attribute hass is None for <Entity DS100880G Laundry Machine State: Off>

2021-08-08 13:43:32 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/ge_home/update_coordinator.py", line 266, in on_device_update
entity.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 457, in async_write_ha_state
raise RuntimeError(f"Attribute hass is None for {self}")
RuntimeError: Attribute hass is None for <Entity SR371810N Laundry Delay Time Remaining: >

2021-08-08 13:43:32 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/ge_home/update_coordinator.py", line 266, in on_device_update
entity.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 457, in async_write_ha_state
raise RuntimeError(f"Attribute hass is None for {self}")
RuntimeError: Attribute hass is None for <Entity SR371810N Laundry Delay Time Remaining: >

So:
Dryer.Delay Time
Dryer.State
Washer.State
Unsure if they're worth investigating in a different issue, because this one seems to be ready to close!
Originally posted by @steveredden in https://github.com/simbaja/ha_gehome/issues/28#issuecomment-894839020

Are there any errors before these start occuring?  Usually, I've seen an issue at startup that eventually results in this happening.

Deleted the integration; full wipe of entities/devices; restarted core; reinstalled integration (no errors); reloaded integration (no errors).
Think we can just chalk it up to lingering duplicate devices, etc.


loggedIn overrides bot name provided via hubot --name NAME ...

This line in loggedIn sets robot.name to the auth username:
https://github.com/loafoe/hubot-matteruser/blob/4f560900146161521a2bbfb12f2cd517b6e8e47b/src/matteruser.coffee#L93
This overrides a value set via hubot --name NAME ....
Should that be a bug? It is for me, at least. At my company we use a corporate LDAP for auth to our Mattermost team. I want the bot to respond to the name "bot", but the access account given me by our operations team is "joybot2". In my copy of hubot-matteruser I remove this line (via this patch: https://gist.github.com/trentm/3decef3c09278b18863744759693af20).
I'm not sure if you'd consider this a bug for this project. Just removing this line would potentially (likely?) break existing users, so either you'd want to make it opt-in or do a major version bump.
Thanks for the library!

@trentm this is a breaking change, but I agree that it should not ignore the --name variable. The instructions we provide generate a script with the --name parameter as default so I will remove the line and will document it in the release notes of the next major release, thanks!

@trentm will be changed release v4.1.0


Need burst library!

Hi,
I try to compile SDNUOJ but it need Burst. Can anyone please share the Burst library. I googled but can't find it.
Thanks a lot.

@burstinair make it open-source and upload it to nuget?

ok, i will make it available soon

Thanks a lot :)

Hi @burstinair ,
You may busy to make Burst project opensource now, can you please share the Burst dll.
I'm sorry if my request bothering you.
Thanks a lot.

Hi, @riverstore
Burst Library is now available here
and you can get the dlls in path /Release

Thanks a lot :+1:


geocoding: ValueError: No objects were found for Czech Republic.

cz = geocode_countries("Czech Republic")
c = cz.get_centroids()

Same error for "Czech".
"CZ" - ok

Fixed with geocoding data update.
cz = geocode_countries("Czech Republic")
cz.get_geocodes()

Out:

id
country
found name

51684
Czech Republic
Česko


cannot add a decoration for a command undefined with no marker

 ERR cannot add a decoration for a command undefined with no marker: Error: cannot add a decoration for a command undefined with no marker
    at c.registerCommandDecoration (vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1934:14829)
    at c.registerMarkDecoration (vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1934:11613)
    at vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1934:11322
    at p.invoke (vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:83:145)
    at l.deliver (vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:83:2266)
    at d.fire (vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:83:1844)
    at m.addMark (vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:656:1889)
    at Ui.addBufferMarker (vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3081:6583)
    at vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1697:37176
    at p.invoke (vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:83:145)
    at l.deliver (vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:83:2266)
    at d.fire (vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:83:1844)
    at i.tryFinish (vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1697:34851)
    at i.processLineInternal (vscode-file://vscode-app/Users/meganrogge/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1697:33723)

repro is to run the VS Code build task and open the dev tools console. You shouldn't see this error


jGRASP warns about unsupported Java distribution

Somewhat similar to #154, we get a warning when starting jGRASP about unsupported Java; however, rather than being about the particular version, the warning is about the "vendor." In order to avoid the warning, we would need to either:

Install a "supported" install (Oracle, AdoptOpenJDK, etc.)
Use the jGRASP that bundles a JDK

Do we want to put in the effort to avoid this warning? If so I think just used the download with a bundled JDK would be easiest.

jGRASP has confirmed privately that they will consider this OpenJDK build for inclusion in their next release, and will be adding a "Don't show warning again".

jGRASP 2.0.6 beta 3 no longer warns about the Ubuntu JDK. Closing this in favor of #348 when it's released.


Support for Python 3.12

Motivation
The toolchain does not support Python 3.12. The latest version we support is 3.10.
Proposal

[ ] Identify required updates.
[ ] Implement changes.

[ ] Try to remove the version variable on the next theme release.


"Configure mod" crashes with Heroes Conversion

Trying to open the Heroes mod's configuration window crashes the Mod Manager. It works on the old SADX Mod Manager.
The error is System.ArgumentException: ''0-General' is not a valid value for property 'Name'.'

Fixed in 0b4577287fcbb62f40fc298b462670e6390a24ce


Add connecting to a running headless server.

Fix #201
Use dlv connect "address" to connect.

Not sure why the linux test is failing here.

Whoops. That's what I get for going too fast.

Merged, thanks!


what version of Visual Studio to use, for both Sensor SDK and body tracking SDK?

Hi, there,
From this page:
https://github.com/microsoft/Azure-Kinect-Sensor-SDK/blob/develop/docs/building.md
It is mentioned that we shall use VS2017 in order to build and install the sensor SDK.
However, from this page:
https://docs.microsoft.com/en-us/azure/kinect-dk/body-sdk-setup
It is recommended we install the VS redistributable for VS 2015.
What is this for, for the Depth engine or Nvdia card?
So, If I want to build the source for both Sensor SDK and body tracking SDK, what version of VS to use?
If I choose to use MSI, this means I don't have the ability to compile but can use the library directly. In this way, I can use either VS 2015 or VS 2019, correct?

Thanks.

There is a distinction.

To compile the SDK itself
To compile your own applications using the SDKs (core sensor and body tracking)

The first link you provided is to compile the core Kinect SDK itself. While you can technically do it, it is a very rare activity. I recommend you follow the instructions given at that link.
The second link you provided is to compile your own applications using the body tracking SDK. The Body Tracking DLL and libraries need the VS redistrib. Luckily the VS redistrib has now been unified and this unified VS redistrib for 2015-2019 is often automatically installed on Windows 10 via Windows Update. You can also download this unified VS redistrib for 2015-2019 from many locations like https://visualstudio.microsoft.com/downloads/
It is not possible to compile the body tracking SDK itself. It is closed-source.

Thank you for your answers.  Just to confirm, below is what I can do:

download MSI for both Kinect SDK and body tracking SDK
download the VS redistrib as suggested by the page, for VS 2015
Use VS 2019, and the 2015 redistrib is compatible with VS 2015.

Is this correct? Thanks.

Yes. These two MSI's will give you the DLLs and libraries needed to compile your own applications.
Yes. You will need the VS redistrib to run your own applications that are compiled/linked with (1). You can compile without it, but when its time to run, you need the redistrib.
I'm a bit unclear what you are asking. The runtime redist and the ABI are specific and versioned. You do have to follow the rules. https://docs.microsoft.com/en-us/cpp/porting/binary-compat-2015-2017?view=vs-2019


oc rsh breaks when using kubecolor

Expected Behavior
One should be able to successfully get a container shell without the presentation be screwed
Current Behavior
I can't work when using kubecolor is set as an alias for oc command as the shell is kind of in a corrupted presentation

This is how it works when the alias is removed:

Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

Operating System: MacOS 14.4.1 (23E224)
kubectl version: Client Version: 4.14.3
kubecolor version: 0.3.0
zsh 5.9 (arm-apple-darwin23.0.0)

Thanks for reporting this @dijarvrella!
Definitely a bug

Hi @applejag and @prune998 I know you fixed this problem as I tested as soon as you merged the PR but I see this resurfacing. Can you please also confirm(see image below for reference):

Thanks for reporting back.
Can you just confirm the exact command executed by orsh alias ?
The patch for the rsh command is still in the code at https://github.com/kubecolor/kubecolor/blob/main/command/subcommand.go#L68, so something else is at play here...
Your shell / terminal also seems to be adding coloring... could it be a side effect ?
Can you do the same but using plain oc (with no alias for kubecolor ?
(I have no OpenShift to test with so far... Not sure about @applejag ... )

There we go, @dijarvrella. That should solve it :)
@prune998 I think we can do a v0.3.3 release. Might take a little while before our other PRs are ready to be merged

Release done. Please upgrade to v0.3.3

Sorry guys, didn't have the chance to see the messages as I was very busy. Works perfectly now! Thank you and great job 👏🏻🙌🏻


lower-level v1.DatastoreClient class under the hood ??

This may not be an error, but it is a point of confusion.
What is the purpose of all the code within the subdirectory "v1"? Its main content seems to be the class "DatastoreClient", defined in the file named "datastore_client.js".
In the docs describing the Datastore constructor, we have:

Idiomatic class for interacting with Cloud Datastore. Uses the lower-level
v1.DatastoreClient class under the hood.

v1.DatastoreClient is listed in "classes".
The v1.DatastoreClient class by itself seems to provide similar or the same functionality as the main export Datastore, but at a lower level.
However, the statement that the main export Datastore "uses the lower-level v1.DatastoreClient class under the hood", is not true. The only bit used is the static class member scopes, which is defined as (a getter for) the following array:
  static get scopes() {
    return [
      'https://www.googleapis.com/auth/cloud-platform',
      'https://www.googleapis.com/auth/datastore',
    ];

I am scratching my head, asking myself what is the purpose of this lower-level v1.DatastoreClient class? What are the use cases where one might want to use it?
(I have actually just stumbled across it while scouring for hints on handling errors: What types of errors are possible to occur, and how should they be handled?
The specific error I came across today was a "deadline exceeded". It would be really good to have a comprehensive guide on what different error types mean and how to best respond to them - apart from the obvious: retrying until successful.)
Environment details

OS: unimportant
Node.js version: unimportant
npm version: unimportant
@google-cloud/datastore version: 1.4.0

Steps to reproduce

Read the docs, looking for hints on what types of errors to expect and how to best handle them.
See reference to an enigmatic "lower-level v1.DatastoreClient class", stated to be "used under the hood".
???
PROFIT

We do actually use it! :) All requests that we make from the various hand-made API methods funnel through this request function. That creates the "GAPIC" client (which is what the auto-generated, v1 directory is).
Many years ago, we had one, big auto-generated library that included the code for all of the API services. There was nothing idiomatic about it-- no care was taken to the conventions of the language. So, we set out to create hand-made APIs, one by one. Datastore was one of the first, but others quickly followed. Storage, Pub/Sub, BigQuery, etc.
We started to hear that some people actually liked the generated libraries, because for whatever reasons, their use case scooted around our goal of 99% common-case coverage. In order to support that last 1%, we expose the generated code, so that every possible dial that can be turned and option that can be configured is accessible.
Regarding the error handling discussion, we can keep that over here: https://github.com/googleapis/nodejs-datastore/issues/83

Ah, I see! Thank you, I overlooked this single entry point.
Now I can finally try to find out and see what is going on there under the hood when I want!
:running:


wasm build failed

  cargo:warning=         ^~~~~~~~~
  cargo:warning=1 error generated.
  exit code: 1

  --- stderr
  fatal: not a git repository (or any of the parent directories): .git

  error occurred: Command "clang" "-Os" "-ffunction-sections" "-fdata-sections" "-fPIC" "--target=wasm32-unknown-unknown" "-I" "/home/vsts/work/1/s/samples/wasm/target/wasm32-unknown-unknown/release/build/libssh2-sys-40529b05f84fbebf/out/include" "-I" "libssh2/src" "-I" "/home/vsts/work/1/s/samples/wasm/target/wasm32-unknown-unknown/release/build/libssh2-sys-40529b05f84fbebf/out/build" "-I" "/home/vsts/work/1/s/samples/wasm/target/wasm32-unknown-unknown/release/build/libz-sys-fe9cf94fa7d719b6/out/include" "-fvisibility=hidden" "-DHAVE_LONGLONG" "-DHAVE_SNPRINTF" "-DHAVE_UNISTD_H" "-DHAVE_INTTYPES_H" "-DHAVE_STDLIB_H" "-DHAVE_SYS_SELECT_H" "-DHAVE_SYS_SOCKET_H" "-DHAVE_SYS_IOCTL_H" "-DHAVE_SYS_TIME_H" "-DHAVE_SYS_UN_H" "-DHAVE_O_NONBLOCK" "-DLIBSSH2_OPENSSL" "-DHAVE_LIBCRYPT32" "-DHAVE_EVP_AES_128_CTR" "-DHAVE_POLL" "-DLIBSSH2_DH_GEX_NEW" "-DLIBSSH2_HAVE_ZLIB" "-o" "/home/vsts/work/1/s/samples/wasm/target/wasm32-unknown-unknown/release/build/libssh2-sys-40529b05f84fbebf/out/build/libssh2/src/agent.o" "-c" "libssh2/src/agent.c" with args "clang" did not execute successfully (status code exit code: 1).

warning: build failed, waiting for other jobs to finish...
error[E0412]: cannot find type `off_t` in crate `libc`
  --> /home/vsts/.cargo/registry/src/github.com-1ecc6299db9ec823/libz-sys-1.1.2/src/lib.rs:25:26
   |
25 | pub type z_off_t = libc::off_t;
   |                          ^^^^^ not found in `libc`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0412`.
error: build failed
Error: Compiling your crate to WebAssembly failed
Caused by: failed to execute `cargo build`: exited with exit code: 101
  full command: "cargo" "build" "--lib" "--release" "--target" "wasm32-unknown-unknown"
##[error]Bash exited with code '1'.
Finishing: Wasm build

error detail link:https://dev.azure.com/nushell/nushell/_build/results?buildId=4858&view=logs&j=1a745d4c-b027-5f34-06d8-d6f256bfe9f9&t=a0a335cb-fa1f-5bbf-be01-1a90d6899e54

This crate depends on a number of C libraries, critically libssh2 itself, that cannot be compiled for a wasm based target.  This is not something that can be fixed as it is a fundamentally incompatible target for those underlying libraries.


ollama model do not contain a 'name' - LPW remains not connected

Here are the models as return by ollama
Connnecting to <IP_ADDRESS>
model='dolphin-mistral:latest' modified_at=datetime.datetime(2024, 12, 3, 13, 27, 45, 424575, tzinfo=TzInfo(+01:00)) digest='5dc8c5a2be6510dcb2afbcffdedc73acbd5868d2c25d9402f6044beade3d5f70' size=4108940323 details=ModelDetails(parent_model='', format='gguf', family='llama', families=['llama'], parameter_size='7B', quantization_level='Q4_0')
model='llama3:latest' modified_at=datetime.datetime(2024, 8, 20, 11, 34, 33, 373873, tzinfo=TzInfo(+02:00)) digest='365c0bd3c000a25d28ddbf732fe1c6add414de7275464c4e4d1c3b5fcb5d8ad1' size=4661224676 details=ModelDetails(parent_model='', format='gguf', family='llama', families=['llama'], parameter_size='8.0B', quantization_level='Q4_0')
This prevents LPW to connect to ollama server.
This error is hidden (or I could not find where it was printed).
I had to reconfigure the script to print to console.
After that I could see
2024-12-03 15:07:08.775 Uncaught app exception
Traceback (most recent call last):
File "/home/gdufour/.local/lib/python3.10/site-packages/streamlit/runtime/scriptrunner/exec_code.py", line 88, in exec_func_with_error_handling
result = func()
File "/home/gdufour/.local/lib/python3.10/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 579, in code_to_exec
exec(code, module.dict)
File "/data/Node/local-packet-whisperer/bin/lpw_main.py", line 8, in
pg.run()
File "/home/gdufour/.local/lib/python3.10/site-packages/streamlit/navigation/page.py", line 303, in run
exec(code, module.dict)
File "/data/Node/local-packet-whisperer/bin/lpw_home.py", line 146, in
loadDefaultSettings()
File "/data/Node/local-packet-whisperer/bin/lpw_home.py", line 25, in loadDefaultSettings
model_list, server_connected = getModelList()
File "/data/Node/local-packet-whisperer/bin/lpw_prompt.py", line 28, in getModelList
return oClient.getModelList()
File "/data/Node/local-packet-whisperer/bin/lpw_ollamaClient.py", line 85, in getModelList
raise e
File "/data/Node/local-packet-whisperer/bin/lpw_ollamaClient.py", line 81, in getModelList
retList.append(model['name'])
File "/home/gdufour/.local/lib/python3.10/site-packages/ollama/_types.py", line 32, in getitem
raise KeyError(key)
KeyError: 'name'
^CReceived CTRL+C !
The fix is easy - you just need to check for presence of name or model.
def getModelList(self) -> List[str] | bool:
    retList = []
    is_Connected = False
    try:
        model_list = self.client.list()
        models = model_list['models']
        for model in models:
            print(model)
            if 'name' in model:
                retList.append(model['name'])
            elif 'model' in model:
                retList.append(model['model'])
        is_Connected = True
    except Exception as e:
        print(f'Error Occured : {e} ')
        raise e
    return retList, is_Connected

Thanks for the report. I noticed this as well. Apparently the new version of ollama client has modified response. It will be corrected in next iteration.
Although I wonder why it happens in your system. Because I haven't pushed the new requirements.txt which contains latest ollama client.
Can you do pip3 freeze | grep ollama and paste the output ?

The requirements did not complete … was stuck forever so I did manual install.
pip3 freeze | grep ollama
ollama==0.4.2
On 3 Dec 2024, at 15:26, Viz @.***> wrote:
Thanks for the report. I noticed this as well. Apparently the new version of ollama client has modified response. It will be corrected in next iteration.
Although I wonder why it happens in your system. Because I haven't pushed the new requirements.txt which contains latest ollama client.
Can you do pip3 freeze | grep ollama and paste the output ?
—
Reply to this email directly, view it on GitHub https://github.com/kspviswa/local-packet-whisperer/issues/13#issuecomment-2514715318, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD3DH2Z6AXZ5ECGKKWXU6232DW5R7AVCNFSM6AAAAABS547TV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJUG4YTKMZRHA.
You are receiving this because you authored the thread.

As per lpw reqs, it requires ollama==0.1.6 . 0.4.2 is the latest one .
You can either install lpw within a virtual env or have the fix in place as you have suggested.
I'll dropping a new release shortly with more features and will upgrade the ollama client and also fix the signature. Thanks for your feedback.

Hi, please upgrade to the latest lpw release. you shouldn't face this issue.
pip install -U lpw


Move number of operations to paramset

Currently, number of operations is defined in flavor. For schemes where this is not inf, the concrete number most certainly will depend on the parameters (for example, it does so in the case of XMSS).
I suggest we move this to paramset. Any thoughts?

Agreed


Cuda out of memory and not freeing memory after error

I tried to run large model and then base model, but they both only return "cuda ouf of memory" error. On top of that they are not freeing taken memory and not resetting segmentation process, so I have to restart both server and interface to recover from error.
How to make it work without error?

I've added code that prints an error message, clears the cache, and returns from the function if a CUDA out-of-memory error occurs during SAM generation.


Use ProjectionsContext to process QueryHeader on proxy

For #4637.

Codecov Report

Merging #4657 into master will increase coverage by 0.13%.
The diff coverage is 42.1%.

@@             Coverage Diff              @@
##             master    #4657      +/-   ##
============================================
+ Coverage     55.36%   55.49%   +0.13%
  Complexity      426      426
============================================
  Files          1134     1134
  Lines         20547    20513      -34
  Branches       3811     3805       -6
============================================
+ Hits          11376    11384       +8
+ Misses         8453     8412      -41
+ Partials        718      717       -1

Impacted Files
Coverage Δ
Complexity Δ

.../communication/jdbc/execute/JDBCExecuteEngine.java
33.33% <ø> (ø)
0 <0> (ø)
:arrow_down:

...nication/jdbc/JDBCDatabaseCommunicationEngine.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...jdbc/execute/callback/ProxySQLExecuteCallback.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...rdingproxy/backend/response/query/QueryHeader.java
84.61% <88.88%> (+30.76%)
0 <0> (ø)
:arrow_down:

...ql/segment/dml/item/SubqueryProjectionSegment.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

.../sql/parser/visitor/impl/PostgreSQLDMLVisitor.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...segment/dml/item/AggregationProjectionSegment.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

.../sql/segment/dml/item/ColumnProjectionSegment.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...dml/item/AggregationDistinctProjectionSegment.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...phere/sql/parser/visitor/impl/MySQLDMLVisitor.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

... and 4 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 5ecf56a...219a579. Read the comment docs.

Pull Request Test Coverage Report for Build 10108

9 of 19 (47.37%)  changed or added relevant lines in 2 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.1%) to 59.05%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/execute/callback/ProxySQLExecuteCallback.java
0
10
0.0%

Files with Coverage Reduction
New Missed Lines
%

sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/util/IpUtils.java
3
76.0%

Totals

Change from base Build 1018:
0.1%

Covered Lines:
12113

Relevant Lines:
20513

💛  - Coveralls


Unexpected compatibility issue with VsCode

Getting the following error when attempting to install: "Can't install 'fireplusteam.vscode-ios' extension because it is not compatible with the current version of Visual Studio Code (version 1.85.1)." I have the most recent version of VSCode and this was published pretty recently. I feel like there should not be many compatibility issues already but I could be wrong.

you need to install vs code at least 1.86

1.85.1 is not supported


Cannot comment on deleted lines or even track them in diff view in VSCode

I only found an issue about deleted files #3421. Can't say this is unrelated, can't say this is the same.

Extension version: v0.50.0
VSCode Version: 1.72.0
OS: Debian 11.5

Steps to Reproduce:

Create a pull request that removes code
Open the pull request in VSCode, and view the file with deleted lines
Attempt to add a comment on a deleted line in diff-view, you can't. The "plus" sign doesn't show to add a comment on deleted lines.
Even worse, if someone does it on github and adds a comment, it's not possible to view them properly on VSCode, and basically VSCode shows an empty file with the comment

Open the pull request in VSCode, and view the file with deleted lines

Where are you opening the file from? Do you have the pull request checked out? If you see this with a pull request in a public repo, can you share a link to the pull request?

I added you to that repo.

I'm wondering whether you faced zero issues on your part

Correct, I faced no issues leaving and viewing comments on deleted lines. Thank you for the example repo, I'm looking into it.


Fix filter on enum value in list view v2

Filtering on legacy enums in a list view gives errors under Rails Admin 3.x (see #3651)
This PR adds to #3647 by adding a test for the fix provided there, as well as providing a similar fix for the Fields::Types::Enum#enum_method method.
I've left the original commit by @fuegas as-is to give due credit, but happy to squash the fix with the associated tests if preferred.
I don't fully grasp why the method is called without bindings (not even an empty hash), and it's not clear if that is something that should ever be expected or is a symptom of a bug somewhere else, however either way it is true that the code paths using abstract_model were not covered by the existing tests.

For now I'm not merging this as https://github.com/railsadminteam/rails_admin/commit/d62f604cc8d7d1434f7dfe0c5aca3aaf3dc2547b will be the proper fix, but I really appreciate your attempt to address this.
Thank you so much, and looking forward to another contribution 👍

@mshibuya Thanks. https://github.com/railsadminteam/rails_admin/commit/d62f604cc8d7d1434f7dfe0c5aca3aaf3dc2547b definitely looks like a better fix! 🎉
Let me know if you'd like me to adapt the tests into some "when the binding don't provide an object" test cases (eg: with an empty binding rather than no binding) instead to add test coverage for the code paths through abstract_model.


[SMALLFIX] Java 8 Improvement

Java 8 Improvement: replace anonymous type with lambda in alluxio.master.block.BlockMasterClientRestServiceHandler#getServiceVersion

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/578/
Test PASSed.


Does not conform to JTAppleCalendarViewDelegate

Everything work find on version 6.1.1
but today I just update to version 7.1.3 and I always got error "does not conform to JTAppleCalendarViewDelegate"
I try to solve with adding willDisplay(), updating syntax for cellForItemAt()
or any solution but I still get this error :(
I use Xcode 8.3.3 with Swift 3.0

In the latest version 7.1.3, you must implement the willDisplayCell function --> #533

Thank you


Exclude some directories from flake8 checks, and disable line length rule

I removed C101, I'll put it back


The tracked metric is too low

First of all thank you for adding Reid to bytetrack and making him open source，however,there are a few confusions when I reproduce your experimental results.
For now,the results are trained on half of MOT17 and tested on the other half of MOT17.
I run the following command：
python3 tools/train.py -f exps/example/mot/yolox_x_mot17_half.py -d 1 -b 2 --fp16 -o -c pretrained/yolox_x.pth.tar
This is the result after 80 rounds of training：
Bytetrack-Reid:

Here I also compared the original bytetrack in the mot17_train_half training, and found that the result of Bytetrack_Reid is not as high as the original, may I ask why this is :
Bytetrack:

Then I used these two weight files to evaluate on MOT17_val_half and got the following results：
Bytrack-Reid:

Bytetrack:

I did not get the same experimental results as you, may I ask where did I go wrong.
Looking forward to your reply.

@yanghaibin-cool Hi, there!
Your results of ByteTrack_ReID is almost the same as mine. But your ByteTrack results are much higher than mine.
I will give it a look, which may need some time?

@yanghaibin-cool And these is something not right in yolox_s_mot17_half.py. The training should use train_half.json, not train.json.
And my results (mAP 0.556 MOTA 72.6) is from yolox_s, not yolox_x. The results of origin bytetrack is mAP 0.535 MOTA 71.5.
Please tell me which model is used (s or x).

For another thing, it is reasonable to see performance degradation after using an additional ReID head. You can go to CSTrack for the detailed reason.

And from my results, adding a reid head will not obviously increase forward time. There are several conflicts between your results and mine.
So, looking forward to your reply!

First of all, glad to hear from you.
The configuration of my computer is 2080ti, 11g video memory.
Below is the config file where I run the program:
Bytetrack-Reid:

Bytetrack:

then the indicators tested on val_half.json with the trained weights are the screenshots above.
I don't understand why the IDF1 metrics are so different (bytetrack-Reid: 64.5; bytetrack: 78.1).

@HanGuangXin Because the effect of yolox_s is not very good, I used yolox_x, the two screenshots above I used yolox_x to train for 80 rounds. I originally thought that I would get the indicators of the screenshots uploaded by your git repository, so I wanted to ask where the problem is, thank you very much.

@yanghaibin-cool And these is something not right in yolox_s_mot17_half.py. The training should use train_half.json, not train.json.
And my results (mAP 0.556 MOTA 72.6) is from yolox_s, not yolox_x. The results of origin bytetrack is mAP 0.535 MOTA 71.5.
Please tell me which model is used (s or x).

Because the effect of yolox_s is not very good, I used yolox_x(yolox_x_mot17_half.py), the two screenshots above I used yolox_x to train for 80 rounds. I originally thought that I would get the indicators of the screenshots uploaded by your git repository, so I wanted to ask where the problem is, thank you very much.
Next, I am going to use yolox_s_mot17_half.py to train again.
Hope to get the same result as you.

Maybe my computer configuration is too low（2080ti,11g video memory）

And from my results, adding a reid head will not obviously increase forward time. There are several conflicts between your results and mine.
So, looking forward to your reply!

Maybe my computer configuration is too low（2080ti,11g video memory）

For another thing, it is reasonable to see detection performance degradation after using an additional ReID head. You can go to CSTrack for the detailed reason.

OK, thanks for reminding.

@yanghaibin-cool Thanks for the reply.
There are some things:

My device is 2080Ti, too. But batchsize matters.
YOLOX_X with mAP 55.6 and MOTA 72.5 is not normal. YOLOX_S can get mAP 55.5, MOTA 71.8 and IDF1 73.8 (more or less) using yolox_s_mot17_half.py. So I think you can run yolox_s for comparison.
Indicators of the screenshots uploaded by myself in not right, which is obtained using train.json. So it is correct with 70+ MOTA. YOLOX_S with mAP 55.5, MOTA 71.8 and IDF1 73.8 is obtained using train_half.json, which should be correct.

Looking forward to more information!

@yanghaibin-cool Thanks for the reply. There are some things:

My device is 2080Ti, too. But batchsize matters.
YOLOX_X with mAP 55.6 and MOTA 72.5 is not normal. YOLOX_S can get mAP 55.5, MOTA 71.8 and IDF1 73.8 (more or less) using yolox_s_mot17_half.py. So I think you can run yolox_s for comparison.
Indicators of the screenshots uploaded by myself in not right, which is obtained using train.json. So it is correct with 70+ MOTA. YOLOX_S with mAP 55.5, MOTA 71.8 and IDF1 73.8 is obtained using train_half.json, which should be correct.

Looking forward to more information!

Thank you for your reply. Yes, I am training Bytetrack-Reid:
yolox_s_mot17_half.py(train_ann:train_half.json;val_ann:val_half).
Then train Bytetrack and compare the two.
Have you trained yolox_x_mot17_half, what is the result? (Could it be that Reid is not suitable for yolox_X_mot17_half?)

I will do it in one week or two.
I'm a little busy now, sorry about that.

I will do it in one week or two. I'm a little busy now, sorry about that.

May I ask what this function is for, it seems that there is no call in the code,

just ignore it.
---Original---
From: "poplar @.>
Date: Mon, Apr 11, 2022 14:55 PM
To: @.>;
Cc: "Han<EMAIL_ADDRESS>Subject: Re: [HanGuangXin/ByteTrack_ReID] The tracked metric is too low (Issue#10)
I will do it in one week or two. I'm a little busy now, sorry about that.
May I ask what this function is for, it seems that there is no call in the code,
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

just ignore it.
…
---Original--- From: "poplar @.> Date: Mon, Apr 11, 2022 14:55 PM To: @.>; Cc: "Han<EMAIL_ADDRESS>Subject: Re: [HanGuangXin/ByteTrack_ReID] The tracked metric is too low (Issue#10) I will do it in one week or two. I'm a little busy now, sorry about that. May I ask what this function is for, it seems that there is no call in the code, — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @

@yanghaibin-cool Thanks for the reply. There are some things:

My device is 2080Ti, too. But batchsize matters.
YOLOX_X with mAP 55.6 and MOTA 72.5 is not normal. YOLOX_S can get mAP 55.5, MOTA 71.8 and IDF1 73.8 (more or less) using yolox_s_mot17_half.py. So I think you can run yolox_s for comparison.
Indicators of the screenshots uploaded by myself in not right, which is obtained using train.json. So it is correct with 70+ MOTA. YOLOX_S with mAP 55.5, MOTA 71.8 and IDF1 73.8 is obtained using train_half.json, which should be correct.

Looking forward to more information!

Hello! I have finished training with yolox_s_mot17_half(self.train_ann=train_half.json;self.val_ann=val_half.json).However,I didn't get the desired result(YOLOX_S with mAP 55.5, MOTA 71.8 and IDF1 73.8).
Below is the result of my training：
Bytetrack-Reid with train.py:

Bytetrack-Reid with track.py:
COCO indicator：

MOT indicator:

Bytetrack with train.py:

Bytetrack with track.py:
COCO indicator:

MOT indicator:

Why is the tracking effect worse after adding Reid? Where am I going wrong?
Looking forward to your reply


Binary stream/Octet vector support

It might be useful to some people to have binary streams support (read-byte rather than read-char).
Because RFC 8259 specifically requires UTF-8, it should be doable without too much effort.
This is primarily in cases where the user already has a stream open from another source, or has a vector of ub8 they'd like to parse as JSON (eg an SQL column)

One thing that stuck out to me in implementing 82eab57 is that stringify would need to be altered to allow outputting a vector, if that's something anyone wants.
I'm erring on saying it's not, but leave it open in case anyone has thoughts


Error while passing parameters to Google Map

I displayed simple Google Map successfully :
<google-map
    latitude="30.283"
    longitude="57.083"
    zoom="12"
    language="fa"
    disable-default-ui
    >

But when I try to add position style, it doesn't apply it and zoom control disappears, I guess the problem is in the way I add additional-map-options, but I don't know how to fix it:
<google-map
    latitude="30.283"
    longitude="57.083"
    zoom="12"
    language="fa"
    disable-default-ui
    additional-map-options='{"zoomControl" : "true",
    "zoomControlOptions" : {"style" : "google.maps.ZoomControlStyle.SMALL",
    "position" : "google.maps.ControlPosition.BOTTOM_RIGHT"}
  }'>

The google-maps.ControlPosition is a javascript Object {TOP_LEFT: 1, TOP_CENTER: 2, TOP: 2, TOP_RIGHT: 3, LEFT_CENTER: 4…} with numeric properties (i.e. BOTTOM_RIGHT = 12).
If you pass properties of type Object (i.e. additional-map-options) decleratively as a String, Polymer will deseralize it to an Object using JSON and thus google.map.ControlPosition.BOTTOM_RIGHT will be converted to a String, but google maps expects a numeric value between 1 and 12.
There are 2 workarounds:

Don't pass it decleratively but use a computed function to set the property directly (make sure that the google maps library is loaded, otherwise google.maps will be undefined)

<google-map additional-map-options="{{_computeAdditionalOptions()}}">

_computeAdditionalOptions: function() {
    return  {zoomControlOptions:....,position: google.maps.ControlPosition.BOTTOM_RIGHT};
}

Pass the numeric value for BOTTOM_RIGHT:

<google-map
    latitude="30.283"
    longitude="57.083"
    zoom="12"
    language="fa"
    disable-default-ui
    additional-map-options='{"zoomControl" : "true",
    "zoomControlOptions" : {"style" : "1",
    "position" : "12"}
  }'>

P.S.: google.maps.ZoomControlStyle.SMALL has the value of 1.

Closing, as the answer above provides two approaches, and this tracker is for the Polymer core library; if there are follow-on issues, please file them in the google-map issue tracker: https://github.com/GoogleWebComponents/google-map/issues.  Thanks!


[BUG] Error: e[i] is not a function, with-content-script-ui

What happened?
import type { PlasmoContentScript } from "plasmo"

import { useStorage } from "@plasmohq/storage"

export const config: PlasmoContentScript = {
  matches: ["<all_urls>"]
}

const PlasmoOverlay = () => {
  const [demo, setDemo] = useStorage<string>("demo")
  const [demo2, setDemo2] = useStorage<any>("demo2")

  return (
    <span onClick={() => setDemo(new Date().toString())}>
      HELLO WORLD TOP{demo}
    </span>
  )
}

export default PlasmoOverlay

on click HELLO WORLD TOP
Version
Latest
What OS are you seeing the problem on?
MacOSX
What browsers are you seeing the problem on?
No response
Relevant log output
Error in event handler: TypeError: e[i] is not a function
    at chrome-extension://jjaceeikmknehidlkcgmigdjkipecdom/plasmo-overlay.19fa8d1f.js:3157:57

(OPTIONAL) Contact Details
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

@crazyair Can you try @plasmohq/storage version 0.6.1. Should be fixed in that version

@crazyair Can you try @plasmohq/storage version 0.6.1. Should be fixed in that version

okay


commit

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
What did you learn from the changes you have made?
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

there were two parts where I was supposed to enter text in the assignment-1. However, they were for python code. So, for interpretation, I just added below the questions.

@amanda-ng518, Thank you! Can you tell me what is my grade is for the A1|?


Thumbnails

Hi!
Is there a fix out there for the default thumbnail issue as of yet?
Best
Gareth

Hi there, can you describe the problem you are experiencing ?

All of the thumbnails now display as so…

I've seen it occur across a few sites. Wordpress version is 5.4.4 and plugin I version 1.1.5
Cheers!

I see - Quick solution is to hit refresh on the plugin button, the plugin fetches and adds the content to WP's DB.
The issue:
If for some reason the link to the image changes it would look broken until new data is fetched. I'm not sure the best way to automate this. Any thoughts are welcome. It's been running for years without this problem, I've seen it occurring once before last year, I think it was due to infrastructure updates.


Mining Q and A  For noobies

How can i get started mining monyx knowing zero information on the basis of mining besides my computing power and This Github
any downloads?
plzz help!

@Sirbearingson I'll compose a FAQ section here about mining on this weekend.

Thanks @monyxcoin
I appreciate your response
The FAQS will be WELL Appreciated <3


Performance issue for yolo model with unknown size

The argument tensor of yolo model is of shape tensor<?x?x?x3xf32> (called dynamic version here). If we change the shape of the argument with the shape of the input tensor used for inference, tensor<1x416x416x3xf32>, the performance (called static version) is much better (more than x100).
I did so investigation into this issue.
First, I added instrumentation for the popular op in yolo model: Conv and Mul. Here are the observations:

Instrumentation overhead is small enough for this investigation.
No significant variation of execution time for each op from run to run.
For the first 6 instrumented op, (in sequence of Conv, Mul, Conv, Mul, Conv, Mul), slow down is 0.99, 1.08, 0.75, 7.85,  6.19, 6.26. In this test, the model is trimmed down to the third Mul op.
For longer sequence of ops, the performance of the first 6 remains the same. The size of tensor gradually decrease and the slowdown increases to 100x

First difference between dynamic and static version is memory usage. In the static version, the virtual memory size is around 400 m for different versions of model (I tried to remove some operations).  For dynamic model, memory usage increases with the number of ops. With only 1/3 of the operations in the original model, the memory size is 22 G.
I am not clear about the impact on performance, cold cache misses, unnecessary cache write back and even extra page fault. Can we run some tool to get the details?
For the operations, now I focused on Mul, which is quite simple.
For the EmitLLVMIR, the major difference is that the extra get dim size operations inside loop body. If the compiler does not know the alias info, it is possible that these operations are not moved to out side of loop, introducing extra load operations.
In next step, we need to check the bc file to verify what the final code is. How to generate bc file?

Just to be clear, the slowdown above are the current implementation with Dynamic vs Static vector shape, right?
From having looked at assembly, even the simplest loop:
for(int I=0; I<64; I++) a[I] = b[I] + c[I]

If unrolled by the backend, there is literally no scheduling of the reads (b and c) past any write (a) because memory disambiguation is quite broken once we are out of MLIR. For this particular example, the only way to move read past write operations was to hav MLIR unroll the loop.
With static sizes, we agree that memory bundling can reuse the memory used for temp tensors quite well. Say this is hard for arbitrary dynamic sizes, the cost of having malloc/free just before every op should technically have nearly the same footprint as the static size (at least same order of magnitude) and I don't believe the overhead associated with malloc/free should be too high if the amount of computations (such as matmul/conv) are nontrivial, as computations are at least O(N3) compared to O(1) of malloc/free costs.
Right now, our policy is to place malloc/free at beginning/end of function. That could be parametrized to before/after op in presence of dynamic tensors. Or malloc/free could be moved toward begin/end of functions vs begin/end of operation depending on static/dynamic tensors.

Hi Tong,

For the operations, now I focused on Mul, which is quite simple.

For unknown dims, Mul needs more operations to check broadcasting.

In next step, we need to check the bc file to verify what the final code is. How to generate bc file?

You can get it as follows, from the output of EmitLLVMIR:
$ mlir-translate test.mlir -mlir-to-llvmir -o test.ll
$ llvm-as test.ll –o test.bc

But you cannot read test.bc since it is not a human-readable file. To get a human-readable output from the bitcode, use llvm-dis test.bc -o test.dis
mlir-translate, llvm-as and llvm-dis are tools in LLVM (in the same folder as FileCheck).

@tungld  Thanks. I used --preserveBitcode flag  and llv-dis to get the .ll code.
My previous concern about the load for get dim for dynamic version is not an issue. llvm moved that load out of loop.
The check of broadcast is there for the dynamic. But the part for load and multiplication is the same in both dynamic and static version. For this model, if mlir provide support for symbolic dim size, the broadcast can be eliminated. The shape of the two inputs come from the same tensor.

One concern for dynamic tensor is that their space can not be reused. If we bundle them, the total space might be huge.
When a memref is generated, memref.alloc is inserted. However, the dealloc is not added, unless the output is not used. In general, the dealloc of memref should be added at the end of of its live range, which can not be done locally with one op. Currently, we only have one free at the end of the program for the bundled space. We need to enhance the memory management code for dynamic shapes.

For unknown dims, Mul needs more operations to check broadcasting.

@tungld Interesting: that is if we have the ranks, we still need to test if the dim is != 1 as this would still force broadcasting, isn't it?
This speak in favor of a N>1 dynamic number, as, for example, a model would typically know that the "sizes" of an image would be runtime but would not invoke "broadcasting" of pixels among there runtime image size, if you see what I mean...

@tungld Interesting: that is if we have the ranks, we still need to test if the dim is != 1 as this would still force broadcasting, isn't it?

Right.

This speak in favor of a N>1 dynamic number, as, for example, a model would typically know that the "sizes" of an image would be runtime but would not invoke "broadcasting" of pixels among there runtime image size, if you see what I mean...

I see. we can make the handling fo broadcasting a bit smarter here.

In general, the dealloc of memref should be added at the end of of its live range, which can not be done locally with one op.

@chentong319 if you want to quickly test this to see any performance change, you can use a MLIR pass, buffer-deallocation. It automatically inserts dealloc just at the end of the live range.

@tungld thanks for the suggestion, let try existing code first before modifying our own.

@chentong319 if you want to quickly test this to see any performance change, you can use a MLIR pass, buffer-deallocation. It automatically inserts dealloc just at the end of the live range.

@tungld Excellent suggestion. I did the experiment in the following steps:
# v6.mlir is a dynamic version with 25 Conv
Debug/bin/onnx-mlir --EmitONNXIR v6.mlir
cp v6.onnx.mlir v6-dealloc-1.mlir
# Skip our own buffer related transformation
Debug/bin/onnx-mlir-opt --convert-onnx-to-krnl v6-dealloc-1.mlir > v6-dealloc-2.mlir
Debug/bin/onnx-mlir-opt -canonicalize --convert-krnl-to-affine v6-dealloc-2.mlir > v6-dealloc-3.mlir

#delete the our own dealloc before return
vi v6-dealloc-3.mlir
~/llvm-project/build/bin/mlir-opt -allow-unregistered-dialect --buffer-deallocation v6-dealloc-3.mlir > v6-dealloc-4.mlir
Debug/bin/onnx-mlir --preserveBitcode v6-dealloc-4.mlir

The result is

No change in execution time
deallocs are added in middle of the code
memory usage in runtime is much lower than directly compiled with onnx-mlir

The slowdown came from other factor. I will check the impact if code is generated with no broadcast assumption.

@chentong319 great, looking forward to hear what we get now. This option can be run in all cases, after bundling terminates, in case there are un-bundled malloc/free

Some correction on the result using mlir buffer-deallocation pass.  Even though there is no  significant change in overall execution time, there is notable change in execution time for onnx.Mul op. I list the comparison of execution time for the first 22 Mul operations. The baseline the dynamic version compiled with onnx-mlir.

onnx.mul
vs. use dealloc
vs. static

1
1.118986
1.40364468

2
1.14244059
7.32108377

3
0.81698702
5.14030296

4
0.91209709
6.43561899

5
1.27468225
6.96805211

6
1.34997306
9.07578612

7
1.74610699
11.1936703

8
1.36749926
42.7274698

9
1.49653903
28.9776616

10
1.66238222
39.7137453

11
1.45076816
39.4212524

12
1.48723424
40.8446663

13
1.88158898
42.286802

14
1.38741428
37.8878981

15
1.51278562
40.3782091

16
1.53740106
44.6491948

17
1.45878552
43.0196265

18
1.51503751
174.397863

19
1.55616374
181.753731

20
1.57064024
172.387887

21
1.50640728
180.047742

22
1.72477148
128.940577

Inspired by this issue, I created a PR #758 to allow us passing static shapes to a dynamic model to avoid performance overhead. It may be  used to test static/dynamic models.

I further investigated the impact of broadcast and found that the code for possible broadcasting is NOT the major source of slowdown. Execution time for onnx.Mul is reduce only about 15% on average.
With dynamic shape, whether broadcasting occurs or not can not be determined at compile time. onnx-mlir generates code with selection operations. However, there is no broadcast occur in this model. We cab analyze where the shapes of two tensor are the same through data-flow. I simply changed the code in the investigation.

I checked the binary with objdump.  Similar to the .ll file, the innermost loop body is the same while the loop structure is slightly different. I cannot figure out why the performance can differ by 4x. I used this link for assembly reference.
The binary for the third onnx.Mul is list here. The offset of main_graph is 6eb0. I annotated some label in the objdump result to show the loop structure.
For static tensor:
    7b6e:	c0 e5 ff ff f2 15 	brasl	%r14,5f98 <InstrumentEntryPoint@plt>
    7b74:	a7 19 00 00       	lghi	%r1,0
    7b78:	a7 29 00 00       	lghi	%r2,0
    7b7c:	e3 d0 f0 a0 00 04 	lg	%r13,160(%r15)
    7b82:	e3 c0 f1 18 00 04 	lg	%r12,280(%r15)
    7b88:	e3 b0 f1 48 00 04 	lg	%r11,328(%r15)
    7b8e:	b9 04 00 31       	lgr	%r3,%r1
    7b92:	a7 49 00 00       	lghi	%r4,0
    7b96:	a7 59 ff ff       	lghi	%r5,-1    //<main_graph+0xce6>
    7b9a:	b9 04 00 e3       	lgr	%r14,%r3

   <main_graph+0xcee>:  // innermost loop
    7b9e:	78 0e b0 00       	le	%f0,0(%r14,%r11)
    7ba2:	ed 0e c0 00 00 17 	meeb	%f0,0(%r14,%r12)
    7ba8:	70 0e d0 00       	ste	%f0,0(%r14,%r13)
    7bac:	41 50 50 01       	la	%r5,1(%r5)
    7bb0:	41 e0 e0 04       	la	%r14,4(%r14)
    7bb4:	ec 54 ff f5 cf 7d 	clgijl	%r5,207,7b9e <main_graph+0xcee>

    7bba:	c2 4e 00 00 00 cf 	clgfi	%r4,207
    7bc0:	41 40 40 01       	la	%r4,1(%r4)
    7bc4:	41 30 33 40       	la	%r3,832(%r3)
    7bc8:	a7 44 ff e7       	jl	7b96 <main_graph+0xce6>
    7bcc:	c2 2e 00 00 00 1f 	clgfi	%r2,31
    7bd2:	41 20 20 01       	la	%r2,1(%r2)
    7bd6:	e3 10 14 00 2a 71 	lay	%r1,173056(%r1)
    7bdc:	a7 44 ff d9       	jl	7b8e <main_graph+0xcde>
    7be0:	b9 04 00 2b       	lgr	%r2,%r11
    7be4:	c0 e5 ff ff f8 3a 	brasl	%r14,6c58 <free@plt>
    7bea:	b9 04 00 2c       	lgr	%r2,%r12
    7bee:	c0 e5 ff ff f8 35 	brasl	%r14,6c58 <free@plt>
    7bf4:	a7 29 00 02       	lghi	%r2,2
    7bf8:	a7 39 00 00       	lghi	%r3,0
    7bfc:	c0 e5 ff ff f1 ce 	brasl	%r14,5f98 <InstrumentEntryPoint@plt>

For dynamic tensors:
    86f4:	c0 e5 ff ff ec 52 	brasl	%r14,5f98 <InstrumentEntryPoint@plt>
    86fa:	b9 04 00 2d       	lgr	%r2,%r13
    86fe:	c0 e5 ff ff f0 3d 	brasl	%r14,6778 <malloc@plt>
    8704:	e3 20 f1 58 00 24 	stg	%r2,344(%r15)
    870a:	e5 58 f0 c8 00 00 	cghsi	200(%r15),0
    8710:	a7 c4 00 90       	jle	8830 <main_graph+0x1980>
    8714:	e3 10 f0 d8 00 04 	lg	%r1,216(%r15)
    871a:	eb 01 00 07 00 0d 	sllg	%r0,%r1,7
    8720:	e3 00 f1 60 00 24 	stg	%r0,352(%r15)
    8726:	eb 11 00 02 00 0d 	sllg	%r1,%r1,2
    872c:	e3 20 f1 80 00 04 	lg	%r2,384(%r15)
    8732:	eb 22 00 02 00 0d 	sllg	%r2,%r2,2
    8738:	a7 59 00 00       	lghi	%r5,0
    873c:	e3 80 f1 70 00 24 	stg	%r8,368(%r15)
    8742:	e3 00 f1 58 00 04 	lg	%r0,344(%r15)
    8748:	a7 f4 00 24       	j	8790 <main_graph+0x18e0>
    874c:	e3 50 f1 68 00 04 	lg	%r5,360(%r15)
    8752:	41 50 50 01       	la	%r5,1(%r5)
    8756:	e3 40 f1 60 00 04 	lg	%r4,352(%r15)
    875c:	b9 08 00 04       	agr	%r0,%r4
    8760:	e3 30 f1 78 00 04 	lg	%r3,376(%r15)
    8766:	b9 08 00 34       	agr	%r3,%r4
    876a:	e3 30 f1 78 00 24 	stg	%r3,376(%r15)
    8770:	e3 30 f1 70 00 04 	lg	%r3,368(%r15)
    8776:	b9 08 00 34       	agr	%r3,%r4
    877a:	e3 30 f1 70 00 24 	stg	%r3,368(%r15)
    8780:	e3 50 f0 c8 00 20 	cg	%r5,200(%r15)
    8786:	e3 70 f1 40 00 04 	lg	%r7,320(%r15)
    878c:	a7 a4 00 52       	jhe	8830 <main_graph+0x1980>
    8790:	e3 50 f1 68 00 24 	stg	%r5,360(%r15)
    8796:	ec 7c ff db 00 7c 	cgijnh	%r7,0,874c <main_graph+0x189c>
    879c:	a7 99 00 00       	lghi	%r9,0
    87a0:	e3 e0 f1 70 00 04 	lg	%r14,368(%r15)
    87a6:	e3 d0 f1 78 00 04 	lg	%r13,376(%r15)
    87ac:	b9 04 00 50       	lgr	%r5,%r0
    87b0:	a7 f4 00 0f       	j	87ce <main_graph+0x191e>
    87b4:	b9 08 00 51       	agr	%r5,%r1
    87b8:	b9 08 00 d1       	agr	%r13,%r1
    87bc:	b9 08 00 e1       	agr	%r14,%r1
    87c0:	c2 9e 00 00 00 1f 	clgfi	%r9,31
    87c6:	41 90 90 01       	la	%r9,1(%r9)
    87ca:	a7 a4 ff c1       	jhe	874c <main_graph+0x189c>
    87ce:	e5 58 f1 80 00 00 	cghsi	384(%r15),0
    87d4:	a7 c4 ff f0       	jle	87b4 <main_graph+0x1904>
    87d8:	a7 79 00 00       	lghi	%r7,0
    87dc:	b9 04 00 6e       	lgr	%r6,%r14
    87e0:	b9 04 00 bd       	lgr	%r11,%r13
    87e4:	b9 04 00 a5       	lgr	%r10,%r5
    87e8:	a7 c9 00 00       	lghi	%r12,0
    87ec:	a7 49 00 00       	lghi	%r4,0
    87f0:	e3 30 f1 80 00 04 	lg	%r3,384(%r15)

   <main_graph+0x1946>: // innermost loop
    87f6:	78 0c 60 00       	le	%f0,0(%r12,%r6)
    87fa:	ed 0c b0 00 00 17 	meeb	%f0,0(%r12,%r11)
    8800:	70 0c a0 00       	ste	%f0,0(%r12,%r10)
    8804:	41 40 40 01       	la	%r4,1(%r4)
    8808:	41 c0 c0 04       	la	%r12,4(%r12)
    880c:	ec 43 ff f5 40 64 	cgrjl	%r4,%r3,87f6 <main_graph+0x1946>

    8812:	41 70 70 01       	la	%r7,1(%r7)
    8816:	b9 08 00 a2       	agr	%r10,%r2
    881a:	b9 08 00 b2       	agr	%r11,%r2
    881e:	b9 08 00 62       	agr	%r6,%r2
    8822:	e3 70 f1 40 00 20 	cg	%r7,320(%r15)
    8828:	a7 44 ff e0       	jl	87e8 <main_graph+0x1938>
    882c:	a7 f4 ff c4       	j	87b4 <main_graph+0x1904>
    8830:	e3 20 f1 38 00 04 	lg	%r2,312(%r15)
    8836:	c0 e5 ff ff f2 11 	brasl	%r14,6c58 <free@plt>
    883c:	b9 04 00 28       	lgr	%r2,%r8
    8840:	c0 e5 ff ff f2 0c 	brasl	%r14,6c58 <free@plt>
    8846:	a7 29 00 02       	lghi	%r2,2
    884a:	a7 39 00 00       	lghi	%r3,0
    884e:	c0 e5 ff ff eb a5 	brasl	%r14,5f98 <InstrumentEntryPoint@plt>

Tong, I checked with ResNet50 and saw the same issue for dynamic dimensions, but found a good news.

batch size and channel are unknown onnx-mlir resnet50.onnx --shapeInformation='0:=-1,-1,224,224' => worked well
onnx-mlir resnet50.onnx --shapeInformation='0:1,3,-1,224' only the image height unknown => same issue as Yolo
onnx-mlir resnet50.onnx --shapeInformation='0:1,3,224,-1' only the image width unknown => same issue as Yolo

So I suppose that there was something wrong with the lowering for Conv, in particular, to handle dynamic dimensions for the image height and width. Perhaps, it wrongly computed loop bounds (two big values would cause an infinite run, or invalid values would cause segfault).
Our end-to-end test, which is make check-onnx-backend-dynamic, only check dynamic dimension for batch size, not height or width. So it did not catch this Yolo situation.
Given that assumption, I edited the numerical test for Conv to check dynamic image height, and it seems we got problems there. See PR #764. I believe we should fix the issue with Conv before going further debugging Yolo.

I think I found at least one issue: the shape inference for Conv is wrong when the shape is not static.
First, code for insert allocate for Conv is wrong: When the shape is not constant, the input shape is always copied.  We need to use IndexExpr to calculate the output shape. @tungld, could you fix this issue since you wrote the shape inference for Conv.  @AlexandreEichenberger, could you help Tung in using IndexExpr if needed?

@chentong319 @AlexandreEichenberger I used IndexExpr to infer shape for Conv. PR #764 is ready to review now.
I tested with Yolo. Inference in case of dynamic dims took 79 seconds on my local machine. Memory consumption was about 1.7 GB. We still need a better buffer management for dynamic tensors in the future.

@tungld so you verified the output in the dyn case?

@tungld so you verified the output in the dyn case?

I only measured the inference time and memory consumption in the dynamic case, but did not verify the output result since I didn't have the reference output for the model.

@tungld Where should I put the expect output? Is your script good enough to be put into git repository?
I ran yolo with the current master branch and got the same execution time as the static version.

@chentong319 how about the same folder you put the yolo model?

Is your script good enough to be put into git repository?
It's a small python script. I will polish it a bit then put it into the git repos.

Compiling with --mtriple=s390x-ibm-linux --mcpu=z14 helps reduce the inference time from 80s to 54s.

@tungld Cool! Do we know what kind optimization is enabled by these flags? simdization?

Its worst than no simd and no unrolling, for code that is simonized and unrolled.

Its worst than no simd and no unrolling. It results in performance that is akin no optimizations, see GEMM example below

@chentong319 maybe just post the latest time with static vs dynamic, and if it is satisfactory, let's close this one.
Working on making conv go faster, this is a separate issue.


Icon change successful

All the fixes regarding the logo have been made.

Resizing and shape binding has been done!
Kindly merge the PR

@Nitish145 can you approve workflow run, I would like to test the build.

Yeah I synced the assets wrongly. Made the changes! sharing them

Please check now @manjotsidhu

Yeah I corrected them.
On Sat, 22 May 2021 at 19:57, Manjot Singh Sidhu @.***>
wrote:

@.**** requested changes on this pull request.
In pubspec.lock
https://github.com/CircuitVerse/mobile-app/pull/96#discussion_r637410316
:

@@ -28,7 +28,7 @@ packages:
name: async

Exclude changes from this file.
In pubspec.yaml
https://github.com/CircuitVerse/mobile-app/pull/96#discussion_r637410382
:

@@ -78,6 +78,22 @@ flutter:
- assets/images/signup/
- assets/images/group/
- assets/images/profile/

android/app/src/main/res/mipmap-mdpi/ic_launcher_foreground.png

Are you sure that these android/* assets are specifically required to be
included ? I don't think so
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CircuitVerse/mobile-app/pull/96#pullrequestreview-666186085,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR44WTSQQJKRNEKAMVVNAITTO65NXANCNFSM45KN2IQQ
.

I will get back to soon after I tested this personally.

sure sure
On Sat, 22 May 2021 at 22:16, Manjot Singh Sidhu @.***>
wrote:

@.**** commented on this pull request.
Looks good, let me test it out.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/CircuitVerse/mobile-app/pull/96#pullrequestreview-666195957,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR44WTVHUUXCFO5OBHHKZJTTO7NU5ANCNFSM45KN2IQQ
.


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 76 ms

Resolved: ClamAV performance has improved in a7b541e.


Short solution needed: "How to get IP address in CLI" (ubuntu)

Please help us write most modern and shortest code solution for this issue:
How to get IP address in CLI (technology: ubuntu)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

How to get IP address in CLI


Feat: Allow plus in ocidir path

Fixes issue
Fixes #855.

Describe the change
This adds a plus to the list of allowed path characters in an OCI Layout reference.

How to verify it
regctl image copy ocidir://output/regctl:scratch ocidir://test/path+with+plus:latest

Changelog text

Feat: Allow plus in ocidir path.

Please verify and check that the pull request fulfills the following requirements

[X] Tests have been added or not applicable
[X] Documentation has been added, updated, or not applicable
[X] Changes have been rebased to main
[X] Multiple commits to the same code have been squashed

Thanks for fixing this @sudo-bmitch

@sudo-bmitch when do you plan to create a release including this PR? This is currently blocking bazel-contrib/rules_oci#738. Thanks.

It should be released this week. The last feature went in this weekend, and there's at least one bug fix remaining.


On french keyboards it doesn't work

Put your keyboard in french. Then try CMD + 1.
It doesn't work.
Probably other keybooards too

use english!! lol
on a serious note, would love help. probably just a simple config in electron somewhere. if anyone sees this, PR welcome

@merwanehamadi , @mwyywm may have fixed this for you. pls try in our latest (beta 7 and above) release!

thanks will check


Missing linguistics dependency

Describe the bug
We are using KStemmer in our code. It is located in the linguistics package and we are adding it as a provided package in our pom.xml.
However, we are getting the following error:
com/yahoo/language/simple/kstem/KStemmer:
    com.yahoo.language.simple.kstem.KStemmer not found by vlex-search

To Reproduce
Steps to reproduce the behavior:

Import com.yahoo.language.simple.kstem.KStemmer;
Create an instance of that class
See error

Expected behavior
We shouldn't see that error
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: macOs
Infrastructure: self-hosted
Versions 8.241.13

Vespa version
8.241.13
Additional context
None

Hi @danitico. The KStemmer is not part of Vespa's public API. Although not accessible directly you may utilize it through com.yahoo.language.simple.SimpleTokenizer.

Thanks @bjorncs !


Add date in section title for days

Maybe add the date with the text "2 days" like this "In 2 days the 3rd march" or juste change section title with Today, Tomorrow and after the date"

In the new version of Caravel, there will be two more views calendar and Gantt view in which you can see the date of each task. The task list view will stay with the "2 days" (time ago display)


Fix DynamicExpressionParser for IQueryable

Could you create a release with this fix?

Could you create a release with this fix?

I'll see if I can release it today or tomorrow.


Polymer2 support

Now Polymer2 is released, have you planned to release your webcomponents in a polymer2 version?

Definitely. These will all be ported when Simpla's elements are, but would also happily accept PRs in the meantime. Most should be pretty trivial to make into hybrids.
The exception is simple-button, which is blocked by this PR on the custom-elements polyfill.

What's the status on this?

Porting all SimpleElements to wc v1 is still blocked by that PR. I'm also flat out at the moment, but would happily accept PR for making simple-modal itself a hybrid Polymer 1/2 element in the meantime. Should be pretty straightforward.


Create yersinnhatrang.txt

@hanhanyersinnhatrang Regrettably, this domain data has signs of inconsistency. I have to close it without merging.
Please apply for free educational license with an official document which proves that you are a student. You can do it using "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.
Thank you for the understanding!


Media Download : Add speaker images and media files into the mockjson folder as well

To be able to test that the download script will work

all portions of this is completed via this https://github.com/fossasia/open-event-webapp/pull/370


Fix so SWIR can have 273 wavelengths

Description
Self-descriptive
Types of changes

Bug fix since SWIR was replaced
Make more generic the raw file size limiting checker

Checklist:

[ ] Passes on hyperspectral_tst 1x1 image for @FlyingWithJerome

@czender addressed the wavelength check with a direct sensor name check in this PR:
https://github.com/terraref/computing-pipeline/pull/235
...so this superseded one is merged as well.


Fix incorrect gui colors in jellybeans theme

I've noticed incorrect section colors when using set termguicolors with jellybeans theme.
It can easily be seen that gui colors are respectively defined as cterm colors except for several cases, this PR fixes this :) The issue was similar in both insert and replace mode. Attached herewith an illustration for insert mode.
Before proposed fix, it looked like this:

After proposed fix, it looks correct:

Best,
gfszr

@chrisbra This PR is almost here for around 8 months, please comment.

I have nothing to say to the jellybean theme unfortunately. Sorry it took so long, let me merge it in then.


Vim9: no error for giving a non-existing variable to :lockvar

Steps to reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    var name: any
    def Func()
        lockvar nameX
    enddef
    Func()
EOF
)

No error is given.
Expected behavior
An error is given because there is a typo in the variable name passed to :lockvar:
lockvar nameX
            ^
            ✘

Operating system
Ubuntu 20.04.3 LTS
Version of Vim
8.2 Included patches: 1-3640
Additional Context
The same thing happens in legacy:
vim9script
var name: any
function Legacy()
    lockvar s:nameX
endfunction
Legacy()
echo 'no error'

no error

Maybe it's a convenient feature, I don't know.
But since Vim9 tries to be more strict, and help the user find their mistakes early, I thought we could give an error, instead of letting them with a variable which they think is locked while in reality it can still mutate, which could give confusing errors much later in their code.

I'm not sure why there was no error for trying to lock or unlock a non-existing variable, but it indeed makes it very hard to spot a typo.


resolved issue, please pull

As per #13, I have changed the templates to support plural tags.
Examples:

http://cloud.ivansmirnov.name/image/0h1W3H2l1p0a
http://cloud.ivansmirnov.name/image/1i2O1j3d3x3K

Sweet, thanks!


Multiple branch build

Is this possible? I've looked through the doc and the open issues and couldn't find anything on this subject.
What's expected: I should be able to specify multiple branches to build from. If multiple developers are doing their stuff in feature branches, a push to any of these branches should trigger a build. Then, all the specified branches are merged into a temporary local branch, and then build should assert that these branches merge cleanly. If they do, then we can run the usual checks, like CS, tests, whatnot.

hello, everyone. Can anybody tell about that issue, does phpci have that functionality? if no, when it can be done if it possible?

It doesn't have this and on this moment there isn't any active plan to add it. But feel free to create a pr to add it


docs: add Roadmap

@achingbrain please feel free to push edits directly to this branch
relates to:

https://github.com/libp2p/js-libp2p/pull/1166
https://github.com/libp2p/js-libp2p/pull/1298
https://github.com/ipfs/js-ipfs/issues/3905

consider pulling in:

https://github.com/libp2p/js-libp2p/issues/824
https://github.com/libp2p/js-libp2p/issues/857
https://github.com/libp2p/js-libp2p/issues/744

Some great stuff here, I'm happy for this to be merged once all the comments above are addressed.

@achingbrain thanks, added a section on "Ergonomic metrics API" and moved the Browser<->Browser to Mid Q2.

@BigLep I think Alex is on PTO, can you take a look to see if we are aligned on the timeline
Specifically this portion
#### End of Q4 (December)
- [A.2 📺 WebRTC: Browser to Server](#2-webrtc-browser-to-server)
- [B.1 🥊 AutoNat](#1-autonat)
- [B.2 🥊 Circuit Relay v2](#2-circuit-relay-v2)

### 2023

#### Early Q1 (January)
- [C.1 🔮 Ergonomic metrics API](#1-ergonomic-metrics-api)
- [***➡ test-plans/DHT server mode scale test***](https://github.com/libp2p/test-plans/blob/master/ROADMAP.md##1-dht-server-mode-scale-test)

#### Mid Q1 (February)
- [A.3 📺 WebRTC: Browser to Browser](#3-webrtc-browser-to-browser)

#### End of Q1 (March)
- [B.3 🥊 Add QUIC Transport](#3-add-quic-transport)
- [***➡ test-plans/Benchmarking using remote runners***](https://github.com/libp2p/test-plans/blob/master/ROADMAP.md#2-benchmarking-using-remote-runners)

C.1 is early Jan (maybe we can get to it sooner but hard to say) because it would be a big QoL improvement for @dapplion and Lodestar, perhaps we can get to it sooner than that.

A.3 is Mid Q1 but I might be underestimating the complexity here. Wdyt?

B.3 is there as a hopeful target but dependent on https://github.com/nodejs/node/pull/44325
(there is recent activity/momentum in that PR though!)


model Path is not compatible with extra_model_paths.yaml

when adding the inpaint folder to extra_model_paths.yaml then Brsuhnet can not load models

Do you need this? Ok, I'll do it.

Done. Try it, please.

yessss, it is working now :).
thank you

would you please also check the CLIP node that is used with PowerPaint.
it does not use the Extra path

SD1.5 text encoder model model.fp16.safetensors should be in clip folder of extra_model_paths.yaml, while pytorch_model.bin is in  inpaint folder of `extra_model_paths.yaml.

SD1.5 text encoder model model.fp16.safetensors should be in clip folder of extra_model_paths.yaml, while pytorch_model.bin is in inpaint folder of `extra_model_paths.yaml.

I checked and the clip is not loading. Could you please check it? Only the clip is not working.


the notification for FA.exe not found comes back even after it's been set and games have been played.

saw this on another PC. win7
this means that create game stays grayed out as well even though he can join and play games.
this persists even if you re-specify the location of FA.

I need log output in order to verify/analyse this

here's the log from another player who has the same bug.
https://drive.google.com/file/d/0BzN9wSaRvA86RUdOUjFudXFuWmM/view?usp=sharing

I experienced that sometimes as well, but not in the last few months. I'll close this for now.


Add ability to scaffolding package with Spatie's skeleton

https://github.com/spatie/package-skeleton-laravel

Just use Spatie's scaffolder as they suggest via template and just run the manuscript play from inside.


System apps do not require valid signatures for files that are not listed in MANIFEST.MF

While trying to figure out how to put classes.dex in an apk file without the invalidating the signatures in the APK file, I found that apks installed to /system/app/ do not require a valid signature for each file. Tested as follows:

Create an apk and install it with adb install TestCmd.apk
Verifify that reinstallation is still possible: adb install -r TestCmd.apk
Add an extra, unsigned file: date > date.txt; zip TestCmd.apk date.txt
Try to install again: adb install -r TestCmd.apk
Installation fails, as expected. Logcat shows (for Android 4.4.4, CM-11-20141107): PackageParser  E  Package nl.lekensteyn.TestCmd has no certificates at entry date.txt; ignoring!

Now I tried to install such a modified on Android 5.1.1 by putting it into /system/app/TestCmd/TestCmd.apk from recovery. Then I restarted and to my surprise the tampered app is still available!
Digging in the framework code, I found the message referenced in PackageParser.java with a special case for PARSE_IS_SYSTEM. According to Yuri, this flag is set for apps from /system/app. This code is from PackageParser.java:
        private static void collectCertificates(Package pkg, File apkFile, int flags)
            throws PackageParserException {
        final String apkPath = apkFile.getAbsolutePath();

        StrictJarFile jarFile = null;
        try {
            jarFile = new StrictJarFile(apkPath);

            // Always verify manifest, regardless of source
            final ZipEntry manifestEntry = jarFile.findEntry(ANDROID_MANIFEST_FILENAME);
            if (manifestEntry == null) {
                throw new PackageParserException(INSTALL_PARSE_FAILED_BAD_MANIFEST,
                        "Package " + apkPath + " has no manifest");
            }

            final List<ZipEntry> toVerify = new ArrayList<>();
            toVerify.add(manifestEntry);

            // If we're parsing an untrusted package, verify all contents
            if ((flags & PARSE_IS_SYSTEM) == 0) {
                final Iterator<ZipEntry> i = jarFile.iterator();
                while (i.hasNext()) {
                    final ZipEntry entry = i.next();

                    if (entry.isDirectory()) continue;
                    if (entry.getName().startsWith("META-INF/")) continue;
                    if (entry.getName().equals(ANDROID_MANIFEST_FILENAME)) continue;

                    toVerify.add(entry);
                }
            }

            // Verify that entries are signed consistently with the first entry
            // we encountered. Note that for splits, certificates may have
            // already been populated during an earlier parse of a base APK.
            for (ZipEntry entry : toVerify) {
                final Certificate[][] entryCerts = loadCertificates(jarFile, entry);
                if (ArrayUtils.isEmpty(entryCerts)) {
                    throw new PackageParserException(INSTALL_PARSE_FAILED_NO_CERTIFICATES,
                            "Package " + apkPath + " has no certificates at entry "
                            + entry.getName());
                }
...

As you can see, files which do not occur in the manifest file (META-INF/MANIFEST.MF) are not checked if they are in /system/app/... which results in the observed behavior.
The relevance of this for make-gapps-zip is that classes.dex can additionally be included in the apk file without breaking the application signature. Another possible result is that adversaries can distribute malicious modifications (additions) to the APKs which are accepted by the system.
To verify the authenticity of APKs, validate the certificate manually and verify the authenticity using jarsigner as described by Chris Stratton at How can I verify the authenticity of an apk file I downloaded?.

Btw, this only applies up to Lollipop. In Marshmallow many ROMs (but not all) do require the APKs content to be equal to filelist stated in the manifest.


Fix for Azure ML SDK web services client

Fix in additional operations extension to call the correct async method that returns the initial request's id

Hi @tudordid, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (tudordid). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Add path property to @ApiOperation

I'm implementing a REST API which does not use a JAX-RS implementation.
There are annotations like @ApiImplicitParam which are intended to use swagger for non JAX-RS services. (as documented here https://github.com/swagger-api/swagger-core/wiki/Annotations#apiimplicitparam-apiimplicitparams)
It would be nice if we also had the possiblity to omit the  javax.ws.rs.Path annotation for a service method and provide the path instead as a property of the @ApiOperation annotation.

Do you use any existing REST framework or did you write one of your own?

We use wicket as web framework and the wicket REST extension which is not a JAX-RS implementation.
Looks to me that the dependency on the @Path annotation is the only obstacle that swagger-core can not be used in my case.

Well, no, it's not the only obstacle. In any case, I don't think we're going to add it to @ApiOperation, and it would require more work in general with a specific Reader (much like the one we're creating for generic servlets). It's unlikely there's going to be an out-of-the-box solution here. You can create your own annotation and produce your own Reader if needed.

Ok. Thanks anyway. Does this reader for generic servlets already exist? The only Reader I can find in the source code is io.swagger.jaxrs.Reader which obviously relies on JAX-RS annotations.

We're in the process of migrating it.

At the moment, we're not looking to add support for additional frameworks. The support for servlets as it's been before is included in 1.5.4.


Create ISSUE_TEMPLATE.md

created more standardized issue template. adherence is up to maintainer

Hey @jasonetorres, I have created the basic issue templates that are given by default from GitHub. So this PR is not needed. I would encourage you to take a look at some other possible improvements :smile:
Happy Contributing!


[Bug]: OpenAPI 3 emitter incorrectly generate duplicate name error

Describe the bug
Simple model definition generates:
@typespec/openapi/duplicate-type-name
Duplicate type name: 'Foo'. Check @friendlyName decorators and overlap with types in TypeSpec or service namespace.

Reproduction
Playground link
Checklist

[X] Follow our Code of Conduct
[X] Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

A slightly more minimal repro
import "@typespec/http";

using TypeSpec.Http;

@service({
  title: "Test Service",
})
namespace DemoService;
model Foo is TrackedResource {
  @path name: string;
}
model Resource {}
model TrackedResource extends Resource {}

Does not repro when without an extends chain 3 deep or more.

the problems comes from the fact that we use Visibility.all to render the unreachable models but when figuring out if the properties are the same we use Visibility.read so Foo gets emitted with both.

though it is weird because it is only doing that with derived models