RTools 4.0 Windows issues warnings on build

Description
As the title says, cmdstan on Windows with RTools 4.0 issues a bunch of warnings.
It all still works, but if someone has ideas on whether we can clean these up that would be great.
On cmdstan build we get
In file included from stan/lib/stan_math/stan/math/rev/core.hpp:55,
                 from stan/src/stan/model/model_base.hpp:5,
                 from src/cmdstan/command.hpp:23,
                 from src/cmdstan/main.cpp:2:
stan/lib/stan_math/stan/math/rev/core/std_isinf.hpp:16:43: warning: optimization attribute on 'bool std::isinf(const stan::math::var&)' follows definition but the attribute doesn't match [-Wattributes]
 inline bool isinf(const stan::math::var& a) {
                                           ^
In file included from stan/lib/stan_math/lib/boost_1.72.0/boost/config/no_tr1/cmath.hpp:21,
                 from stan/lib/stan_math/lib/boost_1.72.0/boost/numeric/conversion/converter_policies.hpp:16,
                 from stan/lib/stan_math/lib/boost_1.72.0/boost/numeric/conversion/converter.hpp:14,
                 from stan/lib/stan_math/lib/boost_1.72.0/boost/numeric/conversion/cast.hpp:33,
                 from stan/lib/stan_math/lib/boost_1.72.0/boost/lexical_cast/detail/converter_numeric.hpp:36,
                 from stan/lib/stan_math/lib/boost_1.72.0/boost/lexical_cast/try_lexical_convert.hpp:43,
                 from stan/lib/stan_math/lib/boost_1.72.0/boost/lexical_cast.hpp:32,
                 from stan/src/stan/callbacks/writer.hpp:4,
                 from src/cmdstan/arguments/argument.hpp:4,
                 from src/cmdstan/arguments/argument_parser.hpp:4,
                 from src/cmdstan/command.hpp:4,
                 from src/cmdstan/main.cpp:2:
C:/rtools40/mingw64/include/c++/8.3.0/cmath:584:3: note: previous definition of 'constexpr bool std::isinf(float)' was here
   isinf(float __x)
   ^~~~~

In file included from stan/lib/stan_math/lib/tbb_2019_U8/include/tbb/task_arena.h:20,
                 from stan/lib/stan_math/stan/math/prim/functor/reduce_sum.hpp:7,
                 from stan/lib/stan_math/stan/math/prim/functor.hpp:21,
                 from stan/lib/stan_math/stan/math/prim.hpp:11,
                 from stan/src/stan/io/dump.hpp:6,
                 from src/cmdstan/command.hpp:20,
                 from src/cmdstan/main.cpp:2:
stan/lib/stan_math/lib/tbb_2019_U8/include/tbb/task.h:1065:84: warning: optimization attribute on 'void* operator new(size_t, const tbb::internal::allocate_root_proxy&)' follows definition but the attribute doesn't match [-Wattributes]
 inline void *operator new( size_t bytes, const tbb::internal::allocate_root_proxy& ) {
                                                                                ^
In file included from C:/rtools40/mingw64/include/c++/8.3.0/bits/exception_ptr.h:40,
                 from C:/rtools40/mingw64/include/c++/8.3.0/exception:143,
                 from C:/rtools40/mingw64/include/c++/8.3.0/ios:39,
                 from C:/rtools40/mingw64/include/c++/8.3.0/ostream:38,
                 from C:/rtools40/mingw64/include/c++/8.3.0/iterator:64,
                 from stan/lib/stan_math/lib/boost_1.72.0/boost/iterator/iterator_traits.hpp:10,
                 from stan/lib/stan_math/lib/boost_1.72.0/boost/range/iterator_range_core.hpp:26,
                 from stan/lib/stan_math/lib/boost_1.72.0/boost/lexical_cast.hpp:30,
                 from stan/src/stan/callbacks/writer.hpp:4,
                 from src/cmdstan/arguments/argument.hpp:4,
                 from src/cmdstan/arguments/argument_parser.hpp:4,
                 from src/cmdstan/command.hpp:4,
                 from src/cmdstan/main.cpp:2:
C:/rtools40/mingw64/include/c++/8.3.0/new:168:14: note: previous definition of 'void* operator new(std::size_t, void*)' was here
 inline void* operator new(std::size_t, void* __p) _GLIBCXX_USE_NOEXCEPT
              ^~~~~~~~

In file included from stan/lib/stan_math/lib/tbb_2019_U8/include/tbb/task_arena.h:20,
                 from stan/lib/stan_math/stan/math/prim/functor/reduce_sum.hpp:7,
                 from stan/lib/stan_math/stan/math/prim/functor.hpp:21,
                 from stan/lib/stan_math/stan/math/prim.hpp:11,
                 from stan/src/stan/io/dump.hpp:6,
                 from src/cmdstan/command.hpp:20,
                 from src/cmdstan/main.cpp:2:
stan/lib/stan_math/lib/tbb_2019_U8/include/tbb/task.h:1103:101: warning: optimization attribute on 'void operator delete(void*, const tbb::internal::allocate_additional_child_of_proxy&)' follows definition but the attribute doesn't match [-Wattributes]
 inline void operator delete( void* task, const tbb::internal::allocate_additional_child_of_proxy& p ) {
                                                                                ^
In file included from C:/rtools40/mingw64/include/c++/8.3.0/bits/exception_ptr.h:40,
                 from C:/rtools40/mingw64/include/c++/8.3.0/exception:143,
                 from C:/rtools40/mingw64/include/c++/8.3.0/ios:39,
                 from C:/rtools40/mingw64/include/c++/8.3.0/ostream:38,
                 from C:/rtools40/mingw64/include/c++/8.3.0/iterator:64,
                 from stan/lib/stan_math/lib/boost_1.72.0/boost/iterator/iterator_traits.hpp:10,
                 from stan/lib/stan_math/lib/boost_1.72.0/boost/range/iterator_range_core.hpp:26,
                 from stan/lib/stan_math/lib/boost_1.72.0/boost/lexical_cast.hpp:30,
                 from stan/src/stan/callbacks/writer.hpp:4,
                 from src/cmdstan/arguments/argument.hpp:4,
                 from src/cmdstan/arguments/argument_parser.hpp:4,
                 from src/cmdstan/command.hpp:4,
                 from src/cmdstan/main.cpp:2:
C:/rtools40/mingw64/include/c++/8.3.0/new:174:13: note: previous definition of 'void operator delete(void*, void*)' was here
 inline void operator delete  (void*, void*) _GLIBCXX_USE_NOEXCEPT { }
             ^~~~~~~~

There are also some that come up when compiling a model:
In file included from stan/lib/stan_math/lib/tbb_2019_U8/include/tbb/task_arena.h:20,
                 from stan/lib/stan_math/lib/tbb_2019_U8/include/tbb/task_scheduler_observer.h:22,
                 from stan/lib/stan_math/stan/math/rev/core/init_chainablestack.hpp:6,
                 from stan/lib/stan_math/stan/math/rev/core.hpp:10,
                 from stan/lib/stan_math/stan/math/rev.hpp:6,
                 from stan/lib/stan_math/stan/math.hpp:19,
                 from stan/src/stan/model/model_header.hpp:4,
                 from examples/bernoulli/bernoulli.hpp:3:
stan/lib/stan_math/lib/tbb_2019_U8/include/tbb/task.h:1103:101: warning: optimization attribute on 'void operator delete(void*, const tbb::internal::allocate_additional_child_of_proxy&)' follows definition but the attribute doesn't match [-Wattributes]
 inline void operator delete( void* task, const tbb::internal::allocate_additional_child_of_proxy& p ) {
                                                                                ^
In file included from stan/lib/stan_math/lib/eigen_3.3.7/Eigen/Core:82,
                 from stan/lib/stan_math/lib/eigen_3.3.7/Eigen/Dense:1,
                 from stan/lib/stan_math/stan/math/prim/fun/Eigen.hpp:22,
                 from stan/lib/stan_math/stan/math/rev.hpp:4,
                 from stan/lib/stan_math/stan/math.hpp:19,
                 from stan/src/stan/model/model_header.hpp:4,
                 from examples/bernoulli/bernoulli.hpp:3:
C:/rtools40/mingw64/include/c++/8.3.0/new:174:13: note: previous definition of 'void operator delete(void*, void*)' was here
 inline void operator delete  (void*, void*) _GLIBCXX_USE_NOEXCEPT { }
             ^~~~~~~~

Current Version:
v3.2.0

This seems to ba a gcc bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89325
A workaround -Wno-attributes is suggested here: https://stackoverflow.com/questions/44532934/eigen-3-3-has-many-warnings-with-mingw-w64-gcc-7-1-0

Thanks!


message_fetch: Remove obsolete UnicodeDecodeError handler

This handler from commit a696141a2515209424ffd191083e894104e4f37d (#7418) was almost certainly made unreachable when commit c3e395b7d8f4165f6677a83514e0449e0ee86f37 (#13092) removed anything that might have thrown a UnicodeDecodeError from highlight_string.

Merged, thanks @andersk!


Error no matches for kind "OCIRepository" in version "source.toolkit.fluxcd.io/v1beta2"

Describe the bug
We are getting error - no matches for kind "OCIRepository" in version "source.toolkit.fluxcd.io/v1beta2" in our Weave UI

Environment
Stage and PROD

Weave-Gitops Version - HEAD-c26a1c39 helm chart version - 3.0.3
Flux: v0.31.5
Kubernetes: v1.20.15-eks-18ef993

To Reproduce
Steps to reproduce the behavior:

Additional Context (screenshots, logs, etc)

Hi @grglzrv
Thank you for filing the issue.
Please use Flux v0.32.0+.
Flux v0.31.x has Helm OCI support, but not OCIRepository.

Closing based on the guidance above, please re-open if you require any further assistance.


Add RFC-0002 (Layer Architecture)

This RFC shall describe the requirements of the individual layers of Racklet in more detail. It doesn't describe the implementation details of each layer, those will be covered by upcoming RFCs.

 Perhaps a bit embarrassingly, the core of Racklet, the compute unit, was missing in the layer description altogether, so that's now been added as well.


Organized folder structure for all 3 tests

Signed-off-by: Owais Kazi<EMAIL_ADDRESS>Description
Organized all 3 tests in test_workflow for better understanding
Issues Resolved
https://github.com/opensearch-project/opensearch-build/issues/424
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #425 (120f026) into main (6cf57c7) will increase coverage by 0.08%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #425      +/-   ##
==========================================
+ Coverage   60.27%   60.36%   +0.08%
==========================================
  Files          39       39
  Lines        1143     1143
==========================================
+ Hits          689      690       +1
+ Misses        454      453       -1

Impacted Files
Coverage Δ

bundle-workflow/src/perf_test.py
0.00% <0.00%> (ø)

bundle-workflow/src/run_integ_test.py
0.00% <0.00%> (ø)

bundle-workflow/src/test.py
0.00% <0.00%> (ø)

...kflow/src/test_workflow/bwc_test/bwc_test_suite.py
90.62% <ø> (ø)

...w/src/test_workflow/integ_test/integ_test_suite.py
0.00% <0.00%> (ø)

...src/test_workflow/integ_test/local_test_cluster.py
0.00% <ø> (ø)

...w/src/test_workflow/perf_test/perf_test_cluster.py
100.00% <ø> (ø)

...low/src/test_workflow/perf_test/perf_test_suite.py
95.23% <ø> (ø)

bundle-workflow/src/system/arch.py
100.00% <0.00%> (+12.50%)
:arrow_up:

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 6cf57c7...120f026. Read the comment docs.

I saw you opened an issue and then put up a PR for it. Are we following this convention? I think just the PR is perfectly fine!

I saw you opened an issue and then put up a PR for it. Are we following this convention? I think just the PR is perfectly fine, we can open issues for things that aren't incoming and we don't want to forget.

I opened the issue to keep the track. I'll go ahead and close the issue if it's not required.

Did you also want to create a matching tree structure in tests? Probably yes.


Allow trailing commas in function calls

This should be valid, but it is currently a syntax error:
let f = (a, b) => 1;

f(
  "really long string",
  "another really long string that should cause this line to break",
);

We've been gathering a collection of situations where trailing commas should be allowed in https://github.com/facebook/reason/issues/1549.


[FEAT] Specify number of backups per day to retain

Problem
Right now you can specify the number of days you want backups for, the frequency of backups, but you cannot specify how many backups per day to keep.
For example, if you backup every 30 minutes you will get

backup 1 - 10:30 am
backup 2 - 11:00 am
backup 3 - 11:30 am
... until you close Obsidian

This will lead to dozens of backups for a period of 7 days.
Solution
Add an input to specify the number of backups per day to retain.
For example, if I had the value to 1 backup per day with a frequency of backup of 30 minutes
I would get

backup 1 - 10:30 am
backup 2 - 11:00 am - AND delete backup 1
backup 3 - 11:30 am - AND delete backup 2

After 3 days I would have

1 backup from Tuesday
1 backup from Wednesday
1 backup from Thursday

Yes it is a necessary feature, I will work on it.

This feature is included in 0.0.9! Plz upgrade and setup in setting page.

I waited until 12 am the next day to see what would happen. I have the Backup history length set to 7 and the Backups per day set to `1. They 1 backup per day is working. It looks like the previous day's back up is being deleted.

I waited until 12 am the next day to see what would happen. I have the Backup history length set to 7 and the Backups per day set to 1. The 1 backup per day is working. However, it looks like the previous day's back up is being deleted.
Current behavior:

backup 1 - 11:00 pm
backup 2 - 11:30 pm
---> delete backup 1 at 11:00 pm
backup 3 at 12:00am
----> delete backup 2 at 11:30 pm

I would expect backup 2 at 11:30 pm backup to be retained and backup 3 to be created.

Yes I met this issue after released, will fix it.

I waited until 12 am the next day to see what would happen. I have the Backup history length set to 7 and the Backups per day set to 1. The 1 backup per day is working. However, it looks like the previous day's back up is being deleted.
Current behavior:

backup 1 - 11:00 pm
backup 2 - 11:30 pm
---> delete backup 1 at 11:00 pm
backup 3 at 12:00am
----> delete backup 2 at 11:30 pm

I would expect backup 2 at 11:30 pm backup to be retained and backup 3 to be created.

FIxed in 0.1.0. 😄


PWE Crashes When Tools -> Edit Layers is Opened

Date Tested: 2/17/2019
PWE Version: v1.2.2
Steps to Recreate: Open PWE v1.2.2 and without opening a project go to the Tools dropdown and click Edit Layers.
primeworldeditor.log

Fixed in d9f149360e8e9b4e9ab1aa4f3a015ec25554bfcc


[BUG] allowHtml interferes with code highlighting

Describe the bug
Some characters are erroneously html-encoded in code highlight section when allowHtml is set to true.
To Reproduce
If allowHtml is set to true and the markdown contains the following code highlight:

```javascript
console.log('test');
```

the output is:

console.log('test');

Expected behavior
The output should be:

console.log('test');

Additional context
We tested this with doctor 1.7.0 and 1.8.0-beta.6217071

Thanks, found what was causing the issue. Fix and extra tests have been added. Once the next build has been completed. It will be available in beta.

This has been released in v1.8.0


replace setuptools version check

increment the setuptools_scm version to v1.16.0
replaced the SetupToolVersion with the packaging.version.Version

please bump again, there was a regression in setuptools_scm 1.16.1 as well and it has been fixed ^^

Thanks @JWDobken for this PR. We updated to setuptools_scm 1.17.0 so this PR can be closed.


[$250] Android - Report Fields - Cursor position jumps to the beginning of the name field

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

Version Number: <IP_ADDRESS>
Reproducible in staging?: Y
Reproducible in prouring regression testing, add the test name, ID and link from TestRail: N/A
Issue reported bduction?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Issue found when executing PR https://github.com/Expensify/App/pull/44275
Action Performed:

Open new expensify app
Create a workspace
Enable report fields feature
Open report fields setting
Tap on add field
Tap on Name and add something and save it
Tap on Name again

Expected Result:
The cursor positions itself at the end of the text
Actual Result:
The cursor jumps to the beginning of the saved text
Workaround:
Unknown
Platforms:

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

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/03a437a3-e2e2-4a98-bfd9-d4b51ce08da8
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ecace54576044ee5
Upwork Job ID:<PHONE_NUMBER>801435309
Last Price Increase: 2024-07-04
Automatic offers:

shubham1206agra | Reviewer | 102994077
dominictb | Contributor | 103082291

Issue OwnerCurrent Issue Owner: @garrettmknight

@marcochavezf  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

I don't consider it a deploy blocker, and can be fixed externally

I am managing this project so going to take over this issue to make sure it gets fixed. Thanks for helping!

@rezkiy37 @waterim Can you please have a look

Proposal
Please re-state the problem that we are trying to solve in this issue.
Report Fields - Cursor position jumps to the beginning of the name field when reopened
What is the root cause of that problem?

The name field inside create report field uses the TextPicker as the  InputWrapper for the user's input field
The TextPicker component uses the TextSelectorModal component in order to render the text field
The TextSelectorModal contains a prop isVisible that decides whether the input field page should be visible or not.
in case the isVisible is false then true (page was reopened), the input field refocuses here in order to show the keyboard.
the inputRef.current.focus() doesn't preserve the cursor position, that's why it just places the cursor at the beginning

PS: This issue occurs in the create new tax page as well
What changes do you think we should make in order to solve the problem?
we should set the cursor selection at the end of the string after focusing, we should modify the useFocusEffect to be as follows:
   useFocusEffect(
        useCallback(() => {
            focusTimeoutRef.current = setTimeout(() => {
                if (inputRef.current && isVisible) {
                    inputRef.current.focus();
                    if (currentValue) {
                        inputRef.current.setSelection(currentValue.length, currentValue.length);
                    }
                }
                return () => {
                    if (!focusTimeoutRef.current || !isVisible) {
                        return;
                    }
                    clearTimeout(focusTimeoutRef.current);
                };
            }, CONST.ANIMATED_TRANSITION);
        }, [isVisible]),

optionally, instead of always placing the cursor at the end when refocusing, we can save the cursor position in a ref and use it instead
POC
https://github.com/Expensify/App/assets/59809993/5a82f5fe-1185-4a22-86b5-0d5e14f2c436

Looks like @rezkiy37 / @waterim will work on this

Hello, I will help with this issue

Hi, I’m Michael (Mykhailo) from Callstack and I would like to work on this issue.

I've opened a PR (https://github.com/Expensify/App/pull/45074) for review 🙂

Just to clarify: the app does not use useAutoFocusInput for this scenario with the new report field name. It uses TextSelectorModal under the hood and this component handlers focusing.

$50 to @abzokhattab as the issue was labeled as Help Wanted and we have used their solution

@dominictb updated offer sent to you for $50

@garrettmknight  I believe there may be a mistake in the offer assignment,  can you please recheck this comment
Thank you for your consideration!

Oops, @abzokhattab you're right. I'll drop the contract to pay $50 when the solution works on prod.

Yeah its 50$

PR reviewed and merged

@abzokhattab all paid out!

Looks like this made it to prod on Monday. Just tested and it's fixed.

Payment Summary:

Reviewer: @rushatgabhane $250

@rezkiy37 @mountiny is there a regression test for this already?

Dropping to weekly for payment


Wrong values - using smartenergy.at

Hi
Just installed the integration. Unfortunately, it seems to deliver incorrect values.
The net price of 23.70 ct seems to be wrong.
Or am I missing something?

Did you configure tax and surcharges in the configuration dialog of the integration?

Thanks for the hint! I overlooked that config parameters somehow.
Maybe set the default values when configuring smartENERGY.at?

Parameter
Value

Percentage Surcharge (%)
0

Absolute Surcharge (ct/kWh)
1.2

Tax (%)
20


Save loading problems

Hi there, I've recently encountered an issue with loading my save. I'm not sure what it means, but I'll attach an image below.

Hello, thanks for reaching out. Would you mind attaching your dorfperfekt save file to this issue? Its a simply plain text file and does not include any identifying information-- let me know if you have any issue locating it.
This error is raised when loading the save file. During loading, the save file reads tiles in one at time in the order they are played... apparently one of the tiles in the file is not a valid placement. Do you have any recollection of how this may have arisen? Like whether you used the "delete tile" feature in the GUI or perhaps modified the save file manually?
Given the save file it should be straightforward to locate the tile where things have gone wrong.

I can't upload the file itself, but here is its contents
GGGGGG 0 0
CCCCCC 4 0
CCCCCC 0 4
CCCCCC 2 2
CCCCCC 1 3
CCCCCC 3 1
CCCCCC -1 4
CCCCCC -2 4
CCCCCC -3 4
CCCCCC -4 4
CCCCCC -4 3
CCCCCC -4 2
CCCCCC -4 1
CCCCCC -4 0
CCCCCC -3 -1
CCCCCC -2 -2
CCCCCC -1 -3
CCCCCC 0 -4
CCCCCC 1 -4
CCCCCC 2 -4
CCCCCC 3 -4
CCCCCC 4 -4
CCCCCC 4 -3
CCCCCC 4 -2
CCCCCC 4 -1
CCDGGC 1 0
GGGFFF -1 0
FFFWFW -2 0
GGGGGG 3 -3
FRRFFF 0 2
FFWRRW -1 -1
GTGTDG 2 -2
DRDDGG 1 -3
FRFGFG -2 1
GGGGFF -3 1
CCCCCC 3 -2
GGGFGG -1 1
CCCCCC 1 -1
GGFFFG 0 -1
RGGRRG -2 2
DGCCCC 0 -3
DGGRRR -1 3
WFFFWT 1 1
FFFGGD 0 1
TRTGRR 2 0
RFDGGF -2 -1
GDDDGG 2 -3
WFWGWD -3 0
GGFFFF 1 2
CCCDRF 0 3
FRFRGF -1 2
CRFGCC -1 -2
WFWWGD 0 -2
TGCCRD 1 -2
TRGGTG 2 -1
CTRTCC 3 -1
GGWTTW 3 0
GWFWRW 2 1
GGCCCG -3 3
RGGGGF -3 2
RCCGGF -2 3
I used the delete tile feature in the gui but I haven't edited the file manually at all

Huh, the ordering of all these tiles is rather odd. What game mode was this?
I'm not surprised this is related to the delete function; I will take another look at it this weekend.

This is creative mode

I've published a fix in commit 190c4cebcadb927eded268037f9f54036bafa3f0 to PyPI that I believe should fix your file when you go to open it. Please run pip install dorfperfekt --upgrade to get the latest and let me know if it resolves your issue.

Yes this worked thank you!


Added Leetcode Problem: Find Peak Element

Hi I've added the leetcode problem Find Peak Element.
Although I'm a bit confused with the folder naming. Please do let me know if the folder name needs to be updated. (Removing "_" from the name).
Thanks.

Hey thanks for your contribution ❗. Keep up the good job and leave a star if you liked the repo .
Happy hacking 😉


Implement Log Likelihood

I probably need a lower level, C++ implementation of log likelihood.
I found this C++ package (maybe there are better options): http://www.cahillsoftware.com/media/af21843f135214fffff850fffffe417.html
Should I make an R wrapper for it using Rcpp?
Here's the thing though: I'm not sure how to apply the above package to a data frame -- nor do I really understand how to measure log likelihood correctly, so I am afraid I am going to mess something up.
Ideally I would find the right person for this job.

@EliasLMann would you be interested in attempting this or nah?
I showed you the TF-IDF measures that we have throughout. We would like more "transparent" measures implemented like log likelihood.
Ideally I would be able to implement log likelihood in real time, like the TF-IDF function.

Yes, definitely. I'll give it a shot starting Sunday night.

Thanks, @EliasLMann!
Here's some background: I want to implement this in the same way that I use TF-IDF for collocates or speaker comparison (so the user will be able to select Log Likelihood from the drop down).
I think it should take a data frame as input, and return another data frame, but with log likelihood scores.
A guess a key thing to check before wrapping this, however, is that this implementation of LL is actually fast enough to run in real time on our data.
R has a few log likelihood implementations, but they're all exceptionally slow and they would be unrealistic in a web app.


PHP 7.4: Remove special condition for converting PHP errors to exceptions

…if they occurred inside of __toString() call.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

closes #17610

Thanks!


systemd-boot-builder.py: add support for profiles

This will also list the generations of other profiles than system in
the boot menu. See the documentation of the --profile-name option of
nixos-rebuild for more information on profiles.
Motivation for this change
To boot other profiles with systemd-boot.
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

What is the use case for this?

Suppose you want to have different Kernel version. You can create a profile for each and get a boot menu entry to select them.

Currently fails to build, when I give no profile argument to nixos-rebuild switch:
created 10635 symlinks in user environment
install-info: warning: no info dir entry in `/nix/store/1zjrj9rna9gs16d36kc53l6dzy9kkxab-system-path/share/info/time.info'
building path(s) ‘/nix/store/w9kjfxkm8hfvrfqlxxr0hilfivxl81cn-dbus-1’
building path(s) ‘/nix/store/y8s1j7cv8maf7i7crjajdmvci4lg5x2v-unit-polkit.service’
building path(s) ‘/nix/store/jqp8b44i1lx82i4h4fpialqxl1qdssdd-unit-systemd-fsck-.service’
building path(s) ‘/nix/store/0p423ar4pj10jxa5277pprm0bn5paavr-unit-dbus.service’
building path(s) ‘/nix/store/6wx3l0v74p32f8icrq9vmkw370m7kdqw-system-units’
building path(s) ‘/nix/store/h4z06sv1nys9sl6mrndk749np9d76bh2-user-units’
building path(s) ‘/nix/store/gyxmp1np5zlk7vnilz71qkc3hr5rppmm-etc’
building path(s) ‘/nix/store/m0w6z41fsj1qdpmw34bxcpq729qngpl8-nixos-system-turingmachine-17.09.git.5334e85’
Traceback (most recent call last):
  File "/nix/store/xns7s94x8a7z24hi9qd9jzrsl445sscz-systemd-boot-builder.py", line 182, in <module>
    main()
  File "/nix/store/xns7s94x8a7z24hi9qd9jzrsl445sscz-systemd-boot-builder.py", line 165, in main
    for profile in get_profiles():
  File "/nix/store/xns7s94x8a7z24hi9qd9jzrsl445sscz-systemd-boot-builder.py", line 127, in get_profiles
    for x in os.listdir("/nix/var/nix/profiles/system-profiles/")
FileNotFoundError: [Errno 2] No such file or directory: '/nix/var/nix/profiles/system-profiles/'
warning: error(s) occurred while switching to the new configuration

Currently fails to build, when I give no profile argument to nixos-rebuild switch:

Ohh, I should have checked the case that no profile exists. My bad, I will update the PR but will only have time earliest on Monday to do so.

@Mic92, let me know if there is still something that needs to be fixed.


Pymotorcad_10_08

Hi all, I have created Cheat sheet for PymotorCAD. Can you review it and merge if there are no conflicts.

Thank you for the PR @pvinod13 , Pinging here @EstherProsperi  for proof reading. Can you please upload the the pdf of the rendered cheatsheet @pvinod13  and please review @EstherProsperi when ever you have some time.

pymotorcad_cheat_sheet_updated.pdf. Hi @EstherProsperi, please review the cheatsheet and give your feedback.

pinging here @PipKat based on her recent review.

@Revathyvenugopal162 @pvinod13 @EstherProsperi I am going to merge this PR and create a new one in which I will edit the cheat sheet. Thanks, all.


Allow CombinedMultiDict.copy()

CombinedMultiDict is immutable, but does not have a .copy() method to get a mutable copy from it. It would be quite useful.

I believe you may be looking for the .to_dict() method, which will return a standard python dictionary with the CombinedMultiDict contents.

Well I was thinking on getting a mutable MultiDict, with all its api

Would passing the returned dictionary to an instantiation of MultiDict work for your use case? Otherwise, you'd end up writing .copy()/.to_dict() methods for every possible output type.
e.g.
 foo = MultiDict([('foo', 'bar')])
 baz = MultiDict([('baz', 'qux')])

 immut_dict = CombinedMultiDict([foo, baz])
 mut_dict = MultiDict(immut_dict.to_dict())

copied_multidict = MultiDict(original_multidict)
If it was implemented, I'd expect ImmutableMultiDict.copy to return another ImmutableMultiDict, not sure how useful that would be.

Yes, that would work indeed. Or creating a MultiDict and updating it with the others instead of creating a CombinedMultiDict directly. My suggestion was just for an enhacement to allow to do that more easily, just like with ImmutableMultiDict, but you can close it if you consider it not necessary.

It's not clear what the behavior should be. Combined is a view of other dicts, what it returns changes as the underlying dicts change. Making a copy would break that expectation. Then again, the current copy seems pretty useless. I'm leaning towards changing to return MultiDict(self), but I'll wait a bit.


how to run dos_x example?

Hi, :)
would you be kind to provide examples about how to run dns over QUIC?
Best,
SZ

@tigertoes this one is for you ;)

Perhaps it would be best to include some instructions in the code itself? I can put a PR together.

I think maybe a README.rst in the examples directory might be better. Just populate the DNS over QUIC part and I'll jump in and add docs for the rest

@jlaine @tigertoes that will be great :)

The PR put together by @tigertoes has been merged!

Thanks @ALL


How can rustc_plugin be used to analyze the code of rustc?

Hi, thank you for open-sourcing rustc_plugin, it has been very helpful for my research.
However, I want to analyze the source code of rustc or the std library, and in this case, I cannot use cargo build for compilation, so I can't directly use commands like cargo tool. Do you have any good suggestions? Thank you so much!

rustc_plugin should be able to run on individual crates in the Rust compiler. I've used Flowistry to analyze rustc source code before. What specific issue are you running into?


chore: add add samples for sessionID support in Load jobs

Do not merge until libraries-bom has been updated wth java-cloud-bigquery 2.27.0


Feature request: ability to edit a voice without being connected to Synergy

Currently, Voicing Mode requires being connected to a Synergy.
A user has asked to be able to edit a voice without being connected to hardware.   Obviously there would be no audible way to hear the effect of the change, but with some small changes to Synergize, it should be possible to enable the editor without a connection to a Synergy.

Now that the Synergia VST is available, the need for this sort of Synergy-less editing is less obvious.  I don't plan to implement this.


Bug 20, don't override medicationUseStatus

Signed-off-by: Brian Cragun<EMAIL_ADDRESS>Handle issue 20.  Remove medicationUseStatus override.

Fixed in https://github.com/LinuxForHealth/CsvToFHIR/pull/21


InvalidImageName for kubernetes dashboard pods

inspection-report-20190320_114642.tar.gz
After a fresh install and enabling the dashboard, when I access http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy I get
{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {

  },
  "status": "Failure",
  "message": "no endpoints available for service \"kubernetes-dashboard\"",
  "reason": "ServiceUnavailable",
  "code": 503
}

I noticed that my pods are not starting correctly:
microk8s.kubectl get all --all-namespaces                                                                                   23.21   11:41:10 
NAMESPACE     NAME                                                  READY   STATUS             RESTARTS   AGE
kube-system   pod/elasticsearch-logging-0                           1/1     Running            0          3m49s
kube-system   pod/fluentd-es-v2.2.0-pfzlp                           1/1     Running            0          3m48s
kube-system   pod/heapster-v1.5.2-6d56f4bd4b-5zdg8                  0/4     InvalidImageName   0          150m
kube-system   pod/kibana-logging-764d446c7d-9vpjq                   1/1     Running            0          3m49s
kube-system   pod/kube-dns-6c4b646d76-4lfwr                         0/3     InvalidImageName   0          4m10s
kube-system   pod/kubernetes-dashboard-666f999c67-qbc9n             0/1     InvalidImageName   0          150m
kube-system   pod/monitoring-influxdb-grafana-v4-8457fbf595-lflnz   0/2     InvalidImageName   0          150m
NAMESPACE     NAME                            TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
default       service/kubernetes              ClusterIP   <IP_ADDRESS>     <none>        443/TCP             158m
kube-system   service/elasticsearch-logging   ClusterIP   <IP_ADDRESS>    <none>        9200/TCP            3m49s
kube-system   service/heapster                ClusterIP   <IP_ADDRESS>   <none>        80/TCP              150m
kube-system   service/kibana-logging          ClusterIP   <IP_ADDRESS>   <none>        5601/TCP            3m48s
kube-system   service/kube-dns                ClusterIP   <IP_ADDRESS>    <none>        53/UDP,53/TCP       4m10s
kube-system   service/kubernetes-dashboard    ClusterIP   <IP_ADDRESS>    <none>        443/TCP             150m
kube-system   service/monitoring-grafana      ClusterIP   <IP_ADDRESS>   <none>        80/TCP              150m
kube-system   service/monitoring-influxdb     ClusterIP   <IP_ADDRESS>   <none>        8083/TCP,8086/TCP   150m
NAMESPACE     NAME                               DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR                              AGE
kube-system   daemonset.apps/fluentd-es-v2.2.0   1         1         1       1            1           beta.kubernetes.io/fluentd-ds-ready=true   3m49s
NAMESPACE     NAME                                             READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/heapster-v1.5.2                  0/1     1            0           150m
kube-system   deployment.apps/kibana-logging                   1/1     1            1           3m49s
kube-system   deployment.apps/kube-dns                         0/1     1            0           4m10s
kube-system   deployment.apps/kubernetes-dashboard             0/1     1            0           150m
kube-system   deployment.apps/monitoring-influxdb-grafana-v4   0/1     1            0           150m
NAMESPACE     NAME                                                        DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/heapster-v1.5.2-6d56f4bd4b                  1         1         0       150m
kube-system   replicaset.apps/kibana-logging-764d446c7d                   1         1         1       3m49s
kube-system   replicaset.apps/kube-dns-6c4b646d76                         1         1         0       4m10s
kube-system   replicaset.apps/kubernetes-dashboard-666f999c67             1         1         0       150m
kube-system   replicaset.apps/monitoring-influxdb-grafana-v4-8457fbf595   1         1         0       150m
NAMESPACE     NAME                                     READY   AGE
kube-system   statefulset.apps/elasticsearch-logging   1/1     3m49s

The kibana service, on the other hand, is working fine.

Hi @aserrallerios
I see you are on Majaro. There is an issue reported for Arch Linux were MicroK8s is not able to identify the machine architecture. The workaround as described here: https://github.com/ubuntu/microk8s/issues/364 is to yay -S libselinux. Could you please try this?
We have already a PR ready to be merged with a permanent fix https://github.com/ubuntu/microk8s/pull/365 . It is under review, we would appreciate any feedback.

Hi @ktsakalozos,
Yeah, that was it... I did see the issue but I was not sure it related to my problem.
I had a look at the PR but I'm afraid I cannot help much on it, anyway, hope it gets merged soon!
Many thanks!


Rancher 2.5 Air-gap goes to github

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Similar to this one: (took some information from community forum that have the same issue)
docker run -d --restart=unless-stopped
-p 80:80 -p 443:443
-e CATTLE_SYSTEM_CATALOG=bundled
-e CATTLE_SYSTEM_DEFAULT_REGISTRY=secretregistry/docker.io-mirror
-v /etc/rancher/ssl/hostcert.crt:/etc/rancher/ssl/cert.pem
-v /etc/rancher/ssl/hostkey.key:/etc/rancher/ssl/key.pem \
-v /etc/rancher/ssl/cacert.pem:/etc/rancher/ssl/cacerts.pem \
-v /opt/rancher:/var/lib/rancher \
-e AUDIT_LEVEL=1
-v /var/log/rancher/auditlog:/var/log/auditlog \
--privileged \
"secretregistry/docker.io-mirror/rancher/rancher:latest”
The same settings with 2.4.x latest we found, is working.
This is for the local cluster that it´s creates, did not add a new cluster, so do not know if that works.
Result:
Feb 4 20:36:01 RTST-A0101 journal: E0204 19:36:01.531114 40 kuberuntime_manager.go:727] createPodSandbox for pod “helm-operation-p7d4h_cattle-system(b32591c0-b958-4f1d-93b9-dd2c7c419cf7)” failed: rpc error: code = Unknown desc = failed to get sandbox image “docker.io/rancher/pause:3.1”: failed to pull image “docker.io/rancher/pause:3.1”: failed to pull and unpack image “docker.io/rancher/pause:3.1”: failed to resolve reference “docker.io/rancher/pause:3.1”: failed to do request: Head https://registry-1.docker.io/v2/rancher/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout
Feb 4 20:36:01 RTST-A0101 journal: E0204 19:36:01.531168 40 pod_workers.go:191] Error syncing pod b32591c0-b958-4f1d-93b9-dd2c7c419cf7 (“helm-operation-p7d4h_cattle-system(b32591c0-b958-4f1d-93b9-dd2c7c419cf7)”), skipping: failed to “CreatePodSandbox” for “helm-operation-p7d4h_cattle-system(b32591c0-b958-4f1d-93b9-dd2c7c419cf7)” with CreatePodSandboxError: “CreatePodSandbox for pod “helm-operation-p7d4h_cattle-system(b32591c0-b958-4f1d-93b9-dd2c7c419cf7)” failed: rpc error: code = Unknown desc = failed to get sandbox image “docker.io/rancher/pause:3.1”: failed to pull image “docker.io/rancher/pause:3.1”: failed to pull and unpack image “docker.io/rancher/pause:3.1”: failed to resolve reference “docker.io/rancher/pause:3.1”: failed to do request: Head https://registry-1.docker.io/v2/rancher/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout”
Feb 4 20:36:02 RTST-A0101 journal: E0204 19:36:02.530509 40 remote_runtime.go:105] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed to get sandbox image “docker.io/rancher/pause:3.1”: failed to pull image “docker.io/rancher/pause:3.1”: failed to pull and unpack image “docker.io/rancher/pause:3.1”: failed to resolve reference “docker.io/rancher/pause:3.1”: failed to do request: Head https://registry-1.docker.io/v2/rancher/pause/manifests/3.1: dial tcp <IP_ADDRESS>:443: i/o timeout

Has it been resolved? I encountered the same problem, but did not find a related solution......


[Settings] App passwords revamp

Stacked on #5775
Animations tested on iOS, Android, and Web
https://github.com/user-attachments/assets/21c9f4bd-0412-43df-bfec-dd1270feed28

Thanks @surfdude29 - I don't know what I'd do without you! You contributions are extremely appreciated, thanks as always

Highlighting something that might not be a good design pattern. It took me a good moment to realize the error was under the input box, and that it was even an error message. Part of me feels that and admonition above the form is actually better for this case.


XY mode

HI
Is XY mode possible (for lissajous, magnetic histeresys etc).
I'm not really sure if it can be done in any simple way
I was thinking about dual port BRAM as scan-line buffer.
Length of 2 video scan lines is buffered, one line is being output
for display while the other is being drawn with pixel content
traces grids etc.
Such concept will (I hope) completely get rid you from delay (align module)
because pixels can be written asynchronously from display during one scan line.
The BRAM port for line buffer when it displays every pixel it can can also clear
the pixel with background color at the same clock cycle on when this pixel is gone
to monitor for display
this method is called write-while-read (or destructive read, some memories in hardware
internally must actually destroy a bit in order to read it).
I use this for video 2D acceleration (sprites) and it works on BRAMs at spartan6, artix7,
cyclone4, ecp5, fx2, machox2

The trace system only writes vertical lines and its very simple and can't do much more. I don't think It is able to do that.
For me, everything is about cost ... I don't know how much the cost is  in resources, I mean the BRAM and the control system compare to what it is working now. Graphics modules(grid, axis, traces, etc) have different latencies and align balance all the data to be just in time to be combined. If I understood it correctly, every module has to write its data to the memory at its time for the video to display then. But they will end only with one port of the BRAM as the other is accessed by the video system, so only one port will be shared by several modules which want to write and in the end the frequency of this modules that depend on the video  should be increased because the graphic modules generates the data with different latencies
I am not a lover of align ... but it is flexible enough ... it works as a FIFO ... any solution that gives flexibility and gets rid of it is welcome

well yes that is true, only one BRAM port has to be shared by different
modules and that can introduce a nasty multiplexer which will cut off fmax
On 7/19/19, Miguel Angel<EMAIL_ADDRESS>wrote:

The trace system only writes vertical lines and its very simple and can't do
much more. I don't think It is able to do that.
For me, everything is about cost ... I don't know how much the cost is  in
resources, I mean the BRAM and the control system compare to what it is
working now. Graphics modules(grid, axis, traces, etc) have different
latencies and align balance all the data to be just in time to be combined.
If I understood it correctly, every module has to write its data to the
memory at its time for the video to display then. But they will end only
with one port of the BRAM as the other is accessed by the video system, so
only one port will be shared by several modules which want to write and in
the end the frequency of this modules that depend on the video  should be
increased because the graphic modules generates the data with different
latencies
I am not a lover of align ... but it is flexible enough ... it works as a
FIFO ... any solution that gives flexibility and gets rid of it is welcome
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/hdl4fpga/hdl4fpga/issues/159#issuecomment-513034465


  We need to revert in order to bump all the operators, then we need to do a fake bump in KAS-o to sort it out.

/lgtm


[staging] openssh: 8.6p1 -> 8.7p1

Motivation for this change
https://lwn.net/Articles/866926/
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests) openssh.nix
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.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

[x] Fits CONTRIBUTING.md.

tested ssh and ssh-add on aarch64-darwin

Can we backport this to 21.05? My server is suffering from https://bugzilla.mindrot.org/show_bug.cgi?id=3286

You could check if 8c396f42c19 applies on 21.05


[release 1.1] Prepare release 1.1.1

What type of PR is this?

What this PR does / why we need it:
Prepare README and bundle version for 1.1.1
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

NONE

Thanks @mlavacca!
/lgtm
/approve

/hold

any rough ETA on this release @mlavacca ? trying to time it with an Envoy Gateway patch release, would be great if this can be released by tomorrow, tia

@arkodg Yep, the plan is to release this tomorrow (31st).

/unhold


[SPARK-10988] [SQL] Reduce duplication in Aggregate2's expression rewriting logic

In aggregate/utils.scala, there is a substantial amount of duplication in the expression-rewriting logic. As a prerequisite to supporting imperative aggregate functions in TungstenAggregate, this patch refactors this file so that the same expression-rewriting logic is used for both SortAggregate and TungstenAggregate.
In order to allow both operators to use the same rewriting logic, TungstenAggregationIterator. generateResultProjection() has been updated so that it first evaluates all declarative aggregate functions' evaluateExpressions and writes the results into a temporary buffer, and then uses this temporary buffer and the grouping expressions to evaluate the final resultExpressions. This matches the logic in SortAggregateIterator, where this two-pass approach is necessary in order to support imperative aggregates. If this change turns out to cause performance regressions, then we can look into re-implementing the single-pass evaluation in a cleaner way as part of a followup patch.
Since the rewriting logic is now shared across both operators, this patch also extracts that logic and places it in SparkStrategies. This makes the rewriting logic a bit easier to follow, I think.

/cc @yhuai for review.

Merged build triggered.

Merged build started.

Test build #43358 has started for   PR 9015 at commit fb0daa1.

Test build #43358 has finished for   PR 9015 at commit fb0daa1.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Average(child: Expression) extends DeclarativeAggregate
case class Count(child: Expression) extends DeclarativeAggregate
case class First(child: Expression) extends DeclarativeAggregate
case class Last(child: Expression) extends DeclarativeAggregate
case class Max(child: Expression) extends DeclarativeAggregate
case class Min(child: Expression) extends DeclarativeAggregate
abstract class StddevAgg(child: Expression) extends DeclarativeAggregate
case class Sum(child: Expression) extends DeclarativeAggregate

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43358/
Test FAILed.

Jenkins, retest this please.

Merged build triggered.

Merged build started.

Test build #43363 has started for   PR 9015 at commit fb0daa1.

Merged build triggered.

Merged build started.

Test build #43364 has started for   PR 9015 at commit fb0daa1.

Test build #43363 has finished for   PR 9015 at commit fb0daa1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43363/
Test PASSed.

Merged build finished. Test PASSed.

Test build #43364 has finished for   PR 9015 at commit fb0daa1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43364/
Test PASSed.

LGTM. Merging to master.


tetragon: handle process threads in clone and process_{exec|exit} events

This PR adds the TID the thread ID to Process object and then it adds support to clone and process_exec|exit events.
The TID makes more sense in kprobe and tracepoints, however since we share the Process object with process_exec, let's reuse it here and ensure that the TID is not zero during process_{exec|exit}
For more details, see commits.

Thanks!
The patch looks good to me, overall. Having this will certainly make our events more robust.
I have some nits, but the main thing I'd like to ensure we do right is always using the thread id from the bpf side rather than the one from the cache. This is something you mention in the comments, and I fully agree but it's not 100% clear to me that it is reflected in the implementation.

Sure that's the aim! so for this PR that handles process_exec/exit we do use the one from BPF side, let's break it please:
* process_exec is received:
  `(msg *MsgExecveEventUnix) HandleMessage()->GetProcessExec(msg, true)->process.AddExecEvent()->GetProcess(process MsgProcess)-> Tid: &wrapperspb.UInt32Value{Value: process.TID},` , so  AddExecEvent() constructs it, add it to the cache and return it for the event , we should be good.

* process_exit with a cache hit, then good we just read it from the cache and that is same value that was added by Clone or Execve one. If an execve happens by another thread other than the thread leader, then tgid and tid transfert should happen and the thread exec'in is the new thread leader with same old values , but we still record that from BPF and return it to update the cache entry.

* process_exit without a cache hit: then we just use the TID returned from BPF side.

Specifically, we seem to be adding the thread id in the process cache. Is there a reason for it? Shouldn't we always use the thread id we get from the bpf side?

So I updated the series and converted the process_exit to always use the bpf TID for both cache hit or miss paths.
Now all events use BPF value, the execve is same one, just the implementation happens to be like that, plus I added warning to ensure that we log in case TID is not set and events are being reported without it..
Much appreciated for your time @kkourt @tpapagian ;-)


ValidateRequestHeaders now not only accept ", " as separator

see RFC2616:
message-header = field-name ":" [ field-value ]
field-name     = token
field-value    = *( field-content | LWS )
CR             = <US-ASCII CR, carriage return (13)>
LF             = <US-ASCII LF, linefeed (10)>
SP             = <US-ASCII SP, space (32)>
HT             = <US-ASCII HT, horizontal-tab (9)>
CRLF           = CR LF
LWS            = [CRLF] 1*( SP | HT )

Coverage decreased (-0.2%) to 99.16% when pulling fb3c9a80efb4f63dc3771fae1da544e75f4371dc on Gnukos:master into 9526714e382db4023de25bfdad89cec9b7446092 on itsjamie:master.

Thanks!
I went through and looked at the CORS spec and they do reference 2616 rather than 7231 which defines headers as defaulting to optional white-space rather than linear whitespace which includes these characters.


Player Moving to Next Level

As George I want to be moved to the next level of the game once I complete all the required tasks.


Add boolean wrap value to result of measure function

Useful for laying out justify-aligned text
Added unit tests
Updated documentation

See https://github.com/Jam3/layout-bmfont-text/pull/5

@mattdesl I see the Travis CI build is failing, but this seems to be a problem with the configuration rather than my changes. Looks like it's missing a rakefile? The test passes on my machine. If you'd like to fix the CI config, I'm happy to merge that into my branch and update the PR.


Link error

Please change logo of 'Dribbble' to 'Instagram' as it redirects to an Instagram account

Hey @vedantk21 ,
So nice of you giving feedback but that's the old preview you can see the latest build at https://gradiot.club/ that hass all the fixes.


Updated Conditions for Endpoint

Docs Build status updates of commit 6789d42:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/compliance/dlp-policy-reference.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@chrfox , submitted for your review

Docs Build status updates of commit a0bb661:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/compliance/dlp-policy-reference.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Error: Request timed out

Does your bot support http proxy? I got this error when trying to use bot:

[10:33:40] Bot Error
Error: Request timed out (>15000ms) on GET /gateway
at ClientRequest. (Discord-SelfBot\node_modules\eris\lib\rest\RequestHandler.js:256:32)
at Object.onceWrapper (events.js:293:19)
at emitNone (events.js:86:13)
at ClientRequest.emit (events.js:188:7)
at TLSSocket.emitTimeout (_http_client.js:679:10)
at Object.onceWrapper (events.js:293:19)
at emitNone (events.js:86:13)
at TLSSocket.emit (events.js:188:7)
at TLSSocket.Socket._onTimeout (net.js:351:8)
at ontimeout (timers.js:386:14)

@koperkiewicz This just means the request the bot sent to discord took longer to process than what discord was prepared to wait. So its most likely a connection issue, either on discord's end or on your end.


Backtester - documentation request

Readme and wiki page says that Tribeca packaged with backtesting mode. But how to run and use it?

hope this helps: https://github.com/michaelgrosner/tribeca/search?utf8=✓&q=inBacktestMode

I agree, a bit of documentation on backtesting would  be very helpful.

@michaelgrosner What market data do you use for backtesting? What format does Tribeca require?

Looking at this line and this section, it seems to take a JSON array of Markets (timestamped order books) or MarketTrades (timestamped trade records). All the Bitcoin market data I've found only has price data, so it seems like recording realtime data from the exchanges is the best bet.

try installing mocha and run test/*.ts files, like:
mocha --compilers ts:ts-node/register test/*.ts
you can see the backtests running at https://travis-ci.org/ctubio/tribeca/jobs/194689928


Include Spanish translation

This pull request adds a Spanish translation to the project.

thanks for your contribution.

Hi @blasferna, released this with the 0.2.4 tag into GitHub and PyPi.


Error behavior?

For my own edification, I'm curious as to why match(x).to(y, function() {}); throws an error, but not match(x, function() {});? It was added here, but without much explanation.

That is something that should be considered a bug. Addressed in the reworking of this library and closing here.


Docs: search results not visible

The search results are cut off. This prevents me from finding information

You could probably inspect the text via developer tools and check the dom.


InputOffset undefined

I don't know anything about go and probably won't learn.  I installed go version go1.3.3 linux/arm (from Raspbian debs) on one of my Raspberry Pi 3B's for hilink and I get this:
go get -u github.com/knq/hilink
github.com/clbanning/mxj
/usr/tmp/gopath/src/github.com/clbanning/mxj/xmlseq.go:308: p.InputOffset
undefined (type *xml.Decoder has no field or method InputOffset)

You need to be running a new version of Go. Go1.3 is 3 years old now -- the call API being used in the mxj package wasn't introduced until after Go1.3.


Fix/codelab basics 1 text

Here are a few suggestions to the text of the codelabs.

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

Thanks a lot guys


vue-cli-service: not found

Version
5.0.0-alpha.5
Reproduction link
https://cnspecialcolor.web.app
Environment info
https://console.firebase.google.com/project/cnspecialcolor/hosting/sites

Steps to reproduce
sudo npm run build
What is expected?
arthur@Arthur:~/Desktop/digital-ocean-app$ npm run build

<EMAIL_ADDRESS>build
react-scripts build

Creating an optimized production build...
Compiled successfully.
File sizes after gzip:
41.34 KB  build/static/js/2.a7ce996d.chunk.js
1.6 KB    build/static/js/3.cb767c74.chunk.js
1.17 KB   build/static/js/runtime-main.b3831708.js
599 B     build/static/js/main.f76335c5.chunk.js
531 B     build/static/css/main.8c8b27cf.chunk.css
The project was built assuming it is hosted at /.
You can control this with the homepage field in your package.json.
The build folder is ready to be deployed.
You may serve it with a static server:
yarn global add serve
serve -s build
Find out more about deployment here:
https://cra.link/deployment
arthur@Arthur:~/Desktop/digital-ocean-app$ firebase deploy
What is actually happening?
arthur@Arthur:~/Desktop/sub-web-master$ sudo npm run build
[sudo] password for arthur:

<EMAIL_ADDRESS>build
vue-cli-service build

sh: 1: vue-cli-service: not found
arthur@Arthur:~/Desktop/sub-web-master$ sudo npm run build

Please follow the instructions in the issue helper to fill in the accurate information;
Have you run npm install before running npm run build?


How frequently does catch pull down new episodes?

I can't see any settings that shows how frequent catch checks for new episodes, nor is it in any documentation I can find.
Thanks!

Hi!
That's undocumented by design :) For two reasons mainly: users shouldn't have to care if we do our job right, and we can change that value with no advertising in case @adrinavarro thinks we're hitting the servers too hard.
Anyway, it's currently every 10 minutes. You can find the value defined here: https://github.com/mipstian/catch/blob/master/CTCDefaults.m#L7
And even if we change it, it'll still be in the "defaults" code.

Ok thanks!  gtk
Hun Kim | GH Kim Photography http://ghkim.com
[image: Instagram] http://instagram.com/hunkim   [image: Facebook]
http://facebook.com/ghkimphotography   [image: Twitter]
http://twitter.com/hunkim   [image: RSS]
http://feeds.feedburner.com/ghkim   [image: Subscribe]
http://ghkim.com/subscribe
On Tue, Mar 10, 2015 at 9:13 AM, Giorgio Calderolla <
<EMAIL_ADDRESS>wrote:

Closed #59 https://github.com/mipstian/catch/issues/59.
—
Reply to this email directly or view it on GitHub
https://github.com/mipstian/catch/issues/59#event-249438242.


Add a function:  minimize to the tray icon , so that subsequent use can be quickly opened.

VSCode Version: 1.10
OS Version: win7

Steps to Reproduce:

open vscode and close it, and reopen it.
still the same slow when i open it again and again

want: faster load speed

Thanks for the suggestion. Faster load speed is always our priority and you can see that  every milestone we assign resources to this.
Closing as we already have this on the plan

all right, thanks!


Create SECURITY.md

@renatomarinho any update on this? Would like a valid SECURITY.MD with a valid email inn it so I can report a few issues.


added CONTRIBUTION.md

just a start

Thanks @bilo-io! This is a good start - much appreciated 🙏
I've added a few comments with what I think needs to change before we can merge this. I can take a stab at making some of the changes if you like.
Also, may I suggest splitting the code of conduct into its own file and a separate PR from the workflow stuff that needs editing?

I've added the Contributor Covenant v1.4.1 in #55 so we can focus purely on workflow documentation in CONTRIBUTING.md.


(feat): Converting pumba daemonset to job with node selector

Signed-off-by: Raj<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Checklist

[x] Does this PR have a corresponding GitHub issue?
https://github.com/litmuschaos/litmus/issues/1225
[ ] Have you included relevant README for the chaoslib/experiment with details?
[ ] Have you added debug messages where necessary?
[ ] Have you added task comments where necessary?
[ ] Have you tested the changes for possible failure conditions?
[ ] Have you provided the positive & negative test logs for the litmusbook execution?
[ ] Does the litmusbook ensure idempotency of cluster state?, i.e., is cluster restored to original state?
[ ] Have you used non-shell/command modules for Kubernetes tasks?
[ ] Have you (jinja) templatized custom scripts that is run by the litmusbook, if any?
[ ] Have you (jinja) templatized Kubernetes deployment manifests used by the litmusbook, if any?
[ ] Have you reused/created util functions instead of repeating tasks in the litmusbook?
[ ] Do the artifacts follow the appropriate directory structure?
[ ] Have you isolated storage (eg: OpenEBS) specific implementations, checks?
[ ] Have you isolated platform (eg: baremetal kubeadm/openshift/aws/gcloud) specific implementations, checks?
[ ] Are the ansible facts well defined? Is the scope explicitly set for playbook & included utils?
[ ] Have you ensured minimum/careful usage of shell utilities (awk, grep, sed, cut, xargs etc.,)?
[ ] Can the limtusbook be executed both from within & outside a container (configurable paths, no hardcode)?
[ ] Can you suggest the minimal resource requirements for the litmusbook execution?
[ ] Does the litmusbook job artifact carry comments/default options/range for the ENV tunables?
[ ] Has the litmusbooks been linted?

Special notes for your reviewer:
Logs

container-kill using pumba.txt
containerd_log.txt

pumba-logs.txt

containerd-logs.txt


Path's assertions should not rely on java.nio.Path.toFile() (fixes #439)

After these changes the memoryfilesystem dependecy can be replaced with jimfs and all tests still succeed.

Thx


support optional chaining in unit test files

with a pointer from @raathigesh I was able to add support to babel which allows unit tests to contain statements that use the new optional chaining syntax.
This is necessary because Majestic processes the unit test file with a locally configured copy of babel. We had to add the experimental plugin for optional chaining to babel.
This fixes issue #164

Looks good to me. Thanks for the PR 👍
@allcontributors please add @gregveres for bug and code


Minor fixes for pod-network-loss and latency experiments

What this PR does / why we need it: Minor fixes for pod-network-loss and latency experiments' README-files
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Checklist

[ ] Does this PR have a corresponding GitHub issue?
[ ] Have you included relevant README for the chaoslib/experiment with details?
[ ] Have you added debug messages where necessary?
[ ] Have you added task comments where necessary?
[ ] Have you tested the changes for possible failure conditions?
[ ] Have you provided the positive & negative test logs for the litmusbook execution?
[ ] Does the litmusbook ensure idempotency of cluster state?, i.e., is cluster restored to original state?
[ ] Have you used non-shell/command modules for Kubernetes tasks?
[ ] Have you (jinja) templatized custom scripts that is run by the litmusbook, if any?
[ ] Have you (jinja) templatized Kubernetes deployment manifests used by the litmusbook, if any?
[ ] Have you reused/created util functions instead of repeating tasks in the litmusbook?
[ ] Do the artifacts follow the appropriate directory structure?
[ ] Have you isolated storage (eg: OpenEBS) specific implementations, checks?
[ ] Have you isolated platform (eg: baremetal kubeadm/openshift/aws/gcloud) specific implementations, checks?
[ ] Are the ansible facts well defined? Is the scope explicitly set for playbook & included utils?
[ ] Have you ensured minimum/careful usage of shell utilities (awk, grep, sed, cut, xargs etc.,)?
[ ] Can the limtusbook be executed both from within & outside a container (configurable paths, no hardcode)?
[ ] Can you suggest the minimal resource requirements for the litmusbook execution?
[ ] Does the litmusbook job artifact carry comments/default options/range for the ENV tunables?
[ ] Has the litmusbooks been linted?

Special notes for your reviewer:

Thanks @LaumiH ! One thought: now that we have the experiment docs maintained at docs.litmuschaos.io do you think it would be useful to redirect there?

Definitely, would make a lot more sense than always remembering to generate the docs and edit these READMEs.

Cool! Could you change the PR/README content to redirect to docs page then ?

Thanks, @LaumiH for the contribution in litmus.


Use startingTime from playlist tracks & onTimeUpdate prop

Solves #365

@benwiley4000 Do you want to help me with the documentation?

So it seems like this could actually be two different pull requests:

Using canplay to set trackLoading: false
The onTimeUpdate callback prop and the startingTime API

I think #1 is basically ready to merge as soon as my comment about force load is addressed.
I'm not totally sure about #2 yet, needs more more thought.. so maybe we can pull out #1 and merge it now?
Also to answer your earlier question: yes I would always love help with documentation!! ☺

Makes sense, let me get 1 prepared.

Ok honestly.. I've spent some time thinking through alternatives again and I think the solution you have implemented makes the most sense. This is an advanced feature and anyone using it will probably be dynamically updating the playlist anyway, so having to update the playlist contents with an updated startingTime should be no big deal.

Is there any file to document startingTime? If not, we only have to add the onTimeUpdate info, and it would be ready to merge.

Everything about the playlist is documented currently here (might be a bit out of date?). I'd stick the info there. I need to integrate that somehow into the docs website eventually. If you have any ideas, go for it!

Yeah, I saw that one, but it doesn't have anything related to playlist tracks structure/fields

Sorry you're right. I got confused.
My plan was to eventually document some of the more complicated PropTypes for PlayerContextProvider, maybe in its markdown file? The info would be similar to what's currently in the README.md but updated for version 2

Maybe we can work on it in another PR, to document all the playlisy track
fields.
On Sat, Feb 16, 2019, 9:24 PM Ben Wiley<EMAIL_ADDRESS>wrote:

Sorry you're right. I got confused.
My plan was to eventually document some of the more complicated PropTypes
for PlayerContextProvider, maybe in its markdown file? The info would be
similar to what's currently in the README.md but updated for version 2
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/benwiley4000/cassette/pull/369#issuecomment-464402482,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIoKWL5aq0YIWemEjjy1JN2NhFx93eg_ks5vOKFbgaJpZM4a-yht
.

That sounds good to me!

And to leave comments for all the PropTypes so they show up in the docs

Thanks!

Released in v2.0.0-alpha.27 (has breaking changes, see the release notes)

BTW, if you think onActiveTrackUpdate should be passed info on the previous track and the currentTime to make things easier.. I'd be open to having that in a separate PR.

I ended up doing this in the latest release. Not there are some small breaking changes in the API. https://github.com/benwiley4000/cassette/releases/tag/v2.0.0-alpha.32


SMTChecker

We should do the initial setup of this https://docs.soliditylang.org/en/v0.8.19/smtchecker.html
I presume there will be modifications we need to do to the code to get this to work, those can be in separate bounties after this is feature is set up.
https://twitter.com/paulrberg/status/1627654614811115520?s=46&t=lQUXMD9A0xd14FiMGl8IEQ

Hi @pavlovcik
Can you assign this bounty to me?

Have been busy last couple of days. I plan picking this again over the next week, feel free to reassign it to another person if needed 🙂

The bot should automatically unassign you if you do not reply after a full week of inactivity!

@0xcodercrane until we officially transition to making "no assignee" the default DevPool role, the bot should technically reassign to @ubiquity-bounties!

/assign

/assign

@chrlschwb sorry we were doing maintenance on the bot this week and you must have attempted the assign command just as it went down! Please feel free to work on this!

@pavlovcik is this still an active issue. It's quite confusing with the comments.

@pavlovcik is this still an active issue. It's quite confusing with the comments.

Yes it's available. You can tell from the lack of assignee on the issue!

/assign

Do you have any updates @FibrinLab? If you would like to release the bounty back to the DevPool, please comment /unassign

Waiting for review

You should re-request reviews from specific reviewers once you incorporated their feedback.

Do you have any updates @FibrinLab? If you would like to release the bounty back to the DevPool, please comment /unassign

I have updates

You should re-request reviews on the pull request when you implement changes after our reviews.

@0xcodercrane check this assign behavior

@pavlovcik i would assume the bots auto-assing time labeling base don what he thinks the task time would be, but i don't consider this one less than a day

How long do you think this task will take? Currently we set the time estimates manually based on a guess. @rndquu what do you think on the time estimate?

less than a week is approchable, but could be matcher sooner

As long as another core team member agrees then we can change it to Time: <1 Week!
Unfortunately I am not familiar with this tech.

perhaps, we could add to the bot, 2 time 1 considering and the other at last, (in less than and at last) also after a couple of weeks it looks like the bot did not unassigned the hunter

/assign

This task is about a CI workflow
So in this issue we should create a workflow that runs SMT checker
There is already an almost ready PR so 1 day is enough for this issue
Fixing SMT errors will be a part of the other issue

The SMT it's time constrained, I'm about to open a PR, but you should already know that checking the files just for the sake of testing takes a LOT of time, and am on fast hardware

a LOT of time

How long exactly?
Could you also provide the SMT log?

4 minutes to output something in just 1 contract using time, i got a good solution, but the time setback it's part of the module (SMT) there's a lot of saying in the solidity's github issues

Z3 building (C++) (required) by SMT https://github.com/molecula451/ubiquity-dollar/actions/runs/5316439907/jobs/9625970853 took 30 min the action to build only the dependencies. It's not suitable to use the libraries that comes with ubuntu, best it to build it, because there is hack to make it work on the compiler due to an issue they have not fixed yet, source: https://github.com/ethereum/solidity/issues/13073
Kindly extend the task label expiration

This task is about a CI workflow
So in this issue we should create a workflow that runs SMT checker
There is already an almost ready PR so 1 day is enough for this issue
Fixing SMT errors will be a part of the other issue

The SMT it's time constrained, I'm about to open a PR, but you should already know that checking the files just for the sake of testing takes a LOT of time, and am on fast hardware

a LOT of time

How long exactly?
Could you also provide the SMT log?

Z3 building (C++) (required) by SMT https://github.com/molecula451/ubiquity-dollar/actions/runs/5316439907/jobs/9625970853 took 30 min the action to build only the dependencies. It's not suitable to use the libraries that comes with ubuntu, best it to build it, because there is hack to make it work on the compiler due to an issue they have not fixed yet, source: https://github.com/ethereum/solidity/issues/13073
Kindly extend the task label expiration

How long exactly?

Z3 building (C++) (required) by SMT https://github.com/molecula451/ubiquity-dollar/actions/runs/5316439907/jobs/9625970853 took 30 min the action to build only the dependencies. It's not suitable to use the libraries that comes with ubuntu, best it to build it, because there is hack to make it work on the compiler due to an issue they have not fixed yet, source: ethereum/solidity#13073
Kindly extend the task label expiration

I don't get why we need to install Z3 solver
I thought we should simply update a foundry config and run forge build in a CI workflow

I don't get why we need to install Z3 solver

This makes worth the bounty. The real reason we need Z3 Solver it's because Ubuntu ships with Z3 Binary, but not with the Z3 Headers (library) installed, required by solidity compiler to read that indeed exists and it handles the work this can be achieved by compiling the library and make install from within the compilation

I thought we should simply update a foundry config and run forge build in a CI workflow

No, it's not enough because you would get

Library installed
With the library installed you'll get actual results

You would be able to run the SMT Checker but not recursively across all the contracts
There is a machine running here with a good config to run the checker for ALL the contracts available https://github.com/molecula451/ubiquity-dollar/actions/runs/5331895073 it just clogged! for many hours, no matter in what hardware you are running, you'll mostly won't get results for over 200+ contracts recursively
I suggest we keep this task locally instead of handling it as a github action
This is a time constrained task. because of the debugging process in both compilation time && github actions time
the Z3 building takes a lot of time, like 30 minutes
a PR It's incoming get ready for this

I don't get why we need to install Z3 solver

This makes worth the bounty. The real reason we need Z3 Solver it's because Ubuntu ships with Z3 Binary, but not with the Z3 Headers (library) installed, required by solidity compiler to read that indeed exists and it handles the work this can be achieved by compiling the library and make install from within the compilation

I thought we should simply update a foundry config and run forge build in a CI workflow

No, it's not enough because you would get

Library installed
With the library installed you'll get actual results

You would be able to run the SMT Checker but not recursively across all the contracts
There is a machine running here with a good config to run the checker for ALL the contracts available https://github.com/molecula451/ubiquity-dollar/actions/runs/5331895073 it just clogged! for many hours, no matter in what hardware you are running, you'll mostly won't get results for over 200+ contracts recursively
I suggest we keep this task locally instead of handling it as a github action
This is a time constrained task. because of the debugging process in both compilation time && github actions time
the Z3 building takes a lot of time, like 30 minutes
a PR It's incoming get ready for this

Could you share a CI run with the libz3.so not found error?
Perhaps we could setup a workflow with manual dispatch that checks a single contract from env variable. This way we could check all the contracts step by step. What do you think?

Perhaps we could setup a workflow with manual dispatch that checks a single contract from env variable. This way we could check all the contracts step by step. What do you think?

You have one here https://github.com/molecula451/ubiquity-dollar/actions/runs/5327648976/jobs/9651321338
This CI run has the compiler error, this is a pre-defined solidity error, nothing wrong with the enviroment, it's pointing that you don't have the library to run Z3 (which it's best that other solvers, IMO)
I am rendering something, and will provide more input

GitHub Actions can run for six hours so I don't expect time to be an issue.

Thanks for your explanations molecula451. GitHub Actions can run for six hours so I don't expect timeouts to be an issue.

Job execution time - Each job in a workflow can run for up to 6 hours of execution time. If a job reaches this limit, the job is terminated and fails to complete.

Your input it's always amazing, awesome friend. Yeah it didn't last, it's too compute intensive. I dropboxed a full video here playing with the SMTChecker and the contracts
https://www.dropbox.com/s/wkgqjir8msrwxa1/full_smt.mp4?dl=0

Perhaps we could setup a workflow with manual dispatch that checks a single contract from env variable. This way we could check all the contracts step by step. What do you think?

@rndquu The SMTChecker tasks it's just too intensive for CI. because under the hood it's not only the compiler working, it is the Z3 Solver which goes down to the hardware level. We better keep this task locally
The SMTChecker it's not suitable for CI Run, there are many reasons, the Solvers are task intensive, even on fast hardware it takes a while to output checker logs. Check the video
Not all the contracts are gonna output about SMTChecker
Some contracts will just compile and that's it, even tho they were scanned using the checker
AccesControlInternal is one of them

The SMTChecker Uses all the possibles checking targets

assert,
constantCondition,
divByZero,
outOfBounds,
overflow,
popEmptyArray,

but it won't output results for all of em if it doesn't exists a particular issue with this in the contract, this searching is task intensive, Z3 under the hood
Don't think you won't get false positives
There are many false positives using the SMTChecker, you are in a heavy (many contracts compiling at the same tiem) computing intensive, and you'll get many falses positives? again not good for CI
Foundry has a bug with SMTChecker
it is clearly state to use show_unproved to output further results we're using show_unproved = True in our foundry
config:

you still get things like:

In it's current stage this tasks is suitable for local use and to make it use when need it by team, when new contributions are made to the contracts, to pass the checker, but not on CI
it'll be much the time/trouble that you'll dealt, than the output logs you'll need to make sure something it's good with the checker
You may deal with other Solvers
Again, to reach to this conclusion, was timely constrained and heavy compute intensive, further testing for the infrascture would be deal with other solvers, but those requires to further include 3rd party dependencies to the project
PR at https://github.com/ubiquity/ubiquity-dollar/pull/702

thanks a lot awesome friends!! @pavlovcik && @rndquu


Regexp unable to distinguish upper and lower case ASCII characters

As far as I know, this is by design, but I don't understand the reason behind it.
One use case that would be useful is using only uppercase characters in empty links used as delimiters for different feeds in the urls file.

I wasn't around back than, but apparently it was so from day 1:

=~ and !~ in filters, e.g. ignore-article: https://github.com/newsboat/newsboat/commit/79adeedd44277c41793ca0e31ede89c1778b818a
highlight and highlight-article: https://github.com/newsboat/newsboat/commit/f647d92a84c0cdc00b660a32b70d0528a49bb3f0

No idea why, though.

One use case that would be useful is using only uppercase characters in empty links used as delimiters for different feeds in the urls file.

I understand what delimiters you're talking about (#412), but I don't get why case would play any role here. Can you give me an example? I guess I need your highlight rules and a part of your urls file.
As for the underlying issue, a short-term fix might be a new setting that instructs Matcher and RegexManager to add or omit REG_ICASE flag when compiling the regex (with a caveat that changing a setting during runtime won't affect already-compiled regexes). This is blocked by #631 and by ConfigContainer being unavailable from Rust (I'll file an issue about that).

Oh, and a long-term solution would be to add flags to regexes, like /regex/i in Perl. This will also make the previous caveat obvious: if you didn't specify a flag, or specified a different one, and now you can't change the regex (because e.g. you can't change highlight rules in runtime), the decision is fixed and you can't affect it.

I understand what delimiters you're talking about (#412), but I don't get why case would play any role here. Can you give me an example? I guess I need your highlight rules and a part of your urls file.

highlight all "^[A-Z]+$" red for highlighting MATHEMATICS.
Currenly in my urls file I use a fancy thick dash to highlight such delimiters, but I would prefer to have a more noticeable alternative.
The issue you linked seems to be a more appropriate place to discuss my use case, but maybe a more "normal" regexp implementation will cover some other situations I can't envision.

Ah, got it. I'm afraid that your approach will still have false positives even when Newsboat starts taking case into account; for example, your regex would highlight "RSS" and "USA", which aren't your labels.
The only real solution for that is #412 (so Newsboat "knows" which lines are delimiters and which ones are text, and can highlight them differently), but in the meantime, you can leverage your thick dash to disambiguate between them: highlight all "^[A-Z]+ ─+$" red.
Радий зустріти співвітчизника ^_^ Якщо користуєшся українською локалізацією і побачиш помилку — пиши, а краще надсилай патч (усе в файлі po/uk.po). Я, чесно кажучи, мало спілкуюсь українською, а в Newsboat взагалі використовую англійську, тому локалізація може бути не дуже вдалою.

Ah, got it. I'm afraid that your approach will still have false positives even when Newsboat starts taking case into account; for example, your regex would highlight "RSS" and "USA", which aren't your labels.

That is true, but can be corrected through ad hoc names for feeds; still, a proper delimiter would be a better solution.

The only real solution for that is #412 (so Newsboat "knows" which lines are delimiters and which ones are text, and can highlight them differently), but in the meantime, you can leverage your thick dash to disambiguate between them: highlight all "^[A-Z]+ ─+$" red.

I've tried but apparently it doesn't support that character at all :/
How rich is the set of characters supported by the regex interpeter?

Радий зустріти співвітчизника ^_^ Якщо користуєшся українською локалізацією і побачиш помилку — пиши, а краще надсилай патч (усе в файлі po/uk.po). Я, чесно кажучи, мало спілкуюсь українською, а в Newsboat взагалі використовую англійську, тому локалізація може бути не дуже вдалою.

Я так само користуюсь англійською. Постараюсь на днях попробувати і українську, якщо замічу недостатки однозначно поправлю!

Ah, my bad: it should be highlight all "[A-Z]+ ─+$" red, without ^ at the beginning of the regex. The regex matches the whole line, and since the line in a feedlist starts with spaces and then some digits ^[A-Z]+ never matches. I verified that this updated line works with the urls file you linked earlier.
The regex is processed by regcomp() and regexec(), so I'd expect them to support everything provided that:

your locale matches the encoding of your urls file; and
the characters you use do not contain zero byte in your locale's encoding.

Ah, my bad: it should be highlight all "[A-Z]+ ─+$" red, without ^ at the beginning of the regex. The regex matches the whole line, and since the line in a feedlist starts with spaces and then some digits ^[A-Z]+ never matches. I verified that this updated line works with the urls file you linked earlier.

It does indeed work, thanks! Lovely :)


File Transfer Updates + RTD Revision

[ ] I have added the tests to cover my changes.
[x] I have updated the documentation and CHANGELOG accordingly.
[x] I have read the CONTRIBUTING document.

Quick comment https://covalent--998.org.readthedocs.build/en/998/how_to/orchestration/file_transfers_for_workflows.html seems to not render properly.

@santoshkumarradha addressed comments, section should be rendering correctly now


Support for COG

I wonder if it is possible or planned to have built-in support for Geotiff to COG conversion?
Reference:
COG – Cloud Optimized GeoTIFF generator - https://gdal.org/drivers/raster/cog.html

Would recommend using the new node-gdal-async library which is more actively maintained.

Thank you.


Does it work on black-forest-labs/FLUX.1-schnell?

Hi, thank you for your work!
I wanted to use your method on the faster Flux model.
But when I run your method on black-forest-labs/FLUX.1-schnell, instead of dev, I get this result:

Is your method only for flux-dev version?

@JunbongJang  RAG is compatible with Flux-Schnell as it doesn't alter the model's structure. However, all our experiments were conducted on Flux-Dev, so you might need to adjust some parameters for optimal results. Here’s an example of the results I achieved using Flux-Schnell.

prompt = "a balloon on the bottom of a dog"
HB_replace = 1
HB_prompt_list =  [
        "Balloon",
        "Dog"
    ]
HB_m_offset_list =  [
        0.1,
        0.1
    ]
HB_n_offset_list =  [
        0.55,
        0.05
    ]
HB_m_scale_list =  [
        0.8,
        0.8
    ]
HB_n_scale_list = [
        0.4,
        0.45
    ]
SR_delta = 0.5
SR_hw_split_ratio = "0.5; 0.5"
SR_prompt = "A playful dog, perhaps a golden retriever, with its ears perked up, sitting on the balloon, giving an enthusiastic demeanor. BREAK A colorful balloon floating gently, its string dangling gracefully, just beneath the dog."
height, width = 1024, 1024
seed = 7


support cordova android version 7 mode="merge"

app/src/main/AndroidManifest.xml mode="merge" . instead of AndroidManifest.xml
3 repkacements

will this still work in versions < 7?

yes this will break on cordova android pre 7. However it is required as via https://cordova.apache.org/announcements/2017/12/04/cordova-android-7.0.0.html


Prepare for Python3

Plenty of progress towards Python2/Python3 compatibility.
This code still works with Python2, but has been made compatible
with Python3.
Some of our dependencies have to be migrated before we can announce
Python3 support, and there are other problems to solve.
50% of the work was done automatically by
python-modernize/python-modernize .
The most important change was adding absolute_import

To clarify - This is not Python3 support yet, but a step in the right direction

I'm interested in seeing this ported to Python 3.5+.  Anything I can help with?

That's cool @AndreLouisCaron
Steps that need to happen before elastalert supports Python3

[ ] Some core maintainer should tell us this will work will be merged. No point wasting our time on this PR if core is not interested. This affects a lot of files, so rebasing will be a problem the longer we wait. Also, this can be incremental, no need for full Python3 support on the first merge. @Qmando
[ ] exotel-py should merge this very simple PR: sarathsp06/exotel-py#5
[ ] More Python3 conversions need to happen. See my workflow below

repackage exotel-py with the Python3 branch.
Run tox.
See error messages, solve some of them
Reiterate.

You are welcome to solve some Python3.6 errors if you want. Start from this branch, push to your fork and let me know. I will add your commits to this PR.
Generally I strive to support both Python2.7 and Python3.6 a.t.m

OK, so I got the Python 3.5+ support merged into exotel-py.  Waiting for a release on PyPI :-)

I'm willing to merge in support for Python3 as long as it doesn't break for Python 2.

@Qmando It's not that hard to support both, we can manage that :-)
Apart from getting the test suite to pass, is there anything else you want us to do to "demonstrate" that Python 2 support is not negatively affected?

Closing in favour of #1210


setLtsPointer() referenced in documentation but function doesn't exist in library

Hi there
I'm trying to run a serial debug task on one core of a pi pico while running moderately time-critical code the other core (I have a separate scheduler running on each core). I thought maybe I could fix a race condition bug by starting a task using a pointer to a char array as shown in implementation idea 7, however the compiler throws a "class has no member" error when I try call this function.
Is this function deprecated, if so should this example be removed from the wiki?
(Also, I'm considering using a circular buffer to load the debug messages into as one core runs through its pass, then emptying it to dump them all to serial at once on the other core, unless anyone has a better idea?)
Thanks!

Oops, just re-read the documentation and this is a compile time option!


Add scale to Leaflet map

What's the problem this feature will solve?
This feature will add a scale, which is a common element of a map.
Describe the solution you'd like
Use Leaflet's builtin scale control, or similar third-party Leaflet plugins. Scale options can be added into mesa_geo.visualization.modules.MapModule.
Additional context

Scale control in Leaflet.js
A better scalebar for leaflet maps

Closed via #123.


Fix #alignemnt-definitions typo, but preserve old link semantics

Right thing to do?

Unfortunately name is a deprecated property.
Fortunately there are alternatives; I'd suggest you wrap the text inside the H3 element in a span with the old id attribute applied.
Sorry about the state of the web, and thanks for caring enough to keep links healthy!


Enable python3 builds

(tested with a 3.6 anaconda build. Old behavior: found mismatching pythoninterp and pythonlib settings. New behavior: they match.)

This is great. In onnx-caffe2 Python3 builds I had to detect the python include directory and libpython path and pass them to cmake.
https://github.com/onnx/onnx-caffe2/blob/master/.travis/build.sh#L38

Yeah, also a shout-out to @ilkarman for noticing the python3 build being tricky in his deep learning framework example repo.

Shoot, travis-ci seems to have an interesting failure, reverting for now.


[ALLUXIO-2886] Rename Rename file ClusterInitializationTest.java to ClusterInitializationIntegrationTest.java

https://alluxio.atlassian.net/browse/ALLUXIO-2886

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15742/
Test PASSed.


feat(imagecard): add expand button

Summary

ImageCard should be expandable

Related Issues

Closes IBM/carbon-addons-iot-react#399

Acceptance Test (how to verify the PR)

Render an image card inside a dashboard and click on expand button

:tada: This PR is included in version 1.75.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-beta.9 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.75.0 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


OIDC4VCI with wallet level strict + draft 13, did:jwk vc_jwt_json

OIDC4VCI Test 5
the status of teh card is red but it should be green after verification of teh signature

https://github.com/Bdaya-Dev/jose/issues/4


Customer page size

What problem does this feature solve?
Currently there is some size opptions for the user, for example A3, A4,A5, but some user maybe need the costomed size, for example 100mm*150mm
What does the proposed API look like?
no

use width and height in options

https://hufe.club/canvas-editor-docs/guide/option.html


🧑💻: Add dynamic price fetching in Bitcoin Rainbow chart

Title
Add dynamic price fetching in Bitcoin Rainbow chart
Enhancement Aim
To replace static values
Changes
Use public API like CoinGecko,
Screenshots 📷

Current logic of static data rendering.

// Define the datasets for the chart
  const datasets = [
    {
      label: "Bitcoin Price",
      data: [200, 500, 2000, 8000, 10000, 20000, 30000, 40000, 60000],
      borderColor: "#ffa500",
      backgroundColor: "rgba(255,165,0,0.4)",
      fill: false,
      tension: 0.1,
    },
    ...rainbowBands.map((band, index) => ({
      label: band.label,
      data: Array(labels.length).fill(500 * (index + 1)), // Simulate data for each band level
      borderColor: band.color,
      backgroundColor: band.color,
      fill: true,
    })),
  ];

Guidelines

[X] I have read the guidelines
[X] I have the link to my latest merged PR

Full Name
Mehul P
Participant Role
GSSOC-Ext

@vanshchauhan21 : please assign it to me


⚠ Bofrost.de has degraded performance

In 32af016, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1050 ms

Resolved: Bofrost.de performance has improved in 508645d after 44 minutes.


use intl for months translations

Type of change
Please select PR type by entering x between [ ].

[ ] Bugfix
[X] Feature
[ ] Refactoring
[ ] Documentation content changes

Description
With this PR this package would introduce a dependency to the intl package. but then it has directly support for a LOT of languages, including the wish for turkish language: #26

Thank you so much for your contribution!


Changed return links to hyperlinks

Closes #1071

coverage: 84.262%. remained the same
when pulling f16d4d732b01803519301bbff601797bac54a9db on 1071-Return_to_dashboard_links
into bcc2f535aa8ed26dc5cae9ecfffe3d39df4bb7ab on main.


Try/From traits for Geometry

This is a couple separate but related things...
The main new functionality is that you can call Geometry::from(wkt)
Along the way, I replaced the Try/Into impls with Try/From. We should prefer TryFrom where possible since it is sometimes nicer to use and also gives you the TryInto impl for free.
Correspondingly, I deprecated methods like try_into_geometry in favor of geometry.try_into which I think is more discoverable.
One thing I was curious about - I think conventionally conversions are done via move, so the caller is responsible for any cloning, but previously all our conversions were done via references and our impls were creating new points for everything. That seemed a little strange to me, so I implemented all the new ones with the move semantics that I'm used to. I did leave the existing functionality (but rephrased them as From) so as not to break the API.
A couple potentially controversial things I'll call out inline...

bors r=frewsxcv

😭

approved! try again?

bors retry

bors r=frewsxcv

approved! try again?

Thanks @frewsxcv !


UX: Setting the bootstrap minion should also set the admin role and the cephadm role

When setting the bootstrap minion, this minion should automatically added to the roles/admin and rolescephadm` list.
Otherwise you have to do theses steps manually.
/ceph_cluster/roles/bootstrap> ls
o- bootstrap ........................................................................................................... [no minion]
/ceph_cluster/roles/bootstrap> set node1.ses7-manual.com
Value set.
/ceph_cluster/roles/bootstrap> exit
master:~ # ceph-salt apply
Bootstrap minion must be 'Admin'

When then adding the same node to the admin role and trying to apply again, I get:
master:~ # ceph-salt apply
Minion 'node1.ses7-manual.com' has 'admin' role but not 'cephadm' role

So next manual step is:
/ceph_cluster/roles/cephadm> add node1.ses7-manual.com
Adding node1.ses7-manual.com...
1 minion added.
/ceph_cluster/roles/cephadm> exit

Or we should consider removing this requirement, and don't force the bootstrap minion to be admin.

FWIW I'd be in favor to decouple this as well. In my case, I would like to have on central node to SSH into if necessary, which also acts as the Salt Master node. While the bootstrap minion acts as the "initial seed node", it may not necessarily be the node used for regular admin work.

Is this related to #252 by any chance?


Update contact-pstn-service-desk.md

Latest support information from the PSTN Service Desk Teams from<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>

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

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

Hey @JohanFreelancer9 just commited your reviews, I believe it should be good to go

@tonysmit
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!