FreeTypeFontGenerator-texture-bleeding-#3521-fix

Fixing https://github.com/libgdx/libgdx/issues/3521

PixmapPacker has a new parameter Color currentTransparentColor; used by Page constructor to fill transparent pixels.
FreeTypeFontGenerator sets packer to use color of the font but with zero alpha for transparent pixels to avoid leaks.

I may suggest the following solution to fix the font shadow.

Merge this PR
Modify FreeTypeFontGenerator so it will

generate regular font pages
then switch packer.setCurrentTransparentColor(shadow color);
generate shadow font pages

Modify font render so it will

render glyph shadow
then render the actual glyph.

Should be good now.


Add single sign on option

Cheers @alex-page, agree it could be made clearer. Non-DTAers dont need to use the --sso, so I'm not sure if adding it like this would be best, but I'll merge this in for now and we'll try to revisit again soon.


similar problem like #111 Connect issues with flannel on Centos 6.

Reference: #111
I use an more older version: CentOS release 6.5 (Final)
This does not definitely happen, but is very likely.
I simply reviewed the code, and added some debug code in proxy.c:find_route, found this function wasn't called when I got "Invalid argument". So I guess perhaps tun_to_udp or tun has some problem to read the incoming data.  But really I can't well understand the structure of the code, so haven't dig more in the problem.
Can you help me troubleshoot the problem?  I have the same env like #111 except I use virtualbox. Please let me know if you want to know more info about this.

@qihuagao It's hard for me to troubleshoot this as I failed to replicate it last time. However, my theory is that the kernel does not like the IP on flannel0. Say the flannel network is <IP_ADDRESS>/16 and the host got allocated  <IP_ADDRESS>/24. flannel0 gets assigned <IP_ADDRESS>/16 and docker0 gets <IP_ADDRESS>/24. Technically <IP_ADDRESS>/16 is a perfectly legal IP but I think because of docker0's /24 "overlaps", flannel0 IP, it randomly causes these problems.
Can you either delete flannel0's IP: ip addr del <IP_ADDRESS>/24 dev flannel0 or, if this doesn't work, give it some IP outside of the allocated subnet: ip addr add <IP_ADDRESS>/16 (just make sure .253 is unused). You will no longer be able to ping flannel0 on the remote host but it may solve the problem. It's not a solution but it will help us figure out if that's what's causing the problem.

Thank you for response.
I tried this:
ifconfig docker0 down
brctl delbr docker0
and then start docker after flanneld finish start.
It seems working, so I guess your analysis should be right. but not sure whether it can solve all occasions.

@qihuagao save my life

There is a fix in v0.7.0 which might help with this.

I'm assuming that v0.7.0 resolved this so closing. Please reopen if you're still having problems.


Example of direct fidelity estimation

Adding an example that illustrates the fidelity estimation, as per these two papers
Direct Fidelity Estimation from Few Pauli Measurements
https://arxiv.org/abs/1104.4695
Practical characterization of quantum devices without tomography
https://arxiv.org/abs/1104.3835

Happy to withdraw if this is premature.
I've been working with mpharrigan@ but will listen to advice from others, of course.

I took another look this morning, and I think I can resolve the last comment now.

Thanks. PTAL.

Thanks. PTAL.

Thanks. PTAL.

Thanks. PTAL.

I think you need to push your changes

Cool. now it will just be a matter of getting the CI checks to go green

Hi Matt,
I'm having trouble with this test:
https://travis-ci.com/quantumlib/Cirq/jobs/249375170
it does indeed seem to be missing from here:
https://github.com/quantumlib/Cirq/blob/1000c9a1995b068ea1890bf5556dff4f9acf4e93/cirq/sim/simulator.py#L503
But it is defined here:
https://github.com/quantumlib/Cirq/blob/1000c9a1995b068ea1890bf5556dff4f9acf4e93/cirq/sim/density_matrix_simulator.py#L500
Do you have advice on how to fix this?

You can correct the type with
    density_matrix: cirq.DensityMatrixTrialResult = simulator.simulate(circuit).final_density_matrix

You can run the mypy check locally by running check/mypy

since sim.simulate is an abstract method it can't tell that you're running it from cirq.DensityMatrixSimulator() so you have to tell the type system explicitly

Hi Matt,
I tried your suggestion:
density_matrix: cirq.DensityMatrixTrialResult = simulator.simulate(circuit).final_density_matrix
But I got a Travis error:
https://travis-ci.com/quantumlib/Cirq/jobs/249708895
I also tried this:
    trial_results: cirq.DensityMatrixTrialResult = simulator.simulate(circuit)     density_matrix = trial_results.final_density_matrix
But I got this error:
examples/direct_fidelity_estimation.py:38: error: Incompatible types in assignment (expression has type "SimulationTrialResult", variable has type "DensityMatrixTrialResult") examples/direct_fidelity_estimation.py:39: error: "SimulationTrialResult" has no attribute "final_density_matrix
So I have the new proposed change. However, it touches another file, so I am not sure it's wise.

Opened https://github.com/quantumlib/Cirq/issues/2413
I think the new change is not the right way to go. We shouldn't compromise the actual executable code to kowtow to mypy
Sorry for the previous suggestion not working. I just remembered that the way to force a type is not with an annotation but rather by using cast from the typing module
cast(DensityMatrixTrialResult, simulator.simulate(circuit)).final_density_matrix

should do the trick

All right. I think all the checks are passing now. If I understand correctly, you are the one with write access who can merge changes (if that PR is indeed ready, otherwise happy to work more on it).
Thanks for your patience and all the guidance.

Automerge cancelled: No approved review.

Automerge cancelled: No approved review.

Automerge cancelled: No approved review.

@CirqBot Bad bot.

    if not any(review['state'] == 'APPROVED' for review in review_status):
        return CannotAutomergeError('No approved review.')

How!?

Automerge cancelled: No approved review.

It's because of a pagination issue.

Automerge cancelled: No approved review.

(testing)


Make it a Web Component

If this counts as 1 line of javascript
Then when you wrap it in a modern native javascript Web Component  <map-kick> it would count as ZERO lines of JavaScript

Hey @Danny-Engelman, thanks for the suggestion, and sorry for the delay. It's an interesting idea, but don't want to support an additional interface right now (however, if someone creates this, feel free to share).


Rename World::new to World::empty

This allows to avoid confusion with the WorldExt::new
from Specs

bors r+

bors r+


supabase-js 2.0rc4 - "This endpoint requires a Bearer token" calling signOut()

Hello,
I'm already using version 2.0.0-rc.4. So in the code below, user is signed in (100% sure), and when I call signOut():
const { error } = await supabase.auth.signOut();
console.log(error.message);

... the following error is thrown in the chrome debug console:
helpers.ts:40          GET https://xxxxxxxxxxxxxx.supabase.co/auth/v1/user 401
common.ts:91 AuthApiError: This endpoint requires a Bearer token
    at fetch.ts:36:16

Anyway, even after the error message, the session is successfully closed. This was working fine on the 1.x branch. What am I doing wrong?
Thanks

Hi @howesteve,
Can you confirm this is still an issue on 2.0.0-rc.8?

Yes, it's still the same with 2.0.0-rc.8.

Hey @fernandops26,
Are you calling getUser() when the user is not logged in? That would be the correct error message in that case.
getUser() is not a direct replacement for user() in V1, as it makes an HTTP request every time it's called for the user. Here's how I'd get the user in V2:
const {
  data: { session },
  error,
} = await supabase.auth.getSession()

if (error) {
  // handle error
}

const user = session?.user

@howesteve you wouldn't happen to be calling getUser() somewhere in your code as well?

@howesteve you wouldn't happen to be calling getUser() somewhere in your code as well?
Yes, I was actually calling getUser() inside a onAuthStateChange() handler. Now that I switched into a getSession() -only approach, it looks fixed. However, that was actually quite confusing, since it's supposed to be regular api.

Thanks


Move splash screen out of main storyboard into

This isn't a very interesting patch in itself. But right now almost all
of the app UI is in one storyboard and this is the first step in
separating it out into separate xibs files.

@hanningni please review

:+1:


Hashrate showing 0.00

We cannot seem to get network hashrate from Console. On most coins we use getnetworkhashps is there some other way to get it?

getinfo will display all 5 altos difficulties. Setting algo= in your conf will set the daemon for whatever algo you choose

@justinvforvendetta Thx!

@justinvforvendetta this gives me the Difficulty, but not the Network Hashrate. Is there a way to get the network hashrate? All other coins have implemented getnetworkhashp.


[BUG] Azure Storage Queue CreateIfNotExistsAsync hangs indefinitely and never returns

Library name and version
Azure.Storage.Queues 12.14.0
Describe the bug
I have updated to a more recent version of the package above. And calls to queue.CreateIfNotExistsAsync() are hanging indefinitely. I do not see any outbound calls via fiddler once the call is made and as far as I can tell, nothing is ever transmitted.
I was able to get to this line in the debugger, after which the code will indefinitely hang until I abort it (this is a test case in visual studio).
 return _pipeline.Span[0].ProcessAsync(message, _pipeline.Slice(1));
(In HttpPipeline.cs line 141)
I also eventually see an IOException occurring in the host process but I'm not 100% sure its related.
Expected behavior
Call will immediately return with 200 success and test execution resumes.
Actual behavior
Test case hangs indefinitely.
Reproduction Steps
I can reproduce locally on demand but I do not believe it will be trivial to provide a minimal debug case. I am internal to Microsoft so I can provide a walkthrough offline if necessary.
Environment
No response

@jetuser Thanks for reaching out to us and reporting this issue. I am unable to reproduce this issue at my end. I was able to create the queue successfully.
 using Azure.Storage.Queues;

           // Define the connection string and queue name
            string connectionString = "XXXXXXXXX";
            string queueName = "myqueuedemo";

            // Create an instance of the QueueClient class
            QueueClient queueClient = new QueueClient(connectionString, queueName);

            // Create the queue if it does not exist
            await queueClient.CreateIfNotExistsAsync();

Please enable the client side logging with .net storage client library. More Info here.

That pointer unfortunately doesnt work but I was able to attach the azure event source logger and get it to dump everything to a file. The log matches what I am seeing. I am seeing all the keyvault calls occur successfully (I redacted the url) and then there's no further outbound calls to azure storage queues when the call is made.

Request [d3debe4f-cfb8-4ce1-85e4-313c88252780] GET https:///secrets/CosmosDbTableAuthKey/?api-version=7.4
Content-Type:application/json
Accept:application/json
x-ms-client-request-id:d3debe4f-cfb8-4ce1-85e4-313c88252780
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Security.KeyVault.Secrets/4.5.0 (.NET 6.0.16; Microsoft Windows 10.0.22621)
client assembly: Azure.Security.KeyVault.SecretsError response [d3debe4f-cfb8-4ce1-85e4-313c88252780] 401 Unauthorized (00.3s)
Cache-Control:no-cache
Pragma:no-cache
WWW-Authenticate:Bearer authorization="https://login.microsoftonline.com/975f013f-7f24-47e8-a7d3-abc4752bf346", resource="https://vault.azure.net"
x-ms-keyvault-region:South Central US
x-ms-client-request-id:d3debe4f-cfb8-4ce1-85e4-313c88252780
x-ms-request-id:f7124c1f-c3ec-4c05-9ec5-f0bbb9957dbb
x-ms-keyvault-service-version:1.9.775.1
x-ms-keyvault-network-info:conn_type=Ipv4;addr=<IP_ADDRESS>;act_addr_fam=InterNetwork;
X-Content-Type-Options:REDACTED
Strict-Transport-Security:REDACTED
Date:Tue, 18 Apr 2023 05:37:35 GMT
Content-Length:97
Content-Type:application/json; charset=utf-8
Expires:-1
ClientCertificateCredential.GetToken invoked. Scopes: [ https://vault.azure.net/.default ] ParentRequestId: d3debe4f-cfb8-4ce1-85e4-313c88252780False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:36Z - 0c68649c-564d-45d2-b20b-825039f4fb59] MSAL MSAL.NetCore with assembly version '<IP_ADDRESS>'. CorrelationId(0c68649c-564d-45d2-b20b-825039f4fb59)False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:36Z - 0c68649c-564d-45d2-b20b-825039f4fb59] === AcquireTokenForClientParameters ===
SendX5C: False
ForceRefresh: False
False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:36Z - 0c68649c-564d-45d2-b20b-825039f4fb59]
=== Request Data ===
Authority Provided? - True
Scopes - https://vault.azure.net/.default
Extra Query Params Keys (space separated) -
ApiId - AcquireTokenForClient
IsConfidentialClient - True
SendX5C - False
LoginHint ? False
IsBrokerConfigured - False
HomeAccountId - False
CorrelationId - 0c68649c-564d-45d2-b20b-825039f4fb59
UserAssertion set: False
LongRunningOboCacheKey set: False
Region configured:
False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:36Z - 0c68649c-564d-45d2-b20b-825039f4fb59] === Token Acquisition (ClientCredentialRequest) started:
Scopes: https://vault.azure.net/.default
Authority Host: login.microsoftonline.comFalse MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:36Z - 0c68649c-564d-45d2-b20b-825039f4fb59] [Instance Discovery] Instance discovery is enabled and will be performedFalse MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:36Z - 0c68649c-564d-45d2-b20b-825039f4fb59] [Region discovery] Not using a regional authority. False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:36Z - 0c68649c-564d-45d2-b20b-825039f4fb59] Fetching instance discovery from the network from host login.microsoftonline.com. Request [6bd5bb5a-17bb-4db2-9882-e4511ec1f459] GET https://login.microsoftonline.com/common/discovery/instance?api-version=1.1&authorization_endpoint=REDACTED
x-client-SKU:REDACTED
x-client-Ver:REDACTED
x-client-CPU:REDACTED
x-client-OS:REDACTED
client-request-id:REDACTED
return-client-request-id:REDACTED
x-app-name:REDACTED
x-app-ver:REDACTED
x-ms-client-request-id:6bd5bb5a-17bb-4db2-9882-e4511ec1f459
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Identity/1.8.2 (.NET 6.0.16; Microsoft Windows 10.0.22621)
client assembly: Azure.IdentityResponse [6bd5bb5a-17bb-4db2-9882-e4511ec1f459] 200 OK (00.4s)
Cache-Control:max-age=86400, private
Strict-Transport-Security:REDACTED
X-Content-Type-Options:REDACTED
Access-Control-Allow-Origin:REDACTED
Access-Control-Allow-Methods:REDACTED
P3P:REDACTED
client-request-id:REDACTED
x-ms-request-id:81adaf2f-fb9d-4dfe-b438-0ed9eeb10b00
x-ms-ests-server:REDACTED
Content-Security-Policy-Report-Only:REDACTED
X-XSS-Protection:REDACTED
Set-Cookie:REDACTED
Date:Tue, 18 Apr 2023 05:37:35 GMT
Content-Type:application/json; charset=utf-8
Content-Length:980
False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:36Z - 0c68649c-564d-45d2-b20b-825039f4fb59] Authority validation enabled? True. False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:36Z - 0c68649c-564d-45d2-b20b-825039f4fb59] Authority validation - is known env? True. Request [4ff3d2bc-10b7-498e-acfd-08e9a586b32e] POST https://login.microsoftonline.com/975f013f-7f24-47e8-a7d3-abc4752bf346/oauth2/v2.0/token
x-client-SKU:REDACTED
x-client-Ver:REDACTED
x-client-CPU:REDACTED
x-client-OS:REDACTED
x-client-current-telemetry:REDACTED
x-client-last-telemetry:REDACTED
x-ms-lib-capability:REDACTED
client-request-id:REDACTED
return-client-request-id:REDACTED
x-app-name:REDACTED
x-app-ver:REDACTED
Content-Type:application/x-www-form-urlencoded
x-ms-client-request-id:4ff3d2bc-10b7-498e-acfd-08e9a586b32e
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Identity/1.8.2 (.NET 6.0.16; Microsoft Windows 10.0.22621)
client assembly: Azure.IdentityResponse [4ff3d2bc-10b7-498e-acfd-08e9a586b32e] 200 OK (00.1s)
Cache-Control:no-store, no-cache
Pragma:no-cache
Strict-Transport-Security:REDACTED
X-Content-Type-Options:REDACTED
P3P:REDACTED
client-request-id:REDACTED
x-ms-request-id:2f0a3445-4770-4a38-9785-f581c3dffe00
x-ms-ests-server:REDACTED
x-ms-clitelem:REDACTED
X-XSS-Protection:REDACTED
Set-Cookie:REDACTED
Date:Tue, 18 Apr 2023 05:37:36 GMT
Content-Type:application/json; charset=utf-8
Expires:-1
Content-Length:1334
False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:37Z - 0c68649c-564d-45d2-b20b-825039f4fb59] ScopeSet was missing from the token response, so using developer provided scopes in the result. False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:37Z - 0c68649c-564d-45d2-b20b-825039f4fb59] Checking client info returned from the server..False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:37Z - 0c68649c-564d-45d2-b20b-825039f4fb59] Saving token response to cache..False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:37Z - 0c68649c-564d-45d2-b20b-825039f4fb59] [SaveTokenResponseAsync] ID Token not present in response. False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:37Z - 0c68649c-564d-45d2-b20b-825039f4fb59] Cannot determine home account id - or id token or no client info and no subject False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:37Z - 0c68649c-564d-45d2-b20b-825039f4fb59] [SaveTokenResponseAsync] Saving AT in cache and removing overlapping ATs...False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:37Z - 0c68649c-564d-45d2-b20b-825039f4fb59] Looking for scopes for the authority in the cache which intersect with https://vault.azure.net/.defaultFalse MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:37Z - 0c68649c-564d-45d2-b20b-825039f4fb59] Intersecting scope entries count - 0False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:37Z - 0c68649c-564d-45d2-b20b-825039f4fb59]
=== Token Acquisition finished successfully:False MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:37Z - 0c68649c-564d-45d2-b20b-825039f4fb59]  AT expiration time: 4/19/2023 5:37:36 AM +00:00, scopes: https://vault.azure.net/.default. source: IdentityProviderFalse MSAL <IP_ADDRESS> MSAL.NetCore .NET 6.0.16 Microsoft Windows 10.0.22621 [2023-04-18 05:37:37Z - 0c68649c-564d-45d2-b20b-825039f4fb59] Fetched access token from host login.microsoftonline.com. ClientCertificateCredential.GetToken succeeded. Scopes: [ https://vault.azure.net/.default ] ParentRequestId: d3debe4f-cfb8-4ce1-85e4-313c88252780 ExpiresOn: 2023-04-19T05:37:36.1206652+00:00Request [d3debe4f-cfb8-4ce1-85e4-313c88252780] GET https:///secrets/CosmosDbTableAuthKey/?api-version=7.4
Content-Type:application/json
Accept:application/json
x-ms-client-request-id:d3debe4f-cfb8-4ce1-85e4-313c88252780
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Security.KeyVault.Secrets/4.5.0 (.NET 6.0.16; Microsoft Windows 10.0.22621)
Authorization:REDACTED
client assembly: Azure.Security.KeyVault.SecretsResponse [d3debe4f-cfb8-4ce1-85e4-313c88252780] 200 OK (00.1s)
Cache-Control:no-cache
Pragma:no-cache
x-ms-keyvault-region:South Central US
x-ms-client-request-id:d3debe4f-cfb8-4ce1-85e4-313c88252780
x-ms-request-id:b9a31133-13c7-4070-bb2c-760684b276d5
x-ms-keyvault-service-version:1.9.775.1
x-ms-keyvault-network-info:conn_type=Ipv4;addr=<IP_ADDRESS>;act_addr_fam=InterNetwork;
x-ms-keyvault-rbac-assignment-id:REDACTED
x-ms-keyvault-rbac-cache:REDACTED
X-Content-Type-Options:REDACTED
Strict-Transport-Security:REDACTED
Date:Tue, 18 Apr 2023 05:37:36 GMT
Content-Type:application/json; charset=utf-8
Expires:-1
Content-Length:345
Request [fa549ac7-999f-42e7-a36d-a2b070ee8a94] GET https:///secrets/StorageAccountConnectionString0/?api-version=7.4
Content-Type:application/json
Accept:application/json
x-ms-client-request-id:fa549ac7-999f-42e7-a36d-a2b070ee8a94
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Security.KeyVault.Secrets/4.5.0 (.NET 6.0.16; Microsoft Windows 10.0.22621)
Authorization:REDACTED
client assembly: Azure.Security.KeyVault.SecretsResponse [fa549ac7-999f-42e7-a36d-a2b070ee8a94] 200 OK (00.1s)
Cache-Control:no-cache
Pragma:no-cache
x-ms-keyvault-region:South Central US
x-ms-client-request-id:fa549ac7-999f-42e7-a36d-a2b070ee8a94
x-ms-request-id:3494741e-6266-41b1-bc88-05f544856a28
x-ms-keyvault-service-version:1.9.775.1
x-ms-keyvault-network-info:conn_type=Ipv4;addr=<IP_ADDRESS>;act_addr_fam=InterNetwork;
x-ms-keyvault-rbac-assignment-id:REDACTED
x-ms-keyvault-rbac-cache:REDACTED
X-Content-Type-Options:REDACTED
Strict-Transport-Security:REDACTED
Date:Tue, 18 Apr 2023 05:37:36 GMT
Content-Type:application/json; charset=utf-8
Expires:-1
Content-Length:456
Request [28e8ff7c-b8d9-4e3b-b7d3-780d22232649] GET https:///secrets/CosmosDbTableAuthKey/?api-version=7.4
Content-Type:application/json
Accept:application/json
x-ms-client-request-id:28e8ff7c-b8d9-4e3b-b7d3-780d22232649
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Security.KeyVault.Secrets/4.5.0 (.NET 6.0.16; Microsoft Windows 10.0.22621)
Authorization:REDACTED
client assembly: Azure.Security.KeyVault.SecretsResponse [28e8ff7c-b8d9-4e3b-b7d3-780d22232649] 200 OK (00.1s)
Cache-Control:no-cache
Pragma:no-cache
x-ms-keyvault-region:South Central US
x-ms-client-request-id:28e8ff7c-b8d9-4e3b-b7d3-780d22232649
x-ms-request-id:e24976f4-b4ef-4aea-bd18-f72904db48b2
x-ms-keyvault-service-version:1.9.775.1
x-ms-keyvault-network-info:conn_type=Ipv4;addr=<IP_ADDRESS>;act_addr_fam=InterNetwork;
x-ms-keyvault-rbac-assignment-id:REDACTED
x-ms-keyvault-rbac-cache:REDACTED
X-Content-Type-Options:REDACTED
Strict-Transport-Security:REDACTED
Date:Tue, 18 Apr 2023 05:37:36 GMT
Content-Type:application/json; charset=utf-8
Expires:-1
Content-Length:345

@jetuser Thanks for your reply. Could you please check the network connectivity? Ensure that your network connection is stable and that there are no firewalls or proxies blocking outbound traffic to the Azure Storage service.
You can try using a different network connection or disabling any firewalls or proxies to see if that resolves the issue.
Are you managing the Storage Account Access keys from Keyvault ? Is your storage account using Microsoft Managed encryption setting ?

Network connectivity is over corpnet so it is fine. There are no proxies or firewalls in the way. Given the keyvault client is functional I question this being an issue anyway.
The access keys on the storage accounts are actually disabled and we are authenticating via a service principal and it is using microsoft managed encryption.

@jetuser I have changed my code to use the Service Principal and even that worked successfully.
            // Define the storage account name and queue name
            string accountName = "MyAccountName";
            string queueName = "MyQueueName";

           // Create an instance of the QueueClient class using the DefaultAzureCredential
            QueueClient queueClient = new QueueClient(new Uri($"https://{accountName}.queue.core.windows.net/{queueName}"), new DefaultAzureCredential());

            // Create the queue if it does not already exist
            await queueClient.CreateIfNotExistsAsync();

Library used: Azure.Storage.Queues 12.14.0

Could you make sure that the clientid, client secrets used by the app are right ?
Also could you try queueClient.CreateIfNotExists( ); instead of async method and check ?
Could you share your sample code snippet ?

Unfortunately changing this code would be non trivial but here's our implementation wrapper around the call. I can confirm by the stack trace we enter the call for the queue client. Authentication token is accurate as our KeyVault calls succeed. And to be 100% clear, based on telemetry I can see there is no outbound call by the SDK once we make the call. It disappears into the http pipeline somewhere and never returns.
protected async Task EnsureQueueExistsAsync(IServiceContext serviceContext)
        {
            if (_queueCreated)
            {
                return;
            }

            await _semaphoreSlim.WaitAsync(serviceContext.CancellationToken).ConfigureAwait(false);

            try
            {
                if (_queueCreated)
                {
                    return;
                }

                await serviceContext.ExecuteWithCountersAsync(async _ =>
                {
                    await _queue.CreateIfNotExistsAsync().ConfigureAwait(false);

                    if (_deadLetterQueue != null)
                    {
                        await _deadLetterQueue.CreateIfNotExistsAsync().ConfigureAwait(false);
                    }
                }, nameof(EnsureQueueExistsAsync), _queue.Uri.Host, _logger, GetDependencyProperties).ConfigureAwait(false);

                _queueCreated = true;
            }
            finally
            {
                _semaphoreSlim.Release();
            }
        }

Also, one additional data point. There is eventually an IOException thrown in the application about a minute after the call is made from System.Net.Http which makes me wonder if the client is not gracefully handling this and returning an error when the connection is aborted. I cannot ensure this is coming from the sdk but given this is the only http call made before this bubbles up, this seems likely:
System.IO.IOException: 'Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request..'
According to diagnostic view, it also does not show an outbound httpclient call to storage, but it does show our keyvault calls. I expected to see a HTTPClient call after the last breakpoint, but nothing...

And more information-
Debugging shows I can get as far as the RedirectPolicy's invocation of await ProcessNextAsync and then I stop being able to step into the pipeline stage executions so I suspect something is hanging between the redirect policy and the storage request validation policy just after this which seems to be holding up the request, but the debugger is acting strange so I am unable to tell whats going on after this. Any attempt to step into the ProcessNextAsync just causes execution to resume and hang spinning doing nothing until I terminate the test task.

@jetuser Thanks for getting back. I am adding the Service team to look into this further.
@xgithubtriage Could you please look into this once you get a chance ? Thanks in advance.
cc @amnguye @seanmcc-msft

After some further digging into the task stack. We found a deadlock in our token cache that was causing the client to hang. A self inflicted problem, thanks for the attention.

@jetuser Thanks for the update.


Vue-editor: document is not defined

If I try to use vue2-editor I get an error
Nuxt.js Error:

ReferenceError: document is not defined
    at i (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:2101)
    at r (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:1923)
    at t.exports (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:3545)
    at Object.t.exports.n (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:262534)
    at e (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:387)
    at Object.t.exports.t (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:261519)
    at e (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:387)
    at Object.defineProperty.value (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:23813)
    at e (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:387)
    at Object.<anonymous> (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:262959)
    at e (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:387)
    at n (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:771)
    at /home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:781
    at n.(anonymous function).i (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:143)
    at Object.<anonymous> (/home/andrey/Projects/node/nuxt-skeditor/node_modules/vue2-editor/dist/index.js:1:264)
    at Module._compile (module.js:570:32)

Include:
File EditorPage.vue
<template>

     <vue-editor v-model="content"></vue-editor>

</template>

File nuxt.config.js
module.exports = {
  head: {
    title: 'starter',
    meta: [
      { charset: 'utf-8' },
      { name: 'viewport', content: 'width=device-width, initial-scale=1' },
      { hid: 'description', name: 'description', content: 'Nuxt.js project' }
    ],
    link: [
      { rel: 'icon', type: 'image/x-icon', href: '/favicon.ico' }
    ]
  },

  loading: { color: '#3B8070' },

  build: {
    vendor : 'vue2-editor',
    extend (config, ctx) {
      if (ctx.isClient) {
        config.module.rules.push({
          enforce: 'pre',
          test: /\.(js|vue)$/,
          loader: 'eslint-loader',
          exclude: /(node_modules)/
        })
      }
    }
  }
}

If I connect the editor to Vue everything works fine

you should use that component only ssr false .
when ssr that will not have document.
https://nuxtjs.org/faq/window-document-undefined

File plugin/vue2-editor.js
import Vue from 'vue'

if (process.BROWSER_BUILD) {
  const VueEditor = require('vue2-editor')
  Vue.use(VueEditor)
}

File nuxt.config.js
module.exports = {
  head: {
    title: 'starter',
    meta: [
      { charset: 'utf-8' },
      { name: 'viewport', content: 'width=device-width, initial-scale=1' },
      { hid: 'description', name: 'description', content: 'Nuxt.js project' }
    ],
    link: [
      { rel: 'icon', type: 'image/x-icon', href: '/favicon.ico' }
    ]
  },

  loading: { color: '#3B8070' },

  plugins: ['./plugins/vue2-editor'],

  build: {
    vendor : 'vue2-editor',
    extend (config, ctx) {
      config.resolve.alias['vue2-editor'] = 'vue2-editor';
      if (ctx.isClient) {
        config.module.rules.push({
          enforce: 'pre',
          test: /\.(js|vue)$/,
          loader: 'eslint-loader',
          exclude: /(node_modules)/
        })
      }
    }
  }
}

File EditorPage.vue
<template>

     <vue-editor v-model="content"></vue-editor>

</template>

There are no errors. But there is no editor. What did I miss? What option have I not yet tried?

Have a look at https://nuxtjs.org/api/configuration-plugins/#the-plugins-property.
You can set the ssr flag to true in your plugins definition.

Not work to!
plugins: [{src: './plugins/vue2-editor', ssr: true}]

Oops, sorry. I meant to say you can set ssr to false, since you only want to be running it on the client.

Try someone to connect this editor to a bare project please. At me it worked in Vue here is not present. But maybe it's not about us at all. I would really appreciate your help.

@QtMobile
I tried read vue2-editor source code .
You got error message that because that package used 'quill' package .
that package need document , and vue2-editor not handle SSR .
so , you can just copy vue2-editor vue single file source to your project .
and modify it support SSR .
Voilà , It works with nuxt.js
https://nuxt-vue-editor.glitch.me/
glitch source
https://glitch.com/edit/#!/nuxt-vue-editor

or , you can make a PR for vue2-editor let it support SSR  😆

Thank you. Very good!

I'm also having this issue when trying to use the vue-carousel npm package. Is there a way to use a package in node_modules without getting the document is not defined error?


Update documentation

It would be good to update the documentation of the package:

All arguments are defined in the same place in a consistent manner (help file of GGIR function).
Default options can be automatically identified in the documentation files, so that they do not have be revised if changed in the future.
Include a vignette with the definition and default options of all the arguments in GGIR.

Hi @vincentvanhees, just finished updating the documentation of the GGIR arguments in GGIR.Rd plus doing a new vignette with all the parameters definition as we agreed. These two documents communicate to each other, so just updating the documentation in GGIR.Rd (in case it is needed in the future) will update the vignette. I had to include 2 new functions in GGIR for that (ShellDoc2Vignette and parametersvignette).
I think everything is fine but we may reduce the info in these documents by elliminating the arguments that are deprecated, and those which are not intended to be used (or very rarely used) by the users. Specifically:
Arguments we could remove:

expand_tail_max_hours
spherecrit
minloadcrit
chunksize --> this is reduced if needed within GGIR, right?
dynrange --> the only scenario when we need this is with ad-hoc files, but we use rmc.dynamic_range for that
rmc.file --> derived from datadir
deprecated arguments

Additionally, to revise:

We could make print.filename and printsummary hardcoded to TRUE and remove arguments,
rmc.check4timegaps --> documentation says "the rest of GGIR is not designed for this", now this is considered within g.imputeTimegaps, right?

Once you tell me what to do with these arguments, I think we can merge this branch into master.

Hi Jairo,

Arguments we could remove:
expand_tail_max_hours

Please keep. I added this argument earlier this year for a client. People kept asking me to allow for a way to include the last day of the recording in part 5 if the recording ends a few hours before midnight. I have added this argument to allow the user to expand the time series in part 1 in order to trigger the analysis of the last day in part 5, but ignores the meaningless last night from the part 4 and part 5 results. The main value of this is that you can still get the waking-hour estimates for the last day if you belief that the person fell asleep before or shortly after the end of the recording. I included a warning in the documentation that this procedure should be done with care. Therefore, I think it is important to keep documentation for this argument.

spherecrit
minloadcrit

Please keep in the technical documentation (man folder), but feel free to omit from the vignette.

chunksize --> this is reduced if needed within GGIR, right?

Please keep. This is used by many studies who use GGIR on a machines with limited memory and/or who process large data files.

dynrange --> the only scenario when we need this is with ad-hoc files, but we use rmc.dynamic_range for that

Please keep in technical documentation, but feel free to omit from the vignette.

rmc.file --> derived from datadir

This argument is needed when testing the read.myacc.csv arguments, because then datadir is not specified. So, I think we need to keep it in the technical documentation, but feel free to omit it from the vignette.

deprecated arguments

Agree. They can be omitted from the vignette.

Additionally, to revise:
We could make print.filename and printsummary hardcoded to TRUE and remove arguments,

With the submission of GGIRread to CRAN and the more thorough review it involved I learnt that they prefer that anything printed to the console can be easily turned off by the user. This means that all warning messages should be generated with warning() and all error messages with error(). Further, we need arguments like printsummary and print.filename to enable users to turn off the console message. At the moment there is no way for the user to turn off all the progress messages in the console
So, I am wondering whether we could find a way to address all of this at the same time. For example:

Do as you suggest, but then add Boolean argument verbose to allow user to turn off all progress messages, including printsummary and print.filename. We could then re-use this argument everywhere in GGIR for all normal non-warning, non-error messages.
Make sure all warning/error messages are correctly given with warning() and error().

`rmc.check4timegaps --> documentation says "the rest of GGIR is not designed for this", now this is considered within g.imputeTimegaps, right?

There is still a line that relies on it, so I think we need to keep it for direct users of read.myacc.csv. However, you could remove it from the vignette as long as it remains part of the technical documentation.

Regarding the arguments in the vignette and the GGIR help file, I will keep them all. The vignette is built to automatically copy all the arguments in the help file, so it would not be easy to remove arguments from only one place.
verbose argument: I think it's a great idea. Should I implement this in this branch or make a new issue/branch for this?

verbose argument: I think it's a great idea. Should I implement this in this branch or make a new issue/branch for this?

Feel free to do it in this branch, but I suspect that this could be more than a day of work and then it may be easier to treat it as a separate project. Initially, it would be good to focus on letting verbose control the console messages in the functions: GGIR, g.part1, g.part2, g.part3, g.part4, g.part5, g.calibrate, and g.getmeta. Once that works we may identify additional console messages that need to be controlled for.
Decision to be made is whether verbose should be a direct argument to the GGIR function, just like mode, do.report, datadir, etc or should it be part of a parameter object? => As verbose is such a generic parameter even relevant to someone not familiar with all the details of GGIR, I think having it as a direct argument is justified. We will then have to pass it to other functions.


CHANGELOG.md needs updating ready for 1.18.0

Ideally we'd have something handle this automatically but for now it seems a manual process once per release isn't too onerous.
We need CHANGELOG.md updating before we can release 1.18.0.

Opened #1784


sim.to_json should create a representation of interventions without a warning

If you call the to_json() method on a sim that has an intervention in it, the sim writes a warning to screen about the inability to serialize the intervention. This clogs up the console in a simulation with more than a few interventions.
Saw this while regressing a ticket with intervention unit tests. What you see below is the console output of looping over 20 random number seeds. I got this for each of the 20 sims and it made the results of each sim hard to see.
Initializing sim with 5000 people for 60 days
Could not sanitize "<covasim.interventions.change_beta object at 0x000001E81C68D470>" <class 'covasim.interventions.change_beta'> (Object of type 'change_beta' is not JSON serializable), converting to string instead
Could not sanitize "<covasim.interventions.change_beta object at 0x000001E81C68D710>" <class 'covasim.interventions.change_beta'> (Object of type 'change_beta' is not JSON serializable), converting to string instead
Could not sanitize "<covasim.interventions.change_beta object at 0x000001E81C68DEB8>" <class 'covasim.interventions.change_beta'> (Object of type 'change_beta' is not JSON serializable), converting to string instead
Could not sanitize "<covasim.interventions.change_beta object at 0x000001E81C68D828>" <class 'covasim.interventions.change_beta'> (Object of type 'change_beta' is not JSON serializable), converting to string instead
ERROR: seed 19
        The cumulative infections at 45 should be the same as at the end.

Could this warning be suppressed? I'm not sure if you can construct these interventions by loading from json but if you can, I think the warning is unnecessary.

Yes, this is a known issue -- will get to it eventually. Need to have both to and from json methods.

Closed by :point_up:


A11y_AzureDataStudio_Welcome_AzureDataStudio-Insiders_ScreenReader : The screen reader focus does not remain within the "Preview" dialog while navigation.

"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags:#A11y_AzureDataStudioJuly2020;#A11y_July27_2020_TestPass;#A11yMAS;#A11yTCS;#SQL Azure Data Studio;#Benchmark;#MAC;#Screenreader;#VoiceOver;#A11ySev1;#Benchmark;#WCAG1.3.1;#WCAG1.3.2;#FTP;
Environment Details:
Application Name: Azure Data Studio
Application Version: 1.21.0-insider
Commit: eccf3cf
Date: 2020-07-24T09:28:31.172Z
VS Code: 1.48.0
Electron: 9.1.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.6.0
Operating system: macOS Catalina (Version 10.15.6 (19G73)
Screen Reader: VoiceOver
Repro Steps:

Launch Azure Data Studio Insiders application.
If Welcome screen is not shown on application launch, then navigate to Help --> Welcome.
Start screen reader, navigate to "Preview" control and activate it.
A dialog appears on the screen, try to navigate within the dialog and observe if the screen reader focus remains within the dialog or not.

Actual:
When the dialog appears on the screen after activating the "Preview" control and the screen reader users start navigating through the dialog content, the screen reader focus does not remain within the dialog itself the user are able to reader the content present out side the dialog without even closing it which is incorrect.
Expected:
The screen reader focus should remain within the dialog when they are navigating through the dialog content and the background content should not be announced to the users until the dialog is closed.
User Impact:
If the screen reader users are able to access the content present in the background of the dialog without closing it than the users will have difficulty in understanding the start and end of the dialog.
Attachment link for Reference:
11541_A11y_AzureDataStudio_Welcome_AzureDataStudio-Insiders_ScreenReader The screen reader focus does not remain within the "Preview" dialog while navigation.zip

I have simplified the preview information to use tooltip to show the text provided by the old dialog.

Closing this bug , as the scenario itself is not present in UI.
GitHubTags:#Closed;


qt5: Disable ltcg for host_build

debug-prefix-map does not work correctly for static libraries
when using ltcg, and since host_build compilations link agaist
the libQt5Bootstrap.a library, it breaks source file packaging
into debug packages.
Signed-off-by: Samuli Piippo<EMAIL_ADDRESS>

5832bf2..3fa1993  master -> master


fix(late-init): Lambda Permission: statement_id_prefix late initialization problem

Description of your changes

fix statement_id_prefix
add working example

Fixes #1001
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

/test-examples="examples/lambda/permission.yaml"


AR turtle tracker (via gps)

Does not seem possible, as AR only allows to draw in 2 Dimensions

Does not seem possible, as AR only allows to draw in 2 Dimensions

You could just limit it to 2 dimensions and make some sort of compass pointing in the general direction of the turtle disregarding the Y-axis.


support minikube w/ hyperkit

Currently ctlptl always uses docker as the driver for minikube
We should be able to customize it to use hyperkit.
This isn't quite as simple as changing a flag, because you also need to do some additional registry plumbing to connect the hyperkit vm to the registry

Please support virtualbox too.

This would be especially nice to have considering that docker desktop is required a paid license now.


Not working for pad only phone

The pad 6  is not completely for tools it is just for phone?? Places support pad for 120 fbs thank

Can you elaborate more about your issue? I quite didn't understand.


Create example showing image background on editor

This feature is used for enabling ability to write text on screenshot pasted from clipboard in velo.


update the demo script

Improvements:

Added Mac-user-friendly commands
Added an extra attribute, so that users can search in the Fleetwise console
Changed vehicle name from "fwdemo" to "fwdemo-${account}" for better readability and identification

Please also include the following statement in the PR description:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.


Top queries panel in Grafana only showing blocked queries

This container is great - thanks so much for making it available! Having said that, I imported the Grafana dashboard, and it appears (by comparing it to the native Pi-Hole dashboard) that the Total Queries graph is displaying blocked queries, but not permitted queries.  I'm going to take a stab at fixing it myself, but I have zero experience with Flux, so I figured I'd post here as well.
Here's a screenshot of the Pi-Hole dashboard:

And this is what I'm seeing on the Grafana dashboard:

Ah - I think I know what the problem is. Could you go to the menu for the panel and click Edit. Then in query B could you try replacing the pihole-01 with $alias on this line:
  |> filter(fn: (r) => r["alias"] == "pihole-01")

One of my Pi-holes is named pihole-01, so it looks like I incorrectly created the dashboard template!
This is what I would expect the correct queries to look like:

Yup - that fixed it.  Thanks for the quick response!


Create NeomakeSh to allow executing of shell commands

Create new function and command to allow execution of arbitrary shell
commands by using :NeomakeSh echo foo bar the same way one would use
! echo foo bar or :Dispatch echo foo bar
The function can also be used by other plugins to make leveraging
jobcontrol easy

Good call. That looks much cleaner.

Thanks for doing this!


Initialising test and removing quark

References to other Issues or PRs or Relevant literature

Issue #85
Brief description of what is fixed or changed
Initialise testing module, Also removed quark(nn initialisation) as was not properly implemented.
Other comments
Ping @rohansingh9001 @TarunTomar122

I will be adding codecov and test to travis soon

LGTM


Trying to connect android with android

Hi! Firstly, I need to know if it is possible connect an android device with an another device using this client.
I want to made an app that could configure an android device which needs a custom configuration (push, pull, etc...)
Currently, when I launch the apk, I get an error "More than one device ...", If I disconnect the host machine (windows) using adb kill-server and click the button another time I get a distinct error, in this case, "JadbException: command failed: device offline".
The problem is that the connection is ok
JadbConnection jadb = new JadbConnection(); // Android Device 1 - "localhost" , "5037"
jadb.connectToTcpDevice(new InetSocketAddress("<IP_ADDRESS>" , 5555));
Could you help me with this pls?

Would you maybe be more specific on errors: stacktrace and the Problem? the title says you want to connect two android devices and in the text you speak of a windows machine you disconnect.
The more than one device error is usually when you have 2 phones connected to the computer and do:
JadbConnection adb = new JadbConnection();
adb.getAnyDevice();

We need some more information on this to be able to help you. Thanks for helping out with writing an answer @root-intruder

@alvaroguiradoASIR Any success in connecting android with android?

Closing this as it seems somewhat unclear


[SelectField] floatingLabelText overlap with falsy value selected

Problem description
Using certain falsy values (null, undefined, '') with SelectField MenuItem does not push the floating label text above the underlying TextField.
Steps to reproduce

Create a SelectField with floatingLabelText, value of null

Non-empty floatingLabelText
value of null

Give the SelectField a child MenuItem

Non-empty primaryText
value of null

floatingLabelText overlaps the MenuItem's primaryText on top of the TextField

Notes
What I'm really trying to do is add the ability to "unselect" a SelectField. If there are better ways of accomplishing this, I'm open to it. I already have a workaround, but it's using "magic" strings to represent a null, which requires me to map from null to that string when working with this component. Feels awkward / error-prone.
Versions

Material-UI: 0.15.0
React: 15.0.2
Browser: Chromium 51.0.2704.36 (nw.js nightly, windows x64)

Images & references

We have the same issue when we are using booleans, ie a SelectField with the following MenuItems:
<MenuItem value={true} primaryText="Yes"/>
<MenuItem value={false} primaryText="No"/>

If you select "No" then the floatingLabelText overlaps the MenuItems primaryText.

This happens to me as well, but I don't have any falsy values in the MenuItems.
I'm passing null as value to SelectField, but it's showing the first MenuItem and floatingLabelText isn't elevating.
"material-ui": "0.15.3",
"react": "~15.3.0",
"react-dom": "~15.3.0"

<SelectField
   value={ null }
   floatingLabelText="Project">
   {projectList.map((item, i) => (
     <MenuItem key={ i } value={ item.id } primaryText={ item.name || item.id } />
   ))}
   </SelectField>

@rhythnic try 0.15.4, there was another regression regarding this in 0.15.3 that was removed for 0.15.4.

@crudh I just updated to 0.15.4. Still experiencing the same issue.
Is there a workaround for to solve this?

@shubham192 0.15.4 solved all of our problems, so not sure what the problem is for you.

We also have the issue on 0.15.4:
const BooleanInput = ({ input, label }) => (
    <SelectInput
        input={input}
        label={label}
        choices={[
            { value: '', label: 'Unknown' }, // <--- issue is here with null value
            { value: false, label: 'No' },
            { value: true, label: 'Yes' },
        ]}
        optionText="label"
        optionValue="value"
    />
);

I have posted some though regarding the direction I think we should follow https://github.com/callemall/material-ui/issues/4891#issuecomment-250904546.


change SVGSpriteLayouter to es6 class

It's safe since this file is totally covered by test

Do you plan to convert everything to Classes? I can't access if that will be a breaking change or not yet :)

I quickly made https://github.com/svg-sprite/svg-sprite/compare/queue-class?w=1, feel free to use it later if you think we could switch everything to classes. Otherwise, I'm not sure it'll make sense to change only a few files :)

@XhmikosR yea I plan but with step by step process. The tests came first and covers all functionality. Then refactoring. If something is breaking in tests - this is a breaking change. Otherwise it's safe.
As for the Queue to es6 - it's important to cover queue.js by tests first


Guidelines for adding new examples

So this issue gives out a template or a guide that can be followed or kept in mind when writing new examples:

The examples should be well documented in terms that can easily be understood by people entering the field of Machine learning or have been in it for a long time.

Make examples simple enough so the user can basically grasp what he needs to build his own full-fledged model and don't over-complicate the examples but still try to include all library functionalities related to that example.

A little bit more can be written about parameters or functionalities which are implemented differently in mlpack than what the common notion is or which might confuse the user.

When adding the comments and writing tutorials try to mention why you followed a particular strategy in the example and maybe mention what are the implications of the strategy that you took and what are the other ways a user can proceed with the example.

Some examples that show things that are particularly interesting or practical can take a divergence from these guidelines and can become a bit complicated, maybe an example of such could be GANs but not limited to it.

And please take a look at the example that exists before and try to avoid redundant examples.

And lastly, this is just a guide, not strict rules so have fun writing examples and show your creativity. :)

@Aakash-kaushik Thank you for writing this, I think we can add some points about tutorials too.
It is quite straightforward to write examples. Most of the above points can be agreed on by most of us.
However, it would interesting to add some points about comments and tutorials considering each example, users would like to know why we followed this pattern in writing code :+1:

I think we should leave space for especially interesting or practical examples, even if they aren't especially simple.

@Aakash-kaushik Thank you for writing this, I think we can add some points about tutorials too.
It is quite straightforward to write examples. Most of the above points can be agreed on by most of us.
However, it would interesting to add some points about comments and tutorials considering each example, users would like to know why we followed this pattern in writing code :+1:

I need to think about how and what to write and then i will add it.

I think we should leave space for especially interesting or practical examples, even if they aren't especially simple.

Yes that is correct I will add that point too.

Hey @shrit, @birm give it a look now.

@Aakash-kaushik Thanks for putting this together, can you run a spell checker over the text?

@Aakash-kaushik Thanks for putting this together, can you run a spell checker over the text?

Edited the issue, please take a look.

@rcurtin do you think we can pin this issue?

Yeah!  Not a bad idea.  Done. :+1:  Thanks @Aakash-kaushik for originally writing these up!

I will add some example tutorial using mlpack. I will document the examples well understood and precise. Please assign this to me

I will add some example tutorial using mlpack. I will document the examples well understood and precise. Please assign this to me

Hey @Saikirannaidu225, welcome and feel free to take those up and create a draft PR for those.
But this issue is just a skeleton and only serves as a guideline on how things should be and not as an actual issue.


ARROW-13108: [Python] Pyarrow 4.0.0 crashes upon import on macOS 10.13.6

I think we have been building the macos wheels with the wrong SDK from the latest iteration.
I managed to force-install the requested sdk version, but the vcpkg build fails with an sdk mismatch.
cc @kou @xhochy

I think the issue is that we link brotli and lz4 from homebrew which built with 10.15 SDK. Investigating further.

Submitted crossbow build: https://github.com/ursacomputing/crossbow/runs/2906443258
Seems like there is no sdk version mismatch warning at this time, though I still need to test the produced wheel on an older macOS.
The vcpkg seems to rebuild the dependencies, I'm also checking what can be the issue there.

We can built with newer SDKs but run on older macOS versions in a lot of cases in conda-forge. Thus I'm not fully sure whether the SDK is the sole issue source. We built arrow-cpp there still with the 10.9 SDK, so this has been working fine.

The solution itself works:

verified manually on travis
verified by the reporter

I'm going to defer the following two to follow-ups, because they consume a lot of time:

we should ensure that this doesn't happen again silently
ensure that vcpkg caching works properly


Jittery keyboard launch

Noticed that the keyboard launch is not very smooth:
https://user-images.githubusercontent.com/56754616/181379614-58866da0-4b57-469c-b54d-725775c9afd6.mp4

Related: https://developer.android.com/develop/ui/views/layout/sw-keyboard


mug: initilizae Point p

gcc-7 had a complaint.
Signed-off-by: Ronald G. Minnich<EMAIL_ADDRESS>

Commit d638fec0d43056b56e4ea1e519a16dbd2ac58c54 is not signed-off.
Please fix these issues:

ron minnich has not signed-off d638fec.

If you'd like more information on how to sign your commits please visit signed-off-by.me


Freeze all immutable classes

This patch makes all the classes freeze. Data classes, which don't have
pre-conditions on their constructors, are simply frozen. Immutable
classes have all of their properties marked with Final.

Pull Request Test Coverage Report for Build 794118751

75 of 79 (94.94%)  changed or added relevant lines in 11 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.1%) to 93.204%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

correct_programs/aoc2020/day_20_jurassic_jigsaw.py
26
28
92.86%

correct_programs/aoc2020/day_21_allergen_assessment.py
6
8
75.0%

Files with Coverage Reduction
New Missed Lines
%

correct_programs/aoc2020/day_12_rain_risk.py
3
80.3%

Totals

Change from base Build 793985592:
0.1%

Covered Lines:
1248

Relevant Lines:
1339

💛  - Coveralls


Removal of staticOntologies folder

We should separate code from ontology data, in particular, we should avoid maintaining manual update service - see https://github.com/edmcouncil/onto-viewer/pull/155#issuecomment-1032598036.
So staticOntologies folder should be removed and code should be improved in such a way that when an imported ontology cannot be downloaded, it informs the user and keeps going.
Initially, we may just log the fact that some ontologies cannot be imported, but later we should log such messages in front end.

@patrycjamia there is a reference to staticOntologies in https://github.com/edmcouncil/onto-viewer/blob/1876facbff2cbd0852a82cdcce5be7bb51e2aaf4/onto-viewer-web-app/config/ontology_config.xml.
Could you have a look and delete it if appropriate?


Provide ability to remove deleted accounts from "Accounts"

No matter how many times I delete the app, both from the home screen, and by going to iPhone storage, an old account I deleted still shows up as an option. Is (could) there (be) a way to prevent this? Thanks.

The next beta will stop loading from the online keychain (what you are experiencing)


[Event Hubs] Performance Test Tweaks

Summary
The focus of these changes is to remove unnecessary initialization already handled by the warmup phase.

API change check
API changes are not detected in this pull request.


Highlighting in results without external dependency

This seems like it may be general enough to have it in Ink, not sure though.
I'd really like to get rid of the Highlights dependency soon, because it's necessary to patch master on Windows to get it running.

I agree, feel free to merge as you think it's ready. I'm guessing the duplicated code isn't going to change too often.
I've copied some of views.coffee over to Ink as a utility (because writing out document.createElement, element.addClass is horrible) but I'm not intending to expose it; I think it's probably out of Ink's scope to provide view rendering. If we wanted to generalise our view system we could always do it as an npm module.


wip: enc28j60 driver.

based on https://github.com/japaric/enc28j60
TODO:

[x] Test that it works
[x] Write an example
[ ] Test in HIL
[ ] Make it use a background task and embassy-net-driver-channel
[ ] Make it use the irq pin, not spin CPU at 100%.
[ ] Perhaps find some other solution for the regs, the current code is very verbose.

no time to do the remaining items, will do later. Driver works fine as-is if you're OK with 100% cpu usage, I've been using in production for years.

Did this get the IRQ pin working prior to merging?

no


Feature request: Put github repo link for each element in catalog for that element

From @dman777 on July 25, 2015 2:27
Feature request: Put github repo link for each element in the catalog for that element. This would be beneficial because the the github code contains demos and examples that the catalog does not. I almost always refer to the code so it would be a great convenience rather than googling.
Copied from original issue: Polymer/polymer#2150

I think this was resolved with this pr :ice_cream:
https://github.com/Polymer/polymer-element-catalog/pull/153

friendly ping :walking:


PullApprove: No need for 3 DCO checks

Signed-off-by: Vincent Batts<EMAIL_ADDRESS>

Vigorously,
LGTM

Did you also want to drop the DCO check from git-validation?

@cyphar fixed. PTAL

LGTM.

LGTM

@cyphar might you remove the trail period in your approval

@vbatts he's not a maintainer on the spec 😅
https://pullapprove.com/opencontainers/runtime-spec/pull-request/1029/reviews/

oh! then nm
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, February 3, 2020 11:09 AM, Tianon Gravi<EMAIL_ADDRESS>wrote:

@vbatts he's not a maintainer on the spec 😅
https://pullapprove.com/opencontainers/runtime-spec/pull-request/1029/reviews/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

cc @opencontainers/runtime-spec-maintainers -- this is an easy one that just needs one more LGTM

LGTM


Fix test subset script

Several changes including

Script now queries analyses (previously this was not implemented)
Script now upserts SG's (previously only samples and assays)
Fixes to additional_samples and additional_families inputs, so they are more compatible with each other.
Implementation of multiple graphql queries (replacing api endpoints)* Not all endpoints have been replaced.
Fixes analyses bug. I think this script was previously responsible for test being overpopulated with analyses entries. We weren't handling upserting correctly here.

Querying has been significantly simplified in this PR, although unfortunately upserting is more complex. So net neutral.

Codecov Report
Patch and project coverage have no change.

Comparison is base (68532b8) 72.05% compared to head (24fa8d3) 72.05%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #519   +/-   ##
=======================================
  Coverage   72.05%   72.05%
=======================================
  Files          90       90
  Lines        7746     7746
=======================================
  Hits         5581     5581
  Misses       2165     2165

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


PR that fixes dendrons cross theme incompatible designs?

Hello,
before I finish the work to do a PR I wanted to ask if it is even a thing that's wanted.
One little flaw I experienced while using dendron is its non-adaptable stylesheet to themes. Working as a designer, I came to learn that this is called "knows it better"-design. E.g., backgrounds for the preview, note graph, calendar etc. have it's fixed values.

This is how they should(?) behave

The next thing that is visible is that the scrollbars are doing their own thing with the given stylesheet  as well.
Which could be as smooth as this

There are some other places i've seen this happens
At lease  the background of the window splits that are so dominant on the screenshots, the fix would be as simple as setting it to transparent.
I know that I'm pretty picky about such things and would understand if there are other things that are prioritized. In any case I'm looking forward to further development. Thanks for the work that far!

this is definitely something we would like to support - just haven't had the bandwidth to. if you would like to contribute a pr, that would be super and be happy to point out relevant parts of the code to get started (code setup docs here)

Hey, @tobealive, this looks fantastic! Non-adaptive themes is an eye-sore for sure.
Linking some related items here for reference:

https://github.com/dendronhq/dendron/issues/496
https://github.com/dendronhq/dendron/discussions/1298
https://github.com/dendronhq/dendron/discussions/2491

Hey,
Thanks for your replies!
Nice, I'll do my best on this next week. Maybe split it into fixes by properties. Then I'd start with the backgrounds because I think this is the easiest and most dominant (also light themes use the dark/brownish background). Scrollbars and stuff will be a bit harder, which can be done separately.
It would also be great if the scrollbars respected the width/height. I didn't look into this yet but, maybe someone knows if vscodes api makes those settings accessible.

Hey hello, please forgive that this takes so long. My job situation changed, and I didn't manage to work on the issue I opened until today.
For now, I started to work on the files of an already active installation and got the colors for the mentioned sections working. Unfortunately I hadn't had the chance yet to implement it on a core level and test it and will barely find the time to do it in the next weeks.
Here is a repo that contains the changed files for an already active installation. It's split into commits that target the coloration of the background, font colors and scrollbars.
https://github.com/tobealive/dendron-adopt-theme-styles/tree/main
I am hoping a bit that someone will come along to help out with this. Maybe seeing those changes makes it easier to hunt them down and integrate them on a core level. A theme I found fitting for testing dendron's behavior on dark / light variants was e.g., Eva.
Sorry again for not having this already finished. I know this is not too big of a commit, but the situation is too busy for me currently to make it a priority.

update: 0.97 has shipped with partial theme support for note preview.


Linting for ninterpolate

@udemy/localization-infra adding linting for our special fancy nintepolate to make sure people pass strings to it, not variables, or gettext() wrapped strings. (pretty identical to the ngettext rule)

I see build is not set up here - ran tests locally to verify they pass

@udemy/web-frontend actually, please review


feature "export to Cirq"

I implemented the feature of "export to Cirq".
However, the manner of implementation may be different that this project intends.
Therefore, there is no problem even if this pull request is not accepted.
Run various_gates.js to check this feature.
import cirq
import numpy as np

def u2(p_phi, p_lambda):
    return cirq.SingleQubitMatrixGate(np.array([[1/np.sqrt(2), -np.exp(1j*p_lambda)/np.sqrt(2)], [np.exp(1j*p_phi)/np.sqrt(2), np.exp(1j*p_lambda+1j*p_phi)/np.sqrt(2)]]))

def u3(p_theta, p_phi, p_lambda):
    return cirq.SingleQubitMatrixGate(np.array([[np.cos(p_theta/2), -np.exp(1j*p_lambda)*np.sin(p_theta/2)], [np.exp(1j*p_phi)*np.sin(p_theta/2), np.exp(1j*p_lambda+1j*p_phi)*np.cos(p_theta/2)]]))

q = [cirq.NamedQubit('q' + str(i)) for i in range(2)]

circuit = cirq.Circuit.from_ops(
    cirq.Rz(0)(q[0]),
    cirq.X(q[0]),
    cirq.Y(q[0]),
    cirq.Z(q[0]),
    cirq.H(q[0]),
    (cirq.X**(1/2))(q[0]),
    cirq.Rz(np.pi / 2)(q[0]),
    cirq.Rz(np.pi / 4)(q[0]),
    cirq.Rz(np.pi / 8)(q[0]),
    cirq.Rx(np.pi / 2)(q[0]),
    cirq.Ry(np.pi / 2)(q[0]),
    cirq.Rz(np.pi / 2)(q[0]),
    cirq.Rz(np.pi / 2)(q[0]),
    u2(np.pi / 2, np.pi / 4)(q[0]),
    u3(np.pi / 2, np.pi / 4, np.pi / 8)(q[0]),
    cirq.S(q[0]),
    cirq.T(q[0]),
    cirq.Rz(-np.pi)(q[0]),
    cirq.Rz(-np.pi / 2)(q[0]),
    cirq.SWAP(q[0], q[1]),
    (cirq.SWAP**(1/2))(q[0], q[1]),
    cirq.CNOT(q[0], q[1]),
    cirq.measure(q[0], key='c0'),
    cirq.measure(q[0], key='c1'),
)

simulator = cirq.google.XmonSimulator()
result = simulator.run(circuit)
print(result)

@snuffkin WOW! This is perfect!!! <3
I will merge later when I reach my computer (4-5 hours after now).
Also, I will update script that generates README.md and extend qps-client to allow running circuits on cirq simulator from UI.
Thank you!!!


Ability to use custom prefix

Implement the ability to allow servers to choose their own prefix to avoid conflicts with other bots.

https://www.youtube.com/watch?v=n-2t4_QX2UE

Added in https://github.com/tvdhout/Lichess-discord-bot/releases/tag/v2.1


bundler crashes with net-http-persistent 3.x

Full log and failure here https://ci.debian.net/data/autopkgtest/unstable/amd64/b/bundler/4243952/log.gz
We discussed this with @deivid-rodriguez earlier this month at debian ruby team sprint and he suggested updating bundler to 2.x but it is still failing.

I wonder if https://github.com/rubygems/bundler/commit/92bdbeddfc6bcd11b9d7e9c6ebc2568875c7a4ce#diff-14a2622eae7471c92a750dce0bbc6538 is relevant here

Hi @pravi, guessing from the backtrace I think the issue here is different.
In ruby 2.7, the URI library has been gemified, so in order to support this new gem, bundler vendors:

A namespaced version of URI.
A namespaced version of net-http-persistent 3.x that itself uses the namespaced version of URI.

Like you can see here.
If you were using these "vendored" versions, I think it should work, but in the backtrace I see that you're using the debian package of net-http-persistent, and the default ruby version of URI. I think that's the issue.
I'm aware that you don't like vendoring things in debian packages, but this is necessary for bundler to be able to support gems like URI.
Our plan for the future is to not vendor the whole version of these gems, but just the minimal parts of them that we absolutely need to use, but for now bundler needs the whole thing so I don't currently have a solution for this other than recommending that you live with vendoring these libraries inside bundler for the time being.
So, sadly, I don't currently have a solution for this :(

@deivid-rodriguez from the log under #Environment it is using ruby 2.5 (ruby 2.7 is not yet default)

Ruby          2.5.7p206 (2019-10-01 revision 67816) [x86_64-linux-gnu]
Full Path   /usr/bin/ruby2.5

Even though during spring, we said we remove vendored copies, apparently we don't remove it actually. See the installed files list https://packages.debian.org/sid/all/ruby-bundler/filelist

I see. In that case, I think the problem is that even if you're not removing the vendored version, you're not actually using it, as you can see in the backtrace:
ArgumentError: bad argument (expected URI object or URI string)
  /usr/lib/ruby/2.5.0/uri/common.rb:745:in `URI'
  /usr/lib/ruby/vendor_ruby/net/http/persistent.rb:954:in `request'
  /usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/fetcher/downloader.rb:59:in `request'

My guess is that even if bundler actually requires the vendored version of this library, the library internally has non-relative requires, so it might be end up jumping into the system version unintentionally due to $LOAD_PATH priority? Merging this PR would probably fix that, but I've been ignored there for a long time.
Can you double check whether removing the dependency on ruby-net-http-persistent from here fixes the issue?

The vendored version already have that patch and patching net-http-persistent does not fix the problem. I can remove ruby-net-http-persistent from Depends and add to Conflicts. ruby-mechanize is another package that requires ruby-net-http-persistent so it will make bundler and ruby-mechanize not installable together.

The vendored version already have that patch

Right, we're manually including that patch, so that's not it.
So, what I don't understand is that in the backtrace, the system URI is being used (/usr/lib/ruby/2.5.0/uri/common.rb), and that's incorrect. We want to vendored URI.
I would expect a backtrace like:
  /usr/lib/ruby/vendor_ruby/uri/common.rb:745:in `URI'
  /usr/lib/ruby/vendor_ruby/net/http/persistent.rb:954:in `request'
  /usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/fetcher/downloader.rb:59:in `request'


[Under the hood] Standardize on "Adapter Integration Tests" GitHub workflow

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt-postgres functionality, rather than a Big Idea better suited to a discussion

Describe the feature
Current
The adapter integration for most adapters maintained by dbt Labs can be found here:
https://github.com/dbt-labs/dbt-postgres/actions/workflows/integration.yml
But the ones for dbt-postgres are here instead:
https://github.com/dbt-labs/dbt-postgres/actions/workflows/integration-tests.yml
The difference is a file name of integration-tests.yml instead of integration.yml.
Proposed
The proposed feature is two-fold:

Rename the workflow file from integration-tests.yml to integration.yml
Standardize the workflow definitions so that dbt-postgres and dbt-redshift so they only differ where they need to (e.g., environment variables, etc.).

Describe alternatives you've considered
No response
Who will this benefit?
People testing a PR in dbt-adapters against each of the adapter repos maintained by dbt Labs, like here: https://github.com/dbt-labs/dbt-adapters/pull/372#issuecomment-2536406292
Are you interested in contributing this feature?
No response
Anything else?
No response

The standardization will effectively happen when we merge all of this into the monorepo. The workflow to run integration tests will probably be _integration-tests.yml, though this isn't expected to be run directly. It will get called by other workflows, such as pull-request-checks.yml and publish.yml. If there is another use case that we need to support, we can add another implementation workflow specific to that use case in the dbt-adapters repo. Let me know if the standardization aspect was the main goal, or if there is something beyond that which we would miss. In the meantime, I'd rather close this as a duplicate of a subset of the monorepo work.


[DUOS-1555][risk=no] multi dataset voting srp component

LInk to Jira ticket
Summary of changes:

Create ResearchPropsalVoteSlab, which displays the requested data uses, the research purpose, and an alert box that is rendered if some of the data uses require manual review
Add a link to the ResearchPropsalVoteSlab to collapse and expand the view of the slab
Create data use pills that display the code and description of a data use
Add a component for the DataUseAlertBox, which filters and displays the data use descriptions of a translated data use based on if they require manual review
Write cypress component tests
Attempt an animation with headless ui Transition component to make the expansion and compression of the slab more smooth (I left the Transition in for a second look, but if the animation part still doesn't work, I will remove)

Have you read Terra's Contributing Guide lately? If not, do that first.

Label PR with a Jira ticket number and include a link to the ticket
Label PR with a security risk modifier [no, low, medium, high]
PR describes scope of changes
Get a minimum of one thumbs worth of review, preferably two if enough team members are available
Get PO sign-off for all non-trivial UI or workflow changes
Verify all tests go green
Test this change deployed correctly and works on dev environment after deployment

Note: currently the enter and leave animation modifiers of Transition are not working (still just a standard appear and disappear). I decided to leave it in for the time being in case I'm missing something simple to make it work. If not, I can remove. It could potentially have something to do with using h(Transition, ...  instead of <Transition ...>... .


Added image for webcam

The image is taken from https://www.flaticon.com/free-icon/webcam_5480222#.
It says that is free por personal use and commercial use with attribution.
I guess this counts as commercial use :rocket: ?
Just in case, I added the credits message on the README.
I do not know 100% if it's needed

It should be fine, all svgs I use aren't created by me. I wish chatgpt could generate a svg image so I wouldn't need to resort to these sites.🤖

:0
Just in case you should check if those have special licenses
(In all honesty it shouldn't be a problem, I do believe this counts as "personal" use!)


cri/sbserver: Use platform instead of GOOS for userns detection

In the sbserver we should not use the GOOS, as windows hosts can run linux containers. On the sbserver we should use the platform param.

@mikebrow solved, PTAL. The windows failure seems completely unrelated to this PR.  The windows error was unrelated.

All green now :)


Laravel Enso as a backend API?

Hello!
I'll be happy for your suggestion here.

Prerequisites

[X] Are you running the latest version?
[X] Are you reporting to the correct repository?
[X] Did you check the documentation?
[x] Did you perform a cursory search?

Description

Hi, I have a small question where I need your input:
I have a website which built with this awesome ENSO system, this website have a backend API (which is should not be connected to the front-end ENSO system), we are connecting and grabbing data from external servers to our db.
We wonder if we should develop this backend (complicated, with many files, including many horizon jobs and auto-scaling) API ONLY over the ENSO system, or, we should work with external Laravel API system (such as Laravel APITO etc), which means, different servers with different code.
What do you think? I'm appreciate your help here.

From a technical point of view, having Enso already in place for the website, you could easily supplement the backend routes / controllers / resources with the one needed for your api. If you do that make sure that you apply the appropriate middleware & middleware groups over these routes (eg: you won't need Enso's core middleware group). You will also have to tackle the api auth.
You should take this path if the business logic / resources between the website and the api are "interpolating". But probably if they were completely separate there would be no question in the first place.

It was very helpful, Thank you @aocneanu


feat: log context

Adds a new context to log to propagate core fields using the central library.  This is similar to trace.AddInfo but has some key differences:

MarshalLog is invoked immediately instead of dynamically
The results are constrained to a finite set of value types

This is intended to be used sparingly, but since this is external OSS, we cannot effectively limit what fields we can supply here.  Perhaps we could set the limit on the number of fields supported, like 5 for example?
This is separate from trace.AddInfo, because we might have values there we do not want to share with logging.   This would also preserve this being an opt in, if you are not interested in these fields, if you don't create a Log context the execution will be the same as before.

@clevelittlefield-outreach I added 1 comment but looking forward to it on master :) so that I can use it

The change itself lgtm but will let dev-tooling folks do the stamp.
Can we prepare the bootstrap changes to set AllowContextFields to the tracing IDs + authn Identities?  If folks use this before we change bootstrap, the bootstrap changes to call AllowContextFields would become breaking changes which I'd like to avoid.


Can't get roles to work with newer versions of Tokens.JWT

If I update to anything never than <IP_ADDRESS> the test application will stop pulling roles from the AD.
I wonder if this is this an issue with JWT, this app or my Azure AD ?

@gpalsson Wow you just saved my life !! I wasted 2 days trying to figure what was wrong between my app and this boilerplate. But a BIG thumb down to Microsoft for not posting back any information on that issue.
Once again Thanks @gpalsson !!

@x3r10n, @gpalsson, thanks for the feedback:
I just tried upgrading the JWT NuGet package from <IP_ADDRESS>250711 (proposed in the sample) to <IP_ADDRESS>8261200 and, although I can log-in, I cannot access the Tasks. I get:
You do not have sufficient priviliges to view this page.

If anyone knows how to fix this...

I'm using ASP.NET Core and am not getting any roles back in my users claims collection. Are there any workarounds or solutions to this problem?

@jmprieur try listing what roles you are part of once you have logged in. If you have configured your user with some roles, you should be able to see them.
@x3r10n no problem, I'm glad it was helpful.

I had the same issue and found not claims with type "role" or "roles".
But this worked:
                   TokenValidationParameters =                      new System.IdentityModel.Tokens.TokenValidationParameters                     {                         ValidateIssuer = false,                         RoleClaimType = "http://schemas.microsoft.com/ws/2008/06/identity/claims/role",                     },

@fwwasol it would be nice if you specified where you added this code.

The upgraded solution is in with the latest token validation lib.


MinIO for Azure deprecation deployment warning + pinning LKG release

MinIO gateway was deprecated in 2022 and the functionality is no longer available in minio/minio:latest images.
This PR updates docs for deploying PROW on Azure to bring attention to this and also references the LKG container image that still containers this functionality.
Deprecation notice - https://blog.min.io/deprecation-of-the-minio-gateway/
Last known release docs - https://github.com/minio/minio/blob/RELEASE.2022-04-29T01-27-09Z/docs/gateway/azure.md

/lgtm

thanks @marosset !
/approve

/lgtm


[ Bug ] parseFiles callback is called after the returning promise is resolved

Summary
callback of parseFiles is called even after parseFiles promise is resolved.
Reproduction repo
https://github.com/ShenQingchuan/repro-sg-parse-files-0.2.2
Reproduction
You could see this kind of output in reproduction:
File: /workspace/repro-sg-parse-files/src/mockFiles/test-file-7304-7bf21e37-8fda-473d-8d0f-74804dd95620.js - Run callback
File: /workspace/repro-sg-parse-files/src/mockFiles/test-file-7303-9f5f76c6-b72f-46bf-a2b7-1c1e01c01a56.tsx - Run callback
File: /workspace/repro-sg-parse-files/src/mockFiles/test-file-7302-d89a12ba-0e94-4e3f-bd95-a0b3ff1fca4e.tsx - Run callback
File: /workspace/repro-sg-parse-files/src/mockFiles/test-file-7301-c85276ef-f257-4563-bc63-74ca8084f8ec.js - Run callback
File: /workspace/repro-sg-parse-files/src/mockFiles/test-file-7300-649fcf13-ce01-4f6f-900b-da37d249b6ca.tsx - Run callback

 --- Main Function Over ---

/workspace/repro-sg-parse-files/src/mockFiles/test-file-9999-5113bbf8-4df2-4bde-b3de-3f13155ede8a.tsx == Imports ==>
/workspace/repro-sg-parse-files/src/mockFiles/test-file-9998-eadc0534-fc86-4a20-acd7-e95d60410f31.ts == Imports ==> './dynamic-plain-65/some-file-1', './dynamic-plain-34/some-file-2', './dynamic-plain-43/some-file-3'

the async function runAstGrepParse is not worked as expected, it should end after every callback function synchronously executed.
Issue cause

Limit maximum synchronous iteration count to prevent event loop
starvation. See src/node_messaging.cc for an inspiration.

https://github.com/nodejs/node/blob/8ba54e50496a6a5c21d93133df60a9f7cb6c46ce/src/node_api.cc#L336

Thanks for the reporting and the detailed reproduction! It is very helpful!
I have found the root cause of the problem. Sorry to introduce this bug due to my limited understanding of Napi and NodeJS.
Here is the detailed walk through of this bug. I hope it can help you.

Background
The parseFiles in ast-grep is implemented by napi-rs' thread safe function. Its behavior is more detailed documented here.
The crux of the problem is that calling thread safe function in napi from Rust will not actually call the JavaScript function. Instead, the callback task is pushed to a queue as a record.

Issue
I expect the parseFiles function call should be resolved only after all JS callbacks are executed. I suspected that pushing to the queue will not immediately call the JS function.
And the bug will be reproduced if Rust has pushed all files to the queue but NodeJS did not feed them to JavaScript. However, when I tried to reproduce the issue by increasing the execution time of the callback, the issue cannot be reproduced, no matter how long I synchronously sleep.

So when will the queue execution be yielded?
Investigation
I investigated the BlockingCall API. It looks like the function just call the C API: napi_call_threadsafe_function.
And that function will eventually call the Push method of ThreadSafeFunction, which looks totally innocent.

Further Repro
I tried another way to reproduce the issue by reducing the file items. Curiously, the returning promise almost always stop when file count is 999.

It probably means that NodeJS will suspend the callback execution when item count reaches 1000. So I "GitHub Search"ed the NodeJS core. Fortunately the 1000 magic number has only a few matching hit.
Indeed! NodeJS' event loop will not drain the sync task queue!

After 1000 files are processed by JavaScript, NodeJS will take a break to make event loop progress. But Rust will ruthlessly push all files to the queue. And the parseFile promise will resolve immediately after all files are pushed while files are still in the message queue awaiting JS callback.

Fixed in https://github.com/ast-grep/ast-grep/commit/ac266dbb3fdb8753e6bc66bc41519ec5deac4bda

I'm a bit confused about the fact that this issue is Closed whereas the documentatiom of findInFiles still refers to this issue as if it's not fixed.

This is not fixable in JavaScript world. Nothing to do from our side so the issue is closed.


Improve sqlite error messages

Also the sqlite error messages are not the best, they are not colorized and it's either kind of hidden or doesn't tell you what went wrong in details.
First one

Second one

Originally posted by @Jolg42 in https://github.com/prisma/prisma/issues/2295#issuecomment-619036556

As of now I can't reproduce. @Jolg42 would be great, if you could post a reproduction repo.

repro-scalar-error-message-Tim.zip
And then do
yarn
ts-node index.ts

Running ts-node index.ts created the prisma/dev.db SQLite file but completely empty and this error appears.
Creating user
(node:66810) UnhandledPromiseRejectionWarning: Error:
Invalid `client.user.create()` invocation in
/Users/j42/Dev/repro/repro-scalar-error-message/index.ts:10:40

   6 const email = [object Object],[object Object],[object Object];
   7
   8 async function main() {
   9   console.log("Creating user");
→ 10   const createUser = await client.user.create(
  Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(SqliteFailure(Error { code: Unknown, extended_code: 1 }, Some("no such table: dev.User"))) })

GitHub should have closed this, but yeah.
Thanks for the context, it's fixed now!
The problem was our code highlighter, we also now have a proper unit test for the stack printer.
It's available in dev.


Kafka Configuration to Enable JMX

One of the aspects that Kafka-manager can use is JMX-Polling. What kind of configuration needs to be done in Kafka to enable metrics reporting to Kafka-Manager.
I have a system with multiple agents (kafka producers), which send logs to different topics. I would like to know how many messages are sent by the agents to each topic. I believe kafka-manager fits the bill.

Make sure JMX_PORT env var is exported before you run the script to start kafka broker:
export JMX_PORT=

in which file inside kafka we have to add export JMX_PORT= property, and while starting kafka-manager it asks for JMX username and password, what should we provide these?? thanks in advance

To enable JMX Monitoring for Kafka broker, please follow below instructions:
Edit kafka-run-class.sh and modify KAFKA_JMX_OPTS variable like below (please replace <> with your Kafka Broker hostname)
KAFKA_JMX_OPTS="-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=<kafka.broker.hostname >-Djava.net.preferIPv4Stack=true"
Add below line in kafka-server-start.sh
export JMX_PORT=${JMX_PORT:-9999}

+1

Awesome @tejasmitha that worked for me! Thanks!

@tejasmitha: yes this is what was missing.
However, I would try to avoid modifying OOTB scripts like kafka-run-class.sh if not necessary. Instead, you can rather export the full KAFKA_JMX_OPTS="..." string into environment, like:
$ export KAFKA_JMX_OPTS="-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=<kafka.broker.hostname >-Djava.net.preferIPv4Stack=true"
$ export JMX_PORT=<your_jmx_port>
and then start your Kafka

Is it possible to run jmx exporter independently and monitor kafka metrices?
Like, I do not(can't) want to edit my kafka scripts.

@chandanatalef you can send all kafka metrics (or any other java based app) via JMX to a metric collection system (e.g. graphite) via jmxtrans-agent (moreover you don't need to enable JMX port on a kafka broker side in this side).

I'm confused. Apologies if I sound too naive.
I have JMX prometheus jar with dependencies, built from
https://github.com/prometheus/jmx_exporter
My kafka broker is running on remote host say, <IP_ADDRESS>:9092
I'm running below command locally:
java -jar jmx_prometheus_httpserver-0.3.2-SNAPSHOT-jar-with-dependencies.jar 7071 kafka.yaml
kafka.yaml is taken from: https://github.com/prometheus/jmx_exporter/blob/master/example_configs/kafka-2_0_0.yml
I am able to see few metrics on localhost:7071
# HELP jmx_scrape_duration_seconds Time this JMX scrape took, in seconds.
# TYPE jmx_scrape_duration_seconds gauge
jmx_scrape_duration_seconds 0.519737032
# HELP jmx_scrape_error Non-zero if this scrape failed.
# TYPE jmx_scrape_error gauge
jmx_scrape_error 1.0
# HELP jmx_exporter_build_info A metric with a constant '1' value labeled with the version of the JMX exporter.
# TYPE jmx_exporter_build_info gauge
jmx_exporter_build_info{version="0.3.2-SNAPSHOT",name="jmx_prometheus_httpserver",} 1.0
# HELP jmx_config_reload_success_total Number of times configuration have successfully been reloaded.
# TYPE jmx_config_reload_success_total counter
jmx_config_reload_success_total 0.0
# HELP jmx_config_reload_failure_total Number of times configuration have failed to be reloaded.
# TYPE jmx_config_reload_failure_total counter
jmx_config_reload_failure_total 0.0

Now, I wonder how would jmx get to know my kafka metrics - I have no where specified kafka broker address in jmx conf.

If https://github.com/yahoo/kafka-manager/issues/187#issuecomment-261467734 doesn't help try appending -Dcom.sun.management.jmxremote.rmi.port=9999 to KAFKA_JMX_OPTS. Worked for me.

JMX_PORT=8081 bin/kafka-server-start.sh -daemon config/server.properties > /dev/null 2>&1
可以通过这种方式指定JMX_PORT的值，而且不需要修改kafka-run-class.sh ，已经在本地验证。


Need to improve search helix log filtering

Need to provide more levers to reduce the set of builds that we are searching. Specifically need to:

Filter on test name the log is contained in
Filter on error message in the test the log is contained in

The underlying search also needs to filter out test results where the specific log kind is not present. For example when doing a testResults search filter out builds that don't have any test result logs.

It would be nice to be able to filter test failures by helix log (not sure if you would consider this the same feature request):
It seems the top-level log can be filtered on, but sometimes the relevant issues are buried.  Example: https://runfo.azurewebsites.net/view/build/?number=1580976
The helix console log shows a specific failure mode, but clicking on the test name shows a history of similar failures with the same "Message". I can filter tests by Message, but this is not granular enough to narrow it down to the same failure mode.


OCPBUGS-23900: config.openshift.io/v1/scheduler: allow profile customizations for DRA

For more info: https://kubernetes.io/docs/concepts/scheduling-eviction/dynamic-resource-allocation/
/hold

/jira refresh

Nit, do we have to use the acronym DRA? Why not spell it out ExperimentalDynamicResourceAllocation?

It's true ExperimentalDynamicResourceAllocation is easier to read. On the other hand the name is too long.

Also, given you've included Experimental in the name, what's the plan for promoting this? How will we transition from ExperimentalDRA to regular DRA?
Is this a tech preview feature?

Yes. It's currently upstream alpha feature. Normally, lifting a feature gate is sufficient for enabling it. However, in this case an additional scheduling plugin needs to be enabled alongside. So even when a customer/user enables the feature (through TPNoUpgrade) the scheduler operator still needs to make an extra step.

How will we transition from ExperimentalDRA to regular DRA
That's still to be debated. Either the new scheduling plugin will be enabled by default after GA eventually. At which point the experimental profile/field gets removed. If not enabled by default after GA, we will promote the profile/field and remove the word experimental.

Too long by what measure?

Too long for typing by hand. Although, that's probably not a blocking issue here. Lemme do some renaming.

Have you considered that the scheduler operator could observe the feature gate being present in the FeatureGate status and auto enable the value based on the feature gate status? At least for the tech preview version of this feature, it would be very obvious what needs to be done when the feature gate is enabled

Auto-enabling based on TPNoUpgrade was discussed before. The decision behind going with an extra step of enabling the feature for kube-scheduler was to allow to enable dynamic resource allocation as a set of functionalities. The DRA implementation itself is an upstream feature that requires additional components deployed. E.g. vendor plugins for NVDIA, Intel, etc. running on each node. So enabling dynamicresource scheduling plugin without these additional components may lead to pods staying in pending state indefinitely.

What do you expect the feature enablement to look like when you GA the feature? Do you expect that users will always opt-in? If that's the case, it's not the first time we've added a "You must set this feature gate, then enable the feature by this field that is only enabled in tech preview clusters".

Users need to deploy third-party plugins before DRA functionality is enabled in the kube-scheduler. Which will always be the case for GA until OpenShift start shipping a generic plugin by default. Which might not happen at all. So this extra step of configuration KSO to enable the plugin will always be required.

If you think after GA we will still want a knob, I think we want to add that now, but use the correct name, and mark it as a TechPreview only field/enum value

The way the plugin is enabled might change in the future. We might actually advocate for always disabling the plugin by default (even after GA) to enable it only when corresponding vendor plugins are installed. Also, the new field might be removed in favor of automatically detecting vendor plugins. Something to be decided in time.

/retest

Auto-enabling based on TPNoUpgrade was discussed before. The decision behind going with an extra step of enabling the feature for kube-scheduler was to allow to enable dynamic resource allocation as a set of functionalities. The DRA implementation itself is an upstream feature that requires additional components deployed. E.g. vendor plugins for NVDIA, Intel, etc. running on each node. So enabling dynamicresource scheduling plugin without these additional components may lead to pods staying in pending state indefinitely.

That seems like a valid argument. In TPNU you must first have the feature gate, then also flick the switch. Once this goes GA, you will still need to flick the switch, but, won't need the feature gate.

The way the plugin is enabled might change in the future. We might actually advocate for always disabling the plugin by default (even after GA) to enable it only when corresponding vendor plugins are installed. Also, the new field might be removed in favor of automatically detecting vendor plugins. Something to be decided in time.

In general we try to be explicit about APIs and having users opt in to features, so I expect we will still want the option in the future, but, sounds like that conversation is a long way off

@JoelSpeed is there a rule against backporting this to 4.15?

@JoelSpeed is there a rule against backporting this to 4.15?

In general, for something like this I expect it won't be an issue, but, before you start backporting, you will want to make sure that you have QE verify the 4.16 changes and that the feature is complete from that sense. And then I'd make sure you have PM and Staff eng buy in. Backports of APIs require a staff eng and API reviewer approval.

/retest-required

error running generator schemacheck on group config.openshift.io:
	could not run schemacheck generator for group/version config.openshift.io/v1:
		error in 0000_10_config-operator_01_scheduler-CustomNoUpgrade.crd.yaml: NoBools: crd/schedulers.config.openshift.io version/v1 field/^.spec.mastersSchedulable may not be a boolean
		error in 0000_10_config-operator_01_scheduler-Default.crd.yaml: NoBools: crd/schedulers.config.openshift.io version/v1 field/^.spec.mastersSchedulable may not be a boolean
		error in 0000_10_config-operator_01_scheduler-TechPreviewNoUpgrade.crd.yaml: NoBools: crd/schedulers.config.openshift.io version/v1 field/^.spec.mastersSchedulable may not be a boolean

The error is expected as .spec.mastersSchedulable is an older field. The new CRDs are duplicates of the original CRD which has already had the field as a boolean.

@JoelSpeed comments addressed. PTAL

/override ci/prow/verify-crd-schema
Failures are from pre-existing errors, future us will not be using booleans

/hold cancel

/retest-required

/backport release-4.15

/cherry-pick release-4.15


ON specific VM

how do I get metrics for specific VM fro mresource group

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

ID: c722777b-9914-5c57-b869-a92bb16e159e
Version Independent ID: 19b7e250-35b0-6e41-6662-b86791cf4c78
Content: az monitor metrics
Content Source: src/azure-cli/azure/cli/command_modules/monitor/_help.py
Service: monitoring-and-diagnostics
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@qwordy Please take a look

reassign this since user is trying to get metrics of VM. Hi @MyronFanQiu  could you pls help to confirm? if it's VM issue feel free to redirect the i ssue.

@5sfayas Hello. Currently, you can get metrics through
az monitor metrics list --resource /subscriptions/xxxxxxx/resourceGroups/myrg/providers/Microsoft.Compute/virtualMachines/myvm

@5sfayas Hello. Did you solve your issue?

IT worked