Not able to connect to CosmosDB using MongoDB API: com.mongodb.MongoSocketOpenException: Exception opening socket

Hi There,
I have created a spring boot application and we are trying to connect to COSMOS DB using MongoDB API.
I followed the steps that has been shown in this article however still getting an exception.
Please see the below code that I have implemented
SpringBootApplication Class--

@SpringBootApplication
public class DemoApplication extends AbstractMongoConfiguration{
public static void main(String[] args) {
	SpringApplication.run(DemoApplication.class, args);
}

}
@Override
public MongoClient mongoClient() {

	return new MongoClient(new MongoClientURI("mongodb://[user]:[pass]@[host]:[port]/?ssl=true&replicaSet=globaldb",MongoClientOptions.builder().sslEnabled(true)));
	// tried passing database name as well
	// return new MongoClient(new MongoClientURI("mongodb://[user]:[pass]@[host]:[port]/[db_name]?ssl=true&replicaSet=globaldb",MongoClientOptions.builder().sslEnabled(true)));
}

@Override
protected String getDatabaseName() {
	// TODO Auto-generated method stub
	return "db_name";
}/*

}
Exception:
com.mongodb.MongoSocketOpenException: Exception opening socket
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:67) ~[mongodb-driver-core-3.8.2.jar:na]
at com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:126) ~[mongodb-driver-core-3.8.2.jar:na]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:117) ~[mongodb-driver-core-3.8.2.jar:na]
at java.lang.Thread.run(Unknown Source) [na:1.8.0_191]
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) ~[na:1.8.0_191]
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) ~[na:1.8.0_191]
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) ~[na:1.8.0_191]
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) ~[na:1.8.0_191]
at java.net.AbstractPlainSocketImpl.connect(Unknown Source) ~[na:1.8.0_191]
at java.net.PlainSocketImpl.connect(Unknown Source) ~[na:1.8.0_191]
at java.net.SocksSocketImpl.connect(Unknown Source) ~[na:1.8.0_191]
at java.net.Socket.connect(Unknown Source) ~[na:1.8.0_191]
at sun.security.ssl.SSLSocketImpl.connect(Unknown Source) ~[na:1.8.0_191]
at com.mongodb.internal.connection.SocketStreamHelper.initialize(SocketStreamHelper.java:64) ~[mongodb-driver-core-3.8.2.jar:na]
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:62) ~[mongodb-driver-core-3.8.2.jar:na]
... 3 common frames omitted
I tried doing with simple Java project(without spring boot) described at below blog still no luck
https://azure.microsoft.com/en-us/resources/samples/azure-cosmos-db-mongodb-java-getting-started/
Any help would be greatly appreciated.
Thanks and Regards,
Akshay Pawar.

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

ID: c84e535d-3c81-b746-3021-767a0e849ce6
Version Independent ID: e831f5c9-a95c-5edf-8cb5-45970f5da8e9
Content: Build a console app using Azure Cosmos DB's API for MongoDB and Java SDK
Content Source: articles/cosmos-db/create-mongodb-java.md
Service: cosmos-db
GitHub Login: @rimman
Microsoft Alias: rimman

Hi there, my use case was with using mongo api.
How can I use mongo api and focus a query to specific partition.
Thanks
Get Outlook for Androidhttps://aka.ms/ghei36

From: Mike Ubezzi<EMAIL_ADDRESS>Sent: Friday, February 1, 2019 4:08:52 PM
To: MicrosoftDocs/azure-docs
Cc: Pradeep Bogati; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Not able to connect to CosmosDB using MongoDB API: com.mongodb.MongoSocketOpenException: Exception opening socket (#22953)
@pradeepbogatihttps://github.com/pradeepbogati Please take a look at this blog: CosmosDB Query with Partitionhttp://alexdrenea.com/2018/02/06/cosmosdb-query-with-partition/
If you send a partition key either as a ‘WHERE’ for SQL or ‘has(‘PartitonKey’, xyz) for graph the SDK will automatically forward that request to the specified partition.
For identical results, you can also specify the partition key as a FeedOption regardless of API used:
new FeedOptions() { PartitionKey = new PartitionKey(xyz) }
Is this information sufficient?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/22953#issuecomment-459868184, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AbinChZwx5SsePvdOUlOrwiGhQr5kvBtks5vJKzkgaJpZM4aLnCr.

For identical results, you can also specify the partition key as a FeedOption regardless of API used:
new FeedOptions() { PartitionKey = new PartitionKey(xyz) }


Add Bitcoin currency icon

The currency icon set misses the most important one: Bitcoin! ;-)
Here a couple of hints
https://cdn2.iconfinder.com/data/icons/money-operations/512/bitcoin-512.png
https://image.freepik.com/free-icon/bitcoin-digital-currency-symbol_318-53073.png

It's already in icon set.
Look into Brands or just CTRL + F (search in your browser) and type bitcoin


Refresh token is not properly set when using service worker

Issue and Steps to Reproduce
When using the service worker, the access token is translated to a protected value for security reasons, and then converted back into the actual token when sending them to the backend.
However this doesn't seem to be happening with the refresh token, this one is sent as the protected value itself and not reset by the service worker.
I have the follow oidc configuration:
import { Environment } from "./env";
import { OidcConfiguration } from "@axa-fr/react-oidc/dist/vanilla/oidc";

function getAuthority() {
    if (Environment.OIDC_AUTHORITY !== undefined) {
        return Environment.OIDC_AUTHORITY;
    } else {
        return `${window.location.protocol}//auth.${window.location.host}`;
    }
}

export function GetOIDCConfiguration(): OidcConfiguration {
    const data: OidcConfiguration = {
        client_id: Environment.OIDC_CLIENT_ID,
        authority: getAuthority(),
        redirect_uri: window.location.origin + "/authentication/callback",
        scope: "openid profile email roles offline_access full.access",
        service_worker_relative_url: "/OidcServiceWorker.js",
        service_worker_only: false,
    };
    return data;
}

On the backend I've set my access token to expire within 90 seconds to trigger refreshing very fast for testing purposes.
Versions
react-oidc: 5.13.5
Screenshots

Expected
The refresh token should be received in the backend as the actual refresh token value, not the service worker protected value.
Actual
The refresh token comes in as the service worker protected value.
Additional Details

Installed packages:

Dependencies:
    "@axa-fr/react-oidc": "^5.7.6-alpha1",
    "@emotion/react": "^11.9.0",
    "@emotion/styled": "^11.8.1",
    "@mui/icons-material": "^5.6.2",
    "@mui/lab": "^5.0.0-alpha.87",
    "@mui/material": "^5.6.4",
    "@mui/x-data-grid": "^5.12.3",
    "@mui/x-date-pickers": "^5.0.0-alpha.6",
    "@openapi-contrib/openapi-schema-to-json-schema": "^3.1.1",
    "axios": "^0.27.2",
    "date-fns": "^2.28.0",
    "formik": "^2.2.9",
    "i18next": "^21.8.9",
    "js-file-download": "^0.4.12",
    "jwt-decode": "^3.1.2",
    "react": "^18.0.0",
    "react-dom": "^18.0.0",
    "react-helmet-async": "^1.3.0",
    "react-i18next": "^11.17.1",
    "react-router-dom": "^6.3.0",
    "react-scripts": "5.0.1",
    "sass": "^1.50.1",
    "swr": "^2.0.0-beta.6",
    "typescript": "^4.6.3",
    "web-vitals": "^2.1.4",
    "yup": "^0.32.11"

Hi @Thodor12 , thank you for the issue.
Have you configured TrustesDomains.js?
For security access token are only send to domains declared in that file.
// OidcTrustedDomains.js // Add here trusted domains, access tokens will be send const trustedDomains = {     default:["http://localhost:4200"],     auth0:[] };

Yes, I have set that one, I have separated by authorization server and resource server, in development they run on port 7068 and 7200 respectively, both are added to the trusted domains

Btw, just in case the doubt maybe with the backend, I am using OpenIddict (for ASP.NET) and the response does correctly return a refresh token.

@Thodor12  if you update to v6.0.0beta3 whithout any code chang,e it should fix your problem.
Before v6 oidc server domain should not be declared in trusteddomain.js.

I updated to 6.0.0-beta3 but the service worker in that version seems not to function.
It crashes with the error:
OidcServiceWorker.js:238 Uncaught TypeError: Cannot read properties of undefined (reading 'startsWith')
    at OidcServiceWorker.js:238:57
    at Array.find (<anonymous>)
    at checkDomain (OidcServiceWorker.js:238:28)
    at OidcServiceWorker.js:279:13

At the function where it wants to validate the userInfoEndpoint, however my system does not expose a userInfoEndpoint because I rely on JWT tokens that already include all the user information.
As per the OpenId discovery document specification the userinfo_endpoint is RECOMMENDED, not REQUIRED.
Should I make a different issue to fix this or can you pick this up?

Sorry again @Thodor12  for that bug. No need another issue i will fix this for beta4.
Thank you for your feedback!

I commented the offending line to be able to test it, but right now the library doesn't even attempt to refresh the token, previously it at least attempted to make a refresh token request, now it does nothing?

Hi  @Thodor12 , have you tried the beta4?

This is strange if the timer do not start :/

The service worker is functional now, however the refreshing still doesn't happen

If you run the demo with your configuration, what does look like your logs ?

On the demo, by default it works and it continuously rolls my token over and over (because it's expiration is currently set to 60 seconds), so that works as expected.
I then updated the demo to use 6.0.0-beta4 and everythings stopped working

Hum, i have an idea where it can come from.
Do you have a sample an idtoken?

CfDJ8OpP9CaZdrhJkH68OTXlDjyZTaYry8DbdHQHLNqeH3yDg27CfsqvM28tzIkGlQM_7Vn0aLwoX7brP3USzJQaNBFoy4BwfBYyGy4LIColEg4JqF3jQ5jo4dKxmooCXJfKU87TYAaTEYIDmVROdtBONvkLrYDAJYFdSGQPvviblYxuOslq9qegIx_5SN7inBMjOIcqavZ2t-_ONX2yOVD-I0dsr5L1zwl6mtyY9Xbx03K0tGcKyhmpIdGDAVH89PElo6xOWbS7Yh75qO4rPMzi7xLBqD_lVOOHYWpKUPD4mLDv9T-gIb37N_toZ9sHrz3qscFtoVngmNBna-XAcLQzmrcDgVl9qYvKvE3-nzMHgQ6Tw8c8jUo-6C0EAf9ws6y1BcHevjSFDFqla4QaZoLCJchx2ES5uO3ALzQslGbXBINCZYiBBu6-o3FgxSm7UUKSrfUT0OSDG_i3xcutKmBDoQIxgU130LKtaJIioxdxWTjD8h5yDoLp3954tYLemBwJwLUm0UVw916JS0cXaARsNERQzaHoMZSebovsGYPaXas2ImKsQkUDrQqwy1SqAlPF8S-DKHWw4cQBs7xLMhlm_1AyAh4QS8MrBe6hIDggHaAgF8ETuM4T3ClDIdnNeXllZ64VMM-BUhMS7oZSf2vRfhZwlSY3B11XxI6S-Y32xMQF6GDTQXAJbWeJSKy9OROzqep8SpWD5rb9B9TEbCYovnNF9FAQ9I8TUjo7AE6gpt-KiWaO0wGur-25quc1tkPiJXufPA4TOSx2nncFaUcMK42ixhUp94A2MxoWzjNUlZV7v17OeNX_1Sa1vcu_4_trslHY2nHTll3TD_bwcxVUqhJMtHLis0WmarTidfz0X1nRXCZ3cTRKhl6oed5JIvYLNdZqX3iIMfeMWCpqxppr3MLL_fXD_S6e0FlRTgnVr_posg48wMquakCZbixwoeuVVZxA_wfevTbeVurSrpSvccT9WeI5851hX8jsimJQBWeIQQPe1hTYP57d3jbcgYb_juppkVh7whoYLTLIQjf5TuIRacROOyxYMsXMNi5QCN0sPMibna_7-VLfW9DH_pOKYMvmR10hrq-GYS2tM63Wy8ILM9XksmIXjnmTi-_aMq4dTqHVS6lv2RXcBLAiP__nI62_KfMfenDzAy7c-O5Y2qQ

This token format is identical to my access token. They're encrypted using ASP.NET Core Data Protection stack

Oh sorry, you said idToken:
eyJhbGciOiJSUzI1NiIsImtpZCI6IkNFNjQ1QUMzNkZCRDUxQzkzNzI1Rjk2MjIwN0ZDNTUxRjlCRTM3N0EiLCJ4NXQiOiJ6bVJhdzItOVVjazNKZmxpSUhfRlVmbS1OM28iLCJ0eXAiOiJKV1QifQ.eyJzdWIiOiI1IiwiZW1haWwiOiJ0aG9tLnZhbmRlbmFra2VyQG91dGxvb2suY29tIiwibmFtZSI6IkFkbWluIiwicm9sZSI6IkFkbWluIiwib2lfYXVfaWQiOiI4NzMiLCJhenAiOiJyZWFjdC1zcGEiLCJhdF9oYXNoIjoiSzhDM0lGTnVXZE5lWERRQUVjcWdrUSIsIm9pX3Rrbl9pZCI6IjU1NiIsImF1ZCI6InJlYWN0LXNwYSIsImV4cCI6MTY1ODU4OTU5NiwiaXNzIjoiaHR0cHM6Ly9sb2NhbGhvc3Q6NzA2OC8iLCJpYXQiOjE2NTg1ODgzOTZ9.h-VaxYT1MPeYaQsXkhn8uyKEuIAajWkTRyaXbIUREmy6tRGJFCFpJaGIkPTjAjZ5FGUFYVCHKnGyu4QN76BckZb2vQqRh_Ff74froKMdfedQs2yLFuJqfGj-6dWKY4FmwSnMk4Ibz58v0Mhm9ONe_UejatVOIoSi942UNQMAL0n8MDP2Vn5q8STWwnF8BAuIQ3nrfrOxOJYmvOjvBjMWe_5L7lPabxTPPCgxgQAHIrMM7Bdi-hOLU8Obbcd7b10liR59g2lh-PYpw-4yItOMn_bX5OOYhSVzM-mTyyB-C-W_Vdy7e0x7KmrhXl3SjWBbvpN7pHaoKT-Xbu90_r2WNQ

Thank you very much @Thodor12 . I understand what append.
Do you have a sample of the first token call after login.
You may remove refresh token value and set an old expired access token. I need to find information to know when access token expire.

This is the initial token call:
{
  "access_token": "CfDJ8OpP9CaZdrhJkH68OTXlDjw10gomah53FkxI3XnCIO7QHl-gUCxDvQgfAX9paDUEaS2ENTtALZlymYD2yNXB-LW_Fc_4mP5Tv9MO0nz5q7er2l-nwWA0JAU_sd1w_-v0w_-nfOhvw2NC_l5l8JvD0wjmXIygrBxEKT9SsMTcTcjI-_eX1dT12Lt-nI1t5CaPDn32YYpbNdpp0N7BXYY0lxpHhVvVJU0EYlt2Rl3uBbzD8YS3J7zcrPLJ_jNdEMYEyL1ziRvdXlDdgz4PNVZ4QIpPPKyISKcEeyOIjnSkoJSMC_9de2ddvo6b0f06iCahLJAQz6WXS4RcIy2Z5O9ykVik8w0h4bH5CKBC8HzYSAFrc9_Zq2c4ISbpLRplZRBp0yQEqC6mJ1nRdEtLr1iDitAUBAD6fZRQvwwiCsC3WK8hCPdPLkBPWn2RYojDLED_7Jxtz-AB3UhTOC_qVPbRWxS2SqSUq_Guqf-S4FwNtMjzo39CeF9J0WJtsd3AMBI73986iqJ-4j0idgjEnMWD4QiY_h7GosegPrYb8Iia9HJK8YMpq-PE9QFEyrgbQQKqs_0cGMRwUYF7sdO3dbhBTZ_p_eMKF4vxbhUHKLzEmcbmjZdVdojt2CCS8BjmtmSSCScaQU4CnDSfFOalpsIevHhY1NqQ7QUPCdPJTLZXsuQ4nC2wDxI2FSKFkmwk0ilFlJUDmQi5QLhbu1fuDkNWb5E",
  "token_type": "Bearer",
  "expires_in": 60,
  "scope": "openid profile email roles offline_access full.access",
  "id_token": "eyJhbGciOiJSUzI1NiIsImtpZCI6IkNFNjQ1QUMzNkZCRDUxQzkzNzI1Rjk2MjIwN0ZDNTUxRjlCRTM3N0EiLCJ4NXQiOiJ6bVJhdzItOVVjazNKZmxpSUhfRlVmbS1OM28iLCJ0eXAiOiJKV1QifQ.eyJzdWIiOiI1IiwiZW1haWwiOiJ0aG9tLnZhbmRlbmFra2VyQG91dGxvb2suY29tIiwibmFtZSI6IkFkbWluIiwicm9sZSI6IkFkbWluIiwib2lfYXVfaWQiOiI4NzMiLCJhenAiOiJyZWFjdC1zcGEiLCJhdF9oYXNoIjoidTFkZVpGZmxsbUVQLU8wZ1FXU2RsUSIsIm9pX3Rrbl9pZCI6IjU2MCIsImF1ZCI6InJlYWN0LXNwYSIsImV4cCI6MTY1ODU5MDIzNiwiaXNzIjoiaHR0cHM6Ly9sb2NhbGhvc3Q6NzA2OC8iLCJpYXQiOjE2NTg1ODkwMzZ9.XVrj0t7m4Xpf4xfQ6z-ZUD4PXes63sQD_Yz4tDtqxiTgb_MdNNJgByT2gJlWoBgo1m_OphR8q4DGVvjc8r3e4yzuCf3mjpiMD4-K9g3Og5AmP_C-cknMUe0zAOo5To1tn8FghEd0mY-gzJo70x5KXKsL5wl45dqRvXfVjlmAR8u-BqMhGmKLOO7BZCETftyUNAICqfJPe-eEkkTo5RzCYuEo6N4trdRmpbap0W3PK3GOLyLEzYGmkxwG4LqfEs09hzSCrpk_Y4GCbQH0X-NNXC4xLev7rXw58R5vv7K1RRFRRN_19PlooDVTjNwOBrSfHop3mr8KeLwcEbPPH8h5_A",
  "refresh_token": "CfDJ8OpP9CaZdrhJkH68OTXlDjz5wKJ8uZfoRgBiUfHIh9KcYOIyiClfOJzFW2hpDh5PjggQU6FmkOjuau5xhMohp3XqnuucAjkfCFcV-nbIUxYh0mSl_IyEkA0XkLL55qkm-sLkM56dbd0wIp2lrb2iv79Lo7UK90ceI-5IdlTuuW1sX2hQzZkLUd6yjIKCxXF2l90UxJ0geQ8TTKM1iusavoOvVxdnYVeIy5ZqBs7iyjQlqWAW5IMHzbsH4tGUe5Uzpud2aNNIRxyfDrYfVQvfhTzCeCl1p0XJr6zqoq6vFkLzbei6K7IoVwl9v8s-oiwJQeEtO3JnKe-eUYpESJfYocJ2TODom13IReT37-VKMbuy82xVuABv5JIesster8AbJrq2hFfe35qaqIjL7-syuRCphy4Uo3v9Kb0WqXIwZqHrfwR6ZC0UXoe1BqjDLTQFoQzRCYR1ldquA5IW0HdaHDe1j-_kA7KTNDPiGC5IzIWKd_p_Q6Lx_7J1O44GqmELT1V2o16Zz9D4BHl4LjpN0xgrBM9t2_J7kBLEiO1hoddJpWgQh12BDGdj80VzHxUMveK3HcVlKdpPQsN7CuvnsEUuZ2zcGZLh9LWSFW8l1LoIqxl_mGt1h5izqdkVMAdEaTKLx_kajy9eRer0tx66x13xCggJ59zb3dJoZhq0v6oZX9ulvTg8K8FdVjTNyJ6NYS-JqqT6enL3Tc8AHXTQGEbc6Ic70KmZLMnyFPLskoieBiGdllC4df7ZXXTONlbFfCLepZ7OPPsp5VL3BN9aarB0Wfh699xYt_YbgP6fHFGQO1wGYSVRMzk_KThJK5C6SAqRI_L_4xDfooBLysx34wzWORgkroK6MZGxwKHOMLY8KvKdmnJbLOybYze3UT5LR-d3JcesjvkfvoeLOJGwsKVtamgwoV_C3eRSbhksh3hLGgnZmsWHNS8kFhcOo9db3BV7FD06BEcn5TpHNg2vm3miR2-wfQobUGXFc0caCrLld6DUJ9C1po3J1qpTQnSxMkAnfstmpMcWNfD0HPlsRQ3E4e1yNU_Y-d4Bf4ahUnEJkzOf_-DbwZGykt_ISgv4ZiQJbcls632Om__HgVVNEKESJmIdfnEmHfB23JuEdphVWGqLWf0FVDyQYbfoviqdljWMu2CbW2bemW-sZJCPxPU"
}

I don't care about any of the tokens, this is just a testing environment

Sorry, that was the response, this is the form data input:
grant_type: authorization_code
client_id: react-spa
redirect_uri: http://localhost:3000/authentication/callback
code: mCbfs6Zmtb4Au-IRja9vKrD-Ov0ZQQjZv8HQiONt2Yw
code_verifier: 30Aux9eTElGqOOp901gt9KRA5YpaE2lRXn7veEaHw6QF5HflN5OUqCa67GQBXxCtCOrBiHCBG6cyQrAPQNlwTdlaozYmMovzDHE8QUf1NFkVTGxD3nd37OTLuu60XC9O

I just noticed that requests that are being made to the OidcKeepAliveServiceWorker.json are resulting in errors (infinitely pending, then failing).
Could that have something to do with it?

Hi @Thodor12 , thank you very much for all your information and your help.
OidcKeepAliveServiceWorker.json is a fake request in order to keepalive the service worker. It fail when window is reloading, but it does not matter.
I just publshed version 6.0.0-beta7 which should fix your issue.

with that commit https://github.com/AxaGuilDEv/react-oidc/pull/817/commits/6ef4da5d12442f9709a700c38185da4c4cce74ce

Checked the commit out, looks good, however for people that do use JWT tokens, and not encrypted tokens you probably want to make use of the iat claim: https://datatracker.ietf.org/doc/html/rfc7519#section-4.1.6
This won't be for me since I have that encrypted token but could be useful for others

@guillaume-chervet Unfortunately beta7 still had no effect, the tokens still won't roll over.
I have attached the onEvent method like the demo application does too, I can in fact see the token_timer, however it's timeLeft is really high despite only having a 60 second expiry time on my token, I don't think the expiresAt calculation is going completely correctly if I'm being honest.

@guillaume-chervet I found the issue (finally), turns out the backend decouples the lifetime of the access_token and id_token into 2 separate things, useful but not well documented.
The default lifetime for the id_token turned out to be 20 minutes, and the access_token only 1 minute.
So this isn't really a problem with react-oidc anymore, I have managed to solve it now.
Howver the following question, we can still see if a request ends in a 401 through our own code, is there a way we can manually trigger a refresh using the refresh_token and retry?

Thank you again @Thodor12  for your information. Beta 6 does not use idtoken information.
It may work for your use case. You may set       refresh_time_before_tokens_expiration_in_second: 20
In your configuration.
I will study how to retrieve well all token expiration date.

On a different note, in v5 I could use Axios using:
    const { accessToken } = useOidcAccessToken();

    const axiosInst = useMemo(() => {
        const config: AxiosRequestConfig = {
            baseURL: Environment.API_HOST + "/api",
        };

        if (accessToken) {
            config.headers = {
                Authorization: `Bearer ${accessToken}`,
            };
        }

        const client = axios.create(config);

        client.interceptors.response.use(originalResponse => {
            handleDates(originalResponse.data);
            return originalResponse;
        });

        return client;
    }, [accessToken]);

    return axiosInst;

The accessToken here would be the service worker protected value but the service worker would replace it with the correct token.
However this functionality seems to be broken in v6, the service worker no longer intercepts the requests? Resulting in all requests ending in a 401, how do you properly use Axios?
I dislike fetch and don't want to use it because the API is quite bad.

Hi @Thodor12 , the same behavior sould happen in v6.
Do you have somewhere on github the code of your oidc dev server?
It may be quicker to reproduce all the problems.

I set up a more robust algorithm in beta 8 : https://github.com/AxaGuilDEv/react-oidc/pull/817/commits/5e76b6dbf25f1cce6dd6ff9f65643cf04b217033

I will grant you access to the 2 repositores, backend and frontend so you can take a look.
Can I contact you elsewhere which is a bit faster in terms of communication?

Hi @Thodor12 , thank you very much.
I will try to create a slack and look a your code.

Just write down your email and I can invite you into a slack group, then we can continue discussion in there, alright?

My mail is guillaume.chervet at gmail.com.
I am in holiday, i won't be a lot in front my computer before next week.

@guillaume-chervet Hey, you managed to take another look at Slack to check if you could manage to get my application running? If you're busy that's alright, still attempting to see if I can get it fixed myself but no progress yet.

Hi @Thodor12 , I'am sorry i will be 2 weeks more in holiday (I have worked that previous week) on the beach :)
Did you tried last version 6 ? I think it should fixes many things.

Your code you give me access at front side looks good.

Hey, I updated to 6.0.12 and it seems to be properly working now.
The token now automatically rolls if it expires, so that's good.
However 1 odd thing that I noticed, if I refresh the page normally, the page reloads properly and the backend serves the content directly.
But if I hard reload (CTRL + Shift + R) the page that it loads results in a 401, because the token is not loaded.
But when I then reload the page normally again, it works again??
It looks like on a hard reload the service worker does not get initialized on time because I do not see the service worker modifying any requests in the network tab, but on a soft reload it does modify them properly

Oh, nevermind, turns out this is intended behaviour: https://web.dev/service-worker-lifecycle/#shift-reload

In that case everything works like a charm now, thank you for all your support and effort and enjoy the rest of your holiday 😄


[FEATURE] Add Dutch (nl) locale

Category:
Feature
Overview
Create nl.json in locales.
Code Quality Checklist

[x] All changes are backwards compatible
[x] All lint checks and tests are passing
[x] There are no (new) build warnings or errors
[ ] Bumps version, if new feature added

Awesome, that looks great- thanks so much :)
Merged


Table state persisting in url

See if it is possible to save table state in url and load it when user comes back via previous-button or link. It's not necessary to yet implement all of these in a functional way, but to be sure that they can be implemented with the current table choice.

[x] Column filters
[x] Current page / page size
[x] Sorting
[x] Combination of these: If all of these have some setting, will the user see the same thing when coming back

Seems to work an is not too complicated.
However, since the table (at least by default) works by instantly updating the table after changes like one character is made to filter, it may not be sensible to save all the url changes to history. Also, because the history is the browsers history this might make the history a mess to navigate. Ask customers later when the feature is more fleshed out, if its ok not to persist the tables internal changes in history every time, but only the last state before going to another view or the individual item page.

The setting "autoResetPageIndex" had to be turned false. Otherwise it would always reset pageIndex to 0 on first render, after reloading state from url. It works now, but it's not known if this will end up having adverse effects: documentation said that this setting prevents user being shown empty pages on certain changes, I did not get this by testing but it could happen.


edac: ibecc: Add support for EHL SKU13, SKU14, SKU15

Add support for missing EHL SKUs. The information about SKUs is
already public and available in Linux kernel:
https://github.com/torvalds/linux/blob/38f80f42147ff658aff218edb0a88c37e58bf44f/drivers/edac/igen6_edac.c#L197-L208

@finikorg do we want to backport this to 2.7?

@finikorg do we want to backport this to 2.7?

Yes, I got such request, this can be done after PR is merged?

@finikorg I added the backport label so that a PR will be automatically created when this is merged. However, you need to open a corresponding issue before the backport PR will be accepted.


Adding support to pass config variable in the publish cmd as a flag. More info b/330606878

Support config variable as parametes of integrationcli CLI
Goal: avoid override of config variable value in the config variable file in cicd pipeline

cmd sample:
integrationcli integrations versions publish -p standalone-ip-prod-testing -r us-east1 -t $(gcloud auth print-access-token) -n deep-config-var-cli-test --config-vars-json<EMAIL_ADDRESS>-s 1 --api autopush


Avoid piping into anonymous functions

https://app.asana.com/0/555089885850811/1207647461641385/f

Use function names instead of Kernel.then

Anonymous functions make sense when they are doing something very basic that isn't particularly reusable.


Age requirement text format

For the Age requirement information the format/logic for the age range information should be, using the info on the sheet:
"Age requirement: [Age min]-[Age max] (until your [Age max+1][suffix] birthday)"
The age max is always an inclusive number. I would prefer that we didn't show any ages that can't access the service, which is why we want to use inclusive numebr sin the age range, but the age range is so often misused by organizations by including the year older than can access the service, that the clarification has always been helpful.

Thanks, Jake Are you able to do a refresh on the ages? AFC maximum age is 1 year high - I know doobneek had all their upper bounds too high, but they edited them last week.

Fixed

Fixed in a7479293c82707c19ebdc91686772210f7e1c160

@adambard1 This is ready for re-review


Great article but useless for beginners

[Enter feedback here]
Great article but useless for beginners. So where can I configure this settings from?

admin.microsoft.com
endpoint.microsoft.com
portal.azure.com
security.microsoft.com
etc

Thanks

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

ID: 6443e532-640d-81c0-8215-b711bd1977d4
Version Independent ID: fc504984-91d7-b586-04ec-4c751fb48998
Content: Windows 10 Subscription Activation - Windows Deployment
Content Source: windows/deployment/windows-10-subscription-activation.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

@Anoni-Mouse Thank you for your feedback. The setting mentioned here - https://learn.microsoft.com/en-us/windows/deployment/windows-10-subscription-activation#how-it-works is through admin.microsoft.com
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @Anoni-Mouse Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


ClusterFixture implementation

Implement the ClusterFixture so we can start automating deployment related unit tests.
Cluster based testing is a little different from normal unit tests because cluster testing requires specific environmental configuration: configured hypervisor hosts, specific IP addresses suitable for the current LAN, credentials for clouds and hypervisors,... and these will need to be configured somehow for each machine running tests.  On top of this, cluster tests will be quite slow compared to normal unit tests, taking several minutes to spin up and reset clusters.
So we're going to disable cluster unit tests by default for most users by requiring the existence of the NEON_CLUSTER_TESTING and then marking test methods with the new [ClusterTest] and [ClusterTheory] attributes which will skip tests unless this environment variable is defined.  ClusterFixture will also disable itself when the variable isn't present.
The next question is: How do manage cluster creation while balancing safety and test reliability?  We'll have three basic test scenarios:

Tests that verify cluster deployment
Tests that verify functionality within an existing cluster
Shared test cluster where tests are executed in unique namespaces

For the first scenario, we're obviously going to be deploying clusters and the issue here will be what to do with VMs and other resources that were deployed by previous test runs and weren't deleted due to test failures or other problems.  We want to avoid having to manually intervene in situations like this, so the fixture will need to be able to remove resources existing conflicting clusters automatically.  For hypervisor hosted clusters, we'll delete conflicting VMs by cluster prefix.  For cloud hosted clusters, we'll delete everything in the cluster resource group.
The idea behind the second scenario is to have one or more pre-provisioned clusters ready to execute unit tests and then use cluster reset to put the cluster into a known (factory default) state.  This will be much faster than deploying a cluster from scratch.  It would be really nice though if ClusterFixture could deploy the cluster if it doesn't exist and also detect changes between the cluster definition required by the test class and what's currently deployed and redeploy the cluster to match when these differ.
We also want unit tests to be blocked when the target cluster is locked.  Note that this check can only be performed on healthy clusters (where API server is responsive) which means that for unhealthy clusters, we'll have to assume that we can blow them away and redeploy, which is a bit of a risk.  We'll need to be very careful about using cluster VM prefixes that will never be used by production or other important clusters as well as ensuring that we don't intermix production and test clusters on the same hypervisor hosts.
The third scenario above is interesting but we're going to set this aside for now.  The idea here is to deploy a larger test cluster that can be shared amongst multiple developers and/or test runners.  This would be suitable more for application testing where ClusterFixture would create a unique namespace for each test run and then remove the namespace afterwards.  The tests would need to take care to not modify global cluster state (should be enforced via RBAC).  We'd also need to be able to remove namespaces orphaned due to test crashes, etc.  One way to handle this would be to have ClusterFixture add a well-known config to the namespace with a delete-after timestamp and then have neon-cluster-operator remove namespaces that have this config and enough time has passed.  We' probably deploy and maintain this cluster manually.
We're going to track scenario 3 here: #1500
Test Profiles
We're going to use neon-assistant (an internal tool) to manage testing profiles for different user workstations as well as test runners.  This is currently restricted to project maintainers but eventually, we'll need a solution that can work for other people as well.
Work Items

[x] Test case attributes that skip tests when NEON_CLUSTER_TESTING environment variable does not exist

[x] [ClusterTest]
[x] [ClusterTheory]
[x] NEON_CLUSTER_TESTING:

[x] Update buildenv.cmd to define NEON_CLUSTER_TESTING
[x] Update WRT servers: jumpbox-00, runner-00, runner-01
[x] Home workstation
[x] Home laptop
[x] Tell @marcusbooyah

[x] Add TestTrait.NeonKube

[x] Add the new TestFixtureStatus.Disabled enum value and have ClusterFixture.Start() return this when NEON_CLUSTER_TESTING is not present
[x] ClusterFixture.Start() options:

[x] Force removal of VMs with specified prefix or in resource group
[x] Require cluster login for existing cluster and ensure that cluster is unlocked before proceeding
[x] Options to retain an existing cluster vs. removing and redeploying
[x] Specify ClusterResetOptions that ClusterFixture.ResetCluster() will use to reset the cluster.

[x] Implement ClusterFixture.Reset()
[x] ClusterFixture.Dispose() should remove or retain cluster based on options passed to Start()

[ ] Test on XenServer
[ ] Test on Hyper-V

DONE!  This one has been open for a very long time.  Nice to be finally done.


Ipmlab doesn't quit after  pressing Quit button

Did the following:

Launched Ipmlab
Created new batch
Imaged one floppy
Pressed Quit

After confirmation dialog, Ipmlab doesn't quit (but Quit button is disabled).
Looks like it's waiting for an (non existent) imaging job to complete.

This happens only when SocketAPI is enabled, and is caused by sth going wrong here:
            if config.enableSocketAPI:
                self.t2.join()

Added some debug code:
https://github.com/KBNLresearch/ipmlab/commit/9d543b94744d04f5826e88113beca4334c6b27a4

After commenting out the self.t2.join() statement Ipmlab closes normally, but not sure if this doesn't result in remaining zombie proceses (can't see any in Windows task manager). So do we need this?
If yes, self.t2.join() should also be added to if not config.readyToStart block, since socket server is already running in that case as well.

From the docs:

join([timeout])
Wait until the thread terminates. This blocks the calling thread until the thread whose join() method is called terminates – either normally or through an unhandled exception – or until the optional timeout occurs.

Since this is a server thread that continuously scans for incoming socket requests, it never terminates, and hence the application will freeze indefinitely.

Removed thread join:
https://github.com/KBNLresearch/ipmlab/commit/8bd6746a1efcc407b6e6afb7dc789698f854da70


TagBot github action?

AFAIK the released version does not support tagbot as github action?

Released version no, master branch yes

Yeah that is a problem.
We need to get this release out the door

Indeed, if I'm lucky I'll have time to fill in the missing pieces this week.

Something I want to hitch on here is the awkward interaction between TagBot and Documenter as github actions.
From here an action can't trigger another action if they are all on secrets.GITHUB_TOKEN. This means that to trigger release builds for documentation you'd have to attach a personal access token. Otherwise users have to manually checkout the TagBot tags, build documentation, and put it into gh-pages branch with manual organization.
I don't know (and I doubt) if there is a good way to solve this in the template, but it would at least be a nice piece of documentation to have.

It is already documented. See:

https://github.com/JuliaRegistries/TagBot/blob/master/README.md#personal-access-tokens
https://github.com/JuliaRegistries/TagBot/blob/master/README.md#ssh-deploy-keys

bump

Gonna close this, track #148 or #145 instead


Remove extraneous dss! and post_explicit! calls

This PR removes extraneous dss calls. Tested out in https://buildkite.com/clima/climaatmos-ci/builds/13595, results look like they've only changed by machine precision.

Results look good.

bors r+

bors r-

I'm just going to manual merge


Improve sample data view

Hi,
Is your feature request related to a problem? Please describe.
When the users see the data, even if they are few (50 rows for example), it is very frustrating because when the table has more than 12 columns you have to scroll down to the bottom of the table to find the horizontal scroll and move it.
Describe the solution you'd like
If the column names could be left fixed, even the header of the whole page, it would improve the user experience.

For example in snowflake, the experience for viewing content in the table is quite good.

thanks in advance
Carlos

Hello @triquinielas , Thanks for filing the issues.
I think you don't have to scroll down to the bottom you can directly scroll to the right using a mouse or touchpad.
For reference, I have attached the video.
https://github.com/open-metadata/OpenMetadata/assets/59080942/b7159e10-64aa-4432-92f9-ada4164568ce
Let me know if you are looking for something else, happy to help.

Closing this issue, @triquinielas, if you are looking for something else then feel free to re-open.


gffutils may have a bug that limits its applicability on parallel systems

gffutils is currently used for gtf file handling for example in bcbio's cufflinks module. It currently may have a serious bug due to a temporary directory path being hardcoded into the gffutils sources, so that multiple parallel gffutils database creation steps executed on the same machine write (and overwrite) the same file in local /tmp. Since the file in question is an intermediate textfile, this error will likely be silent and result in missing transcript annotations for cufflinks.
I added this issue here in order to make resolution of this error tractable.

The error has been resolved upstream in the gffutils repository, but the updated version is not yet on pypi.


Morph pivot table name conventions wrong when using MorphPivot model

Laravel Version: 9.25.1
PHP Version: 8.1.9
Database Driver & Version: N/A

Description:
You can tell a morphToMany or morphedByMany relations to use a Morph Pivot model by using a third parameter as the Model class name. This will also set the pivot table from it.
return $this->morphToMany(Tag::class, 'taggable', Taggable::class).

The problem is that Eloquent tries to find the subscription table, where as it should be subscriptions. This is becase getTable() in a Pivot|MorphPivot model doesn't returns the model plural, but rather the snake-singular.
class Post extends \Illuminate\Database\Eloquent\Model {
    public function tags()
    {
        return $this->morphToMany(Tag::class, 'taggable', Taggable::class);
    }
}

Post::find(1)->tags()->dd();

// "select * from "tags"
//    inner join "taggable" on "tags"."id" = "taggable"."tag_id"
//    where
//        "taggable"."taggable_id" = ?
//    and
//        "taggable"."taggable_type" = ?"

Here, the table should be taggables instead of taggable. This would force the developer to, unexplainably, set the table name property in the pivot model.
What it should happen?
If the developer is setting the morph pivot model, it should always use the plural instead of a two-model-junction to guess the table. This shouldn't affect the normal pivot model (for belongs to many).

Heya, thanks for reporting.
We'll need more info and/or code to debug this further. Can you please create a repository with the command below, commit the code that reproduces the issue as separate commits on the main/master branch and share the repository here? Please make sure that you have the latest version of the Laravel installer in order to run this command. Please also make sure you have both Git & the GitHub CLI tool properly set up.
laravel new bug-report --github="--public"

Please do not amend and create a separate commit with your custom changes. After you've posted the repository, we'll try to reproduce the issue.
Thanks!


site.yml management at the outside of vccw.

I had wanted to manage my project like below:
my-project # <- git
├ vccw/ # <- e.g. submodule
├ site.yml
└ wordpress/

By defined like follows, wordpress/ can be managed I want.
# site.yml
synced_folder: ../wordpress

But we could not of cours define at site.yml where site.yml is.
At this change, writing one line in ~/.vccw/config.yml, we'll be able to manage site.yml at the outside of vccw.
# ~/.vccw/config.yml
site_config_dir: ../ # Relative path from Vagrantfile

Thanks for PR. But we have another idea. 😄

I'm looking forward it :)


Admin issues when loading ballots etc.

In election/controllers.py, we were determining api requests success
based on http success, not returned data success.  Fixed that.
In voter_guide/models.py we were referencing a variable that had not
been initialized, and were crashing.

👍


Add client IP as Template variable [feature req]

It would be useful to be able to use $CLIENT_IP in a template, and have it replaced by the IP address of the client being used to deploy the template.
The use case for this is X-Windows client applications.  We have a large app, that users currently run by using VNC to remote-control a virtual machine.  This is necessary because of the CPU requirements of the app, and for licensing restrictions.   It is possible to run the app inside a container with XWindows sending the display to the users workstation; however they need to manually specify the address of their workstation on service creation.  It would be helpful if it could be set to default to the client browser IP, for the benefit of users who do not know their IP address or how to find it.
Making the CLIENT_IP exposed to the template would help with any future XWindows app, or any other applications that needs to interact with a desktop.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Domain: Events

Event system. Assume that users exist and that users have a unique identifier.
Relevant issues can be found in https://github.com/dotkom/a3s
https://miro.com/app/board/uXjVO3y02Jk=/

Umbrella issue for Events


Add links to Replicate's mPLUG-Owl demo

Hi team 👋 ! This PR modifies the mPLUG-Owl README with links to Replicate's mPLUG-Owl demo.
I've added mPLUG-Owl to the Replicate platform so that our users and the greater community can experiment with this incredible model! Replicate is a serverless ML platform that lets you run models with a few lines of code. We currently have mPLUG-Owl running on A100s that will scale with demand.
I attempted to maintain the style and format you've already established in your README, but let me know if I need to modify anything!
We would also love to transfer the model to your group's namespace. If someone would like to create an account, we can handle the transfer of the model to your account. It's free, of course, and your model would be properly associated with your group (e.g. see Whisper here, for an example)!

Cool. Thanks for contributing the demo link.

@joehoover Since we would have a large update on the codebase that support huggingface natively as well as add the support for video input in the next few days. Would you mind supporting it as well once we have release the latest codebase?

Also it would be great if adding paper citation information on the demo page as well so others can easily find the paper. Thanks. 😄

Hi @MAGAer13 , awesome, thanks for merging! And I'll be sure to open an issue to update the model in our backlog.
In the meantime, it'd be great if you could open an account for your team at replicate. Just pick a username that's associated with your group, I can move the model's ownership to your namespace!


docker-for-win: Xvfb in image provided to xpra on host

Coming from #121
Setup example to run Xvfb in docker image used by xpra on host.
Dockerfile:
FROM debian:stretch-slim
RUN apt-get update
RUN apt-get install -y xvfb
CMD Xvfb :20 -listen tcp -screen 0 4720x3840x24 -ac

Script:
# x11docker running Xvfb.
# read and --showpid1 serve to continue script after container is up and running
read dummy < <(x11docker --tty --name xvfb --showpid1 -- x11docker/xvfb)
# Get IP of container:
Containerip=$(docker inspect --format '{{ .NetworkSettings.IPAddress }}' xvfb)
# Run xpra server
xpra start $Containerip:20 --use-display

xpra client fails here with: unknown format for display name: <IP_ADDRESS>:20. I am not sure if this is due to my recent switch to the python3 version. If I provide DISPLAY without IP I get  cannot find live server for display :20

Feel free to re-open if this is of interest again.


Add eslint a11y plugin

Closing as a duplicate of:

https://github.com/vegaprotocol/frontend-monorepo/issues/618

The console lite team are picking this up


v2.0.1 mainnet upgrade

Do not merge this before the network has been upgraded.

for Hardware::CPU.intel? -- should this check be also on Mac + have else branches for arm?


Add "geo", "tel", and "sms" uri schemes

Allowing these three would bring Caja into the modern era of mobile web usage.
Please consider it.

UriPolicyNanny is old code; if this change has an effect then you're using the old ES5/3 branch which you should not be.
The place you want to update is in the top of domado.js, ALLOWED_URI_SCHEMES.
Also, please sign the CLA and ensure that your pull request has exactly one rebased commit.

Please squash to a single commit, correct spelling in your commit messages, and sign the CLA.

Working on it.

ok, I've got it all in one commit now. I'm not sure why this pull request is not updating to show that.
Also, I've signed the first CLA as my company "Cutting Edge Plumbing & Mechanical".

Also, please make sure you've entered your GitHub username in the CLA agreement.

I've signed it with the same e-mail and username, and have also changed the commit description.


Modified XML for B

This is modified GPO and Federal Register XML that's required to cleanly parse CFPB Reg B.

:heavy_multiplication_x: :m:  L


Feature/controllers

Description
This pull request addresses the requirements outlined in the project guidelines for creating controllers and views for the Blog app. Instead of using rails generate scaffold, I've manually set up controllers, routes, and views to handle the specified URLs as per the wireframes.
Changes Made

Created routes for the following URLs:

/users (All users page)
/users/:id (Single user page)
/users/:user_id/posts (All posts by a given user page)
/posts/:id (Single post page)

Implemented corresponding actions in the controllers:

UsersController for user-related actions
PostsController for post-related actions

Added view files for each action with placeholders in plain HTML, such as displaying lists of users and posts.

Additional Notes

All code adheres to the Ruby best practices as recommended in the project guidelines.
Linter errors have been addressed to ensure clean code.
A README file is included with setup instructions and project details.

Checklist

[x] Checked for linter errors and fixed them.
[x] Followed Gitflow by creating a separate branch for this feature.
[x] Documented the work in the README file.
[x] Manually created controllers, routes, and views.
[x] Implemented the four required URLs.
[x] Pushed all changes to this branch.

Screenshots

Please review this feature to merge this pull request into the develop branch and give me feedback to improve. Thank you in advance!
Greetings,
@ClaudiaRojasSoto

Thank you @anagudelogu.


Completed with all the functional mock illustration requirements.

No bootstrap used. (sticky header included), div created at top, before the header to make work the "back to top" links.

div created before header to make the "back to top" links. The header has a sticky property and the links were pointing to header section.


General PDF re-order/rename section headers to match journal PDF

Description
A few section headings on the general PDF need to be reordered and renamed to match with the Journal PDF.
Tasks:

[ ] Section "Algorithm Availability" needs to move within Data Access
[ ] Performance Assessment subheadings need renaming (remove "Performance Assessment").  The top level header remain as "Performance Assessment Validation."
[ ] Data Access subheadings need renaming. "Input Data Data Access" becomes "Input Data Access" and "Output Data Data Access" becomes "Output Data Access."
[ ] Remove section number from "References."

See below example for how it needs to look.
Acceptance Criteria:

[ ] General PDF is reordered/renamed to match example.
[ ] PDF downloaded and reviewed to make sure it is the correct order.

Hi @bwbaker1, we're assuming that these need to be changed in the view mode?

Section "Algorithm Availability" needs to move within Data Access
Could you explain why the heading structure needs to change?

@wrynearson This ticket is not a priority.  I'm closing it.


NoCheatPlus compatibility.

Would it be possible to add a hook compatibility for NoCheatPlus?
The cheat violation vehicle.vehicleenvelope seems to occur and randomly teleport players to a different location when they try to ride a mob. Disabling that violation check in NCP, players can ride again.
    vehicle:
      preventdestroyown: true
      enforcelocation: default
      schedulesetbacks: default
      morepackets:
        active: false
        actions: cancel vl>20 log:morepackets:0:11:i cancel
      envelope:
        active: default
        actions: cancel vl>100 cancel log:vehicleenvelope:0:11:i

I have no idea what vehicle.envelope even means. I generally don't support anti cheat plugins simply because some of the logic to make things happen gets detected as cheats. I have another plugin that let's you edit signs by right clicking them and NCP complains about it too.

NoCheatPlus has a compatibility plugin which can register hooks via an API I believe.
https://github.com/asofold/CompatNoCheatPlus
https://dev.bukkit.org/projects/compatnocheatplus-cncp/
This is the currently maintained fork of NCP I use since the main NCP repo is inactive.
https://github.com/CaptainObvious0/NoCheatPlus
@CaptainObvious0 has made some changes to vehicle envelop, so it could be likely that a tweak made is conflicting and reporting as a false positive. In the meantime, I just disabled the envelope check.

I edited at same time you commented. ^_^ See my edited message above.

I'll leave this open for now. Since both NCP and Ridables have APIs, when I get some spare time I'll see about making an add-on plugin that links the two plugins.

Vehicle.Envelope is just a fancy name, it just prevents speeding/flying while in a vehicle (Horse, minecart, boat)

@CaptainObvious0 has made some changes to vehicle envelop, so it could be likely that a tweak made is conflicting and reporting as a false positive. In the meantime, I just disabled the envelope check however.
Changes I made were reverted the next day. Unless you compiled it yourself within the time of the changes, you shouldn't have the changes effected. The changes also wouldn't have effected this issue.

I'll leave this open for now. Since both NCP and Ridables have APIs, when I get some spare time I'll see about making an add-on plugin that links the two plugins.
API should be fairly simple to implement into the plugin.  Take a look at the code: NCPExemptionManager Heres the wiki for the API: Link

And here's an example on how to implement it into your plugin:
`public static void exemptPlayer(Player player) {
NCPExemptionManager.exemptPermanently(player);
}
public static void unexemptPlayer(Player player) {
	NCPExemptionManager.unexempt(player);
}`

Let me know if you have any issues


Update display and rm2fb-client to v0.0.27

Added support for <IP_ADDRESS>9

LGTM tested both on <IP_ADDRESS>9 and <IP_ADDRESS>7 rm2


Player v Enemy collision

Player v enemy collision is not working as intended.
Expected behaviour is to deal 10 damage to the player, drop an item, and remove the enemy.

 for enemy in self.enemies:
            print(f"Player: ({self.rect.x}, {self.rect.y}), Enemy: ({enemy.rect.x}, {enemy.rect.y})")
            if self.rect.colliderect(enemy.rect):
                print("Collision Detected!")
                self.health -= 20
                drop = handle_drops(enemy.rect)
                self.drops.append(drop)
                enemy.kill()

This is not being ran, and I don't know why at this stage. Will look into this before v1.1.0

Issue resolved, needed to put in the main game loop.
        '''
        Checks for player v enemy collision.
        Upon collision, players health is reduced by 20,
        Enemy then drops a bonus, and is killed from the screen.
        '''
        for enemy in enemies:
            if player.rect.colliderect(enemy.rect):
                print("Collision Detected!")
                player.health -= 20
                player.xp += 10
                drop = handle_drops(enemy.rect)
                drops.append(drop)
                enemy.kill()


Forkchoice protoarray

Goal

Resolves #720
Need to implement restoring forkchoice in #911

The protoarray forkchoice implementation works fine with the new sync. I can sync till slot 10000 in ~48min.


Backbone.Events.proxy

Proxy events and arguments from one object to another. Usage:
var a = _.extend({}, Backbone.Events);
var b = _.extend({}, Backbone.Events);
b.proxy(a, 'event').bind('event', function() {

});
a.trigger('event');

Neat idea, but this would have to be motivated by specific use cases.
Proxying in general is useful, but is often implemented along a number of axes that this PR doesn't address.

Listen to "all" events, and only pass some along.
Don't proxy through events synchronously, but _.defer them until the next tick instead.
Proxy events, but mutate arguments in a relevant fashion (see Backbone.Collection).

I don't think that this specific and limited form of proxying is useful enough on its own without covering the other cases -- it's also not hard to write by hand. (pardon my coffeescript):
a.on 'event', -> a.trigger 'event'


[#99686132] Delete old Postgres backups

What
A new cron job is created which runs every day in /etc/cron.d/wal_e_backup_delete.
The cron job invokes WAL-E's delete subcommand which deletes all backups older than number we want to retain, as well as the archived WAL files older than that.
Based on a variable called wal_e_backup_delete_retain it will keep that number of backups and delete the rest.
How To Test
Go to your tsuru-ansible directory and change the version of ansible-playbook-wal-e to point to this PR in requirements.yml.
Install Ansible Galaxy requirements:
ansible-galaxy install -r requirements.yml --force

Then, provision the Postgres master. For example, given you have an AWS environment called michael:
ansible-playbook -i ec2.py postgres.yml -e<EMAIL_ADDRESS>-e "deploy_env=michael"

Now ssh to the Postgres box. You can find the IP by running something like ./ec2.py | grep postgres -C 2.
Make sure the cron job has been created:
ls /etc/cron.d/wal_e_backup_delete

Change user to postgres:
sudo su postgres -

Now create several backups by running the backup-push command:
/usr/bin/envdir /etc/wal-e /usr/local/bin/wal-e --aws-instance-profile backup-push  /var/lib/postgresql/9.3/main/

You can always review backups by running the backup-list command:
/usr/bin/envdir /etc/wal-e /usr/local/bin/wal-e --aws-instance-profile backup-list

Generate more than 5 backups and try running:
/usr/bin/envdir /etc/wal-e /usr/local/bin/wal-e --aws-instance-profile delete --confirm retain 5

Old backups should be deleted and 5 should be retained.
Who To Review
Somebody other than @RichardKnop or @russss.

The PR is cool, but it seems that WAL-E fails on Google when trying to delete, it gets in a infinite loop saying:
      HINT: A better error message should be written to handle this exception.  Please report this output and, if possible, the situation under which it arises.
        STRUCTURED: time=2015-07-30T16:26:21.219809-00 pid=21619
wal_e.retries WARNING  MSG: retrying after encountering exception
        DETAIL: Exception information dump:
        Traceback (most recent call last):
          File "/usr/local/lib/python2.7/dist-packages/wal_e/retries.py", line 62, in shim
            return f(*args, **kwargs)
          File "/usr/local/lib/python2.7/dist-packages/wal_e/worker/s3/s3_deleter.py", line 27, in _delete_batch
            bucket.delete_keys([key.name for key in page])
          File "/usr/lib/python2.7/dist-packages/boto/s3/bucket.py", line 602, in delete_keys
            while delete_keys2(headers):
          File "/usr/lib/python2.7/dist-packages/boto/s3/bucket.py", line 601, in delete_keys2
            body)
        S3ResponseError: S3ResponseError: 400 Bad Request
        <?xml version='1.0' encoding='UTF-8'?><Error>InvalidArgument<Message>Invalid argument.</Message>Cannot create buckets using a POST.</Error>

Seems that we hit the issue commented by @russss

:-1:
How to we address this issue? Do we try to investigate if it could be easy to fix in WAL-E?

I think the issue is in the boto library itself, when deleting buckets.

This works fine, but as described in the card we are facing this issue with the deletion on GCE which can be solved with a PR like this.
Talking with @brettansley , we will disable this feature for the time being in GCE, and create a card to enable it once the root issue is solved in WAL-E or depending libraries.
Because that, is OK to merge this, but we must explicitly disable this cronjob in GCE


Namadillo: Add proposals table pagination, fix pagination bugs

Note for testing: Needs the latest version of namada-indexer including https://github.com/anoma/namada-indexer/pull/75.

Changed

Bump indexer to 0.0.17 to get the all proposals endpoint.
Refactor TableWithPaginator to not create its own pages. It now just receives pages of items and lets its parent handle creating pages.

Added

Add pagination to the All Proposals table.

Fixed

Fix proposal count by counting all proposals, not just one page of proposals. These numbers are shown on the right panel of the Governance page under "Total Proposals", "Proposals in Voting Period" etc.
Fetch all validators, not just the first page.

This one also closes #916


krew repo

Please add to the krew repository

Hi @mrlioncub, when I created this repo (long time ago), there was already plugin in krew with very similar name - https://github.com/chenjiandongx/kubectl-images
But I needed something slightly different for the project I was working on. You can still install via brew (it is in the README). If you would still prefer krew, and do not think it will cause a bit of confusion with the existing project with similar name, I can add it later this week.

Thank you. I will wait

@mrlioncub kubectl image is now in krew, I'm closing this issue


Function parameters.json file being ignored in new deployment.

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
12.10.1
What operating system are you using?
Linux
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made.
Describe the bug
I have several lambda functions with parameters provided in parameters.json. Parameters.json is in the root of the function, e.g. amplify/backend/function/plateletAddNewTenant/parameters.json and contains data like:
{
    "plateletWelcomeEmail"<EMAIL_ADDRESS>    "plateletDomainName": "app.platelet.app"
}

In the past this is how I've provided environment variables to functions. Existing deployments and new deployments have worked with this setup.
Recently I updated my lambda functions to node 18 and also updates the build settings to use the latest image and CLI version:

However I receive this output on the Amplify console.
2024-03-17T20:21:45.455Z [WARNING]: ✖ There was an error initializing your environment.
2024-03-17T20:21:45.455Z [INFO]: 🛑 This environment is missing some parameter values.
2024-03-17T20:21:45.456Z [INFO]: [plateletDomainName,plateletWelcomeEmail,plateletDomainName,plateletWelcomeEmail,plateletDomainName,plateletWelcomeEmail,plateletSendFromEmailAddress,plateletSendToEmailAddress] do not have values.
                                 Resolution: Run 'amplify push' interactively to specify values.
                                 Alternatively, manually add values in SSM ParameterStore for the following parameter names:
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletAddNewTenant_plateletDomainName
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletAddNewTenant_plateletWelcomeEmail
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletAdminAddNewUser_plateletDomainName
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletAdminAddNewUser_plateletWelcomeEmail
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletAdminResetUserPassword_plateletDomainName
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletAdminResetUserPassword_plateletWelcomeEmail
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletSendUserFeedback_plateletSendFromEmailAddress
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletSendUserFeedback_plateletSendToEmailAddress
                                 Learn more at: https://docs.amplify.aws/cli/reference/ssm-parameter-store/#manually-creating-parameters
2024-03-17T20:21:45.493Z [INFO]:
2024-03-17T20:21:45.493Z [INFO]: Session Identifier: 787d8900-f996-4d45-8bb8-cbede870d338
2024-03-17T20:21:45.516Z [ERROR]: !!! Build failed
2024-03-17T20:21:45.516Z [ERROR]: !!! Error: Command failed with exit code 1
2024-03-17T20:21:45.517Z [INFO]: # Starting environment caching...
2024-03-17T20:21:45.517Z [INFO]: # Environment caching completed
Terminating logging...

I'm triggering these builds with pushes to github.
This is my amplify.yml:
version: 1
env:
  variables:
    REACT_APP_OFFLINE_ONLY: false
    REACT_APP_POPULATE_FAKE_DATA: false
    REACT_APP_DEMO_MODE: false
    REACT_APP_RESIZE_BUCKET_NAME: platelet-resize-bucket
    REACT_APP_DEMO_PROFILE_PICTURES_BUCKET_NAME: platelet-demo-profilepics
    REACT_APP_DEMO_PROFILE_PICTURES_BUCKET_REGION: eu-west-1
backend:
  phases:
    build:
      commands:
        - '# Execute Amplify CLI with the helper script'
        - npm install -g prebuild-install --unsafe-perm=true
        - amplifyPush --simple
frontend:
  phases:
    preBuild:
      commands:
        - npm install
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*
test:
  artifacts:
    baseDirectory: cypress
    configFilePath: '**/mochawesome.json'
    files:
      - '**/*.png'
      - '**/*.mp4'
  phases:
    artifacts: # arbitrary values (other than baseDirectory) bc amplify test phase will fail without them
      baseDirectory: ./
      configFilePath: '**/mochawesome.json'
      files:
        - '**/*.png'
        - '**/*.mp4'
    preTest:
      commands:
        - npm ci
    test:
      commands:
        - echo "no tests"

I am not committing team-provier-info.json and would rather these values are taken from the parameters.json file if that's possible.
Expected behavior
I would expect building to use the values in parameters.json for functions instead of saying they are missing.
Reproduction steps

Add a function to your project
Include parameters when creating the function
Create parameters.json in the function directory
Place values in that file.
Set up Branch autodetections in Repository settings (I have it set to production/**)
Push to a new github branch production/something

Project Identifier
No response
Log output

# Put your logs below this line

2024-03-17T20:20:05.760Z [INFO]: # Cloning repository: git@github.com:platelet-app/platelet.git
2024-03-17T20:20:08.673Z [INFO]:
2024-03-17T20:20:08.673Z [INFO]: Cloning into 'platelet'...
2024-03-17T20:20:08.674Z [INFO]: # Switching to commit: 6ec2d08f5a397fdc631ce3b1210a9d65e819a9b4
2024-03-17T20:20:08.725Z [INFO]: Note: switching to '6ec2d08f5a397fdc631ce3b1210a9d65e819a9b4'.
                                 You are in 'detached HEAD' state. You can look around, make experimental
                                 changes and commit them, and you can discard any commits you make in this
                                 state without impacting any branches by switching back to a branch.
                                 If you want to create a new branch to retain commits you create, you may
                                 do so (now or later) by using -c with the switch command. Example:
                                 git switch -c <new-branch-name>
                                 Or undo this operation with:
                                 git switch -
                                 Turn off this advice by setting config variable advice.detachedHead to false
                                 HEAD is now at 6ec2d08f print amplify version
2024-03-17T20:20:08.779Z [INFO]: Successfully cleaned up Git credentials
2024-03-17T20:20:08.779Z [INFO]: # Checking for Git submodules at: /codebuild/output/src1790987902/src/platelet/.gitmodules
2024-03-17T20:20:08.790Z [INFO]: # Retrieving environment cache...
2024-03-17T20:20:08.831Z [WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}
2024-03-17T20:20:08.832Z [INFO]: ---- Setting Up SSM Secrets ----
2024-03-17T20:20:08.832Z [INFO]: SSM params {"Path":"/amplify/dlkp8fs0a5r7s/production/another.platelet.app/","WithDecryption":true}
2024-03-17T20:20:11.434Z [INFO]: # Patching NPM package '@aws-amplify/cli' from 12.8.2 to 12.10.1...
2024-03-17T20:20:38.935Z [INFO]: # Installed '<EMAIL_ADDRESS>2024-03-17T20:20:39.035Z [INFO]: # Done patching NPM package '@aws-amplify/cli' to version 12.10.1
2024-03-17T20:20:39.052Z [INFO]: # Retrieving cache...
2024-03-17T20:20:39.091Z [INFO]: # Retrieved cache
2024-03-17T20:20:39.282Z [INFO]: BackendEnvironment name production/another.platelet.app for app dlkp8fs0a5r7s is invalid
2024-03-17T20:20:39.358Z [INFO]: Random environment name saloma generated
2024-03-17T20:20:43.789Z [INFO]: ## Processing Environment Variables
                                 # Set Environment Variable: REACT_APP_OFFLINE_ONLY
                                 # Set Environment Variable: REACT_APP_POPULATE_FAKE_DATA
2024-03-17T20:20:43.798Z [INFO]: # Set Environment Variable: REACT_APP_DEMO_MODE
                                 # Set Environment Variable: REACT_APP_RESIZE_BUCKET_NAME
                                 # Set Environment Variable: REACT_APP_DEMO_PROFILE_PICTURES_BUCKET_NAME
                                 # Set Environment Variable: REACT_APP_DEMO_PROFILE_PICTURES_BUCKET_REGION
                                 ## Starting Backend Build
                                 # Starting phase: build
                                 # Executing command: npm install -g prebuild-install --unsafe-perm=true
2024-03-17T20:20:45.365Z [INFO]: added 37 packages in 1s
2024-03-17T20:20:45.366Z [INFO]: 9 packages are looking for funding
                                 run `npm fund` for details
2024-03-17T20:20:45.371Z [INFO]: # Executing command: amplify --version
2024-03-17T20:20:46.617Z [INFO]: 12.10.1
2024-03-17T20:20:48.588Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2024-03-17T20:20:48.828Z [INFO]: Amplify AppID found: dlkp8fs0a5r7s. Amplify App name is: platelet-production
2024-03-17T20:20:48.872Z [INFO]: Adding backend environment saloma to AWS Amplify app: dlkp8fs0a5r7s
2024-03-17T20:20:54.205Z [INFO]:
2024-03-17T20:20:54.212Z [INFO]: CREATE_IN_PROGRESS amplify-platelet-saloma-202048 AWS::CloudFormation::Stack Sun Mar 17 2024 20:20:49 GMT+0000 (Coordinated Universal Time) User Initiated
                                 CREATE_IN_PROGRESS AuthRole                       AWS::IAM::Role             Sun Mar 17 2024 20:20:51 GMT+0000 (Coordinated Universal Time)
                                 CREATE_IN_PROGRESS DeploymentBucket               AWS::S3::Bucket            Sun Mar 17 2024 20:20:51 GMT+0000 (Coordinated Universal Time)
                                 CREATE_IN_PROGRESS UnauthRole                     AWS::IAM::Role             Sun Mar 17 2024 20:20:51 GMT+0000 (Coordinated Universal Time)
                                 CREATE_IN_PROGRESS UnauthRole                     AWS::IAM::Role             Sun Mar 17 2024 20:20:52 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
                                 CREATE_IN_PROGRESS AuthRole                       AWS::IAM::Role             Sun Mar 17 2024 20:20:52 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
                                 CREATE_IN_PROGRESS DeploymentBucket               AWS::S3::Bucket            Sun Mar 17 2024 20:20:52 GMT+0000 (Coordinated Universal Time) Resource creation Initiated
2024-03-17T20:21:19.223Z [INFO]:
2024-03-17T20:21:19.468Z [WARNING]: - Uploading files.
2024-03-17T20:21:19.760Z [WARNING]: - Uploading files.
2024-03-17T20:21:20.809Z [WARNING]: - Initializing your environment: saloma
2024-03-17T20:21:20.853Z [WARNING]: - Building resource api/platelet
2024-03-17T20:21:37.327Z [WARNING]: Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
2024-03-17T20:21:37.335Z [WARNING]: Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
                                    Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.
2024-03-17T20:21:38.952Z [INFO]: ⚠  You are using the "pipelineFunctions" directory for overridden and custom resolvers. Please use the "resolvers" directory as "pipelineFunctions" will be deprecated.
2024-03-17T20:21:39.020Z [INFO]: ✅ GraphQL schema compiled successfully.
                                 Edit your schema at /codebuild/output/src1790987902/src/platelet/amplify/backend/api/platelet/schema.graphql or place .graphql files in a directory at /codebuild/output/src1790987902/src/platelet/amplify/backend/api/platelet/schema
2024-03-17T20:21:39.021Z [WARNING]: - Building resource auth/platelet61a0ac07
2024-03-17T20:21:42.123Z [WARNING]: - Building resource auth/userPoolGroups
2024-03-17T20:21:45.275Z [WARNING]: - Building resource storage/plateletStorage
2024-03-17T20:21:45.337Z [WARNING]: ✔ Initialized provider successfully.
2024-03-17T20:21:45.455Z [WARNING]: ✖ There was an error initializing your environment.
2024-03-17T20:21:45.455Z [INFO]: 🛑 This environment is missing some parameter values.
2024-03-17T20:21:45.456Z [INFO]: [plateletDomainName,plateletWelcomeEmail,plateletDomainName,plateletWelcomeEmail,plateletDomainName,plateletWelcomeEmail,plateletSendFromEmailAddress,plateletSendToEmailAddress] do not have values.
                                 Resolution: Run 'amplify push' interactively to specify values.
                                 Alternatively, manually add values in SSM ParameterStore for the following parameter names:
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletAddNewTenant_plateletDomainName
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletAddNewTenant_plateletWelcomeEmail
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletAdminAddNewUser_plateletDomainName
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletAdminAddNewUser_plateletWelcomeEmail
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletAdminResetUserPassword_plateletDomainName
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletAdminResetUserPassword_plateletWelcomeEmail
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletSendUserFeedback_plateletSendFromEmailAddress
                                 /amplify/dlkp8fs0a5r7s/saloma/AMPLIFY_function_plateletSendUserFeedback_plateletSendToEmailAddress
                                 Learn more at: https://docs.amplify.aws/cli/reference/ssm-parameter-store/#manually-creating-parameters
2024-03-17T20:21:45.493Z [INFO]:
2024-03-17T20:21:45.493Z [INFO]: Session Identifier: 787d8900-f996-4d45-8bb8-cbede870d338
2024-03-17T20:21:45.516Z [ERROR]: !!! Build failed
2024-03-17T20:21:45.516Z [ERROR]: !!! Error: Command failed with exit code 1
2024-03-17T20:21:45.517Z [INFO]: # Starting environment caching...
2024-03-17T20:21:45.517Z [INFO]: # Environment caching completed
Terminating logging...

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @duckbytes :wave: thanks for raising this! While this approach is not officially supported for adding environment variables, you can get away with manually modifying amplify/team-provider-info.json and specifying key value pairs for your Function env vars. These will then be hydrated on init/checkout/pull and uploaded to SSM, which should resolve this issue.
Otherwise you can use amplify update function to CRUD env vars/secrets for your Functions https://docs.amplify.aws/react/build-a-backend/functions/environment-variables/

Thanks @josefaidt .
Originally I had not committed team-provider-info.json because the project is open source and it only seemed to contain data about my development environment. I'm also not working in a team.
Is using amplify/backend/function/<something>/parameters.json no longer a supported method?

Hey @duckbytes it is not an officially-supported method, but likely worked prior to the change of lifting those env-specific parameters to SSM Parameter Store (around CLI v9/v10). Those parameters/env vars are written to team-provider-info.json per env, and hydrated to backend-config.json as SSM Parameters on env checkout/pull. Those then flow to the Function on synth.
Despite the name, team-provider-info.json holds information relevant to each environment. If this file does not exist or we create a new env the CLI should prompt for env var values for each Function.

Hey @josefaidt. How would you recommend I maintain the team-provider-info.json file when working with multiple deployments? At the moment I have the Amplify console set to automatically create a deployment on new branches that match production/**.
What this meant is that I could create a new branch from master, push it up and the new deployment would be created for me without any interventions.
It sounds like now I will need to generate a new team-provider-info.json file every time I create a new deployment, which I guess means creating a new environment manually to put in those values, and then connecting the new environment to a branch afterwards. Or can I have one version of the file that is common to all branches and it'll pull those values? It seems like there is a lot of environment specific data held in that file, but those function parameters don't change between each deployment.
I'm just wondering how much of this I can automate, since it was working so well before.

@duckbytes if Amplify CLI is unable to find values from team-provider-info.json file, it will fetch the values from SSM parameter store. Refer to the documentation providing this information.
on a new branch creation you should be able to run a script on hosting preBuild phase that creates the SSM parameters for the branch as Amplify CLI tries to retrieve parameters with format /amplify/<appId>/<environment-name>/AMPLIFY_<category-name>_<resource-name>_<parameter-name>

Thanks @ykethan
In the end I've hard coded the values into the lambda function, since they aren't secrets and don't often change between deployments this seemed like the simplest solution.


HDDS-3344. Remove Jenkins file

What changes were proposed in this pull request?
Remove Jenkins file as this is no longer in use.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3344
How was this patch tested?
Clean build.

Thank You @dineshchitlangia for the contribution

Thanks Bharat!


Modifier keys by themselves should not be counted as key presses to scroll to bottom

Details

Browser and browser version: vscode 1.8.0-insiders
OS version: Ubuntu 16.04
xterm.js version: 2.1.0

Steps to reproduce

Run a command to give you a scrollbar
Scroll up
Press shift, xterm.js scrolls down to the bottom

I don't believe the shift is routed to the terminal's shell process so it shouldn't scroll down as it isn't technically input.

This issue is actually pretty important as you can no longer copy something when scrolled up as when the viewport is scrolled to the bottom on ctrl the selection is dropped.


C# syntactic colorization not working

Environment data
dotnet --info output:
VS Code version:1.14.2
C# Extension version:1.11.0
Steps to reproduce
I install the C# extension and enable it
Expected  behavior
expected the different parts of syntax to be colored differently but almost everything is colored the same
This is how I expect it to look

Actual behavior
this is how my code looks

It looks to me like the problem is that you don't have semi-colons after using System or Console.WriteLine(...)

FWIW, do let me know if this doesn't fix the problem for you.

Yes that did fix my issue. Thanks!


[🐛] APP crash take picture from camera

Description
APP crash take picture from camera
How to repeat issue and example

Take picture from launchCamera
press ok  APP crashed

Solution

Take picture from launchCamera
press ok
response image uri

Additional Information

Image Picker version: "react-native-image-picker": "^4.1.2"
React Native version:"react-native": "0.66.1",
Platform: Android(Redmi Note 7 pro) && iPhone 12
Development Operating System: MacOS
Dev tools:  Xcode  13.0  or Android Studio Arctic Fox

Hi, I have the same problem on a Samsung SM-G960F with Android 10.
It works fine on the Emulator Nexus 6P API 29 with Android 10.

@Johan-dutoit another example why de-scoping this library to only handle image picking may be more maintainable and suggesting something like: https://github.com/mrousavy/react-native-vision-camera

Have this problem on android 10+. 9's version looks like stable.

@Johan-dutoit another example why de-scoping this library to only handle image picking may be more maintainable and suggesting something like: https://github.com/mrousavy/react-native-vision-camera

I like the idea of reducing the scope!  Major version bump required though.  Also nice feeling of deleting lots of code :D

any solution to this issue , facing on android 11 devices ??


There may be some bugs in the JdbcSourceEventDispatcher class

I used OracleSourceBuilder.OracleIncrementalSource to read the records of the oracle, and when listening for schema change, I found that the following error was reported

I think these errors because Oracle Record does not have file, server_id, pos  field，but in the JdbcSourceEventDispatcher class schemaChangeRecordValue method according to mysql record resolution, and mysql-cdc does not use this class,
private Struct schemaChangeRecordValue(SchemaChangeEvent event) throws IOException {
           Struct sourceInfo = event.getSource();
           Map<String, Object> source = new HashMap<>();
           String fileName = sourceInfo.getString(BINLOG_FILENAME_OFFSET_KEY);
           Long pos = sourceInfo.getInt64(BINLOG_POSITION_OFFSET_KEY);
           Long serverId = sourceInfo.getInt64(SERVER_ID_KEY);
           source.put(SERVER_ID_KEY, serverId);
           source.put(BINLOG_FILENAME_OFFSET_KEY, fileName);
           source.put(BINLOG_POSITION_OFFSET_KEY, pos);

oracle
Struct{version=1.6.4.Final,connector=oracle,name=oracle_logminer,ts_ms=0,db=ORCL,schema=FLINKUSER,table=STU,scn=0,commit_scn=0}
mysql
Struct{version=1.6.4.Final,connector=mysql,name=mysql_binlog_source,ts_ms=0,db=test,table=stu,server_id=0,file=,pos=0,row=0}
Environment :

Flink version :  1.13.2
Flink CDC version: 2.3.0
Database and version: oracle 11g

Duplicate with https://github.com/ververica/flink-cdc-connectors/issues/1792.


Fail to work on my Mac

I'm using the latest version of NearDrop. It was correctly installed and displayed in the bar, but when I tried to transfer files from my phone, tablet and PC (with Nearby Share beta) I couldn't find Mac in list.
Nowadays it can show menu in system bar, though the entry "Visible to everyone" and "Device name: MacBook Air" both grey and unchangeable. What should I do? Thx.

Are you sure your devices are on the same network and your router permits direct connections between them?

Yes, in the same WiFi hotspot.

Oh, I found when I close 5G on my phone, it works!


find/ls: use list_object_versions instead of list_objects_v2 for version aware filesystems

Fixes https://github.com/fsspec/s3fs/issues/653

Version aware filesystems use list_object_versions instead of list_objects_v2 for listing directories
fs.dircache will only cache entries for the latest file versions (file versions with IsLatest == True)
Individual file lookups (via _info) will return the cached version when the requested version is latest (when requested version_id is None)
When _info is doing a lookup for a specific (non-None) version_id, it will check if the cached version matches and then make the required HeadObject call if needed.

Ideally I think we should also be caching the full results of list_object_versions, so dircache would actually contain another level of nesting (for files -> versions), but for now this PR maintains current behavior while also fixing the original bug.
I'll most likely send a follow up PR that handles this additional caching at some point (it will probably be needed for downstream DVC eventually) but I don't think I'll be able to get to it right away.

Thank you


[Bug] Uploaded Files aren't checked for encoding or type

Current behavior and impact:
When users upload files, they aren't checked for type or content.
This might also be an "issue" with the text input not being validated.
Steps to reproduce:

Generate a file with random content (e.g. with dd if=/dev/urandom of=largefile.txt bs=100K count=1)
Upload said file in the user code upload menu
Alternatively:
Upload a binary from /usr/bin in the user code upload menu

Expected behavior:
Text box stays empty, when a file, that isn't a text-file is uploaded.
Acceptance Criteria:

[ ] Code Text box stays empty, when a file, that isn't a text-file is uploaded.

Same here as in #155 : Since we are currently working on using a real code editor and therefore (probably) redo the entire coding page, i will would look at this issue when doing that.


Automated cherry pick of #5113

Cherry pick of #5113 on release-5.22.

#5113: - Animate drag and drop handles to transition out

/cc  @nevyangelova

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: c5fe29423cec9d43df1f6a58ed0286874ed13383


Have spell-check.R ignore the style-sets directory

Purpose/implementation Section
What changes are being implemented in this Pull Request?
I didn't think about this but its' making spelling errors show up in the style-sets directory. So I'm having it ignore that folder.

Yes this is what we want.


Modifications to work in Windows?

I'm just curious how feasible you think it would be to get this running in Windows.  tf.contrib.ffmpeg ops aren't currently supported in Windows (is this only used for animation?), and neither is fcntl. flask, flask-cors, hyperchamber, tensorflow, scipy, and Pillow already work in Windows.
Great work by the way!

OK - I think I got it running.  I'll confirm by training a larger dataset over the weekend, but at least Improved-GAN is generating samples.

Thanks for testing on Windows.  Glad to know it's working!

@DippedPretzels how did you get around the fcntl requirement?

I used the comment on this thread:
You make a fcntl.py that contains:
def fcntl(fd, op, arg=0):
    return 0

def ioctl(fd, op, arg=0, mutable_flag=True):
    if mutable_flag:
        return 0
    else:
        return ""

def flock(fd, op):
    return

def lockf(fd, operation, length=0, start=0, whence=0):
    return`

and put in your PATH for python.  This worked for 0.8, and I'm trying to get 0.9 working in Windows, but samples don't seem to be saving (training appears to work though.)  It may be an issue with Windows and gi.repository.

Samples don't save automatically now, use --save_samples.  This will probably make more sense once this is merged: https://github.com/255BITS/HyperGAN/pull/111

I got HyperGAN to run on Windows 10 today, and here's the guide to do it:

Get Python 3.6.x, 64 bit (32 bit won't work; 64 bit is x86-64) from here: https://www.python.org/downloads/windows/
Follow the guide for Tensorflow GPU here: https://www.tensorflow.org/install/install_windows (CUDA Toolkit 9.0 and cuDNN v7.0. are required)
Here are the download links:
CUDA Toolkit 9.0 - https://developer.nvidia.com/cuda-90-download-archive
cuDNN v7.0 - https://developer.nvidia.com/cudnn (you need to register first)
Launch PowerShell in admin mode - just right click the Windows icon/start button and click Windows PowerShell (Admin)
Install the dependencies for hypergan and hypergan itself:
pip3 install numpy tensorflow-gpu hyperchamber pillow pygame
pip3 install hypergan --upgrade
I recommend getting tensorflow-gpu 1.6.0 - I had issues with 1.7.0:
pip3 install tensorflow-gpu==1.6.0
Update cli.py like in #161 . cli.py is located here if you installed for all users: "C:\Program Files\Python36\Lib\site-packages\hypergan". You might need to copy/move the file to desktop/anywhere else, edit it and then copy/move it back.
Go to any folder you want to use HyperGAN in. It's possible to write hypergan as a command in PowerShell, but it didn't work for me, so when reading the guide on the main page, replace "hypergan" with the following:
python 'C:\Program Files\Python36\Scripts\hypergan'

And an example of the full command usage would be:
hypergan new mymodel
or
python 'C:\Program Files\Python36\Scripts\hypergan' new mymodel
I hope this helps!

@europax Thanks! Confirming that this works. I'm confused tho why can't we just run python -m hypergan?

i  tried to use @europax guide but i hit a wall with installing hypergan #187

@europax Even after installing old versions of hypergan (0.9.0, 0.9.1, 0.9.5) it is always looking for CUDA 10 dlls for some reason.  We're also planning a windows installer post 1.0.


--base-href to be configurable in .angular-cli.json

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request

Versions.
@angular/cli: 1.0.2
node: 6.9.4
os: linux x64
@angular/animations: 4.1.1
@angular/common: 4.1.1
@angular/compiler: 4.1.1
@angular/core: 4.1.1
@angular/forms: 4.1.1
@angular/http: 4.1.1
@angular/platform-browser: 4.1.1
@angular/platform-browser-dynamic: 4.1.1
@angular/platform-server: 4.1.1
@angular/router: 4.1.1
@angular/cli: 1.0.2
@angular/compiler-cli: 4.1.1
@angular/language-service: 4.1.1

Desired functionality.
I need to configure multiple apps with different --base-href values. Right now the only place where I can set this setting is via command line, but that leads to too complex NPM scripts. A better solution would be a setting inside the app array of .angular-cli.json. We already have deployUrl, so I don't understand why there is no baseHref yet.

You have my vote, looking for exactly the same feature.

There's a pending PR: https://github.com/angular/angular-cli/pull/6461

Thanks!
I've just noticed, #3010 already considered this feature, but then got dismissed due to the last comment realizing that it is enough to change the base href in the index.html. However, I've seen certain StackOverflow answers pointing out that it may not be enough to change the HTML:

https://stackoverflow.com/questions/41515028/set-base-href-from-an-environment-variable-with-ng-build
https://stackoverflow.com/questions/38112891/set-base-href-dynamically-angular-2

Would love to see that feature !

just add "baseHref" : "YOUR_CUSTOM_HREF" to the "apps" in the angular-cli.json
{
   ....
 "apps": [
    {
       "baseHref" : "YOUR_CUSTOM_HREF"
     }
  ],
}

How does this work in Angular 6 with the new angular.json file?

@ffMathy
It's more or less the same way. In your angular.json file:
Build -> Configurations -> YOUR_CONFIG -> "baseHref" : "YOUR_CUSTOM_HREF"


Parallel Download Options - BREAKING CHANGE

API signatures between sync and async are not consistent. One provides a block size and one does not.
I believe both signatures should instead provide a new ParallelDownloadOptions/ParallelUploadOptions type containing the knobs that we wish to expose for tweaking the "from file" operations. Every knob should have a default value.

@gapra-msft, as you implement this, please consult with @seanmcc-msft on how this is done in the .Net library.  If there are idiomatic reasons why parallel upload/download in java should be different, that's fine, but if not, let's be consistent.


Sync missing entries (pt_BR).

Requesting review @marcossffilho

Thanks.

@Maikuolan did in #60. Thanks!!!


Allow Forced Refresh on Comment View

This is to allow for comment view's "refresh" button to bypass the cache. Otherwise, the network disk cache will always be used. Which is not the intent of a refresh.

TODO: It would probably be better to just use the volley cache all over instead of relying on your internal caching to resolve stories. That way we won't have two caches that are conflated with each other easily.

Does it actually use cache for any requests? I think no, because responses don't contain any Cache-Control or Expires headers, so it always runs networks request.
Still I do agree that using Volley's cache is a good idea. Looking through CacheDispatcher it is possible to make it both return cached request and make a network request by overriding StringRequest#parseNetworkResponse like this (barely tested code, but I do see success callback twice in logs):
StringRequest stringRequest = new StringRequest(Request.Method.GET, url, response ->{...}, error ->{...}) {
            @Override
            protected Response<String> parseNetworkResponse(NetworkResponse response) {
                Response<String> res = super.parseNetworkResponse(response);
                if (res != null && res.cacheEntry != null) {
                    res.cacheEntry.ttl = Long.MAX_VALUE;
                }
                return res;
            }
        };

@AppearamidGuy I honestly don't remember now because it's been a few months since I looked at this and my computer has since been bricked (waiting for a repair).
What I do remember is, using a debugger to step through scenarios on my S23 Ultra and my changes had performed some extra network requests that were otherwise not happening before (meaning they were cached).
I am definitely open to somehow testing this better but my point still stands that this should just be using your cache as it is much better IMO to cache in the way they you had set it up.
Too bad there's no unit tests and I'm far too lazy to set those up right now 😅.


Update protos to 0.299

...but they don't build yet

One minor update should be needed, but it needs either a change in proto definition itself or we need to unmarshal it from byte array.
NEW: PublicData    []byte
OLD:  PublicData    *PlayerPublicProfileProto

One minor update should be needed, but it needs either a change in proto definition itself or we need to unmarshal it from byte array.
NEW: PublicData    []byte
OLD: PublicData    *PlayerPublicProfileProto

Please feel free to complete the changes and/or contact furtif about correcting anything - this branch was just my quick attempt to solve and I have no time to complete at the moment


Stress tool not working when a dc has multiple nodes

Hi,
I was trying to deploy Eiger in cluster.  For this I used kodiak_dc_launcher.bash with necessary modifications. However when I ran it with 2 data centers and only 1 machine per data center, I was able to run the stress tool. To run the stress tool I used the test.sh script, specifying --nodes as list of nodes in the cluster. But when I have more than one machine per data center when I try to run the stress tool, operations failed and got an output similar to below.
0,0,0,0,0,NaN,10
0,0,0,0,0,NaN,20
Do I have to do some other configurations other than doing necessary changes in kodiac_dc_launcher.sh (attached run.sh), cassandra-topology.properties and the config file which has server details?
With the same configurations generated by using the above scripts and only commenting sliced_buffer_size_in_kb: 64 , I was able to run stress tool with cassandra 1.1, even with multiple nodes per dc. So I think I'm missing something specific to eiger.
Can you please help me to figure this out?
Thank you very much!

Furthermore, I found the below error in my log file. The assertion causing the error is added by Eiger and not available in cassandra only version.
ERROR [MutationStage:14] 2015-11-03 11:27:31,964 AbstractCassandraDaemon.java (line 137) Fatal exception in thread Thread[MutationStage:14,5,main]
java.lang.AssertionError: Do not expect replication mutations from the localDC (yet)
at org.apache.cassandra.db.RowMutationVerbHandler.doVerb(RowMutationVerbHandler.java:55)
at org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:59)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

That error suggests that maybe you are trying to replicate data within a datacenter? The prototype only supports replicating data once inside each datacenter, and I believe this assertion is firing because a node is getting a replicated write from another node in the same datacenter.
If that's not your intention, I suspect that something might be weird with the configuration.  Maybe the clients are configured to access both datacenters? (They should only access 1 at a time).
The experiment directory has the scripts I used to run the experiments, that might be a helpful place to look too.

Thank you for the reply.But I'm using replication factor as 1 and still getting the same error.

Hmm, maybe the strategy-properties for the clients aren't set in the way Eiger expects them to be?
I'd recommend looking at
https://github.com/wlloyd/eiger/blob/eiger-release/experiments/kodiak_scale.bash
and
https://github.com/wlloyd/eiger/blob/eiger-release/experiments/kodiak_common
to see the list of options that I had used for the stress tool when running experiments and how I configured certain things like the strategy-properties

Thank you! I was able to fix it. The problem was when using the stress tool, data needed to be insert through the InsertCL method. I was trying to insert with the default insert method.


x/tools/cmd/gopls: GoToDef does not work with Module Replace Clause

Summary
I am working on a project where  "GoToDef" works on all the symbols except the ones that come from a module that has been "replaced" in go.mod through the replace clause.
Reproduce
# be outside of GOPATH
1. ~ git clone https://github.com/marwan-at-work/authproxy
2. ~ cd authproxy
3. ~ go build ./...
4. ~ code . # open VSCode pointed at this prject

5. Open authproxy.go file and go to line 63 that reads `cfg, err := google.JWTConfigFromJSON(bts)`

6. Hover over the `JWTConfigFromJSON` part and try to GoToDef

Expected: go to the replaced definition insode $GOPATH/pkg/mod
Actual: nothing happened.
Editor Settings
GO111MODULE: on
Editor: VSCODE
GoPls Settings:
{
    "atomKeymap.promptV3Features": true,
    "editor.multiCursorModifier": "ctrlCmd",
    "editor.formatOnPaste": true,
    "window.zoomLevel": 0,
    "editor.fontSize": 12,
    "editor.lineHeight": 22,
    "go.buildOnSave": "off",
    "go.vetOnSave": "off",
    "go.useLanguageServer": true,
    "go.alternateTools": {
        "go-langserver": "gopls"
    },
    "go.languageServerExperimentalFeatures": {
        "format": false,
        "autoComplete": true,
        "rename": true,
        "goToDefinition": true,
        "hover": true,
        "signatureHelp": true,
        "goToTypeDefinition": true,
        "goToImplementation": true,
        "documentSymbols": true,
        "workspaceSymbols": true,
        "findReferences": true
    },
    "go.lintTool": "golint",
    "go.coverageDecorator": {
        "type": "highlight"
    },
    "editor.hideCursorInOverviewRuler": false,
    "editor.formatOnSave": true,
    "editor.codeActionsOnSave": {
        "source.organizeImports": true,
    },
    "breadcrumbs.enabled": true
}

I also can no longer reproduce this. Closing.


Make a way to go back to the picker window

Feature request
It would be nice, after closing the markdown file, to go back to the picker window
Or at least, setting a filetype to the floating window that is opening, so people could trigger an event and trigger :DevdocsOpenCurrenFloat again, after closing the markdown.
(at least i did the trigger event with filetype, because :Glow set a filetype, and i could use it

The plugin is using Telescope picker and telescope pickers are cached, you can use :Telescope resume to resume your last search.

The plugin is using Telescope picker and telescope pickers are cached, you can use :Telescope resume to resume your last search.

i meant another thing, but you gave me an idea, thanks!

i meant another thing, but you gave me an idea, thanks!
Sorry if I misunderstood it, but I still don't get it...