The amount of metadata returned from EMR/Glue renders dbt-spark not working/hanging on the query

dbt version 0.16.1
Spark version 2.4.4

Hey folks,
I have encountered a problem where creating models/relations using dbt and EMR/Glue is limited to the point where the amount of metadata stored in Glue about the relations makes the dbt run/query hanging.
First, I noticed that after creating 6 relations in my target schema every subsequent run of dbt results in dbt hanging, not advancing.
Looking at the Thrift logs in the master node, I noticed that the problem was the following query:
SparkExecuteStatementOperation: Running query '/* {"app": "dbt", "dbt_version": "0.16.1", "profile_name": "emr_datalake", "target_name": "dev", "connection_name": "list__dbt_spark"} */
show table extended in dbt_spark like '*'
 ' with 6adf8996-814e-4a8c-93a1-1caa85c13340

Looking at the dbt.log file, I noticed that the process stops at the step TGetResultSetMetadataResp:
2020-07-21 19:16:57.017962 (ThreadPoolExecutor-1_0): Acquiring new spark connection "list__dbt_spark".
2020-07-21 19:16:57.018235 (ThreadPoolExecutor-1_0): Re-using an available connection from the pool (formerly list_).
2020-07-21 19:16:57.019701 (ThreadPoolExecutor-1_0): NotImplemented: add_begin_query
2020-07-21 19:16:57.019795 (ThreadPoolExecutor-1_0): Using spark connection "list__dbt_spark".
2020-07-21 19:16:57.019868 (ThreadPoolExecutor-1_0): On list__dbt_spark: /* {"app": "dbt", "dbt_version": "0.16.1", "profile_name": "emr_datalake", "target_name": "dev", "connection_name": "list__dbt_spark"} */
show table extended in dbt_spark like '*'

2020-07-21 19:16:57.020019 (ThreadPoolExecutor-1_0): /* {"app": "dbt", "dbt_version": "0.16.1", "profile_name": "emr_datalake", "target_name": "dev", "connection_name": "list__dbt_spark"} */
show table extended in dbt_spark like '*'

2020-07-21 19:16:57.020118 (ThreadPoolExecutor-1_0): TExecuteStatementReq(sessionHandle=TSessionHandle(sessionId=THandleIdentifier(guid=b'iF\x80\x1fj\xcfB\xcf\x86o\xd4\xa4,\xa1\xdd/', secret=b'vR$j\x9cbGW\x8c\x07\x91\x84\xb0\xe8\xb6\x80')), statement='/* {"app": "dbt", "dbt_version": "0.16.1", "profile_name": "emr_datalake", "target_name": "dev", "connection_name": "list__dbt_spark"} */\nshow table extended in dbt_spark like \'*\'\n  ', confOverlay=None, runAsync=True, queryTimeout=0)
2020-07-21 19:16:57.164044 (ThreadPoolExecutor-1_0): TExecuteStatementResp(status=TStatus(statusCode=0, infoMessages=None, sqlState=None, errorCode=None, errorMessage=None), operationHandle=TOperationHandle(operationId=THandleIdentifier(guid=b'\xdb\xad4\x04\x91\xfdMQ\xac\xd3\tN&\xd8DC', secret=b't\x80\xfa<\x1e\xf2@\x83\xae]\t\xd69\x1bq\xea'), operationType=0, hasResultSet=True, modifiedRowCount=None))
2020-07-21 19:16:59.199866 (ThreadPoolExecutor-1_0): TGetOperationStatusResp(status=TStatus(statusCode=0, infoMessages=None, sqlState=None, errorCode=None, errorMessage=None), operationState=2, sqlState=None, errorCode=None, errorMessage=None, taskStatus=None, operationStarted=None, operationCompleted=None, hasResultSet=None, progressUpdateResponse=None)
2020-07-21 19:16:59.200094 (ThreadPoolExecutor-1_0): Poll status: 2, query complete
2020-07-21 19:16:59.200222 (ThreadPoolExecutor-1_0): SQL status: OK in 2.18 seconds
2020-07-21 19:16:59.778318 (ThreadPoolExecutor-1_0): TGetResultSetMetadataResp(status=TStatus(statusCode=0, infoMessages=None, sqlState=None, errorCode=None, errorMessage=None), schema=TTableSchema(columns=[TColumnDesc(columnName='database', typeDesc=TTypeDesc(types=[TTypeEntry(primitiveEntry=TPrimitiveTypeEntry(type=7, typeQualifiers=None), arrayEntry=None, mapEntry=None, structEntry=None, unionEntry=None, userDefinedTypeEntry=None)]), position=1, comment=''), TColumnDesc(columnName='tableName', typeDesc=TTypeDesc(types=[TTypeEntry(primitiveEntry=TPrimitiveTypeEntry(type=7, typeQualifiers=None), arrayEntry=None, mapEntry=None, structEntry=None, unionEntry=None, userDefinedTypeEntry=None)]), position=2, comment=''), TColumnDesc(columnName='isTemporary', typeDesc=TTypeDesc(types=[TTypeEntry(primitiveEntry=TPrimitiveTypeEntry(type=0, typeQualifiers=None), arrayEntry=None, mapEntry=None, structEntry=None, unionEntry=None, userDefinedTypeEntry=None)]), position=3, comment=''), TColumnDesc(columnName='information', typeDesc=TTypeDesc(types=[TTypeEntry(primitiveEntry=TPrimitiveTypeEntry(type=7, typeQualifiers=None), arrayEntry=None, mapEntry=None, structEntry=None, unionEntry=None, userDefinedTypeEntry=None)]), position=4, comment='')]))

Since I am not that familiar with the steps that I should be expecting, I removed 6 previously created relations and created 7 dummy relations, in order to reject the "6 maximum number of relations" hypothesis.
  WITH dummy     AS (
      SELECT 1 AS col1,
             1 AS col2,
             1 AS col3,
             1 AS col4,
             1 AS col5,
             1 AS col6,
             1 AS col7,
             1 AS col8,
             1 AS col9,
             1 AS col10,
             1 AS col11,
             1 AS col12
      )
SELECT *
  FROM dummy

I created 7 of these copies:
Running with dbt=0.16.1
Found 37 models, 0 tests, 0 snapshots, 0 analyses, 143 macros, 0 operations, 0 seed files, 17 sources

21:57:25 | Concurrency: 1 threads (target='dev')
21:57:25 |
21:57:25 | 1 of 7 START view model .dbt_spark.src_dummy_1................ [RUN]
21:57:27 | 1 of 7 OK created view model .dbt_spark.src_dummy_1........... [OK in 2.34s]
21:57:27 | 2 of 7 START view model .dbt_spark.src_dummy_2................ [RUN]
21:57:29 | 2 of 7 OK created view model .dbt_spark.src_dummy_2........... [OK in 2.20s]
21:57:29 | 3 of 7 START view model .dbt_spark.src_dummy_3................ [RUN]
21:57:31 | 3 of 7 OK created view model .dbt_spark.src_dummy_3........... [OK in 2.16s]
21:57:31 | 4 of 7 START view model .dbt_spark.src_dummy_4................ [RUN]
21:57:34 | 4 of 7 OK created view model .dbt_spark.src_dummy_4........... [OK in 2.14s]
21:57:34 | 5 of 7 START view model .dbt_spark.src_dummy_5................ [RUN]
21:57:36 | 5 of 7 OK created view model .dbt_spark.src_dummy_5........... [OK in 2.05s]
21:57:36 | 6 of 7 START view model .dbt_spark.src_dummy_6................ [RUN]
21:57:38 | 6 of 7 OK created view model .dbt_spark.src_dummy_6........... [OK in 2.25s]
21:57:38 | 7 of 7 START view model .dbt_spark.src_dummy_7................ [RUN]
21:57:40 | 7 of 7 OK created view model .dbt_spark.src_dummy_7........... [OK in 2.17s]
21:57:42 |
21:57:42 | Finished running 7 view models in 22.47s.

Checking the Thrift logs, I noticed a step that should have been the next one had the query resumed and not hanged.
2020-07-21 19:20:50.359768 (ThreadPoolExecutor-1_0): TFetchResultsResp
This call/return is a big one since it returns the full metadata about the relations in your target schema, essentially what you are asking for through show table extended in <schema_name> like '*'
In order to confirm it is the size of the metadata payload returned from Glue, I add more columns and text to a model.

Running the same set of models results in hanging because the metadata size of the new models is too big (pointing that there is a certain cap to the amount of data that can be returned/parsed).
Running with dbt=0.16.1
Found 37 models, 0 tests, 0 snapshots, 0 analyses, 143 macros, 0 operations, 0 seed files, 17 sources

22:03:56 | Concurrency: 1 threads (target='dev')
22:03:56 |
22:03:56 | 1 of 7 START view model .dbt_spark.src_dummy_1................

@Dandandan experienced something similar. Would it be possible to test if this is still in dbt-spark 1.17.x?

@Fokko
Tested now with 0.17.0, still the same.
Running with dbt=0.17.0
* Deprecation Warning: dbt v0.17.0 introduces a new config format for the
dbt_project.yml file. Support for the existing version 1 format will be removed
in a future release of dbt. The following packages are currently configured with
config version 1:
 - bi_etl_dbt_spark

For upgrading instructions, consult the documentation:
  https://docs.getdbt.com/docs/guides/migration-guide/upgrading-to-0-17-0
Found 37 models, 0 tests, 0 snapshots, 0 analyses, 155 macros, 0 operations, 0 seed files, 17 sources

09:09:22 | Concurrency: 1 threads (target='dev')
09:09:22 |
09:09:22 | 1 of 7 START view model dbt_spark.src_dummy_1................. [RUN]

Looking at the dbt.log, I can see a difference:
2020-07-23 07:11:26.683553 (ThreadPoolExecutor-1_0): /* {"app": "dbt", "dbt_version": "0.17.0", "profile_name": "emr_datalake", "target_name": "dev", "connection_name": "list_None_dbt_spark"} */
show table extended in dbt_spark like '*'

2020-07-23 07:11:26.683667 (ThreadPoolExecutor-1_0): TExecuteStatementReq(sessionHandle=TSessionHandle(sessionId=THandleIdentifier(guid=b'\x17\x15%\x8aQ.J\xde\xaa\xf5H,E\xee=\xda', secret=b'\xf2\xeaL\x19yMIy\x91\xb0\xf1f`\xb3\xac*')), statement='/* {"app": "dbt", "dbt_version": "0.17.0", "profile_name": "emr_datalake", "target_name": "dev", "connection_name": "list_None_dbt_spark"} */\nshow table extended in dbt_spark like \'*\'\n  ', confOverlay=None, runAsync=True, queryTimeout=0)
2020-07-23 07:11:26.745280 (ThreadPoolExecutor-1_0): TExecuteStatementResp(status=TStatus(statusCode=0, infoMessages=None, sqlState=None, errorCode=None, errorMessage=None), operationHandle=TOperationHandle(operationId=THandleIdentifier(guid=b'\x1b\xb5\x0c\xbb\xeeYOx\xb6R!\x93\xd7F\xcdH', secret=b'.\xecJ\x1f1WM1\x8f\xa1\x9b\x1cSr\x02S'), operationType=0, hasResultSet=True, modifiedRowCount=None))
2020-07-23 07:11:29.407600 (ThreadPoolExecutor-1_0): TGetOperationStatusResp(status=TStatus(statusCode=0, infoMessages=None, sqlState=None, errorCode=None, errorMessage=None), operationState=2, sqlState=None, errorCode=None, errorMessage=None, taskStatus=None, operationStarted=None, operationCompleted=None, hasResultSet=None, progressUpdateResponse=None)
2020-07-23 07:11:29.407865 (ThreadPoolExecutor-1_0): Poll status: 2, query complete
2020-07-23 07:11:29.407992 (ThreadPoolExecutor-1_0): SQL status: OK in 2.72 seconds
2020-07-23 07:11:29.568888 (ThreadPoolExecutor-1_0): TGetResultSetMetadataResp(status=TStatus(statusCode=0, infoMessages=None, sqlState=None, errorCode=None, errorMessage=None), schema=TTableSchema(columns=[TColumnDesc(columnName='database', typeDesc=TTypeDesc(types=[TTypeEntry(primitiveEntry=TPrimitiveTypeEntry(type=7, typeQualifiers=None), arrayEntry=None, mapEntry=None, structEntry=None, unionEntry=None, userDefinedTypeEntry=None)]), position=1, comment=''), TColumnDesc(columnName='tableName', typeDesc=TTypeDesc(types=[TTypeEntry(primitiveEntry=TPrimitiveTypeEntry(type=7, typeQualifiers=None), arrayEntry=None, mapEntry=None, structEntry=None, unionEntry=None, userDefinedTypeEntry=None)]), position=2, comment=''), TColumnDesc(columnName='isTemporary', typeDesc=TTypeDesc(types=[TTypeEntry(primitiveEntry=TPrimitiveTypeEntry(type=0, typeQualifiers=None), arrayEntry=None, mapEntry=None, structEntry=None, unionEntry=None, userDefinedTypeEntry=None)]), position=3, comment=''), TColumnDesc(columnName='information', typeDesc=TTypeDesc(types=[TTypeEntry(primitiveEntry=TPrimitiveTypeEntry(type=7, typeQualifiers=None), arrayEntry=None, mapEntry=None, structEntry=None, unionEntry=None, userDefinedTypeEntry=None)]), position=4, comment='')]))
2020-07-23 07:11:29.815104 (ThreadPoolExecutor-1_0): On list_None_dbt_spark: ROLLBACK
2020-07-23 07:11:29.815346 (ThreadPoolExecutor-1_0): NotImplemented: rollback
2020-07-23 07:11:29.815497 (ThreadPoolExecutor-1_0): Error while running:
macro list_relations_without_caching
2020-07-23 07:11:29.815635 (ThreadPoolExecutor-1_0): 'utf-8' codec can't decode byte 0x9e in position 4509: invalid start byte
2020-07-23 07:11:29.815811 (ThreadPoolExecutor-1_0): Error while retrieving information about dbt_spark: 'utf-8' codec can't decode byte 0x9e in position 4509: invalid start byte
2020-07-23 07:11:29.816703 (MainThread): Acquiring new spark connection "master".
2020-07-23 07:11:29.816853 (MainThread): Opening a new connection, currently in state init
2020-07-23 07:11:29.817021 (MainThread): NotImplemented: add_begin_query
2020-07-23 07:11:29.817133 (MainThread): NotImplemented: commit
2020-07-23 07:11:29.817443 (MainThread): 09:11:29 | Concurrency: 1 threads (target='dev')
2020-07-23 07:11:29.817622 (MainThread): 09:11:29 |
2020-07-23 07:11:29.819471 (Thread-1): Began running node model.bi_etl_dbt_spark.src_dummy_1
2020-07-23 07:11:29.820895 (Thread-1): 09:11:29 | 1 of 7 START view model dbt_spark.src_dummy_1.................


jenkinsx-quickstart-nuxeo-poc to 1.0.15

Promote jenkinsx-quickstart-nuxeo-poc to version 1.0.15

 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.jenkins-x-bot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Return pts per frame after video decoding on GPU

When can we expect this functionality for VideoReader with device="cuda" otherwise users can't extract frames between two timestamps?
for frame in itertools.takewhile(lambda x: x['pts'] <= 5, reader.seek(2)):
    frames.append(frame['data'])


Variable modification

It is not clear how to access the dimensions of a variable or to change them. Is this working? What if I want to make a 1d plot of the time history of a variable. Is this working?

@glpotter the line I sent you actually grabs a very old version, i'm worki g on getting the newer packages on anaconda right now, will ping you when it's up and running.


Import Error: undefined symbol: _Py_CheckRecursionLimit

Hello, when I ran mrd_pyflow.py, I got the Python Import Error:
"
File "mrd_pyflow.py", line 4, in
from umi_dedup_duplex import run_umi_extract_consensus
ImportError: /prophet/umi_dedup_duplex.so: undefined symbol: _Py_CheckRecursionLimit
"
Here's my environment information:
Python = 3.10.8
System = Ubuntu
What problem could this be?

Hi,  the core codes were compressed with python 3.6.4, maybe you could try running it with this version of python.

Hi, the core codes were compressed with python 3.6.4, maybe you could try running it with this version of python.

Thanks a lot, this solved my problem after I create a environment of Python 3.6.4.


W-10743083 S/4HANA SOAP non-repeatable streams

W-10743083 S/4HANA SOAP non-repeatable streams

This was in the 2.2 docs and removed in https://github.com/mulesoft/docs-connectors/pull/1818 . Devs explained that it was still valid for 2.3, even though it was not in the generated reference file.


[Google Gemini] Extension Unable to Access Gemini API - All Queries Failing

Extension
https://www.raycast.com/EvanZhouDev/raycast-gemini
Raycast Version
1.85.0
macOS Version
15.1 (Sequoia)
Description
The Google Gemini extension is currently unable to access the Gemini API for any type of query. All attempts to use the extension result in an access error, regardless of the query content. This has been tested with various types of queries including technical questions ("What is overloading"), medical information ("What is the cause of multiple sclerosis"), and general knowledge questions ("What is trial").
Steps To Reproduce

Open Raycast
Access the Google Gemini extension –> Ask AI
Enter any query (tested with multiple different topics)
Press Enter

Current Behaviour
For all queries, the extension returns the following error:
"Could not access Gemini. This may be because Gemini has decided that your prompt did not comply with its regulations. Please try another prompt, and if it still does not work, create an issue on GitHub."
Expected Behaviour
The extension should be able to successfully connect to the Gemini API and return relevant responses for standard queries across all topics. The current behavior suggests there might be an underlying authentication issue or API connection problem rather than a content policy violation since it affects all types of queries.

I have tried the extension, and I cannot seem to replicate this on my end. Try to use Gemini's website, and see if it works there. Alternatively, also try getting a new API key.

Hey @EvanZhouDev, thank you. Creating a new API key worked. I don't know why the old API key was causing an issue, but creating a new one worked. If it happens again, I will keep this in mind.


nuxt.hooks not working

Environment
Node: v16.19.1
NPM: 9.6.1
Nuxt: 3.2.3 with Nitro 2.2.3
Module version: v8.0.0-beta.10
Reproduction
Create a i18n.js plugin as described in the documentation.
Create a component with the following template:
<template>
  <nav>
    <NuxtLink :to="switchLocalePath('en')">English</NuxtLink>
    <NuxtLink :to="switchLocalePath('pt')">Português</NuxtLink>
  </nav>
</template>

<script setup lang="ts">
  const switchLocalePath = useSwitchLocalePath();
</script>

Describe the bug
While navigating between languages, i expected to see the console.log() from i18n.js but nothing gets printed in the console.
Also, when i change the file extension to .ts a typescript error shows up:
Argument of type '"i18n:beforeLocaleSwitch"' is not assignable to parameter of type 'HookKeys<RuntimeNuxtHooks>';
Argument of type '"i18n:localeSwitched"' is not assignable to parameter of type 'HookKeys<RuntimeNuxtHooks>';
I checked that this PR was created in order to use these two hooks, but somehow they don't seem to work at all.
Additional context
No response
Logs
No response

Hi, I'd like to ensure that the hooks are working fine so I'm really hoping to investigate further into this. Could you provide the source code of your plugin and/or a replication over Stackblitz please?

hi @ineshbose  and thanks for the response.
There's a stackblitz replication.
As you can see, while changing language, the message gets updates, but no console log is triggered from i18n.ts.
Also, you can see the typescript errors that i mentioned in the i18n.ts file.

Thanks for the replication - yes, it seems that the latest change has not been released on edge so the hooks aren't working. /cc @kazupon
https://www.npmjs.com/package/@nuxtjs/i18n-edge/v/8.0.0-beta.10-27972923.f3bacb5?activeTab=readme
Meanwhile, you can refer to v7 docs as the same for this purpose - https://v8.i18n.nuxtjs.org/guide/callbacks/#onbeforelanguageswitch

hi @ineshbose . I updated the version to edge, but still does not work.
I also updated the replicate to the edge version, so you can check that the hooks still don't seem to work.

The stackblitz doesn't seem updated - but I tested manually and you'll be able to see the logs in your browser console (the functions, hook and plugins are runtime)

I can confirm now that after removing package-lock.json and node_modulesand run npm i locally, i can see the logs and also no erros in the i18n.ts file.
Many thanks for your suppor @ineshbose


Attempt at cherry picking the Env items

Introducing Env, which is a propagation of data.

Can we keep poise as a dependency out of this PR?


Update LLVM-style inline assembly

Addresses LLVM-style inline assembly deprecated mode, as described in https://github.com/shenango/shenango/issues/3

Sure @aousterh! Done ✅


Having Authentication failed error

I followed the instructions above and also this one https://docs.microsoft.com/en-us/azure/healthcare-apis/register-resource-azure-ad-client-app but when I used the generated token (guide from here https://docs.microsoft.com/en-us/azure/active-directory/develop/v1-oauth2-client-creds-grant-flow) I got Authentication failed error. Am I missing something, been trying to resolve this for 3 days but I can't fix it. Already talked to chat support and he told me to comment in the docs im following. Can you help me point to the right direction? Thank you.

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

ID: a4edd558-abd8-fbbe-9255-067ca0d2d039
Version Independent ID: dd4bf590-eb0e-605a-1ac2-8b18db6d1e80
Content: Register a service application in Azure Active Directory - Azure API for FHIR
Content Source: articles/healthcare-apis/register-service-azure-ad-client-app.md
Service: healthcare-apis
GitHub Login: @hansenms
Microsoft Alias: mihansen

First thing to check would be the headers returned when you get an authentication error. They will give you some guidance on what is wrong with the token.
Some of the possibilities are that you don't have the right Audience or that the token is expired. In that case you would typically see error code 401 and some header fields indicating what is wrong.
If the token has the right audience, etc. but the service principal for the client is not allowed in, you would get a 403 Forbidden. In that case you need to check that the object id (token claim oid) is in the list of allow object ids for the FHIR service. More details here:
https://docs.microsoft.com/en-us/azure/healthcare-apis/find-identity-object-ids
Hope this helps

Hi, thank you its now working, really appreciated it. So what happened was the header was saying invalid_audience so I changed it, and then I got the 403 error and I just added the object id in the fhir service.

Sure thing. Glad you got it working.
#please-close


How to change text color?

I got the solution on my own.
Just need to edit the file "AbstractWheelTextAdapter.java" at line number 47.
public static final int DEFAULT_TEXT_COLOR = 0xFF101010;
In this file you can customise the whole style of the wheel & also apply custom text fonts too.


Mode to show/hide selected items

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[x] Mac OS X
[x] Windows
[ ] Etc.

Shell

[x] bash
[x] zsh
[x] fish

Feature request
It would be nice to have an action, mode or toggle that shows/hides only the selected items when -m-flag is set. Same for the unselected items.
I could not find this feature on the manpage or on the web. Am i missing something?
Thanks for this amazing tool.

No, we don't have such an option. fzf was optimized to handle very large input lists (e.g. 10s of millions of items) and unfortunately, that optimization makes it non-trivial to implement an option that affects the output list without hurting performance and increasing memory footprint. So we're going to pass on this one. But you can achieve a similar effect using reload action like so
fzf --multi --bind 'ctrl-r:reload:cat {+f}'


Break assumption of istio control plane existing in release namespace

Please provide a description of this PR:
Fixes #43569.
This PR:

Creates a couple of new Helm values to allow users to specify the namespace of istio components separately from the release namespace (defaults to release namespace if empty). global.istioNamespace is used where available and appropriate.
Adds a test for installing the Helm release in a separate namespace AND installing istio in a non-istio-system namespace
Removes hardcoded istio-system namespace declarations in a couple of tests

@keithmattix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test integ-operator-controller

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test integ-operator-controller

gencheck_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test integ-operator-controller

gencheck_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test gencheck

unit-tests-arm64_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test integ-operator-controller

gencheck_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test gencheck

unit-tests-arm64_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test unit-tests-arm64

lint_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test integ-operator-controller

gencheck_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test gencheck

unit-tests-arm64_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test unit-tests-arm64

lint_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test lint

integ-helm_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test integ-helm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test integ-operator-controller

unit-tests-arm64_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test unit-tests-arm64

lint_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test lint

integ-helm_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test integ-helm

gencheck_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test integ-operator-controller

unit-tests-arm64_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test unit-tests-arm64

integ-helm_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test integ-helm

gencheck_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test gencheck

lint_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test integ-operator-controller

integ-helm_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test integ-helm

gencheck_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test gencheck

lint_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test lint

unit-tests-arm64_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-operator-controller_istio
4082de37eba9e09378dba7e28269c3208c78945f
link
true
/test integ-operator-controller

integ-helm_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test integ-helm

gencheck_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test gencheck

lint_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test lint

unit-tests-arm64_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test unit-tests-arm64

unit-tests_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test integ-helm

gencheck_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test gencheck

lint_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test lint

unit-tests_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test unit-tests

unit-tests-arm64_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test integ-helm

unit-tests_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test unit-tests

unit-tests-arm64_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test unit-tests-arm64

gencheck_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
6d4c9212c26b0be371f475594c6f1b3e4ef0ece3
link
true
/test integ-helm

unit-tests-arm64_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test unit-tests-arm64

gencheck_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test gencheck

unit-tests_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test unit-tests-arm64

gencheck_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test gencheck

unit-tests_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test unit-tests

integ-helm_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test integ-helm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test unit-tests-arm64

gencheck_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test gencheck

unit-tests_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test unit-tests

integ-helm_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test integ-helm

integ-pilot-istiodremote_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test gencheck

unit-tests_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test unit-tests

integ-helm_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test integ-helm

integ-pilot-istiodremote_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test integ-pilot-istiodremote

unit-tests-arm64_istio
772ec1de43a9278995063c4fd0da21d27656daee
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test unit-tests

integ-helm_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test integ-helm

integ-pilot-istiodremote_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test integ-pilot-istiodremote

unit-tests-arm64_istio
772ec1de43a9278995063c4fd0da21d27656daee
link
true
/test unit-tests-arm64

gencheck_istio
772ec1de43a9278995063c4fd0da21d27656daee
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
0c205c6131f9cbb7d9d3bbbb5923e508c37210cd
link
true
/test unit-tests

unit-tests-arm64_istio
772ec1de43a9278995063c4fd0da21d27656daee
link
true
/test unit-tests-arm64

gencheck_istio
e2645aefa63bfcadb910a51615ecf88492f80607
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest-required

@keithmattix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
b0fd947ed083690b970faf046c53a291d0ea1b58
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster

@keithmattix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
7268623f7d48811dc05c16655d82e20f8344f30a
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
7268623f7d48811dc05c16655d82e20f8344f30a
link
true
/test lint

gencheck_istio
7268623f7d48811dc05c16655d82e20f8344f30a
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test lint

gencheck_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test lint

gencheck_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test gencheck

integ-basic-arm64_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test lint

gencheck_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test gencheck

integ-basic-arm64_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-basic-arm64

integ-ipv6_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-ipv6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test lint

gencheck_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test gencheck

integ-basic-arm64_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-basic-arm64

integ-ipv6_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-ipv6

integ-distroless_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-distroless

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test lint

gencheck_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test gencheck

integ-ipv6_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-ipv6

integ-distroless_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-distroless

integ-basic-arm64_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test gencheck

integ-ipv6_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-ipv6

integ-distroless_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-distroless

integ-basic-arm64_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-basic-arm64

lint_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test gencheck

integ-distroless_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-distroless

integ-basic-arm64_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-basic-arm64

lint_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test lint

integ-ipv6_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ipv6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test gencheck

integ-distroless_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-distroless

integ-basic-arm64_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-basic-arm64

lint_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test lint

integ-ipv6_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ipv6

integ-ds_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ds

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
736fa8a10398b396aa1b67af2af39693929b2012
link
true
/test integ-distroless

integ-basic-arm64_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-basic-arm64

lint_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test lint

integ-ipv6_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ipv6

integ-ds_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ds

gencheck_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-basic-arm64

lint_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test lint

integ-ipv6_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ipv6

integ-ds_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ds

gencheck_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test gencheck

integ-distroless_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-distroless

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-basic-arm64

lint_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test lint

integ-ipv6_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ipv6

integ-ds_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ds

gencheck_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test gencheck

integ-distroless_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-distroless

integ-cni_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-basic-arm64

lint_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test lint

integ-ipv6_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ipv6

integ-ds_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ds

gencheck_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test gencheck

integ-distroless_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-distroless

integ-cni_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-cni

integ-pilot_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-basic-arm64

lint_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test lint

integ-ipv6_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ipv6

integ-ds_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ds

gencheck_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test gencheck

integ-distroless_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-distroless

integ-cni_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-cni

integ-pilot_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot

integ-pilot-istiodremote_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-basic-arm64

lint_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test lint

integ-ipv6_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ipv6

integ-ds_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ds

gencheck_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test gencheck

integ-distroless_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-distroless

integ-cni_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-cni

integ-pilot_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot

integ-pilot-istiodremote_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-istiodremote

integ-pilot-multicluster_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-basic-arm64

lint_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test lint

integ-ipv6_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ipv6

integ-ds_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ds

gencheck_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test gencheck

integ-distroless_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-distroless

integ-cni_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-cni

integ-pilot_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot

integ-pilot-istiodremote_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-istiodremote

integ-pilot-multicluster_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Let's discuss this in next WG - maybe I don't understand your use case, but it may already be supported.

Happy to - I'll add an item to the agenda. Thanks!

Not sure I understand why you would want the 'helm release' to be in a
different namespace from istio.
Having multiple istiod namespaces, each representing a different tenant is
relatively common. Users creating
a 'private' install of istiod is also possible. What I don't get is why
would you have the helm chart info in a separate
namespace - wouldn't the helm user need RBAC in both ?
Another use case is having a 'central' istiod handling certs/etc - and per
namespace istiod for other things.
In any case - a short doc with the use case would be best, I'm generally ok
with install flexibility and it's not the first
tenant-related use case we support.
On Fri, Mar 3, 2023 at 1:39 PM Keith Mattix II @.***>
wrote:

@.**** commented on this pull request.
In manifests/charts/base/templates/endpoints.yaml
https://github.com/istio/istio/pull/43572#discussion_r1125037820:

@@ -8,7 +8,7 @@ metadata:
{{- else }}
name: istiod
{{- end }}

namespace: {{ .Release.Namespace }}

namespace: {{ .Values.global.istioNamespace | default .Release.Namespace }}

The goal here is to enable the Helm release (i.e. the secret with the
Chart information) to be installed in a different namespace than the istio
control plane itself. Because Istio's helm charts use .Release.Namespace
as an alias for the system, this is not currently possible and breaks
scenarios where users may want to centralize all helm releases in a
different namespace than the actual compute. Note that cert-manager and
prometheus (2 popular cloud native charts) enable this scenario:
Cert manager: {{.Values.namespace|default.Release.Namespace}}
Prom: .Values.forceNamespace | default .Release.Namespace
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/43572#discussion_r1125037820, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUR2SYBSXD4YLD46V73XTW2JQKRANCNFSM6AAAAAAVGFBJ74
.
You are receiving this because your review was requested.Message ID:
@.***>

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ipv6_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ipv6

integ-ds_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ds

integ-distroless_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-distroless

integ-cni_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-cni

integ-pilot_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot

integ-pilot-istiodremote_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-istiodremote

integ-pilot-multicluster_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-istiodremote-mc

integ-basic-arm64_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ds_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-ds

integ-distroless_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-distroless

integ-cni_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-cni

integ-pilot_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot

integ-pilot-istiodremote_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-istiodremote

integ-pilot-multicluster_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-istiodremote-mc

integ-basic-arm64_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-basic-arm64

integ-ipv6_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ipv6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-distroless

integ-cni_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-cni

integ-pilot_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot

integ-pilot-istiodremote_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-istiodremote

integ-pilot-multicluster_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-istiodremote-mc

integ-basic-arm64_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-basic-arm64

integ-ipv6_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ipv6

integ-ds_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ds

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-distroless

integ-cni_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-cni

integ-pilot_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot

integ-pilot-multicluster_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-istiodremote-mc

integ-basic-arm64_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-basic-arm64

integ-ipv6_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ipv6

integ-ds_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ds

integ-pilot-istiodremote_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-cni

integ-pilot_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot

integ-pilot-multicluster_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-istiodremote-mc

integ-basic-arm64_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-basic-arm64

integ-ipv6_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ipv6

integ-ds_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ds

integ-pilot-istiodremote_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-istiodremote

integ-distroless_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-distroless

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-cni

integ-pilot_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot

integ-pilot-multicluster_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot-multicluster

integ-basic-arm64_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-basic-arm64

integ-ipv6_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ipv6

integ-ds_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ds

integ-pilot-istiodremote_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-istiodremote

integ-distroless_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-cni

integ-pilot_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot

integ-basic-arm64_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-basic-arm64

integ-ipv6_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ipv6

integ-ds_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ds

integ-pilot-istiodremote_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-istiodremote

integ-distroless_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
d9947eb3c3843f401a85f863727aa2d6cf6302dd
link
true
/test integ-pilot

integ-basic-arm64_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-basic-arm64

integ-ipv6_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ipv6

integ-ds_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ds

integ-pilot-istiodremote_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-istiodremote

integ-distroless_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-multicluster

integ-cni_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@keithmattix: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-basic-arm64

integ-ipv6_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ipv6

integ-ds_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-ds

integ-pilot-istiodremote_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-istiodremote

integ-distroless_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-distroless

integ-pilot-istiodremote-mc_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot-multicluster

integ-cni_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-cni

integ-pilot_istio
63abb6ff00b4a7825a629767c5b507aaa75e9c11
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Closing this PR for a more urgent, smaller scoped PR. We found a way around this for now


added build files for raspberry pi 3

Cleaned up previous pull request.
Sorry, it took a while to get back to this.

No problem. It's easy to lose track of time. Thanks for getting back to this :+1:


New icon - BABB

New icon for a crypto firm called BABB (Bank Account Based on Blockchain).
Thanks!

Merged, thanks to @IISlapDashII


Update interactive docs

This updates our interactive/Jupyter documentation.  We focus a bit more now on JupyterLab, and remove the link to the pangeo docs, which was a bit stale.

Thanks for the feedback @guillaumeeb .  I think I've responded to all of your suggestions.

Thanks @mrocklin !

Thanks for the review!
On Wed, Sep 25, 2019 at 2:26 PM Guillaume Eynard-Bontemps <
<EMAIL_ADDRESS>wrote:

Thanks @mrocklin https://github.com/mrocklin !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-jobqueue/pull/340?email_source=notifications&email_token=AACKZTGPO3TBLSOGDPA7ISTQLO3ORA5CNFSM4IZL555KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7TB34Y#issuecomment-535174643,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACKZTEVVE4E7CX45YCZQKTQLO3ORANCNFSM4IZL555A
.


Enable to add custom pylint plugins to lintPython

Context
Pylint allows to load custom plugins or checkers for customized linting. It's a very nice option for pylint, mypy or prospector disabilities.
Proposal
Allow to /lintPython builtin to receive a pylintPluginsDir argument for describing the custom rules that developers want.
Links / References

https://pylint.pycqa.org/en/latest/development_guide/how_tos/plugins.html

Too much complexity for makes. I would prefer deprecating makes' lintPython and maintaining our own in Universe.


Startup Editor

Issue Type: Bug
I've set Workbench: Startup Editor to newUntitledFile and yet when I close the application and start it up again nothing opens.
Note: It was working properly before the last update.
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:09.080Z)
OS version: Windows_NT ia32 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8 x 3408)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.82GB (3.73GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

csharp
ms-
1.18.0

duplicate of https://github.com/Microsoft/vscode/issues/71837
This issue has already been fixed in our insiders version but not yet released to the stable version. To benefit from the fix, you can give our preview releases a try from: https://code.visualstudio.com/insiders/


Add reusable action for npm publishing

The action makes it easy to publish to npm using GitHub Actions after running some light validation (e.g. npm test).
Possible future improvements:

Validate that the version we're attempting to release isn't already published.
Automatically create GitHub Release with auto-generated changelog.
Add a confirmation step if running the script locally.
Add support for creating release branches (for minor versions) and the ability to release from them. Or alternatively, run the Action against a tag.

To Test Locally

Checkout the vip-actions repo and this branch.
Find the path for this script using pwd
cd to package you want to publish (you can also just create a test package via npm init and give it a unique name like <username>-npm-publish-test)
/path/to/vip-actions/npm-publish/bin/publish.sh -t patch

Going to merge this so we can test it out.


support --strictNullChecks

address #4 by explicitly typing members of SpiedMember  as non-nullable

Coverage remained the same at 100.0% when pulling 8b405025f21788b3aeea3e2ff829dfcbf2c2fc2d on bug/strict-null into 04501fe7d1822b6e9f10d0bf3f7e71cb94d64cea on master.


Add a Gitter chat badge to README.rst

pyrate-build/pyrate-build now has a Chat Room on Gitter
@FredStober has just created a chat room. You can visit it here: https://gitter.im/pyrate-build/pyrate-build.
This pull-request adds this badge to your README.rst:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Current coverage is 90.84%

Merging #1 into master will not affect coverage as of 4398ff7

@@            master      #1   diff @@
======================================
  Files            1       1
  Stmts          688     688
  Branches         0       0
  Methods          0       0
======================================
  Hit            625     625
  Partial          0       0
  Missed          63      63

Review entire Coverage Diff as of 4398ff7

Powered by Codecov. Updated on successful CI builds.


fix: run CLI dll extension using dotnet cli

see
https://github.com/ElectronNET/Electron.NET/issues/29

For "local development" with this repository this would be ok I guess. The current solution for our development here is quite frustrating because of the NuGet cache.
But just that we all are on the same side: This is just an issue with our development enviroment. In theory you should be able to run dotnet electron..., because this is the way to consume dotnet cli extensions.

Of course this is only for the "BuilAll.cmd" so this repo only for dev
once the CLI is published, it is either used from within a nuget of an executable in the path,
Still this buiildall.cmd has no idea about any of it

Ok - I will merge it tonight, maybe this will also resolve our nuget cache pain 👍


ag grid theme custom editor

Salt ag grid theme now only contain editable-cell which targets basic text editor. Teams has asked what's best approach for other type of editors.

Can we theme more native ag grid editors? e.g. Should Rich select editor be overridden with chevron icon instead of triangle?
What's the best way to support custom Salt form components (Dropdown, Combobox)? e.g. how to deal with additional padding in .ag-cell, how to pick correct board?

Some prototype maybe useful: https://stackblitz.com/edit/salt-ag-grid-theme-v2-mgojro?file=index.js,App.jsx,package.json,style.css

Galao Goal:  kickoff to help us define the requirements

Galao Goal: update theme to work with AG Grid theme to work with custom editor

Oct 7 - starting today with some stories

Latte Goal:  release Salt theme support for built-in Editor

Oct 17: Half way, will continue after #4275

Oct 21 : Ben to review previews in PR

moving into Lungo pending @bhoppers2008 review

Lungo : @bhoppers2008 blocked, requires review

Moved to Macchiato sprint. No capacity in Lungo

Macc Goal: Review by EOS (secondary priority to filter icon, which will unblock MTK)

red eye goal: @bhoppers2008  to review but @origami-z  has only half a sprint

Met with Ben

Cell editor doc example move under checkbox selection
Move checkbox column to not first column, to avoid confusion with ag row selection
Wording / guidance update

Prefer built-in, then custom editors
Rich select – more capability, requires enterprise

Styling

Check large text editor - textarea’s text / size/color/weight
Text area overlay, remove spacing-100, remove border, pad out
Default select: Right Chevron spacing
Select & rich select

Selected item top/bottom border
Dropdown list border -> blue (refer to dropdown)
Dropdown list shadow, check whether can match

TODO

Check HD Compact
Add Backlog: ag grid Custom editor examples doc to Q2

Red Eye goal: now reviewed, PR to update by end of wk 1 (before zh leaves)
Figma updates to follow in Feb (@bhoppers2008 to create)


Adding tests for returning invalid value when validation is false

Adding tests for PR https://github.com/angular-ui/ui-utils/pull/149 which @blowsie previously made.

UI.Utils modules was split in individuals repositories. If still valid, please consider re-submitting on its dedicated repository: https://github.com/angular-ui/ui-validate
See the README for details.


tesseract 4.00 exit 1 with several different tiffs

I get the below error when passing several different images to tesseract
ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK! object 0x1efe4f0 still has count 1 (id /usr/local/share/tessdata/dan.traineddatalstm-punc-dawg)
ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK! object 0x1ce7610 still has count 1 (id /usr/local/share/tessdata/dan.traineddatalstm-word-dawg)
ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK! object 0x1ef08c0 still has count 1 (id /usr/local/share/tessdata/dan.traineddatalstm-number-dawg)
ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK! object 0x3465870 still has count 1 (id /usr/local/share/tessdata/eng.traineddatalstm-punc-dawg)
ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK! object 0x298c100 still has count 1 (id /usr/local/share/tessdata/eng.traineddatalstm-word-dawg)
ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK! object 0x1ef0240 still has count 1 (id /usr/local/share/tessdata/eng.traineddatalstm-number-dawg)

I use a modification of this example from the wiki.. It works on most images but some images makes tesseract program return exitcode 1
I use OEM_LSTM_ONLY
tesseract::TessBaseAPI.Version() => 4.0.0-86-gbee8
Here are the images
https://imgur.com/a/e5vyzLL
  Pix *image = pixRead("/usr/src/tesseract/testing/phototest.tif");
  tesseract::TessBaseAPI *api = new tesseract::TessBaseAPI();
  api->Init(NULL, "eng");
  api->SetImage(image);
  api->Recognize(0);
  tesseract::ResultIterator* ri = api->GetIterator();
  tesseract::PageIteratorLevel level = tesseract::RIL_WORD;
  if (ri != 0) {
    do {
      const char* word = ri->GetUTF8Text(level);
      float conf = ri->Confidence(level);
      int x1, y1, x2, y2;
      ri->BoundingBox(level, &x1, &y1, &x2, &y2);
      printf("word: '%s';  \tconf: %.2f; BoundingBox: %d,%d,%d,%d;\n",
               word, conf, x1, y1, x2, y2);
      delete[] word;
    } while (ri->Next(level));
  }

install
- Install Leptonica
# apt-get install libleptonica-dev

- Install 4.00 from source
# apt-get install autoconf automake libtool pkg-config
# cd /var/bin && git clone https://github.com/tesseract-ocr/tesseract.git tesseract-4.00
# cd tesseract-4.00 && ./autogen.sh && ./configure && make -j $(nproc) && make install && ldconfig

- Install language fastest (4.00 - only works with OEM_LSTM_ONLY)
# cd /usr/local/share/tessdata && wget https://github.com/tesseract-ocr/tessdata_fast/raw/master/eng.traineddata && wget https://github.com/tesseract-ocr/tessdata_fast/raw/master/dan.traineddata

I already asked you to respect guidelines! Use tesseract user forum for asking support.

This must be a bug...?

Probably yes - in your code unless you prove it with tesseract executable ;-)
We DO NOT SUPPORT 3d party projects.

Ok
I have now copy/pasted the example directly from the wiki.. and it produce the extact same error with exitcode 1
This must be a bug in the API
#include <tesseract/baseapi.h>
#include <leptonica/allheaders.h>

/*
	g++ -rdynamic -O2 -std=c++11 test.cpp -o test -llept -ltesseract
*/

int main()
{
  Pix *image = pixRead("/root/test/003.tif");
  tesseract::TessBaseAPI *api = new tesseract::TessBaseAPI();
  api->Init(NULL, "eng");
  api->SetImage(image);
  api->Recognize(0);
  tesseract::ResultIterator* ri = api->GetIterator();
  tesseract::PageIteratorLevel level = tesseract::RIL_WORD;
  if (ri != 0) {
    do {
      const char* word = ri->GetUTF8Text(level);
      float conf = ri->Confidence(level);
      int x1, y1, x2, y2;
      ri->BoundingBox(level, &x1, &y1, &x2, &y2);
      printf("word: '%s';  \tconf: %.2f; BoundingBox: %d,%d,%d,%d;\n",
               word, conf, x1, y1, x2, y2);
      delete[] word;
    } while (ri->Next(level));
  }
}

This example is used as is and it produce the same error.. so this must be a bug somewhere in the API
https://github.com/tesseract-ocr/tesseract/wiki/APIExample#result-iterator-example

It is just short example what you can do with API - not how to program and handle all possible issue!

The error occurs at this line
api->Init(NULL, "eng");

Can't see how you can handle an issue when the API is initiated?

The code works fine for the most images.. but for some the program exit with 1

ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK!

To avoid the leaks, you should do what tesseract does here:
https://github.com/tesseract-ocr/tesseract/blob/f0a4d04187da58883dc86e7855b6f520b384d9eb/src/api/tesseractmain.cpp#L572-L578

Thanks :)
This should be a part of the examples..
But which file do I have to include?
test.cpp: In function ‘int main()’:
test.cpp:11:3: error: incomplete type ‘tesseract::Dict’ used in nested name spec                  ifier
   tesseract::Dict::GlobalDawgCache();
   ^

#include <tesseract/dict.h>
test.cpp:2:28: fatal error: tesseract/dict.h: No such file or directory

https://github.com/tesseract-ocr/tesseract/blob/f0a4d04187da58883dc86e7855b6f520b384d9eb/src/dict/Makefile.am#L12-L13
@stweil, I think we should install the dict.h header.

How can I manually install the headers? :) And do I only need dict.h ?

When adding dict.h I get a new error
In file included from test.cpp:2:0:
/usr/local/include/tesseract/dict.h:22:20: fatal error: ambigs.h: No such file or directory
 #include "ambigs.h"
                    ^

Copy it to the dir where the other tesseract headers live in your system.
Probably to /usr/local/tesseract.

You already did so (I missed your last message).

Which error are you referring now?

The one from the first post
ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK! object 0x1efe4f0 still has count 1 (id /usr/local/share/tessdata/dan.traineddatalstm-punc-dawg)
ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK! object 0x1ce7610 still has count 1 (id /usr/local/share/tessdata/dan.traineddatalstm-word-dawg)
ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK! object 0x1ef08c0 still has count 1 (id /usr/local/share/tessdata/dan.traineddatalstm-number-dawg)
ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK! object 0x3465870 still has count 1 (id /usr/local/share/tessdata/eng.traineddatalstm-punc-dawg)
ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK! object 0x298c100 still has count 1 (id /usr/local/share/tessdata/eng.traineddatalstm-word-dawg)
ObjectCache(0x7f3b07159740)::~ObjectCache(): WARNING! LEAK! object 0x1ef0240 still has count 1 (id /usr/local/share/tessdata/eng.traineddatalstm-number-dawg)

but why is the reason for the error?

In short: 'Object Lifetime'.

is it because the OCR result is empty or something?

No.

I don't see how someone using the API can handle the dawgs caching like tesseact does.
@stweil, can you say what you think about this issue?

The current code in tesseractmain.cpp is a hack, and we should not force users of the API to understand and use the same kind of hack in their code. So we need a better solution for the DawgCache object in the future.
Until that solution is available, there will be a memory leak for applications using the API. I don't think that this is a big problem as memory usage does not grow over time.

@stweil thanks for the confimation :)
looking forward to a solution..

This is not bug (at least not proved).
Solution is to use correctly API (which you did not).
If you do not how, asks at right place - use forum.

@amitdo @stweil

So how is the "correct" way to use the API?
Can't see anything from the examples?
https://github.com/tesseract-ocr/tesseract/wiki/APIExample


pre-populate onboarding primary color

This PR fix issue 270 https://github.com/Mirrorful/mirrorful/issues/270.
A similar colour name is suggested based on the Onboarding Primary colour selected in Step 1.
Here's a short video showing how it works. https://vimeo.com/815414449/b02661cf55

Hey @JoshuaRotimi I just took a look at the video - it looks amazing 😍  Can't wait for this to get merged ( It's a good thing I didn't pick it up - I wouldn't have been able to do it so quickly )
I've left some minor comments on the PR. Maybe you can address them if you feel they're appropriate and @alexdanilowicz agrees.

The deployment and workflow build keep failing. I think I may be missing something. Any ideas? @alexdanilowicz

Were you able to build it locally? I think it's possible the build is failing because we aren't using the ES6 import of the library correctly.
That being said, I looked at the library source code and it isn't a lot, just one distance calculating function from 'chromajs' and a list of colours. What do you think about building the same logic in our project instead of using the dependency?
Pro's:

No need to unnecessary download other color types
Control over color names, number of color names, delta function etc
Less dependency to worry about

Con:

We need to maintain this function, we can't just assume it'll always work.

I think the single con is as strong as the multiple pro's. But if you think we want it in-house. I'll be happy to make it ready this weekend.


GE: Kubernets Chatflow chooses wrong IP subnet

while deploying K8S on network: 9585
it chooses IP <IP_ADDRESS> for worker 2 which is not part of the network !

According to this reservation this IP is part of your network.
Bare in mind the full network is a /16 and each node inside your network is assigned a /24 subnet out of it.


CLI: Services startup services log to files

With the new implementation using the node-mac package, the stdout and stderr aren't logging application errors to the appropriate ~/.codeclimbers/codeclimbers.log files. Likely due to the fact that we are running a node script that then runs a bash script. Need to figure out how to pipe that together better.

Closed with #134


cmd/link: allow configuration of dsymutil and strip for darwin/mach-o linking

What version of Go are you using (go version)?
1.16.6
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/chancila/.cache/go-build"
GOENV="/home/chancila/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/chancila/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/chancila/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/snap/go/7954"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/snap/go/7954/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.6"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1637780390=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I am cross-compiling a darwin executable from linux with cgo enabled. I have successfully compiled everything but the link step fails due to xcrun missing since the go link command assumes xcrun exists if targeting darwin/mach when it really should probably only assume that if targeting darwin and host is darwin. I'm currently planning to work around this by creating a shim xcrun however having the ability to directly set these tools would be cleaner and easier to integrate with other build systems (namely bazel which I'm using in this case). The underlying tools have equivalents in open source llvm so they are not exclusive to macos hosts.
The code in question https://github.com/golang/go/blob/master/src/cmd/link/internal/ld/lib.go#L1643 should allow configuration of the tool in some way so that this use-case can be covered.
What did you expect to see?
Successful build
What did you see instead?
Linker error from ld/lib.go: Exitf("%s: running dsymutil failed: %v\n%s", os.Args[0], err, out) due to missing xcrun

@cherrymui

If as you say you are planning on writing a shim xcrun, would this not take care of the problems you describe?
Putting additoinal knobs/controls into the linker would mainly just make it more complicated and hard to understand (for example, for the 99% of folks not doing cross compilation, they might think that they need to specify a dsymutil path, or something to this effect).

I mean it would solve the issue in a very annoying way, in general this is a somewhat odd inconsistency given how the rest of the external c toolchain tools are configurable

trying to force xcrun in the path, I'm now running into another issue... https://github.com/golang/go/issues/43783
due to how bazel works pretty much everything is relative to a execution root...so the go invocation sees that the xcrun which is added in the c++ toolchain is relative and complains...

@chancila could you share more information about your C cross toolchain? What tools are included and how are they named? Thanks.
We used to just run dsymutil and strip from PATH. Some user reported that they installed GNU tools to PATH and it doesn't work.
Maybe we could use $CC --print-prog-name dsymutil. Would that work for you?

@cherrymui

hosted on linux (ubuntu 20.04)
targeting macos (amd64 and arm64)
plain llvm (12) release (from official llvm releases on github)
linux hosted apple ld64 (from https://github.com/tpoechtrager/cctools-port)
apple macos sysroot from xcode 12.1 (and 12.5 for arm64)

I'm exercising this whole thing through bazel and rules_go...the fundamental issue is that the go compiler tries to use xcrun when targeting mach binaries but it probably needs a fallback path when the compiler is hosted on non-macos systems rather than blindly using xcrun.
I think --print-prog-name would work fine actually, verifying with my toolchain it does the right thing.
I have successfully managed to cgo cross compile for both arm64 and amd64 by adding a shim xcrun wrapper in my system to /usr/bin globally as a hack, I would prefer to not have to do this as the toolchain is otherwise hermetic to the build and handled by bazel without modifying the system tools at all.

@chancila thanks! I think I'd go with --print-prog-name.


Issue with Settings popup close button

Hey,
While navigating through the application, I've opened up the "Settings" model and while looking into it, I've found this small issue with the "Close" button of the popup. What is happening here is, I'm not able to close the popup by clicking anywhere on the button including the edges(which is the intended behaviour) but instead you specifically need to hit the "X" inside the button which is a relatively small area and that can create the sense of sluggishness among the users if they can not close the popup in multiple tries.
I looked into the code and found that we can mitigate this issue here https://github.com/taniarascia/takenote/blob/master/src/containers/SettingsModal.tsx#L66 by replacing the following
<div className="action-button">
    <X
        size={20}
        onClick={() => {
        if (isOpen) {
            _toggleSettingsModal()
        }
        }}
    />
</div>

To this
<div
    className="action-button"
    onClick={() => {
        if (isOpen) {
            _toggleSettingsModal()
        }
        }}
>
    <X
        size={20}
    />
</div>

i.e. To move the click event to the surrounding div. I believe this will fix this issue.
Let me know what you think about it.
Regards!

Sounds good to me. Want to make a PR?

Sure! I'll work onto it.

@amitmerchant1990 any movement on this?


LICENSE file should go to top level directory

See my comment in sbt/sbt-header#42: The Apache License file should be located in the top level directory of a project.

Closed via #20.


Cherry pick two commits to release-1.0

/run-all-tests

Can you also pick 0cb7a7dedba66cfe91e47e3df68facbbeceba8d2?

Sure

/run-all-tests


Basic rebranding and parameters for Xaya

This updates Electrum-NMC with some basic rebranding (required things, like the data directory) and general network parameters for Xaya.  It is the first step in turning Electrum-NMC to Electrum-CHI.

Sorry, wrong repository.


iPrice RESTful API Generator doesn't have permission

A non-admin user is able to access to the API because the iPrice RESTful API Generator doesn't have any permission.
Permission should be added to this plugin so we can restrict users from accessing if they haven't been granted to manage this plugin

Fixed in #3


feat: add vpc

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[SMALLFIX] Reorder common and client in alluxio-core-server

@jsimsa @apc999

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12875/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/12876/
Test PASSed.


Add new elements to readme

Add vaadin-button, vaadin-form-layout and vaadin-text-field to the table of elements.

This change is

Button should be before combo-box.
Also, should we separate themable elements from core elements and put them to another table?

Button should be before combo-box.

🤦♂ – I definitely intended to put it there – not sure what happened 😆

Also, should we separate themable elements from core elements and put them to another table?

I don’t think so. They’ll all be themable eventually, and part of the same bundle/product.


feat: show next best grid amount

Description
The feature suggests the amount of money you would need to invest in a coin (as a new grid item or a manual trade) to expect closing the grid at break-event (i.e. without losing money) if the coin price eventually reaches your current sell percentage trigger.
The amount appears only for coins with active grid trades that have one selling grid.
The calculation is based on the following formula:
next best grid quantity = - qi * (1+(p - pi) / (gain * p)),
where gain = (triggerSellPercentage - 1)
and:

Current grid state
Suggested best trade

Quantity bought (qi)
Quantity to determine (q)

Last price (pi)
Current price (p)

Spent amount (ai)
Amount to spend (a)

Motivation and Context
When a coin goes deeper than expected for too long, I often find myself doing a lot of calculations to figure out the best next grid I would need to add to reactivate trading without losing money.
For new comers, it can be difficult to understand how to setup buy-grid-trades and this feature gives some better insight for grid management
How Has This Been Tested?
It's been running on my server.
Screenshots (if appropriate):

@rando128 merged!!!

Thx @chrisleekr! Hope it will help better adapt our grids to the market changes.

@chrisleekr when could you release this? The last one 0.93 is from Oct. 7

@peweb Sorry, I will release now.

@rando128 this is quite usefull feature but can we make it even better?
It is currently sugegsting the amount to buy at the current price. What if it could offer a purchase amount at a certain percentage difference from the current price?
When I analize the market I set up the next grid to be executed at say -3.5% from the last buy price. I want to profit of say 0.3% so... how to calculate the amount to buy?

Good suggestion. I'll look into it.
On Wed, Nov 30, 2022 at 11:25 AM peweb @.***> wrote:

@rando128 https://github.com/rando128 this is quite usefull feature but
can we make it even better?
It is currently sugegsting the amount to buy at the current price. What if
it could offer a purchase amount at a certain percentage difference from
the current price?
When I analize the market I set up the next grid to be executed at say
-3.5% from the last buy price. I want to profit of say 0.3% so... how to
calculate the amount to buy?
—
Reply to this email directly, view it on GitHub
https://github.com/chrisleekr/binance-trading-bot/pull/540#issuecomment-1331935846,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALMG62D7RGJG6XEENZNJP3WK4TTDANCNFSM6AAAAAASFIFFOQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


NO-JIRA: Add PodDisruptionBudget for router deployment

This PR was merged in a backport, the reverted and this will restore back and this is the timeline:
Timeline:

First backport merge: https://github.com/openshift/hypershift/pull/4661
Revert: https://github.com/openshift/hypershift/pull/4667
This PR will put back the initial PR

The Why:
I've misunderstood that a Bare metal HCP on 4.14 cannot deploy a MHC because it never reaches the IgnitionReached and mixed that with the PDBs. So to summarise, we need this backport to add the PDBs for the router deployment in 4.14 payload.
Original msg:
The router deployment is in the request serving path and should be protected from outages by a PDB like the other request serving components

/lgtm


Password reset link not working for usernames with "+"

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

[x] You've met the prerequisites.

[x] You're running the latest version of Parse Server.

[x] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup
Ran https://github.com/ParsePlatform/parse-server-example with changes for email adapter on AWS Elastic Beanstalk.
Steps to reproduce

Request for password reset for any existing user with username that contains "+".
In the password reset email, when the user click the link, "+" gets translated into space.

Logs/Trace
n/a
https://github.com/ParsePlatform/parse-server/blob/master/views/choose_password#L152
https://github.com/ParsePlatform/parse-server/blob/master/views/choose_password#L163
Seems choose_password is changing '+' in usernames to ' '. If I change ' ' back to '+' using the browser's dom inspector, changing password works.

Will be fixed very soon by #1001.


Chinese version

Hi, there! I have read your project, it is great! I wonder if I want to complete your project in Chinese version, which part of your project should I change? Thanks so much

All languages are the same. You only need to change the data and model.

Thanks so much

You welcome 🙏
2023년 4월 24일 (월) 오전 11:38, Bob Wayne @.***>님이 작성:

Closed #1 https://github.com/gyunggyung/DistilKoBiLSTM/issues/1 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/gyunggyung/DistilKoBiLSTM/issues/1#event-9076326270,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGL6VOW77UHYX5E33TKDNB3XCXRSPANCNFSM6AAAAAAXHYZIOE
.
You are receiving this because you commented.Message ID:
@.***>