Unable to load System.Data.SqlClient, Version <IP_ADDRESS>

Steps to reproduce
Call a custom Cmdlet, which uses the current version 2.0.2 of Entity Framework Core, which uses the current version 4.4.3 of System.Data.SqlClient, which has the actual assembly version <IP_ADDRESS>.
> [System.AppDomain]::CurrentDomain.GetAssemblies() |? { $_.Location -match "SqlClient" }
> Get-Geburtstagsliste
Get-Geburtstagsliste : Could not load file or assembly 'System.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. Could not find or load a specific file. (Exception from HRESULT: 0x80131621)
At line:1 char:1
+ Get-Geburtstagsliste
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Get-Geburtstagsliste], FileLoadException
+ FullyQualifiedErrorId : noe.dotnuts2.Jobs.Commands.GetGeburtstagsliste

> [System.AppDomain]::CurrentDomain.GetAssemblies() |? { $_.Location -match "SqlClient" }

GAC    Version        Location
---    -------        --------
False  v4.0.30319     C:\Program Files\PowerShell\6.0.2\System.Data.SqlClient.dll

The then loaded assembly has the version <IP_ADDRESS>, which matches the version 4.4.2 of System.Data.SqlClient, but is older / not compatible with the desired version 4.4.3.
Shouldn't include an update to .NET Core version 2.0.6 as described for PowerShell Core 6.0.2 also include an update for stuff like 'System.Data.SqlClient'?
Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.0.2
PSEdition                      Core
GitCommitId                    v6.0.2
OS                             Microsoft Windows 10.0.16299
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

6.0.2 is only a security update.

Any idea how to load the "correct" version of System.Data.SqlClient?

After opening PWSH:
No load required:
$getSqlSvr = "mars";
$sqlcon = "server=$getSqlSvr;database=Master;Integrated Security=false;User ID=sa;" + 'Password=$SaPasswd1!';

## - SQL Query:
$SqlQry = @'
sp_who2
'@;

## - Create connection to SQL Server and execute the T-SQL command:
$sda = New-Object System.Data.SqlClient.SqlDataAdapter ($SqlQry, $sqlcon);
$sdt = New-Object System.Data.DataTable;
$sda.fill($sdt) | Out-Null;

PS [20] > $sdt.rows | Select-Object -first 10 | Format-Table;

SPID  Status                         Login HostName BlkBy DBName Command          CPUTime DiskIO LastBatch
----  ------                         ----- -------- ----- ------ -------          ------- ------ ---------
1     BACKGROUND                     sa      .        .          XTP_CKPT_AGENT   0       0      03/19 12:39:25
2     BACKGROUND                     sa      .        .          LOG WRITER       0       0      03/19 12:39:25
3     BACKGROUND                     sa      .        .          RECOVERY WRITER  0       0      03/19 12:39:25
4     BACKGROUND                     sa      .        .          LAZY WRITER      0       0      03/19 12:39:25
5     BACKGROUND                     sa      .        .          LOCK MONITOR     0       0      03/19 12:39:25
6     BACKGROUND                     sa      .        .   master SIGNAL HANDLER   0       0      03/19 12:39:25
7     BACKGROUND                     sa      .        .          XIO_RETRY_WORKER 0       0      03/19 12:39:25
8     BACKGROUND                     sa      .        .          XIO_LEASE_RENEWA 0       0      03/19 12:39:25
9     BACKGROUND                     sa      .        .   master BRKR TASK        0       0      03/19 12:39:31
12    BACKGROUND                     sa      .        .          RESOURCE MONITOR 0       0      03/19 12:39:25

Works perfectly!!

Using it directly isn’t the same as using it as a dependency (of another dependency), when it’s referenced using a higher (!) assembly version.
The problem is, that the current PowerShell version, which is build on the current .NET Core version, comes with an older (?) SqlClient version. And that does not work, if a Cmdlet has a dependency, which uses the current Entity Framework, which uses the current (!) SqlClient.

Let me check on my setup and see what I get then.
:)

@axelheer Did you find any workaround? I have the same issue.

@axelheer did the release of new SDK version change anything?
https://github.com/PowerShell/PowerShell/issues/6475

Hi there!
You may want to try either the latest 6.0.4 GA  and/or Preview-4.
Both work as expected!
:)

@mi-hol I don't compile against the full SDK, only the PowerShell Standard

I experienced a similar problem on PowerShell 6.1.1 when loading System.Data.SqlClient, however it appears to be resolved under PowerShell 6.2.0-preview.3
PowerShell 6.1.1
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS C:\Program Files\PowerShell\6> Add-Type -Path F:\Temp\System.Data.SqlClient.dll
Add-Type : Could not load file or assembly 'System.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
At line:1 char:1
+ Add-Type -Path F:\Temp\System.Data.SqlClient.dll
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Add-Type], FileLoadException
+ FullyQualifiedErrorId : System.IO.FileLoadException,Microsoft.PowerShell.Commands.AddTypeCommand
PS C:\Program Files\PowerShell\6-preview>

PowerShell 6.2.0-preview.3
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

PS C:\Program Files\PowerShell\6-preview> Add-Type -Path F:\Temp\System.Data.SqlClient.dll
PS C:\Program Files\PowerShell\6-preview>

Further usage allows me to run Entity Framework Core. Loading Newtonsoft.Json.dll also works under the preview version.

@brent-robinson
Hum! Something is missing in your sample.
First, System.Data.SqlClient.dll is included in the PowerShell 6.1.1 folder, and it's working fine.
So, I'm dare to assuming that you installed another version of the DLL. Right!
If that's the case then... maybe... that DLL on the F: drive wasn't build to work with 6.1.1 .NET Core Version(??)
Any way, look at the https://github.com/PowerShell/PowerShell/releases where is states that on the PowerShell Core v6.2.0-preview.3 - "Bump System.Data.SqlClient from 4.5.1 to 4.6.0".
Loading the DLL from either of the PowerShell Core 6.1.1 and 6.2.0 location works!

I'm curious! How and from where you install the System.Data.SqlClient.dll on your F: drive?

This assembly is shipped with PSCore6 and that version should be used.  Older .NET Framework based ones are not compatible.


MangoPay.configuration is now a thread-local variable

Thanks very much for this @TristeFigure - looks like the Travis tests are failing though - are the tests passing when run in local?

They weren't, as I forgot to reset the config at the end of the new tests. It should be ok now.

Great stuff, thank you very much!


Password Complexity and Reuse

The first time you use the auth service you are asked to change password. There are no password complexity rules enforced. You can reuse the same password.

I've added checks but they're provisional until I can confirm the requirements:

Cannot re-use previous password. Does not check against all previous passwords. If this is policy then it will require a database change.
Configurable complexity, using a regex.
Configurable minimum password length. A regex can do this, obviously. Except length is a salient requirement and if there aren't any other complexity requirements it avoids a regex. Possibly we'll always need complexity requirements, and if we do I'll consider scraping the length option.

I'll leave this open until the requirements are confirmed. NB: NCSC guidance says "enforcing the requirement for complex character sets in passwords is not recommended".


wgpu: Use write_buffer_with rather than write_buffer

This can be a performance improvement due to reduced data copying.
From the updated (post 0.20) docs:
    /// Write to a buffer via a directly mapped staging buffer.
    ///
    /// Return a [`QueueWriteBufferView`] which, when dropped, schedules a copy
    /// of its contents into `buffer` at `offset`. The returned view
    /// dereferences to a `size`-byte long `&mut [u8]`, in which you should
    /// store the data you would like written to `buffer`.
    ///
    /// This method may perform transfers faster than [`Queue::write_buffer`],
    /// because the returned [`QueueWriteBufferView`] is actually the staging
    /// buffer for the write, mapped into the caller's address space. Writing
    /// your data directly into this staging buffer avoids the temporary
    /// CPU-side buffer needed by `write_buffer`.
    ///
    /// Reading from the returned view is slow, and will not yield the current
    /// contents of `buffer`.
    ///
    /// Note that dropping the [`QueueWriteBufferView`] does *not* submit the
    /// transfer to the GPU immediately. The transfer begins only on the next
    /// call to [`Queue::submit`] after the view is dropped. To get a set of
    /// scheduled transfers started immediately, it's fine to call `submit` with
    /// no command buffers at all:

(This is partly a reminder to myself. I planned to do this and keep forgetting.)

Not sure if this actually an improvement, need to ask upstream.


Add 'name' field to webhook application context

This will always be factotum for now

Was this post-linter too?


Add crypto_sign and crypto_sign_open to Signature

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Tyler Perkins seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


NVMe Device Configuration

Receiving ERROR: Partition specification unsupported at this time. when attempting to run docker-storage-setup with nvme device. This is due to a bug with the device configuration validation routine believing that I've chosen a partition rather than a device.
Configuration:
DEVS=/dev/nvme0n1
VG=docker

Workaround:
Create docker volume group manually and remove DEVS line.

Create docker volume group manually and remove DEVS line.

I think this could be called "best practice" instead of "workaround", actually. :-)

@shishir-a412ed is cleaning up @mvollmer patch to remove hard coded assumptions about partition name being '${dev}1'. Once that patch gets merged, this problem should be solved.

Related (but possibly distinct) c-s-s fails to GROWPART=true with Fedora Atomic Host 28 in AWS on NVME (defaults).
# rpm -q container-storage-setup
container-storage-setup-0.10.0-1.gitdf0dcd5.fc28.noarch
# rpm-ostree status
State: idle; auto updates disabled
Deployments:
● ostree://fedora-atomic:fedora/28/x86_64/atomic-host
                   Version: 28.20180613.0 (2018-06-13 13:52:10)
                    Commit: c51100f14cf12b25c16562cede7455191e536c0534e3b2ef87e66be9e12899ae
              GPGSignature: Valid signature by 128CF232A9371991C8A65695E08E7E629DB62FB1
# cat /etc/sysconfig/docker-storage-setup
...
GROWPART=true
ROOT_SIZE=+100%FREE
# lsblk
NAME              MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1           259:0    0  42G  0 disk
├─nvme0n1p1       259:1    0   1G  0 part /boot
└─nvme0n1p2       259:2    0   5G  0 part
  └─atomicos-root 253:0    0   5G  0 lvm  /sysroot
# journalctl -b -r -u docker-storage-setup
-- Logs begin at Tue 2018-06-26 01:39:40 UTC, end at Tue 2018-06-26 01:49:03 UTC. --
Jun 26 01:41:38 ip-172-18-3-8 systemd[1]: Started Docker Storage Setup.
Jun 26 01:41:38 ip-172-18-3-8 container-storage-setup[1013]:   Logical volume atomicos/root successfully resized.
Jun 26 01:41:38 ip-172-18-3-8 container-storage-setup[1013]:   Size of logical volume atomicos/root unchanged from <5.00 GiB (1279 extents).
Jun 26 01:41:38 ip-172-18-3-8 container-storage-setup[1013]:   1 physical volume(s) resized / 0 physical volume(s) not resized
Jun 26 01:41:38 ip-172-18-3-8 container-storage-setup[1013]:   Physical volume "/dev/nvme0n1p2" changed
Jun 26 01:41:38 ip-172-18-3-8 container-storage-setup[1013]: FAILED: /dev/nvme: does not exist
#

So it's definitely
    # Split device & partition.  Ick.
    growpart $( echo $pv | sed -r 's/([^0-9]*)([0-9]+)/\1 \2/' ) || true

And yeah the comment.  Ick.  We can use sysfs for this, something like $(basename $(dirname $(readlink /sys/dev/block/$major:$minor))).


Fixes for RTools 3.5

Summary
Current develop fails with RTools 3.5 tests. This PR fixes that by removing the use of some C++ features only available with compilers that have full C++14 support.
Also splits one failing test in two (the test was too big for RTools 3.5).
No release notes as this is just fixing develop.
Tests
/
Side Effects
/
Release notes
Checklist

[x] Math issue N/A

[ ] Copyright holder: Tadej Ciglarič, Rok Češnovar
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

@syclik this is blocking the https://github.com/stan-dev/cmdstan/pull/924 cmdstan PR (we test that models compile with RTools 3.5 in cmdstan as well).

Ready for review.

I can’t see the diff on my phone. I’ll check on it later.
On Sat, Aug 15, 2020 at 11:35 AM Rok Češnovar<EMAIL_ADDRESS>wrote:

Ready for review.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/pull/2016#issuecomment-674413009, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADH6F4C5HATSBY6WRBQ3JDSA2TNFANCNFSM4QAGLNDA
.

Oh it says there in the comments, cool.

Thanks, Ben and Rok!
On Mon, Aug 17, 2020 at 12:32 PM Ben Bales<EMAIL_ADDRESS>wrote:

Merged #2016 https://github.com/stan-dev/math/pull/2016 into develop.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/pull/2016#event-3662670295, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADH6F33N532TQJPG7OBHXDSBFLSRANCNFSM4QAGLNDA
.


3.30.0 - StartCopyFromUriAsync - 500 Error

Which service(blob, file, queue, table) does this issue concern?
blob
Which version of the Azurite was used?
3.30.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
docker
What's the Node.js version?
N/A
What problem was encountered?
Error Message:
   Azure.RequestFailedException : Service request failed.
Status: 500 (Internal Server Error)

Headers:
Server: Azurite-Blob/3.30.0
Date: Fri, 26 Apr 2024 10:04:24 GMT
Connection: keep-alive
Keep-Alive: REDACTED
Content-Length: 0

Stack Trace:
   at Azure.Storage.Blobs.BlobRestClient.StartCopyFromURLAsync(String copySource, Nullable`1 timeout, IDictionary`2 metadata, Nullable`1 tier, Nullable`1 rehydratePriority, Nullable`1 sourceIfModifiedSince, Nullable`1 sourceIfUnmodifiedSince, String sourceIfMatch, String sourceIfNoneMatch, String sourceIfTags, Nullable`1 ifModifiedSince, Nullable`1 ifUnmodifiedSince, String ifMatch, String ifNoneMatch, String ifTags, String leaseId, String blobTagsString, Nullable`1 sealBlob, Nullable`1 immutabilityPolicyExpiry, Nullable`1 immutabilityPolicyMode, Nullable`1 legalHold, CancellationToken cancellationToken)
   at Azure.Storage.Blobs.Specialized.BlobBaseClient.StartCopyFromUriInternal(Uri source, IDictionary`2 metadata, IDictionary`2 tags, Nullable`1 accessTier, BlobRequestConditions sourceConditions, BlobRequestConditions destinationConditions, Nullable`1 rehydratePriority, Nullable`1 sealBlob, BlobImmutabilityPolicy destinationImmutabilityPolicy, Nullable`1 legalHold, Boolean async, CancellationToken cancellationToken)
   at Azure.Storage.Blobs.Specialized.BlobBaseClient.StartCopyFromUriAsync(Uri source, BlobCopyFromUriOptions options, CancellationToken cancellationToken)

Steps to reproduce the issue?
Our test creates two containers, uploads an image to one container then tries to copy by url with sas token.
var blobService = new BlobServiceClient(connectionString);

var a = blobService.GetBlobContainerClient("container-a");
await a.CreateIfNotExistsAsync();

var b = blobService.GetBlobContainerClient("container-b");
await b.CreateIfNotExistsAsync();

var blob = a.GetBlobClient("Test1/Test2/Example.png");

const string base64Image = "iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAIAAAD8GO2jAAAARUlEQVR4nGJxk6tkIAUwFcSSpp4k1WSAUQtGLRi1YNSCUQuoAViqbmiTpOE2vwRJ6od+EI1aMGrBqAWjFowICwABAAD//8sqBHDcliZLAAAAAElFTkSuQmCC";
using (var ms = new MemoryStream(Convert.FromBase64String(base64Image)))
{
    await blob.UploadAsync(ms, new BlobHttpHeaders
    {
        ContentType = "image/png"
    });
}

var sasCredential = new StorageSharedKeyCredential("AccountNameFromConnectionString", "AccountKeyFromConnectionString");
var blockBlob = new BlockBlobClient(blob.Uri, sasCredential);

var policy = new BlobSasBuilder(BlobSasPermissions.Read, DateTimeOffset.UtcNow.AddMinutes(5))
{
    StartsOn = DateTimeOffset.UtcNow
};

var sasUri = blockBlob.GenerateSasUri(policy);

var bBlobClient = b.GetBlobClient("Test3/Example.png");
var blobProperties = await blockBlob.GetPropertiesAsync();

var options = new BlobCopyFromUriOptions
{
    DestinationConditions = new BlobRequestConditions { IfModifiedSince = null }
};
var copyOperation = await bBlobClient.StartCopyFromUriAsync(sasUri, options); // <--- Error here
await copyOperation.WaitForCompletionAsync();

Have you found a mitigation/solution?
Downgrade to 3.29.0

@AshleyMedway
I can't repro this problem with above code and Azurite docker image 3.30.0 on my local test machine.
Would you please share the Azurite debug log of the failed request for investigation?

I'm facing the same issue too. Below are the debug logs for this:
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: BlobStorageContextMiddleware: RequestMethod=PUT RequestURL=https://<IP_ADDRESS>/devstoreaccount1/240c8d06-19a5-42cc-bd9f-fa81bfcb208b/destination.txt?sv=2023-11-03&se=2024-05-03T06%3A15%3A26Z&sr=c&sp=rc&sig={redacted} RequestHeaders:{"host":"<IP_ADDRESS>:10000","x-ms-copy-source":"https://<IP_ADDRESS>:10000/devstoreaccount1/240c8d06-19a5-42cc-bd9f-fa81bfcb208b/source.txt?sv=2023-11-03&se=2024-05-03T06%3A15%3A26Z&sr=c&sp=r&sig={redacted}","x-ms-version":"2023-11-03","accept":"application/xml","x-ms-client-request-id":"8e9ee6ef-a7d3-434f-a376-1914e962e3af","x-ms-return-client-request-id":"true","user-agent":"azsdk-net-Storage.Blobs/12.19.1 (.NET 6.0.29; Microsoft Windows 10.0.22631)","content-length":"0"} ClientIP=<IP_ADDRESS> Protocol=https HTTPVersion=1.1
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: BlobStorageContextMiddleware: Account=devstoreaccount1 Container=240c8d06-19a5-42cc-bd9f-fa81bfcb208b Blob=destination.txt
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb verbose: DispatchMiddleware: Dispatching request...
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: DispatchMiddleware: Operation=Blob_StartCopyFromURL
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb verbose: AuthenticationMiddlewareFactory:createAuthenticationMiddleware() Validating authentications.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: PublicAccessAuthenticator:validate() Start validation against public access.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: PublicAccessAuthenticator:validate() Getting account properties...
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: PublicAccessAuthenticator:validate() Retrieved account name from context: devstoreaccount1, container: 240c8d06-19a5-42cc-bd9f-fa81bfcb208b, blob: destination.txt
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: PublicAccessAuthenticator:validate() Skip public access authentication. Cannot get public access type for container 240c8d06-19a5-42cc-bd9f-fa81bfcb208b
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: BlobSharedKeyAuthenticator:validate() Start validation against account shared key authentication.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: BlobSharedKeyAuthenticator:validate() Request doesn't include valid authentication header. Skip shared key authentication.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: AccountSASAuthenticator:validate() Start validation against account Shared Access Signature pattern.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: AccountSASAuthenticator:validate() Getting account properties...
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: AccountSASAuthenticator:validate() Retrieved account name from context: devstoreaccount1, container: 240c8d06-19a5-42cc-bd9f-fa81bfcb208b, blob: destination.txt
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: AccountSASAuthenticator:validate() Got account properties successfully.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: AccountSASAuthenticator:validate() Retrieved signature from URL parameter sig: WrVp7OH5U3jvN1j7gZf1kVazEsb8pJCHLEgwf9yCbU0=
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: AccountSASAuthenticator:validate() Failed to get valid account SAS values from request.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: BlobSASAuthenticator:validate() Start validation against blob service Shared Access Signature pattern.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: BlobSASAuthenticator:validate() Getting account properties...
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: BlobSASAuthenticator:validate() Retrieved account name from context: devstoreaccount1, container: 240c8d06-19a5-42cc-bd9f-fa81bfcb208b, blob: destination.txt
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: BlobSASAuthenticator:validate() Got account properties successfully.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: BlobSASAuthenticator:validate() Retrieved signature from URL parameter sig: WrVp7OH5U3jvN1j7gZf1kVazEsb8pJCHLEgwf9yCbU0=
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: BlobSASAuthenticator:validate() Signed resource type is c.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: BlobSASAuthenticator:validate() Successfully got valid blob service SAS values from request. {"version":"2023-11-03","expiryTime":"2024-05-03T06:15:26Z","permissions":"rc","containerName":"240c8d06-19a5-42cc-bd9f-fa81bfcb208b","blobName":"destination.txt","signedResource":"c"}
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: BlobSASAuthenticator:validate() Validate signature based account key1.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: BlobSASAuthenticator:validate() String to sign is: "rc\n\n2024-05-03T06:15:26Z\n/blob/devstoreaccount1/240c8d06-19a5-42cc-bd9f-fa81bfcb208b\n\n\n\n2023-11-03\nc\n\n\n\n\n\n\n"
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: BlobSASAuthenticator:validate() Calculated signature is: WrVp7OH5U3jvN1j7gZf1kVazEsb8pJCHLEgwf9yCbU0=
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: BlobSASAuthenticator:validate() Signature based on key1 validation passed.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: BlobSASAuthenticator:validate() Validate start and expiry time.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: BlobSASAuthenticator:validate() Validate IP range.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: BlobSASAuthenticator:validate() Validate request protocol.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: BlobSASAuthenticator:validate() Got permission requirements for operation Blob_StartCopyFromURL - {"permission":"wc"}
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: BlobSASAuthenticator:validate() For Blob_StartCopyFromURL, if blob exists, the permission must be Write.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: BlobSASAuthenticator:validate() Blob service SAS validation successfully.
2024-05-02T06:15:39.144Z 933256cb-d95d-4f81-8611-90d52f90a8cb verbose: DeserializerMiddleware: Start deserializing...
2024-05-02T06:15:39.145Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: HandlerMiddleware: DeserializedParameters={"options":{"metadata":{},"requestId":"8e9ee6ef-a7d3-434f-a376-1914e962e3af","sourceModifiedAccessConditions":{},"modifiedAccessConditions":{},"leaseAccessConditions":{}},"copySource":"https://<IP_ADDRESS>:10000/devstoreaccount1/240c8d06-19a5-42cc-bd9f-fa81bfcb208b/source.txt?sv=2023-11-03&se=2024-05-03T06%3A15%3A26Z&sr=c&sp=r&sig={redacted}","version":"2023-11-03"}
2024-05-02T06:15:39.145Z 933256cb-d95d-4f81-8611-90d52f90a8cb debug: BlobHandler:startCopyFromURL() Validating access to the source account devstoreaccount1
2024-05-02T06:15:39.149Z 933256cb-d95d-4f81-8611-90d52f90a8cb error: ErrorMiddleware: Received an error, fill error information to HTTP response
2024-05-02T06:15:39.149Z 933256cb-d95d-4f81-8611-90d52f90a8cb error: ErrorMiddleware: ErrorName=Error ErrorMessage=self-signed certificate ErrorStack="Error: self-signed certificate\n    at TLSSocket.onConnectSecure (node:_tls_wrap:1674:34)\n    at TLSSocket.emit (node:events:518:28)\n    at TLSSocket._finishInit (node:_tls_wrap:1085:8)\n    at ssl.onhandshakedone (node:_tls_wrap:871:12)"
2024-05-02T06:15:39.149Z 933256cb-d95d-4f81-8611-90d52f90a8cb error: ErrorMiddleware: Set HTTP code: 500
2024-05-02T06:15:39.149Z 933256cb-d95d-4f81-8611-90d52f90a8cb info: EndMiddleware: End response. TotalTimeInMS=5 StatusCode=500 StatusMessage=undefined Headers={"server":"Azurite-Blob/3.30.0"}

I can repro this issue with https.
The error report from function validateCopySource(): https://github.com/Azure/Azurite/blob/2bb552e703772b9a57ca713ef271c3c7c624a535/src/blob/handlers/BlobHandler.ts#L735
However, this issue not happen before since copy inside same account won't call this function.
The direct cause of this failure is caused by recent change from https://github.com/Azure/Azurite/pull/2330, which makes even copy inside same account will go through validateCopySource() function.
https://github.com/EmmaZhu/Azurite/blob/0e6b520543c47d5b296e2933c028c43ca9e3aad9/src/blob/handlers/BlobHandler.ts#L666
@EmmaZhu  Would you please help to look?

Server side behavior is like:
When source and destination are under the same account: if source URI doesn't include SAS token credential, server will allow the copy; if source URI includes a SAS token credential, it will check source with the SAS token
Azurite should change to have the same behavior.

Hi @SamarthMayya ,
I think your issue is because it doesn't have write permission for destination. Your destination SAS token only have rc but copy operation would require wc permission:
=[https://<IP_ADDRESS>/devstoreaccount1/240c8d06-19a5-42cc-bd9f-fa81bfcb208b/destination.txt?sv=2023-11-03&se=2024-05-03T06%3A15%3A26Z&sr=c&sp=rc&sig=](https://<IP_ADDRESS>/devstoreaccount1/240c8d06-19a5-42cc-bd9f-fa81bfcb208b/destination.txt?sv=2023-11-03&se=2024-05-03T06%3A15%3A26Z&sr=c&sp=rc&sig=%7B)

Hi @SamarthMayya ,
I think your issue is because it doesn't have write permission for destination. Your destination SAS token only has rc but copy operation would require wc permission:
=[https://<IP_ADDRESS>/devstoreaccount1/240c8d06-19a5-42cc-bd9f-fa81bfcb208b/destination.txt?sv=2023-11-03&se=2024-05-03T06%3A15%3A26Z&sr=c&sp=rc&sig=](https://<IP_ADDRESS>/devstoreaccount1/240c8d06-19a5-42cc-bd9f-fa81bfcb208b/destination.txt?sv=2023-11-03&se=2024-05-03T06%3A15%3A26Z&sr=c&sp=rc&sig=%7B)

Hi @EmmaZhu,
Is this the case even in production storage accounts?

https://learn.microsoft.com/en-us/rest/api/storageservices/copy-blob?tabs=shared-access-signatures#account-sas
According to this link, for Copy Blob operation, Write permission isn't necessary, if we want to copy to a new destination. Create should be enough.

I'm having similar issue, but only in our GitLab pipelines. Here's the stack trace:
2024-05-22T06:02:15.680+0000 [DEBUG] [TestEventLogger]     2024-05-22 09:02:15:679 +0300  WARN 817 --- [ool-38-worker-7] f.r.store.request.StoreClientRequest     : Store client request exception Status code 500, (empty body)
2024-05-22T06:02:15.681+0000 [DEBUG] [TestEventLogger]     2024-05-22 09:02:15:681 +0300  WARN 817 --- [ool-38-worker-7] f.r.store.request.StoreClientRequest     : [FAILED]  StoreClient@AzureBlobStoreAdapter@http://localhost:32769/devstoreaccount1/test-container -> copy file /tmp/test-container2153505541716169122/my_endpoint_test-container/data/input/file1.csv to /tmp/test-container2153505541716169122/my_endpoint_test-container/data/test/file1.csv and took 1102.107602893
2024-05-22T06:02:16.860+0000 [DEBUG] [TestEventLogger]     2024-05-22 09:02:16:860 +0300  WARN 817 --- [eduled-thread-2] f.r.s.r.StoreClientRequestExecutor       : FAILED: StoreClient@AzureBlobStoreAdapter@http://localhost:32769/devstoreaccount1/test-container -> copy file /tmp/test-container2153505541716169122/my_endpoint_test-container/data/input/file1.csv to /tmp/test-container2153505541716169122/my_endpoint_test-container/data/test/file1.csv, going to retry, retries used: 0/1, exception: fi.relex.store.StoreException: : com.azure.storage.blob.models.BlobStorageException: Status code 500, (empty body),
2024-05-22T06:02:16.860+0000 [DEBUG] [TestEventLogger]         java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710)
2024-05-22T06:02:16.860+0000 [DEBUG] [TestEventLogger]         com.azure.core.implementation.MethodHandleReflectiveInvoker.invokeWithArguments(MethodHandleReflectiveInvoker.java:35)
2024-05-22T06:02:16.860+0000 [DEBUG] [TestEventLogger]         com.azure.core.implementation.http.rest.ResponseExceptionConstructorCache.invoke(ResponseExceptionConstructorCache.java:51)
2024-05-22T06:02:16.860+0000 [DEBUG] [TestEventLogger]         com.azure.core.implementation.http.rest.RestProxyBase.instantiateUnexpectedException(RestProxyBase.java:356)
2024-05-22T06:02:16.860+0000 [DEBUG] [TestEventLogger]         com.azure.core.implementation.http.rest.AsyncRestProxy.lambda$ensureExpectedStatus$1(AsyncRestProxy.java:128)

When I run the same test locally, all goes well. Downgrade to 3.29.0 solves the problem.

What's the status of that issue? I cannot use the newest Azure.Storage.Blobs (version 12.22.1) which requires Blob API version 2024-11-04 introduced in version 3.32.0. I don't want to downgrade to pre 3.30.0, as I will need to downgrade Azure.Storage.Blobs, Microsoft.Azure.WebJobs.Extensions.Storage.Blobs, etc. It's just too much of a hassle. Please fix this issue.

What's the status of that issue? I cannot use the newest Azure.Storage.Blobs (version 12.22.1) which requires Blob API version 2024-11-04 introduced in version 3.32.0. I don't want to downgrade to pre 3.30.0, as I will need to downgrade Azure.Storage.Blobs, Microsoft.Azure.WebJobs.Extensions.Storage.Blobs, etc. It's just too much of a hassle. Please fix this issue.

@michalchecinski
Would you please share the Azurite debug log, so we can identify if it's the same issue?
Besides that, if you downgrade to Azurite 3.29.0, you can start Azurite with "--skipApiVersionCheck", then you don't need downgrade the SDK version.

We are also seeing this issue, but using the dotnet client.
Everything works perfectly fine using an actual azure storage account, but when we switch to azurite we get this internal server error when trying to use the BlobClient.StartCopyFromUriAsync method.
It is solved by downgrading to version 3.29.0.

@michalchecinski
Would you please share the Azurite debug log for the failed request?
@EmmaZhu  Would you please help to look?


Show extra space only when qr appears!

Show extra space only when qr appears!
[]

Can you elaborate on this issue?

Can you elaborate on this issue?

the white blank space under create buttons should only appear when create button is clicked and in that white space qr code appears!

@all-contributors please add @jakebolam for infrastructure, tests and code

I'd like to work on this one!

I'd like to work on this one!

You have been assigned

This issue has been resolved by @heart thank you!


The error traceback

While the executing task raise an exception.
The qcluster only shows the error message, without error traceback
Where I can find the error traceback to debug?

@lucemia you may want to look at #177. Its not merged yet, but the diff merges cleanly onto the current master if you want to try and use it.


pull-request for unpushed branch opens message editor with unrelated remote

Steps to reproduce:

git checkout -b feature_branch org/master
git commit
hub pull-request -b org:master

This results in the following prepopulated message:
  1
  2 # Requesting a pull to org:master from unrelated:feature_branch
  3 #
  4 # Write a message for this pull request. The first block
  5 # of text is the title and the rest is description.

The .git/config for the feature_branch is
[branch "feature_branch"]
	remote = org
	merge = refs/heads/master

My remotes are listed as follows on git remote -v
org	git@github.com:xxx (fetch)
org	git@github.com:xxx (push)
unrelated	git@github.com:xxx (fetch)
unrelated	git@github.com:xxx (push)
unrelated2	git@github.com:xxx (push)
unrelated2	git@github.com:xxx (fetch)
myfork	git@github.com:xxx (fetch)
myfork	git@github.com:xxx (push)
unrelated3	git@github.com:xxx (fetch)
unrelated3	git@github.com:xxx (push)
unrelated4	git@github.com:xxx (push)
unrelated4	git@github.com:xxx(fetch)
unrelated5	git@github.com:xxx (fetch)
unrelated5	git@github.com:xxx (push)

I am guessing it picks up first that does not match base from the list. I think it should rather fail if it finds there's more than one potential remote.

... and org was what the world calls "origin", which you for some reason renamed to make things interesting? :)

@danmbox because I keep it named after organization which I abbreviated org. I think origin is misleading when you have many remotes. Might be just me though.

Looking at the report I wasn't at first sure whether "org" was just origin, the origin's github username, or the fork author's username. But thankfully you have the remote list at the end :)

What is your git config push.default and hub version? Thanks

 $ git config push.default
 $ hub version
git version 2.3.2
hub version 2.2.1

Thank you. Did you say that "feature_branch" was unpushed? From your .git/config, it seems that "feature_branch" was pushed to "org" remote. Is that true? In that case, it seems that hub failed to detect that the upstream for "feature_branch" was "org:feature_branch" and instead thought that the branch was pushed to "unrelated" remote. Does that remote also have a branch with the same name "feature_branch"?
Just to be clear: none of your remotes are named literally "origin", "github", or "upstream", right?

@mislav It was not pushed. The .git/config entry you get by just checking out a new branch as can be seen by following the steps listed in the report:
$ git checkout -b my_new_thingy org/master
Branch my_new_thingy set up to track remote branch master from org.
Switched to a new branch 'my_new_thingy'
$ tail -n 3 .git/config
[branch "my_new_thingy"]
	remote = org
	merge = refs/heads/master

Yes none of the following names are in use for remotes: "origin", "github", or "upstream"

Thanks for the info. I'm guessing that hub just didn't know if and where "feature_branch" was ever pushed, so it simply defaulted to "unrelated" remote which was likely first in the alphabetical order of remotes. I don't know who better hub can behave in this case. What did you expect to get?

@mislav check the last paragraph of my report

I understand. We'll see what we can do.

I'm getting the same behavior here, just worse. I've just been through the following steps :

Make some new fancy branch for an awesome. bugfix. pushed to "org" repo.
git pull-request, got proposed "pull to unrelated:master from more_unrelated:some-branch"
Jumped to the issue tracker because it's been doing that since, well, maybe 3 years :wink:
Opened .git/config in TextMate to check for settings and such (I'm including that because magic happened)
Tried git pull-request -h org:master, got "org:master from another_unrelated:something".
Tried git pull-request. Got it right, this is "org:master from org:fixes/1000". As I said, magic, and confusion.

Note that step 5 actually failed with the following :
Error creating pull request: Unprocessable Entity (HTTP 422)
Missing field: "head_sha"
Missing field: "base_sha"
No commits between master and fixes/100

but after a few minutes it worked fine.

I think what would be nice is a hub.defaultremote config or something along those lines (that would handle the case where hub doesn't guess the correct "origin").

@tiennou Sorry you had trouble. Yeah, hub sometimes has a hard time guessing where everything is. The origin remote should be named one of "github", "upstream", or "origin". This might be configurable in the future.

@mislav I'm getting this issue too where I'm no longer able to get the last commit message propagated into my log, any ideas?
▶ git remote -v
origin  git@github.com:cdrage/streamlink.git (fetch)
origin  git@github.com:cdrage/streamlink.git (push)
upstream        git@github.com:streamlink/streamlink.git (fetch)
upstream        git@github.com:streamlink/streamlink.git (push)

@cdrage This is still an issue, sorry! Steps you can take to make it easy for hub:

Push to the same-named branch on "origin" if git config push.default is "simple" (default since git 2.0) or "current";
If the push configuration is "upstream", then ensure that the local branch is set up to track the branch you pushed to on "origin": git push origin -u my-local-branch:the-remote-branch;
See which commands hub tries to run in the background by using HUB_VERBOSE=1 hub pull-request ....


Use B+Tree for larger DIM

The implementation currently uses std::map for DIM >= 10.
A custom B+Tree (a tree with larger and horizontally connected nodes) may be more efficient.

Benchmark report:
2022-03-BPlusTree.txt


Support Request for Sagemath

Currently sagemath is not supported. Would be nice if its added. sage itself is a wrapper around python, thus adding it should be fairly easy.
Thanks

+1 on this. It would be useful for a class I am taking.

+1


[Enhancement]: Grant needs more details

Is there an existing issue about this enhancement?

[X] I have checked the existing issues.

Describe the enhancement.
https://docs.matrixorigin.io/dev/MatrixOne/Reference/SQL-Reference/0.6-Database-Administration-Statements/grant-privileges/
https://docs.matrixorigin.io/dev/MatrixOne/Reference/SQL-Reference/0.6-Database-Administration-Statements/grant-role/
We need more details about the grant and privilege, what kind of privileges are possible?  Who has right to grant to whom?
For users, where do they find what kind of privilege they have?  In what case they need to interact with the grant and privilege ?

edit the docs here：https://github.com/matrixorigin/matrixorigin.io/pull/123


[FLINK-31696] ElasticSearch nightly CI failure

ElasticSearch nightly CI failure

@MartijnVisser bringing the fixes to Elasticsearch Connector :-)

@reta Can you include setting the version for the connector to 4.0-SNAPSHOT, given that we'll drop support for Flink 1.16 with this PR?

@MartijnVisser it was done already, https://github.com/apache/flink-connector-elasticsearch/blob/main/pom.xml#L32 :)

Nightly triggered at https://github.com/apache/flink-connector-elasticsearch/actions/runs/4670944068


Fix newsletter form submit button text is off center

Just a quick PR to center the newsletter submit button text.
BEFORE

AFTER

You bet! 🙌


Forte for payment processing (including ACH)?

https://www.forte.net/

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/21789621-forte-for-payment-processing-including-ach?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

Thanks, @catskul!

Called, no answer.

I filled out their contact form.

Thank you for your inquiry to Forte Payment Systems.

At this time we are not accepting merchants in your industry.  If this should change in the future, we will gladly notify you back.

If you have further questions, please feel free to let me know.


support output raw content for CommadWidget

Don't call format_string if the command_xxx_format doesn't contains style syntax.
This will let the external command to take the responsibly for the output of the content. For example, this feature let conky output its result along with the raw color codes.

my config files

zjstatus.kdl
conky.conf

conky

I use conky-1.19.6
I built conky with

cmake -DBUILD_X11=OFF -DBUILD_WAYLAND=OFF

to make it even more lightweight, because I don't need graphic support.

If you prefer to use package-manager, it is advice to check whether your disto have conky-cli

Hey @benzwt
thank you so much for the contribution! It's really awesome to see conky within zjstatus! Is it ok, if I put your config and screenshot to the examples section?
This merge request inspired me for another idea for the command widget: specifying the rendering mode for the command widget (static, dynamic or raw).
Thanks a lot and enjoy the holidays.

@dj95
Just go ahead to put my config to examples/.
I am conceiving to put every static data into cache, since the kdl config is read only once. Such thing only to be processed only once. This should make the render go faster. Let's open an issue or discussion to talk about it.
Thanks!

Thanks.
What exactly do you want to cache? I've implemented the render modes a few hours ago.

Actually I implemented zjstatus from the beginning, such that everything from the config is parsed on plugin start and remains in memory. It only prints the data with the format on re-rendering the bar. Therefore it should be mostly cached and out of the way except for the dynamic mode in the command widget. However, I don't think this one can be cached properly.

Actually I implemented zjstatus from the beginning, such that everything from the config is parsed on plugin start and remains in memory. It only prints the data with the format on re-rendering the bar. Therefore it should be mostly cached and out of the way except for the dynamic mode in the command widget. However, I don't think this one can be cached properly.

@dj95
I have just pulled and sync with the HEAD.
I saw your commits, you are vigorous !
dynamic render mode is cool !
About the cache I mentioned earlier is a little bit aggressive. Instead of caching Colorinfo in FormattedPart, I would like to try to cache the raw ansi color sequences, instead. Just a plan without any confidence that whether it will help.

With the latest commit on the main branch only widgets, that receive new data via an event, are re-rendered. Everything else is now cached.
This allowed me to push the rendering time in the benchmarks from 20 microseconds to 3.5 microseconds (+ time for the widget that needs an update). Thanks a lot for the input! It really helps me to optimise zjstatus further!

@benzwt I used the benchmark for render_bar. You can run benchmarks with just bench, when you have just installed.
Please keep in mind that these numbers are heavily depending on your hardware and system configuration. So these numbers are only valid for my setup on my MBP with M1Pro and nix-darwin. For a good result you should benchmark zjstatus without and with your changes to get a comparable value.


"Expand macros" command for procedural macros

Yes please!

I can imagine two options here:

expand macro in the active editor
peek expansion in a popup editor

What about use cargo-expand ?

Seems like the feature has been already implemented, hasn't it?
That's what I've got when expanded an invocation of a procedural macro

Seems like a perfect expansion, or am I missing something? :)

@mexus cool!
It still doesn't work for custom derives, though, maybe it's worth opening a different issue.


Non customer comms

Handle TriggeredV3 events (as well as existing TriggeredV2 events) and deal with the new DeliverTo field.
Handle CancellationRequested and CancellationRequestedV2 events.

This PR was successfully deployed to production by CircleCI build 228 at 2017-05-22 16:12 BST.


tools: Added thanos bucket tool rewrite (e.g allowing block series deletions and relabelling).

Added rewrite tool:
thanos tools bucket rewrite --no-dry-run \
  --id 01DN3SK96XDAEKRB1AN30AAW6E \
  --objstore.config "
type: FILESYSTEM
config:
  directory: <local dir>
" \
  --rewrite.to-delete-config "
- matchers: \"{__name__!~\\\".*total\\\"}\"
"

Not that inefficient as for first iteration. Deleting ALL gauges from 2w 8.3mln series block while gathering changelog file took ~1m30s
Head of changelog for prod block I used:
Deleted {To="1007c280a27d8401", __name__="alerts", _id="f10e61fd-069c-49eb-8ed9-b1633c6259de", alertname="etcdMemberCommunicationSlow", alertstate="firing", endpoint="etcd-metrics", instance="<IP_ADDRESS>:9979", job="etcd", namespace="openshift-etcd", pod="etcd-member-control-plane-1", prometheus="openshift-monitoring/k8s", prometheus_replica="prometheus-telemeter-1", service="etcd", severity="warning"} [{1568135206056<PHONE_NUMBER>000}]
Deleted {To="1007c280a27d8401", __name__="alerts", _id="f10e61fd-069c-49eb-8ed9-b1633c6259de", alertname="etcdMemberCommunicationSlow", alertstate="firing", endpoint="etcd-metrics", instance="<IP_ADDRESS>:9979", job="etcd", namespace="openshift-etcd", pod="etcd-member-control-plane-2", prometheus="openshift-monitoring/k8s", prometheus_replica="prometheus-telemeter-1", service="etcd", severity="warning"} [{1568135206056<PHONE_NUMBER>000}]
Deleted {To="10378dab77f14db3", __name__="alerts", _id="d6856f61-6fee-4f3c-a563-34f3d3f86e4a", alertname="etcdMemberCommunicationSlow", alertstate="firing", endpoint="etcd-metrics", instance="<IP_ADDRESS>:9979", job="etcd", namespace="openshift-etcd", pod="etcd-member-master-0.bm.int.shifti.us", prometheus="openshift-monitoring/k8s", prometheus_replica="prometheus-telemeter-1", service="etcd", severity="warning"} [{1568144193553<PHONE_NUMBER>564}]
Deleted {To="10378dab77f14db3", __name__="alerts", _id="d6856f61-6fee-4f3c-a563-34f3d3f86e4a", alertname="etcdMemberCommunicationSlow", alertstate="firing", endpoint="etcd-metrics", instance="<IP_ADDRESS>:9979", job="etcd", namespace="openshift-etcd", pod="etcd-member-master-2.bm.int.shifti.us", prometheus="openshift-monitoring/k8s", prometheus_replica="prometheus-telemeter-1", service="etcd", severity="warning"} [{1568138793744<PHONE_NUMBER>645}]
Deleted {To="1039efb496924464", __name__="alerts", _id="dee71917-dcd6-495f-bc59-59037658d9f4", alertname="etcdMemberCommunicationSlow", alertstate="firing", endpoint="etcd-metrics", instance="<IP_ADDRESS>:9979", job="etcd", namespace="openshift-etcd", pod="etcd-member-control-plane-2", prometheus="openshift-monitoring/k8s", prometheus_replica="prometheus-telemeter-1", service="etcd", severity="warning"} [{1568499368241<PHONE_NUMBER>241}]
Deleted {To="10c3d0fe3c4349f9", __name__="alerts", _id="3fec22a4-ce8b-4380-a36d-2bce5f61223e", alertname="etcdMemberCommunicationSlow", alertstate="firing", endpoint="etcd-metrics", instance="<IP_ADDRESS>:9979", job="etcd", namespace="openshift-etcd", pod="etcd-member-ip-172-31-136-170.us-west-1.compute.internal", prometheus="openshift-monitoring/k8s", prometheus_replica="prometheus-telemeter-1", service="etcd", severity="warning"} [{1568117253564<PHONE_NUMBER>545}]
Deleted {To="10feb7ef9262777e", __name__="alerts", _id="b572f112-998b-45b9-ab2f-d80f99356723", alertname="etcdMemberCommunicationSlow", alertstate="firing", endpoint="etcd-metrics", instance="<IP_ADDRESS>:9979", job="etcd", namespace="openshift-etcd", pod="etcd-member-ip-10-3-158-139.eu-west-3.compute.internal", prometheus="openshift-monitoring/k8s", prometheus_replica="prometheus-telemeter-1", service="etcd", severity="warning"} [{1567802082565<PHONE_NUMBER>565}]
Deleted {To="1170e6974f79ad38", __name__="alerts", _id="c03103eb-1571-498d-b1fd-70587b445faa", alertname="etcdMemberCommunicationSlow", alertstate="firing", endpoint="etcd-metrics", instance="<IP_ADDRESS>:9979", job="etcd", namespace="openshift-etcd", pod="etcd-member-ip-10-0-138-59.ec2.internal", prometheus="openshift-monitoring/k8s", prometheus_replica="prometheus-telemeter-1", service="etcd", severity="warning"} [{1567804893521<PHONE_NUMBER>521}]
Deleted {To="1170e6974f79ad38", __name__="alerts", _id="c03103eb-1571-498d-b1fd-70587b445faa", alertname="etcdMemberCommunicationSlow", alertstate="firing", endpoint="etcd-metrics", instance="<IP_ADDRESS>:9979", job="etcd", namespace="openshift-etcd", pod="etcd-member-ip-10-0-164-93.ec2.internal", prometheus="openshift-monitoring/k8s", prometheus_replica="prometheus-telemeter-1", service="etcd", severity="warning"} [{1567805133521<PHONE_NUMBER>744}]
Deleted {To="11c401372d21c33f", __name__="alerts", _id="b6acd906-6fc0-4d26-b4e6-e29d412c43ae", alertname="etcdMemberCommunicationSlow", alertstate="firing", endpoint="etcd-metrics", instance="<IP_ADDRESS>:9979", job="etcd", namespace="openshift-etcd", pod="etcd-member-master-1", prometheus="openshift-monitoring/k8s", prometheus_replica="prometheus-telemeter-1", service="etcd", severity="warning"} [{1568427608246<PHONE_NUMBER>437}]

cc @SuperQ, you might find it useful (:
Signed-off-by: Bartlomiej Plotka<EMAIL_ADDRESS>

Example log:
ts=2020-11-09T01:02:57.31884196Z caller=level.go:63 level=info msg="loading bucket configuration"
ts=2020-11-09T01:02:57.822533681Z caller=level.go:63 level=info msg="downloading block" source=01DN3SK96XDAEKRB1AN30AAW6E
ts=2020-11-09T01:03:10.891061066Z caller=level.go:63 level=info msg="changelog will be available" file=/tmp/thanos-rewrite/01EPN8EF1AAER6WZ6H0KSXDAEF/change.log
ts=2020-11-09T01:03:10.901763718Z caller=level.go:63 level=info msg="starting rewrite for block" source=01DN3SK96XDAEKRB1AN30AAW6E new=01EPN8EF1AAER6WZ6H0KSXDAEF toDelete="\n- matchers: \"{__name__!~\\\".*total\\\"}\"\n"
modify [{[__name__!~".*total"] []}]
ts=2020-11-09T01:03:22.477395782Z caller=level.go:63 level=info msg="processed 10.00% of 8377876 series"
ts=2020-11-09T01:03:33.502961899Z caller=level.go:63 level=info msg="processed 20.00% of 8377876 series"
ts=2020-11-09T01:03:46.514366225Z caller=level.go:63 level=info msg="processed 30.00% of 8377876 series"
ts=2020-11-09T01:04:01.191199992Z caller=level.go:63 level=info msg="processed 40.00% of 8377876 series"
ts=2020-11-09T01:04:12.062844251Z caller=level.go:63 level=info msg="processed 50.00% of 8377876 series"
ts=2020-11-09T01:04:22.684655823Z caller=level.go:63 level=info msg="processed 60.00% of 8377876 series"
ts=2020-11-09T01:04:36.599985847Z caller=level.go:63 level=info msg="processed 70.00% of 8377876 series"
ts=2020-11-09T01:04:49.444169472Z caller=level.go:63 level=info msg="processed 80.00% of 8377876 series"
ts=2020-11-09T01:05:02.105350091Z caller=level.go:63 level=info msg="processed 90.00% of 8377876 series"
ts=2020-11-09T01:05:18.180069182Z caller=level.go:63 level=info msg="processed 100.00% of 8377876 series"
ts=2020-11-09T01:05:18.180177192Z caller=level.go:63 level=info msg="wrote new block after modifications; flushing" source=01DN3SK96XDAEKRB1AN30AAW6E new=01EPN8EF1AAER6WZ6H0KSXDAEF
ts=2020-11-09T01:05:18.437332093Z caller=level.go:63 level=info msg="uploading new block" source=01DN3SK96XDAEKRB1AN30AAW6E new=01EPN8EF1AAER6WZ6H0KSXDAEF
ts=2020-11-09T01:05:18.4957816Z caller=level.go:63 level=info msg=uploaded source=01DN3SK96XDAEKRB1AN30AAW6E new=01EPN8EF1AAER6WZ6H0KSXDAEF

Docs preview: https://deploy-preview-3421--thanos-io.netlify.app/tip/components/tools.md/#bucket-rewrite

This looks really interesting! Excuse my likely ignorance, but I have a couple of observations/queries

is there any particular reason that motivates use of the metadata.DeletionRequest format in the --rewrite.to-delete-config.* flag design here? Since logically this is doing similar stuff that a Prometheus relabel config might be doing on people's proms, I wonder whether this format (or a subset of it) might be a suitable DSL; even if action: drop is all it supports initially? Perhaps such relabel config is rather complex to translate to the actions you need to take inside the tooling - or this is to be consistent with existing "prior art" for such block-oriented tooling, however. Just a thought 👍
how are you anticipating that users will select the blocks that require rewriting/deletion of series? What should I do, if I don't know which block IDs have the problematic time series in them? Can we suggest how that could be achieved in the docs somehow?

Good questions @chadlwilson chadlwilson

is there any particular reason that motivates use of the metadata.DeletionRequest format in the --rewrite.to-delete-config.* flag design here? Since logically this is doing similar stuff that a Prometheus relabel config might be doing on people's proms, I wonder whether this format (or a subset of it) might be a suitable DSL; even if action: drop is all it supports initially? Perhaps such relabel config is rather complex to translate to the actions you need to take inside the tooling - or this is to be consistent with existing "prior art" for such block-oriented tooling, however. Just a thought +1

Good point. Relabelling is amazing, although a bit hard to understand and configure correctly by users. Still, it's a plan to add relabelling on top of the existing deletion request. The main problem for me is that relabelling was made for labels NOW (discovery, scraping), so it's has no time awareness. So it's hard currently to define some relabelling for a certain time range (e.g delete series only from 2:00pm to 3:00pm).
Unless we are ok to do it for the whole block always. OR we can extend relabelling to be time interval based. Any preferences?

how are you anticipating that users will select the blocks that require rewriting/deletion of series? What should I do, if I don't know which block IDs have the problematic time series in them? Can we suggest how that could be achieved in the docs somehow?

Let's add that in later PRs. Usually, you need to remove some series if you have some corruption/problem with a particular block. To print all IDs for certain labels thanos  tools bucket ls or thanos tools bucket inspect are useful. On top of that thanos tools bucket web is amazing UI to view things cc @kunal-kushwaha @prmsrswt  (: But good point about documenting this.

how are you anticipating that users will select the blocks that require rewriting/deletion of series? What should I do, if I don't know which block IDs have the problematic time series in them? Can we suggest how that could be achieved in the docs somehow?

One useful feature in promtool is the promtool tsdb analyze command, which analyze a single TSDB block and it shows information like highest cardinality labels. It would be good if we can support this for blocks in the object storage.
But if we can expose this information via UI, then that would be perfect

If we specify a block that doesn't have any matching series of the specified deletion requests, then we will still write a new block and flush it to the obj store?
This is not a problem since we support dry-run. Just curious about whether we can improve the logic to not create a duplicate block

Fixed all, PTAL (:

PTAL :hugs:

ping (:

I suggest we add a --selector.relabel-config flag to allow user relabel metrics like they do when scraping, not just delete

Is this rdy to be merged? :hugs:

@bwplotka Are failing tests flaky ones? In any case, I have re-run them. We'll see soon enough


Feature/generalize docker registry

This updates the UI so that it can support the addition of new docker registries.

[x] Check that you pass the basic compilation and unit tests by running grunt

Getting weird errors with the Cypress testing, I think there might be some race condition that is causing some tests to sometimes fail.

I think the errors are from the page not loading fast enough. Need to investigate if cypress/mocha has a wait option or a retry.


Error Handling

Create a general error modal to be handled by vuex state. This error can be accessed by various actions/components.

Need to add the following features

[ ] error state - can show modal if an error has occurred - loading invalid file or data should be checked
[ ] toggle all plots in file - add a check box / button to toggle on/off all plots in a file
[ ] speed enhancements - looks for places where arrays may be iterated multiple times or where debouncing state change could be helpful


Out-of-Box Stereo Neural Inference Support

Start with the why:
As it stands now using stereo neural inference requires a decent knowledge of homography to rectify the metadata results.  Although such adjustments of the results is very low load on the host (and even low load for a microcontroller), it is quite high mental load for the programmer to implement and verify the correctness of the implementation.
And without these corrections, the stereo neural inference is not very accurate (e.g.: https://github.com/luxonis/depthai-experiments/tree/master/triangulation-3D-visualizer).
If the stereo neural inference is performed on the rectified_left and rectified_right images directly, the no adjustment to the metadata results (e.g. the Key-Points) is necessary on the host, and so getting 3D position results is trivial.
Move to the how:
Implement the capability to run stereo neural inference on the rectified_left and rectified_right streams such that the metadata results (Key-Points) are already stereo rectified and able to be used directly for triangulation of the physical location in meters of the Key-Points.
Use the onboard eeprom data of the camera extrinsics to triangulate the 3D position of the Key-Points and return the XYZ positions of each as part of the meta-data.  Return both the pixel-space meta-data and also the 3D XYZ position points alongside - allowing the host to also do its own calculation if desired.
Implement in 3 stages:

On device decoded networks object-detector support (MobileNetv2-SSD, tiny-YOLOv3, YOLOv3)
In terms of onboard processing, mobilenet/yolo are parsed internal to DepthAI.  So when implementing this we can do bounding box triangulation on DepthAI directly (probably do based on center of the box?).

Host side decoding of networks that are not decoded directly on DepthAI.
And then after that is working, we can do examples of host-side triangulation of key-point networks for which we don't have on-device decoding.  And example is facial landmarks or human pose estimation - both of which we have host-side decoding but not yet on-device decoding.

microPython neural network decoding on-device
And then once microPython (https://github.com/luxonis/depthai/issues/207) is out, we could replicate the same, but on-device with microPython.  And with this functionality, even networks that the Luxonis team is unaware of, can be supported with completely on-device neural decoding and stereo neural inference.

Move to the what:
Support "Out-of-Box" stereo neural inference, where the XYZ locations of the Key-Points is returned alongside the pixel-coordinates.

We implemented this with the new script node, such that the stereo neural inference metadata results are processed directly on DepthAI - but importantly - the code that does the processing on DepthAI can be modified/customized by any developer (such that filters can be added, other/different code can be added, etc.).
https://github.com/luxonis/depthai-experiments/pull/110

And the direct link is here: https://github.com/luxonis/depthai-experiments/tree/master/gen2-triangulation


bleManager.connectToDevice is NOT reporting any error on fail

Expected Behavior
Trying to run bleManager.connectToDevice(deviceId) on a recently scanned but now shutdown device, should fail throwing an error.
Current Behavior
No error is thrown, however obviously the connection is not achieved.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.

Switch on sensor tag
Init scan
Switch off sensor tag
Try to connect to reported sensor tag

Context
Let's say that for some reason a device just successfully scanned gets shutdown, there should a way of failing the connection intent (or at least to have a configurable timeout) to let the user know something went wrong.

Library version: 2.0.0
Platform: Android/iOS.
Formatted code sample or link to a repository:

bleManager
        .connectToDevice(deviceId)
        .then(device =>
          console.log(`Device ${deviceId} connected successfully!`),
        )
        .catch(err => console.log('ERROR ON CONNECTION =', err));

For Android using this setup the promise should fail after ~30 seconds. I do not remember if iOS is doing the same. What platform you test on?

@dariuszseweryn thanks for your answer.
I'm working with both platforms.
I can confirm a fail message after 30'' on Android:
BleError: Device AA:BB:CC:DD:EE:FF was disconnected
Unfortunately that's not the case on iOS. Nothing is being returned...

That is exactly as the underlying platforms behave by default. iOS does not timeout a connect request on its own. Android may not timeout if autoConnect is set to true but it will most probably take more time than in default (autoConnect: false) mode. Exactly as it is described in the wiki. I will add a note on default behaviour of iOS.


Scale facet filters

Purpose
In the search filters pane, we display the top N (by default 10) values for each filter, ordered by facet count. It makes sense to show the values with the most matching courses more prominently, but users might want to filter by other values, especially on Richie instances that host a large number of courses.
Proposal
Add a button on said search filters that opens a modal with a search field that is specialized to that filter.
This will let users easily add any value for a given filter through a full-text search.

Note: part of #376, along with #790


Replace Q for a better promises solution

Some benchmark tests show that the Q lib is not the best in performance when it comes to libraries that deal with the concept of promises.
The Bluebird lib has proven to be the best for this purpose, but we can also test the option of native ES6 promises, although this offers less features than the first two options.
In the case of native promises we would still need other libs to use features present in the other two libs. In particular: promisify and async with generators.
It is important to note that there is no point in replacing the Q lib inside azk if it is not done in the libs that are part of azk dependencies as well, after all the two libs would still have to be loaded.

[ ] Research if we're going to use ES6 or Bluebird promises
[ ] Replace Q with the one chosen above
[ ] Replace the use of q-io to the version compatible with the choice above
[ ] Benchmark

This is an up to date benchmark comparing all known promises libraries.
bluebird has almost the same performance that callbacks
https://github.com/petkaantonov/bluebird/tree/master/benchmark


export IconSpriteConfig

Added IconSpriteConfig to public API, to allow use DI benefits on module configuration

Merged via commit and version bump on master


Update redirects in Readme

Created with https://github.com/dkhamsing/frankenstein

Thanks again @ReadmeCritic

:wink:


[WIP] Add optional mutual TLS for aggregate drains

Description
Please include a summary of the change.
Type of change

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

Testing performed?

[ ] Unit tests
[ ] Integration tests
[ ] Acceptance tests

Checklist:

[ ] This PR is being made against the main branch, or relevant version branch
[ ] I have made corresponding changes to the documentation
[ ] I have added testing for my changes

If you have any questions, or want to get attention for a PR or issue please reach out on the #logging-and-metrics channel in the cloudfoundry slack

@Benjamintf1 we had a chat with @fhambrec and decided that it would be better to use the following configuration structure as it would be better to fit it in the new Binding struct:
aggregate_drain_certificates:
  - url: url1
     ca: |
      --begin cert--...
    cert: |
       -- begin cert--....
     key: |
       -- begin key--...
  - url: url2
     ca: |
      --begin cert--...
    cert: |
       -- begin cert--....
     key: |
       -- begin key--...

The definition of the aggregate drains will stay as is at the moment:
url1,url2

Activating mTLS will be optional. If the url in the aggregate_drains definition matches the url of an object in the aggregate_drain_certificates than mTLS config will be sent to the syslog agent which will activate mTLS with the given configuration.
What do you think about this?

(yamlizing the old aggregate drain config and new map together in the templating step might be the easiest way to merge the properties?)

@Benjamintf1 I agree with you that having both properties feels awkward. IMO keeping the old config backward compatible and doing some template merging would be even worse.
I personally would make breaking changes and extend the aggregate_drains as an array of objects together with the certs. I don't think that at the moment someone uses the aggregate drains extensively, except as we used them for Log Cache ...
@fhambrec, @ctlong Any thoughts on this?

I'm aware of people using aggregate drains, but it's not used as extensively as nozzles. Ideally, I'd like to see people move over to them though.

What if we say that the value of the aggregate_drains property can be either string or array of objects? The only overhead would be that the value has to be unmarshalled manually. There might be more manual work for validating and parsing the value, but it will be backward compatible.

That's possible? Sorry for the very late response, but that sounds nice to me.

@Benjamintf1 I'm sorry for the late response too :) We've discussed this with @fhambrec how can we implement this with the new mtls structs, I've started to implement something, so that we have some code to discuss on, but due to some other more urgent things I was not able to bring it to some possibly usable state. I'll try to finish the initial changes this week, so that we can continue the discussion.

I assume you got busy? I'm working on something here that should handle things. https://github.com/cloudfoundry/loggregator-agent-release/tree/ben-aggregate-drain-mtls

https://github.com/cloudfoundry/loggregator-agent-release/pull/276 made it in pr form here.

Can't get it to work at the moment and I'm not entirely sure why.... binding-cache seems to be fine, and seems to be reporting swimingly, but I can't get it to actually send logs to log-cache.

Yup, unfortunately I got too busy with other stuff :( I'll take a look at your PR and we can sync on how should we proceed. If you already have a working solution, I guess we can close this PR

https://github.com/cloudfoundry/loggregator-agent-release/pull/276 done I believe.


Create "About" Page.

Create the About Page which must contain all the basic details of this project like "Working","Features", "Developer details" etc.
Please go through README.md and links mentioned below for the instructions and help:-
GO-GREEN featuring GITHUB
git push: You just need a little PUSH.

@nitish-awasthi @vinitshahdeo  I can do it
please assign it to me

@flyingsonu122 Thanks for creating the PR.
But it is requested to kindly wait for the team to assign you the issue.
Kindly do not raise the PR before the assignment.

@flyingsonu122 Thanks for creating the PR.
But it is requested to kindly wait for the team to assign you the issue.
Kindly do not raise the PR before the assignment.

Alright, thank you

@Kashish121 @vinitshahdeo added a new PR #142
please look into it


Feature/inline shortcodes

Add Inline Shortcode Handling
Provide a full example of adding an inline shortcode to be processed and be available for editing inside the Draftail editor.
Ticket URL: https://projects.torchbox.com/projects/wordpress-to-wagtail-importer-package/tickets/67

Testing

[x] CI passes
[x] If necessary, tests are added for new or fixed behaviour
[x] These changes do not reduce test coverage

Documentation.

[x] This PR adds or updates documentation

There are lots of unaddressed review comments here. Do you have any pending responses, @nickmoreton?

Sorry Nick should be OK now.


[Youtube] Embed timestamps from description as chapters

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm requesting a feature unrelated to a specific site
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2022.10.04 (update instructions) or later (specify commit)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
Yt-dlp recognizes the Timestamps as chapters only when they are in the format Timestamp ChapterName.
But if it's like this ChapterName Timestamp it doesn't recognizes them as chapters.

mpv on the other hand displays them as chapters.

This is what I believe mpv uses.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://www.youtube.com/watch?v=jJbxS0eGRIc', '--embed-chapters']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.10.04 [4e0511f] (win32_exe)
[debug] Python 3.8.10 (CPython 64bit) - Windows-10-10.0.19043-SP0
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] exe versions: ffmpeg git-2022-10-28-79508ee52 (setts), ffprobe 2022-01-13-git-c936c319bd-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2022.09.24, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
[debug] Loaded 1690 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.10.04, Current version: 2022.10.04
yt-dlp is up to date (2022.10.04)
[debug] [youtube] Extracting URL: https://www.youtube.com/watch?v=jJbxS0eGRIc
[youtube] jJbxS0eGRIc: Downloading webpage
[youtube] jJbxS0eGRIc: Downloading android player API JSON
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec:vp9.2, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), channels, acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] jJbxS0eGRIc: Downloading 1 format(s): 247+251
[debug] Invoking http downloader on "https://rr2---sn-ugp2ax2a5t-qxal.googlevideo.com/videoplayback?expire=1667612572&ei=PGtlY7zZMavkrtoPivSl8AY&ip=<IP_ADDRESS>&id=o-ABBYQaW7smwFWMO04rhO0a4fAfpwXcORT1hVsaZcmk9Z&itag=247&source=youtube&requiressl=yes&mh=JQ&mm=31%2C29&mn=sn-ugp2ax2a5t-qxal%2Csn-qxaelnez&ms=au%2Crdu&mv=m&mvi=2&pl=24&initcwndbps=1451250&spc=SFxXNu5n1f-GCLNmU988xlgmFM-c9-4&vprv=1&svpuc=1&mime=video%2Fwebm&gir=yes&clen=2240428332&dur=37576.105&lmt=1666212090105673&mt=1667590624&fvip=3&keepalive=yes&fexp=24001373%2C24007246&c=ANDROID&txp=6319224&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt&sig=AOq0QJ8wRAIgLoAVI2f4MFhvnkxugquoSTLabOs6V4p3s1w9Qz3XYEICICkg4f-WiWj6MQqT-OIcR0h5tvqEJ0fWAdZtSiX794ZM&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRgIhAOTt6F6TZQCmWVvLSphap2neRzWKi-r3sQQAWG1pW9nRAiEAirsz_RjOzEARyYSlJP8A0GdZuMR0rRfuZbiRfrQCZtQ%3D"
[debug] File locking is not supported. Proceeding without locking
[download] Destination: COST BOOSTER MARATHON PART 1 BY CA NAMIT ARORA SIR [jJbxS0eGRIc].f247.webm
[download] 100% of    2.09GiB in 00:03:19 at 10.73MiB/s
[debug] Invoking http downloader on "https://rr2---sn-ugp2ax2a5t-qxal.googlevideo.com/videoplayback?expire=1667612572&ei=PGtlY7zZMavkrtoPivSl8AY&ip=<IP_ADDRESS>&id=o-ABBYQaW7smwFWMO04rhO0a4fAfpwXcORT1hVsaZcmk9Z&itag=251&source=youtube&requiressl=yes&mh=JQ&mm=31%2C29&mn=sn-ugp2ax2a5t-qxal%2Csn-qxaelnez&ms=au%2Crdu&mv=m&mvi=2&pl=24&initcwndbps=1451250&spc=SFxXNu5n1f-GCLNmU988xlgmFM-c9-4&vprv=1&svpuc=1&mime=audio%2Fwebm&gir=yes&clen=575792378&dur=37576.121&lmt=1666217660071165&mt=1667590624&fvip=3&keepalive=yes&fexp=24001373%2C24007246&c=ANDROID&txp=6318224&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt&sig=AOq0QJ8wRQIhAKHzEfgiUAIZ4TWJFwZyrBWiZNkS1nQa2ZzK4PH0DAb0AiAwKZGb0LnazYCNxFCZS5YeXhdrhSt3_si13OTvsdHOkw%3D%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRgIhAOTt6F6TZQCmWVvLSphap2neRzWKi-r3sQQAWG1pW9nRAiEAirsz_RjOzEARyYSlJP8A0GdZuMR0rRfuZbiRfrQCZtQ%3D"
[download] Destination: COST BOOSTER MARATHON PART 1 BY CA NAMIT ARORA SIR [jJbxS0eGRIc].f251.webm
[download] 100% of  549.12MiB in 00:00:51 at 10.60MiB/s
[Merger] Merging formats into "COST BOOSTER MARATHON PART 1 BY CA NAMIT ARORA SIR [jJbxS0eGRIc].webm"
[debug] ffmpeg command line: ffmpeg -y -loglevel "repeat+info" -i "file:COST BOOSTER MARATHON PART 1 BY CA NAMIT ARORA SIR [jJbxS0eGRIc].f247.webm" -i "file:COST BOOSTER MARATHON PART 1 BY CA NAMIT ARORA SIR [jJbxS0eGRIc].f251.webm" -c copy -map "0:v:0" -map "1:a:0" -movflags "+faststart" "file:COST BOOSTER MARATHON PART 1 BY CA NAMIT ARORA SIR [jJbxS0eGRIc].temp.webm"
Deleting original file COST BOOSTER MARATHON PART 1 BY CA NAMIT ARORA SIR [jJbxS0eGRIc].f247.webm (pass -k to keep)
Deleting original file COST BOOSTER MARATHON PART 1 BY CA NAMIT ARORA SIR [jJbxS0eGRIc].f251.webm (pass -k to keep)
[Metadata] There isn't any metadata to add

In general, the chapters must be in the format that Youtube processes as chapter markers in video. We do perform our own parsing to cover some common issues with Youtube's parsing, and this specific case can be handled similarly. But there is no intention to make the parsing as lenient as mpv's


[pt-br] Add docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md

Hello everyone,
Brazilian portuguese translation for the Communicate-containers-same-pod-shared-volume page.
Related issues
https://github.com/kubernetes/website/issues/13939

/cc

/retitle [pt-br] Add docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md

@devlware @edsoncelio could one of you please provide a second review?

/cc

Looks good, thanks!
/lgtm

/lgtm
/cc @devlware @edsoncelio

Thanks!
/lgtm
/approve


HDDS-1613. Opening of rocksDB in datanode fails with No locks available. Contributed by Mukul Kumar Singh.

This problem occurs because in the current container cache, if an eviction is being requested on an entry with a reference, the entry is removed from the map while reference is still held onto the rocksdb. This reference also has acquired the lock as well.
When another consumer tries to fetch the rockdb from the cache, it does not find the entry and now tries to acquire the lock, this step will fail as the other reference is holding the lock.
Tested this on MiniOzoneChaosCluster after the fix.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
26
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1
mvninstall
515
trunk passed

+1
compile
282
trunk passed

+1
checkstyle
78
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
973
branch has no errors when building and testing our client artifacts.

+1
javadoc
158
trunk passed

0
spotbugs
332
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
547
trunk passed

_ Patch Compile Tests _

+1
mvninstall
496
the patch passed

+1
compile
293
the patch passed

+1
javac
293
the patch passed

+1
checkstyle
85
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
731
patch has no errors when building and testing our client artifacts.

+1
javadoc
161
the patch passed

+1
findbugs
745
the patch passed

_ Other Tests _

-1
unit
169
hadoop-hdds in the patch failed.

-1
unit
1240
hadoop-ozone in the patch failed.

+1
asflicense
84
The patch does not generate ASF License warnings.

6741

Reason
Tests

Failed junit tests
hadoop.ozone.container.ozoneimpl.TestOzoneContainer

hadoop.hdds.scm.pipeline.TestSCMPipelineManager

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-876/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/876

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux f963c23aace1 4.4.0-139-generic #165~14.04.1-Ubuntu SMP Wed Oct 31 10:55:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / f1552f6

Default Java
1.8.0_212

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-876/1/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-876/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-876/1/testReport/

Max. process+thread count
4854 (vs. ulimit of 5500)

modules
C: hadoop-hdds/container-service U: hadoop-hdds/container-service

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-876/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

The changes look good to me. There is a test failure reported related to this change. Can you please check?

Thanks for the review @bshashikant, TestBCSID is passing locally.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
24
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1
mvninstall
506
trunk passed

+1
compile
266
trunk passed

+1
checkstyle
76
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
926
branch has no errors when building and testing our client artifacts.

+1
javadoc
148
trunk passed

0
spotbugs
320
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
532
trunk passed

_ Patch Compile Tests _

+1
mvninstall
476
the patch passed

+1
compile
301
the patch passed

+1
javac
301
the patch passed

-0
checkstyle
37
hadoop-hdds: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
805
patch has no errors when building and testing our client artifacts.

+1
javadoc
160
the patch passed

+1
findbugs
542
the patch passed

_ Other Tests _

+1
unit
238
hadoop-hdds in the patch passed.

-1
unit
1181
hadoop-ozone in the patch failed.

+1
asflicense
49
The patch does not generate ASF License warnings.

6484

Reason
Tests

Failed junit tests
hadoop.ozone.client.rpc.TestOzoneRpcClientWithRatis

hadoop.ozone.client.rpc.TestOzoneAtRestEncryption

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-876/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/876

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 39599861d086 4.4.0-139-generic #165~14.04.1-Ubuntu SMP Wed Oct 31 10:55:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e49162f

Default Java
1.8.0_212

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-876/2/artifact/out/diff-checkstyle-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-876/2/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-876/2/testReport/

Max. process+thread count
5138 (vs. ulimit of 5500)

modules
C: hadoop-hdds/container-service U: hadoop-hdds/container-service

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-876/2/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Thanks @mukul1987 for updating the patch. There is a checkstyle issue which can be addressed while committing. I am +1 on this change.

I will fix the checkstyle issue while committing.


IO-558 nginx pidfile path

Quick correction, nginx_pidfile_path will not populate on install unless the file is added as a template.

Team Approved


eight_sleep.heat_set fails with "'bool' object is not callable" error

The problem

Trying to set the heating level using the eight_sleep.heat_set service results in an error and does not work.
Environment

Home Assistant release with the issue: > 0.106.0
Last working Home Assistant release (if known): 0.105.5
Operating environment (Hass.io/Docker/Windows/etc.): Docker on RPi4
Integration causing this issue: eight_sleep
Link to integration documentation on our website: https://www.home-assistant.io/integrations/eight_sleep

Problem-relevant configuration.yaml

# Eight Sleep Bed
eight_sleep:
    username: {username}
    password: {password}
    partner: true

Traceback/Error logs

Logger: homeassistant.components.websocket_api.http.connection.2877539312
Integration: websocket_api (documentation, issues)
First occured: 4:35:31 PM (4 occurences)
Last logged: 4:35:46 PM

'bool' object is not callable
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 134, in handle_call_service
    connection.context(msg),
  File "/usr/src/homeassistant/homeassistant/core.py", line 1230, in async_call
    await asyncio.shield(self._execute_service(handler, service_call))
  File "/usr/src/homeassistant/homeassistant/core.py", line 1253, in _execute_service
    await handler.func(service_call)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 198, in handle_service
    self._platforms.values(), func, call, required_features
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 402, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 590, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 433, in _handle_entity_call
    await result
  File "/usr/src/homeassistant/homeassistant/components/template/switch.py", line 191, in async_turn_on
    await self._on_script.async_run(context=self._context)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 247, in async_run
    await self._handle_action(action, variables, context)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 331, in _handle_action
    await self._actions[_determine_action(action)](action, variables, context)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 413, in _async_call_service
    context=context,
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 101, in async_call_from_config
    domain, service_name, service_data, blocking=blocking, context=context
  File "/usr/src/homeassistant/homeassistant/core.py", line 1230, in async_call
    await asyncio.shield(self._execute_service(handler, service_call))
  File "/usr/src/homeassistant/homeassistant/core.py", line 1253, in _execute_service
    await handler.func(service_call)
  File "/usr/src/homeassistant/homeassistant/components/script/__init__.py", line 207, in service_handler
    await script.async_turn_on(variables=service.data, context=service.context)
  File "/usr/src/homeassistant/homeassistant/components/script/__init__.py", line 288, in async_turn_on
    raise err
  File "/usr/src/homeassistant/homeassistant/components/script/__init__.py", line 283, in async_turn_on
    await self.script.async_run(kwargs.get(ATTR_VARIABLES), context)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 247, in async_run
    await self._handle_action(action, variables, context)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 331, in _handle_action
    await self._actions[_determine_action(action)](action, variables, context)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 413, in _async_call_service
    context=context,
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 101, in async_call_from_config
    domain, service_name, service_data, blocking=blocking, context=context
  File "/usr/src/homeassistant/homeassistant/core.py", line 1230, in async_call
    await asyncio.shield(self._execute_service(handler, service_call))
  File "/usr/src/homeassistant/homeassistant/core.py", line 1253, in _execute_service
    await handler.func(service_call)
  File "/usr/src/homeassistant/homeassistant/components/eight_sleep/__init__.py", line 184, in async_service_handler
    await usrobj.set_heating_level(target, duration)
  File "/usr/local/lib/python3.7/site-packages/pyeight/user.py", line 662, in set_heating_level
    if self.device.is_pod():
TypeError: 'bool' object is not callable``

## Additional information

Thanks for reporting.  Error fixed in library and PR submitted to bump hass dependency.


[FormRecognizer] Merge feature branch to main

This feature branch contains the new features for 2022-06-30-preview. All changes have already been reviewed.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.AI.FormRecognizer

/azp run net - formrecognizer - tests

Current failure is a flaky service error we've been seeing in the pipeline for some time now. Not caused by these changes.

public partial class BoundingRegion

Curious - why do we special case the BoundingPolygon?

Refers to: sdk/formrecognizer/Azure.AI.FormRecognizer/src/BoundingRegion.cs:11 in 594f6a6. [](commit_id = 594f6a6c5951c31c80e0559fd179c70da4c6e8e9, deletion_comment = False)

BoundingRegion.cs

public partial class BoundingRegion

Curious - why do we create a special type BoundingPolygon and not use BoundingRegion directly from the rest API?
Refers to: sdk/formrecognizer/Azure.AI.FormRecognizer/src/BoundingRegion.cs:11 in 594f6a6. [](commit_id = 594f6a6, deletion_comment = False)

BoundingRegion and BoundingPolygon are different concepts, and we expose both in the SDK. BoundingRegion is defined by a BoundingPolygon + a page number. This pair uniquely determines a region in a multipage input document.
In addition to this, BoundingPolygon is an SDK-only model. The definition exists in the service's swagger, but it's treated only as an array of float coordinates, so CodeGen does not generate a corresponding model (swagger here):
    "BoundingPolygon": {
      "description": "Bounding polygon, with coordinates specified relative to the top-left of the page. The numbers represent the x, y values of the polygon vertices, clockwise from the left (-180 degrees inclusive) relative to the element orientation.",
      "type": "array",
      "items": {
        "type": "number",
        "minimum": 0
      }
    },

We encapsulate this array of floats in the BoundingPolygon type, which contains an array of PointF instead.

/check-enforcer override

Current failure is a flaky service error we've been seeing in the pipeline for some time now. Not caused by these changes.

Merging this to unblock the next PR. Feel free to add more comments to this PR and I'll address in the next one.


[2.0a0 AutoGraph] segmentation fault after refactoring into smaller functions

System information

TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.0.0alpha0
Python version: 3.6.5

Code to reproduce the issue

# -*- coding: utf-8 -*-
# @Author  : Lin Lan<EMAIL_ADDRESS>
from __future__ import absolute_import
from __future__ import division
from __future__ import print_function

import numpy as np
import tensorflow as tf

class Model(tf.keras.Model):
    def __init__(self):
        super(Model, self).__init__()
        self.dense = tf.keras.layers.Dense(10)

    def call(self, inputs):
        return self.dense(inputs)

model = Model()

def forward(x):
    batch_size = x.shape[0]
    ys = tf.TensorArray(tf.float32, size=batch_size)
    for i in tf.range(batch_size):
        y = model(x[i][tf.newaxis, :])
        ys = ys.write(i, y)
    return ys.stack()

def train(x, forward_func):
    with tf.GradientTape() as tape:
        ys = forward_func(x)
        loss = tf.reduce_mean(ys)
    grads = tape.gradient(loss, model.trainable_weights)
    return grads

def big_train(x, forward_func):
    with tf.GradientTape() as tape:
        batch_size = x.shape[0]
        ys = tf.TensorArray(tf.float32, size=batch_size)
        for i in tf.range(batch_size):
            y = model(x[i][tf.newaxis, :])
            ys = ys.write(i, y)
        ys = ys.stack()
        loss = tf.reduce_mean(ys)
    grads = tape.gradient(loss, model.trainable_weights)
    return grads

x = np.random.rand(10, 100).astype(np.float32)

train(x, forward)
print("pass")

tf.function(big_train)(x, tf.function(forward))
print("pass")

tf.function(train)(x, tf.function(forward))    # lead to segmentation fault (core dumpled)
print("pass")

Other info / logs
Possibly related to #29393 . Also, due to that issue, we have to decorate some nested methods with tf.function.
@alextp @mdanatg

@martinwicke I ran the above code with tf-nightly-gpu-2.0-preview 2.0.0.dev20190606, and the segmentation fault disappeared. However, there are some other errors. Thus, I prefer to close this issue and open another.


Icons (various improvements part 2)

Show icons next to the name and description
Disable the button for the currently selected tab to give a visual indication that it is selected
Update Fabric Loader and API again

build failed because gradle couldn't find minotaur?
is it just me or is half the internet broken right now


fix(pre-upgrade): don't call environmentCheck without necessary bind mounts

Which issue(s) this PR fixes:
https://github.com/longhorn/longhorn/issues/8974
Additional documentation or context
I think this is the right fix, but I may be missing some context. Feel free to open a different PR if the fix should be different @mantissahz.

The issue https://github.com/longhorn/longhorn/issues/8974 in is fixed by https://github.com/longhorn/longhorn/issues/8974#issuecomment-2221727128. Let's close this one.


Require Client Open - Added Bypass Switch

Also:

Wrapped DataStore functions in utils.js.
Bumped Version to 1.11

We'll take a look at this and merge it soon.

Sounds good. Lmk if you need any changes.