Commands for terminal control in the debugger

Issue Type: Feature Request
It would be great to be able to send commands to the debugger console similar to those supported by any other first class terminal:
Most notably things I see missing:

Go back/forward in the command history (e.g. Ctrl+p / Ctrl+n)
History search based on partial matches, e.g. as with readline in the shell, see e.g. this, (e.g. also  Ctrl+p / Ctrl+n)
Commands to copy / paste text in the REPL from / to the debug console
Command to exit the REPL itself, while keeping the focus and cursor in the debug console, so that one can scroll up and generally navigate the screen history of the debugging console to e.g. copy / paste text from the history debugging console window. This is equivalent to e.g. the copy-mode in tmux, or e.g. the "char mode" in a terminal within Emacs.

For cross-reference, this was also also asked here.
VS Code version: Code - Insiders 1.45.0-insider (b83339a3a7bd8e3ec8a8b79deda9c37e0d91f094, 2020-04-21T05:38:43.781Z)
OS version: Darwin x64 19.4.0

This is a fair feature request, however we do not have it on our immediate plan. Thus assigning to backlog and we might add this in the future. Thanks

Thanks @isidorn  That's great to hear. On this note, the keybindings Up and Down specifically already go back / forward in the command history and they are pretty fundamental. Are they tied to any particular command ID? (or is there any way to configure them?)

@amelio-vazquez-reina yeah the commands are history.showPrevious and history.showNext and you should be able to customise them.
Code pointer https://github.com/microsoft/vscode/blob/1af3b9dce3d2ead4c3c0bb010dc47a4752af13d1/src/vs/platform/browser/contextScopedHistoryWidget.ts#L78


Incorrect parsing/coercing of invalid timestamps

Dask does not appear to handle out of bounds dates very well:
# minimal-0.csv
id,date
1,2017-10-31 00:00:00

# minimal-1.csv - out of bounds date/timestamp
id,date
2,4998-01-01 00:00:00

    import dask.dataframe as ddf

    df = ddf.read_csv('minimal-*.csv', dtype={'id': 'int',
                                              'date': 'str'},
                      parse_dates=['date']).compute()

For some reason, this doesn't fail, but produces incorrect timestamps
df
Out[1]:
   id                          date
0   1 2017-10-31 00:00:00.000000000
0   2 2075-03-26 02:07:11.452241920
df.dtypes
Out[2]:
id               int64
date    datetime64[ns]
dtype: object

Pandas will ignore the failing parse_dates directive and return an object dtype. pd.to_datetime will throw a pandas._libs.tslib.OutOfBoundsDatetime error as expected.
Is it possible to use pd.to_datetime(.., error='coerce') with Dask (which would return NaT in this case?).
pandas (0.21.0rc1)
distributed (1.19.3)
numpy (1.13.3)
dask (0.15.4)

ddf.read_csv('minimal-*.csv', parse_dates=['date']).head(n=2) seems to just drop the row. How is this impacted by the distributed scheduler? The source CSV (not the minimal example) has ~300M rows with ~100 dodgy dates.

Unfortunately, I don't think there's much dask can. It'd be nice if pandas had an option to throw an error when the CSV parser encounters an out of bounds value.

This should be fixed by #2863.
The issue here was that the first partition worked, so the dtype of the column was found to be a datetime64. In the other partitions dask tries to convert mismatched dtypes, and succeeds in this case as numpy astype is much more lax with conversion (leading to the overflow you saw above):
In [1]: import numpy as np

In [2]: np.array(['4998-01-01 00:00:00'], dtype='M8[ns]')
Out[2]: array(['2075-03-26T02:07:11.452241920'], dtype='datetime64[ns]')

To fix this, we now error nicely when a parse_dates column fails to properly convert. Your example:
>>> df = dd.read_csv('minimal-*.csv', parse_dates=['date']).compute()
<traceback...>
ValueError: Mismatched dtypes found in `pd.read_csv`/`pd.read_table`.

The following columns failed to properly parse as dates:

- date

This is usually due to an invalid value in that column. To
diagnose and fix it's recommended to drop these columns from the
`parse_dates` keyword, and manually convert them to dates later
using `dd.to_datetime`.

As you and @TomAugspurger both mentioned, you can use dd.to_datetime (note that we implement this method, no need to use map_partitions) to convert datetimes, failing or coercing as needed. The error message also suggests that you use this.

Also filed a bug for this in numpy: https://github.com/numpy/numpy/issues/9956.

Thank you @jcrist for looking into this, that sounds like good news!
I've been using a workaround similar to what @TomAugspurger suggested.
I somehow had convinced myself that dd.to_datetime did not support errors='coerce', but I might have been playing with too many things at the same time when trying to figure out what was happening :)


overview.md typo

It seems there is a blank or LF in headless- and service in url, which leads to error format

/lgtm
/approve


postgres: add connection limit

Currently lnd does not apply a limit to the number of open postgres connections. In high load scenarios, the postgres server may reject new connections, leading to errors in lnd.
This is also why the connection limit is set to 500 to pass the async benchmark integration test:
https://github.com/lightningnetwork/lnd/blob/b0fa19e8b0430b221e3eace92d619f858deabaf0/Makefile#L197
This PR adds a configuration option to set the maximum number of connections in lnd. By setting this to a value that is below the server limit, it shouldn't be possible to run into errors because of being denied another connection.

I've added this to the 0.14 release notes because I think it will prevent lots of questions and error cases.


Unused processed images should not be copied to /public

I discovered this while tightening up the test suite in this department. One could argue that these images don't hurt anyone, and it was probably implemented like this so speed things up, but they take up disk space and should not be there.
This is a common pattern:
{{ $original := resources.Get "sunset.img" }}
{{ $firstStep := $original.Resize "400x" }}
{{ $thumb := $firstStep.Fill "100x100" }}
{{ $thumLarge := $firstStep.Fill "200x200" }}

Currently, all the processed versions of that image (including $firstStep) will be copied to /public. This will be even more visible once we add image filters to the mix.
These should follow the rules of how the transformations in Hugo Pipes works (e.g. fingerprint, resources.Get):
A processed image will only be published (copied to /public) if one of .RelPermalink or .Permalink is called on that processed image.
/cc @regisphilibert

Yes makes sense, and as the rule keeps being enforced, I think it's time to introduce https://github.com/gohugoio/hugo/issues/6267


make sys table expressions type safe

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1172042). Click here to learn what that means.
The diff coverage is 87.28%.

@@            Coverage Diff            @@
##             master    #5596   +/-   ##
=========================================
  Coverage          ?   82.74%
  Complexity        ?    11762
=========================================
  Files             ?     1390
  Lines             ?    45235
  Branches          ?     5619
=========================================
  Hits              ?    37430
  Misses            ?     5188
  Partials          ?     2617

Impacted Files
Coverage Δ
Complexity Δ

...te/operation/collect/sources/SysTableRegistry.java
100% <ø> (ø)
2 <0> (?)

...ava/io/crate/operation/user/SysUsersTableInfo.java
95% <100%> (ø)
8 <1> (?)

...ion/reference/sys/RowContextReferenceResolver.java
86.93% <87.17%> (ø)
56 <46> (?)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1172042...a42f553. Read the comment docs.


Fix typo in tooltip-examples page

It's = it is
Its = possessive pronoun

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

May you sign the CLA please?

@FezVrasta For some reason, I cannot.
I open https://cla-assistant.io/FezVrasta/popper.js?pullRequest=380, then I click on "Sign in with GitHub to agree", I sign in with GH, and then I get redirected to https://cla-assistant.io.
No confirmation or anything, and the signature does not get registered.

Try with  cla-assistant.io/FezVrasta/popper.js

@FezVrasta heh, I just found the bug https://github.com/cla-assistant/cla-assistant/issues/247 and used that link. 👍


Use labels and annotations from istio/api repo

This moves a few labels and annotations to using constants defined in API. The 3 changes are separate commits if that makes review easier. Please note the proxyConfig one is actually changing its value (not yet shipped, so not breaking), the others are just changing where its defined

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test unit-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test unit-tests_istio

integ-local-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-local-tests_istio

release-test_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test release-test_istio

integ-distroless-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-distroless-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test unit-tests_istio

integ-local-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-local-tests_istio

release-test_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test release-test_istio

integ-distroless-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-distroless-k8s-tests_istio

lint_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test lint_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test unit-tests_istio

integ-local-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-local-tests_istio

release-test_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test release-test_istio

integ-distroless-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-distroless-k8s-tests_istio

lint_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test lint_istio

integ-pilot-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-pilot-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test unit-tests_istio

integ-local-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-local-tests_istio

release-test_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test release-test_istio

integ-distroless-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-distroless-k8s-tests_istio

lint_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test lint_istio

integ-pilot-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-telemetry-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test unit-tests_istio

integ-local-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-local-tests_istio

release-test_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test release-test_istio

integ-distroless-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-distroless-k8s-tests_istio

lint_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test lint_istio

integ-pilot-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-security-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test unit-tests_istio

integ-local-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-local-tests_istio

release-test_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test release-test_istio

integ-distroless-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-distroless-k8s-tests_istio

lint_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test lint_istio

integ-pilot-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-security-k8s-tests_istio

integ-mixer-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-mixer-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test unit-tests_istio

integ-local-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-local-tests_istio

release-test_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test release-test_istio

integ-distroless-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-distroless-k8s-tests_istio

lint_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test lint_istio

integ-pilot-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-security-k8s-tests_istio

integ-mixer-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-mixer-k8s-tests_istio

integ-multicluster-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-multicluster-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test unit-tests_istio

integ-local-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-local-tests_istio

release-test_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test release-test_istio

integ-distroless-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-distroless-k8s-tests_istio

lint_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test lint_istio

integ-pilot-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-security-k8s-tests_istio

integ-mixer-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-mixer-k8s-tests_istio

integ-multicluster-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-multicluster-k8s-tests_istio

integ-galley-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-galley-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test unit-tests_istio

integ-local-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-local-tests_istio

release-test_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test release-test_istio

integ-distroless-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-distroless-k8s-tests_istio

lint_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test lint_istio

integ-pilot-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-telemetry-k8s-tests_istio

integ-security-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-security-k8s-tests_istio

integ-mixer-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-mixer-k8s-tests_istio

integ-multicluster-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-multicluster-k8s-tests_istio

integ-galley-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-galley-k8s-tests_istio

integ-conformance-k8s-tests_istio
29f6f05b9419a2d4bfe7770a9f82f339bd101898
link
/test integ-conformance-k8s-tests_istio

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.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-galley-k8s-tests_istio
0f8d9139f800dc88eb2a32816f0ebd1cdfc211c7
link
/test integ-galley-k8s-tests_istio

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-galley-k8s-tests_istio

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

unit-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test unit-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

unit-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test unit-tests_istio

release-test_istio
1527ff290501476380705024823d81c241d08117
link
/test release-test_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

unit-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test unit-tests_istio

release-test_istio
1527ff290501476380705024823d81c241d08117
link
/test release-test_istio

lint_istio
1527ff290501476380705024823d81c241d08117
link
/test lint_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

unit-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test unit-tests_istio

release-test_istio
1527ff290501476380705024823d81c241d08117
link
/test release-test_istio

lint_istio
1527ff290501476380705024823d81c241d08117
link
/test lint_istio

integ-security-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-security-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

unit-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test unit-tests_istio

release-test_istio
1527ff290501476380705024823d81c241d08117
link
/test release-test_istio

lint_istio
1527ff290501476380705024823d81c241d08117
link
/test lint_istio

integ-security-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-conformance-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

unit-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test unit-tests_istio

release-test_istio
1527ff290501476380705024823d81c241d08117
link
/test release-test_istio

lint_istio
1527ff290501476380705024823d81c241d08117
link
/test lint_istio

integ-security-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-pilot-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

unit-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test unit-tests_istio

release-test_istio
1527ff290501476380705024823d81c241d08117
link
/test release-test_istio

lint_istio
1527ff290501476380705024823d81c241d08117
link
/test lint_istio

integ-security-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-distroless-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

unit-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test unit-tests_istio

release-test_istio
1527ff290501476380705024823d81c241d08117
link
/test release-test_istio

lint_istio
1527ff290501476380705024823d81c241d08117
link
/test lint_istio

integ-security-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-telemetry-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

unit-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test unit-tests_istio

release-test_istio
1527ff290501476380705024823d81c241d08117
link
/test release-test_istio

lint_istio
1527ff290501476380705024823d81c241d08117
link
/test lint_istio

integ-security-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-galley-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

unit-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test unit-tests_istio

release-test_istio
1527ff290501476380705024823d81c241d08117
link
/test release-test_istio

lint_istio
1527ff290501476380705024823d81c241d08117
link
/test lint_istio

integ-security-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-mixer-k8s-tests_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

unit-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test unit-tests_istio

release-test_istio
1527ff290501476380705024823d81c241d08117
link
/test release-test_istio

lint_istio
1527ff290501476380705024823d81c241d08117
link
/test lint_istio

integ-security-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-mixer-k8s-tests_istio

gencheck_istio
1527ff290501476380705024823d81c241d08117
link
/test gencheck_istio

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.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-local-tests_istio

unit-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test unit-tests_istio

release-test_istio
1527ff290501476380705024823d81c241d08117
link
/test release-test_istio

lint_istio
1527ff290501476380705024823d81c241d08117
link
/test lint_istio

integ-security-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-conformance-k8s-tests_istio

integ-pilot-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-pilot-k8s-tests_istio

integ-distroless-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-distroless-k8s-tests_istio

integ-telemetry-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-telemetry-k8s-tests_istio

integ-galley-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-galley-k8s-tests_istio

integ-mixer-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-mixer-k8s-tests_istio

gencheck_istio
1527ff290501476380705024823d81c241d08117
link
/test gencheck_istio

integ-multicluster-k8s-tests_istio
1527ff290501476380705024823d81c241d08117
link
/test integ-multicluster-k8s-tests_istio

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.

In response to a cherrypick label: #23393 failed to apply on top of branch "release-1.6":
Using index info to reconstruct a base tree...
M	operator/pkg/helmreconciler/reconciler.go
Falling back to patching base and 3-way merge...
Auto-merging operator/pkg/helmreconciler/reconciler.go
Applying: Use new proxy config annotation
Applying: Move TLS label
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	operator/pkg/helmreconciler/reconciler.go
M	pilot/pkg/model/service.go
M	pilot/pkg/serviceregistry/external/conversion.go
Falling back to patching base and 3-way merge...
Auto-merging pilot/pkg/serviceregistry/external/conversion.go
CONFLICT (content): Merge conflict in pilot/pkg/serviceregistry/external/conversion.go
Auto-merging pilot/pkg/model/service.go
Auto-merging operator/pkg/helmreconciler/reconciler.go
CONFLICT (content): Merge conflict in operator/pkg/helmreconciler/reconciler.go
Patch failed at 0003 Move TLS label

cc @howardjohn @brian-avery @irisdingbj
The cherry-pick failed and does not have a manual cherry picked PR for 1.6. John found this earlier. I'm using this to document. Please link associated PR when done.

/cherry-pick release-1.6

@jacob-delgado: #23393 failed to apply on top of branch "release-1.6":
Using index info to reconstruct a base tree...
M	istioctl/pkg/kubernetes/client.go
M	operator/pkg/helmreconciler/reconciler.go
Falling back to patching base and 3-way merge...
Auto-merging operator/pkg/helmreconciler/reconciler.go
Auto-merging istioctl/pkg/kubernetes/client.go
Applying: Use new proxy config annotation
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	pilot/cmd/pilot-agent/main.go
M	pkg/kube/inject/testdata/inject/traffic-annotations.yaml
M	pkg/kube/inject/testdata/inject/traffic-annotations.yaml.injected
Falling back to patching base and 3-way merge...
Auto-merging pkg/kube/inject/testdata/inject/traffic-annotations.yaml.injected
CONFLICT (content): Merge conflict in pkg/kube/inject/testdata/inject/traffic-annotations.yaml.injected
Auto-merging pkg/kube/inject/testdata/inject/traffic-annotations.yaml
Auto-merging pilot/cmd/pilot-agent/main.go
Patch failed at 0002 Use new proxy config annotation

In response to this:

/cherry-pick release-1.6

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.

@jacob-delgado: new issue created for failed cherrypick: #23629

In response to this:

/cherry-pick release-1.6

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.


Fixed CI temporarily

This is just a temporary fix. Will refactor CI later.

Task linked: CU-hq1h41 Fix pip 20.3 CI


ERROR: Failed building wheel for causal-conv1d with torch>2.4

pip install torch==2.4.0 helps

@tridao  would it be possible to release torch 2.5 wheels?

it ended up being an NVCC version for me. I was able to solve it by doing the following:
wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2204/x86_64/cuda-ubuntu2204.pin
sudo mv cuda-ubuntu2204.pin /etc/apt/preferences.d/cuda-repository-pin-600
wget https://developer.download.nvidia.com/compute/cuda/12.4.0/local_installers/cuda-repo-ubuntu2204-12-4-local_12.4.0-550.54.14-1_amd64.deb
sudo dpkg -i cuda-repo-ubuntu2204-12-4-local_12.4.0-550.54.14-1_amd64.deb
sudo cp /var/cuda-repo-ubuntu2204-12-4-local/cuda-*-keyring.gpg /usr/share/keyrings/
sudo apt-get update
sudo apt-get -y install cuda
export PATH=/usr/local/cuda/bin${PATH:+:${PATH}}
export LD_LIBRARY_PATH=/usr/local/cuda/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
nvcc --version

I ran into similar issues, but was able to install successfully on Python 3.11, PyTorch 12.5.1, and CUDA 12.4 simply by installing from source (e.g. pip install causal-conv1d @ git+https://git@github.com/Dao-AILab/causal-conv1d@v1.4.0).


Include html exercises

Review by commit.
Basically, we now include the exercise htmls (we didn't before!) and then change the node file_name to include the language.

Seems fine apart from one question.

Might need to rebuild the casettes for tests?

Yey tests pass!


asyncio examples request

Hello,
Its so happy to find this library released as the first io_uring api stuff for Python.
As a newbie for the io_uring and underlayer Kernel IO API, too many details are required to learn it.
Could you provide some asyncio style based python examples for understanding ?
p.s
python-3.6.8 with pip-9.0.3 install liburing at newest released Centos (version 8.1.1911), will case datestamp ModuleNotFoundError about "file liburing/setup.py", line 3, thus pip-3 install liburing will fail if not manually run pip-3 install datestamp first.
p.s.s
libs/liburing seems should git clone from https://github.com/axboe/liburing which is empty, and case the pip install liburing process failure.
unless clone this repo to local directory and overwriting libs/liburing by https://github.com/axboe/liburing, and then pip install path/to/this/repo works.
at least works for me :} .

for example can you look at test folder files for now?
could you install directly from github using pip install --upgrade git+https://github.com/YoSTEALTH/Liburing
datestamp should have worked as its preinstalled here https://github.com/YoSTEALTH/Liburing/blob/master/pyproject.toml#L2

I will upload newer version to pypy once i get a chance to do more tests

thanks for reply.
test folder files seems not relate to Python's asyncio style coding what io_uring and liburing may mainly focus on, and liburing for python binding is brand new (i wanna it working with the async and await keywords in a right way officially) especially for newbie like me.
yes, pip install --upgrade git+https://github.com/YoSTEALTH/Liburing success.
last time i failed because:

I did missing '--upgrade' option which i fool myself "i am do installing liburing fresh new, not upgrade", then it case git's submodule axboe/liburing missing and fail.
Centos (8.1.1911) default builtin pip (9.0.3) is too old to understood the PEP 517 (pyproject.tomal), and pip-3 -U pip solved datestamp not found issue.

so, patch setup.py a PEP 517 support checking maybe an idea for fool proof ?
thanks again for spending of your time.

Python liburing is really low level library to something like asyncio. There are plans for Trio to adapt to using io_uring https://github.com/python-trio/trio/issues/932 its still very much in early planning stages, most of the feature needed are only in newer linux version 5.5+ and such...


fixed .unload() and .destroy() for jquery string selectors

currently it isn't possible to use .destroy() or .unload() when using jquery selector strings for the arrows. If you do so, your arrows simply will be removed, since they are obviously not an object or DOM node. This fixes this wrong behaviour.

I belive this is no longer an issue :)


Help! I cant run my app.

I can't run my app on ios simulator. It was working perfectly a few months ago. But now I have a problem.
How to fix this error?

I delete node_module and pod files. Then I reinstall. But not fixed.

Add --resetCache to the start command to clear any caches


Add full log of the repo_json file

We need to log the response from https://github.com/ossf/scorecard-action/blob/main/entrypoint.sh#L50, because there seems to be intermittent errors when querying this endpoint which are hard to fix: see https://github.com/ossf/scorecard-action/issues/154
@rohankh532 are you interested in taking this one?
/cc @azeemshaikh38

@rohankh532 are you interested in taking it as your farewell :-)?

closed by https://github.com/ossf/scorecard-action/pull/211


Return light colors when platformColor is not supported (iOS13)

I think it would be good to return the light colors when the device is running iOS 13 or below, otherwise there will be no color at all.
wdyt?
I can do a PR if so

Just noticed it's fixed in RCTConvert on master!


RX 580 and Linux: SteamVR Home and Beat Saber are laggy, display driver crashes, jitter

Please follow the general troubleshooting steps first:

[x] I carefully followed the instructions in the README and completed successfully the setup wizard.
[x] I read the ALVR Wikis here and here

Quick description:

SteamVR either crashes my display driver, or in the rare occasions it does work, FPS is low and everything (including SteamVR and Beat Saber) is jittery and laggy; basically unusable. I've been told a few times in Discord that this isn't expected.
GItHub Discussion: https://github.com/alvr-org/ALVR/discussions/860

Environment:

CPU: Ryzen 7 2700X
GPU: RX 580 (8GB, POLARIS10, DRM 3.42.0, 5.14.15-300.fc35.x86_64, LLVM 13.0.0) (0x67df))
Audio: Realtek ACL 1120 (ASUS PRIME-X470 PRO built-in, 4.0 speaker channels)
Headset: Quest 2 (V34)
OS: Fedora 35 (GNOME 41, tried both Xorg and Wayland)
Kernel: 5.14.15-300.fc35.x86_64
glxinfo: Pastebin
ALVR: alvr-16.0.0-1.0.0+1635915618+8dc973b6.x86_64 (trae32566)
SteamVR: 1.20 and linux_v1.14.16

Description

I start Steam (desktop launcher entry), and then launch ALVR (desktop launcher entry), which then automatically starts up SteamVR
Dashboard is accessible from http://localhost:8082/
Usually when launching ALVR on my Quest 2, it will say it's restarting the server, freeze the screen on the headset, and then my computer's display will go black, show some purple corruption all over everything for maybe 5-10 seconds, and then blank my display entirely.
In the rare-event ALVR launches properly on both the headset and computer, SteamVR Home starts, and is jittery and low FPS. I launch Beat Saber on the PC and it appears in the HMD, but it too is a jittery low FPS mess. Here is a short video showing the low FPS and slow drawing on the sides over USB.
I've had this happen on Fedora 34, openSUSE Tumbleweed, with the pre-compiled Ubuntu binaries on the Nightly repo, self-compiled, and trae32566's repo

Troubleshooting

Tried different routers (one is known-good with Air Link and Virtual Desktop on Windows)
Did USB forwarding (Option 2 - SideQuest, although I typed the two commands as-is with my distro's adb package)
Tried Xorg and Wayland on GNOME 40 and 41
Tried stable, beta, and linux_1.14 SteamVR builds

I have the same exact problem. Screen blanks, purple & green squares. Pretty normal driver crash for AMDGPU.
I'm on an RX 5700XT.
Occasionally after the crash, journald will log the following output:
Dec 25 13:43:30 compooter kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
Dec 25 13:43:35 compooter kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
Dec 25 13:43:35 compooter kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=97985, emitted seq=97987
Dec 25 13:43:35 compooter kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process steamtours pid 23410 thread steamtours:cs0 pid 23535
Dec 25 13:43:35 compooter kernel: amdgpu 0000:2f:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
Dec 25 13:43:35 compooter kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ disable failed
Dec 25 13:43:36 compooter kernel: amdgpu 0000:2f:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
Dec 25 13:43:36 compooter kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed
Dec 25 13:43:36 compooter kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Dec 25 13:43:39 compooter kernel: amdgpu_cs_ioctl: 31 callbacks suppressed
Dec 25 13:43:39 compooter kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

This is also a fairly standard AMDGPU crash log. Looks like the Steam Home is crashing our driver here. Might be something you have to reach out to valve about.


onChange doesn't fire

When already date selected, onChange won't fire if user wants to clear the input

@alidehghan I'll check it ASAP.

@alidehghan this issue fixed.

thanks


Move from fn to FnOnce

We originally used fn because there was no need, but building more complex stuff needs FnOnce; for example, a framework writing their own listen method will want to use stuff from self inside of the server, but you can't create that stuff inside the fn passed to new.

let's just use https://doc.rust-lang.org/std/ops/trait.Fn.html

yeah, i miss-spoke 👍


CustomScrollView within ExpansionTile error

Hi, Tried to fix this reading some documentation and some open issues but was not lucky.. Could someone please help?
I am getting this error:

type 'bool' is not a subtype of type 'double' in type cast

`import 'package:flutter/material.dart';

class SampleData {
  SampleData(this.title, [this.children = const <SizedBox>[]]);

  final String title;
  final List<SizedBox> children;
}

final List<SampleData> data = <SampleData>[
  SampleData("IT", [
        SizedBox(
          height: 300,
          width: 300,
          child: CustomScrollView(
            scrollDirection: Axis.horizontal,
            slivers: <Widget>[
              new SliverToBoxAdapter(
                child: Text('fesfefes'),
              ),
            ],
          ),
        ),
  ]),
];

class Branch extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Test 123'),
      ),
      body: Container(
        width: 500,
        child: ListView.builder(
          scrollDirection: Axis.horizontal,
          itemBuilder: (BuildContext context, int index) => Item(data[index]),
          itemCount: data.length,
        ),
      ),
    );
  }
}

// Displays one Entry. If the entry has children then it's displayed
// with an ExpansionTile.
class Item extends StatelessWidget {
  const Item(this.sample);

  final SampleData sample;

  Widget _buildTiles(SampleData root) {
    return SizedBox(
      width: 500,
      child: ExpansionTile(
        key: PageStorageKey<SampleData>(root),
        title: Text(root.title),
        children: root.children,
      ),
    );
  }

  @override
  Widget build(BuildContext context) {
    return _buildTiles(sample);
  }
}
`

Hi @fernandocoronatomf
everything looks alright with this sample code
This platform is not meant for assistance on personal code. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


AVIF images not working

Past Issues Searched

[X] I have searched open and closed issues to make sure that the bug has not yet been reported

Issue is a Bug Report

[X] This is a bug report and not a feature request, nor asking for support

Describe the bug
If I use AVIF images, I get this error:
Error: error building site: "/home/pedro/Documentos/GitHub/m3upt-lotusdocs/content/docs/intro.md:1:1": "/home/pedro/.cache/hugo_cache/modules/filecache/modules/pkg/mod/github.com/colinwilson/lotusdocs@v0.1.0/layouts/docs/_markup/render-image.html:18:77": execute of template failed: template: docs/_markup/render-image.html:18:77: executing "docs/_markup/render-image.html" at <.Width>: error calling Width: this method is only available for image resources
Expected behavior
It works fine if I use the JPG format.
Screenshots
No response
Environment
- OS: I use Arch btw
- Browser: Chromium
- Browser Version: latest

Hugo's image processing doesn't support the AVIF image format currently :( - see here

Yes, I know that Hugo can't process AVIF images.
However I use AVIF images with other Hugo themes without problems. The theme just has to not process the image.
Some themes like Clarity or Hugo Bootstrap even have a neat feature to display AVIF images with fallback formats (in case the browser doesn't support it).

Ah, I see.
That's more of a feature request then. I'll close this. Make a feature request in the discussion section, I track (and implement) feature requests there.


support for # type: ignore

Description
An option to parse "# type: ignore" comments and disable the flake8-annotations checks on the corresponding lines of code.
Rationale/Use Case
I am currently using mypy to check the type annotations on a large code base, but that is slow to run. I would like to use flake8-annotations (or the ruff re-implementation) before calling mypy in order to be able to catch missing annotation faster than with mypy and thus to be able to iterate faster.
My code contains quite a few "# type: ignore" comments that are currently ignored by flake8-annotations, which gives me many errors when using flake8-annotations while mypy does not raise any error. I would like to have the option to tell flake8-annotations to detect   "# type: ignore" comments so that, like mypy,  it does not check the corresponding lines and so that I can get  flake8-annotations check passing on that code without having to modify the code on each line where I currently use # type: ignore.

I can see this being interesting, and shouldn't be too difficult to explore since ast parses these comment locations already. I think it would have to be opt-in because we would not be able to do anything about specific ignore codes, e.g. # type: ignore[arg-type] would be treated the same as # type: ignore, which could be an annoying caveat for many.

(or the ruff re-implementation)
As an aside, it's worth noting that I do not have any influence on this implementation, this is wholly Astral's work and under their editorial control.

"If you'd like to use the ruff plugin you'll need to request this feature there as well." Understood. I believe that having the new option in flake8-annotations would help in motivating the implementation of an equivalent option in ruff.

This should be available now to try out. I don't have a large amount of latent code to explore this with so please let me know if there are any issues.

I tried and it seem to work as expected:). I am still getting some errors in my code base in places mypy does not give me any error. The two type of errors  are due to two reasons

# type: ignore can be added at the beginning of a file in which case mypy while ignore type errors in the entire file. In contrast, Flake8-annotations will not apply the ignore to the entire file.
mypy does not complain about missing annotation for the the first argument in class methods (usually self) while Flake8-annotations does.

The first should be easy to add, I'll make another issue to track. For the second, it sounds like you want to ignore ANN101 (See: #75).


wip: Feat/ohif tmtv

PR Checklist

[ ] Brief description of changes
[ ] Links to any relevant issues
[ ] Required status checks are passing
[ ] User cases if changes impact the user's experience
[ ] @mention a maintainer to request a review

https://github.com/OHIF/Viewers/issues/2864

CI does not work, will create another PR


Featuremodel objects

All applicable methods return objects. Also hcanged the return types of double to Float where only a float value was stored anyway.
This depends on the annotations PR. Can pnly be merged if that pr is merged as is.

yay!

Did you run it through your pipeline?


Could not start application logger error on Elixir 1.17.2 Erlang 27.0.1

I tried to implement Sentry 10.6.2 in my phoenix project and followed these steps.
In lib/myapp_web/endpoint.ex
use Sentry.PlugCapture at the start
plug Sentry.PlugContex after plug Plug.Parsers
In config/config.exs
config :logger,
  backends: [:console, Sentry.LoggerBackend],
  format: "$time $metadata[$level] $message\n",
  metadata: [:request_id]

config :sentry,
  dsn: System.get_env("SENTRY_DSN", ""),
  environment_name: Mix.env(),
  included_environments: [:prod, :dev],
  enable_source_code_context: true,
  root_source_code_paths: [File.cwd!()]

After I do this I get the following error on mix phx.server
10:02:54.599 [notice]     application: logger
    exited: {bad_return,
                {{'Elixir.Logger.App',start,[normal,[]]},
                 {'EXIT',
                     {badarg,
                         [{maps,from_list,
                              [[request_id]],
                              [{error_info,#{module => erl_stdlib_errors}}]},
                          {'Elixir.Enum',into_map,1,
                              [{file,"lib/enum.ex"},{line,1532}]},
                          {'Elixir.Logger.App',start,2,
                              [{file,"lib/logger/app.ex"},{line,40}]},
                          {application_master,start_it_old,4,
                              [{file,"application_master.erl"},
                               {line,295}]}]}}}}
    type: temporary

10:02:54.599 [error]   crasher:
    initial call: application_master:init/3
    pid: <0.6531.0>
    registered_name: []
    exception exit: {bad_return,
                     {{'Elixir.Logger.App',start,[normal,[]]},
                      {'EXIT',
                       {badarg,
                        [{maps,from_list,
                          [[request_id]],
                          [{error_info,#{module => erl_stdlib_errors}}]},
                         {'Elixir.Enum',into_map,1,
                          [{file,"lib/enum.ex"},{line,1532}]},
                         {'Elixir.Logger.App',start,2,
                          [{file,"lib/logger/app.ex"},{line,40}]},
                         {application_master,start_it_old,4,
                          [{file,"application_master.erl"},{line,295}]}]}}}}
      in function  application_master:init/3 (application_master.erl, line 143)
    ancestors: [application_controller,<0.10.0>]
    message_queue_len: 1
    messages: [{'EXIT',<0.6532.0>,normal}]
    links: [<0.45.0>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 376
    stack_size: 29
    reductions: 77
  neighbours: []
** (Mix) Could not start application logger: exited in: Logger.App.start(:normal, [])
    ** (EXIT) an exception was raised:
        ** (ArgumentError) argument error
            (stdlib 6.0.1) :maps.from_list([:request_id])
            (elixir 1.17.2) lib/enum.ex:1532: Enum.into_map/1
            (logger 1.17.2) lib/logger/app.ex:40: Logger.App.start/2
            (kernel 10.0.1) application_master.erl:295: :application_master.start_it_old/4

I do not know where I am going wrong and would appreciate some help.

I might be wrong but this does not seem related to Sentry in any way. You don't configure :logger's :metadata like that; that metadata should be logger:metadata/0.
Instead, you want to configure that metadata for the :console (and/or Sentry) backends:
config :logger, :console,
  metadata: [:request_id]

Does that fix the issue? In the meantime, closing this issue as I cannot see any reference to Sentry anywhere. Feel free to comment and we can absolutely reopen if it's Sentry's fault 😉

I might be wrong but this does not seem related to Sentry in any way. You don't configure :logger's :metadata like that; that metadata should be logger:metadata/0.

My config is based on taking the original code on a fresh phoenix project:
config :logger, :console,
  format: "$time $metadata[$level] $message\n",
  metadata: [:request_id]

And combining it with what is found at the end of this page https://glitchtip.com/sdkdocs/elixir
That's why I modified my config/config.exs to look like that

Right, but you changed it so that you're not changing the :logger's :console config anymore, but the global :logger config.
Change this:
config :logger,
  backends: [:console, Sentry.LoggerBackend],
  format: "$time $metadata[$level] $message\n",
  metadata: [:request_id]

to this:
config :logger,
  backends: [:console, Sentry.LoggerBackend]

config :logger, :console,
  format: "$time $metadata[$level] $message\n",
  metadata: [:request_id]


model .pth

hi and thanx for your code 👍
but if i want use it i have 2 way:

train your configs from scratch : it take much time to train each one even if i use colab it takes me out after one epoch ):
you give us the .pth checkpoint file : if you upload the checkpoint and log files it doesnt need we train it from first and we just need to test
+could you please upload  .pth and log file here or send it to me the link of them in google drive??
my second email is<EMAIL_ADDRESS>

The models and logs will be uploaded right away. Now I am collecting and sorting models.

The models and logs will be uploaded right away. Now I am collecting and sorting models.

where is .pth files for obb detections???

The models and logs will be uploaded right away. Now I am collecting and sorting models.

where is .pth files for obb detections???

Hello, I recently uploaded the models of oriented rcnn. Please check here for details.


Add API to allow creating Screen using custom terminfo as well as custom tty.

A followup to #148 -- currently NewTerminfoScreenFromTty still uses local OS environment to get the terminfo and there is no public API to override it.
This PR adds such API, in form of

function NewTerminfoScreenFromTtyTerminfo that also accepts terminfo instance
function LookupTerminfo that exposes current name-to-terminfo lookup procedure

While NewTerminfoScreenFromTty still defeaults to LookupTerminfo with $TERM contents to maintain backwards compatability.

yes, I can see how this would be useful -- thanks for your contribution.


ignore HTF test framework artifact directory

Reasons for making this change:
A popular haskell testing framework is HTF. By default the framework writes historical testing data to .HTF when running test-suites.
Links to documentation supporting these rule changes:
See http://hackage.haskell.org/package/HTF-<IP_ADDRESS>/docs/Test-Framework-CmdlineOptions.html (opts_historyFile)

@agrafix thanks!


[Bug] WeekStart placeholder returning incorrect date

Describe the Bug
The {{ .WeekStart }} template placeholder is always returning the Tuesday of the current week, regardless of the input date. It should instead return the Monday of the week for the specified date, but instead, it is consistently returning the Tuesday of the current week.
Steps to Reproduce
Steps:

Use the {{ .WeekStart }} template placeholder with any date input (current or past).
Observe that it always returns the Tuesday of the current week, instead of the Monday of the week for the given date.
Try using the placeholder with various dates (e.g., past dates) and note that it still returns the incorrect Tuesday of the current week.

Expected Behaviour
The {{ .WeekStart }} placeholder should return the Monday of the week corresponding to the specified date, not the Tuesday of the current week.
Screenshots or Logs
No relevant screenshots or logs are available at the moment. However, the issue can be reproduced with the steps above.
Environment

OS: macOS
Dodl Version: 0.2.2
Go Version: 1.23
Additional context: none

Checklist

[x] I have searched the existing issues for similar bugs.
[x] I have run make build locally and confirmed the issue persists.

After investigating, I found that the issue stemmed from the tests overriding a WeekStart placeholder using the value of the WeekStart function (and a test date) but this same override wasn't being done for production code (so the production code was calling the WeekStart function with no input date and thus weird dates were being returned.
To resolve this, I’ve split the existing functionality into two new placeholders to give more flexibility and ensure the correct behavior:
weekStart: A function that calculates the start of the week for a specific date. This allows for dynamic date-based calculations. Example usage: {{ .Now | weekStart | date "02-01-2006" }}
This will return the Monday of the week for the reference date (whatever date is provided).
WeekStart: A standalone placeholder that returns the start of the week (Monday) based on the reference date used by the application, not the current date. Example usage: {{ .WeekStart }}
This will consistently return the Monday of the current week according to the reference date.
With these changes, both placeholders should now work as expected, fixing the issue of returning Tuesday instead of Monday. Feel free to test these and let me know if there are any further issues.

https://github.com/matthewchivers/dodl/pull/44 merged - closing.


Import and initialize prisma

Bug description
@prisma/client did not initialize yet
How to reproduce

Expected behavior
No response
Prisma information

// Add your schema.prisma

// Add your code using Prisma Client

Environment & setup

OS:
Database:
Node.js version:

Prisma Version

i just import prisma, but he cannot initialize


Add Maestro UI & workflow editor

Will add UI support for better usability.

This is very important

can we use https://github.com/camunda/camunda-modeler instead of building from scratch?


could not replicate the sample code of TreeWASDir

Hi, there:
Can someone please let me know the difference between TreeWAS and TreeWASDir? It seems that the former is not updated for a long while.
I am trying to follow the example code in TreeWASDir github page. However, I got the following error.

Can someone please let me know how to fix this?
Thank you & Best regards,
Jie

looks like you haven't installed the dependencies. are you able to load Rgraphviz and graph?

Thank you very much!
The error message is now gone, after I loaded library(Rgraphviz) in R.
However, there is no plot in the output, but only some text as shown below.

As I asked in my original email, can you please let me know the difference between TreeWAS and TreeWASDir? What does "Dir" here mean? It seems that the github page for TreeWAS has not been updated for a long while. Is it retired?
Best regards,
Jie


Add support for mongo express

We have support for redis commander and pgadmin, we should add support for mongo express.
https://hub.docker.com/_/mongo-express/

@timheuer did you want to take a stab at this? Note that there was an issue with mongo express where it wasn't possible to access it without logging it. But I note that the container image was recently updated so maybe that bug was fixed.

Yeah, likely same pattern as others I would imagine.

@timheuer Does your PR address this issue? Can it be closed?


[Bug] CC0057 Displayed even if the parameter is used.

As can be seen the warning is displayed in a constructor that passes the argument to the parent.

Sorry It is the same as #251

Exactly.


Problems after the target host is remote desktop

Problems after the target host is remote desktop
Dear Developer Hello!
It's a pleasure to try your open source project, I have some problems after using it, here is my advice:

The target host uses Microsoft's remote desktop connection. After the link is disconnected, the target host enters the lock screen interface. At this time, the PowerRemoteDesktop_Viewer interface enters a black screen, and the interface cannot be reactivated.
After this situation occurs, you cannot enter the target host desktop after restarting the connection in powershell.
I have tried to set the host login mode to automatic login, but I still cannot bypass this scenario.

Additional Issues: Frame Delay and File Delivery
Can the screen lag be improved? (I tried reducing ImageCompressionQuality to 30%, still lag)
Can file transfer be done through the clipboard?
Looking forward to your reply, thank you!
(maybe there is something semantically wrong because I used a translator)

Hello,
Thank you for your feedback

Lock Screen Issue

This is a known and expected behavior, since the project is ment to use only PowerShell code and not rely on external application / services it will be very difficult to support "Secure Desktop" / Winlogon capture.
To do so, you need to create dedicated system service running on another desktop (winlogon desktop) and stream this desktop.
I can't yet guarantee at 100% that it is not possible in pure PowerShell since I did not tried yet but following my existing knowledge it is likely not possible (to be confirmed).
If my initial feeling is confirmed, I will probably offer as an option an extra plugin to attach to Winlogon in a near future.
Until that moment, what I can offer is to propose a new option to next version, this option will while the server is running temporarily disable UAC prompt and Lock Screen.

Frame Delay

This is the next big feature to be available in coming version.
Actually the whole screen is sent thus slowing the streaming process considerably.
I will add a motion update mode which will only send pieces of screen that changed thus improving considerably the streaming speed. Stay tune for this improvement in a next release.

Clipboard File

I'm planing to add a such feature in a future release too, first I want to focus on streaming speed through motion update.
Regards,
DCSC

End files

End files

What do you mean?

UPDATE: after some tests and research I finally found a way to capture secure desktop (UAC Prompt, Logon etc...) without the need to use an external app or dll but just from PowerShell with certain conditions I can control and respect.
I will work on it tomorrow and try to push something very shortly .
I will adapt my PowerRemoteDesktop_LogonUI to PowerShell

@DarkCoderSc That's great. I'm also troubled by this problem. If I'm in powerremote desktop_ It would be better to specify a common screen resolution for everyone on the server

Additional Issues: Frame Delay and File Delivery Can the screen lag be improved? (I tried reducing ImageCompressionQuality to 30%, still lag)

Hello, the v3.0 was just released.
It would be cool if you could leave a feedback about the new performance.
better or worse
Thank you in advance


config: some variables in configuration-qemu-virtiofs.toml are not replaced with actual values

Description of problem
# XXX: Source file: "@CONFIG_QEMU_VIRTIOFS_IN@"

.
.
.

shared_fs = "@DEFSHAREDFS_QEMU_VIRTIOFS@"

@chavafg that was replaced with this PR https://github.com/kata-containers/runtime/commit/4134571e86ac7736f722a6937ce54fdced85ce11#diff-ebce02844da8831ba833219d9a0d0d36 , it seems that you are missing something in the MAKEFILE


Docker image tags based on kafka version

It would be awesome if the docker image had more tags than just "latest".  How difficult would it be for there to be different tags for different versions?  I'm working with some other systems to do not yet support kafka 0.10.

I agree, it would be great to have an old image with kafka 0.8 still available on docker hub.

Would also love this, 0.9 specifically

This is indeed keeping us from using the Spotify image right now, as we need reproducible builds.


Destiny

Add option to spend multiple force point in one command

Doesn't happen enough in the game to warrant all the code.  Just type "!destiny l" as many times as you need too


Add field to vCard generator - ease ?

How difficult/easy is it to add more fields to vCard generator?

I just did it with a help of https://en.wikipedia.org/wiki/VCard
For vCard 3.0
For what I need of course.
I don't have time to contribute at the moment, but when I do, will definitely add it if it is possible.

string payload = string.Format("BEGIN:VCARD\r\nVERSION:3.0\r\nN:{0};{1};;;\r\nFN:{1} {0}\r\nTEL;TYPE=HOME,CELL:{2}\r\nTEL;TYPE=WORK,VOICE:{3}\r\nADR;TYPE=HOME,PREF:;;{4} ;{5};;{6};\r\nURL:{7}\r\nEMAIL:{8}\r\nORG:{9}\r\nTITLE:{10}\r\nADR;TYPE=WORK,PREF:;;{11}; {12};;{13};\r\nEND:VCARD",
 lastName, firstName, mobile, workphone, homeAddress, homeCity, homeZip, url, email, company, title, workAddress, workCity, workZip);

The question was if it is easy. The answer is yes. So I'll close this issue. If you want specific fields added, please raise a new issue and name the fields that shall be added. :-)


[Feature] Allow users to select materialization type in salesforce_formula_view

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
salesforce_formula_utils.salesforce_formula_view.sql hardcodes the materialization. As a user I am unable to change that, even if I set a configuration in the dbt_project.yml or create a config in the model sql file using CTE. The only way I can change the materialization is by changing the salesforce_formula_view.sql file and hard coding it to materialize as a table. This is problematic as I need to use these updated formula tables for downstream models.
There should be an argument that allows the user to change the materialization configuration of a model.
Describe alternatives you've considered
I have tried changing the config in the dbt_project.yml. Also, tried changing the config in the model sql file above the macro. I have also created a CTE using the macro and then overriding the config in the model sql file. None of these solutions work. Only hardcoding the salesforce_formula_view.sql file.
Are you interested in contributing this feature?

[ ] Yes.
[X] Yes, but I will need assistance and will schedule time during your office hours for guidance.
[ ] No.

Anything else?
No response

Closed this issue as the feature has been implemented in the latest version of the package.


swift 3.0

update swift 3.0

@yavuz Many thanks for pull request.
Swift 3 is supported in release 0.0.9.


PACKAGES: ION causing IOS build to fail from mod-template

make flu-mob-run
apple@x-MacBook-Pro client % make flu-mob-run
fatal: No names found, cannot describe anything.
cd /Users/apple/workspace/go/src/github.com/winwisely99/packages/maintemplate/client/ && flutter run -d all
Launching lib/main.dart on win’s iPhone in debug mode...

Signing iOS app for device deployment using developer identity: "Apple Development: XXX XXX (YYY)"
Running pod install...                                              1.8s
CocoaPods' output:
↳
      Preparing

    Analyzing dependencies

    Inspecting targets to integrate
      Using `ARCHS` setting to build architectures of target `Pods-Runner`: (``)

    Fetching external sources
    -> Fetching podspec for `Flutter` from `Flutter`
    -> Fetching podspec for `flutter_plugin_android_lifecycle` from
    `.symlinks/plugins/flutter_plugin_android_lifecycle/ios`
    -> Fetching podspec for `flutter_webrtc` from `.symlinks/plugins/flutter_webrtc/ios`
    -> Fetching podspec for `image_picker` from `.symlinks/plugins/image_picker/ios`
    -> Fetching podspec for `path_provider` from `.symlinks/plugins/path_provider/ios`
    -> Fetching podspec for `path_provider_macos` from `.symlinks/plugins/path_provider_macos/ios`
    -> Fetching podspec for `shared_preferences` from `.symlinks/plugins/shared_preferences/ios`
    -> Fetching podspec for `shared_preferences_macos` from
    `.symlinks/plugins/shared_preferences_macos/ios`
    -> Fetching podspec for `shared_preferences_web` from
    `.symlinks/plugins/shared_preferences_web/ios`
    -> Fetching podspec for `sqflite` from `.symlinks/plugins/sqflite/ios`
    -> Fetching podspec for `url_launcher` from `.symlinks/plugins/url_launcher/ios`
    -> Fetching podspec for `url_launcher_macos` from `.symlinks/plugins/url_launcher_macos/ios`
    -> Fetching podspec for `url_launcher_web` from `.symlinks/plugins/url_launcher_web/ios`

    Resolving dependencies of `Podfile`
      CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is
      only perfomed in repo update
    [!] CocoaPods could not find compatible versions for pod "flutter_webrtc":
      In Podfile:
        flutter_webrtc (from `.symlinks/plugins/flutter_webrtc/ios`)

    Specs satisfying the `flutter_webrtc (from `.symlinks/plugins/flutter_webrtc/ios`)` dependency
    were found, but they required a higher minimum deployment target.

    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:328:in
    `raise_error_unless_state'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:310:in `block in
    unwind_for_conflict'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:308:in `tap'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:308:in
    `unwind_for_conflict'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:684:in
    `attempt_to_activate'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:254:in
    `process_topmost_state'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:182:in `resolve'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolver.rb:43:in `resolve'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/resolver.rb:94:in `resolve'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/installer/analyzer.rb:986:in `block
    in resolve_dependencies'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/user_interface.rb:64:in `section'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/installer/analyzer.rb:984:in
    `resolve_dependencies'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/installer/analyzer.rb:124:in
    `analyze'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/installer.rb:410:in `analyze'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/installer.rb:234:in `block in
    resolve_dependencies'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/user_interface.rb:64:in `section'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/installer.rb:233:in
    `resolve_dependencies'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/installer.rb:156:in `install!'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/command/install.rb:52:in `run'
    /Library/Ruby/Gems/2.6.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/lib/cocoapods/command.rb:52:in `run'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.8.4/bin/pod:55:in `<top (required)>'
    /usr/local/bin/pod:23:in `load'
    /usr/local/bin/pod:23:in `<main>'

Error output from CocoaPods:
↳

    [!] Automatically assigning platform `iOS` with version `8.0` on target `Runner` because no
    platform was specified. Please specify a platform for this target in your Podfile. See
    `https://guides.cocoapods.org/syntax/podfile.html#platform`.

Error running pod install
make: *** [flu-mob-run] Error 1

I noticed also that flutter packages automatic watcher in VSCODE when to grab a SQLlite dependency.
We do NOT want a SQLite dependency at all BTW.

@winwisely99 The # platform: ios, '9.0' comment in ios/Podfile needs to be removed, because GoogleWebRTC.framework requires iOS 9.0 as a minimum


No Kafka ElasticSearch enable magic

This removes the logic where "if the Kafka server configured in phoebus-alarm-server/phoebus-alarm-logger is localhost, then automagically enable Kafka", and same for ElasticSearch.
Now the user always has to configure Kafka and ElasticSearch themselves, and we document how to do it in the Phoebus alarm guide.
Fixes #54.

Tests are ok except a time difference between the alarm time and the message time.


Update Python support matrix

Update the Python support matrix, dropping Python 3.6 support and adding 3.9, 3.10 and 3.11.
To do this, we must also update a few other things, such as the pre-commit plugins. The list of changes is thus:

tox: Replace '--strict' with '--strict-markers'
Use collections.abc, not collections
pre-commit: Bump plugin versions
Add support for recent Python versions
Use latest Python + Action versions in CI

@ikalnytskyi I'm going to cross my fingers and hope you're okay with me merging this to get the CI passing again :crossed_fingers: If you're not, please feel free to revert it and accept my apologies for interfering.


probability tensor contains either inf, nan or element < 0

CUDA_VISIBLE_DEVICES=0 python llama_inference.py decapoda-research/llama-7b-hf --wbits 4 --load llama7b-4bit.pt --text "this is llama"
Loading model ...
Done.
Traceback (most recent call last):
File "llama_inference.py", line 115, in
generated_ids = model.generate(
File "/root/miniconda3/lib/python3.8/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "/root/miniconda3/lib/python3.8/site-packages/transformers-4.27.0.dev0-py3.8.egg/transformers/generation/utils.py", line 1452, in generate
return self.sample(
File "/root/miniconda3/lib/python3.8/site-packages/transformers-4.27.0.dev0-py3.8.egg/transformers/generation/utils.py", line 2504, in sample
next_tokens = torch.multinomial(probs, num_samples=1).squeeze(1)
RuntimeError: probability tensor contains either inf, nan or element < 0

Changed to use Triton instead of CUDA now. It seems that this problem won't happen.


--custom-oidc-scopes flag has no effect

Describe the bug
When using OIDC then providing custom scopes via the --custom-oidc-scopes flag to the gitops-server binary doesn't result in the server actually requesting the scopes defined in the flag value.
Environment

Weave-Gitops Version: 0.15.0
Flux Version: 0.38.3
Kubernetes version: 1.26

To Reproduce

Create the oidc-auth Secret with valid OIDC parameters
gitops create dashboard wego --password=foo --export | yq e 'select(.kind == "HelmRelease") as $hr | select(.kind != "HelmRelease") as $o |$hr.spec.values.additionalArgs=["--custom-oidc-scopes=foo,bar"] | ($hr, $o)' | k apply -f-
k -n flux-system port-forward svc/wego-weave-gitops 9001
In the browser navigate to http://localhost:9001
Open the developer tools of the browser to see network requests
Click on "LOGIN WITH OIDC PROVIDER"
Look at the list of requests and see that the Oauth2 request's scope URL query parameter doesn't have any of the values provided through the --custom-oidc-scopes flag

Expected behavior
The server should requests the scopes provided in the flag value.
Actual Behavior
The scopes provided in the flag value aren't used.
Additional Context (screenshots, logs, etc)
The reason for this happening is this line where the value is always overridden.

Yes, right now there is an implicit and probably undoc'd behaviour where all config should specified in either but not both of:

cli flags
oidc secret

If secret is found, everything specified on the cli will be ignored.
Solutions:

Doc this better (given)
Panic if both are provided (fail fast with a good error)
Merge the cli/env and secret configs? Could be harder to debug sometimes, but might be a more desired behaviour, specify scopes/claims etc in "config" / env / flags and read secrets (clientSecret (and clientId ?)) from a secret.

If you asked me I would ditch all the OIDC-related CLI flags, especially the client secret one as we likely don't want to encourage our users to have secrets lurking in Deployment resources (that usually aren't as well protected as Secrets in both, the cluster and also the source of truth, i.e. Git repository or the like).


Fix assertions not visible on timeout

Fix #22

Thanks. My only concern is possible performance impact for kata with many assertions/test cases. Some kata has a lot.
I'm assuming it shouldn't be too bad.

I can also update when adding next Python version. I'm hoping automatic update will work for most of them.

This was included in Python 3.10


how to do this?

Say please, how you do this?

Say please, how you do this?

It's a plugin. zsh-autosuggestions

Thank

Plugin


Go: Slice literal for new postings

Simplifies the expression for creating a new postings list. This suggestion came from @arp242 though I'm not sure why he didn't include it in his PR
I have found no performance regressions with this change

I don't recall suggesting this, but in the old version it would pre-allocate to the cap of 4, saving a few alloc+copy in case of appends.
If it doesn't matter in testing then that's fine, but sometimes you can get big performance win by pre-allocating a small array size in tight loops.

Yeah I'm not sure on the memory layout of Go whether a copy is required as soon as the slice is appended to. Anyway in this case the optimisation doesn't appear to help and complicates the code


chore: snap.diff changed

Summary

Test Plan

Require Documentation?

[ ] No
[ ] Yes, the corresponding rspack-website PR is __

@IWANABETHATGUY I noticed that the snap.diff has changed after running cargo test in the crates/rspack directory. Could you please check if the changes are acceptable?


Installation script fails with ubuntu 24.04

Installation script doesn't work anymore. Tried 2 options and both fail
###Direct install
`
bash -c "$(curl -sL https://get-gnmic.openconfig.net)"
Downloading https://github.com/openconfig/gnmic/releases/download/null/gnmic_ull_linux_x86_64.tar.gz
tar: This does not look like a tar archive
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Failed to install gnmic
For support, go to https://github.com/openconfig/gnmic/issues
`
###Install using pkg option:
bash -c "$(curl -sL https://get-gnmic.openconfig.net)" -- --use-pkg Downloading https://github.com/openconfig/gnmic/releases/download/null/gnmic_ull_linux_x86_64.deb Preparing to install gnmic ull from package dpkg-deb: error: unexpected end of file in archive magic version number in /tmp/tmp.zWqBKlXYsp/gnmic_ull_linux_x86_64.deb dpkg: error processing archive /tmp/tmp.zWqBKlXYsp/gnmic_ull_linux_x86_64.deb (--install):  dpkg-deb --control subprocess returned error exit status 2 Errors were encountered while processing:  /tmp/tmp.zWqBKlXYsp/gnmic_ull_linux_x86_64.deb

this is likely a gh rate limiting in action
you can invole curl separately and see the contents of the downloaded file


Need Help !!! Decentraland Desktop Client Problem

What happened?
decentralands new desktop client.. when im trying to change server in-game it throws me on chrome instead of change it via desktop client
Steps to reproduce
add metamask wallet in desktop clients wallet connecting section please
Operating System
Windows 7  (6.1.0) 64bit
Wallet
Metamask
CPU
AMD Athlon(tm) II X3 445 Processor
GPU
NVIDIA GeForce GT 430 969MB
RAM
6141MB
Kernel Version
1.0.0-1918065042.commit-710b300
Unity Version
desktop-main.commit-7e33653
Realm
dg
NameTag
W1KO#45f6

What happened?
decentralands new desktop client.. when im trying to change server in-game it throws me on chrome instead of change it via desktop client
Steps to reproduce
add metamask wallet in desktop clients wallet connecting section please
Operating System
Windows 7 (6.1.0) 64bit
Wallet
Metamask
CPU
AMD Athlon(tm) II X3 445 Processor
GPU
NVIDIA GeForce GT 430 969MB
RAM
6141MB
Kernel Version
1.0.0-1918065042.commit-710b300
Unity Version
desktop-main.commit-7e33653
Realm
dg
NameTag
W1KO#45f6

How are you trying to change server in-game?

This is because the scene is triggering a URL, not an issue of the Decentraland client.
Althought I know a fix is on the works for scenes to be able to trigger realm changes.


Add v4 TPU manifests samples

Updates TPU v4 sample manifests for Kuberay v1.1

@kevin85421 All done, please take a look.

Fixed the broken tests.


Update SHOW RESTORE.md

Add two missing fields.
What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[x] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：
This will clarify the return fields of the query return.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

Signed-off-by: Kaiwei Wang<EMAIL_ADDRESS>

Thank you for your contribution @fieldsfarmer .


Allow Pointer Lock for Webview?

I want use pointer lock api in my webview panel, but:
Blocked pointer lock on an element because the element's frame is sandboxed and the 'allow-pointer-lock' permission is not set.

What is the use case?

@mjbvz I want create graph editor (something like that react-diagrams demo) in webview panel and i need to use pointer lock for dragging playground without lose focus from webview panel.

@mjbvz we want to allow continuous dragging without letting go mouse button. Something like this: demo video.

This works for electron webviews, but not when "webview.experimental.useIframes": true


Removing deprecated "duration" field from ancla.

Hi @joe94, when are we planning to remove deprecated duration field from ancla as while retrieving hooks its giving a misleading duration field to the users.

Hey @utsavbatra5, we've had some initial discussions about this but since changes in this area might be API impacting, it might take us some time to deliberate especially as we are tackling some other higher priority tasks at the moment.
Find some notes from our initial discussion:
Some of the options to consider for the flow to indicate how long a webhook should last:
A) Keep only 'until' field
Changes:

Remove duration field from struct used in both GET /hooks and POST /hook endpoints.
Use the until field as the only field dictating when a webhook expires: the field is a quoted string in RFC 3339 format. The until field is heavily used internally for determining until what specific time a webhook destination should be served.

B) Keep both 'duration' and 'until' fields
Changes:

Keep 'duration' as the API field that determines a webhook's expiration on the POST /hook endpoint: this has the advantage that the format is more concise than 'until' (i.e. '3m' vs 2019-10-12T07:20:50.52Z')
Keep 'until' and set the value to be RegistrationTime + Duration. When users request to see their webhooks using the 	GET /hooks endpoint, they would be able to see both 'duration' and 'until' fields.

Other considerations made so far:

Regardless of which field is used to specify the expiration date for the webhook, the expiration should be capped at 5mins. If an invalid value is specified, an error should be returned. Depending on the use case, we may make this cap configurable.

HI @joe94
when  we are getting response for  GET /hooks endpoint we are getting duration as<PHONE_NUMBER>00 instead of this we are expecting this to be 5m or 300s.


Using Operation

Thanks for your many help!
I want to switch various filters to video real timely. I made some code but it's not flexible to use so how can I use => operation for MTIImage? For example, I am using below code to switch filters real timely.

 let composition = MTIVideoComposition(asset: asset, context: renderContext, queue: DispatchQueue.main, filter: { [weak self] request in
        return FilterGraph.makeImage { output in
            let out = self?.processfilter(source: request.anySourceImage!)
            out! => output
      }!
 })

 private func processfilter(source: MTIImage) -> MTIImage? {
    switch flag {
    case 0:
        let pixellateFilter = MTIPixellateFilter()
        let dotScreenFilter = MTIDotScreenFilter()

        pixellateFilter.inputImage = source
        dotScreenFilter.inputImage = pixellateFilter.outputImage
        return dotScreenFilter.outputImage!
    case 1:
    }
    return nil
}

How can I exchange with specific operation(=>)? like below.

 private func processfilter(source: MTIImage, outputPort: (ImageReceiverInputPort) -> Void) -> MTIImage? {
    switch flag {
    case 0:
        let pixellateFilter = MTIPixellateFilter()
        let dotScreenFilter = MTIDotScreenFilter()
        return source => pixellateFilter => dotScreenFilter => outputPort
    case 1:
    }
 }

private func processfilter(source: MTIImage) -> MTIImage? {
    switch ... {
        case ...
        return FilterGraph.makeImage { output in
            return source => filterA => filterB => output
        }
    }
}


Upgrade SBT to 0.13.9, sbt-assembly to 0.14.1

Can one of the admins verify this patch?

I think you forgot to actually upgrade sbt-assembly

@sjrd Argh... sorry, yes, you are correct. I had one in my global SBT conf, which caused me to upgrade this in the first place. Will fix.

Updated.

LGTM. Jenkins, test this please

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2499/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/3234/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2501/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/3236/
Test FAILed.

For some strange reason, this PR causes library/scalastyle to fail.

Argh ... ScalaStyle is an SBT plugin too? Maybe it needs to be updated, too...

perhaps you are running afoul of https://github.com/scalastyle/scalastyle/issues/156

@SethTisue Thanks for the hint!

Scalastyle 0.8.0 is out. Maybe it resolves this problem.

@sjrd Updated.

Jenkins, retest this please

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2547/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/3290/
Test PASSed.

LGTM


GitHub secrets exposed in PR comments

Describe the bug
There is a critical issue that needs immediate attention. When a GitHub secret is passed in via the arg_env input parameter, it gets automatically redacted in Job Summaries. However, this redaction does not occur in the PR comments posted by the tf-via-pr action.
Screenshots

Given that the workflow simply returns its command input to the PR comment, I'm inclined to label this as expected behaviour: especially given the context that sentive input variables (e.g., credentials/tokens) should be passed in as TF_VAR_<name> prefixed environment variables, as documented here.
With that said, I do see value in optionally hiding user-configured input arguments from the PR comment, if not to hide secrets, but limit it to relevant information only. For example, hiding the -lock argument since it doesn't add a whole lot of value in each PR comment.


Add GitHub throttling logic

This adds throttling and retry logic to the plugin. This code is untested, since I have no idea how to properly run this locally.
I've reused most of the logic I used in the past to crawl GitHub, that solved this limit issues (https://github.com/elastic/issue-crawler/blob/master/index.js#L15-L32) as well as the @actions/github readme, about how to properly extend the octokit instance with plugins.

@supertopher let's give this a shot.

done.  looks great Tim.
I also was thinking about switching this logic to use Oauth which I think from documentation seems to have  a higher rate limit.  let's see how this goes though.  I'll release 'v14' for the other side... or I could move the 13 tag.  let's talk about it in slack.  merging this


Rename FBSimulatorFramebuffer to FBFramebuffer

All the the other Frambuffer classes (including the delegate) begin with FBFramebuffer so the container object should too.

@facebook-github-bot shipit


No error shown why push notification is not sent

What App Center service does this affect?
Name of service or sdk with the issue.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@divyamakkar26 thanks for this, but can you please provide a detailed description of the issue? We provided the issue template for you to populate with the data we need to understand the problem.


seed -> cache_seed

Why are these changes needed?
openai introduces a new param in chat completion api:
seed: This feature is in Beta. If specified, our system will make a best effort to
sample deterministically, such that repeated requests with the same seed and
parameters should return the same result. Determinism is not guaranteed, and you
should refer to the system_fingerprint response parameter to monitor changes
in the backend.
"Determinism is not guaranteed" - that's a reason to keep the seed in autogen, but rename it to cache_seed. Then, we'll be able to support both openai seed and autogen seed.
### Tasks
- [x] seed -> cache_seed in code + doc
- [x] add this change to migration guide
- [ ] seed -> cache_seed in notebooks & blogposts for retrieve chat, teachable agent, mathchat

The last task won't be performed in this PR.
Related issue number
#599
Checks

[x] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report

Merging #600 (51a2ea9) into main (2a96e4d) will decrease coverage by 4.76%.
The diff coverage is 30.76%.

@@            Coverage Diff             @@
##             main     #600      +/-   ##
==========================================
- Coverage   34.04%   29.28%   -4.76%
==========================================
  Files          25       24       -1
  Lines        3005     2998       -7
  Branches      668      668
==========================================
- Hits         1023      878     -145
- Misses       1906     2053     +147
+ Partials       76       67       -9

Flag
Coverage Δ

unittests
29.28% <30.76%> (-4.70%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

autogen/agentchat/groupchat.py
61.20% <ø> (ø)

autogen/code_utils.py
45.45% <ø> (-5.38%)
:arrow_down:

autogen/version.py
100.00% <100.00%> (ø)

autogen/oai/client.py
25.73% <20.00%> (-11.77%)
:arrow_down:

autogen/oai/completion.py
15.17% <28.57%> (ø)

... and 5 files with indirect coverage changes

see -> cache_seed in notebooks & tests for llava_agent as well?

I had a look at https://github.com/microsoft/autogen/blob/main/test/agentchat/test_conversable_agent.py
I didn't find a test case for reproducible replies. I think we don't need to test use_cache directly on OpenAI's API (that would be tested by OpenAI), but I think it might be a good idea to add a test to test for reproducible, identical replies on the Autogen class, like conversable agent?
Perhaps we can test for:
if use_cache is set: then we expect at least 2 out of 5 calls from the conversable agent to be identical, because there is no gurantee.
else: we expect at most 3 out of 5 calls from the agent to be identical
The above numbers are arbitrary and dependent on the prompt/temperature (to be set in the test case). Any thoughts?


[ spi_host ] Transition to D1

This IP is largely ready for transition to D1.  Please reach out to me if you need a review.
Signed-off-by: Martin Lueker-Boden<EMAIL_ADDRESS>

FYI @mateenfaisal

I believe @eunchan is the primary reviewer for SPI Host IP. He works on SPID. Right, @dsandrs?

The functional documentation is now complete (minus implementation details) and in #7135
The note about SRAMs has been removed.
Some of the D2 details have been checked off (I'll be coming back around late next week to check off more)

We can't merge this before we have a "Done" in the spec column. So #7135 needs to go in first, but beyond that there's nothing blocking from my side.


Cleans up image loading for Android

…pe images are explicitly set; reduces the shouldUpdate calls on textileimage types

@asutula I'm going to bang this guy out to android users as the app is pretty slow to use without it


Added 'start' and 'watch' scripts

It'll be helpful for debugging and making changes on the fly

I do not have write access so someone else will have to merge this
@blueblackzebra @AlenJoseph