Looking for additional maintainers

Hello, I'm looking for additional maintainers that would help me with triaging bugs, keeping this port sync with the other official language ports etc. I'm happy to assist with PR reviews. Just thinking if there is maybe someone who is interested in it.
https://github.com/playwright-community/playwright-go/issues/238 night be a good issue, but also a big one.

Hi, mxschmitt!
I'm a big fan of this project and want to help you enhance playwright-go.
I'm now implementing #238 , so I will create a PR for the issue in a few days.

thats amazing! Looking forward to it and happy to hear! 💯

HI @mxschmitt . I have explored project. Great work. I am very grateful for your initiative. I also want to thank every contributor and maintainer.
I found a few places that need improvement. It relates to  #274 . I prepared a fix to this issue. I would appreciate if I can help with it. Also I guess I can help with tests, examples and docs and more.

@mxschmitt  I would like to be a maintainer of this library. I have started contributing to issues and at the same time trying to understand the lib functionality

@mxschmitt  I would like to be a maintainer of this library. I have started contributing to issues and at the same time trying to understand the lib functionality

Cool! I invited you for having access, to triage issues and pull requests. In a few weeks we can extend the access but I'd like to keep having a review required before merging since it's a great best practice.


Issues with wilcoxon and mannwhitney_u tests

Scipy's implementation of the Wilcoxon signed-rank and Mann-Whitney tests use the normal approximation to calculate the p-value, therefore it's recommended to only use them when n > 20 (see Notes section at: https://docs.scipy.org/doc/scipy/reference/generated/scipy.stats.wilcoxon.html). Perhaps a constraint on minimum value of n could be added for this test? Or a function could be added to Tea to implement calculating the exact p-value when n <= 20.
Tea ignores whether the hypothesis is two-sided or one-sided for these tests. For the test test_integration.test_wilcoxon_signed_rank, which is a paired-samples test with a one-sided hypothesis, it reports the same result (two-sided p-value) regardless of whether you do
tea.hypothesize(['day', 'value'], ['day:sundayBDI > wedsBDI']) or
tea.hypothesize(['day', 'value'], ['day:sundayBDI < wedsBDI']) . It is possible to apply the test to a one-sided hypothesis, but scipy.stats.wilcox does not support this. So Tea should either add a constraint that only applies this test if the user's hypothesis is two-sided, or it should implement a one-sided version of the Wilcoxon signed-rank test.
Tea throws an exception when I try to change this to a two-sided hypothesis by specifying 'day:sundayBDI != wedsBDI' :

>>> tea.hypothesize(['day', 'value'], ['day:sundayBDI != wedsBDI'])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/mnt/d/projects/tea-lang/tea/api.py", line 131, in hypothesize
    relationship = relate(v_objs, prediction)
  File "/mnt/d/projects/tea-lang/tea/build.py", line 321, in relate
    return Relate(vars, predict(vars, prediction))
  File "/mnt/d/projects/tea-lang/tea/build.py", line 299, in predict
    pred = create_prediction(categorical_prediction, vars, p)
  File "/mnt/d/projects/tea-lang/tea/build.py", line 223, in create_prediction
    assert(rhs in var.categories.keys())
AssertionError

scipy.stats.mannwhitney_u can do a one-sided test on two independent samples, but Tea hardcodes alternative='two-sided'. The alternative parameter should instead be set depending on the direction of the user's hypothesis.

Just for comparison, note that R's wilcox.test function can handle one-sample/two paired samples or two independent samples, one-sided or two-sided, and calculates either exact or normal-approximate p-values, defaulting to exact when n < 50.

P-values for Wilcoxon signed-rank test: Added implementation - see wilcox_signed_rank_exact function in evaluateHelperMethods.py
P-values for Mann-Whitney U test: Added implementation - see mann_whitney_exact in evaluateHelperMethods.py
One-sided test for Wilcoxon signed-rank test: It looks like scipy.stats.wilcoxon supports two-sided and one-sided tests. However, Tea was defaulting to using the two-sided test. Tea now sets the appropriate one-sided/two-sided parameter for scipy.stats.wilcoxon.
Hypothesis exception: I can't reproduce your bug, but we did refactor the hypothesis functionality.  I think we may have fixed this bug.
One-sided test for Mann-Whitney U: Tea now picks which one-sided vs. two-sided test to conduct based on the end-user's hypothesis.

Finally, notes on R: Thanks for summarizing! It was helpful to have a few concrete comparison points.  For both, when n < 20, the exact p-value is computed. When n >20, the normal-approximate p-values from Scipy/statsmodels are used.


Isnt at all like darkweb gpt

i tried asking him questions related creating a mallicious python script , it didnt responded saying the same stuff sorry i cant provide you with that info, i cxant assist you with that request and so on, i mean it was so simple even anyone whom i have given a custom made prompt have generated me a python malware that grabs computer's username, external ip address, and google chrome cookies, zip everything and send to a Telegram webhook. but it was unable to do it.
please correct it otherwise its just a same gpt working in a termux and nothing else.

okay, I understand your issue this is because it use chatGPT as AI so sometime it happens try by staring your question by "write a python script" like this it should work  if not than i try to find something

Well , i was doing the same , but on your saying i tried it again , it still didn't happened.

Hello @Hiroshi0Nohara 👋
i am working on it and new version are coming very soon


ninja check-clangd fails with protobuf-related errors on recent trunk

With a recent trunk, while the clangd and ClangdTests targets build successfully for me, building the check-clangd target fails with the following errors:
$ ninja check-clangd
[7/9] Building CXX object tools/clang/tools/extra/clangd/index/remote/monitor/CMakeFiles/clangd-index-server-monitor.dir/Monitor.cpp.o
FAILED: tools/clang/tools/extra/clangd/index/remote/monitor/CMakeFiles/clangd-index-server-monitor.dir/Monitor.cpp.o
CCACHE_CPP2=yes CCACHE_HASHDIR=yes /usr/bin/ccache /usr/bin/clang++-15 -DGOOGLE_PROTOBUF_NO_RTTI=1 -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GLIBCXX_ASSERTIONS -D_GNU_SOURCE -D_LIBCPP_ENABLE_ASSERTIONS -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/home/nr/dev/projects/llvm/build/tools/clang/tools/extra/clangd/index/remote/monitor -I/home/nr/dev/projects/llvm/src/clang-tools-extra/clangd/index/remote/monitor -I/home/nr/dev/projects/llvm/src/clang-tools-extra/clangd/../include-cleaner/include -I/home/nr/dev/projects/llvm/build/tools/clang/tools/extra/clangd/../clang-tidy -I/home/nr/dev/projects/llvm/src/clang/include -I/home/nr/dev/projects/llvm/build/tools/clang/include -I/home/nr/dev/projects/llvm/build/include -I/home/nr/dev/projects/llvm/src/llvm/include -I/home/nr/dev/projects/llvm/src/clang-tools-extra/clangd -I/home/nr/dev/projects/llvm/build/tools/clang/tools/extra/clangd -I/home/nr/dev/projects/llvm/build/tools/clang/tools/extra/clangd/index/remote -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -fno-common -Woverloaded-virtual -Wno-nested-anon-types -O0 -g3  -fno-exceptions -funwind-tables -fno-rtti -std=c++17 -MD -MT tools/clang/tools/extra/clangd/index/remote/monitor/CMakeFiles/clangd-index-server-monitor.dir/Monitor.cpp.o -MF tools/clang/tools/extra/clangd/index/remote/monitor/CMakeFiles/clangd-index-server-monitor.dir/Monitor.cpp.o.d -o tools/clang/tools/extra/clangd/index/remote/monitor/CMakeFiles/clangd-index-server-monitor.dir/Monitor.cpp.o -c /home/nr/dev/projects/llvm/src/clang-tools-extra/clangd/index/remote/monitor/Monitor.cpp
/home/nr/dev/projects/llvm/src/clang-tools-extra/clangd/index/remote/monitor/Monitor.cpp:71:53: error: no member named 'code' in 'google::protobuf::util::Status'
                        static_cast<int>(JsonStatus.code()),
                                         ~~~~~~~~~~ ^
/home/nr/dev/projects/llvm/src/clang-tools-extra/clangd/index/remote/monitor/Monitor.cpp:72:36: error: no member named 'message' in 'google::protobuf::util::Status'
                        JsonStatus.message().as_string());
                        ~~~~~~~~~~ ^
2 errors generated.
ninja: build stopped: subcommand failed

I did a clean build to rule out something being incorrectly cached from a previous build.
Any ideas as to what may be going wrong?

I guess it's caused by https://reviews.llvm.org/D144599.
cc @MatzeB

If building with -DCLANGD_ENABLE_REMOTE=ON requires a certain minimum version of gRPC, shouldn't this be checked at CMake time, and an error issued if the installed gRPC version is too low?

Also, what is the minimum required gRPC version? I upgraded from 1.16 to 1.30, and now I'm getting even more errors... is 1.30 still too old?

Is 1.30 still too old?

I am using official Ubuntu package, it comes with 1.30.2:
$ apt list *gRPC*
...
libgrpc++-dev/kinetic,now 1.30.2-3build6 amd64 [installed]
...

I added --target check-clangd to my build command for a test and it succeeded. But I have to say that I do cmake --build ... instead of invoking ninja directly.

Ok, I filed #1603 for the errors I'm getting trying to build with 1.30.

I'll close this since I can't reproduce #1603 any more (and the original issue was presumably fixed by the upgrade from 1.16 to 1.30).


The dataset connection has failed

Dataset Link https://1drv.ms/u/s ! AiV6XqkxJHE2pme7CIkceyLGsng2? E=6qsnlt is no longer accessible, please restore it.

it is available at  https://1drv.ms/u/s!AiV6XqkxJHE2pme7CIkceyLGsng2?e=6qsnlt


Transactions api split

So that it's clearer and different people can work on different files at the same time

@SteveMarshall @ibrechin what do you think?
This would allow @ibrechin and I to work on different parts at the same time.
It is also cleaner I guess

Looks much cleaner to me! @ibrechin?

I like.


docs: Add an introduction to actors

This new document introduces the actor programming model and how to use it in Frequenz SDK.

Based on #667, ignore the first 4 commits.

Did you review all the commits or only what wasn't in #667? If you reviewed everything maybe you can approve #667 too :D

Investigating an issue with numbered annotations rendering wrongly...

Seems to be an upstream bug: https://github.com/squidfunk/mkdocs-material/issues/6042

If you have any specific suggestions I can try to add some of that, it is weird, when I'm coding or reading issues I see a lot of things that it would be good to have in docs, but when I sit down to write docs I get a writers block and I don't know what to put in there :laughing:

But I think I will merge this since it is approved so we can keep moving, I can write up any suggestions you make later in a separate PR.


Try Manticore on the codebase

https://github.com/trailofbits/manticore

the command line tool can give us some interesting inputs to EVM programs

I'm having a look at the EVM examples https://github.com/trailofbits/manticore/tree/master/examples/evm

Deferring this till I try out the more quick-to-use linters.

Maybe it can find overflows https://twitter.com/trailofbits/status/944353285305257985?lang=en .

The tool crashed.
(venv) skk% manticore ./TokenNetworkJoined.sol --contract TokenNetwork                                   (git)-[master]  ~/src/raiden-contracts
2019-05-02 15:49:21,592: [26743] m.c.manticore:INFO: Verbosity set to 1.
2019-05-02 15:49:21,615: [26743] m.main:INFO: Registered plugins: DetectEnvInstruction, DetectReentrancySimple, DetectUninitializedMemory, DetectDelegatecall, DetectUninitializedStorage, DetectReentrancyAdvanced, DetectSuicidal, DetectUnusedRetVal, DetectInvalid, DetectIntegerOverflow, DetectExternalCallAndLeak
2019-05-02 15:49:21,615: [26743] m.main:INFO: Beginning analysis
2019-05-02 15:49:21,616: [26743] m.e.manticore:INFO: Starting symbolic create contract
zsh: segmentation fault (core dumped)  manticore ./TokenNetworkJoined.sol --contract TokenNetwork

With a faulthandler I see
(venv) skk% manticore ./TokenNetworkJoined.sol --contract TokenNetwork                                   (git)-[master]  ~/src/raiden-contracts
2019-05-02 15:52:28,937: [26971] m.c.manticore:INFO: Verbosity set to 1.
2019-05-02 15:52:28,960: [26971] m.main:INFO: Registered plugins: DetectDelegatecall, DetectSuicidal, DetectReentrancySimple, DetectExternalCallAndLeak, DetectUninitializedMemory, DetectUninitializedStorage, DetectReentrancyAdvanced, DetectUnusedRetVal, DetectEnvInstruction, DetectInvalid, DetectIntegerOverflow
2019-05-02 15:52:28,960: [26971] m.main:INFO: Beginning analysis
2019-05-02 15:52:28,961: [26971] m.e.manticore:INFO: Starting symbolic create contract
Fatal Python error: Segmentation fault

Current thread 0x00007f6f3c467740 (most recent call first):
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/utils/helpers.py", line 159 in serialize
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/core/workspace.py", line 152 in save_state
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/core/workspace.py", line 401 in save_state
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/core/executor.py", line 261 in enqueue
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/core/manticore.py", line 252 in enqueue
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/core/manticore.py", line 407 in _start_run
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/core/manticore.py", line 432 in run
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/ethereum/manticore.py", line 1153 in run
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/ethereum/manticore.py", line 1026 in _transaction
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/ethereum/manticore.py", line 793 in create_contract
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/ethereum/manticore.py", line 730 in solidity_create_contract
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/ethereum/manticore.py", line 1084 in multi_tx_analysis
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/ethereum/cli.py", line 68 in ethereum_main
  File "/home/yoichi/src/raiden-contracts/venv/lib/python3.6/site-packages/manticore/__main__.py", line 41 in main
  File "/home/yoichi/src/raiden-contracts/venv/bin/manticore", line 13 in <module>
zsh: segmentation fault (core dumped)  manticore ./TokenNetworkJoined.sol --contract TokenNetwork

@pirapira Let us know if you try this again! We spent most of our summer improving the correctness of Manticore on EVM. You may also want to try crytic/slither or https://crytic.io for more immediate results, or crytic/echidna to quickly enhance your testing.

@pirapira can you try:

Run ulimit -s<PHONE_NUMBER>9 before executing the manticore command.
Use the --exclude-all flag to disable the detectors ?


Fix error when removing the entire map

Hello,
When we are unmounting the component map we get this error:
Uncaught TypeError: Cannot read property 'bottomright' of undefined     at NewClass.onRemove (react-leaflet-googlemutant.js:417)     at NewClass.removeLayer (leaflet-src.js:6476)     at NewClass.removeFrom (leaflet-src.js:6357)     at NewClass.remove (leaflet-src.js:6350)     at NewClass.remove (leaflet-src.js:3640)     at Map.componentWillUnmount (Map.js:182)     at ReactCompositeComponent.js:406     at measureLifeCyclePerf (ReactCompositeComponent.js:73)
In this pull request you can find the fix :)

@FlorianBouron thank you very much


Error encoding UTF-8 characters

When adding a String with UTF-8 Symbols (for example in Location), it is shown as above.

I found a way that should resolve this, but without success, although the test file from the document below doesn't seem to work in my versions of Acrobat eighter.
https://www.pdfa.org/understanding-utf-8-in-pdf-2-0/
Can you try to download this test file and check if the document properties are shown correctly for you?
https://github.com/pdf-association/pdf20examples/raw/master/pdf20-utf8-test.pdf

It might actually better to use UTF-16 encoding, I will do some testing with that.

Text is now encoded with UTF-16BE encoding when required, this resolved the issue on my side, please check if your issue has been resolved for you as well.


Allow path to migrations to be str

Codecov Report

Merging #32 (ed8f601) into main (8a84f95) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #32   +/-   ##
=======================================
  Coverage   91.04%   91.04%
=======================================
  Files          42       42
  Lines        1497     1497
=======================================
  Hits         1363     1363
  Misses        134      134

Impacted Files
Coverage Δ

apgorm/database.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


[Formatter] add support for asInterval

Add support for asInterval.
When inputig /DateInterval to RelativeTime, it does exactly what it should(shows time relative to now, altough DateInterval consists of no DateTime information, that is needed for it, but let's keep that
What is needed is asInterval(\DateInterval) that outputs strings something like 23 years or 11 days 4 hours

https://github.com/yiisoft/yii2/blob/master/framework/i18n/Formatter.php#L711

No, it outputs string like 23 years ago or 11 days ago, I'd like to have just interval(right now I just strip that ago part off and works, but that is not long term success plan)

Duplicate of #5146

implemented by #10018


Support environments without pip

Before: use pip installed in the target environment.
After: If pip is available in the current environment, use it, pointing it to the target environment using the --python flag. Otherwise, if Python is not installed in the same environment as flit, fall back to the old behavior.
This change is inspired by rye. It allows to use flit with virtual environments created with --without-pip flag.

Right. I broke tests because they mock pip in the target environment. Well, tell me if you like the change, and I'll take care of actualizing tests.

Thanks, I think this makes sense, if people are going to rely on this new-ish pip feature to make virtualenvs without pip inside. Sorry it's taken me a while to look at it.
There's at least one more call to pip that should be changed in the same way:
https://github.com/pypa/flit/blob/6035005746ac1ee2f7952a9fd89431705ab0a5da/flit/install.py#L372
I think that's all, but please have a look yourself in case I've missed one.
Unfortunately I suspect this will be quite a pain for the tests, because as you spotted, we use the ability to point it to an arbitrary Python to mock out the installation command for the tests. If you get stuck with that, one way out might be to swap around the priority, e.g. doing target_python -m pip --version to check if it's installed in the target environment, and only using the pip --python option if not. :thinking:


Save code cleanup and remove icon from toolbar

Once the notebooks save is implemented from File menu, we need to remove Save icon from tool bar and its corresponding code base.

@rajmusuku fixed this with #4407 and #4347.


[feature]: Implement crown levels to encourage user donations

What does this PR do?

This Pull request adds the feature for a user to be motivated with a crown to encourage donation.

Description of Task to be completed?

The aim is to Define alternatives for increasing donations received through the app.
A user gets a silver or gold crown depending on the amount donated.

How should this be manually tested?

start the app: npm run start:dev
Check for user image while game starts. There should be a silver crown, gold crown or no crown.

Any background context you want to provide?

N/A

What are the relevant pivotal tracker stories?

https://www.pivotaltracker.com/story/show/157801306

Screenshots (if appropriate)

No

Questions:

No

Pull Request Test Coverage Report for Build 253

3 of 20 (15.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.2%) to 52.358%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/controllers/users.js
2
19
10.53%

Totals

Change from base Build 247:
-1.2%

Covered Lines:
641

Relevant Lines:
1062

💛  - Coveralls


Consolidate the retry logic

Update aws_service so that it uses the retry() function in the util
module.  Add the ability to use a RetryExceptionChecker to determine
whether we should retry.  We need this in order to check
EC2ResponseError.error_code.  Change the retry interval to a time period
instead of counting the number of attempts, so that the caller doesn't
have to do math to determine the timeout.
Remove the retry_boto decorator and replace it with a retry_boto()
function.  This gives us the flexibility of retrying either in
AWSService or in the higher-level application code.  Add unit tests for
util.retry().

lgtm


Avoid using invlalid null_mask for zero null_count

Fixes #1363

adds a unit test reproducing the issue
adds a null_count check

Signed-off-by: Gera Shegalov<EMAIL_ADDRESS>

The changes look good for the most part. Not thrilled about having changes to CUDF in with this too. It can mess with the auto-update if we are not careful. Are they needed?

Just noticed it too, cudf changes were Included accidentally. Fixed

build


Create skhu.txt

Add SKHU

@vegemil Could you please provide us with a link to a page on the official website which confirms that students at the university have emails in skhu.kr domain? Official website address is www.skhu.ac.kr, it is in another domain, this is why I am asking. Thank you!

I don't know why my university is .kr.
But I really have offical school email is<EMAIL_ADDRESS>

@vegemil Thank you! Pull request merged.


feat: add crate keyword

In the Packages and Crates section, current examples use the crate's name to traverse the module tree.

Rework the examples to use the crate keyword
Rework the explanation to introduce that keyword

References:

Existing page
https://doc.rust-lang.org/book/ch07-01-packages-and-crates.html

@enitrat  can i be assigned this task

@enitrat Can i work on this task?

@NueloSE how are things going?

make a PR before end of today

Yes the entire section 7 so from 7.1 to 7.5


Fix use of delvewheel with a namespace package

See https://github.com/dwavesystems/dwave-preprocessing/pull/131, https://github.com/adang1345/delvewheel/issues/38.
Should fix the errors in https://github.com/dwavesystems/dwave-system/pull/518 once it's deployed.

I manually confirmed that the patch is applied to the correct __init__.py. It's kind of hard to test in CI.


update fastapi follow upstream

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

hi @Sclare87 @xhiroga please review since version v4.42.0 without pining fastapi will crash

close for 4.44 fix fastapi issue


Disable Tabs (since opening multiple tabs/windows can cause download conflicts)

In the View menu of Mist, you can Show Tab Bar and add another Mist window tab (which can even be dragged out to be another Mist window). This allows you to start multiple downloads simultaneously, but the underlying code doesn't account for this and the multiple downloads conflict with each other and the first one will end up failing and then both progress displays actually show progress for just the download that was started last.
I could show more detail here with screenshots if needed, but it's pretty easy to replicate and pretty easy to avoid the issue by just disabling tabs from being able to be opened so that there is only ever a single Mist tab/window and only one download can be done at a time.

Nice pickup @PicoMitchell!
And boom, one-line fix: 8f47603af3bce79fb6bbb1cfb253d36a74394d6b


Add VIEW support

hi @goccy,
thanks for the initiative in creating this project. Do you see any problems in adding VIEW support to the emulator? We can contribute with a PR proposal.
Thanks

hi @goccy, i've sent a proposal to https://github.com/goccy/go-zetasqlite/pull/85

update go-zetasql version sent to https://github.com/goccy/bigquery-emulator/pull/140

view statement support sent to https://github.com/goccy/bigquery-emulator/pull/141

It will be very helpful for me also!

I've released this support with v0.2.13 . Please confirm it !

Looks good @goccy ! Thanks


Sorting between two dragging targets doesn't work

I am working on a designer with a set of questions in the left field, and an open editor to move these questions into on the right. To give an idea, it currently looks like this.

Now if I can sort the two questions in the right field just fine. If i drag a question from the left field to the right however, it will automatically drop the question if i mouse over an already existing question in the field. What i want is to be able to drag a question from the left field over the questions in the right field, and drop it whenever i let go off my mouse.
Currently i run into the problem described above. I can also remove the sortingScope on the left field, in which case the question always drops on the bottom of the right field when dragged, which is also not what i want. I have seen a couple of similar issues, but i couldn't quite make out if someone ran into thisone yet, so apologies if this is a duplicate.
If anyone has a workaround available i would appreciate that too!

Unfortunately it's a known issue at this time, there is no workaround for it. I just need to make some changes to the addon to allow dropping outside of a existing item.

Alright. Thank you for your reply.

Any recommendations how to solve the dragging between targets? I'm trying to use jquery-ui sortable but always getting this error: ember.debug.js:26513 Error: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

Separate issue. Would be better if you opened another issue. This library isn't meant to be used with jquery-ui-sortable. It has it's own sort capabilities.  I haven't seen that particular error before. Can't really help you without a reproduction.


Disable Customers Endpoint

Commented out 'customers' endpoint. Should be easily reenabled by uncommenting pretty much everything in the Controller/Feed/Customers.php file. Also removed a line in the readme that referenced a file that was removed.

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1203428828765684

@Ipswich
It looks like at some point our version number reset. We were at 1.1.4 before:
https://github.com/searchspring/magento2-searchspring-feed/commit/ca3c04b8cbd74a5226bd43b099328e8e8bcfbd60
Then it got removed:
https://github.com/searchspring/magento2-searchspring-feed/commit/f831176a55e1234eba8ed2f7346ad36232b4204c
Then added back in as 1.0.0:
https://github.com/searchspring/magento2-searchspring-feed/commit/d7e1dfa2ec258677fd6dfaad0f05ea34e859bcd1
Can we reset this and make this 1.2.0?
Also, I was thinking the easiest way to make this change would just be to make return $resultJson->setData($data); instead be return $resultJson->setData(array());. This would just make it so this doesn't return any data.

👍


Autocomplete: Add NoItemsTemplate render fragment

Description

This PR adds a NoItemsTemplate that is shown when no items are returned from the Search function. Example:
<MudAutocomplete T="Element" Label="Periodic Table Element" @bind-Value="value2"
    SearchFunc="@SearchEmpty" ToStringFunc="@(e=> e==null?null : $"{e.Name} ({e.Sign})")">
   <NoItemsTemplate>
        <MudText Align="Align.Center" Class="px-4 py-1">
           No items found
        </MudText>
    </NoItemsTemplate>
</MudAutocomplete>

I have also added a docs section for both the NoItemsTemplate and the MoreItemsTemplate (#4566) render fragments.
This PR additionally closes #4668.
How Has This Been Tested?

Unit
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

@henon Could you peek at this? I have also added the requested docs for the #4566 change.

Right, this is the logical extension of the other PR and makes Autocomplete even more user friendly. Thanks!

I considered that, but I don't necessarily think it should be considered a bug. Closing the dropdown on click indicates an item has been selected, which is different than clicking a purely informational "item."
I'd like to here what henon thinks, though.

I agree with Mr-Technician, I don't think it should be selectable by default. There are some nice use cases like it is right now, like adding "Buttons" such as :
" No items found Clear Filters"
or "Load more" button, etc..
Having the whole MudListItem overlay would make these weird in my opinion.

@mckaragoz since it is a render fragment a user can implement closing the autocomplete on click if they want to.

@mckaragoz since it is a render fragment a user can implement closing the autocomplete on click if they want to.

First argument, the dropdown is unified? Doesnt this behavior should be the same with the other dropdown content? I think if dropdown close when we click on items, it should also close when we click anywhere (no/more item context etc) on the dropdown. Different  default behaviors may confuse.
The second argument, i didnt see a simple parameter (like CloseOnInteract) to control dropdown open/close state. Giving OnClick method and using autocomplete ref sounds a bit complex for an easy implemen. User should use this only they want to move away from defaults.
The third and last argument, there is no reason to keep it open :slight_smile:

I partially agree on third one :) it may be true for more item template, but when i first see "no item template" i automatically clicked directly on the template i think "ok, there is no item, i understand and clicked, so you should close"
And for more item template, as you said its not interactive, it doesnt show the next 10 item etc. when you click.
When dropdown is open, it will be surely close when you click everywhere (inside or outside the component). But except these templates :)
Maybe i cant tell completely, but i feel something different on it.


Issue with version when creating a new program

Whenever I try to create a new program using the mbed-cli command, mbed new 'new-proj'. The mbed-os version of the code that gets pulled is an old one i.e v5.15.4. Even when I try to update the master using mbed update master command it still doesn't update the mbed-os to latest version i.e 6.4.
Mbed-cli version = 1.10.4
Python version = 3.7.9
git version =2.29.2

What do the .lib files state? If the .lib files do not have an exact hash, well - the results are rather unpredictable.

The mbed-os.lib file has this link- https://github.com/ARMmbed/mbed-os/#e4b81f67f939a0c0b11c147ce74aa367271e1279
Also noticed that the tag latest is on v5.15.4

Are you using mbed cache? That has had some issues.

Yeah so that was the issue, I just disabled the cache using mbed cache off cmd before importing a new program and now it cloned the latest version 6.4.0. Before closing this issue, do I need to do this every time or this cache setting a universal thing.

The setting stays, if you turn it off (especially if you used the -G then it should be globally) if stays off.

Thank you. Closing this now.

It's probably still a bug, though. :-)

Also, on the tag - any notion of using a tag to identify latest is just blatant misuse of git tags - detailed out here in the official git documentation. There should have never been a tag called latest. There could have been a branch called latest, but not a tag. Tags are write once, they cannot and should not be updated/moving.


Strange non internal handles

There are ~11 handles like below

What are they? Will they remain working (to the degree they work now) after migration?

All those seem to be handles of collections/communities so I'm guessing this dates back to when we had a collection/community per LINDAT partner. Anyways these exist in the v5 database so the import is correct...
@vidiecan any idea why we've put the ?err=not_an_item param to some of the current col/com url (for example try resolving https://hdl.handle.net/11858/00-097C-0000-0001-486F-D)


[Snyk] Security upgrade django from 1.11 to 2.2.18

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements.txt

⚠ Warning
django-rq 0.9.1 requires django, which is not installed.

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

441/1000  Why? Recently disclosed, Has a fix available, CVSS 3.1
Directory Traversal SNYK-PYTHON-DJANGO-1066259
django:  1.11 -> 2.2.18
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Coverage remained the same at 91.688% when pulling 274d5827416e6be17e621ef5ad55f4865aa19c23 on snyk-fix-9626ac109b3b1ae8da9a2094bf562c8e into 3503a1517d86ed272129028223b98cccbbcf1dde on master.


objid_t: Exploit compile-time declared size bounds

Original issue: https://charm.cs.illinois.edu/redmine/issues/172

-- charmxi declaration syntax
-- code generation for conversion functions
-- change generated code to directly call conversion functions when given a CkArrayIndex (rather than runtime querying of idx -- id from locmgr)
-- change generated chare array constructor to specify conversion function

Original date: 2013-10-07 19:05:51

This won't be ready for 6.6, so push it back.


[discussion] - Ways to ensure content quality

Is your feature request related to a problem? Please describe.
The system is very open at the moment, before general release we will likely want to put in place some sort of system to help ensure inappropriate content can be quickly removed or put aside, and potentially include ways to promote content which is viewed as more useful by the community.
Describe the solution you'd like
Perhaps a simple system to flag inappropriate content for review, and either a rating or up/down vote system to help promote content. Possibilities include reddit-style voting, facebook-style likes, or ebay-style rating based on one or more characteristics.
Describe alternatives you've considered
Manual curation and moderation, however this would likely become tedious and could go against some of the more open philosophy of the platform. I would be interested to know other people's thoughts on the roles of moderators vs automation...

is this about a forum or articles ? either way; I wrote Adrian a few thoughts and in the last 30 years i haven't seen better than Stackoverflow. Simplest and more fitted model I see at the moment is :

turn conversations in to content : more difficult and needs community help;
turn content into conversations : easy and would to funnel new findings, ideas, etc.. into the right place; that assumes a good search system (as on SO) which suggests users already existing questions. to, publiclab.org (different discussions on articles) is doing this quite right and evtl. you have a look at it because it seems a quite few years ahead of one-army. we pre-release a new module in  Sept. called 'PP Search' which searches the forum and other sources; I can leave you a react compatible search box with an auto-suggestion implementation of your choice.

other than that; forum software typically provides split, flag, merge - actions for posts. in the case of PP I'd possibly also add 'private' (sensitive) and 'meta' (collab work) at some point.

publiclab.org also has 'templates' for posts/articles btw. that also helps a lot to ensure some policies for content.

Thanks for all the advice @catx23 !
In the first case we are talking more about articles, such as the 'how-to' guides that people can create. These are built on top of our own custom system, so whilst less susceptible to the likes of robo spam, we need to develop our own custom means of moderation for contributors. Currently anyone can write a how-to and it appears immediately at the top for the world to see - clearly this isn't a very good way to go about things. A few options could include:

Force all content to be approved but some sort of admin before going live
Allow users to quickly flag content that might not be suitable for whatever reason for review
Allow users to promote/demote content via some sort of voting/rating system
Restrict who can post content to only those that have passed some sort of approval system

I personally do like the models on stackoverflow and reddit, and would be most keen on something where less gatekeeping is required, and responsibility is shared more widely. Whether this would work in reality, is anyone's guess.
I like the templates and guidelines suggested, we have that currently and I hope will continue to do so for all new parts of the platform. We don't have a good option at the moment for turning content into conversations, but hopefully use of a 3rd party forum will help to achieve that, and as you said come with its own set of tools.

Ok,
in the short term you could :

place a guide or an example article (links to supplies write a sort of best practice article, similar to the IOS UX guide lines; basically a collection of dos and don'ts; Since you're on react / material-ui; there is a repo of Microsoft (https://developer.microsoft.com/en-us/fabric/#/controls/web/breadcrumb)
for the moderating/promoting/demoting/approval part : you could create a simple panel with 'new how-to', 'changes', etc.. and leave the order of articles sorted : ie : by upvotes and/or activities/views first. For multi-dimensional sorting; the filter code I gave you for the discussion list is generic. Possibly I have to add some notes on how to use it.

Discussion moved to slack/other general discussions. closing here


$sg-collapse has not !default

$sg-collapse variable has not !default value, so you can't override it.
Just use $sg-collapse: false !default; instead.
:)

Yeah, I've totally forgot that...
I've already merged the pull request.
Thanks

Update also bower and npm ;)
Thank you!


Register package

@JuliaRegistrator register

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

Updated dependencies.
@JuliaRegistrator register

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

Also, note the warning: This looks like a new registration that registers version 0.2.0.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register()

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


File contents "scrambled" after copy/paste operations

While working on either PHP or HTML files in Codiad (possibly other file types, too - I just haven't been working on other types), If I paste any content (plain text, code, etc.) into the file I'm working on there's a fairly high likelihood that either the content I just pasted or the content surrounding it will become "scrambled". An example is illustrated, below:
Let's say I have the following code already in place:
    error_log("There is a file type missing. overlayImageFilename = $overlayImageFilename, fileIndex = $fileIndex\n", 3, "my.error.log");

and I want to paste the following into the next line down:
  	header('Location:myFile.php'); // redirect to re-run the script

What sometimes ends up happening (about 30-40% of the time) looks something like this:
    error_log("There is a file type missing. overlayImageFilename = $overlayImageFilename, fileIndex = $fileIndex\n", 3, "emr.yor.log");
  	heeadr('Laotcnio:myFile.php'); // redirect to re-run the script

If I'm not paying attention, this can result in a significant amount of debugging time, trying to locate the bugs the text scrambling generates, and even if I'm looking out for this problem, it still represents a great deal of "wasted time" to go back and re-write what was scrambled.
I'm using Codiad in the most recent version of Chrome, with no extensions enabled. If further information is necessary, I'll be happy to supply what I can.

Codiad has updated its internal editor which should resolve this issue. Please check it and state your result at #516


Add option to collapse parallel test runs

As of Xcode 16, test runs that are parallelized result in a separate message for each test case. This adds a new flag called collapse_parallelized_tests (defaults to true), which collapses the messages into one per target.

Nice @evandcoleman, thanks for working on this!
Do you mind to also do some tests?


[UI] Missing Gitlab icon after app deployment

Issue
Gitlab icon seems missing after latest version v1.9.0-0.0.1-next andEpinio Server Version: v1.9.0-rc3

Verified on Epinio Server Version: v1.9.0-rc3-1-g4ef26278 with ui image ghcr.io/epinio/epinio-ui:latest-next

Rechecked in Epinio v1.9.0-rc4 with epinio-ui image v1.9.0-0.0.2


Case statement auto complete

It would be nice to auto complete case statements depending on there type like the atom package does.
Some examples:
type alias Model = { Maybe Foo }

someFunc : Model -> ..
someFunc model =
    case model.foo of -- At this point it would be nice if the package could auto complete Just and Nothing

Or a slightly more complex example
type Foo = Bar | Baz | Hi Bye
type alias Model = { Foo }

someFunc : Foo-> ..
someFunc foo =
    case foo of -- At this point it would be nice if the package could auto complete Bar, Baz and Hi bye

Is this something on the roadmap?
Thanks

Was just talking about this to a co-worker, he's new to Elm and was wanting this for emacs, like Lisp has. Would be nice, but probably not as impactful as, say, https://github.com/Krzysztof-Cieslak/vscode-elm/issues/188


Port to node v0.6

It would be great, if you could port the lib to node 0.6.

I will take a stab at this this week.
Is there anything specific that you see failing in 0.6?

Weird, it was an off by one bug that should have shown up in any version of node. shrug Tested against 0.4.x and 0.6.11.
Fixed in v0.2.0, which you can pull or install with npm.
Cheers.

Thanks, great!


fix(theme-classic): do not add microdata item prop to trailing breadcrumb

Motivation
Fix #7135
cc @kotryna-k
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Tested on Rich Results.

Last item no longer has id.

@Josh-Cena thank you very much for solving this. This is causing massive warnings in my google search console on almost all the pages. need this merged badly in the upcoming release.

@sh0umik Really? I've tested both configs in the rich results console; neither warned me anything. Where should I test this?


Web UI always bind on default port

See log:
$ ./MailHog_linux_amd64 -ui-bind-addr <IP_ADDRESS>:8025
2019/11/04 11:19:36 Using in-memory storage
2019/11/04 11:19:36 [SMTP] Binding to address: <IP_ADDRESS>:1025
[HTTP] Binding to address: <IP_ADDRESS>:8025
2019/11/04 11:19:36 Serving under http://<IP_ADDRESS>:8025/
[HTTP] Binding to address: <IP_ADDRESS>:8025
Creating API v1 with WebPath:
Creating API v2 with WebPath:
[HTTP] Error binding to address <IP_ADDRESS>:8025: listen tcp <IP_ADDRESS>:8025: bind: address already in use

I am having this same issue when trying to bind to port 8025 but what is weird is that my dummy emails still go through to mailhog?

See log:
$ ./MailHog_linux_amd64 -ui-bind-addr <IP_ADDRESS>:8025
2019/11/04 11:19:36 Using in-memory storage
2019/11/04 11:19:36 [SMTP] Binding to address: <IP_ADDRESS>:1025
[HTTP] Binding to address: <IP_ADDRESS>:8025
2019/11/04 11:19:36 Serving under http://<IP_ADDRESS>:8025/
[HTTP] Binding to address: <IP_ADDRESS>:8025
Creating API v1 with WebPath:
Creating API v2 with WebPath:
[HTTP] Error binding to address <IP_ADDRESS>:8025: listen tcp <IP_ADDRESS>:8025: bind: address already in use

You probably already have something (another mailhog ?) running (address already in use)

I am having this same issue when trying to bind to port 8025 but what is weird is that my dummy emails still go through to mailhog?

Not weird at all, you have another Mailhog already running at this port and collecting mail, isn't it ?

@AdrienViala
See this sequence:
$ ./MailHog_linux_amd64 -ui-bind-addr <IP_ADDRESS>:8025
(...)
[HTTP] Binding to address: <IP_ADDRESS>:8025
2019/11/04 11:19:36 Serving under http://<IP_ADDRESS>:8025/
[HTTP] Binding to address: <IP_ADDRESS>:8025

I want bind only on localhost, why <IP_ADDRESS> (default) is in use?

I guess you're missing -api-bind-addr.
Here's my command:
➜  ~ ✗ MailHog -api-bind-addr "<IP_ADDRESS>:1029" -ui-bind-addr "<IP_ADDRESS>:1029" -smtp-bind-addr "<IP_ADDRESS>:1030"
2020/12/24 19:13:25 Using in-memory storage
2020/12/24 19:13:25 [SMTP] Binding to address: <IP_ADDRESS>:1030
[HTTP] Binding to address: <IP_ADDRESS>:1029
2020/12/24 19:13:25 Serving under http://<IP_ADDRESS>:1029/
Creating API v1 with WebPath:
Creating API v2 with WebPath:
[APIv2] GET /api/v2/jim
[APIv2] GET /api/v2/messages
[APIv2] GET /api/v2/websocket
[APIv1] KEEPALIVE /api/v1/events

In Browser


adding coinbase connector

Type of Change

[ ] Bugfix
[x] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates

Description

Additional Changes

[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Checklist

[ ] I formatted the code cargo +nightly fmt --all
[ ] I addressed lints thrown by cargo clippy
[ ] I reviewed submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

Should a connector integration PR specific to coinbase touch so many files across other connectors?
If this is related to supported payment methods error handling, how to minimize the surface area of such a change?

Should a connector integration PR specific to coinbase touch so many files across other connectors?
If this is related to supported payment methods error handling, how to minimize the surface area of such a change?

Should a connector integration PR specific to coinbase touch so many files across other connectors?
If this is related to supported payment methods error handling, how to minimize the surface area of such a change?

Should a connector integration PR specific to coinbase touch so many files across other connectors?
If this is related to supported payment methods error handling, how to minimize the surface area of such a change?

Yes, it is because of adding new payment method(crypto), which was not handled in few other connectors if any new payment method got added. But now I added the default case in other connectors too, so we don't need to change any other connector's files, if we add any new payment method

Can you please provide a reason as to why this PR was closed?

This was a forked branch with my personal account. At the time of raising this PR, I didn't have the write access for juspay/hyperswitch repo. After getting access, me and @jagan-jaya created new branch opennode-v2


[1pt] PR: ESRI CRS's error out

Previously, ras2fim could only accommodate projections in the EPSG format. This PR is a quick fix to how the projection is processed to accommodate projection codes in the ESRI format.
Changes

src/ras2fim.py: Replaced CRS.from_epsg with CRS.from_string in order to accommodate ESRI projections.
src/shared_functions.py: Edited error message for clarity.

Testing

Tested on HUC 12040101, which uses an ESRI projection. The 'unable to find projection' error no longer occurred after the fix.

Checklist
You may update this checklist before and/or after creating the PR. If you're unsure about any of them, please ask, we're here to help! These items are what we are going to look for before merging your code.

[x] Informative and human-readable title, using the format: [_pt] PR: <description>
[x] Links are provided if this PR resolves an issue, or depends on another other PR
[x] If submitting a PR to the dev branch (the default branch), you have a descriptive Feature Branch name using the format: dev-<description-of-change> (e.g.: dev-revise-levee-masking)
[ ] Changes are limited to a single goal (no scope creep)
[x] The feature branch you're submitting as a PR is up to date (merged) with the latest dev branch
[x] Changes adhere to PEP-8 Style Guidelines
[x] Any change in functionality is tested
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged / future todos are captured in comments
[ ] Project documentation has been updated (CHANGELOG and/or README)
[x] Reviewers requested

Updates.. sorry.. Emily. Can you add your Changelog update to this?


Container exit does not clear IP occupation

Description
nerdctl
$ sudo nerdctl network create test-br
61c84410830227bcdb72d9c2bb08aec945d85f5c69d35600bfcb24168464a404

$ sudo nerdctl run --net test-br alpine ip addr
2: eth0@if968: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether 0e:ad:43:ab:24:2d brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::cad:43ff:feab:242d/64 scope link
       valid_lft forever preferred_lft forever

$ sudo nerdctl run --net test-br alpine ip addr
2: eth0@if969: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether 52:5e:96:74:c9:a6 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::505e:96ff:fe74:c9a6/64 scope link
       valid_lft forever preferred_lft forever

docker
$ docker network create test-br
d1d9b84082c5ffff180ea111767412d06d6690d5015602421696075ede7cdf26

$ docker run --net test-br alpine ip addr
963: eth0@if964: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether 02:42:c0:a8:20:02 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/20 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever

$ docker run --net test-br alpine ip addr
965: eth0@if966: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether 02:42:c0:a8:20:02 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/20 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever

Steps to reproduce the issue

Describe the results you received and expected
keep the same as docker
What version of nerdctl are you using?
master
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
No response
Host information
No response

/assign
🙋♂

After thinking a little about this behavior,  I'm not sure if we need  to keep the same as docker
Because in nerdctl the IP is allocated/released by host-local IPAM  by
default and It actually clears the IP occupation, but just round-robin IP address.
I created >256 (actually only need 254?) containers by
docker run --nettest-br alpine ip addr,  we can see that the released  IP is available.
Can also observe from the host-local's dataDir that the existed  container's IP is released,
which is /var/lib/cni/networks/test-br in this case.
https://github.com/containernetworking/plugins/blob/v1.1.1/plugins/ipam/host-local/backend/disk/backend.go#L149
@junnplus

Looks like this issue has to be fixed on the CNI plugin side (if we still want to fix it?)

$ sudo nerdctl network create test-br
61c84410830227bcdb72d9c2bb08aec945d85f5c69d35600bfcb24168464a404
$ sudo nerdctl run --net test-br alpine ip addr
2: eth0@if38: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether ee:38:e6:86:49:90 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::ec38:e6ff:fe86:4990/64 scope link
       valid_lft forever preferred_lft forever
$ sudo nerdctl run --net test-br --ip=<IP_ADDRESS> alpine ip addr
FATA[0000] failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process:
error during container init: error running hook #0: error running hook: exit status 1, stdout: ,
stderr: time="2022-08-03T13:36:01Z" level=fatal msg="failed to call cni.Setup: plugin type=\"bridge\" failed (add): failed to allocate for range 0: requested IP address <IP_ADDRESS> is not available in range set <IP_ADDRESS>-<IP_ADDRESS>"
Failed to write to log, write /var/lib/nerdctl/1935db59/containers/default/f5a6e2556ebbf6af11f06b4d35bd3541fa7d8a6463a59c956649e7c70edcb5ba/oci-hook.createRuntime.log: file already closed: unknown

I haven't confirmed the implementation of host-local, but in fact the IP doesn't seem to be released

It will release after nerdctl rm <cont_id>.
TLDR:
nerdctl run --rm will release after container exit.
# nerdctl run --net test-br --rm alpine ip addr
...
2: eth0@if332: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether b6:9b:55:32:33:16 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::b49b:55ff:fe32:3316/64 scope link
       valid_lft forever preferred_lft forever

root in cni/networks/test-br took 2s
❯ nerdctl run --net test-br --ip=<IP_ADDRESS> alpine ip addr
...
2: eth0@if333: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether 1e:e3:e4:3b:f3:50 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::1ce3:e4ff:fe3b:f350/64 scope link
       valid_lft forever preferred_lft forever

more detailed process:
# sudo nerdctl run --net test-br --name=test alpine ip addr
...
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth0
...

# ls /var/lib/cni/networks/test-br
<IP_ADDRESS>  last_reserved_ip.0  lock

# cat /var/lib/cni/networks/test-br/last_reserved_ip.0
<IP_ADDRESS>

# sudo nerdctl run --net test-br --ip=<IP_ADDRESS> alpine ip addr
FATA[0001] failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: time="2022-08-03T23:51:18+08:00" level=fatal msg="failed to call cni.Setup: plugin type=\"bridge\" failed (add): failed to allocate for range 0: requested IP address <IP_ADDRESS> is not available in range set <IP_ADDRESS>-<IP_ADDRESS>"
Failed to write to log, write /var/lib/nerdctl/1935db59/containers/default/3c6e967945daefb0d6bac9fbad418fa5e00364f071258cd79094853080c0ba84/oci-hook.createRuntime.log: file already closed: unknown

#  sudo nerdctl rm test
test

# nerdctl run --net test-br --ip=<IP_ADDRESS> alpine ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0@if331: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether 46:25:d6:34:12:db brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::4425:d6ff:fe34:12db/64 scope link
       valid_lft forever preferred_lft forever

It will release after nerdctl rm <cont_id>

I know that deleting the container can release the IP, I mean stop a container.

@junnplus did it formerly release IP on container exit? i.e. is this a breaking change in behavior or has it always been like this, to your knowledge?

@junnplus did it formerly release IP on container exit? i.e. is this a breaking change in behavior or has it always been like this, to your knowledge?

@obataku it always been like this

related to #458


[8.x] Ability to specify the broadcaster to use when broadcasting an event

This PR adds an optional attribute on an Event $broadcaster which can be defined per "broadcastable" Event in order to specify which Broadcaster to use when broadcasting the said event.

As it stands, once we have configured the default "connection" to use within config/broadcasting.php we cannot use another one for a specific event.
This is due to the BroadcastServiceProvider always registering a singleton with a default connection set to null within the IoC, which means that whenever a new Event which needs to be broadcast is handled, it will resolve the Broadcaster contract from the IoC, always fetching the default broadcaster configured.
It could be quite handy to be able to have a bit more flexibility if we were to use a different broadcaster per type of event or type of clients our server-side events should broadcast to.
This is supported by:

A trait InteractsWithBroadcaster adding the definition for the optional attribute as well as a method to set the broadcaster on the fly.

In a similar fashion to what we can currently do with queued jobs
class ProcessPodcast implements ShouldQueue
{
    use InteractsWithQueue;

    public function __construct()
    {
        $this->onQueue('processing');
    }
}

we could have the following for basic broadcast events
class OrderShipped implements ShouldBroadcast
{
    use InteractsWithBroadcaster;

    public function __construct()
    {
        $this->withBroadcaster('log');
    }
}

An additional method on the PendingBroadcast class in order to specify on the fly which broadcaster to use.

broadcast(new OrderShipped($order))->withBroadcaster('log');

Instead of fetching the Broadcaster from the IoC upon broadcast event handling, we now resolve the Manager and call connection() there using the optional broadcaster attribute. Note that we fallback to the current behaviour which prevents introducing any breaking change.

Note: Even though the "connection" term is used throughout the config/broadcasting.php file, I've decided to use "broadcaster" to prevent any confusion with the existing $connection property you can have on a queued event.

Interesting - what led you to use multiple broadcasters for your application?

Thanks. From a pure Broadcasting point of view, you could need to broadcast some events using the log broadcaster for auditing purposes while keeping Pusher for others. You could also want to separate concerns and use two different broadcasters for two different client-side JavaScript applications.
What really pushed me looking into this was the fact that we are currently trying to leverage Broadcasting in order to implement some PubSub pattern between applications using SNS and SQS.
We understand Broadcasting is primarily for client-side JavaScript applications but in a PubSub context, when publishing an event to the outside world, it is literally "broadcasting" a server-side event, hence why we think Broadcasting makes totally sense.
We would like to be able to use a different broadcaster for these kind of PubSub events while keeping the ability to use Pusher for our client-side JavaScript application.

Thanks for this. Would you be happy if I start drafting some documentation for it? Or is it something you prefer to do internally?

For anyone upgrading 7 -> 8 and getting broken tests, e.g.
TypeError: Argument 1 passed to Illuminate\Broadcasting\BroadcastEvent::handle() must be an instance of Illuminate\Contracts\Broadcasting\Factory, instance of Mockery_0_OurApp_Broadcast_Broadcasters_GoogleBroadcaster given

Take a look at the way the test were updated in this diff...
https://github.com/laravel/framework/pull/38086/files#diff-feb39f42d76515221e9edfa1b8239c0f88f2561065f165ec69978e0eec1616dd


Set up 110H/100H boys/girls logic

        # TODO: Set up 110H/100H boys/girls logic

https://github.com/mitchellggreenhalgh/mid-distance-webscrapers/blob/255ab570ac5d779805c717691c964c126aa38e1c/scrape_milesplit.py#L297

Finished with match/case statement


[QUESTION] Have huge messages

Hi . I have huge message in second  like 10000  queue how I can use this package for insert db ?

Hi @vahidalvandi can you please describe better your problem? I don't know exactly what you want.
You can insert data into the database normally like in any other part of the application, just need to call your model inside your consumer.

I have microservice crypto currency it build very huge data in second like 1000 or 100000 event in second .
Do laravel kafka handle it in dB insert ?

You can use database features inside Kafka consumers like in any other part of your application. This package will only consume messages from the topics you specify in your consumer configuration, so you can save it to the database or do whatever you want with the event being consumed.

Closing this due to lack of updates.


Harvesting: Move fee selector to pop-up

Description:
Currently, on harvesting view, we have a "Fee" selector. Users confuse very often value selected there with a potential reward for a harvested fee and try to change it to "Fast".

Change proposition:
Because the "Fee" selector applies to the transaction we will send when "Stop harvesting", then maybe we can move the "Fee" selector on the transaction pop-up.

@cryptoBeliever Maybe it just makes sense to add a warning under the fee selector that the fee doesn't affect the Harvesting reward?

@NikolaiB it will probably reduce questions but giving text don't change that UI is bad and very confusing for user.

There's already a warning under that input box :)
How about we change the label Fee to Fee to pay for this transaction. There is plenty of room to the right since the dropdown is oversized given its actual content.
And I agree whatever we do we need to be consistent and do the same in all Fee selection dropdowns.

@segfaultxavi user will don't know which one transaction ("Fee to pay for this transaction"). When the user opens this harvesting view mostly, he doesn't want to send any transaction (it's another case compared to the transfer transaction view), he activated harvesting, and that's all.
This fee applies to transactions that will be sent when the user will click "Stop harvesting".
So correct field name should be like "Fee to pay for the transaction if you click 'stop harvesting' button" :)
That's why I think removing the fee selector from there and moving it to a place when we are sure the user want send a transaction is a good idea. But of course, I'm open to other propositions.

Oh, I see. I agree, yes, the user doesn't know anything about "transactions" when he's trying to enable harvesting.
Moving the selector to a place where it is more clear that you are about to send a transaction looks like the right thing to do, yeah.


chore: remove sentry performance tracker

Description
Fix the following errors
POST https://o296332.ingest.sentry.io/api/1546547/envelope/... 429 (Too Many Requests)
We have an integration with Sentry to instrument page loads and other transactions. This is no longer used. All page load metrics are collected using a new relic integration.
The sentry transactions api was throwing a 429 error when we exceed our trial quota. Removing the integration should curb this error.
Slack thread for more context on our sentry sub exceeding its quota.
TypeError: e.className.split is not a function at t.value (PageLoadInstrumentation.ts:112:33)
Add a type check for string.
Fixes #Issue Number
or
Fixes Issue URL

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation
/ok-to-test<EMAIL_ADDRESS>:mag: Cypress test results

[!WARNING]
Tests have not run on the HEAD 215b753e257570992f38b0a975bf204e0df39ff7 yet
Thu, 15 Aug 2024 07:32:44 UTC

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

/build-deploy-preview skip-tests=true

This PR has some fixes for https://github.com/appsmithorg/appsmith-ee/issues/4748


Task: Remove authn/z, login and token related documentation

What is the task about?
This issue is required as a follow up of
Task: Remove authn/z and token feature from rstuf CLI #406
and
Task: Remove authn/z and token feature from API #460
Remove all documentation about auth/z, login instructions and tokens.
DO NOT remove docs that are references to the CLI and API repos.
Parent feature
Feature: Remove built-in Authn/z from RSTUF #491
References
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

From a conversation with Kairo and Ivana about this issue:

remove all references for of:

auth
token
authorization
login

remove using the volume rstuf-api-data: https://github.com/repository-service-tuf/repository-service-tuf/blob/main/docs/source/guide/deployment/guide/docker.rst
rephrase the WARNING here: https://github.com/repository-service-tuf/repository-service-tuf/blob/main/docs/source/guide/deployment/guide/kubernetes.rst to use custom authorization
remove if using authentication/authorization the login is required note from https://github.com/repository-service-tuf/repository-service-tuf/blob/main/docs/source/guide/deployment/setup.rst
add an API/Gateway doc
remove last sentence from  https://github.com/repository-service-tuf/repository-service-tuf/blob/main/docs/source/guide/deployment/planning/deployment.rst#authenticationauthorization
remove the DATA[optional] warning from https://github.com/repository-service-tuf/repository-service-tuf/blob/main/docs/source/guide/deployment/planning/volumes.rst#data-optional

https://repository-service-tuf.readthedocs.io/en/latest/guide/deployment/planning/volumes.html


Revised durability

This is a first pass at the work described in #198 .
There are two protocols in clara.rules.durability

ISessionSerializer

Responsible for serializing and deserializing the session (and rulebase) structure of the rule sessions

This one will likely rarely, if ever, need to be customized by a consumer.  It has to be tightly coupled to the implementation of a rule session memory, which should generally be advised against

Clara is going to provide a default implementation via Fressian in clara.rules.durability.fressian namespace

This namespace requires a dependency on org.clojure/data.fressian see https://github.com/clojure/data.fressian
This is an "optional" dependency and not included in Clara's explicit dependencies (it's only a :dev dependency for testing).

IWorkingMemorySerializer

Responsible for serializing and deserializing the "consumer-defined" facts that are contained within working memory

This one is expected to be implemented by consumers in a way that makes the most sense for serializing their domain model objects

We could provide some helpful defaults here in the future (I hope to have some additions here soon).

Many of the serialization functions exposed in clara.rules.durability can be useful concepts or helpful to implement the IWorkingMemorySerializer.  The Fressian handlers defined in clara.rules.durability.fressian have been written to be able to serialize/deserialize most Clojure persistent data structures, metadata, and preserve record identity relationships among each other or where they are used in different aggregates.  This is useful to implementations of IWorkingMemorySerializer as well, if Fressian is in consideration.

The approach to serialization is documented quite a bit within the clara.rules.durability and clara.rules.durability.fressian namespaces.
The old functions from this clara.rules.durability namespace have been removed since they were not actively maintained and were out of sync with the evolution of Clara's memory and the engine over time.  The motivations behind this new approach to durability can be found in #198 .
As the clara.rules.durability namespace doc string states, this namespace should be considered experimental still.  The API itself is subject to change and even more importantly, rule sessions or rulebases serialized in one version of Clara are not guaranteed to be able to be deserialized in another version.

I re-pushed these changes since I didn't realize I broke my tests in a last minute change yesterday.  The tests should be passing now.

Looking at this, the current implementation needs to be aware of each type of node and serialize it, and attach additional information to the nodes like the expressions used to create them. This effectively makes all of our node types part of the serialization contract. This might be necessary, but has the downside of making sure we keep the compatible with what previous versions may have serialized with them.
Just for discussion -- either as part of this change or a future one -- should we consider keeping and serializing the beta graph structure defined by this schema, and using a Fressian (or other) serialization of that as our rule base? It keeps the node IDs and all expressions that need to be compiled, which we could cache at deserialization time as well. It seems like it might be simpler to keep and (de-)serialize that rather than plugging into the runtime network.
Perhaps there are some downsides to this, such as performance costs, that make it not worthwhile?

Looking at this, the current implementation needs to be aware of each type of node and serialize it, and attach additional information to the nodes like the expressions used to create them. This effectively makes all of our node types part of the serialization contract. This might be necessary, but has the downside of making sure we keep the compatible with what previous versions may have serialized with them.

Just for discussion -- either as part of this change or a future one -- should we consider keeping and serializing the beta graph structure defined by this schema, and using a Fressian (or other) serialization of that as our rule base? It keeps the node IDs and all expressions that need to be compiled, which we could cache at deserialization time as well. It seems like it might be simpler to keep and (de-)serialize that rather than plugging into the runtime network.

Perhaps there are some downsides to this, such as performance costs, that make it not worthwhile?

I agree with you that I think this is a better approach in the longer term if we are going to get to a place where serialization from one version of Clara can be deserialized in a different version.  The more we can "delay the compilation" process the better off we'd be in that regard as long as the compilation "recipe" (the beta graph here) doesn't need to change in non-passive ways.
This would add added cost to the deserialization of the rulebase however.  I think we'd need to
work on tuning the clara.rules.compiler more if it became a more critical path.  However, in our scenarios at least, we want to only serialize and deserialize the rulebase a single time and then just rapidly deserialize sessions that "attach" to that single rulebase later.  In that sort of workflow, the deserialization of the rulebase execution time isn't as critical.
The main drivers behind these changes (from the perspective of how it is implemented currently and our real-world use-case) are for highly optimized deserialization times, with the serialization time a lesser concern.  Obviously people's use-cases will vary and we should really strive to make all paths as quick as we can.
I think we also are going to run up to issues with maintaining a passivity on serialization of sessions that were based on the (local only right now) memory representations that we may also change from one version of Clara to another.  Again, any sort of added logic we have to do during deserialization time can hurt performance.
Overall, I would like to just take this approach for the rulebase serialization with strong intention of changing it to something like the beta graph as you suggest.  I actually went with this upon first pass because it was least invasive to the clara.rules.compiler and the clara.rules.engine.  The implementation of the ISessionSerializer is not something that we'd expect to have many customized implementations of, since it will necessarily have a decent level of coupling to Clara's internal structures.  So I thought we could evolve it a bit more before starting to claim that rulebase serialization can be passive across versions of Clara.
Let me know of any further concerns you have over this right now though.  The feedback is certainly valuable.

I forgot to add that before I went with the Fressian based ISessionSerializer implementation, I had a mostly working branch that required no foreign dependencies and instead relied on print-method.  I think this was interesting and more easily available to get started with, but in reality the performance characteristics in both time and space were just really bad and there was no real fix for them.  I think print-method + the clojure.lang.LispReader are best kept to just sending "code as data" style data, not huge data structures - especially huge structures with many java.lang.Class style references and constructor calls.
I did keep this stuff in a public gist in case you or anyone else was interested to see it (just for fun or learning).  I will not claim that it 100% works with the latest version of clara.rules.durability though, but it is close.
https://gist.github.com/mrrodriguez/4c2b3a122cec8cb7327dd224198543ec
I do not plan to maintain this right now though, since like I said, it just wasn't performant enough for our practical use.

Fair enough. I don't mind moving forward with an experimental approach and refactoring it as we go.
As for performance, I'd imagine most use cases would involve (de-)serialization of sessions rather than putting rule bases in the critical path. I'm sure we can optimize our current compiler logic, but in the rule base scenario you'd have to go through the compilation/JIT/JVM hotspot optimization every time you deserialized no matter what.

As for performance, I'd imagine most use cases would involve (de-)serialization of sessions rather than putting rule bases in the critical path. I'm sure we can optimize our current compiler logic, but in the rule base scenario you'd have to go through the compilation/JIT/JVM hotspot optimization every time you deserialized no matter what.

I agree that the session deserialization is likely to be the most reasonable case to expect to be put on the critical performance path.
You have good points on the compilation of the rulebase issues.  A lot of the Clara compiler time is really spent in the Clojure compiler, so there is only so far you can go with some of that (not sharing, trying to share compiled forms a bit more perhaps, etc).


[Issue with new version] Not able to create instrumenal version, old version was working fine

Hello,
I did a quick check "Multi-step generation"
Step 1: vocals/instrumentals separation
Vocals is fine and instrumentals include vocals too. I can confirm it was working fine yesterday before the update.
Input song (Copyright free)
https://www.youtube.com/watch?v=7UmBGMktAoI
Vocal and Instrumental
https://drive.google.com/file/d/13kscfz84qn9o4Jkaf0ByyP4x8Bttr-ha/view?usp=sharing

Is the problem that the the instrumentals include traces of the vocals?

@nitinmukesh Also, I would be curious to know your general thoughts on the quality of the audio output in the new version of ultimate-rvc. I was debating alot whether or not to do this upgrade, as some things are indeed worse than before. If the output audio quality is sufficiently bad I might revert to the old version, but that would have to be a very serious issue, as there are many other benefits with the new version of ultimate-rvc

I guess the issue of vocals in instrumental is because earlier MDX models were used and it was working fine. Now only RVC models are used. Please correct me if I am wrong. I would request to make it work like earlier as it is one important feature of having only instrumental version without vocals. I loved that feature.
Audio quality, even though I have not done much comparison but it was slightly better earlier. I checked with the same song earlier and with new version. Can't say it is noticeable.

@nitinmukesh You are wrong about only RVC being used now. MDXNet models are still being used. their default settings are just a bit different. The problem with vocal residue in extracted instrumentals was also present before the update. It may be that the problem is bigger now. Did you test with many different songs? As i mentioned before, the new models with their current settings seems to improve quality of vocals but not instrumentals. In general, it seems difficult to strike a perfect balance, as you are always compromising on quality somewhere.
I really appreciate all your testing. If you continue to experience problems with instrumentals, please let me know.

No problem. I am ready to test any new features.
I still don't find any MDXNet models in new version

the mdxnet models are stored in models/audio_separator/ :blush:

the mdxnet models are stored in models/audio_separator/ They will be downloaded on the fly as needed 😊

Got it, thanks.
Sorry for asking so many questions and I hope this is the last one. Is there any way to get instrumental version like before i.e. without vocals.

No worries, your questions are appreciated.
Currently you can't do anything to get better instrumentals stems. But, if the quality of the instrumentals stems you generate in general is not good enough (bleed through of vocals) and that is something important to you (and potentially other users), then I will look into improving the performance. First of all, I will try to fiddle around with some settings. If that does not improve things, then I might revert the app to the old version.

Appreciate you looking into this. It's not the quality, quality is good. It's just the instrumental version should not have vocals.
Thank you.

@JackismyShephard
I guess I was wrong about instrument version not having vocals. I just tried original AIICoverGen and it have vocals too.
Sorry for wasting your time.


Bump deps, move to Jest, rollup 2

Cleanup
What should be cleaned up or changed:
Working on V2 with Jest provides an incredibly fast feedback loop - it's a pleasure, I love working on it. Working on this is pretty slow at times, need to run yarn build to rebuild the bundle, and mocha-webpack just provides a less nice developer experience. Rollup v1 is also very old at this point.
To make the codebase maintainable for years to come, and more enjoyable to work on (thus more motivation to fix bugs) I would like to:

move to Jest
upgrade to rollup v2
bump dependencies in general

Provide any links for context:

Something else that might help (but that it is probably out of scope here) is to remove any sync mode leftover. I feel things derailed a bit there, and a lot of code was compromised due to that (now removed) feature. Is it doable?

Also: monorepo. Is it really needed?

@afontcu Yes we should remove sync mode (different PR though).
Re mononrepo: I do not like the monorepo here; it adds little value but lots of complexity. I think moving away from it is a pretty significant change and I don't think see that many short-term benefits. We can discuss this more, but I think bumping dependencies (I can finish this week) and removing sync mode have the most immediate value.
I also think we can consider dropping support for earlier versions of Vue 2 (maybe < v2.5) or something. Step by step! I think removing sync mode leftovers and Jest will help a lot; getting the open issues down to around 50 would be nice.

Yes we should.
sync mode can probably be removed, if you are feeling motivated go for it.


fix: dissalow contributor to update own role

Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #336

Alright, I can check if we can disallow the PUT only, but I am not sure we can.

We can, by removing the permission from the roles. However, I don't think that's enough, because the route still allows the users that can call it complete control over their own user record. That's bound to cause problems.


RightMenuViewController

Hello,
I am developing an application and using your MFSideMenu.
I want to handle both side menus if device language was Arabic or English.
It works fine in English but when I tried to test it with arabic device language set The view looked like attached picture. Any idea why this happened?
Your help will be appreciated.
Thanks in advance.
MFSideMenuContainerViewController *container = [MFSideMenuContainerViewController containerWithCenterViewController:centerViewController leftMenuViewController:leftSideMenuViewController rightMenuViewController:leftSideMenuViewController];

I solved it.
I was using the same defined view for both. (Defined two instances from sideMenuView).
Thanks.


I have found problems with double backslashes

If a value contains double backslashes, the writing to the file is incorrect. To correct the problem I changed the function "Escape" like this:
case '\\':
 stringBuilder.Append(@"\\");  // Aggiunta la seconda barra da Marco
 break;

If a value ends with double backslashes, the reading is incorrect. To correct the problem I changed the function "ProcessQuotedValueCharacter" like this:
if (isNonLiteral && c == TomlSyntax.ESCAPE_SYMBOL)
  //if (next >= 0 && (char) next == quote) // Linea eliminata da Marco
     escaped = true;

If there is no newline at the end of the file, the last value remains dirty. To correct the problem I changed the function "ToTomlString" like this:
if (sectionableItems.Count == 0)
{
  tw.Flush();  // Line aggiunta da Marco
  return;
}

I'm probably not following the correct path to reporting bugs, but I'm new to github and don't understand English. So I apologize.
Ciao

Thanks for the reports!
I added the fixes and some basics unit tests regarding the first two problems.
As for the Flush, it's a bit more complicated: while flushing is something that TextWriter API provides, it is not always needed. For instance, it's usually needed if you are using StreamTextWriter with a stream for which you haven't enabled autoflushing (or for which it's not needed).
Because flushing itself can be quite an expensive operation, I think it's best to leave it to Tommy user to flush the writer if they need to after all writing is completed, like so for example
using var writer = new StreamWriter(File.OpenWrite("out.toml"))
toml.WriteTo(writer);
// Flush at the end after all tables and subtables have been written
writer.Flush();

Because of that, I simply added a reminder of this into README.


Download youtube playlist

I have a weird issue where if you download a playlist it will sometimes get to a video and the speed will just drop to where it's going to take like hours but if I kill the command and re-run it skips all downloaded ones and the one that was slow will download at normal speed. is there any way to detect that the speed has dropped and re try the video?

Not at the moment.
Duplicate of #29790, and see also #29326.

Closed in af9e72507.


Add clickable link on the Service Name.

Description
It comes naturally to me to click on the name of the service and not the icon. It would be helpful to include the clickable link to the service in the name as well.
Priority
Medium (Would be very useful)
Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues

Done in f36e7b8abb982a42cb6de3d75c1eb523af19f873 🎉


Issue mapping "-" to leftshift

for some reason this does not work:
- = leftshift

but this does:
- = oneshot(shift)

You want - = layer(shift) (the default mapping). If you inspect your logs you should see a warning about directly mapping modifier keycodes.


Improve Stripe Link support

Description
This Feature will add support to Link when it is saved in the customer wallet.

:tada: This issue has been resolved in version 4.10.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


sbclPackages.nyxt: 3.11.1 -> 3.11.2

Description of changes
changelog: https://nyxt-browser.com/article/release-3.11.2.org

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

2 packages built:

nyxt
sbclPackages.nyxt (sbclPackages.nyxt-gtk)


Adding cohost completion handler

### Summary of the changes

Moving most of the completion code to the common (Workspaces) layer
Adding cohost handler for completion

I tried making each commit small and serving a single purpose, so looking commit-by-commit could be helpful, though returned data in each individual commit is not going to be correct, especially in the first few commits. A lot of merging, filtering and ordering was added in the last few commits to ensure correct final completion list is returned.
One unfortunate thing here is conversion between VS and Roslyn LSP types that we have to do until we move to Roslyn LSP types everywhere in our code. Completion code uses LSP types throughout most of the common code much more so than other requests, and while we need common code for non-cohost LSP endpoint, most of it has to use VS LSP types for now.
Fixes: https://github.com/dotnet/razor/issues/10697

Thanks!

In reply to:<PHONE_NUMBER>


(SIMP-9710) Fix service disable

Fixed

Mask the service when disabling for rngd compatibility so that it is not
restarted on reboot

Changed

Support puppetlabs/stdlib 7.X
Updated REFERENCE.md

SIMP-9710 #close

Other observations (not specifically about this PR):

The README has class parameters in it.  Should reference the REFERENCE.md
I do not see a discussion in the README or init.pp that tells you that the haveged service will not be started (and now masked) if the rngd service is running.

Have verified 'mask' option in Puppet service resource now works. Yeah!

@lnemsick-simp Could you drop those other items in a ticket for future resolution? Given that this is causing issues in other modules, I don't want to hold it up if possible.


ctrl+A  not working in Lyric Editor

Steps to reproduce
1.when we presss ctrl + A  then nothing happend
2.os >windows 8.1 Pro
3. well working in windows 10
4. video is given below for proof
Expected behavior

Versions

https://user-images.githubusercontent.com/100966712/190586574-7ef4cbac-2304-4fa6-9394-e584a65a8b0b.mp4

foobar2000 version:
OpenLyrics version:

Additional information

It's just a standard windows text box. =/
Does the same apply for other text boxes around fb2k? Does the same apply for older versions? etc.

Problem create  for cut /copy/ paste
when not select all  by pressing Ctrl+A


merge poll constants in BSD platforms

Sorry for the different PR about the same constants, the miss in the different architectures appeared progressively as I modify nix source to expose the poll function for the different platforms.
Hopefully, it should be the last one !

@bors: r+

:pushpin: Commit 463e23e has been approved by alexcrichton

:hourglass: Testing commit 463e23e161106aea86208aac98814e8fed134e2f with merge 4f44ccfe48bda0909c86c77de256e9a091e5ce61...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 4f44ccfe48bda0909c86c77de256e9a091e5ce61 to master...


Draft posts are published

Currently posts marked as drafts are published. Configuration needs adding that enables/disabled their generation.

Fixed with https://github.com/carbontwelve/tapestry/pull/14 now pulled into development branch


Migrating from beta3 to beta4

@selvasingh please review

Hi @anuchandy, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (anuchan). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@selvasingh Please sign off on this PR.


Extension API: window.activeColorTheme does not report the correct theme

VSCode Version: 1.45.0
OS Version: Win / Lubuntu

Steps to Reproduce:

Chose a light theme
Restart VS Code
Invoke an extension command that does this:

const ui = {
    [ColorThemeKind.Light]: "light",
    [ColorThemeKind.Dark]: "dark",
    [ColorThemeKind.HighContrast]: "highContrast",
}[window.activeColorTheme.kind];
console.log(`Theme is ${ui}`);

This extension should now report Theme is light. However, for me it reports Theme is dark.
If I change the theme to a dark theme, then back to a light theme and then run the extension command again, it correctly reports Theme is light.
If I restart VS Code, it reports again Theme is dark, even though the theme is light.

Sorry for that, pushed a fix. Hope it's ok if that comes in May, or do you need it urgent?

Thank you for fixing it so quickly! Great work by the way! It is not urgent ;)


Convert ISO region code into flag emoji

🚀
E.g. convert "AU" -> 🇦🇺
Checklist

[x] I checked the Contributing Guidelines before creating this request.
[x] New extensions are written in Swift 5.0.
[x] New extensions support iOS 10.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
[x] I have added tests for new extensions, and they passed.
[x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[x] All extensions are declared as public.
[x] I have added a changelog entry describing my changes.

          4 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 639 tests, with 0 failures (0 unexpected) in 10.512 (12.942) seconds

:book:
tvOS: Executed 607 tests, with 0 failures (0 unexpected) in 2.607 (3.197) seconds

:book:
macOS: Executed 470 tests, with 0 failures (0 unexpected) in 0.641 (0.814) seconds

  Generated by :no_entry_sign: Danger


Query experience does not indicate which cluster you are connected to

Issue Type: Bug
Repro:

Connect to any database and execute a query.

The query experience lists the database name. If you are dealing with multiple clusters/servers having the same database names it is not possible to identify which cluster this particular window is querying by just looking at the query window.
Azure Data Studio version: azuredatastudio 1.31.1 (65fb22cc7c36db9c53af1ed2fdbdf48f66c682be, 2021-07-28T21:03:21.018Z)
OS version: Windows_NT x64 10.0.19043

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.84GB (9.38GB free)

Process Argv

Screen Reader
no

VM
0%

as shown above, there are 3 places you can see the context: document tab header, ADS app title and the status bar.
Does it help?

Closing as per above comment.


Update requirements.txt

A module that was compiled using NumPy 1.x cannot be run in NumPy 2.0.0 as it may crash. To support both 1.x and 2.x versions of NumPy, modules must be compiled with NumPy 2.0. Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.
If you are a user of the module, the easiest solution will be to downgrade to 'numpy<2' or try to upgrade the affected module. We expect that some modules will need time to support NumPy 2.
https://github.com/modelscope/FunClip/issues/90

Thanks


JUnitSoftAssertions not working??

Installed software:

Java 7
Selenium 2.45.0
JUnit 4.12
AssertJ 2.0.0

Relevant pom.xml section:
<dependency>
	<groupId>junit</groupId>
	<artifactId>junit</artifactId>
	<version>4.12</version>
	<scope>test</scope>
</dependency>

<dependency>
	<groupId>org.assertj</groupId>
	<artifactId>assertj-core</artifactId>
	<!-- use 3.0.0 for Java 8 projects -->
	<version>2.0.0</version>
	<scope>test</scope>
</dependency>

<dependency>
	<groupId>org.seleniumhq.selenium</groupId>
	<artifactId>selenium-java</artifactId>
	<version>RELEASE</version>
	<scope>test</scope>
</dependency>

Test code:
@Rule
public final JUnitSoftAssertions softly = new JUnitSoftAssertions();

@Test
public void test() {
        driver.get("some url");
	Select select = new Select(driver.findElement(By.id("select-id")));
	select.selectByValue("option-value");
	driver.findElement(By.id("button")).click();

	int actual = driver.findElements(By.xpath("some xpath")).size();
	int expected = 5;
	softly.assertThat(actual).isEqualTo(expected);

actual != expected, yet the test passes.
When I change softly.assertThat to assertThat, it fails, as it should.
EDIT: BTW, I should say that I had previously used JUnitSoftAssertions in another project with no problems at all, but that was a few months ago.

Can't reproduce it, I tried this test zith assertj-core 2.0.0, JUnit 4.11 and 4.12 using java 7:
public class A {
	@Rule
	public final JUnitSoftAssertions softly = new JUnitSoftAssertions();
	@Test
	public void test() {
		final int actual = 6;
		final int expected = 5;
		this.softly.assertThat(actual).isEqualTo(expected);
	}
}

Can you provide additional information ?

Closing issue as it cannot be reproduced and lack of feedback (I'll reopen the issue if a test case is provided).