Allow only one instance of 'CANpie Server' application

Only one instance of application should be allowed.

HI.  this means that the Application that uses the CANPie driver shall be open only in one instance.  and if you try to open two instances there is a problem??… for example windows applications, you rise the first instance and you get access to CAN Bus... but if i try to reopen a second instance of the application, the second will not get access to CAN Bus?

Solved by introduction of the QCanServerSettings class


feat: python bindings

upgrade deps
feat: publish to pypi

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@nicelyc @corrjo @zubinmadon @mark-ship-it Hit me up and I'll add you as maintainers on PyPi.
https://pypi.org/project/multi-convention-namer/
A

Ohh schwifty.

Needs some GitHub secrets added: TWINE_USERNAME: token and TWINE_PASSWORD: pypi-...
I can either generate and add them myself (if folks are cool with me becoming an admin of this repo), or you can and I'll add you in pypi.


fix(api-reference): hash replacement

this pr fixes hash replacement that is leading to some redirection issue turning #tag/authentication into #/tag/authentication when using sub root in url.
originally reported by Henrique

closing this in favor of #2858

I'm not sure if that pr fixes this issue, it just fixes the double click to link


Implementation of the first performance test scenario

Readiness checklist

[ ] I added/updated unit tests.
[ ] I added/updated integration tests.
[x] I ensured that the PR title is good enough for the changelog.
[x] I labeled the PR.

Please refer to the added readme files:
https://github.com/nmshd/backbone/blob/NMSHDB-65-implementation-of-the-first-performance-test-scenario/Applications/ConsumerApi/test/ConsumerApi.Tests.Performance/src/scenarios/README.md
https://github.com/nmshd/backbone/blob/NMSHDB-65-implementation-of-the-first-performance-test-scenario/Applications/ConsumerApi/test/ConsumerApi.Tests.Performance/README.md
Example output of scenario 1 (verbose):
$ npx webpack && k6.exe run .\dist\s01.test.js -v
asset s01.test.js 70.7 KiB [emitted] (name: s01.test)
orphan modules 14.1 KiB [orphan] 11 modules
runtime modules 937 bytes 4 modules
built modules 66.5 KiB [built]
  ./src/scenarios/s01.test.ts + 11 modules 16.2 KiB [not cacheable] [built] [code generated]
  ./node_modules/papaparse/papaparse.js 50.3 KiB [built] [code generated]
  external "stream" 42 bytes [built] [code generated]
webpack 5.93.0 compiled successfully in 1755 ms
DEBU[0000] Logger format: TEXT
DEBU[0000] k6 version: v0.52.0 (commit/20f8febb5b, go1.22.4, windows/amd64)

          /\      |‾‾| /‾‾/   /‾‾/
     /\  /  \     |  |/  /   /  /
    /  \/    \    |     (   /   ‾‾\
   /          \   |  |\  \ |  (‾)  |
  / __________ \  |__| \__\ \_____/ .io

DEBU[0000] Resolving and reading test '.\dist\s01.test.js'...
DEBU[0000] Loading...                                    moduleSpecifier="file:///D:/backbone/Applications/ConsumerApi/test/PerformanceTests/dist/s01.test.js" originalModuleSpecifier=".\\dist\\s01.test.js"
DEBU[0000] '.\dist\s01.test.js' resolved to 'file:///D:/backbone/Applications/ConsumerApi/test/PerformanceTests/dist/s01.test.js' and successfully loaded 72349 bytes!
DEBU[0000] Gathering k6 runtime options...
DEBU[0000] Initializing k6 runner for '.\dist\s01.test.js' (file:///D:/backbone/Applications/ConsumerApi/test/PerformanceTests/dist/s01.test.js)...
DEBU[0000] Detecting test type for...                    test_path="file:///D:/backbone/Applications/ConsumerApi/test/PerformanceTests/dist/s01.test.js"
DEBU[0000] Trying to load as a JS test...                test_path="file:///D:/backbone/Applications/ConsumerApi/test/PerformanceTests/dist/s01.test.js"
DEBU[0000] Loading...                                    moduleSpecifier="https://jslib.k6.io/httpx/0.1.0/index.js" originalModuleSpecifier="https://jslib.k6.io/httpx/0.1.0/index.js"
DEBU[0000] Fetching source...                            url="https://jslib.k6.io/httpx/0.1.0/index.js?_k6=1"
DEBU[0000] Fetched!                                      len=8730 t=272.2943ms url="https://jslib.k6.io/httpx/0.1.0/index.js?_k6=1"
DEBU[0000] Babel: Transformed                            t=289.3635ms
INFO[0000] Loading identities                            source=console
INFO[0000] Finished Loading                              source=console
DEBU[0000] Runner successfully initialized!
DEBU[0000] Parsing CLI flags...
DEBU[0000] Consolidating config layers...
DEBU[0000] Parsing thresholds and validating config...
DEBU[0000] Initializing the execution scheduler...
DEBU[0000] Starting 2 outputs...                         component=output-manager
DEBU[0000] Starting...                                   component=metrics-engine-ingester
DEBU[0000] Started!                                      component=metrics-engine-ingester
     execution: local
        script: .\dist\s01.test.js
        output: -

     scenarios: (100.00%) 1 scenario, 1 max VUs, 1h0m30s max duration (incl. graceful stop):
              * constantRequestRate: 0.00 iterations/s for 1h0m0s (maxVUs: 1, gracefulStop: 30s)

DEBU[0000] Starting the REST API server on localhost:6565
DEBU[0000] Trapping interrupt signals so k6 can handle them gracefully...
DEBU[0000] Starting emission of VUs and VUsMax metrics...
DEBU[0000] Start of initialization                       executorsCount=1 neededVUs=1 phase=execution-scheduler-init
DEBU[0000] Initialized VU #1                             phase=execution-scheduler-init
DEBU[0000] Finished initializing needed VUs, start initializing executors...  phase=execution-scheduler-init
DEBU[0000] Initialized executor constantRequestRate      phase=execution-scheduler-init
DEBU[0000] Initialization completed                      phase=execution-scheduler-init
DEBU[0000] Start of test run                             executorsCount=1 phase=execution-scheduler-run
DEBU[0000] setup() is not defined or not exported, skipping!
DEBU[0000] Start all executors...                        phase=execution-scheduler-run
DEBU[0000] Starting executor                             executor=constantRequestRate startTime=0s type=constant-arrival-rate
DEBU[0000] Starting executor run...                      duration=1h0m0s executor=constant-arrival-rate maxVUs=1 preAllocatedVUs=1 scenario=constantRequestRate tickerPeriod=5m0s type=constant-arrival-rate
DEBU[3600] Regular duration is done, waiting for iterations to gracefully finish  executor=constant-arrival-rate gracefulStop=30s scenario=constantRequestRate
DEBU[3601] Executor finished successfully                executor=constantRequestRate startTime=0s type=constant-arrival-rate
DEBU[3601] teardown() is not defined or not exported, skipping!
DEBU[3601] Test finished cleanly
DEBU[3601] Stopping vus and vux_max metrics emission...  phase=execution-scheduler-init
DEBU[3601] Sending usage report...
DEBU[3601] Metrics emission of VUs and VUsMax metrics stopped
DEBU[3601] Releasing signal trap...
DEBU[3601] Waiting for metrics and traces processing to finish...
DEBU[3601] Metrics and traces processing finished!
DEBU[3601] Stopping outputs...
DEBU[3601] Stopping 2 outputs...                         component=output-manager
DEBU[3601] Stopping...                                   component=metrics-engine-ingester
DEBU[3601] Stopped!                                      component=metrics-engine-ingester
DEBU[3601] Generating the end-of-test summary...

     ✓ response code was 201
     ✓ challenge contains correct device
     ✓ challenge contains correct address
     ✓ challenge id is not empty

     checks.........................: 100.00% ✓ 52                  ✗ 0
     data_received..................: 28 kB   7.697837102571258 B/s
     data_sent......................: 18 kB   4.937836839599921 B/s
     http_req_blocked...............: avg=62.3µs   min=0s       med=0s       max=1.11ms   p(90)=0s       p(95)=381.75µs
     http_req_connecting............: avg=22.58µs  min=0s       med=0s       max=587.09µs p(90)=0s       p(95)=0s
     http_req_duration..............: avg=268.91ms min=103.68ms med=219.42ms max=1.49s    p(90)=338.57ms p(95)=474.16ms
       { expected_response:true }...: avg=268.91ms min=103.68ms med=219.42ms max=1.49s    p(90)=338.57ms p(95)=474.16ms
     http_req_failed................: 0.00%   ✓ 0                   ✗ 26
     http_req_receiving.............: avg=1.84ms   min=0s       med=1.7ms    max=4.44ms   p(90)=4.17ms   p(95)=4.32ms
     http_req_sending...............: avg=104.93µs min=0s       med=0s       max=2.21ms   p(90)=0s       p(95)=384.52µs
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s
     http_req_waiting...............: avg=266.97ms min=100.12ms med=219.23ms max=1.49s    p(90)=337.72ms p(95)=470.81ms
     http_reqs......................: 26      0.007221/s
     iteration_duration.............: avg=539.06ms min=325.21ms med=388.82ms max=2.01s    p(90)=551.75ms p(95)=1.13s
     iterations.....................: 13      0.003611/s
     vus............................: 0       min=0                 max=1
     vus_max........................: 1       min=1                 max=1

running (1h00m00.4s), 0/1 VUs, 13 complete and 0 interrupted iterations
constantRequestRate ✓ [======================================] 0/1 VUs  1h0m0s  0.00 iters/s
DEBU[3601] Usage report sent successfully
DEBU[3601] Everything has finished, exiting k6 normally!

I have added a small utility which can be used to analyze the output of k6.
Example:
# node .\result-analyzer\src\main.js .\result.csv
HTTP Request Metrics Grouped by Route and Type:

 ===

Route: /connect/token
Total Requests: 107
Status Codes:
  200: 107
Timings:
http_req_duration:       524.23 ms
http_req_blocked:        0.02 ms
http_req_connecting:     0.01 ms
http_req_tls_handshaking:        0.00 ms
http_req_sending:        0.06 ms
http_req_waiting:        523.90 ms
http_req_receiving:      0.26 ms
http_req_failed:         0.00 ms

 ===

Route: /api/v1/Challenges
Total Requests: 107
Status Codes:
  201: 107
Timings:
http_req_duration:       290.02 ms
http_req_blocked:        0.01 ms
http_req_connecting:     0.00 ms
http_req_tls_handshaking:        0.00 ms
http_req_sending:        0.02 ms
http_req_waiting:        277.18 ms
http_req_receiving:      12.81 ms
http_req_failed:         0.00 ms

I have added a small utility which can be used to analyze the output of k6.

This utility should be part of the script that is used to run the tests, so that you don't have to know/remember to call the script.
What does "Type" mean? ("HTTP Request Metrics Grouped by Route and Type"

Oh, and 3. what if there are for example GET /Tokens and POST /Tokens? Currently, your output only shows the rquest path, not the request method.

I've changes the output to group by and include the method:
Route: POST /connect/token
Total Requests: 31
Status Codes:
  200: 31
Timings:
http_req_duration:       193.00 ms
http_req_blocked:        0.06 ms
http_req_connecting:     0.04 ms
http_req_sending:        0.03 ms
http_req_waiting:        192.74 ms
http_req_receiving:      0.23 ms
http_req_failed:         0.00 ms

Route: POST /api/v1/Challenges
Total Requests: 31
Status Codes:
  201: 31
Timings:
http_req_duration:       121.26 ms
http_req_blocked:        0.00 ms
http_req_connecting:     0.00 ms
http_req_sending:        0.08 ms
http_req_waiting:        116.09 ms
http_req_receiving:      5.10 ms
http_req_failed:         0.00 ms

I have also created windows (PS) and Linux (bash) scripts that take care of compiling and running the test, and then calling the analyzer. Hence,

Fixed.
I've renamed type to timings
Fixed.

I really don't like all the abbreviations you use throughout the code and readme files. This makes it so much harder to understand everything when you work with it for the first time.

@tnotheis I cannot rerequest review here, but it should be good to go.

I must call attention to these results: https://github.com/nmshd/backbone/pull/785/files#r1756606368


scope all css rules to .mermaid

Prevents the css from messing with other styles on the site.

@knsv any chance to get this PR merged? :slightly_smiling_face:

@tylerlong do you have an ability to merge PRs? :slightly_smiling_face:

If I'm not mistaken this will resolve: https://github.com/knsv/mermaid/issues/584

Anyone with permissions, please, merge this bugfix. :slightly_smiling_face:
/cc @knsv @tylerlong

Waiting for this merge too :innocent:

By the way, mermaid adds this style (for neutral theme):
svg {
  color: rgb(46, 46, 46);
  font: normal normal 400 normal 13px / 20.8px Menlo, "DejaVu Sans Mono", "Liberation Mono", Consolas, "Ubuntu Mono", "Courier New", "andale mono", "lucida console", monospace;
}

which breaks other SVG elements on pages.
It seems this PR does not fix that styles. :slightly_smiling_face:

Sorry for the late reply guys.
I am working on version 8.0 and the CSS part has been completely rewritten.
I will merge this PR manually into the latest code base.

Applied in commit: https://github.com/knsv/mermaid/commit/be33c41a4023a5054b3ab25945d9806d957881c8

@tylerlong
What about this diff? :slightly_smiling_face:
diff --git a/src/mermaidAPI.js b/src/mermaidAPI.js
index 2a45de7..6e85592 100644
--- a/src/mermaidAPI.js
+++ b/src/mermaidAPI.js
@@ -440,7 +440,7 @@ const render = function (id, txt, cb, container) {
   const cs = window.getComputedStyle(svg)
   s.innerHTML = `
   ${themes[config.theme] || defaultTheme}
-svg {
+.mermaid svg {
   color: ${cs.color};
   font: ${cs.font};
 }

@blackst0ne I removed that part because I don't what it is. And the CSS style seems to work fine.

I made it even better. I scope the css with svg ID, so even there are multiple diagrams in the single page, each of them could have different CSS styles: https://github.com/knsv/mermaid/commit/2ed515091f7d45c29db5071c7b3ae8f272503e62

@tylerlong is it possible to get a bumped version in npm, please? :slightly_smiling_face:

@blackst0ne  Yes. yarn add<EMAIL_ADDRESS>But keep in mind it's just an alpha version.


Executing tests in parallel would be impaired by synchronized block in Spectrum

In a situation where something like JUnit's ParallelComputer were used, or where other test runners were parallelising the construction of test classes run with the Spectrum runner, the fact that the test class construction happens inside a synchronized block will constrain the execution time.
This is relatively easy to fix. It's in a synchronized block to protect a stack from being bombarded by different threads. By introducing a thread-independent singleton into the mix, this will become thread-safe. This is what I propose to do.

@greghaskins - this was resolved by #77

I'm going to close this, since it's a detail, rather than an issue.


Project status

Is this still actively being developed? I'm planning on making a few improvements and would rather not fork but contribute to this repo.

Thank You for being interested in this app. However, I am not working on this app any more.  I am currently kind of busy, so I can't promise response on any pull requests. Therefore, maybe it's better to fork it then continue to improve on your own.
Best of luck


Query current raspimjpeg activities and settings in effect

Hi,
Is there some command that queries the running raspimjpeg to see what it is currently doing? Like performing a capture (or not), or engaging in a timelapse collection (or not), or what the exposure settings currently are, or etc...? Maybe by specifying a command or variable name and returning its current operational value, or maybe just performing a dump of it all to STDOUT or some file?  In many cases these can be indirectly deduced from raspimjpeg.conf and uconfig, but not always reliably,  particularly not those collection activities currently in (or not in) progress -- or so it seems.  Shuffling through the documentation, I can't find any specific command to do this.  Looking at the behavior of the web pages, however, it appears they do have access to such info, but is not clear to me how it is obtained or if there is a consistent general approach to take.  But before I get too deep into the PHP files, thought I should ask, as it would be useful for external scripting/monitoring and/or the debugging thereof.
Thanks,
-- Fred P.

The state of the program is maintained in the status file status_mjpeg.txt. This physically resides in /dev/shm/mjpeg but a link to it is made in the web folder. It can be read by local applications or via the web using the status_mjpeg.php. This is what the client does.
The file just has 1 text line with a keywords indicating what the application is currently doing
Error
halted
image
tl_video
video
tl_md_video
md_video
timelapse
ready
tl_md_ready
md_ready

Thanks.  I thought something had to be somewhere.  I just missed finding it.  I will note that during a timelapse sequence it oscillates between "timelapse" while it's waiting and "image" when it's capturing the image, but for my purposes I can work with that.
-- Fred P.


flutter upgrade issue

ubuntu 22.10
running the command flutter upgrade yields the following output:
michael@meerkat-2$ flutter upgrade
clang++: symbol lookup error: clang++: undefined symbol: , version LLVM_10
Downloading Linux x64 Dart SDK from Flutter engine 857bd6b74c5eb56151bfafe91e7fa6a82b6fee25...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  204M  100  204M    0     0  9856k      0  0:00:21  0:00:21 --:--:-- 10.1M
unzip: error while loading shared libraries: /snap/core20/current/lib/x86_64-linux-gnu/libbz2.so.1.0: unsupported version 0 of Verneed record

It appears that the downloaded file is corrupt; please try again.
If this problem persists, please report the problem at:
  https://github.com/flutter/flutter/issues/new?template=1_activation.md

I have tried a few times with the same result.
flutter doctor yields:
michael@meerkat-2$ flutter doctor -v
clang++: symbol lookup error: clang++: undefined symbol: , version LLVM_10
clang++: symbol lookup error: clang++: undefined symbol: , version LLVM_10
Downloading Linux x64 Dart SDK from Flutter engine 857bd6b74c5eb56151bfafe91e7fa6a82b6fee25...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  204M  100  204M    0     0  10.3M      0  0:00:19  0:00:19 --:--:-- 10.3M
unzip: error while loading shared libraries: /snap/core20/current/lib/x86_64-linux-gnu/libbz2.so.1.0: unsupported version 0 of Verneed record

It appears that the downloaded file is corrupt; please try again.
If this problem persists, please report the problem at:
  https://github.com/flutter/flutter/issues/new?template=1_activation.md

Note the clang++ message.  I am not sure whether this is connected to the upgrade problem.

Hi @MontrealMike
What is your previous Flutter version? Can you share the output of uname -r?
Also, it seems you have installed Flutter with snapd, right? If so, please check this issue on snap forum: https://forum.snapcraft.io/t/unsupported-version-0-of-verneed-record-linux-6-0/32160 (Should be fixed with linux 6.0.7). You can also check a workaround at here.

Thank you.
Here is my uname -r:
@.***$ uname -r
6.0.2-76060002-generic
I will look into the workaround you referenced.
Regards,
Mike

Michael Bleau | @.*** |<PHONE_NUMBER>
On Tue, Nov 8, 2022 at 12:48 AM huycozy @.***> wrote:

Hi @MontrealMike https://github.com/MontrealMike
What is your previous Flutter version? Can you share the output of uname
-r?
Also, it seems you have installed Flutter with snapd, right? If so,
please check this issue on snap forum:
https://forum.snapcraft.io/t/unsupported-version-0-of-verneed-record-linux-6-0/32160
(Should be fixed with linux 6.0.7). You can also check a workaround at
here
https://forum.snapcraft.io/t/unsupported-version-0-of-verneed-record-linux-6-0/32160/16
.
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/114840#issuecomment-1306669665,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBZPGNPH2TU7L5E73HV6RTWHHSR7ANCNFSM6AAAAAARZRHZRY
.
You are receiving this because you were mentioned.Message ID:
@.***>


If launched with the desktop launcher, Sparrow won't exit properly when quitting

Hitting the quit button in the main menu in the UI, the Sparrow process doesn't exit, and the wallets remain open. I can for example see various processes open in htop belonging to Sparrow even afterwards. If you then reopen Sparrow it'll fail with an error message saying this wallet is already open in another process. The desired behavior would be for quitting to completely close all wallets and cause all the processes to stop.
Interestingly, this behavior doesn't happen if you start it by calling /opt/sparrow/bin/Sparrow directly, only with the menu launcher.
I had a look at the launcher and it seems that is calls /opt/sparrow/bin/Sparrow %U - I don't know what the U% does but I removed it and that made it work as expected.
Sparrow Version: 1.6.1, present since at least 1.5.x
OS: Linux Mint 20.3

Loosely related, but on Windows my Sparrows always end up not bein able to get connections,
2022-03-04 10:03:20,475 ERROR [ElectrumServerReadThread] c.s.s.n.TcpTransport [null:-1] Error opening socket inputstream java.net.SocketException: Socket is closed 	at java.base/sun.security.ssl.SSLSocketImpl.getInputStream(Unknown Source) 	at com.sparrowwallet.sparrow@1.6.0/com.sparrowwallet.sparrow.net.TcpTransport.readInputLoop(Unknown Source) 	at com.sparrowwallet.sparrow@1.6.0/com.sparrowwallet.sparrow.net.ElectrumServer$ReadRunnable.run(Unknown Source) 	at java.base/java.lang.Thread.run(Unknown Source)
and whenever that happen the process would not close.

YES! I have this same problem. After I exit Sparrow I need to go into the task manager and cancel a Sparrow process before I can open my wallet again. This only started happening after the last couple of updates.
Every time I get the error:
"Error Opening Wallet
The wallet is locked. Is another instance of Sparrow already running?"

YES! I have this same problem. After I exit Sparrow I need to go into the Windows task manager and cancel a Sparrow process before I can open my wallet again. This only started happening after the last couple of updates. Every time I get the error: "Error Opening Wallet The wallet is locked. Is another instance of Sparrow already running?"

I also have this exact issue on Windows 10. I am fairly sure that the bug only exists in the 1.6.0 and 1.6.1 releases.

I can't reproduce this on OSX 11.6.2, Ubuntu 20.04, or Windows 10 Home with the v1.6.1 install.
Given this I will need assistance to investigate further. @YellowWords, once you have quit Sparrow and can see the Sparrow processes with htop as you have described, please issue:
kill -3 <PID>

where <PID> is the process id that you can see in htop. This will print out a long thread dump of all active threads to ~/.sparrow/sparrow.log. Please copy this output into this issue.

@craigraw I actually can't reproduce the issue now for some reason - I reverted my workaround on the desktop file I mentioned, but now Sparrow is exiting correctly. I can't rule out it was just something local to my machine so I'll close this issue for now.

I do not understand how to do the workaround and still have this issue. It never happened before the last two updates.
What is the solution for a more non-technical person?
Thanks very much for your attention to this.

@althea16 please open a separate issue.

I think the issue happen once it's been running for about one day.


cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<std::pair<bool, unsigned int> (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:360:10: error: expected expression
  cargo:warning=  return [=](State & state) {
  cargo:warning=         ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:367:21: warning: 'Peek' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=Condition peek_with(Peek pred) { return fst<bool, uint32_t> * peeks(pred); }
  cargo:warning=                    ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (unsigned int)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:367:1: warning: 'Condition' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=Condition peek_with(Peek pred) { return fst<bool, uint32_t> * peeks(pred); }
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:86:37: warning: 'function<bool (State &)>' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=template<class A, class B, class C> function<C(A)> operator*(C (&f)(B), function<B(A)> g) {
  cargo:warning=                                    ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:86:73: warning: 'function<std::pair<bool, unsigned int> (State &)>' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=template<class A, class B, class C> function<C(A)> operator*(C (&f)(B), function<B(A)> g) {
  cargo:warning=                                                                        ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<std::pair<bool, unsigned int> (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:369:1: warning: 'Condition' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=Condition varid = cond::peek_with(cond::varid_start_char);
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:374:1: warning: 'Condition' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=Condition peek(uint32_t c) { return fst<bool, uint32_t> * peeks(eq(c)); }
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:380:20: warning: 'Peek' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=PeekResult skip_if(Peek pred) {
  cargo:warning=                   ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (unsigned int)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:380:1: warning: 'PeekResult' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=PeekResult skip_if(Peek pred) {
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<std::pair<bool, unsigned int> (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:381:10: error: expected expression
  cargo:warning=  return [=](State & state) {
  cargo:warning=         ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:391:17: warning: 'Peek' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=Condition skips(Peek pred) { return fst<bool, uint32_t> * skip_if(pred); }
  cargo:warning=                ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (unsigned int)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:391:1: warning: 'Condition' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=Condition skips(Peek pred) { return fst<bool, uint32_t> * skip_if(pred); }
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:397:1: warning: 'Condition' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=Condition skip(uint32_t c) { return skips(eq(c)); }
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:402:23: warning: 'Peek' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=PeekResult consume_if(Peek pred) {
  cargo:warning=                      ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (unsigned int)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:402:1: warning: 'PeekResult' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=PeekResult consume_if(Peek pred) {
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<std::pair<bool, unsigned int> (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:403:10: error: expected expression
  cargo:warning=  return [=](State & state) {
  cargo:warning=         ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:413:20: warning: 'Peek' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=Condition consumes(Peek pred) { return fst<bool, uint32_t> * consume_if(pred); }
  cargo:warning=                   ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (unsigned int)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:413:1: warning: 'Condition' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=Condition consumes(Peek pred) { return fst<bool, uint32_t> * consume_if(pred); }
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:418:1: warning: 'Condition' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=Condition consume(uint32_t c) { return consumes(eq(c)); }
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:424:1: warning: 'Condition' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=Condition seq(const string & s) {
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:425:10: error: expected expression
  cargo:warning=  return [=](State & state) { return all_of(s.begin(), s.end(), [&](auto a) { return consume(a)(state); }); };
  cargo:warning=         ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:428:36: warning: 'Peek' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=function<void(State &)> read_while(Peek pred) {
  cargo:warning=                                   ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (unsigned int)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:428:1: warning: 'function<void (State &)>' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=function<void(State &)> read_while(Peek pred) {
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<void (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:429:10: error: expected expression
  cargo:warning=  return [=](State & state) {
  cargo:warning=         ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:439:39: warning: 'Peek' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=function<void(State &)> consume_while(Peek pred) { return read_while(pred); }
  cargo:warning=                                      ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<bool (unsigned int)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  exit status: 0
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:439:1: warning: 'function<void (State &)>' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=function<void(State &)> consume_while(Peek pred) { return read_while(pred); }
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<void (State &)>' has been explicitly marked deprecated here
  running: "ar" "s" "/var/folders/8t/fn6f5ynj3dj7yx3mjjxk9chr0000gn/T/cargo-install6o3zj8/release/build/difftastic-3cb36cd3d7b8fdd7/out/libtree-sitter-go.a"
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=vendor/tree-sitter-haskell-src/scanner.cc:442:1: warning: 'function<void (State &)>' is deprecated: Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type [-Wdeprecated-declarations]
  cargo:warning=function<void(State &)> consume_until(string target) {
  cargo:warning=^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1444:27: note: 'function<void (State &)>' has been explicitly marked deprecated here
  cargo:warning=template<class _Fp> class _LIBCPP_DEPRECATED_CXX03_FUNCTION _LIBCPP_TEMPLATE_VIS function; // undefined
  cargo:warning=                          ^
  cargo:warning=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/c++/v1/functional:1439:24: note: expanded from macro '_LIBCPP_DEPRECATED_CXX03_FUNCTION'
  cargo:warning=        __attribute__((deprecated("Using std::function in C++03 is not supported anymore. Please upgrade to C++11 or later, or use a different type")))
  cargo:warning=                       ^
  cargo:warning=fatal error: too many errors emitted, stopping now [-ferror-limit=]
  cargo:warning=49 warnings and 20 errors generated.
  exit status: 1

  --- stderr

  error occurred: Command "c++" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-arch" "x86_64" "-I" "vendor/tree-sitter-haskell-src" "-Wall" "-Wextra" "-Wno-unused-parameter" "-Wno-ignored-qualifiers" "-o" "/var/folders/8t/fn6f5ynj3dj7yx3mjjxk9chr0000gn/T/cargo-install6o3zj8/release/build/difftastic-3cb36cd3d7b8fdd7/out/vendor/tree-sitter-haskell-src/scanner.o" "-c" "vendor/tree-sitter-haskell-src/scanner.cc" with args "c++" did not execute successfully (status code exit status: 1).

Yep, this was fixed in #38. The Haskell parser requires an additional flag to the C++ compiler on macOS.
I've released 0.10.1, which is 0.10 with #38 cherry-picked.

It works now! Thank you!


”Hărău”, ”Banpotoc”, ”Bârsău”, ”Chimindia” are listed in the drop-down menu

Description:
When user writes ”Hărău”, ”Banpotoc”, ”Bârsău”, ”Chimindia” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Hărău"

Expected results
The location appears in the drop-down menu as "Sat Hărău, HUNEDOARA (Hărău)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Banpotoc"

Expected results
The location appears in the drop-down menu as "Sat Banpotoc, HUNEDOARA (Hărău)".

Step 5
Write in the search bar "Bârsău"

Expected results
The location appears in the drop-down menu as "Sat Bârsău, HUNEDOARA (Hărău)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Chimindia"

Expected results
The location appears in the drop-down menu as "Sat Chimindia, HUNEDOARA (Hărău)".


Parse String API to JSON

hi i have somthing Web Stream API but this is not Pure JSON Data
the Data Like this
id: 0
data: {"code":"start","data":1}
id: 0
data: {"code":"server","data":["<IP_ADDRESS>","9333"]}
id: 0
data: {"code":"Create","data":1}
Attempting to connect to '<IP_ADDRESS>' on port '9333'...id: 0
data: {"code":"Connect","data":1}
id:<PHONE_NUMBER>
data: {"code":"sending","data":"R|LT|1|1\r\n"}
id:<PHONE_NUMBER>
data: {"code":"counter","data":0}
how i parse this data to Json ?

Hey @armadeas
Sorry for the delayed response
As this is not pure json, unfortunately, you will not be able to do it
However, we might be able to sort something out if you can give me a little more information

is this a log file?
can you give me a sample (is it exactly the same as above?)
what is used to separate the lines? a newline character?
which bit would you want to stream to the database?

Closing due to inactivity - please reopen if you still have questions


fix: cherry-pick #13078 and #13046

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
close #13093
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

@kwannoel
I encountered a fuzzing test error, which I believe was not caused by this PR. Has it been fixed in main branch?
2022-08-24T01:04:16.275573Z ERROR node{id=7 name="frontend-1"}:task{id=606}:process_query_msg_one_stmt{session_id=0 stmt=CREATE MATERIALIZED VIEW m10 AS SELECT TIMESTAMP '2022-04-19 10:04:39' AS col_0, (approx_count_distinct(hop_0.c13) FILTER(WHERE false) + hop_0.c3) AS col_1, hop_0.c4 AS col_2, internal_last_seen_value(DISTINCT (hop_0.c13 + hop_0.c10)) FILTER(WHERE CAST((INT '321') AS BOOLEAN)) AS col_3 FROM hop(alltypes2, alltypes2.c11, INTERVAL '61', INTERVAL '61') AS hop_0 WHERE hop_0.c1 GROUP BY hop_0.c11, hop_0.c4, hop_0.c6, hop_0.c1, hop_0.c14, hop_0.c3}: risingwave_frontend::session: failed to handle sql:
CREATE MATERIALIZED VIEW m10 AS SELECT TIMESTAMP '2022-04-19 10:04:39' AS col_0, (approx_count_distinct(hop_0.c13) FILTER(WHERE false) + hop_0.c3) AS col_1, hop_0.c4 AS col_2, internal_last_seen_value(DISTINCT (hop_0.c13 + hop_0.c10)) FILTER(WHERE CAST((INT '321') AS BOOLEAN)) AS col_3 FROM hop(alltypes2, alltypes2.c11, INTERVAL '61', INTERVAL '61') AS hop_0 WHERE hop_0.c1 GROUP BY hop_0.c11, hop_0.c4, hop_0.c6, hop_0.c1, hop_0.c14, hop_0.c3:
Bind error: failed to bind expression: internal_last_seen_value(DISTINCT (hop_0.c13 + hop_0.c10)) FILTER(WHERE CAST((INT '321') AS BOOLEAN))

Caused by:
  Invalid input syntax: DISTINCT, ORDER BY or FILTER is only allowed in aggregation functions, but `internal_last_seen_value` is not an aggregation function
2022-08-24T01:04:16.275573Z  INFO node{id=7 name="frontend-1"}:task{id=606}: pgwire_query_log: mode=(simple query) session=0 status=err time=0ms sql=CREATE MATERIALIZED VIEW m10 AS SELECT TIMESTAMP '2022-04-19 10:04:39' AS col_0, (approx_count_distinct(hop_0.c13) FILTER(WHERE false) + hop_0.c3) AS col_1, hop_0.c4 AS col_2, internal_last_seen_value(DISTINCT (hop_0.c13 + hop_0.c10)) FILTER(WHERE CAST((INT '321') AS BOOLEAN)) AS col_3 FROM hop(alltypes2, alltypes2.c11, INTERVAL '61', INTERVAL '61') AS hop_0 WHERE hop_0.c1 GROUP BY hop_0.c11, hop_0.c4, hop_0.c6, hop_0.c1, hop_0.c14, hop_0.c3
2022-08-24T01:04:16.275573Z ERROR node{id=7 name="frontend-1"}:task{id=606}: pgwire::pg_protocol: error when process message error=QueryError: Bind error: failed to bind expression: internal_last_seen_value(DISTINCT (hop_0.c13 + hop_0.c10)) FILTER(WHERE CAST((INT '321') AS BOOLEAN))

Caused by:
  Invalid input syntax: DISTINCT, ORDER BY or FILTER is only allowed in aggregation functions, but `internal_last_seen_value` is not an aggregation function
2022-08-24T01:04:16.280404Z  INFO node{id=14 name="client"}:task{id=605}: risingwave_sqlsmith::runner: [UNEXPECTED ERROR]: Error {
    kind: Db,
    cause: Some(
        DbError {
            severity: "ERROR",
            parsed_severity: None,
            code: SqlState(
                EXX000,
            ),
            message: "QueryError: Bind error: failed to bind expression: internal_last_seen_value(DISTINCT (hop_0.c13 + hop_0.c10)) FILTER(WHERE CAST((INT '321') AS BOOLEAN))\n\nCaused by:\n  Invalid input syntax: DISTINCT, ORDER BY or FILTER is only allowed in aggregation functions, but `internal_last_seen_value` is not an aggregation function",
            detail: None,
            hint: None,
            position: None,
            where_: None,
            schema: None,
            table: None,
            column: None,
            datatype: None,
            constraint: None,
            file: None,
            line: None,
            routine: None,
        },
    ),
}

Didnt see this before. Looks like a regression perhaps. Taking a look.

internal_last_seen_value should not be used. I guess it still works in latest main. Let me ban it.

internal_last_seen_value should not be used. I guess it still works in latest main. Let me ban it.

Building new snapshot https://buildkite.com/risingwavelabs/generate-sqlsmith-snapshots-weekly/builds/129


feat(containers): add UI to view and edit Docker HEALTHCHECK configuration values on containers

This issue is probably better tied to https://github.com/portainer/portainer/issues/3321, which is closed, but mentions that the solution belongs with https://github.com/portainer/portainer/issues/3572 instead, thus the branch named after that issue.
When launching a Docker container with a HEALTHCHECK in the container or added at the command-line, the values are not visible in Portainer. Previous enhancements to the container views show the health status while the container is starting or running.
For example, this line in a container's Dockerfile will trigger a curl of the root of a website, issuing an error if content isn't returned (it's a short example, which could barf out a lot of content, so better examples are in order). It will pause for 30 seconds to allow the container to finish starting, wait for 1 second at each request, and repeat every 5 minutes, waiting for 5 failures to report the container unhealthy.
HEALTHCHECK --start-period=30s --interval=5m --timeout=1s --retries=5 CMD curl -sf http://localhost/ || exit 1

This PR provides a simple view of the health-check values in the container details, next to the health check status data previously displayed. When creating or editing (duplicating) a container, the "Advanced container settings" area has a Healtcheck tab, which allows disabling or editing these fields, with some validation for the intervals, to allow the "5m" shorthand entry.
Changes to the Docker views are complete to the documentation found at https://docs.docker.com/engine/reference/builder/#healthcheck and information found in the config.v2.json file in the container on the running system. Additionally, disabling the health check will allow maintaining the other settings between edits.
The npm module https://www.npmjs.com/package/simple-duration has been added to simplify the date formatting and conversion between Docker's nanoseconds and a human-readable value. This code does limit the resolution to ms, but if that's found to be important, it's a small change to allow passing µs or ns as well, as are allowed by the simple duration module.

/azp run

/pull-dog up

Note that the remaining "conflicts" are where there are added lines, and not actually conflicts. The worst of which is this import in the createContainerController.js which seems to be replacing a blank line. All of the other conflictss are new code replacing empty blocks.
<<<<<<< feat3572-healthcheck
import * as simpleDuration from 'simple-duration';
=======

>>>>>>> develop

Another refresh from origin/develop, and all conflicts have been resolved. I cannot clear the "has conflicts" label, but there are none in this PR.
Please review and merge to enable Docker HEALTHCHECK directive editing in Portainer.

Another refresh from origin/develop, and all conflicts have been resolved. I cannot clear the "has conflicts" label, but there are none in this PR.
Please review and merge to enable Docker HEALTHCHECK directive editing in Portainer.


move events to sidebar

upcoming event should be displayed big and past events just as a list of location

Solved in https://github.com/protocultural/protocultural.org/tree/v1-with-sidebar but still need some styling and love


Update Contact.js

An error in the code has been corrected and an comment has been added after correcting it

Hoping that you agree with the change


Moving payed account functionality from gorgias.io

Integrated "Manage Account" Menu
With all the features availables on gorgias.io. The menu can be accessed from the dropdown on the right of the profile block (in "Account"). This includes :

My Account
Team Members
Member Groups
Subscriptions

Started to move "Tags" to the left sidebar
I created a specific controller for the sidebar, "list.js", which has access to the tags. Though, they are not usable yet, so they're just hidden for now. Also, the menu item to access the list of templates is now "All" (and should soon be followed by "Shared with me" and "Private").

Before merging this branch, as a rule, please 'squash' your intermediary commits.
Everybody has their commit style (which is fine). For me commits like these (where big functionalities are added) should be grouped into 2-3 commits with clear descriptions - ideally independent of each other.
The reason here is first that I don't care at all about forgotten console.log's, or fixing merge errors, but I do care about big changes and I should be able to read them. The second is that I should be able to revert a few commits without pulling my hair off.

Review status: 0 of 31 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

Comments from the review on Reviewable.io

Reviewed 24 of 31 files at r1, 8 of 10 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from the review on Reviewable.io

Seems good, however I noticed that some styles have changed in between branches (inputs are bigger). Make sure design-v2 is rebased on top of master.
Also, how does a non-authenticated user access settings? There doesn't seem to be a link anymore.

Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from the review on Reviewable.io

design-v2 has been rebased on top of master but I'll do it again to make sure.
I didn't think about that; how do you want it to behave ? A "Settings" list item below "All", or I leave the dropdown with just the "Settings" item ?

Comments from the review on Reviewable.io

@martinlatrille: sent you some comments on slack. There are still differences between design-v2 and master

Reviewed 2 of 3 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from the review on Reviewable.io

Reviewed 1 of 9 files at r5, 12 of 14 files at r6.
Review status: 34 of 43 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

src/background/js/app.js, line 150 [r6] (raw file):
connectSocial is defined twice for some reason.

src/background/js/app.js, line 175 [r6] (raw file):
If no longer used, remove the comment please.

src/pages/bg.html, line 5 [r6] (raw file):
Why change the title here?

Comments from the review on Reviewable.io

src/pages/bg.html, line 5 [r6] (raw file):
Couldn't find why it was "Gorgias Options", so I thought "Gorgias" alone would be better. Why "Options" ?

Comments from the review on Reviewable.io

Reviewed 7 of 9 files at r5, 2 of 14 files at r6, 1 of 1 files at r7.
Review status: all files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

src/pages/bg.html, line 5 [r6] (raw file):
Because it opens up when you click on the Options button in Chrome Extensions. Keep it as it was please.

Comments from the review on Reviewable.io

I fixed the last minor issues; go for merging ?


php82: php82-beta1 -> php82-beta2

That test was not failing in 8.2-beta1
=====================================================================
FAILED TEST SUMMARY
---------------------------------------------------------------------
pcntl_setpriority() - Check for errors [tests/pcntl_setpriority_error_linux.phpt]
=====================================================================

Find the complete build log here: https://gist.github.com/drupol/a3fd7c7febee964ad595540b32530332
Do you think I should an issue in php/php-src ?

First, we need to get the actual test protocol. Build it with nix build .#php82.extensions.pcntl --keep-failed and then look at php-8.2.0beta2/ext/pcntl/php_test_results* in the reported build directory.

Another thing you can check is the tests/pcntl_setpriority_error_linux.phpt file in the PHP source code for any recent changes.

Another thing you can check is the tests/pcntl_setpriority_error_linux.phpt file in the PHP source code for any recent changes. And the changelog of course.

That file has been introduced in this commit (https://github.com/php/php-src/commit/520bb2ec6ca01698f863cb16a5e9a28764df01ae#diff-d517133d2e2c271fcdba556de2330cd984828e7cb14fd42e93a43106aab2b3c2). This test is failing is failing on CI.


stdout Environment / Backend

Related to #108
This will be really useful for dev and debugging

I propose a better name than "stdout" (maybe "console"?) but otherwise strongly agree with this idea.


Merge usercase

Do we have a strategy/user case for handling merges in Wikidata ? I guess the "statement_guid" will "change"
Both Wikidata and example WikiTree (Property:P2949) are wikis --> objects are not persistant...

Example merges done last week in Wikidata for objects connected to WikiTree

I'll open a ticket for this in phabricator for later consideration.


[AIRFLOW-2778] add explicit import for dag_processing.list_py_filepaths in collect_dags

Make sure you have checked all steps below.
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a JIRA issue.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

I run the following test to make sure there are no import errors in our CI. After upgrading to 1.10-stable from 1.9.0, the following test starting failing:
class TestAirflowDag:

    def test_dagbag_import(self):
        """Verify that Airflow will be able to import all DAGS in the repo
        """

        dagbag = self._get_dagbag()
        assert len(dagbag.import_errors) == 0

    def _get_dagbag(self):
        dag_folder = os.getenv('AIRFLOW_DAGS', False)
        assert dag_folder is not None

        return DagBag(dag_folder=dag_folder, include_examples=False)

The following error is raised:
# Used to store stats around DagBag processing
stats = []
FileLoadStat = namedtuple(
    'FileLoadStat',
    "file duration dag_num task_num dags"
)
for filepath in utils.dag_processing.list_py_file_paths(dag_folder):

E AttributeError: module 'airflow.utils' has no attribute 'dag_processing'

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
I am not sure how to introduce test for this specific issue, as it looks like the area is tested but works because dag_processing is imported at some point. Please advise on this.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

No tests are fine on this -- there's not really an easy way to test this.

Test failure is a random timeout in the Kubernetes env on py3, everything else passed so merging anyway.


Code for fibonacci series.

I have used C++ to write code.

Well done!
Thank You for your contributions
@Zaid-Parkar


Text/plain or custom Content-Type bypasses body evaluation.

Description
POST requests with an explicit Content-Type header equal to text/plain or even just an empty space lead to not analyzing the body and directly sending it to the server.
I'm running a Coraza instance with a simple rule that checks the request body against a string (maliciouspayload):
...
SecRequestBodyAccess On
SecRule REQUEST_BODY "@rx maliciouspayload" "id:102,phase:2,t:lowercase,deny"
...

Curl requests like the followings, with explicit Content-Type different than application/x-www-form-urlencoded are leading to not checking the body:

curl -i -X POST -H 'Content-Type: text/plain' 'http://localhost:8090' --data "maliciouspayload"
curl -i -X POST -H 'Content-Type: ' 'http://localhost:8090' --data "maliciouspayload"

Logs:
[Evaluating phase 2
[[102] Evaluating rule 102
[[102] Expanding 1 arguments for rule 102
[[102] Transforming argument "" for rule 102
[[102] Arguments transformed for rule 102: []
[[102] Evaluating operator "@rx maliciouspayload" against "": NO MATCH
[[102] Finish evaluating rule 102
[Finished phase 2

"@rx maliciouspayload" against "": NO MATCH particularly caught my eye, meaning that the evaluation is performed, but against an empty string.
While, with application/x-www-form-urlencoded, the body is evaluated and the request is denied:

curl -i -X POST -H 'Content-Type: application/x-www-form-urlencoded' 'http://localhost:8090' --data "maliciouspayload"

Logs:
Attempting to process request body using "URLENCODED"
Evaluating phase 2
[102] Evaluating rule 102
[102] Expanding 1 arguments for rule 102
[102] Transforming argument "maliciouspayload" for rule 102
[102] Arguments transformed for rule 102: [maliciouspayload]
[102] Matching rule 102 REQUEST_BODY:
[102] Evaluating action log for rule 102
[102] Evaluating action auditlog for rule 102
[102] Evaluating action t for rule 102
[102] Evaluating operator "@rx maliciouspayload" against "maliciouspayload": MATCH
[102] Disrupting transaction by rule 102
[102] Evaluating action deny for rule 102
rule 102 matched

Steps to reproduce
Curl commands above against this branch (http-server example).
Is this an intended behaviour evaluating only super specific Content-Types? If so, shouldn't this behaviour be handled by the CRS rule 900220 that checks allowed Content-Types?
Thanks!

Hey! Evaluation of content-types for urlencoded is only enforced if content-type is x-www-form-urlencoded or the CTL variable ForceRequestBodyVariable is set. Rule 900220 should stop an unknown content-type. I will look into it

Hi @jptosso!
Just to specify:

setting application/x-www-form-urlencoded  seems to actually be the only way to parse the body request.
Speaking about 900220, I was just thinking loud about CRS duties and Coraza ones, in the example, the CRS is NOT loaded.

I debugged a bit and seems that if no processing is done on the body, the latter is not added to the transaction. With https://github.com/corazawaf/coraza/pull/439 it is now working.  Could it make sense to have a generic bodyprocessor that just performs this option of populating the transaction and will performed with no other bodyprocessors are triggered Inside the (if rbp == "" {)?
Thanks for the help and feedbacks

There is a design reason for that. There are many cases where we just want to avoid processing the body, mostly because of resources and DDOS. Specific pages, specific mimes, specific lengths.
We cannot accept all bodies by default, it must be custom tailored by the user according to his needs.

I see, and I understand the reasoning behind the necessity of defining boundaries between analyzing it or not.
I'm just not so sure about the overall default behaviour.
By default:

A request with a payload as simple as text/plain is not evaluated, but always allowed.
A request with a payload with content typeapplication/x-www-form-urlencoded is processed and (always?) evaluated.
A request with any malformed content type is not evaluated, but always allowed.

Why should a user expect that a legit content type like text/plain is not being evaluated but application/x-www-form-urlencoded is? Currently bypassing a request-body rule is a matter of changing the content type to any value different than application/x-www-form-urlencoded. My mind is now getting trapped in a rabbit hole thinking that the only way to have this rule effective is indeed to enable ForceRequestBodyVariable. 😵💫

You can also force the body processor by ctl: requestBodyProcessor=JSON, for example.
If you would like to expand this discussion, we could check it on tomorrow's meeting #388

Just for context. What is modsec default behaviour?
On Tue, 27 Sept 2022, 19:38 Juan Pablo Tosso, @.***>
wrote:

You can also force the body processor by ctl: requestBodyProcessor=JSON,
for example.
If you would like to expand this discussion, we could check it on
tomorrow's meeting #388 https://github.com/corazawaf/coraza/issues/388
—
Reply to this email directly, view it on GitHub
https://github.com/corazawaf/coraza/issues/438#issuecomment-1259838124,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYARJEUVAQMVH2ACCIN3WAMWHXANCNFSM6AAAAAAQW36QN4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Writing down a recap about when the request body is evaluated:

First of all RequestBodyAccess requires to be On.
By default, with just 1. the REQUEST_BODY variable is populated only if the content-type is application/x-www-form-urlencoded. Against any other content-type the variable will be empty and rules will never match.
We can force to populate the REQUEST_BODY:

via ForceRequestBodyVariable
Enforcing a specific body processor. E.g. ctl:requestBodyProcessor=JSON

Speaking about running the CRS:

3. is basically enforced during the initialization by rule 901340.
Content-type manipulation is mitigated by 900220 where it is possible to explicit the list of allowed content types.

To the best of my knowledge, ModSecurity:

v2:  Behaves just like described above (Manual ref). (Not personally tested)
v3: Always populates the REQUEST_BODY therefore by default any content-type leads to analyze the body (ref). (tested)

If we are on the same page about the described behaviour I would close this issue and propose to just merge @jcchavezs's PR https://github.com/corazawaf/coraza/pull/441.

Is this still an issue @M4tteoP?

I think that we somewhat agreed that the behaviour described in the previous comment) is the intended one. So, unless new considerations are made, we can keep this issue closed


Support eval with custom dataset

Eval extract class names from dataset. It allows to evaluate models on datasets with classes different from coco.

 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.

Thanks for contribution. You format check also failed, plz lint your code also @ArMaxik

LGTM.


Cursing Gaze,Shaman can‘t chant as a move action

Under turn-based mode.
Before the Shaman get the mythic ability "Cursing Gaze",she can use the ability "Chant" as a move action.
After the Shaman get the mythic ability "Cursing Gaze", she can't use the ability "Chant" as a move action.She has to chant as a swift action or a standard action.
I dont't know how to post a screenshot,sorry.

Maybe Witch's hex "cackle" were influce by "Cursing Gaze" too.

This is fixed by Patch: Fix Quicken Metamagic. Did you disable this patch?

Now，I can use 1、Evil Eye or any swift action 2、cackle (not passive) 3、Evil Eye one by one in sequence，with "Cursing Gaze".
I can use 1、one swift action 2、Evil Eye 3、cackle (not passive)   in sequence，without "Cursing Gaze".
But I can't use 1、Evil Eye or any swift action 2、Evil Eye 3、cackle (not passive)  one by one in sequence，with "Cursing Gaze".

That's a pretty bad explaination. A better description would be "cackle
starts as a swift action and becomes a move action, after any swift
action is used, then comes a standard action, if any standard action is
used".
I can see that I chose a bad requirement for my patch and will fix it.


How to control bit rate of generated wav

refer to https://github.com/librosa/librosa/issues/361#issuecomment-219874390


Labels Query

Aim - I wish to be able to query for host metrics based upon a server's role easily.
Challenge - I’m doing this within a container orchestration platform that supports DNS service discovery. I’m using this platform to schedule the running of our node-exporter globally. Prometheus then retrieves the list of node-exporters through DNS service discovery. This works well and our results are filterable on ‘instance’ (IP/Port).
What i’ve tried
I’ve tried Adding a textile collector to node-exporter, can now see ‘role’ metric returned, i figured once my data is all in the same place, it should be easy... But I couldn’t see a way of manipulating this returned data into something i could use in other metrics. I attempted relabel configs to try map the values but i don’t think it's possible to re-map a metric result to a label like that?
I think the usual way here is to split up the jobs so that each group has a label, that’s not something i can easily do here, there isn't a config management platform behind this deployment. I guess fundamentally i shouldn't need one as all the data is there, I can obtain the servers role within a container, how can i easily either replace an existing label with this data, or add a new label from it?
Think i’ve just gotten confused with labels in general, apologies if this is covered, i have searched around a lot.
Any help appreciated,
Thanks
Ed

It sounds like you're looking for http://www.robustperception.io/how-to-have-labels-for-machine-roles/

I do indeed, thanks for the heads up @brian-brazil


Show the feature type on the gene pages

Currently it always says gene or pseudogene.  We should say "tRNA gene" or "snoRNA gene" etc.

Fixed by 70bcf7d093a4


test(python): add azure integration tests

Description
Adding Azure integration tests to the Python bindings.
Will need to rebase after we merge #893.
Related Issue(s)

fixes #955

Documentation

I need to fix the CI job for Python.


v1.1.5 crashes 1.19.2 client and 1.19.2 server

Server log
latest.log
Client log
latest.log

Server log latest.log
Client log latest.log

Please, download the latest version.

It was the latest on Modrinth when I downloaded it, and it was like 2 or 5 hours old according to Modrinth.  I went back one version and it seems to be running fine.

It was the latest on Modrinth when I downloaded it, and it was like 2 or 5 hours old according to Modrinth. I went back one version and it seems to be running fine.

If it works fine, do not touch anything, if it continues to give you problems, you should remove it.

It was the latest on Modrinth when I downloaded it, and it was like 2 or 5 hours old according to Modrinth. I went back one version and it seems to be running fine.

The last version is the 1.1.6


Add lambda deployment rfc

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

@khanhtc1202 Thank you. Let's merge this pull request and Go Bold.
/approve

Go Bold!


Design System: Consistent use of spacing within components

Problem to be solved
#3564 addresses the treatment of space between page sections and the space between components. We need to establish/implement rules for space within components where possible.
Design guidelines
Initial spacing rules for e.g. compact cards are at https://zpl.io/aBqOM9L
TODO

[ ] establish rules
[ ] implement: start with updating components on works, exhibitions, stories; then update other components in Cardigan

@GarethOrmerod @davidpmccormick Can this be closed or refined in any way?

I think this should be closed – don't think it needs any further refinement now we're using the spacing component everywhere.


Issue with Travis CI  , gcloud and Fastlane

I got the following error when trying to run the tests on Firebase Test Lab using Fastlane and gcloud
/home/travis/.rvm/gems/ruby-2.4.1/gems/fastlane-2.116.1/fastlane_core/lib/fastlane_core/ui/interface.rb:153:in `shell_error!': [!] Exit status of command 'tee instrumentation_output.txt < testlab-pipe & gcloud firebase test android run --type instrumentation --app ./app/build/outputs/apk/[apk file] --test ./app/build/outputs/apk/androidTest/[test.apk] --device model=walleye,version=27,locale=en_US,orientation=portrait --timeout 30m  > testlab-pipe 2>&1' was 1 instead of 0. (FastlaneCore::Interface::FastlaneShellError)

Hi @moatazeldebsy!
You only get that info in the stack trace?
Btw, can you ssh the travis machine and test if you have the gcloud and tee commands?
Cheers

@bffcorreia Thank you for your help I solved it

I have similar issue on Bitrise (CI/CD). My workflow always throw an error:
[12:28:26]: ----------------------------------------
[12:28:26]: Starting run_tests_firebase_testlab plugin...
[12:28:26]: Set Google Cloud target project.
[12:28:26]: $ gcloud config set project my-project-name
**[12:28:26]: No such file or directory - gcloud**

Even if in the step before I added install glcoud manually fastlane somehow doesn't have access to this command. Locally everything is fine.

Hey @ahanusek!
Which stack are you using to run your workflows? Apparently, the gcloud is installed in the Ubuntu stacks. Check this.
If after manual installation you can't use the gcloud command, it's probably just because you don't have it in you PATH.
Hope it helps :)

Thanks, switching to Ubuntu stack solved my issue.


[QUESTION] How to setup a mailing list

Hi all, thank you for this project. I've installed with success the docker container in my system but i have a question: how can i create a mailing list with existing postfix installation?
Thank you,
Stefano Zaniboni

Hi,
You will need to do some adjustments, you can integrate Sympa or Mailman in the image or as a independent service sharing conf files with DMS.

Question issue template should be used for questions,

Please see https://github.com/tomav/docker-mailserver/issues/370

A very simple mailing list can be implemented with aliases. For a "real" list you need to use mailman or some other external tool. Good luck!

This issue was closed due to one or more of the following reasons:

Age
Contributor inactivity
The issue seems to be resolved

If you think this happened by accident, or feel like this issue was not actually resolved, please feel free to re-open it. If there is an issue you could resolve in the meantime, please open a PR based on the current master branch so we can review it.


:flag_pl: Fixes to polish

Fixed some typos, changed some stuff
We got a number one victory royale
Yeah, Fortnite, we 'bout to get down (Get down)
Ten kills on the board right now
Just wiped out Tomato Town
My friend just got downed
I revived him, now we're heading south-bound
Now we're in the Pleasant Park streets
Look at the map, go to the marked sheet
Take me to your Xbox to play Fortnite today
You can take me to Moisty Mire, but not Loot Lake
I really love to chug jug with you
We can be pro Fortnite gamers

I don't know what this description is, but it gives me the impression you are just trolling.
Please change that and describe in a meaningful way what you have changed and why, else i will have to deny this pull-request..

i just had nothing to say, i fixed some typos and stuff thats all

Thank you @kacperleague9 for correcting my minor oversights in my translation.

Done

oops, fixed


[enhancement]: Install In-Place - Model Manager - Retain last state

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
I would like for the checkbox in the Model Manager, when installing from local path or scan folder, to remember whether you have unchecked or checked it rather than resetting.
Alternatives
An alternative would be to allow some button somewhere, to click for an In-Place model to get converted/copied into an Invoke folder, essentially undoing an In-Place install if you accidentally forgot to uncheck the box.
Additional Content
No response

Implemented in #7167


CreateGroupResponse missing its UnitTest file

Fixes #32

cool. Thanks!

cool. Thanks!

Thanks for spotting that the test was missing 😃

it was not a spotting - it was the confession :(


Fix handling of recursion depth in WKT JSON decoding.

All of the WKTs are actually objects from a parsing depth pov, so they need to
track in the recursion budget. This seems to track the C++ code for accounting.

I need to expand testing, but getting this up for an initial look.

Looking at the C++ json_stream_parser.cc, it is entirely stack based, so while they have a recursion limit, it only kicks in on objects ({ ... }), so it likely would come into play on google.protobuf.Struct but not the types like they do for binary parsing. With our design having to call the generated decode call to drive the next field loop, we can't do the same sorta approach.  So it will come down to where how we want to impose a limit.
ps - we've also go recursion issues within the skip support used for Any, that might actually be able to use a state state, but will be a different PR.

New commit up with tests.

Pulling this back to a draft for revision.
While I'm inclined to agree about JSON object vs. list distinctions not really being valid in a general context; while thinking about this some more, I think we need to not focus on it from the POV of JSON, but think about it in the scope of this library as the context.
Looking at BinaryDecodingOptions, JSONDecodingOptions, and TextFormatDecodingOptions, they all have this exact same thing:
  /// The maximum nesting of message with messages.  The default is 100.
  ///
  /// To prevent corrupt or malicious messages from causing stack overflows,
  /// this controls how deep messages can be nested within other messages
  /// while parsing.
  public var messageDepthLimit: Int = 100

So the already public/released definition of this support tied to message depth.  All of the WKTs do make messages, no matter what their special encoding is for JSON.
I think a user is fair to expect that a messageDepthLimit = x on any DecorderOptions would limit the depth of the proto graph being created in the same way.  i.e. - even though the JSON of a google.protobuf.Timestamp happens to be a string, that the Google_Protobuf_Timestamp still counts as a message from a depth pov, so it is consistent in all three formats.
With binary parsing, the concept of a message is pretty bottlenecked in the decoder, and TextFormat is also pretty good from that POV.  JSON is just going to be a little more messy because the common case is the curly brace for object starts, but thanks to all the custom encoding support, it will need some extra apis so the places that do custom override can properly track their MessageDepth.
Assuming this makes sense, I'll be working on a PR to move back into this direction, and I'll drop the draft status from the PR when it is ready.

That argument works for binary and text formats because they cannot arbitrarily nest arrays (repeated fields) without intervening messages.
As you say, JSON custom coding is an oddball.  Only ListValue and Struct can nest arbitrary other content, so those are the two cases that must participate in the nesting limits.  Other types with custom JSON coding cannot nest arbitrary content, so they do not "need" to participate.
This is ignoring Any for the moment, which is its own special set of curiosities.

This is ignoring Any for the moment, which is its own special set of curiosities.

Yup.  We do preserve the depth used from the scanner so when we do decode things it does get validated in the end.
So I have a partial PR that actually moves the depth tracking all into decodeFullMessage and it is looking pretty clean, but…
I did a little more digging, and since C++ just does the JSON ⇨ Binary transform, it doesn't face the same issues Swift's impl does.  The only enforcement I can find on the JSON side there is JSON parsing: JsonStreamParser::HandleBeginObject, which is inline with what we have.  I just wish we hadn't called the option something message named.  ☹
So I guess the question is how do we want to hand lists of lists since that is what is failing as either WKTs or are unknown JSON.  A new parser design for the unknown JSON (skip) could avoid the stack issue, maybe WKT List could move to a heap based stack to track context to avoid the problem?

I've got a little test app built against the C++ interface that I'm gonna reach out to the protobuf team about.
I tested with List of List, Struct of Struct, and a recursive Message.


custom session_interface + optional SESSION_TYPE: 'custom'

If you want to use custom session you can subclass ServerSideSessionInterface and then assign using to app.session_interface = CustomSessionInterface(....)
Making an option in the standard API seems potentially confusing unless you fully documented it which would then seem excessive given it can be done already.
Closing as not planned


Don't try to set devices fact when osd_auto_discovery was skipped

Right now, under certain OS and Ansible versions, ie Rocky Linux and
ansible-core 2.17, devices_check variable is getting defined even if
task was skipped.
That results in set_fact to fail, as resulting variable has no results
key in it.
Structure of such variable looks like that:
"devices_check": {
    "changed": false,
    "false_condition": "osd_auto_discovery | default(False) | bool",
    "skip_reason": "Conditional result was False",
    "skipped": true
}

Checking for task not being skipped solves such issues.
Signed-Off-By: Dmitriy Rabotyagov<EMAIL_ADDRESS>

Would be very nice if it's possible to backport to stable-8.0 as well

Thanks a ton for prompt review!


[BACKLOG-26073] Update help links for steps in PDI that have moved fr…

…om wiki to MindTouch in 8.2

@pentaho/r2d2


We should be able to specify width for leftstciky column

For the left sticky column, It would be nice if we could set a minwidth for it or this should even be the default behavior of the package
Because on mobile phones with small screens the leftstcikycolumn takes up a lot of space on the screen
And I really really wish the width was implemented like flutters default width.
That would make this package a 100/100 literally..I understand it would cause performance issues though so anyhoo well done

What is leftstcikycolumn exactly?

Fixedleftcolumn

Consider opening the issue sir

Please submit proper description of the feature, what you've described above deosn't make sense to me.

What I asked is straight forward
Can you ask questions where you're confused?
I simply asked if there's a way to specify the minWidth of the fixedleftcolumn so it's different from the reat

Each column can have either fixed or relative (SML) size
Checkbox column can't be resized
There can be multiple fixed left columns


[benchmark] Exclude C++ from OSS benchmarks CI.

QPS worker build is currently failing.

Issue is fixed, PR is no longer required.


pack.install display username:password as plaint txt from WebGUI

Use st2 pack install from git, but seems the username and password will print out as plaint text from WebGUI.
For example:
st2 pack install<EMAIL_ADDRESS>

Tracking here: https://github.com/StackStorm/st2web/issues/368


Update the FAQ for RHEL and Windows

RHEL 6.5 is not supported
Windows info was way out of date

@friism @londoncalling PTAL

@mstanleyjones Uh-oh, merge conflict :(

👍


Cant play youtube videos at all now.

Script version
5.5
Describe the bug
Video tries to start playing but then the video player goes away.
Expected behavior
the video to start
Screenshots

Desktop (please complete the following information):

OS: Windows 11
Browser: Edge
Version 125.0.2535.92 (Official build) (64-bit)

Additional context
Before this I had the issue with videos playing twice.

Youtube is did a good job for being cancer of this planet. Turned from biggest video platform into shithole.  I wish some other companies would step in to counter this monopoly loving google nonsense. World don't belong to you. And people will quickly realise that there is always same good alternatives without this rape with those disguisting ads which I WAS BLOCKING ALL MY LIFE. IT MEANS MORE THAN 15 YEARS IN A ROW.  GET CANCER, GOOGLE


quick refactor to make a future pull request more focused

We can use reduce here to easily get the result of applying the transformations
without overwriting the original email variable.

Coverage decreased (-0.02%) to 98.75% when pulling 363b81edca6ee9ccb3323cac2403092647022a6d on jt-changes into 62100cef5a5bd1948737ee05e242782e41f1be32 on master.

facepalm

Coverage decreased (-0.02%) to 98.75% when pulling e968e39064eaf3d437e184db37dda6fe89f9a991 on jt-changes into 62100cef5a5bd1948737ee05e242782e41f1be32 on master.

bump - any thoughts?


Accelerate embedding

Accelerate embedding using the new kernel https://github.com/dmlc/mxnet/issues/2612
Update mshadow

Backward computation of the embedding layer will be as fast as Torch now (GPU). About 10 times speedup.
For the speed-testing code in https://github.com/dmlc/mxnet/issues/2612
forward+backward time of previous version: 0.01396
forward+backward time of new version: 0.001021


Apache OpenWhisk logo referenced as IBM OpenWhisk

The logo here should say Apache OpenWhisk instead of IBM OpenWhisk (or replace with IBM Cloud Functions logo if that's what is intended). If the Apache OpenWhisk logo is intended, should the proper logo be used?
https://serverless.com/framework/docs/providers/openwhisk/
The readme in this repo should also refer to OpenWhisk as Apache Openwhisk. The proper link is https://openwhisk.apache.org

looks like the place to patch the serverless.com docs is here https://github.com/serverless/serverless/edit/master/docs/providers/openwhisk/README.md

Closing and opened in the proper repo.


fix: Fix schema for canister .build property

The #[serde(default)] nature of CanisterTypeProperties::Custom.build was preserved when Deserialize was manually implemented, but without an attribute, derive(JsonSchema) can't see it. This fixes the schema to make it look optional again.
Fixes #2908, SDK-932

Can you add a changelog entry? And I think the schema in the docs (docs/dfx-json-schema.json) should be updated too


Multi Lang Issue

I use 2 languages in my site. When I enable the localization on my site, it loads both menu items in the Child Links menu for whatever languages I selected. That means it shows 2 links for both languages.
But It works well on my main menu in the skin. It shows only one link according to the selected language.
I appreciate it if you could provide us with a multilingual support installable module.
Thank you for the great module.

We appreciate it if we could have a solution for the Multilanguage support.
Currently, it is loading both language pages in the same menu. not only the selected languages.