source_id registration of CSIRO-Mk3L-1-3

label = CSIRO Mk3L 1.3
label_extended = CSIRO Mk3L 1.3
source_id = CSIRO-Mk3L-1-3
institution_id = UTAS
release_year = 2006
activity_participation = [CMIP, PMIP]
aerosol:
description = none
nominal_resolution = none
atmos:
description = unnamed (R21; 64 x 56 longitude/latitude; 18 levels; top level 36355 m)
nominal_resolution = 500 km
atmosChem:
description = none
nominal_resolution = none
land:
description = unnamed
nominal_resolution = 500 km
landIce:
description = none
nominal_resolution = none
ocean:
description = unnamed (128 x 112 longitude/latitude; 31 levels; base 5000 m)
nominal_resolution = 250 km
ocnBgchem:
description = none
nominal_resolution = none
seaIce:
description = unnamed
nominal_resolution = 500 km

@sjphipps can you update the format of the ocean description above? I've had a go below
ocean:
description = MOM2? (128 x 112 longitude/latitude; 31 levels; top grid cell 0-10 m; base level 5000 m)

How about:
description = MOMx (128 x 112 longitude/latitude; 31 levels; top grid cell 0-10 m; bottom grid cell 4600-5000 m)
I feel the need to be a little vague about the MOM version number. The
original CSIRO ocean model was MOM 1.x, but it's been so heavilly modified
and upgraded over the years that it no longer meaningfully corresponds to
any numbered version of MOM. If you think that "MOMx" is too confusing or
vague, then "MOM 1.x" would be adequate.
Also, I've clarified the depth of the ocean: the base of the water column
is at 5000m, but the bottom level is centred at 4800m.

@sjphipps can you update the format of the ocean description above? I've had a go below
ocean:
description = MOM2? (128 x 112 longitude/latitude; 31 levels; top grid cell 0-10 m; base level 5000 m)

--
Dr Steven J Phipps
Paleo Ice Sheet Modeller
Antarctic Gateway Partnership
Institute for Marine and Antarctic Studies
University of Tasmania
Private Bag 129, Hobart, TAS 7001, Australia
Tel  +61 3 6226 6902
Fax  +61 3 6226 2973
https://www.stevenphipps.com
https://twitter.com/StevenJPhipps
University of Tasmania Electronic Communications Policy (December, 2014).
This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise.

@sjphipps is the seaice really on a different grid to the ocean (500 km vs 250 km for the ocean?) I'm assuming these grids are consistent - correct me if I am wrong. The model is now registered, so take a peek at CMIP6_source_id.html let me know if I need to tweak this

@sjphipps just a query, the Mk3 manual (Gordon et al., 2002 - see here) notes that CSIRO Mk3 included the MOM2.2 ocean component:
"The ocean component of the Mk2 model was based on the GFDL Cox (1984) code. In the Mk3
model the ocean component has been upgraded to the GFDL MOM2.2 code (Section 20). This
has been specifically designed to match the horizontal land-sea grid of the Mk3 AGCM."
I'm just wondering why you note MOM1.x above? Is this valid?

Yes, the sea ice really is on a different grid. The CSIRO family of models
have an unusual design feature, whereby the sea ice is on the AGCM grid
rather than the OGCM grid.
The model description looks fine, thanks!

@sjphipps is the seaice really on a different grid to the ocean (500 km
vs 250 km for the ocean?) I'm assuming these grids are consistent -
correct me if I am wrong. The model is now registered, so take a peek at
CMIP6_source_id.html
let me know if I need to tweak this

--
Dr Steven J Phipps
Paleo Ice Sheet Modeller
Antarctic Gateway Partnership
Institute for Marine and Antarctic Studies
University of Tasmania
Private Bag 129, Hobart, TAS 7001, Australia
Tel  +61 3 6226 6902
Fax  +61 3 6226 2973
https://www.stevenphipps.com
https://twitter.com/StevenJPhipps
University of Tasmania Electronic Communications Policy (December, 2014).
This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise.

Yes, this is correct. There have been two different CSIRO ocean models
over time. The first was based on MOM1.x, the second on MOM2.2. The
transition happened at around Mk3.0, so the Mk3.x family of models uses
MOM2.2 while Mk3L uses MOM1.x. Hope this helps to clear things up!

@sjphipps just a query, the Mk3 manual (Gordon et al., 2002 - see here) notes that CSIRO Mk3 included the MOM2.2 ocean component:
"The ocean component of the Mk2 model was based on the GFDL Cox (1984) code. In the Mk3
model the ocean component has been upgraded to the GFDL MOM2.2 code (Section 20). This
has been specifically designed to match the horizontal land-sea grid of the Mk3 AGCM."
I'm just wondering why you note MOM1.x above? Is this valid?

--
Dr Steven J Phipps
Paleo Ice Sheet Modeller
Antarctic Gateway Partnership
Institute for Marine and Antarctic Studies
University of Tasmania
Private Bag 129, Hobart, TAS 7001, Australia
Tel  +61 3 6226 6902
Fax  +61 3 6226 2973
https://www.stevenphipps.com
https://twitter.com/StevenJPhipps
University of Tasmania Electronic Communications Policy (December, 2014).
This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise.

@sjphipps reopening this issue as the seaIce nominal_resolution information is currently incorrect. We'll also have to think about your seaice data contribution as the CMIP6 data request expects data for the siconc variable on the ocean (not atmosphere) grid, and so if you are planning to contribute your seaice data, it'll have to be written as siconca

Thanks for the clarification. Will you reset the seaIce
nominal_resolution to 500km, or do I need to take some action here?

@sjphipps reopening this issue as the seaIce nominal_resolution
information is currently incorrect. We'll also have to think about your
seaice data contribution as the CMIP6 data request expects data for the
siconc
variable on the ocean (not atmosphere) grid, and so if you are planning
to contribute your seaice data, it'll have to be written as
siconca

--
Dr Steven J Phipps
Paleo Ice Sheet Modeller
Antarctic Gateway Partnership
Institute for Marine and Antarctic Studies
University of Tasmania
Private Bag 129, Hobart, TAS 7001, Australia
Tel  +61 3 6226 6902
Fax  +61 3 6226 2973
https://www.stevenphipps.com
https://twitter.com/StevenJPhipps
University of Tasmania Electronic Communications Policy (December, 2014).
This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise.

@sjphipps that change is now made, you can peruse the full details here


[OoB_testing_5.4] : Thread connection fails on NUCLEO_F429ZI + AT233 shield.

Steps to reproduce:

Clone the example, switch to OoB_5.4 branch, mbed update.
Change settings in mbed_app.json. (enabled trace, thread config as below)
Update firmware of gateway with https://github.com/ARMmbed/mbed-os-example-client/tree/master/GW_Binary . Tried with both ThreadDynamic.bin and ThreadStatic.bin
Compile application: mbed compile -t ARM -m NUCLEO_F429ZI -c
Flash binary to target. Output as follows on serial terminal:

Connecting...
[DBG ][evlp]: event_loop_thread
Connection failed!

Here is mbed_app.json
{
    "config": {
        "trace": {
        	"help": "options are true, false",
        	"value": true
        },
        "radio-type":{
            "help": "options are ATMEL, MCR20, NCS36510",
            "value": "ATMEL"
        },
        "mesh-type":{
            "help": "options are MESH_LOWPAN, MESH_THREAD",
            "value": "MESH_THREAD"
        }
    },
    "target_overrides": {
        "*": {
            "target.features_add": ["NANOSTACK", "THREAD_ROUTER", "COMMON_PAL"],
            "mbed-mesh-api.thread-config-panid": "0x0700",
            "mbed-mesh-api.thread-master-key": "{0x10, 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77, 0x88, 0x99, 0xaa, 0xbb, 0xcc, 0xdd, 0xee, 0xff}",
            "mbed-mesh-api.thread-config-channel": 22,
			"mbed-mesh-api.thread-device-type": "MESH_DEVICE_TYPE_THREAD_ROUTER",
			"mbed-mesh-api.heap-size": 14000,
            "mbed-trace.enable": true,
            "platform.stdio-convert-newlines": true,
            "platform.stdio-baud-rate": 115200
        }
    }
}

And here is mbed ls:
mbed-os-example-mesh-minimal (e017eb6fe4e3)
|- atmel-rf-driver (57f22763f4d3)
|- mbed-os (3a27568a505b)
`- mcr20a-rf-driver (d8810e105d7d)

@MarceloSalazar @SeppoTakalo

Issue also seen with GCC_ARM and IAR compilers too.

@mikter @artokin Please check.

@ashok-rao Ah.. Actually, you just told what the problem is.
I don't think the bootstrap continues without IPv6.
Router waits to receive ICMPv6 Router-Adverticement message from Ethernet segment. Then that prefix is cloned into mesh network side, and RF side is started up.
If your test environment does not have IPv6 router, then the router newer starts up.

@SeppoTakalo @mikter @artokin .. I have a working IPv6 tunnel now. Results are still the same unfortunately. Can you please have a look? Screenshot below. mbed_app.json is the same as shown above.

I cannot replicate this.
I'm using your mbed_app.json and it still works
Link: mbed-os-example-mesh-minimal
Elf2Bin: mbed-os-example-mesh-minimal
+-----------------------------+--------+-------+-------+
| Module                      |  .text | .data |  .bss |
+-----------------------------+--------+-------+-------+
| Fill                        |    321 |    47 |    48 |
| Misc                        | 233561 |  2634 |  1691 |
| drivers                     |   2249 |     4 |   164 |
| features/FEATURE_COMMON_PAL |  14317 |    94 |  8431 |
| features/FEATURE_LWIP       |     44 |     0 | 12536 |
| features/mbedtls            | 119141 |    51 |  8867 |
| features/nanostack          |  16618 |    37 | 14134 |
| features/netsocket          |   2819 |    85 |     0 |
| hal                         |    622 |     0 |     8 |
| platform                    |   1742 |    20 |   299 |
| rtos                        |    820 |     4 |     4 |
| rtos/rtx                    |   7347 |    20 |  6870 |
| targets/TARGET_STM          |  17840 |     4 |  1292 |
| Subtotals                   | 417441 |  3000 | 54344 |
+-----------------------------+--------+-------+-------+
Allocated Heap: 24576 bytes
Allocated Stack: unknown
Total Static RAM memory (data + bss): 57344 bytes
Total RAM memory (data + bss + heap + stack): 81920 bytes
Total Flash memory (text + data + misc): 420441 bytes

Image: ./BUILD/NUCLEO_F429ZI/GCC_ARM/mbed-os-example-mesh-minimal.bin
~/src/tmp/mbed-os-example-mesh-minimal$ cat mbed_app.json
{
    "config": {
        "trace": {
            "help": "options are true, false",
            "value": true
        },
        "radio-type":{
            "help": "options are ATMEL, MCR20, NCS36510",
            "value": "ATMEL"
        },
        "mesh-type":{
            "help": "options are MESH_LOWPAN, MESH_THREAD",
            "value": "MESH_THREAD"
        }
    },
    "target_overrides": {
        "*": {
            "target.features_add": ["NANOSTACK", "THREAD_ROUTER", "COMMON_PAL"],
            "mbed-mesh-api.thread-config-panid": "0x0700",
            "mbed-mesh-api.thread-master-key": "{0x10, 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77, 0x88, 0x99, 0xaa, 0xbb, 0xcc, 0xdd, 0xee, 0xff}",
            "mbed-mesh-api.thread-config-channel": 22,
            "mbed-mesh-api.thread-device-type": "MESH_DEVICE_TYPE_THREAD_ROUTER",
            "mbed-mesh-api.heap-size": 14000,
            "mbed-trace.enable": true,
            "platform.stdio-convert-newlines": true,
            "platform.stdio-baud-rate": 115200
        }
    }
}
~/src/tmp/mbed-os-example-mesh-minimal$ mbed ls
mbed-os-example-mesh-minimal (e017eb6fe4e3)
|- atmel-rf-driver (57f22763f4d3)
|- mbed-os (3a27568a505b)
`- mcr20a-rf-driver (d8810e105d7d)

After flashing
[DBG ][ThSA]: Service 3, Uri registration uri: a/as
[DBG ][ThSA]: Service 3, Uri registration uri: a/ar
[DBG ][ThSA]: Service 3, Uri registration uri: c/lp
[DBG ][ThSA]: Service 3, Uri registration uri: c/la
[DBG ][ThSA]: Service 3, Uri registration uri: a/sd
[DBG ][ThSA]: Service 3, Uri registration uri: c/as
[DBG ][ThSA]: Service 3, Uri registration uri: c/ps
[DBG ][ThSA]: Service 3, Uri registration uri: c/cs
[DBG ][ThSA]: service init interface 1, port 61631, options 0
[DBG ][ThSA]: Service 6, Uri registration uri: a/aq
[DBG ][ThSA]: service init interface 1, port 61631, options 0
[DBG ][ThSA]: Service 7, Uri registration uri: a/an
[DBG ][ThSA]: Service 7, Uri registration uri: a/ae
[DBG ][m6Thread]: app_parse_network_event() 0
[INFO][m6Thread]: Thread bootstrap ready
[DBG ][m6Thread]: GP IPv6: fd00:db8::ff:fe00:0
[DBG ][m6Thread]: MAC 16-bit: 00:00
[DBG ][m6Thread]: PAN ID: 07:00
[DBG ][m6Thread]: MAC 64-bit: fe:c2:3d:00:00:04:d1:cf
[DBG ][m6Thread]: IID (Based on MAC 64-bit address): fc:c2:3d:00:00:04:d1:cf
[DBG ][nsth]: getOwnIpAddress()
[DBG ][nsth]: getOwnIpAddress()
connected. IP = fd00:db8::ff:fe00:0

Issue resolved. On my target board (NUCLEO_F429ZI), I had the zero resistor manually shorted to SB122 (SPI pin clash with ethernet controller's CRS_DV pin for a different application) instead of the factory config at SB121 .. which may have interfered with the SPI config for the 6LoWPAN shield.
Closing issue now.

Hi @ashok-rao
Can you also try using binaries from 5.4 RC/OOB branch: https://github.com/ARMmbed/mbed-os-example-client/tree/oob_test_mbed-os-5.4/GW_Binary
NOTE: I believe actually the -static one should be able to boot, even when you don't have proper IPv6 network. Just connect the ethernet cable to somewhere.

Ah, ok.
Thanks for reporting.

@SeppoTakalo , I tried the 5.4 GW_Binary you mentioned above, I'm getting these warnings after that on the gateway and unable to connect the target.
IP Addr: 2a01:348:6:8810::
LL Addr: (STALE 0) b8:27:eb:e6:9f:d4
Router IP Addr: fe80::3f91:4b36:f231:95bb
LL Addr: (STALE 0) b8:27:eb:e6:9f:d4
Neighbour Cache 0
Reachable Time: 36672   Retrans Timer: 1000   MTU: 1280
[DBG ][icmp]: Possible Default Router
[DBG ][ip6s]: Interface ID: 1, ipv6: 2a01:348:6:8810:fec2:3dff:fe04:8a99
[DBG ][6Bo ]: Send MLE Advertisement
[WARN][mDa ]: Unknown neighbour (fe:c2:3d:00:00:04:e4:a3)
[WARN][mDa ]: Duplicate Frame counter: -1
[DBG ][icmp]: Possible Default Router
[DBG ][ip6s]: Interface ID: 1, ipv6: 2a01:348:6:8810:fec2:3dff:fe04:8a99
[WARN][mDa ]: Unknown neighbour (fe:c2:3d:00:00:04:e4:a3)
[WARN][mDa ]: Duplicate Frame counter: -1
[WARN][mDa ]: Unknown neighbour (fe:c2:3d:00:00:04:e4:a3)
[WARN][mDa ]: Duplicate Frame counter: -1
[DBG ][icmp]: Possible Default Router
[DBG ][ip6s]: Interface ID: 1, ipv6: 2a01:348:6:8810:fec2:3dff:fe04:8a99

At least you were able to get IPv6 address from the router 2a01:348:6:8810:fec2:3dff:fe04:8a99
What exactly did not work?
How far away the devices are? Duplicate frame counter might mean transmission errors.
Also, Thread GW images were updated just a minutes ago. They noticed a bug that if Border Router is not the first device to start up, it might take 10 minutes to change mode to router.
Try again by shutting down all devices, then start up the BR, then other devices.

Yes, got the IPv6 address from the GW. The connection from end node failed. The GW and end node are sitting on the same table..maybe few inches away :-). I will try with the new GW binaries & report back.

Closing this as there has not been enough proof that any issues still remaining.
F429CI is part of our CI testing and this problems is not visible there: https://jenkins-internal.mbed.com/job/mbed-os-example-mesh-minimal-6lowpan-hw-test/


glow painter every where

egui_web webgl1 and webgl2 use almost same code .
egui_glow painter use very similar code to web painters.
so i port PostProcess to egui_glow.
and create new crate that only contains painter and context create utility.
Current status(Requires VertexArrayObject support)

Desktop(same as glow and glium)
WebGL2(same as egui_web)
WebGL1(same as egui_web)
WebGL1 + sRGB(same as egui_web)

eliminated VAO by emulating VAO in painter.

What is the motivation for adding egui_glow_painter as a separate crate? If you don't want the winit-stuff of egui_glow, perhaps we can hide that behind a feature-flag instead so we don't get too many crates?

OK I will make more acceptable new PR.


Feature request: Panes

Like tmux.
If this is implemented, it would require changing the main data structure for the terminal buffer to something like this:

type PaneId = u32; // For now, ideally should be String

struct Term {
    ...
    panes: PaneInfo,
    pane_grids: Vec<(PaneId, Grid<Cell>)>,
    // No more Term.grid
}

// Contains the layout of the panes.
struct PaneInfo {
    vertical_sections: u32,
    horizontal_sections: u32,
    panes: Vec<Pane>
}

// A pane. Indicates length & width.
struct Pane {
    width: u32, // in vertical sections
    height: u32, // in horizontal sections
    id: PaneId
}

AFAIK the preferred solution for this is just "use tmux".

Read the about section in the README.
Alacritty is focused on simplicity and speed. Panes, tabs and splits are not vital for a terminal, especially when tmux/screen/byobu already exist.


chore: add dependency manager for Dart

Description
This PR adds the new dependency manager alongside a few changes:

Allow the user to add dependencies for each model in the constraint and presets phase.
As a side effect of the implementation, this enables the user to selectively overwrite options so you do not have to create a new generator instance all the time.

These changes currently live on the dependency_-manager (wups) branch and are a WIP until all generators are adapted, that is why the tests are failing.
Related issue(s)
Read more about the change here: https://github.com/asyncapi/modelina/pull/947
Fixes: https://github.com/asyncapi/modelina/issues/851

/rtm


Docker: Update deviceQuery install script

I encountered a trouble (download time out) while trying to install the prebuillt deviceQuery binary and made the alternative install script.

I encountered a trouble (download time out) while trying to install the prebuillt deviceQuery binary and made the alternative install script.

Hi @gsa88 , there is a Docker build-arg INSTALL_MODE to decide whether to use prebuilt package(s) or to build and install package(s) from source.  This applies to deviceQuery installer as well.
Besides, we prefer official package releases to the ones cloned from VCS, since the former is more stable and well-tested.  Moreover, git clone operations to GitHub from China (where the maintenance team members live) is relatively slow, so the use of direct GIT operations is discouraged. Sorry for the inconvenience.
We will look into the download timeout issue of the deviceQuery binary program. Please stay tuned.


Mac(m1) "read_csv"-->object store size (9.313GiB) exceeds

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):

mac (m1) (8core + 16G memory)
macos 12.3

Modin version (modin.__version__):

modin-0.14.0

Python version:

python3.8.9(intel -version,only after 3.9 match for arm)

Code we can use to reproduce:

Describe the problem

Source code / logs

file type:csv
file size: 1.1GB
fle shape:(327483, 290)
part of this decode by "gb18030"

use pandas to read_csv

import pandas as pd

path1 = "/Users/nobb/Downloads/2022-04-02all.csv"
%time df = mpd.read_csv(path1,encoding="gb18030",low_memory=False)

result:

CPU times: user 27.7 s, sys: 4.75 s, total: 32.5 s
Wall time: 40.4 s

use modin.pandas to read_csv

import modin.pandas as mpd

path1 = "/Users/nobb/Downloads/2022-04-02all.csv"
%time df = mpd.read_csv(path1,encoding="gb18030")

Error:

ValueError: The configured object store size (9.313GiB) exceeds the optimal size on Mac (2.0GiB). This will harm performance! There is a known issue where Ray's performance degrades with object store size greater than 2.0GB on a Mac.To reduce the object store capacity, specifyobject_store_memory when calling ray.init() or ray start.To ignore this warning, set RAY_ENABLE_MAC_LARGE_OBJECT_STORE=1.

I can't find how to gnore this warning or reset ray.init() on the net
arter this i test some different xlsx, even empty "csv" still can't read

i has already
pip install "modin[dask]"
pip install "modin[ray]"
pip install typing

according to after blog i find the slove way, the error said

you need ignore this warning or reset ray.init()

i find two days to slove this problem
first:you need  import ray
you need set something when you import ray init()
import ray
import warnings
warnings.filterwarnings('ignore')
# num_cpus is how much you want use
ray.init(num_cpus=4, ignore_reinit_error=True)
import modin.pandas as pd

start = timer()
pd.read_csv("/Users/nobb/Downloads/2022-04-02审管系all.csv" ,encoding="gb18030")
end = timer()
print(end - start)

result:

10.758918999999992

it's so fast use 4 core the time is the same  4times fast
slove url:https://blog.csdn.net/qq_41865652/article/details/103992998

from a chinese data analyst

Hi @NOBB2333 thanks for posting!
It looks like this was fixed by the following:
import ray
ray.init()

@mvashishtha is this related to #4330 ?

@devin-petersohn Yes, the bug is the same. The solution @NOBB2333 found was to initialize ray with the default object store size. The default object store size was presumably less than 2 GB, the level that triggers the ValueError.

@NOBB2333 your solution will give your mac less object store memory than we suggest. That could potentially lead to worse performance in other Modin operations. I suggest you do one of the following instead:

Set environment variable RAY_ENABLE_MAC_LARGE_OBJECT_STORE=1 when using Modin.
Use a version of Modin with fix #4335 included, e.g. by pip install git+https://github.com/mvashishtha/modin.git@4330-start-modin-on-ray-1-11-0-on-mac

Once #4335 is merged, Modin will automatically do solution (1).

Thank you for  @mvashishtha @devin-petersohn   generous reply.
brefore I thought it would take a long time to solve this problem.
I didn't expect your response to be so fast and efficient.
Through this, I realized that writing a pacage is really not an easy thing.
Thank you very much again，I believe Modin will be the main force in the near future.

@NOBB2333 thanks for the kind comments. Now that #4335 is merged, I'll close this bug. Please reach out again if you have any other concerns.


Robot Framework == 7.0.0 - "List Should Contain Sub List" Output Result Issue.

When List Should Contain Sub List keyword is used from collections library, it gives False as a return value and keyword gets passed. Here values from list2 are present in list1, But it still returns the value as False. Keyword does not result in failure though, Just the value is returned as False which is an abnormal behavior.
Sample Use case:
*** Test Cases ***
Test Case - Collections List Issue
    ${reference_list}    Create List    egg    foo    bar
    ${candidate_list}    Create List    egg    bar
    List Should Contain Sub List    ${reference_list}    ${candidate_list}

Test case is passed
Report Generated:

I would expect return value as True as all the elements from candidate list are present in reference list, This can cause issue when used it as flags for further expansion of testcase.
Packages and Python Version used:
Python 3.10.1
Robot Framework 7.0 (Python 3.10.1 on win32)

It seems that the keyword returned back "None" value right now.

It would be useful if the keyword can return False or True for following usage into some conditions

That False wasn't the return value, instead the keyword accidentally logged the value of the ignore_case argument. I had missed this issue, but the same problem was reported also as #5130 and was fixed in RF 7.0.1.
@MininAS, pretty much all these Should keywords return None (i.e. return nothing) when they succeed. If they fail, they report it with an exception. If you don't want to get the status, you can use the TRY/EXCEPT structure or BuiltIn keywords such as Run Keyword And Return Status.

Thanks for comment, it seems I am losing my touch.
Really need to use RKARS for that because similar keyword don't return anything.

Thanks @pekkaklarck


Translation for Simplified Chinese.

Oh nice! Just so you know the current dev/1.20 branch has a couple new items/Lang changes. I don't think anything else will be added till after the next release so probably makes sense to do those as well. Could do it in this PR or make a separate one. Whatever suits you.

Oh, actually scratch that I'll probably be adding a couple more achievements or just generally fiddle with them some more. I'll try remember to ping you once dev stuff is merged, or just come in here and make another PR after the mod gets another release

ok,I'll wait for it

Hey, the dev/1.20 branch is going to get merged likely within a couple days. I'll pretty confidently say that the lang is finalized so it's safe to translate the stuff there. Can close or rebase the PR either works


properly handle String variables argument, plus tests

related to issue:
https://github.com/RisingStack/graffiti/issues/19

Thanks for the PR @zopf! As far as I know you always need to wrap JSON.parse in a try-catch block. I hope you don't mind if I applied your changes on #23.

Hm.  Do we really want to ignore JSON parsing errors?  I was planning to let those bubble up to top-level middleware handlers...
Seems like somehow the user ought to see that their input is improperly structured.

GraphQL will eventually throw some kind of error if the input is not structured properly, but I might be wrong. Is it true that the variables are always a JSON? Relay includes variables too, and graffiti-todo is working fine without this patch.

graffiti-todo works because it's making a different call:
{
"query":"mutation AddTodoMutation($input_0:addTodoInput!){addTodo(input:$input_0){clientMutationId,...__RelayQueryFragment773nd7g}} fragment __RelayQueryFragment773nd7g on addTodoPayload{changedTodoEdge{cursor,node{id,complete,text}}}",
"variables":{"input_0":{"text":"Testing","complete":false,"clientMutationId":"0"}}
}

As you can see above (just captured on a local session with graffiti-todo), variables is sent as a JSON obj, not as a stringified JSON obj.  I think Relay expects to send them that way, and graphql expects to receive them that way.  The only impedance mismatch is with graphiql's constructor.
The graphql constructor definitely needs variables to be a JSON obj, whereas the graphiql constructor definitely needs variables to be a stringified JSON obj.
You're right that GraphQL will throw an error if the input was incorrectly structured.  If the JSON object is broken, it just won't parse properly, so the variables object will stay a string and be treated as not having been provided.  It won't say "bad JSON object at this parse point" or something... just "GraphQL input of type XXX was not provided" or something like that.
Anyway, my vote is that the error should bubble up, as I'm generally against throwing away exceptions (otherwise, why do they get thrown?).  But you guys own the library, I'll defer to your judgement.

Here's what the GraphiQL devs did in their express-graphiql implementation:
https://github.com/graphql/express-graphql/blob/master/src/index.js#L248


Downgrade okhttp 3.9.0 to 3.4.1

CI build have been failing after okhttp was upgraded. This PR downgrades the version to 3.4.1. We also will investigate why for future okhttp upgrade.

The cause of CI failing may be that td-client was upgraded from 0.7 to 0.8 on https://github.com/treasure-data/digdag/pull/843. As we will investigate why td-client causes the failing, I will close this PR.


PresharedKey usage is broken since version 6.0.2

Hi @jchristn , I have a small problem that maybe has not been noticed, I have version 6.0.1 of the nuget WatsonTcp package currently in my project, I have noticed many improvements in the new versions so I need to implement in my project the current version 6.0.5....
As nothing prevents it I made the update in both client and server and the connection stopped working, like crazy I searched and found that the problem was in: server.Settings.PresharedKey = "1234567891234567"; and await client.AuthenticateAsync("1234567891234567");
Maybe there was some change that I did not see in the implementation, or maybe something is wrong, I would like to have your opinion, thank you very much.

Hi @SnowdenDev I'm sorry for the delay in getting back to you.  Are you indicating that the PresharedKey is hard-coded somewhere in the library?  I'm not seeing it.  I'll do a quick test and report back.


Create skeleton pipeline for project copy HCA

Why
We need to start building the project copying tool in HCA and we need to create the skeleton to map out the structure first
Relevant ticket
This PR
Creates the skeleton pipeline that utilizes the 6 solid stubs that we want to later implement
Also creates a test to see if the solids are passed through the pipeline
Checklist

[ ] Documentation has been updated as needed.

@quazi-broad I think mypy is getting confused because there is no __init__.py in the solids/copy_project module; @eparkmonster  just put an empty __init__.py file at that path and it should pass static type checks.


Add support for parseable-output straight from the frontend

This PR adds initial support for emitting parseable-output JSON directly from swift-frontend.
"began" and "finished" messages are currently supported.

The existing parseable-output library used by the Driver is sunk into Basic and extended with entry-points that accept a CompilerInvocation of a swift-frontend, in addition to existing entry-points used by the Driver that accept a Job.
A new diagnostic consumer is added in order to capture all produced diagnostics during the frontend's execution, mirroring what the printing consumer would do, except simply accumulating diagnostics, on a per-primary-input basis.
For batch jobs, "began" and "finished" messages are emitted on a per-primary-input basis, with quasi-PIDs assigned to the messages of jobs we are "faking". The same scheme as used by the driver is employed to generate quasi-PIDs: start at -1000 and decrement for each next primary input. Non-batch jobs get a real OS PID.

Note: The code in ParseableOutput.h and ParseableOutput.cpp with a  Job-based interface is not new. I tried moving these files carefully to preserve history, but enough stuff seems to have changed to not get nice diffs here.

@swift-ci Please Test Source Compatibility

@swift-ci Please Smoke Test

@swift-ci Please Smoke Test

@swift-ci Please Smoke Test

@swift-ci Please Smoke Test Windows platform

@swift-ci Please Smoke Test Windows platform

@swift-ci Please Smoke Test Windows platform

@swift-ci Please Smoke Test

@swift-ci Please Smoke Test

@swift-ci Please Smoke Test Linux Platform

@swift-ci Please Smoke Test

@swift-ci Please smoke Test

@swift-ci Please Test

@swift-ci Please Test Source Compatibility

@brentdax Thank you for such thorough and insightful feedback.

Build failed
Swift Test Linux Platform
Git Sha - ba2f677daed0578ad9dd2efda70199f21294cfdf

Build failed
Swift Test OS X Platform
Git Sha - ba2f677daed0578ad9dd2efda70199f21294cfdf

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 789504ec10b2c40b32c1e4094766aedc26e8ea5b

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - e3c955c783afde79c330fa7a1f0bd17a86583801

@swift-ci please test

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test Windows platform

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - e7861e6fb3174d4d70e933a83cbc9c6b6b9917c6

Build failed
Swift Test Linux Platform
Git Sha - e7861e6fb3174d4d70e933a83cbc9c6b6b9917c6

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 5053cf030cbfd3b1802e2bb609da5a742bc872e0

@swift-ci please test Windows platform

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 94e56953b3ccf3c5c9fc52a33706ec5291bfad81

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - ed242439584a6ecd6f1f3be2839024e43fbab437

@swift-ci please test

@brentdax ping. The feedback above has been addressed, I believe.

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 234c49ce0d3a86f1d4042b0c8f6374268bedb81c

@swift-ci please test macOS platform

@swift-ci please test

@swift-ci please test


Add anchors to individual attributes in a markdown table

Should be able to update:

https://github.com/open-telemetry/semantic-conventions/blob/main/templates/registry/markdown/attribute_table.j2
https://github.com/open-telemetry/semantic-conventions/blob/main/templates/registry/markdown/attribute_namespace.md.j2

I think the later is the important one, as it gives us the ability to anchor-link to the attribute registry.

Hello @jsuereth is the currently being worked on, or can I take it up please?


add a section before usage for technologies to readme file

spring boot version and database, jquery and others...

I am working on this. Would you like any other information?

add maven
h2 version
jquery version
hibernate title
thank you for commit


mustang not available in Maven Central

Please make mustang available in Maven Central, so other maven/gradle projects can easily depend on it.

mustang 2 alpha 3 is now available there, it was 2 days of work :-(


GHA: extend 'install-cilium-cli' to build from source

This PR extends the 'install-cilium-cli' composite workflow to additionally support building the cilium CLI from source if the corresponding repository is available locally.

Last push split the build and install operations, to avoid issues with caching due to running everything as root


Text input box sometimes collapses after editing text

the current look box deals better with this but textarea node boxes on the whole have sizing issues.


Minor spelling a grammar fixes in readme

Visual diff: https://github.com/amio/badgen-service/pull/142/files?short_path=04c6e90#diff-04c6e90faac2675aa89e2176d2eec7d8

So many typos 😅
Thanks! @lukechilds


Inline CSS not working when running eve *.eve command

Using the npm witheve package to run a file does not load the css from the file.
Use the following gist
https://gist.githubusercontent.com/anonymous/710df37a0e9706193ee9198519595d5e
Once you save it into a file, lets say test.eve, run the command eve test.eve on it to load it in a browser.
View it with the browser, and you will see that the todo items do not get line-through'd, even though their class does change to 'done' when clicked (viewed with the browser inspector).

This is a dupe of #704. Let's track it there instead.


improve preview update performance

I ported https://github.com/sparksuite/simplemde-markdown-editor/pull/634 to easymde.
Previews are now way more performant and less flickery :)

Dang my prettier plugin auto-formatted the code, the changes are way less crazy as it seems. Will remove the reformatting later

Reduced to diff to include only actual changes.
Demo: https://axe312ger.github.io/mdx-live-editor/

A few things I've noticed with this change:

html2idom for some reason has very low download rates, why? If this feature is so prevalent in other editors, what do they use?

Some changes to the markdown still cause the preview to reload. For example changing a header to normal text or vise-versa, or removing a few lines above an iframe. While making text bold does not reload it. This is inconsistent behavior, why do those markdown changes cause a reload while others do not?

@lonaru you are right here, I just ported the old PR. I came accross https://github.com/developit/htm which is low footprint, well maintained and the performance is blazing.
I cant find any more flickering, even when using complex content elements.

I published this branch as npm i @axe312/easymde@beta is anybody wants to play around.
My https://github.com/axe312ger/mdx-live-editor is using this for now, you can use it as demo for this branch :)

Ohh, sorry for not testing the default usecase.
Looks like the way easyMDE handles the preview rendering won't be enough for my mdx editor. I might build my own editor based on codemirror or ace.
Should we keep this PR open? I think I have no use for it anymore, maybe somebody wants to chime in?
Best


fix(react): Avoid using stale deps from closure when executing query in useQuery

Summary
Currently if you change pause it does not recreate executeQuery so it ends up using stale values from deps. In order to ensure that it uses the freshest values without adding another case that can trigger re-renders or break memoization, I made it use state[2] instead with resolves the issue. If this is undesirable I can change it to just add args.pause as a dependency of the useCallback which I think will also fix the issue.
Set of changes

useQuery now uses state[2] instead of deps within executeQuery

Could you provide a unit test or a sandbox/code sample of when this fails specifically please?
I haven't worked on this for a while, but I don't really feel at ease with changing code that can affect a combination of React edge cases.
Not your fault of course, but basically, with strict mode, non-strict mode / older versions, pre- and post-concurrent having been added, and suspense, there's a lot of cases that I'd like to test, if you have a case that previously caused issues

I just found #1982 which does the exact and literal opposite change. So, I'm sorry, but I'll have to ask for a proper bug report here 😅 I want to avoid a situation where we fix one issue and introduce and regress an old one. There's also a lot of manual tests I'll have to do on old sandboxes, so while I don't doubt you had a specific issue in mind, I'll have to assume that this regresses on a separate issue for now

I just found #1982 which does the exact and literal opposite change. So, I'm sorry, but I'll have to ask for a proper bug report here 😅 I want to avoid a situation where we fix one issue and introduce and regress an old one. There's also a lot of manual tests I'll have to do on old sandboxes, so while I don't doubt you had a specific issue in mind, I'll have to assume that this regresses on a separate issue for now

Ha I see, I'll consider an alternative strategy that doesn't regress on the past issue (but I'll need to figure out how to reproduce the old issue first).
Here's a sample that reproduces the bug I was encountering:
https://codesandbox.io/p/sandbox/ecstatic-clarke-tyrf3m
Steps:

Unpause it
Refetching will no longer refetch

I'll have to look at this tomorrow in more detail.
Looking at the change, I don't actually know anymore why the change over from state[2] to deps works.
I also don't know why its dependencies contain getSnapshot still, which is obsolete.
Overall, your change should be correct, although, I'm not sure whether state[2] also then needs to go into deps. Basically, the thinking is, the intention of the code is to bypass the in-render setState via executeQuery, hence, state[2] should be correct, as long as we also update the dependencies.
We could then just test against the old reproduction in the old issue.
But I agree that your change back to the old implementation on the surface makes sense. I'm just not sure if the actual issue is that useCallback's dependencies array is wrong, in the current implementation, in the one before, and in this PR still 🤔
I'd have to test all changes against the reproduction of yours and the old issue, I suppose

This is superseded by #3323. I tested this exact change against this PR's and the prior issue's reproduction and am still testing it against some older edge cases.


RDK-29867 : bring in the missing changes from PR #452

Reason for change: Build fix.
Test Procedure: It builds.
Risks: None
Signed-off-by: Nikita Poltorapavlo<EMAIL_ADDRESS>

To complete picking #775 and #452 from 2010


Bumped version from 1.0.0 to 1.0.1

Coverage remained the same at 28.475% when pulling 3f51879cab804bdc7a2a72bce90760bc8bacd3d3 on version_bump into e26bafe44e90ba9bf68f5b83857e5f25d71a6dff on develop.


Mining Rockets stopping at Build Limit instead of returning

Minecraft Version:
-1.12.2
Forge Version:
-Tried under multiple builds of Forge
Advanced Rocketry Version:
-1.2.6-25
LibVulpes Version:
-0.2.6-16
is this the latest curseforge build?
No and Yes
Explain issue in detail:
Every mining rocket sent up stops at the build limit (256) on its way back down. I have no idea why this happens.
Every now and then, the mining rocket doesn't do its mission, just goes up and comes back down. When this happens, the rocket returns all the way to the launchpad.
I tried the latest build of AR, but it caused an index out of bounds crash every time I opened/interacted with any multiblock machine, so I had to roll that back.

does the issue occur every time, or some of the time?
can you send the crash report you're getting with the latest build?  All the 1.2.x builds should be compatible

Yes, it happens every time the rocket is on a mining mission. Just to test different things, I have tried different areas, biomes, launch pads at various heights to see if any of that made a difference.
I will reinstall the latest build and try it and get the crash reports.

I'm not able to replicate this on my end, are you running any other mods?  What's the most recent build of forge you tried with?

https://pastebin.com/r0YLbt6K
This is the index out of bounds I am getting when I updated to the most recent version of AR and its Lib.
I crashed before I could test the rocket to see if it comes back. Still working on testing that piece.

Ok, just sent two rockets up. 1 vanished completely after it finished its mission. No return, just gone and the monitor was no longer tracking it. The other stopped again at build height.
I know there isn't a lot to go on since it isn't giving any kind of crash to look at.
I have tried this with most versions of Forge from 2566 through today's release of 2578.

I noticed you're running sponge in the crash report you gave me, unfortunately there is a lot of known issues when sponge is used with Advanced rocketry, can you test without sponge installed?

It will be later tonight before I can do that, but yes, I can see what happens when I take Sponge out, not a problem.

Alright, I also just got a chance to look at the code for the crash report and will have that crash fixed shortly.

Taking Sponge off the server proved to be more difficult than I thought it would be...
That aside, removing Sponge did solve the issue of rockets not returning to the launchpad. I did however have to roll back to the previous version of AR because the IndexOutOfBounds issue was keeping the server from even launching. I know you said you are working on that piece.
Your mod is amazing by the way.  I just wanted to say thank you for all your hard work.

Alright, unfortunately due to the shear volume of bugs with advanced rocketry itself I cannot get to sponge compat for a while, I hope you understand.
Thanks for the complements, it really means a lot to me that you like the mod.  I've actually got a whole game in development with a similar concept, minecraft unfortunately has a lot of limitations, especially with performance and dimloading.

I run a server for my students and they wanted to keep AR over the few things we used that required Sponge, so Sponge has been removed from my server permanently. I completely understand why don't have time to get to the compat issues right now and honestly don't blame you. Sponge seems very wonky at best.

you need to disable entity activation for the AR rockets in the Sponge global.conf this is not a bug on either end..

Is this still a issue? Please comment if it is and i will reopen if if you are unable? We are closing old issues to see what is still relevant and needs to be fixed.


Circuit for TCRT5000

I redrawn the circuitry and found that the 4.7K resistor could be positioned like this:

I don't understand why this resistor is there and can I replace two 10K and 4.7k resistors with one 3.3K resistor?
Is there a special connection diagram for the TCRT5000 for MUX?

I assembled a device for 5 piezo and TCRT5000. TCRT5000 assembled without a 4.7k resistor. Everything works fine (I will try to flash it on DualMoko).
It seems to me that 4.7 k is not needed.
Once again, forgive me if I was wasting your time and thank you very much for your library. You are my hero! :)

Thanks for trying it out, I used a 4.7kΩ resistor on the first breadboard because I thought it could be used with the FSR and Roland controller when I eventually convert it to a PCB.
Regarding the MUX, try connecting the yellow signal wire to the pins of the MUX, just like the UNO.

Thak you very much!


Update Dockerfile

Description
The Dockerfile for the repository right now is vanilla and has no optimisation what so ever, the Dockerfile needs to be updated to a multi stage docker file optimised for faster build times and security. Something on the lines of the explanation here

This has been fixed in the tagged PR


Update security-roadmap.md

Updated PAW dead link

@JohanFreelancer9 please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/3997

@Kateyanne Please merge this PR. Thanks


refactor: try groqd for typed sanity queries

I thought this would be an interesting spike. I'm not sure if I'm sold on it yet or not.
Pros:

Zod parsing/types are baked into the groqd API, so that stays in sync as you evolve the query
easier to share/reuse partial queries

Cons:

you kinda have to do two layers of mental translation: [data I want] --> groq --> groqd
groqd doesn't support the full groq syntax, not clear on where those edges are yet

groqd was worth trying out, but I think the limitations to the query language are going to conflict with some of our query patterns. That will make adoption tricky and having two ways to write queries scattered around the codebase seems more like tech debt than an enhancement.


Arabic language text becomes invisible in textboxes.

Describe the bug
Invisible text in Textbox Arabic language
Steps to reproduce the bug

Steps to reproduce the behavior:

Open UWP app Language Settings.
Install Arabic (Algerea) and set it as primary UI language.
Go to 'Xaml Controls Gallery App available in windows store'
Open AllControls->Textbox
Switch keyboard layout to English
Click on textbox to acquire focus
Insert 111111. (it's important to follow all the steps before otherwise the issue won't be reproduced)->Text will be left aligned and visible.
Click outside of the control (loose focus)
Change language to Arabic
Click on the textbox with 111111. ->Text will be right aligned and invisible. You can select it and it will be selected but invisible.
Expected behavior
Click on the textbox with 111111. ->Text will be right aligned and visible.

Screenshots

Version Info
I reproduce this bug even in non WinUI project in simple UWP app. This bug also reproduced in https://github.com/microsoft/Xaml-Controls-Gallery with
PackageReference Include="Microsoft.UI.Xaml
Version 2.4.0-prerelease.200322001

My OS version which reproduces the problem:
version 1909 OS Build 18363.720

Device: Desktop
Additional context

Possible cause: We might not get keyboard layout changed events when we don't have focus (note repro requires removing focus in that step).
Obviously, we shouldn't draw invisible text :)
This would be in the TextBox code, so will require WinUI3, not possible in WinUI2.

Nice!

Reopening per request in #8727

Hi @Mogikan , we tried this on winui3 and it does not repro. Does this repro for you in WinUI3 ?


Improve filters documentation

Issue submitter TODO list

[X] I've searched for an already existing issues here
[X] I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?
No
Describe the feature you're interested in
Currently, the documentation for the filters is a bit barebones and simplistic. Users like me that are new to the syntax are not able to take full advantage of this feature.

I would appreciate it the built in documentation of the UI is extended with some sample documents as well as more examples.
Describe alternatives you've considered
Reading the documentation manually is always an option but the UI should try to be self-documented if possible
Version you're running
2956664
Additional context
No response

The web documentation (FAQ) should also be updated to match: https://ui.docs.kafbat.io/faq/faq#smart-filters-syntax


server crash in h2+caddy config

I'm submitting a...

[*] bug report

What is the current behavior?
server crashed

If the current behavior is a bug, please provide the steps to reproduce
config with h2+caddy as examples
use curl download 100mb file from cachefly use proxy, and ctrl+c to stop curl before download complete.

What is the expected behavior?
server close the error connection asap

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

blinksocks version: [3.3.3]
Node.js version: [10.x]
npm version: [6.x]
os: [debian 9]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix)
server log

events.js:167
      throw er; // Unhandled 'error' event
      ^

Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
    at doWrite (_stream_writable.js:406:19)
    at clearBuffer (_stream_writable.js:517:5)
    at onwrite (_stream_writable.js:465:7)
    at WriteWrap.afterDoStreamWrite [as oncomplete] (internal/http2/core.js:1449:10)
Emitted 'error' event at:
    at onwriteError (_stream_writable.js:425:12)
    at onwrite (_stream_writable.js:456:5)
    at doWrite (_stream_writable.js:406:11)
    at clearBuffer (_stream_writable.js:517:5)
    at onwrite (_stream_writable.js:465:7)
    at WriteWrap.afterDoStreamWrite [as oncomplete] (internal/http2/core.js:1449:10)

Can you install the latest build and check again?
$ npm i -g https://github.com/blinksocks/blinksocks-nightly-releases/raw/master/v3.3.4-20180702071427-d9050ef.tgz

Have you also experienced a large amount memory usage when download a large file via websocket or http2? This will probably be fixed in the next release, please stay tuned.

@micooz yes, last build fix crash problem.
And blinksocks use 167M memory after that download (even cancelled on curl side)

Fixed in v3.3.4, thanks for your participation.


Fix with router

Q
A

Bug fix?
No

New feature?
No

Description

Removed unnecessary bound checks interfaces in ServiceProvider.php. Due to the fact that the service provider of the package is loaded earlier than the service provider of the application.
Removed an incomplete test tests/ServiceProviderBoundIfTest.php that should have checked this

Fixes # (issue)
Checklist

[x] My code follows the style guidelines of this project
[ x I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I wrote unit tests for my code (if tests is required for my changes)
[x] I have made changes in CHANGELOG.md file

Codecov Report

Merging #3 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             master     #3   +/-   ##
=======================================
  Coverage       100%   100%
+ Complexity      149    147    -2
=======================================
  Files            24     24
  Lines           301    299    -2
=======================================
- Hits            301    299    -2

Impacted Files
Coverage Δ
Complexity Δ

src/ServiceProvider.php
100% <100%> (ø)
4 <0> (-2)
:arrow_down:

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 3b41c3c...9d461bb. Read the comment docs.


Fix for issue 47

Here a proposed fix for issue 47.
Added some tests as well.

Thank you!

Thanks to you !


Path to Model Weights

I have ran the training of the network with VOC dataset as shown in the repo and ran the inference like shown. The results which I have got were not matching with that shown in the paper, they were very high (FPR95 was around 95). I thought there was some issues in the training. So, I tested again by replacing the model.pth with the pre-trained network which I have downloade from the link provided but still I got the same result as with the trained network. I don't know what is going wrong here.
This is the output which I got when I have tested with the pre-trained network:

the ouput after inference with coco_ood_val:

the output after inference with voc_val:

Please let me know if any additional info is needed, I have given the information needed to the best of my knowledge.

Hi, thanks for the query. Your energy threshold is 0.0906, which you should not get. This problem occurs when the inference code uses the weights from regnetx_detectron2.pth in the path Flow-Feature-Synthesis/detection/configs. For your information, regnetx_detectron2.pth contains the weights of the pre-trained backbone network. In contrast, your inference code should use the pre-trained FFS model weights provided in the link on README page. Please check the README section titled 'Using Pre-trained FFS Models' to know how to place the pre-trained FFS weights in the correct folder path for the inference code to use these weights rather than regnetx_detectron2.pth. Once you use the pre-trained FFS weights, the inference should first be made on inlier PASCAL-VOC and only then on the outlier dataset such as MS-COCO. When the inference on PASCAL-VOC is complete, the energy threshold should be 0.5959, as also mentioned on the README page. I hope this answers your question.

Hi, Thanks for your quick response. The threshold 0.0906 was obtained when I have trained the network with the config file provided. I don't know why the threshold was that off. As per my understanding, all the required inputs are in the regnetx.yaml file and that should reproduce somewhat close results around the published value. Is that file the only thing or are there anything else to be observed during training. Also, I have used only one GPU instead of 4 ( I don't think that will affect the process).
I have downloaded the final_model.pth from the provided drive link and placed it at /home/jovyan/FFS/Flow-Feature-Synthesis/detection/data/VOC-Detection/faster-rcnn/regnetx/random_seed_0/ as mentioned in the first two steps of using pre-trained model section. Later I have perfomed the inference procedure like mentioned. It is still generating the same threshold value.
I have deleted all the previous .pkl, .pth, .txt files, deleted the final_model.pth and regnetx_detectron2.pth, redownloaded it from the links in the README.md, placed them at the respective places and then ran the inference on custom_voc_val and coco_ood_val before typing this comment but still I got the same result for threshold.
The location of the model:

The location of the regnetx:

Results of voc_custom_val:

Results of coco_ood_val:

The config file:

I have changed the path and then ran the inference using python apply_net.py  --dataset-dir /home/jovyan/Datasets/VOC_DATASET_ROOT/ --test-dataset voc_custom_val --config-file VOC-Detection/faster-rcnn/regnetx.yaml --inference-config Inference/standard_nms.yaml --random-seed 0 --image-corruption-level 0 --visualize 0 but still the threshold value is 0.0906

Hi, I have changed the path in the config file but it didn't change the threshold value. let me know if you need anything else for better understanding of the issue. like config.yaml regnetx.yaml log.txt files produced during inference or any other information to shed more light.
Thank you.

Hi @NikhilMank, It is weird that you still get the threshold value of 0.0906, which means the model is not trained at all and just uses the initial weights. I and a couple of other users had reproduced the results using the same weights provided on the drive which means there is a bug in your code version setup which is hard to know. What I can do is I will run the code again on my machine with the weights I shared on the drive and try to reproduce the results. I will get back to you as soon as possible.

Hi, I will also delete everything, re-download everything again, and do it fresh. I will let you know once after that.
Thank you for your time, much appreciate it.

Hi, Now doing it again fresh made me realised I made a few changes in the inference. I was getting not on same device error when I ran the inference code so I have did the following changes as the errors were shown in the below order:

when I ran inference I got not on same device error @line157 in detection/inference/rcnn_predictor.py so I changed the line to  "det_labels = det_labels[filter_mask.to(det_labels.device)]" from "det_labels = det_labels[filter_mask]
"
same happened @line84 of detection/inference/inference_utils.py so I changed the line to "result.det_labels = det_labels[keep.to(det_labels.device)]"  from "result.det_labels = det_labels[keep]"
same happened @line463 of the same above file so I have replaced the line with “results = results[output_boxes.nonempty().to(results.pred_boxes.tensor.device).cpu()]”

then the inference could continue without error but the threshold is the same. I don't know if these changes are the reason for the wrong inference or not but these are the changes I made.

Hey, I think I know the issue now. I did it again fresh and this time I got a threshold of 0.5971 for voc_custom_val.
The issue was there was a checkpoint saved, the checkpoint was regnetx_detectron2.pth, and it was loading that model despite of giving the model weights in the config file. I don't know how to solve it yet but that was the issue.
This is how it should have happen

but it was happening like this

Do you have any suggestion on how can I solve this in my old workspace?
Also, Please add that we have to change the path to weights in the README.md file as students who are beginners like me don't know how much about operating through config files.

Thank you.

Hi, great that the issue is solved according to my suggestion. Yes, I will add a short note in the ReadME file about the correct way of loading the weights when using the pre-trained model.

Hi, I did not understand why it is searching for a checkpoint during inference. It made sense for me doing that during the training but I don't understand why we need that during infernece? Can you also please tell me how to prevent this from hapenning, like which part should I change in the code base?
Thank you.

Hi @NikhilMank , you cannot prevent this as I think it is a functionality of the Detectron2 framework itself. Please check the class fvcore.common.checkpoint.Checkpointer in this link. It clearly describes that in addition to the trained model weights, the functionality will also search for any checkpointable objects in the code setup. It is not a problem during the training phase since the code setup just has a single model checkpoint in the form of regnetx_detectron2.pth. However, during inference, there are two checkpoints in the code setup in the form of model_final.pth and regnetx_detectron2.pth. Hence, fvcore.common.checkpoint.Checkpointer uses regnetx_detectron2.pth as per the config file assignment. Hope this helps.


Convert type to atom when choosing a different database

We need to convert the database type to atom when selecting a different one. the field came as string and Mysql is always selected.

The type of database should be an atom in the configs with the default database being MySql for this project. Perhaps it should be clearer that we are expecting an atom.


GeoFence Costs is missing total cost field

i type my kWh cost but testmate only track to the loaded energy... but my charging provider charge more costs because of "charging losses" so maybe a field for total costs is better or automatic add ~10% to costs for charging losses

I am sure the cost is calculated by the actual energy "used", not the energy "added", so already have the charging loss considered

I am sure the cost is calculated by the actual energy "used", not the energy "added", so already have the charging loss considered


Include conversation_id in params

Include Conversation ID
THIS PROJECT IS IN MAINTENANCE MODE. We accept pull requests for Bug Fixes ONLY. NO NEW FEATURES ACCEPTED!

Description

I modified the init function in the Bard class to allow a conversation_id parameter to be passed. Its only purpose is to assign the conversation_id attribute of the class to a specified value prior to calling the get_answer function.
Related Issue

https://github.com/dsdanielpark/Bard-API/issues/32
Motivation and Context

I found through local experimentation that this was necessary in order to actually get conversational context. Just reusing the session object on its own didn't seem to be achieving that result.
How Has This Been Tested?

I am running the package in a back end FastAPI application locally with a Flutter Linux app for a front end. To test the context, I began by asking a pair of related questions to the official Bard site. This was my control for what a working, context-aware response looked like. I then used my API to ask the same two questions with the same session reuse pattern suggested in the readme. While I was able to get responses, they did not match the context-aware responses from the official site and the second answer didn't indicate awareness of the first question. However, after making the proposed changes to my local instance of the module, I was able to exactly reproduce the context-aware responses generated by the official site.
Screenshots (if appropriate):
test context prompt

context-aware control response

result when only reusing the session object

result after implementing proposed changes

I may need some clarification on what you mean by the 'developer version'.
My understanding was that I had forked the developer version here:
https://github.com/thecodekitchen/Bard-API
I referenced this fork in the Dockerfile for the following image in my
Dockerhub registry:
https://hub.docker.com/r/codekitchenxyz/bardchat
I have been using that image in a Docker Compose file with a SurrealDB to
run a local Bard interface through a Flutter app on Linux.
Everything has been working great for me using this fork. Here is the code
for the FastAPI backend application where I handle the Bard API code from
my fork.
https://github.com/thecodekitchen/bardchat-python
I hope these links clarify my implementation and how it works. Please let
me know if any of it looks insecure or otherwise inadvisable.
Thanks,
Andy
On Wed, Jun 7, 2023 at 7:42 AM Daniel Park @.***> wrote:

Thank you for your contribution.
I have found that bard is designed to return the most appropriate query
probabilistically, but I have discovered that fixing the conversation_id
when consistently responding to a single context is more efficient. While
the current session maintains some previous conversation when it is fixed,
I have observed that fixing the conversation_id allows us to receive
consistent responses for inference from a single parameter.
Could you please provide examples related to the developer version?
—
Reply to this email directly, view it on GitHub
https://github.com/dsdanielpark/Bard-API/pull/55#issuecomment-1580737911,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5G7TBGLPHIV565YN25ZYWLXKBZL7ANCNFSM6AAAAAAY4RJQ2Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thank you for your sharing! have a nice day!


Migrate to MapboxGL

Maps use Leaflet, we would like to migrate those map components to MapboxGL

https://github.com/kturney/ember-mapbox-gl @chriswhong

Closed by #18


Make the bot able to join groups.

Hi! It will be very useful to make this bot able to join groups.
It is something that can be done with @BotFather.
/setjoingroups — toggle whether your bot can be added to groups or not. Any bot must be able to process private messages, but if your bot was not designed to work in groups, you can disable this.
Will appreciate any feedback from you on this. Thanks!

@shotmk


Update the legal files

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] File:../externals/skia not existed.
[Error] Some error ocurred while parsing changelist file: W:\bqk5-log-b415c83d\change-list-with-redirection.mapped.tsv.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Added Feature Card Component

Description
It is a single card component, which can contain three features about a product with feature title, feature image, feature description, and view more buttons of the feature. It can be used as a template in multiple projects.
Fixes #120
Type of change

[x] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

@kiruba-r11 Resolve conflict

@Ayush7614 conflicts resolved.


[REQUEST Membership]: New membership for baowj-678

GitHub Username
@baowj-678
Github Organization you are requesting membership in

koordinator-sh
Sponsors

@eahydra
@FillZpp
Requirements

[x] I have joined in the community Slack or DingTalk
[x] I often attend Koordinator Community Week
[x] I have reviewed the membership docs
[x] I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application
[x] I have fixed my affiliation in cncf/gitdm)
[x] I am actively contributing to 1 or more Koordinator subprojects

List of your contributions

PRs reviewed / authored:
https://github.com/koordinator-sh/koordinator/pull/1454
https://github.com/koordinator-sh/koordinator/pull/1571
https://github.com/koordinator-sh/koordinator/pull/1586
https://github.com/koordinator-sh/koordinator/pull/1625
https://github.com/koordinator-sh/koordinator/pull/1651

Issues :
https://github.com/koordinator-sh/koordinator/issues/1644

Welcome!

+1 Welcome!

@baowj-678 I have invited you to our organization, please check your email box, and remember to change your organization visibility to public. https://github.com/orgs/koordinator-sh/people
/close

Welcome!


Adding more tests for build + bugfix

This PR adds more tests for building as suggested in https://github.com/emjun/tea-lang/pull/46#pullrequestreview-400447517
During this testing I have discover a bug similar to #38 which is now fixed. The bug caused showing None in the output for the following: +Var_1 ~ +Var_2, +Var_1 ~ +Var_2, +Var_1 ~ -Var_2.
Please review and merge it after #47 as this PR includes a commit from that PR.

Thanks for these fixes!!


Drawer input field not visible on native iPhone12Mini Screen when selected

When testing the example with scrollable content and inputs, the keyboard pushes the field so much to the top that a user cannot see what's being typed: https://73f8jw-3000.csb.app/
If you try to drag it a bit down to get the field into view it closes the whole drawer. In the codebox example the lowest field is possible. I am not sure if there's an easy tailwind fix or if this goes a bit deeper.
https://github.com/emilkowalski/vaul/assets/29236063/999b83a1-19e0-48fb-9952-8edde2a81542

I've faced the same issue but on android OS. any solution? thanks

Make sure you've set a  max-height on the Vaul.Content Component.

Thank you for reporting, I'll working on a fix this week.

@Zawalga @feliche93 Does this happen on any other browser than Brave? I'm only able to reproduce it in Brave.

This should be fixed in the latest release, feel free to open a new issue if this persists.


Show real sources instead of "compiled" source with HoC

 Issue by tleunen
Friday Sep 16, 2016 at 13:49 GMT
Originally opened as https://github.com/storybooks/react-storybook-addon-info/issues/73

At first, I thought the plugin was showing the real sources of a story (the exact code that a story contains), but in fact it's showing the sources from the used components, or compiled sources.
Lets say I have this code and this story:
import MyComp from '../MyComp';

storiesOf('MyComp', module)
.addWithInfo(
    'Default MyComp',
    () => (
        <MyComp />
    ),
    { inline: true, propTables: false }
);

//and MyComp.js, something like:
function enhance(Component) {
  return class EnhanceComp extends React.Component {
    render() {
      return <Component>super enhanced</Component>
    }
  };
}

const MyComp = ({children}) => {
    return
My {children} Component

};
export default enhance(MyComp);

but if MyComp is actually something using HoC, the rendering won't be
<MyComp /> but <EnhanceComp />
It would be best to keep showing MyComp instead because that's what users should use.

 Comment by dimaip
Monday Sep 19, 2016 at 13:36 GMT

Even worse, in my case it may turn into something like this:
<StoryWrapper>
<Themed Button>
The Button
</Themed Button>
</StoryWrapper>

So it would also be good to specify the exact component, the way it works with propTables.
Related to #44

 Comment by gnarf
Friday Oct 21, 2016 at 17:24 GMT

You can also use displayName on the class which is what the react debugger / this addon will use to "name" a class:
//and MyComp.js, something like:
function enhance(Component) {
  class EnhanceComp extends React.Component {
    render() {
      return <Component>super enhanced</Component>
    }
  };
  // default enhancment, just decorate the display name of the parent component
  EnhanceComp.displayName = `Enhanced(${Component.displayName || Component.name})`;
  return EnhanceComp;
}

const MyWrappedComp = ({children}) => {
    return
My {children} Component

};
const enhanced = enhance(MyWrappedComp);
// we want this to look like a normal <MyComp>
enhanced.displayName = 'MyComp';

 Comment by gnarf
Friday Oct 21, 2016 at 17:34 GMT

I was digging into using the "real" source - but it's basically impossible unless you separate each story into it's own .js file and then just use webpacks raw-loader to load the source... I kind of hacked around and did something like this:
storiesOf('MyComponent')
  .addWithInfo('default', `
    ### Source:
\`\`\`js
${require('!!raw-loader!./MyComponent/default.js')}
\`\`\`
`, require('./MyComponent/default.js'))

Found out it works, but how much do we REALLY want that? :)

 Comment by gnarf
Wednesday Oct 26, 2016 at 16:04 GMT

This is the more generalized code I was using in my storybook index.js: https://gist.github.com/gnarf/ea9bd0f76e36516b6f1f38e4aba542a3
I'm using this to export real "example code" for the story

 Comment by mnmtanish
Thursday Oct 27, 2016 at 00:46 GMT

@madushan1000 is it possible to attach the source code with the component using the docgen plugin?
( bad idea! )

 Comment by darioghilardi
Friday Dec 23, 2016 at 11:33 GMT

I just pushed #127 trying to provide a solution for this issue. If you want to provide some feedback it would be great.

@mnmtanish I wonder why it's a bad idea?

@darioghilardi can you explain your suggested solution here?

can't we add an option like a displayName? it'd be an analogous design to the current propTables ... we can't tell by inspecting the code, so we tell explicitly what it is. Or support an extended syntax like propTables: [{myDisplayName: MyObject}, ...]

Hi @ndelangen,
I was working on this feature and ran into something. I'm sorry I can't remember the reason. Please ignore that comment.


Update AboutUs page

Codecov Report

Merging #14 (d4438b7) into master (6997996) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head d4438b7 differs from pull request most recent head ad5d778. Consider uploading reports for the commit ad5d778 to get more accurate results

@@            Coverage Diff            @@
##             master      #14   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[sdl2] Disable X11 feature and make it and Wayland defaults

What does your PR fix?

- Disabling the X11 feature now correctly disables the X11 backend
- Make x11 and wayland features the default on Linux, because that's what you usually always want.
- SDL_HIDAPI_JOYSTICK is set to ON by default, so no need to pass it explicitly

Which triplets are supported/not supported? Have you updated the CI baseline?


facenet model convert to tensorflow lite

Hi, are you able to convert facenet model to tensorflow lite? I have been trying with tensorflow 1.12 but failed with several unsupported options from original graph.

Facenet on tensorflow-lite - get the converted model here
The notebook used to convert the model here

Awesome, many thanks!

tested and worked well ! Suggest to normalize embeddings to be consistent with original facenet output
def l2_normalize(x, axis=-1, epsilon=1e-10):
output = x / np.sqrt(np.maximum(np.sum(np.square(x), axis=axis, keepdims=True), epsilon))
return output
def extract_features(filename):
....
results = l2_normalize(results)
return results

Yes! You are absolutely right. In the android app, I added this step but missed it in the notebook!
thanks for pointing it out @haicongfu :)

@haicongfu Do you plan to open source your tensorflow lite version?

@tigerzhang I used notebook provided by @divSivasankaran  for testing tensorflow lite. I may start work on tensorflow lite facenet on Android and contribute to this project soon.


Reorganize & renumber deploy scripts

Description
Part of an ongoing shift to all scripts in folders && 2-digit numbering.

The existing ordering of the previously numbered scripts has been preserved.
If you have to insert a new script between 2 existing ones, the simplest way is to use a decimal. ie:
07.5_some new script... will be inserted between 07_... and 08_...

Checklist:

[ ] Pull Request references Jira issue
[ ] Pull Request applies to a single purpose
[ ] I've added comments to my code where needed
[ ] I've updated any relevant docs
[ ] I've added tests to show that my changes achieve the desired results
[ ] I've reviewed my code
[ ] I've followed established naming conventions and formatting
[ ] All tests are passing locally

so we can simply do 01, 02, 03... with existing deploy script in each folder and use your suggestion of .1 if needed


Added the Figure Eight Labelled Textual Dataset 40K entries.

I recently found this dataset while searching for few dataset for my current project, although the ones mentioned in this dataset are great, I think this one can also add up to the collection.
I could not find the original author[s], but the link to download this dataset is found on Kaggle here.

That's the CrowdFlower dataset, which is already present in this project. FigureEight, which is now (part of) Appen, used to be called CrowdFlower.


Register with Julia Package Registry

@JuliaRegistrator register

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/29989
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 036990a4c938380c6325dccc3850473234715603
git push origin v0.1.0


bot-calling-meeting not launching

Hello everyone,
I hope this is the right place to ask such a question. I've been following this  guide to create a calling-meeting bot. I had some issues along the way but eventually managed to roughly understand whats going on and got through everything without errors - up until I build the manifest.zip and tried to add it to teams. No errors appeared, but the bot is unable to do anything. For the past few days Ive done everything I possible could imagine (including redoing ALL of the steps on another computer), but I just cant figure out what Im doing wrong.
To clarify:

I follow the steps from the guide mentioned above and receive a manifest.zip
I launch ngrok with ngrok http --host-header=rewrite 3978
I launch the "bot-calling-meeting" sample which has my edited manifest.json aswell as my edited appsettings.json
I upload it to teams or try using the Bot Framework Emulator to get any signs of life but it this fails.

What I personally just cannot understand is why Im supposed to tunnel the port 3978 for ngrok? When I launch the sample bot I get the following:

And this web-page opens on its own:

Here it says once again to connect to http://localhost:3978/api/messages, but in the sample code available here, this port is not mentioned once besides on this very webpage (which is just a plain html text).
In short: My bot cant be reached whatsoever and I dont understand why. The guide tells me to use port 3978 for tunneling but I cant comprehend how this port is ever used. I also dont understand why its instead launching port 5000 and 5001, because I havent seen this port being used at all in the guide or anywhere else.
Lastly Id like to mention that accessing localhost:5001/api/messages gives me the following:

sadly, even when using localhost:5001/api/messages it doesnt seem to work.

I feel like Im just missing something very simple that I however cant figure out myself, so Id deeply appreciate any help! Thanks.
Lil Update: when using the Bot Framework-Emulator on https://localhost:5001/api/messages I indeed get the "welcome to bot" message - however thats all it does and adding it to teams still does nothing. And something else I noticed: I cannot open the URL I forwarded with ngrok, which afaik should be possible:

@JulianJoachim -We are looking into this we will get back to you soon.

@JulianJoachim - You have to run the ngrok on port 5001 or change the port number as 3978 in launchSetting.json.

@Nivedipa-MSFT as said at the bottom, updated part of my question, Ive tried that already.
Accessing the bot then works, but ONLY in the tab opened by running the code. If I go to any other tab or use the forwarded ngrok url (e. g. https://5b26-2a02-8109-9a40-29e4-8d57-acf4-5d4b-b7aa.eu.ngrok.io), I always meet some kind of error. This is probably also why my bot wont respond at all.
I really sticked to what the guide said, and it already misled me with the port issue, so I wonder if there may be something else I have to do thats not mentioned in the guide.
Feel free to check out the error I get on your own at https://5b26-2a02-8109-9a40-29e4-8d57-acf4-5d4b-b7aa.eu.ngrok.io/
On that note, it would be great if, for the future, you could edit the code to instantly launch port 3978. Its unneccesarily complicated that the whole guide is based on port 3978 and suddenly you have to figure out on your own that the sample code doesnt actually use it. Even in the samples' own readme it says port 3978.

@JulianJoachim - Thanks for your feedback. We will update the port number in launchSetting.json.
We will let you know once its updated.

@JulianJoachim - Are you running this code with IIS express?

@Nivedipa-MSFT I am not, Ive tried to do so in the past but it always launched with a 44346 port which seemed wrong to me. Should I be using IIS express?

@JulianJoachim - Could you please check by using Profile CallingBotSample?
Also update the applicationURI  of CAllingBotSample profile to http://localhost/:3978.

@Nivedipa-MSFT Unfortunately I already did both of those things. Ive tried IIS Express once in the beginning but have only been using the CallingBotSample profile for the last few days.
My launchSettings.json looks as such:

Oh. I think I found the problem... In the original launchSettings.json it said "https://localhost:5001" which I simply edited to 3978... I however didnt notice it was using https instead of normal http. Will try it without now.

It seems like this was the only problem for now. Thanks for your assistance!

@Nivedipa-MSFT, sorry for re-opening this thread but I got another difficulty I'm facing and cant seem to find anything online:
I want my bot to run 24/7. Currently, I have to run the code aswell as ngrok on my local machine. The biggest problem here: I always have to update both my code aswell, aswell as the messaging endpoint in the azureportal. Surely theres a better way to do this. Would appreciate if you could give me some instructions, sample code or some online ressources to help me here.

@JulianJoachim - We are checking this internally. We will update you soon.

Ive found a solution that seems to work myself and this no longer is a priority, closing this.


Debug fmt test

This PR is just to demonstrate and test an issue which seems strange.
For a type that is an argument for a dispatchable it is required that it implements the Debug trait. The fmt() method appears to get invoked only in native execution of the runtime and when global log level is info, debug or trace, but only when a client is syncing and importing blocks.
To get a stack trace I implemented the trait to panic, to confirm the above.
The stack trace will look like this:
Version: 3.0.0-5bae08659-x86_64-macos

   0: backtrace::backtrace::trace
   1: backtrace::capture::Backtrace::new
   2: sp_panic_handler::set::{{closure}}
   3: std::panicking::rust_panic_with_hook
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/std/src/panicking.rs:595:17
   4: std::panicking::begin_panic::{{closure}}
   5: std::sys_common::backtrace::__rust_end_short_backtrace
   6: std::panicking::begin_panic
   7: <pallet_template::pallet::Arg as core::fmt::Debug>::fmt
   8: core::fmt::builders::DebugInner::entry::{{closure}}
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/builders.rs:417:17
      core::result::Result<T,E>::and_then
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/result.rs:704:22
      core::fmt::builders::DebugInner::entry
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/builders.rs:403:23
   9: core::fmt::builders::DebugSet::entry
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/builders.rs:492:9
  10: <&T as core::fmt::Debug>::fmt
  11: core::fmt::builders::DebugTuple::field::{{closure}}
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/builders.rs:345:17
      core::result::Result<T,E>::and_then
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/result.rs:704:22
      core::fmt::builders::DebugTuple::field
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/builders.rs:332:23
  12: pallet_template::pallet::_::<impl core::fmt::Debug for pallet_template::pallet::Call<T>>::fmt
  13: core::fmt::builders::DebugTuple::field::{{closure}}
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/builders.rs:345:17
      core::result::Result<T,E>::and_then
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/result.rs:704:22
      core::fmt::builders::DebugTuple::field
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/builders.rs:332:23
  14: <node_template_runtime::Call as core::fmt::Debug>::fmt
  15: core::fmt::write
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/mod.rs:1092:17
  16: core::fmt::Formatter::write_fmt
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/mod.rs:1535:9
  17: <&T as core::fmt::Debug>::fmt
  18: core::fmt::builders::DebugInner::entry::{{closure}}
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/builders.rs:417:17
      core::result::Result<T,E>::and_then
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/result.rs:704:22
      core::fmt::builders::DebugInner::entry
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/builders.rs:403:23
  19: core::fmt::builders::DebugSet::entry
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/builders.rs:492:9
  20: <alloc::vec::Vec<T,A> as core::fmt::Debug>::fmt
  21: core::fmt::builders::DebugStruct::field::{{closure}}
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/builders.rs:154:17
      core::result::Result<T,E>::and_then
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/result.rs:704:22
      core::fmt::builders::DebugStruct::field
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/builders.rs:137:23
  22: <&T as core::fmt::Debug>::fmt
  23: core::fmt::write
             at /rustc/07e0e2ec268c140e607e1ac7f49f145612d0f597/library/core/src/fmt/mod.rs:1092:17
  24: core::fmt::Write::write_fmt
  25: <tracing_subscriber::fmt::format::DefaultVisitor as tracing_core::field::Visit>::record_debug
  26: tracing_core::span::Attributes::record
  27: <tracing_subscriber::fmt::fmt_layer::Layer<S,N,E,W> as tracing_subscriber::layer::Layer<S>>::new_span
  28: <tracing_subscriber::fmt::Subscriber<N,E,F,W> as tracing_core::subscriber::Subscriber>::new_span
  29: <tracing_subscriber::layer::Layered<L,S> as tracing_core::subscriber::Subscriber>::new_span
  30: tracing::span::Span::make_with
  31: tracing_core::dispatcher::get_default
  32: tracing::span::Span::new
  33: frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPallets,COnRuntimeUpgrade>::execute_block
  34: <node_template_runtime::Runtime as sp_api::runtime_decl_for_Core::Core<sp_runtime::generic::block::Block<sp_runtime::generic::header::Header<u32,sp_runtime::traits::BlakeTwo256>,sp_runtime::generic::unchecked_extrinsic::UncheckedExtrinsic<sp_runtime::multiaddress::MultiAddress<<<sp_runtime::MultiSignature as sp_runtime::traits::Verify>::Signer as sp_runtime::traits::IdentifyAccount>::AccountId,()>,node_template_runtime::Call,sp_runtime::MultiSignature,(frame_system::extensions::check_spec_version::CheckSpecVersion<node_template_runtime::Runtime>,frame_system::extensions::check_tx_version::CheckTxVersion<node_template_runtime::Runtime>,frame_system::extensions::check_genesis::CheckGenesis<node_template_runtime::Runtime>,frame_system::extensions::check_mortality::CheckMortality<node_template_runtime::Runtime>,frame_system::extensions::check_nonce::CheckNonce<node_template_runtime::Runtime>,frame_system::extensions::check_weight::CheckWeight<node_template_runtime::Runtime>,pallet_transaction_payment::ChargeTransactionPayment<node_template_runtime::Runtime>)>>>>::execute_block
  35: sp_api::runtime_decl_for_Core::execute_block_native_call_generator::{{closure}}
  36: std::thread::local::LocalKey<T>::with
  37: sc_executor::native_executor::WasmExecutor::with_instance::{{closure}}
  38: sc_executor::wasm_runtime::RuntimeCache::with_instance
  39: <sc_executor::native_executor::NativeExecutor<D> as sp_core::traits::CodeExecutor>::call
  40: sp_state_machine::execution::StateMachine<B,H,N,Exec>::execute_aux
  41: sp_state_machine::execution::StateMachine<B,H,N,Exec>::execute_using_consensus_failure_handler
  42: <sc_service::client::call_executor::LocalCallExecutor<B,E> as sc_client_api::call_executor::CallExecutor<Block>>::contextual_call
  43: <sc_service::client::client::Client<B,E,Block,RA> as sp_api::CallApiAt<Block>>::call_api_at
  44: sp_api::runtime_decl_for_Core::execute_block_call_api_at
  45: sp_api::Core::execute_block_with_context
  46: sc_service::client::client::Client<B,E,Block,RA>::prepare_block_storage_changes
  47: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll

To reproduce, build the node-template from this branch and run a dev chain (alice as validator). Use polkadot-js to send an extrinsic dispatching templateModule.breakIt()
start another node using first node as its bootnode.
To bypass the panic run the second node either with --log warn  or --execution Wasm
This behavior happens on substrate latest master, substrate v2.0.1
It does not happen on substrate v2.0.0-rc4
As far as I know the Debug trait is useful when writing tests for comparing values of a type in assertions, like assert_eq but never realized it was used elsewhere in the runtime.
Questions:
Where does the formatted string get logged/written?
Does it in anyway affect consensus, chain-state?
Is this a bug or by design?

Questions:
Where does the formatted string get logged/written?
Does it in anyway affect consensus, chain-state?
Is this a bug or by design?

So looking at the first few lines of execute_block()
/// Actually execute all transitions for `block`.
	pub fn execute_block(block: Block) {
		sp_io::init_tracing();
		sp_tracing::within_span! {
			sp_tracing::info_span!("execute_block", ?block);

Clearly this is a just attempt to log the block and that is what is eventually invoking Debug::fmt on what ever makes up a block and obviously this includes the transactions and their arguments. Strangely I've never actually seen block being logged in console with info level logging.
Anyway this seems to be a none issue.

afaik, you  must use the native execution of the runtime to have logging work
https://substrate.dev/docs/en/knowledgebase/advanced/executor#execution-strategy
have you tried that? also using substrate v3 is likely the best place to start, v2 is (slowly) being deprecated.