Bad Request (400) when logging into CRM in Pipeline Create Export from Dev

Power Platform ALM Workshop : Module2 - Item 30 fails when running the pipeline 👎

Details                                            Agent job 1                                                           1 error(s), 0 warning(s)                                                                      Failed to connect to         instance: https://Organisation ID.crm11.dynamics.com/.         Please verify your credentials for *** and instance url. ERROR         REQUESTING Token FROM THE Authentication context ERROR REQUESTING Token         FROM THE Authentication contextOne or more errors occurred. =>         AADSTS50126: Error validating credentials due to invalid username or         password. Trace ID: e3e48a84-99ba-45f4-b600-421f9214c700 Correlation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14         18:13:24Z => Response status code does not indicate success: 400         (BadRequest). =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to connect to CRM: AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         One or more errors occurred. => AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         => Response status code does not indicate success: 400 (BadRequest).         =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to Login to Dynamics CRM Unable to Login to         Dynamics CRM
Details
Agent job 1                                                           1 error(s), 0 warning(s)                                                                      Failed to connect to         instance: https://organisation ID.crm11.dynamics.com/.         Please verify your credentials for *** and instance url. ERROR         REQUESTING Token FROM THE Authentication context ERROR REQUESTING Token         FROM THE Authentication contextOne or more errors occurred. =>         AADSTS50126: Error validating credentials due to invalid username or         password. Trace ID: e3e48a84-99ba-45f4-b600-421f9214c700 Correlation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14         18:13:24Z => Response status code does not indicate success: 400         (BadRequest). =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to connect to CRM: AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         One or more errors occurred. => AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         => Response status code does not indicate success: 400 (BadRequest).         =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to Login to Dynamics CRM Unable to Login to         Dynamics CRM
Agent job 1
1 error(s), 0 warning(s)                                                                      Failed to connect to         instance: https://Organisation ID.crm11.dynamics.com/.         Please verify your credentials for *** and instance url. ERROR         REQUESTING Token FROM THE Authentication context ERROR REQUESTING Token         FROM THE Authentication contextOne or more errors occurred. =>         AADSTS50126: Error validating credentials due to invalid username or         password. Trace ID: e3e48a84-99ba-45f4-b600-421f9214c700 Correlation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14         18:13:24Z => Response status code does not indicate success: 400         (BadRequest). =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to connect to CRM: AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         One or more errors occurred. => AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         => Response status code does not indicate success: 400 (BadRequest).         =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to Login to Dynamics CRM Unable to Login to         Dynamics CRM
1 error(s), 0 warning(s)

Failed to connect to         instance: https:// Organisation ID.crm11.dynamics.com/.         Please verify your credentials for *** and instance url. ERROR         REQUESTING Token FROM THE Authentication context ERROR REQUESTING Token         FROM THE Authentication contextOne or more errors occurred. =>         AADSTS50126: Error validating credentials due to invalid username or         password. Trace ID: e3e48a84-99ba-45f4-b600-421f9214c700 Correlation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14         18:13:24Z => Response status code does not indicate success: 400         (BadRequest). =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to connect to CRM: AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         One or more errors occurred. => AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         => Response status code does not indicate success: 400 (BadRequest).         =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to Login to Dynamics CRM Unable to Login to         Dynamics CRM

Details

Agent job 1                                                           1 error(s), 0 warning(s)                                                                      Failed to connect to         instance: https://Organisation ID1.crm11.dynamics.com/.         Please verify your credentials for *** and instance url. ERROR         REQUESTING Token FROM THE Authentication context ERROR REQUESTING Token         FROM THE Authentication contextOne or more errors occurred. =>         AADSTS50126: Error validating credentials due to invalid username or         password. Trace ID: e3e48a84-99ba-45f4-b600-421f9214c700 Correlation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14         18:13:24Z => Response status code does not indicate success: 400         (BadRequest). =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to connect to CRM: AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         One or more errors occurred. => AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         => Response status code does not indicate success: 400 (BadRequest).         =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to Login to Dynamics CRM Unable to Login to         Dynamics CRM
Agent job 1
1 error(s), 0 warning(s)                                                                      Failed to connect to         instance: https://Organisation ID.crm11.dynamics.com/.         Please verify your credentials for *** and instance url. ERROR         REQUESTING Token FROM THE Authentication context ERROR REQUESTING Token         FROM THE Authentication contextOne or more errors occurred. =>         AADSTS50126: Error validating credentials due to invalid username or         password. Trace ID: e3e48a84-99ba-45f4-b600-421f9214c700 Correlation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14         18:13:24Z => Response status code does not indicate success: 400         (BadRequest). =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to connect to CRM: AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         One or more errors occurred. => AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         => Response status code does not indicate success: 400 (BadRequest).         =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to Login to Dynamics CRM Unable to Login to         Dynamics CRM
1 error(s), 0 warning(s)

Failed to connect to         instance: https://org9a7eff11.crm11.dynamics.com/.         Please verify your credentials for *** and instance url. ERROR         REQUESTING Token FROM THE Authentication context ERROR REQUESTING Token         FROM THE Authentication contextOne or more errors occurred. =>         AADSTS50126: Error validating credentials due to invalid username or         password. Trace ID: e3e48a84-99ba-45f4-b600-421f9214c700 Correlation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14         18:13:24Z => Response status code does not indicate success: 400         (BadRequest). =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to connect to CRM: AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         One or more errors occurred. => AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         => Response status code does not indicate success: 400 (BadRequest).         =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to Login to Dynamics CRM Unable to Login to         Dynamics CRM

Agent job 1

1 error(s), 0 warning(s)                                                                      Failed to connect to         instance: https://Organisation ID.dynamics.com/.         Please verify your credentials for *** and instance url. ERROR         REQUESTING Token FROM THE Authentication context ERROR REQUESTING Token         FROM THE Authentication contextOne or more errors occurred. =>         AADSTS50126: Error validating credentials due to invalid username or         password. Trace ID: e3e48a84-99ba-45f4-b600-421f9214c700 Correlation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14         18:13:24Z => Response status code does not indicate success: 400         (BadRequest). =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to connect to CRM: AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         One or more errors occurred. => AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         => Response status code does not indicate success: 400 (BadRequest).         =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to Login to Dynamics CRM Unable to Login to         Dynamics CRM
1 error(s), 0 warning(s)

Failed to connect to         instance: https://.crm11.dynamics.com/.         Please verify your credentials for *** and instance url. ERROR         REQUESTING Token FROM THE Authentication context ERROR REQUESTING Token         FROM THE Authentication contextOne or more errors occurred. =>         AADSTS50126: Error validating credentials due to invalid username or         password. Trace ID: e3e48a84-99ba-45f4-b600-421f9214c700 Correlation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14         18:13:24Z => Response status code does not indicate success: 400         (BadRequest). =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to connect to CRM: AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         One or more errors occurred. => AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         => Response status code does not indicate success: 400 (BadRequest).         =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to Login to Dynamics CRM Unable to Login to         Dynamics CRM

1 error(s), 0 warning(s)

Failed to connect to         instance: https://Organisation ID.dynamics.com/.         Please verify your credentials for *** and instance url. ERROR         REQUESTING Token FROM THE Authentication context ERROR REQUESTING Token         FROM THE Authentication contextOne or more errors occurred. =>         AADSTS50126: Error validating credentials due to invalid username or         password. Trace ID: e3e48a84-99ba-45f4-b600-421f9214c700 Correlation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14         18:13:24Z => Response status code does not indicate success: 400         (BadRequest). =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to connect to CRM: AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         One or more errors occurred. => AADSTS50126: Error validating         credentials due to invalid username or password. Trace ID:         e3e48a84-99ba-45f4-b600-421f9214c700 Correlation ID:         f0421c7c-ffae-499e-804e-25c2c6c2e1fc Timestamp: 2020-01-14 18:13:24Z         => Response status code does not indicate success: 400 (BadRequest).         =>         {"error":"invalid_grant","error_description":"AADSTS50126:         Error validating credentials due to invalid username or         password.\r\nTrace ID: e3e48a84-99ba-45f4-b600-421f9214c700\r\nCorrelation         ID: f0421c7c-ffae-499e-804e-25c2c6c2e1fc\r\nTimestamp: 2020-01-14         18:13:24Z","error_codes":[50126],"timestamp":"2020-01-14         18:13:24Z","trace_id":"e3e48a84-99ba-45f4-b600-421f9214c700","correlation_id":"f0421c7c-ffae-499e-804e-25c2c6c2e1fc","error_uri":"https://login.microsoftonline.com/error?code=50126"}:         Unknown errorUnable to Login to Dynamics CRM Unable to Login to         Dynamics CRM

I have checked that Username and Password are correct.  If they were wrong I would expect a 403 error.
Details I suspect in the manual are a little out of date.

Facing similar issue in Export solution task, Failed to connect to instance: https://.crm.dynamics.com/. Please verify your credentials for *** and instance url

@NPrice99
Is this issue related to the build tool hands-on labs that you downloaded from this repo? If so, let us know in a followup comment.
If you need assistance with the Power Apps build tools, post a message to the Power Apps component framework, ALM & Pro Dev forum.

Yes it was related to the build tool hands on labs that I downloaded from this repo.

@NPrice99
After looking into this matter further, we now have a support policy in place.
If you need assistance with the Power Apps build tools or the hands-on labs, post a message to the Power Apps component framework, ALM & Pro Dev forum.


Installing Additional Packages

First of all, thanks for all the hard work!
I'd love to be able to install tensorflow/keras, as I think that's the only package I'm missing for my work.
Give us a nice in-app way install packages?

Give us a nice in-app way install packages?

A not nice option is to open the terminal tab and use pip install.
It is not nice because on Linux it will install in the user directory, because the default install location is not writable. So there is a risk of mixing environments.

so i was able to install package with conda in ipython console:
!conda install -c conda-forge rich -y

however i am not sure which conda environment is being used. for command: !conda invo --envs i get star next to my miniconda base env and not the jupyterlabApp env?

Trying a %pip install from a code cell in a notebook inside the JuoyterLab puts things seemingly outside the path of the current kernel with a Defaulting to user installation because normal site-packages is not writeable warning.

@psychemedia I have opened a separate issue for this #234.


Feature: automated update of builder's API

Our builders need to use the API of https://github.com/slsa-framework/slsa-github-generator at HEAD.
This means every time we make an update to the generic API, we need to update the builder's go.sum/mod
I don't think we can check for it in pre-submits, because the hash to update to is unknown until the commit is pushed to main.
I think we have the following options:

Figure out how to configure dependabot to send us PR
Write our own schedule-trigger workflows once every X days to create an PR.

Note that this may quickly become an endless cycle if we're not careful: each new commit will create a new HEAD, which would trigger a new PR, etc. We may want to send a PR only if the code of the generic API has changed.

BTW, is it necessary to have a separate go.mod for each builder? what benefit does it actually give us if we're in the same repo? Currently we don't have one for provenance-only and I'm wondering if we should add one, or if maybe removing the one for the go builder is possible way to solve the issue.

I think the original idea was to have each builder separate so that they have their own dependencies, and not the cumulative sum of all builder's dependencies. I'm not sure the dependencies for each builder will be different in practice, so it may be ok to share the the same go.mod?
Another reason was to keep them private. I think we can achieve via internal/, right?

internal/ should keep folks from importing it directly but it'll still get included.


AVRO-3824: [Doc] The instruction for building the website should be more precise

AVRO-3824
What is the purpose of the change
How to build the website is instructed in doc/README.md but we cannot build even though we follow it.
The cause is that an instruction to do git submodule update --init --recursive is missing.
Verifying this change
After git submodule update --init --recursive, I confirmed I can build the website with the instructions in doc/README.md.
Documentation
No new features added.

Thank you!


Factor out bnv derivs

This is a first step towards fitting the PSF in Celeste.  I'd like to submit the PR now to avoid nasty merges while I finish the rest.  Tests pass on my machine, but currently waiting on Travis.

Have/will you re-run the benchmark script to make sure the changes haven't slowed down the objective function evaluations?

The file SensitiveFloat.jl is a duplicate of SensitiveFloats.jl. The rename to plural was done in #134 -- necessary because SensitiveFloats is now a module and has to be plural to avoid name collision with the type SensitiveFloat. (This sort of pluralization is typical in Julia module names for this reason.)

@rgiordan Just checking: are you going to remove SensitiveFloat.jl and make the other minor changes as part of the next PR finishing the work?
BTW git rebase can be helpful for situations like this. Rather than submitting a half-done PR to merge, run git rebase [remote]/master locally - you still have to resolve conflicts like merge, but it makes it look like your branch started from the current commit of [remote]/master, making later merging easier.

@kbarbary , yes, I'll fix them.  Thanks for catching it.  (I think I'll leave v as an array for the moment if you don't mind, though.)
Thank you for the pointer about rebasing.  I am learning a lot on this project these days!

Yeah I agree it's not the time to fiddle with v.


Proposal diff will now correctly compare studies. Fixes #97

A classic case of 'this never worked how was this not noticed for so long'

A classic case of 'this never worked how was this not noticed for so long'

(Also fixed a bug in which observation studies couldn't be compared because of a faulty if statement

(Also fixed a bug in which observation studies couldn't be compared because of a faulty if statement


Corrected "Hello World" example

I saw the history of README.markdown just now and noticed that it was already modified earlier due to an API change in the newest version (for which docs.rs build is failing). Current "Hello World" example is correct, Sorry.


QueryEditor : Add optional prop to diable running queries onBlur

Description
As a pre-requisite for https://github.com/grafana/athena-datasource/issues/116
Added an optional prop to avoid running queries on blur
Next steps:

Add that prop to ResourceSelector to avoid running there too
Bump package.json to publish new version

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Allow patch and diff to be used with arbitrary string types

Fixes #4134

coverage: 99.634% (-0.02%) from 99.65%
when pulling 72af4a6ff213cfd5320bf787ac93450d7a836ec6 on issue4134
into e6cafa573aac6ed9227f752a5371c0b3f436307d on develop.


fix(NumberConstraint): force positive value on first arg

Resolves #315 - multipleOf is inconsistent, fails for negative numbers

@leongersen please review

abs has no side effects and doesn't negatively affect multipleOf behaviour, test shows a previously failing case. Looks good to me.


Code Intellisense doesn't work on Macbook Pro M1

Javascript and other code intellisense don't work on Macbook Pro M1. Auto suggest is not working as well.

/needsMoreInfo including version and whether the problem still occurs if you run with all extensions disabled.

/needsMoreInfo including version and whether the problem still occurs if you run with all extensions disabled.

VS code version: version 1.54;
Mac OS version: Big Sur v11.2.1 (Macbook Pro M1 Silicon)
I tried disabling all extensions and tying but the intellisense didnt work;
Update: I know the root cause of this issue: when I switch to the typing source (from ABC to simple telex), the intellisense doesn't work; but when switching to ABC, the intellisense works correctly.

Please provide steps to reproduce the issue and describe the expected behavior


Changed caps lock into control

It's not like anybody uses it anyway, and there's plenty of feature requests asking for this.

Thanks for the hint, I will use this (caps <--> ctrl) to compile one for myself.


[ENG-4419][eas-cli] use asc api token to authenticate for EAS build

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.

Why

Authenticate locally with a ASC Api Key by specifying it in the eas.json build profile. You can create distribution certs, provisioning profiles and bundle identifiers with the api key. But you cannot create a push key and modify capabilities.
There isn't a good way to determine the Apple Team with ASC Api Key (based on my research, it seems that Apple has intentionally done this for privacy reasons). Because we are resigning/creating provisioning profiles, we need to know information about the apple team, like if it is inHouse/Enterprise. For this reason, I also require apple team info be passed in as well.

how you can help (dominik, wojtek)

is the build profile the best place to pass in a local asc api key? i see there's also credentials.json but that seems target based and only for build creds like dist cert and provisioning profile.

how you can help (bacon)

There isn't a good way to type a jwt AuthState right now. The object I return is missing a lot of things that are expected like session or appleId/applePassword/username. I think this may lead to undefined behaviour in the third party package if it is expecting those fields. See review comments below.
I'd suggest making upstream changes in Thirdparty so we can differentiate between different types of AuthState (ie) UserAuthState or JwtAuthState.

Test Plan
todo

is the build profile the best place to pass in a local asc api key? i see there's also credentials.json but that seems target based and only for build creds like dist cert and provisioning profile.

values in credentials.json are intended for unmanaged credentials so if credentials.json is present asc api key is unnecessary, I would prefer not to mix those 2 methods. We technically could put that in eas.json like we already do in submit a profile, but that case is a bit for legacy reasons.
My preference would be to prompt for the key the same way we are already prompting for username and password, but also provide a way to configure that via environment variable(can we just pass a path to the file, or are those 3 values necessary like for submit profile?)

I'm okay with the eas.json approach. However, as Wojtek suggested, I'd like to have support for env variables there. Similarly to what we have for submit profiles - see https://github.com/expo/eas-cli/blob/main/packages/eas-json/src/submit/resolver.ts#L28
This is important so we don't force users to store potentially sensitive data in files committed to the repo.

I've updated the PR with wojtek's suggestion where we authenticate with the api key the same way we do with username/password. You can supply the following env vars: EXPO_ASC_API_KEY_PATH, EXPO_ASC_KEY_ID, EXPO_ASC_ISSUER_ID, EXPO_APPLE_TEAM_ID, EXPO_APPLE_TEAM_TYPE. If there are any missing, it will prompt the user.
If none of the ASC env vars are present, it will assume we are doing username/password authentication.


improvement: remove back button css and misc

to allow for translating the back button copy lol

LGTM, but where are the updated props living? they didn't show up in the diff

It's in the @spells package, they already existed and this was a fix because I forgot to just import them


GA Migration Java PostCommit ValidatesRunner (Flink, Flink Jv11, Samza, Twister2)

As part of the migration of Precommit and Postcommit Jobs from Jenkins to GA in self-hosted runners, this PR contains:

Migrated workflow job-postcommit-java-validaterunners-flink.yml
Migrated workflow job-postcommit-java-validaterunners-flink-java11.yml
Migrated workflow job-postcommit-java-validaterunners-samza.yml
Migrated workflow job-postcommit-java-validaterunners-twister2.yml

The migrated workflows were added to CI.md
DO NOT MERGE until the effort to use self-hosted runners is completed #22703
These workflows use base actions listed in #23109 (Dependency)

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

hmmm what should we do here @damccorm ?

Lets leave this open for now so that we can take this effort forward if we're able to get the resources to do so.


Unexpected underscore in generated name of nested message

What version of protobuf and what language are you using?

go v1.16.2
libprotoc v3.15.6
proto-gen-go v1.26.0

What did you do?

Defined a message called Outer
Defined a nested message within Outer called Inner
User Inner inside a oneof with a name that differs only by case (inner, note lower case i).

underscore.proto:
syntax = "proto3";
package underscore;

option go_package = "./underscore";

message Outer {
  message Inner {}

  oneof value {
    Inner inner = 1;
  }
}

go.mod:
module underscore

go 1.16

require (
	github.com/golang/protobuf v1.5.1
	google.golang.org/protobuf v1.26.0
)

Generated with:
protoc --go_out=paths=source_relative,plugins=grpc:. ./*.proto

What did you expect to see?
I expected the Inner message be represented in Go by a struct named Outer_Inner.
What did you see instead?
An unexpected trailing underscore, such that the type name is Outer_Inner_.
Anything else we should know about your project / environment?
This looks very similar to https://github.com/golang/protobuf/issues/780, insofar as I think there is a perceived conflict that does not actually exist.
The unexpected underscore is not present if the field name within the oneof is changed, for example:
oneof value {
    Inner something_else = 1;
  }

/cc @danilvpetrov

This is working as expected, as protoc-gen-go is generating:

a Go struct called Outer_Inner for the underscore.Outer.Inner message.
a Go struct called Outer_Inner_ as the wrapper type to represent the underscore.Outer.inner oneof field.

They obviously cannot be the same name due a namespace conflict.
The rules for how protoc-gen-go avoids namespace conflicts are obscure and grew organically over the years. Unfortunately, we also cannot change them without breaking many existing usages.

Oops, my apologies! Thank you for pointing that out :)


QUESTION: how could I handle subsequent run after a failure and patching

Hi guys, thanks for the action.
I was using this action a year or so ago but ran into a problem, but had other priorities so forgot about this.
Scenario:
featA PR -> base
Solution with multiple projects, some projects depend on others etc...
action picks up that 3 projects are affected by the change.
But for some other reason, the workflow run fails, e.g. fail to deploy to Azure due to some error, e.g. syntax error in the deployment workflow.
Given the featA branch is already merged with base and lets say the branch is now deleted, I created a new branch fixA and PR that into main.
Now the action runs, but no longer detects any changes because the only file that changed was the deployment workflow.
How could I address this issue, in the event the workflow run fails, a code change to address the issue most likely will not affect the same projects or any project for that matter.
when running dotnet affected directly, one can pass the --assume-changes flag, I'm not sure if this is the solution, or if there's another approach for this problem, I've also noticed the dotnet-affected-action does not support the flag anyway, so if this would be the way to deal with this edge case, I would have to install dotnet affected tool and run it separately.
Please kindly advice

Hi @brazarb , I think that the trick you are missing is to run dotnet affected between the current commit and the "last successful build" commit. This is explained in the readme
Do let me know if you need more clarification :+1: , or if I misunderstood.
Leo

Hi @leonardochaia , thanks for replying.
I don't have access to the link you added above, perhaps it was added by mistake?
I was referring to building PR's as described in the readme for-building-prs.
So I guess the answer is to use the for-building-branches instead right?
If so, is there a case where one might want to use building for prs given the fact that in case of failure, subsequent run after a patch most likely will not result in the same affected.proj?
PS. I've noticed in the readme it suggests the use of nrwl/last-successful-commit-action@v1, but this action has been archived and replaced with nx-set-shas

Hi @brazarb , sorry I pasted the wrong link. I've fixed my comment.

If so, is there a case where one might want to use building for prs given the fact that in case of failure, subsequent run after a patch most likely will not result in the same affected.proj?

When building pull requests, you should be comparing your PR branch to your destination branch(usually main/master). When doing so, the affected projects will always be the diff between the PR branch and the destination branch, despite of the build status of main or the pr branch. In such case, building PRs, there's no need to use the "last successful build" trick
For example: dotnet affected --from=origin/main --to origin/features/my-feat.
When the PR is merged, continuing with your scenario:

But for some other reason, the workflow run fails, e.g. fail to deploy to Azure due to some error, e.g. syntax error in the deployment workflow.
Given the featA branch is already merged with base and lets say the branch is now deleted, I created a new branch fixA and PR that into main.
Now the action runs, but no longer detects any changes because the only file that changed was the deployment workflow.

If the workflow failed, and you are using the "last successful build" trick on your main branch workflow, you should be fine since affected will do the git diff between the last successful build commit and the current one.
For a proper CI/CD you need to combine both: have a separate workflow for PRs that uses the source and destination branch for the diff, and have a separate workflow for main that uses the "last successfull commit" trick.

PS. I've noticed in the readme it suggests the use of nrwl/last-successful-commit-action@v1, but this action has been archived and replaced with nx-set-shas

The replacement action seems to be pretty much the same, we should update this readme to reflect that.

Awesome, thank you. I think with that information I'm more prepared for the change.


Bug: Argument labels overflow argument input boxes

Encountered this today while trying to test sha256.

Command Preview does not accept this input

That input is clearly not valid JSON. Also, not related to this issue.


failed to connect to postgres: failed to connect to host=<IP_ADDRESS> user=postgres database=postgres: failed to receive message (read tcp <IP_ADDRESS>:34868-><IP_ADDRESS>:54320: read: connection reset by peer)

Just trying out supabase migration squash for the first time and got:
failed to connect to postgres: failed to connect to `host=<IP_ADDRESS> user=postgres database=postgres`: failed to receive message (read tcp <IP_ADDRESS>:34868-><IP_ADDRESS>:54320: read: connection reset by peer)
I did also try  supabase migration squash with --db-url passing the local db url, did not work, i tried too --local. did not work.
All i am trying to do is squash the local migrations.
Cli version: 1.150.0
OS: debian 12 bookworm
Wanna see the command with --debug?
Here you go:
2024/03/21 00:59:24 Connect Start: tcp <IP_ADDRESS>:54320
2024/03/21 00:59:24 Connect Done: tcp <IP_ADDRESS>:54320
2024/03/21 00:59:24 PG Send: {"Type":"StartupMessage","ProtocolVersion":196608,"Parameters":{"database":"postgres","user":"postgres"}}

The result ?
failed to connect to postgres: failed to connect to `host=<IP_ADDRESS> user=postgres database=postgres`: dial error (timeout: dial tcp <IP_ADDRESS>:54320: i/o timeout)

PS: other commands work fine like migration list, migration new, db diff, db reset.

Could you run with --create-ticket flag? ie.
supabase migration squash --create-ticket

This helps us to collect a stacktrace to reproduce.

Also which version of docker engine are you running?

Also which version of docker engine are you running?

docker -v
Docker version 25.0.3, build 4debf41

Could you run with --create-ticket flag? ie.
supabase migration squash --create-ticket

This helps us to collect a stacktrace to reproduce.

Alright, Done it with internet connected!
same error. And hopefully that will give you any info it is required info to reproduce the issue.
supabase migration squash --create-ticket
failed to connect to postgres: failed to connect to `host=<IP_ADDRESS> user=postgres database=postgres`: failed to receive message (read tcp <IP_ADDRESS>:49762-><IP_ADDRESS>:54320: read: connection reset by peer)

I get that when connected to a VPN

I get that when connected to a VPN

That's helpful to know. I can probably make a quick fix for this by connecting to the local project's docker network.


Add Digest to Bundle models

Pull request check list

[X] Proper tests/regressions included?
[ ] Documentation updated?

Affected functionality
N/A
Description of change
In order to make things simpler in the Server, it's best to store the bundle digests and also to require the Harvester to send the Digest as part of the Bundle upload, so the Server doesn't need to do that expensive operation.
Removed SignatureAlgorithm field that is not used right now.
Make Signature and Signing_cert not required to support the scenario where the Bundle verification is opted out.
Which issue this pull requests fixes

The changes are OK, I don't know if we can do that. Even if the harvester sends the digest, the server still needs to calculate to ensure the digest is correct.

The server is already trusting that the Harvester is sending the correct bundle, so it seems reasonable to also trust that the Harvester is sending the correct digest. The server is primarily using the digests for bundle comparison rather than for bundle validation.

Sending the wrong bundle will make the communications fail. Sending the wrong digest will make unnecessary bundle syncs. I know that we trust the harvester but that does mean we can skip validations.

The changes are OK, I don't know if we can do that. Even if the harvester sends the digest, the server still needs to calculate to ensure the digest is correct.

The server is already trusting that the Harvester is sending the correct bundle, so it seems reasonable to also trust that the Harvester is sending the correct digest. The server is primarily using the digests for bundle comparison rather than for bundle validation.

Sending the wrong bundle will make the communications fail. Sending the wrong digest will make unnecessary bundle syncs. I know that we trust the harvester but that does mean we can skip validations.

Ok, I'll add a validation on the Server.


Object field "collapsed" not working

Describe the bug
We are using netlify cms in conjuction with Gatsby via the gatsby-plugin-netlify-cms. I have tried several variations of using the Object Widget's property collapsed throughout our app and am not seeing any kind of behavior change. For reference I have tried using the List Widget's collapsed property, and am seeing that work as expected.
To Reproduce

In your template configuration, create an Object widget with the configuration collapsed: true
Navigate to CMS backend

Expected behavior
I expect to see the Object's fields collapsed instead of expanded.
Applicable Versions:
netlify-cms-app 2.12.3
netlify-cms-core 2.23.3

Git provider: Github
OS: MacOS 10.14
Tested in all browsers
Node.JS version: 11.15

CMS configuration
We are using a JS configuration via the gatsby integration. This is what a sample widgte looks like:
export default {
  label: 'Hero',
  name: 'hero',
  widget: 'object',
  collapsed: true,
  fields: [
    {
      label: 'Heading',
      name: 'heading',
      widget: 'string',
      collapsed: true,
    },
    {
      label: 'Heading Width',
      name: 'headingMaxWidth',
      widget: 'number',
      default: 400,
      min: 200,
      max: 540,
    },
    {
      label: 'Subheading',
      name: 'subheading',
      widget: 'string',
      required: false,
    },
    {
      label: 'Subheading Width',
      name: 'subheadingMaxWidth',
      widget: 'number',
      default: 400,
      min: 200,
      max: 540,
    },
    {
      label: 'Button Text',
      name: 'buttonText',
      widget: 'string',
    },
    {
      label: 'Button Link',
      name: 'buttonUrl',
      widget: 'string',
      required: false,
    },
    {
      label: 'Image',
      name: 'image',
      widget: 'image',
    },
    {
      label: 'Thumbnail',
      name: 'thumbnail',
      widget: 'image',
      required: false,
    },
  ],
}

Closing as stale and/or outdated.


[Feature request]: implement BIP-352

It would be great to have Silent Payments implemented in 2025 IMHO.
For now we can mostly use BlueWallet & Cake Wallet for this (and Silentium in alpha stage)

Hey @Sami32, thank you for the great suggestion! Silent Payments is pretty awesome. I'll bring this to the team's backlog and we'll investigate the possibility.


update electron to 305 and remove applescript. move back to using electrons method for login items

@keybase/react-hackers

could get rid of getDarwinAppName too if this works

I also tested on macos too

it skips on dev, you can comment that out

no I mean even after commenting out our DEV test. If we're shipping with this I'll just sanity check this part of the build first.

Test installer with this merged into master correctly sets startup key


Suggestion for spaceframe: cetacean deep space explorer

Cetacean deep space explorer, Shackleton expanse p. 286

It seems like the book, itself, does not describe the spaceframe -- it stats up a full ship, rather than a separate spaceframe and mission profile.

It also notes that the ship sent to the Expanse is an SS, not USS. Which isn't a problem, necessarily, as civilian ships could very well be something the tool could provide, but I think in this case it adds to the evidence that this is a special type of ship, built "as-is," rather than a frame with profiles.

I think the "Simplified Starship" workflow is probably the best way to handle this kind of thing.


recent upgrade to tokio-native-tls breaks crates that depend on hyper-tls

i see this crate was released an hour ago - seems to have broken my crates relying on reqwest.
see https://github.com/seanmonstar/reqwest/issues/971 for report on reqwest crate
more specifically - it looks like std::convert::From<(connect::HttpConnector, tokio_tls::TlsConnector)> is no longer implemented (i think this commit) which is causing this issue

the oauth2 and openidconnect crates I maintain are similarly affected:
https://travis-ci.org/github/ramosbugs/oauth2-rs/jobs/705496763
https://travis-ci.org/github/ramosbugs/openidconnect-rs/jobs/705496401
thanks @EverlastingBugstopper for tracking down the root cause!

Oh no, sorry about that. @LucioFranco does this look like it shouldn't have broken? I'll try to publish a revert ASAP.

@seanmonstar probably, my fault for not checking that From impl. It is a breaking change since the from now wants the TlsConnector from tokio_native_tls not tokio_tls crate.

I left a note on the PR with what I think we should do.

The real solution should be to just swap out tokio-tls for tokio-native-tls since it was a crate rename. Sorry about the trouble!

The crates should be 1-1 the same.

The crates should be 1-1 the same.

Maybe doing a patch release on tokio-tls that reexports tokio-native-tls as itself would fix the problem in a nice way until everything that depends on tokio-tls has new releases?

@kaj I believe that would still be a breaking change? Since, a reexport doesn't change the type?

I've yanked v0.4.2, so hopefully no one new should be downloading the broken version. I think though we have to release a v0.4.3 in order to fix it for those who already have, right? Or I suppose you could also just run cargo update -p hyper-tls 0.4.1.

@seanmonstar we could cherrypick the ipv6 commit for a 0.4.3, then place the tokio-native-tls commit into a 0.5 release.

That sounds good!

Ok, published v0.4.3 that should be better for everyone!


Timezone setting

Hi, I noticed you used arrow library from datetime management. Is there a way to modify the Timezone as it defaults to UTC. Thanks

The default timestamp is determine by the fresh_timestamp() method of the models, so you could overwrite it like this:
class User(Model):

    def fresh_timestamp(self):
        return arrow.now().naive

Pls how I do simply convert every timestamp column (created_at and updated_at) to UTC+1 time zone when accessing then. I want to leave them stored as UTC in d database

The easiest way would be to use an accessor, like so:
import arrow
from orator.orm import accessor

class User(Model):

    @accessor
    def created_at(self):
        return arrow.get(self._attributes['created_at']).to('Europe/Paris')

When I did this, I was getting a JSON serialization error, as the result of the model was to be coverted to a dict using the to_dict() method and passed to jsonify thus:
return(jsonify({"orders": user.orders().order_by("created_at","DESC").get().to_dict()}))

The problem with the solution u provided was that the accessor returned an object of type Arrow, while I think the serializer was expecting a datetime object.
Anyways, I found a hack around it by creating an accessor in the model thus:
 @accessor
    def created_at(self):
        dt = arrow.get(self.get_raw_attribute('created_at')).to('+01:00')
        return datetime(dt.year, dt.month, dt.day, dt.hour, dt.minute, dt.second).isoformat()

This should suffice for now till I get a better solution

Yes, the example I gave you actually raises an error. That's a problem in how the accessors work for date attributes.
Basically, once an attribute has been marked as mutated (either with the accesor or the mutator decorator) it will not be properly serialized.
I will see how to fix it.

The serialization error should be fixed on the develop branch.

i use like this:
 def fresh_timestamp(self):
        return pendulum.now()


Variable length syntax when passing arguments to fmt.Sprintf(str, v...)

Added variable length syntax when passing interface values to fmt.Sprintf(str, v...) in curses.Addstr() function

Original repository for this pull request is moved, so the change has been made manually with credit.


local path check added

condition added to proceed only if path exists

Closes https://github.com/WarmSaluters/mailmerge-js/issues/12


Balance history does not agree with balance

Balance history e.g. shows that current balance is 1100, but on the dashboard it is 200. I think the reason is that history doesn't actually check that the UTXOs are synced -- or more concretely, they difference between the two results probably is a result of UTXOs on abandoned forks.

I think this can be closed.   Balances match for me since 6ad9549a9b3cd780de5d41d0122bc1eb64dff60e

I think this can be closed. Balances match for me since 6ad9549

Agreed :)


This page is not for Python fuction

Hi!
This page is not for people who wants to use Python function, while this was not mentioned on the page.
So Python users ideally should be redirected to a correct tutorial.

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

ID: 6cf91d8c-d16b-346d-759b-f3c787dea2e5
Version Independent ID: 7e422baf-0a19-dded-ee83-a71b1c819f2f
Content: Create your first function in the Azure portal
Content Source: articles/azure-functions/functions-create-first-azure-function.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@xiafu-msft,
Thank you for your feedback! We will review and update as appropriate.

@xiafu-msft While creating functions from the Azure Portal is possible, its recommended to develop functions locally. The quickstart doc for creating functions using Visual Studio Code covers languages with first-class support in Azure Functions.
Also, note that editing python function apps is not supported in the Azure portal as shown in the portal.

Thanks a lot @ChaitanyaNaykodi-MSFT and @PramodValavala-MSFT that's helpful!

@xiafu-msft Glad we could help!
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


[WIP]: GHA: Migrate release logic from OSCI to GHA

Description
TODO:

Add secrets for

GCLOUD_SERVICE_ACCOUNT_GHA_ROXCTL_UPLOADER
SLACK_TEST_WEBHOOK
SLACK_ENG_RELEASE_WEBHOOK

Run a dummy release pipeline for release-0.0 branch and a 0.0.1 tag.

Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Created artifacts:

https://github.com/stackrox/release-artifacts/pull/78
https://github.com/stackrox/collector/pull/976
roxctl upload

@gavin-stackrox before merging, I'd need your help to clean up the openshift/release pipelines.

@gavin-stackrox before merging, I'd need your help to clean up the openshift/release pipelines.

I think they are already clear of this functionality. But can you review and call out any concerns?

I think they are already clear of this functionality. But can you review and call out any concerns?
@gavin-stackrox example: https://github.com/stackrox/openshift-release/blob/master/ci-operator/config/stackrox/stackrox/stackrox-stackrox-master.yaml#L451-L461.


Remove react-dom as a peerDependency

Removed the findDOMNode call in VirtualScroll. HTML element refs already give you the DOM node in v0.14.x.

Removed react-dom as a peerDependency, since it's not used by react-virtualized

Added react and react-dom as devDependencies, otherwise they don't get installed with npm@3

This breaks support with react 0.13, but I'm not sure it worked before?
At the very least, npm would yell at you for installing an incompatible react version, so the allowed versions in peerDependencies would probably need to be updated.
Furthermore, there's no react 0.13 react-dom package nor does it support pure function components, which are used in FlexTable.
If you decide to keep support for react 0.13, I'd probably suggest using following check in VirtualScroll:
if (/^(0\.13\.\d+)$/.test(React.version)) {
  this._scrollingContainer = this.refs.scrollingContainer.getDOMNode()
} else {
  this._scrollingContainer = this.refs.scrollingContainer
}

Since react 0.14 still has getDOMNode, you can't do a key check on the refs.
Also, the pure function components would need to be updated as React.Component or React.createClass classes in order to support react 0.13.
I don't know what usage % is like, so I don't know if it's worth supporting react 0.13 or not. Since it's slightly annoying to setup a harness that can work with both, I probably wouldn't bother with it. But then again, the required changes aren't super big.
In any case, removing react-dom and adding react / react-dom as devDependencies is a good idea :D.

This breaks support with react 0.13, but I'm not sure it worked before?

Hmm.. I had tested what was there before with both React 0.13 and 0.14 and it worked for me. (I had a local test harness running off of 0.13.)
The check did feel kind of hackish though. I don't mind "officially" stop trying to support 0.13.


NullPointerException when configuring SSL in the wrong way

Version: logstash-input-kafka-8.0.4

Operating System: Any

Config File (if you have sensitive info, please remove it):

	 kafka {
		bootstrap_servers => 'xxxxx:9092'
		topics => ["xxxxx"]
		codec => json { }
		security_protocol => "SSL"
		ssl_keystore_location => "/path/to/xxxx.jks"
		ssl_keystore_password => "xxx"
	}

Sample Data: None

Steps to Reproduce:

Start logstash.
Inspect logs:
[2018-04-05T10:58:08,080][ERROR][logstash.pipeline        ] A plugin had an unrecoverable error. Will restart this plugin.
  Pipeline_id:main
  Plugin: <LogStash::Inputs::Kafka ......config here>
  Error: uncaught throw java.lang.NullPointerException
  Exception: UncaughtThrowError
  Stack: org/jruby/RubyKernel.java:1137:in `throw'
/Users/Gabriel/Documents/ElasticSearch/logstash-6.2.3/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.4/lib/logstash/inputs/kafka.rb:329:in `create_consumer'
/Users/Gabriel/Documents/ElasticSearch/logstash-6.2.3/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.4/lib/logstash/inputs/kafka.rb:224:in `block in run'
org/jruby/RubyFixnum.java:305:in `times'
org/jruby/RubyEnumerator.java:323:in `each'
org/jruby/RubyEnumerable.java:830:in `map'
/Users/Gabriel/Documents/ElasticSearch/logstash-6.2.3/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.4/lib/logstash/inputs/kafka.rb:224:in `run'
/Users/Gabriel/Documents/ElasticSearch/logstash-6.2.3/logstash-core/lib/logstash/pipeline.rb:516:in `inputworker'
/Users/Gabriel/Documents/ElasticSearch/logstash-6.2.3/logstash-core/lib/logstash/pipeline.rb:509:in `block in start_input'

It seems that the following lines are causing this: https://github.com/logstash-plugins/logstash-input-kafka/blob/v8.0.4/lib/logstash/inputs/kafka.rb#L333-L343
I added some debugging and it seems that when security_protocol => "SSL"  then the ssl_truststore_location is required. But, the error message isn't clear enough for all these.
Once you add the trustore location, then we will bypass this exception. But, if the trustore is invalid then you get a new UncaughtThrowError:
[2018-04-05T11:02:30,816][ERROR][logstash.pipeline        ] A plugin had an unrecoverable error. Will restart this plugin.
  Pipeline_id:main
  Plugin: <LogStash::Inputs::Kafka configuration here poll_timeout_ms=>100, sasl_mechanism=>"GSSAPI", decorate_events=>false>
  Error: uncaught throw org.apache.kafka.common.KafkaException: Failed to construct kafka consumer
  Exception: UncaughtThrowError
  Stack: org/jruby/RubyKernel.java:1137:in `throw'
/Users/Gabriel/Documents/ElasticSearch/logstash-6.2.3/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.4/lib/logstash/inputs/kafka.rb:329:in `create_consumer'
/Users/Gabriel/Documents/ElasticSearch/logstash-6.2.3/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.4/lib/logstash/inputs/kafka.rb:224:in `block in run'
org/jruby/RubyFixnum.java:305:in `times'
org/jruby/RubyEnumerator.java:323:in `each'
org/jruby/RubyEnumerable.java:830:in `map'
/Users/Gabriel/Documents/ElasticSearch/logstash-6.2.3/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.4/lib/logstash/inputs/kafka.rb:224:in `run'
/Users/Gabriel/Documents/ElasticSearch/logstash-6.2.3/logstash-core/lib/logstash/pipeline.rb:516:in `inputworker'
/Users/Gabriel/Documents/ElasticSearch/logstash-6.2.3/logstash-core/lib/logstash/pipeline.rb:509:in `block in start_input'

So i think here we need a couple of things:

To enhance the error handling to better understand what is wrong.
Enhance the documentation to explain what is required and what not to build the trustore/keystore settings (and possibly add examples?).

Im having the same issue, is there any fix on the way?


Support ~/ on Windows

Vim supports ~/ and ~\ on all platforms. This PR helps my muscle memory so I can type :e ~/.ideavimrc on Windows and it works the same in both IdeaVim and Vim.
Vim supports backslashes on Unix (tested on Vim) but both forward- and back-slashes on Windows. VFS supports both forward- and back-slashes on all platforms.

Great, thank you!


When installing @glint/template to provide types via HelperLike, etc, I get an error about @glimmer/component being a missing peer

 WARN  Issues with peer dependencies found

└─┬ @glint/template
  └── ✕ missing peer<EMAIL_ADDRESS>Peer dependencies that should be installed:
<EMAIL_ADDRESS>

My library shouldn't add @glimmer/component as a peer dependency, so I'm wondering if @glint/template maybe needs to set @glimmer/component as an option peer dependency or if there should be a separate package for just helper types?
idk

I'm going to leave it to you to suggest a path forward here, as you're the person driving pnpm usage in the community therefore likely to have the most firsthand experience with what common pain points and possible remedies are for its stricter handling peerDependencies.
Currently we need @glimmer/component for its ExpandSignature, though, so just setting it as an optional peer isn't viable.

driving pnpm

fwiw, I think(? haven't confirmed) that yarn3 gives the same warnings / errors -- though I'm not sure if yarn3 does "strict peers" like pnpm7 does (pnpm 7 is like.. a month or two old and previously didn't error on peer violations).

Currently we need @glimmer/component for its ExpandSignature, though, so just setting it as an optional peer isn't viable.

makes sense!
I figured that'd be the case as I was poking around in there for some other stuff I was looking at.
So, for library authors/consumers of @glint/template, what can be done is to use a pnpm entry in the package.json
mine currently looks like this:
  "pnpm": {
    "peerDependencyRules": {
      "ignoreMissing": ["@glimmer/component"],
    }

I think this should be ok? at least, for now, I haven't ran in to any issues with @glimmer/component not being a dependency in my library -- I imagine the dep is being resolved elsewhere (or not used) as I'm only relying on HelperLike atm.

I kind of also wonder if ExpandSignature  would benefit from living in some types-only package? @glint/types perhaps? (idk) could host a bunch of stuff, and have no runtime or additional dependencies?

That's already what @glint/template is, but like we've talked about, ExpandSignature isn't a Glint-specific thing.
The @glimmer/component package needs that type to determine e.g. the type of this.args

Gonna close this for now as the peerDependencyRules seems sufficient for now.
If they cause any problems, I'll re-open.

Separate guidance for addons:
  "pnpm": {
    "peerDependencyRules": {
      "ignoreMissing": [
        "webpack",
        "ember-cli-htmlbars"
      ]
    }
  },

and then, @glimmer/component, etc (any other upstream peer) should be forwarded to the consumer of <your addon>.
(devDep (for types) + peerDep (for runtime resolving))
Thankfully, all apps consuming addons will already have @glimmer/component.
The downside, is that the more addons that forward peers, the more gnarly peer error will get, as we'll have a lot of (nearly)redundantly reported information.


Update helper text

Just a tiny helper text update that I got confused when coding. I hope it is all good, but let me know if you think I should change anything :)

thx


ROX-14933: Skip flaky ticker tests

Description
This test fails from time to time. In this PR I tried to adjust bacoff settings to make it pass.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
CI

Current dependencies on/for this PR:

master

PR #4781   👈

This comment was auto-generated by Graphite.

/retest

/retest

/test grouped-static-checks


Implement new dsl_ode_trigger_tracker_confidence_max_get/set services.

New services to set a maximum tracker confidence filter for all triggers - similar/opposite of the current minimum inference confidence service.
/**
 * @brief Gets the current maximum Tracker confidence setting for the ODE Trigger
 * A value of 0.0 (default) indicates the maximum Tracker confidence criteria is disabled
 * @param[in] name unique name of the ODE Trigger to query
 * @param[out] max_confidence current maximum Tracker confidence criteria
 * @return DSL_RESULT_SUCCESS on successful query, DSL_RESULT_ODE_TRIGGER_RESULT otherwise.
 */
DslReturnType dsl_ode_trigger_tracker_confidence_max_get(const wchar_t* name,
    float* max_confidence);

/**
 * @brief Sets the maximum Tracker confidence setting for the ODE Trigger
 * Set the value of 0.0 to disable maximum Tracker confidence criteria.
 * Note: the confidence level is only checked with the reported value is > 0.0
 * @param[in] name unique name of the ODE Trigger to update
 * @param[in] max_confidence maximum Tracker confidence to trigger an ODE occurrence
 * @return DSL_RESULT_SUCCESS on successful query, DSL_RESULT_ODE_TRIGGER_RESULT otherwise.
 */
DslReturnType dsl_ode_trigger_tracker_confidence_max_set(const wchar_t* name,
    float max_confidence);

Merged into v0.26.alpha


added token lending js cli

@jordansexton here's the lending cli.
So I'm running into an issue with addresses, specifically:

If I use the existing program address + existing oracle address I'm getting

  logs: [
    'Program<PHONE_NUMBER>1111111111111111111111 invoke [1]',
    'Program<PHONE_NUMBER>1111111111111111111111 success',
    'Program 6TvznH3B2e3p2mbhufNBpgSrLx6UkgvxtVQvopEZ2kuH invoke [1]',
    'Program log: Instruction: Init Reserve',
    'Program log: Pyth product account provided is not owned by the lending market oracle program',
    'Program log: Input oracle config is invalid',
    'Program 6TvznH3B2e3p2mbhufNBpgSrLx6UkgvxtVQvopEZ2kuH consumed 9417 of 200000 compute units',
    'Program 6TvznH3B2e3p2mbhufNBpgSrLx6UkgvxtVQvopEZ2kuH failed: custom program error: 0x2a'
  ]

I think this might be happening if you haven't redeployed the token lending program after the bug fixes (we swapped around the pyth product account's position in instructions for init_reserve).

If I use the existing program address + updated oracle address I'm geting

logs: [
    'Program<PHONE_NUMBER>1111111111111111111111 invoke [1]',
    'Program<PHONE_NUMBER>1111111111111111111111 success',
    'Program 6TvznH3B2e3p2mbhufNBpgSrLx6UkgvxtVQvopEZ2kuH invoke [1]',
    'Program log: Instruction: Init Reserve',
    'Program log: Pyth product account provided has a different version than expected',
    'Program log: Input oracle config is invalid',
    'Program 6TvznH3B2e3p2mbhufNBpgSrLx6UkgvxtVQvopEZ2kuH consumed 9575 of 200000 compute units',
    'Program 6TvznH3B2e3p2mbhufNBpgSrLx6UkgvxtVQvopEZ2kuH failed: custom program error: 0x2a'
  ]

I think this explains why our pyth owner accounts were different - sounds like we're using different versions. I'm happy to go with whichever you think is best.

Now the weird one. With a freshly deployed program + oracle I'm actually getting non-determnistic behavior. In 50% of cases it works (cli prints "All tests passed!"), but in 50% of cases I'm getting this error:

logs: [
    'Program AhTXZQVzdtZjbUwMYhti1EggUx778n72kmgP6DT6xURY invoke [1]',
    'Program log: Instruction: Refresh Reserve',
    'Program log: Oracle price is stale',
    'Program log: Input oracle config is invalid',
    'Program AhTXZQVzdtZjbUwMYhti1EggUx778n72kmgP6DT6xURY consumed 3692 of 200000 compute units',
    'Program AhTXZQVzdtZjbUwMYhti1EggUx778n72kmgP6DT6xURY failed: custom program error: 0x2a'
  ]

and sometimes even
QxqGfwKZH6FsR7mciJ91dyaUpwcB6RBocRS8wKHKEWw27Qe3cdDXcPtAWUXRqU8agnXXTtq178nMW86dFzRbqFp failed ({"err":{"InstructionError":[1,{"Custom":42}]}})

which from errors.rs maps to the same "input oracle config is invalid" error:
/// Oracle config is invalid
#[error("Input oracle config is invalid")]
InvalidOracleConfig,

Any idea for why the non-determenistic results?
Let me know how you want to proceed here, including any other comments on the cli.
Btw, in case it matters, I more or less modelled the cli on the one found in token swap. The big difference is I went with a class-based approach - I was starting to have a lot of global variables and I thought it made sense to capture everything inside a single "blockchain" instance. Open to discussion ofc.

you haven't redeployed the token lending program after the bug fixes (we swapped around the pyth product account's position in instructions for init_reserve).

Yeah, I haven't done this yet -- was hoping to do it later this week, since there are a few other open PRs I want to get wrapped.

Btw, in case it matters, I more or less modelled the cli on the one found in token swap.

What's the reason you decided to go with a JS CLI instead of using/adding to the Rust CLI @ https://github.com/solana-labs/solana-program-library/tree/master/token-lending/cli ?
My first instinct is that having two is going to lead to problems, and the Rust version gives us better guarantees about the CLI working correctly with the program, but I'm open to another argument.

you haven't redeployed the token lending program after the bug fixes (we swapped around the pyth product account's position in instructions for init_reserve).

Yeah, I haven't done this yet -- was hoping to do it later this week, since there are a few other open PRs I want to get wrapped.

Btw, in case it matters, I more or less modelled the cli on the one found in token swap.

What's the reason you decided to go with a JS CLI instead of using/adding to the Rust CLI @ https://github.com/solana-labs/solana-program-library/tree/master/token-lending/cli ?
My first instinct is that having two is going to lead to problems, and the Rust version gives us better guarantees about the CLI working correctly with the program, but I'm open to another argument.

Tbh I wrote the cli as a learning exercise, and just shared in case others might find it useful (eg token swap cli was very useful for me).
If you think it brings more problems than good, we can just leave it out. I won't be offended:)


Add drupal guidelines to the php-part

@wanze: Fully agree with snake vs. camel case issue. For module development I vote for using CamelCase as well, except for the required files as *.module or *.install. It's more consistent if custom functions in the these file are snake case as well, imho. For theme development I vote for snake case, since more or less all system theme hooks and functions are snake case.

@axooh, @wanze Fully agree with this issue.
I prefer @axooh's proposal: In files like *.module or *.install or *.theme we can use snake_case and in all other files, the "real" phpFiles, Classes and so on, we will use camelCase.
The name of each function is checked by phpcs in the default Drupal settings already. The names of the variables are not checked.

I tried to write it down, please take a look at it, @axooh & @wanze

Thanks for updating the guidelines @btemperli - no additional comments from my side 👍