[RemoveContainer] Cannot bind argument to parameter 'Path' because it is null

Getting this error message when executing RemoveContainer.
$ExtensionsFolder var is not set before doing the JoinPath to initialize the $containerFolder var.
Fixed by adding parameter [string] $ExtensionsFolder in Remove-NavContainer.ps1

Sorry wrong url ... How can I delete this issue ?


Add table syntax to 005 knitr lesson

A brief table would be useful, perhaps in Iris section.
| Species    | Mean Petal Length |
|------------|-------------------|
| setosa     | <r code for mean> |
| versicolor | <r code for mean> |
| virginica  | <r code for mean> |

Fairly minimal example added in 229de90.


Expose memmap dtype in data config

This is expose dtype in the data config so that we can support reading memmap files with different dtypes

@2015aroras  Thanks for the review. Updated the PR to address the comment

@2015aroras Went though instructions and added all the missing things. Can I get another 👍  so that it kicks off all the auto checks?

There are style issue due to imports. Make sure to follow the steps here so that required automatic checks pass.

@2015aroras  Went though instructions and added all the missing things. Can I get another 👍 so that it kicks off all the auto checks?


Shorten name of constants of Person's attributes #399

Fixes #399
Each of these classes: Name, Phone, Email, Address and Tag has a MESSAGE_X_CONSTRAINTS and X_VALIDATION_REGEX (X referring to the name of the class).

It is unnecessary to have X as part of the names of these constants. For example, Name.MESSAGE_NAME_CONSTRAINTS doesn't seem to provide more information than Name.MESSAGE_CONSTRAINTS.

As such, let's remove X as part of the names of these constants.

@apoorva17 I'll take a closer look later, but in the meantime can you wrap the commit message to a width of 72 characters per line?


Is it suppose to be root_source_code_paths or root_source_code_path ?

Environment

Elixir version (elixir -v): 1.11.2
Erlang/OTP version (erl): 23.1.3
Sentry version (mix deps): 8.0.0
Operating system: debian-buster
Is this an umbrella application?: no
Release type (Distillery, mix release, Mix, etc.): Docker

Description
Is it suppose to be root_source_code_paths or root_source_code_path ?
Expected Behavior
==> sentry
Compiling 15 files (.ex)
Generated sentry app

Actual Behavior
== Compilation error in file lib/sentry/event.ex ==
** (ArgumentError) :root_source_code_path must be configured
    lib/sentry/config.ex:86: Sentry.Config.root_source_code_path/0
    lib/sentry/sources.ex:67: Sentry.Sources.load_files/0
    lib/sentry/event.ex:64: (module)
    (stdlib 3.13.2) erl_eval.erl:680: :erl_eval.do_apply/6

Steps to Reproduce
Fails
config :sentry,
  dsn: System.get_env("SENTRY_DSN"),
  environment_name: System.get_env("RELEASE_LEVEL") || "development",
  included_environments: ~w(production staging),
  enable_source_code_context: true,
  tags: %{
    env: System.get_env("RELEASE_LEVEL") || "development"
  },
  root_source_code_paths: [File.cwd!()]

compiles
config :sentry,
  dsn: System.get_env("SENTRY_DSN"),
  environment_name: System.get_env("RELEASE_LEVEL") || "development",
  included_environments: ~w(production staging),
  enable_source_code_context: true,
  tags: %{
    env: System.get_env("RELEASE_LEVEL") || "development"
  },
  root_source_code_path: File.cwd!()

has the readme got it wrong ?

The README reflects the most recently released version. If you try updating from 8.0.0 to 8.0.4, does the error persist?

A different error but still root_source_code_path works while root_source_code_paths fails

root_source_code_paths

root_source_code_path

Thanks for the detail. What configuration do you have in each of those cases?
I can reproduce the first error if I pass a string as the config instead of a list.

This works on 8.0.4
==> sentry
Compiling 15 files (.ex)
Generated sentry app

config :sentry,
  dsn: System.get_env("SENTRY_DSN"),
  environment_name: System.get_env("RELEASE_LEVEL") || "development",
  included_environments: ~w(production staging),
  enable_source_code_context: true,
  tags: %{
    env: System.get_env("RELEASE_LEVEL") || "development"
  },
  root_source_code_paths: [File.cwd!()]

Thanks for the help

Good to hear, thank you!


API/COMPAT: add pydatetime-style positional args to Timestamp constructor

[X] closes #10758
[X] tests added / passed
[X] passes git diff upstream/master | flake8 --diff
[x] whatsnew entry

If more tests are desired, please let me know where to put them. Same for the whatsnew entry. This is my first pull request for Pandas.
cc @jreback

pls add a whatsnew entry.
any luck with accepting the kwargs as well? (or too complicated)

Should the whatsnew go in for 18.1 or something else?
kwargs got too complicated. I wanted to reach a working version of positional parameters first before building kwargs on top of it. I will try out an idea this weekend.

you can put in 0.18.1; if you finish up before we release we can just move

@thejohnfreeman can you rebase / update & move whatsnew to 0.18.2

Ok, I rebased. I have time this week to finish this patch. I wrote a longer comment asking a question, but I'll just go ahead and try the signature you gave above.
def __new__(cls,
        object ts_input, object offset=None, tz=None, unit=None,
        year=None, month=None, day=None,
        hour=None, minute=None, second=None, tzinfo=None):

[Current coverage][cc-pull] is 84.14%

Merging [#12482][cc-pull] into [master][cc-base-branch] will increase coverage by +<.01%

@@             master     #12482   diff @@
==========================================
  Files           137        137
  Lines         50287      50287
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          42311      42312     +1
+ Misses         7976       7975     -1
  Partials          0          0

File ...das/tseries/index.py (not in diff) was modified. more

Misses -1
Partials 0
Hits +1

Powered by Codecov. Last updated by [af7bdd3...1feb3e2][cc-compare]
[cc-base-branch]: https://codecov.io/gh/pydata/pandas/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/pydata/pandas/compare/af7bdd3883c8d61e9d9388d3aa699930eee7fff8...1feb3e2ec65bfd72c80080bd52bc9a1605cb58a2
[cc-pull]: https://codecov.io/gh/pydata/pandas/pull/12482?src=pr

@thejohnfreeman You will also need to update the Timestamp docstring

also I believe its trivial to close #11630 (or it might already be done). Add a test and should be straightforward.

Take a look at my attempt at supporting both positional and keyword arguments. I removed some tests for TypeError; it just means we are more permissive. I'll fix up the doc string and add the other requested tests tomorrow.

whoosh @thejohnfreeman nice constuctor now! yeah prob need some more tests.

Effectively, we are doing type dependent multiple dispatch here with the Timestamp constructor. To be honest, I'm not a big fan of adding multiple paths like this that do such different things with the arguments.

@shoyer that doesn't make any sense. Timestamp is a sub-class of datetime. It doesn't take the correct (positional, nor keyword args ATM). I don't see the problem here. Yes it also does a lot more, but that's exactly the point, it IS user friendly w/o be ambiguous.

I updated the docstring and added tests. I'm considering this a first draft submitted for approval. If it's approved, I'll squash the commits and we can wait for Travis.

did you add a test for #11630 as well (I think you covered it in code, just need the test)

For #11630, I'm considering the test in test_constructor_positional to be equivalent:
ts = Timestamp(2000, 1, 2)

I can add a test with the exact parameters from #11630 too. Regardless, I will add the issue in a comment.

@thejohnfreeman yes add that exact test (e.g.
self.assertEqual(repr(Timestamp(2015, 11, 12)),  repr(Timestamp('20151112')))

should be enough

@shoyer that doesn't make any sense. Timestamp is a sub-class of datetime. It doesn't take the correct (positional, nor keyword args ATM). I don't see the problem here. Yes it also does a lot more, but that's exactly the point, it IS user friendly w/o be ambiguous.

You cannot add alternate signatures without adding ambiguity. For example, suppose a naive user tries to pass three string arguments instead of integers into the new constructor. This is invalid for both datetime and the existing Timestamp signature, but because these arguments are supplied as strings, it would still trigger the existing codepath.
Let's compare what they would see:
>>> pd.Timestamp('2000', '01', '01')
UnknownTimeZoneError: '01'

>>> datetime.datetime('2000', '01', '01')
TypeError: an integer is required

The error from datetime is much more informative.
The standard library datetime.datetime class does not accept a string to convert to avoid exactly these sorts of issues. Instead, you are forced to use alternate constructors such as strptime.
It is unambiguously poor API design to make functions that do two very different things depending on the exact form of the input.
I'm all for making pd.Timestamp more consistent with datetime.datetime if you're willing to deal with the hassle of a long deprecation cycle, but the right approach is not to overload the constructor to do something totally different. The right approach would be to switch the constructor entirely.

Personally, I can sympathize with @shoyer. In all languages, I prefer that constructors just directly initialize fields and leave any magic to ordinary functions. Especially in Python, you only get one constructor but you can make unlimited functions for every style of construction you want, and it becomes easier to create custom test objects.
That said, I think it's more important to fit into a project's existing style and API, and I can see an argument for fitting this functionality into the Timestamp constructor. For now, I'm going to follow Jeff's instructions on this since that's what I've been doing all along.

What about deprecating passing a single object (string or datetime) to pd.Timestamp in favor of using pd.to_datetime? That way we could get back to only one constructor eventually.
It would not be the end of the world to add this alternate constructor but IMO it would not be a positive improvement to have both.
If to do do it, let's clearly document the two constructors at the top of the docstring for the class, e.g.,
Timestamp(ts_input, object_offset=None, tz=None, unit=None)
Timestamp(year, month, day[, hour[, minute[, second[, microsecond[, tzinfo]]]]])

Timestamp is...

I think sphinx can process that correctly but we should double check.

@shoyer why would you blow up a very useful interface?
 The whole notion of a user having to choose alternate constructors (and I know we had this discussion w.r.t. RangeIndex) is completely bonkers to me.
Sure if things are ambiguous, then you have to choose. In this case it is wholly unambiguous, replicates the existing (python datetime.datetime API), and provides very useful parsing abilities, not to mention its very light weight.

I agree -- my proposal is not entirely serious. I do think we need to make hard choices like this to achieve reliable APIs.

the entire point is to REDUCE mental effort here. The whole notion of a user having to choose alternate constructors (and I know we had this discussion w.r.t. RangeIndex) is completely bonkers to me.

Just to prove I'm not crazy, here are some high lights from the first page of a Google search for "Python multiple constructors":
http://stackoverflow.com/questions/2164258/multiple-constructors-in-python
http://stackoverflow.com/questions/682504/what-is-a-clean-pythonic-way-to-have-multiple-constructors-in-python
http://www.erol.si/2016/01/python-and-multiple-constructors/
https://pythonconquerstheuniverse.wordpress.com/2010/03/17/multiple-constructors-in-a-python-class/ (read the comments)
I could go on, but you get the point.
You'll notice that the universal advice seems to be to skip the magic and use classmethods for alternate constructors instead of overloading __init__.

If we are to add more code paths in the constructor, is it possible to make the entry points more obvious by calling specific from_* methods inside __new__ or __init__?  After reading the doc string I feel like it might become harder for a casual contributor like me to debug the code.  But I think this can be remedied by making the intention of each code path more visible in the code.

Hi @kawochen, I too want to make the code paths understandable. I had added some comments to each new path to document its intention. Did they help clarify at all?

I keep getting lint errors in the automated check. It doesn't say what the error is, and running trace8 locally doesn't give me any indication either.
The command "ci/script.sh" exited with 1.
1.00s$ ci/lint.sh
inside ci/lint.sh
discarding /Users/travis/miniconda/envs/pandas/bin from PATH
prepending /Users/travis/miniconda/envs/pandas/bin to PATH
NOT Linting

Any ideas what I need to do to get Travis to pass?

it's not lint errors but a failed test
https://travis-ci.org/pydata/pandas/jobs/129782361

Ah, it expects Timestamp(None) to return Not a Time (NaT).

lgtm. @thejohnfreeman nice explanations in the comments. I think it is clear.
@jorisvandenbossche @shoyer
comments?

@thejohnfreeman did you add the test for #11630 (e.g the repr expr from above)

thanks @thejohnfreeman great PR!

Thank you!


formatting error in date

In today's version of SARS-CoV-2-Sequenzdaten_Deutschland.csv.xz
in line 408310, date is incorrectly formatted as 2021-12sss-02.

Dear @benmaier
Thank you for your comment.
This issue should be fixed with today's data upload.

cool, thanks! do you mean in an update later today? because it's still in there :)

I mean tomorrow morning with the usual 6am update.

thanks!


menger_cubes example

I can't seem to run the menger_cubes example:
moltemplate.sh v2.0.2 2016-12-04

lttree_check.py v0.76 2014-12-19

    "Data Atoms" column format:
    atom-ID molecule-ID atom-type q x y z

lttree_check.py:    parsing the class definitions...
Error(ttree.StaticObj.Parse()):
       Syntax error at or before "menger_cubes.lt", line 48:
       "cells_xz= new".

I looked at the syntax in menger_cubes.lt but can't seem to spot the error. Could you assist please?

You found an error in one of my favorite examples. (Dammit.)  Wow, great!
It's actually a nasty error, not in the menger_cubes example, but in the lexer ("ttree_lexer.lt")
I must have changed that example after I originally wrote it, and not bothered to test it.
The problem is the lack of spaces on either side of the '=' character.  This should not be necessary.  At some point I removed the '=' and ' and '' characters from TtreeLex.word_terminators.  This was a bad idea, but the original intention was  to allow users to give their atoms type names like:
c=
O3'
c
...which show up often in popular force-fields.
Don't worry about this.  I will fix it right now and communicate the changes
Thanks!

The bug was corrected release 2.0.5.  Thanks again Shyam


perf(staking): remove duplicated totalSupply query logic

Move totalSupply check logic outside the for loop at updateReward.

Codecov Report
Patch and project coverage have no change.

Comparison is base (f5fed1f) 94.85% compared to head (684e8d4) 94.85%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #10   +/-   ##
=======================================
  Coverage   94.85%   94.85%
=======================================
  Files           6        6
  Lines         350      350
  Branches       58       58
=======================================
  Hits          332      332
  Misses         10       10
  Partials        8        8

Impacted Files
Coverage Δ

contracts/MangoStakedToken.sol
98.55% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Small fix related to internal interface

Related to this PR https://github.com/istio/istio/pull/11321
I forgot to change from "r" to "k" in the installation yaml.
@rshriram can you help me with this small fix?
I tested this end2end and it works.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: SchSeba
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ostromart
If they are not already assigned, you can assign the PR to them by writing /assign @ostromart in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @SchSeba. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

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.

/ok-to-test

@SchSeba: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
50c941021b6db775e82ebca118ec117b8516ce3a
link
/test e2e-simpleTests-cni

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

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

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
50c941021b6db775e82ebca118ec117b8516ce3a
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
50c941021b6db775e82ebca118ec117b8516ce3a
link
/test istio-integ-k8s-tests

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

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

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
50c941021b6db775e82ebca118ec117b8516ce3a
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
50c941021b6db775e82ebca118ec117b8516ce3a
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
50c941021b6db775e82ebca118ec117b8516ce3a
link
/test istio_auth_sds_e2e

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.


Add test case test_csi_umount_when_longhorn_block_device_is_disconnected_unexpectedly

Add test case test_csi_umount_when_longhorn_block_device_is_disconnected_unexpectedly
ref: 6373

Is it possible to have a test result of it?

Is it possible to have a test result of it?

Test result on pipeline

@mergify backport v1.5.x

@mergify backport v1.4.x


Reddit stops working after every reboot

I install Reddit Revanced Extended, because Revanced marked as not secure, and every time I reboot it stops working, if I try to open it, it crashes and the app name is broken as shown on the screenshot above

Closing this issue as invalid.
The app crashing after reboot and the broken app name are issues with the modified Reddit app provided by the provider, not with UpdateMe itself. UpdateMe is only responsible for downloading and installing the APK file - any functionality issues or bugs within the modified apps themselves are related to how the provider modified the app.
If you're experiencing issues with this specific mod, you might want to try a different mod version or provider.


design simple vector graphics framework

Add possibility to draw antialiased curves and filled paths

no need for filled paths so far

done in separate project 'sintezator'


update of c/c++ extension not running due to missing binary

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

/extC++

It looks like this is caused by the C++ extension. Please file the issue to the C++ extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


refactor(appinfo)!: improve application models

Summary
Refactors application models, deduplicating and generally merging related code.
The diff is fairly unreadable as-is, skipping the first commit (that just moves PartialAppInfo above AppInfo) improves readability quite a bit.
tl;dr on the important changes, see changelog for everything:

new hierarchy: PartialAppInfo < AppInfo < BotAppInfo (where BotAppInfo is equivalent to the old AppInfo)

note: this shouldn't have any practical effect on user code unless these types are created there

AppInfo.summary is no more (deprecated in previous version)
Invite.target_application (which is now AppInfo) contains more fields
now using the correct cover_image url format

Checklist

[x] If code changes were made, then they have been tested

[x] I have updated the documentation to reflect the changes
[x] I have formatted the code properly by running task lint
[x] I have type-checked the code by running task pyright

[x] This PR fixes an issue
[x] This PR adds something new (e.g. new method or parameters)
[x] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

@shiftinv would you please resolve conflicts?

would you please resolve conflicts?

@onerandomusername done.

@shiftinv would you please resolve conflicts again?


typescript typings for fela-native

Type: Feature

Packages
Version

fela-native
5.0.22

Description
The fela-native renderer is missing typings.
Proposal
It's very similar to react-fela's renderer, so maybe we can copy-paste for the most part.

Feel free to send a PR for those types :)
I'm not using TypeScript so I don't have a high priority for those :P


How to reproduce this visualization from the VQVAE 2 paper

The original paper had this cool graphic in it, which showed what I believe is a decoded representation of different parts of the network. But I don't understand how in practice you could obtain a decoded image using only the top level FFHQ encoder representation. In the case of the three level FFHQ model, the final decoder layer is applied to a concatenation of the upscaled middle layer and the double upscaled top layer, and expects 192 layers.
Is there a way, only using information from the top level encoded quantized representation, to get an image out of the network?

This is something I also never quite understood about the original paper, nor have I explored myself. So I can't really answer this question. It could be something as naive as passing a zero tensor as a substitute for the lower level codes in the final decoder, but only the original authors know.
Thanks for bringing this to my attention, I am currently working on a refactor of this repo (see #5) so I might investigate this once that is done. There are actually quite a lot of unclear things in the paper that we may never know for sure how it was done for the paper.


[TF] More echo cleanup

Removing WorkloadPort and just adding to the Ports list.
Updated common ports to be a single list that includes both service and workload-only ports.
Renaming CallOptions.Target->To. Just a bit more concise.
Added Ports utility and moving aggregate port operations there.
Added Configurable and WorkloadContainer interfaces in preparation for allowing different target types (e.g. Instances).
Added Cluster to Workload in preparation to switching to use workloads for accessing all clusters for a set of Instances.

Please provide a description of this PR:

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test unit-tests_istio

lint_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test unit-tests_istio

lint_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test lint_istio

integ-ipv6_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-ipv6_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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test unit-tests_istio

lint_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test lint_istio

integ-ipv6_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-ipv6_istio

integ-distroless_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-distroless_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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test unit-tests_istio

lint_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test lint_istio

integ-ipv6_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-ipv6_istio

integ-distroless_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-distroless_istio

gencheck_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/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.

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test unit-tests_istio

lint_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test lint_istio

integ-ipv6_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-ipv6_istio

integ-distroless_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-distroless_istio

gencheck_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test lint_istio

integ-ipv6_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-ipv6_istio

integ-distroless_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-distroless_istio

gencheck_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test gencheck_istio

unit-tests_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/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.

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

Test name
Commit
Details
Required
Rerun command

integ-ipv6_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-ipv6_istio

integ-distroless_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-distroless_istio

gencheck_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test gencheck_istio

unit-tests_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test unit-tests_istio

lint_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/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.

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

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-distroless_istio

gencheck_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test gencheck_istio

unit-tests_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test unit-tests_istio

lint_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test lint_istio

integ-ipv6_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-ipv6_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.

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

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-distroless_istio

gencheck_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test gencheck_istio

unit-tests_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test unit-tests_istio

lint_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test lint_istio

integ-ipv6_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote_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.

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

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-distroless_istio

gencheck_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test gencheck_istio

unit-tests_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test unit-tests_istio

lint_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test lint_istio

integ-ipv6_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_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.

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

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-distroless_istio

gencheck_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test gencheck_istio

unit-tests_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test unit-tests_istio

lint_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test lint_istio

integ-ipv6_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot_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.

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

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
c8af6dbd73227a4d93db09ffed54ca33113772e1
link
true
/test integ-distroless_istio

gencheck_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test gencheck_istio

unit-tests_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test unit-tests_istio

lint_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test lint_istio

integ-ipv6_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot_istio

integ-cni_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-cni_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.

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

Test name
Commit
Details
Required
Rerun command

gencheck_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test gencheck_istio

unit-tests_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test unit-tests_istio

lint_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test lint_istio

integ-ipv6_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot_istio

integ-cni_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-cni_istio

integ-distroless_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-distroless_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.

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

Test name
Commit
Details
Required
Rerun command

gencheck_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test gencheck_istio

unit-tests_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test unit-tests_istio

lint_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test lint_istio

integ-ipv6_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot_istio

integ-cni_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-cni_istio

integ-distroless_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-distroless_istio

integ-pilot-multicluster_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-multicluster_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.

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

Test name
Commit
Details
Required
Rerun command

gencheck_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test gencheck_istio

integ-ipv6_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot_istio

integ-cni_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-cni_istio

integ-distroless_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-distroless_istio

integ-pilot-multicluster_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-multicluster_istio

lint_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/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.

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

Test name
Commit
Details
Required
Rerun command

integ-ipv6_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot_istio

integ-cni_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-cni_istio

integ-distroless_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-distroless_istio

integ-pilot-multicluster_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-multicluster_istio

lint_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test lint_istio

gencheck_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/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.

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

Test name
Commit
Details
Required
Rerun command

integ-ipv6_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot_istio

integ-distroless_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-distroless_istio

integ-pilot-multicluster_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-multicluster_istio

lint_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test lint_istio

gencheck_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test gencheck_istio

integ-cni_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-cni_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.

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

Test name
Commit
Details
Required
Rerun command

integ-ipv6_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-ipv6_istio

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot_istio

integ-distroless_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-distroless_istio

integ-pilot-multicluster_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-multicluster_istio

lint_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test lint_istio

gencheck_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test gencheck_istio

integ-cni_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-cni_istio

integ-pilot-istiodremote_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote_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.

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot_istio

integ-distroless_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-distroless_istio

integ-pilot-multicluster_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-multicluster_istio

lint_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test lint_istio

gencheck_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test gencheck_istio

integ-cni_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-cni_istio

integ-pilot-istiodremote_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote_istio

integ-ipv6_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-ipv6_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.

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot_istio

integ-pilot-multicluster_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-multicluster_istio

lint_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test lint_istio

gencheck_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test gencheck_istio

integ-cni_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-cni_istio

integ-pilot-istiodremote_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote_istio

integ-ipv6_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-ipv6_istio

integ-distroless_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-distroless_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.

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_istio

integ-pilot-multicluster_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-multicluster_istio

lint_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test lint_istio

gencheck_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test gencheck_istio

integ-cni_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-cni_istio

integ-pilot-istiodremote_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote_istio

integ-ipv6_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-ipv6_istio

integ-distroless_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-distroless_istio

integ-pilot_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot_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.

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
3fe20d3c5ad0fb1807b9883b45a6828e8086dcc0
link
true
/test integ-pilot-istiodremote-mc_istio

lint_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test lint_istio

gencheck_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test gencheck_istio

integ-cni_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-cni_istio

integ-pilot-istiodremote_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote_istio

integ-ipv6_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-ipv6_istio

integ-distroless_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-distroless_istio

integ-pilot_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot_istio

integ-pilot-multicluster_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-multicluster_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.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test lint_istio

gencheck_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test gencheck_istio

integ-cni_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-cni_istio

integ-pilot-istiodremote_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote_istio

integ-ipv6_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-ipv6_istio

integ-distroless_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-distroless_istio

integ-pilot_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot_istio

integ-pilot-multicluster_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-multicluster_istio

integ-pilot-istiodremote-mc_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote-mc_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.

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

Test name
Commit
Details
Required
Rerun command

gencheck_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test gencheck_istio

integ-cni_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-cni_istio

integ-pilot-istiodremote_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote_istio

integ-ipv6_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-ipv6_istio

integ-distroless_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-distroless_istio

integ-pilot_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot_istio

integ-pilot-multicluster_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-multicluster_istio

integ-pilot-istiodremote-mc_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote-mc_istio

lint_istio
f0087c1628ed6b691ebb07373a36ce5b5c1c2a9a
link
true
/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.

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

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-cni_istio

integ-pilot-istiodremote_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-multicluster_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-multicluster_istio

integ-pilot-istiodremote-mc_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote-mc_istio

lint_istio
f0087c1628ed6b691ebb07373a36ce5b5c1c2a9a
link
true
/test lint_istio

integ-telemetry-mc_istio
eaf8fb36ee3149079150ad5cc144c357d00538e2
link
true
/test integ-telemetry-mc_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.

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

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-cni_istio

integ-pilot-istiodremote_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote_istio

integ-pilot-multicluster_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-multicluster_istio

integ-pilot-istiodremote-mc_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-pilot-istiodremote-mc_istio

integ-telemetry-mc_istio
eaf8fb36ee3149079150ad5cc144c357d00538e2
link
true
/test integ-telemetry-mc_istio

lint_istio
eaf8fb36ee3149079150ad5cc144c357d00538e2
link
true
/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.

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

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
7895d1a11a94813812a59d58a644f7f8fc5c31a7
link
true
/test integ-cni_istio

integ-telemetry-mc_istio
eaf8fb36ee3149079150ad5cc144c357d00538e2
link
true
/test integ-telemetry-mc_istio

integ-pilot_istio
6ec6df12820a19339dc843f5a5d8412504573954
link
true
/test integ-pilot_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.

/retest

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
c2da8d246a9b58910fa096a3af9fcf5696b05b22
link
unknown
/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.

/retest

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
c2da8d246a9b58910fa096a3af9fcf5696b05b22
link
unknown
/test unit-tests_istio

integ-security-multicluster_istio
c2da8d246a9b58910fa096a3af9fcf5696b05b22
link
unknown
/test integ-security-multicluster_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-security-multicluster_istio

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

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
c2da8d246a9b58910fa096a3af9fcf5696b05b22
link
unknown
/test integ-pilot-multicluster_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.


Fixes third argument in call to output->write

The third parameter of Symfony\Component\Console\Output\OutputInterface::write() is $type; not $verbosity. This is intended for distinguishing between normal, raw, and plain output.
The previous code happens to work in most cases because these constants are similar.
interface OutputInterface
{
    const VERBOSITY_QUIET = 0;
    const VERBOSITY_NORMAL = 1;
    const VERBOSITY_VERBOSE = 2;
    const VERBOSITY_VERY_VERBOSE = 3;
    const VERBOSITY_DEBUG = 4;

    const OUTPUT_NORMAL = 0;
    const OUTPUT_RAW = 1;
    const OUTPUT_PLAIN = 2;

When VERBOSITY_DEBUG is used (-vv), an InvalidArgumentException is thrown with the message Unknown output type given (3).
When VERBOSITY_DEBUG is used (-vvv), an InvalidArgumentException is thrown with the message Unknown output type given (4).

Hey! You need to open this on the main symfony/symfony repo - this is a read only split.
Cheers!

Thanks. I PR'd this into the main repo back in April/May


TPanic crash

Above is the crashed thread stack and info which crash at FEngine::Loop. Is there clue the crash happen?
the crash happened:

is the crash happened here?

I checked the possible panic at FEngine::Loop，is the crash happened here？

Our panic macros emit messages, is it possible for you to obtain more complete log output?

yes, I've tried to print the emit messages to our app log, but I've found that sometimes it didn't invoke the panic function.

If all panic will invoke the e.log()?

@starccode Are you able to show us the full log output of your program when it crashes?

@starccode Are you able to show us the full log output of your program when it crashes?

no problem, I'm trying to collect the crash log, I will show the log as soon as I get them~

Recently, I've collected some TPanic crash macro output log, here it is:

Panic
in MetalTexture:474
reason: Could not create Metal texture. Out of memory?
2.Panic
in acquireDrawable:145
reason: Could not obtain drawable.

for the first crash log, I've checked the memory info log when crash happend, and it seems not "Out of memory".

Internally, Filament calls Metal API methods on a separate thread which is not set up to report asynchronous failures. If newTextureWithDescriptor is returning nil, then your app is most likely running out of memory. You could experiment with reducing the amount of texture allocations and/or their size/pixel format to reduce memory pressure. You could also see if iOS is sending your app low memory warnings and respond accordingly.
Closing for now, but feel free to reopen if you suspect there's a bug in Filament.


Need Refresh page after posting a comment to display

We should see it display directly.
Now i see comment count updated but only after Refresh page F5 we can see it

This is happening for every new action created on the blockchain. F5 is required to actualize blockchain statut, every posts, likes,comments,posts information,etc..need a page refresh to update. It would be great if all the info could update just by changing pages.

It's not the case anymore, now its automatically updated, i'm closing this ticket.


Add Duy Tan University

Add Duy Tan University

@tungooxx I am sorry, the domain dtu.edu.vn is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


TypeInitializationException is raised when I run the code

I created one O365dev account using my msdn subscription. Now i followed all the steps connecting the app to the O365 service and giving all the privileges. When i run the code I get TypeInitializationException . Can somebody help me with this issue. Am i missing something here?

I haven't been able to reproduce the problem that you're seeing. Do you have values for ClientID and AuthorizationUri in your App.xaml file?
    <x:String x:Key="ida:ClientID"><Client ID></x:String>
<x:String x:Key="ida:AuthorizationUri">https://login.windows.net</x:String>

Also, does your packages.config file match up with this?

Did all of your references load when you built the project? You might run into trouble if you don't build the project before adding the connected services.
And could you pass along the full details of the inner exception and the call stack?
Thanks.

Sorry. The packages.config xml didn't display. Check to make sure that the package versions all match up:
package id="Microsoft.Azure.ActiveDirectory.GraphClient" version="2.0.8" targetFramework="win81" /
package id="Microsoft.Data.Edm" version="5.6.4" targetFramework="win81" /
package id="Microsoft.Data.OData" version="5.6.4" targetFramework="win81" /
package id="Microsoft.Data.Services.Client" version="5.6.4" targetFramework="win81" /
package id="Microsoft.IdentityModel.Clients.ActiveDirectory" version="2.10.10910.1511" targetFramework="win81" /
package id="Microsoft.OData.Client" version="6.8.1" targetFramework="win81" /
package id="Microsoft.OData.Core" version="6.8.1" targetFramework="win81" /
package id="Microsoft.OData.Edm" version="6.8.1" targetFramework="win81" /
package id="Microsoft.Office365.Discovery" version="1.0.22" targetFramework="win81" /
package id="Microsoft.Office365.OAuth.Windows" version="1.0.21" targetFramework="win81" /
package id="Microsoft.Office365.OutlookServices" version="1.0.22" targetFramework="win81" /
package id="Microsoft.Office365.SharePoint" version="1.0.22" targetFramework="win81" /
package id="Microsoft.Spatial" version="6.8.1" targetFramework="win81" /
package id="Newtonsoft.Json" version="6.0.5" targetFramework="win81" /
package id="System.Spatial" version="5.6.4" targetFramework="win81" /

this is the package config details I've and few of them are higher versions than what you mentioned and please correct me if my clientId & authorizationUri are not correct.
Stacktrace:
at Office365StarterProject.AuthenticationHelper.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()    at Office365StarterProject.Helpers.UserOperations.<GetCurrentUserAsync>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at Office365StarterProject.ViewModels.UserViewModel.d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Office365StarterProject.ViewModels.UserViewModel.<<get_ToggleSignInCommand>b__0>d__2.MoveNext()
I created one O365 dev account and started using this application. Do i need to follow some other steps to configure my O365 account?

Your  Microsoft.IdentityModel.Clients.ActiveDirectory assembly and Microsoft.OData assemblies are out of sync with the solution that's on the repo. Could you start over with a new clone or a fresh download? Make sure that your packages.config file is identical with the one in the repo. Build the solution before you do anything else, and then add the connected services. I'll work on updating the sample to use the newer assemblies, but your solution should work if it uses the same assembly versions as the ones specified in the packages.config file in the repo.

I've looked into this some more. It looks like you manually installed the Microsoft.OData.ProxyExtensions and Microsoft.IdentityModel.Clients.ActiveDirectory NuGet packages, giving you the latest stable versions of those packages, but we haven't tested this sample with those packages yet. This version of the sample also doesn't require the Microsoft.OData.ProxyExtensions package at all.
Update your packages.config file so that it matches the one that is stored on this repo (https://github.com/OfficeDev/O365-Windows-Start/blob/master/Office365StarterProject/packages.config).
Then build the solution to restore the original package versions. It might be easiest to start with a clean version of the solution.

Just checking back on this issue. Have you been able to update your packages.config file or start with a clean solution?

We had to resort to other solution for the problem we are solving. I believe the change in versions of dlls referenced might be the reason. Anyways I'll close the issue
    Sent by Outlook for Android

On Fri, May 8, 2015 at 12:38 PM -0700, "jamescro"<EMAIL_ADDRESS>wrote:
Just checking back on this issue. Have you been able to update your packages.config file or start with a clean solution?
—
Reply to this email directly or view it on GitHub.

Thanks for the update. If you have the time, we would appreciate learning more about your situation, especially with respect to how your solution ended up with the different versions of the required assemblies. Did you update the assemblies manually, or did something go wrong with the package restoration?

I uninstalled and reinstalled the packages from Nuget and all the dependant packages manually. I did some combinations with those packages and couldn't figure out the root cause for buid failure. The goal of using this code is to know if the latest O365 api exposes calendar details and I can programatically schedule a meeting & block a meeting room. Later we decided on using Exchange Web service for some other reasons.
    Sent by Outlook for Android

On Mon, May 11, 2015 at 9:54 AM -0700, "jamescro"<EMAIL_ADDRESS>wrote:
Thanks for the update. If you have the time, we would appreciate learning more about your situation, especially with respect to how your solution ended up with the different versions of the required assemblies. Did you update the assemblies manually, or did something go wrong with the package restoration?
—
Reply to this email directly or view it on GitHub.

You might look at issue #15 to see if you had the same problem.


Springster Polls & Survey Patterns - Wagtail Admin

Please review
These are the error pages and previous fix for comments on Wagtail admin


Update pod ready++ link

@ialidzhikov Thank you for your contribution. Please sign the CLA so we can accept your PR for review.

/lgtm
Defer to @bradtopol for approval :)

Change looks good. Verified the new link works in preview. Great job!
/lgtm
/approve


Fix issue with Index arrow for QN case of correlation_matrix

Great, thanks!

Codecov Report

Merging #702 (0537e8e) into main (af73681) will decrease coverage by 1.73%.
The diff coverage is 100.00%.

:exclamation: Current head 0537e8e differs from pull request most recent head 3d79e77. Consider uploading reports for the commit 3d79e77 to get more accurate results

@@            Coverage Diff             @@
##             main     #702      +/-   ##
==========================================
- Coverage   79.92%   78.19%   -1.74%
==========================================
  Files          81       81
  Lines        9113     7699    -1414
==========================================
- Hits         7284     6020    -1264
+ Misses       1829     1679     -150

Impacted Files
Coverage Δ

src/mps/mps.jl
96.40% <100.00%> (+2.39%)
:arrow_up:

src/NDTensors/octavian.jl
0.00% <0.00%> (-100.00%)
:arrow_down:

src/NDTensors/similar.jl
33.33% <0.00%> (-30.31%)
:arrow_down:

src/NDTensors/dims.jl
42.85% <0.00%> (-28.58%)
:arrow_down:

src/broadcast.jl
60.16% <0.00%> (-25.56%)
:arrow_down:

src/NDTensors/empty.jl
56.04% <0.00%> (-21.74%)
:arrow_down:

src/physics/site_types/tj.jl
53.22% <0.00%> (-13.45%)
:arrow_down:

src/qn/qnindexset.jl
86.66% <0.00%> (-13.34%)
:arrow_down:

src/NDTensors/tensorstorage.jl
66.66% <0.00%> (-10.08%)
:arrow_down:

src/lastval.jl
57.14% <0.00%> (-7.15%)
:arrow_down:

... and 68 more

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 af73681...3d79e77. Read the comment docs.


Rewrite /profiles/name/{{name}}/copy/{{fromName}} to Go

I'm submitting an ...
improvement request (usability, performance, tech debt, etc.)
Traffic Control components affected ...

Documentation (possibly)
Traffic Ops

Current behavior:
/profiles/name/{{name}}/copy/{{fromName}} is handled by Perl
Expected / new behavior:
/profiles/name/{{name}}/copy/{{fromName}} should be handled by Go.
Minimum API Version
1.1
Request Methods

[ ] POST

Minimal reproduction of the problem with instructions:
N/A

i think this should be deprecated (not rewritten to Go and a deprecation notice added to the response) because....weird...
also, if your intent is to clone a profile, you can do that with import/export i believe.

I believe TP uses this endpoint for cloning profiles. I think ops probably uses this one quite a bit, so I'm unsure about deprecating it. It's one of those things that could be done using the other APIs, but this acts like a kind of "bulk create" API instead of just creating a new profile with one call, creating all the parameters with individual calls, and associating the parameters to the profile with individual calls.


Attempting to use unirest in osgi causes error

I'm including unirest in a Liferay osgi activator, and white the dependencies seem to be fine, once the module is deployed, I get:
Unresolved requirement: Import-Package: org.apache.avalon.framework.logger
I've tried this with the stock unirest jar and building a unirest-java-1.4.10-SNAPSHOT-jar-with-dependencies.jar
Any insight?

Was able to fix this issue by adding
Import-Package: !org.apache.avalon.framework.,
!org.apache.log.,
*
As it appears these were optional dependencies, that were not marked as such in the library they were defined in.


Issue in prob.solve() --cell 30

I am trying to reimplement code in your notebooks. I get the error "PulpSolverError: Pulp: Error while executing /usr/local/lib/python3.6/dist-packages/pulp/solverdir/cbc/linux/64/cbc"
I tried checking the installations which seems to be fine. Can you suggest what might be the issue?

I have probably the same error as nainadhingra2012 when trying to run the code. It gives me this:

PulpSolverError                           Traceback (most recent call last)
 in ()
1 # The problem is solved using PuLP's choice of Solver
----> 2 prob.solve()
~/anaconda3/lib/python3.6/site-packages/pulp/pulp.py in solve(self, solver, **kwargs)
1711         """
1712
-> 1713         if not(solver): solver = self.solver
1714         if not(solver): solver = LpSolverDefault
1715         wasNone, dummyVar = self.fixObjective()
~/anaconda3/lib/python3.6/site-packages/pulp/solvers.py in actualSolve(self, lp, **kwargs)
1410     def available(self):
1411         """True if the solver is available"""
-> 1412         return self.executable(self.path)
1413
1414     def solve_CBC(self, lp, use_mps=True):
~/anaconda3/lib/python3.6/site-packages/pulp/solvers.py in solve_CBC(self, lp, use_mps)
1484             self.readsol_MPS(tmpSol, lp, lp.variables(), variablesNames, constraintsNames)
1485         lp.assignVarsVals(values)
-> 1486         lp.assignVarsDj(reducedCosts)
1487         lp.assignConsPi(shadowPrices)
1488         lp.assignConsSlack(slacks, activity=True)
PulpSolverError: Pulp: Error while executing /home/gorgi/anaconda3/lib/python3.6/site-packages/pulp/solverdir/cbc/linux/64/cbc


Jobs are scheduled in wrong order if one job failed once

Given the following job graph where job Parent is a scheduled job. Child1 takes longer to execute than Child2. After both jobs have finished, End is triggered to run.
         +--------+
         |        |
    +----+ Parent +----+
    |    |        |    |
    |    +--------+    |
    |                  |
    |                  |
    |                  |
+---+----+        +----+---+
|        |        |        |
| Child1 |        | Child2 |
|        |        |        |
+---+----+        +----+---+
    |                  |
    |                  |
    |                  |
    |    +--------+    |
    |    |        |    |
    +----+  End   +----+
         |        |
         +--------+

When Parent is executed, the order of execution looks like this:
1: Parent (success)
2: Child1 (success) - Child2 (success)
3: End (success)

On the next execution of Parent, imagine that Child2 fails and the order of execution now looks like this:
1: Parent (success)
2: Child1 (success) - Child2 (fails)
3: End (not scheduled)

Now Child2 recovers but End is being executed before Child1 has finished (remember that Child1 takes longer than Child2):
1: Parent (success)
2: Child2 (success)
3: End (success)
4: Child1 (success)

Expected: End should only run after Child1 has finished.
This last order of execution persists until either Child1 has failed once too or Chronos is being restarted.

@wndhydrnt thanks for reporting this.
cc @gkleiman

@pierlo-upitup @gkleiman I've been trying to fix this myself but without success. All things I tried introduced new bugs like jobs being scheduled too often or not at all in certain scenarios.
Most of my solutions did not work because Chronos does not constrain the parents of a job, as it is possible to depend on a parent job and on the parent job of that parent job at the same time.
Any ideas?

We could add the idea that a dependent job will only run once all of its parents jobs have at least one success and none of the parent jobs are running. If this is acceptable, this can be done by updating the edgeInvocationCount map in JobGraph.scala at the start of every task to update the number of successful invocations to be 0 for that job. This way Child2 will not kick off End on completion if Child1 had started / is still running.
I've run into this bug as well as it can be caused by updating a child job during a dependency chain as well when a parent has already finished but another parent job is still running during the update of the child job.
A potential problem is that if a child has parent jobs where at least one is always running for a child then the child would never be triggered. I find this to be unlikely however.

@wndhydrnt did you ever end up (eventually) getting a fix? (like with https://github.com/Jimdo/chronos/commit/6015035ce085aec7323722da3b22327f80e27eb4)
If so, how about a PR?

@solarkennedy No, I never was able to fix it without introducing new bugs. Sadly, to me, it looks like the whole logic that handles dependencies between jobs needs to be rewritten in order to fix it. Instead of doing that, I would suggest you use Airflow.


METRON-1341 Implemented SELECT transformer to project fields from parser

Contributor Comments
This is a simple PR to add FieldTransformation capabilities to the parsers allowing basic projection. There are definitely better ways to implement this as reflected in the comments, but those would need a wide ranging refactor of FieldTransformations, so I've decided to shelve that for now.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[x] Have you included steps or a guide to how the change may be verified and tested manually?

[x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && build_utils/verify_licenses.sh

[x] Have you written or updated unit tests and or integration tests to verify your changes?

[x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

Thanks Simon. Before a code review, a couple of questions:
I see a check next to steps to verify manually, but I don't see the steps.
This is also missing documentation.

Somehow I knew you were going to say something about docs.... will add.

It suddenly occurs to me that we should probably whitelist the original_string and timestamp fields, so that these are always kept by this transformation. Does that make sense?

That is an excellent catch @simonellistonball, a test to go with it too ;)

Right, that should cover it.

I trying to run this up in full dev.  I have two issues:

expressJS is failing download, obviously outside this PR
The usability of this transform.  If a user just wants a couple of fields, then no problem, but If they want anything more than that, then selecting all the fields that they want seems like a bit of a chore.  So if they want to select most of the fields, they have to list them all out.   It seems tough.  I wonder if we don't need regex support or something.

Thoughts?

If they want to select most, and remove the ones they don't want, then I would recommend using the remove transformation, or a set null in stellar. Perhaps regex support might be a nice follow on, but it breaks the mental model of people who are used to any other language that handles projection, such as SQL. The goal for this was to allow user to explicitly select only a defined set of fields. To be honest, people have lived with the idea of explicitly choosing fields for decades in SQL and quite liked it, so I suspect adding something that is pattern based might make it less usable than more.

Sure, that makes sense.  I am just trying to wrap my head around why I would use this based on the data I would send through.  I don't have to understand it for it to be useful ;)
Do you have a use case or scenario that would help me?

A typical case might be something like the CEF parser. You could potentially kick out a lot of fields you really don't care about, which at scale can produce huge amounts of ES and HDFS storage (in addition to the original_string representation. The goal for this is to focus on just outputting fields which match active use cases in the rest of the flow to control data storage costs and data clarity.
This also allows you to map an explicit data model and provide some governability to the data model.

Actually, to follow up on that... I have a proxy feed, and some proxy use cases (enrichment, profile, etc). I want to keep my data clean and be explicit about which fields I pass on, so I have a 'library' field set that means "proxy like stuff", these are the fields I push into the output here.

I ran the following test:
Modified the default snort parser configuration such that it was :
{
  "parserClassName":"org.apache.metron.parsers.snort.BasicSnortParser",
  "sensorTopic":"snort",
  "parserConfig": {},
  "fieldTransformations" : [
    {
      "output" : ["msg" ],
      "transformation" : "SELECT"
    }
  ]
}

And the default snort enrichment configuration such that it was :

{
  "enrichment" : {
  },
  "threatIntel" : {
    }
  }
}

I got the following:
<IP_ADDRESS>,49189,<IP_ADDRESS>,80,00:00:00:00:00:00,00:00:00:00:00:00,0x3C,***A****,0x9DFB1927,0xF1BD72CC,,0xFAF0,128,0,2360,40,40960,,,,","enrichmentsplitterbolt.splitter.end.ts":"1512763453749","enrichmentsplitterbolt.splitter.begin.ts":"1512763453749","guid":"08a84757-bf05-431b-9d81-5fa95fb99938","timestamp":1512763452000}
	at org.apache.metron.enrichment.bolt.EnrichmentJoinBolt.getStreamIds(EnrichmentJoinBolt.java:53) ~[stormjar.jar:?]
	at org.apache.metron.enrichment.bolt.EnrichmentJoinBolt.getStreamIds(EnrichmentJoinBolt.java:33) ~[stormjar.jar:?]
	at org.apache.metron.enrichment.bolt.JoinBolt.execute(JoinBolt.java:138) [stormjar.jar:?]
	at org.apache.storm.daemon.executor$fn__6573$tuple_action_fn__6575.invoke(executor.clj:734) [storm-core-<IP_ADDRESS>.5.3.0-37.jar:<IP_ADDRESS>.5.3.0-37]
	at org.apache.storm.daemon.executor$mk_task_receiver$fn__6494.invoke(executor.clj:466) [storm-core-<IP_ADDRESS>.5.3.0-37.jar:<IP_ADDRESS>.5.3.0-37]
	at org.apache.storm.disruptor$clojure_handler$reify__6007.onEvent(disruptor.clj:40) [storm-core-<IP_ADDRESS>.5.3.0-37.jar:<IP_ADDRESS>.5.3.0-37]
	at org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:451) [storm-core-<IP_ADDRESS>.5.3.0-37.jar:<IP_ADDRESS>.5.3.0-37]
	at org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:430) [storm-core-<IP_ADDRESS>.5.3.0-37.jar:<IP_ADDRESS>.5.3.0-37]
	at org.apache.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:73) [storm-core-<IP_ADDRESS>.5.3.0-37.jar:<IP_ADDRESS>.5.3.0-37]
	at org.apache.storm.daemon.executor$fn__6573$fn__6586$fn__6639.invoke(executor.clj:853) [storm-core-<IP_ADDRESS>.5.3.0-37.jar:<IP_ADDRESS>.5.3.0-37]
	at org.apache.storm.util$async_loop$fn__554.invoke(util.clj:484) [storm-core-<IP_ADDRESS>.5.3.0-37.jar:<IP_ADDRESS>.5.3.0-37]
	at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_77]
2017-12-08 20:04:17.171 o.a.m.e.b.EnrichmentSplitterBolt [ERROR] Trying to retrieve a field map with sensor type of null
2017-12-08 20:04:17.171 o.a.m.e.b.EnrichmentSplitterBolt [ERROR] Trying to retrieve a field map with sensor type of null
2017-12-08 20:04:17.171 o.a.m.e.b.EnrichmentSplitterBolt [ERROR] Trying to retrieve a field map with sensor type of null
2017-12-08 20:04:17.171 o.a.m.e.b.EnrichmentSplitterBolt [ERROR] Trying to retrieve a field map with sensor type of null
2017-12-08 20:04:17.171 o.a.m.e.b.EnrichmentSplitterBolt [ERROR] Trying to retrieve a field map with sensor type of null
2017-12-08 20:04:17.171 o.a.m.e.b.EnrichmentSplitterBolt [ERROR] Trying to retrieve a field map with sensor type of null
2017-12-08 20:04:17.171 o.a.m.e.b.EnrichmentSplitterBolt [ERROR] Trying to retrieve a field map with sensor type of null
2017-12-08 20:04:17.171 o.a.m.e.b.EnrichmentSplitterBolt [ERROR] Trying to retrieve a field map with sensor type of null
2017-12-08 20:04:17.171 o.a.m.e.b.EnrichmentSplitterBolt [ERROR] Trying to retrieve a field map with sensor type of null

So it looks like there are more fields to protect.

Good catch, my test included the source.type in the select list, and generalised badly in the instructions. We should include the source.type in the protected system fields, let me update the test and implementation.

OK,
Re-ran my scenario after the latest changes, and verified in kibana that only the msg field was indexed ( except for metron system or added fields ).
+1

Yeah, this is good.  +1 by inspection.

Thank you for the contribution @simonellistonball, please be sure to assign and close METRON-1341 in jira.  Cheers! #ynwa


[Asana] Need to update docs for Multi-Org Dpeloyment

Hello!
I'm an engineer at Asana and we would like to update the documentation at https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/asana-provisioning-tutorial (presumably here at https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory/saas-apps/asana-provisioning-tutorial.md) and https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/asana-tutorial (at https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory/saas-apps/asana-tutorial.md) in order to reflect our new product offerings. How should we go about doing this, do we submit a PR to this repo?
Thanks!
Victor<EMAIL_ADDRESS>
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 7a630935-6d99-85d7-04ec-232d58246a8a
Version Independent ID: 8e3e2d98-a1e2-7080-fc04-0eea42e9a7b8
Content: Tutorial: Configure Asana for automatic user provisioning with Microsoft Entra ID - Microsoft Entra
Content Source: articles/active-directory/saas-apps/asana-provisioning-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @twimmers
Microsoft Alias: thwimmer

@victor-yf-stone
Thanks for your feedback! We will investigate and update as appropriate.

@victor-yf-stone
Yes, you can submit a pull request to update the documentation at the GitHub repository for Microsoft Docs. Here are the general steps to follow:

Fork the repository to your own GitHub account.
Clone the forked repository to your local machine.
Make the necessary changes to the documentation files.
Commit the changes to your local repository.
Push the changes to your forked repository on GitHub.
Create a pull request from your forked repository to the main repository.

When creating the pull request, be sure to provide a clear description of the changes you made and why they are necessary. It's also a good idea to reference any relevant issues or documentation that you used as a reference. Once the pull request is submitted, it will be reviewed by the Microsoft Docs team and merged if it meets the necessary criteria. Let me know if you have any other questions!


the hi of cursorlinenum looks lost when diff mode in some case?

Describe the bug
the hi of cursorlinenum looks lost when diff mode in some case?  (pls check screen cut at following).
To Reproduce
1, vim diff mode
2, cursorlineoption=number
Expected behavior
hi as usual.
Screenshots

Environment (please complete the following information):
v8.2.472
Additional context
n/a

not sure if you can see the attached screen-cut, the short of descrition was the hi of cursorlinenr right after diffdelete was not highlighting... before and after that line is normal (hightlighted).
or i may missunderstood sth ?

i tried --clean, looks that's a bug when cursorlineopt is number, no issue if both. fyi.

I don't know how to reproduce it.
Please provide the complete reproducible steps:

2 concrete small files to diff
and exact command line option you use (with --clean)

xx:
aaa
bbb
ddd
eee

yy:
aaa
ccc

ddd

vimdiff --clean xx yy
set cursorliine
set cursorlineopt=number
hi cursorline ctermbg=red
set nu

hi cursorlinenr ctermbg=red

sorry, probably this was not a bug, or depends on user thought ... that line (#3 in this creen-cut) was not hightlight at that linenr (#3), maybe highlight at #3 better? or current is good enough?

but when cursorlineopt=both, #3 is highlighted, not sure if you can see the diff.. i think this way of highlight when cursorlineopt=both (but for linenr only - the cursorline is still non-hightlighted - since it is number only) is better.

or actually i did not know which one was better,
but just the linenr hightlight should be uniformed ..

for number and both (regardless line - if just talk about linenr).

closing, this is more like a preference & discuss & record. thx.


Other Transport Layers

[Context]
I would like to see (and potentially help build) other kinds of transport laters, i.e. SQS, Redis, Nats, etc.
[Alternatives]
NestJS has something similar.
[Currently implemented]
NestJS has something similar.
[Additional context]
I need to become more familiar with Deno and then I would be happy to help with this.

This is something we want to do. We want to implement microservices, but I’m not sure how to approach that... it would be nice if you can elaborate on this, just a minimal example on the way you see it...
As far as I understand, a microservice would have a handler (which is pretty much a JS function) so the messages would be sent to that JS function (handler), just like an HTTP server in JS works but instead of HTTP requests, it would be messages from the microservice providers. Is this understanding right?

I need to become more familiar with Deno and then I would be happy to help with this.
Absolubtely, As many hands as we can are welcome. Mandarine is always looking for new collaborators, and I am sure this is a huge feature to implement where help will be gladly received.

I want to implement the first part of it by 3.0.0, the idea is to allow websockets to be mandarine-powered. Deno already has a websocket API, I think there's something that can be done here.

Closing as it is being addressed in #274 . For future references please refer to #274


Add osx-arm64

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number — not needed, new platform
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

You're going to need some changes to meta.yaml to get the cross-compilation to work.  In particular, in the build section you'll need:
    - python                                 # [build_platform != target_platform]
    - cross-python_{{ target_platform }}     # [build_platform != target_platform]
    - numpy                                  # [build_platform != target_platform]

Also I like to bump the build number, but I guess that's optional in a migration like this?

Oh!  Didn't notice at first but you need     - cython                                 # [build_platform != target_platform] as well.

Thanks for the tips @erykoff!


ARC-441 Add React

Initial setup of react with a couple of dummy pages to confirm everything works. Building out the UI for each pg, adding state & functionality, and updating documentation will be covered in upcoming PRs.

No longer planning to use React.


asciidoctor: fix build

Description of changes
followup of https://github.com/NixOS/nixpkgs/pull/240499

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build git-lfs

Hi @marsam! Thanks for merging #240499. Can you pleas help me figure out what this follow-up is about (so I can do better next time)? That was my first nixpkgs contribution.
I'd be happy with a link to any relevant docs, don't want to take away even more of your time.


Fix jms/serializer dependency

jms/serializer introduced a bug in version 1.8
Fixes #1868

Thanks for this pr. I decided to change your pr a bit to limit the used version of the serializer. But not upgrading it yet. We will do this in the near future but since not everything is covered by tests jet, I cannot be sure that we won't break anything with this change.
See:
https://github.com/phpDocumentor/phpDocumentor2/commit/a98fd26da9950f19ec4dc987bac25b983e65ff47

Thanks @jaapio. Good thing that this is fixed now so we can switch back to the original phpDocumentor repo instead of having to user our temporary fork.

It will take some time before we are able to create a new release, so please use develop for now.


The console is blurred

version 1.71

/duplicate https://github.com/microsoft/vscode/issues/157585

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


tudat-multidoc not documenting with pydantic v2.3.0

When trying to document the current (local) version of the documentation - using either python cli d or python cli a - pydantic throws a weird error when trying to parse the initial yaml file (package.yaml) in the docstrings. I've attached the entire error output as a .txt file.
pydantic_error_output.txt

You should be able to use this one to create the correct environment:
https://github.com/tudat-team/tudatpy/blob/master/docs/environment_readthedocs.yaml
I'll keep the issue open to correct this properly

Neither Conda nor mamba are able to successfully solve all dependency conflicts for this environment (after un-uncommenting tudat-team from the channels, otherwise nothing works, trivially)... Any ideas?

Could you add the full conda and mamba outputs. In the various configurations you've tried? Which OS are you on?

Sure - I've attached them here. OS-wise I work on a macOS MacBook with an Apple Silicon chip.
conda_error_environment_readthedocs.txt
mamba_error_environment_readthedocs.txt

It looks like it has some issues with the basemap. Try removing it

Works!

Hey team,
I'm afraid I'm also running into this issue, however, even after removing basemap I still receive some errors related to the __package__.yaml when trying python cli d or python cli a. The error I get is shown below in error.log. I removed basemap and basemap-data-hires, and uncommented tudat-team as @kgzenk mentioned previously. Any suggestions?
Best,
Sean
error.log
ps. Miss you all!

Hi Sean,
My apologies, I could have sworn I replied to this already! Great to see you still using Tudat :) We made a correction to the cli tool and pushed it to tudat-bundle:
https://github.com/tudat-team/tudat-bundle
it should work now,
Cheers,
Dominic

Hey Dominic,
No worries! After looking at the recent change to the cli tool, it seems that the cpp API documentation was just commented out. It happens that I would like to access the C++ API documentation, not the python one. Is the C++ API documentation not working at all?
Best,
Sean

Hi Sean, the C++ documentation (in this new setup) has never worked properly... Since we have very few C++-'native' users, we're also seriously considering not proceeding with setting an API-docs for the C++ interface. But, be aware that the 'C++ documentation' as foreseen through moultidoc would not have anything different compared to the current setup, except proper listing of C++ types/names.


Only send consumer metrics when API key is valid

Equivalent to the Java pull request here: https://github.com/cloudendpoints/endpoints-management-java/pull/10

Current coverage is 96.22% (diff: 100%)

Merging #12 into master will increase coverage by <.01%

@@             master        #12   diff @@
==========================================
  Files            28         28
  Lines          2857       2859     +2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           2749       2751     +2
  Misses          108        108
  Partials          0          0

Powered by Codecov. Last update 291a5a0...a75fd4d

Just a note...this pull request is half of the other one, at least by description.

Hmm, nevermind, maybe you don't have to do that. :)