Problems with the EN_NEXTEVENT Time Parameter

When the API function EN_gettimeparam() is called with the EN_NEXTEVENT parameter it returns the smaller of the hydraulic time step and the shortest time to drain or fill a tank. This, however, does not determine when the true next hydraulic event will occur as it ignores points in time where demands might change or when controls are activated. The companion time parameter EN_NEXTEVENTIDX is used to identify which tank is the controlling one. So if the intent is to simply determine the next time interval for a tank to be full or empty then the parameters should be re-named to something like EN_NEXTTANKEVENT and EN_NEXTTANKEVENTIDX, and not include the possibility of returning the hydraulic time step.
On the other hand, if the intent is to truly identify when the next hydraulic event occurs, then the timestep() function in HYDRAUL.C should be used instead of the tanktimestep() function. However, timestep() and ruletimestep() would have to be modified so as not to actually update tank levels when rule-based controls are evaluated since we don't want a call to EN_gettimeparam() to alter the state of the network.

i would vote for renaming EN_NEXTEVENT to EN_NEXTTANKEVENT as you suggest - it's less invasive and better expresses what is actually being requested.


Only a subset of LaTeX formulas supported?

In our testing, we found the engine unable to render a number of LaTeX formulas. Is only a subset of the LaTeX formula engine currently implemented? Or is it more likely we are using the engine incorrectly or perhaps making a mistake elsewhere?
For example, we were unable to render the following formulas/symbols:
\iff
\iint
\iiint
\dots
\notin
\vdots
\ddots
\nexists
\implies
\idotsint
\idotsint
\mapsto
\ulcorner
\urcorner
\sqsubset
\nsubseteq
\varnothing
\rightleftarrows
{ }
{^n}C_r
\dddot{a}
\ddddot{a}
\textup{A}A
\mathring{a}
1 \tfrac{1}{2}
\int\limits_a^b
\int_a^b \dotsi
A_1\dotso A_N
A_1,A_2,\dotsc,
_{10}^{5}C^{16}
A_1 \dotsm A_N
\left { A \right }
A_1+\dotsb+A_N
\overleftarrow{AB}
\boldsymbol{A}+B
\stackrel\frown{AAA}
1 \mathbf{\tfrac{1}{2}}
\overleftrightarrow{AB}
( \big( \Big( \bigg( \Bigg(
\textrm{z}\textsl{y}\texttt{t}
\frac{d}{dx}e^{ax}=a,e^{ax}
\left{\frac{x^2}{y^3}\right}
\sqrt[n]{1+x+x^2+x^3+\dots+x^n}
2H_2 + O_2 \xrightarrow{n,m}2H_2O
P\left(A=2\middle|\frac{A^2}{B}>4\right)
\sum_{\substack{0<i<m \ 0<j<n }}  P(i, j)
\vec{F}_g=-F\frac{m_1 m_2}{r^2} \vec{e}_r
\int_0^\infty \mathrm{e}^{-x},\mathrm{d}x
A\underset{0}{\overset{a}{\rightleftarrows}}B
\begin{pmatrix} 1 & 0 \ 0 & 1 \end{pmatrix}
A\underset{b}{\overset{a}{\longleftrightarrow}}B
\begin{array}{c|c} 1 & 2 \ \hline 3 & 4 \end{array}
M = \bordermatrix{~ & x & y \cr A & 1 & 0 \cr B & 0 & 1 \cr}
\left(\begin{ array}{c} n \ r \end{array} \right) = \frac{n!}{r!(n-r)!}
A\underset{0^{\circ}C }{\overset{100^{\circ}C}{\rightleftarrows}}B
\begin{pmatrix} a_{11} & \cdots & a_{1n}\  \vdots & \ddots & \vdots\ a_{m1} & \cdots & a_{mn} \end{pmatrix}
\begin{pmatrix} a_{11} & a_{12} & a_{13}\ a_{21} & a_{22} & a_{23}\ a_{31} & a_{32} & a_{33} \end{pmatrix}
f(n) = \begin{cases} n/2 & \quad \text{if } n \text{ is even}\ -(n+1)/2  & \quad \text{if } n \text{ is odd} \end{cases}
\begin{pmatrix} a_{11} & a_{12} & a_{13} & a_{14}\ a_{21} & \hdotsfor{2} & a_{24}\ a_{31} & a_{32} & a_{33} & a_{34}\end{pmatrix}

Hello! Yes, only a subset of full LaTeX markup is supported currently. Right now, I'm working on matrix support (i.e. pmatrix will be supported sooner or later); other samples from your collection will require small pieces of additional work. I would be happy if someone could take the collection, convert it into a unit test set (should be very easy) and started implementing the necessary commands/features.
\begin{} / \end{} environments will require a lot more additional work and I'd suggested to create another issue for them; most of the other stuff is simple enough.
And thanks for your thorough testing, it will help us a lot with the development of the corresponding features!

I'm confused about the suggestion to create another issue for the \begin \end environments, as these seem to be integral to the work you are already doing to support pmatrix. I'm happy to create a separate issue but what differentiates these \begin \end environments in your mind from the matrix work you are doing?

Alright, I'll explain. In my view, \pmatrix is a proper command itself: it requires no additional stuff to work with; it's just a command (that parses its own arguments as it wants). It almost works already in #155.
On the other hand, \begin{matrix} is not just a command: it is a whole world consisting of named environments that behave like commands. There's no single command \begin; there're subcommands (if you wish) \begin{something} and \begin{marix}.
For now, our command/parser system has no place for these environments at all; that's why I think that it deserves its own ticket. It is a separate problem not from the rendering point of view, but a separate problem/world (we have no infrastructure for) from parsing point of view.

Understood. Creating a separate ticket now. Thanks for the explanation!


dev scripts are broken

it is impossible to dev like this
debugging native in xcode is the only thing that now works
all the documented scripts in https://github.com/wix/detox/tree/master/detox
that help develop the JS part are now broken

With new changes to project structure and the usage and lerna, I doubt we need them. I didn't need any of them this week.

Dev scripts are dead. Look in the contribution guide for new instructions.


stories

I want to know "stories", but I can not download it from the link, can you tell me

Click on "here" that's next to stories. Download the tgz file, and you can unzip it.

I want to know "stories", but I can not download it from the link, can you tell me

http://cs.nyu.edu/~kcho/DMQA/


ql plugin: move all families libraries in family directories

Signed-off-by: Alessandro Comodi<EMAIL_ADDRESS>This PR moves all QL family data files to a family directory upon installation.
Before:
/usr/local/share/yosys/quicklogic/pp3_cells_sim.v

After:
/usr/local/share/yosys/quicklogic/pp3/cells_sim.v

cc @lnsharma, @tpagarani, can you please take a look at this PR?


chore(tests): Retry E2E on error

Thanks for submitting a PR! Please check the boxes below:

[x] I have run pre-commit to check linting
[ ] I have added information to docs/ if required so people know about the feature!
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?
[x] I have used a Conventional Commit title for this Pull Request

Changes
After merging this, E2E jobs will retry once on failure.
Hopefully, this will make flaky E2E tests slightly less painful.
How did you test this code?
This is a CI change.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.87%.  Consider uploading reports for the commit 9831634 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3892   +/-   ##
=======================================
  Coverage   95.87%   95.87%
=======================================
  Files        1134     1134
  Lines       36009    36009
=======================================
  Hits        34522    34522
  Misses       1487     1487

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


ReportPreview Avatar should change when settled

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Create a request from userA to userB
UserB should settle the request

Expected Result:

The ReportPreview Avatar should switch to the person who settled

Actual Result:

The ReportPreview Avatar is the person who requested

Please appreciate my fat cat:

Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: v1.3.16-4
Reproducible in staging?: Yes
Reproducible in production?: Yes
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ec9da10b9656eeb9
Upwork Job ID:<PHONE_NUMBER>042917376
Last Price Increase: 2023-05-19

Hey @cristipaval, looks like you're already working on updating the action. Do you want to take this task too? As I think it should be a small addition to your current PR.

yes I can take it

Thanks. I'm still subscribed to the issue if you have any questions.

Update:
This is fixed in Auth in the PR which also updates the report previews when sending money or paying a money request. The PR is still WIP, I hope that it will be ready for review today. I'm going to open an App PR soon to also fix this when the report preview is optimistically created.

Made sure this one was in the issue tracker and project. 👍

Oh, thanks. Must have missed this one in the chaos last week.

On hold for Auth PR #7976 which should be ready soon.

Moving to weekly until the Auth PR is done.

The Auth PR is still in review

Was only just merged: https://github.com/Expensify/Auth/pull/7976#issuecomment-1599082114

This is partially fixed. I am closing it though, because it will be complete when this issue is closed. Working on it.


Build success on Windows (with cmake and mingw)

At first I tried bazel, but it seems its broken with the VS toolchain ( at least in versions 2017+ ).
So cmake it is. For a saner build environment, I use msys2.
msys2 includes a package manager 'pacman' for installing the dev tools and libraries required for building. Ensure you select the mingw variants of golang, gcc, and cmake, or you'll encounter build errors.
You can get a list of packages with: pacman -Ss <package_name>
For the most part, the build went well. It is missing unistd.h's 'pread' , and cc/util/util_test.cc makes use of file permissions not supported by Windows (specifically 'group' and 'other'). Those were the only two issues blocking compilation for me.
I was able to get the aead_cli example working. Here is the CMakeLists.txt I used to build my exe.
cmake_minimum_required(VERSION 3.5)
project(aead_cli CXX)
set(CMAKE_CXX_STANDARD_REQUIRED ON)
set(CMAKE_CXX_STANDARD 14)

add_subdirectory(third_party/tink)
add_subdirectory(util)

add_executable(aead_cli aead_cli.cc)
set(CMAKE_EXE_LINKER_FLAGS "-static-libgcc -static-libstdc++ -static")
target_link_libraries(aead_cli tink::static absl::flags_parse util)

There is an issue with it trying to link in librt on my setup, which doesn't fly for Windows. For the time being, I just delete the -lrt in build.ninja file after running cmake -DCMAKE_GENERATOR=ninja
I created a pull request #660  in case there's any interest by the tink devs.

Hi @dhthwy thanks for looking into this! Have you tried building Tink with -DTINK_BUILD_TESTS=ON and running the unit tests with ctest to check if you patch works?

Nope. But I'll try doing that and provide an update.

Great news. The tests are built.
Do I need to write a script to process them, or is there something already built to run them all?
$ ./tink_test_core_restricted_data_test.exe
Running main() from C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest
/src/gtest_main.cc
[==========] Running 9 tests from 1 test suite.
[----------] Global test environment set-up.
[----------] 9 tests from RestrictedDataTest
[ RUN      ] RestrictedDataTest.CreateAndGetSecret
[       OK ] RestrictedDataTest.CreateAndGetSecret (2 ms)
[ RUN      ] RestrictedDataTest.GenerateRandomAndSize
[       OK ] RestrictedDataTest.GenerateRandomAndSize (0 ms)
[ RUN      ] RestrictedDataTest.GenerateRandomNegative
Running main() from C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest
/src/gtest_main.cc
[       OK ] RestrictedDataTest.GenerateRandomNegative (331 ms)
[ RUN      ] RestrictedDataTest.Equals
[       OK ] RestrictedDataTest.Equals (0 ms)
[ RUN      ] RestrictedDataTest.NotEquals
[       OK ] RestrictedDataTest.NotEquals (0 ms)
[ RUN      ] RestrictedDataTest.CopyConstructor
[       OK ] RestrictedDataTest.CopyConstructor (0 ms)
[ RUN      ] RestrictedDataTest.CopyAssignment
[       OK ] RestrictedDataTest.CopyAssignment (0 ms)
[ RUN      ] RestrictedDataTest.MoveConstructor
[       OK ] RestrictedDataTest.MoveConstructor (0 ms)
[ RUN      ] RestrictedDataTest.MoveAssignment
[       OK ] RestrictedDataTest.MoveAssignment (0 ms)
[----------] 9 tests from RestrictedDataTest (625 ms total)

[----------] Global test environment tear-down
[==========] 9 tests from 1 test suite ran. (749 ms total)
[  PASSED  ] 9 tests.

You can use ctest --rerun-failed --output-on-failure to run them all.

Yeah, sorry, I missed that part. Seems to get hung on test #42, so I force skipped that one for now. Looks like there might be issues with calls to pread. I think that's the reason some tests are failing. I'll look into it further.
 94% tests passed, 14 tests failed out of 222

Total Test time (real) = 774.14 sec

The following tests FAILED:
          1 - tink_test_core_version_test (Failed)
         42 - tink_test_aead__internal_ssl_aead_large_inputs_test (Not Run)
        157 - tink_test_streamingaead_streaming_aead_wrapper_test (Failed)
        158 - tink_test_streamingaead_aes_gcm_hkdf_streaming_key_manager_test (Failed)
        159 - tink_test_streamingaead_aes_ctr_hmac_streaming_key_manager_test (Failed)
        164 - tink_test_streamingaead_decrypting_random_access_stream_test (Failed)
        166 - tink_test_streamingaead_shared_random_access_stream_test (Failed)
        175 - tink_test_subtle_aes_gcm_hkdf_streaming_test (Failed)
        176 - tink_test_subtle_aes_ctr_hmac_streaming_test (Failed)
        199 - tink_test_subtle_decrypting_random_access_stream_test (Failed)
        210 - tink_test_util_file_input_stream_test (Failed)
        211 - tink_test_util_file_output_stream_test (Failed)
        212 - tink_test_util_file_random_access_stream_test (Failed)
        214 - tink_test_util_ostream_output_stream_test (Failed)
Errors while running CTest

Error from pread:
C:/msys64/home/da/projects/app/third_party/tink/cc/streamingaead/aes_ctr_hmac_streaming_key_manager_test.cc:134: Failu
re
Value of: EncryptThenDecrypt(streaming_aead_from_manager_result.value().get(), streaming_aead_direct_result.value().ge
t(), subtle::Random::GetRandomBytes(10000), "some associated data", params.ciphertext_offset)
Expected: is a Status with an OK value
Actual: INTERNAL: Random access decryption failed at position=0 with count=1 and status: INTERNAL: PRead failed with
status: INVALID_ARGUMENT: verification failed (of type crypto::tink::util::Status), INTERNAL: Random access decryptio
n failed at position=0 with count=1 and status: INTERNAL: PRead failed with status: INVALID_ARGUMENT: verification fai
led
Test 1 errors:
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 0 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": '[' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 4 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": ']' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 6 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": '[' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 8 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": ']' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 9 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": '[' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 13 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": ']' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 15 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": '[' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 17 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": ']' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 18 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": '[' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 22 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": ']' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 24 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": '(' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 26 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": '[' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 36 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": ']' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest/src/gtest-port.cc:8
65: Failure
Failed
Syntax error at index 38 in simple regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?": ')' is unsupported.
C:/msys64/home/da/projects/app/third_party/tink/cc/core/version_test.cc:37: Failure
Value of: Version::kTinkVersion
Expected: matches regular expression "[0-9]+[.][0-9]+[.][0-9]+(-[A-Za-z0-9]+)?"
Actual: "1.7.0" (of type char [6])
[  FAILED  ] VersionTest.testVersionFormat (1393 ms)
[----------] 1 test from VersionTest (1402 ms total)
[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (1433 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] VersionTest.testVersionFormat

I was able to make some quick tests on a Windows VM and I found that one of the issues is with the fact that open should open files for read/write as O_BINARY; otherwise the \x1A byte is considered EOF and the read stops. Adding this to all the open calls in cc/util/test_util.cc should make some of these failures go away.

Thanks. You're right.
Now we're left with:
The following tests FAILED:
1 - tink_test_core_version_test (Failed)
42 - tink_test_aead__internal_ssl_aead_large_inputs_test (Not Run)
212 - tink_test_util_file_random_access_stream_test (Failed)
42 takes roughly ~30 secs on my mac m1. I waited > 30 mins on my Windows box with no updates. So I skipped that one.
212 seemingly fails at random. It is also randomly failing on my mac. I just re-ran it again on Windows and it passed.
I haven't looked into '1' yet.

212 is still randomly failing for me on Windows and OSX. I pulled a fresh copy.
@ FileRandomAccessStreamTest.ConcurrentReads
$ time ./tink_test_aead__internal_ssl_aead_large_inputs_test.exe
Running main() from C:/msys64/home/da/projects/app/third_party/tink/__third_party/com_google_googletest/src/googletest
/src/gtest_main.cc
[==========] Running 5 tests from 1 test suite.
[----------] Global test environment set-up.
[----------] 5 tests from SslOneShotAeadLargeInputsTests/SslOneShotAeadLargeInputsTest
[ RUN      ] SslOneShotAeadLargeInputsTests/SslOneShotAeadLargeInputsTest.EncryptDecryptLargeInput/AesGcm256
[       OK ] SslOneShotAeadLargeInputsTests/SslOneShotAeadLargeInputsTest.EncryptDecryptLargeInput/AesGcm256 (173347 m
s)
[ RUN      ] SslOneShotAeadLargeInputsTests/SslOneShotAeadLargeInputsTest.EncryptDecryptLargeInput/AesGcm128
[       OK ] SslOneShotAeadLargeInputsTests/SslOneShotAeadLargeInputsTest.EncryptDecryptLargeInput/AesGcm128 (145109 m
s)
[ RUN      ] SslOneShotAeadLargeInputsTests/SslOneShotAeadLargeInputsTest.EncryptDecryptLargeInput/AesGcmSiv256
[       OK ] SslOneShotAeadLargeInputsTests/SslOneShotAeadLargeInputsTest.EncryptDecryptLargeInput/AesGcmSiv256 (10256
65 ms)
[ RUN      ] SslOneShotAeadLargeInputsTests/SslOneShotAeadLargeInputsTest.EncryptDecryptLargeInput/AesGcmSiv128
[       OK ] SslOneShotAeadLargeInputsTests/SslOneShotAeadLargeInputsTest.EncryptDecryptLargeInput/AesGcmSiv128 (75775
0 ms)
[ RUN      ] SslOneShotAeadLargeInputsTests/SslOneShotAeadLargeInputsTest.EncryptDecryptLargeInput/Xchacha20Poly1305
[       OK ] SslOneShotAeadLargeInputsTests/SslOneShotAeadLargeInputsTest.EncryptDecryptLargeInput/Xchacha20Poly1305 (
51371 ms)
[----------] 5 tests from SslOneShotAeadLargeInputsTests/SslOneShotAeadLargeInputsTest (2153469 ms total)

[----------] Global test environment tear-down
[==========] 5 tests from 1 test suite ran. (2153547 ms total)
[  PASSED  ] 5 tests.

real    35m53.943s
user    0m0.015s
sys     0m0.094s

Old CPU.
Processor:	AMD Phenom(tm) II X4 965 Processor, 3400 Mhz, 4 Core(s), 4 Logical Processor(s)

It's looking for librt in /mingw64/lib, but cmake finds it in /usr/lib
https://github.com/YosysHQ/nextpnr/issues/666

212 is still randomly failing for me on Windows and OSX. I pulled a fresh copy.
@ FileRandomAccessStreamTest.ConcurrentReads

Scratch that. It was using the pread variant in my pull request for some reason, which isn't thread safe due to lseek, causing the random fails for me. My bad, sorry!

For gtest regex fails. It appears when POSIX regex.h isn't available gtest falls back to a less capable regex processor that doesn't support brackets, etc.
There is a library for mingw called 'libsystre' (pacman -Ss libsystre will pull it up) that supposedly provides a compatible POSIX regex to solve this problem.

Hi @dhthwy, we discussed internally and we decided not to merge https://github.com/google/tink/pull/660. We opted for the simpler solution of doing some refactoring to limit POSIX APIs to util/file.*stream.* classes, and simply excluding them from the list of build targets when WIN32. This removes the need for us to port these APIs to Windows and support different build environments. Related to that, we decided not to support msys2 and only focus on MSVC to align with other Google OSS C++ projects (see here). Though I think the changes above would work on msys2 as well.
Thanks a lot for your contribution, it helped me better understand what the delta was to make Tink C++ build on Windows.

Sure. Happy to be of some assistance. Thank you for the update!


shear maps of SDM predictions

Three species with different-looking distributions

is this along the same lines as #8?

It's for Ethan's talk. He wanted maps that looked like the one I posted in #45.  We should be able to close this once that branch gets merged, I think.

(#8 is also covered by #45)

fixed in #77


Added rotation of origin container stack to MovementAnimation.toComponentView calculation.

Closing #212.

Codecov Report

Merging #240 (580cf4e) into dev (61f836b) will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##              dev     #240   +/-   ##
=======================================
  Coverage   12.26%   12.27%
=======================================
  Files         219      219
  Lines        5153     5149    -4
  Branches      863      863
=======================================
  Hits          632      632
+ Misses       4444     4440    -4
  Partials       77       77

Impacted Files
Coverage Δ

...bgw/examples/maumau/view/scenes/MauMauGameScene.kt
0.00% <0.00%> (ø)

...tlin/tools/aqua/bgw/animation/MovementAnimation.kt
0.00% <0.00%> (ø)

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 61f836b...580cf4e. Read the comment docs.


Fix the wrong GroupIdNode output

The output type of GroupIdNode is constructed by the outputGroupingKeyNames, which is stored in map and will be sorted by map key. So when the grouping sets keys are out of order, the output type will be wrong. This PR use int as the key to fix the above wrong output type issue.

@mbasmanova @FelixYBW @rui-mo
Please help to review if you have available time. Thanks for your help!

@JkSelf I'm curious why is this causing a problem. Would you share the use case?

I am working on supporting  GroupId in Gluten. And the result of Q18 in TPC-DS was wrong. Here the grouping keys is n_7, n_8, n_9, n_10, which turn out n_10,  n_7, n_8, n_9 in the output of GroupId.

@mbasmanova  I have resolved the comments and please help to review again. Thanks.

@mbasmanova
In my use case, the ProjectNode comes after GroupIdNode. And we construct the ProjectNode in velox based on the col index of GroupIdNode output. So when the output of GroupIdNode is wrong, the result of ProjectNode will be wrong.

@mbasmanova In my use case, the ProjectNode comes after GroupIdNode. And we construct the ProjectNode in velox based on the col index of GroupIdNode output. So when the output of GroupIdNode is wrong, the result of ProjectNode will be wrong.

I see. Thank you for clarifying. It might be more robust to construct the ProjectNode based on field names in that case.

@mbasmanova Thanks for your timely reply! I have updated your comments. Please help to review again. Thanks!

@JkSelf Would you rebase onto latest main?

Rebased to latest main branch

@JkSelf CI is red. Would you rebase again?

@JkSelf CI is red. Would you rebase again?

Already rebased again. Thanks.


Old Cached credentials in build step trump server creds even when checkbox to override is not set

Problem:

Activate artifactory for a build step
Enter personal credentials
save
Go back, uncheck the "override server credentials" checkbox and save
Build continues to use the cached values to connect to artifactory
Must reenable the override checkbox, clear the two text fields, then uncheck the override checkbox and save to eliminate issue.

also appears the text fields for override credentials autofill, at least in Chrome. I did not put in my TC username and creds but they got auto entered for me.  I believe the override creds were accidentally entered by another admin user.
TeamCity version 8.1.5 build 30240
Plugin version: 2.1.10

Please note related issue logged on JetBrain's site: https://youtrack.jetbrains.com/issue/TW-24293. Appears that indeed credentials get cached and presented to all users opening a security hole.


pretrain with blip2 stage1

1,How to pretrain blip2 stage 1 with multi node multi gpus?
2,dataset sample ratio with multi datasets?
Looking forward to your reply

Same issue. Anyone else figure this out?

@ZhaoyangLi-nju hi guy, did u solve the problem?

@aburns4 same issue. Have you solved the problem

@ZhaoyangLi-nju  Have you solved the problem


[Bug]: Type of input_arg seems incorrect

Bug description
When creating a TomSelect the input_arg is string|TomInput. TomInupt extneds HTMLElement, but that means any type cheker gets angry with a regular HTMLElement For example I get:
[tsl] ERROR in /home/matthew/dev/ce/compiler-explorer/static/panes/cfg-view.ts(172,47)
      TS2345: Argument of type 'HTMLElement' is not assignable to parameter of type 'string | TomInput'.

Expected behavior
I'm not sure - maybe I'm using this wrong but I don't know whether it's OK to ignore this error.
Steps to reproduce
Sorry - couldn't get this to happen injsfiddle (I'm not certain how to get tit to do type checking)
Additional context
Typescript 4.9.5.node v20

Is there a strong argument for using TomSelect on elements other than input
and select?
The TomInput type
https://github.com/orchidjs/tom-select/blob/master/src/types/core.ts#L6
is defined as an HTMLElement with attributes: value, disabled,
validity..etc. It was done this way because the closest common ancestor for
HTMLInputElement and HTMLSelectElement is the HTMLElement type. However,
since HTMLElement doesn't have the value, disabled, or validity attributes
that TomSelect uses, you'll see this error.
On Mon, Oct 30, 2023 at 8:27 PM Matt Godbolt @.***>
wrote:

Bug description
When creating a TomSelect the input_arg is string|TomInput. TomInupt
extneds HTMLElement, but that means any type cheker gets angry with a
regular HTMLElement For example I get:
[tsl] ERROR in /home/matthew/dev/ce/compiler-explorer/static/panes/cfg-view.ts(172,47)
TS2345: Argument of type 'HTMLElement' is not assignable to parameter of type 'string | TomInput'.
Expected behavior
I'm not sure - maybe I'm using this wrong but I don't know whether it's OK
to ignore this error.
Steps to reproduce
Sorry - couldn't get this to happen injsfiddle (I'm not certain how to get
tit to do type checking)
Additional context
Typescript 4.9.5.node v20
—
Reply to this email directly, view it on GitHub
https://github.com/orchidjs/tom-select/issues/648, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH6YRABEV5USPO5AF4IQ3LYCBO2RAVCNFSM6AAAAAA6W6Y55GVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3DSNJRHA2TANA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Are you saying this error

Argument of type 'HTMLElement' is not assignable to parameter of type 'string | TomInput'.

comes after

assert(selector instanceof HTMLSelectElement, '.function-selector is not an HTMLSelectElement');

I just cloned a fresh copy of compiler-explorer, updated tom-select to 2.3.1 and ran npm run ts-check and didn't see any errors.

@oyejorge yes, that error happens after the assert.
I'll try updating to 2.3.1 and if I can get it to repro with that I'll publish full repro steps, else I'll gladly close this! Thank you!

Well: I'm beyond glad to report this is fixed with 2.3.1 and I can't see how it was ever a problem! Thanks @oyejorge for your patience on this! :blush:


[Addition]: Fake location in Madrid (Spain)

Hotspot b58 Addresses
1129bbtTEwLty8vB6qo7RUZxYTYVvn8tuwiE91PTbkVeNkvDpahg
Discord Handle
Guille#3609
Reason(s)
He is faking the location to have scale 1

Cluster offline.


Raspberry Pi 3 model B+ definition

Basically copied the configuration for 4 and updated hardware.deviceTree.filter, which was sufficient to boot to the console for me.

Turns out the default nixos-generate-config-generated config is fine


Update transform.py

Isn't it better to create a mapping suite metadata property that includes just digest for now?


Fixed issue-triage link in community guide

/assign @Bradamant3

@jlumme Thank you! This is a good catch -- but unfortunately, this PR is superseded by #10501, which is needed because the community docs are all moving to the new contributor site, https://contributor.kubernetes.io/


Live server is stopped error appears while atom-ide package is enabled

I can't start live server while atom-ide package is enabled. It's starts and stops immediately.
When I checked the atom's console, I see this:
Exited with code 1
Package: https://atom.io/packages/atom-ide-ui

Ok. It is working again with v2.2.0.


test_file

Hi! I'm very glad to read your codes, but I have a problem, that is how to test my test_file after training.
as you know, Testing a single image in your code.
Especially these two lines of code, if there is a folder test picture, is it necessary to change？
LR_tensor = graph_def.get_tensor_by_name("IteratorGetNext:0")
HR_tensor = graph_def.get_tensor_by_name("NHWC_output:0")
Thanks!

I'm afraid I don't understand your question; could you elaborate on what your 'test_file' would be?


[TASK] Add possibility to use CLOUDSDK_PYTHON var on linux

Until now, the environment variable for an alternative python interpreter ist only used on windows boxes.
This patch applies a similar condition to check for it even when no windows is present.

Any updates?

Checking: Did you sign the CLA agreement? https://cla.developers.google.com/about/google-individual

I did so now. Thx for taking care.


Simplify dependencies

Currently VSDB2 has a dependency to exasol-test-setup-abstraction-java in file pom.xml while the tests are only using ETC.
So the dependency could be replaced by a dependency to exasol-testcontainers.

Will be fixed in https://github.com/exasol/db2-virtual-schema/pull/31


Add Turbolinks(Rails) compatibility

I'm using minigrid in Rails project with Turbolinks.
I realized that minigrid not work the step below.

Access page without .minigrit element. (whole page reload.)
Access page with .minigrid. (not work) (page chage by turbolinks)

but this step works.

Access page with .minigrid (whole page reload). this works well.
Access page without .minigrid. (page chage by turbolinks)
Access page with .minigrid again. this works well.

Anyway, I added Turbolinks page:load event.
Thanks.

ping

Hey @kntmrkm thanks for the PR and sorry about the delay.
I've added a comment to your PR but also would like to question if this is even minigrid's job. Your proposal covers a very specific scenario and could be fixed by adding a more flexible approach for bootstraping the grid. Maybe something like this:
var grid = minigrid(/* ... */);

function doSomethingAsync() {
  // ...
  // Bootstrap the Grid
  grid.initialize();
}

Thoughts? @kntmrkm @henriquea

Hey @kntmrkm sorry for the delay again. I've been sunk at work in the past months.
I agree with @rafaelrinaldi here I don't think this is minigrid's job because it's very specific scenario. We want to keep the API as minimal as possible.

Thanks for reply.
I agree less API idea.
I tried another way. but...
Turbolinks never fire 'load' event (without first rendering and reload.).
If move to page which contain minigrid element by turbolinks.
Then, never invoke below code init(containerEle, itemsNodeList, props);.
if (/webkit/.test(navigator.userAgent.toLowerCase())) {
      window.addEventListener('load', function(){
        init(containerEle, itemsNodeList, props);
      });
    } else {
      window.onload = function() {
        init(containerEle, itemsNodeList, props);
      };
    }

    /*if (typeof(Turbolinks) == 'object') {
      window.addEventListener('page:load', function () {
        init(containerEle, itemsNodeList, props);
      });
    }*/

My code is ...
function doMiniGrid() {
  minigrid({
    container: '.minigrid',
    item: '.minigrid-item',
    gutter: 6
  });
}

function initMiniGrid() {
  if (!(_browser.phone())) {
    doMiniGrid();
    window.addEventListener('resize', function(){
      doMiniGrid();
    });
  }

  $(document).on('page:restore page:load', function() {
    // page:restore => browser back button
    doMiniGrid();
   // I expect page:load event fire minigrid but never invoke.
  });
}

... In the writing this comment
I found one solution.
To use skipWindowOnLoad props.
It works.
I think that without skipWindowOnLoad is best.
If you don't mind.
Cloud you consider accept this PR or another solution without  skipWindowOnLoad.

@kntmrkm yes indeed! This is related with #40. Going to fix this bug this weekend. Thanks for the writeup :)

great thanks!


Implement data validation & default assumptions

Description
Please edit this description with new bullets as you think of them:

[ ] If GraphAssetData.investable is an array of years, investment_cost should also be an array of equal length. (After multi-year investment is implemented.)
[ ] Consistency checks for connections of assets: We shouldn't allow a transport asset to be the charging flow for a storage asset (but double-check).
[ ] Check that all assets have a type associated (i.e., consumer, producer, conversion, storage, hub)
[ ] Check that the flows that are defined as investable are also defined as transport
[ ] If a storage asset has a missing is_seasonal, the default is false (non-seasonal storage).
[ ] Check that units are consistent - either correct or throw a warning/error (this should include euro value year)
[ ] If storage inflows are missing, then assign the default = 0
[ ] Check that if there is a defined initial_storage_level, it must be between the asset's max/min limits. Also, we need to check that if there are max/min profiles, then you must also check that the initial value is between those values.
[ ] Add validation described in #437
[ ] #453

Related Issues
No response

We just discussed adding arguments or options to define the use case instead of relying on the existence or not of specific files. I'm not sure how to translate that into a bullet point. I think it still needs some definition of the main use cases.

Yes the discussion was that we should have the user explicitly specify what "features" they're implementing, so that when we perform validation etc we don't have to guess what they want.
For instance, instead of only relying on cost data being present to activate investing, they have to specify when running the model that they want investment, therefore the model checks for certain parameters needed for that feature. Also if they give cost data without specifying they want investment, the model should give feedback that it's ignoring the cost data.
Depending on how many switches there are, this might be a file. But for now we want to have it as arguments to a function call, with defaults for the "regular" way of running and only specifying to change from the default.


Authentication use case

Hi! I want to use recognito for authentication purposes. However, when you try to authenticate a voice recognito doesnt know it just picks a random entry instead of saying "Voice unrecognized" or something.
I know it's expected behaviour but can you make it reject unrecognized voices somehow?

I would think the threshold depends on your use case. A confidence ratio is returned in the results so you can decide where to put the balance between false positives and false negatives.


HTTP Error 404 on Youtube

Checklist

[x] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2020.09.20
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'https://www.youtube.com/watch\\?v\\=tVZyjLSfETE']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2020.09.20
[debug] Python version 2.7.18rc1 (CPython) - Linux-5.4.0-47-generic-x86_64-with-Ubuntu-20.04-focal
[debug] exe versions: ffmpeg 4.2.4, ffprobe 4.2.4, phantomjs 5, rtmpdump 2.4
[debug] Proxy map: {}
[generic] watch\?v\=tVZyjLSfETE: Requesting header
WARNING: Could not send HEAD request to https://www.youtube.com/watch\?v\=tVZyjLSfETE: HTTP Error 404: Not Found
[generic] watch\?v\=tVZyjLSfETE: Downloading webpage
ERROR: Unable to download webpage: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 632, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2238, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib/python2.7/urllib2.py", line 435, in open
    response = meth(req, response)
  File "/usr/lib/python2.7/urllib2.py", line 548, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python2.7/urllib2.py", line 473, in error
    return self._call_chain(*args)
  File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
    result = func(*args)
  File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

Description

I tried to download a video from Digital Foundry and it didn't work, as I was getting 404 errors each time. I also tried a few other videos with youtube-dl but they did not work as well. The same videos played fine in Firefox.

Invalid URL escaping.


MARP-620 Add release-drafter workflow

This PR adds the Release Drafter workflow to the repository.

Hold on, please don't merge this PR: the master file https://github.com/axonivy-market/github-workflows/blob/v4/.github/workflows/release-drafter.yml has no event workflow-call. So @ndkhanh-axonivy please create a PR to adapt it, then maybe you must change this script to v5 or higher

I think we could also re-use the tag v4  (as we do not introduce any changes for the existing pipelines)
Simply delete the v4 remote tag in github-workflows and re-create it from a commit that contains the release-drafter should be sufficient.


Tests - should be easier to run them towards private calendar servers

Looked through the test framework a bit again, it does have some gotchas making it difficult for anyone else than me to run the tests:

conf_private - any errors in that file, and it will be silently ignored, should probably try and figure out a better way to import from conf_private.  I.e. re-raise the ImportError if file exists but contains syntax errors, import once instead of once per variable and use getattr, etc.
even with "nosetests --verbose" it's not clear what calendar servers are probed
Tests are most likely to break when run towards any server, as almost no servers implement the RFC fully and correctly.  Should try to fix descriptive errors when things break and it's expected that the problem is due to compatibility issues.
Maybe consider to read .config/calendar.conf (in a calendar-cli compatible way)

Related to #117


nixos/boot/systemd-boot: add UEFI Secure Boot via lanzaboote

Description of changes
This introduces a feature preview of UEFI Secure Boot via lanzaboote in nixpkgs.
Depends on #263712 #231951 #263711.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

What's the state of this merge request? We have a discussion about it on https://github.com/NixOS/nixpkgs/pull/324911


Characters & Staff returning empty

An example here is https://api.jikan.moe/v3/anime/11757/characters_staff/
Empty arrays are then returned, this seems to be occurring for all ids, however the data is OCASSIONALLY retrieved and is not consistant.

Duplicate https://github.com/jikan-me/jikan-rest/issues/132
Please track the other issue, thanks!


A eureka client with no archaius

We're removing archaius from spring-cloud-netflix but the eureka client still depends on it.
https://github.com/spring-cloud/spring-cloud-netflix/tree/remove-maint
I know there's archaius2 version, but looking for something pluggable.

Turns out our biggest issue might be here https://github.com/Netflix/eureka/blob/master/eureka-core/src/main/java/com/netflix/eureka/util/StatusInfo.java#L71-L72. It prevents the eureka console from displaying properly.
Since we have our own config instances, many of the amazon specific classes that used archaius are used in those classes.

See https://github.com/spring-cloud/spring-cloud-netflix/pull/3746


Has anyone tried setting this up for multiple users?

This isn't so much an issue as a question for others that may have implemented AnythingLLM for multiple people (or this may become an enhancement request if there's no good, easy, and inexpensive way to do it).
I essentially want to be able to run this remotely on AWS but potentially have multiple users access it. Is the only way to do this without users stepping on each others' toes, to set up a separate AWS instance for each one? Or, perhaps create a separate workspace and each user sticks to their own workspace?
I'm just curious if others have attempted to do such a thing and what the best way might be to give this a whirl.

Multiple user support is coming soon on the roadmap that will be published this week.
This will be native in the app for specifically cloud-hosted users who will have their own logins and workspaces they are allowed to access and/or create.

awesome to hear, @timothycarambat. I can't seem to find a current roadmap and don't want to miss the posting. Where will it be posted exactly?
Also, do you have a Patreon or some sort of way to chip in for this? I really like the work you've done so far and want to do a small monthly contribution to help keep up the amazing work.

@AlexanderMoen The roadmap is planning to be published tomorrow evening PST since we are working on it currently!
Appreciate the thought of a donation a ton, right now nothing is set up so just the vocalized support will have to suffice 😄

moved to #115


Feature: --rustfmt output.

Adds a new flag ‘-r’ ‘--rustfmt’ that pretty-prints the generated rust output with the rustfmt library. This makes the output human readable and easy to compile.

Presumably if merged, there would need to be README/doc updates. I'm using it as svd2rust -r -i somefile.svd > $halcrate/src/lib.rs which then builds fine with cargo build.

Thanks for the PR, @archaelus.
I feel that adding rustfmt right now is more of a disadvantage than an advantage. For one, rustfmt is still undergoing development and new options are being added to it as part of the RFC process to define the default / official Rust style. That means that if we depend on rustfmt right now we would have to bump svd2rust everytime rustfmt has a new release; otherwise, people would still have to run (a more updated) rustfmt on the svd2rust output. OTOH, the advantage of this PR is that you don't have to install or run rustfmt but people are likely to already have rustfmt installed as they probably use it for others projects and, in the future, it's likely that rustfmt will become part of the "Rust platform" distribution so it will be installed by default along with rustc and the RLS. As for not having to rustfmt yourself, I don't see much advantage to that since it's easy to pipe svd2rust to rustfmt so you only save yourself some keystrokes on a not too common operation.
Thanks again but I won't take this PR. We can reevaluate once rustfmt hits version 1.0 and the default style has been decided.

That sounds fair and reasonable - thanks for explaining.
To make a pitch for something like this as a future addition to svd2rust, it was surprising to me initially that there was an expected post-processing step - rust code that you would commit to a hardware crate is probably a default that many people will expect. One other point in favour of integration is that if you need any changes from rustfmt's defaults (using it as a library I needed to tweak a couple of things like line length not being a hard error), then integration is going to save people having to rediscover that independently and setup a rustfmt config file.


Maintenance updates

Ruby v3.3 in test matrix; version updates for gems via gemspec.

Diif looks good to go & tests all passing now -> Merging.


Enforce Protection Mode

In the doc it states, 'Enforce protection mode is disabled until further notice.' When will we have an update on this? It's not a useful feature unless we can actually enforce our controls.

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

ID: 8d5df7a3-8abc-026a-7bee-2861ba4a2e38
Version Independent ID: 9c91b1ee-7874-a992-4e52-c621e914da08
Content: Adaptive application controls in Azure Security Center
Content Source: articles/security-center/security-center-adaptive-application.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@jzuchora87 Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

Enforcement mode is due to be reenabled within the coming few months.
Thanks for the feedback. If you have any further questions, please feel free to contact us again.
#please-close


injection not working

try {
var Spooky = require('spooky');
} catch (e) {
var Spooky = require('../lib/spooky');
}
var spooky = new Spooky({
child: {
transport: 'http'
},
casper: {
logLevel: 'debug',
verbose: true,
clientScripts: ["abc.js"]
}
}, function (err) {
if (err) {
e = new Error('Failed to initialize SpookyJS');
e.details = err;
throw e;
}
spooky.start("http://www.google.com");

spooky.then(function(){
    this.evaluate(function() {
        console.log("testing");
        var x = abc.check();
        console.log("x: "+x);
    });
});

spooky.run();

});
spooky.on('error', function (e, stack) {
console.error(e);
if (stack) {
console.log(stack);
}
});
spooky.on('console', function (line) {
console.log(line);
});
spooky.on('remote.message', function(message) {
console.log('[Inside Evaluate] ' + message);
});
The value of X doesn't get displayed

[info] [phantom] Starting...
[info] [phantom] Running suite: 3 steps
[debug] [phantom] opening url: https://www.google.com/, HTTP GET
[debug] [phantom] Navigation requested: url=https://www.google.com/, type=Other, willNavigate=true, isMainFrame=true
[debug] [phantom] Navigation requested: url=https://www.google.co.in/?gfe_rd=cr&ei=ZIXqVvXoGuHI8AeX06uYAg, type=Other, willNavigate=true, isMainFrame=true
[debug] [phantom] url changed to "https://www.google.co.in/?gfe_rd=cr&ei=ZIXqVvXoGuHI8AeX06uYAg"
[debug] [phantom] Automatically injected /Users/BitBucket/headless_browser/abc.js client side
[debug] [phantom] Successfully injected Casper client-side utilities
[debug] [phantom] start page is loaded
[info] [phantom] Step anonymous 3/3 https://www.google.co.in/?gfe_rd=cr&ei=ZIXqVvXoGuHI8AeX06uYAg (HTTP 200)
end of
[info] [phantom] Step anonymous 3/3: done in 1037ms.
remote message caught: in eval
[info] [phantom] Done 3 steps in 1055ms
This is the output

I have tried entering the absolute file also.

Looks like you have got your abc.js injected successfully...
I think path to a script is relative to where casperjs is located. So, if your casperJS is installed locally in node_module folder of your project and abc.js is located at root of your project, using './abc.js' will work. It is how I include jQuery into casperJS instance.


add_TriviaQA_Benchmark

🤔 Reasoning
This was an assigned issue about adding TriviaQA benchmark.
🚧 Changes
Added TriviaQA instruction and few-shots examples in prompts/react. Created a temporary notebook for testing.
✅ PR Checklist

[✔] Using this PR template?
[✔] Linked issue?
[✔] Added feature?

[✔] Added/updated docs?
[✔] Added/updated tests?

Prompts link: https://arxiv.org/pdf/1705.03551 (TriviaQA)
https://arxiv.org/pdf/1705.03551 (Critic)


python310Packages.govee-ble: 0.19.1 -> 0.20.0

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 206926 run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.govee_ble

3 packages built:

home-assistant-component-tests.tilt_ble
python310Packages.govee-ble
python39Packages.govee-ble


HTTP notifier json api support with the injection of the disruption inside the payload of the callback request

What does this PR do?

[ ] Adds new functionality
[x] Alters existing functionality
[ ] Fixes a bug
[ ] Improves documentation or testing

Please briefly describe your changes as well as the motivation behind them:

Add the serialized disruption field inside the payload of the HTTP request
Normalize the HTTP request body with jsonapi

Example of a request sent by the HTTP notifier:
{
    "data": {
        "type": "http_notifier_events",
        "id": "37da196f-c355-4251-9785-69247fce0wdf",
        "attributes": {
            "cluster": "lama",
            "disruption": "{\"kind\":\"Disruption\",\"apiVersion\":\"chaos.datadoghq.com/v1beta1\",\"metadata\":{\"name\":\"network-drop\",\"namespace\":\"chaos-demo\",\"uid\":\"37da196f-c355-4251-9785-69247fce0cdf\",\"resourceVersion\":\"1697329\",\"generation\":1,\"creationTimestamp\":\"2024-04-23T11:40:41Z\",\"annotations\":{\"SpanContext\":\"{\\\"traceparent\\\":\\\"00-00000000000000002f2ab245feb7fd18-2f2ab245feb7fd18-01\\\",\\\"tracestate\\\":\\\"dd=s:1;t.dm:-1\\\"}\",\"UserInfo\":\"{\\\"username\\\":\\\"system:admin\\\",\\\"groups\\\":[\\\"system:masters\\\",\\\"system:authenticated\\\"]}\",\"kubectl.kubernetes.io/last-applied-configuration\":\"{\\\"apiVersion\\\":\\\"chaos.datadoghq.com/v1beta1\\\",\\\"kind\\\":\\\"Disruption\\\",\\\"metadata\\\":{\\\"annotations\\\":{},\\\"name\\\":\\\"network-drop\\\",\\\"namespace\\\":\\\"chaos-demo\\\"},\\\"spec\\\":{\\\"count\\\":\\\"100%\\\",\\\"level\\\":\\\"pod\\\",\\\"network\\\":{\\\"drop\\\":100},\\\"selector\\\":{\\\"app\\\":\\\"demo-curl\\\"}}}\\n\"},\"finalizers\":[\"finalizer.chaos.datadoghq.com\"],\"managedFields\":[{\"manager\":\"kubectl-client-side-apply\",\"operation\":\"Update\",\"apiVersion\":\"chaos.datadoghq.com/v1beta1\",\"time\":\"2024-04-23T11:40:41Z\",\"fieldsType\":\"FieldsV1\",\"fieldsV1\":{\"f:metadata\":{\"f:annotations\":{\".\":{},\"f:kubectl.kubernetes.io/last-applied-configuration\":{}}},\"f:spec\":{\".\":{},\"f:count\":{},\"f:level\":{},\"f:network\":{\".\":{},\"f:drop\":{}},\"f:selector\":{\".\":{},\"f:app\":{}}}}},{\"manager\":\"manager\",\"operation\":\"Update\",\"apiVersion\":\"chaos.datadoghq.com/v1beta1\",\"time\":\"2024-04-23T11:40:42Z\",\"fieldsType\":\"FieldsV1\",\"fieldsV1\":{\"f:metadata\":{\"f:finalizers\":{\".\":{},\"v:\\\"finalizer.chaos.datadoghq.com\\\"\":{}}}}},{\"manager\":\"manager\",\"operation\":\"Update\",\"apiVersion\":\"chaos.datadoghq.com/v1beta1\",\"time\":\"2024-04-23T11:40:42Z\",\"fieldsType\":\"FieldsV1\",\"fieldsV1\":{\"f:status\":{\".\":{},\"f:desiredTargetsCount\":{},\"f:ignoredTargetsCount\":{},\"f:injectedTargetsCount\":{},\"f:injectionStatus\":{},\"f:selectedTargetsCount\":{},\"f:targetInjections\":{\".\":{},\"f:demo-curl-bcff97d44-vbhl7\":{\".\":{},\"f:network-disruption\":{\".\":{},\"f:injectionStatus\":{}}}}}},\"subresource\":\"status\"}]},\"spec\":{\"count\":\"100%\",\"selector\":{\"app\":\"demo-curl\"},\"triggers\":{\"inject\":{\"notBefore\":null},\"createPods\":{\"notBefore\":null}},\"duration\":\"1h0m0s\",\"level\":\"pod\",\"network\":{\"drop\":100}},\"status\":{\"injectionStatus\":\"NotInjected\",\"targetInjections\":{\"demo-curl-bcff97d44-vbhl7\":{\"network-disruption\":{\"injectionStatus\":\"NotInjected\",\"since\":null}}},\"selectedTargetsCount\":1,\"ignoredTargetsCount\":0,\"injectedTargetsCount\":0,\"desiredTargetsCount\":1}}",
            "disruption_name": "network-drop",
            "event_message": "Disruption 'network-drop' emitted the event ChaosPodCreated: Created disruption injection pod for \"network-drop\"",
            "involved_object_kind": "Disruption",
            "namespace": "chaos-demo",
            "notification_title": "Disruption 'network-drop' received a notification.",
            "notification_type": "Info",
            "targets_count": 1,
            "timestamp":<PHONE_NUMBER>047144026
        }
    }
}

Code Quality Checklist

[x] The documentation is up to date.
[ ] My code is sufficiently commented and passes continuous integration checks.
[x] I have signed my commit (see Contributing Docs).

Testing

[ ] I leveraged continuous integration testing

[ ] by depending on existing unit tests or end-to-end tests.
[ ] by adding new unit tests or end-to-end tests.

[x] I manually tested the following steps:

x
[x] locally.
[x] staging
[ ] as a canary deployment to a cluster.

That seems possible. Could you give more explanation of what you're hoping for? Right now we do include the entire disruption object, along with the status, which includes all injector names + targets

We're building a web interface with the ability to launch experiments and it would be nice to have realtime update notifications of the experiment and injector pods as it's ongoing~ More or less having data of what was added / updated would help prevent needing to statefully track and analyze the disruption object and injector names / targets when a new target pod comes online (or goes away) during an experiment.  In the current example state, we'll be told that a new disruption pod was created, but then it's up to us to determine which one is new/came online;
However, with all of that said, I suppose maybe a different 'type' of message such as "involved_object_kind": "InjectorPod" with an update of just that one injector pod update might be a better approach (sadly much more work).

We're building a web interface with the ability to launch experiments and it would be nice to have realtime update notifications of the experiment and injector pods as it's ongoing~ More or less having data of what was added / updated would help prevent needing to statefully track and analyze the disruption object and injector names / targets when a new target pod comes online (or goes away) during an experiment. In the current example state, we'll be told that a new disruption pod was created, but then it's up to us to determine which one is new/came online;
However, with all of that said, I suppose maybe a different 'type' of message such as "involved_object_kind": "InjectorPod" with an update of just that one injector pod update might be a better approach (sadly much more work).

hmm. I think I understand. We're finding it simpler to send the entire body of the latest object + status so that the consumer of these notifications is never dealing with partial data. For individual notifications, we've been using the slack notifier.


Rpi docker image

To run on RPI's duh

Codecov Report

Merging #64 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #64   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           8      8
  Lines         167    167
=====================================
  Hits          167    167

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 1d1cf3b...a1bd645. Read the comment docs.


Kaiwa npm install fails

Hello
With a fully up to date npm, kaiwa fails with the following error-
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Linux 2.6.32-042stab108.2
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/garrett/kaiwa/node_modules/LDAP
gyp ERR! node -v v0.12.7
gyp ERR! node-gyp -v v2.0.1
gyp ERR! not ok
npm ERR! Linux 2.6.32-042stab108.2
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.7
npm ERR! npm  v3.1.0
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the LDAP package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls LDAP
npm ERR! There is likely additional logging output above.

I tried installing openldap as suggested on here, but it failed in the same way. Link to the fail log-
http://pastebin.com/raw.php?i=mq2G5nse
I would really like to try out kaiwa as it looks great, so any advice would be appreciated.

Figured it out, run the following script to install kaiwa-
#!/bin/bash
sudo apt-get install git libldap2-dev uuid-dev nodejs nodejs-legacy npm -y
cd ~
git clone https://github.com/digicoop/kaiwa.git
cd kaiwa
npm install
node server

Could you send in a pull request for to update the readme with the packages needed?


feat(controller): Sum resources duration for DAGs and steps

Checklist:

[x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[x] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[x] I've signed the CLA.
[x] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
[ ] My builds are green. Try syncing with master if they are not.
[x] My organization is added to USERS.md.

Related to #3864

@JPZ13  can you try argoproj/workflow-controller:res-dur please?

@alexec Will do

@alexec Code looks really good - my only question is about a nested case. I'm not seeing the parent resources duration be the sum of the children. Is that expected? Here's my output for the ./tests/e2e/functional/dag-nested.yaml run:
Name:                dag-nested-4xx2m
Namespace:           argo
ServiceAccount:      default
Status:              Succeeded
Conditions:
 Completed           True
Created:             Mon Sep 21 16:28:48 -0400 (2 minutes ago)
Started:             Mon Sep 21 16:28:48 -0400 (2 minutes ago)
Finished:            Mon Sep 21 16:29:52 -0400 (1 minute ago)
Duration:            1 minute 4 seconds
ResourcesDuration:   2s*(1 cpu),1s*(100Mi memory)

STEP                 TEMPLATE        PODNAME                      DURATION  ARTIFACTS  MESSAGE  RESOURCESDURATION             NODENAME
 ✔ dag-nested-4xx2m  diamond                                                                    1s*(1 cpu),0s*(100Mi memory)
 ├-✔ A               nested-diamond                                                             1s*(1 cpu),0s*(100Mi memory)
 | ├-✔ A             echo            dag-nested-4xx2m-2908879225  3s        main-logs           1s*(1 cpu),0s*(100Mi memory)  docker-desktop
 | ├-✔ B             echo            dag-nested-4xx2m-2858546368  6s        main-logs           3s*(1 cpu),1s*(100Mi memory)  docker-desktop
 | ├-✔ C             echo            dag-nested-4xx2m-2875323987  6s        main-logs           3s*(1 cpu),1s*(100Mi memory)  docker-desktop
 | └-✔ D             echo            dag-nested-4xx2m-2959212082  3s        main-logs           2s*(1 cpu),1s*(100Mi memory)  docker-desktop
 ├-✔ B               nested-diamond                                                             2s*(1 cpu),1s*(100Mi memory)
 | ├-✔ A             echo            dag-nested-4xx2m-1211952452  5s        main-logs           1s*(100Mi memory),2s*(1 cpu)  docker-desktop
 | ├-✔ B             echo            dag-nested-4xx2m-1262285309  10s       main-logs           5s*(1 cpu),3s*(100Mi memory)  docker-desktop
 | ├-✔ C             echo            dag-nested-4xx2m-1245507690  9s        main-logs           4s*(1 cpu),2s*(100Mi memory)  docker-desktop
 | └-✔ D             echo            dag-nested-4xx2m-1161619595  6s        main-logs           2s*(1 cpu),1s*(100Mi memory)  docker-desktop
 ├-✔ C               nested-diamond                                                             3s*(1 cpu),1s*(100Mi memory)
 | ├-✔ A             echo            dag-nested-4xx2m-3799189731  6s        main-logs           3s*(1 cpu),1s*(100Mi memory)  docker-desktop
 | ├-✔ B             echo            dag-nested-4xx2m-3815967350  9s        main-logs           4s*(1 cpu),2s*(100Mi memory)  docker-desktop
 | ├-✔ C             echo            dag-nested-4xx2m-3832744969  10s       main-logs           4s*(1 cpu),2s*(100Mi memory)  docker-desktop
 | └-✔ D             echo            dag-nested-4xx2m-3849522588  7s        main-logs           1s*(100Mi memory),3s*(1 cpu)  docker-desktop
 └-✔ D               nested-diamond                                                             1s*(1 cpu),0s*(100Mi memory)
   ├-✔ A             echo            dag-nested-4xx2m-4249798190  3s        main-logs           1s*(1 cpu),0s*(100Mi memory)  docker-desktop
   ├-✔ B             echo            dag-nested-4xx2m-4233020571  6s        main-logs           4s*(1 cpu),2s*(100Mi memory)  docker-desktop
   ├-✔ C             echo            dag-nested-4xx2m-4216242952  5s        main-logs           3s*(1 cpu),2s*(100Mi memory)  docker-desktop
   └-✔ D             echo            dag-nested-4xx2m-38718989    4s        main-logs           2s*(1 cpu),1s*(100Mi memory)  docker-desktop

I'm not seeing the parent resources duration be the sum of the children. Is that expected?

Not at all. That is a bug. I'll investigate.

It is a zero-day bug.

Damn. Is there anything I can do to be helpful with on that? I don't have the context of the bug or nearly the same depth of knowledge of the codebase as you, but I'm happy to help run test cases or do anything you need for the next couple hours

It is a zero-day bug.

I'm actually not sure it is a bug now. A misunderstand of how something works.

Algo v2. It was a very interesting challenge iterating over the graph and summing up child nodes. @JPZ13 , this is not actually what I expected (the CLI layout is very different to the UI), so it makes the values look wrong.
Name:                dag-nested-bm4zp
Namespace:           argo
ServiceAccount:      default
Status:              Succeeded
Conditions:
 Completed           True
Created:             Tue Sep 22 08:12:36 -0700 (4 minutes ago)
Started:             Tue Sep 22 08:12:36 -0700 (4 minutes ago)
Finished:            Tue Sep 22 08:13:14 -0700 (3 minutes ago)
Duration:            38 seconds
ResourcesDuration:   23s*(1 cpu),7s*(100Mi memory)

STEP                 TEMPLATE        PODNAME                      DURATION  ARTIFACTS  MESSAGE  RESOURCESDURATION              NODENAME
 ✔ dag-nested-bm4zp  diamond                                                                    23s*(1 cpu),7s*(100Mi memory)
 ├-✔ A               nested-diamond                                                             23s*(1 cpu),7s*(100Mi memory)
 | ├-✔ A             echo            dag-nested-bm4zp-2090476449  2s        main-logs           1s*(1 cpu),0s*(100Mi memory)   k3d-k3s-default-server
 | ├-✔ B             echo            dag-nested-bm4zp-2040143592  1s        main-logs           0s*(1 cpu),0s*(100Mi memory)   k3d-k3s-default-server
 | ├-✔ C             echo            dag-nested-bm4zp-2056921211  2s        main-logs           1s*(1 cpu),0s*(100Mi memory)   k3d-k3s-default-server
 | └-✔ D             echo            dag-nested-bm4zp-2140809306  1s        main-logs           0s*(1 cpu),0s*(100Mi memory)   k3d-k3s-default-server
 ├-✔ B               nested-diamond                                                             17s*(1 cpu),7s*(100Mi memory)
 | ├-✔ A             echo            dag-nested-bm4zp-1462094412  2s        main-logs           1s*(1 cpu),0s*(100Mi memory)   k3d-k3s-default-server
 | ├-✔ B             echo            dag-nested-bm4zp-1512427269  2s        main-logs           1s*(1 cpu),0s*(100Mi memory)   k3d-k3s-default-server
 | ├-✔ C             echo            dag-nested-bm4zp-1495649650  2s        main-logs           1s*(1 cpu),0s*(100Mi memory)   k3d-k3s-default-server
 | └-✔ D             echo            dag-nested-bm4zp-1411761555  2s        main-logs           1s*(1 cpu),0s*(100Mi memory)   k3d-k3s-default-server
 ├-✔ C               nested-diamond                                                             17s*(1 cpu),7s*(100Mi memory)
 | ├-✔ A             echo            dag-nested-bm4zp-854040075   2s        main-logs           1s*(1 cpu),0s*(100Mi memory)   k3d-k3s-default-server
 | ├-✔ B             echo            dag-nested-bm4zp-870817694   2s        main-logs           1s*(1 cpu),0s*(100Mi memory)   k3d-k3s-default-server
 | ├-✔ C             echo            dag-nested-bm4zp-887595313   2s        main-logs           1s*(1 cpu),0s*(100Mi memory)   k3d-k3s-default-server
 | └-✔ D             echo            dag-nested-bm4zp-904372932   2s        main-logs           0s*(100Mi memory),1s*(1 cpu)   k3d-k3s-default-server
 └-✔ D               nested-diamond                                                             13s*(1 cpu),7s*(100Mi memory)
   ├-✔ A             echo            dag-nested-bm4zp-2373193270  8s        main-logs           7s*(1 cpu),4s*(100Mi memory)   k3d-k3s-default-server
   ├-✔ B             echo            dag-nested-bm4zp-2356415651  3s        main-logs           2s*(1 cpu),1s*(100Mi memory)   k3d-k3s-default-server
   ├-✔ C             echo            dag-nested-bm4zp-2339638032  3s        main-logs           2s*(1 cpu),1s*(100Mi memory)   k3d-k3s-default-server
   └-✔ D             echo            dag-nested-bm4zp-2457081365  2s        main-logs           2s*(1 cpu),1s*(100Mi memory)   k3d-k3s-default-server

@alexec Makes sense - the UI view definitely makes it clearer that the resources duration for the A DAG should contain the sums of the B, C, and D DAGs as well

Re-run jobs.


[Bug]: Duplicate CSS Styles and Unconverted Tailwind Identifiers on Official Website

Version
https://rspress.dev/

Details
I've noticed an issue on the official website where the same CSS styles are being included twice.
it appears that some Tailwind identifiers within the CSS have not been converted.

Reproduce link
https://rspress.dev/
Reproduce Steps

visit https://rspress.dev/
open chrome devtools
search css selector .menu

I have investigated this issue. The cause is still unknown.
Reproduction environment

My research environment is rspress version: 1.10.1
This problem is reproduced only with rspress monorepo

The official rspress site is in packages/document. So the problem is happening on the official site
Reproduce in dev,prod

pnpm dev:website
pnpm build:website

Reproduce with chrome,safari,firefox

Problem Details
import './vars.css';
import './base.css';
import './code.css';
import './scrollbar.css';

The contents of packages/theme-default/src/styles/index.ts is bundled twice.
/*
This is the built index.css
The middle part is omitted. Only .menu is written.
 */
/* src/styles/base.css */

.menu {
  display: flex;
  align-items: center;
  justify-content: space-around;
  font-size: 0.875rem;
  line-height: 1.25rem;
  font-weight: 700;
}

/* #region "../theme-default/src/styles/base.css" */
.menu {
  @apply flex justify-around items-center text-sm font-bold;
}

The first time, the tailwind is built correctly.
The second time, the tailwind is not built and is output as is. So, the apply syntax is output to index.hash.css as it is.
Suspected cause
There could be a problem caused by monorepo, I checked the Modern.js configuration file and I couldn't find the problem for me.

Hi @naoyashiga ,
Thank you for bringing this issue to our attention. I've discovered a potential cause for the problem.
The CSS is being imported twice.

The first import is from packages/theme-default/dist/bundle.css, which does not include the tailwindcss @apply directive.
The second import is from the source file package/theme-default/src/styles/index.ts, which does include the tailwindcss @apply.

Since the document does not have any handling for tailwindcss directives, the second import is loaded as is.
This second import is due to the paths configuration in packages/document/tsconfig.json.
Unfortunately, I have not yet found a good solution to this configuration issue. I will continue to investigate and update you as soon as I have more information.

Thank you for your attention and thought about the style issue. Here i can explain why the style is imported twice.
In packages/document/tsconfig, we set the paths:
{
  'rspress/theme': '../theme-default/src/index.ts'
}

It aims to compile the source code of default theme in the development phase. So it's more convenient to debug the default theme code because there is no need to run modern build command to build the default theme every time. The default theme source code can take part in the hmr process of the whole build.
And in the ideal result, the style will be imported once(That is packages/theme-default/src/styles/index.ts) instead of twice. That may confuse you a lot. You can pay attention to this alias: @/theme-default.The source code of default theme appear the following import statement:
import { scrollToTarget } from '@/theme-default';

Then the @/theme-default will be redirected to @rspress/theme-default, in other words, dist/bundle.css will be imported. That's why style has beed imported twice.
That's a very interesting problem because after importing the second css, we can get the compiled style code for tailwind. If we remove the second style code import by the following way:
// packages/theme-default/src/components/Toc/index.tsx
// before
import { scrollToTarget } from '@/theme-default';

// after
import { scrollToTarget } from '../../logic';

the tailwind usage will stay as it is and the style of official site is broken😄

After we import only once, the current problem is how to compile the tailwind in the source code build process to ensure the style of official website is as normal as before.

please check #600
@sumy7 @sanyuan0704


Compiling mysendevent.c for android

Hey,
I'm trying to compile mysendevent.c for a specific android architecture and specific API Level. I have created foldersendevent/jni/containing mysendevent.c, Android.mk and Application.mk. Once I run ndk-build in sendevent directory, it creates a libs and obj folder containing the the executable for the specific arch but when pushing this executable into my android and trying to replay the touch events, nothing happens.
If I push your mysendevent executable into my android, replaying touch events works just fine.
How did you compile your mysendevent.c?
Here's my Anroid.mk:
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
# give module name
LOCAL_MODULE    := mysendevent
# list your C files to compile
LOCAL_SRC_FILES := mysendevent.c
# this option will build executables instead of building library for android application.
include $(BUILD_EXECUTABLE)

Here's my Application.mk:
APP_ABI := arm64-v8a
APP_PLATFORM := android-28

Issue was not with compiling. Issue was in the mysendevent.c code


Added Process Scheduling Calculator

Fixes Issue🛠
Closes #1024
Description👨💻
This adds the calculator for calculating wait-time and turnaround-time for various CPU scheduling algorithms including FCFS, SJF, and Round-Robin. Users can input arrival and burst times and, for Round-Robin, the time quantum. The input form includes validation to ensure all necessary data is entered and is in the correct format. Then calculates and displays the output.
Type of change📄

[x] New feature (non-breaking change which adds functionality)

How this has been tested✅

I have checked the output by calculating the Wait time and Turnaround time manually as well as checked the answer from various trusted websites like GeekforGeeks. The output of the calculator matches the examples of the sources.
Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added demonstration in the form of GIF/video file
[x] I am an Open Source Contributor

Screenshots/GIF📷
1)FCFS:

2)SJF:

3)Round-Robin:

Pls add your folder in main index.html file to display on the website @MohiniMehta

added my folder in main index.html file to display on the website.


[DepShield] (CVSS 7.4) Vulnerability due to usage of lodash.sortby:4.7.0 in Jest 24.1.0

🐛 Bug Report
I'm not an expert and this could very much be a false positive. I see you guys are using snyk and have 0 vulnerable dependencies right now on it, but I wanted to share in case this can be fixed. I tried to find myself where loadash sortby was being used, with no luck.
Vulnerabilities
DepShield reports that this application's usage of lodash.sortby:4.7.0 results in the following vulnerability(s):

(CVSS 7.4) CWE-471: Modification of Assumed-Immutable Data (MAID)

Occurrences
lodash.sortby:4.7.0 is a transitive dependency introduced by the following direct dependency(s):
• jest:24.1.0
        └─ jest-cli:24.1.0
              └─ jest-environment-jsdom:24.0.0
                    └─ jsdom:11.12.0
                          └─ data-urls:1.1.0
                                └─ whatwg-url:7.0.0
                                      └─ lodash.sortby:4.7.0
                          └─ whatwg-url:6.5.0
                                └─ lodash.sortby:4.7.0
This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.
To Reproduce
Activate DepShield in any repo using Jest 24.1.0
Steps to reproduce the behavior:
Once you activate DepShield in any repo using package.json, you will get a new issue with the vulnerability notice.
Expected behavior
Clean dependencies, no issues.
Run npx envinfo --preset jest
Paste the results here:
➜ npx envinfo --preset jest
npx: installed 1 in 2.465s

  System:
    OS: macOS 10.14.4
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  Binaries:
    Node: 11.1.0 - ~/.nvm/versions/node/v11.1.0/bin/node
    Yarn: 1.9.4 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v11.1.0/bin/npm
  npmPackages:
    jest: 24.1.0 => 24.1.0

Thanks for the heads up! You should open up an issue with https://github.com/lodash/lodash (and potentially https://github.com/jsdom/whatwg-url)

@SimenB Thanks for the feedback, I actually checked and it seems that lodash is on 4.7.11, so probably I should notify whatwg-url so they can update their dependency to .11, and probably it's already fixed on that minor patch (Y)
Ok, nope, the problem seems to be with whatwg-url not wanting to update/fix this vulnerability
OK, so I was going to open the issue in whatwg-url but after a little finding it was already reported (twice) and closed.
https://github.com/jsdom/whatwg-url/issues/127

Thanks, but without an actual vulnerability proof of concept reported, this won't be a priority for us.

So I don't know, maybe close this issue, I don't know if jest might want to use anything else besides whatwg-url, or this is just not that dangerous to need a fix right away and can wait until whatwg maintainers update their lodash deps.

It's a dependency of jsdom, so it's not really actionable for us.

wait until whatwg maintainers update their lodash deps.

It's already at the latest version in whatwg-url - this needs to be fixed in lodash
https://www.npmjs.com/package/lodash.sortby

But in whatwg-url package.json
It's pinned to "lodash.sortby": "^4.7.0",
The problem was fixed on lodash 4.7.15, so if whatwg-url was to update it's dependency to latest .17 version, the problem should be fixed, right?
Sorry, maybe I'm getting something wrong about this, but I found a related resource where it was stated that lodash fixed this on .15, and even linked to the responsible commit

I gave the owners of whatwg-url a shout about merging a pr to update to the main sort.by function but it was closed, they aren't going to update it.
Lodash are going to deprecate the packages on npm as part of their roadmap this year.
From the original vulnerability reports, it was only functions merge, mergeWith, and defaultsDeep that were affected.
https://snyk.io/vuln/SNYK-JS-LODASH-73638
The original hackerone report
https://hackerone.com/reports/380873
The scanners probably need tightening up to only alert about vulns in those modules/functions only, rather than raising an issue about every lodash and lodash.* npm module
https://github.com/lodash/lodash/search?q=sortby&unscoped_q=sortby
I'll probably get round to raising an issue with synk, depshield, npm to see what they say.
npm list the modules in advisories but dont link to them on any of the package versions. affected versions of lodash.merge mergewith and defaultsdeep are still available on npm
There are papers out there showing how to use this vulnerability
https://github.com/HoLyVieR/prototype-pollution-nsec18/blob/master/paper/JavaScript_prototype_pollution_attack_in_NodeJS.pdf
and ways to mitigate by using object schema validators amongst other things.
I think a few things should happen off the back of this

for the few affected lodash npm modularised packages (merge, mergeWith, defaultsDeep, set, setWith), they should all be updated, and any older version marked as deprecated
deprecation notices should be added to all npm lodash modular packages
scanners that are picking up anyone using lodash <4.17.11 modular packages, that aren't in the affected list, shouldn't be picking up notices.
npm should make advisory notices visible on package pages, rather than abstracted away

Back on topic with regards to Jest and whatwg-url using lodash.SortBy. SortBy doesn't seem like it ever had a vuln in it, so I think its a bit of a red herring of a notice, and because every repository hooked up with synk / depshield etc gets hammered with these alerts, I bet loads don't get looked at, and it means we might miss the alerts that actually use affected packages!

Thanks for digging in @YOU54F!
As this is not actionable at all for us, I'll close this. Hopefully the false positive gets removed or somehow fixed at some point


Some text edits for better comprehension and additional mesh mapping …

…entries

@meshjoerg please rebase and resolve conflicts


Disable dropdowns which have no choices

ie no storage classes, not network configs, no templates..

/remove-lifecycle rotten
/reopen


Add valcol support

Support for the .valcol file format should be added. Specifically, libSparseConvert should have a full read/write implementation, and the C++ io implementation should have read only support at a minimum.

issue closed in e299aea


allow callable in .loc

[x] Closes #256
[x] Tests added:

test_frame.py:test_loc_callback()

This handles the original issue, and some examples that came up during the discussion in the issue, but may not handle all the cases where a Callable can be used in .loc.  Can always enhance based on further user reports.

Thanks @Dr-Irv !


Change the type of file's attribute 'url' from xs:string to xs:anyURL

.. this would allow an automatic type checking at schema-level.

Not considered for schema v1.2, because a relative link requires 'uri-reference' which is supported only with JSON Schema Draft-6.


Feature request: Documentation on how to get started

Context

This project is intended to be accessible to others. Currently, you need to have a good grasp on (web) development and infrastructure to get it going.

Solution

Find a workflow that makes the token gating solution more accessible to non tech nerds. Document this, and create good docs/ (with images) to help others out.

See: https://github.com/0xGeel/loopgate/pull/12


libSyntax: add a test to ensure the generated syntax kinds from parser are expected.

@swift-ci please smoke test and merge


fix rpn_fn codegen unit test

What have you changed?
#5993 changed the rpn_fn macro codegen code but didn't change the unit tests accordingly. This PR fixes it.
Fixes #6033
What is the type of the changes?

Bugfix (a change which fixes an issue)

How is the PR tested?

Unit test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No
Does this PR affect tidb-ansible?
No

/test

/merge


Suggestion: levels workflows, branching models and best practices

Hi,
There are some good blogs that suggest branching models and workflows for git.
As example: A successful Git branching model, or OneFlow
By the way not everyone think that this is a good model
I suggest to add new tab for "real world" examples. With some levels as adding new feature to existing project, fixing bugs, etc. The main focus is keeping the remote branch clean according to the best practices.
Thanks

Yeah I definitely don't think that [http://nvie.com/posts/a-successful-git-branching-model/](the successful git branching model) is the right one :P Over at Facebook/Instagram/Oculus, we have a single trunk that we push to and thats it. It's a lot simpler than maintaining all these different branches and forks.
That being said I didn't want to be too assumptive/argumentative about the right models; I tried to introduce the git tools without imposing a certain way to use them, so thats why ive avoided the third tab for the time being around the right way to use git. thanks for the suggestion though!


OpenGL installation

Hi Authors, thanks for your interesting work : )
It would be appreciated if you could share any environment in which you are running this demo. I am using Linux with x11 forward to Mac machine, but it seems that an OpenGL error is reported.
Thanks a lot!

This is likely an environment setup problem. I wonder if the example scripts in pybullet work for you. If so, does the CLIPort scripts work for you?

I am exactly running the command python gensim/run_simulation.py disp=True prompt_folder=vanilla_task_generation_prompt_simple. I think it is an env problem, is there any way to save the generated video instead of visualizing the video? Thanks a lot!

got it thanks!


Restart terminal or run source ~/.zshrc.

This is what I got:
%(12V.%F{242}%12v%f .)%(?.%F{magenta}.%F{red})${PURE_PROMPT_SYMBOL:-❯}%f

Do you think it might be some conflict with pure?

It looks like they are conflicting.
But instant mode will be replaced with shell_logger that shouldn't conflict with pure.

OK, cool. I'll wait for that, then. :)
I think we can close this one for now. Thanks!

Distributor ID: Ubuntu
Description:    Ubuntu 20.04.2 LTS
Release:        20.04
Codename:       focal

This is an WSL1 environment. The Windows host system is ...
Version:          Windows 10 Home China
Version ID:       20H2
OS Inner Version: 19042.928
Experiment:       Windows Feature Experience Pack 120.2212.551.0

How to reporduce?

Have not confirmed.

Anything relative?

None (Maybe???)

What did echo $PS1 responsed after initialized The Fuck?
\[\e[0;34m\]\W/\[\e[34;1m\]\[\e[32;1m\] \[\e[0m\]$

I'm not using that old system anymore (the MacBook one I reported this on back in 2018), but still having the same issue on my WSL1/Ubuntu.
 And yes, still using Pure prompt... 😉


class Node highlighted with red line

I'd like to create class Node in ES6 syntax. But IntelliSense underlined class Node with red and wrote a message Duplicate identifier 'Node'.

@greybax Does the other file also contain a Node type? Or you are including all of lib.d.ts such that this collides with the DOM Node

@jrieken I'm not using typescript, so I haven't *.d.ts files. Also I haven't any files where I've already declared class Node.
So it can be reproduced just create new .js file and declare class Node.

We now use Salsa for this


Workflow fix for overhaul

github.ref wasn't returning the desired information, tested using github.base_ref and it works as intended for pull requests

@wasade Can you please give this a quick look when you have a moment? Swapped the GitHub environment variable used to detect the target branch of a PR as the initial strategy wasn't working as intended.


Can't perform a React state update on an unmounted component

https://github.com/floating-ui/floating-ui/blob/ec1aabac66d138f3f5ab1c247b86b7fc0467084e/packages/react-dom/src/index.ts#L78
Hi,
I'm getting Can't perform a React state update on an unmounted component, when the component recreated!
The error comes from setData:     computePosition(reference.current, floating.current, {       middleware: latestMiddleware,       placement,       strategy,     }).then(setData);

Do you have a repro? Interesting that the component can unmount during a promise microtask, but we'd probably need a flag like this
useEffect(() => {
  let isMounted = true;
  someAsyncOperation().then(data => {
    if (isMounted) setState(data);
  })
  return () => { isMounted = false };
}, []);

I get a similar error in v 0.4.3 .
I think an isMounted check should be added to the beginning of the update method too, like this:
if (!isMounted.current || !reference.current || !floating.current) {
    return;
}

My issue originates from calling "update()" in setFloating

I don't think that will change anything, setData() is somehow getting called after the component is unmounted which is already guarded with the check; you'll need to provide a repro


Notify vocabulary engineers of errors

To make more precise what we wrote in the paper: I think there is an easy way of assigning vocabulary engineers to all generated validation issues. We could assume that a team vocabulary_engineers has been set up in the repository, and determine all users in this team. Thus, issues would be Cced to all vocabulary engineers. (I don't see an easy way of notifying the single vocabulary engineer who should be “in charge” of a specific issue.)

For now, I assign the issue to the latest person, who changed something. I can adapt it to a team, but then, one needs always to create these teams themselves before being able to use our script.

Fixed.


Support trackpad scroll on Desktop platforms

Refactored scroll_behavior.dart to add const constructors and use TargetPlatform dragDevices as a baseline even if dragWithMouse enabled.
The methodology I used is one way of accomplishing this which I thought made the most sense though it isn't necessarily the most immediately obvious. The simpler solution would have been to just add the trackpad device manually, but I think this approach covers the bases more dynamically.
I'm happy to make any additional tweaks that may be desired to get this merged (such as upping the version in the pubspec, which I haven't done in case there was anything else that wanted to be added)

Awesome, thanks for the contribution! I'll take a look this week - Ray
On Mon, Aug 5, 2024 at 10:48 AM Trefa1998 @.***> wrote:

Refactored scroll_behavior.dart to add const constructors and use
TargetPlatform dragDevices as a baseline even if dragWithMouse enabled.
The methodology I used is one way of accomplishing this which I thought
made the most sense though it isn't necessarily the most immediately
obvious. The simpler solution would have been to just add the trackpad
device manually, but I think this approach covers the bases more
dynamically.
I'm happy to make any additional tweaks that may be desired to get this
merged (such as upping the version in the pubspec, which I haven't done in
case there was anything else that wanted to be added)
You can view, comment on, or merge this pull request online at:
https://github.com/Codelessly/ResponsiveFramework/pull/183
Commit Summary

6b72c3c
https://github.com/Codelessly/ResponsiveFramework/pull/183/commits/6b72c3c70765110e29e6447a93db21382c9671d4
Refactored scroll_behavior.dart to add const constructors and use
TargetPlatform dragDevices as a baseline even if dragWithMouse enabled

File Changes
(1 file https://github.com/Codelessly/ResponsiveFramework/pull/183/files
)

M lib/src/utils/scroll_behavior.dart
https://github.com/Codelessly/ResponsiveFramework/pull/183/files#diff-e0e84bdf729e8e0a5a02f652a36733317d1bb694963698ed9590cd9af02864b7
(34)

Patch Links:

https://github.com/Codelessly/ResponsiveFramework/pull/183.patch
https://github.com/Codelessly/ResponsiveFramework/pull/183.diff

—
Reply to this email directly, view it on GitHub
https://github.com/Codelessly/ResponsiveFramework/pull/183, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEXZO3UJJUMDZQBQKOLDKW3ZP6NDFAVCNFSM6AAAAABMASHF5CVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2DQOBZGI2TEMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Unable to Run Android App Without NuGet Package Xamarin.Google.Dagger

Upon running this example for Xamarin Android, a Java error occurs.
The NuGet package Xamarin.Google.Dagger is needed for it to work.

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

ID: ae6b97ae-ec64-6de9-8f02-16f91f5f9519
Version Independent ID: d9748b97-4afb-fc97-9598-188bd460cc13
Content: Send push notifications to Xamarin.Forms apps using Azure Notification Hubs via a backend service
Content Source: articles/mobile-apps/notification-hubs-backend-service-xamarin-forms.md
Service: mobile-services
GitHub Login: @mikeparker104
Microsoft Alias: miparker

Closing this issue due to staleness. We apologize for the delayed response. If you are still encountering the problem you've described, please re-open the issue within 2 weeks and we'll take a look. Thanks!
#label:"UUF-Stale-Not Planned"


add search option also a voice assistant

add search option also a voice assistant

Hey @kusol2004, I don't exactly understand what you're trying to say. You described it in just one sentence, which doesn't clearly explain what you want to work on. Please don't do that.
You raised a blank issue. You should choose the appropriate issue template and describe it accordingly, as the chosen template will clarify what you want to work on. I will be happy to assign issues that are clearly understandable. Please keep this in mind—I'm not instructing you, just trying to show the correct roadmap for working on open source. Please don't be discouraged; I am closing this issue for now.


[Slider] double handle : add prop to set active handle

As per concept in order to avoid the upper and lower range values crossing each other, an api for setting which handle is active should be added
see related concept for the requested microbehaviour
https://github.com/sociomantic/ursula/blob/Milestone-UIModels/src/lego/Presenters/Slider/docs/Slider.spec.md#microbehavior
simple suggestion would be adding an isActiveHandle prop.

I don’t think this is going to be possible. At least not with the current Slider implementation where each handle is associated with a hidden native <input type="range">.
Problem is, setting the active handle actually implies programmatically focusing the <input> associated with the desired handle. But we should never implement behaviors where the Nessie component steals the focus like that.
Marking as status-blocked for now, while we find an alternative solution

@conor-cafferkey-sociomantic okay, sorry for this request. No need for any Nessie changes, we can just treat e.g the upper as lower handle, if it passes the lower and vice versa, as there's no visual difference.. No dependency!

actually as initially discussed swapping values does ensure correct lower and upper range values, however the focus is not swapped!

We’ll add an inputRef prop similar to that on other props to allow the host app to programmatically focus the input(s):

in the case of a single value/handle the inputRef callback will receive a single ref to the native <input>
in the case of multiple values/handles the callback will receive an array of refs