Breakpoints do not seem to be forwarded to gdb

Does this issue occur when all extensions are disabled?: Cannot check without the extension enabled.

VS Code Version:1.67.2
OS Version:Ubuntu 20.04.2

Hello,
I am opening this bug report here as suggested on the original report (https://github.com/microsoft/vscode-cpptools/issues/9361)
I am trying to run debugging with the cpptools extension, but no breakpoints are hit. In the original report, I submitted the plugin log and it seems that their plugin is not even receiving the list of requested breakpoints that are set in vscode.
Steps to Reproduce:

Set some breakpoints in the code
2.Launch debugging, breakpoints are not received in the debugger.

Hello,
Let me add as well that I just tried reverting to 1.66.2 and with that version, everything is working as expected.

Hm, I can't reproduce and I can't think of any relevant changes on our end.
If you download the last version of vscode from the links at the top of the page here: https://code.visualstudio.com/updates/v1_66 does it work in that version? (Or you can go older if you think it was a longer time ago.)
And while taking that log, you tried setting and unsetting breakpoints?
Do the breakpoints show as gray circles?
Any errors in vscode devtools (Help > Toggle developer tools)?

Hello,
I have tried indeed to set and unset breakpoints while taking the log (and saw no movement in the log at all), and the breakpoints where showing full red dots.
While checking, I have been going back and forth between the latest version and earlier ones, also downgrading and upgrading some of the plugins (the latest version of some of them do not seem to be compatible with older versions of vscode). Eventually the issue disappeared and I am not able anymore to reproduce it anymore. I am rather sure that my current situation in terms of versions of vscode and each individual plugins is the same as before (everything at the latest), so I don't know what changed in the process of downgrading and upgrading...

That's strange, I'm not sure what happened. Thanks for doing that experimentation. I'm going to close this for now but we can reopen it if you see this issue again.


Register v0.1.0

@JuliaRegistrator register
Register first release of IterativeLQR.jl

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


Fix for memory leak in NSUUID

@swift-ci please test and merge

Does init?(uuidString: String) also leak? Looks like that one allocates 16 bytes too.

Hi @ianpartridge Have provided the fix for the leaks in  init?(uuidString: String)  and  init?(coder: NSCoder) as well. Thanks!

@swift-ci please test and merge


tail plugin stops tailing the log files which are rotated based on file size.

Describe the bug
The application log rotation policy is defined based on log file size to limit the disk space consumption.
It is observed after some days fluentd tail plugin skip the file rotation and entire file contents are lost.
The log files are generated in below format and each log file size is limit to 4096MB
applog.log
applog.log.1
applog.log.2
applog.log.3
and so on to max 10
To Reproduce
Tail the files which is rotated based on size (let's say 9 MB).
applog.log
applog.log.1
applog.log.2
applog.log.3
and so on (upto 12 files)
Expected behavior
The rotating files must not be skipped which cause data loss of entire rotated file contents
Your Environment
- Fluentd version: 1.16.1
- TD Agent version:
- Operating system: RHEL 8
- Kernel version:4.18.0-477.13.1.el8_8.x86_64

Your Configuration
I have the below tail plugin configuration and I observed the tail plugin stops reading the data from the log file which is writing new logs of application.

<source>
@type tail path /opt/appxyz/logs/applog.log
tag xyzApplogingest
read_from_head false
pos_file /opt/td-agent/fluentd/file-tail.log.pos
follow_inodes true
refresh_interval 2
skip_refresh_on_startup true
enable_stat_watcher false
from_encoding UTF-8
encoding UTF-8
exclude_path [""]
multiline_flush_interval 5s
<parse>
    @type none
  </parse>
</source>

Your Error Log
No errors in log but observing log statement difference between working on not working (when file is skipped) when file is rotated
Working logs:
2023-12-11 12:11:32 -0500 [info]: #7 following tail of /opt/appxyz/logs/applog.log
	Line  6110: 2023-12-11 12:11:32 -0500 [info]: #7 detected rotation of /opt/appxyz/logs/applog.log; waiting 5 seconds

Non Working: (log related to "detected rotation of .... " is missing"
2023-12-11 13:25:16 -0500 [info]: #7 following tail of /opt/appxyz/logs/applog.log

Additional context
Looks like fluentd tail plugin fails to detect log rotation.

Could you try fluentd v1.16.2 or later?
v1.16.2 and v1.16.3 fixes known in_tail stop issues:

v1.16.2
v1.16.3

Could you try fluentd v1.16.2 or later? v1.16.2 and v1.16.3 fixes known in_tail stop issues:

v1.16.2
v1.16.3

Thanks for the response, I will try with 1.16.3 .

Will try with latest version and update.
Closing for now.


TS Compilation Error: Cannot find name TextDecoder

I'm running this with TypeScript 4.4.0 and I'm getting the error in the title.
I've edited amqp-message.d.ts to add the proper import as a temporary workaround, but I'm surprised no one complained about this, so I'm thinking maybe I'm doing something wrong.
I have not added "dom" to the list of libs in tsconfig.json, nor will I do that, since this is a backend server app.
Any suggestions would be much appreciated.

Ok, yeah, TextEncoder is availabe in nodejs, so i guess it's only if you manually disable dom in tsconfig that it will complain.

Thanks, Carl!
I'd argue that you manually enable dom instead of disabling it. Server apps should not have that enabled by default in my opinion.
Just to chime in on the fix a bit, you might be able to get away with a static decoder if you do a conditional import from util when running in nodejs. Not sure if there's a benefit over the Buffer approach though.


Optionally allow a different branch for each repo

https://github.com/ManageIQ/manageiq-appliance-build/issues/95
This PR will make building development image to test proposed changes simpler.
This will be done by adding optional command line arguments where specific branch names
can be specified for each of the repos.
No default behavior is changing.

@abellotti Please review.
I have used these changes to successfully build a test image with the command of the form:
ruby /build/scripts/vmbuild.rb --type nightly --only openstack -b branch_name -B https://github.com/jvlcek/manageiq-appliance-build.git

I'm working on fixing the travis failure now.

Hi Joe, looks good.
l think we still need to support the -r option for compatibility, we have scripts that make use of that option,  in the code if -r is specified, set to -m, -a and -b (if not specified).  That will also make it a nice shortcut if we really want all three to be the same.
Thanks for the quick turnaround on this !!

@abellotti Thank you. Yes I had reviewed this with @simaishi  and she also suggested maintaining the -r flag. Which I have now done.

LGTM :+1:


feat: trigger on context, validate and parse errors

closes https://github.com/n1ru4l/envelop/issues/1201

Shouldn't the type of the ErrorHandler error be the same as the one of the useMaskedError plugin?


/en-US/docs/Tools/Performance/Waterfall

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details
Possible Typo in "A string the indicating the reason GC was performed"
Should be "A string indicating the reason GC was performed"

@himanshugarg I fixed it.

@bershanskiy thanks! Closing.


Upgrade to Retrofit 2.0

This PR upgrades the library to use Retrofit 2 and Okhttp 3.
There are a few changes that need some discussion:

Retrofit 2 no longer has the ability to set HttpExecutors and no longer has the MainThreadExecutor for callbacks (Callbacks are executed on the main thread on android by default). Do we still need to set executors?
Error handling has changed. RetrofitError no longer exists. I've implemented deserializing of the error response and modified the SpotifyCallback, but is this callback really needed anymore?

Addresses #106

Sorry for the commit spam - lint warnings are now fixed :)

Do you have documentation on how to use your updated API? I'm running into errors declaring a new SpotifyAPI


VSCode become laggy after some time and then crash (reason: crashed, code: 132)

Type: Bug
With verbose mode i see many
potential listener LEAK detected, having XXX listeners already
REFUSES to accept new listeners because it exceeded its threshold by far
SLOW task detected (744ms) but renderer profiling is disabled via 'application.experimental.rendererProfiling'" vscode
And then got crash with:
CodeWindow: renderer process gone (reason: crashed, code: 132)
Verbose log:
vscode_log.txt
I think this is because one of extensions, because on other profile no such problems
VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:16:23.416Z)
OS version: Linux x64 6.8.0-76060800daily20240311-generic
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 5 2600 Six-Core Processor (12 x 3834)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
2, 2, 1

Memory (System)
23.40GB (16.96GB free)

Process Argv
--crash-reporter-id b7df5783-d000-42d0-9761-a4d348c98d80

Screen Reader
no

VM
0%

DESKTOP_SESSION
pop

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
pop

XDG_SESSION_TYPE
x11

Extensions (19)

Extension
Author (truncated)
Version

aessoft-class-autocomplete
AES
0.1.0

vscode-django
bat
1.15.0

django-snippets
bib
1.1.1

django
big
1.0.2

file-shortcuts
bra
0.0.9

django-import-libraries
Dha
0.0.4

vscode-html-css
ecm
2.0.9

auto-rename-tag
for
0.1.10

vscode-drawio
hed
1.6.6

vscode-django-support
jun
1.0.32

document
min
2.2.1

vscode-html-format
moh
0.1.6

autopep8
ms-
2024.0.0

debugpy
ms-
2024.6.0

python
ms-
2024.6.0

remote-ssh
ms-
0.110.1

indent-rainbow
ode
8.3.1

django-intellisense
sha
0.0.2

python-auto-venv
Wol
1.3.2

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
tftest:31042121
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
chatpanelt:31048053
dsvsc021:30996838
f3je6385:31013174
pythoncenvpt:31049070
a69g1124:31046351
pythonprc:31047982
dwnewjupyter:31046869
26j00206:31048877

So I tested some things, here what i got:

Lags starting only in html files
After disabling Django extension lags stopped
my settings for html:
"files.associations": {
"*.html": "django-html"
},
"emmet.includeLanguages": {
"html": "html",
"jinja-html": "html",
"django-html": "html",
},

I dont know if extensions are conflicting each other or there is a problem in this particular extension

Thanks for identifying that, can you file an issue against the extension too?
In case there is anything for us to look at, here's the stack that's producing the listener warnings:
at [`./base/common/event.ts:889:24`](https://github.com/Microsoft/vscode/blob/dc96b837cf6bb4af9cd736aa3af08cf8279f7685/src/vs/./base/common/event.ts#L889)
    at [`./base/common/event.ts:1055:33`](https://github.com/Microsoft/vscode/blob/dc96b837cf6bb4af9cd736aa3af08cf8279f7685/src/vs/./base/common/event.ts#L1055)
    at [`./editor/common/model/bracketPairsTextModelPart/bracketPairsImpl.ts:41:37`](https://github.com/Microsoft/vscode/blob/dc96b837cf6bb4af9cd736aa3af08cf8279f7685/src/vs/./editor/common/model/bracketPairsTextModelPart/bracketPairsImpl.ts#L41)
    at [`./editor/common/model/textModel.ts:327:38`](https://github.com/Microsoft/vscode/blob/dc96b837cf6bb4af9cd736aa3af08cf8279f7685/src/vs/./editor/common/model/textModel.ts#L327)
    at [`./editor/common/services/modelService.ts:317:27`](https://github.com/Microsoft/vscode/blob/dc96b837cf6bb4af9cd736aa3af08cf8279f7685/src/vs/./editor/common/services/modelService.ts#L317)
    at [`./editor/common/services/modelService.ts:452:20`](https://github.com/Microsoft/vscode/blob/dc96b837cf6bb4af9cd736aa3af08cf8279f7685/src/vs/./editor/common/services/modelService.ts#L452)
    at [`./workbench/api/browser/mainThreadDocumentContentProviders.ts:49:32`](https://github.com/Microsoft/vscode/blob/dc96b837cf6bb4af9cd736aa3af08cf8279f7685/src/vs/./workbench/api/browser/mainThreadDocumentContentProviders.ts#L49)
    at [`./workbench/services/textmodelResolver/common/textModelResolverService.ts:187:17`](https://github.com/Microsoft/vscode/blob/dc96b837cf6bb4af9cd736aa3af08cf8279f7685/src/vs/./workbench/services/textmodelResolver/common/textModelResolverService.ts#L187)
    at [`./workbench/services/textmodelResolver/common/textModelResolverService.ts:78:3`](https://github.com/Microsoft/vscode/blob/dc96b837cf6bb4af9cd736aa3af08cf8279f7685/src/vs/./workbench/services/textmodelResolver/common/textModelResolverService.ts#L78)
    at [`./base/common/lifecycle.ts:683:18`](https://github.com/Microsoft/vscode/blob/dc96b837cf6bb4af9cd736aa3af08cf8279f7685/src/vs/./base/common/lifecycle.ts#L683)

can you file an issue against the extension too?

I dont think this will work. last extension update was 5 years ago.

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!


The README.txt link to comercial application coverage is broken(404)

The link: https://modsecurity.org/projects/commercial/rules/application_coverage.html
that is present in the README.txt is broken(404)

I live pushed the fix to this thank you for the report!


more reactor re-factoring

@robertroeser I think we can close this one since you are working on this in a different branch?


BUG: Data race reported by TSan in kvrocks

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
unstable, linux
Minimal reproduce step
./build.sh build --unittest -DENABLE_TSAN=ON
./build/unittest

What did you expect to see?
No TSan report.
What did you see instead?
Selected TSan log in unittest:
WARNING: ThreadSanitizer: data race (pid=14679)
  Read of size 1 at 0x7b7c0000673b by thread T1:
    #0 memcmp <null> (libtsan.so.0+0x67cb3)
    #1 rocksdb::Slice::compare(rocksdb::Slice const&) const /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/rocksdb-src/include/rocksdb/slice.h:250 (unittest+0x5d75ef)
    #2 Compare /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/rocksdb-src/util/comparator.cc:34 (unittest+0x5d75ef)
    #3 Engine::SubKeyFilter::Filter(int, rocksdb::Slice const&, rocksdb::Slice const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*, bool*) const /home/runner/work/incubator-kvrocks/incubator-kvrocks/src/compact_filter.cc:111 (unittest+0x18605c)
    #4 rocksdb::CompactionFilter::FilterV2(int, rocksdb::Slice const&, rocksdb::CompactionFilter::ValueType, rocksdb::Slice const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*) const /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/rocksdb-src/include/rocksdb/compaction_filter.h:171 (unittest+0x67ba24)
    #5 rocksdb::CompactionIterator::InvokeFilterIfNeeded(bool*, rocksdb::Slice*) /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/rocksdb-src/db/compaction/compaction_iterator.cc:276 (unittest+0x67ba24)
  Previous write of size 1 at 0x7b7c0000673b by main thread (mutexes: write M19766):
    #0 memcpy <null> (libtsan.so.0+0x61afe)
    #1 memcpy /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34 (unittest+0x427deb)
    #2 rocksdb::MemTable::Add(unsigned long, rocksdb::ValueType, rocksdb::Slice const&, rocksdb::Slice const&, rocksdb::ProtectionInfoKVOS<unsigned long> const*, bool, rocksdb::MemTablePostProcessInfo*, void**) /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/rocksdb-src/db/memtable.cc:556 (unittest+0x427deb)
    #3 Redis::Bitmap::SetBit(rocksdb::Slice const&, unsigned int, bool, bool*) /home/runner/work/incubator-kvrocks/incubator-kvrocks/src/redis_bitmap.cc:217 (unittest+0x1b727e)
    #4 RedisBitmapTest_BitPosSetBit_Test::TestBody() /home/runner/work/incubator-kvrocks/incubator-kvrocks/tests/t_bitmap_test.cc:86 (unittest+0xedaa1)
    #5 void testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/gtest-src/googletest/src/gtest.cc:2607 (unittest+0x7ee349)
    #6 void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/gtest-src/googletest/src/gtest.cc:2643 (unittest+0x7ee349)
    #7 __libc_start_main <null> (libc.so.6+0x21c86)
  Location is heap block of size 3264 at 0x7b7c00006200 allocated by main thread:
    #0 operator new(unsigned long) <null> (libtsan.so.0+0x8e62e)
    #1 rocksdb::ColumnFamilyData::ConstructNewMemtable(rocksdb::MutableCFOptions const&, unsigned long) /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/rocksdb-src/db/column_family.cc:1065 (unittest+0x66cc9d)
    #2 Engine::Storage::Open() /home/runner/work/incubator-kvrocks/incubator-kvrocks/src/storage.cc:323 (unittest+0x306775)
    #3 TestBase::TestBase() /home/runner/work/incubator-kvrocks/incubator-kvrocks/tests/test_base.h:34 (unittest+0xef3c8)
    #4 RedisBitmapTest::RedisBitmapTest() /home/runner/work/incubator-kvrocks/incubator-kvrocks/tests/t_bitmap_test.cc:28 (unittest+0xef3c8)
    #5 RedisBitmapTest_BitPosSetBit_Test::RedisBitmapTest_BitPosSetBit_Test() /home/runner/work/incubator-kvrocks/incubator-kvrocks/tests/t_bitmap_test.cc:82 (unittest+0xef3c8)
    #6 testing::internal::TestFactoryImpl<RedisBitmapTest_BitPosSetBit_Test>::CreateTest() /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/gtest-src/googletest/include/gtest/internal/gtest-internal.h:472 (unittest+0xef3c8)
    #7 testing::Test* testing::internal::HandleSehExceptionsInMethodIfSupported<testing::internal::TestFactoryBase, testing::Test*>(testing::internal::TestFactoryBase*, testing::Test* (testing::internal::TestFactoryBase::*)(), char const*) /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/gtest-src/googletest/src/gtest.cc:2607 (unittest+0x7ee4f9)
    #8 testing::Test* testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::TestFactoryBase, testing::Test*>(testing::internal::TestFactoryBase*, testing::Test* (testing::internal::TestFactoryBase::*)(), char const*) /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/gtest-src/googletest/src/gtest.cc:2643 (unittest+0x7ee4f9)
    #9 __libc_start_main <null> (libc.so.6+0x21c86)
  Mutex M19766 (0x7b0c000cbc70) created at:
    #0 pthread_mutex_lock <null> (libtsan.so.0+0x532b4)
    #1 __gthread_mutex_lock /usr/include/x86_64-linux-gnu/c++/7/bits/gthr-default.h:748 (unittest+0x1ada7e)
    #2 std::mutex::lock() /usr/include/c++/7/bits/std_mutex.h:103 (unittest+0x1ada7e)
    #3 LockManager::Lock(rocksdb::Slice const&) /home/runner/work/incubator-kvrocks/incubator-kvrocks/src/lock_manager.cc:49 (unittest+0x1ada7e)
    #4 LockGuard::LockGuard(LockManager*, rocksdb::Slice) /home/runner/work/incubator-kvrocks/incubator-kvrocks/src/lock_manager.h:52 (unittest+0x1b698f)
    #5 Redis::Bitmap::SetBit(rocksdb::Slice const&, unsigned int, bool, bool*) /home/runner/work/incubator-kvrocks/incubator-kvrocks/src/redis_bitmap.cc:[169](https://github.com/apache/incubator-kvrocks/runs/6922999327?check_suite_focus=true#step:7:170) (unittest+0x1b698f)
    #6 RedisBitmapTest_BitPosSetBit_Test::TestBody() /home/runner/work/incubator-kvrocks/incubator-kvrocks/tests/t_bitmap_test.cc:86 (unittest+0xedaa1)
    #7 void testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/gtest-src/googletest/src/gtest.cc:2607 (unittest+0x7ee349)
    #8 void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/gtest-src/googletest/src/gtest.cc:2643 (unittest+0x7ee349)
    #9 __libc_start_main <null> (libc.so.6+0x21c86)
  Thread T1 'rocksdb:low' (tid=14682, running) created by main thread at:
    #0 pthread_create <null> (libtsan.so.0+0x5fe84)
    #1 std::thread::_M_start_thread(std::unique_ptr<std::thread::_State, std::default_delete<std::thread::_State> >, void (*)()) <null> (unittest+0x83c9d4)
    #2 Engine::Storage::Open(bool) /home/runner/work/incubator-kvrocks/incubator-kvrocks/src/storage.cc:238 (unittest+0x304953)
    #3 Engine::Storage::Open() /home/runner/work/incubator-kvrocks/incubator-kvrocks/src/storage.cc:323 (unittest+0x306775)
    #4 Compact_Filter_Test::TestBody() /home/runner/work/incubator-kvrocks/incubator-kvrocks/tests/compact_test.cc:36 (unittest+0xc57be)
    #5 void testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/gtest-src/googletest/src/gtest.cc:2607 (unittest+0x7ee349)
    #6 void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) /home/runner/work/incubator-kvrocks/incubator-kvrocks/build/_deps/gtest-src/googletest/src/gtest.cc:2643 (unittest+0x7ee349)
    #7 __libc_start_main <null> (libc.so.6+0x21c86)
SUMMARY: ThreadSanitizer: data race (/usr/lib/x86_64-linux-gnu/libtsan.so.0+0x67cb3) in memcmp

For more details check https://github.com/apache/incubator-kvrocks/runs/6922999327 or reproduce in your side.
Anything Else?
As in https://github.com/apache/incubator-kvrocks/pull/630#discussion_r900909805, we create an issue for this bug to reference easily.
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

I think maybe it's a false leak report. Coz the main thread
will write the memtable and convert the memtable to immutable state after it reached
the max limit, then RocksDB background will read the memtable and flush them into disk.
So it should be expected behavior that main thread and background thread will have data race,
but will not cause problem.
HDYT? @ShooterIT @PragmaTwice @tisonkun

I think maybe it's a false leak report. Coz the main thread will write the memtable and convert the memtable to immutable state after it reached the max limit, then RocksDB background will read the memtable and flush them into disk. So it should be expected behavior that have the data race between main thread and background thread, but will not cause problem.
HDYT? @ShooterIT @PragmaTwice @tisonkun

Seems the writing in kvrocks main thread and the reading in rocksdb background thread occurs at the same time and in the same memory location? Won't this be a problem?

Yes, background thread will read the immutable memory table only which the main thread won't write after it become immutable.

RocksDB will only have one "writeable" memtable, on default, it will be a lock-free skiplist. And when it's full, it will be "frozen" and only readable. Frozen memtable will only be read by user or compaction, it will never be modified.
I think the case strange, the memory is created by ConstructNewMemtable, modified by rocksdb::MemTable::Add, and detect a race when CompactionFilter is called. And an "writable" memtable will not be compacted.
Maybe TSAN thinks Memtable is protected by LockGuard, but only write is guarded by it, and the following read didn't call LockGuard.
I'm not familiar with TSAN, maybe I made some mistakes.

I may know the root cause of this problem, it may be a false positive due to the rocksdb library not being instrumented by TSan.
Did not notice this when I refactor cmake files. I will fix it later.

Solved by #759.

Thanks for @PragmaTwice great help, we finally got the TSAN and ASAN in CI.


Strong verification frontend

Should include:

Three-step form for submitting details
Periodic polling of backend for verification status
Display of verification status

@darrenvong is this something you might be interested in and available to work on?

I'm going to be out for the next two weeks at least, and unsure if I will
have time immediately after to commit to doing this on a decent time scale
so maybe not for the time being 😅 will post if that changes!
On Tue, 9 Jul 2024 at 22:54, Tristan Schrader @.***>
wrote:

@darrenvong https://github.com/darrenvong is this something you might
be interested in and available to work on?
—
Reply to this email directly, view it on GitHub
https://github.com/Couchers-org/couchers/issues/4413#issuecomment-2218796320,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADIJH4RUGSFQQ4VUWOUNPQTZLRLZBAVCNFSM6AAAAABIZE4H3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJYG44TMMZSGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@aapeliv What's up with this? Should it move back to ideas?

@aapeliv What's up with this? Should it move back to ideas?

we are waiting for the UI mockup (AFAIK)


Added code for finding factorial of a number using recursion

What a great code :smile: ! Just a little tip, its good to always put a description on your PRs to make more understandable.
Thank you for contributing! :rocket:


Error In pip install -r requirements.txt

Here is windows, when I install the requirements, I met those error, this is the log
INFO: pip is looking at multiple versions of modelscope[cv] to determine which version is compatible with other requirements. This could take a while.
ERROR: Ignored the following versions that require a different python version: 1.11.0 Requires-Python <3.13,>=3.9; 1.11.0rc1 Requires-Python <3.13,>=3.9; 1.11.0rc2 Requires-Python <3.13,>=3.9; 1.11.1 Requires-Python <3.13,>=3.9; 1.11.2 Requires-Python <3.13,>=3.9; 1.11.3 Requires-Python <3.13,>=3.9; 1.11.4 Requires-Python >=3.9; 1.12.0rc1 Requires-Python >=3.9; 1.12.0rc2 Requires-Python >=3.9; 1.25.0 Requires-Python >=3.9; 1.25.0rc1 Requires-Python >=3.9; 1.25.1 Requires-Python >=3.9; 1.25.2 Requires-Python >=3.9; 1.26.0 Requires-Python <3.13,>=3.9; 1.26.0b1 Requires-Python <3.13,>=3.9; 1.26.0rc1 Requires-Python <3.13,>=3.9; 1.26.1 Requires-Python <3.13,>=3.9; 1.26.2 Requires-Python >=3.9; 1.26.3 Requires-Python >=3.9; 2.1.0 Requires-Python >=3.9; 2.1.0rc0 Requires-Python >=3.9; 2.1.1 Requires-Python >=3.9; 2.1.2 Requires-Python >=3.9; 2.1.3 Requires-Python >=3.9; 2.1.4 Requires-Python >=3.9; 2.2.0 Requires-Python >=3.9; 2.2.0rc0 Requires-Python >=3.9; 3.8.0 Requires-Python >=3.9; 3.8.0rc1 Requires-Python >=3.9; 3.8.1 Requires-Python >=3.9; 3.8.2 Requires-Python >=3.9
ERROR: Could not find a version that satisfies the requirement bmt-clipit>=1.0; extra == "cv" (from modelscope[cv]) (from versions: none)
ERROR: No matching distribution found for bmt-clipit>=1.0; extra == "cv"

same  here.

try pip install modelscope==1.10.0 without [cv]?

try pip install modelscope==1.10.0 without [cv]?

Its work, but when i use 'python app.py', another error happen
ModuleNotFoundError: No module named 'torch'

Fixed with full required packages, pull the latest code and try again

python render.py

get error:
ModuleNotFoundError: No module named 'numba'

and I mannaul pip install numba, another error:
  File "C:\ProgramData\miniforge3\envs\en3d\lib\site-packages\modelscope\pipelines\cv\human3d_render_pipeline.py", line 78, in format_nvdiffrast_format
    vtx_pos = torch.from_numpy(vert.astype(np.float32)).cuda()
  File "C:\ProgramData\miniforge3\envs\en3d\lib\site-packages\torch\cuda\__init__.py", line 221, in _lazy_init
    raise AssertionError("Torch not compiled with CUDA enabled")
AssertionError: Torch not compiled with CUDA enabled

seems pytorch is not installed correctly, https://pytorch.org/ FYI.


Collect xen

Fixes #103
Added code to import xen
Tried to make it run by modifying the importer_yielder.py and some other files but couldn't. The code is somewhat similar to the ubuntu_usn importer. Can't figure out why I'm getting an unexpected keyword argument

Also what could we do about XSA-377 released in a few days/weeks on 2021-06-08 17:00 per https://xenbits.xen.org/xsa/ ? (I guess just waiting may be enough?)

Yes, we can wait

@Pushpit07 do think you want to finish this?
Other I can close for now and we can reopen later.

@Pushpit07 do think you want to finish this?
Other I can close for now and we can reopen later.

Sorry for leaving in between. Will surely finish this. Give me a few days time

Sorry for leaving in between. Will surely finish this. Give me a few days time

That's very nice of you! thank you ++

@Pushpit07 Thanks! Think you missed  a signoff on a few commits... do you mind to amend these?

@Pushpit07 before we can merge, please just confirm here that your DCO signoff "Signed-off-by: Pushpit<EMAIL_ADDRESS>applies to all your commits. Thank you!

Yes, it does

Yes, it does

@Pushpit07 Thank you ++ , you rock :heart:

@pombredanne Will do after fixing tests here


window10 build release branch failed

Describe the bug
build release branch failed
To Reproduce
Steps to reproduce the behavior:

cd d:/Documents/MyProject/Public/Graphics/filament/
git clone -b release https://github.com/google/filament.git ./
mkdir out
cd out
cmake ..

Expected behavior
build failed
Screenshots

Desktop (please complete the following information):

OS: Windows10
GPU: NVIDIA GTX 1050
Backend: OpenGL

i tried main branch and rc/1.10.7 ,  failed too.

This is more of a glslang build issue than a Filament issue. I think the build_info.py script is erroring out, so the GLSLANG_VERSIONS variable in the CMake is empty.

What version of CMake are you using?

@bejado cmake version is 3.20.5

Seems like this is a Python-related problem. I recommend filing an issue directly with glslang.

@bejado  i clone and build glslang. it's success. thanks for any help. i'm not good at cmake. can't find any issue.
build glslang sucess.

I'm not sure why this isn't working for you, but I notice that our glslang CMakeLists.txt is out-of-date. For example, they no longer use Python to retrieve the GLSLANG version: https://github.com/KhronosGroup/glslang/commit/05798c17fb17d339d66e064a407e75ceae4c0316.
I'll update our CMakeLists.txt, which hopefully will fix the issue fo ryou.

@bejado Can we update glslang while we're at it?

@romainguy I think we just did, but not the CMakeLists.txt.

Thanks for looking into this Ben, it's my fault, when I updated glslang I didn't notice this detail.


Setup on Funhouse to read AHT20 sensor to Fahrenheit reverted back to Celsius

Describe the bug
A clear and concise description of what the bug is.
I started with beta .51 and setup the Funhouse with an AHT sensor to read and display Fahrenheit temperature every 5 minutes. I noticed the first couple of readings were in Celsius, then readings 5 and 6 were in Fahrenheit, the the rest reverted back to Celsius. I updated to beta .52 and I am still getting the same Celsius readings. I've also deleted the setup and reconfigured, but it appears to still be reading in Celsius. I am unable to get it to recreate the reading Celsius then Fahrenheit, then Celsius, but it does still continue to read in Celsius when I have set it up for Fahrenheit.
Arduino board
INSERT ARDUINO BOARD NAME/TYPE HERE
Adafruit Funhouse ESP32-S2
To Reproduce
Steps to reproduce the behavior:

Go to '... Devices and click on the  Funhouse device, click on new component and scroll down and select the AHT20 component. Uncheck the box next to "Enable AHT20: Temperature Sensor (°C)?". I changed the send every dropdown for both the temperature and humidity readings to every 5 minutes and then finalized by clicking create component button

Expected behavior
A clear and concise description of what you expected to happen.
I expected to get a graph and table with Fahrenheit readings.
Which components are connected to your device
Which components are set up on the WipperSnapper device page?
Funhouse and AHT20 sensor
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows 10
Browser Chrome Version 106.0.5249.119 (Official Build) (64-bit)

Additional context
Add any other context about the problem here.

@kspray

setup the Funhouse with an AHT sensor to read and display Fahrenheit temperature every 5 minutes. I noticed the first couple of readings were in Celsius, then readings 5 and 6 were in Fahrenheit, the the rest reverted back to Celsius.

I'm unable to replicate this so far on Beta 55. I have my funhouse logging and will keep it online overnight to check. Is this issue still occurring for you?

It's working right now. you can close this. I'm embarrassed. I must have not had the sensor plugged in all the way or somehting.

Great!


Diagram typo?

Minor issue - in the diagram at the top of this page, I believe the box label "Azure DevOps release gate" should be "Azure DevOps release pipeline". Other than that, great diagram. Thanks a lot.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c64e76ff-1388-ed4d-4c8b-92bb4419cc61
Version Independent ID: 3cdec53f-38ba-c0bb-3315-5ad8b357aabf
Content: MLOps for Python models using Azure Machine Learning - Azure Reference Architectures
Content Source: docs/reference-architectures/ai/mlops-python.md
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @praneet22
Microsoft Alias: pnp

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#280997

@edwiles, the text refers to Gating a process stop through Azure DevOps, the diagram also refers to a Manual release gate.  IN that context this labeling makes sense.  Please let me know your thoughts. Will close the issue after we hear form you.

Thanks for the reply. I still suggest it should be "pipeline", because there are 3 pipelines as described in the page text (underneath the MLOps Pipeline heading) which correspond to the 3 shaded areas in the diagram. Two of them are correctly labelled pipeline. The Manual release gate is only one part of the pipeline, not the whole thing.

@edwiles agree with your perspective. thanks for the clarification.  Will update the diagram to change Azure DevOps release gate to pipeline.


$global:skuValue is null for Lenovo devices

The SKU value is not populated when setting Lenovo variables.
Packages created with version 6.4.8 have nothing in the "Models Included" part of its description.
Quickly looking at the code, I can see that in the function Find-LenovoModelType, a section is commented out which included setting the $global:skuValue

Issue fixed. Updated EXE available


Implement a named groups contract.

This contract should allow DAOs to manage list of addresses and associated them with a named group. It should support adding and removing addresses from a group as well as listing all members of a group and querying for what group an address is in.
For example: a dao may create a core team group with a set of addresses. A governance module may then only allow proposal creation by members of that group.
This contract may be added / removed from a DAO as an item via the the SetItem and RemoveItem execute messages. Likely it will be standard that this contract is stored under the groups key.
In order to make it so that a DAO may be instantiated with a group (this is important for DAO creation UX) we should add the ability for a DAO to be instantiated with a set of items. This can be done by adding a field to the cw-governance contract's instantiate message which takes a mapping of name -> ModuleInstantiateInfo. On instantiation the DAO should dispatch submessages to create those items and then store them in its item map.

Done! https://github.com/DA0-DA0/dao-contracts/tree/main/contracts/cw-named-groups


Fix Frames, a journey

do not rely on browser hover when dropping components into frame. perform the math to see what we are inside.
this lets us remove the hack in cypress tests
fix to missing parentId (was renamed to parentComponentId)
set_component_position endpoint needed to change for the new engine
fixed a swap of width & height bug on resizing
send a web event from the set_component_position endpoint
frame movement now supports deeply nested children
nudging is debounced now, so we don't flood the system with changes
creating or attaching a component inside a frame expands the child to the available size and fully bounded by the parent
so long as there are no other children, in that case, it makes the frame smaller and does not attempt a "best fit".

bors merge

bors retry


refactor limits.py

Good morning!
As I see my last PR went through, I decided to do another small refactor. This time it was the "limits.py" package's turn.
Changes:
*Make code for 'ip_check' clearer by abstracting logic away into functions.
*Make comments prettier and correct typo.
*Make the intervals generation a bit easier and less verbose.
I hope you like the changes!

By the way, I wasn't able to run the tests. I'm not sure what I'm doing wrong.

I also wasn't sure enough, but shouldn't _clear_counters_if_needed use integer division? And isn't this whole thing in Python 3, with / being float division?

@StrikingLoo Luciano, thank you very much for your PR.
It is much better now, but please fix these two minor things first.
Regarding integer division, yes, you are right. Probably we should use // instead.
Regarding the tests, if you are only starting the test script, it does not test your current code, it tests the code running at cheat.sh (what makes not so much sense). To run the tests locally you should run the test server in a docker container (docker support will be added soon), or start a test server manually (not so straightforward process, at least not yet), or I can prepare a test environment for you.
What would you prefer?

Good morning! I didn't realize I was using self, I will correct it soon.
About the test environment, I don't really know much about Docker or how to get the server started, so I would love it if you made it easier to run a local server for testing (or just told me how to).
Thanks!

I will prepare a test environment for you and give you access to it.
I think it should be the best solution.

I think new commits get added automatically.
Please check if this works now.
Thanks for the feedback!

Please check variable names (ip/ip_addr etc.) + check function names _get_limit/get_limit + check code indentation.
What editor do you use?
If it is Vim, I recommend you the syntastic + pylint combination: many obvious mistakes will be found immediately.

I was actually using gedit, I just didn't realize the variable names had changed. Now I made it more consistent. I will look into installing syntastic and pylint later, I've never installed a vim package.

Even if you would have to invest some time in it, you would save much more time in the future.
Pylint + syntastic is a great combination. (and you could use cheat.sh-vim plugin too).


ERROR: Glaros server hosting metis is down

Both the travis and appveyor builds fail due to unavailability of metis.
Perhaps put files on an llnl mirror?

The METIS website seems to be back up. I'll restart the failed CI runs.


update executeUserOp implementation

msgSender field that the hook sees
one major upside of delegatecalling to the account only is that existing hooks will be more easily compatible
eg a spending limit hook will decode the execute calldata and check for the function signature but in the case of using the executeUserOp func on nexus the calldata could be address(erc20), transfer(...) in which case hooks also need to be able to decode this
If you instead have the account delegatecall to eg execute, then the hook can just decode normally
there are no real downsides to delegatecall here

I have a question. Can we limit execute to be onlyEntryPoint , not onlyEntryPointOrSelf ? Now when executeUserOp doesn't call execute , I think we can do it This will make execute safer for using with SmartSessions

executeUserOp can now delegate call to self with any calldata actually
btw these below methods are also onlyEntryPointOrSelf

installModule
uninstallModule
setRegistry
upgradeToAndCall
_authorizeUpgrade
withdrawDepositTo

executeUserOp can now delegate call to self with any calldata actually

yep, which is good.
I mean, since it can delegatecall now, can we make execute to be onlyEntryPoint ?
It will make execute->execute impossible. so the flow is more deterministic.
otherwise it will be possible to trick user to create some execute->execute permission and bypass some limits with sessions
so I suggest execute to be onlyEntryPoint

what do you mean by making execute-> execute impossible? and need for that


1- Showing Flow details of BF level only were relevant

2- exppanding "Data Validation" automatically in case of Flow Control context

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 1

See the complete overview on Codacy


Possible to have backdrop constantly stay until tour end?

Hi,
When set backdrop to true, is it possible to have backdrop constantly stay until tour end?

On version v0.10.3, backdrop stays on page until tour ends.
But after updating to newer version like v0.12.0, backdrop hides and appears between steps which is kind of annoying for users.
I hope it gets fixed in coming update

+1 for this.
I solved this by having a div that covers the whole viewport and appears when the step is hidden and then goes away when the step is shown.
This is what I did:

Add a div to the HTML and give it an id and the tour-backdrop class:

Add the css to make it span over the whole viewport:
#backdropFallback{ top:0; left:0; height: 100vh; width: 100vw; }
Add the handlers that deal with showing and hiding the fallback
onHidden: function (tour) {$("#backdropFallback").removeClass("hide");},
onShown: function (tour) {$("#backdropFallback").addClass("hide");},
onEnd: function (tour) {$("#backdropFallback").addClass("hide");},

Hope that helps

Recommend the following so it can remain hidden for the times the javascript is not loaded / properly rendered.


Add support for beta channels

Might be interesting for new releases that are already branched but not released yet.
Looks like this:

Can this be detected automatically? Then we could make a workflow that adds new channels and removes the beta tag appropriately.

Probably, yes. I don't think I can do that however because I lack skills in Workflows, Flakes and the current Tooling :(

Lets incorporate this change into #455


teleport: fix for darwin

Description of changes

Resolves issue from https://github.com/NixOS/nixpkgs/pull/194271#issuecomment-1273932766
Needs to be checked

The example override seemed to only need this for the main teleport package, not the rust subpackage also.
Also needs checking if this is only if using the rdp feature, or if it should always be in build inputs for darwin.
There could also be nuance where this is x86_64 darwin only but as long as it doesn't break aarch64 darwin we can probably keep it generally
cc: @takeda
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

build at least on M1 mac


Make Karpenter pod QoS Guaranteed

Currently the Karpenter pod has QoS Burstable. We should make this Guaranteed.

Nice! Yes!


EPIC: ESL Select & ESL Select List (beta)

Support for single selection
Both select and select list moved under forms directory
Beta doc placeholder created

:tada: This PR is included in version 2.0.0-beta.17 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Integrate Resilliency retry policies with rollback to transactional message brokers

I know that not all pubsub dapr components are backed by a real transactional message broker that has commit/rollback/deadletter capability, but it would be nice if the components that are backed by a transactional message broker would leverage the broker's native features for rollback/retry/deadletter functionality when implementing a retry policy.
For example, I'm getting expected behavior under "normal circumstances" when using an Azure ServiceBus pubsub with maxDeliveryCount=1 and an exponential retry policy with maxRetries=10. The message is tried 10 times with an increasing amount of time between each try, and it finally ends up on the deadletter queue for the subscription.

If you change maxDeliveryCount to 10 and maxRetries to 1, you get the 10 retries without the exponential backoff, which would reduce the risk of deadlettering because of transient error, but obviously doesn't behave as desired with respect to the backoff.
If the ASB component could be changed to so that it leverages the broker's native features for retry count and deadletter
to implement the retry policy, I think you could both get the exponential retry AND avoid exposure to scenarios that could cause unnecessary premature deadlettering.
To try to clarify what I'm thinking: If one sidecar instance receives a message, posts it to the subscriber service, and the subscriber returns a "retry" response, then the sidecar would use the Resiliency backoff policy to compute the amount of time needed for the backoff just as it does now (it could use the DeliveryCount property of the message in that computation), and holds the lease on the message that long before calling Abandon on it.  When Abandon is called, the message becomes available to be delivered again.  The DeliveryCount property of the message has increased, so the computed hold time is longer if the subscriber service returns a "retry" again.  This continues until either the message is successfully processed, or the Nth Abandon occurs, and the broker deadletters the message.
@ItalyPaleAle

I previously mentioned this in another issue, as it seemed related... let me know if I should just delete that comment from this issue: https://github.com/dapr/dapr/issues/4917


FR: Show file/folder details

Hi
it would be so nice if Gitea shows some additional details about files like file size, file creation date. Also it would be nice if Gitea shows folder sizes where folders aare present including a total repo size for the opened repo.
thanks

Folder size calculation would be quite expensive operation


Proper way to reuse c headers from the exposed lua library

In addition to using the @import("ziglua") module from zig code, I need to compile additional C extensions which depend on the headers for the correct lua version as exposed by ziglua.
After some trial and error I found this to work:
    my_module.addImport("ziglua", ziglua.module("ziglua"));
    // addImport already links by itself. but we need headers as well..
    my_module.linkLibrary(ziglua.artifact("lua"));

This feels a bit hacky as it relies on the artifact name "lua" which might be seen as internal to ziglua (not part of the exported module), and also, as addImport by itself is enough to add the .o files for the lua library, linkLibrary would add the same objects a second time?
This should "safely" be handled gracefully by most linkers, but it would be best to avoid this if possible.
Any thoughts about what the proper way would be?

Hey @bfredl!
This is a use case I'm working on right now. Currently your approach is what I'm planning to do.
Just a few months ago actually, using ziglua.module("ziglua") only gave you the Zig module. You actually did need to use ziglua.artifact("lua") to link the lua library. Only recently did I link lua to the zig module by default.
I actually have a draft blog post (waiting for Zig 0.12.0 to stabilize the APIs) that shows how to compile LPeg linked against Ziglua in a project: https://bc4b5350.nathancraddock.pages.dev/blog/ziglua-package/#compiling-lpeg
Am I understanding your question correctly?

Yes, that's exactly what I want. Including lpeg specifically, I discovered and had to work around the zig fetch bug yesterday myself  :sweat_smile: .

Great! I'll keep this issue open for a bit. You raised some questions about linkers and I want to make sure that this approach is correct. Once I have confirmed that, and have this process documented I'll close it.

Thanks. Just one more piece of information in case if it useful for anyone:
I also needed to get the lua include path as a LazyPath as well (this is workaround to an unrelated limitation in std.Build but anyway), which you can do using ziglua.artifact("lua").getEmittedIncludeTree() .


⚠ Bofrost.be has degraded performance

In 591baac, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1435 ms

Resolved: Bofrost.be performance has improved in 16b94b2.


Better exception reporting

In order for the error reports to propagate back to the requester, we also need to be sending problem report messages. These problem report messages are what will trigger DIDNotFound errors on the requester to resolve its Future that is waiting for a response from the resolver

We seem to have missed the mark a bit here.
Consider the following diagram:

In didcomm_resolver/protocol/v0_9.py, the ResolveDID.handle method raises HandlerExceptions. This halts the flow on the resolver but we still need to notify the requester. It is important to note that the same handle created to receive the ResolveDIDResult will also receive a ResolveDIDProblemReport and raise an exception mapped for it (ResolveDIDProblemReport.map_exception) as long as the thread of the ResolveDIDProblemReport message is assigned to the same thread as the ResolveDID message. We should not be creating a second handle with the send_and_wait_for_response method.


Problem in data/AMR/amr_2.0_utils/text_anonymization_rules.json

I got an error when runing sh preprocess_raw.sh sentence.txt：

Recategorizing subgraphs...2021年 08月 06日 星期五 23:57:10 CST
[2021-08-06 23:57:11,707 INFO] Better speed can be achieved with apex installed from https://www.github.com/nvidia/apex .
Traceback (most recent call last):
File "/data/leon/miniconda3/envs/amrgs/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/data/leon/miniconda3/envs/amrgs/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/data/leon/LP4EE/RAMS_1.0/AMR-gs-master/stog/data/dataset_readers/amr_parsing/preprocess/text_anonymizor.py", line 250, in
amr.abstract_map = text_anonymizor(amr)
File "/data/leon/LP4EE/RAMS_1.0/AMR-gs-master/stog/data/dataset_readers/amr_parsing/preprocess/text_anonymizor.py", line 61, in call
amr, text_map, max_length, anonym_type, pos_tag
File "/data/leon/LP4EE/RAMS_1.0/AMR-gs-master/stog/data/dataset_readers/amr_parsing/preprocess/text_anonymizor.py", line 83, in _abstract
collected_entities,
File "/data/leon/LP4EE/RAMS_1.0/AMR-gs-master/stog/data/dataset_readers/amr_parsing/preprocess/text_anonymizor.py", line 181, in _replace_span
if length == 1 and self._leave_as_is(start, amr, text_map, anonym_type):
File "/data/leon/LP4EE/RAMS_1.0/AMR-gs-master/stog/data/dataset_readers/amr_parsing/preprocess/text_anonymizor.py", line 143, in _leave_as_is
if is_anonym_type(index, amr, text_map, ['DATE_ATTRS']) and next_token_is(index, 1, amr, r"^''$"):
File "/data/leon/LP4EE/RAMS_1.0/AMR-gs-master/stog/data/dataset_readers/amr_parsing/preprocess/text_anonymizor.py", line 28, in is_anonym_type
return lemma in text_map and text_map[lemma]['ner'] in types

and the text_map  above was got by
text_anonymizor = TextAnonymizor.from_json(         os.path.join(args.util_dir, "text_anonymization_rules.json"))
so i analysis the json file and i find there are two wrong key in this file:
"span": "Chinese" in the anonym_type of named-entity
and
"span": "2002 08 28" in the anonym_type of date-entity
so i delete them and the error above don't show again.
I guess the key of "span" was mis-written in the text_anonymization_rules.json, is that right?

I found an error also originated from this file
RAMS_1.0/AMR-gs-master/data/AMR/amr_2.0_utils/text_anonymization_rules.json
when I run sh postprocess_2.0.sh

multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "/data/leon/miniconda3/envs/amrgs/lib/python3.6/multiprocessing/pool.py", line 119, in worker
result = (True, func(*args, **kwds))
File "/data/leon/miniconda3/envs/amrgs/lib/python3.6/multiprocessing/pool.py", line 44, in mapstar
return list(map(*args))
File "/data/leon/LP4EE/RAMS_1.0/AMR-gs-master/stog/data/dataset_readers/amr_parsing/postprocess/postprocess.py", line 27, in postprocess2
for amr in expander.expand_file(file_path + '.frame.wiki'):
File "/data/leon/LP4EE/RAMS_1.0/AMR-gs-master/stog/data/dataset_readers/amr_parsing/postprocess/expander.py", line 68, in expand_file
self.expand_graph(amr)
File "/data/leon/LP4EE/RAMS_1.0/AMR-gs-master/stog/data/dataset_readers/amr_parsing/postprocess/expander.py", line 94, in expand_graph
self.expand_ordinal_node(node, saved_dict, amr)
File "/data/leon/LP4EE/RAMS_1.0/AMR-gs-master/stog/data/dataset_readers/amr_parsing/postprocess/expander.py", line 169, in expand_ordinal_node
graph.add_node_attribute(node, 'value', int(saved_dict['ops'][0]))
ValueError: invalid literal for int() with base 10: '"-1"'

I guess the reason for this error is that there is a problem with the value of the key "ops" in this json
"ops": ["\"-1\""] and "ops": ["\"-4\""]
so I edit this file again by change:
"ops": ["\"-1\""] and "ops": ["\"-4\""] to"ops": ["-1"] and "ops": ["-4"]
and do sh preprocess_raw.sh -> sh work.sh -> sh postprocess_2.0.sh
at last I got xx.pred.post and the information from terminal like this:

[2021-08-14 22:42:27,415 INFO] Better speed can be achieved with apex installed from https://www.github.com/nvidia/apex .
ckpt/amr2.0.bert.gr/ckpt.pt_train_out.pred data/AMR/amr_2.0_utils
Something went wrong!!!
[2021-08-14 22:45:46,307 INFO] Restored 44947 name nodes.
[2021-08-14 22:45:46,308 INFO] Expanded 46538 name nodes.
[2021-08-14 22:45:46,308 INFO] Expanded 4619 date nodes.
[2021-08-14 22:45:46,308 INFO] Expanded 1 score nodes.
[2021-08-14 22:45:46,308 INFO] Expanded 1135 ordinal nodes.
[2021-08-14 22:45:46,308 INFO] Expanded 9342 quantities.
[2021-08-14 22:45:46,308 INFO] Expanded 2 urls.
Done.2021年 08月 14日 星期六 22:45:46 CST

it shows that something went wrong by assert Something went wrong!!!
but I don't know where it from, could you help me?  :-)

Hi @leoliner ,
The preprocessing scripts were borrowed from stog.  To be honest, I do not fully understand the details. Pls see if you can find help there.


Data Ordering is wrong in version 1.9.2, but size of the grid is the best -- is there a simple fix I can apply?

Hi,  I am still stuck at 1.9.2 because the size of the grid is most stable in that version.  For newer versions, when I load the grid again, the size becomes smaller.
However, in version 1.9.2, when there are more than 10 items in the data array, the order of the array is not honored in the grid.  This seems to be the only problem I am facing with 1.9.2.  Could you please point me to right place to fix the ordering problem?
Thanks.

For newer versions, when I load the grid again, the size becomes smaller.

This is your problem. If that gets fixed, then you can come to the latest version? What do you mean by the size becomes smaller? Sounds like you are having issues sizing your div.
PS This isn't an issue with the grid, so closing it. The best place for questions and help is on the forum :)


Docs: update for v0.12

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind documentation

/kind tests

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area commands

/area pkg

/area events

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/hold for the release to be out

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [alacuku,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/hold cancel


RDK-50885 : Crash handling [Thunder Master]

Reason for change: Improve Thunder Responsiveness [Crash handling in Thunder Master]
Test Procedure: Simulate crash in rdkservices and verify the call stack activity logs are generated
Risks: NO
Priority: P1
Signed-off-by: Sethulakshmi SK<EMAIL_ADDRESS>

This seems yet another push of : https://github.com/rdkcentral/Thunder/pull/1618 See those pull requests for the concerns.
Still looking for answers on what is the usecase? Who overwrites the signal handles why do you now find the rootcause, the plugin that rewrites the signal handlers.
Second remark, no need to create a PR per prelease. If applicable we will cherry-pick (feature of SCM to keep track on whats where) the commits to othere branches!! You are breqaking the SCM system this way!

@sethulakshmisk could you please elaborate on the usecases question?


New FaucetScript endpoint

This will remove the need for bitcoinjs-lib in the regtest-client for faucetComplex

Also allows hex string in place of address to use scriptPubkey.


Vortex Scans: Update domain

Closes #5023
Closes #5024
Checklist:

[ ] Updated extVersionCode value in build.gradle for individual extensions
[x] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[x] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[ ] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio
[ ] Have removed web_hi_res_512.png when adding a new extension

seems like they are back on their old domain


Bug: absolute value of exp not working properly

Hey! I just installed Skript-parser and tested it. I wanted to have a sample script to start, so I downloaded the one linked in this release note: https://github.com/SkriptLang/skript-parser/releases (https://gist.github.com/Blueyescat/8793eecf545088bf78007a18f19a2013)
This script generated the following errors:
[18:53:39] ERROR: No expression matching ''abs e' was found (line 15: "print "absolute of e = %abs e% (= %|e|%)"", test.sk)
[18:53:39] ERROR: No expression matching ''abs e' was found (line 16: "if abs e = |e|", test.sk)

The code is (lines 15, 16 and 17):
	print "absolute of e = %abs e% (= %|e|%)"
	if abs e = |e|:
		print "yeah 'abs e' = '|e|'"

Again, try it with the correct and latest build first and see if this still exists. This looks like a critical issue we had a month ago but was fixed.

Again, sorry I forgot to mention that in my issue, but I'm using the latest nightly build of Skript-parser. I downloaded it here: https://github.com/SkriptLang/skript-parser/actions/runs/233965848
And I've just download the JDK (14.0.1 iirc), on macOS 10.15.6.

You're right. I am able to reproduce this issue as well.


Create ai edge admins team

Description

Adding a new team with admin permission for the ai-edge repo
New Open Data Hub Member Requirements

[ ] New members have reviewed and acknowledged the Open Data Hub:

Code of Conduct
Contribution Guide
Community Membership Guidelines

[ ] Enabled 2FA on their GitHub account

Pull Request Requirements

[ ] New members are added in alphabetical order
[ ] Only one new member change per commit (if you add two members separate it in two commits
[ ] For individual user changes: Commit message format Add <USERNAME> to <opendatahub-io, mlops-sig, ...>.
[ ] For new team requests: Commit message format Create <TEAMNAME>. If the new team consists solely of existing members, you may
[ ] New GitHub team requests are from an existing opendatahub-io member who will function as the maintainer of the team. Each additional member will follow the same requirements for adding new members

@LaVLaS FYI


Support for R# 10

Believe support for R# 10 would be added soon? Would love to have that asap.

Agreed

Yep, planning on having it out tomorrow.

Any news here?

+1 :)

Yes, didn't manage to get it done last week :(
On the plus side, I'm working on it right now, just trying to get StyleCopPlus working. About to implement a hack that is slightly less dirty than the hack that is already there :)

Thanks for your efforts!
Maybe you can separate this two features - R# 10 and StyleCopPlus support - and release them independently?

Hi Matt, Any ETA on this?

Hi all. This is available on the Extension Manager - search for "StyleCop by JetBrains". (Long story short, there are two versions of StyleCop on the extension gallery. I'd love to merge them, but the other project's owner isn't responding)

Thanks for this @citizenmatt, installed and working perfectly :+1:

Thanks @citizenmatt! I've already installed it


Getting the consensus branch id fails on x86 Android emulator

This call to get the consensus branch ID for a given block height fails in certain situations, which can be easily reproduced on an x86 Android emulator. Instead of giving the proper consensus branch ID, it gives a repeating value:

Invalid branch ID for Sapling at height 419200 on mainnet expected:<76b809bb[]> but was:<76b809bb[76b809bb]>

This prevents a wallet from starting successfully because it requires a consensus branch id from the server that matches what the client is using.

Turns out that the Kotlin code was expecting a Long but the Rust code was returning an Int! Somehow, the JNI mapping didn't catch that the method signatures did not match.
Apparently, on 64-bit processors this worked fine but on 32-bit chips it failed. This probably has something to do with how Ints are actually represented on 64-bit hardware.
Switching the Rust code to return a long fixed the issue.

Update: the fix is shipped in alpha06 which is now live on maven central.


Fix contact us in restfiddle website.

Hi,
What issue in the contact us is being faced?
Regards,
Sameera
On Sat, Nov 7, 2015 at 7:17 PM, Anuja Kumar<EMAIL_ADDRESS>wrote:

—
Reply to this email directly or view it on GitHub
https://github.com/AnujaK/restfiddle/issues/403.

We need to integrate it with our mail system.


Escaping Issues

The implementation of readMulti builds the resulting URL by joining arguments with
let url = this.services.interpolator.interpolate(loadPath, { lng: languages.join('+'), ns: namespaces.join('+') });

This causes trouble for me when the namespace contains whitespaces as these can the not be recovered correctly on the backend.
More generally, this is problematic when the namespace contains anything that gets escaped by interpolate. Characters seem to get escaped as the HTML entities which is very confusing to parse on the backend since you would expect URL escaped arguments.

you can build your own function: https://github.com/i18next/i18next-xhr-backend/blob/master/src/index.js#L29

Thanks for the hint. Do you agree that things should be properly escaped as a default though?

got no opinion on that...namespaces should be simple - so your case is the first in 7 years...
backends are extra done as plugins to feel needs as user demand...personally I would completely remove multiload

This would for example be a problem if the namespace names are not in English (which makes sense if the default language is not English) or if they contain spaces. I agree that it's an unfortunate choice for namespaces to contain spaces…
Note that only the escaping of spaces is a problem in the multiload scenario. The general escaping of HTML entities is a problem in the normal code path as well.
Let me try to propose a PR to improve the situation and we can discuss things further :)


Formulate optimization batches to minimize overfitting

For instance, batch optimization executions as:
-walk forward tests
-in sample candidates gauged by out of sample measure
-fitness as function of multiple periods
This is all mostly already possible with simple scripting of the executable, which suggests effort is not too great.

Walk forward in/out sample is complete in batcher branch


fixed metadata date

fixed metadata date to reflect last (real) commit.

@larryms : Thanks for your contribution! The author, @KumudD, has been notified to review your proposed change.


I have something wrong with input file

ERROR: m_fusion: for direct speech input, only HMM trained by MFCC ior filterbank is supported
ERROR: m_fusion: failed to initialize AM
ERROR: Error in loading model
I want input .wav file to julius but get something wrong.
HELP!
I'm crazy,now.

I know what's wrong.
I didn't install git-lfs correctly.


travis: run integration tests via script

eliminates the in .travis.yam duplication of the integration test script.
if the change passes CI phase of integration test then the change is ok

Looking at the failed CI, it tries to push to ghcr.io. @hunchback can you please fix this?

@roee88 - have rebased


Use mixcoord for milvus cluster by default

What this PR does / why we need it:
Use mixcoord instead of separate rootcoord, datacoord, querycoord and indexcoord.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ x] Chart Version bumped
[ x] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [mychartname])
[ ] PR only contains changes for one chart

/lgtm


syntax of dockerfile is wrong

@sdake commented on Fri Oct 26 2018
see https://github.com/istio/cni/blob/master/deployments/kubernetes/Dockerfile.install-cni#L3
Also, please use ubuntu rather than Alpine Linux.  I'm not sure how this dockerfile is used, but as a project Istio should avoid distro proliferation.

Using hadolint to check the Dockerfile:
$ docker pull hadolint/hadolint:latest
...
$ docker run --rm -i hadolint/hadolint:latest < ./deployments/kubernetes/Dockerfile.install-cni
/dev/stdin:6 DL3018 Pin versions in apk add. Instead of `apk add <package>` use `apk add <package>=<version>`
/dev/stdin:6 DL3019 Use the `--no-cache` switch to avoid the need to use `--update` and remove `/var/cache/apk/*` when done installing packages
/dev/stdin:10 DL3020 Use COPY instead of ADD for files and folders
/dev/stdin:11 DL3020 Use COPY instead of ADD for files and folders
/dev/stdin:12 DL3020 Use COPY instead of ADD for files and folders
/dev/stdin:13 DL3020 Use COPY instead of ADD for files and folders
/dev/stdin:14 DL3020 Use COPY instead of ADD for files and folders

Nothing serious. I'll send a PR to address those warnings, and move to Ubuntu Xenial.
The image size is still good using Xenial:
$ make docker.install-cni
...
$ docker images istio/install-cni
REPOSITORY          TAG                                        IMAGE ID            CREATED              SIZE
istio/install-cni   0221a1e288c21b4cdca5ddf5498fcb4f70546f24   c4089449f56d        About a minute ago   155MB


Output mode for submitting results directly to AWS Security Hub

Hi @toniblyx
I came across https://aws.amazon.com/blogs/security/use-aws-fargate-prowler-send-security-configuration-findings-about-aws-services-security-hub/ which achieves my goal of submitting findings to Security Hub, but I would like to find a simpler method if I can.
Would you accept a pull request that added a new output mode, securityhub, then when chosen, Prowler would submit each check result directly to AWS Security Hub using the AWS CLI? I envisage the output mode generating a JSON string and then calling: aws securityhub batch-import-findings --findings <JSON Finding>.
If this is acceptable, I'll spend the time on a PR and add the optional IAM permission to the README etc.
Appreciate this is somewhat inefficient as the batch API can accept 100 checks at a time, so if you don't think this is a good idea, I'll look to generate a CSV and use a wrapper approach like the Wazuh integration instead.
Many thanks

Hi @marcjay, that's a great idea. It is something I'd like to do as well to simplify the integration, I also played with batch-import-findings and it makes the job pretty easy, initially. There are some considerations to take into account though. Due to the need of sending finding as ASFF (AWS Security Finding Format):

In Prowler It is easy to create ASFF output in json by adapting include/outputs. I would add another output type called json-asff for that and leaf the former json output as it is.

Each finding requires a unique identifier (Id) and it has to be the same identifier if its status changes afterwards otherwise Security Hub won't realize that a particular finding has changed status. That may require persistence somewhere, a DB, that's why in the POC you mention in the blopost uses DynamoDB (see aws securityhub update-findings help).

That POC mentioned also uses a lambda to generate and map findings in CSV output with a valid JSON ASFF formated. It also requires more data that ASFF has as mandatory and Prowler doesn't provide quite yet (like severity for example) but I can work on that with you. See below the minimum set of attributes that are required and my comments on what Prowler has today:

AwsAccountId: YES, that's available
CreatedAt: KIND OF, that's available but not at finding level, needs a change.
Description: YES, that's available
GeneratorId: this could be prowler-version
Id: NO, has to be unique and not recycled, I.e: prowler-checkID-accountID-region.
ProductArn: NO, has to be gotten somehow and it may require rewrite some checks.
Resources: NO, has to be created somehow.
SchemaVersion: YES, 2018-10-08.
Severity: NO, has to be added per check.
Title: YES.
Types: NO, has to be defined as namespace/category/classifier
UpdatedAt: NO, this is what I mentioned before, this is needed at creation and update.

Limits: there is a limit of 100 findings per request, that has to be considered.

Did you have that in mind? If that's all right for you we could move forward with that.

Hi @toniblyx - thank you for the swift and considered reply. Adding in my thoughts

In Prowler It is easy to create ASFF output in json by adapting include/outputs. I would add another output type called json-asff for that and leave the former json output as it is.

That sounds good to me. I can see from #190 that the current approach whereby each check outputs a valid, self-contained JSON object causes issues for some, where they are wanting a single valid JSON array object, containing all the checks. Presumably the existing design would apply here, with the user needing to post-process the JSON ASFF output, in order to either put up to 100 lines of findings into a JSON array and sending to AWS as a batch, or to wrap each object in [] and send each individually?
Architecturally, I don't imagine there's any other way? Holding the check outputs in memory and outputting fully-formed array(s) of findings for submitting to the API in batches once all checks are completed seems like it would require a big design change?

Each finding requires a unique identifier (Id) and it has to be the same identifier if its status changes afterwards otherwise Security Hub won't realize that a particular finding has changed status. That may require persistence somewhere, a DB, that's why in the POC you mention in the blopost uses DynamoDB (see aws securityhub update-findings help).

I also think an Id following the format prowler-checkID-accountID-regionis very sensible. Incidentally I took a look at the POC code and it would appear that status updates are not happening on existing findings, as it generates a random UUID on every request: link. From some testing, I think with this consistent format, persistence won't be necessary.

That POC mentioned also uses a lambda to generate and map findings in CSV output with a valid JSON ASFF formated. It also requires more data that ASFF has as mandatory and Prowler doesn't provide quite yet (like severity for example) but I can work on that with you. See below the minimum set of attributes that are required and my comments on what Prowler has today:

Again I was a little surprised that the Lambda function avoided many of these issues and is rather simplistic it seems: link.

CreatedAt: Fetch current time in include/outputs?
ProductArn: The lambda function approach looks good here, having read the docs: 'arn:aws:securityhub:' + awsRegion + ':' + accountId + ':product/' + accountId + '/default'
Resources: Is the generic approach in the Lambda sufficient for a first stab? link Otherwise it's considerable changes to all checks I would imagine?
Severity: I would argue same approach as Resources?
Types: Same again? link
UpdatedAt: Again current time here should be fine I think? From testing, 'updating' a finding, with a newer but identical CreatedAt and UpdatedAt correctly updates UpdatedAt in Security Hub but doesn't touch the CreatedAt time

Perhaps for Resources, Severity and Types, we use those values as generic defaults, with checks being able to override them, so a gradual approach could be taken to classify existing/new checks, falling back to these sane generic defaults?

Limits: there is a limit of 100 findings per request, that has to be considered.

My initial thought was that if a securityhub output mode was chosen, each call to textPass(), textFail() and textInfo() would pipe an ASFF JSON string directly into a aws securityhub batch-import-findings --findings {} call - i.e. the CLI would be invoked once per check, so no concern around limits. Going back to the architecture question, Is there a way you think we could batch this?

Thanks for all your feedback @marcjay, those examples on the code mentioned in the blog post are pretty limited to make it work, that is why I say that is a POC or an initial test, which is good but I don't see it for a real use case since it does not update exiting findings. I also agree with you on sending findings in securityhub output mode per call, that makes it probably easier to manage in terms of limits. If we go with the import per check we don't have to think about batch, do we? My main concern here is persistence for existing checks and their updates. What do you suggest for that?

Hey folks, weighing in here real quick since I was the one that wrote the blog (with Toni's help) and I was the TPM on the Security Hub team during our major ASFF and Product ARN Changes.
The blog is a limited first pass, this is due to the lack of any sort of resource information being output from Prowler, which Toni has addressed in another branch somewhere. That is why I mapped everything to the AwsAccount Resource.Type.
In a perfect world, if Prowler can output Resource ARN and had a mapping of Resource.Type that matched the ones for ASFF then it would be trivial to pick up the other needed items that are mandatory for a finding and I would also drop the UUID as I'd be able to from an ID of Resource + Check + Compliance status. ID's in Security Hub are stateful and forming ID's in that way can strongly bind them to the resource. I got around this by using DyanmoDB as an intermediary and streaming NEW_IMAGES to Lambda before going to Security Hub, it would keep duplicates from coming in, but it would also prevent a resource moving in and out of compliance from going to Security Hub which is not ideal.
As far as findings go, our BatchImportFindings API has a rate limit of 10TPS with a burst of 30TPS before being throttled. The throttle will reset every second, and if Prowler was calling BIF after every Group or individual Check that would be fine, you are metered for finding ingestion events above 10K per month per region per Account in Security Hub, it doesn't matter if you call BIF with batches of 100 or 1 finding per call.
As far as CreatedAt goes, if you are using the same finding ID then it will ignore that in the backend, which is proper functionality, you still need to include it in the call funnily enough. We were looking at having our back end handle both CreatedAt and UpdatedAt but I'm not sure if that decision was scuttled completely or will be brought about.
If I wrote that blog today, I'd convert CSV to JSON in Fargate and directly call BIF instead of going to DyanmoDB. That said, I still need a Resource.Type and an ARN per Prowler finding to be able to do that. Ideally I'd also get a Severity that matched Security Hub as an output so there are no translations needed at all.

Thanks @toniblyx and @jonrau1 for your input - good to hear some of the context behind the blog post and integration method.
I figured that it was easier to have a conversation with some code to look at, so I've open a draft pull request: #530. There are still some tasks to work on which I've noted on the PR, keen to get feedback and make changes
On the question of addressing the need for a unique Id per finding - to allow for updates over time but also handle the fact that each check might run against multiple resources making check ID non-unique, I used the format prowler-TITLE_ID-accountID-region-UNIQUE_ID, where UNIQUE_ID is the message from prowler, with all non conforming characters (according to the ASFF spec) removed. So, output such as:

1.3  [check13] Ensure credentials unused for 90 days or greater are disabled (Scored)
PASS! User "bsmith" found with credentials used in the last 90 days
PASS! User "jdoe" found with credentials used in the last 90 days

Translates to separate findings with Ids:
prowler-1.3-1234567890-eu-west-1-User_bsmith_found_with_credentials_used_in_the_last_90_days
prowler-1.3-1234567890-eu-west-1-User_jdoe_found_with_credentials_used_in_the_last_90_days
I do appreciate this means that if a new version of prowler makes changes to the messaging for a particular check, findings from it won't update existing findings, but I don't see an easy solution, given that some checks iterate over multiple resources across multiple regions so there can be quite a few variables in each message
How findings appear in Security Hub:

From prowler output:
$ ./prowler -M securityhub
                          _
  _ __  _ __ _____      _| | ___ _ __
 | '_ \| '__/ _ \ \ /\ / / |/ _ \ '__|
 | |_) | | | (_) \ V  V /| |  __/ |
 | .__/|_|  \___/ \_/\_/ |_|\___|_|v2.2.1
 |_| the handy cloud security tool

 Date: Tue  7 Apr 2020 15:28:02 BST

 Colors code for results:
 INFO (Information), PASS (Recommended value),  FAIL (Fix required),  Not Scored

 This report is being generated using credentials below:

 AWS-CLI Profile: [] AWS API Region: [eu-west-1] AWS Filter Region: [all]

 Caller Identity:
-------------------------------------------------------------------------------------
|                                 GetCallerIdentity                                 |
+--------------+------------------------------------------+-------------------------+
|    Account   |                   Arn                    |         UserId          |
+--------------+------------------------------------------+-------------------------+
|  123456789|  arn:aws:iam::123456789:user/marcjay  |  ABCDEFGH  |
+--------------+------------------------------------------+-------------------------+

 1.0 Identity and Access Management - CIS only - [group1] ***********

 0.1 Generating AWS IAM Credential Report...

 1.1  [check11] Avoid the use of the root account (Scored)
       PASS! Root user in the account wasn't accessed in the last 1 days... Successfully submitted finding

 1.2  [check12] Ensure multi-factor authentication (MFA) is enabled for all IAM users that have a console password (Scored)
       FAIL! User bsmith has Password enabled but MFA disabled... Successfully submitted finding
       FAIL! User jdoe has Password enabled but MFA disabled... Successfully submitted finding
       FAIL! User bwilliams has Password enabled but MFA disabled... Successfully submitted finding

 1.3  [check13] Ensure credentials unused for 90 days or greater are disabled (Scored)
       PASS! User "bsmith" found with credentials used in the last 90 days... Successfully submitted finding
       PASS! User "jdoe" found with credentials used in the last 90 days... Successfully submitted finding
       PASS! User "bwilliams" found with credentials used in the last 90 days... Successfully submitted finding

This is awesome! Thanks for the clarification @jonrau1 and for your code @marcjay, looking at it.


Cyclic Block Placer deletes Better with Mods mini blocks instead of placing them

Minecraft version & Mod Version:
Minecraft 1.12.2
Cyclic 1.15.3
Better With Mods 1.18
Single player or Server:
Both
Describe problem (what you were doing / what happened):
Block Placer deletes Better With Mods Mini Blocks instead of placing them.
Mini blocks are siding, moulding, and corners.
Crash log (if any):
None
Originally posted on the SevTech issue tracker. https://github.com/DarkPacks/SevTech-Ages/issues/2538
Maybe provide a block placer blacklist in the config?

Ill poke the BWM devs and see if i can get some insight.  If not then yeah maybe blacklist?
Bottom line is that when i go "world.setBlockState(...)" it returns TRUE for success, which is supposed to mean "yep block is placed in the world" and thats why i steal from slot.

https://minecraft.curseforge.com/projects/cyclic/files/2564637


[PORT] Keep handoff event value as JObject

Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/3521

Changed projects

Microsoft.Bot.Builder
Microsoft.Bot.Builder.Tests

C# change


Fix for the overlapping of workspace scrollbar onto the blocks drawer.

I've implemented functionality to detect whether the drawer within the workspace is opened. If it is open, I've ensured that the scrollbar gets hidden to provide a seamless user experience to interact with the last block. (changes made in the hideChaff() function).

I've added code to set the scrollbar visibility upon zooming in or out if the user wants to position the existing blocks properly. (changes made in the onMouseWheel_() function).

BEFORE:
Link: https://github.com/mit-cml/appinventor-sources/assets/116882464/88a26769-242b-409d-ae9b-5da3c93f941f
**AFTER: **
Link: https://github.com/mit-cml/appinventor-sources/assets/116882464/42a95582-9173-4ee6-ac9e-fc66a12203fc
Would love to hear any other possible better solutions or suggestions.

Can one of the admins verify this patch?

@AppInventorWorkerBee ok to test


Discrepancy in display of total run time in reports

Describe the bug
Discrepancy in display of total run time in reports
To Reproduce
Steps to reproduce the behavior:

Run a Small Test suite to verify the total run time
after execution note the total time from the execution log
go to clucumber report and note the total time for execution and compare with the above step.
See below screenshot
Actual behaviour
total runtime displayed on the report is sum of runtime of all the scenarios
Expected behavior
Good to have parallel runtime on the reports apart from sum of the runtime.

Attachments
If applicable, add screenshots or sample JSON files to help explain your problem.
Additional context
Add any other context about the problem here.

If you use a newer Cucumber jvm, this will display the parallel runtime since its generated json contains timestamps for each scenario. In older versions, there is no information about when a scenario actually ran - that's why you get the total time instead.

Thanks for the input.
I have updated the Cucumber-Jvm to latest version, now i could able to see the parallel run time on clucumber reports.

Thank you Very much Benjamin Bischoff!
Closing the issue

i am still seeing little difference in test run time - Please find the screens below

Well the report looks only at the tests that were run and not the total build time (which is shown in your screenshot of the console output). Depending on what is being done during the build this naturally takes longer than the test runs.
If you look at the start and end time in the report, it is correct.

Thanks for details explanation.


New map index

Overview

@pwestman82 - Hey Peter, the map and the cards are now displayed properly.
@jones-sam - can we merge this PR with the Master and then Peter can create a new branch to add additional styling to the map markers?


Try to run "python setup.py build_ext --inplace" in Windows 10

C:\Users\Downloads\Compressed\R2CNN_Faster-RCNN_Tensorflow-master\libs\box_utils>python setup.py build_ext --inplace
running build_ext
Traceback (most recent call last):
File "setup.py", line 132, in
cmdclass={'build_ext': custom_build_ext},
File "C:\Users\Anaconda3\lib\distutils\core.py", line 148, in setup
dist.run_commands()
File "C:\Users\Anaconda3\lib\distutils\dist.py", line 966, in run_commands
self.run_command(cmd)
File "C:\Users\Anaconda3\lib\distutils\dist.py", line 985, in run_command
cmd_obj.run()
File "C:\Users\Anaconda3\lib\site-packages\Cython\Distutils\old_build_ext.py", line 186, in run
_build_ext.build_ext.run(self)
File "C:\Users\slcib\Anaconda3\lib\distutils\command\build_ext.py", line 340, in run
self.build_extensions()
File "setup.py", line 104, in build_extensions
customize_compiler_for_nvcc(self.compiler)
File "setup.py", line 77, in customize_compiler_for_nvcc
default_compiler_so = self.compiler_so
AttributeError: 'MSVCCompiler' object has no attribute 'compiler_so'

https://github.com/DetectionTeamUCAS/RetinaNet_Tensorflow_Rotation/issues/50

You can refer to this script, which was modified by others before, and it is not guaranteed to be used directly. @Cibi075
setup.txt

C:\Users\Downloads\Compressed\R2CNN_Faster-RCNN_Tensorflow-master\libs\box_utils>python setup.py build_ext --inplace
running build_ext
Traceback (most recent call last):
File "setup.py", line 132, in
cmdclass={'build_ext': custom_build_ext},
File "C:\Users\Anaconda3\lib\distutils\core.py", line 148, in setup
dist.run_commands()
File "C:\Users\Anaconda3\lib\distutils\dist.py", line 966, in run_commands
self.run_command(cmd)
File "C:\Users\Anaconda3\lib\distutils\dist.py", line 985, in run_command
cmd_obj.run()
File "C:\Users\Anaconda3\lib\site-packages\Cython\Distutils\old_build_ext.py", line 186, in run
_build_ext.build_ext.run(self)
File "C:\Users\slcib\Anaconda3\lib\distutils\command\build_ext.py", line 340, in run
self.build_extensions()
File "setup.py", line 104, in build_extensions
customize_compiler_for_nvcc(self.compiler)
File "setup.py", line 77, in customize_compiler_for_nvcc
default_compiler_so = self.compiler_so
AttributeError: 'MSVCCompiler' object has no attribute 'compiler_so'

Have you solved the problem


Add option for Visualize attribute to constantly update its field / property

I have some variables in player template project I would like to see constantly update in-game.
The control the visualize attribute creates should be non-editable / read-only / disabled from user input.

This feature has now been added.


makers: add vue ft

Add makers for https://vuejs.org/ (.vue filetype).

@mhinz all done. How does it look to you now?

LGTM. I'm just waiting for the tests to finish, although I see no reason why they should fail. :)

Thanks!


add optional debug info to Ops calls

@wsmoses i made the debug info optional because calling stacktrace has a big overhead. for example, stacktrace takes around 800-900 $\mu s$ in my laptop, while creating a Location takes around 3 $n s$
in order to add the debug info, i've added the DEBUG_MODE global var and the with_debug method to manage it

Did the passes or jll change.
That probably indicates you’re running an invalid pass

error: 'transform.apply_patterns' op expected children ops to implement PatternDescriptorOpInterface

I updated the transforms in https://github.com/EnzymeAD/Reactant.jl/commit/9e04ba658a25640c870b635ebf4458b6011209d1 but did not update Reactant_jll compat so you might need to update Reactant_jll?


配置模板

Signed-off-by: Alex chow<EMAIL_ADDRESS>{PR title}

Summary of the changes (Less than 80 chars)
Description
fixes #{bug number}

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
54b3d7e -> 4d3c7e4

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.10.8 -> v1.10.10

terraform-ibm-modules/common-pipeline-assets
action
minor
v1.16.1 -> v1.17.0

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.10.10
Compare Source
Bug Fixes

fixed a bug in upgrade test (#&#8203https://github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper/issues/579es/579)) (8d18919)

v1.10.9
Compare Source
Bug Fixes

deps: update module golang.org/x/crypto to v0.11.0 (#&#8203https://github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper/issues/578es/578)) (7d3a4ef)

terraform-ibm-modules/common-pipeline-assets (terraform-ibm-modules/common-pipeline-assets)
v1.17.0
Compare Source
Features

CRA will now use SCC instances api instead of deprecated account api (#&#8203https://github.com/terraform-ibm-modules/common-pipeline-assets/issues/500es/500)) (4044cc1)
default CRA profile is now FSCloud 1.3.0 for v2 pipeline (#&#8203https://github.com/terraform-ibm-modules/common-pipeline-assets/issues/500es/500)) (4044cc1)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 0.2.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Enable bitcode for watchOS and tvOS

Description of Change
Enable bitcode for watchOS and tvOS
Bugs Fixed
None.
API Changes
None.
Behavioral Changes
Making sure bitcode is enabled in all the libraries that need it.
PR Checklist

[ ] Has tests (if omitted, state reason in description)
[ ] Rebased on top of master at time of PR
[ ] Changes adhere to coding standard
[ ] Updated documentation

/azp run


fix panda/rakudo star installation on system with no previous perl6

Test for presence of 'ls' rather than 'perl6' since Shell::Command may be used before perl6 is in the path.
This happens when panda in Rakudo Star is bootstrapped on a system without a previous perl6 install using the Shell::Command as embedded in panda.

Maybe this should be fixed in star by adding a PATH definituin


feat: code action for OSS via LS in IntelliJ [IDE-284]

Description
This PR enhances the existing codeActions returned via the LS for OSS with quickfix actions that tell us what version to upgrade a package to. In order to do this without code duplication and be consistent with the HTML rendered remediation advice that gets rendered in VSCode, I had to refactor some of the code and introduce a Remediation field to the internal snyk.Issue representation.
NewPreferredCodeAction is not used so I removed it.
The only difference is that the new "OSS via LS" code actions have Snyk Learn actions too and we return quickfix code actions for all possible upgrade paths, rather than just the one.
To do:

test for all different package managers that have a corresponding annotator in https://github.com/snyk/snyk-intellij-plugin/blob/1b78014fbf3f8810e35ef7ce7d48e5a63ffbbf02/src/main/kotlin/snyk/oss/annotator/
verify that in VSCode the OSS code actions and suggestion panel still look the same
verify that in IntelliJ it still works with and without our changes

Checklist

[x] Tests added and all succeed
[x] Linted
[ ] README.md updated, if user-facing
[ ] License file updated, if new 3rd-party dependency is introduced

🚨After having merged, please update the CLI go.mod to pull in latest language server.
Screenshots / GIFs
This was tested by building snyk-ls and then the CLI with a snyk-ls replace directive, then changing the IntelliJ sandbox generated from https://github.com/snyk/snyk-intellij-plugin/pull/530 to point at the local CLI.
The tests were run on https://github.com/snyk-labs/snyk-chat-goof.
Before:

After:

Would be nice to also have a code lens (like snyk autofix) :)


feat: add support for sponsored txs

Try out this version of the Stacks Wallet - download extension builds.

Fixing #947. Would like feedback from @aulneau on the UI updates:

Type of Change

[x] New feature

Does this introduce a breaking change?
No
Are documentation updates required?
Can be tracked here: https://github.com/blockstack/docs/issues/1133
Checklist

[x] Code is commented where needed
[ ] Unit test coverage for new or modified code paths
[ ] Changelog is updated
[x] Tag @hstove

as noted, this will stay in draft until https://github.com/blockstack/connect/pull/100 is merged and released

@agraebe Does this PR resolve #947 completely?

@markmhx yes


capitalize grid_size_x, grid_size_y, grid_size_z as per convention

If possible, I'd like to capitalize these variable names as per the convention for preprocessor defines. (code)

I disagree with doing this. It really hurts readability and breaks the symmetry with with all the other tunable parameters currently in use, such as "block_size_x" and so on. It's better to regard these as built-in variables that the Kernel Tuner inserts, rather than constants people use in their code.