Problem with some Tardis data

Hey!
I am having problems converting data from Tardis for following assets/days:
Reading data/binance-futures/SOLUSDT/_trades_2024-01-09_SOLUSDT.csv.gz
Reading data/binance-futures/SOLUSDT/_incremental_book_L2_2024-01-09_SOLUSDT.csv.gz
Error occurred during conversion: index 1500 is out of bounds for axis 0 with size 1500

Reading data/binance-futures/TRBUSDT/_trades_2023-12-31_TRBUSDT.csv.gz
Reading data/binance-futures/TRBUSDT/_incremental_book_L2_2023-12-31_TRBUSDT.csv.gz
Error occurred during conversion: index 1500 is out of bounds for axis 0 with size 1500

I get the sam error on both dates:
Error occurred during conversion: index 1500 is out of bounds for axis 0 with size 1500
Which seem very strange to get the same kind of error on two different asset/date combinations.
P.S. Please, let me know if data upload somewhere on is necessary for debugging.

Please provide the data for the investigation.

Here's the data.
You can download it from here.

Both SOL and TRB converted nicely. TRB required larger buffer size (i indeed used 1500) and SOL went nicely through the converter after applying the fix you kindly provided.
Thank you once again!


data reset on server restart

Reopening #1 as it still happens when using latest ReforgedBingo-Forge-2.0.3-1.12.2:
"Hi, i am experiencing data reset on server restart sometimes for some players. Randomly without errors.
I am using latest bingo on sponge 7.4 and sometimes players caught pokemon is reseted. Bingo card remains the same but they have to catch already caught pokemon as they are no longer green (completed) upon server restart."

Update: its happening only to player who are online when server resets - if you log out before the restart then your bingo progress is saved and working as intended.

Fixed in upcoming version


Update init.py

Type of Change
feature or bug fix or documentation or others
API changed or not
avoid RuntimeError: unexpectedly reached end of file
Raise the error during convert process
Description
detail description
Issues: xxx
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
any library dependency introduced or removed

https://inteltf-jenk.sh.intel.com/job/nlp_toolkit_optimize_validation_localtest/6585/


adds get_source_path function to utils

Provides an alternative to snakemake's workflow.source_path(), that does
not cache the file, and can be used on directories too.
Doesn't fix #101, but provides an alternative to using config['snakemake_dir']

I literally just ran into this problem yesterday (needing a directory reference), so I'm glad to see my wishes so immediately coalesce into a PR without any effort on my part. Thanks for pulling this together

I'm kind of thinking a nicer interface may be to have a 0-argument function that just returns the Path to snakemake app dir or the Snakefile dir. Then you could have something like snakemake_dir()/'resources/whatever'. To me that feels more intuitive and simpler. Or perhaps you just make the argument optional and set it by default to Path.cwd().resolve(), which would have the same effect. That's probably the best actually

Ya I was also initially considering a 0-arg function, but actually the optional argument would be the best of both worlds.. wondering if the name of the function could be more meaningful then? feel free to make any edits!

Would snakemake_dir() be good?
Also, would we keep "snakemake_dir" in the config? It would be more for provenance I guess?

The way it is set-up now, the paths are relative to the folder where the snakefile or rule file is calling it from. That seems intuitive since it's the convention used for other things, like the script: directive.
We could just perhaps add both kinds of functions, source_path, and snakemake_dir as functions in snakebids utils?

Having two separate functions seems reasonable to me. I'd suggest names like snakefile_dir and relative_to_snakefile for clarity (although source_path does have the benefit of being similar to the Snakemake name, so I'm fine with that too).

Just for clarity, @akhanf , when you say two functions, are you thinking one function relative to the snakefile and one function relative to the app directory? Or are you thinking one 0-arg function that returns the snakefile argument and on function of the form function(path) -> path_resolved_to_snakefile

The issue is for this function (and similarly for existing workflow.source_path function), the path is not relative to the snakefile or app directory, it is relative to the file the function is called from. I actually don't know how to automatically get the app directly in this way, since it could be called from a Snakefile in the root dir, a Snakefile in the workflow folder, or a rules file in any rules subdirectory (and so on)..
So I was suggesting one function that does just that (similar semantically to workflow.source_path), and then if there is a way to automatically get the snakemake working directory, another function for that. I can't think of how to implement that right now but I assume there is some way to get that? If there isn't a way to do that, then the one function would suffice.
Both of them can be 0-arg functions for ease of use.

So I just did some digging into the snakemake source. Turns out there's two properties that basically achieve our purpose:

workflow.basedir is the directory containing the root level Snakefile
workflow.current_basedir is the directory containing the file requesting that property (e.g. /path/to/workflow/rules)

Because snakemake uses os.chdir() to change the working directory when the --directory flag is used, I don't believe it's possible to recover the app base directory. It's not saved anywhere so far as I can tell: snakemake only tracks the Snakefile and configfile directories.
At any rate, if the above properties work, that should eliminate the need to roll out our own solution.

Ah that's great! Yes I agree no need to roll out some thing custom then!
Perhaps we can just document it somewhere and/or include the use of them in any examples/templates we have


Problem with another missing icon + icon that has a white background

I created the issue on the upstream repo. https://github.com/themesberg/flowbite-icons/issues/31


[BUG]  Get-PnPSharingForNonOwnersOfSite to get the default sharing setting details is giving incorrect output.

Reporting an Issue or Missing Feature
The command Get-PnPSharingForNonOwnersOfSite to get the default sharing setting details is giving incorrect output.
As per the article https://pnp.github.io/powershell/cmdlets/Get-PnPSharingForNonOwnersOfSite.html the command should return $false if sharing of the site and items in the site is restricted only to owners. I tested on one of our test sites and it returns $True.
Expected behavior
The value returned to be "False"
Actual behavior
The value returned is "True"
Steps to reproduce behavior
Connected via PowerShell:
Connect-PnPOnline -Url https://m365x30315824.sharepoint.com/sites/Design -Interactive
Get-PnPSharingForNonOwnersOfSite

What is the version of the Cmdlet module you are running?
ModuleType Version    PreRelease Name                                PSEdition ExportedCommands

Manifest   2.3.0
Which operating system/environment are you running PnP PowerShell on?

[x] Windows
[ ] Linux
[ ] MacOS
[ ] Azure Cloud Shell
[ ] Azure Functions
[ ] Other : please specify

@hmihaella - Have you just tuned off the ability to share directly via the UI and then run the command?
I have just tested with 2.9.0, but there might be a delay when turning off via SharePoint and running the cmdlet straight after.
However, if you use Disable-PnPSharingForNonOwnersOfSite and then run Get-PnPSharingForNonOwnersOfSite, it will correctly show False.

The command Get-PnPSharingForNonOwnersOfSite simply returns the result of the CSOM method Office365Tenant.IsSharingDisabledForNonOwnersOfSite , so if there is an issue, it should be with CSOM itself.
The SharePoint Online Management Shell has a similar command at Get-SPOSite -Identity https://contoso.sharepoint.com -DisableSharingForNonOwnersStatus with this note:

DisableSharingForNonOwnersStatus is not a persisted setting but rather an analysis of the state of the site collection.

That might explain the delay.

Closing this , it’s all CSOM under the hood and the delay looks like server side thingy, nothing we can do to fix  .


Led pulsing green constantly

I was going through the home app live viewing a few of my nest cams and after I closed the app, I noticed one of them began pulsing as if someone was viewing it live and wouldn’t stop. I restarted homebridge and the camera stopped pulsing. I obviously assume this is a bug and not an actual intrusion. But can someone clarify this for me?

If you mean the error message home app shows (“someone is viewing”) then
it’s probably a bug that ffmpeg failed to quit in background…
On Wed, Aug 8, 2018 at 6:39 PM massimov383<EMAIL_ADDRESS>wrote:

I was going through the home app live viewing a few of my nest cams and
after I logged of one of them began pulsing as if someone was viewing it
live. I assume this is a bug and not an actual intrusion. But can someone
clarify this for me?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/KhaosT/homebridge-nest-cam/issues/31, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABpU4Ay6-LCLw0Qss1cZWHCaD6To_aFIks5uO5LogaJpZM4V06aJ
.


[EC-180][EC-181] Add ommers and transactions from network to new blocks

for convenience this PR is for
[EC-180] Use transaction from pool to construct new block for mining
[EC-181] Create ommers pool and use them in block creation
which are the last pieces of functionality for mining new blocks
~this PR depends on https://github.com/input-output-hk/etc-client/pull/183~

we can do this but I would create separate task for transactions dropping strategy


Howto combine color() and  css variables

Hello,
I'd like to combine postcss-color-function and postcss-css-variables in a single declaration:

:root
{	--color-primary: #f00;
	--color-primary-light: color(var(--color-primary) l(50%));
}

This results a fatal error:

 Unable to parse color from string "var(--color-primary)"

Thank you

This is working with postcss-custom-properties
:root
{   --color-primary: #f00;
    --color-primary-light: color(var(--color-primary) l(50%));
}

body
{
  color: var(--color-primary-light);
}

Gives
body
{
  color: rgb(255, 0, 0);
}

(No error, even if the color is unchanged. Try with a(50%)).
Try by yourself on cssnext playground

postcss-css-variables is harmful in too many way, so I won't do anything special for this plugin. It's exlpained in postcss-custom-properties readme

Looks like a battle between two or multiple developers. Thanks for pointing it out.

It's not a battle. It's allowing future-proof code. postcss-css-variables allow you to write code that will never work in any browser according to specifications, and even worst, that behave in a different way.
By using postcss-css-variables you will not be able any time soon to just "remove this plugin" to benefit from native custom properties support in browsers. And that's a shame for a plugin that use the name "css variables".

I understand the issue and totally agree that a css4 polyfill should follow the W3C specifications. However, I switched to postcss-custom-properties and everything is working fine.
Have a nice weekend


Adding a shared device test suite

Context:
Adds device tests to the plugins folder. These tests can be applied to any device in the PennyLane ecosystem, to verify that it integrates with PennyLane's core, for example when used to create qnodes and run circuits.
The tests are designed to be overly explicit at the expense of code duplication. Every test should be self-explanatory and take minimum effort to run outside of pytest. Since tests only apply to specific types of devices, the _capabilities are used to skip tests if necessary.
The test suite will grow bigger in future, this PR introduces the basic skeleton.
Description of the Change:
Calling the tests should be done with command line via

pytest pennylane/plugins/tests --device default.qubit --shots 60000 --analytic False

The tests are skipped if they do not apply. Currently there are only tests for basic qubit devices (no passthru, no tokens or api, no keyword arguments or backends specified).
The tests support analytic or non-analytic mode (and hence also hardware). For both, the final probability is computed (to not worry about phase factors introduced by devices), and the tolerance of the assert statement is lowered for non-analytic devices. Flaky is used in addition to increase chances of stochastic tests to pass.
Note: Also an analytic device has stochastic tests, namely for the sample return method.
What is still missing
It will be a great challenge to extend the tests further, because the devices need to be "cleaned up" and standarized alongside with the growing test suite. Often, this involves design decisions with ADRs -  for example to determine how capabilities is used in the tests.
Separate CV tests will need to be added.
Important in this PR
This PR proposes a few design solutions that should be reviewed before writing more tests:

Use of flaky
Use of different tolerance but same tests for analytic and non-analytic devices
Creating device in fixture factory and passing the function to the tests
Skipping functions with a simple fixture skip_if
Putting "measurement" and "gate" tests into one file each
Drawing the command line argument using pytest - this could still become a problem if we need to allow passing arbitrary arguments

I am not sure how to handle CodeFactor and Codecov - obviously the style and coverage of the tests inside the pennylane code folder is not applicable...

Hey @thisac @antalszava @josh146 @co9olguy, I tagged you for a pre-review. Usually I'd try to minimize work load like this, but I realised that I had to take lots of design decisions that I would like your opinion on.
This test suite will also determine how devices are written (and may require some updates of plugins), so I think we need a lot of eyes on it... Thanks :heart_decoration:

Also, re: codefactor and codecov:

With codefactor, we currently don't lint the test folder. We could either set up pennylane/plugins/tests to also be skipped, or lint the test folder.

I assume codecov is failing because the new tests directory counts as PennyLane source code, and since these tests aren't being run on Travis, they aren't being marked as covered.

Thanks for your review Josh! Very helpful. I will try to crack the pytest unknown arguments somehow, but it's poorly documented.

About code factor: I don't mind skipping or linting the folder. What would you prefer? Where could I set this?
About codecov: I added an "ignore" flag to codecov.yml.

I think the stochasticity is a deeper discussion we should have with @co9olguy .

By the way, I already used the test when developing the qulacs plugin and they are very helpful in picking up capabilities a device does not have! I think this could become very useful.

Thanks so much for your code review @antalszava and @josh146 .
Overall I implemented your very useful suggestions where ever I could:

Added the new gates like CRY to tests
Make pytest exit if device cannot be created
Lowered default shots to 10,000
fixed complaints from codefactor
Use math functions instead of numpy
Ignore tests in coverage report (we can change this if we decide to run the tests by CI, in which case they are covered)

A few things were tricky and I suggest we revisit them with a refactor of the devices themselves:

Splitting cv and qubit tests - For now the tests will be qubit only. The default.gaussian device is removed from the list of automatically tested core devices, and the tests will exit if the model is not qubit.
Use pytest.mark to skip tests - I tried to implement that, and it would be much neater. We could just parametrize a test with @pytest.mark.capabilities("inverse_operations.true", "model.qubit") or so. But it seems impossible to retrieve the device capabilities in the hook, and I cannot find an option to make it work. So I cleaned up the skip_if fixture a bit, and we can revisit this in future. At the moment, mark would not reduce code.
Use slow decorator to mark stochastic tests - if the user chooses a non-analytic device, this would skip all tests but 2 :) But since the stochastic tests run quite fast, I think this is not necessary?
Making the tol fixture use the device fixture to decide whether to represent the analytic or non-analytic tolerance - the device is only created inside the test, since the test only knows the correct number of wires...This is a basic design decision that we could change (i.e., hack the correct wires into an instance of the device later), but I don't know how stable this is for the future.


Invoke-Command: calling a program via a UNC path in a remote session results in the wrong error being reported

Note that the error only occurs if the executable path passed to & is a UNC path.
Steps to reproduce
Run on Windows, from an elevated console (due to use of "loopback remoting"):
{ $ErrorActionPreference='Stop'; Invoke-Command -ComputerName . { & '\\foo\bar' } } |
  Should -Throw -ErrorId CommandNotFoundException

Expected behavior
The test should pass.
Actual behavior
The test fails:
Expected an exception, with FullyQualifiedErrorId 'CommandNotFoundException' to be thrown, but the FullyQualifiedErrorId was 'RuntimeException'

Instead of  the expected &: The term '\\foo\bar' is not recognized as the name of a cmdlet, function, script file, or operable program. message, the nondescript RuntimeException: An error occurred while creating the pipeline. is reported.
Environment data
PowerShell Core 7.1.0-preview.5

Loop in @PaulHigin for insights.

This is by design.  Invoke-Command returns a RemoteException that wraps the original CommandNotFoundException as the serialized remote exception.  The ActionPreferenceStopException wraps it yet again.  You can see the original exception by:
$err = Get-Error
$err.ErrorRecord.Exception.SerializedRemoteException

@PaulHigin. Yes the original error is wrapped, but it normally - sensibly - still presents like the original error.
As stated, the nondescript wrapping only happens if the executable path happens to be a UNC path.
Contrast the behavior demonstrated in the OP (UNC path) with a local (non-existent) path:
# OK:
PS>  Invoke-Command -ComputerName . { & 'c:\foo\bar' }
ObjectNotFound: The term 'c:\foo\bar' is not recognized as the name of a cmdlet, function, script file,
or operable program.

More equivalently it would be:
Invoke-Command -ComputerName . { & 'c:\foo\bar' } -ErrorAction Stop
ObjectNotFound: The term 'c:\foo\bar' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

$err = Get-Error
$err.ErrorRecord.FullyQualifiedErrorId
CommandNotFoundException

The problem is that in one case an ErrorRecord is returned and the other a RuntimeException, and seems to be how ErrorAction throws a terminating error.  This appears not be related to Invoke-Command since I can get the same results with this:
& { $ErrorActionPreference = "Stop"; & 'c:\foo\bar' }
$err = Get-Error
$err.ErrorRecord.FullyQualifiedErrorId
CommandNotFoundException

The only reason I brought -ErrorAction Stop into the mix was for the sake of the Pester test, so let's leave it out of the picture.
To recapitulate the original concern:
If a non-UNC path yields the expected error message on the caller's side:
# OK
PS>  Invoke-Command -ComputerName . { & 'c:\foo\bar' }
ObjectNotFound: The term 'c:\foo\bar' is not recognized as the name of a cmdlet, function, script file,
or operable program.

then I see no reason why a UNC path should act differently, given that in local, direct invocation the two scenarios yield the same error message:
# !! Unexpectedly yields nondescript error.
PS>  Invoke-Command -ComputerName . { & '\\foo\bar' }
RuntimeException: An error occurred while creating the pipeline.

Hmm, I don't see that behavior with my latest local build of 7.1.0-preview.5.  I get the same RemoteErrorRecord error object in each case you show above.  I get the RuntimeException object only if I use -ErrorAction Stop or set $ErrorActionPreference = 'Stop' as shown in by above examples.

I just tried again in a loaded-without-profiles elevated preview-5 session with $ErrorActionPreference at its default (Continue), and I can reliably reproduce the symptom (on Windows 10 version 1909, but I presume that doesn't matter):
PS> icm -cn . { & C:\no\such }; '---'; icm -cn . { & \\no\such }

ObjectNotFound: The term 'C:\no\such' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
---
RuntimeException: An error occurred while creating the pipeline.


Couldn't launch headless browser: could not send message

2022/12/05 14:14:28 Couldn't launch headless browser: could not send message: could not send message to server: Timeout 30000ms exceeded.
=========================== logs ===========================
<launching> /home/berliangur/.cache/ms-playwright/chromium-978106/chrome-linux/chrome --disable-background-networking --enable-features=NetworkService,NetworkServiceInProcess --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=ImprovedCookieControls,LazyFrameLoading,GlobalMediaControls,DestroyProfileOnBrowserClose,MediaRouter,AcceptCHFrame,AutoExpandDetailsElement --allow-pre-commit-input --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --disable-sync --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --password-store=basic --use-mock-keychain --no-service-autorun --export-tagged-pdf --no-sandbox --user-data-dir=/tmp/chatgpt --remote-debugging-pipe about:blank
<launched> pid=24010
============================================================
exit status 1

added following logs for debugging:

resulting:

my guess it's because I'm running within WSL2 and the solution might be running playwright browser on the host windows and then connect to the running instance from the script instead of launching

See the new Browserless Authentication section of the README.


Enhance references in OMIS payments

This:

adds the order reference to the description of a GOV.UK payment
uses the order reference and the first 8 chars of the payment gateway session id as GOV.UK payment reference. This is because it's shown to the user at the end of the transaction and it could be used to get to the record either from the GOV.UK Pay admin area and/or in our system
stores the GOV.UK payment reference on the OMIS payment record as transaction_reference

Codecov Report

Merging #862 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #862   +/-   ##
========================================
  Coverage    96.65%   96.65%
========================================
  Files          160      160
  Lines         4720     4720
  Branches       456      456
========================================
  Hits          4562     4562
  Misses          99       99
  Partials        59       59

Impacted Files
Coverage Δ

datahub/omis/payment/managers.py
100% <ø> (ø)
:arrow_up:

datahub/omis/payment/utils.py
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[Debug] Cannot launch node2 debug configuration for electron application

VSCode Version: 1.8.1
OS Version: Windows 8.1 x64

I have an electron application. When using "type": "node" in launch.config debugging is going fine. When I change to "type": "node2", I get the following error message at the start:

Cannot connect to runtime process, timeout after 10000 ms - (reason: Cannot connect to the target: connect ECONNREFUSED <IP_ADDRESS>:5372).

Restarting VS Code doesn't help.
I've noticed that when using "type": "node", I get the following output in Debug Console:
c:\dev\myApp/node_modules/.bin/electron.cmd --debug-brk=11978 c:\dev\myApp --enable-logging --remote-debugging-port=9222 built\app.js
And for "type": "node2":
c:\dev\myApp/node_modules/.bin/electron.cmd --inspect=5372 --debug-brk c:\dev\myApp --enable-logging --remote-debugging-port=9222 built\app.js
In "node" case VS Code uses --debug-brk=11978 parameter and in "node2" case it uses --inspect=5372.

This is caused by Electron hasn't landed the newest version of V8, which includes V8_inspector that's required by our new Node debugger.
https://github.com/electron/electron/issues/6634

Yep, what @auchenberg said


Logging error in pycalico.ipam

With calico-kubernetes v0.6.0, I'm seeing a logging error:
Nov 14 00:30:34 kubernetes-minion-1 kubelet[22990]: 2015-11-14 00:30:33,099 28521 [00bf223be692] INFO Configuring Calico network interface
Nov 14 00:30:34 kubernetes-minion-1 kubelet[22990]: 2015-11-14 00:30:33,148 28521 [00bf223be692] INFO Using Calico IPAM
Nov 14 00:30:34 kubernetes-minion-1 kubelet[22990]: Traceback (most recent call last):
Nov 14 00:30:34 kubernetes-minion-1 kubelet[22990]: File "/code/build/calico_kubernetes/out00-PYZ.pyz/logging", line 850, in emit
Nov 14 00:30:34 kubernetes-minion-1 kubelet[22990]: File "/code/build/calico_kubernetes/out00-PYZ.pyz/logging", line 723, in format
Nov 14 00:30:34 kubernetes-minion-1 kubelet[22990]: File "/code/build/calico_kubernetes/out00-PYZ.pyz/logging", line 467, in format
Nov 14 00:30:34 kubernetes-minion-1 kubelet[22990]: KeyError: 'identity'
Nov 14 00:30:34 kubernetes-minion-1 kubelet[22990]: Logged from file pycalico.ipam, line 403

Not sure if it's benign yet. Can you do a code read to see if we're setting the Formatter on the wrong log handler Alex?

Fixed by #102


Added DefaultBranch in git RepoInfo.

fix #275
Added action GetRepoInfo to get repo info.
Updated gateway api to return default branch into type ProjectResponse

@sgotti I didn't implement tests because gitea 1.8.3 hasn't api to change default repo branch. I can add them when we change gitea (and sdk) version

@alessandro-sorint Thanks for the PR. I don't think it's a good idea to call the remote source api everytime an agola project api is called. We should store the default branch in the configstore and add an api to let the user refresh the remote project info (that could be used also for other needs) and, as a future improvement, automatically update it when a call to the remote source api returns an updated default branch.

@sgotti I didn't implement tests because gitea 1.8.3 hasn't api to change default repo branch. I can add them when we change gitea (and sdk) version

We definetly needs tests before merging. So you should update the gitea version and manually implement the gitea api request if not provided by the sdk (we are already doing something similar for some gitea apis) or find a way to update the gitea sdk (see #247 that's blocked).

@sgotti I didn't implement tests because gitea 1.8.3 hasn't api to change default repo branch. I can add them when we change gitea (and sdk) version

We definetly needs tests before merging. So you should update the gitea version and manually implement the gitea api request if not provided by the sdk (we are already doing something similar for some gitea apis) or find a way to update the gitea sdk (see #247 that's blocked).

I update gitea in this PR? It's ok the gitea v1.15.9?

@sgotti I didn't implement tests because gitea 1.8.3 hasn't api to change default repo branch. I can add them when we change gitea (and sdk) version

We definetly needs tests before merging. So you should update the gitea version and manually implement the gitea api request if not provided by the sdk (we are already doing something similar for some gitea apis) or find a way to update the gitea sdk (see #247 that's blocked).

I update gitea in this PR? It's ok the gitea v1.15.11?

Please open a new PR so we could check that there're no regressions in the tests.

@sgotti can you do the review please?

Hi @sgotti can you review please?

Hi @sgotti can you review please?

@sgotti can you restart the run please?


元数据配置-yaml格式

What would you like to be added:
希望和seata-java的配置文件格式保持一致
设计文档：https://transaction.yuque.com/lq4znd/me6vqg/px6i86
Why is this needed:

ok


Modal menus subject to bugs

Currently, I'm unable to get any graph node modal menus on the Jupyter notebook with a Python kernel. This regression happened after a development installation. Previously, I had them. I'll check again and add more details here.
Moreover on Jupyterlab, right clicking opens a specific Jupyterlab context menu. See https://github.com/jupyterlab/jupyterlab/issues/3521

Humm, I’ve always thought you had to press SHIFT and then right click to see custom menus on jupyterlab... need to investigate this further...

It's possibly a regression. Last time I tried, SHIFT-right-click would replace the Jupyterlab context menu by .. the browser context menu.

Fixed on #88


build: Add logging lint checks to ruff

Checks for some common logging patterns to avoid.
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have bumped the version of the library

Needs #205


Debug with code inside of the virtual environment directory.

I can't agree with https://github.com/Microsoft/vscode-python/issues/2993#issuecomment-438087231

Using the debugger helps to understand the external code.
Sometimes, when I try to find a bug, I find that the bug is not mine, but from external code.
p.s. I used PyCharm before.

Thank you for your help.

You can use the setting debugStdLib=true for now to debug and step through 3rd party code.


Allow both HMR clients and live reloading clients

Explain the motivation for making this change. What existing problem does the pull request solve?

I almost preview on multi devices, sometimes I switch a device to HMR mode, and others are Live Reload mode, currently only the "HMR device" can update. I already used this patch a few months, and I think I'm not the only need it.

Prefer small pull requests. These are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it.

Very small :-)

Test plan (required)

Test Steps:

Open multi devices or emulators, switch one to HMR mode, and others are Live Reloading mode.
Update your code.

Expected result:

All devices can updated.
The "HMR device" only update with HOT RELOADING experience.

Aha, I forgot I created a pull request about this and it was closed.
See #6837
What's the status about that after a few months? can this be merged? I used it long time, but I must patch every version.

The comments are a bit odd, usually you don't want comments in the source code to refer to "this commit" because it's totally unclear what commit that's referring to.
Is there any behavior that gets degraded with this pull request?
Can you add a test to ensure this functionality continues to work? The reloading stuff seems to break a lot so we could really use better tests there.

Hi there!
The packager no longer lives in this repo. It now lives in https://github.com/facebook/metro-bundler. The reasoning for the split is explained here: https://github.com/facebook/react-native/issues/13976.
If you're still interested in pursuing changes to the packager for this PR, please open a PR on that repo! :)
Thanks!
-Adam


Prisma Connect Causes NodeJS to Close With Exit Code 0

Bug description
Prisma causes nextjs dev environment to exit with code 0 after connection
How to reproduce
# Commands
npx prisma generate
npm run dev  # Crashes when loading http://<IP_ADDRESS>:3000/database

# When running production, the build process gets stuck
npx prisma generate
npm run build  # Never gets past this
npm run start

I don't have a pages directory, I only have an app directory. The client exits no matter if using route.ts(x) or page.ts(x)
Expected behavior
Prisma to retrieve all rows and not exit the nextjs app instead
Prisma information

// {root}/prisma/schema.prisma
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "cockroachdb"
  url      = env("DATABASE_URL")
}

model test {
  id    BigInt  @id(map: "test_pk") @default(sequence())
  hello String?
}

model posts {
  id   BigInt  @id(map: "posts_pk") @default(sequence())
  slug String?
}

// {root}/app/database/page.tsx
// TODO: Find Out If Prisma Can Even Work In The App Directory
import prisma from '../../lib/prisma';

export default async function Page({params}) {
	const posts = await prisma.posts.findMany()  // This line is what causes the app to exit

// 	return (
//

//
Hello

// 			{posts.map((post) => (
//
{post.slug}

// 			))}
//

// 	)
}

// {root}/lib/prisma.ts
// https://vercel.com/guides/nextjs-prisma-postgres#step-4.-install-and-generate-prisma-client
import { PrismaClient } from '@prisma/client';

let prisma: PrismaClient;

if (process.env.NODE_ENV === 'production') {
	prisma = new PrismaClient();
} else {
	if (!global.prisma) {
		global.prisma = new PrismaClient();
	}
	prisma = global.prisma;
}

export default prisma;

Environment & setup

OS: Debian
Database: CockroachDB
Node.js version: v19.7.0

Prisma Version
npx prisma -v
Environment variables loaded from .env
prisma                  : 4.11.0
@prisma/client          : 4.11.0
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 8fde8fef4033376662cad983758335009d522acb (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 8fde8fef4033376662cad983758335009d522acb (at<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.11.0-57.8fde8fef4033376662cad983758335009d522acb
Default Engines Hash    : 8fde8fef4033376662cad983758335009d522acb
Studio                  : 0.483.0

I'll be adding the results of DEBUG="*" npm run dev > ~/Desktop/prisma.log 2>&1 once I ensure no private information is stored in the log

# ~/Desktop/prisma.log
><EMAIL_ADDRESS>dev
> next dev

 ready  - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
 info   - Loaded env from /home/alexis/Desktop/site/.env
 warn   -  You have enabled experimental feature (appDir) in next.config.mjs.
 warn   - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.

 info   - Thank you for testing `appDir` please leave your feedback at https://nextjs.link/app-feedback
2023-03-15T18:31:17.738Z next:jsconfig-paths-plugin tsconfig.json or jsconfig.json paths: {}
2023-03-15T18:31:17.739Z next:jsconfig-paths-plugin resolved baseUrl: /home/alexis/Desktop/site
 info   - automatically enabled Fast Refresh for 1 custom loader
2023-03-15T18:31:17.840Z next:jsconfig-paths-plugin tsconfig.json or jsconfig.json paths: {}
2023-03-15T18:31:17.840Z next:jsconfig-paths-plugin resolved baseUrl: /home/alexis/Desktop/site
2023-03-15T18:31:17.844Z next:jsconfig-paths-plugin tsconfig.json or jsconfig.json paths: {}
2023-03-15T18:31:17.844Z next:jsconfig-paths-plugin resolved baseUrl: /home/alexis/Desktop/site
 event  - compiled client and server successfully in 1042 ms (263 modules)
 wait   - compiling...
 wait   - compiling /database/page (client and server)...

2023-03-15T18:31:25.127Z next:jsconfig-paths-plugin paths are empty, bailing out
... (Redacted Because Same Message 1,000+ times)
2023-03-15T18:31:25.127Z next:jsconfig-paths-plugin paths are empty, bailing out

 event  - compiled client and server successfully in 6s (452 modules)
2023-03-15T18:31:25.589Z prisma:tryLoadEnv  Environment variables loaded from /home/alexis/Desktop/site/.env
2023-03-15T18:31:25.592Z prisma:tryLoadEnv  Environment variables loaded from /home/alexis/Desktop/site/.env
2023-03-15T18:31:25.593Z prisma:client  dirname /home/alexis/Desktop/site/node_modules/.prisma/client
2023-03-15T18:31:25.593Z prisma:client  relativePath ../../../prisma
2023-03-15T18:31:25.593Z prisma:client  cwd /home/alexis/Desktop/site/prisma
2023-03-15T18:31:25.593Z prisma:client  protocol graphql
2023-03-15T18:31:25.594Z prisma:client  clientVersion 4.11.0
2023-03-15T18:31:25.594Z prisma:client  clientEngineType library
2023-03-15T18:31:25.594Z prisma:client:libraryEngine  internalSetup
2023-03-15T18:31:25.668Z prisma:tryLoadEnv  Environment variables loaded from /home/alexis/Desktop/site/.env
2023-03-15T18:31:25.671Z prisma:tryLoadEnv  Environment variables loaded from /home/alexis/Desktop/site/.env
2023-03-15T18:31:25.671Z prisma:client  dirname /home/alexis/Desktop/site/node_modules/.prisma/client
2023-03-15T18:31:25.671Z prisma:client  relativePath ../../../prisma
2023-03-15T18:31:25.671Z prisma:client  cwd /home/alexis/Desktop/site/prisma
2023-03-15T18:31:25.672Z prisma:client  protocol graphql
2023-03-15T18:31:25.672Z prisma:client  clientVersion 4.11.0
2023-03-15T18:31:25.672Z prisma:client  clientEngineType library
2023-03-15T18:31:25.673Z prisma:client:libraryEngine  internalSetup
2023-03-15T18:31:25.600Z prisma:get-platform  Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "debian"
}
2023-03-15T18:31:25.611Z prisma:get-platform  Command "uname -m" successfully returned "x86_64
"
2023-03-15T18:31:25.611Z prisma:get-platform  Trying platform-specific paths for "debian" (and "ubuntu")
2023-03-15T18:31:25.636Z prisma:get-platform  Command "ls -v "libssl.so.0*" /usr/lib/x86_64-linux-gnu | grep libssl.so | grep -v "libssl.so.0"" successfully returned "libssl.so.1.1
"
2023-03-15T18:31:25.636Z prisma:get-platform  Found libssl.so file using platform-specific paths: libssl.so.1.1

2023-03-15T18:31:25.636Z prisma:get-platform  The parsed libssl version is: 1.1.x
2023-03-15T18:31:25.637Z prisma:get-platform  Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "debian"
}
2023-03-15T18:31:25.642Z prisma:get-platform  Command "uname -m" successfully returned "x86_64
"
2023-03-15T18:31:25.642Z prisma:get-platform  Trying platform-specific paths for "debian" (and "ubuntu")
2023-03-15T18:31:25.666Z prisma:get-platform  Command "ls -v "libssl.so.0*" /usr/lib/x86_64-linux-gnu | grep libssl.so | grep -v "libssl.so.0"" successfully returned "libssl.so.1.1
"
2023-03-15T18:31:25.666Z prisma:get-platform  Found libssl.so file using platform-specific paths: libssl.so.1.1

2023-03-15T18:31:25.667Z prisma:get-platform  The parsed libssl version is: 1.1.x
2023-03-15T18:31:25.668Z prisma:client:libraryEngine:loader  Searching for Query Engine Library in /home/alexis/Desktop/site/node_modules/.prisma/client
2023-03-15T18:31:25.668Z prisma:client:libraryEngine:loader  loadEngine using /home/alexis/Desktop/site/node_modules/.prisma/client/libquery_engine-debian-openssl-1.1.x.so.node
2023-03-15T18:31:25.760Z prisma:get-platform  Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "debian"
}
2023-03-15T18:31:25.777Z prisma:get-platform  Command "uname -m" successfully returned "x86_64
"
2023-03-15T18:31:25.778Z prisma:get-platform  Trying platform-specific paths for "debian" (and "ubuntu")
2023-03-15T18:31:25.819Z prisma:get-platform  Command "ls -v "libssl.so.0*" /usr/lib/x86_64-linux-gnu | grep libssl.so | grep -v "libssl.so.0"" successfully returned "libssl.so.1.1
"
2023-03-15T18:31:25.819Z prisma:get-platform  Found libssl.so file using platform-specific paths: libssl.so.1.1

2023-03-15T18:31:25.819Z prisma:get-platform  The parsed libssl version is: 1.1.x
2023-03-15T18:31:25.821Z prisma:get-platform  Found distro info:
{
  "targetDistro": "debian",
  "familyDistro": "debian",
  "originalDistro": "debian"
}
2023-03-15T18:31:25.836Z prisma:get-platform  Command "uname -m" successfully returned "x86_64
"
2023-03-15T18:31:25.836Z prisma:get-platform  Trying platform-specific paths for "debian" (and "ubuntu")
2023-03-15T18:31:25.876Z prisma:get-platform  Command "ls -v "libssl.so.0*" /usr/lib/x86_64-linux-gnu | grep libssl.so | grep -v "libssl.so.0"" successfully returned "libssl.so.1.1
"
2023-03-15T18:31:25.876Z prisma:get-platform  Found libssl.so file using platform-specific paths: libssl.so.1.1

2023-03-15T18:31:25.877Z prisma:get-platform  The parsed libssl version is: 1.1.x
2023-03-15T18:31:25.878Z prisma:client:libraryEngine:loader  Searching for Query Engine Library in /home/alexis/Desktop/site/node_modules/.prisma/client
2023-03-15T18:31:25.878Z prisma:client:libraryEngine:loader  loadEngine using /home/alexis/Desktop/site/node_modules/.prisma/client/libquery_engine-debian-openssl-1.1.x.so.node
2023-03-15T18:31:25.882Z prisma:client:libraryEngine  library starting

This is the log from when I commented out the code that causes the crash. Nothing else was changed in the code
# ~/Desktop/prisma-no-crash.log
><EMAIL_ADDRESS>dev
> next dev

 ready  - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
 info   - Loaded env from /home/alexis/Desktop/site/.env
 warn   -  You have enabled experimental feature (appDir) in next.config.mjs.
 warn   - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.

 info   - Thank you for testing `appDir` please leave your feedback at https://nextjs.link/app-feedback
2023-03-15T18:32:47.651Z next:jsconfig-paths-plugin tsconfig.json or jsconfig.json paths: {}
2023-03-15T18:32:47.652Z next:jsconfig-paths-plugin resolved baseUrl: /home/alexis/Desktop/site
2023-03-15T18:32:47.668Z next:jsconfig-paths-plugin tsconfig.json or jsconfig.json paths: {}
2023-03-15T18:32:47.668Z next:jsconfig-paths-plugin resolved baseUrl: /home/alexis/Desktop/site
2023-03-15T18:32:47.679Z next:jsconfig-paths-plugin tsconfig.json or jsconfig.json paths: {}
2023-03-15T18:32:47.680Z next:jsconfig-paths-plugin resolved baseUrl: /home/alexis/Desktop/site
 info   - automatically enabled Fast Refresh for 1 custom loader
 event  - compiled client and server successfully in 1497 ms (263 modules)
 wait   - compiling...
 wait   - compiling /database/page (client and server)...

2023-03-15T18:32:56.104Z next:jsconfig-paths-plugin paths are empty, bailing out
... (Redacted Because Same Message 1,000+ times)
2023-03-15T18:32:56.105Z next:jsconfig-paths-plugin paths are empty, bailing out

 event  - compiled client and server successfully in 6.6s (450 modules)
2023-03-15T18:32:56.565Z compression gzip compression
 error  - SyntaxError: "undefined" is not valid JSON
    at JSON.parse (<anonymous>)
2023-03-15T18:32:56.653Z send allow dotfile "/home/alexis/Desktop/site/.next/static/chunks/polyfills.js"
2023-03-15T18:32:56.654Z send stat "/home/alexis/Desktop/site/.next/static/chunks/polyfills.js"
2023-03-15T18:32:56.656Z send pipe "/home/alexis/Desktop/site/.next/static/chunks/polyfills.js"
2023-03-15T18:32:56.657Z send accept ranges
2023-03-15T18:32:56.657Z send modified Wed, 15 Mar 2023 18:32:48 GMT
2023-03-15T18:32:56.657Z send etag W/"16544-186e68bd39c"
2023-03-15T18:32:56.657Z send content-type application/javascript
2023-03-15T18:32:56.662Z send allow dotfile "/home/alexis/Desktop/site/.next/static/chunks/webpack.js"
2023-03-15T18:32:56.663Z send stat "/home/alexis/Desktop/site/.next/static/chunks/webpack.js"
2023-03-15T18:32:56.664Z send allow dotfile "/home/alexis/Desktop/site/.next/static/chunks/main-app.js"
2023-03-15T18:32:56.665Z send stat "/home/alexis/Desktop/site/.next/static/chunks/main-app.js"
2023-03-15T18:32:56.667Z send pipe "/home/alexis/Desktop/site/.next/static/chunks/webpack.js"
2023-03-15T18:32:56.667Z send accept ranges
2023-03-15T18:32:56.667Z send modified Wed, 15 Mar 2023 18:32:56 GMT
2023-03-15T18:32:56.668Z send etag W/"dac4-186e68beffc"
2023-03-15T18:32:56.668Z send content-type application/javascript
2023-03-15T18:32:56.668Z send pipe "/home/alexis/Desktop/site/.next/static/chunks/main-app.js"
2023-03-15T18:32:56.668Z send accept ranges
2023-03-15T18:32:56.669Z send modified Wed, 15 Mar 2023 18:32:48 GMT
2023-03-15T18:32:56.669Z send etag W/"4bc31a-186e68bd39c"
2023-03-15T18:32:56.669Z send content-type application/javascript
2023-03-15T18:32:56.670Z compression gzip compression
2023-03-15T18:32:56.671Z compression gzip compression
2023-03-15T18:32:56.672Z compression gzip compression
2023-03-15T18:32:57.125Z send allow dotfile "/home/alexis/Desktop/site/.next/static/chunks/app-client-internals.js"
2023-03-15T18:32:57.126Z send stat "/home/alexis/Desktop/site/.next/static/chunks/app-client-internals.js"
2023-03-15T18:32:57.126Z send pipe "/home/alexis/Desktop/site/.next/static/chunks/app-client-internals.js"
2023-03-15T18:32:57.126Z send accept ranges
2023-03-15T18:32:57.126Z send modified Wed, 15 Mar 2023 18:32:56 GMT
2023-03-15T18:32:57.126Z send etag W/"82e07-186e68bf000"
2023-03-15T18:32:57.126Z send content-type application/javascript
2023-03-15T18:32:57.127Z compression gzip compression

Maybe read through these and see if there is a workaround that might work for you: https://github.com/prisma/prisma/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A"topic%3A+segmentation+fault"

I had tested https://github.com/prisma/prisma/issues/10649#issuecomment-1445170405 and setting engineType = "binary" does provide a workaround which allows me to use Prisma in my dev environment. Prisma Studio still segfaults though

Hi @alexisart and thank you for the report! Could you check if updating prisma and @prisma/client to 4.12.0-integration-rtld-deepbind.3 fixes the issue for you? It does in the cases that I tested, but it would be very helpful to test this on more different systems. Since your bug report is a bit different than other similar ones and you're using CockroachDB and not Postgres, it would be especially valuable to know if it works in your case.
This is an experimental dev version not intended for production but if it works as expected, we'll work on making this land in a stable release. Thank you!

4.12.0-integration-rtld-deepbind.3

Yes, this fixes the issue both for Prisma studio and for not using engineType = "binary"

Thank you for checking and for confirming! I'm going to leave this issue open for now since https://github.com/prisma/prisma/pull/18426 is not merged yet, we are now confident that it works and doesn't introduce any unwanted side effects, and will work on finalizing and releasing it ASAP.

This issue is fixed in Prisma 4.13.0 which will be released tomorrow, on Tuesday, Apr 18. If you need to temporarily use a pre-release version until then, you can use 4.13.0-dev.33.

For future readers:
Note that this GitHub issue is about a specific bug that occurs when using Node.js 17+ on a system with OpenSSL 1.1 on x86-64 CPUs when using TLS to connect to database. Please do not post comments here if you encounter a segfault under different circumstances, and open a new issue instead.
If you are facing segfaults on ARM, please leave a comment in https://github.com/prisma/prisma/issues/18510 or open a new issue.


Remove Hidden Libraries from new Library Dropdown

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
SharePoint CSOM
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
No response
Issue description
Is there any configuration on hidden libraries to remove them from the new Library Dropdown feature?
Feature details

https://www.microsoft.com/en-ie/microsoft-365/roadmap?filters=&searchterms=81990
https://m365log.com/onedrive/microsoft-onedrive-sharepoint-library-dropdown-menu/

At first I regarded this as a support issue, but after contacting support I have been told this feature cannot be removed from a site or changed so I am hopping there is something I have missed which will stop hidden libraries from being displayed in the dropdown.

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
SharePoint CSOM
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

[ ]  💥 Internet Explorer
[x]  💥 Microsoft Edge
[x]  💥 Google Chrome
[ ]  💥 FireFox
[ ]  💥 Safari
[ ]  mobile (iOS/iPadOS)
[ ]  mobile (Android)
[ ]  not applicable
[ ]  other (enter in the "Additional environment details" area below)

Additional environment details
No response
Issue description
Is there any configuration on hidden libraries to remove them from the new Library Dropdown feature?
Feature details

https://www.microsoft.com/en-ie/microsoft-365/roadmap?filters=&searchterms=81990
https://m365log.com/onedrive/microsoft-onedrive-sharepoint-library-dropdown-menu/

At first I regarded this as a support issue, but after contacting support I have been told this feature cannot be removed from a site or changed so I am hopping there is something I have missed which will stop hidden libraries from being displayed in the dropdown.

Not only that, we are deliberately not showing certain libraries in the navigation since hey are backend libraries. With this drop down, users can now actively switch to these libraries and easily get confused. The ability to hide this drop down will be very valuable. Thanks!


[c-ares] build failure cross compile

Host Environment

OS: Ubuntu/Linux
Compiler: x86_64-w64-mingw32-gcc 9.3.0
Triplet: mingw-static

To Reproduce
Steps to reproduce the behavior:
./vcpkg install --triplet mingw-static c-aries
Failure logs
This seems to be issue with generation of `ares_config.h` not really sure how to pass any variables in.
# vcpkg install c-ares
Computing installation plan...
The following packages will be built and installed:
    c-ares[core]:x64-mingw-static -> 1.17.1#2
Detecting compiler hash for triplet x64-mingw-static...
Could not locate cached archive: /root/.cache/vcpkg/archives/d8/d85b98e9a8c24305b5174ec64e76f3f71df2a3a15b407df27541a6a4342e5f77.zip
Starting package 1/1: c-ares:x64-mingw-static
Building package c-ares[core]:x64-mingw-static...
-- Using community triplet x64-mingw-static. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: /vcpkg/triplets/community/x64-mingw-static.cmake
-- Using /vcpkg/downloads/c-ares-c-ares-cares-1_17_1.tar.gz
-- Cleaning sources at /vcpkg/buildtrees/c-ares/src/res-1_17_1-7723edf4cb.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /vcpkg/downloads/c-ares-c-ares-cares-1_17_1.tar.gz
-- Using source at /vcpkg/buildtrees/c-ares/src/res-1_17_1-7723edf4cb.clean
-- Configuring x64-mingw-static-dbg
-- Configuring x64-mingw-static-rel
-- Building x64-mingw-static-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:155 (message):
    Command failed: /vcpkg/downloads/tools/cmake-3.20.2-linux/cmake-3.20.2-linux-x86_64/bin/cmake --build . --config Debug --target install -- -v -j33
    Working Directory: /vcpkg/buildtrees/c-ares/x64-mingw-static-dbg
    See logs for more information:
      /vcpkg/buildtrees/c-ares/install-x64-mingw-static-dbg-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_build_cmake.cmake:104 (vcpkg_execute_build_process)
  scripts/cmake/vcpkg_install_cmake.cmake:44 (vcpkg_build_cmake)
  ports/c-ares/portfile.cmake:25 (vcpkg_install_cmake)
  scripts/ports.cmake:141 (include)

Error: Building package c-ares:x64-mingw-static failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `./vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: c-ares:x64-mingw-static
  Vcpkg version: 2021-08-03-unknownhash

Additionally, attach any relevant sections from the log files above.

install-x64-mingw-static-dbg-out.log
Additional context

was trying to install grpc which this is a dependency.
cross compiling from in linux docker container.
ares_config.h is generated via src/lib/ares_config.h.cmake called from src/lib/CMakeList.txt:7
however not sure how to override the cmake variables within vcpkg

figured workaround that to get c-ares on the copy of vcpkg on Linux for mingw.

build on windows computer using msys2 and x64-mingw-static
transfer $VCPKG_ROOT/installed/vcpkg/info/c-ares_1.17.2_x64-mingw-static.list and files listed to Linux box.
copy entry for c-ares install from $VCPKG_ROOT/installed/vcpkg/status or $VCPKG_ROOT/installed/vcpkg/updates/${SOME_NUMBER} to Linux box's $VCPKG_ROOT/installed/vcpkg/status

Still have to test and use the library but I have installed grpc:x64-mingw-static that depends on successfully.
problem issue seems to be with c-ares build and not necessary vcpkg.

This issue hasn’t been updated in 3 month, if it is still an issue, please reopen this issue.


Refactor oauth flow

Removes redundant self.bus definition
Refactor oauth message handling to use get_response instead of registering handlers
Remove redundant data=None from message.forward calls causing editor warnings
Add annotations to methods

Needs https://github.com/OpenVoiceOS/ovos-PHAL-plugin-oauth/pull/15


Tensorflow merge

Merge tag 'swift-DEVELOPMENT-SNAPSHOT-2019-09-02-a' into tensorflow from tensorflow-merge

@ematejska Welcome back! :)


Byron wallet restoration not possible on latest versions

Context
Back in december I have restored two Byron wallets successfuly, then I migrated one of them. Last month (and today) I tried migrating the other one, unsuccessfully. I run into the same issue as described here: #1552. On that issue there is a workaround mentioned. One needs to delete and restore the Byron wallet. However restoration of said wallet also fails.

Information
-

Version
2020.4.7 (git revision: cff0e391985887f60b9076aace207674bef6a2b4), jormungandr 0.8.15

Platform
Linux, the least

Installation
From Github Release

Steps to Reproduce

  $ curl -X POST http://localhost:8090/v2/byron-wallets/random \
  -H "Content-Type: application/json" \
  -d '{
    "name": "MyByronWallet",
    "passphrase": "MySecurePassphrase",
    "mnemonic_sentence": [
      "survey",
      "wonder",
      ...
  ]}'

Expected behavior
returns
{ ..., "id": "aa129a07d1ce083e67597348f1788747a034686e", ... }

Actual behavior
returns
{"code":"bad_request","message":"wallet id should be a hex-encoded string of 40 characters"}

Resolution

QA

Hi Viktor. There has been a breaking change in the API. The style of wallet has moved from path parameters to body parameters. So instead of http://localhost:8090/v2/byron-wallets/random you should hit http://localhost:8090/v2/byron-wallets/ and, the body should now contain a style field set to random.
See also: https://input-output-hk.github.io/cardano-wallet/api/edge/#operation/postByronWallet


Nav bar fix and refactoring

Got the nav menu working. I also removed the drawer functionality, since I didn't really see a point in it opening and closing, at least on desktop. We can re-visit it later when we want to optimize it for mobile. Right now I want to get the core working. I also tried to use the default MudBlazor dark theme, but I have not yet been able to figure out how to get it to apply the theme to the page. This is something that I think can also wait until we have the site working more, I would rather us spend time on core functionality than fun bits like themes. I have not re-factored other code out yet, since it really isn't doing anything yet.

 Refactor @Code Sections Into Separate Files

Destination branch switched to development.


revive the doc for building without nix

@kentosugama

Before merging, did someone test if this still works reliably?

Just doing some repo cleanup for better focussing on active work:
Closing PR as it seems inactive for a longer time. Please re-open if it is still relevant and after it has been updated with latest master changes.


App Approve | App Manager is not receiving the notification

Current Behavior
App Manager is not receiving the notification on an App Approval by an authorised approver but Service Manager is receiving it instead.
Expected Behavior
App Manager should received Approval of App notification instead of Service Manager.
Steps To Reproduce

Log in to portal as CX-Operator.
Navigate to the "App Release Process" page and Release an App (currently App Manager is not able to do so, because there is an issue, please follow the issue for more details)
Navigate to the "App Management: Admin Board" page.
Locate an application in "In Review" status.
Click on the approval icon to approve the application.
Verify if a notification is received on the portal interface (Notification) or via email.

Findings
This issue is related to the notification of an APP. App Manager is not receiving the notification if Admin approves the APP but when I investigate it so, I found that Service Manager is receiving the APP's notification instead
On further investigation, I found that wrong role Service Manager has been mentioned instead of App Manager under approveAppUserRoles param in CD repo:
appmarketplace.approveAppUserRoles.role0 : `"Sales Manager"`
appmarketplace.approveAppUserRoles.role1 : `"Service Manager"`

https://github.com/Cofinity-X/portal-charts/blob/262d6c60e56d88f5ecaea1291be3a0218e2ad215/portal/charts/values.yaml#L504

For decline the receiving user is coming from ServiceManagerRoles:
https://github.com/eclipse-tractusx/portal-backend/blob/e20a452aa7aa51b7ed43175debbebb4f9808219c/src/marketplace/Apps.Service/BusinessLogic/AppReleaseBusinessLogic.cs#L366
Either we need AppManagerRoles or DeclineAppUserRoles config.


Using backbone-rails with jasmine-webkit-headless

When I tried to run jasmine-webkit-headless it complained that it could not find the backbone/#{application_name} file.
couldn't find file 'backbone/application_name'
This refers to an entry in 'application.js' placed there to load the generated/scaffolded main backbone application file into the Rails assets pipeline:
//= require backbone/application_name
When this line is changed to
//= require ./backbone/application_name
the problem is solved. In other application.js files I saw relative paths being loaded using the leading dot-slash too.
Maybe you could adapt your generators/scaffolders to incorporate this minor change.

when you load up the application as usual, outside of jasmine-webkit, do you get the same errors? Also what version of rails are you using?

I took this from the Sprockets 2.1.2 source code:
  # The `require` directive functions similar to Ruby's own `require`.
  # It provides a way to declare a dependency on a file in your path
  # and ensures its only loaded once before the source file.
  #
  # `require` works with files in the environment path:
  #
  #     //= require "foo.js"
  #
  # Extensions are optional. If your source file is ".js", it
  # assumes you are requiring another ".js".
  #
  #     //= require "foo"
  #
  # Relative paths work too. Use a leading `./` to denote a relative
  # path:
  #
  #     //= require "./bar"
  #
  def process_require_directive(path)
    if @compat
      if path =~ /<([^>]+)>/
        path = $1
      else
        path = "./#{path}" unless relative?(path)
      end
    end

    context.require_asset(path)
  end

The comments instruct to use a leading "./" for relative paths. The code however prepends this "./" when the path is not relative. That seems to be why relative assets can be required even when the path is not defined as a relative path.
Apparently the jasmine-rails gem (https://github.com/searls/jasmine-rails) does not have this behavior and therefore cannot require the relative files.

Since this problem seems to be more related to the jasmine-rails gem, I decided to stop using it. Now everything works fine when compiling assets.


2: React.lazy load HyloEditorMobile for code-splitting to improve load time in HyloApp

Remaining tasks:

[x] Remove store/dispatch dependency from mention and topic suggestions queries (this mobile editor bundle will not include the store). See notes to this regard in the related HyloApp ticket

Benefits:

Reduces the size of hyloApp/editor / HyloEditorMobile load in HyloApp from ~2 MB to ~600k, which made a palpable difference in testing. It would be more important of a difference in the case of a poor or slow mobile data connection.

Most likely we will also be creating a WebView for our ReactPlayer usage to get Video Emebeds working in the App. It will also want/need this top-level treatment: https://github.com/Hylozoic/HyloReactNative/issues/567

A good and likely necessary first step towards moving the Mobile Editor code locally into the native app, which is where we ultimately should be (ref. https://github.com/Hylozoic/HyloReactNative/issues/572)

Sets the stage for further lazy-loading / code-splitting down the line in the router.

Background:
We are currently using React.lazy and Suspense to delay load of the Notifications and Messages drop-downs and this extends that usage to the very top. Our previously somewhat woven-in SSR setup wouldn't have allowed us to use React.lazy in non-authed views (Suspense is not supported by React server rendering). The cleaned-up SSR setup in the branch this is based upon should remedy that such that App (which was clientRouter) now will only ever get rendered client-side.

so it this no longer a Draft?

It likely needs to have dev merged-up and make sure things are still happy, but yeah it should be good.


support --write-verification-metadata and --export-keys together

Expected Behavior
It would be nice if it were possible to run ./gradlew --write-verification-metadata --export-keys --dry-run ${someTask} and for that to generate both gradle/verification-metadata.dryrun.xml and gradle/verification-keyring-dryrun.keys together
Current Behavior
Currently if a user passes --write-verification-metadata and --export-keys as command-line arguments, and if gradle/verification-metadata.xml specifies <key-servers enabled="false"/> then it seems that Gradle doesn't export the keys
Context
When a I'm importing a new key for an artifact, I'd like to be able to do this as a single action. This would run more quickly and would also be simpler. Currently I think it's required to update the verification-metadata before the keyring, which I wasn't initially expecting.

Also related: it seems that it's necessary to run a fully clean build when regenerating the verification metadata (see https://github.com/gradle/gradle/issues/19228 ) which makes it more inconvenient to have to run more builds to update the metadata and keys.
I'm guessing that if https://github.com/gradle/gradle/issues/19228 were resolved then this issue would be less important

Also interesting, partially as a result of this issue, for the moment we have a script for regenerating both the verification metadata and the keys, and this script runs the two Gradle invocations serially: https://android.googlesource.com/platform/frameworks/support/+/a12813fdb62ffeb3dcfeae9604ade7f8d92e8afc/development/update-verification-metadata.sh#40

After re-testing with Gradle 7.5 this doesn't seem to be happening anymore
If it happens again I'll have to add more details - in the meanwhile I think it's resolved
Thanks!


Banners

Closes #354
Because of difference in HTML structure, this is the closest we can get it.. but I think it works well:

Also added a file variable.pcss for adjusting the global variables, but scoped to the editions css class.

@forsbergplustwo maybe it will make sense to have configuration setting on the back-end to turn on v12 styling? We could use it to tweak markup for v12 version a little bit. It seems like moving the icon from the left column to the top will be a biggest change required for banners.

@kirillplatonov - I'll give it a shot, but I think we have to be careful of going too far with these customizations 😅

Regarding a setting, would they not just be able to pin the gem to an earlier version if they really don't want the upgrade?

@forsbergplustwo If we're going to make new styles optional then we'll need to keep markup compatible with both v11 and v12 css. It's an extra work without real benefits. Thinking more about this it might be easier to just go with v2.0 release that will include only v12 styles. This way we could adjust markup without additional configuration. The only requirement would be to introduce new helper polaris_html_classes similar to existing polaris_html_styles. This helper could be used to add Polaris-Summer-Editions-2023 class to html tag automatically. What do you think?

@kirillplatonov - Sounds great! I think dropping backwards compatability will allow us to get the final parts really nice. It is a bit more complicated to adjust the markup too, but I think it's not too many components that need it.

@kirillplatonov - Do you want to review these before I merge to the 'polaris-v12' branch?
This turned out pretty good in the end, and match up nicely:

(Our withinContainer has slightly more padding than Shopify's, but it's a pain to change)


Parse error when output.xml contains latin characters

It seems that the code is not encoding free (Given #41)
table_td.string = str(kw.kwname)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe0' in position 36: ordinal not in range(128)

On solution may be to sanitise the xml input to make robotframework-metrics error free. It is frustrating that the script does not go throught for 1 unrecognised character. However it would not matter if that character was replace by ?.
u.encode('ascii', 'replace')

@xNok In recent change I have modified robotmetrics to use uft-8 decode, could you please try reported issue with latest change
Change - https://github.com/adiralashiva8/robotframework-metrics/blob/a4c0c60bd2d2e40c1b4f33f67cb13f2d7c441436/setup.py#L4
For latest (master) changes installation use pip install git+https://github.com/adiralashiva8/robotframework-metrics

This is solved as of v3.1.4, Howerver v3.1.4 as not been release to pypi so impossible to get it from pip install

Use following command to install latest changes until new release!
pip install git+https://github.com/adiralashiva8/robotframework-metrics


Suggestion: search bar for "Favorites" category

First of all, love the extension. Thanks for your work.
Is there any possibility you'll be adding search function for the "Favorites" category? It would save a lot of scrolling and searching,

Thank you so much for it, I appreciate it!!
Adding the search function can be done but there's an issue with it, so when you open the extension, it loads 50 followed streams that are live, the search function would only be able to search on those 50 and not all your followed because Twitch API doesn't allow it. If you have more than 50 and you scroll to the bottom it would load 50 more and so on.
Basically, the search would only be able to filter streams that are already loaded on the extension. Do you think that's something useful despite this issue?

Oh, I thought you had access to all live channels at once. I still think it could be useful, but I see the issue it might bring, mainly confusion. Personally, I never have more than 50 channels live at the same time, but this could be a problem for someone else.
I have an idea, but I don't know the technical limitations. Here is the idea for an algorithm:

Search through the 50 live channels.
If there is a match, display it.
If there is no match, load 50 more channels and try again (repeat until there are no more live channels to load).

This idea might not be feasible, but it would be great if it could work. The last extension I used before yours had a search bar, so it never occurred to me that it could be more complicated than that. However, they might have changed how the API works since then.

Yeah, loading all the followed streams in memory might cause memory issues for users that follow a lot of people, that's why I have it 50 at each time.
The older extensions used a now deprecated Twitch Api that I can no longer use and that limited everyone. I think I can try another way but for it to work, as you're my sample on this let me know :D If you input the exact twitch username, I think I can check if you follow it and if it's live, who it be something useful? It has to be the exact one, if you input just part of it, I think I won't be able to get it

Alright, got it. Using the exact username is probably not the best way to go, since I usually don't remember every character in their name, and I suppose many other people don't either. So, let's just leave it as it is. Thanks for the explanation and effort. The extension might be easier to use without the exact-match search bar. If you agree, I think we can close the thread. Cheers!

I asked around on Twitch API discord and it might be "possible" using multiple calls to their API. Basically use this to get streams by input (doesn't need to be exact just like in the search bar) and then check if from the list of results which ones you follow using this endpoint. My main concern is performance but it's something that I can evaluate while coding too. So on the Favorites, you'd be able to search by name the Live and Followed streams. Would this fit your use case?

This feature is now live as I just pushed a new version with it. Let me know if you find any issues

Aw man I forgot to answer last time, sorry about that. I just downloaded the update and it seems to be working like a charm! Exactly what I had in mind. You're the man, thank you so much. I'll let you know if something breaks in the future, but I don't see any issues right this time.

No worries!! I'll keep this open for a couple of days, if you find anything just let me know. I tested with my own account and everything seemed fine but I may have way fewer follows than the average twitch user

I took the time to follow some streamers, so I now have more than 50 streams live at once (52 to be exact), and everything worked smoothly. The search function worked as expected, so it seems that all is good to go.
I have one suggestion that might make the extension more user-friendly for lazy people like myself: could the search bar be active as soon as the extension loads, so users don't have to click into it themselves? This is just a small suggestion, so don't worry if it doesn't make sense to implement. I thought that since scrolling works even when the search bar is active, it might make the search process faster for those who use it, without bothering anyone else who doesn't use the search bar.

That's good news, thank you!!
I can have a look at it and see how to implement it, I don't think it should be that complicated, if it isn't, I don't mind adding it, that's something that didn't cross my mind. but nice catch

I was a super easy change, just pushed it, during today, you should see it working, let me know if there's any issue!


[FEATURE] improve transparency on throttling parameters

I tried using this package and I am a bit confused about these parameters which I find in the source code:
  concurrency: 1,
  throttleInterval: 1,
  intervalCap: 5,
  concurrencyInterval: 5000

From the tests I run I see that run is somehow throttled by default.
Practically I want to dump/import as fast as possible, no throttling no nothing.
Can you guide me a bit here?

Those properties have been disabled and no longer supported
On Thu, 10 Nov 2022 at 12:11 PM, klodoma @.***> wrote:

I tried using this package and I am a bit confused about these parameters
which I find in the source code:
concurrency: 1,
throttleInterval: 1,
intervalCap: 5,
concurrencyInterval: 5000
From the tests I run I see that run is somehow throttled by default.
Practically I want to dump/import as fast as possible, no throttling no
nothing.
Can you guide me a bit here?
—
Reply to this email directly, view it on GitHub
https://github.com/elasticsearch-dump/elasticsearch-dump/issues/937, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABHAFC62CSODS3ECHKPHXTWHUNBLANCNFSM6AAAAAAR4XDWXY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
"Give me a place to stand on, and I will move the Earth."
Ferron Hanse

Those properties have been disabled and are no longer supported

Can you maybe help me with this?
Practically I want to dump/import as fast as possible, no throttling no nothing.
I have throttling when exporting things.


接收不到数据怎么解决

type=1400 audit(0.0:2416): avc: denied { read } for name="ttyS5" dev="tmpfs" ino=10395 scontext=u:r:untrusted_app:s0:c120,c256,c512,c768 tcontext=u:object_r:serial_device:s0 tclass=chr_file permissive=1 app=com.ex.serialport
2023-04-13 17:19:50.217 m.ex....port                    I  type=1400 audit(0.0:2417): avc: denied { write } for name="ttyS5" dev="tmpfs" ino=10395 scontext=u:r:untrusted_app:s0:c120,c256,c512,c768 tcontext=u:object_r:serial_device:s0 tclass=chr_file permissive=1 app=com.ex.serialport
2023-04-13 17:19:50.220 Thread-6                        I  type=1400 audit(0.0:2420): avc: denied { getattr } for path="/dev/ttyS5" dev="tmpfs" ino=10395 scontext=u:r:untrusted_app:s0:c120,c256,c512,c768 tcontext=u:object_r:serial_device:s0 tclass=chr_file permissive=1 app=com.ex.serialport
请教一下，接收不到数据，是上面的错误引起的吗？安卓端能解决吗

It's depends of SELinux restrictions. You cannot do so much to avoid it.
In easy words: it means that there is "someone" that has tried to "{read}" something but SELinux stops it because that App wasn't found in the "trusted" list of SELinux. Usually some specific and dangerous locations of the System are restricted from installed Apps, so SELinux stops to read/wrote/execute things in/from that locations.
The given SELinux violation:
type=1400 audit(0.0:2416): avc: denied { read } for name="ttyS5" dev="tmpfs" ino=10395 scontext=u:r:untrusted_app:s0:c120,c256,c512,c768 tcontext=u:object_r:serial_device:s0 tclass=chr_file permissive=1 app=com.ex.serialport

Below I'll try to give explanation of important parts of above violation:
denied { read } : Operation Permission State : The denied permission that was requested / executed. In this case, it is a read operation. SELinux denying permission to execute read dir/file operation.
name="ttyS5": Target name : The name of the target (in this case, the file/dir name) which your application, probably, trying to read.
scontext=u:r:untrusted_app:s0 : Source Context : The Source Context for this security violation. This indicates which domain/process is trying to execute read functionality. Here, untrusted_app applications are those which are launched by zygote
tcontext=u:object_r:serial_device:s0 : Target Context : The security context of the target resource (in this case the file). Here, the source tried to read file in serial_device file system which has been denied.
tclass=chr_file : Target Class : The class of the target.
In one sentence, SELinux denied the permission to untrusted_app to read the ttyS5 file in serial_device.
From Google source, check SEPolicy file untrusted_app.te how the permission has been denied.
To avoid it you should rebuild the ROM after changed specific files about SELinux where you have to add your App in the "trusted zone".
You can install a different Kernel with a different SELinux settings.


netty is adding content-length=0 header in 204 response

Expected behavior
A server MUST NOT send a Content-Length header field in any response
with a status code of 1xx (Informational) or 204 (No Content).  A
server MUST NOT send a Content-Length header field in any 2xx
(Successful) response to a CONNECT request
Actual behavior
netty is adding content-length=0 header in 204 response
Steps to reproduce
Run a http request/response with response code 204.
Minimal yet complete reproducer code (or URL to code)
    @Override
    @RequestMapping("/**")
    public ResponseEntity<?> handleReq(RequestEntity<byte[]> reqEntity,
                    @RequestHeader HttpHeaders reqHeaders) {
            HttpHeaders responseHeaderMap = new HttpHeaders();
            responseHeaderMap.set("abc11", "xyz11");
            responseHeaderMap.set("abc12", "xyz12");
            responseHeaderMap.set("abc13", "xyz13");
            responseHeaderMap.set("abc14", "xyz14");

            return (new ResponseEntity<byte[]>(responseHeaderMap, HttpStatus.NO_CONTENT));
    }

Netty version
4.1.82
JVM version (e.g. java -version)
jdk:17.0.5
OS version (e.g. uname -a)
Linux 4.14.35-1818.3.3.el7uek.x86_64

Is Netty doing that or Spring?

any chance this is related to #12760 ?

Any chance this is related to https://github.com/netty/netty/pull/12921?

Sorry but we need more info here. I suspect its spring that is doing this as need does not add this kind of headers automatically.


Add clickable external link icon for referral urls

Just a small utility/improvement that makes it easier to visit referring URLs.

I think I want to play with the appearance a bit before landing.


Removing 'id' field from Typegoose

Would it be possible to remove the id field from the Typegoose class?
My documents have their own id field which are numbers instead of strings, so TypeScript gives me an error telling me that I haven't extended the Typegoose class properly. However, removing the id field from the Typegoose typings allows it to compile and work just fine.
If having the id field is necessary in some way, maybe consider renaming it to _id since id does not necessarily seem to be reserved in MongoDB.

Hello, yes currently id is forced into the model with ObjectID. I'm planning to extend this with customization.


HDDS-9381. Remove @Flaky annotations from now-stable test cases.

What changes were proposed in this pull request?
Remove the @Flaky annotations from the test cases that have been successfully fixed and are no longer experiencing flakiness.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9381
How was this patch tested?
I ran the Test class 300 times for each test class and ensured that there were no intermittent failures.

Class Name
CI Runs

TestSCMContainerPlacementPolicyMetrics HDDS-2961
https://github.com/ArafatKhan2198/ozone/actions/runs/6398416895 https://github.com/ArafatKhan2198/ozone/actions/runs/6398418026 https://github.com/ArafatKhan2198/ozone/actions/runs/6398419702

TestOzoneManagerHAMetadataOnly HDDS-6644
https://github.com/ArafatKhan2198/ozone/actions/runs/6235727447 https://github.com/ArafatKhan2198/ozone/actions/runs/6235729232

TestOzoneManagerHAMetadataOnly HDDS-6642
https://github.com/ArafatKhan2198/ozone/actions/runs/6235727447 https://github.com/ArafatKhan2198/ozone/actions/runs/6235729232

TestBlockOutputStreamWithFailures HDDS-1967
https://github.com/ArafatKhan2198/ozone/actions/runs/6398347226 https://github.com/ArafatKhan2198/ozone/actions/runs/6398357035 https://github.com/ArafatKhan2198/ozone/actions/runs/6398360165

TestCloseContainerByPipeline HDDS-3263
https://github.com/ArafatKhan2198/ozone/actions/runs/6377459304 https://github.com/ArafatKhan2198/ozone/actions/runs/6377460878 https://github.com/ArafatKhan2198/ozone/actions/runs/6377461812

TestRandomKeyGenerator HDDS-5993
https://github.com/ArafatKhan2198/ozone/actions/runs/6025312941 https://github.com/ArafatKhan2198/ozone/actions/runs/6028746303 https://github.com/ArafatKhan2198/ozone/actions/runs/6028751338

TestRecursiveAclWithFSO HDDS-8092
https://github.com/ArafatKhan2198/ozone/actions/runs/6402939616 https://github.com/ArafatKhan2198/ozone/actions/runs/6402940691 https://github.com/ArafatKhan2198/ozone/actions/runs/6402942430

TestOzoneFileSystem HDDS-6645
https://github.com/ArafatKhan2198/ozone/actions/runs/6403238608 https://github.com/ArafatKhan2198/ozone/actions/runs/6403241618 https://github.com/ArafatKhan2198/ozone/actions/runs/6403245347

Thanks @ArafatKhan2198 for working on this.  Please link the repeated runs for each test class in this PR.

Thanks @ArafatKhan2198 for working on this. Please link the repeated runs for each test class in this PR.

Just finalising the list, will post it shortly.

These aren't passing, or Am I checking it wrong?
TestOzoneFileSystem

@ayushtkn You are right, TestOzoneFileSystem has failures.  Note that:

failure in testListStatusOnKeyNameContainDelimiter is being fixed in #5093, and does not have @Flaky annotation
failure in testTrash was already fixed and @Flaky annotation was removed  in #5330, but the repeated run's code preceded that change
@Flaky does not even work for TestOzoneFileSystem since it's a JUnit4-based test class

So basically the part of this PR related to TestOzoneFileSystem can be ignored, the same change is already on master.

@adoroszlai I have updated the list for the final time, I believe we should merge it !!

Thanks @ArafatKhan2198 for testing these and the patch, @ayushtkn for the review.


NEST 6.X - Nested path/filter in sort

NEST/Elasticsearch.Net version:
6.0
Elasticsearch version:
6.1.3
Description of the problem including expected versus actual behavior:
Hello, I'm trying to write in c# using Nest 6.0 version code provided here: https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-sort.html
POST /_search
{
   "query" : {
      "term" : { "product" : "chocolate" }
   },
   "sort" : [
       {
          "offer.price" : {
             "mode" :  "avg",
             "order" : "asc",
             "nested": {
                "path": "offer",
                "filter": {
                   "term" : { "offer.color" : "blue" }
                }
             }
          }
       }
    ]
}

How can write this nested object in c#?
The only thing that I found in the library for the SortDescriptor object is NestedPath() and NestedFilter(), unfortunatelly both of them are deprecated:

#! Deprecation: [nested_path] has been deprecated in favor of the [nested] parameter
#! Deprecation: [nested_filter] has been deprecated in favour for the [nested] parameter

Hey @vicariouskp,
GitHub issues are reserved for bugs and feature requests. The best place to ask this question would be over at https://discuss.elastic.co/c/elasticsearch. Not only will it gain more attention there, the answers may help out other users in the future, and the forum will be an easier place for others to find similar questions that have been asked before.
Thanks!


DPL-042 | Research: Understand changes required to move 'fit to pick logic' from core informatics to GSU [Heron]

Description
DPL-042 | Research: Understand changes required to move 'fit to pick logic' from core informatics to GSU
Who the primary contacts are for this work
Callum S (GSU)
Rhys (GSU)
Rich L
End point

Allow PAM (via API) to direct which samples to pick on Beckmans or Biosero Hamiltons

Assumptions

Pick set as a boolean value on PSG (The details of why should be picked are not know to PSD services, it maybe the case that positive samples will not be picked as there are other positives to pick that have a high scientific value to sequence)
In first iteration its understood plates that have samples that must be picked will still be preferentially selected by operation using Box buster.

Context
Overview of existing service here: https://lucid.app/lucidchart/invitations/accept/inv_798c58a7-ba85-4bfc-af26-fe287e763688

Resolved as part of GSU handover work.
Deprecated by the Product Owner.


Implement LM Eval Harness call in pretrain_score.py

Potential duplicate of https://github.com/mukobi/Unadaptable-Foundation-Models/issues/7
From Apr 3rd Meeting notes:

Implement LM Eval Harness calling code in pretrain_score.py that gets waits for completion and gets the numbers in Python

wandb script from
https://github.com/EleutherAI/lm-evaluation-harness/blob/main/examples/visualize-wandb.ipynb
Eval tasks from https://huggingface.co/spaces/HuggingFaceH4/open_llm_leaderboard

For now, can just test a single eval like MMLU


Implement UpdateUser transaction type

Used by Hotline client > 1.5 to edit multiple accounts in single transaction.

Implemented in v0.4.0


Remove  *Rec/*V/*Ex/*Pro postfix for draw overloads?

They have no point to exist in nim and remembering them can be hard. Would make the library easier to use but deviate from the original. Opinions?
Ex is supposed to mean extended parameters
Pro pro parameters? Actually means rotation, but it's not Ro?
V Vector2
Rec Rectangle

drawRectangleGradientV and drawRectangleGradientH have completely different meaning and should be left alone.

Functions that return Vector2 or Rectangle should be left alone.

getGestureDragVector, getGesturePinchVector, measureTextEx are inconsistent with the naming of the rest.


Support alternate S3 endpoint and credentials

Add support for secondary S3 credentials. This will enable cases where the data source and catalog are not co-located. S3 buckets may have different credentials.

@g-saransh, thank you for submitting the issue!
Would you like to contribute to implement the feature?
We can keep the conversation going about the implementation details here.


make oss migrations run as part of dev-dracon

This PR introduces two new ways of installing dracon
make dev-deploy will build everything and deploy it to the local cluster
 make install will download the latest version of every package and install it to the local cluster
both commands first setup the local cluster in an idempotent way

the commits on this PR all modify the Makefile in different ways.
I know this is a hard PR to review so I've added comments to make it easier, I can merge the makefile mods to one commit but it's a lot of small independend changes


Package is not supported (package is missing install action)

I’ve created an SSM automation deployment successfully using option B in the README. The execution works until the last step which is the installation task. Im testing with two instance types: Amazonlinux2 and Windows 2019 server. Both deployed as EC2 instances using AWS’s AMI’s. SSM was confirmed functional on both as well. The Linux instance works flawlessly, while the windows part fails with:
Package is not supported (package is missing install action)
Things I have tried so far:
Repackaging the installer using the packager.py with the various versions I’ve found in this repo for the windows install.ps1/uninstall.ps1 scripts.
Downloaded the files I have uploaded to S3 and confirmed their checksum matched the included manifest.json.
I’m at a loss at this point as to why its failing to find the package while the Linux install in the same document works.

For the people who may come across this issue:
We are revamping and cleaning up this repository. As part of that effort our ssm examples have been move to aws-ssm-distributor
These new examples resolve the issues currently present in the systems-manager folder.


RegisterAddresses_IPv4_Success fails on OSX

Failed   RegisterAddresses_IPv4_Success(addressInput: "http://Davids-MacBook-Pro-3.local:0/", testUrls: Func`2 { Method = System.String[] GetTestUrls(Microsoft.AspNetCore.Hosting.Server.Features.IServerAddressesFeature), Target = null })
Error Message:
 System.Net.Sockets.SocketException : Device not configured

/cc @halter73

No stack trace? Does this fail consistently?

Every time
[xUnit.net 00:00:55.7797780]     RegisterAddresses_IPv4_Success(addressInput: "http://Davids-MacBook-Pro-3.local:0/", testUrls: Func`2 { Method = System.String[] GetTestUrls(Microsoft.AspNetCore.Hosting.Server.Features.IServerAddressesFeature), Target = null }) [FAIL]
[xUnit.net 00:00:55.7866230]       System.Net.Sockets.SocketException : Device not configured
[xUnit.net 00:00:55.7881750]       Stack Trace:
[xUnit.net 00:00:55.7956470]         /Users/dfowler/dev/Universe/KestrelHttpServer/test/shared/HttpClientSlim.cs(124,0): at Microsoft.AspNetCore.Testing.HttpClientSlim.<GetSocket>d__7.MoveNext()
[xUnit.net 00:00:55.7958040]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:55.7958910]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:55.7959780]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[xUnit.net 00:00:55.7960440]            at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
[xUnit.net 00:00:55.7961190]         /Users/dfowler/dev/Universe/KestrelHttpServer/test/shared/HttpClientSlim.cs(85,0): at Microsoft.AspNetCore.Testing.HttpClientSlim.<GetStream>d__6.MoveNext()
[xUnit.net 00:00:55.7962070]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:55.7962800]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:55.7963290]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[xUnit.net 00:00:55.7963760]            at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
[xUnit.net 00:00:55.7964320]         /Users/dfowler/dev/Universe/KestrelHttpServer/test/shared/HttpClientSlim.cs(24,0): at Microsoft.AspNetCore.Testing.HttpClientSlim.<GetStringAsync>d__1.MoveNext()
[xUnit.net 00:00:55.7964770]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:55.7965370]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:55.7966080]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[xUnit.net 00:00:55.7966540]            at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
[xUnit.net 00:00:55.7967140]         /Users/dfowler/dev/Universe/KestrelHttpServer/test/Microsoft.AspNetCore.Server.Kestrel.FunctionalTests/AddressRegistrationTests.cs(94,0): at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.AddressRegistrationTests.<RegisterAddresses_Success>d__7.MoveNext()
[xUnit.net 00:00:55.7967820]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:55.7968630]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:55.7969400]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[xUnit.net 00:00:55.7970150]         /Users/dfowler/dev/Universe/KestrelHttpServer/test/Microsoft.AspNetCore.Server.Kestrel.FunctionalTests/AddressRegistrationTests.cs(33,0): at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.AddressRegistrationTests.<RegisterAddresses_IPv4_Success>d__0.MoveNext()
[xUnit.net 00:00:55.7970850]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:55.7971540]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:55.7972070]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[xUnit.net 00:00:55.7972490]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:55.7972960]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:55.7973410]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[xUnit.net 00:00:55.7974090]         --- End of stack trace from previous location where exception was thrown ---
[xUnit.net 00:00:55.7974570]            at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[xUnit.net 00:00:55.7975060]            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
Failed   RegisterAddresses_IPv4_Success(addressInput: "http://Davids-MacBook-Pro-3.local:0/", testUrls: Func`2 { Method = System.String[] GetTestUrls(Microsoft.AspNetCore.Hosting.Server.Features.IServerAddressesFeature), Target = null })
Error Message:
 System.Net.Sockets.SocketException : Device not configured
Stack Trace:
   at Microsoft.AspNetCore.Testing.HttpClientSlim.<GetSocket>d__7.MoveNext() in /Users/dfowler/dev/Universe/KestrelHttpServer/test/shared/HttpClientSlim.cs:line 124
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.AspNetCore.Testing.HttpClientSlim.<GetStream>d__6.MoveNext() in /Users/dfowler/dev/Universe/KestrelHttpServer/test/shared/HttpClientSlim.cs:line 85
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.AspNetCore.Testing.HttpClientSlim.<GetStringAsync>d__1.MoveNext() in /Users/dfowler/dev/Universe/KestrelHttpServer/test/shared/HttpClientSlim.cs:line 24
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.AddressRegistrationTests.<RegisterAddresses_Success>d__7.MoveNext() in /Users/dfowler/dev/Universe/KestrelHttpServer/test/Microsoft.AspNetCore.Server.Kestrel.FunctionalTests/AddressRegistrationTests.cs:line 94
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.AddressRegistrationTests.<RegisterAddresses_IPv4_Success>d__0.MoveNext() in /Users/dfowler/dev/Universe/KestrelHttpServer/test/Microsoft.AspNetCore.Server.Kestrel.FunctionalTests/AddressRegistrationTests.cs:line 33
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

That's a pretty weird "IP address" to start with 😝

No repro


Browserify doesn't build under Windows

When commands are prefaced with a runner to resolve #94, we get here:

Not actually going to fix it; instead going to replace it with #83

It seems that node under Windows gets in f glob pattern browser/*, and under Linux that pattern is expanded by the shell.


Coordinator can return partial results after the timeout when allow_partial_search_results is true

Description
In query phase, the coordinate concurrently search each shard, If any shard is blocked or responds very slowly, the coordination node will be stuck even if the timeout is set.
The pr supports timeout waiting, if the timeout is exceeded, the coordinator considers the shard as failed and gos on the fetch phase.
Related Issues
Resolves https://github.com/opensearch-project/OpenSearch/issues/817#issuecomment-2039383610

Check List

[x] Functionality includes testing.
[x] API changes companion pull request created, if applicable.
[x] Public documentation issue/PR created, if applicable.

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

❌ Gradle check result for b6802ae: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

org.opensearch.search.basic.SearchWithRandomExceptionsIT.testRandomExceptions #15828