Indefinite kernel hang on ROCm 1.9.211 for MXNet HIP Port on VEGA10

Issue:
Indefinite kernel hang issue is observed on executing the mxnet training application on VEGA10 gpu.
Environment info:

Operating System: Ubunut 16.04

ROCm version:
$ dpkg -s rocm-dkms
Package: rocm-dkms
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 1
Maintainer: Advanced Micro Devices Inc.
Architecture: amd64
Version: 1.9.211
Depends: rocm-dev, rock-dkms
Description: Radeon Open Compute (ROCm) Runtime software stack
Homepage: https://github.com/RadeonOpenCompute/ROCm

HIP environment details:
$ hipconfig --full
HIP version  : 1.5.18353
== hipconfig
HIP_PATH     : /opt/rocm
HIP_PLATFORM : hcc
CPP_CONFIG   :  -D__HIP_PLATFORM_HCC__=   -I/opt/rocm/include -I/opt/rocm/hcc/include
== hcc
HSA_PATH     : /opt/rocm/hsa
HCC_HOME     : /opt/rocm/hcc
HCC clang version 7.0.0 (ssh://gerritgit/compute/ec/hcc-tot/clang                                                                  e2b51bfd063e4ccd426b64290bdc1587f2bf855a) (ssh://gerritgit/compute/ec/hcc-tot/llvm   009cb63e6e67f60303e7b11642113db848619871) (based on HCC 1.2.18354-ec91fed-e2b51bf-009cb63 )
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /opt/rocm/hcc/bin
LLVM (http://llvm.org/):
LLVM version 7.0.0svn
Optimized build.
Default target: x86_64-unknown-linux-gnu
Host CPU: broadwell
Registered Targets:
amdgcn - AMD GCN GPUs
r600   - AMD GPUs HD2XXX-HD6XXX
x86    - 32-bit X86: Pentium-Pro and above
x86-64 - 64-bit X86: EM64T and AMD64
HCC-cxxflags :  -hc -std=c++amp -I/opt/rocm/hcc/include -I/opt/rocm/includeHCC-ldflags  :  -hc   -std=c++amp -L/opt/rocm/hcc/lib -Wl,--rpath=/opt/rocm/hcc/lib -ldl -lm -lpthread -lhc_am -Wl,--whole-archive -lmcwamp -Wl,--no-whole-archive

Analysis
On executing the application on GPU it hangs at the kernel,
<<hip-api tid:1.115 1.115 hipLaunchKernel 'ZN5mxnet2op8mxnet_op20mxnet_generic_kernelINS1_11op_with_reqINS1_10set_to_intILi0EEELi1EEEJPfEEEviDpT0' gridDim:{1024,1,1} groupDim:{256,1,1} sharedMem:+0 stream:0.1 @791653796943586
We have tried to execute the application by exporting HSA_ENABLE_SDMA=0 but the issue still persists.
Steps to Reproduce

$ git clone --recursive -b downstream_27Mar2018 --single-branch https://github.com/ROCmSoftwarePlatform/mxnet.git
$ cd mxnet
$ export HIP_PLATFORM=hcc
$ make -jn (n = no of cores)
$ cd python
$ sudo python setup.py install
$ cd ../example/adversary
$ python adversary_generation.py
NOTE: to run on cpu modify code as mx.cpu() and to run on gpu modify code as mx.gpu().

Please suggest to identify the cause which might lead to indefinite hang of the kernel.

@sriharikarnam, apologies for the lack of response.  Do you still see the issue in a more recent ROCm version?  Thanks.

Closing the ticket as it is stale.  @sriharikarnam, please re-open if you still need assistance with this issue.  Thanks.


Cannot select new object with constructor

Hi,
Love your framework! Just a small inconvenience here...
var query = _client.Queryable<ConsonantModel, ConsonantTransliterationModel, TransliterationModel>
(
    (c, ct, t) => new JoinQueryInfos
    (
        JoinType.Inner, c.ConsonantId == ct.ConsonantId,
        JoinType.Inner, ct.TransliterationId == t.TransliterationId
    )
);

// OK, not using constructor
var r1 = query.Select((c, ct, t) => new ConsonantAggregate() { Consonant = c, Transliteration = t }).ToList();

// Not OK! Throws NullReferenceException!
var r2 = query.Select((c, ct, t) => new ConsonantAggregate(c, t)).ToList();

return r1;

Would be great to be able to use constructor parameters with Select() to populate an aggregate like this :)
public class ConsonantAggregate
{
    public ConsonantAggregate()
    {
    }

    public ConsonantAggregate(ConsonantModel consonant, TransliterationModel transliteration)
    {
        Consonant = consonant;
        Transliteration = transliteration;
    }

    public ConsonantModel Consonant { get; set; }
    public TransliterationModel Transliteration { get; set; }
}

Cheers,
Matt

Thank you for your feedback and follow-up support.


Bump to v0.4.0

:point_up:

Up to you to decide what makes a minor version vs a patch. Here I'd intuitively say we are just fixing some error parsing, thus maybe releasing it as 0.3.1?

That would have been awesome but there were some API breaking changes, specifically with the version of web3. This would cause unexpected build errors if the old 0.3.0 version was being used.


Docs: Fix 2 anchors on profile backend plugin topic

Fix broken anchors. Fixes https://github.com/grafana/plugin-tools/issues/1116

@academo @jackw - This PR is being blocked by an unsuccessful "Run commands when issues or PRs are labeled / main (pull_request)". I haven't encountered this error before and I'm not sure how to act upon the info in the detail view. Any suggestions for passing it?

@academo @jackw - This PR is being blocked by an unsuccessful "Run commands when issues or PRs are labeled / main (pull_request)". I haven't encountered this error before and I'm not sure how to act upon the info in the detail view. Any suggestions for passing it?

@josmperez I merged main into this branch to solve the issue and it's now merged. Apologies for not spotting your ping sooner.


Set HOSTING_ENV=comcom for on-premise node jobs

Change summary:

Set HOSTING_ENV=comcom for on-premise node jobs

Related issues:

https://github.com/ainblockchain/ain-blockchain/issues/1285

Thanks for the review! @jiyoung-an Now merging..


Use relative call instructions between wasm functions

This commit is a relatively major change to the way that Wasmtime
generates code for Wasm modules and how functions call each other.
Prior to this commit all function calls between functions, even if they
were defined in the same module, were done indirectly through a
register. To implement this the backend would emit an absolute 8-byte
relocation near all function calls, load that address into a register,
and then call it. While this technique is simple to implement and easy
to get right, it has two primary downsides associated with it:

Function calls are always indirect which means they are more difficult
to predict, resulting in worse performance.

Generating a relocation-per-function call requires expensive
relocation resolution at module-load time, which can be a large
contributing factor to how long it takes to load a precompiled module.

To fix these issues, while also compromising on the previously simple
implementation technique, this commit switches wasm calls within a
module to using the colocated flag enabled in Cranelift-speak, which
basically means that a relative call instruction is used with a
relocation that's resolved relative to the pc of the call instruction
itself.
When switching the colocated flag to true this commit is also then
able to move much of the relocation resolution from wasmtime_jit::link
into wasmtime_cranelift::obj during object-construction time. This
frontloads all relocation work which means that there's actually no
relocations related to function calls in the final image, solving both
of our points above.
The main gotcha in implementing this technique is that there are
hardware limitations to relative function calls which mean we can't
simply blindly use them. AArch64, for example, can only go +/- 64 MB
from the bl instruction to the target, which means that if the
function we're calling is a greater distance away then we would fail to
resolve that relocation. On x86_64 the limits are +/- 2GB which are much
larger, but theoretically still feasible to hit. Consequently the main
increase in implementation complexity is fixing this issue.
This issue is actually already present in Cranelift itself, and is
internally one of the invariants handled by the MachBuffer type. When
generating a function relative jumps between basic blocks have similar
restrictions. At this time, however, I decided to not try to reuse
MachBuffer for inter-function relocations. The main reason for this is
that MachBuffer doesn't actually handle any of the cases that
inter-function relocations need to handle, namely the 26-bit relocation
and 32-bit relocations of AArch64 and x86_64. If a 26-bit relocation
isn't resolvable because a function gets too large then MachBuffer
will simply panic. I also opted to not use MachBuffer for now, though,
because it doesn't quite have the infrastructure already set up where
when inserting an island for a smaller jump sequence the result should
be a relocation to fill in later. Today it simply promotes a 19-bit
branch on AArch64 to a 26-bit branch, assuming the 26 bits is enough.
All-in-all I felt that at this time MachBuffer wasn't reusable enough
and would need enough work that it was probably more worthwhile to do
this in wasmtime-cranelift first and looking to unify the strategies
in the future.
For these reasons the wasmtime_cranelift::obj module has grown in
complexity quite a bit. This now entirely handles relative relocations
between functions, automatically inserting "jump veneers" to resolve
calls between functions that are too far away. The general strategy is
similar to MachBuffer, but different in the final tracking of
relocations. The current assumption is that each TargetIsa has the
ability to generate a fixed "jump veneer" which internally has an 8-byte
immediate value that is added to its own address to reach the
destination of an indirect call. This relative jump, even in the veneer,
means that when veneers are used we still don't need absolute
relocations since the code is still all implemented as relative jumps.
The veneer jumps, however, are larger in code size because they don't
fit into the native versions.
I've added some simple testing of this for now. A synthetic compiler
option was create to simply add padded 0s between functions and test
cases implement various forms of calls that at least need veneers. A
test is also included for x86_64, but it is unfortunately pretty slow
because it requires generating 2GB of output. I'm hoping for now it's
not too bad, but we can disable the test if it's prohibitive and
otherwise just comment the necessary portions to be sure to run the
ignored test if these parts of the code have changed.
The final end-result of this commit is that for a large module I'm
working with the number of relocations dropped to zero, meaning that
nothing actually needs to be done to the text section when it's loaded
into memory (yay!). I haven't run final benchmarks yet but this is the
last remaining source of significant slowdown when loading modules,
after I land a number of other PRs both active and ones that I only have
locally for now.
cc #3230

Ok talked with @cfallin offline about merging all this into MachBuffer and after some fiddling I think it's going to work (got the test suite passing locally on arm64 at least). I'm gonna close this and I'll reopen with a cleaned up history, a rebase, and a new commit message.


DNS in digital twin

make sure digitaltwin uses sites.json and all dns info from there and answers for them using local prod IP addr
if dns not know forward to e.g. <IP_ADDRESS>

done
base) hamdy@myth:~$ dig @<IP_ADDRESS>  threefold.io

; <<>> DiG 9.16.6-Ubuntu <<>> @<IP_ADDRESS> threefold.io
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58964
;; flags: qr rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;threefold.io.


Markdown preview does not always refresh

VSCode Version: 1.5.3
OS Version: OS X 10.11.6

Steps to Reproduce:

Open new VSCode window
Open a project folder
Click on README.md
Both text and .md preview tabs open
Close .md text tab (preview still open)
Open another editor window (Sublime)
Open the same project folder
Open README.md, make changes and save
Click on README.md in VSCode Explorer
Text tab shows modified content
.md preview is now stale
Close preview tab so only text tab visible
Click on Open Preview icon in upper right
.md preview still shows old content
Pressing Shift-Cmd-V same thing
(Both text and preview tabs still open)
Right-click on README.md in Explorer pane and choose Open Preview
Focus changes to preview tab, but still stale
Close .md preview tab
Do step 18 again, and preview shows refreshed content
Make more changes in the other editor and save
Now it doesn't matter what I do (tried any/all steps above), .md is not refreshing
But text tab always refreshes
OK, found a pattern: the .md preview will only reliably refresh if its text tab is open AND in focus - when making external changes, the text tab auto-updates, and THEN switching to the preview tab shows updated content
If .md preview tab is in focus and external change is made, clicking back to the text tab causes a weird flicker with the focus staying on the preview tab. Click the text tab again to see updated content, but the refresh problem remains

Closing as duplicate of #5687


ENH: Allow function in Series/DataFrame get syntax

Currently, pandas makes clever use of __getitem__ to filter/mask Series and DataFrame.  At times, the current abstraction is leaky - for instance, df[18 < df['age'] < 25] would raise an exception, even though cascaded compare symbols in that manner are legal Python syntax.
It would be awesome to also be able to pass in a function to the __getitem__ function that would act as a filter.  This would allow users to use all of Python's language features for filtering while still maintaining the brevity intended for these statements.
For example:
df[lambda row: 18 < row['age'] < 25]

This would also allow lengthier filters to be defined outside of the getter square brackets:
def age_filter(row):
    return 18 < row['age'] < 25 if row['country'] == 'USA' else row['age'] > 13
df[age_filter]

Functions as viable filters would also allow for chaining of filter functions without creating multiple intermediary DataFrames or Series, making optimization of cascaded filters much easier.

this is a dupe of #2560. you can do this using query/eval, see docs here
you can do chained relationships as well.
__getitem__ is already hopelessly overloaded. I don't think this add any clarify. And it will be prone to non-vectorized evaluation, losing performance. All of the operations you show above are vectorizable


golangci-lint issues: G114: Use of net/http serve function that has no support for setting timeouts (gosec)

In the current state of this repo, any new PR will fail because of this error below in the golangci-lint job:
G114: Use of net/http serve function that has no support for setting timeouts (gosec)

Closed by https://github.com/sigstore/cosign-gatekeeper-provider/pull/23 now merged in main.


Only add a new condition to a VC's .status.conditions

What this PR does / why we need it:
In the current implementation, there can be a large number of redundant conditions with the identical Reason, Message and Status in a VC's .Status.Conditions.   A large number of duplicated conditions can cause potential performance issues. It's hard to read too.
This PR makes a change on how to add a VC's  condition to .Status.Conditions.  It checks whether a new condition exits by Reasonand Status and adds the condition only when it does not exist. if the condition already exists, it will only update the condition's lastTransitionTime.  It sets .Conditions.Status value too.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

/assign @christopherhein


CASMMON-129 Added Grafana_Dashboards_by_Component.md documentation

Added Grafana Dashboard documentation

/backport main

/backport main

I created the main branch backport for this: https://github.com/Cray-HPE/docs-csm/pull/1858
If this PR applies to csm-1.0, need a backport there.


Update Slack URL to be more user friendly.

Signed-off-by: Mike Ng<EMAIL_ADDRESS>

/approve
/lgtm


fixing broken references to cpu-constraints yaml

Hello,
This PR fixes the broken urls of the descriptors that are still pointing to k8s.io
Best regards,
Wassime.

For some reason k8s.io is not always resolving, probably a CNAME record in k8s.io ==> kubernetes.io would be better and can fix all those potential issues.

Why is this necessary? Looks to me the k8s.io domain still works?

Why is this necessary? Looks to me the k8s.io domain still works?

k8s.io was not reachable yesterday since it's not a CNAME to kubernetes.io, the redirection server(<IP_ADDRESS>) was probably unresponsive. you can close the PR.
Thanks.


Font manifest does not exist

Please bundle a default FontManifest for Flutter Web
Steps to Reproduce

open Vscode
Flutter: New Web Project
Start without Debugging
when page is loaded in Chrome, go to console

Logs
dart_sdk.js:100734 Font manifest does not exist at `assets/FontManifest.json` – ignoring

✓] Flutter (Channel master, v1.6.4-pre.27, on Mac OS X 10.14.4 18E226, locale fr-FR)
    • Flutter version 1.6.4-pre.27 at /Users/xxx/dev/flutter-test/flutter
    • Framework revision 2d9b158faf (3 days ago), 2019-05-28 11:35:03 -0700
    • Engine revision 8dc3a4cde2
    • Dart version 2.3.2 (build 2.3.2-dev.0.0 e3edfd36b2)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/xxx/Library/Android/sdk/
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /Users/xxx/Library/Android/sdk/
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.2.1, Build version 10E1001
    • CocoaPods version 1.5.3

[✓] iOS tools - develop for iOS devices
    • ios-deploy 1.9.4

[✓] Android Studio (version 3.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 29.1.1
    • Dart plugin version 181.5656
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)

[✓] IntelliJ IDEA Ultimate Edition (version 2019.1.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 29.1.3
    • Dart plugin version 182.4892.25

[✓] VS Code (version 1.34.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.0.2

[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.

Closing as duplicate of https://github.com/flutter/flutter/issues/32245


glyphs missing when system call to configure fallbacks using the user provided font

tracking issue for work that was backed out of #575

I have a provisional fix for this, where we base the fallbacks always on Menlo regardless of the user configured font.
The only issue, and maybe it isn't an issue, is when the user configures some like "Source Code Pro Light" as the normal font, the weight doesn't match in the fallback.
So if say, a Japanese character would still be the normal weight, even if the Japanese font has a light.

PR #610 was intended to remedy this, but that was before @jwilm changed the title :)

Looks like the list of fonts in .yml file is not supported still. Is this WIP? I see PR #610 was required to be changed a month ago. I'm glad to help if needed.

closing in favor of #957


Change GQ and QR to Float instead of integer when values are written in scientific format

Hello,
I was using the --gcvf format output recently and came across a problem:
As the values for both GQ and QR are really high in chunks of the genome were the coverage is high, they are written in the scientific format (1e+6 and more). However the dot is not accepted by the vcf format for an Integer type.
I found that changing the the type of both fields in the header to float resolved my problem.
Cheers and thanks for the nice software !

Sorry for the delay answering you  and thanks for your answer ! No I don't think it would cause other problem either. Sorry maybe I was not used to working with VCF a lot and I was stuck for quite a while on this problem and thought that other people might have the same problem. I just fixed it with sed and it did not seem to cause other problem. Will close this then.


Unable to install origin 3.6 on RedHat 7.4 - AWS

I have been working around in how to install origin 3.6 on Redhat and AWS.
openshift-ansible-contrib/roles/prerequisites/defaults/main.yaml
Modified to 3.6.0

Modified:  playbooks/aws-prerequisite.yaml with recent pull request.

hosts: cluster_hosts
gather_facts: yes
become: yes
serial: 1
roles:

role: aws-rhsm-subscription
when: deployment_type in ["enterprise", "atomic-enterprise", "openshift-enterprise"] and
ansible_distribution == "RedHat" and rhel_subscription_user is not defined

hosts: cluster_hosts
gather_facts: no
become: yes
roles:

role: rhsm-repos
when: deployment_type in ["enterprise", "atomic-enterprise", "openshift-enterprise"] and
ansible_distribution == "RedHat" and rhel_subscription_user is not defined
prerequisites

hosts: master
gather_facts: no
become: yes
roles:

master-prerequisites

Nice, I can start installing origin 3.6 on Redhat 7.4 but it needs more space on root disk (40GB) and the playbook only provisioned 10GB. I provisioned 50GB

name: Create Greenfield Infrastructure
cloudformation:
stack_name: "{{ stack_name }}"
state: "present"
region: "{{ region }}"
template: "roles/cloudformation-infra/files/greenfield.json"
template_parameters:
Region: "{{ region }}"
Route53HostedZone: "{{ public_hosted_zone }}."
PublicHostedZone: "{{ public_hosted_zone }}"
MasterApiPort: "{{ console_port }}"
MasterHealthTarget: "TCP:{{ console_port }}"
MasterClusterHostname: "{{ openshift_master_cluster_hostname }}"
MasterClusterPublicHostname: "{{ openshift_master_cluster_public_hostname }}"
AppWildcardDomain: "*.{{ wildcard_zone }}"
VpcCidrBlock: "{{ cidr_block }}"
VpcName: "{{ vpc_prefix }}"
SubnetCidrBlocks: "{{ subnet_blocks }}"
KeyName: "{{ keypair }}"
MasterInstanceType: "{{ master_instance_type }}"
AmiId: "{{ ami }}"
BastionInstanceType: "{{ bastion_instance_type }}"
BastionUserData: "{{ lookup('file', 'user_data_bastion.yml') | b64encode }}"
MasterRootVolSize: "50"
BastionRootVolType: gp2
MasterRootVolType: gp2
MasterDockerVolSize: "{{ docker_storage }}"
MasterDockerVolType: gp2
MasterEtcdVolSize: "{{ etcd_storage }}"
MasterEtcdVolType: gp2
MasterEmptyVolSize: "5"
MasterEmptyVolType: gp2
MasterUserData: "{{ lookup('file', 'user_data_master.yml') | b64encode }}"
InfraInstanceType: "{{ node_instance_type }}"
InfraRootVolSize: "50"
InfraRootVolType: gp2
InfraDockerVolSize: "{{ docker_storage }}"
InfraDockerVolType: gp2
NodeEmptyVolSize: "{{ emptydir_storage }}"
NodeEmptyVolType: gp2
NodeUserData: "{{ lookup('file', 'user_data_node.yml') | b64encode }}"
AppNodeInstanceType: "{{ app_instance_type }}"
NodeRootVolSize: "50"
NodeRootVolType: gp2
NodeDockerVolSize: "{{ docker_storage }}"
NodeDockerVolType: gp2
S3BucketName: "{{ s3_bucket_name }}"
S3User: "{{ s3_username }}"
tags:
KubernetesCluster: "{{ stack_name }}"
when: create_vpc == "yes"

Start installation:

CHECK [memory_availability : ose-master03.mindcurv-labs.es] ******************************************************************************
fatal: [ose-master03.mindcurv-labs.es]: FAILED! => {"changed": false, "checks": {"disk_availability": {}, "docker_image_availability": {"failed": true, "msg": "Some dependencies are required in order to check Docker image availability.\nUnable to install required packages on this host:\n    python-docker-py,\n    skopeo\nEnsure that all required dependencies can be installed via yum.\n"}, "docker_storage": {"failed": true, "msg": "Some dependencies are required in order to query docker storage on host:\nUnable to install required packages on this host:\n    python-docker-py\nEnsure that all required dependencies can be installed via yum.\n"}, "memory_availability": {}, "package_availability": {"skipped": true, "skipped_reason": "Not active for this host"}, "package_version": {"skipped": true, "skipped_reason": "Not active for this host"}}, "failed": true, "msg": "One or more checks failed", "playbook_context": "install"}

Host:     ose-master03.mindcurv-labs.es
Play:     Verify Requirements
Task:     openshift_health_check
Message:  One or more checks failed
Details:  check "docker_image_availability":
Some dependencies are required in order to check Docker image availability.
Unable to install required packages on this host:
python-docker-py,
skopeo
Ensure that all required dependencies can be installed via yum.
       check "docker_storage":
       Some dependencies are required in order to query docker storage on host:
       Unable to install required packages on this host:
           python-docker-py
       Ensure that all required dependencies can be installed via `yum`.

The execution of "playbooks/openshift-install.yaml"
includes checks designed to fail early if the requirements
of the playbook are not met. One or more of these checks
failed. To disregard these results, you may choose to
disable failing checks by setting an Ansible variable:
openshift_disable_check=docker_image_availability,docker_storage
Failing check names are shown in the failure details above.
Some checks may be configurable by variables if your requirements
are different from the defaults; consult check documentation.
Variables can be set in the inventory or passed on the
command line using the -e flag to ansible-playbook.
Ok, modified
/home/ec2-user/openshift-ansible-contrib/reference-architecture/aws-ansible/playbooks/openshift-setup.yaml
and add:
Disable Checks
  openshift_disable_check: docker_image_availability,docker_storage

Start again:

TASK [etcd_common : Install etcd for etcdctl] *****************************************************************************************************
fatal: [ose-master02.mindcurv-labs.es]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'etcd' found available, installed or updated", "rc": 126, "results": ["No package matching 'etcd' found available, installed or updated"]}
fatal: [ose-master03.mindcurv-labs.es]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'etcd' found available, installed or updated", "rc": 126, "results": ["No package matching 'etcd' found available, installed or updated"]}
fatal: [ose-master01.mindcurv-labs.es]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'etcd' found available, installed or updated", "rc": 126, "results": ["No package matching 'etcd' found available, installed or updated"]}
PLAY RECAP ****************************************************************************************************************************************
localhost                  : ok=20   changed=5    unreachable=0    failed=0
ose-app-node01.mindcurv-labs.es : ok=95   changed=9    unreachable=0    failed=0
ose-app-node02.mindcurv-labs.es : ok=95   changed=9    unreachable=0    failed=0
ose-infra-node01.mindcurv-labs.es : ok=95   changed=9    unreachable=0    failed=0
ose-infra-node02.mindcurv-labs.es : ok=95   changed=9    unreachable=0    failed=0
ose-infra-node03.mindcurv-labs.es : ok=95   changed=9    unreachable=0    failed=0
ose-master01.mindcurv-labs.es : ok=150  changed=35   unreachable=0    failed=1
ose-master02.mindcurv-labs.es : ok=141  changed=27   unreachable=0    failed=1
ose-master03.mindcurv-labs.es : ok=141  changed=27   unreachable=0    failed=1
Failure summary:

Host:     ose-master02.mindcurv-labs.es
Play:     Configure etcd
Task:     etcd_common : Install etcd for etcdctl
Message:  No package matching 'etcd' found available, installed or updated

Host:     ose-master03.mindcurv-labs.es
Play:     Configure etcd
Task:     etcd_common : Install etcd for etcdctl
Message:  No package matching 'etcd' found available, installed or updated

Host:     ose-master01.mindcurv-labs.es
Play:     Configure etcd
Task:     etcd_common : Install etcd for etcdctl
Message:  No package matching 'etcd' found available, installed or updated

Now it cannot install etcd.
RHEL-7.4_HVM_GA-20170808-x86_64-2-Hourly2-GP2 (ami-d74be5b8) - Frankfurt Region

@jcperezamin - Have you since found any resolution to your problem with etcd?

I merged in 3.6 code that should resolve any issues. I tested in a similar
format using origin with the. Let me know if you have any issues.
Ryan
On Aug 17, 2017 10:23 PM, "Chrrrles Paul"<EMAIL_ADDRESS>wrote:

@jcperezamin https://github.com/jcperezamin - Have you since found any
resolution to your problem with etcd?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openshift/openshift-ansible-contrib/issues/636#issuecomment-323242446,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADoslJFMiZY37oXGrNzdglttaypIVGTLks5sZPWQgaJpZM4O1oKK
.

Update:
TASK [non-atomic-docker-storage-setup : Gather facts] *********************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: main.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'
fatal: [ose-app-node01.mindcurv-labs.es]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n  File "/tmp/ansible_tIDQZ1/ansible_module_openshift_facts.py", line 2555, in \n    main()\n  File "/tmp/ansible_tIDQZ1/ansible_module_openshift_facts.py", line 2542, in main\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_tIDQZ1/ansible_module_openshift_facts.py", line 1950, in init\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_tIDQZ1/ansible_module_openshift_facts.py", line 1974, in generate_facts\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_tIDQZ1/ansible_module_openshift_facts.py", line 2412, in init_local_facts\n    save_local_facts(self.filename, new_local_facts)\n  File "/tmp/ansible_tIDQZ1/ansible_module_openshift_facts.py", line 1586, in save_local_facts\n    "Could not create fact file: %s, error: %s" % (filename, ex)\n__main__.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 1}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: main.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'
fatal: [ose-master01.mindcurv-labs.es]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n  File "/tmp/ansible_m1Y1Lx/ansible_module_openshift_facts.py", line 2555, in \n    main()\n  File "/tmp/ansible_m1Y1Lx/ansible_module_openshift_facts.py", line 2542, in main\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_m1Y1Lx/ansible_module_openshift_facts.py", line 1950, in init\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_m1Y1Lx/ansible_module_openshift_facts.py", line 1974, in generate_facts\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_m1Y1Lx/ansible_module_openshift_facts.py", line 2412, in init_local_facts\n    save_local_facts(self.filename, new_local_facts)\n  File "/tmp/ansible_m1Y1Lx/ansible_module_openshift_facts.py", line 1586, in save_local_facts\n    "Could not create fact file: %s, error: %s" % (filename, ex)\n__main__.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 1}
An exception occurred during task execution. To see the full traceback, use -vvv.  To see the full traceback, use -vvv. The error was: main.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'
fatal: [ose-master02.mindcurv-labs.es]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n  File "/tmp/ansible_JBDx_D/ansible_module_openshift_facts.py", line 2555, in \n    main()\n  File "/tmp/ansible_JBDx_D/ansible_module_openshift_facts.py", line 2542, in main\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_JBDx_D/ansible_module_openshift_facts.py", line 1950, in init\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_JBDx_D/ansible_module_openshift_facts.py", line 1974, in generate_facts\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_JBDx_D/ansible_module_openshift_facts.py", line 2412, in init_local_facts\n    save_local_facts(self.filename, new_local_facts)\n  File "/tmp/ansible_JBDx_D/ansible_module_openshift_facts.py", line 1586, in save_local_facts\n    "Could not create fact file: %s, error: %s" % (filename, ex)\n__main__.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 1}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: main.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'
fatal: [ose-infra-node03.mindcurv-labs.es]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n  File "/tmp/ansible_vN8uUn/ansible_module_openshift_facts.py", line 2555, in \n    main()\n  File "/tmp/ansible_vN8uUn/ansible_module_openshift_facts.py", line 2542, in main\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_vN8uUn/ansible_module_openshift_facts.py", line 1950, in init\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_vN8uUn/ansible_module_openshift_facts.py", line 1974, in generate_facts\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_vN8uUn/ansible_module_openshift_facts.py", line 2412, in init_local_facts\n    save_local_facts(self.filename, new_local_facts)\n  File "/tmp/ansible_vN8uUn/ansible_module_openshift_facts.py", line 1586, in save_local_facts\n    "Could not create fact file: %s, error: %s" % (filename, ex)\n__main__.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 1}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: main.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'
fatal: [ose-infra-node02.mindcurv-labs.es]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n  File "/tmp/ansible_GLXK7J/ansible_module_openshift_facts.py", line 2555, in \n    main()\n  File "/tmp/ansible_GLXK7J/ansible_module_openshift_facts.py", line 2542, in main\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_GLXK7J/ansible_module_openshift_facts.py", line 1950, in init\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_GLXK7J/ansible_module_openshift_facts.py", line 1974, in generate_facts\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_GLXK7J/ansible_module_openshift_facts.py", line 2412, in init_local_facts\n    save_local_facts(self.filename, new_local_facts)\n  File "/tmp/ansible_GLXK7J/ansible_module_openshift_facts.py", line 1586, in save_local_facts\n    "Could not create fact file: %s, error: %s" % (filename, ex)\n__main__.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 1}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: main.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'
fatal: [ose-app-node02.mindcurv-labs.es]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n  File "/tmp/ansible_HHsI_M/ansible_module_openshift_facts.py", line 2555, in \n    main()\n  File "/tmp/ansible_HHsI_M/ansible_module_openshift_facts.py", line 2542, in main\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_HHsI_M/ansible_module_openshift_facts.py", line 1950, in init\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_HHsI_M/ansible_module_openshift_facts.py", line 1974, in generate_facts\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_HHsI_M/ansible_module_openshift_facts.py", line 2412, in init_local_facts\n    save_local_facts(self.filename, new_local_facts)\n  File "/tmp/ansible_HHsI_M/ansible_module_openshift_facts.py", line 1586, in save_local_facts\n    "Could not create fact file: %s, error: %s" % (filename, ex)\n__main__.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 1}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: main.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'
fatal: [ose-master03.mindcurv-labs.es]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n  File "/tmp/ansible_Sw0fJk/ansible_module_openshift_facts.py", line 2555, in \n    main()\n  File "/tmp/ansible_Sw0fJk/ansible_module_openshift_facts.py", line 2542, in main\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_Sw0fJk/ansible_module_openshift_facts.py", line 1950, in init\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_Sw0fJk/ansible_module_openshift_facts.py", line 1974, in generate_facts\n    protected_facts_to_overwrite)\n  File "/tmp/ansible_Sw0fJk/ansible_module_openshift_facts.py", line 2412, in init_local_facts\n    save_local_facts(self.filename, new_local_facts)\n  File "/tmp/ansible_Sw0fJk/ansible_module_openshift_facts.py", line 1586, in save_local_facts\n    "Could not create fact file: %s, error: %s" % (filename, ex)\n__main__.OpenShiftFactsFileWriteError: Could not create fact file: /etc/ansible/facts.d/openshift.fact, error: [Errno 13] Permission denied: '/etc/ansible/facts.d'\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 1}
PLAY RECAP ****************************************************************************************************************
localhost                  : ok=9    changed=5    unreachable=0    failed=0
ose-app-node01.mindcurv-labs.es : ok=0    changed=0    unreachable=0    failed=1
ose-app-node02.mindcurv-labs.es : ok=0    changed=0    unreachable=0    failed=1
ose-infra-node01.mindcurv-labs.es : ok=0    changed=0    unreachable=0    failed=1
ose-infra-node02.mindcurv-labs.es : ok=0    changed=0    unreachable=0    failed=1
ose-infra-node03.mindcurv-labs.es : ok=0    changed=0    unreachable=0    failed=1
ose-master01.mindcurv-labs.es : ok=0    changed=0    unreachable=0    failed=1
ose-master02.mindcurv-labs.es : ok=0    changed=0    unreachable=0    failed=1
ose-master03.mindcurv-labs.es : ok=0    changed=0    unreachable=0    failed=1
Failure summary:

Host:     ose-app-node01.mindcurv-labs.es
Play:     nodes
Task:     non-atomic-docker-storage-setup : Gather facts
Message:  MODULE FAILURE

Host:     ose-master01.mindcurv-labs.es
Play:     nodes
Task:     non-atomic-docker-storage-setup : Gather facts
Message:  MODULE FAILURE

Host:     ose-infra-node01.mindcurv-labs.es
Play:     nodes
Task:     non-atomic-docker-storage-setup : Gather facts
Message:  MODULE FAILURE

Host:     ose-master02.mindcurv-labs.es
Play:     nodes
Task:     non-atomic-docker-storage-setup : Gather facts
Message:  MODULE FAILURE

Host:     ose-infra-node03.mindcurv-labs.es
Play:     nodes
Task:     non-atomic-docker-storage-setup : Gather facts
Message:  MODULE FAILURE

Host:     ose-infra-node02.mindcurv-labs.es
Play:     nodes
Task:     non-atomic-docker-storage-setup : Gather facts
Message:  MODULE FAILURE

Host:     ose-app-node02.mindcurv-labs.es
Play:     nodes
Task:     non-atomic-docker-storage-setup : Gather facts
Message:  MODULE FAILURE

Host:     ose-master03.mindcurv-labs.es
Play:     nodes
Task:     non-atomic-docker-storage-setup : Gather facts
Message:  MODULE FAILURE

Spent some time on this today. Give it a check. Sorry for the delay

Update:
TASK [non-atomic-docker-storage-setup : create the docker-storage-setup config file] ********************************
fatal: [ose-infra-node02.mindcurv-labs.es]: FAILED! => {"failed": true, "msg": "The conditional check 'not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'' failed. The error was: error while evaluating conditional (not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'): 'ansible_distribution' is undefined\n\nThe error appears to have been in '/home/ec2-user/openshift-ansible-contrib/reference-architecture/aws-ansible/playbooks/roles/non-atomic-docker-storage-setup/tasks/main.yaml': line 6, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: create the docker-storage-setup config file\n  ^ here\n"}
fatal: [ose-master03.mindcurv-labs.es]: FAILED! => {"failed": true, "msg": "The conditional check 'not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'' failed. The error was: error while evaluating conditional (not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'): 'ansible_distribution' is undefined\n\nThe error appears to have been in '/home/ec2-user/openshift-ansible-contrib/reference-architecture/aws-ansible/playbooks/roles/non-atomic-docker-storage-setup/tasks/main.yaml': line 6, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: create the docker-storage-setup config file\n  ^ here\n"}
fatal: [ose-master01.mindcurv-labs.es]: FAILED! => {"failed": true, "msg": "The conditional check 'not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'' failed. The error was: error while evaluating conditional (not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'): 'ansible_distribution' is undefined\n\nThe error appears to have been in '/home/ec2-user/openshift-ansible-contrib/reference-architecture/aws-ansible/playbooks/roles/non-atomic-docker-storage-setup/tasks/main.yaml': line 6, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: create the docker-storage-setup config file\n  ^ here\n"}
fatal: [ose-master02.mindcurv-labs.es]: FAILED! => {"failed": true, "msg": "The conditional check 'not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'' failed. The error was: error while evaluating conditional (not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'): 'ansible_distribution' is undefined\n\nThe error appears to have been in '/home/ec2-user/openshift-ansible-contrib/reference-architecture/aws-ansible/playbooks/roles/non-atomic-docker-storage-setup/tasks/main.yaml': line 6, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: create the docker-storage-setup config file\n  ^ here\n"}
fatal: [ose-infra-node01.mindcurv-labs.es]: FAILED! => {"failed": true, "msg": "The conditional check 'not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'' failed. The error was: error while evaluating conditional (not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'): 'ansible_distribution' is undefined\n\nThe error appears to have been in '/home/ec2-user/openshift-ansible-contrib/reference-architecture/aws-ansible/playbooks/roles/non-atomic-docker-storage-setup/tasks/main.yaml': line 6, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: create the docker-storage-setup config file\n  ^ here\n"}
fatal: [ose-infra-node03.mindcurv-labs.es]: FAILED! => {"failed": true, "msg": "The conditional check 'not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'' failed. The error was: error while evaluating conditional (not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'): 'ansible_distribution' is undefined\n\nThe error appears to have been in '/home/ec2-user/openshift-ansible-contrib/reference-architecture/aws-ansible/playbooks/roles/non-atomic-docker-storage-setup/tasks/main.yaml': line 6, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: create the docker-storage-setup config file\n  ^ here\n"}
fatal: [ose-app-node02.mindcurv-labs.es]: FAILED! => {"failed": true, "msg": "The conditional check 'not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'' failed. The error was: error while evaluating conditional (not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'): 'ansible_distribution' is undefined\n\nThe error appears to have been in '/home/ec2-user/openshift-ansible-contrib/reference-architecture/aws-ansible/playbooks/roles/non-atomic-docker-storage-setup/tasks/main.yaml': line 6, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: create the docker-storage-setup config file\n  ^ here\n"}
fatal: [ose-app-node01.mindcurv-labs.es]: FAILED! => {"failed": true, "msg": "The conditional check 'not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'' failed. The error was: error while evaluating conditional (not openshift.common.is_atomic | bool and ansible_distribution != 'CentOS'): 'ansible_distribution' is undefined\n\nThe error appears to have been in '/home/ec2-user/openshift-ansible-contrib/reference-architecture/aws-ansible/playbooks/roles/non-atomic-docker-storage-setup/tasks/main.yaml': line 6, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: create the docker-storage-setup config file\n  ^ here\n"}

Can you validate these are the same values you are using
Configured values:
	stack_name: test
	ami: ami-d74be5b8
	region: eu-central-1
	master_instance_type: m4.xlarge
	node_instance_type: t2.large
	app_instance_type: t2.large
	app_node_count: 1
	bastion_instance_type: t2.micro
	keypair: OSE-key
	create_key: yes
	key_path: /root/.ssh/id_rsa.pub
	create_vpc: yes
	vpc_id: None
	private_subnet_id1: None
	private_subnet_id2: None
	private_subnet_id3: None
	public_subnet_id1: None
	public_subnet_id2: None
	public_subnet_id3: None
	byo_bastion: no
	bastion_sg: /dev/null
	console port: 443
	deployment_type: origin
	openshift_sdn: redhat/openshift-ovs-multitenant
	public_hosted_zone: ci.sysdeseng.com
	app_dns_prefix: apps
	apps_dns: apps.ci.sysdeseng.com
	containerized: False
	s3_bucket_name: test-ocp-registry-ci
	s3_username: test-s3-openshift-user
	github_client_id: *******
	github_client_secret: *******
	github_organization: openshift
	openshift_metrics_deploy: true
	openshift_metrics_storage_volume_size: 20Gi
	openshift_logging_deploy: true
	openshift_logging_storage_volume_size: 100Gi

I was able to go straight through with the latest master branch
TASK [Gathering Facts] ********************************************************************************************************************************************************************************************
ok: [ose-infra-node01.ci.sysdeseng.com]
ok: [ose-master02.ci.sysdeseng.com]
ok: [ose-infra-node03.ci.sysdeseng.com]
ok: [ose-app-node01.ci.sysdeseng.com]
ok: [ose-infra-node02.ci.sysdeseng.com]
ok: [ose-master03.ci.sysdeseng.com]
ok: [ose-master01.ci.sysdeseng.com]

TASK [non-atomic-docker-storage-setup : Gather facts] *************************************************************************************************************************************************************
changed: [ose-master03.ci.sysdeseng.com]
changed: [ose-infra-node02.ci.sysdeseng.com]
changed: [ose-infra-node01.ci.sysdeseng.com]
changed: [ose-infra-node03.ci.sysdeseng.com]
changed: [ose-app-node01.ci.sysdeseng.com]
changed: [ose-master01.ci.sysdeseng.com]
changed: [ose-master02.ci.sysdeseng.com]

TASK [non-atomic-docker-storage-setup : create the docker-storage-setup config file] ******************************************************************************************************************************
changed: [ose-infra-node03.ci.sysdeseng.com]
changed: [ose-master03.ci.sysdeseng.com]
changed: [ose-infra-node01.ci.sysdeseng.com]
changed: [ose-app-node01.ci.sysdeseng.com]
changed: [ose-infra-node02.ci.sysdeseng.com]
changed: [ose-master02.ci.sysdeseng.com]
changed: [ose-master01.ci.sysdeseng.com]

TASK [non-atomic-docker-storage-setup : create the docker-storage-setup config file] ******************************************************************************************************************************
skipping: [ose-infra-node02.ci.sysdeseng.com]
skipping: [ose-infra-node01.ci.sysdeseng.com]
skipping: [ose-master03.ci.sysdeseng.com]
skipping: [ose-master01.ci.sysdeseng.com]
skipping: [ose-master02.ci.sysdeseng.com]
skipping: [ose-infra-node03.ci.sysdeseng.com]
skipping: [ose-app-node01.ci.sysdeseng.com]

TASK [openshift-versions : Set Origin fact] ***********************************************************************************************************************************************************************
ok: [ose-master03.ci.sysdeseng.com]
ok: [ose-infra-node01.ci.sysdeseng.com]
ok: [ose-master01.ci.sysdeseng.com]
ok: [ose-master02.ci.sysdeseng.com]
ok: [ose-infra-node03.ci.sysdeseng.com]
ok: [ose-infra-node02.ci.sysdeseng.com]
ok: [ose-app-node01.ci.sysdeseng.com]

PLAY [nodes] ******************************************************************************************************************************************************************************************************

TASK [rhsm-timeout : Gather facts] ********************************************************************************************************************************************************************************
ok: [ose-infra-node01.ci.sysdeseng.com]
ok: [ose-master02.ci.sysdeseng.com]
ok: [ose-infra-node03.ci.sysdeseng.com]
ok: [ose-master01.ci.sysdeseng.com]
ok: [ose-app-node01.ci.sysdeseng.com]
ok: [ose-master03.ci.sysdeseng.com]
ok: [ose-infra-node02.ci.sysdeseng.com]

TASK [rhsm-timeout : Allow rhsm a longer timeout to help out with subscription-manager] ***************************************************************************************************************************
changed: [ose-master02.ci.sysdeseng.com]
changed: [ose-infra-node03.ci.sysdeseng.com]
changed: [ose-master03.ci.sysdeseng.com]
changed: [ose-app-node01.ci.sysdeseng.com]
changed: [ose-master01.ci.sysdeseng.com]
changed: [ose-infra-node01.ci.sysdeseng.com]
changed: [ose-infra-node02.ci.sysdeseng.com]

TASK [atomic-update : Determine Atomic Host Docker Version] *******************************************************************************************************************************************************
skipping: [ose-infra-node02.ci.sysdeseng.com]
skipping: [ose-master03.ci.sysdeseng.com]
skipping: [ose-infra-node03.ci.sysdeseng.com]
skipping: [ose-infra-node01.ci.sysdeseng.com]
skipping: [ose-master01.ci.sysdeseng.com]
skipping: [ose-master02.ci.sysdeseng.com]
skipping: [ose-app-node01.ci.sysdeseng.com]

TASK [atomic-update : assert] *************************************************************************************************************************************************************************************
skipping: [ose-master01.ci.sysdeseng.com]
skipping: [ose-master02.ci.sysdeseng.com]
skipping: [ose-infra-node01.ci.sysdeseng.com]
skipping: [ose-master03.ci.sysdeseng.com]
skipping: [ose-infra-node03.ci.sysdeseng.com]
skipping: [ose-infra-node02.ci.sysdeseng.com]
skipping: [ose-app-node01.ci.sysdeseng.com]

PLAY [nodes] ******************************************************************************

the interesting / weird part we are going to have is enabling a repository that has the docker package available. Ill look into that now

I found Docker has changed his policy about to support Docker CE on RHEL. If you want to use docker on RHEL it has to be Docker EE and imply to have a docker EE subscription.
Attached steps:
Docker CE on Redhat 7.x
pre-requisite for container-selinux-2.9-4.el7.noarch.rpm
sudo yum install policycoreutils-python
wget http://mirror.centos.org/centos/7/extras/x86_64/Packages/container-selinux-2.9-4.el7.noarch.rpm
sudo rpm -i container-selinux-2.9-4.el7.noarch.rpm
#Set up the Docker CE repository on RHEL:
sudo yum install -y yum-utils
sudo yum install -y device-mapper-persistent-data lvm2
sudo yum-config-manager --enable rhel-7-server-extras-rpms
sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
sudo yum makecache fast
Install the latest version of Docker CE on RHEL:
sudo yum -y install docker-ce
#Start Docker:
sudo systemctl start docker
#Test your Docker CE installation:
sudo docker run hello-world
configure Docker to start on boot
sudo systemctl enable docker
add user to the docker group
sudo usermod -aG docker jethro
install Docker Compose:
install python-pip
wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
sudo yum install ./epel-release-latest-7.noarch.rpm
sudo yum install -y python-pip
sudo pip install docker-compose
upgrade your Python packages:
sudo yum upgrade python*

Update:
Configured values:
stack_name: openshift-atomic
ami: ami-d74be5b8
region: eu-central-1
master_instance_type: m4.xlarge
node_instance_type: t2.large
app_instance_type: t2.large
app_node_count: 2
bastion_instance_type: t2.micro
keypair: OpenshiftKeyPub
create_key: no
key_path: /dev/null
create_vpc: yes
vpc_id: None
private_subnet_id1: None
private_subnet_id2: None
private_subnet_id3: None
public_subnet_id1: None
public_subnet_id2: None
public_subnet_id3: None
byo_bastion: no
bastion_sg: /dev/null
console port: 443
deployment_type: origin
openshift_sdn: redhat/openshift-ovs-multitenant
public_hosted_zone: mindcurv-labs.es
app_dns_prefix: dev
apps_dns: dev.mindcurv-labs.es
containerized: false
s3_bucket_name: openshift-atomic-ocp-registry-mindcurv-labs
s3_username: openshift-atomic-s3-openshift-user
github_client_id: *******
github_client_secret: *******
github_organization: openshift,Mindcurv
openshift_metrics_deploy: true
openshift_metrics_storage_volume_size: 20Gi
openshift_logging_deploy: true
openshift_logging_storage_volume_size: 100Gi
failed: [ose-infra-node03.mindcurv-labs.es] (item=docker) => {"changed": false, "failed": true, "item": "docker", "msg": "No package matching 'docker' found available, installed or updated", "rc": 126, "results": ["No package matching 'docker' found available, installed or updated"]}
ok: [ose-infra-node01.mindcurv-labs.es] => (item=NetworkManager)
failed: [ose-app-node01.mindcurv-labs.es] (item=docker) => {"changed": false, "failed": true, "item": "docker", "msg": "No package matching 'docker' found available, installed or updated", "rc": 126, "results": ["No package matching 'docker' found available, installed or updated"]}
ok: [ose-master02.mindcurv-labs.es] => (item=NetworkManager)
failed: [ose-master03.mindcurv-labs.es] (item=docker) => {"changed": false, "failed": true, "item": "docker", "msg": "No package matching 'docker' found available, installed or updated", "rc": 126, "results": ["No package matching 'docker' found available, installed or updated"]}
failed: [ose-infra-node02.mindcurv-labs.es] (item=docker) => {"changed": false, "failed": true, "item": "docker", "msg": "No package matching 'docker' found available, installed or updated", "rc": 126, "results": ["No package matching 'docker' found available, installed or updated"]}
failed: [ose-app-node02.mindcurv-labs.es] (item=docker) => {"changed": false, "failed": true, "item": "docker", "msg": "No package matching 'docker' found available, installed or updated", "rc": 126, "results": ["No package matching 'docker' found available, installed or updated"]}
failed: [ose-master01.mindcurv-labs.es] (item=docker) => {"changed": false, "failed": true, "item": "docker", "msg": "No package matching 'docker' found available, installed or updated", "rc": 126, "results": ["No package matching 'docker' found available, installed or updated"]}
failed: [ose-infra-node01.mindcurv-labs.es] (item=docker) => {"changed": false, "failed": true, "item": "docker", "msg": "No package matching 'docker' found available, installed or updated", "rc": 126, "results": ["No package matching 'docker' found available, installed or updated"]}
failed: [ose-master02.mindcurv-labs.es] (item=docker) => {"changed": false, "failed": true, "item": "docker", "msg": "No package matching 'docker' found available, installed or updated", "rc": 126, "results": ["No package matching 'docker' found available, installed or updated"]}

It looks like the installation playbooks require the "docker" package instead the "docker-ce" https://github.com/openshift/openshift-ansible/blob/master/roles/docker/tasks/package_docker.yml#L35
Is there any reason to use docker-ce instead the included RHEL docker package?

Actually u have to install docker yourself in 3.4 now
Sent from my iPhone

On 29 Aug 2017, at 5:18 PM, Eduardo Mínguez<EMAIL_ADDRESS>wrote:
It looks like the installation playbooks require the "docker" package instead the "docker-ce" https://github.com/openshift/openshift-ansible/blob/master/roles/docker/tasks/package_docker.yml#L35
Is there any reason to use docker-ce instead the included RHEL docker package?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Because of this: https://docs.docker.com/engine/installation/linux/docker-ee/rhel/

I'm talking about installing the docker package provided by RHEL:
[cloud-user@master-0 ~]$ rpm -qi docker
Name        : docker
Epoch       : 2
Version     : 1.12.6
Release     : 48.git0fdc778.el7
Architecture: x86_64
Install Date: Tue 29 Aug 2017 06:01:04 AM EDT
Group       : Unspecified
Size        : 54227529
License     : ASL 2.0
Signature   : RSA/SHA256, Thu 20 Jul 2017 12:37:10 AM EDT, Key ID 199e2f91fd431d51
Source RPM  : docker-1.12.6-48.git0fdc778.el7.src.rpm
Build Date  : Thu 20 Jul 2017 12:08:10 AM EDT
Build Host  : x86-038.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor      : Red Hat, Inc.
URL         : https://github.com/docker/docker
Summary     : Automates deployment of containerized applications
Description :
Docker is an open-source engine that automates the deployment of any
application as a lightweight, portable, self-sufficient container that will
run virtually anywhere.

Docker containers can encapsulate any payload, and will run consistently on
and between virtually any server. The same container that a developer builds
and tests on a laptop will run at scale, in production*, on VMs, bare-metal
servers, OpenStack clusters, public instances, or combinations of the above.

It is located in the rhel-7-server-extras-rpms repo which is included in every RHEL subscription https://access.redhat.com/downloads/content/docker/1.12.6-48.git0fdc778.el7/x86_64/fd431d51/package

Something has changed because is not taking RHEL docker package. I tested an openshift allinone with this inventory and CentOS image
CentOS
ami-fa2df395 - Frankfurt
[OSEv3:children]
masters
nodes
[OSEv3:vars]
ansible_ssh_user=root
openshift_release=v3.6
deployment_type=openshift-enterprise
openshift_master_identity_providers=[{'name': 'htpasswd_auth', 'login': 'true', 'challenge': 'true', 'kind': 'HTPasswdPasswordIdentityProvider', 'filename': '/etc/origin/master/htpasswd'}]
containerized=true
openshift_cloudprovider_kind=aws
enable_docker_excluder=false
enable_openshift_excluder=false
openshift_release=3.6
openshift_image_tag=v3.6.0
openshift_install_examples=true
openshift_public_hostname=logging.mindcurv-labs.com
openshift_master_default_subdomain=logging.apps.mindcurv-labs.com
openshift_hosted_metrics_deploy=true
openshift_metrics_cassandra_storage_type=dynamic
openshift_disable_check=docker_storage
openshift_hosted_logging_deploy=true
openshift_hosted_logging_deployer_version=v3.6
openshift_hosted_logging_storage_kind=dynamic
[masters]
logging.mindcurv-labs.com openshift_schedulable=true
[nodes]
logging.mindcurv-labs.com openshift_node_labels="{'region': 'infra', 'zone': 'default'}" openshift_schedulable=true
But I had to install docker separately and is working out.

7.4 rhel with ocp 3.6 single vm on azure
Working fine
Sent from my iPhone

On 29 Aug 2017, at 6:42 PM, Eduardo Mínguez<EMAIL_ADDRESS>wrote:
I'm talking about installing the docker package provided by RHEL:
[cloud-user@master-0 ~]$ rpm -qi docker
Name        : docker
Epoch       : 2
Version     : 1.12.6
Release     : 48.git0fdc778.el7
Architecture: x86_64
Install Date: Tue 29 Aug 2017 06:01:04 AM EDT
Group       : Unspecified
Size        : 54227529
License     : ASL 2.0
Signature   : RSA/SHA256, Thu 20 Jul 2017 12:37:10 AM EDT, Key ID 199e2f91fd431d51
Source RPM  : docker-1.12.6-48.git0fdc778.el7.src.rpm
Build Date  : Thu 20 Jul 2017 12:08:10 AM EDT
Build Host  : x86-038.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. http://bugzilla.redhat.com/bugzilla
Vendor      : Red Hat, Inc.
URL         : https://github.com/docker/docker
Summary     : Automates deployment of containerized applications
Description :
Docker is an open-source engine that automates the deployment of any
application as a lightweight, portable, self-sufficient container that will
run virtually anywhere.
Docker containers can encapsulate any payload, and will run consistently on
and between virtually any server. The same container that a developer builds
and tests on a laptop will run at scale, in production*, on VMs, bare-metal
servers, OpenStack clusters, public instances, or combinations of the above.
It is located in the rhel-7-server-extras-rpms repo which is included in every RHEL subscription https://access.redhat.com/downloads/content/docker/1.12.6-48.git0fdc778.el7/x86_64/fd431d51/package
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

yum install docker from extras
Checking startup bash for azure
One thing come to mind is inclusion of epel can cause havoc
Also it might be storage setup as well
Sent from my iPhone

On 29 Aug 2017, at 6:42 PM, Eduardo Mínguez<EMAIL_ADDRESS>wrote:
I'm talking about installing the docker package provided by RHEL:
[cloud-user@master-0 ~]$ rpm -qi docker
Name        : docker
Epoch       : 2
Version     : 1.12.6
Release     : 48.git0fdc778.el7
Architecture: x86_64
Install Date: Tue 29 Aug 2017 06:01:04 AM EDT
Group       : Unspecified
Size        : 54227529
License     : ASL 2.0
Signature   : RSA/SHA256, Thu 20 Jul 2017 12:37:10 AM EDT, Key ID 199e2f91fd431d51
Source RPM  : docker-1.12.6-48.git0fdc778.el7.src.rpm
Build Date  : Thu 20 Jul 2017 12:08:10 AM EDT
Build Host  : x86-038.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. http://bugzilla.redhat.com/bugzilla
Vendor      : Red Hat, Inc.
URL         : https://github.com/docker/docker
Summary     : Automates deployment of containerized applications
Description :
Docker is an open-source engine that automates the deployment of any
application as a lightweight, portable, self-sufficient container that will
run virtually anywhere.
Docker containers can encapsulate any payload, and will run consistently on
and between virtually any server. The same container that a developer builds
and tests on a laptop will run at scale, in production*, on VMs, bare-metal
servers, OpenStack clusters, public instances, or combinations of the above.
It is located in the rhel-7-server-extras-rpms repo which is included in every RHEL subscription https://access.redhat.com/downloads/content/docker/1.12.6-48.git0fdc778.el7/x86_64/fd431d51/package
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Footer relative links issue.

On 888.de footer we have links to internal pages, the links on our current site are relavative.
We change some of the footer links,

in the EDS site (https://main--888de--aemsites.hlx.live/ >> https://eds-www.888.de/) to be relative (in the file https://888holdings.sharepoint.com/:w:/r/sites/888-eds/_layouts/15/Doc.aspx?sourcedoc={41AAFAA0-8CB6-4BD6-BFD7-D88305688342}&file=footer.docx&action=default&mobileredirect=true , share point), with editing the link via Word’s widget, but it does not accept relative links

originally inserted: “/banking/”.
When the footer was published via (Sidekick), the link was removed from the source code, this is what I get in “inspect element”
Both https://main--888de--aemsites.hlx.live/ & https://eds-www.888.de/
Is there a way to change links to relative ?

Hi @rafim888 ,
the Edge Delivery Service (formerly known as "Franklin") is smart, and should be automatically handling links that are entered using the project branch + hlx.page URL, and showing as relative on the published page. I will have a look at our 888 footer to see what's happening.
Here's an example from a previous project:

I had a quick look, I am seeing the local paths on https://eds-dev-www.888.de/ where I edited (see screenshot).

I do see an extra word on the 1st link, but I am thinking it might be because you have it open and are currently editing...?

10x Charity.
all clear now


Fix open collective link

Codecov Report

Merging #289 into develop will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           develop   #289   +/-   ##
======================================
  Coverage      100%   100%
======================================
  Files            1      1
  Lines            1      1
======================================
  Hits             1      1

Continue to review full report at Codecov.

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


fix: Use Kubeconfig endpoint to recover temporal kubeconfig

Fixes https://github.com/stackitcloud/terraform-provider-stackit/issues/244

I'm validating the PR right now with my own project

I will also update the field description and some method/variable names but I can do it in a follow-up PR

I can upgrade my PR to include you changes if you want

I can upgrade my PR to include you changes if you want (or including my changes as part of your PR)

Yeah that would be great! Maybe the second option is best

Do you mean including my changes as part of your PR? as you prefer, I don't have problems with that

I'm checking the changes on my local project and it still doesn't work

Do you mean including my changes as part of your PR? as you prefer, I don't have problems with that

Yes I think we can just use my PR, since it already includes your changes and the additional updates to the descriptions. I'm also running acceptance tests on that branch.

I'm checking the changes on my local project and it still doesn't work

What error are you getting?

What error are you getting?

I'm not getting any error, but Kubeconfig is nil

Closing this one in favor of #250


create code scan workflow

as per security requested

removed some of the comments and kept the others as they might be useful for us to understand the workflow in the future


Merge dev into tokio migration

@ashthespy I'm leaving any PRs that touch the tokio_migration branch for you to deal with since it's your branch and it's in progress/draft atm.


Old YOLO detector Models

Can I use previous yolo  detector models  for MOT (object tracking) like yolov3 /yolov4 networks trained on our custom dataset. What possible changes we have to do if I can modify the existing code for yolov3. THanks

Hi @sharoseali ,
Yes of course you can replace the YOLOX detector with other detectors. I think you only need to modify demo/demo_mot.py. Please have a look at the code then you will understand :)

Hi @sharoseali,
I am not sure I understood your question, maybe you could use code in this repo for parsing cfg and loading model weights?

Hi @sharoseali , Yes of course you can replace the YOLOX detector with other detectors. I think you only need to modify demo/demo_mot.py. Please have a look at the code then you will understand :)

Hi @Zhongdao i have my YOLOv3 custom detection models in .weights file. I want to use them in Multi class Multi tacker. I go through the code but didn't find any code parsing cfg and .weights files used in official dark-net repo. is there any way that i can use them.

do you solve this problem?

Hi @sharoseali , Yes of course you can replace the YOLOX detector with other detectors. I think you only need to modify demo/demo_mot.py. Please have a look at the code then you will understand :)

Hi @Zhongdao i have my YOLOv3 custom detection models in .weights file. I want to use them in Multi class Multi tacker. I go through the code but didn't find any code parsing cfg and .weights files used in official dark-net repo. is there any way that i can use them.

do you solve this problem?

Not yet.... I choose  to work on MCMOT YOLOV4. It contains YOLOv3/v4 parsing code but also many problems exist there and needed to be fixed.😐


Replace gif with the blog production photo

@andrewowen, please update the readme.md and use the latest production image.

@jaygarcia I think the README uses the correct image, please can you confirm.  It uses the image that was also used in http://moduscreate.com/announcing-evade-our-first-arduboy-game/


JavaScript rename not working for JSDoc param name for function assignment

Issue Type: Bug

Try to rename item (at any place)
item in code successfully renamed while JSDoc name stayed the same

/**
 * @param {*} item
 */
let f = function (item) {}

VS Code version: Code - Insiders 1.36.0-insider (9ff8ae037e8e6109d65e4b5e3eb3dc60cc187e21, 2019-06-21T07:52:00.716Z)
OS version: Windows_NT x64 10.0.18362

Confirmed with TypeScript 3.6.0-dev.20190623

Binding only works on function declarations right now.
/**
 * @param {*} item
 */
function f(item) {}


pull request for e2e test at 12/31/2016 07:26:15

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Remove NodeCommand for AWS

Related to issue #373.
It seems as though AWS no longer supports NoeCommand, and running a fresh example install throws "NodeCommand not found".
Not sure if this has any impact on previous deployments on AWS.

@TomWFox, @acinader who has write rights to review this?

Feel free to add a review but @davimacedo & @dplewis have access (as do I).

running a fresh example install throws "NodeCommand not found".

Interesting, I do not observe that, I see it deploy and run as expected.

Related to this community discussion

@TomWFox Can we add the "issue" in this repo? I feel that linking PRs to threads in the Community Forum is generally not good practice, as we may loose the info there. The link above for example does not work, the correct link is this.
Related AWS doc.

Issues turned on - I see why they were turned off - could do with closing some issues. I corrected the link.

could do with closing some issues

You can add me to the repo and I'll clean it up.

Done, 105 -> 1 all but the remaining were 3+ years old (obviously inactive) and many seemed to be issues that should have been created on the Parse Server repo.

@mtrezza I’ve added this repo to the Server team so you should have write access now.

Thanks Tom, reviewed it and LGTM.

🎉 This change has been released in version 1.2.0


Add an option to load few columns only from HiPSCat

It would be nice if read_hipscat() could load few columns only to reduce I/O and memory usage.

Yep, and I think in general we want to be able to pass kwargs to read_hipscat and pass them on to the pd.read_parquet call


typo in SCT_DIR

there are two "//" in the variable:
SCT_DIR="/usr/local//spinalcordtoolbox"

fixed in commit c5b742236d330cc948415f1722830314922b758f


[ES VCCV] VCC and CC fix + ValidateAlias for "E" semivowel

Some stylistic adjustments.

Seems there are some conflicts with your other merged PRs. Could you rebase?

Oh, I will take a look at that right now.


Fix a misuse of NULL check

Fixes: #17356

I am OK with CLA: trivial.

@kaduk Can you please confirm if you are OK with CLA:trivial?

Yes, I am OK with CLA:trivial

That's fine. Thanks @t8m @kaduk for the approval and discussion.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged to master and 3.0 branches. Thank you for your contribution.


iOS: Fix dev menu sometimes not showing

Summary
RCTDevMenu can get into a state where a UIAlertController is created but
never presented. When in this state, we will never be able to show the
dev menu unless we restart the app.
Changelog
[iOS] [Fixed] - Fix dev menu sometimes not showing
Test Plan
This is a bit difficult to test as I cannot consistently get the
module into this state. It seems to trigger if one randomly shakes the
device while navigating.

cc @hramos

A unit test failed while trying to land this:
	RNTesterUnitTests:
		-[RCTDevMenuTests testShowCreatingActionSheet]

I can now see that this test also failed here on Circle CI, in the test_ios job: https://circleci.com/gh/facebook/react-native/130989?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

Thanks, @hramos. Also discovered that -testClosingActionSheetAfterAction was always succeeding because it's looping over an empty array 😄

This is failing a Unit Test, testViewManagerNotInitializedBeforeSetBridgeModule.

@hramos: This is failing a Unit Test, testViewManagerNotInitializedBeforeSetBridgeModule.

I don't think that's caused by this change. It passes locally after I rebased on latest master.

This one is blocked internally because of this failing unit test:
Failing tests:
	RNTesterUnitTests:
		-[RCTModuleInitTests testCustomInitModuleInitializedAtBridgeStartup]

I've rebased on top of master, but the failure is still there. I don't see why this would fail with these changes. I'll need to investigate a bit more.

This one is blocked internally because of this failing unit test:
Failing tests:
	RNTesterUnitTests:
		-[RCTModuleInitTests testCustomInitModuleInitializedAtBridgeStartup]

I've rebased on top of master, but the failure is still there. I don't see why this would fail with these changes. I'll need to investigate a bit more.

@hramos: This is a different test from before. The previous one was testViewManagerNotInitializedBeforeSetBridgeModule.

@hramos: I'm trying to revive this PR and I still can't figure out why -[RCTModuleInitTests testCustomInitModuleInitializedAtBridgeStartup] fails. I can't reproduce this locally, and I keep seeing other randomly tests fail. They just all seem very flaky to me 😞
Have you had any luck with this?


Cleanup chunked imaging

I'm doing it - we're effectively developing on main. Can't stop me!

Use task_cleanup with caution!! I didn't finish an initial local test and there's an rm -rf in there!