Build failed

I tried to build chronos on ec2 instance and it failed with the following error:
Execute:Java13CommandLauncher: Executing 'node' with arguments:
'/home/ec2-user/newchronos/chronos/src/main/resources/assets/r.js'
'-o'
'/home/ec2-user/newchronos/chronos/src/main/resources/assets/app.build.js'

The ' characters around the executable and arguments are
not part of the command.
  [antcall] Exiting /home/ec2-user/newchronos/chronos/build.xml.
      [ant] Exiting /home/ec2-user/newchronos/chronos/build.xml.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.597 s
[INFO] Finished at: 2015-03-24T19:15:41+00:00
[INFO] Final Memory: 11M/27M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (ant-run-requirejs) on project chronos: An Ant BuildException has occured: The following error occurred while executing this line:
[ERROR] /home/ec2-user/newchronos/chronos/build.xml:26: The following error occurred while executing this line:
[ERROR] /home/ec2-user/newchronos/chronos/build.xml:5: Execute failed: java.io.IOException: Cannot run program "node": error=2, No such file or directory
[ERROR] around Ant part ...<ant antfile="/home/ec2-user/newchronos/chronos/build.xml">... @ 9:62 in /home/ec2-user/newchronos/chronos/target/antrun/build-main.xml
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (ant-run-requirejs) on project chronos: An Ant BuildException has occured: The following error occurred while executing this line:
/home/ec2-user/newchronos/chronos/build.xml:26: The following error occurred while executing this line:
/home/ec2-user/newchronos/chronos/build.xml:5: Execute failed: java.io.IOException: Cannot run program "node": error=2, No such file or directory
around Ant part ...<ant antfile="/home/ec2-user/newchronos/chronos/build.xml">... @ 9:62 in /home/ec2-user/newchronos/chronos/target/antrun/build-main.xml

You need to install node.js before installing chronos.

thanks! Any idea on the version of node.js required?

Sure! Installing the latest version with brew worked fine for me.

The Build is successful with node.js installation.
For future reference: ran the following command to install node.js
sudo yum install nodejs npm --enablerepo=epel


Investigate potential models to use with deep-sort

Create a list of potential models that we can use to detect items from this list.

Various sized trucks
Cars
Busses
Pedestrians
Cyclists
People with mobility devices

We will probably need to take and existing model and train it further for accuracy in different conditions. (nighttime, rain, snow, etc.)
If there is not a sufficient model for this purpose, we will have to train our own.

Take a look at this repo: https://github.com/pythonlessons/TensorFlow-2.x-YOLOv3
It may provide some guidance as to what kinds of models we can use. We don't have to find a model that is specifically cars, trucks, pedestrians, etc. We can just ignore the objects that we don't need.

@cczarnuch I want to make sure that my understanding of the issue is correct:
Deepsort an algorithm that given boundary boxes classifies objects, using its own association metrics. The subject of this issue is to find DL architectures that find the boundary boxes in the first place.

@cczarnuch I want to make sure that my understanding of the issue is correct:
Deepsort an algorithm that given boundary boxes classifies objects, using its own association metrics. The subject of this issue is to find DL architectures that find the boundary boxes in the first place.

Yeah sorry, I could have worded it better. But yeah that's pretty much what we need. I linked the other repo because they have an example where they were able to use the tensor flow implementation of YOLOv3, ...v4, etc. That would be able to generate the bounding boxes so we can run the tracker on them.


apps: -msg flag enhancement

The s_client "-msg" flag currently output lots of short records like:
>>> ??? [length 0005]
    16 03 01 01 3b

and
<<< ??? [length 0005]
    16 03 03 00 7a

The "???" is confusing, as end users may think something is wrong. It turns out these are usually TLS record headers.
This patch improves the reporting of these record headers, and also replaces some "magic values" in apps/lib/s_cb.c with the appropriate #define labels.
Example without:
$ ./apps/openssl s_client -connect www.google.com:443 -msg
CONNECTED(00000003)
>>> ??? [length 0005]
    16 03 01 01 3b
>>> TLS 1.3, Handshake [length 013b], ClientHello
    01 00 01 37 03 03 9f a8 aa d4 8e e2 86 9c 6b 1a
    [...]
<<< ??? [length 0005]
    16 03 03 00 7a
<<< TLS 1.3, Handshake [length 007a], ServerHello
    02 00 00 76 03 03 f0 b9 3c d9 95 73 eb 29 ae c0
    [...]
<<< ??? [length 0005]
    14 03 03 00 01
<<< ??? [length 0005]
    17 03 03 09 c6
<<< TLS 1.3 [length 0001]
    16
<<< TLS 1.3, Handshake [length 0006], EncryptedExtensions
    08 00 00 02 00 00
<<< TLS 1.3, Handshake [length 092c], Certificate
    0b 00 09 28 00 00 09 24 00 04 cc 30 82 04 c8 30
    82 03 b0 a0 03 02 01 02 02 11 00 d6 7d e6 ca a5
    [...]
depth=1 C = US, O = Google Trust Services, CN = GTS CA 1O1
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 C = US, ST = California, L = Mountain View, O = Google LLC, CN = www.google.com
verify return:1
<<< TLS 1.3, Handshake [length 004f], CertificateVerify
    0f 00 00 4b 04 03 00 47 30 45 02 20 22 9b 35 f7
    [...]
<<< TLS 1.3, Handshake [length 0034], Finished
    14 00 00 30 c1 a4 c2 12 da 3d f3 5c 93 0b 9c 2e
    [...]
>>> ??? [length 0005]
    14 03 03 00 01
>>> TLS 1.3, ChangeCipherSpec [length 0001]
    01
>>> ??? [length 0005]
    17 03 03 00 45
>>> TLS 1.3 [length 0001]
    16
>>> TLS 1.3, Handshake [length 0034], Finished
    14 00 00 30 5a ac 29 fa 3e f1 2a 79 bb 94 ae d9
    [...]
---
Certificate chain
 0 s:C = US, ST = California, L = Mountain View, O = Google LLC, CN = www.google.com
   i:C = US, O = Google Trust Services, CN = GTS CA 1O1
   a:PKEY: id-ecPublicKey, 256 (bit); sigalg: RSA-SHA256
   v:NotBefore: Jun 10 09:29:11 2020 GMT; NotAfter: Sep  2 09:29:11 2020 GMT
 1 s:C = US, O = Google Trust Services, CN = GTS CA 1O1
   i:OU = GlobalSign Root CA - R2, O = GlobalSign, CN = GlobalSign
   a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: Jun 15 00:00:42 2017 GMT; NotAfter: Dec 15 00:00:42 2021 GMT
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIEyDCCA7CgAwIBAgIRANZ95sqlyjj2CAAAAABGdOMwDQYJKoZIhvcNAQELBQAw
[...]
-----END CERTIFICATE-----
subject=C = US, ST = California, L = Mountain View, O = Google LLC, CN = www.google.com

issuer=C = US, O = Google Trust Services, CN = GTS CA 1O1

---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: ECDSA
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 2640 bytes and written 400 bytes
Verification error: unable to get local issuer certificate
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 256 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 20 (unable to get local issuer certificate)
---
DONE
>>> ??? [length 0005]
    17 03 03 00 13
>>> TLS 1.3 [length 0001]
    15
>>> TLS 1.3, Alert [length 0002], warning close_notify
    01 00

Example with:
$ ./apps/openssl s_client -connect www.google.com:443 -msg
CONNECTED(00000003)
>>> TLS 1.0, RecordHeader [length 0005]
    16 03 01 01 3b
>>> TLS 1.3, Handshake [length 013b], ClientHello
    01 00 01 37 03 03 cd 63 f0 6e 75 bc b2 f8 a1 6d
    [...]
<<< TLS 1.2, RecordHeader [length 0005]
    16 03 03 00 7a
<<< TLS 1.3, Handshake [length 007a], ServerHello
    02 00 00 76 03 03 f2 3b 68 51 33 fb 0e 5f 22 5d
    [...]
<<< TLS 1.2, RecordHeader [length 0005]
    14 03 03 00 01
<<< TLS 1.2, RecordHeader [length 0005]
    17 03 03 09 c5
<<< TLS 1.3 [length 0001]
    16
<<< TLS 1.3, Handshake [length 0006], EncryptedExtensions
    08 00 00 02 00 00
<<< TLS 1.3, Handshake [length 092b], Certificate
    0b 00 09 27 00 00 09 23 00 04 cb 30 82 04 c7 30
    [...]
depth=1 C = US, O = Google Trust Services, CN = GTS CA 1O1
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 C = US, ST = California, L = Mountain View, O = Google LLC, CN = www.google.com
verify return:1
<<< TLS 1.3, Handshake [length 004f], CertificateVerify
    0f 00 00 4b 04 03 00 47 30 45 02 21 00 ae b1 48
    [...]
<<< TLS 1.3, Handshake [length 0034], Finished
    14 00 00 30 70 02 7a 83 c7 bb d2 e4 eb 47 b9 69
    [...]
>>> TLS 1.2, RecordHeader [length 0005]
    14 03 03 00 01
>>> TLS 1.3, ChangeCipherSpec [length 0001]
    01
>>> TLS 1.2, RecordHeader [length 0005]
    17 03 03 00 45
>>> TLS 1.2 [length 0001]
    16
>>> TLS 1.3, Handshake [length 0034], Finished
    14 00 00 30 85 04 a1 4d eb 43 f9 08 be 9d dc 27
    [...]
---
Certificate chain
 0 s:C = US, ST = California, L = Mountain View, O = Google LLC, CN = www.google.com
   i:C = US, O = Google Trust Services, CN = GTS CA 1O1
   a:PKEY: id-ecPublicKey, 256 (bit); sigalg: RSA-SHA256
   v:NotBefore: May 26 15:30:03 2020 GMT; NotAfter: Aug 18 15:30:03 2020 GMT
 1 s:C = US, O = Google Trust Services, CN = GTS CA 1O1
   i:OU = GlobalSign Root CA - R2, O = GlobalSign, CN = GlobalSign
   a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: Jun 15 00:00:42 2017 GMT; NotAfter: Dec 15 00:00:42 2021 GMT
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIExzCCA6+gAwIBAgIRALJsaMAobZ6SCAAAAABDVSUwDQYJKoZIhvcNAQELBQAw
[...]
-----END CERTIFICATE-----
subject=C = US, ST = California, L = Mountain View, O = Google LLC, CN = www.google.com

issuer=C = US, O = Google Trust Services, CN = GTS CA 1O1

---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: ECDSA
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 2639 bytes and written 400 bytes
Verification error: unable to get local issuer certificate
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 256 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 20 (unable to get local issuer certificate)
---
DONE
>>> TLS 1.2, RecordHeader [length 0005]
    17 03 03 00 13
>>> TLS 1.2 [length 0001]
    15
>>> TLS 1.3, Alert [length 0002], warning close_notify
    01 00

NB: I do have a CLA
I will try to fix the Travis build failure. I see what the problem is.

Maybe clean up the commit message to be something like:
Enhance '-msg' option used by s_client/s_server applications.
Improve the logging of record headers.
Replaces "magic values" in apps/lib/s_cb.c with the appropriate #define labels.

Maybe clean up the commit message to be something like:
Enhance '-msg' option used by s_client/s_server applications.
Improve the logging of record headers.
Replaces "magic values" in apps/lib/s_cb.c with the appropriate #define labels.

Agreed - I don't know how to change the commit message, but if/when this gets merged it can be "squashed" into one commit with that message.

NB: I do have a CLA. It just seems the CLA check has an issue with github email addresses.
See https://github.com/openssl/openssl/pull/7975 & https://github.com/openssl/openssl/pull/10757 for some other PRs that have been merged.
@mattcaswell - can you help move this along?

It looks like there were some issues getting the CLA to work for your other issue also. @levitte any ideas?

@mattcaswell - can you help move this along?

Matt is away at the moment.

This PR has the label 'hold: cla required' and is stale: it has not been updated in 30 days. Note that this PR may be automatically closed in the future if no CLA is provided.  For CLA help see https://www.openssl.org/policies/cla.html

NB: I do have a CLA. It just seems the CLA check has an issue with github email addresses.
See #7975 & #10757 for some other PRs that have been merged.
Can someone help move this along? It would be good to get it into the next alpha or beta release.
Thanks & kind regards.

NB: I do have a CLA. It just seems the CLA check has an issue with github email addresses.

Perhaps @levitte can help with the bot issue?

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Squashed and merged. Many thanks!


Chore/change folder names

Main improvements in this PR:
This partly addresses #232 by changing folder names to be compliant with MetabolicAtlas/standard-GEM.
Note that:

This branch should not be merged until a new release of RAVEN is out (or at least https://github.com/SysBioChalmers/RAVEN/pull/303 is merged).
After merging this branch, there will be conflicts with our master branch that should be handled before a new release is made.

I hereby confirm that I have:

[x] Tested my code with all requirements for running the model
[x] Selected devel as a target branch (top left drop-down menu)

@edkerk was too quick with this one: before reviewing maybe we should first settle on the model folder issue in #232 and also merge #228 to avoid conflicts :)


Cilium, documentation create Architecture section

This creates a new documentation section "Architecture" to describe the BPF datapath at a higher level than the BPF reference guide and slightly different from the prescriptive style documents that explain how to use these features. Previously these existed in the "Concepts" section but that wasn't a great fit either.
We moved Kubernetes Integration diagram into the new Architecture as well as a BPF datapath description. In the future we can get more diagrams to show how BPF datapath hooks into Cilium Agent.

This change is

@joestringer one option is to move the Arch section up a level on par with GettingStarted and Integration to get it out of gettingstarted section. Although keeping it out of Developer is probably good.

just moved the Arch section up a level and thought it looked a bit strange I think leaving it where its at for now makes sense. If it gets larger we can pull it out in a later commit. My $.02

Do we need to run Cilium-Gikgo-Tests on doc only commits?

Do we need to run Cilium-Gikgo-Tests on doc only commits?

@jrfastab - no, we do not. It says 'Required' because we mark it as such since 95 % of our changes are to the code base which do require the integration tests to be ran. I do wonder if we can dynamically mark which builds are 'required' by detecting the nature of the change in the PR in the future.


lint(frontend): fix HeaderLinks lint error

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@david-leifker any idea why this just started causing issues? looks like its been in the code for months


add grace period for pod kill chaos

What problem does this PR solve?

Solve #569.
What is changed and how does it work?
Added a gracePeriod field in the PodChaos CRD.
Check List

Tests

Unit test
E2E test
Manual test (add detailed scripts or steps below)

Code changes

Has Go code change

Related changes

Need to update the documentation to add gracePeriod field.

Does this PR introduce a user-facing change?

The gracePeriod field is available in podChaos to set the duration before the pod is deleted.

 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.

Codecov Report

Merging #663 into master will decrease coverage by 0.06%.
The diff coverage is 40.00%.

@@            Coverage Diff             @@
##           master     #663      +/-   ##
==========================================
- Coverage   55.78%   55.71%   -0.07%
==========================================
  Files          68       68
  Lines        4383     4397      +14
==========================================
+ Hits         2445     2450       +5
- Misses       1768     1776       +8
- Partials      170      171       +1

Impacted Files
Coverage Δ

api/v1alpha1/podchaos_types.go
37.14% <ø> (ø)

controllers/networkchaos/ipset/ipset.go
37.14% <0.00%> (ø)

pkg/store/experiment/experiment.go
32.20% <0.00%> (-6.58%)
:arrow_down:

pkg/utils/chaosdaemon.go
51.21% <0.00%> (ø)

pkg/utils/grpc.go
0.00% <0.00%> (ø)

controllers/twophase/types.go
54.20% <40.00%> (-1.68%)
:arrow_down:

controllers/networkchaos/netem/types.go
47.27% <50.00%> (ø)

controllers/podchaos/containerkill/types.go
64.38% <100.00%> (ø)

controllers/podchaos/podkill/types.go
63.82% <100.00%> (ø)

controllers/timechaos/types.go
61.44% <100.00%> (ø)

... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 699993e...98a2df9. Read the comment docs.

@namco1992 Thanks for your contribution! Can you fix DCO checker?

@cwen0 Fixed, thanks!

/run-e2e-tests

/merge

/run-all-tests

/run-all-tests


Option to build using snappy.

 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.:x: rotrida sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Adding Snappy compression option.

Related issue: #7454

Hi! @rotrida Sorry for not solving your problem before, as I thought librdkafka is always built with snappy:
https://github.com/edenhill/librdkafka/blob/d443b4f025058172d2c8568376e36e54aba0b8b4/src/win32_config.h#L38
https://github.com/edenhill/librdkafka/blob/master/packaging/cmake/config.h.in#L34
As we can see, librdkafka has two configuration header files:
One named config.h.in, which is supposed to be used when configuring with CMake.
The other one, win32_config.h, is supposed to be used together with the VS solution provided by librdkafka.
Unfortunately, in rd.h:
https://github.com/edenhill/librdkafka/blob/master/src/rd.h#L54-L60
That is, win32_config.h is always used when building with MSVC, even you configuring with CMake.
And in win32_config.h:
#ifndef WITHOUT_WIN32_CONFIG
#define WITH_SSL 1
#define WITH_ZLIB 1
#define WITH_SNAPPY 1
#define WITH_ZSTD 1
/* zstd is linked dynamically on Windows, but the dynamic library provides
 * the experimental/advanced API, just as the static builds on *nix */
#define WITH_ZSTD_STATIC 1
#define WITH_SASL_SCRAM 1
#define WITH_SASL_OAUTHBEARER 1
#define ENABLE_DEVEL 0
#define WITH_PLUGINS 1
#define WITH_HDRHISTOGRAM 1
#endif

WITHOUT_WIN32_CONFIG is defined here, which has a default value 'ON':
https://github.com/edenhill/librdkafka/blob/d443b4f025058172d2c8568376e36e54aba0b8b4/CMakeLists.txt#L167

I guess this patch should fix the snappy support:
diff --git a/ports/librdkafka/portfile.cmake b/ports/librdkafka/portfile.cmake
index 5bc66fdf..88bcf5e3 100644
--- a/ports/librdkafka/portfile.cmake
+++ b/ports/librdkafka/portfile.cmake
@@ -27,6 +27,7 @@ vcpkg_configure_cmake(
         -DRDKAFKA_BUILD_EXAMPLES=OFF
         -DRDKAFKA_BUILD_TESTS=OFF
         -DWITH_BUNDLED_SSL=OFF
+        -DWITHOUT_WIN32_CONFIG=OFF
         ${FEATURE_OPTIONS}
     OPTIONS_DEBUG
         -DENABLE_DEVEL=ON

I have created a PR in the upstream before: https://github.com/edenhill/librdkafka/pull/2323

I have created a PR in the upstream before: edenhill/librdkafka#2323

Great! Thank you for getting into it.

Hi! @rotrida Please do not close your PR yet. Instead please update your PR like this:
vcpkg_configure_cmake(
    SOURCE_PATH ${SOURCE_PATH}
    PREFER_NINJA
    OPTIONS
        -DRDKAFKA_BUILD_STATIC=${RDKAFKA_BUILD_STATIC}
        -DRDKAFKA_BUILD_EXAMPLES=OFF
        -DRDKAFKA_BUILD_TESTS=OFF
        -DWITH_BUNDLED_SSL=OFF
        -DWITHOUT_WIN32_CONFIG=OFF # ADD THIS OPTION HERE
        ${FEATURE_OPTIONS}
    OPTIONS_DEBUG
        -DENABLE_DEVEL=ON
        -DENABLE_REFCNT_DEBUG=ON
        -DENABLE_SHAREDPTR_DEBUG=ON
        -DWITHOUT_OPTIMIZATION=ON
    OPTIONS_RELEASE
        -DENABLE_DEVEL=OFF
        -DENABLE_REFCNT_DEBUG=OFF
        -DENABLE_SHAREDPTR_DEBUG=OFF
        -DWITHOUT_OPTIMIZATION=OFF
)

and bump the version number in the CONTROL file.

Hi! @rotrida Thanks! This way this issue can get a quick fix in vcpkg and maybe other guys can benefit from this PR too.

Superseded by #7469 . So close this one.

Hi @myd7349 ,
Unfortunatelly removal, adding "-DWITHOUT_WIN32_CONFIG=OFF" didn't worked as expected. We can see at https://github.com/microsoft/vcpkg/pull/7469. Do you have any other idea?
Thanks,
Rodrigo.


Liveness property checked incorrectly

Hello! First of all, impressive work with his library. Thanks for releasing it.
I was trying to port some stuff from TLA+ to Spectacle and run into some weird behaviour with eventually and eventually . always properties.
The test file below reproduces the issues.
The expected behaviour of the model is that a Right counter value will be incremented until it gets to the maxCounter constant, and then it shifts to the final state Left counter. Thus, it should hold that #counter is eventually equal to Left maxCounter, and it is also the case that it eventually is always equal to Left counter. However, this property should be violated if the initialCounter value is larger than maxCounter.
What I see, though, is that eventually seems to reject cases where the model gets stuck forever in a state, even though that state matches the formula. On the other hand, it looks like eventually . always accepts possibilities that actually never achieve the desired state.
Of course it may be that I'm making a mistake using the library. If that's the case I would be very thankful if you could point me in the right direction.
Versions:

MacOS Mojave
GHC 8.10.7
Spectacle - git commit 7e7efd64755252f2697f19ff44da47893c15629c

Test module
{-# LANGUAGE DataKinds, ImportQualifiedPost, OverloadedLabels, TypeOperators #-}

module Specs.SimpleCounterSpec where

import Data.Either qualified as Either
import Language.Spectacle (Action, Initial, Invariant, always, define, eventually, modelCheck, plain, weakFair, (.=), type (#))
import Language.Spectacle.Specification (Specification (..))
import Test.Hspec (Spec, describe, hspec, it, shouldSatisfy)

main :: IO ()
main = hspec spec

spec :: Spec
spec =
  describe "Counter spec" $ do
    describe "eventually is maxCounter" $ do
      let specification constants =
            Specification
              { initialAction = initSpec constants
              , nextAction = next
              , temporalFormula = eventually $ formula constants
              , terminationFormula = Nothing
              , fairnessConstraint = weakFair
              }
      it "passes when initialCounter < maxCounter" $ do
        modelCheck (specification (1, 4)) `shouldSatisfy` Either.isRight
      it "passes when initialCounter = maxCounter" $ do
        modelCheck (specification (4, 4)) `shouldSatisfy` Either.isRight
      it "fails when initialCounter > maxCounter" $ do
        modelCheck (specification (4, 2)) `shouldSatisfy` Either.isLeft
    describe "eventually always is maxCounter" $ do
      let specification constants =
            Specification
              { initialAction = initSpec constants
              , nextAction = next
              , temporalFormula = eventually . always $ formula constants
              , terminationFormula = Nothing
              , fairnessConstraint = weakFair
              }
      it "passes when initialCounter < maxCounter" $ do
        modelCheck (specification (1, 4)) `shouldSatisfy` Either.isRight
      it "passes when initialCounter = maxCounter" $ do
        modelCheck (specification (4, 4)) `shouldSatisfy` Either.isRight
      it "fails when initialCounter > maxCounter" $ do
        modelCheck (specification (4, 2)) `shouldSatisfy` Either.isLeft

type CounterSpec = '["goal" # Word, "counter" # Either Word Word]

initSpec :: (Word, Word) -> Initial CounterSpec ()
initSpec (initialCounter, maxCounter) = do
  #goal `define` pure maxCounter
  #counter `define` pure (Right initialCounter)

next :: Action CounterSpec Bool
next = do
  goal <- plain #goal
  counter <- plain #counter
  case counter of
    Right c
      | c < goal -> do
        #counter .= pure (Right $ c + 1)
        pure True
      | otherwise -> do
        #counter .= pure (Left c)
        pure True
    Left _ -> pure True

formula :: (Word, Word) -> Invariant CounterSpec Bool
formula (_, maxCounter) = do
  counter <- plain #counter
  pure $ counter == Left maxCounter

Output of test run:
Counter spec
  eventually is maxCounter
    passes when initialCounter < maxCounter [✘]
    passes when initialCounter = maxCounter [✘]
    fails when initialCounter > maxCounter [✔]
  eventually always is maxCounter
    passes when initialCounter < maxCounter [✔]
    passes when initialCounter = maxCounter [✔]
    fails when initialCounter > maxCounter [✘]

Failures:

  test/Specs/SimpleCounterSpec.hs:24:9:
  1) Counter spec, eventually is maxCounter, passes when initialCounter < maxCounter
       predicate failed on: Left [MCFormulaError <<0x86c03a317:goal=4 counter=Left 4 RNil>> --> <<0x86c03a317:goal=4 counter=Left 4 RNil>> (Just (SrcLoc {srcLocPackage = "main", srcLocModule = "Specs.SimpleCounterSpec", srcLocFile = "test/Specs/SimpleCounterSpec.hs", srcLocStartLine = 19, srcLocStartCol = 35, srcLocEndLine = 19, srcLocEndCol = 65})) EventuallyPropK]

  To rerun use: --match "/Counter spec/eventually is maxCounter/passes when initialCounter < maxCounter/"

  test/Specs/SimpleCounterSpec.hs:26:9:
  2) Counter spec, eventually is maxCounter, passes when initialCounter = maxCounter
       predicate failed on: Left [MCFormulaError <<0x86c03a317:goal=4 counter=Left 4 RNil>> --> <<0x86c03a317:goal=4 counter=Left 4 RNil>> (Just (SrcLoc {srcLocPackage = "main", srcLocModule = "Specs.SimpleCounterSpec", srcLocFile = "test/Specs/SimpleCounterSpec.hs", srcLocStartLine = 19, srcLocStartCol = 35, srcLocEndLine = 19, srcLocEndCol = 65})) EventuallyPropK]

  To rerun use: --match "/Counter spec/eventually is maxCounter/passes when initialCounter = maxCounter/"

  test/Specs/SimpleCounterSpec.hs:43:9:
  3) Counter spec, eventually always is maxCounter, fails when initialCounter > maxCounter
       predicate failed on: Right (ModelMetrics {_distinctStates = 2, _treeDepth = 2, _treeWidth = 0})

  To rerun use: --match "/Counter spec/eventually always is maxCounter/fails when initialCounter > maxCounter/"

Randomized with seed<PHONE_NUMBER>

Finished in 0.0219 seconds
6 examples, 3 failures
*** Exception: ExitFailure 1

I just adapted my example to use the current version from main (commit 21337e45f710a88de7760e3d4b51458969d6eb63), and everything seem to be working now! New code below:
module Specs.SimpleCounterSpec where

import Data.Either qualified as Either
import Data.Hashable (Hashable)
import GHC.Generics (Generic)
import Language.Spectacle (
  ActionType (ActionWF),
  Fairness (WeakFair),
  Modality (Eventually, Stays),
  Specification (..),
  Temporal,
  TemporalType (PropF, PropFG),
  modelcheck,
  plain,
  (.=),
  pattern ConF,
  pattern NilF,
  type (#),
 )
import Test.Hspec (Spec, describe, hspec, it, shouldSatisfy)

main :: IO ()
main = hspec spec

spec :: Spec
spec =
  describe "SimpleCounter spec" $ do
    describe "eventually is maxCounter" $ do
      specification <- pure $ specification @Eventually PropF
      it "passes when initialCounter < maxCounter" $ do
        result <- modelcheck (specification (1, 4))
        result `shouldSatisfy` Either.isRight
      it "passes when initialCounter = maxCounter" $ do
        result <- modelcheck (specification (4, 4))
        result `shouldSatisfy` Either.isRight
      it "fails when initialCounter > maxCounter" $ do
        result <- modelcheck (specification (4, 2))
        result `shouldSatisfy` Either.isLeft
    describe "eventually always is maxCounter" $ do
      specification <- pure $ specification @Stays PropFG
      it "passes when initialCounter < maxCounter" $ do
        result <- modelcheck (specification (1, 4))
        result `shouldSatisfy` Either.isRight
      it "passes when initialCounter = maxCounter" $ do
        result <- modelcheck (specification (4, 4))
        result `shouldSatisfy` Either.isRight
      it "fails when initialCounter > maxCounter" $ do
        result <- modelcheck (specification (4, 2))
        result `shouldSatisfy` Either.isLeft

data Counter = Counting Word | Done Word
  deriving stock (Eq, Show, Generic)
  deriving anyclass (Hashable)

type CounterSpec modality =
  Specification CounterState CounterActions (CounterProperty modality)

type CounterState =
  '[ "goal" # Word
   , "counter" # Counter
   ]

type CounterActions =
  '[ "counterInc" # 'WeakFair
   ]

type CounterProperty modality =
  '["counterEqualsMax" # modality]

specification ::
  (forall s. Temporal s Bool -> TemporalType s modality) ->
  (Word, Word) ->
  CounterSpec modality
specification toProp (initialCounter, maxCounter) =
  Specification
    { specInit =
        ConF #goal (pure maxCounter)
          . ConF #counter (pure (Counting initialCounter))
          $ NilF
    , specNext =
        ConF #counterInc (ActionWF counterInc) NilF
    , specProp =
        ConF #counterEqualsMax (toProp counterEqualsMax) NilF
    }
 where
  counterInc =
    plain #counter >>= \case
      Done _ -> pure False
      Counting counter -> do
        goal <- plain #goal
        let counter' =
              if counter < goal
                then Counting $ counter + 1
                else Done counter
        #counter .= pure counter'
        pure True
  counterEqualsMax = do
    goal <- plain #goal
    counter <- plain #counter
    pure
      case counter of
        Done c -> c == goal
        _ -> False


Fill in openapi 'summary' field

Currently the comment on a table is used for the 'description' but the 'summary' field is left blank.
https://github.com/begriffs/postgrest/blob/2243f4b6539577a6534e11bee66052ae5cda7e71/src/PostgREST/OpenAPI.hs#L188
I propose using the first line of the comment as the 'summary', and anything following as the description (sort of like a git commit).

This should happen for columns (as well as tables/view): if there is no summary, then swagger-ui prefills <input> boxes with the whole column description.


Send logging output to a text file on CI

Send logging output into a text file
Send console output to a text file
Attach above text file as artifacts for each test job on CI

Here's what the console log looks like:

Here's what the log file looks like:


Need output string details

Is the output volume name string zero-terminated? If so, does the Length field in the descriptor include the terminator?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 55e05b21-c927-e661-6ad4-e430eb5d59ac
Version Independent ID: 3b6c2052-2fa5-5542-5f56-9ab43b3b7846
Content: FltGetVolumeName function (fltkernel.h) - Windows drivers
Content Source: wdk-ddi-src/content/fltkernel/nf-fltkernel-fltgetvolumename.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @lorihollasch
Microsoft Alias: loriwhip

@briancatlin, the answer to this question is on the UNICODE_STRING page, which has disappeared from our doc set and resulted in broken links like the one on this page, sorry! We will work to find the disappeared page and get it back online. In the interim, I'll answer your questions and close this issue. The output volume name string is not null-terminated and length is the length of the non-null-terminated string. Until we get the UNICODE_STRING page up, you can find the info on NTSCSI_UNICODE_STRING. Thanks for making us aware of this!

The good news is that the page for UNICODE_STRING is restored.  The bad news is that there's a known rendering bug with the ref doc pipeline that is messing up the description of the Buffer member.


Roll Flutter Engine from b5b41ff66dae to 029a7df85f9d (11 revisions)

https://github.com/flutter/engine/compare/b5b41ff66dae...029a7df85f9d
2023-08-09<EMAIL_ADDRESS>Manual roll Dart SDK from f664f4b9c50d to d89e4ead966d (11 revisions) (flutter/engine#44560)
2023-08-09<EMAIL_ADDRESS>Make toJS'd function use JS types (flutter/engine#44469)
2023-08-09<EMAIL_ADDRESS>[web] Fix rendering of gradients in html mode (flutter/engine#40345)
2023-08-09<EMAIL_ADDRESS>Flutter iOS Interactive Keyboard: Fixing Animation Issue (flutter/engine#44514)
2023-08-09<EMAIL_ADDRESS>Roll Skia from 8c9a8d3e073c to 3d5a6138b7e5 (4 revisions) (flutter/engine#44557)
2023-08-09<EMAIL_ADDRESS>Roll Skia from d210bab77137 to 8c9a8d3e073c (1 revision) (flutter/engine#44555)
2023-08-09<EMAIL_ADDRESS>Roll Skia from 25aedb939915 to d210bab77137 (2 revisions) (flutter/engine#44550)
2023-08-09<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from e7bMhkfY-RPMrSMhB... to zoCGnScKZWbm5s9Hy... (flutter/engine#44548)
2023-08-09<EMAIL_ADDRESS>Roll Skia from 17ba2122707b to 25aedb939915 (3 revisions) (flutter/engine#44547)
2023-08-09<EMAIL_ADDRESS>Android a11y bridge sets importantness (flutter/engine#44452)
2023-08-09<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from tO6r8iQqnmsYkLcvZ... to ZCP8LDbKF4LTBFz_W... (flutter/engine#44545)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from tO6r8iQqnmsY to ZCP8LDbKF4LT
fuchsia/sdk/core/mac-amd64 from e7bMhkfY-RPM to zoCGnScKZWbm
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC chinmaygarde@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Scroll Wheel Moving Hands

Everything works great in my test project, however in the project I am currently working on, the scroll wheel is not behaving as normal.
Instead of moving the camera up and down, the scroll wheel is moving the hands up and down, spawning issues such as clipping through the floor when teleporting.
I likely missed a step when setting up the XR functionality, if you know what could be causing this error please let me know.

This behavior happens when you have a PlayerBody and the camera y position goes bellow 0.5 or above PlayerBody.player_height_max - PlayerBody.player_head_height (2.1 by default). I added a way to limit the camera y movement between 0.5 and 2.0 in the default settings. You can also adjust those values in the XRSimulator

But I don't know if this is the best way to fix this issue.
You can download the update here:
https://github.com/Cafezinhu/godot-vr-simulator/releases/tag/v1.0.4

Yup, increasing the camera's y-position to 0.5 fixed the issue. Thanks again!


perf: Initial DataCubeComponents / dimension values query optimizations

Closes #1372.
This PR is a first step towards optimizing the performance situation related to DataCubeComponents query.

Disabled loading of dimension values where applicable
Adjusted several places in the code to not send unnecessary filters to the server to make sure we use sh:in as much as possible
Fixed an issue with not using optional chaining to access last dimension value
Refactored the approach to fetching available filter values from one combined DataCubesComponents call with filters for every dimension to individual calls directly from filter components. This enables us to more precisely pass filters and rely more on sh:in, as for the first filter we won't send filters object anymore
Fixed an issue with fetching dimension values which resulted in fetching values that couldn't be selected (combinations resulting in no observations, fixed after selection by possible filters query)

Next steps

Consolidate DataCubeComponents-related queries into CONSTRUCT query/ies
Consider using mobx to improve manageability of data fetching across the app
Consider decoupling dimension values fetching from components to make it more clear where we actually need to fetch values (currently it's not ideal, as we might or might not have values fetched)

How to test
PR

Go to this link.
✅ See that the filters are loaded in the background (some might fail to load due to Vercel's 15s timeout).
✅ See that the last filter (4. Zusatzmengencode - EN) contains five values.

TEST

Go to this link.
❌ See that the initial view loads much slower compared to the PR link.
❌ See that the last filter (4. Zusatzmengencode - EN) contains seven values.
Try to change value of above filter to Metres.
❌ See that the chart reloads back to No supplementary unit.

@bprusinowski now that you pass loadValues this is the condition when to ask for hierarchies
https://github.com/visualize-admin/visualization-tool/blob/9de220438a23a37b88c12f6a364e6688839c2c3b/app/graphql/resolvers/rdf.ts#L228-L229
only if loadValues is true
impact: gain speed by skipping unecessary hierachy queries alltogether


Update version to v1.1 as described in AIRR meeting

Well, we don't have the v1.0 tag yet though, we should decide what if anything we want in that tag (#55). Maybe create v1.0.0 now then very soon release v1.0.X with documentation, software, and etc. I'm thinking we don't want to actually be v1.1 until MiAIRR and others have new standards. For example, new standards from germline WG or common repository WG being likely candidates.


Fix model update add documentation (#1)

Add is performed only on set/number

Summary:
Updated documentation for Model.update to better reflect what $ADD actually does.

GitHub linked issue:
Closes #388
Type (select 1):

[ ] Bug fix
[ ] Feature implementation
[x] Documentation improvement
[ ] Testing improvement

[ ] Test added to report bug (GitHub issue #--- @---)
[ ] Something not listed here

Is this a breaking change? (select 1):

[ ] 🚨 YES 🚨
[x] No
[ ] I'm not sure

Is this ready to be merged into Dynamoose? (select 1):

[x] Yes
[ ] No

Are all the tests currently passing on this PR? (select 1):

[x] Yes
[ ] No

Other:

[x] I have searched through the GitHub pull requests to ensure this PR has not already been submitted
[x] I have updated the Dynamoose documentation (if required) given the changes I made
[x] I have added/updated the Dynamoose test cases (if required) given the changes I made
[x] I have run npm test from the root of the project directory to ensure all tests continue to pass
[x] I agree that all changes made in this pull request may be distributed and are made available in accordance with the Dynamoose license
[x] All of my commits and commit messages are detailed, explain what changes were made, and are easy to follow and understand
[x] I have confirmed that all my code changes are indented properly using 2 spaces
[x] I have filled out all fields above

Pull Request Test Coverage Report for Build 673

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.566%

Totals

Change from base Build 669:
0.0%

Covered Lines:
1866

Relevant Lines:
2132

💛  - Coveralls

@pkonneker Thanks for this! Will get merged in soon.


Does this support GPU?

I wonder if this library supports GPU like cuBLAS?

@marker68 , OpenBLAS didn't support GPU so far.
@wernsaar, Werner has optimized some kernels for GPU by OpenCL.  We plan to release GPU optimization codes in the near future.

When you will release GPU like cuda or through OpenCL?

@guangwei , there are some experiment codes at https://github.com/xianyi/clOpenBLAS

@xianyi  thank you for your information

Any updates on this? It would be awesome to have an OpenCL implementation of OpenBLAS.

By the looks of it, the last work on clOpenBLAS happened in April 2015 (and wernsaar its primary developer was last seen on github in January 2017,  even xianyi himself appears to be absorbed in his own business lately). Have you looked at clBLAS and/or clBLAST ?

@martin-frbg Sad to hear that the main developers have abandoned their work.
I'm actually aware of several OpenCL implementations of BLAS API:  CLBlast, clBLAS, clMAGMA, ArrayFire and ViennaCL, to mention a few. Although they are great, OpenBLAS seems to be the most prominent BLAS implementation of the API, used by a great majority of other projects. If we should have true cross platform and vendor natural GPGPU accelerated BLAS, OpenBLAS is the best one to invest in.
P.S. Unfortunately CUDA is eating away the whole GPGPU world and there will be a monopoly if the community keeps ignoring the issue.

You can certainly fork and continue the project (I do not have collaborator status there, so would not be able to merge PRs in the original clOpenBLAS repository). I think it is possible that the block algorithms originally introduced by K.Goto to make the most use of (x86) CPU caches are less well suited for GPU hardware. (This seems to be a major performance obstacle in the RISC V port of OpenBLAS at least, I know very little about OpenCL coding)

Nowadays, most of the GPUs have tensor cores that do a multiply of 16x16 matrices at once. So, GPUs work at tile granularity, not at the element granularity as it was in the classical GPGPU. From what I see, OpenBLAS uses tiling/dispatching strategy and calls tiled multiplies as elemental operations of its scheduler. Therefore it feels that the GPU tensor cores could serve as drop-in implementation of tiled multiplies within the existing OpenBLAS scheduler. Of course, threading has to change, but overall the OpenBLAS design and GPU tensor cores are potentially highly compatible.

potentially, yes. not sure offhand if "the threading has to change" wouldn't be a major obstacle, especially if one wants new GPU kernels and the present CPU code to coexist. I feel I dont know enough about current GPU offloading techniques to assess if it would make (more) sense now, or if one would be fighting the existing codebase most of the time.


Webpack Mode for externally loaded chunks - don't reject if not loaded yet

Feature request
Webpack mode that's a mix of lazy/weak, bundle generated to be loaded like lazy mode, but loaded externally like weak mode (and waits for the file to load if not loaded, like lazy)

What is the expected behavior?
If doing a dynamic import, allow the chunk to be loaded with external code, but don't reject if it isn't loaded by the time the dynamic import happens. Keep waiting until it loads.
What is motivation or use case for adding/changing the behavior?
I'm trying to use my script on a site that has anti-malware code blocking scripts from adding new scripts to the page. Scripts can only be added by the site owner.
My script is large and I would like to break it into smaller pieces, only loading the code needed for the entry UI first. I can set it up to load a second script after the first is loaded, but there isn't a webpack mode that supports this (weak mode is close, but rejects if the script hasn't loaded)
How should this be implemented in your opinion?
the importing side should behave almost like weak mode, but if the script is missing, it should set up a listener, and resolve once that's called
the imported side should be generated the same way lazy mode is, but with a bit of added code that triggers the listener on the importing side if it exists
Are you willing to work on this yourself?
no

Out of scope webpack, you can implement this in your application code


Add proc_key/1 function match for literals

Supports Cargo.toml configurations such as:
[target.'cfg(windows)'.dependencies]

which are matched by the lexer as {:literal, _} but fail to parse with a function missing error.

@erik-nymi looks like this PR was based on the vendor-erl-nif-sys branch?
Can you please close this and base your changes on master instead?


fix the client side reliance on the analysis data

that means storing the analysis serverside and not relying on client sided locastorage

we can implement this via github octokit and make every conversation automatically a shared link

ill implement the change when i get back from this

nvm im kinda lazy ill do this when i want to do it

fixed in commit adbf4c66d00ff65809e54b2bdf66ee87b2bcecf0


Don't export dom module if on node

Would be nice to only export the dom module if the user's targeting the browser, similar to how fetch-ponyfill and others do it.
Currently, including the entire package through require('js-utility-belt') on node results in errors because node doesn't have window or document.
From the looks of it, this should be easily done by using the package.json's browser field for lib/index.js and changing the main field for a lib/node.js that strips away the dom export.

See https://github.com/webpack/webpack/issues/1122 for some ideas for webpack building.


Implement Connector ShortIds

In the new api (V5) there is a shortId added to connectors to be able to avoid the 200 character limit when updating connectors.
Doc
example message that gets send:
{
  "type":"shortConnectorIdNotification",
  "pluginId":"id of the plugin",
  "shortId":"shortid of the connector",
  "connectorId":"the long normal connector id"
}

Thanks for adding - it's probably less of an issue since this doesn't auto generate those long id's like the Java SDK, but definitely to be fully up to date on newest TP SDK it needs to be added.


Pick up correct columns for Rt indicators

This PR addresses issue #309
Please Check

[ ] Are the JSON schemas updated?
[ ] Are the api docs updated?
[ ] Are tests passing?

This is expected to fail until #308 lands.


TPC-H Q3,7, 20 take too much time with low thread usage.

Steps to reproduce the behavior (Required)
3 BE nodes, 1 FE nodes.
TPC-H SF100, creating tables do not use the default key.
CREATE TABLE `orders` (
  `o_orderkey` int(11) NOT NULL COMMENT "",
  `o_orderdate` date NOT NULL COMMENT "",
  `o_custkey` int(11) NOT NULL COMMENT "",
  `o_orderstatus` varchar(1) NOT NULL COMMENT "",
  `o_totalprice` decimal64(15, 2) NOT NULL COMMENT "",
  `o_orderpriority` varchar(15) NOT NULL COMMENT "",
  `o_clerk` varchar(15) NOT NULL COMMENT "",
  `o_shippriority` int(11) NOT NULL COMMENT "",
  `o_comment` varchar(79) NOT NULL COMMENT ""
) ENGINE=OLAP
DUPLICATE KEY(`o_orderkey`, `o_orderdate`, `o_custkey`)
COMMENT "OLAP"
DISTRIBUTED BY HASH(`o_comment`, `o_orderkey`) BUCKETS 55
PROPERTIES (
"replication_num" = "1",
"in_memory" = "false",
"storage_format" = "DEFAULT"
);

CREATE TABLE `lineitem` (
  `l_shipdate` date NOT NULL COMMENT "",
  `l_orderkey` int(11) NOT NULL COMMENT "",
  `l_linenumber` int(11) NOT NULL COMMENT "",
  `l_partkey` int(11) NOT NULL COMMENT "",
  `l_suppkey` int(11) NOT NULL COMMENT "",
  `l_quantity` decimal64(15, 2) NOT NULL COMMENT "",
  `l_extendedprice` decimal64(15, 2) NOT NULL COMMENT "",
  `l_discount` decimal64(15, 2) NOT NULL COMMENT "",
  `l_tax` decimal64(15, 2) NOT NULL COMMENT "",
  `l_returnflag` varchar(1) NOT NULL COMMENT "",
  `l_linestatus` varchar(1) NOT NULL COMMENT "",
  `l_commitdate` date NOT NULL COMMENT "",
  `l_receiptdate` date NOT NULL COMMENT "",
  `l_shipinstruct` varchar(25) NOT NULL COMMENT "",
  `l_shipmode` varchar(10) NOT NULL COMMENT "",
  `l_comment` varchar(44) NOT NULL COMMENT ""
) ENGINE=OLAP
DUPLICATE KEY(`l_shipdate`, `l_orderkey`, `l_linenumber`)
COMMENT "OLAP"
DISTRIBUTED BY HASH(`l_comment`, `l_orderkey`) BUCKETS 96
PROPERTIES (
"replication_num" = "1",
"in_memory" = "false",
"storage_format" = "DEFAULT"
);

CREATE TABLE `customer` (
  `c_custkey` int(11) NOT NULL COMMENT "",
  `c_name` varchar(25) NOT NULL COMMENT "",
  `c_address` varchar(40) NOT NULL COMMENT "",
  `c_nationkey` int(11) NOT NULL COMMENT "",
  `c_phone` varchar(15) NOT NULL COMMENT "",
  `c_acctbal` decimal64(15, 2) NOT NULL COMMENT "",
  `c_mktsegment` varchar(10) NOT NULL COMMENT "",
  `c_comment` varchar(117) NOT NULL COMMENT ""
) ENGINE=OLAP
DUPLICATE KEY(`c_custkey`, `c_name`)
COMMENT "OLAP"
DISTRIBUTED BY HASH(`c_comment`, `c_custkey`) BUCKETS 24
PROPERTIES (
"replication_num" = "1",
"in_memory" = "false",
"storage_format" = "DEFAULT"
);

Expected behavior (Required)
finished in several seconds.
Real behavior (Required)
taking Q3 for example:
mysql> set enable_pipeline_engine = false;
Query OK, 0 rows affected (0.05 sec)

mysql> select         l_orderkey,         sum(l_extendedprice * (1 - l_discount)) as revenue,         o_orderdate,         o_shippriority from         customer,         orders,         lineitem where         c_mktsegment = 'AUTOMOBILE'         and c_custkey = o_custkey         and l_orderkey = o_orderkey         and o_orderdate < '1995-03-13'         and l_shipdate > '1995-03-13' group by         l_orderkey,         o_orderdate,         o_shippriority order by         revenue desc,         o_orderdate limit 10;
ERROR 1064 (HY000): Memory of Fragment 4eeaf6e9-e0b0-11ec-8992-4cd98f4b99cf exceed limit.  Used:<PHONE_NUMBER>, Limit:<PHONE_NUMBER>. Mem usage has exceed the limit of single query, You can change the limit by set session variable exec_mem_limit.
mysql> set enable_pipeline_engine = true;
Query OK, 0 rows affected (0.06 sec)

mysql> select         l_orderkey,         sum(l_extendedprice * (1 - l_discount)) as revenue,         o_orderdate,         o_shippriority from         customer,         orders,         lineitem where         c_mktsegment = 'AUTOMOBILE'         and c_custkey = o_custkey         and l_orderkey = o_orderkey         and o_orderdate < '1995-03-13'         and l_shipdate > '1995-03-13' group by         l_orderkey,         o_orderdate,         o_shippriority order by         revenue desc,         o_orderdate limit 10;
+------------+-------------+-------------+----------------+
| l_orderkey | revenue     | o_orderdate | o_shippriority |
+------------+-------------+-------------+----------------+
|   92511430 |<PHONE_NUMBER> | 1995-03-06  |              0 |
|  593851010 |<PHONE_NUMBER> | 1994-12-21  |              0 |
|  188390981 |<PHONE_NUMBER> | 1995-03-11  |              0 |
|  241099140 |<PHONE_NUMBER> | 1995-03-12  |              0 |
|  520521156 |<PHONE_NUMBER> | 1995-03-07  |              0 |
|  160196293 |<PHONE_NUMBER> | 1995-02-13  |              0 |
|  324814597 |<PHONE_NUMBER> | 1995-03-12  |              0 |
|   81011334 |<PHONE_NUMBER> | 1995-03-07  |              0 |
|   88281862 |<PHONE_NUMBER> | 1995-03-03  |              0 |
|   28840519 |<PHONE_NUMBER> | 1995-03-08  |              0 |
+------------+-------------+-------------+----------------+
10 rows in set (21.54 sec)

StarRocks version (Required)
2.2.0

It's pretty fast right now, less than 1 second in 48 cores cluster.


MediaSessionService leak

Media3 Version
Media3 1.0.1
Devices that reproduce the issue
Android emulator API 33
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Not tested
Reproduction steps

Connect MediaController in one process to MediaSession (via MediaSessionService) in another process.
Do some minimal interaction.
Release MediaController.
Wait for MediaSessionService to be destroyed.
Wait a long time to really make sure that Android will give up the Service references. Mash the Android Studio Profiler GC button.
Observe MediaSessionService leaking, via LeakCanary, Android Studio Profiler, and StrictMode setClassInstanceLimit.

Expected result
MediaSessionService garbage collected
Actual result
MediaSessionService leaks. Is this a known leak or expected? If so, is there a workaround? If it's not clear what's going on here I can work on a repro.
It looks like something (Binder-related I assume) is keeping a reference to MediaSessionStub.
====================================
HEAP ANALYSIS RESULT
====================================
1 APPLICATION LEAKS

References underlined with "~~~" are likely causes.
Learn more at https://squ.re/leaks.

5665 bytes retained by leaking objects
Signature: ee46fed2ca31f02081399eeb1f2a47c36a7e8daf
┬───
│ GC Root: Global variable in native code
│
├─ androidx.media3.session.MediaSessionStub instance
│    Leaking: UNKNOWN
│    Retaining 16.5 kB in 252 objects
│    ↓ MediaSessionStub.connectedControllersManager
│                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~
├─ androidx.media3.session.ConnectedControllersManager instance
│    Leaking: UNKNOWN
│    Retaining 15.7 kB in 245 objects
│    ↓ ConnectedControllersManager.sessionImpl
│                                  ~~~~~~~~~~~
├─ androidx.media3.session.MediaSessionImpl instance
│    Leaking: UNKNOWN
│    Retaining 14.6 kB in 221 objects
│    context instance of com.bubenheimer.rucksack.d.CW
│    ↓ MediaSessionImpl.context
│                       ~~~~~~~
╰→ com.bubenheimer.rucksack.d.CW instance
     Leaking: YES (ObjectWatcher was watching this because com.bubenheimer.rucksack.d.CW received Service#onDestroy()
     callback and Service not held by ActivityThread)
     Retaining 5.7 kB in 95 objects
     key = 4ec1a0de-07d9-487f-b346-18fa0fe5c9f5
     watchDurationMillis = 1233
     retainedDurationMillis = 229
     mApplication instance of com.bubenheimer.rucksack.d.D
     mBase instance of android.app.ContextImpl
====================================
0 LIBRARY LEAKS

A Library Leak is a leak caused by a known bug in 3rd party code that you do not have control over.
See https://square.github.io/leakcanary/fundamentals-how-leakcanary-works/#4-categorizing-leaks
====================================
0 UNREACHABLE OBJECTS

An unreachable object is still in memory but LeakCanary could not find a strong reference path
from GC roots.
====================================
METADATA

Please include this in bug reports and Stack Overflow questions.

Build.VERSION.SDK_INT: 33
Build.MANUFACTURER: Google
LeakCanary version: 2.10
App process name: com.bubenheimer.rucksack
Class count: 28631
Instance count: 179207
Primitive array count: 132734
Object array count: 25331
Thread count: 36
Heap total bytes: 27161738
Bitmap count: 0
Bitmap total bytes: 0
Large bitmap count: 0
Large bitmap total bytes: 0
Db 1: open /data/user/0/com.bubenheimer.rucksack/databases/com.google.android.datatransport.events
Db 2: open /data/user/0/com.bubenheimer.rucksack/databases/rucksack-16885692033713938602.db
Stats: LruCache[maxSize=3000,hits=108537,misses=178040,hitRate=37%]
RandomAccess[bytes=9035219,reads=178040,travel=58762959483,range=32300280,size=40283652]
Heap dump reason: 1 retained objects, app is visible
Analysis duration: 25266 ms
Heap dump file path: /storage/emulated/0/Download/leakcanary-com.bubenheimer.rucksack/2023-04-20_12-46-30_323.hprof
Heap dump timestamp:<PHONE_NUMBER>088
Heap dump duration: 4144 ms

Media
N/A
Bug Report

[ ] You will email the zip file produced by adb bugreport to<EMAIL_ADDRESS>after filing this issue.

To be clear: I use a pure MediaSessionService approach, my Manifest does not declare MediaBrowserService, so I'd think that media3 should be expected to handle this cleanly, without baggage from legacy code & requirements.
I have some bound services of my own in the same process as MediaSessionService.
I have verified these behaviors on APIs 33 & 32. UpsideDownCake 34 Beta1 appears to leak all services whatsoever.

Also, I see that the leaking behavior is more significant if there is no significant interaction between MediaController & MediaSession. In this case the MediaSession is torn down when the MediaController calls release(), the MediaSessionService is destroyed and leaks.
In the case where there is more interaction, the MediaSession does not seem to be released upon MediaController.release(), and is reused when a MediaController connects again. May be another bug, or I'm doing something wrong. I thought it would release right away in the case of a pure MediaSessionService, as opposed to when it also supports MediaBrowserService compatibility.

I can reproduce a similar leak that looks slightly different, which I assume is due to differences in the type of controller and/or the interactions caused with it. In any case, fixing the leak I can reproduce affects the same code location your leak above is complaining about, so I'd assume it fixes this as well.

I found a bug in AndroidX code that caused the leak in the "little interaction" case. However, now there is still a somewhat lengthy delay of about 10 seconds from onDestroy() to being finalizable on my MediaSessionService. If I trigger a GC at 11 seconds, it will be finalized, with 10 seconds it won't. Can this be reduced? It tends to trigger spurious leak reports.
I also still don't understand the second case: Why will the MediaSessionService not be destroyed if is there is meaningful interaction prior to releasing the MediaSession?

Thanks for detailed investigations - feels like you found a few interesting edge case bugs in our libraries!
I'd suggest you retry your tests once the Media3 fix is uploaded to GitHub. If there is another (different) leak you can reproduce in Media3 code after including the fix, then please open a new issue. If you see any leaks reported in other libraries (Android system code or androidx.media. packages, then please continue the discussion on the already existing Android bugs. Just pointing this out to make sure we have individual tracking bugs for distinct libraries and we can make sure they are all fixed individually.

Thanks for the fix! I'm not sure how to publish the project artifacts, in particular publishToMavenLocal is not doing anything for me on main branch.

To depend on the latest dev branch, you'd need to checkout the sources and depend on them locally. See https://github.com/androidx/media#locally for details. We are also planning to publish a 1.0.2 release with this fix as the stable 1.1.0 will still be while off.

I'll close this issue under the assumption that it is fixed. If you still see something similar (in media3 code), please reopen or file a new issue.

Thanks. Like I mentioned earlier, depending on media3 project locally fails due to my project's build setup being incompatible with media3. In particular, I use the current AGP 8.0+, and media3 does not. I'd expect this recommendation to not work smoothly in general.
This being a public Github project, it would be desirable to have a way to test out artifacts that's less dependent on requiring me to have a build setup that's compatible with whatever you guys have.

I've validated that the 10 second finalization delay leak is fixed in 1.1.0-alpha01. Yay and thanks!
The problem with the MediaSessionService not reaching onDestroy() after some amount of player interaction is still present. I will create a new issue.


galaxy badge is not earnable.

galaxy badge is not earnable.

Scoring the Galaxy Brain badge is all about showcasing your knowledge and helping others in the discussions. Here's what you need to do: 1. Find the discussions area on the platform. 2. Look for questions from other users where you can provide helpful answers. 3. Do your research and craft clear, informative responses that address their questions directly. 4. Crucially, the user you helped needs to mark your answer as "answered" or similar, acknowledging your assistance. That's it! By providing valuable insights and getting at least two of your answers marked as helpful in public discussions, you'll be well on your way to earning the coveted Galaxy Brain badge.

i Think its not earnable.
im ready to open a PR for it.

i Think its not earnable.
im ready to open a PR for it.

ask the community before opening a PR.

i Think its not earnable.
im ready to open a PR for it.

ask the community before opening a PR.

Im sorry but im confused, what do you mean by ask the community?

Finally I earn Galaxy Brain Badge

Finally I earn Galaxy Brain Badge

how?

Finally I earn Galaxy Brain Badge

how?

Go to the 'Discuss' section of any repository and participate in the Q&A. Remember, in each discussion, only one answer is marked as the correct answer. We need to create two Q&As in the repository and provide answers to those questions.
One more thing: do not try this in your own repository. Instead, try it in the repository of someone who knows about this process. Answer the questions in the Q&A section of their repository's discussions. If the repository owner marks your answers as correct in both Q&As, you will receive the Galaxy Brain badge

I have an idea. If I create 10 Q&As in my repository, and each person answers 1 Q&A each, then, for example, if I create 10 Q&As in the repository's discussion section, each user can answer 2 different Q&As, meaning 5 users in total. All five users will receive the Galaxy Brain badge as soon as I review and mark their answers as correct.
If anyone is interested, let me know. I'll create the Q&As.

I am interested!

Finally I earn Galaxy Brain Badge

how?

See your profile now u have brain galaxy badge 🎉

I'm interested in solving this issue


when will the car get the traffic light data? and some questions about CARLA

Thanks for the open source of CARLA. Here I have some questions about the environment.
Firstly, I am wondering when will the ego-vehicle receive the traffic light information, and can I let the car know the information of the next traffic light instantly when it passed the last intersection?
Another question is what is the code of autopilot in the manual_control.py? I want to learn more about that.
Finally, can I just control the acceleration manually and let the car do other actions automatically? like lane following and stop at an intersection, etc.
Please help out, thank you very much.

The car knows what traffic light it is at when it enters the traffic light's trigger box that is placed a few meters before the intersection.
To enable autopilot, call world.player.set_autopilot(True). This sends a call to the server to tell the vehicle being controlled by the player to use auto-pilot.
You cannot control the acceleration manually when in auto-pilot. Maybe some semi-autopilot mode could be added in the future or you could modify the code and add one if you want.
To see how the auto-pilot functionality is implemented, check the TickAutopilotController function of the AWheeledVehicleAIController class located in the WheeledVehicleAIController.cpp file.

@wattsavolt Thank you so much for your kind and clear reply! Actually, I want to modify a semi-autopilot mode which let the car follow the waypoint automatically and the acceleration and whether to lane change is determined by external input. Is that possible if I don't change the internal C++ file and just use PythonAPI to achieve that?
Thanks a lot！


Proposal: Links: Upgrading the network model

This is a two part proposal. The other portion is at #7468.
Problem
Links currently do not satisfy the needs of users for a couple of reasons:

service discovery suffers from the static nature of linking
links are volatile. ip addresses, port mappings, link names can change as the result of manipulating a link, and other containers are not notified of these changes nor can they trivially deal with these issues.

Solution:
These subjects will be addressed:

fixating containers to resources
essential service discovery changes

Fixating containers to resources
We should guarantee that:

IP addresses should not change between specific container invocations. A container is assigned a specific IP address that will not change until the container is removed, or if stopped and the existing address space is exhausted (in least recently used order of stopped containers).
Likewise, the above should apply to external port mappings.
Changing a link should:

retarget the port mappings
retarget the IP address(es)
rewrite the hosts files (see more on service discovery below) for all linked resources with updated content
Strategies for retargeting (only one will be used for now):

moving the veth to a new network namespace for the target container (via ip link set) from the host, should incur no arp issues. This method still needs to be tested but should provide great failover benefits that we wouldn’t get with ip address reassignment.
reassign the ip to the veth in the target container. This has some arp issues but may be significantly less surprising or complicated to end-users digging through the links abstraction.
Use an iptables facade to mimic a higher level network that links containers. This would be the point of reference, making retargeting these addresses easily. This would use another internal subnet but is rather flexible.

Service Discovery Changes
Service discovery currently relies on two methods of propagating links information: the environment and hosts files. Since the environment is essentially static, and will become outdated, the solution is to rely on hosts files only. A future proposal will bring DNS support to this scheme.
As mentioned above, global rewriting of hosts files will be necessary. This should be done at link change time, unless the container is started with --link.
Port Discovery
Port discovery will be solved in two fashions. Both are subject to further discussion.

The environment will provide DOCKER_LINK_PORT_${link_name}. The value will be a comma separated list of ports.
The environment will provide SRV records to be queried with DNS. The record format will be _${link_name}._${proto} and will respond with multiple port -> A mappings.

Tickets Resolved:
https://github.com/docker/docker/issues/5186
https://github.com/docker/docker/issues/2733
https://github.com/docker/docker/issues/3285
https://github.com/docker/docker/issues/3155
https://github.com/docker/docker/issues/2658
https://github.com/docker/docker/issues/2588 (I think)

Any update on this?

@adamkdean A tremendous amount has happened.
See github.com/docker/libnetwork
This is now being used by Docker, which includes plugins support, as well.
And see: #13441

We should probably close this.


Question about the supplementary video

Thank you for sharing this amazing work!
I watched your supplementary video and surprised by the good quality. i wonder if you predict trajectories for all objects in one calculation or predict each object as target object then combine the results?

@L4zyy Thanks for your comments. In the supplementary video, we just collect all the target vehicles as a batch. The network generates all trajectories in one forward pass. Essentially, the predictions for each vehicle are independent.
I think there may be some methods to make this process more efficient. For example, we can have multiple goal decoders and trajectory decoders, while the encoder part is shared (similar to LaneGCN).

@L4zyy Thanks for your comments. In the supplementary video, we just collect all the target vehicles as a batch. The network generates all trajectories in one forward pass. Essentially, the predictions for each vehicle are independent. I think there may be some methods to make this process more efficient. For example, we can have multiple goal decoders and trajectory decoders, while the encoder part is shared (similar to LaneGCN).

Does "collect all the target vehicles as a batch" means for each target vehicle, you transform all positions to its local coordinates? (If there are 10 vehicles, you will do 10 transformations?)

@L4zyy Exactly, the current model only supports one target vehicle.

Got it. Thank you again for the quick and detailed replies!


Is this project abondoned?

I cannot see any updates since 6 months ago on the related repo on docker hub. Are you still maintaining this project, or I have to switch to another one?

I need to migrate the build process to github actions. I will have time to do it beginning next year.

See #25


CSS Subgrid Firefox 69

See https://trello.com/c/Yo7oH9PY/6-css-grid-subgrid-fx-69 for original trello card
Acceptance criteria

[ ] [css-grid-2] Enable subgrid by default in Nightly (and early beta?) (just BCD update needed, and maybe experimental features?)

So it seems that the change here is to enable subgrid by default (no flag required) in Nightly. I don't think it is shipping in 69 into Firefox, so I don't think there is anything to do given I've already documented the feature.
Unless we have a way to indicate "only in Nightly" in the compat data?

@rachelandrew so for this work, I'd like to:

Add entries for the subgrid value on the grid-template-columns and grid-template-rows ref pages (don't worry about an example yet, maybe just link to the subgrid page you wrote in the grid guides? Also add the value to the /data repo entries for them).
Add a BCD entry for the value, for each of them. You should specify that it is available behind a flag in 69 onwards using a flags field, and perhaps also include a note to say it is enabled by default in Nightly only.
See if the Experimental features entry for Subgrid needs updating at all?

Usually we wouldn't go to quite this much trouble for a feature that is so early on in implementation, but subgrid has a big buzz around it.

BCD PR https://github.com/mdn/browser-compat-data/pull/4657

Data PR https://github.com/mdn/data/pull/382

@chrisdavidmills While doing this I've found a lot of the pages have a polyfill added, which I started to remove, however I note that some also have hidden text referring to https://discourse.mozilla.org/t/mdn-rfc-001-mdn-wiki-pages-shouldnt-be-a-distributor-of-polyfills/24500, so I don't really understand what is going on here? https://developer.mozilla.org/en-US/docs/Web/CSS/grid-column (edit it and you'll see the hidden section).
The person who added this, only seems to have ever made edits in order to add it: https://developer.mozilla.org/en-US/dashboards/revisions?user=motine
I do not think we should be encouraging people to add stuff like this to the pages. As it looks like an endorsement.

Removed the polyfill sections, added a link to the level 2 spec, added subgrid as an allowable value, linked to the subgrid page from grid-template-columns, grid-template-rows. Once the data and BCD shows up that should I think be most things for now.

Nice one Rachel. I've reviewed and merged the data/ updates. So once the BCD is sorted and it all shows up, we can defo close this, yes.


Capacitors increasing the amount of RF produced by Solar 2

So, capacitors should increase the Amount of RF that is produced when you have Solar 2 on your Dark Helm in this order: Basic Capacitor makes that it will produce 128RF/t, Double-Layer 256RF/t and Octadic Capacitor 1024RF/t

This would then produce much more than a normal photo voltaic panel and that on a smaller area - doesn't sound like a balanced idea.

Than we should be able to upgrade them too?

Actually I remembered that the Advanced Solar Panel produces 4RF/t.. so, 12.8;  25.6 and 102.4?

We now have a third tier of solar panel. It produces enough energy for a full set of Ender IO items, so I see no need for action here. When Ender IO is used together with other mods, it's the modpack creater's job to configure the mods to work well together, i.e. to set energy production and usage values into a comparable range. The solar upgrades can be configure that way.
So closing. Feel free to try me to convince to reopen, I'll still be getting notifications for comments here.


Deleting old notes after re-sharing

When re-sharing (either using the drop-down menu on the top right, or the icon in the properties pane), I often get a new URL / ID assigned. But the old link stays active.
This way, the old note remains online without any changes, but there is also no way to delete or revoke this (old) shared note. So there is no way to take it down anymore.
I assume, when re-sharing the link / ID should actually stay the same, so updates will be available after re-sharing for people I already shared the link with.

The link should stay the same when re-sharing a note. I suggest testing in the sandbox vault, in case there is some other plugin affecting this.

@paradeiser did you find out which plugin was causing this issue?

after a lot of trial and error I suspect the Lint setting:
Format Tags in YAML
Remove Hashtags from tags in the YAML frontmatter, as they make the tags there invalid.

as it also removes the hashtag from the share_link value - although it's not within the "tags" section.
I also reported this on https://github.com/platers/obsidian-linter/issues/1155

@paradeiser that will be exactly what the issue is, because it's changing the share link URL from r0w1vdtw to r0w1vdtwgoaVfYU2NExAphdG8oHzVUZ2h8E22JDbJHC5BBEsZPo, which are two very different remote URLs.
Thank you for further investigating that. I'll close this issue as unfortunately there's nothing I can do from my plugin to stop Linter from altering that non-tag frontmatter property.
@cjl12377 - please see above for the solution.

Sorry about the issue here. I believe I have a fix for this in the Linter and it should fix this going forward.


How to fill zeros before problem id in file name?

Cannot find solution in Customize the Relative Folder and the File Name of the Problem File
💬 Questions
The format of my file name is
"filename": "${id}-${kebab-case-name}.${ext}"

Now I want ${id} to be four digits so that the files can be sorted by their IDs on my Github repo.
For example, I click "Show Problem" and generate a file named "1.两数之和.py" and I want it to be "0001.两数之和.py". How can I implement this setting?

See https://github.com/LeetCode-OpenSource/vscode-leetcode/pull/582 maybe add later.


Sophia Unreal Eye mechanic locking camera movement when AI is enabled

When the mechanic starts it does it correctly however after that it locks the camera from moving even after the enemy is dead.
it happened 100% of the time for 4 consecutive pulls.
if AI is disabled while the camera is locked because of the Eye mechanic it returns to normal and reenabling is good to use after without any issues.
are knockbacks mechanics meant to be manually resolved or can AI do them too? wondering if its capable but I assume not at the moment.
Everything else is excellent!! this plugin always amazes me.
Thank you!

Rofl I'm surprised AI is even remotely working on things like Sophia.
I used it when multiboxing early ARR content, modules typically had to provide customized AI hints to make it work - and this is not done for e.g. EW modules.
Someday maybe AI will work in general case, but I don't expect it to happen soon :)


add popup message box on duplicate #52

Hello,
I tried to add the duplicate popup message when you add icon with the same name
I had troubles with modal so I decided to do this native popup, here is how it looks.

The only issue I didn't manage to solve is that the icon does not change after submit, I thought invalidating queries would solve the issue, but it seems to work only after full refresh.

LGTM.
I made some changes so that the icons list is refreshed and shows the updated icon preview

Awesome, that's exactly what I couldn't figure out!


Does not work on Windows

What happened?
I am using Windows (11) and running the example programs does not work. I start the server and run dns-sd -q my-domain.local from another computer (macOS) and expect to receive a response from the Windows machine running the pion mDNS server. But I don't get anything. I see the mDNS packets coming through in Wireshark but the Go program does not seem to get them and therefore does not respond.

Hi @eberkund,
are you still experiencing this issue? If so, have you tried doing this the other way around? I'm asking, because I'd like to understand whether this is solely a Windows issue or whether something else in your setup might be causing these issues. If it is solely a Windows issue, it might be worth double checking the interface bindings of the server. To my knowledge, the pion/mdns server tries to bind to all available network interfaces - see: https://github.com/pion/mdns/blob/04d95eb6db2ae497c22f08cee9e1f0ac63ec9269/conn.go#L60-L65
I currently cannot test on Windows, so I cannot confirm this. However, using two Linux machines works.
Let me know how it goes.
Cheers
Ben
@Sean-Der: Maybe this is related to #93?

I think this was fixed in https://github.com/pion/mdns/commit/bde59ba7419409133f31f611677c24ea6bc36f22

@edaniels, the latest version fixes it. Thanks.

Great! Thanks for testing :)

@edaniels I am seeing a regression after updating to v2

Ah, sorry! Can you describe the regression so I can look into it? We need windows testing

Ah, sorry! Can you describe the regression so I can look into it? We need windows testing

I did a basic investigation with WireShark and the client seems to be working fine. I can see the mDNS queries but the server does not respond back.
Reverting back to 1.x fixed the issue.

Gotcha, I likely broke something, sorry! I'll try to test this in the coming days.

Annoying that it auto closed. @eberkund can you check on v2.0.7?

It works on 2.0.7, thanks!


Just a question

Any plans to set something up for nicovideo.jp?

Not sure, it depends on how many people would use it and what the issues with it are

I see, guessing it's not a popular request judging by your response. Well if you ever feel like looking into it and need data I'll be happy to provide.

First time I've been asked for nicovideo, but if there's enough demand I suppose I could whip something up


How to provide intents to discord.js 13?

Discord.js 13 requires providing intents, but is there way to provide it in GCommandsClient?
D:\Programowanie\Projekty\DiscordBackup\node_modules\discord.js\src\client\Client.js:544
      throw new TypeError('CLIENT_MISSING_INTENTS');
      ^

TypeError [CLIENT_MISSING_INTENTS]: Valid intents must be provided for the Client.
    at GCommandsClient._validateOptions (D:\Programowanie\Projekty\DiscordBackup\node_modules\discord.js\src\client\Client.js:544:13)
    at new Client (D:\Programowanie\Projekty\DiscordBackup\node_modules\discord.js\src\client\Client.js:73:10)
    at new GCommandsClient (D:\Programowanie\Projekty\DiscordBackup\node_modules\gcommands\src\base\GCommandsClient.js:23:9)
    at Object.<anonymous> (D:\Programowanie\Projekty\DiscordBackup\index.js:3:12)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:79:12)
    at node:internal/main/run_main_module:17:47 {
  [Symbol(code)]: 'CLIENT_MISSING_INTENTS'
}

Just pas the intents option in the GCommandsClient
new GCommandsClient({
   intents: [all your intents],
});

You can put discord.js client options in GCommandsClient, but you can also put GCommands options in GCommandsClient. So you just add intents:[etc].
Next time we will be glad if you prefer to go to our discord server Garlic Team for questions.

How to provide all intents without providing them all manually

intents: Object.keys(Intents.FLAGS)

How to provide all intents without providing them all manually

It's bullshit, intents are just to keep the bot from eating your ram unnecessarily.

How to provide all intents without providing them all manually

It's bullshit, intents are just to keep the bot from eating your ram unnecessarily.
For some smaller bots this doesn't make difference


Navigator scene config problem

Version

react-native-router-flux v3.37.0
react-native v0.37.0

Expected behaviour
After this code:
sceneConfig={Navigator.SceneConfigs.FloatFromBottom}
Actual behaviour
my navigator should have other transition. But nothing change:
Here is where i got this: https://facebook.github.io/react-native/docs/navigator.html
Screenshot of code

If you want the animation to come from the bottom up, you can do this:
Scene Setup:
import { Scene, Actions, Modal } from 'react-native-router-flux';
...

<Scene key="modal" component={Modal} >
   <Scene key="root">

<Scene key="currencySearch" title={'My Popup'} component={MyComponent} direction="vertical" />

   </Scene>
</Scene>

Note the direction="vertical" which will cause the animation from bottom.

+1 on this - @ddolheguy 's solution solves from the bottom - but doesn't address the issue that using sceneConfig seems to do nothing...

@getnashty  and @rshmiraf i guess, you need to define Schema itself
 <Schema name="modal" sceneConfig={Navigator.SceneConfigs.FloatFromTop}/> <Schema name="default" sceneConfig={Navigator.SceneConfigs.FloatFromBottom}/>

@sainthardaway - I'm not able to make this work. it seems as though its completely ignored.

Where I put the code with Scene ?

Please add the full code...
I always get the warning: React.createElement type is invalid...


Adding calibration information to SwzDeviceFeed

Discussed in https://github.com/usdot-jpo-ode/wzdx/discussions/262

Originally posted by #benafischer94 March 17, 2022
Proposal
Given that Smart Work Zone Devices, or more generically, ITS devices include some that require
calibration for valid data, e.g.: detection, cameras, various sensors; adding fields for calibration
would make sense.  I would propose something along the lines of the following as an optional field
collection for devices that regularly require calibration.
Initial Proposal for Format
Format is not in full schema formatting, but should provide a basis to kick off the conversation
for further debate around what the fields, and potential acceptable values are. I would caution
against being all encompassing initially, and instead allow a "good enough" approach to be acceptable
as the format evolves and is further used it should naturally lead to full coverage.
{
  "calibration": {
    "last_calibrated" : "datetime+tz",
    "manual_calibration": "boolean",
    "calibrated_by": "Organization that is calibrating rather than individual within an organization",
    "calibration_standard": "url",
    "next_calibration_recommended": "datetime+tz",
    "device_malfunctions": {
      "malfunctions": [
        {
          "malfunction_type": [
            {
              "description": "a grouping of acceptable malfunction types should accompany e.g. 'pan-tilt':'boolean', 'detection':'boolean', 'led:'boolean'",
              "severity": "integer",
            }
          ],
        },
      ],
      "functionality_impacted":[
        {
          "name": "generalize name of functionality",
          "description": "one of an acceptable set of functionalities based on device. e.g: led_out, led_stuck_on, coupled with what is affected"
        }
      ],
      "total_severity": "integer"
    }
  }
}

Rationale
This will allow organizations to determine the reliability of data coming into system. e.g. an auto
manufacturer may require a higher level of confidence in detection devices than a parking lot
operator. Additionally, help assist in keeping operators honest about malfunctions in devices as well
as initial deployment being verified.
A growing number of OEMs are expressing concern of devices being improperly deployed to the field
reducing the actual impact. This leads to safety theater, organizations implementing ITS devices
with no accountability of proper deployment to effectively check a box with contract owners. It
should hopefully help provide a structure for allowing adoption of requirements on calibration of
devices to be properly certified. This could be a multi enforcement effort from OEMs, FHWA, USDOT,
State DOTs, down to municipalities and private operators.
This makes the inclusion of the calibration_standard an important part so that it is clear to installers
and operators what the expected calibration standard is. This should also lead to transparency within
contracts as to what the standards are that are being adhered to for third party validation.
Additionally, this can help lead to further creation of automatic device health-checking capabilities.
e.g: a higher confidence device can be used to provide baseline in corridor detection services.
Field clarification

Last Calibrated: a timestamp of when the device was calibrated. For manual calibrations where technicians
may not be entering the data immediately on the side of the road, the date with zeroed out hours should
be acceptable. For machine based calibration, an exact timestamp makes sense.

Manual Calibration: A true false to determine if human calibrated or done by machine

Calibrated by: The organization doing the calibration and certification. It would be reasonable for
organizations to track the individual doing it, but not to publish the exact individual for all.

Calibration standard: Manufacturer and organizations calibration standards vary, by publishing the
exact standard followed, ambiguity can be eliminated. OEMs should make a linkable version for their
devices that they recommend public for linking and best practice adhesion.

Device malfunctions: Some devices may have multiple capability e.g. a PDMS with detection. The detection
is a secondary function, and could be malfunctioning while the PDMS is still considered good. so an array
to support all possible malfunctions

Malfunction type: A generic set of lists that can be determined across a device of a given type. E.g. LEDs
for PDMS, speed variance for detection.

Severity: A number that can be assigned to the impact of the individual malfunction. Working group
could come up with standard based severity for malfunctions of primary, secondary, and tertiary function
of components on a device of a given type.

Functionality impacted: Some standardized items impact of the specific malfunction to devices. This
can be regardless of primary purpose of the device. An array of impacted functions

Name: Generic name of functionality e.g. message viewability, detection

Description: Generic descriptions to accompany this for reporting what it means to end-users.

Total severity: A total severity for all individual malfunctions. Organizations can make decisions
and set thresholds for usability of data based on the total severity number.

Call To Action
Initial implementation would be optional for all devices to allow a period of adoption, either based
on time or major version revision. This should reduce heartburn associated with making a requirement
for calibration of devices.
Given the high priority and push for devices to be deployed into work zones, making sure that they are
reporting good actionable data should be accompanying this push. Along with the rapid development that
the WZDX has demonstrated, a draft proposal should be possible within a three to six month period.
Justification / Resources
A few examples of systems not working due to failures in comms, calibration, etc. As well as existing
data feeds use verification confidence. The quiet part not always acknowledged out-loud is that the majority
of devices work well when calibrated, but if no one is watching, it gets skipped occasionally. Redeployment
due to changing work zones can exasperate this problem. These sources aren't exhaustive, and there admittedly
is a lot of anecdotal evidence as well. Though there is no shortage of documentation to support improperly
calibrated/deployed devices if individuals request additional it can be presented.

England smart system failure
TPIMS Data Feed specification
Data sources used in RCA

I think this proposal has good intent, but is drilling too deep and not really accommodating most agency users. We need to walk before we run and in my opinion most systems and SWZ specs already require an acceptable level of accuracy for traffic sensors. If devices are not calibrated or out of service or other...they should either not be in the feed or be presented with an error or unknown condition/status. In addition, this would likely have to be manually entered by the provider or agency to populate the feed for this proposal. We believe that as much as possible needs to be automated to allow for success and widespread adoption. If traffic sensor are not providing good data 24/7, then we have a much bigger issue and should not even be providing that associated data. We either trust the date or the spec if not being satisfied and needs to be corrected ASAP. Garbage in-garbage out. Most agencies we do business with do not really care about the maintenance and calibration issues, they just want good data and system performance 24/7 and they have ways to enforce that outside of the WZDx and SWZ Device feeds. We are open to this overall discussion but need to not get caught in the weeds. We are not saying that sensors are perfect all the time, they are not. But is the sensor data representative of the current conditions to an acceptable level? If yes, then let the traffic data flow. If not than let's discuss how to address that in as automated a way as possible. The data must represent the conditions and have integrity, but not be a roadblock to the larger purpose. My two cents.
There’s also another issue that is trying to solve essentially the same problem (verify data integrity) but differently, with a timestamp per value instead of manual checkups: https://github.com/usdot-jpo-ode/wzdx/issues/253. This shows that there’s some kind of need and consumers of the data want to be confident in the data one way or another. I am guessing most data consumers just want to ensure the data is valid, but timestamps alone do not eliminate that potential of invalid data. I know internally we do many other things to ensure data integrity, but I cannot assure you that all data suppliers have the same levels of ensuring data integrity upon deployment and during the entire time in the field. If devices are calibrated and deployed correctly and accepted by an agency, why would we need to include a confidence/calibration value every minute in such a feed? I look forward to the dialogue (especially from active agencies). This may or may not be something we solve this development cycle.

@tfoster-vm , could you elaborate how it fails to accommodate agency users?  Coming from that background, having standardized data formats around data calibration provides more benefits than negatives that I can think of. Having the spec marked as optional for a release or more, allows them to adjust systems to begin using before mandatory status.
The calibration itself, could yes, have to be input manually. Some devices are adding the ability to self-calibrate via implementations of ML algos and the like.  Other devices without such capability, sure they'll need an interface to update.
Regardless, this doesn't stop the feed from automatically updating. Additionally, this gives manufacturers the ability to add business rules such as if device moved more than threshold distance -> mark for calibration. As @rdsheckler mentioned in https://github.com/usdot-jpo-ode/wzdx/discussions/262#discussioncomment-2382057_ this is something others are looking to do regardless. The agencies and researchers I've worked with have always mentioned that more filtering ability is a positive. This gives them an additional criteria for filtering with more granularity than Source->Score applied to all in feed.
Additionally, by the device in the field providing a score that can be used at ingestion time, it provides the OEM the ability to help the Agency develop rules for automatically flagging devices for calibration. We've all been a part of a workzone where a device may be deployed initially and calibrated, then it's moved/turned by a worker for whatever reason. Maybe it gets put back correctly, maybe not. This allows business rules to be developed to help flag this so the agency can charge the device maintainer, or agency staff to return for calibration.
Depending on the TMS exporting the data, they may choose to include all devices in the system. So you end up with both WZ specific devices, as well all permanent ITS devices that exist within a given WZ, or a mixture of both. Ideally the system should be able to track the reliability/calibration of the data. They may also choose to pass through directly the data as presented from the device, or apply additional business rules prior to publishing and giving their mark of approval. This can help reduce the need for Agency staff to login and toggle specific devices as publish/don't publish by generating additional business rules around publish scores.
#253 looks to solve a similar issue, I agree. But there's a difference between a system lagging with good data, and the determination of good/bad data. I foresee the need to support both.

@benafischer94 in general I think the more manual entry there is the less likely it will be utilized. I think most of what you are proposing is manual entry. If I am wrong, please let me know. I suggest we see if there is wider support for this, since the only comments are from the two of us. I will solicit comments at our next subgroup meeting and you can feel to add context or specifics during that meeting.

Closed based on SWZ co-chairs discussion on 2022-09-09.


iree-compile failures with n-D vector.bitcast ops

https://github.com/llvm/llvm-project/commit/137a7451f458cf7d8e1d88df93dbd8da6888886d enables support for n-D arith.trunci narrow type emulation. This causes iree-compile failures in the benchmark suite, so it is reverted in IREE by https://github.com/iree-org/iree/pull/17770.
The compiler failure can be reproduced with these steps:

reapply https://github.com/llvm/llvm-project/commit/137a7451f458cf7d8e1d88df93dbd8da6888886d in third_party/llvm-project
Compile the following IR with iree-compile --output-format=vm-bytecode --mlir-print-op-on-diagnostic=false --iree-hal-target-backends=llvm-cpu --iree-input-type=none --iree-llvmcpu-target-triple=aarch64-none-linux-android29 --iree-opt-data-tiling=true --iree-llvmcpu-enable-ukernels=all --iree-llvmcpu-target-cpu-features=+dotprod --iree-vm-emit-polyglot-zip=true --iree-llvmcpu-debug-symbols=false linalg.mlir -o /tmp/linalg.vmfb:

module @jit_forward {
  util.func public @main(%arg0: !hal.buffer_view) -> !hal.buffer_view attributes {iree.abi.stub, iree.reflection = {iree.abi.declaration = "sync func @main(%input0: tensor<1x256xi8>) -> (%output0: tensor<1x2048xi32>)"}} {
    %cst = arith.constant dense_resource<__elided__> : tensor<256x2048xi4>
    %c0_i32 = arith.constant 0 : i32
    %0 = hal.tensor.import %arg0 "input0" : !hal.buffer_view -> tensor<1x256xi8>
    %collapsed = tensor.collapse_shape %0 [[0, 1]] : tensor<1x256xi8> into tensor<256xi8>
    %1 = tensor.empty() : tensor<2048xi32>
    %2 = linalg.fill ins(%c0_i32 : i32) outs(%1 : tensor<2048xi32>) -> tensor<2048xi32>
    %3 = linalg.vecmat ins(%collapsed, %cst : tensor<256xi8>, tensor<256x2048xi4>) outs(%2 : tensor<2048xi32>) -> tensor<2048xi32>
    %expanded = tensor.expand_shape %3 [[0, 1]] output_shape [1, 2048] : tensor<2048xi32> into tensor<1x2048xi32>
    %4 = hal.tensor.export %expanded "output0" : tensor<1x2048xi32> -> !hal.buffer_view
    util.return %4 : !hal.buffer_view
  }
}

This should cause the error:
error: LLVM Translation failed for operation: builtin.unrealized_conversion_cast
    %3 = linalg.vecmat ins(%collapsed, %cst : tensor<256xi8>, tensor<256x2048xi4>) outs(%2 : tensor<2048xi32>) -> tensor<2048xi32>

cc @banach-space @mub-at-arm this is breaking IREE, so we reverted it on our llvm-project fork. We'll need some help to land it to IREE. Can we revert the upstream commit until it's fixed? I can help provide a repro without IREE specifics.

Sorry, I missed this yesterday (for whatever reason I assumed https://github.com/iree-org/iree/issues/17780 was identical).
For this one it looks like IREE is missing some patterns. Indeed, this worked for me (we need to add populateVectorBitCastLoweringPatterns):
diff --git a/compiler/src/iree/compiler/Codegen/LLVMCPU/ConvertToLLVM.cpp b/compiler/src/iree/compiler/Codegen/LLVMCPU/ConvertToLLVM.cpp
index 22b4ce09a1..60d689d70c 100644
--- a/compiler/src/iree/compiler/Codegen/LLVMCPU/ConvertToLLVM.cpp
+++ b/compiler/src/iree/compiler/Codegen/LLVMCPU/ConvertToLLVM.cpp
@@ -1049,6 +1049,7 @@ void ConvertToLLVMPass::runOnOperation() {
   arith::populateArithToLLVMConversionPatterns(typeConverter, patterns);
   arith::populateExpandBFloat16Patterns(patterns);
   populateVectorToSCFConversionPatterns(patterns);
+  vector::populateVectorBitCastLoweringPatterns(patterns);
   populateVectorToLLVMMatrixConversionPatterns(typeConverter, patterns);
   populateVectorToLLVMConversionPatterns(
       typeConverter, patterns, targetReassociateFpReductions.getValue());
diff --git a/third_party/llvm-project b/third_party/llvm-project
index 8ded6ce55d..c31a6ef9fc 160000
--- a/third_party/llvm-project
+++ b/third_party/llvm-project
@@ -1 +1 @@
-Subproject commit 8ded6ce55deafcad4b78ec814f1ecc80f9889392
+Subproject commit c31a6ef9fca11ff5c662019f8a4d3feac860b24c

I am travelling this week and most of our team is OOO. This is me trying to say - apologies if there's a delay from our side 😅
I prepared a PR for ^^^:

https://github.com/iree-org/iree/pull/17790

Thanks thanks, and sorry for bothering you when you're traveling. I think we can land the change with dropping the local revert LLVM commit. It could need additional permission, so I'll coordinate with the integrator this week. Also, I need to figure out if we can directly add it to EmulateNarrowType pass. It can be done later. Thanks again for looking at this!

sorry for bothering you when you're traveling.

Not at all - this is a work trip, so no excuses :-)


[DEV-2194] change limit request mail

Release Checklist
Pre-Release

[ ] Check migrations

No database related infos (sqldb-xxx)
Impact on GS (new/removed columns)

[ ] Check for linter errors (in PR)
[ ] Test basic user operations

Login/logout
Registration
Update user data
Create/delete payment routes

Post-Release

Test basic user operations
Monitor application insights log

Update env when merging on prd