Fake PR to test the tests

@hklai: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

prow/daily-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

prow/daily-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

prow/daily-e2e-bookinfoTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-bookinfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

prow/daily-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

prow/daily-e2e-bookinfoTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-bookinfo

prow/daily-perf-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-perf-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

prow/daily-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

prow/daily-e2e-bookinfoTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-bookinfo

prow/daily-perf-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-perf-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

prow/daily-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

prow/daily-e2e-bookinfoTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-bookinfo

prow/daily-perf-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-perf-tests

prow/daily-unit-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

prow/daily-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

prow/daily-e2e-bookinfoTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-bookinfo

prow/daily-perf-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-perf-tests

prow/daily-unit-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-unit-tests

prow/daily-e2e-pilot-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-pilot-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

prow/daily-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

prow/daily-e2e-bookinfoTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-bookinfo

prow/daily-perf-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-perf-tests

prow/daily-unit-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-unit-tests

prow/daily-e2e-pilot-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-pilot-no_auth

prow/daily-e2e-mixer-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

prow/daily-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

prow/daily-perf-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-perf-tests

prow/daily-unit-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-unit-tests

prow/daily-e2e-pilot-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-pilot-no_auth

prow/daily-e2e-mixer-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-mixer-no_auth

prow/daily-e2e-bookinfoTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-bookinfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

prow/daily-perf-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-perf-tests

prow/daily-unit-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-unit-tests

prow/daily-e2e-pilot-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-pilot-no_auth

prow/daily-e2e-mixer-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-mixer-no_auth

prow/daily-e2e-bookinfoTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-bookinfo

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

prow/daily-perf-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-perf-tests

prow/daily-unit-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-unit-tests

prow/daily-e2e-pilot-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-pilot-no_auth

prow/daily-e2e-mixer-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-mixer-no_auth

prow/daily-e2e-bookinfoTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-bookinfo

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

prow/daily-e2e-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

prow/daily-perf-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-perf-tests

prow/daily-unit-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-unit-tests

prow/daily-e2e-pilot-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-pilot-no_auth

prow/daily-e2e-mixer-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-mixer-no_auth

prow/daily-e2e-bookinfoTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-bookinfo

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

prow/daily-e2e-dashboard.sh
fdeeb05dccefe6ea8149efff79cb52eabc0afa79
link
/test daily-e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hklai: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/daily-dashboard.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-dashboard

prow/daily-unit-tests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-unit-tests

prow/daily-e2e-pilot-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-pilot-no_auth

prow/daily-e2e-mixer-no_auth.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-mixer-no_auth

prow/daily-e2e-bookinfoTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-bookinfo

prow/daily-e2e-simpleTests.sh
6a4a2f8e69429fa29446a417f6ab68f80591c97c
link
/test daily-e2e-simple

prow/daily-e2e-dashboard.sh
fdeeb05dccefe6ea8149efff79cb52eabc0afa79
link
/test daily-e2e-dashboard

prow/daily-perf-tests.sh
fdeeb05dccefe6ea8149efff79cb52eabc0afa79
link
/test daily-perf-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


General question in which conditions a vector lives only in the stack? "Collecting headers to a stack local vector"

General question in which conditions a vector lives only in the stack? "Collecting headers to a stack local vector" https://docs.rs/curl/0.4.6/curl/easy/struct.Easy.html#method.header_function
http://mibpaste.com/r7og1n

Oh  this basically just has to do with lifetimes in Rust. The Easy::header_function requires a closure with 'static which means it can't have any borrowed references, but the Transfer::header_function relaxes this restriction.

Closing for now


Zephyr sample build broken

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution: Linux Ubuntu 18.04
TensorFlow installed from (source or binary): source
GCC/Compiler version: Ubuntu 7.5.0-3ubuntu1~18.04

Describe the current behavior
After the Zephyr build system compiles all of the TFLM library files itself based on the CMakeLists.txt generated by TF's build system, it breaks during linking with undefined references:
...
[ 94%] Linking CXX executable zephyr_prebuilt.elf
...
~/zephyr-sdk-0.12.3/riscv64-zephyr-elf/bin/../lib/gcc/riscv64-zephyr-elf/10.2.0/../../../../riscv64-zephyr-elf/bin/ld.bfd: ../app/libapp.a(all_ops_resolver.cc.obj): in function `tflite::MicroMutableOpResolver<128u>::AddArgMin()':
~/tflite-micro/tensorflow/lite/micro/tools/make/gen/zephyr_vexriscv_x86_64_default/prj/hello_world/cmake/./tensorflow/lite/micro/micro_mutable_op_resolver.h:138: undefined reference to `tflite::Register_AVERAGE_POOL_2D()'
...
(74 other undefined references)

libtensorflow-microlite.a, which TF's build system builds but the Zephyr build system does not use, compiles and links successfully.
Comparing the files included in the libtensorflow-microlite.a (from the log) to the files listed in the generated tensorflow/lite/micro/tools/make/gen/zephyr_vexriscv_x86_64_default/prj/hello_world/cmake/third_party/CMakeLists.txt, my conclusion is that Zephyr is missing the files of MICROLITE_CC_KERNEL_SRCS (listed at tensorflow/lite/micro/tools/make/Makefile:349):
MICROLITE_CC_KERNEL_SRCS := \
tensorflow/lite/micro/kernels/activations.cc \
tensorflow/lite/micro/kernels/activations_common.cc \
tensorflow/lite/micro/kernels/add.cc \
...

Describe the expected behavior
The Zephyr build of the samples should be able to link the executable without undefined references.
Contributing

Do you want to contribute a PR? (yes/no): Yes
Briefly describe your candidate solution(if contributing):

Change tensorflow/lite/micro/examples/hello_world/zephyr_riscv/Makefile.inc:15 and tensorflow/lite/micro/examples/magic_wand/zephyr_riscv/Makefile.inc:18 from
$(eval $(call generate_project,cmake,zephyr_cmake_project.cmake,hello_world,$(MICROLITE_CC_SRCS) $(THIRD_PARTY_CC_SRCS) $(ZEPHYR_HELLO_WORLD_SRCS) $(MICROLITE_CC_HDRS) $(THIRD_PARTY_CC_HDRS) $(HELLO_WORLD_HDRS),,$(LDFLAGS) $(MICROLITE_LIBS),$(CXXFLAGS),$(CCFLAGS),))

to:
$(eval $(call generate_project,cmake,zephyr_cmake_project.cmake,hello_world,$(MICROLITE_CC_SRCS) $(MICROLITE_CC_KERNEL_SRCS) $(THIRD_PARTY_CC_SRCS) $(ZEPHYR_HELLO_WORLD_SRCS) $(MICROLITE_CC_HDRS) $(THIRD_PARTY_CC_HDRS) $(HELLO_WORLD_HDRS),,$(LDFLAGS) $(MICROLITE_LIBS),$(CXXFLAGS),$(CCFLAGS),))

(Add $(MICROLITE_CC_KERNEL_SRCS))
Standalone code to reproduce the issue
make -f tensorflow/lite/micro/tools/make/Makefile TARGET=zephyr_vexriscv hello_world_bin

@laurenmurphyx64 you should consider adding a community supported zephyr build.  It can build the library and the examples daily.
I made one for esp32 last week in #293.
You put a script into tensorflow/lite/micro/tools/ci_build that runs the build and then add a GitHub action to invoke it. It's status is shown on the readme and helps detect breakage sooner.

Just to back up @mocleiri's comment, we'd love to have a community build tracking the Zephyr integration. #293 is a good template to follow, and I've got some similar PRs for RISC-V linked from #322.

Note that TFLM is moving towards encouraging targets to build examples in their own standalone reporitories.
@laurenmurphyx64 , can you try out https://github.com/antmicro/tensorflow-zephyr-vexriscv-examples?
My preference would be to delete zephyr integration from tflite-micro and have everyone use https://github.com/antmicro/tensorflow-zephyr-vexriscv-examples

Note that TFLM is moving towards encouraging targets to build examples in their own standalone repositories.
@laurenmurphyx64 , can you try out https://github.com/antmicro/tensorflow-zephyr-vexriscv-examples?
My preference would be to delete zephyr integration from tflite-micro and have everyone use https://github.com/antmicro/tensorflow-zephyr-vexriscv-examples

@advaitjain That's cool with me! 👍 I'd prefer it too. But if you delete the zephyr integration from tflite-micro, I think the Antmicro repository will no longer work. Their build script uses it to build:
...
make -f tensorflow/lite/micro/tools/make/Makefile TARGET=zephyr_vexriscv $1_bin
...

The Zephyr repo recently added two samples and official build support for TensorFlow Lite Micro as a library and doesn't use the TFLM build system. So, the Zephyr repo will be fine even after integration is removed from the TFLM repo. More details if you're curious: https://github.com/zephyrproject-rtos/zephyr/pull/34057.
I've used the Antmicro repo before and I like it a lot. I referenced their old repository while adding the build support and samples (one has Renode support) to Zephyr. But I'd prefer if Zephyr users were pointed towards the Zephyr repo first now that the support is there.

Happy to get your current fix merged (we get get that in once the CLA is signed).
Adding in @PiotrZierhoffer from Antmicro to this conversation. TFLM won't delete zephyr integration from tflite-micro without a transition plan for the Antmicro repository.
However, the generate_project macro invocation that you are fixing with https://github.com/tensorflow/tflite-micro/pull/333/ is hard to maintain and untested and may again be broken by changes to TFLM.
My primary concern is to make sure that updates to TFLM are less likely to break the Zephyr build. To that end, we are rolling out a new project generation interface.
If you decide to use this project generation interface, then the process of updating tflite-micro in Zephyr would look like:
git clone https://github.com/tensorflow/tflite-micro.git
cd tflite-micro
python3 tensorflow/lite/micro/tools/project_generation/create_tflm_tree.py <path_to_tflite-micro_in_zephyr>

The file paths in CMakeLists would still have to be manually updated. Or you could try and use something like:
python3 tensorflow/lite/micro/tools/project_generation/create_tflm_tree.py <path_to_tflite-micro_in_zephyr> --print_dest_files --no_copy

This create_tflm_tree.py is tested in our CI and the expectation is that it will make it much easier to stay up to date with the TFLM code.
Forking the TFLM samples and having the documentation be Zephyr specific is the way to go.

Cc @mateusz-holenko
I'll be able to get back to this next week

@advaitjain Got myself covered by the CLA. Thanks for letting me know about the new project generation template! I'll look into  using it in Zephyr.

Note that TFLM is moving towards encouraging targets to build examples in their own standalone reporitories.
@laurenmurphyx64 , can you try out https://github.com/antmicro/tensorflow-zephyr-vexriscv-examples?
My preference would be to delete zephyr integration from tflite-micro and have everyone use https://github.com/antmicro/tensorflow-zephyr-vexriscv-examples

==
This sample is broken for the current tflite_micro repo. Are there any other updated samples available?
https://github.com/tensorflow/tflite-micro

Forking the TFLM samples and having the documentation be Zephyr specific is the way to go.

==
Anything done on the following?
Forking the TFLM samples and having the documentation be Zephyr specific is the way to go.
If not, is there any change in the thought process?


how to clearQueue

let audioPlayer = QueuedAudioPlayer()

audioPlayer.clearQueue()  // not work
audioPlayer.reset() // not work

Hey @stfenjobs
You can use my fork version https://github.com/parth0072/SwiftAudio
Let me know if you have any question on that.
Thanks

thank you  @parth0072


Fix schema enums

when limited to the first 100 rows, and the column had missing data in the first 100, the LLM was stating that columns "were placeholders" or it had no available data, which was misleading

Instead, it should mention the data was truncated:

I changed the limit from 100 to 1000; shouldn't seriously affect performance on modern processors(?)
The count was placed in the nested dict vs outer dict.

Seems like a bigger problem than I expected; it won't load the data because it assumes the column is null.


[Feature-wip](MySQL Load)Support cancel query for mysql load

Proposed changes
Issue Number: close #xxx
Problem summary
Notice some changes:

Support cancel query for mysql load
Change the thread pool for mysql load manager.
Fix sucret path check logic
Fix some doc error

Checklist(Required)

[ ] Does it affect the original behavior
[x] Has unit tests been added
[x] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34 seconds
stream load tsv:          485 seconds loaded<PHONE_NUMBER>9 Bytes, about 147 MB/s
stream load json:         41 seconds loaded<PHONE_NUMBER> Bytes, about 54 MB/s
stream load orc:          69 seconds loaded<PHONE_NUMBER> Bytes, about 15 MB/s
stream load parquet:          29 seconds loaded 861443392 Bytes, about 28 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230302031001_clickbench_pr_106778.html

run p0

run buildall

run buildall

run buildall

run p0

run p0

run buildall

run buildall

run compile

run  p0

run p0

run p1

run p1


[sync materialized view]create task failed when refresh by year/quarter/month/week

Steps to reproduce the behavior (Required)
CREATE TABLE t1 (
col1 date,
col2 double,
col3 varchar(20)
) ENGINE=OLAP
DUPLICATE KEY(col1)
COMMENT "OLAP"
DISTRIBUTED BY HASH(col1) BUCKETS 3
PROPERTIES (
"replication_num" = "3"
);
CREATE MATERIALIZED VIEW mv1
DISTRIBUTED BY HASH(col1) BUCKETS 10
REFRESH ASYNC START('2050-12-31') EVERY(INTERVAL 1 YEAR)
AS SELECT col1, col2
FROM t1;
Expected behavior (Required)
query ok
Real behavior (Required)
ERROR 1064 (HY000): Can not get TimeUnit from UnitIdentifier description: YEAR
StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()

mysql> select current_version();
+----------------------+
| current_version()    |
+----------------------+
| MAIN-RELEASE c3faf63 |
+----------------------+

LGTM


Ability to remove the background

First of all, thank you for this repository. I'm having an issue related to after crop. If the CGShapeLayer is smaller than the imageView of the original image, the outside parts are transparent, and after the following code, I couldn't remove the background either, and select the smallest section of the image.
    func cropImage() {
        if path.isEmpty {
            return
        }

        shapeLayer.fillColor = UIColor.black.cgColor
        viewSource.imageView.layer.mask = shapeLayer
        viewSource.imageView.layer.masksToBounds = true

        UIGraphicsBeginImageContextWithOptions(viewSource.imageView.bounds.size, false, UIScreen.main.scale)
        viewSource.imageView.layer.render(in: UIGraphicsGetCurrentContext()!)
        let newImage = UIGraphicsGetImageFromCurrentImageContext()
        UIGraphicsEndImageContext()

        self.completionObservable.onNext(newImage)
    }

If I add this newImage to another imageview and show it, I still see the transparent layers and not just the cropped area itself.
Example:

any update in this. or any workarounds ?

remove alpha layer from the screenshot using a image processing lib


Lab 9 Level 4 order of output

Hi everyone,
for my level 4, the approach I used is to keep an ArrayList of promise,
then using allOf().join() by converting the ArrayList into an Array (after the while loop) and thereby outputting the result.
However, it seems that the order of output is different from the one in codecrunch, (in fact it changes every time I submit it) so I can't pass level four.
I also noticed that when I just try using .join() for each individual promise then I can pass level four and get A, but I know that the lab requires to use allOf() as seen from the introduction.
Any tips on this? Any help would be appreciated!

I think for level4, we need to use allOf.join() to get an ArrayList of CompletableFuture, then after everything is done, we use a for loop to change it to CopletableFuture and then .join() each individual promise and print it out.

Hi @jbkim1999 !
allOf ensures that itself is done after all the promises inside the array is done. So after you call allOf.join(), that means all the promises inside the array are done and now you should still need to look through the array/list again to get the result from each promise.

My way of doing is the same as @snoidetx
Actually even after allOf().join(), the result obtained is null. So I'm kinda curious about how you obtained your randomly ordered result from here haha

Thank you everyone! Now I got it :)
In response to @FYimu, what I did was to use thenAccept() and use x -> System.out.println(x) to print out the response. That was why after calling allOf(...).join(), the one that is finished first print out the output first, so the order of output was random.
after each promise is completed.


fix: response can be aborted during e.g. hasGzipId12

Request/Response can be aborted while doing async stuff... handle it

Codecov Report

Merging #250 into master will decrease coverage by 0.09%.
The diff coverage is 50%.

@@            Coverage Diff            @@
##           master     #250     +/-   ##
=========================================
- Coverage   75.31%   75.22%   -0.1%
=========================================
  Files          11       11
  Lines         555      557      +2
  Branches      126      127      +1
=========================================
+ Hits          418      419      +1
- Misses         48       49      +1
  Partials       89       89

Impacted Files
Coverage Δ

lib/ecstatic.js
72.72% <50%> (-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 d0c3e94...6853bea. Read the comment docs.

I honestly have no idea how to fix the code coverage on this...

I'm honestly not sure how to test this either, these kinda time-dependent things are tough! I say don't sweat the codecov report, I'm not 100% taking it to heart.

I implemented this in the on-finished PR with onFinished.isFinished.


Fix freezing-web docker-compose setup

The docker-compose setup is not working quite right in freezing-web.
This is a simplified version that should get people going without having to build everything from scratch.
This is not quite there yet, there's a matter of bootstrapping the database that I haven't figured out yet. But it's a start.
Maybe another container can start up and run a script to bootstrap the database, then shut down?

For long-term database bootstrapping for dev, we could use a synthetic data set, see #339


Customizable Blocks[Feature]

As of now i couldn't find any functionality to customize different blocks in resume. Resume varies person to person, profession to profession and that's why customizable blocks, I think, are must to have when target is a larger audience.
There can be one Option in settings to enable or disable or to create some blocks as per the user requirement, there is no doubt this would enable a larger set of people to actually customize the resume.
Now, I know the templates have already been defined in the system. which is why i think there is no option to customizable blocks. But one or two flexible, basic templates can be added. And if user adds a new block that block can be appended in the last.
Anyway, I love your app and documentation both. <3

Merging with #90 as both are quite similar in terms of implementation. Will reply to your query there, thank you so much @n-goyal :)


Update API versioning documentation

Update table of supported APIs to reflect the changes in Antrea v1.0
(all CRDs to defined in the same API group). We can now track
versioning of indvidual CRDs independently.
Provide guidelines on which version to use when introducing new CRDs.

Signed-off-by: Antonin Bas<EMAIL_ADDRESS>

Codecov Report

Merging #2482 (92a5590) into main (6f33da3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2482   +/-   ##
=======================================
  Coverage   42.02%   42.02%
=======================================
  Files         148      148
  Lines       18131    18131
=======================================
  Hits         7620     7620
+ Misses       9828     9827    -1
- Partials      683      684    +1

Flag
Coverage Δ

unit-tests
42.02% <ø> (ø)

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

Impacted Files
Coverage Δ

pkg/apiserver/storage/ram/store.go
77.44% <0.00%> (-1.51%)
:arrow_down:

pkg/apiserver/storage/ram/watch.go
88.46% <0.00%> (+3.84%)
:arrow_up:


Re-add some removed ones

xref https://github.com/martenson/public-galaxy-servers/pull/14#issuecomment-333956896
I also hardcoded SIFTED's URL since they couldn't be bothered to use a proper 3xx response code. I'm not interested in now additionally parsing HTML pages for meta tags / javascript that indicates a redirect.

Thanks Eric.


Keep track of rejected transactions in mempool storage service

Motivation

Specifications

Designs

Related Work

Closed by PR #2651.


Issue template isnt working anymore

... maybe something wrong in the config/settings. @MichMich can you see if somethings wrong in the settings of the repo?

@MichMich can you please take a look?

It doesn't appear to see the issue template in the repo. It allows me to create one via settings. But I think it's better if it's part of the repo. Not sure why it doesn't work.

Maybe create a new one then via settings and we move the template over?

this was introduced with this "cleanup" commit 2908c15ea61d39a9fdee3485407e46e6bdd8a8a0
Solution is to revert this which means
rename from .github/ISSUE_TEMPLATE/custom.md
rename to .github/ISSUE_TEMPLATE.md

I tested this on my fork.
@rejas I can prepare a PR with this change only (no changelog) and we merge it on master with mastermerge label to have the fix now (I will not wait until 2024). Because I changed the updatenotification logic this will trigger no notifications. O.k. or other ideas?


PR: Improve messages for missing modules in Variable Explorer

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[ ] Included a screenshot or animation (if affecting the UI, see Licecap)

Improved messages for missing modules in Variable Explorer: Added special messages for numpy and pandas, and another message for other missing modules.
Pandas:

Numpy:

Other modules:

Issue(s) Resolved

Fixes #12563
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:
Juanis2112

@ccordoba12  I applied your suggestions and updated the screenshots!


Setup moderators and trustees dashboard

add automatic watch of the src folder to trigger build when there are changes
fix replacements for common include files ( only the first export was removed )
support both jsx and tsx in the same project

the line with the build script in package.json does not seem to copy .jsx files when combining typescript and jsx  in transforms.
a quick fix is to have two sucrase commands like this:
  "build": "npm run fmt && rimraf .bos/transpiled && mkdir -p .bos/transpiled/src && sucrase ./src -d .bos/transpiled/src/neardevhub-trustees --transforms jsx --jsx-runtime preserve --disable-es-transforms --out-extension jsx && sucrase ./src -d .bos/transpiled/src/neardevhub-trustees --transforms typescript --jsx-runtime preserve --disable-es-transforms --out-extension jsx && node ./build.js",

@Megha-Dev-19 see my latest commit that makes sure that both transpiled tsx and jsx files are copied. It also fixes so that every line starting with export in common.tsx is adjusted to not contain the export statement.

@Megha-Dev-19 Check out the watcher in the latest commit. You can now run npm run build:watch to automatically build when there are changes in the src folder.

@petersalomonsen thank you so much, everything works as expected

Closing, since we will integrate bos-workspace


pendingchannels "confirmation_height" seemingly unset

Funding tx has >1 confirmation and yet it's always been 0.
{
    "total_limbo_balance": "0",
    "pending_open_channels": [
        {
...
            },
            "confirmation_height": 0,
...
        }
    ],
    "pending_closing_channels": [
    ],
    "pending_force_closing_channels": [
    ],
    "waiting_close_channels": [
    ]
}

Closing as duplicate of https://github.com/lightningnetwork/lnd/issues/1217.

apologies :+1:


https://packages.microsoft.com/config/ubuntu/19.10/packages-microsoft-prod.deb not found

Problem encountered on https://dotnet.microsoft.com/download/linux-package-manager/ubuntu19-10/sdk-current
Operating System: Linux Ubuntu 19.10 - x64
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

How did you get to that page, and what is it showing for you? I don't see a 19.10 entry in the dropdown, and the link just takes me to RHEL instructions (the default). We don't have a 19.10-specific package feed, as you can see by the 404.
(Keeping up better is tracked by https://github.com/dotnet/core/issues/2576.)

just guess the package name should exists. but it not.

For what it's worth, the 19.04 repository's packages work in 19.10 for me.

Yeah, https://packages.microsoft.com/ubuntu/19.10/prod/pool/main/ doesn't have the packages just like 19.04 would under: https://packages.microsoft.com/ubuntu/19.04/prod/pool/main/
Should we be expected to install the 19.04 or wait for 19.10 or ...?

Should we be expected to install the 19.04

It's definitely not ideal, but yes, in cases like this you need to use the "nearest" packages available (or an alternative install method like snaps or tar.gz), and they should work. Our plans to get better at having packages for each distro are at https://github.com/dotnet/core/issues/2576.

cannot use 19.04 package on 19.10.
apt update will report error:
Err:2 https://packages.microsoft.com/ubuntu/19.04/prod disco/main amd64 Packages
File has unexpected size (23655 != 156065). Mirror sync in progress? [IP: <IP_ADDRESS> 443]
Hashes of expected file:

Filesize:156065 [weak]
SHA512:12e6dffcd247d1ff067acfa61a3c4eb6078c326c2858feb4f6f141a1d809e22292a78282414a5c103038ea80bb63cd734c7516782c9809c341335083d4e7611b
SHA256:c850f35f1979831ac75641978c397e51519fa22313598ec12bde5f52277044c0
SHA1:1f65f4a7388c22bcf7b7f30fb7bc337c60d94b2e [weak]
MD5Sum:4153a12e4a5629bfb14ed98f4c8ac234 [weak]
Release file created at: Thu, 12 Dec 2019 19:59:19 +0000

@scegg That's caused by an outage tracked at https://github.com/dotnet/core/issues/3988, once that's fixed up it should work.


Degree Converter

Degree Converter with java

@nouvaldhaa Your PR has been merged successfully, Thank you for your contribution.
Give repo a star if it was useful.
Happy hacking.


not install tools

how install DEPENDENCIES

The script installs the dependencies (except nmap and amass at this point) automatically if it does not find the subjack binary installed (very crude check, I know). It should echo that it is installing dependencies on first run.  If you have subjack installed but not the other binaries, you can manually run the commands listed in the code. It is still on my list to create a separate and complete installation script (ref. #4 and #3).
If you are encountering any errors upon first run and you have nmap and amass pre-installed, please paste them here!


Dataset images size?

Hi i have manually labeled some images(.png and .jpg formats) with labelme and i converted the annotations to coco format using labelme2coco tool. My images are all of different size do i have to manually resize them to 512x512 ? If how i can do it without having to redo the labeling? It is fine to have pngs and jpgs in the dataset or i need to convert pngs to jpgs?
Thanks you!

It's always resized, so you don't need to worry about labelling. Concerning the pngs, I think it would work. I didn't try but in data/coco.py where the images are loaded.
    img = cv2.imread(path)
    height, width, _ = img.shape

It doesnt care about channels... Well not sure. Just try out

@suchiz Hi I have the same issue should I have to change my labels and my ground truth data or the network will take care of it?


refactor: migrate library to Lit

Codecov Report

Merging #1991 (6a34174) into master (ab917b0) will increase coverage by 20.56%.
Report is 1676 commits behind head on master.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@             Coverage Diff             @@
##           master    #1991       +/-   ##
===========================================
+ Coverage   54.85%   75.41%   +20.56%
===========================================
  Files          49       13       -36
  Lines        1659      545     -1114
  Branches      406        4      -402
===========================================
- Hits          910      411      -499
+ Misses        671      134      -537
+ Partials       78        0       -78

see 57 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


MV Object Deletion rules

The report says that I have no MV Object deletion rules configured when I have 7 setup for declared-any and 1 for declared-last

Thanks David! Please keep them coming! Really appreciated.

Nilesh,
It is a great tool – even despite the flaws I am loving it and can’t wait for updates. Where has this tool been all my life?
David
From: Nilesh Ghodekar<EMAIL_ADDRESS>Sent: Wednesday, May 24, 2017 11:06 PM
To: Microsoft/MIMConfigDocumenter<EMAIL_ADDRESS>Cc: DLundell<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/MIMConfigDocumenter] MV Object Deletion rules (#5)
Thanks David! Please keep them coming! Really appreciated.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/MIMConfigDocumenter/issues/5#issuecomment-303930997, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AArZPjepd7U0LdGuM6SDr4Zzv_OtiVnPks5r9RpUgaJpZM4Nl96U.

This is fixed in the latest release.


PHP Deprecated:  Calling session_set_save_handler() in PHP 8.4.

Closed via https://github.com/php-forge/yii2-core/pull/55


Split auto-updates into separate actions, generate workflow/fanout boilerplate

Extract shell scripts embedded in auto-updates.yaml into separate files/actions.
Add script to auto-generate workflows based on auto-apply.yaml files in action directories.
Attempt to extract boilerplate and env-var passing and move to inputs/outputs between stages.
Change "update-deps" to support running autogen even on non-go.mod directories.
Add the ability to run automation for just one repo rather than all repos.

/assign @chizhg @n3wscott
(This is not urgent, but might be a general improvement for future automation.)

nit on copyright for all files

/assign @xtreme-sameer-vohra
was going to look at this

nit on copyright for all files

Oops, thanks!
Added licenses to all the Dockerfiles and YAML files under actions

Hey @evankanderson
Unfortunately, Fabian and I may not be able to get to reviewing this together for at least a week, possibly more.
If that doesn't work, I'll un-assign myself so that I am not blocking.


Consider consolidating general checking for TDZ

As @rbuckton  point out in PR #4814, we have multiple ways for checking use before definition for many concepts such as this before super, use before declaration for let and const. We should consolidate the checking to be more general purpose that we can extend rather than continuously create new ways of checking

do you have a proposal?

@mhegazy  not yet. This is for keeping track for now.

if we do not have a suggestion for an immediate action, i would close this issue. keeping a backlog of engineering work items never worked in the past :)


cann't switch user with search guard on ES 6.5.1

hi,
i use to work with search gurad on ES 6.4.2, and it worked perfectly.
when i install ES 6.5.1, i've install with the last version of SG. But i notice that i can't switch user.
when i enter the username/password in the login page of Kibana, it send back pop-up the enter again the information (" Authorization Required")
once i'm connected to kibana, i can logout and go to the login page. or if i enter a new user/password, it will connect with the old one.
did anyone else encounter this situation??
thanks.

Hi there,
could you please check if you've disabled Kibana Spaces in your kibana.yml file?
Like so:
xpack.spaces.enabled: false
The authorization required dialog shouldn't come up. When you use it, your login credentials will be "cached" in the browser headers, which is probably the reason you get logged in with your first user.
More details here: https://docs.search-guard.com/latest/upgrading-560

Indeed, it's my fault. It work now, thank you very much.


0.8.0 RC-2 (Request For Comments)

The latest Release Candidate is 2.  THIS IS THE LATEST RC.
This issue is for reporting issues with this specific version of MeerK40t.
Please do all further testing on this release. Please do not report any further bugs with previous beta releases. Do give any other types of feedback, questions, concerns or comments.

Previous Issue: https://github.com/meerk40t/meerk40t/issues/886
Carry-overs from RC-1

[x] Keybinds with Ctrl do not work
[ ] Continues to try USB on quit; when there is no USB driver selected.
[ ] Polygon and polyline ignore quite a lot of mouseclicks
[ ] Adding elements via the Tools section add those only to the Operations part of the tree, not to the Elements-part:
[ ] Stroke appears nearly invisible when drawing shapes. (OSX)
[ ] It would also help to have any kind of feedback when in a drawing mode.
[ ] Lighting up the selected ribbon button would be fine, or changing the mouse cursor.
[ ] Galvo is still up-side down.
[ ] GRBL still no pre-post gcode.
[x] The loading of some items where the units are units.Length are used and are mixed and matched with svgelements.Length.

Galvo flip might be fixed... unsure.

The interpretation of lengths without units (i.e. mils) has changed. Try:
rect 0 0 1000 1000
circle 1000 1000 1000

The interpretation of lengths without units (i.e. mils) has changed. Try:

This isn't unexpected. I tried to get Sophist to change the default keymaps for circle and rect to account for that change, but I think it fell through the cracks. I think the defaults should now be:
rect 0 0 1in 1in stroke red classify
circle 1in 1in 1in stroke red classify
Or something of that nature. IF we think 'fill black' would be better than 'stroke red', I'm fine with that.

A few minor bugs as I started to use MK 0.8 for preparing files for later burning on 0.7.5 executable...
a. Right click change raster op speed, was not reflected in the Op label. A few more tries changing with right click / speed and through Op properties and it seems to be a bit hit and miss,.

Just tried to load the file I saved in 0.8.0RC2 into MK 0.7.5 and instead of two raster ops I got 1 raster op and two unknown ops.
Circular Nikki Smith - Cici Daisy LASER7.txt

Galvo is still upside down.

The interpretation of lengths without units (i.e. mils) has changed. Try:

It has. They used to be 1:1 with mils/steps in the M2 Nano. But, they got switched to nano meters and then switched again to Pixels. Specifically 1/96th of an inch pixels. This should be somewhat configurable but was part of a larger units upgrade that was needed to correctly process different distances with different devices. GRBL for example runs gcode and can run mm or inch mode though the stepper motors for those typically runs at about 1 mil per step. Ruida runs in micrometers. Galvo lasers have distances that differ based on the lens being used and distance from the material.

The interpretation of lengths without units (i.e. mils) has changed. Try:

This isn't unexpected. I tried to get Sophist to change the default keymaps for circle and rect to account for that change, but I think it fell through the cracks. I think the defaults should now be: rect 0 0 1in 1in stroke red classify circle 1in 1in 1in stroke red classify
Or something of that nature. IF we think 'fill black' would be better than 'stroke red', I'm fine with that.

I've provided PR#902 for this.

I had still quite a lot of old "control+" keybinds from previous versions (therefore PR#900), We should either mention to do a 'bind default' or provide a migration routine.

no gui command line options -z and -Z do not seem to work. -c works, but e.g. a crash with -cZ still shows a GUI crash box showing that wx has still been loaded.

Ran from source with -cZ. When I typed quit at the console prompt, the GUI opened. When I quit I received this crash:
MeerK40t crash log. Version: 0.8.0003 RC2 git on Windows:AMD64 - 4.1.1 msw (phoenix) wxWidgets 3.1.5
Traceback (most recent call last):
  File "D:\MeerK40t-64\Source\meerk40t_meerk40t\meerk40t.py", line 10, in <module>
    sys.exit(main.run())
  File "D:\MeerK40t-64\Source\meerk40t_meerk40t\meerk40t\main.py", line 228, in run
    kernel()
  File "D:\MeerK40t-64\Source\meerk40t_meerk40t\meerk40t\kernel\kernel.py", line 1031, in __call__
    self.set_kernel_lifecycle(self, LIFECYCLE_KERNEL_MAINLOOP)
  File "D:\MeerK40t-64\Source\meerk40t_meerk40t\meerk40t\kernel\kernel.py", line 744, in set_kernel_lifecycle
    plugin(kernel, "mainloop")
  File "D:\MeerK40t-64\Source\meerk40t_meerk40t\meerk40t\gui\plugin.py", line 184, in plugin
    meerk40tgui = kernel_root.open("module/wxMeerK40t")
  File "D:\MeerK40t-64\Source\meerk40t_meerk40t\meerk40t\kernel\context.py", line 389, in open
    return self.open_as(registered_path, registered_path, *args, **kwargs)
  File "D:\MeerK40t-64\Source\meerk40t_meerk40t\meerk40t\kernel\context.py", line 428, in open_as
    self.kernel.set_module_lifecycle(instance, LIFECYCLE_MODULE_OPENED)
  File "D:\MeerK40t-64\Source\meerk40t_meerk40t\meerk40t\kernel\kernel.py", line 955, in set_module_lifecycle
    m.module_open(*args, **kwargs)
  File "D:\MeerK40t-64\Source\meerk40t_meerk40t\meerk40t\gui\wxmeerk40t.py", line 555, in module_open
    context.setting(int, "language", None)
  File "D:\MeerK40t-64\Source\meerk40t_meerk40t\meerk40t\kernel\context.py", line 141, in setting
    load_value = self._kernel.read_persistent(
  File "D:\MeerK40t-64\Source\meerk40t_meerk40t\meerk40t\kernel\settings.py", line 78, in read_persistent
    value = self._config_dict[section][key]
AttributeError: 'Kernel' object has no attribute '_config_dict'

Ran from source with -cZ. When I typed quit at the console prompt, the GUI opened. When I quit I received this crash:

Ah, yes. When you type quit the gui still opens but the kernel has shutdown and thus _config_dict is deleted by that time. It should probably avoid launching the gui in that case or abort the mainloop processing in that case. I'm not quite sure what the correct answer is but I have seen that before and it certainly does need fixing.

Also, for the old style keybinds. These aren't actually needed. The code integrates in a Settings code that does the persistent settings itself rather than depending on wx to perform that with wx.Control this is so that CLI versions can preserve persistent settings etc. This creates the settings in the relevant save-directory which depends on the OS type but also it means that the settings from 0.7.x and before are NOT compatible and thus will never have older carried over settings since that's impossible.

Properties windows should be changed to a lookup based system with pages that are defined rather than type based different window categories.
Properties windows should be changed when the selection changes (not double clicking on something) (I think jpirnay has a stab at that and I thought it was charming but also ties into #879 where the properties weren't reflected the currently selected object.
Images and the screen sizes for correct raster sizes may be in error.
RasterWizard scripts should defer to the planning stage.
Images should have properties to set the DPI of the image. This can often be exactly a raster-step amount on the image but all DPIs are functionally plausible.

Agree with all of the above - we could then have a properties pane.

Discord user @bax had trouble in 0.7.5 getting camera working - initial settings for all 5 cameras are to point at the same default camera rather than having enumerated the cameras on the system at startup and add any newly found ones to the end of the existing list. Of course, you may only be able to enumerate camera devices that are physically attached to the computer rather than streaming devices - streaming devices may need to be manually added.

Properties windows should be changed to a lookup based system with pages that are defined rather than type based different window categories.
Properties windows should be changed when the selection changes (not double clicking on something) (I think jpirnay has a stab at that and I thought it was charming but also ties into [rPi and general issues list (Tat's

I am working on this indeed, but my focus is right now to get my code for item manipulation ported to the new Widget methodology

Collapse All Children on Operations and Elements nodes actually collapse these nodes, whereas for these specific nodes, they should only collapse the children nodes. (Bug in 0.7 and 0.8)
Some elements in my standard test file are not being classified - fewer operations are being created and the elements that should be classified into them are not being classified. These are clearly linked, but without looking the code I am not sure which is cause and which effect. (I will create a PR to fix this.)

I am working on this indeed, but my focus is right now to get my code for item manipulation ported to the new Widget methodology

@jpirnay Jens - I certainly didn't intend any criticism of your progress, and knowing @tatarize I am reasonably sure he didn't either. This is a team effort and we are all doing what we can.

Emphasised elements / bbox is not working correctly.
Select an operation, children have grey background, but corresponding elements in elements part of tree are not emphasised and bbox is not shown. Select the operation children, and the children elements are emphasised. However elements groups where all (not sure which) children are emphasised should also be emphasised.

Simulate is starting bottom left (even though I have not selected Home Bottom in Device Config.

Balor/GRBL settings do not save or load correctly from the crc.
Beep triggers on data send complete but not on wait-finish at the laser.

user_scale_x/y amounts do not seem to take effect correctly.

Just tried to load the file I saved in 0.8.0RC2 into MK 0.7.5 and instead of two raster ops I got 1 raster op and two unknown
I suspect that the Raster op was one generated by Classification and the two unknowns are from the file.

I tested this and it produced no unknown operations.

Python crashes on MK 0.8 exit on Windows - not an exception style crash, python itself crashes.

Only thing I know that causes a windows crash there is a GraphicPath bug. You can sometimes set one and fail to delete it and it'll crash after the program closes. So if you open the program and don't get a crash if you close immediately it might be one of those.
If you open it draw a rect with tools and it crashes it's likely graphicpath with tools or whatever. So try it a few things.

I get it without drawing anything. But perhaps only when I have loaded a file.


Update requirements.txt

Coverage remained the same at 97.131% when pulling f8c10b37bac3727f21aa647b7e41ad76a3ddc9e5 on ipython into c08da329d2b4ce930e743627b8aa07df6269563e on master.


Release Tasks for v7.0.0b4 / v6.4.0

Drop Python 2 CI configurations for master branch

Chainer

[x] Travis CI #8013
[x] AppVeyor #8014
[ ] Jenkins https://github.com/chainer/chainer-test/pull/523
[x] PFN CI #8017

CuPy

[x] Travis CI cupy/cupy#2428
[x] ~AppVeyor~ (not tested on Py2)
[ ] Jenkins https://github.com/chainer/chainer-test/pull/523
[x] PFN CI cupy/cupy#2429

After release:

[ ] Rebuild CI image

We postpone https://github.com/chainer/chainer-test/pull/523 to the next release because it is not a blocker of this beta release.


Underlying Identity Solution

Question/Comment on Identity Mgt
David @ DSoft
Section of RFQ documents
Question/Comment
•	What is the underlying identity engine that is supporting the login.gov solution?

Please see Issue #19.


SLogger cooperation with python logger

Hello i have discovered that every slogging.getLogger call is setting custom _loggerClass to SLogger which as i understand has to be done in order to use SLogger instead original Logger.
However if project is also using original python logger it is beginning to be messy.
After replacement of logger class, original logging.getLogger function is constructing SLogger objects which are added to logging dict but are not configured as other logger objects (log levels are not set for them). Also they are not configurable through slogging.configure since they are not added to slogging dict.
I would propose change to Slogger to reset original _loggerClass so original logging function can work properly?

Happy to merge a PR with this change


can't find the nuxt.ts module from 0.4.14

Describe the bug
I tried to install it on Nuxt3 according to the manual, but I get an error.
ERROR Cannot find module ... /node_modules/bootstrap-vue-3/nuxt.ts

To Reproduce
I set it up according to this manual.
https://cdmoro.github.io/bootstrap-vue-3/getting-started/#installation-nuxt-js-3
export default defineNuxtConfig({
  modules: ['bootstrap-vue-3/nuxt'],
  css: ['bootstrap/dist/css/bootstrap.css'],
})

It seems that /node_modules/bootstrap-vue-3/nuxt.js, which existed until 0.4.13, does not exist in 0.4.14.
Environment (please complete the following information):

OS: Mac 11.7
Version 0.4.14.

@tomomo Faced a similar problem. I tried to add a file "nuxt.ts" from the previous version and it started.

https://github.com/cdmoro/bootstrap-vue-3/releases/tag/v0.4.15


admonish code block do not render properly

I use mdbook-admonish in my book. To test the installation, I wrote:
Some text

'''admonish
A beautifully styled message.
'''

(replace the ' with markdown's fenced block syntax)
When building the book with mdbook serve --open, the block is rendered as plain text without any style and without errors or warnings. I downloaded the package today and I updated mdbook to v0.4.25.
The installation process didn't yield any error either. I installed the package with cargo install mdbook-admonish & mdbook-admonish install path/to/my_book with path/to/my_book set to the correct path.
Attached to this issue, is a minimal working example (as a .zip archive) with all the plugins I use in the book.
docs.zip

I suppose the syntax should be like the following:
```admonish  note  "Note title"
    ...
```

Not sure what happens with must a single admonish...

It doesn't seem to be copying the file mdbook-adminosh.css to the output...

mdbook-adminosh.css is indeed empty, It was like that by default as I installed it via the crate.

Can you run it again?  It should at least not be empty...

@schungx I uninstalled the mdbook-admonish crate and reinstalled it again. This didn't produce any errors. I deleted the previous config files and rerun the installation process for my book. The result remains the same (no errors, no warning, admonish block rendered as plain text). The .css file is still empty and wiped each time I run mdbook serve --open.

Can you try not having a full path?
Just do additional_css = ["mdbook-admonish.css"] in book.toml...

I believe the absolute path is screwing things up because it makes the output file the same as the input file, instead of inside the output directory.

Can you try not having a full path?
Just do additional_css = ["mdbook-admonish.css"] in book.toml...

This solved the issue. Thank you for your help. I believe the README.md is not clear on that point. I will close the issue.


Sorry, this group is not accessible

Gak bisa akses Agile Circles Indonesia

Saya bisa koq --> https://t.me/agilecirclesid

Saya bisa koq --> https://t.me/agilecirclesid

No response?
Then, I will close this issue.

No response?
Then, I will close this issue.


use equals instead of ==

I ran across the issue described in #67 and thought you might consider it more if I went ahead and put up a PR :D

I believe this needs changing on line 149 as well.
And a +1 for this pull request - I was about to make the same request, so you saved me some time :)

Hi! I've just opened another pull request on that issue: https://github.com/libgdx/gdx-ai/pull/105
My solution is a little bit more general and maintains backward compatibility with versions of library, where identity check was used.

This is effectively possible now via a StopCondition added by #105 . There's a EqualsMethodStopCondition available by default now, which should act like this PR does. Thanks for waiting this out so long!


prevent PNG files from cluttering directories

Spencer just got 3700 PNG files - ick!

Tried to replicate behavior in EG and Batch but did not get any PNG files.
Still, better safe than sorry. Added ODS LISTING statement to redirect PNG files to WORK directory.


How to run 1.6 cp example?

I'm new to golang. How could I run 1.6 cp example?
test version: latest main(3ecaf00b33b6b5f94c9e198cfc793b238297147c) and v0.16.0
golang version: go1.20.3 windows/amd64
Use Windows 10
go run .\example\1.6\cp\charge_point_sim.go

result:
# command-line-arguments
example\1.6\cp\charge_point_sim.go:74:67: undefined: ChargePointHandler
example\1.6\cp\charge_point_sim.go:79:2: undefined: checkError
example\1.6\cp\charge_point_sim.go:82:2: undefined: updateStatus
example\1.6\cp\charge_point_sim.go:87:2: undefined: checkError
example\1.6\cp\charge_point_sim.go:88:90: undefined: getExpiryDate
example\1.6\cp\charge_point_sim.go:90:2: undefined: updateStatus
example\1.6\cp\charge_point_sim.go:93:2: undefined: checkError
example\1.6\cp\charge_point_sim.go:94:133: undefined: getExpiryDate
example\1.6\cp\charge_point_sim.go:97:2: undefined: updateStatus
example\1.6\cp\charge_point_sim.go:100:59: undefined: MeterValueSampleInterval
example\1.6\cp\charge_point_sim.go:100:59: too many errors

I made it run like this:
go run ./example/1.6/cp/*.go

The package is not found, most likely due to GOPATH issues. Maybe try running a go mod download && go build <example>.
You may also run the docker containers directly, if you just want to try out the functionality.

The package is not found, most likely due to GOPATH issues. Maybe try running a go mod download && go build <example>.
Still the same error.

You may also run the docker containers directly, if you just want to try out the functionality.
Thanks for the replay. I'll try it with docker.


Create build pipeline

MacOS flakiness continues: https://github.com/microsoft/sammo/actions/runs/7560893210/job/20587901919?pr=11#step:8:121


Embedded browser stuck on cloudflare verification when opening chat.openai.com

Is your feature request related to a problem? Please describe.

Thanks for the helpful extention for vscode.
Describe the solution you'd like:  open the website like in a normal webbrowser, and don't stuck in  the CloudFlare verify loop.

Describe alternatives you've considered:

Additional context:

@ali-yuze this seems like a valid bug of the embedded browser. Not sure if it's fixable, but it seems like something we should look into anyway. Why did you close the issue?


Gracefully handle unexpected source maps

When encountering a source map that the agent doesn't expect (e.g., a css source map), the agent seem to fail to initialize. Here's a sample log entry:
ERROR:@google-cloud/debug-agent: Error processing the sourcemaps. Error: An error occurred while processing the sourcemap filesError: No sources listed in the sourcemap file public/vi-assets/main-b7c14129f872a062abe21d8edb364c0d.css.map

Thanks for letting us know about this issue.  It is being addressed in PR #371 .

@google-cloud/debug-agent version 2.3.2 addresses this issue.

thank you!


[11.x] Fix adding constraints on sqlite

SQLite schema grammar silently ignores adding primary key and foreign key constraints when altering table, this PR fixes that. I understand that this was to preventing failure when running tests using SQLite, but please consider that it's more important to let the user know that these constraints are not actually added. A simple workaround for users that use SQLite for running tests is to simply check for their database before adding constraints:
Schema::table('posts', function (Blueprint $table) {
    // ...

    if (! Schema::getConnection() instanceof \Illuminate\Database\SQLiteConnection) {
        $table->foreign('user_id')->references('id')->on('users');
    }
});

Or alternatively if #49723 merged:
Schema::table('posts', function (Blueprint $table) {
    // ...

    if (! DB::is('sqlite')) {
        $table->foreign('user_id')->references('id')->on('users');
    }
});

I don't see a big reason to change this atm.

@taylorotwell I was trying to fix a long time issue #24876


Optimize updates

Based on some profiling data we did for a client, it seemed that Liquibase was recompiling a lot of often used regexes, e.g.:

The latest code also seems to contain lots of them, e.g. https://github.com/liquibase/liquibase/blob/master/liquibase-core/src/main/java/liquibase/changelog/DatabaseChangeLog.java#L645-L650, resulting in a horrible performance.
Extracting every regex on the critical path shouldn't be difficult. Creating fewer Strings may be more difficult, but would be worth it.
I'd gladly help, but I don't have the reproducer code available, our client does.
┆Issue is synchronized with this Jira Bug by Unito

Hi @paplorinc Thanks for the chart and pointer to There will always be ways we can increase performance.  Can you provide a little more context?  What version were you using?
The code that you pointed to in your link deals with files in the classpath.  How many files are in the application that is running Liquibase?  How big is the classpath?
The image you show has RanChangeSet.isSameAs -
How many changesets are in the changelog?
What type of changesets are being used?
Are changesets inlined as part of the changelog or are they pointers to the files?
There are a bunch of different factors that can affect performance and there are also things outside the code that can be done to help as well.

Hi @molivasdat,
Liquibase version is 4.3.5
We have more than 40K class files from the project. The application classpath is quite big
We have more than 3k changesets in the changelog
We are using SQL format for changesets and all changesets are inlined.

@molivasdat , please let me know if any other information required.

Hi @harshSE If you have a recreate-able test case, I can bump the priority of this and move it along faster.  A GH repo that shows the error is way easier to consume and move through the process.


Feature Request: Set ASSETCATALOG_COMPILER_APPICON_NAME?

Without it set:

With it set:

https://github.com/buildbuddy-io/rules_xcodeproj/pull/932


Update example with correct version syntax

The example was using a wrong version syntax

@roidelapluie I think you are qualified to validate this :)

Thanks!


CacheTool:Fix Unmarshal code and check for loops while scanning

ahh forgot that ts::string_view does not exist anymore


chore(release): v0.1.0

:robot: I have created a release beep boop
0.1.0 (2023-02-06)
Features

add link component. (e0c36bb)

Performance Improvements

custom theme merge logic. (ddd9a1c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/riccox/sira/releases/tag/v0.1.0 :sunflower:


Nomination Green Reviews WG Chair: Antonio di Turi

Dear TAG ENV and Green Reviews WG members,
Due to me stepping down as the Green Reviews WG co-chair and transitioning into a TAG Tech Lead role, the working group needs a second chair that can together with @nikimanoledaki drive further the group and the projects that are being worked on in the group, according to it's mission.  It is my pleasure to nominate Antonio di Turi (@AntonioDiTuri) for the chair role for the Green Reviews WG.
Antonio has been an invaluable member of the Green Reviews working group since its inception, demonstrating significant commitment and enthusiasm. Antonio's active participation in the working group meetings has positively affected collaboration and contributed to the meaningful discussions in the group. His contributions extend beyond mere attendance of group meetings - he's also one of the most active contributors in the green-reviews-tooling repository, especially when it comes to discussions and engagement in the repo's GitHub Issues.
Antonio consistently raises thought-provoking questions that highlight potential gaps and areas for enhancement within the working group. His proactive approach to identifying and resolving challenges demonstrates a keen eye for detail and a genuine concern for the group's success.
In addition to his individual contributions, Antonio has taken initiative in coordinating and collaborating with Melissa and other Falco maintainers by driving discussions like potential ways to implement testing with synthetic workloads in our assessment pipeline.
Upon discussion with Antonio, it is evident that he is willing to step up into the role as the Green Reviews working group chair.
Please consider this nomination for Antonio.
All community members are welcome to vote by leaving a comment on this issue. Votes are non-binding for community members and binding for TAG Chairs & TLs. Please vote (+1/0/-1) by replying to this thread.
As mentioned in the TAG ENV Governance:

Community nominations will run for at least 2 weeks, with a maximum up to 1 months. The TAG Chairs will take a vote. Upon close of nominations, a decision should be made within the next month.

Kind regards,
Kristina

+1 NB for Antonio!

+1 NB!

+1 NB

+1 B

The nomination is now open for over two weeks and passed the vote. I opened the PR to add @AntonioDiTuri as a Chair to WG Green Reviews. Thank you very much for your volunteering and congratulations!


tools: cherry-pick fpgadiag changes from N3000 release

Coverage remained the same at 81.042% when pulling fea821487a0f45623f0735e99b5fde20924a3aa5 on aravuri/vc_fpgadiag into d206d14431d001fbe76c144c2fa46e39d587ef39 on master.

What kind of testing was performed?

tested on VC system


An option to change error message to error stack

Currently only the error message is available:
https://github.com/SamVerschueren/listr/blob/88dca6293690b560509fdcfe253b93a6c32ae01c/lib/task.js#L184-L192
and in case a dumb JavaScript error like Cannot convert undefined or null to object leaks through, this message is the only thing available to debug.
With the listr-multiline-renderer, the multiline stack is properly printed.

The error is thrown further upstream, so you are able to catch it and print it after the tasks exit.
'use strict';
const Listr = require('listr');

const tasks = new Listr([
	{
		title: 'Do something',
    task: () => {
      throw new Error('foo bar');
    }
	}
]);

tasks.run().catch(err => {
	console.error(err);
});

Which results in:

But this doesn't seem to apply if I'm setting exitOnError to false (which I need to do).

So just to be clear, you want to be able to show the error stack in the listr-update-renderer?
Currently, only the error message is sent to the renderers. What I could do though is emitting the entire error.
this.next({
	type: 'ERROR',
	data: err
});

That way, you have more control in a custom renderer as I don't think I will ever print the entire stack trace in the update-renderer. It will totally break the UI.

Yes, in the listr-multiline-renderer which seems to be a fork of listr-update-renderer that allows multiline output.
Please let the users decide whether the stack breaks the UI or not. You can have an option for that (e.g. a renderErrorStack or errorRenderMode option) but not just silently discard useful bits of information that can help find the root cause of an error.

I'm 👍 with this. Requires updates in listr-update-renderer and in listr itself to dispatch the full errors.

Any updates on this? Would appreciate it too, if the error is passed completely.


Documentation in regards to Test Environment

🚀 Feature Proposal
(Possibly not a feature proposal, but also not a bug per se)
Having recently invested time in understanding Jest properly, one of the hardest concepts to understand was the term "test environment". This was especially hard in relation to these configuration options:
globalSetup: './globalSetup.js',
globalTeardown: './globalTeardown.js',
testEnvironment: './myTestEnvironment',
setupFiles: ['./setupFiles'],
setupFilesAfterEnv: ['./setupFilesAfterEnv'],

For reference, it is good to explain some terminology:
test file testA.test.js
test case test() # or it()
test suite describe() (I am not sure this is true. Reason is that the documentation seems to use the word "test file" and "test suite" interchangeably but actually always mean "test file". Never seen describe() referred specifically to "test suite" in the Jest documentation, so maybe it isn't a test suite?)
The problem I had with the documentation
If we take these terms, together with the "test environment" term and the above configuration options, I found some parts of the documentation ambiguous.
https://jestjs.io/docs/en/configuration#setupfiles-array

Since every test runs in its own environment,

Concern: It should probably say "every test file" instead of "every test". Refer to terminology above.
https://jestjs.io/docs/en/configuration#setupfilesafterenv-array

A list of paths to modules that run some code to configure or set up the testing framework before each test.

Concern: It should probably say "before each test file" instead of "before each test". Refer to terminology above.
https://jestjs.io/docs/en/configuration#globalsetup-string

This option allows the use of a custom global setup module which exports an async function that is triggered once before all test suites.

Concern: Not sure what to write here, but "before all test suites" can be interpreted in various ways as a test suite can be considered a describe() block.
Solution proposal
It would be good to go through both the Configuring Jest and Jest CLI Options documentation, and possible all other docs, to align this properly.
I also think that in general, having a completely specific section (possibly as a guide) describing what a test environment is and how it relates to the above specified configuration options would be great. The way I learnt was to setup a project and testing all these files with a bunch of console.log to actually see what happened.
Motivation
To make it easier for newcomers to understand Jest and how to extend its functionality.
Pitch
It belongs in the main Jest documentation as that is what users refer to when learning Jest.

I think we should use the unambigious terms 'test file' and 'test case', and only those terms. 'Test suite' is way too ambigious. 'Describe block' would be fine if we need that terms somewhere as well.
Also happy to take PRs improving the test environment section of the configuration page - we could consider moving that into a "Creating test environments" guide as it's quite extensive already.

@jeysal Would you say 'test file' is equal to 'test environment'? It is kind of a rhetorical question from my side, as each test file does run in it's own environment. So they are 1-to-1 if I understood all this correctly. The documentation often use both terms, but I think that in some cases it is more correct to use one over the other, but I am not sure exactly where to distinguish there. I am not sure it is even possible to strictly define these two to know when to use which one.

Clear no on that, it's n test files to 1 test environment - this is a test environment, and this is a test file running in that environment.

I am confused, how can multiple test files run in one environment? E.g. https://jestjs.io/docs/en/configuration#setupfilesafterenv-array specifies that it is "installed in the environment" and the files specified there are definitely run once per test file. If what you are saying are true, then I must have misread the docs in multiple places.

I think you do get it right, it's just another case of wording ambiguity. The environment is indeed instantiated once per test file.

@jeysal Great, thanks for clarifying. Let's see if I or someone else steps in as a hero and tries to make it slightly less confusing in the docs.

/unstale

unstale

The bot runs every 10 minutes, doesn't react to the comment event 🙂
But yes, we should explain this better

Not sure if we should close this or not. The comments are relevant, but I don't have time to fix them and not sure others have either.


Tab stops not aligned when option 'tabstospaces' is on

Hi there,
I like this editor so far but have found a problem when using it with the option tabstospaces turned on.
Observed behaviour
Whenever I press the tab key, four spaces are inserted, no matter in which column the cursor actually is at the moment.
Expected behaviour
When I press the tab key, I would like to have as many spaces inserted as are needed to take me to the next tabsize * x + 1th column. So, to illustrate, assuming that tabsize is set to 4:

If I am currently in column 1 (the cursor is at the beginning of the line), I want the tab key to insert 4 spaces.
If I am currently in column 2 (I wrote one single character at the beginning), I want the tab key to insert 3 spaces.
...
If I am currently in column 4, I want the tab key to insert a single space
If I am in column 5, I want the tab key to start over again by inserting 4 spaces.
???
profit

Starting point/possible cause
I had a look at the InsertTab function and I am pretty sure the solution to this issue lies somewhere in ll. 689 to 693. I could take this up myself, but I have never contributed to any Go project until now, so I'm hesitating.

This bug is a tad annoying... @zyedidia @fceschmidt  are either of you looking into a fix? If not, I'd be happy to.

@tanuck I haven't looked into it, so you're free to go as far as I am concerned.

Yeah I haven't done anything about this either. It shouldn't be too hard to fix.


Impl IntoOptPropValue for Option -> Option

The only implemented types are those passed to impl_into_prop! macro
Description
I need this so I can pass Option<String> to some html attributes such as style and id.
Here is an simplified example of what I have:
impl Compoent for Input {
    fn view(&self) -> Html {
        // this is Option<String>
        let input_style = self.design_system.get_style::<Input>(self);
        <input style=input_style ...etc />
    }
}

without this PR I get error saying:
error[E0277]: the trait bound `Option<std::string::String>: IntoPropValue<Option<Cow<'static, str>>>` is not satisfied
   --> src/input.rs:258:30
    |
258 |                        style=input_style
    |                              ^^^^^^^^^^^ the trait `IntoPropValue<Option<Cow<'static, str>>>` is not implemented for `Option<std::string::String>`
    |
   ::: .../yew/packages/yew/src/virtual_dom/mod.rs:69:47
    |
69  |     pub fn new(key: &'static str, value: impl IntoOptPropValue<AttrValue>) -> Self {
    |                                               --------------------------- required by this bound in `PositionalAttr::new`
    |
    = note: required because of the requirements on the impl of `IntoOptPropValue<Cow<'static, str>>` for `Option<std::string::String>`

Checklist

[ ] I have run cargo make pr-flow
[ ] I have reviewed my own code
[ ] I have added tests

:thinking: I'm starting to wonder if it would be possible to add a compiler warning to discourage people using String or make it a hard error. It's not like Cow<'static, str> has any inconvenient for the developers... does it?

thinking I'm starting to wonder if it would be possible to add a compiler warning to discourage people using String or make it a hard error. It's not like Cow<'static, str> has any inconvenient for the developers... does it?

Can we even warn about this? As far as I know, there's no way to check if the type is String at compile time in the proc-macro.

It's not always feasible to create Cow<'static, str> especially when user use 3rd party crate that
return Option<String/&'static str> that user want to pass directly to component just like in my case. If we force the user code to only pass Cow<'static, str> then the user would need to make the conversions before passing it to the prop which is verbose and we can do that for user.

thinking I'm starting to wonder if it would be possible to add a compiler warning to discourage
people using String or make it a hard error. It's not like Cow<'static, str> has any
inconvenient for the developers... does it?

I think this apply on the component code not on user code, since the user code only use what the component props type. So it's the components developer responsibility to make sure the props type are of Cow<'static, str> (if that make sense for the component which is usually is)

I think we need to split the problem in 2 concerns we want to address:

The complication due to the conversion
The intuitiveness/ergonomic of having all components using Cow<str> instead of String

Point1: conversion
I just made this temporary project:
use yew::prelude::*;

struct MyComponent;

impl Component for MyComponent {
    type Properties = ();
    type Message = ();

    fn create(_: <Self as yew::Component>::Properties, _: ComponentLink<Self>) -> Self {
        todo!()
    }
    fn update(&mut self, _: <Self as yew::Component>::Message) -> bool {
        todo!()
    }
    fn change(&mut self, _: <Self as yew::Component>::Properties) -> bool {
        todo!()
    }
    fn view(&self) -> Html {
        let option_string: Option<String> = None;
        let string: String = String::new();
        html! {
            <>

            </>
        }
    }
}

fn main() {
    println!("Hello, world!");
}

Which seems to work fine AND it's very concise:
   Compiling tmp-tjisdy v0.1.0 (/home/cecile/.cache/cargo-temp/tmp-tjiSdy)
    Finished dev [unoptimized + debuginfo] target(s) in 0.23s
     Running `target/debug/tmp-tjisdy`
Hello, world!

Now we can debate whether or not this is ergonomic but it seems to me using map() on Option is a pretty common thing to do in Rust.
Point 2: intuitiveness/ergonomic
On intuitiveness
Rust is a programming language without GC. We use the borrow checker to enforce safety. The alternative to borrowing is reference counting (Rc).
Either our API is capable to handle borrowed values (this means having lifetimes everywhere) or we extensively use Rc. I have personally not explored the path of using more lifetimes but I suspect it might be getting crazy with the React-like component hierarchy. The other thing is that v0.18 will not change its implementation. So cloning and reference counting in Yew 0.18 is going to stay. This doesn't mean we can't create an issue and try to find new solutions for further versions.
Because of the requirement of cloning everywhere, it means we are going to clone a lot of unnecessary things like String. Strings can be costly to clone and since HTML is kinda "stringly typed", using &'static str can be a huge benefit.
Of course it's not because HTML is stringly typed that we want a web framework API to rely on string typing. That is why it is important to discourage the use of String and Option<String> by the user. At this time we do not discourage the use of String but we do discourage the use of Option<String>. It's interesting to know we might not be very consistent here.
(Side note: one alternative would be to use Rc<String> everywhere and force the user to deal with that instead. This is a breaking change so it's not really worth to talk about it here.)
On ergonomic
It's kinda annoying to type Cow<'static, str>. It is possible to make things more "friendly" by using type alias like we have Html and ShouldRender. The unfortunate cost of that is the lack of explicitness: it makes the user wonder what is it and force them to use the doc to understand how it works. I'm personally not against this solution (but I'm not for it either).
To improve the situation we could improve the error message provided by the macro. As @hamza1311 said it is not possible to check at compile time what the type is. But we can definitely parse the types of the user's own components and detect Option<String>. Because that is the anti-pattern we want to avoid. Though I'm not sure if we can print warnings.
Possible solution

Add a warning for Option<String> (and String) in user's component props
Allow automatic conversion like you did in this PR

If we can't do the point 1, than we shouldn't do the point 2.

Now we can debate whether or not this is ergonomic but it seems to me using map() on Option is a pretty common thing to do in Rust.

While that approach is fine for elements, I'm not sure how well it'd work for components which take Option<Cow<'static, str>> in their props.
In that situation Cow must be created manually (do note that into was unable to infer the type when I tried to do it) which isn't ergonomic but that's a limitation of type system.
@siku2 mentioned on discord that we should have a string type in Yew which is a wrapper around Cow<'static, str> and I agree with that.

one alternative would be to use Rc<String> everywhere and force the user to deal with that instead. This is a breaking change so it's not really worth to talk about it here

I'm not sure if that's a good idea because there would be no way mutate it without cloning or interior mutability.

At this time we do not discourage the use of String but we do discourage the use of Option<String>. It's interesting to know we might not be very consistent here.

I think we should stay consistent. I don't think Cow<'static, str> is any less ergonomic than String. It might be a good idea to also discourage use of String.

If nothing else, I think we should clarify anti-patterns in the documentation. If we can, I wouldn't mind logging a warning to browser's console on use String or Option<String>.


Add gridtools_cpp 2.3.6

Could the older version 2.3.4 be removed?
This would keep the number of supported version smaller.

Could the older version 2.3.4 be removed?
This would keep the number of supported version smaller.

I can't answer that question, I'll leave it to someone else.

@havogt CI should tell us!

launch jenkins


In range mode, is there a way to initialize the first thumb to the starting value and second/last thumb to the end value such that it selects the whole slider ?

@hearsilent Thank you in advance for the help.

Hi @raghavkishan
Just set in xml
app:ds_count="21"
app:ds_minProgress="0"
app:ds_maxProgress="20"

or in java
slider.setCount(21);
slider.setMinProgress(0);
slider.setMaxProgress(20);


Make a New Blog Post

WHEN I click on the button to add a new blog post
THEN I am prompted to enter both a title and contents for my blog post

We can upload a new blogpost!


Created Code of Conduct for Contributors this fixes #19

Code of Conduct for all Contributors to the Project repo

Thanks this is great!


Make sure LSP url is a valid url when switching

still doesn't work

Main purpose of this wasn't to be able to get people out of this state but to prevent it from happening. Added some trim()s everywhere that should help get your wallet unstuck

I used a new wallet and still got into this state.

Think this should prevent everywhere, otherwise plz lmk how you reproduce


updated functions and organization

Codecov Report

Merging #12 (470dd88) into master (425d105) will increase coverage by 2.51%.
The diff coverage is 60.92%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
+ Coverage   59.00%   61.51%   +2.51%
==========================================
  Files           5       12       +7
  Lines         322      395      +73
==========================================
+ Hits          190      243      +53
- Misses        132      152      +20

Impacted Files
Coverage Δ

src/MvSim.jl
100.00% <ø> (ø)

src/Parallel/Parallel.jl
0.00% <0.00%> (ø)

src/PearsonMatching/pearson_bounds.jl
0.00% <0.00%> (ø)

src/rand_vec.jl
0.00% <0.00%> (ø)

src/Correlation/nearest_pos_def.jl
40.60% <40.60%> (ø)

src/Correlation/utils.jl
50.00% <50.00%> (ø)

src/PearsonMatching/pearson_match.jl
86.66% <86.66%> (ø)

src/Correlation/random.jl
90.24% <90.24%> (ø)

src/PearsonMatching/utils.jl
95.12% <95.12%> (ø)

src/Correlation/nearest_pos_semi_def.jl
100.00% <100.00%> (ø)

... and 12 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 425d105...470dd88. Read the comment docs.


Multiple reply addresses

Hello!
I'm trying to document MQTT Request/Response pattern where a single Request can result in multiple channel/message replies, something similar to AWS IoT Core Shadow /shadow/get, /shadow/get/accepted, shadow/get/rejected
It seems V3 currently only supports a single reply address object. Is there any recommended way I could achieve this with the current spec?
Thanks :)

In the current version you would have to create multiple operations where each results in a single reply 🙂 When the feature was created we never discussed that a single operation should be able to result in multiple addresses on a single operation, either through channel or reply 🤔


add a dumb timeout logic

issue: https://github.com/WebAssembly/wasi-testsuite/issues/42
a few notes on this implementation:

the timeout is hardcoded to 3 seconds for now. we can add a configuration in per-test json files when necessary.
unit test doesn't cover the new code. i have no plan to write tests at this point.
adapters may need something like https://github.com/yamt/toywasm/pull/117 for better cleanup

@loganek please review when you have time. this is not urgent for me.

Thanks for the change, and sorry for being late with the review. I'll try to get to it by end of this week.

@loganek ping


some question about FPGA-VERILOG

Describe the bug
A clear and concise description of what the bug is.
Hello! Recently, I wanted to get some results such as the synthesized netlist of the FPGA verilog module generated by Opefpga, but there were many warnings in the process of using DC, which made it impossible to run, and finally killed, so imagine you ask for advice What tools did you use to do the synthesis before? Or what tools did you use to get those reports on area power consumption? Does Openfpga have this function? Or would you like to ask if you have modified anything before synthesizing? I hope you can give some pointers, thank you very much

To Reproduce
Steps to reproduce the behavior:

Clone OpenFPGA repository and checkout commit id:
Version: 1.1.53-dev+968a03cd-dirty

Execute OpenFPGA task or your own example:
python3 openfpga_flow/scripts/run_fpga_task.py basic_tests/full_testbench/configuration_chain
See error
none

您好！最近想要得到利用Opefpga产生的FPGA的verilog模块的综合后的网表等一些结果，但是在使用DC的过程中出现了很多警告，导致跑不下去，最终kill了，所以想像您请教一下您们之前综合是使用的什么工具做的呢？或者说那些面积功耗的相关报告您们是使用什么工具得到的呢？Openfpga是否有这个功能呢？或者想请问您在综合之前有修改什么嘛？希望您可以指点一下，万分感谢

@kangliyu1
Since there are many comb loops in FPGA fabric, ASIC synthesis tools have difficulties when optimizing.
Base on our previous practice, we typically use technology mapped netlists (skip synthesis).
We are now actively looking into synthesis support.
We will keep you posted on new features.

Do you mean that your practice is to skip synthesis in OpenFPGA Flow? If YES, then what file are you giving as input to the Semi-custom design flow?


Patch device YANGs in user-friendly way

Some device YANGs are broken. That is, they announce a yang that does not match the config they support.
In particular, there may be XML tags, eg  that have no corresponding YANG statement.
This may not be fixed bu augmenting the YANG (eg from a local clixon- extension YANG) since it has another namespace.
It can be solved by the C yang-patch callback, but that involves writing C code for patching a YANG on load, and this may be considered user-unfriendly.

Actually, you may just as well patch the modules after downloading them and leave them in the local MNT dir.
Instead, handle broken device yangs with: https://github.com/clicon/clixon-controller/issues/59


feat: add Virtual Machine

Hello,
I'm excited to present a release candidate for the first prototype of the VM. The new VM is designed to replace the previous Tree Walker Interpreter because we don't need it anymore.
The VM is built to run on 32-bit long instructions and is capable of compiling an assembler-like language initially. In future releases, it will also support compiling Reg-Lang in this architecture.
The current version of the VM includes 20 functional instructions, which have been tested to a limited extent. The VM also has a memory that operates as a mix between a stack and a heap, along with 16 general-purpose registers (each 32 bits). Additionally, there are specific registers such as t_reg (temporary register), pc (program counter), cmp_register (comparison register, stores the result of the last comparison), bp (base pointer), sp (stack pointer), and fp (frame pointer).

The VM has several new instructions, each with a specific purpose:

cst: This instruction allows you to cast the contents of a register from one type to another. It doesn't change the size of the register (which remains an u32), but it allows you to store a number with a different encoding (such as a float).

inc: This instruction increments the contents of a register by 1. It only works with integer values, so be careful when using it with floating point values, as there may be precision errors.

dec: This instruction decrements the contents of a register by 1. Like inc, it only works with integer values.

or: This instruction performs a bitwise OR operation on two registers, and stores the result in a third register.


Create new annotation @AutoStan

The I50Message class has a public method called generateStan which is used for automatically generating Stans. This could be used automatically by @AutoStan annotation. In this way Stan does not need to hold any value.

This has now been fixed in 1685394f3858972dbeb7e220dcb68ad4337780a0