[SPARK-27747][SQL] add a logical plan link in the physical plan

What changes were proposed in this pull request?
It's pretty useful if we can convert a physical plan back to a logical plan, e.g., in https://github.com/apache/spark/pull/24389
This PR introduces a new feature to TreeNode, which allows TreeNode to carry some extra information via a mutable map, and keep the information when it's copied.
The planner leverages this feature to put the logical plan into the physical plan.
How was this patch tested?
a test suite that runs all TPCDS queries and checks that some common physical plans contain the corresponding logical plans.

cc @pengbo this is a more general approach than https://github.com/apache/spark/pull/24389
also cc @maryannxue @bogdanrdc @gatorsmile

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/10719/
Test PASSed.

Test build #105456 has started for PR 24626 at commit d57ecc1.

Test build #105456 has finished for PR 24626 at commit d57ecc1.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TreeNodeTagName(name: String)

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105456/
Test FAILed.

Test build #105482 has started for PR 24626 at commit 9f377d7.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/10743/
Test PASSed.

Test build #105482 has finished for PR 24626 at commit 9f377d7.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #105482 has finished for PR 24626 at commit 9f377d7.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105482/
Test FAILed.

retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/10746/
Test PASSed.

Test build #105485 has started for PR 24626 at commit 9f377d7.

Test build #105485 has finished for PR 24626 at commit 9f377d7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105485/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/10757/
Test PASSed.

Test build #105497 has started for PR 24626 at commit dafad5c.

Test build #105497 has finished for PR 24626 at commit dafad5c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105497/
Test FAILed.

After changing to carry over the tags in transform, it seems that the unit test has to be adjusted as well. Can you please inform the reason?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/10802/
Test PASSed.

Test build #105548 has started for PR 24626 at commit b033f55.

LGTM, pending Jenkins.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/10803/
Test PASSed.

Test build #105549 has started for PR 24626 at commit b380f1d.

Test build #105548 has finished for PR 24626 at commit b033f55.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #105549 has finished for PR 24626 at commit b380f1d.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105549/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105548/
Test FAILed.

retest this please.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/10826/
Test PASSed.

Test build #105572 has started for PR 24626 at commit b380f1d.

Test build #105572 has finished for PR 24626 at commit b380f1d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105572/
Test PASSed.

LGTM
Thanks! Merged to master.


Propagate types from the v3 schema into the v2 query request

In v2 queries, the types of columns or scalar values were often inlined into the query. In v3, the types are omitted from the query and the connector is expected to remember the types from the schema stored in its state.
This PR updates the code that maps v3 queries into v2 queries to ensure all types are inlined into the v2 query from the v3 schema.
Some bugs were fixed along the way:

Queries with predicates that compare against columns in the root query table have been blocked as currently unsupported instead of incorrectly reading the column from the current table
Order by elements that involved relations were not correctly generating a relations (v2::OrderBy.relations) map. They now are.
v3 queries with predicates that involve comparisons against columns in other tables via the column path have been blocked as not supported. This was previously incorrectly mapped to the v2::ComparisonColumn.path property, but this property only ever supported the current table and the query root table, and never an arbitrary path of relationships like v3.

Also: v3 scalar types were being generated every time they were needed; however, this is static data, so they have been generated once and stored in a lazy static and are now reused everywhere.
Issue ticket number and link
JIRA: MDB-7

@hallettj Thanks for fixing those integration tests. 🙏


Re-Enable CI-Infra

Ticket
No ticket that I'm aware of.
Changes

Re-enable CI-Infra checks
Fix some spacing issues

Context for reviewers

There is a failing check in terraform
This is blocked by #120.

Testing

Running the checks here: https://github.com/joeyg/iv-cbv-payroll/actions/runs/10173629424

@GeorgeCodes19 Do you mind looking at this terraform check failure https://github.com/joeyg/iv-cbv-payroll/actions/runs/10173629424/job/28138022832 ?

@joeyg I say we ignore that check. We needed to make that IAM user for the Massachusetts integration.

@tdooner thanks. I updated the PR to skip that check. I'll move this to review once #120 lands.

@tdooner @allthesignals @GeorgeCodes19 for your review


Add IconAlignment to ButtonStyle and styleFrom methods

Fixes Proposal to add iconAlignment to ButtonStyle
Description
This PR refactors buttons IconAlignment, adds to ButtonStyle and styleFrom methods. Which makes it possible to customize iconAlignment same way as icon size and color in the ButtonStyle.
Code sample

expand to view the code sample
import 'package:flutter/material.dart';

enum StyleSegment {
  none,
  widgetButtonStyle,
  widgetStyleFrom,
  themeButtonStyle,
  themeStyleFrom
}

void main() => runApp(const MyApp());

class MyApp extends StatefulWidget {
  const MyApp({super.key});

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  StyleSegment _selectedSegment = StyleSegment.none;

  ThemeData? getThemeStyle() => switch (_selectedSegment) {
        StyleSegment.themeButtonStyle => ThemeData(
            textButtonTheme: const TextButtonThemeData(
              style: ButtonStyle(
                iconAlignment: IconAlignment.end,
              ),
            ),
            elevatedButtonTheme: const ElevatedButtonThemeData(
              style: ButtonStyle(
                iconAlignment: IconAlignment.end,
              ),
            ),
            outlinedButtonTheme: const OutlinedButtonThemeData(
              style: ButtonStyle(
                iconAlignment: IconAlignment.end,
              ),
            ),
            filledButtonTheme: const FilledButtonThemeData(
              style: ButtonStyle(
                iconAlignment: IconAlignment.end,
              ),
            ),
          ),
        StyleSegment.themeStyleFrom => ThemeData(
            textButtonTheme: TextButtonThemeData(
              style: TextButton.styleFrom(
                iconAlignment: IconAlignment.end,
              ),
            ),
            elevatedButtonTheme: const ElevatedButtonThemeData(
              style: ButtonStyle(
                iconAlignment: IconAlignment.end,
              ),
            ),
            outlinedButtonTheme: const OutlinedButtonThemeData(
              style: ButtonStyle(
                iconAlignment: IconAlignment.end,
              ),
            ),
            filledButtonTheme: const FilledButtonThemeData(
              style: ButtonStyle(
                iconAlignment: IconAlignment.end,
              ),
            ),
          ),
        _ => null
      };

  ButtonStyle? getTextButtonStyle() => switch (_selectedSegment) {
        StyleSegment.widgetStyleFrom => TextButton.styleFrom(
            iconAlignment: IconAlignment.end,
          ),
        StyleSegment.widgetButtonStyle => const ButtonStyle(
            iconAlignment: IconAlignment.end,
          ),
        _ => null
      };

  ButtonStyle? getElevatedButtonStyle() => switch (_selectedSegment) {
        StyleSegment.widgetStyleFrom => ElevatedButton.styleFrom(
            iconAlignment: IconAlignment.end,
          ),
        StyleSegment.widgetButtonStyle => const ButtonStyle(
            iconAlignment: IconAlignment.end,
          ),
        _ => null
      };

  ButtonStyle? getOutlinedButtonStyle() => switch (_selectedSegment) {
        StyleSegment.widgetStyleFrom => OutlinedButton.styleFrom(
            iconAlignment: IconAlignment.end,
          ),
        StyleSegment.widgetButtonStyle => const ButtonStyle(
            iconAlignment: IconAlignment.end,
          ),
        _ => null
      };

  ButtonStyle? getFilledButtonStyle() => switch (_selectedSegment) {
        StyleSegment.widgetStyleFrom => FilledButton.styleFrom(
            iconAlignment: IconAlignment.end,
          ),
        StyleSegment.widgetButtonStyle => const ButtonStyle(
            iconAlignment: IconAlignment.end,
          ),
        _ => null
      };

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      theme: getThemeStyle(),
      home: Scaffold(
        appBar: AppBar(
          title: const Text('ButtonStyle Icon Alignment'),
        ),
        body: Center(
          child: Padding(
            padding: const EdgeInsets.all(16.0),
            child: Column(
              mainAxisAlignment: MainAxisAlignment.center,
              spacing: 20,
              children: [
                Wrap(
                  spacing: 16,
                  runSpacing: 16,
                  children: [
                    TextButton.icon(
                      style: getTextButtonStyle(),
                      onPressed: () {},
                      icon: const Icon(Icons.add),
                      label: const Text('Text Button'),
                    ),
                    ElevatedButton.icon(
                      style: getElevatedButtonStyle(),
                      onPressed: () {},
                      icon: const Icon(Icons.add),
                      label: const Text('Elevated Button'),
                    ),
                    OutlinedButton.icon(
                      style: getOutlinedButtonStyle(),
                      onPressed: () {},
                      icon: const Icon(Icons.add),
                      label: const Text('Outlined Button'),
                    ),
                    FilledButton.icon(
                      style: getFilledButtonStyle(),
                      onPressed: () {},
                      icon: const Icon(Icons.add),
                      label: const Text('Filled Button'),
                    ),
                    FilledButton.tonalIcon(
                      style: getFilledButtonStyle(),
                      onPressed: () {},
                      icon: const Icon(Icons.add),
                      label: const Text('Filled Button Tonal Icon'),
                    ),
                  ],
                ),
                StyleSelection(
                  selectedSegment: _selectedSegment,
                  onSegmentSelected: (StyleSegment segment) {
                    setState(() {
                      _selectedSegment = segment;
                    });
                  },
                ),
              ],
            ),
          ),
        ),
      ),
    );
  }
}

class StyleSelection extends StatelessWidget {
  const StyleSelection(
      {super.key,
      this.selectedSegment = StyleSegment.none,
      required this.onSegmentSelected});

  final ValueChanged<StyleSegment> onSegmentSelected;
  final StyleSegment selectedSegment;

  @override
  Widget build(BuildContext context) {
    return SegmentedButton<StyleSegment>(
      segments: const <ButtonSegment<StyleSegment>>[
        ButtonSegment<StyleSegment>(
          value: StyleSegment.none,
          label: Text('None'),
        ),
        ButtonSegment<StyleSegment>(
          value: StyleSegment.widgetButtonStyle,
          label: Text('Widget Button Style'),
        ),
        ButtonSegment<StyleSegment>(
          value: StyleSegment.widgetStyleFrom,
          label: Text('Widget Style From'),
        ),
        ButtonSegment<StyleSegment>(
          value: StyleSegment.themeButtonStyle,
          label: Text('Theme Button Style'),
        ),
        ButtonSegment<StyleSegment>(
          value: StyleSegment.themeStyleFrom,
          label: Text('Theme Style From'),
        ),
      ],
      selected: <StyleSegment>{selectedSegment},
      onSelectionChanged: (Set<StyleSegment> newSelection) {
        onSegmentSelected(newSelection.first);
      },
    );
  }
}

Preview

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Looks like this is failing google testing.

Waiting cl/700088185 to land.

@QuncCccccc
Please let me know when it  lands so I can rebase this.

It landed JUST now haha. Please try to rebase master. Hope all tests can pass now:)

It landed JUST now haha. Please try to rebase master. Hope all tests can pass now:)

Rebased and also pushed additional empty commit for safety.


Random Number Generator Entropy Loss Warning

If the random number generator entropy is lost during a simulation, it should be a warning except during the initialization.

This no longer is a problem.


[openebs/litmus] (test): Include a litmus book to perform application node name replacement (via ansible ec2 shutdown module).

Signed-off-by: mittachaitu<EMAIL_ADDRESS>
What this PR does / why we need it:

Include a litmus book to perform application node replacement. (by shutting down the application node)
This test requires AWS kops cluster and by shutting down the node kops will create another node(with a different name).
Pre-chaos and post chaos will verify the application pod status by verifying the liveness pod status.
Test logs::

ansible-playbook 2.7.4
  config file = None
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python2.7/dist-packages/ansible
  executable location = /usr/local/bin/ansible-playbook
  python version = 2.7.15rc1 (default, Nov 12 2018, 14:31:15) [GCC 7.3.0]
No config file found; using defaults
/etc/ansible/hosts did not meet host_list requirements, check plugin documentation if this is unexpected
/etc/ansible/hosts did not meet script requirements, check plugin documentation if this is unexpected

PLAYBOOK: test.yml *************************************************************
1 plays in ./percona/chaos/app_node_failure_ups_diff_name/test.yml
 [WARNING]: Found variable using reserved name: action

PLAY [localhost] ***************************************************************

TASK [Gathering Facts] *********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:2
ok: [<IP_ADDRESS>]
META: ran handlers

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:13
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:17
included: /common/utils/create_testname.yml for <IP_ADDRESS>

TASK [Record test instance/run ID] *********************************************
task path: /common/utils/create_testname.yml:3
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Construct testname appended with runID] **********************************
task path: /common/utils/create_testname.yml:7
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:19
included: /chaoslib/aws_chaos/prerequisites_aws.yml for <IP_ADDRESS>

TASK [Installing pip] **********************************************************
task path: /chaoslib/aws_chaos/prerequisites_aws.yml:2
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "apt install python-pip", "delta": "0:00:01.405323", "end": "2018-12-05 08:24:27.321882", "rc": 0, "start": "2018-12-05 08:24:25.916559", "stderr": "\nWARNING: apt does not have a stable CLI interface. Use with caution in scripts.", "stderr_lines": ["", "WARNING: apt does not have a stable CLI interface. Use with caution in scripts."], "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\npython-pip is already the newest version (9.0.1-2.3~ubuntu1).\n0 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "python-pip is already the newest version (9.0.1-2.3~ubuntu1).", "0 upgraded, 0 newly installed, 0 to remove and 16 not upgraded."]}

TASK [Installing boto] *********************************************************
task path: /chaoslib/aws_chaos/prerequisites_aws.yml:7
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "pip install boto", "delta": "0:00:01.844309", "end": "2018-12-05 08:24:29.300764", "rc": 0, "start": "2018-12-05 08:24:27.456455", "stderr": "", "stderr_lines": [], "stdout": "Collecting boto\n  Downloading https://files.pythonhosted.org/packages/23/10/c0b78c27298029e4454a472a1919bde20cb182dab1662cec7f2ca1dcc523/boto-2.49.0-py2.py3-none-any.whl (1.4MB)\nInstalling collected packages: boto\nSuccessfully installed boto-2.49.0", "stdout_lines": ["Collecting boto", "  Downloading https://files.pythonhosted.org/packages/23/10/c0b78c27298029e4454a472a1919bde20cb182dab1662cec7f2ca1dcc523/boto-2.49.0-py2.py3-none-any.whl (1.4MB)", "Installing collected packages: boto", "Successfully installed boto-2.49.0"]}

TASK [Check the status of nodes and have count of nodes] ***********************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:22
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl get nodes --no-headers | grep -v 'master'", "delta": "0:00:00.490638", "end": "2018-12-05 08:24:29.925141", "rc": 0, "start": "2018-12-05 08:24:29.434503", "stderr": "", "stderr_lines": [], "stdout": "ip-10-0-1-196.us-west-1.compute.internal   Ready   node     3h    v1.11.0\nip-10-0-1-197.us-west-1.compute.internal   Ready   node     30m   v1.11.0\nip-10-0-1-223.us-west-1.compute.internal   Ready   node     18m   v1.11.0", "stdout_lines": ["ip-10-0-1-196.us-west-1.compute.internal   Ready   node     3h    v1.11.0", "ip-10-0-1-197.us-west-1.compute.internal   Ready   node     30m   v1.11.0", "ip-10-0-1-223.us-west-1.compute.internal   Ready   node     18m   v1.11.0"]}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:29
included: /common/utils/update_litmus_result_resource.yml for <IP_ADDRESS>

TASK [Generate the litmus result CR to reflect SOT (Start of Test)] ************
task path: /common/utils/update_litmus_result_resource.yml:3
changed: [<IP_ADDRESS>] => {"changed": true, "checksum": "e909735046d5c6ee8373199726aa1bce8b2c254c", "dest": "./litmus-result.yaml", "gid": 0, "group": "root", "md5sum": "f3cc97d53b74529366406c555ecc059b", "mode": "0644", "owner": "root", "size": 465, "src": "/root/.ansible/tmp/ansible-tmp-1543998270.05-107062844560661/source", "state": "file", "uid": 0}

TASK [Analyze the cr yaml] *****************************************************
task path: /common/utils/update_litmus_result_resource.yml:14
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "cat litmus-result.yaml", "delta": "0:00:00.287629", "end": "2018-12-05 08:24:30.838701", "rc": 0, "start": "2018-12-05 08:24:30.551072", "stderr": "", "stderr_lines": [], "stdout": "---\napiVersion: litmus.io/v1alpha1\nkind: LitmusResult\nmetadata:\n\n  # name of the litmus testcase\n  name: node-shutdown-up-with-diff-name \nspec:\n\n  # holds information on the testcase\n  testMetadata:\n    app: percona \n    chaostype: node-shutdown-up-diff-name \n\n  # holds the state of testcase,  manually updated by json merge patch\n  # result is the useful value today, but anticipate phase use in future \n  testStatus: \n    phase: in-progress  \n    result: none ", "stdout_lines": ["---", "apiVersion: litmus.io/v1alpha1", "kind: LitmusResult", "metadata:", "", "  # name of the litmus testcase", "  name: node-shutdown-up-with-diff-name ", "spec:", "", "  # holds information on the testcase", "  testMetadata:", "    app: percona ", "    chaostype: node-shutdown-up-diff-name ", "", "  # holds the state of testcase,  manually updated by json merge patch", "  # result is the useful value today, but anticipate phase use in future ", "  testStatus: ", "    phase: in-progress  ", "    result: none "]}

TASK [Apply the litmus result CR] **********************************************
task path: /common/utils/update_litmus_result_resource.yml:17
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl apply -f litmus-result.yaml", "delta": "0:00:00.448031", "end": "2018-12-05 08:24:31.424967", "failed_when_result": false, "rc": 0, "start": "2018-12-05 08:24:30.976936", "stderr": "", "stderr_lines": [], "stdout": "litmusresult.litmus.io/node-shutdown-up-with-diff-name configured", "stdout_lines": ["litmusresult.litmus.io/node-shutdown-up-with-diff-name configured"]}

TASK [Generate the litmus result CR to reflect EOT (End of Test)] **************
task path: /common/utils/update_litmus_result_resource.yml:27
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Analyze the cr yaml] *****************************************************
task path: /common/utils/update_litmus_result_resource.yml:38
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Apply the litmus result CR] **********************************************
task path: /common/utils/update_litmus_result_resource.yml:41
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Display the app information passed via the test job] *********************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:36
ok: [<IP_ADDRESS>] => {
    "msg": [
        "The application info is as follows:",
        "Namespace    : app-percona-ns",
        "Label        : name=percona"
    ]
}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:44
included: /common/utils/status_app_pod.yml for <IP_ADDRESS>

TASK [Checking Percona pod is in running state] ********************************
task path: /common/utils/status_app_pod.yml:2
changed: [<IP_ADDRESS>] => {"attempts": 1, "changed": true, "cmd": "kubectl get pods -n app-percona-ns -o jsonpath='{.items[?(@.metadata.labels.name==\"percona\")].status.phase}'", "delta": "0:00:00.356346", "end": "2018-12-05 08:24:32.139700", "rc": 0, "start": "2018-12-05 08:24:31.783354", "stderr": "", "stderr_lines": [], "stdout": "Running", "stdout_lines": ["Running"]}

TASK [Get application pod name] ************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:54
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl get po -n app-percona-ns -l name=percona --no-headers -o=custom-columns=NAME:\".metadata.name\"", "delta": "0:00:00.356654", "end": "2018-12-05 08:24:32.642383", "rc": 0, "start": "2018-12-05 08:24:32.285729", "stderr": "", "stderr_lines": [], "stdout": "percona-6966c6db86-8gxk4", "stdout_lines": ["percona-6966c6db86-8gxk4"]}

TASK [Generate some random name for database creation] *************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:62
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "echo $(mktemp) | cut -d '.' -f 2", "delta": "0:00:00.279384", "end": "2018-12-05 08:24:33.057051", "rc": 0, "start": "2018-12-05 08:24:32.777667", "stderr": "", "stderr_lines": [], "stdout": "VKT5yG2OtF", "stdout_lines": ["VKT5yG2OtF"]}

TASK [Create test load in the mysql database] **********************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:70
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Get Application pod Node to perform chaos] *******************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:82
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl get pod percona-6966c6db86-8gxk4 -n app-percona-ns --no-headers -o custom-columns=:spec.nodeName", "delta": "0:00:00.352246", "end": "2018-12-05 08:24:33.588562", "rc": 0, "start": "2018-12-05 08:24:33.236316", "stderr": "", "stderr_lines": [], "stdout": "ip-10-0-1-197.us-west-1.compute.internal", "stdout_lines": ["ip-10-0-1-197.us-west-1.compute.internal"]}

TASK [Get the AWS instance Id of APP NOde] *************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:91
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl get node ip-10-0-1-197.us-west-1.compute.internal -o jsonpath={.spec.providerID} | cut -d '/' -f 5", "delta": "0:00:00.355376", "end": "2018-12-05 08:24:34.079103", "rc": 0, "start": "2018-12-05 08:24:33.723727", "stderr": "", "stderr_lines": [], "stdout": "i-09644e5558538b7d8", "stdout_lines": ["i-09644e5558538b7d8"]}

TASK [Get region from app node] ************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:97
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl get nodes ip-10-0-1-197.us-west-1.compute.internal -o jsonpath='{.metadata.labels.failure-domain\\.beta\\.kubernetes\\.io\\/region}'", "delta": "0:00:00.356482", "end": "2018-12-05 08:24:34.571390", "rc": 0, "start": "2018-12-05 08:24:34.214908", "stderr": "", "stderr_lines": [], "stdout": "us-west-1", "stdout_lines": ["us-west-1"]}

TASK [set_fact] ****************************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:103
ok: [<IP_ADDRESS>] => {"ansible_facts": {"instance_id": "i-09644e5558538b7d8", "region": "us-west-1"}, "changed": false}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:108
included: /chaoslib/aws_chaos/chaosutil_aws.yml for <IP_ADDRESS>

TASK [Stop the AWS ec2 instances] **********************************************
task path: /chaoslib/aws_chaos/chaosutil_aws.yml:2
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": false, "msg": "wait for instances running timeout on Wed Dec  5 08:29:38 2018"}
...ignoring

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:111
included: /common/utils/check_no_of_nodes.yml for <IP_ADDRESS>

TASK [Waiting for application pod reschedule (evict)] **************************
task path: /common/utils/check_no_of_nodes.yml:4
ok: [<IP_ADDRESS>] => {"changed": false, "elapsed": 50, "path": null, "port": null, "search_regex": null, "state": "started"}

TASK [Checking the status of chaos injected node] ******************************
task path: /common/utils/check_no_of_nodes.yml:8
changed: [<IP_ADDRESS>] => {"attempts": 1, "changed": true, "cmd": "kubectl get nodes --no-headers | grep -vi 'master'", "delta": "0:00:00.361597", "end": "2018-12-05 08:30:29.059198", "rc": 0, "start": "2018-12-05 08:30:28.697601", "stderr": "", "stderr_lines": [], "stdout": "ip-10-0-1-196.us-west-1.compute.internal   Ready   node     3h    v1.11.0\nip-10-0-1-223.us-west-1.compute.internal   Ready   node     24m   v1.11.0\nip-10-0-1-93.us-west-1.compute.internal    Ready   node     2m    v1.11.0", "stdout_lines": ["ip-10-0-1-196.us-west-1.compute.internal   Ready   node     3h    v1.11.0", "ip-10-0-1-223.us-west-1.compute.internal   Ready   node     24m   v1.11.0", "ip-10-0-1-93.us-west-1.compute.internal    Ready   node     2m    v1.11.0"]}

TASK [Checking the no.of nodes] ************************************************
task path: /common/utils/check_no_of_nodes.yml:22
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:116
included: /common/utils/status_app_pod.yml for <IP_ADDRESS>

TASK [Checking Percona post chaos pod is in running state] *********************
task path: /common/utils/status_app_pod.yml:2
FAILED - RETRYING: Checking Percona post chaos pod is in running state (30 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (29 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (28 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (27 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (26 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (25 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (24 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (23 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (22 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (21 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (20 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (19 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (18 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (17 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (16 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (15 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (14 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (13 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (12 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (11 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (10 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (9 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (8 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (7 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (6 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (5 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (4 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (3 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (2 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (1 retries left).
fatal: [<IP_ADDRESS>]: FAILED! => {"attempts": 30, "changed": true, "cmd": "kubectl get pods -n app-percona-ns -o jsonpath='{.items[?(@.metadata.labels.name==\"percona\")].status.phase}'", "delta": "0:00:00.361336", "end": "2018-12-05 08:35:43.453856", "rc": 0, "start": "2018-12-05 08:35:43.092520", "stderr": "", "stderr_lines": [], "stdout": "Pending", "stdout_lines": ["Pending"]}

TASK [set_fact] ****************************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:152
ok: [<IP_ADDRESS>] => {"ansible_facts": {"flag": "Fail"}, "changed": false}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:156
included: /common/utils/update_litmus_result_resource.yml for <IP_ADDRESS>

TASK [Generate the litmus result CR to reflect SOT (Start of Test)] ************
task path: /common/utils/update_litmus_result_resource.yml:3
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Analyze the cr yaml] *****************************************************
task path: /common/utils/update_litmus_result_resource.yml:14
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Apply the litmus result CR] **********************************************
task path: /common/utils/update_litmus_result_resource.yml:17
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Generate the litmus result CR to reflect EOT (End of Test)] **************
task path: /common/utils/update_litmus_result_resource.yml:27
changed: [<IP_ADDRESS>] => {"changed": true, "checksum": "172ad245da32aeaf259c6b1090839707494baa19", "dest": "./litmus-result.yaml", "gid": 0, "group": "root", "md5sum": "bb91bd76c32793425a40a7447b4a7257", "mode": "0644", "owner": "root", "size": 463, "src": "/root/.ansible/tmp/ansible-tmp-1543998943.73-228328549819093/source", "state": "file", "uid": 0}

TASK [Analyze the cr yaml] *****************************************************
task path: /common/utils/update_litmus_result_resource.yml:38
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "cat litmus-result.yaml", "delta": "0:00:00.279322", "end": "2018-12-05 08:35:44.872047", "rc": 0, "start": "2018-12-05 08:35:44.592725", "stderr": "", "stderr_lines": [], "stdout": "---\napiVersion: litmus.io/v1alpha1\nkind: LitmusResult\nmetadata:\n\n  # name of the litmus testcase\n  name: node-shutdown-up-with-diff-name \nspec:\n\n  # holds information on the testcase\n  testMetadata:\n    app: percona \n    chaostype: node-shutdown-up-diff-name \n\n  # holds the state of testcase,  manually updated by json merge patch\n  # result is the useful value today, but anticipate phase use in future \n  testStatus: \n    phase: completed  \n    result: Fail ", "stdout_lines": ["---", "apiVersion: litmus.io/v1alpha1", "kind: LitmusResult", "metadata:", "", "  # name of the litmus testcase", "  name: node-shutdown-up-with-diff-name ", "spec:", "", "  # holds information on the testcase", "  testMetadata:", "    app: percona ", "    chaostype: node-shutdown-up-diff-name ", "", "  # holds the state of testcase,  manually updated by json merge patch", "  # result is the useful value today, but anticipate phase use in future ", "  testStatus: ", "    phase: completed  ", "    result: Fail "]}

TASK [Apply the litmus result CR] **********************************************
task path: /common/utils/update_litmus_result_resource.yml:41
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl apply -f litmus-result.yaml", "delta": "0:00:00.419271", "end": "2018-12-05 08:35:45.431301", "failed_when_result": false, "rc": 0, "start": "2018-12-05 08:35:45.012030", "stderr": "", "stderr_lines": [], "stdout": "litmusresult.litmus.io/node-shutdown-up-with-diff-name configured", "stdout_lines": ["litmusresult.litmus.io/node-shutdown-up-with-diff-name configured"]}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:162
included: /common/utils/check_no_of_nodes.yml for <IP_ADDRESS>

TASK [Waiting for application pod reschedule (evict)] **************************
task path: /common/utils/check_no_of_nodes.yml:4
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Checking the status of chaos injected node] ******************************
task path: /common/utils/check_no_of_nodes.yml:8
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Checking the no.of nodes] ************************************************
task path: /common/utils/check_no_of_nodes.yml:22
changed: [<IP_ADDRESS>] => {"attempts": 1, "changed": true, "cmd": "kubectl get nodes --no-headers | grep -vi 'master' | grep -i 'Ready'", "delta": "0:00:00.352739", "end": "2018-12-05 08:35:46.053236", "rc": 0, "start": "2018-12-05 08:35:45.700497", "stderr": "", "stderr_lines": [], "stdout": "ip-10-0-1-196.us-west-1.compute.internal   Ready   node     3h    v1.11.0\nip-10-0-1-223.us-west-1.compute.internal   Ready   node     29m   v1.11.0\nip-10-0-1-93.us-west-1.compute.internal    Ready   node     7m    v1.11.0", "stdout_lines": ["ip-10-0-1-196.us-west-1.compute.internal   Ready   node     3h    v1.11.0", "ip-10-0-1-223.us-west-1.compute.internal   Ready   node     29m   v1.11.0", "ip-10-0-1-93.us-west-1.compute.internal    Ready   node     7m    v1.11.0"]}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:166
included: /common/utils/check_cstor_pool_pod.yml for <IP_ADDRESS>

TASK [Get the cstor pool pods which remains in a pending state] ****************
task path: /common/utils/check_cstor_pool_pod.yml:2
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": true, "cmd": "kubectl get po -n openebs -l app=cstor-pool -o jsonpath='{.items[?(@.status.phase==\"Pending\")].metadata.name}' | cut -d '-' -f -4", "delta": "0:00:00.359822", "end": "2018-12-05 08:35:46.616208", "failed_when_result": true, "rc": 0, "start": "2018-12-05 08:35:46.256386", "stderr": "", "stderr_lines": [], "stdout": "cstor-sparse-pool-h5s8", "stdout_lines": ["cstor-sparse-pool-h5s8"]}
	to retry, use: --limit @/percona/chaos/app_node_failure_ups_diff_name/test.retry

PLAY RECAP *********************************************************************
<IP_ADDRESS>                  : ok=33   changed=17   unreachable=0    failed=2

@ksatchit @vishnuitta @dargasudarshan @gprasath  PTAL on this PR
Note: Triggered Pipeline and it passed as expected.
Pipeline url: https://gitlab.openebs.ci/openebs/e2e-aws/-/jobs/1098

can we change the job name  like app_node_restart_with_diff_name ?

@ksatchit  logs after including the util (Platform dependent AWS)
kubectl logs -f node-replacement-fvm5c-rzgbz -n litmus
ansible-playbook 2.7.4
  config file = None
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python2.7/dist-packages/ansible
  executable location = /usr/local/bin/ansible-playbook
  python version = 2.7.15rc1 (default, Nov 12 2018, 14:31:15) [GCC 7.3.0]
No config file found; using defaults
/etc/ansible/hosts did not meet host_list requirements, check plugin documentation if this is unexpected
/etc/ansible/hosts did not meet script requirements, check plugin documentation if this is unexpected

PLAYBOOK: test.yml *************************************************************
1 plays in ./percona/chaos/app_node_failure_ups_diff_name/test.yml
 [WARNING]: Found variable using reserved name: action

PLAY [localhost] ***************************************************************

TASK [Gathering Facts] *********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:2
ok: [<IP_ADDRESS>]
META: ran handlers

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:13
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:17
included: /common/utils/create_testname.yml for <IP_ADDRESS>

TASK [Record test instance/run ID] *********************************************
task path: /common/utils/create_testname.yml:3
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Construct testname appended with runID] **********************************
task path: /common/utils/create_testname.yml:7
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:19
included: /chaoslib/aws_chaos/prerequisites_aws.yml for <IP_ADDRESS>

TASK [Installing pip] **********************************************************
task path: /chaoslib/aws_chaos/prerequisites_aws.yml:2
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "apt install python-pip", "delta": "0:00:01.397367", "end": "2018-12-08 18:33:19.653497", "rc": 0, "start": "2018-12-08 18:33:18.256130", "stderr": "\nWARNING: apt does not have a stable CLI interface. Use with caution in scripts.", "stderr_lines": ["", "WARNING: apt does not have a stable CLI interface. Use with caution in scripts."], "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\npython-pip is already the newest version (9.0.1-2.3~ubuntu1).\n0 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "python-pip is already the newest version (9.0.1-2.3~ubuntu1).", "0 upgraded, 0 newly installed, 0 to remove and 16 not upgraded."]}

TASK [Installing boto] *********************************************************
task path: /chaoslib/aws_chaos/prerequisites_aws.yml:7
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "pip install boto", "delta": "0:00:01.834495", "end": "2018-12-08 18:33:21.618739", "rc": 0, "start": "2018-12-08 18:33:19.784244", "stderr": "", "stderr_lines": [], "stdout": "Collecting boto\n  Downloading https://files.pythonhosted.org/packages/23/10/c0b78c27298029e4454a472a1919bde20cb182dab1662cec7f2ca1dcc523/boto-2.49.0-py2.py3-none-any.whl (1.4MB)\nInstalling collected packages: boto\nSuccessfully installed boto-2.49.0", "stdout_lines": ["Collecting boto", "  Downloading https://files.pythonhosted.org/packages/23/10/c0b78c27298029e4454a472a1919bde20cb182dab1662cec7f2ca1dcc523/boto-2.49.0-py2.py3-none-any.whl (1.4MB)", "Installing collected packages: boto", "Successfully installed boto-2.49.0"]}

TASK [Check the status of nodes and have count of nodes] ***********************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:22
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl get nodes --no-headers | grep -v 'master'", "delta": "0:00:00.488112", "end": "2018-12-08 18:33:22.243534", "rc": 0, "start": "2018-12-08 18:33:21.755422", "stderr": "", "stderr_lines": [], "stdout": "ip-10-0-1-13.us-west-1.compute.internal    Ready   node     10h   v1.11.0\nip-10-0-1-232.us-west-1.compute.internal   Ready   node     10h   v1.11.0\nip-10-0-1-65.us-west-1.compute.internal    Ready   node     24m   v1.11.0", "stdout_lines": ["ip-10-0-1-13.us-west-1.compute.internal    Ready   node     10h   v1.11.0", "ip-10-0-1-232.us-west-1.compute.internal   Ready   node     10h   v1.11.0", "ip-10-0-1-65.us-west-1.compute.internal    Ready   node     24m   v1.11.0"]}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:29
included: /common/utils/update_litmus_result_resource.yml for <IP_ADDRESS>

TASK [Generate the litmus result CR to reflect SOT (Start of Test)] ************
task path: /common/utils/update_litmus_result_resource.yml:3
changed: [<IP_ADDRESS>] => {"changed": true, "checksum": "6c89d31299310b5fb0f466845094d788af589c6b", "dest": "./litmus-result.yaml", "gid": 0, "group": "root", "md5sum": "dd7bb31a2659051485535d0cde60f85c", "mode": "0644", "owner": "root", "size": 450, "src": "/root/.ansible/tmp/ansible-tmp-1544294002.37-21580064841878/source", "state": "file", "uid": 0}

TASK [Analyze the cr yaml] *****************************************************
task path: /common/utils/update_litmus_result_resource.yml:14
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "cat litmus-result.yaml", "delta": "0:00:00.281137", "end": "2018-12-08 18:33:23.141316", "rc": 0, "start": "2018-12-08 18:33:22.860179", "stderr": "", "stderr_lines": [], "stdout": "---\napiVersion: litmus.io/v1alpha1\nkind: LitmusResult\nmetadata:\n\n  # name of the litmus testcase\n  name: node-replacement \nspec:\n\n  # holds information on the testcase\n  testMetadata:\n    app: percona \n    chaostype: node-shutdown-up-diff-name \n\n  # holds the state of testcase,  manually updated by json merge patch\n  # result is the useful value today, but anticipate phase use in future \n  testStatus: \n    phase: in-progress  \n    result: none ", "stdout_lines": ["---", "apiVersion: litmus.io/v1alpha1", "kind: LitmusResult", "metadata:", "", "  # name of the litmus testcase", "  name: node-replacement ", "spec:", "", "  # holds information on the testcase", "  testMetadata:", "    app: percona ", "    chaostype: node-shutdown-up-diff-name ", "", "  # holds the state of testcase,  manually updated by json merge patch", "  # result is the useful value today, but anticipate phase use in future ", "  testStatus: ", "    phase: in-progress  ", "    result: none "]}

TASK [Apply the litmus result CR] **********************************************
task path: /common/utils/update_litmus_result_resource.yml:17
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl apply -f litmus-result.yaml", "delta": "0:00:00.448848", "end": "2018-12-08 18:33:23.725749", "failed_when_result": false, "rc": 0, "start": "2018-12-08 18:33:23.276901", "stderr": "", "stderr_lines": [], "stdout": "litmusresult.litmus.io/node-replacement created", "stdout_lines": ["litmusresult.litmus.io/node-replacement created"]}

TASK [Generate the litmus result CR to reflect EOT (End of Test)] **************
task path: /common/utils/update_litmus_result_resource.yml:27
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Analyze the cr yaml] *****************************************************
task path: /common/utils/update_litmus_result_resource.yml:38
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Apply the litmus result CR] **********************************************
task path: /common/utils/update_litmus_result_resource.yml:41
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Display the app information passed via the test job] *********************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:36
ok: [<IP_ADDRESS>] => {
    "msg": [
        "The application info is as follows:",
        "Namespace    : app-percona-ns",
        "Label        : name=percona"
    ]
}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:44
included: /common/utils/status_app_pod.yml for <IP_ADDRESS>

TASK [Checking Percona pod is in running state] ********************************
task path: /common/utils/status_app_pod.yml:2
changed: [<IP_ADDRESS>] => {"attempts": 1, "changed": true, "cmd": "kubectl get pods -n app-percona-ns -o jsonpath='{.items[?(@.metadata.labels.name==\"percona\")].status.phase}'", "delta": "0:00:00.355140", "end": "2018-12-08 18:33:24.437558", "rc": 0, "start": "2018-12-08 18:33:24.082418", "stderr": "", "stderr_lines": [], "stdout": "Running", "stdout_lines": ["Running"]}

TASK [Get application pod name] ************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:54
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl get po -n app-percona-ns -l name=percona --no-headers -o=custom-columns=NAME:\".metadata.name\"", "delta": "0:00:00.353195", "end": "2018-12-08 18:33:24.939496", "rc": 0, "start": "2018-12-08 18:33:24.586301", "stderr": "", "stderr_lines": [], "stdout": "percona-6966c6db86-x2xwn", "stdout_lines": ["percona-6966c6db86-x2xwn"]}

TASK [Generate some random name for database creation] *************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:62
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "echo $(mktemp) | cut -d '.' -f 2", "delta": "0:00:00.282810", "end": "2018-12-08 18:33:25.355335", "rc": 0, "start": "2018-12-08 18:33:25.072525", "stderr": "", "stderr_lines": [], "stdout": "vbhzUtamIt", "stdout_lines": ["vbhzUtamIt"]}

TASK [Create test load in the mysql database] **********************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:70
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Get Application pod Node to perform chaos] *******************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:82
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl get pod percona-6966c6db86-x2xwn -n app-percona-ns --no-headers -o custom-columns=:spec.nodeName", "delta": "0:00:00.355870", "end": "2018-12-08 18:33:25.890280", "rc": 0, "start": "2018-12-08 18:33:25.534410", "stderr": "", "stderr_lines": [], "stdout": "ip-10-0-1-13.us-west-1.compute.internal", "stdout_lines": ["ip-10-0-1-13.us-west-1.compute.internal"]}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:91
included: /common/utils/fetch_aws_details.yml for <IP_ADDRESS>

TASK [Get the AWS instance Id of APP NOde] *************************************
task path: /common/utils/fetch_aws_details.yml:3
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl get node ip-10-0-1-13.us-west-1.compute.internal -o jsonpath={.spec.providerID} | cut -d '/' -f 5", "delta": "0:00:00.352628", "end": "2018-12-08 18:33:26.442100", "rc": 0, "start": "2018-12-08 18:33:26.089472", "stderr": "", "stderr_lines": [], "stdout": "i-0578abec273c95f73", "stdout_lines": ["i-0578abec273c95f73"]}

TASK [Get region from app node] ************************************************
task path: /common/utils/fetch_aws_details.yml:9
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl get nodes ip-10-0-1-13.us-west-1.compute.internal -o jsonpath='{.metadata.labels.failure-domain\\.beta\\.kubernetes\\.io\\/region}'", "delta": "0:00:00.354543", "end": "2018-12-08 18:33:26.934060", "rc": 0, "start": "2018-12-08 18:33:26.579517", "stderr": "", "stderr_lines": [], "stdout": "us-west-1", "stdout_lines": ["us-west-1"]}

TASK [set_fact] ****************************************************************
task path: /common/utils/fetch_aws_details.yml:16
ok: [<IP_ADDRESS>] => {"ansible_facts": {"instance_id": "i-0578abec273c95f73", "region": "us-west-1"}, "changed": false}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:95
included: /chaoslib/aws_chaos/chaosutil_aws.yml for <IP_ADDRESS>

TASK [Performing action on AWS ec2 instances] **********************************
task path: /chaoslib/aws_chaos/chaosutil_aws.yml:2
changed: [<IP_ADDRESS>] => {"changed": true, "instance_ids": ["i-0578abec273c95f73"], "instances": [{"ami_launch_index": "0", "architecture": "x86_64", "block_device_mapping": {"/dev/sda1": {"delete_on_termination": true, "status": "attached", "volume_id": "vol-026d66c141337bf59"}}, "dns_name": "", "ebs_optimized": false, "groups": {"sg-03a4da4ce3ead292b": "nodes.k8s-sai-ubuntu.k8s.local"}, "hypervisor": "xen", "id": "i-0578abec273c95f73", "image_id": "ami-0ad16744583f21877", "instance_type": "t2.xlarge", "kernel": null, "key_name": "kubernetes.k8s-sai-ubuntu.k8s.local-14:ef:42:fe:eb:1c:4e:6f:1f:f1:e1:87:75:95:96:df", "launch_time": "2018-12-08T07:46:18.000Z", "placement": "us-west-1a", "private_dns_name": "ip-10-0-1-13.us-west-1.compute.internal", "private_ip": "<IP_ADDRESS>", "public_dns_name": "", "public_ip": null, "ramdisk": null, "region": "us-west-1", "root_device_name": "/dev/sda1", "root_device_type": "ebs", "state": "stopped", "state_code": 80, "tags": {"KubernetesCluster": "k8s-sai-ubuntu.k8s.local", "Name": "nodes.k8s-sai-ubuntu.k8s.local", "aws:autoscaling:groupName": "nodes.k8s-sai-ubuntu.k8s.local", "k8s.io/cluster-autoscaler/node-template/label/kops.k8s.io/instancegroup": "nodes", "k8s.io/role/node": "1"}, "tenancy": "default", "virtualization_type": "hvm"}], "tagged_instances": []}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:98
included: /common/utils/check_no_of_nodes.yml for <IP_ADDRESS>

TASK [Waiting for application pod reschedule (evict)] **************************
task path: /common/utils/check_no_of_nodes.yml:4
ok: [<IP_ADDRESS>] => {"changed": false, "elapsed": 50, "path": null, "port": null, "search_regex": null, "state": "started"}

TASK [Checking the status of chaos injected node] ******************************
task path: /common/utils/check_no_of_nodes.yml:8
 [WARNING]: when statements should not include jinja2 templating delimiters
such as {{ }} or {% %}. Found: '{{ app_node.stdout }}' not in node_names.stdout

changed: [<IP_ADDRESS>] => {"attempts": 1, "changed": true, "cmd": "kubectl get nodes --no-headers | grep -vi 'master'", "delta": "0:00:00.355353", "end": "2018-12-08 18:34:49.323509", "rc": 0, "start": "2018-12-08 18:34:48.968156", "stderr": "", "stderr_lines": [], "stdout": "ip-10-0-1-232.us-west-1.compute.internal   Ready   node     10h   v1.11.0\nip-10-0-1-65.us-west-1.compute.internal    Ready   node     25m   v1.11.0", "stdout_lines": ["ip-10-0-1-232.us-west-1.compute.internal   Ready   node     10h   v1.11.0", "ip-10-0-1-65.us-west-1.compute.internal    Ready   node     25m   v1.11.0"]}

TASK [Checking the no.of nodes] ************************************************
task path: /common/utils/check_no_of_nodes.yml:22
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:103
included: /common/utils/status_app_pod.yml for <IP_ADDRESS>

TASK [Checking Percona post chaos pod is in running state] *********************
task path: /common/utils/status_app_pod.yml:2
FAILED - RETRYING: Checking Percona post chaos pod is in running state (30 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (29 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (28 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (27 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (26 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (25 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (24 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (23 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (22 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (21 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (20 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (19 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (18 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (17 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (16 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (15 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (14 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (13 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (12 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (11 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (10 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (9 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (8 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (7 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (6 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (5 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (4 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (3 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (2 retries left).
FAILED - RETRYING: Checking Percona post chaos pod is in running state (1 retries left).
fatal: [<IP_ADDRESS>]: FAILED! => {"attempts": 30, "changed": true, "cmd": "kubectl get pods -n app-percona-ns -o jsonpath='{.items[?(@.metadata.labels.name==\"percona\")].status.phase}'", "delta": "0:00:00.350688", "end": "2018-12-08 18:40:03.404411", "rc": 0, "start": "2018-12-08 18:40:03.053723", "stderr": "", "stderr_lines": [], "stdout": "Pending", "stdout_lines": ["Pending"]}

TASK [set_fact] ****************************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:139
ok: [<IP_ADDRESS>] => {"ansible_facts": {"flag": "Fail"}, "changed": false}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:143
included: /common/utils/update_litmus_result_resource.yml for <IP_ADDRESS>

TASK [Generate the litmus result CR to reflect SOT (Start of Test)] ************
task path: /common/utils/update_litmus_result_resource.yml:3
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Analyze the cr yaml] *****************************************************
task path: /common/utils/update_litmus_result_resource.yml:14
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Apply the litmus result CR] **********************************************
task path: /common/utils/update_litmus_result_resource.yml:17
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Generate the litmus result CR to reflect EOT (End of Test)] **************
task path: /common/utils/update_litmus_result_resource.yml:27
changed: [<IP_ADDRESS>] => {"changed": true, "checksum": "d168e1bba34a32789adf3b7ea22bad77e0b426db", "dest": "./litmus-result.yaml", "gid": 0, "group": "root", "md5sum": "c2e52ecf7226fff51117c3d6b9ff9ad7", "mode": "0644", "owner": "root", "size": 448, "src": "/root/.ansible/tmp/ansible-tmp-1544294403.68-257087846009718/source", "state": "file", "uid": 0}

TASK [Analyze the cr yaml] *****************************************************
task path: /common/utils/update_litmus_result_resource.yml:38
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "cat litmus-result.yaml", "delta": "0:00:00.282641", "end": "2018-12-08 18:40:04.825658", "rc": 0, "start": "2018-12-08 18:40:04.543017", "stderr": "", "stderr_lines": [], "stdout": "---\napiVersion: litmus.io/v1alpha1\nkind: LitmusResult\nmetadata:\n\n  # name of the litmus testcase\n  name: node-replacement \nspec:\n\n  # holds information on the testcase\n  testMetadata:\n    app: percona \n    chaostype: node-shutdown-up-diff-name \n\n  # holds the state of testcase,  manually updated by json merge patch\n  # result is the useful value today, but anticipate phase use in future \n  testStatus: \n    phase: completed  \n    result: Fail ", "stdout_lines": ["---", "apiVersion: litmus.io/v1alpha1", "kind: LitmusResult", "metadata:", "", "  # name of the litmus testcase", "  name: node-replacement ", "spec:", "", "  # holds information on the testcase", "  testMetadata:", "    app: percona ", "    chaostype: node-shutdown-up-diff-name ", "", "  # holds the state of testcase,  manually updated by json merge patch", "  # result is the useful value today, but anticipate phase use in future ", "  testStatus: ", "    phase: completed  ", "    result: Fail "]}

TASK [Apply the litmus result CR] **********************************************
task path: /common/utils/update_litmus_result_resource.yml:41
changed: [<IP_ADDRESS>] => {"changed": true, "cmd": "kubectl apply -f litmus-result.yaml", "delta": "0:00:00.420960", "end": "2018-12-08 18:40:05.382500", "failed_when_result": false, "rc": 0, "start": "2018-12-08 18:40:04.961540", "stderr": "", "stderr_lines": [], "stdout": "litmusresult.litmus.io/node-replacement configured", "stdout_lines": ["litmusresult.litmus.io/node-replacement configured"]}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:149
included: /common/utils/check_no_of_nodes.yml for <IP_ADDRESS>

TASK [Waiting for application pod reschedule (evict)] **************************
task path: /common/utils/check_no_of_nodes.yml:4
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Checking the status of chaos injected node] ******************************
task path: /common/utils/check_no_of_nodes.yml:8
skipping: [<IP_ADDRESS>] => {"changed": false, "skip_reason": "Conditional result was False"}

TASK [Checking the no.of nodes] ************************************************
task path: /common/utils/check_no_of_nodes.yml:22
changed: [<IP_ADDRESS>] => {"attempts": 1, "changed": true, "cmd": "kubectl get nodes --no-headers | grep -vi 'master' | grep -i 'Ready'", "delta": "0:00:00.353358", "end": "2018-12-08 18:40:06.006999", "rc": 0, "start": "2018-12-08 18:40:05.653641", "stderr": "", "stderr_lines": [], "stdout": "ip-10-0-1-232.us-west-1.compute.internal   Ready   node     10h   v1.11.0\nip-10-0-1-33.us-west-1.compute.internal    Ready   node     3m    v1.11.0\nip-10-0-1-65.us-west-1.compute.internal    Ready   node     30m   v1.11.0", "stdout_lines": ["ip-10-0-1-232.us-west-1.compute.internal   Ready   node     10h   v1.11.0", "ip-10-0-1-33.us-west-1.compute.internal    Ready   node     3m    v1.11.0", "ip-10-0-1-65.us-west-1.compute.internal    Ready   node     30m   v1.11.0"]}

TASK [include_tasks] ***********************************************************
task path: /percona/chaos/app_node_failure_ups_diff_name/test.yml:153
included: /common/utils/check_cstor_pool_pod.yml for <IP_ADDRESS>

TASK [Get the cstor pool pods which remains in a pending state] ****************
task path: /common/utils/check_cstor_pool_pod.yml:2
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": true, "cmd": "kubectl get po -n openebs -l app=cstor-pool -o jsonpath='{.items[?(@.status.phase==\"Pending\")].metadata.name}' | wc -l", "delta": "0:00:00.355772", "end": "2018-12-08 18:40:06.575589", "failed_when_result": true, "rc": 0, "start": "2018-12-08 18:40:06.219817", "stderr": "", "stderr_lines": [], "stdout": "0", "stdout_lines": ["0"]}
	to retry, use: --limit @/percona/chaos/app_node_failure_ups_diff_name/test.retry

PLAY RECAP *********************************************************************
<IP_ADDRESS>                  : ok=34   changed=18   unreachable=0    failed=2

Good one @mittachaitu ! !


#2761 Exception: ERROR java.nio.file.NoSuchFileException: /tmp/testng…

…XmlPathInJar
Fixes #2761
Did you remember to?

[ ] Add test case(s)
[ ] Update CHANGES.txt
[ ] Auto applied styling via ./gradlew autostyleApply

We encourage pull requests that:

Add new features to TestNG (or)
Fix bugs in TestNG

If your pull request involves fixing SonarQube issues then we would suggest that you please discuss this with the
TestNG-dev before you spend time working on it.
Note: For more information on contribution guidelines  please make sure you refer our Contributing section for detailed set of steps.

Please, could you add a non regression test for issue?

How to add a regression test for this?


Return promise for each async action

Use case:
calling play return nothing so in order to know when the media is actually playing, we have to add an event listener just before calling play and remove it in the callback itself. Same thing for a lot of action like pause, muted, ...
example
const onPlaying = () => {
    mediaEl.removeEventListener('playing', onPlaying)

    // state dependent actions
}

mediaEl.addEventListener('playing', onPlaying)
mediaEl.play()

This is quite ugly and old school. Would be very nice to be able to
try {
    await mediaEl.play()
} catch (e) {
    // handle playing error
}
// state dependent actions

I think this could be quite easy to achieve as a lot of action already use Promises, the function calls and switch case in it just does not return the Promise.
Plus this will mimic the actual media API browser vendor are going to. Chrome already advice to use the Promise returned by play()

In build/mediaelement.js, add on line 884 this:
return response;

and then, in the else code following that line, add a return so you will have the return t.mediaElement.renderer[methodName](args); for the else statement. See if that does the trick for you and then I'll push the code to the repo. Thanks

Thank you for the hint, I will try ;)

I think I missed something else. Try also the code above for assignMethod:
assignMethods = function assignMethods(methodName) {
		t.mediaElement[methodName] = function () {
			for (var _len = arguments.length, args = Array(_len), _key = 0; _key < _len; _key++) {
				args[_key] = arguments[_key];
			}

			if (t.mediaElement.renderer !== undefined && t.mediaElement.renderer !== null && typeof t.mediaElement.renderer[methodName] === 'function') {
				if (t.mediaElement.promises.length) {
				        Promise.all(t.mediaElement.promises).then(function () {
						return triggerAction(methodName, args);
					}).catch(function (e) {
						t.mediaElement.generateError(e, mediaFiles);
					});
				} else {
					return triggerAction(methodName, args);
				}
			}
			return null;
		};

Note the return on triggerAction method. I think I missed that

I tried, I encounter some issues:

Youtube return a object which is not a promise (the player?)
Dailymotion return nothing
When the player is not ready, you are pushing action to a stack which return nothing. If each action is a Promise, maybe the stack should start with a Promise.resolve and chaining all actions with .then instead of a simple array push.

I know this is quite a change, not as easy to do, but I think it would worth the effort for the health of the exposed API.

Yeah that may require more work than I can handle right now. If you wanna submit a PR I'd be happy to review it

Same for me, I was working on a poc, but real life come up sooner than expected :(


HOTFIX-WrongBankPath : Use FMOD bank path instead of hard drive bank …

We were unable to retrieve a bank in driver as we used hard drive path to manages them.
Using FMOD bank path in Map solve this. Enabling us to unload bank as an example.

I don't agree, we have to use the hard drive path in the map. Users should use the same string for loading and unloading.
Also loadBank(path, flag) start with:
if (banks.has(pathToBank)) return pathToBank; // bank is already loaded
If we store the fmod path it won't work

Sounds good to me, I code that.

Solved by #32


[WFCORE-3500] Upgrade javax.json from 1.0.4 to 1.1.2.

https://issues.jboss.org/browse/WFCORE-3500
Java EE 8 requires javax.json:javax.json-api upgrade to 1.1. This was already done in WildFly https://github.com/wildfly/wildfly/pull/10872. This just upgrades core to the new version as before we move to full Java EE 8 compatibility this will be required. There should not be backwards compatibility issues and this will allow core to be tested with the newer version.
There is also a possible issue where the wrong version of the temporary org.wildfly.javax.json module could be overridden in Galleon from the version in full.

@jmesnil I wasn't going to fully remove the 1.0.4 reference until we are fully Java EE 8 compliant. So for WildFly full we still need the 1.0.4 version. We could change the version in the client, but I don't think it's required.


Sagiri search results are different from SauceNAO

Please describe the problem you are having in as much detail as possible:
Sometimes, when I searched for an image, the Sagiri search results were different from when I searched for the same image on SauceNAO website. It usually failed to get the first results. Here's an example:

Include a reproducible code sample here, if possible:
const sauceNAO = sagiri(process.env.SAUCENAO_TOKEN);
const results = await sauceNAO(url, { results: 8, db: 999 });
console.log(results);

Further details:

version: 3.1.1
Node.js version: 14.17.0
Operating system: Zorin OS
Priority this issue should have – please be realistic and elaborate if possible:

[ ] I have also tested the issue on latest master, commit hash:

Just a note, I'm no longer maintaining code for this so please do send a patch instead that fixes the issue.


Merge config files to nanomq.conf

Related to https://github.com/nanomq/NanoNNG/pull/266

fix  https://github.com/emqx/nanomq/issues/820


REST API agents/Y/kill fails

Empire Version
2.0
OS Information (Linux flavor, Python version)
kali linux
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
curl --insecure -i -H "Content-Type: application/json" https://localhost:1337/api/agents/qsdfqsdfqsdf/kill?token=qsdfqsdfqsdf

"NameError("global name 'sessionID' is not defined",)"

Screenshot of error, embedded text output, or Pastebin link to the error
"NameError("global name 'sessionID' is not defined",)"
Any additional information
Commenting line 1036 fixes the issue

you can confirm that was a active agent right @ElysiumSecurity ?

Yes @killswitch-GUI

emprie is not run dll and nothing shell!

Fixed


add rtx3060 result

Added my pc result.
10th i5 rtx3060-12gb

Thanks for the interest, but in general this repository won't be accepting non-bugfix PRs.


Passing 'cycle1' as the scope name breaks isolate

From @Keyamoon on January 15, 2016 22:22
This is just a silly bug that I spotted when reading the code. Can be easily fixed by prefixing all scope names passed to isolate to prevent conflicts with auto generated names. Here's a test case.
Copied from original issue: cyclejs/isolate#5

This is now fixed in @cycle/dom v21 :tada:


Add data harbor_group

Is your feature request related to a problem? Please describe.
When using OIDC login, OIDC groups are created on the fly when users login. I would like to read group without importing it as I don't directly manage it.
Describe the solution you'd like
I would prefer to use data harbor_group instead of a resource block.
Describe alternatives you've considered
Use resource block

hi @guyguy333
does something like will handle your case ?
#387

Hi @flbla, yes it looks perfect :) Thank you !

Hi @flbla, yes it looks perfect :) Thank you !

Great, I merged it, it will be available with version 3.10.4 (build in progress) :)


Minor adjustment to angle translation

Makes the conversion of angle from wire format to millidegree imho more readable.

Sorry, got mixed up in my own branch mess

Woops, forget to indicate both comments. The same comment on line 478 in get_scan_direct() could be removed. Then I'll get this merged!

I went ahead and removed the extra comment and merged. Thanks MikeGitb

Thanks


Is there any way to set the background image on MediaElement control?

There isn't an exposed property and we'd like to replace the blank black background

All future MediaElement work will take place at https://github.com/xamarin/XamarinCommunityToolkit


Gather models and data for the June 2021 release

Description
As a developer, I want to release the following data in June 2021 taken metadata and data are received on time.
Acceptance criteria

[ ] all tickets in the Epic are done

Release was done, closing epic.


Can't make it work

After adding library to my project it displays error
addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component's `render` method, or you have multiple copies of React loaded

Please provide code and errors from chrome console

No code .

My project is working just fine.
I run yarn add react-native-video-processing. no react-native link
then I run react-native run-ios
after app load error on console is

Also if I remove react-native-video-processing from package.json and run yarn
error disappears

Thanks for reporting this issue.
Seems like in your project you have 2 react versions, we need to remove react from react-native-video-processing package.json or move it to peer dependency. This should fix your issue

I see there is react in react-native-video-processing package.json.
I will try removing it.

@shahen94 sorry
I tried removing node_modules/react-native-video-processing /node_modules folder. But no luck.
there is no react in package.json of react-native-video-processing
same error

@matart15 Did you stop and rerun the package ?

Yes i eve tried rm -rf $TMPDIR/react-* && watchman watch-del-all && rm -rf ios/build/ModuleCache/* && rm -rf node_modules/ && yarn cache clean && yarn

@shahen94
ok I figured it out. in podfile i had this.
  pod 'React', path: '../node_modules/react-native', :subspecs => [
      'Core',
      'RCTActionSheet',
      'RCTGeolocation',
      'RCTImage',
      'RCTLinkingIOS',
      'RCTNetwork',
      'RCTSettings',
      'RCTText',
      'RCTVibration',
      'RCTWebSocket'
  ]

react-native-maps instruction required it.
But it works if i comment out these lines.
I wonder how other dependencies like react-native-video and react-native-camera were working with 2 react installed.

Closing the issue

I'm having the same exact issue, but I'm not using cocoapods, so @matart15's fix doesn't apply. I also attempted to remove react from the react-native-video-processing package.json and I'm still getting the same error.
My app is building without errors and it's not until I open the camera library that this error comes up. If I remove react-native-video-processing, the error doesn't show up.
Any ideas @shahen94?

@shahen94 Nevermind, the problem was React in the dependencies in package.json. I moved it to peerDependencies in my fork and created a PR for you: #81


Encryption failure when using HTTPS for webperms or web configs

This issue is caused by mono not trusting any certificates by default. However, since only the owner of a server is able to set the URL for permissions and configs it should never be a security issue. I actually got it working on a local copy of rocket: https://pastebin.com/u84Vy7Je that's the only class I changed.

That will disable certificate checking completely. You might also just add the root ca to the trusted ca's of the os.


Update display of supported browsers for CSS properties on-hover.

I wanted to try messing around with extension development, but more importantly I wanted it clear what the browsers list is supposed to mean.
Old style: '(Chrome 31, Firefox 27, IE 11, Edge)'
New style: 'Browser Support: Chrome 31, Firefox 27, IE 11, Edge'
Before:

After:

For me I think it's actually too much noise. For all properties that's standard and implemented across all browsers we should just hide the browser support part.

IMO its pretty clear what the browser list means. I'd rather not make a change.

That’s fine by me 👍 you can close this PR then :)


[cleanup] Remove dead vine.co extractor

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

Removes vine.co extractors as http error 404 will be returned from the api when using the test urls.
Fixes # N/A
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)
[x] Other -  Cleanup

can we remove the Vine tests from the twitter extractor too please


Int#divisible_by? doesn't care about the value being floored.

The if statement in % might be optimized away by LLVM, but why
force an optimization if the code isn't harder to understand when doing the optimized thing?

Thank you @yxhuvud :)


enable summary_plot to return the figure if show=False

I was trying to access the underlying pyplot figure so that I could export it to a .png. This solved my problem. Is there an even easier way?

I was just thinking about the same thing.
https://github.com/slundberg/shap/issues/197

Hmm...is just calling pl.savefig(filename) right after calling with show=False not working for you? You should (I think) be able to just call pl.gcf() right after the plot call if show=False was passed.

At the moment I'm getting bizarre behavior regardless of which version I use - I have not been able to get your method to work, but may follow up later. Regardless, one argument in favor of passing back the figure explicitly is that the recipient need not have imported pl to access and use it.

I think I buy that. However I apologize that a recent refactor means that the update now needs to go in plots/summary.py. I am happy to copy it over there it if you prefer, but if you copy it over then github will correctly record you as the author.

Thanks for checking in, but I'm going to pass this back to you as I don't think the solution I proposed is ultimately satisfactory. In the context of a notebook, I'm observing that the plot gets displayed regardless of whether show = True or False. Specifically, deleting every pl.show() command seems to have no effect in a notebook. (It works as expected, on the other hand, in a regular non-interactive script). I'm wondering if it's necessary to define a fig variable at the outset of creating the plot rather than picking it up at the last minute (as pl.gcf()) to really get full control.

Okay. If you end up with a solution let us know :)


Make random delay before performing sntp request configurable via sdkconfig (IDFGH-13513)

Is your feature request related to a problem?
We are developping a very energy-sensitiv product (based on esp32s3 / idf 5.2.1), that is battery powered and therefore relays on little power consumption as possible. A hugh proprotion of battery life time goes by the regularly performed send attempts via wifi, otherwise the system is in deep sleep. Nice we are communicating via https we need a correct time on the device for authentification of the certificate. So we perform a sntp request each time we do a send attempt. Apparently there is a default random delay implemented (0s - 5s) before a sntp request is triggered.
Describe the solution you'd like.
sntp implementation checks for a macro called SNTP_STARTUP_DELAY if a random delay is applied or not. Unfortunately this macro is hardcoded. This marco is checked in nstp_opts.h from lwip library:
#if !defined SNTP_STARTUP_DELAY || defined __DOXYGEN__
#ifdef LWIP_RAND
#define SNTP_STARTUP_DELAY          1
#else
 #define SNTP_STARTUP_DELAY          0
 #endif
#endif

sntp_init(void)
{
 ...
#if SNTP_STARTUP_DELAY
        sys_timeout((u32_t)SNTP_STARTUP_DELAY_FUNC, sntp_request, NULL);
#else
        sntp_request(NULL);
#endif
...
}

the feature that is requested here is to include this option (SNTP_STARTUP_DELAY) to sdkconfig, so it can be set via menuconfig.
Describe alternatives you've considered.
To get rid of the random delay before sntp request, we add this definiton via cmake file. But in general we do not want to manipulate idf implementations from "outside"
add_compile_definitions(SNTP_STARTUP_DELAY=0)
Additional context.
No response

Hi @EngineerOfMaster
It's already possible to configure:

CONFIG_LWIP_SNTP_STARTUP_DELAY
CONFIG_LWIP_SNTP_MAXIMUM_STARTUP_DELAY

But only available from v5.3, is it okay for you to switch to it (already latest stable)?

Thank you for your fast response.
I wasn`t aware of this. This is fine, at some point we will go forward with the new idf version.


run on baremetal Raspberry Pi?

I found this C++ lib: https://github.com/rsta2/circle
But I don't know C, wondering if someone else is trying to get it working via that route?

hi tom.
building for arm would require also building the v8 lib for arm, which i don't know much about and would have to do some research on. i have some raspberry pi's lying around that i can experiment with if i ever get time to look into this, but should be able to cross-compile on non-arm too. happy for other folks to try too and i'll help any way i can.
i don't think you will need anything like that library. most of the just-js code should work just same on ARM barring maybe the http module which uses x86 specific instructions for the parsing. so the key task here would be figuring out how to build v8lib for arm - i don't think it should be too difficult for anyone that has built v8 or chromium on arm before.
https://github.com/just-js/libv8

hi tom.
building for arm would require also building the v8 lib for arm, which i don't know much about and would have to do some research on. i have some raspberry pi's lying around that i can experiment with if i ever get time to look into this, but should be able to cross-compile on non-arm too. happy for other folks to try too and i'll help any way i can.
i don't think you will need anything like that library. most of the just-js code should work just same on ARM barring maybe the http module which uses x86 specific instructions for the parsing. so the key task here would be figuring out how to build v8lib for arm - i don't think it should be too difficult for anyone that has built v8 or chromium on arm before.
https://github.com/just-js/libv8

hi tom.
building for arm would require also building the v8 lib for arm, which i don't know much about and would have to do some research on. i have some raspberry pi's lying around that i can experiment with if i ever get time to look into this, but should be able to cross-compile on non-arm too. happy for other folks to try too and i'll help any way i can.
i don't think you will need anything like that library. most of the just-js code should work just same on ARM barring maybe the http module which uses x86 specific instructions for the parsing. so the key task here would be figuring out how to build v8lib for arm - i don't think it should be too difficult for anyone that has built v8 or chromium on arm before.
https://github.com/just-js/libv8


Improving the button for dark and light mode.

Describe the feature
I would like to change the button appearance for switching for light and dark mode and make it more UI friendly.
Add ScreenShots

I have highlighted the button with red color which I want to change.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@Its-Aman-Yadav I would like to resolve this. Please assign this to me.


Flutter gist: Error: No 'main' method found.

Unable to link to flutter gist, I get:
gist:
https://gist.github.com/JCzz/f9e2ae58b0e987317a66875e95b75fc3
link to dartpad:
https://dartpad.dev/f9e2ae58b0e987317a66875e95b75fc3
Alsop tried adding /flutter/:
https://dartpad.dev/flutter/f9e2ae58b0e987317a66875e95b75fc3
Error compiling to JavaScript:
Error: No 'main' method found.
Error: Compilation failed.

You should have main.dart file in your gist.

DartPad looks for three files in each gist:
main.dart
index.html (optional)
styles.css (optional)

https://github.com/dart-lang/dart-pad/wiki/Sharing-Guide

+1 to what @eladcandroid said. DartPad expects the Dart code you'd like loaded into the editor to be in a file called main.dart. If you rename the file in your gist to have that name, it should work just fine.


Incorrect vite warning regarding nesting tr directly in table element

Vue version
3.5.10
Link to minimal reproduction
https://play.vuejs.org/#eNp9kDELwjAQhf9KuVnqoJMUQcVBBxV1zFLrWatpEpKLFqT/3SSlrYN0CS/vexfe5QMLpeKXRZhBQlgqnhLOmYiihNILb6S/6Hkydkcg4xY51Y/ACMhkUtyKPH4YKdyLHx9nkMlSFRz1XlEhhWEwiwLxLOVcvrfBI21x1PrZHbPnH/9hKu8xOGg0qF/IoGOU6hypwevTDiunO1jKq+UuPQCPaCS3vmMTW1pxdbV/cqHtplRSUyHys1lXhMK0S/miPlmHPAP3rauB1fu6k3ga5pioof4CfnKCSA==
Steps to reproduce
Create a SFC with this content.
<template>

</template>

Vite will issue a warning:

warning:
 cannot be child of
, according to HTML specifications. This can cause hydration errors or potentially disrupt future functionality.

This warning is factually incorrect.  The relevant spec says that a
 may contain:

In this order: optionally a caption element, followed by zero or more colgroup elements, followed optionally by a thead element, followed by either zero or more tbody elements or one or more tr elements, followed optionally by a tfoot element, optionally intermixed with one or more script-supporting elements.

This is because htmlNesting.ts does not list tr as a valid child of table, despite the spec allowing it.
What is expected?
I expect no warning to be produced.
What is actually happening?
A warning is produced from vite:

warning:
 cannot be child of
, according to HTML specifications. This can cause hydration errors or potentially disrupt future functionality.

System Info
+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>

const table = document.createElement('table');
table.innerHTML = '

';
console.log(table.innerHTML);

Maybe we should modify the warning message.

I’d suggest making the check more flexible, as it’s not very comprehensive at the moment.

const table = document.createElement('table');
table.innerHTML = '

';
console.log(table.innerHTML);

I don't think this is showing what you think it is showing.
This is a serialized DOM.  In HTML,
 is explicitly optional, by specification, as I've cited above.

I don't think this is showing what you think it is showing.我不认为这显示了你认为它所显示的内容。
This is a serialized DOM. In HTML,
 is explicitly optional, by specification, as I've cited above.这是一个序列化的 DOM。在 HTML 中，
根据规范是明确可选的，正如我上面引用的那样。

The directly generated

 during SSR becomes

 during CSR, as mentioned in the warning, resulting in hydration mismatch. This is what I want it to showing.

At a minimum the warning shouldn't claim that this is due to a spec.  It seems this is constraint introduced by the implementation details of hydration.  It could say something like this.

Despite being valid HTML, Vue SSR does not support direct nesting of
 within a
.  Doing this can cause discrepancies during hydration.

Personally, I'm not using SSR at all, so then I would know it's perfectly safe to ignore this warning.

Yes, the warning should be corrected. Perhaps we can try adding some transformations to similar behaviors so that
 can be automatically generated.

I see the same thing. Fix the warning or provide a work around?

I'm seeing my stdout absolutely brim-filled with this warning and its accompanying template print out in both dev and build environments, to a point that it swallows and obscures any legitimate warnings.
I do not use SSR so I'm not impacted by the discrepancy between the hydration feature implementation and the html specification.
Could this warning be predicated by SSR actually being used? Or could we disable this warning in any way? (except writing a custom vite logger to filter it out)
If not I think this warning should be removed. Can't really expect everyone to change all table based components to an optional html syntax or lose functionality of the console.
I see that this issue is labeled as an edge-case, my vote is that it is not.

Can there be some additional smarts going on, such that this warning only displays if there is a mismatch detected between SSR and CSR?
Alternatively, Vue should not be adding  nodes because the browser is fine with no such node being present. Perhaps that's the real problem, that Vue should not be doing this at all?

Update... I just spent the time to modify source to always use either thead or tbody or both. I had maybe a dozen cases in which I was not using the optional node. So now I guess I'm on team tbody. Moooving on.

Can't really expect everyone to change all table based components to an optional html syntax or lose functionality of the console.
i agree with @aelgn - i dont think this is an edge case and, since this is optional html syntax, it makes it harder to debug actual errors

 and/or  did fix the error bug which showed up when running: npm run dev. I just did an update and its still there:
 ──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
Technically that same spec says this too:

For historical reasons, certain elements have extra restrictions beyond even the restrictions given by their content model.
A table element must not contain tr elements, even though these elements are technically allowed inside table elements according to the content models described in this specification. (If a tr element is put inside a table in the markup, it will in fact imply a tbody start tag before it.)

https://html.spec.whatwg.org/multipage/syntax.html#element-restrictions

Technically, that same spec says this too:

For historical reasons, certain elements have extra restrictions beyond even the restrictions given by their content model.
A table element must not contain tr elements, even though these elements are technically allowed inside table elements according to the content models described in this specification. (If a tr element is put inside a table in the markup, it will in fact imply a tbody start tag before it.)

https://html.spec.whatwg.org/multipage/syntax.html#element-restrictions

That quote is regarding the document object, not the markup.  The parenthesized part explicitly explains the relationship between the markup and the document object.
If you don't believe me, you can use the WHATWG's own validator service, which shows no errors or warnings for direct nesting of
 in
.

Also, even if someone is not using SSR, they shouldn't be writing invalid HTML.

Agreed.  But this isn't invalid.  I've quoted the relevant spec.

Svelte also throws similar error:

True.  But at least the error message doesn't claim that it's because it's invalid, just that it breaks Svelte's assumptions.


Change to use TypeData for rawbody (to allow for undefined)

Fixes an issue with the rawBody support for GET cases where it should be undefined (based on previous v1 behavior)

@christopheranderson,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


QR Code is not working

I can't use QR code in playground

QR code in nativescript playground page is not working

What happen to the NativeScript Playground?  The QR code is failed and the browser keep have the following error:
https://ps6.pndsn.com/v2/presence/sub-key/sub-c-2d2f1312-4f78-11e7-ab90-02ee2ddab7fe/channel/b-ch-HJLAid8ww%2Cm-ch-HJLAid8ww-pnpres/heartbeat?state={}&heartbeat=300&uuid=pn-ed83de4b-fac3-4dcb-a6b0-d649a49e1e8c&pnsdk=PubNub-JS-Web%2F4.21.2
net::ERR_CONNECTION_RESET

I'm not sure, but I'm experiencing the same, as far as I can tell. I'm just started no NativeScript.
So, the first app I've created launch QR code and made no changes at all, I open Playground app, open camera, shot the screen, it beeps and that's all. No response on my phone, neither on playground web site (neither on my local console when I try it). The app just holds on the same QR screen and that's all.

QR code scan isn't working on my iPhone 12, iOS 14, either.  No error codes or anything.   Curious if there is a resolution.  Would love to transition to native script.


Update OWASP Top Ten link

It used to point to an outdated list (2013). Now it points to the general OWASP Top Ten Project.

There is also docs/ref/class-based-views/mixins-single-object.txt:        .. _insecure direct object reference: https://www.owasp.org/index.php/Top_10_2013-A4-Insecure_Direct_Object_References.

I've updated the top ten link to point to the web version of the 2017 top ten list.
The insecure direct object reference item has been merged into the broken access control item:
(from the PDF)
Merged or retired, but not forgotten:
• A4-Insecure Direct Object References and A7-Missing Function Level Access Control merged into A5:2017-Broken Access
Control.


new Intent() must have a action and a type - cannot be null

Likewise action and type are readonly.

Must raise a TypeError


Enable large part writing

On .NET Core and .NET 5+, there is an issue that prevents largs parts from being written to a package. This is due to the underlying ZipArchive buffering everything in memory when updating an archive entry. Because of the way that we use the archive, the only way around that is to load the package in a write-only mode. With the recent addition of being able to reload a package, we can work around this behavior by redirecting streams and then writing them to a write-only package after everything else has been written.
Fixes #807

This will need some more work. Closing for now