Adding classes to the tether overlay

I'm using Radium and trying to add custom styles to the datepicker. Thankfully I'm using webpack so bundling the css files within the code is a breeze. To add custom styles, I am using the <Style> component of Radium, which injects a Style node within the component's DOM.
I am facing a problem regarding the targeting of styles to the tether overlay which opens up on clicking the input. The <Style> component has a scopeSelector to add custom class to target the styles, but the DatePicker unfortunately does not accept a className for the overlay like it does for the input.
Can you add a prop called overlayClassName or something like that, which adds a class to the overlay too?
Edit: Nevermind, it slipped my mind that I don't even need to specify the scopeSelector :stuck_out_tongue_closed_eyes:  since I want to style ALL the Datepickers anyways.
But maybe it'd be a useful feature to have to scope styles properly?

Hi @kumarharsh,
I had a hard time understanding what you wanted to achieve, but looks like you found it out. All styles are prefixed with `datepicker__ to scope it correctly according to BEM. (See https://github.com/Hacker0x01/react-datepicker/blob/master/src/stylesheets/datepicker.scss). Does this work for you?

Ah, sorry for not being clear.
Basically what I am suggesting is that: would it be viable to add another propType to the datepicker which can add some user-defined class to the datepicker overlay?

What's the class you want to style. Can you provide the current class the overlay has, and is there a reason we should allow custom classes for that overlay?

Right now, there are the classes applied on the Datepicker overlay:
datepicker__container tether-element tether-enabled tether-abutted tether-abutted-left tether-element-attached-top tether-element-attached-left tether-target-attached-bottom tether-target-attached-left
All of them are the ones supplied by tether, except for the datepicker__container which is specific to the picker.
I'm suggesting that you allow a user to also specify a class which can be added to this list, say something like: holiday_picker, workday_picker, etc, so that they can style two pickers differently in the same app. Right now users can have only ONE style for the datepicker overlay per app.
Again, it's just a suggestion, and I don't require it myself anymore because I will not have two different styled overlays in my app.

Right, I get it. So the goal you want to achieve here is to style 2 datepickers differently. IMO, a really specific use case but I'll see if I can work out something.

Let's handle this in #377


APEXCORE-453 decreased the heartbeat interval in the DelayOperator unit test because otherwise the committed window call may occur much later than expected, hence missing the failure simulation

@PramodSSImmaneni  please review and merge

I verified this fix. Tried it 10 times and the test case passed all 10 times.

@sandeepdeshmukh thanks for verifying this fix.

@tweise  done


Databricks on GCP

When using photon, I receive the message queries are not support in photon when I change the timezone in the spark configuration using the java options on the executor and driver. The Databricks team said I need to raise a ticket for this issue.

Could you raise a Databricks support ticket instead? This is not a forum for Databricks issues.


test(e2e): adjust kitchen-sink snapshot

Adjustment of the kitchen-sink snapshot allowing the E2E test to succeed
Refactoring of the GitHub trunk and release-stable workflow

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

npm package (@next-major dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Nested support-library dependency in travis

Honestly, I don't know if it can be considered an issue.
My library doesn't require the support-library, but uses a dependency (Etsy staggered grid) that requires it.
Locally I can build the lib without any problems.
When I build in travis,without calling an explicit sdk-update for the Support library repository, I've a failed build.
> Could not find any version that matches com.android.support:support-v4:19.0.+.

My dependencies:
dependencies {
    compile project(':library')
    compile 'com.etsy.android.grid:library:1.0.4'
}

Log on travis:
Android SDK not found. Downloading...
SDK extracted at '/home/travis/.android-sdk'. Writing to local.properties.
Build tools 19.0.3 missing. Downloading....
Compilation API android-19 missing. Downloading...
Download http://repo1.maven.org/maven2/com/etsy/android/grid/library/1.0.4/library-1.0.4.pom
Relying on packaging to define the extension of the main artifact has been deprecated and is scheduled to be removed in Gradle 2.0
FAILURE: Build failed with an exception.
* Where:
Build file '/home/travis/build/gabrielemariotti/cardslib/build.gradle' line: 31
* What went wrong:
A problem occurred evaluating root project 'cardslib'.
> A problem occurred configuring project ':library-extra'.
   > Could not resolve all dependencies for configuration ':library-extra:_debugCompile'.
      > Could not find any version that matches com.android.support:support-v4:19.0.+.
        Required by:
            com.github.gabrielemariotti.cards:library-extra:1.5.1-SNAPSHOT > com.etsy.android.grid:library:1.0.4
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED

Adding in travis.yml the sdk update for support library/repository it can work.

@gabrielemariotti @JakeWharton Travis supports downloading the Android SDKs in it's own way. Are you still seeing this issue?

@jaredsburrows I am curious about this too, and what impact this library will have on current Travis-ci build.

@IgorGanapolsky Well I do not use this plugin with Travis because you can use the .travis.yml config file.

Right now plugin scans only top level dependencies, listed at the build.gradle.
https://github.com/JakeWharton/sdk-manager-plugin/blob/master/src/main/groovy/com/jakewharton/sdkmanager/internal/PackageResolver.groovy#L272
To understand, that next library has nested child dependency
dependencies {
    compile 'com.etsy.android.grid:library:1.0.4'
}

In general case it is required to make internet connection to the repository to download pom file, for example.
Which means, that plugin wouldn't do local scan anymore and those numbers from the readme
It currently takes about 100ms on average to check all of the above conditions.

may no longer be true. Yes, gradle will do this scan anyway to determine if all dependencies are present for the build and can cache already downloaded values, but do we want to do it at the plugin? May not be obvious why for the plugin users.
Proof of concept is here: https://github.com/JakeWharton/sdk-manager-plugin/pull/98


Consider using named tuples in public and internal APIs

... instead of Item1, Item2 everywhere. :/

What's the syntax for what you are proposing?  I was reading through tuple types documentation for C#, but apparently this isn't correct:  public abstract IEnumerable<(MethodTable: ulong, Token: int)> EnumerateTypeDefToMethodTableMap();.  Or do you mean defining a struct with Deconstruct?

Type declaration is (int Age, string Name).
Instantiation is (1, "foo") or (Age: 1, Name: "Foo")

I think I've found and fixed all instances of this.  Please let me know if you find one I missed.
I've also taken the time to remove the last remaining IReadOnlyList usage which shouldn't have been there.


System.AggregateException: Configuration for CosmosSourceSettings is invalid (ConnectionString must be specified unless UseRbacAuth is true)

Hi Team,
When i used this migration tool after run dmt command given below error.
ConnectionString must be specified unless UseRbacAuth is true
System.AggregateException: Configuration for CosmosSourceSettings is invalid (ConnectionString must be specified unless UseRbacAuth is true)
Thank's
Gopal

As the error states, ConnectionString is a required setting for the extension you're using. Refer to extension documentation for required and optional settings: https://github.com/AzureCosmosDB/data-migration-desktop-tool#extension-documentation


does the densenet support gpu memory effecient implement?

the densenet team give a efficent implement https://github.com/gpleiss/efficient_densenet_pytorch/blob/master/models/densenet.py
does torchvision merge that and offer pretrained model ?

The efficient implementation from the repo you pointed out should not be difficult to implement: from what I understand, it basically uses torch.utils.checkpoint in the DenseLayer. This means that it could probably be added as an extra option, while keeping everything backwards-compatible I'd believe.

@fmassa Can I take this up?

@ekagra-ranjan sure. Make sure everything is backwards-compatible.

@soumith I haven't seen any code which takes care of backward-compatibility. Can you please guide me with this?

you basically have to make sure API calls to the class constructor and forward function work (so if you add any new arguments to a function, they have to come at the end), and old pre-trained models / state_dicts are loadable after the PR.

This was implemented in #797


Exclude slf4j implementation from lets-plot-common

Is it possible to exclude "org.slf4j:slf4j-simple" implementation of SLF4J logger as it's considered to be a bad practice to include concrete implementations for logger API?

This is good point, thanx.

Fixed in Lets-Plot v2.0.3, Lets-Plot Kotlin v3.0.0


❓ 2.8.0 > 2.9.1 - Android build error: JSI_LIB not found

Question
Hi,
I'm attempting to upgrade from RNVC 2.8 > 2.9 and hitting a build error:
Execution failed for task ':react-native-vision-camera:generateJsonModelDebug'.
> C:\dev\MeshMobile\node_modules\react-native-vision-camera\android\CMakeLists.txt : C/C++ debug|arm64-v8a : CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
  Please set them or make sure they are set and tested correctly in the CMake files:
  JSI_LIB
      linked by target "VisionCamera" in directory C:/dev/MeshMobile/node_modules/react-native-vision-camera/android

Observations:

No problems with 2.8.xx.
Seems to only affect 2.9.0 and 2.9.1
I'm not seeing this error when building the example app
Affecting multiple projects (all based on boilerplate provided by npx react-native init ProjectName)

Repo+branch demonstrating the issue here
Full Build Log: rnvc2.9.1-build-error.log
The offending CMakeLists.txt: ~\node_modules\react-native-vision-camera\android\CMakeLists.txt
I'm stumped. Any thoughts on what I'm doing wrong?
What I tried

Read the install instructions
Tested all releases of RNVC from 2.8.0 onwards
Enable/disable hermes in build.gradle
Set compileSdkVersion to 31
Set targetSdkVersion to 31
Add android:exported to main activity
cd android && gradlew clean
Build via npm run android and Android Studio

VisionCamera Version
2.9.0 and 2.9.1
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Thanks for that, all good now.

@D4nt4lion alternatively if you're using yarn 2, you can use yarn patch react-native-vision-camera (docs)

I'm getting same issue even I tried that patch solutions..
Where should I fix?
//package.json
 "react-native": "^0.64.2",
 "react-native-gesture-handler": "^1.10.3",
 "react-native-reanimated": "^2.2.3",
 "react-native-scan-barcode": "^3.1.5",
 "react-native-vision-camera": "^2.9.3",

//build.gradle
buildscript {
    ext {
        buildToolsVersion = "29.0.3"
        minSdkVersion = 26
        compileSdkVersion = 31
        targetSdkVersion = 31
    }
}

errors in terminal
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-vision-camera:externalNativeBuildDebug'.
> Build command failed.
 Error while executing process /Users/yudahye/Library/Android/sdk/cmake/<IP_ADDRESS>88404/bin/ninja with arguments {-C /Users/projectName/node_modules/react-native-vision-camera/android/.cxx/cmake/debug/armeabi-v7a VisionCamera}
 ninja: Entering directory `/Users/projectName/node_modules/react-native-vision-camera/android/.cxx/cmake/debug/armeabi-v7a'
 [1/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JHashMap.cpp.o
 [2/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JImageProxy.cpp.o
 [3/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JFrameProcessorPlugin.cpp.o
 [4/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/CameraView.cpp.o
 [5/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/JSIJNIConversion.cpp.o
 FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/JSIJNIConversion.cpp.o

 ~~
   In file included from ../../../../src/main/cpp/JSIJNIConversion.cpp:15:
 In file included from /Users/projectName/android/../node_modules/react-native/ReactAndroid/src/main/jni/react/jni/NativeMap.h:11:
 ../../../../build/third-party-ndk/folly/folly/dynamic.h:63:10: fatal error: 'boost/operators.hpp' file not found
 #include <boost/operators.hpp>
          ^~~~~~~~~~~~~~~~~~~~~
 1 error generated.
 [6/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCameraScheduler.cpp.o
 [7/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o
 FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o

 ~~
 BUILD FAILED in 19s

   at makeError (/Users/projectName/node_modules/@react-native-community/cli-platform-android/node_modules/execa/index.js:174:9)
   at /Users/projectName/node_modules/@react-native-community/cli-platform-android/node_modules/execa/index.js:278:16
   at processTicksAndRejections (internal/process/task_queues.js:93:5)
   at async runOnAllDevices (/Users/projectName/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:94:5)
   at async Command.handleAction (/Users/projectName/node_modules/react-native/node_modules/@react-native-community/cli/build/index.js:186:9)

Any update on this issue? Still doesn't work on Android.

Any update? 🥲

here is the juicy part about this error
error: redefinition of 'JHashMap'

here is the full error
In file included from ../../../../src/main/cpp/JSIJNIConversion.cpp:25:
../../../../src/main/cpp/java-bindings/JHashMap.h:16:8: error: redefinition of 'JHashMap'
../../../../build/fbjni-0.3.0-headers.jar/fbjni/detail/Iterator.h:170:8: note: previous definition is here
In file included from ../../../../src/main/cpp/java-bindings/JHashMap.cpp:5:
../../../../src/main/cpp/java-bindings/JHashMap.h:16:8: error: redefinition of 'JHashMap'
../../../../build/fbjni-0.3.0-headers.jar/fbjni/detail/Iterator.h:170:8: note: previous definition is here
../../../../src/main/cpp/java-bindings/JHashMap.cpp:15:43: error: redefinition of 'create'
../../../../build/fbjni-0.3.0-headers.jar/fbjni/detail/Iterator-inl.h:230:42: note: previous definition is here

@TheEhsanSarshar update to version 2.9.4 this is solved.

Thank you so much @Hajan39

The only way I was able to fix this issue was updating my react and react-native packages
"react-native": "0.66.3",
"react": "17.0.2",

I used this tool also

Expo SDK 44, Custom Dev Client, I get:
Version: 2.10.0
* What went wrong:
Execution failed for task ':react-native-vision-camera:generateJsonModelDebug'.
> /myapp//node_modules/react-native-vision-camera/android/CMakeLists.txt : C/C++ debug|armeabi-v7a : CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
  Please set them or make sure they are set and tested correctly in the CMake files:
  JSI_LIB
      linked by target "VisionCamera" in directory /myapp//node_modules/react-native-vision-camera/android

still have error when building for Android, any update ?

I am still getting this error too.

I met this kind of Error and solved by uninstall and reinstall react-native-vision-camera.
"react-native-vision-camera": "^2.12.2",
"react-native": "0.67.2",
hermes enabled
* What went wrong:
Execution failed for task ':react-native-vision-camera:externalNativeBuildDebug'.
> Build command failed.
   There's no error here.
Maybe try cleaning everything and making sure your NDK and CMake is installed correctly via Android Studio

Awesome, nice to hear!

[android, didn't check iOS] I'm getting same issue even I tried that patch solutions.. Where should I fix?
//package.json
 "react-native": "^0.64.2",
 "react-native-gesture-handler": "^1.10.3",
 "react-native-reanimated": "^2.2.3",
 "react-native-scan-barcode": "^3.1.5",
 "react-native-vision-camera": "^2.9.3",

//build.gradle
buildscript {
    ext {
        buildToolsVersion = "29.0.3"
        minSdkVersion = 26
        compileSdkVersion = 31
        targetSdkVersion = 31
    }
}

errors in terminal with patch package solution
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-vision-camera:externalNativeBuildDebug'.
> Build command failed.
 Error while executing process /Users/yudahye/Library/Android/sdk/cmake/<IP_ADDRESS>88404/bin/ninja with arguments {-C /Users/projectName/node_modules/react-native-vision-camera/android/.cxx/cmake/debug/armeabi-v7a VisionCamera}
 ninja: Entering directory `/Users/projectName/node_modules/react-native-vision-camera/android/.cxx/cmake/debug/armeabi-v7a'
 [1/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JHashMap.cpp.o
 [2/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JImageProxy.cpp.o
 [3/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/java-bindings/JFrameProcessorPlugin.cpp.o
 [4/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/CameraView.cpp.o
 [5/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/JSIJNIConversion.cpp.o
 FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/JSIJNIConversion.cpp.o

 ~~
   In file included from ../../../../src/main/cpp/JSIJNIConversion.cpp:15:
 In file included from /Users/projectName/android/../node_modules/react-native/ReactAndroid/src/main/jni/react/jni/NativeMap.h:11:
 ../../../../build/third-party-ndk/folly/folly/dynamic.h:63:10: fatal error: 'boost/operators.hpp' file not found
 #include <boost/operators.hpp>
          ^~~~~~~~~~~~~~~~~~~~~
 1 error generated.
 [6/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/VisionCameraScheduler.cpp.o
 [7/10] Building CXX object CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o
 FAILED: CMakeFiles/VisionCamera.dir/src/main/cpp/FrameProcessorRuntimeManager.cpp.o

 ~~
 BUILD FAILED in 19s

   at makeError (/Users/projectName/node_modules/@react-native-community/cli-platform-android/node_modules/execa/index.js:174:9)
   at /Users/projectName/node_modules/@react-native-community/cli-platform-android/node_modules/execa/index.js:278:16
   at processTicksAndRejections (internal/process/task_queues.js:93:5)
   at async runOnAllDevices (/Users/projectName/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:94:5)
   at async Command.handleAction (/Users/projectName/node_modules/react-native/node_modules/@react-native-community/cli/build/index.js:186:9)

errors without patch package solution
* What went wrong:
Execution failed for task ':react-native-vision-camera:generateJsonModelDebug'.
> /Users/yudahye/today/todaypickup_partners/node_modules/react-native-vision-camera/android/CMakeLists.txt : C/C++ debug|armeabi-v7a : CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
  Please set them or make sure they are set and tested correctly in the CMake files:
  JSI_LIB
      linked by target "VisionCamera" in directory /Users/yudahye/today/todaypickup_partners/node_modules/react-native-vision-camera/android

In iOS compiled with success. But in android I'm getting both error, like you. With or without the patch fix

I'm on RN 0.64.2.
After i saw this issue #957 , I've updated the library to v2.13.0 and worked on Android.
But for now, I need to use v2.10.0 for iOS builds (with XCode 12) #716  and v 2.13.0 for android.
I'll try to build with v2.13.0 in iOS with XCode 13.

You must only install C++ sdk to your pc.
For x64: here
For x86: here
and do the following processes respectively:

delete node_modules directory.
delete android/build directory.
delete android/.gradle directory.
delete android/app/build directory
then
run "yarn ios" or "yarn android" command. ( run the project. )


API to query Historical data

Is your feature request related to a problem? Please describe.
we want to do some simple analytics on historical events. Eg: count the number of events where some key in the output JSON has ‘x’ value.
For Cadence, we tried querying Cassandra directly, but it seems it serialized into a thrift binary object. We were able to find the thrift definitions but not sure of the right data structure. We’re able to query from S3 but since we’ve set up archival with retention of 14 days, the events only arrive in S3 after 14 days.
Proposed Solution
Maybe have an API which exposes this data, or a way to export data to a data warehouse.
Additional context
https://community.temporal.io/t/whats-the-best-way-to-do-simple-analytics-on-historical-data/1264

If you already have the workflowID and runID, you can call the GetWorkflowExecutionHistory API directly, it will automatically query archived history if it can't find the workflow history in Cassandra.
If you don't have workflowID and runID, you can get those info from ElasticSearch or visibility archival. Visibility archival happens after workflow closes instead of the retention period, so data will be available soon after the workflow closes.

@yycptt Thanks for the response.
what if we want to build dashboards based on the results of events? should we use the API to query the data or directly read the DB (either batched or CDC) and process them to feed the dashboards?

@yycptt Thanks for the response.
what if we want to build dashboards based on the results of events? should we use the API to query the data or directly read the DB (either batched or CDC) and process them to feed the dashboards?

what if we want to build dashboards based on the results of events?

Those metrics are already emitted by Cadence server. See the bottom of Client dashboard/monitor in https://docs.google.com/document/d/1tQyLv2gEMDOjzFibKeuVYAA4fucjUFlxpojkOMAIwnA/edit#
It will be moved to cadence-docs soon.

what if we want to build dashboards based on the results of events?

Those metrics are already emitted by Cadence server. See the bottom of Client dashboard/monitor in https://docs.google.com/document/d/1tQyLv2gEMDOjzFibKeuVYAA4fucjUFlxpojkOMAIwnA/edit#
It will be moved to cadence-docs soon.

@slayerjain We don't recommend looking into history events except for debugging purposes. These are implementation details of Cadence and can change in later released.
You should be able to emit these metrics in your workflows.


[FEATURE/PR] flowise full deployment with kamal; development with vs code devcontainer

Hi there,
I am deploying flowise with Kamal (https://github.com/basecamp/kamal) on a cheap Hetzner machine (Ubuntu 24.04 LTS, ARM64, 4 cores) with docker.
Works great! Thank you everyone for developing and supporting flowise!
In order to get it to work with kamal healthchecks and vs code devcontainers and I made the following small changes to the standard flowise dockerfile:
# Install curl, kamal uses curl for traefik healthchecks
RUN apk add --no-cache curl
# Install Git, to make developers life easier in vs code devcontainers
RUN apk add --no-cache git

Is anyone here interested in a full kamal deploy.yml for flowise, which includes

remote bullder for arm64
automatic letsencrypt SSL with redirect
persistant volumes
environment variables, auth
healthchecks

I am using vs code and have a working devcontainer.json for flowise.
I also would like to deploy local kamal accessories for redis memory, unstructured.io and qdrant vector store as the next step.
Maybe this config could become part of the repository/readme to make flowise deployment easier?
I would be willing to make a PR with some examples. Let me know what you think.
Christian

absolutely 💯  here's our docs - https://github.com/FlowiseAI/FlowiseDocs, feel free to make a PR for that!

Thank you @HenryHengZJ  for your feedback. Will do it, give me a few days.


fix: Expose react/preact on mobile

This is needed for the cozy-bar to work on mobile.

 (2) Mettre à jour webpack


beautify is not working

Description
The results of beautification are not what I expect.
Input Before Beautification
This is what the code looked like before:
<INSERT CODE HERE>

Expected Output
The beautified code should have looked like this:
<INSERT CODE HERE>

Actual Output
The beautified code actually looked like this:
<INSERT CODE HERE>

Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code does not look right!

Debug
Here is a link to the debug.md Gist:
Checklist
I have:

[ ] Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[ ] Reloaded (or restarted) Atom to ensure it is not a caching issue
[ ] Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[ ] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[ ] Generated debugging information by executing Atom Beautify: Help Debug Editor command in Atom and added link for debug.md Gist to this issue

@vm1990 ignore the probot-no-response bot, it's not working properly.  But we do need a lot more information to investigate.  Please follow the instructions from the issue-complete bot.

Please follow the issue template provided. More specifically, update the original comment for this issue by adding a link to the required debug.md gist which includes debugging information that answers our most commonly asked questions. Thank you.


Godot 4 editor crash on Ubuntu 20.0.4 on project load without error message

Godot version
4.0 beta 10
System information
Ubuntu <IP_ADDRESS>
Issue description
When starting the engine and loading any project (also when creating a new one), the editor crashes before the loading is complete (while the Godot splash screen is shown). The console does not show any error, the crash occurs shortly after the blend file import warning.
Even in verbose mode, I did not find any error.
I tried running almost all Godot 4 betas. Every one crashed on project load, some even sooner. Then I cloned Godot and compiled it. I tried to debug, with little success. The call stack shows that some Thread llvmpipe-3 has a Segementation fault, but with "Unkown source", so I don't know where exactly it is coming from.
This can be related to #68043 or #59318, since I also get the error /lib/x86_64-linux-gnu/libasound.so.2: undefined symbol: snd_dlpath on starting the launcher, but with the args --audio-driver Dummy the error disappears but the crash still occurs.
Steps to reproduce

Be daring enough to use Linux (Ubuntu 20.0.4)
Download Godot 4 beta 10 and create new project
Watch the Editor crash
Become sad and go back to using Windows

Minimal reproduction project
Any empty project

I am running Ubuntu 20.04.5 LTS.
Are you trying to run the Mono version?  Mine would crash using Mono and I had to run the binary in the terminal window to get the correct error message.  I was missing a directory or something, but chasing down that error message is what got the Mono version of Godot running for me.  I am running Godot Mono v4.0b10 just fine now,

I think I fixed it. My graphics card does not support Vulkan, so running the engine with --rendering-driver opengl3 lets the engine run, finally! Will update thread name accordingly.
(I found this out by installing Windows on another drive on this PC, where it then shows the error message)

Duplicate of https://github.com/godotengine/godot/issues/58927.


feature request: Find a way to extend the spectral default ruleset without installing it local

To extend the @ibm-cloud/openapi-ruleset in the spectral-file, it is necessary to install the ruleset into the project which is checked. (see also the customization documentation)
An extension of the default spectral ruleset spectral:oas can be done without any local installation.
It would be nice to be able to extend the default ibm ruleset without having to run npm install @ibm-cloud/openapi-ruleset especially if rules only needs to be disabled and the users want to run the checks in a container based environment.
Resolving of the upstream included rules is done in spectral's extends.ts.
I'm not experienced enough in typescript to find out how this can be done. This may even need a upstream patch first to be able to register custom rulesets to be able to extend them later.

Hey @Blaimi, thanks for the issue. I very much understand the desire for this feature so I spent some time on Friday investigating how we might approach it but unfortunately, I don't believe it can be done.
Spectral performs this lookup in their own code and there isn't a plugin point for us to be able to add ours. They can give special treatment to their own ruleset by bundling it, like you mentioned.

This may even need a upstream patch first to be able to register custom rulesets to be able to extend them later.

This would probably be the only realistic avenue - getting Spectral to add a feature to support this - but I doubt it would be trivial and I don't know what the priority would be on their end. They seem to have intentionally solved the custom ruleset loading by relying on NPM or local file systems.
So, right now, the only way around a separate dependency is to use the ruleset installed with the validator in your local file system like so:
extends<EMAIL_ADDRESS>
I'm going to close, as we're not able to put additional work into this at the moment.


Rename AssignmentNormalizer to NormalizeAssignments

Closes #115

Codecov Report

Merging #120 (e01b7cb) into main (30428c1) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Current head e01b7cb differs from pull request most recent head 32732fb. Consider uploading reports for the commit 32732fb to get more accurate results

@@           Coverage Diff           @@
##             main     #120   +/-   ##
=======================================
  Coverage   97.01%   97.02%
=======================================
  Files          24       24
  Lines        1241     1242    +1
=======================================
+ Hits         1204     1205    +1
  Misses         37       37

Impacted Files
Coverage Δ

robotidy/transformers/__init__.py
94.73% <ø> (ø)

robotidy/transformers/NormalizeAssignments.py
100.00% <100.00%> (ø)

robotidy/utils.py
96.24% <100.00%> (+0.02%)
:arrow_up:

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 30428c1...32732fb. Read the comment docs.


VmwareStorageLayoutHelper throws StackOverflowError fix

The static method syncVolumeToRootFolder() from VmwareStorageLayoutHelper.java:146 has been incorrectly called and leads to an infinite recursive call that ends up in a StackOverflowError. This PR fixes this.
    public static void syncVolumeToRootFolder(DatacenterMO dcMo, DatastoreMO ds, String vmdkName, String vmName) throws Exception {         syncVolumeToRootFolder(dcMo, ds, vmdkName, null);     } ->     public static void syncVolumeToRootFolder(DatacenterMO dcMo, DatastoreMO ds, String vmdkName, String vmName) throws Exception {         syncVolumeToRootFolder(dcMo, ds, vmdkName, vmName, null);     }
Description

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Screenshots (if appropriate):

How Has This Been Tested?

@anuragaw @rafaelweingartner @DaanHoogland @GabrielBrascher please have a look at this.

@SudharmaJain please review

@blueorangutan package

@dhlaluku a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2498

@blueorangutan test centos7 vmware-65

@dhlaluku a Trillian-Jenkins test job (centos7 mgmt + vmware-65) has been kicked to run smoke tests

@blueorangutan test centos7 vmware-65

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-65) has been kicked to run smoke tests

Trillian test result (tid-3268)
Environment: vmware-65 (x2), Advanced Networking with Mgmt server 7
Total time taken: 29378 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3105-t3268-vmware-65.zip
Intermittent failure detected: /marvin/tests/smoke/test_multipleips_per_nic.py
Intermittent failure detected: /marvin/tests/smoke/test_outofbandmanagement.py
Intermittent failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Smoke tests completed. 68 look OK, 2 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_nic_secondaryip_add_remove
Error
73.92
test_multipleips_per_nic.py

test_04_rvpc_network_garbage_collector_nics
Failure
531.86
test_vpc_redundant.py

LGTM, @dhlaluku since this is a bugfix do you think 4.11 can benefit from it?


IndexError: list index out of range in CustomControlTowerStateMachineLambda lambda function

Describe the bug
Encountered "IndexError: list index out of range" when accounts are provisioned to a previously empty OU and there are stack_set resources defined in the manifest.yaml targetted to the OU.
To Reproduce

Set up Control Tower
Create a new OU (for example "TEST")
Deploy CfCT
Update manifest to deploy a valid stack set to the "TEST" OU and upload the manifest file to s3 bucket (the CfCT pipeline and Step Functions are working fine when the OU is still empty)
Provision a new account to "TEST" OU, Step Functions execution for the stackset instance is executed but failed at "CustomControlTowerStateMachineLambda"

Expected behavior
CfCT creates stackset instances successfully
Please complete the following information about the solution:

2.70 version
[ ap-northeast -1 ] Region: [e.g. us-east-1]
[ no ] Was the solution modified from the version published on this repository?
[ ] If the answer to the previous question was yes, are the changes available on GitHub?
[yes ] Have you checked your service quotas for the sevices this solution uses?
[ yes ] Were there any errors in the CloudWatch Logs?

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context
Log messages from CloudWatch Logs of the Lambda function
{
    "time_stamp": "2024-03-08 11:29:29,334",
    "log_level": "INFO",
    "log_message": {
        "RequestType": "Create",
        "ResourceProperties": {
            "StackSetName": "CustomControlTower-xxxxxxx-stackset",
            "TemplateURL": "https://customizedforcontrotowers-customcontroltowerpipeli-xxxxxxxx.s3.ap-northeast-1.amazonaws.com/_custom_ct_templates_staging/templates/backstage_cross_account_roles.yaml",
            "Capabilities": "[\"CAPABILITY_NAMED_IAM\",\"CAPABILITY_AUTO_EXPAND\"]",
            "Parameters": {
                "BackstageAccountId": "xxxxxxx",
                "BackstageStepFunctionsServiceProvisionRoleName": "xxxxxxx",
                "BackstageStepFunctionsAccountProvisionRoleName": "xxxxxxx",
                "SharedBackstagePortfolioId": "xxxxxxx"
            },
            "AccountList": [
                "<AccountId1>",
                "<AccountId2>",
                "<AccountId3>",
                "<AccountId4>",
                "<AccountId5>"
            ],
            "RegionList": [
                "ap-northeast-1"
            ],
            "SSMParameters": {}
        },
        "SkipUpdateStackSet": "yes",
        "params": {
            "ClassName": "CloudFormation",
            "FunctionName": "list_stack_instances"
        },
        "LoopFlag": "not-applicable",
        "StackSetExist": "yes",
        "StackInstanceAccountList": []
    }
}

Input StackInstanceAccountList is an empty list. However, the code checks only if the StackInstanceAccountList is not None, and tries to access the first account ID in the empty list which cause an error.
I manually added a stack instance (via console) to one of the target accounts, then trigger the pipeline again, the Step Functions execution is working fine.

@pimpuks thank you for reporting the bug and providing the context.
I have created an internal backlog to address this edge case and bug.

We hit the same bug. As no contributions are accepted, if anyone is reading this, we fixed it by changing the following code:
diff --git a/source/src/cfct/state_machine_handler.py b/source/src/cfct/state_machine_handler.py
index 961a747..30e65c2 100644
--- a/source/src/cfct/state_machine_handler.py
+++ b/source/src/cfct/state_machine_handler.py
@@ -223,7 +223,7 @@ class CloudFormation(object):
                 # to trigger create operation accordingly.
                 if (
                     not response.get("Summaries")
-                    and self.event.get("StackInstanceAccountList") is None
+                    and (self.event.get("StackInstanceAccountList") is None or not self.event.get("StackInstanceAccountList"))
                 ):
                     self._set_only_create_stack_instance_operation()
                     return self.event

This seems to be a fatal flaw in getting started, is there any way to use CfCT with this bug in place on a new set up?  @snebhu3 is there any guidance on how to get any implementation to work in a new configuration without forking this repository?
I don't fully understand @pimpuks solution:

I manually added a stack instance (via console) to one of the target accounts, then trigger the pipeline again, the Step Functions execution is working fine.

How (and where) do I add this stack instance?  Is there a handy no-op stack that will work?


How can I import a class field type definition?

I have installed Flow type definitions for ExpressJS (https://github.com/flow-typed/flow-typed/blob/master/definitions/npm/express_v4.16.x/flow_v0.32.x-/express_v4.16.x.js).
I have a function that accepts a single argument (the query property of express$Request - line 33). How can I import just that particular type (e.g. as queryType) to type my function (e.g. function foo(query: queryType) { ... }?
Currently, I declared a queryType by copying and pasting the definition, but this is obviously undesirable because I have to manually update the type definition should express$Request change in the future.

type Query = $PropertyType<express$Request, 'query'>

// or:

type Query = $PropertyType<typeof myRequest, 'query'>

?

I'll look into that, thanks!
Also, I apologize for the wrong forum :)


[Event Change Request] Table 36 Sales Header - Field "Bill-to City"

Dear ALAppExtensions Team,
We would like to request the following change
field(9; "Bill-to City"; Text[30])
{
    Caption = 'Bill-to City';
    TableRelation = IF ("Bill-to Country/Region Code" = CONST('')) "Post Code".City
    ELSE
    IF ("Bill-to Country/Region Code" = FILTER(<> '')) "Post Code".City WHERE("Country/Region Code" = FIELD("Bill-to Country/Region Code"));
    //This property is currently not supported
    //TestTableRelation = false;
    ValidateTableRelation = false;

    trigger OnLookup()
    begin
        OnBeforeLookupBillToCity(Rec, PostCode);

        PostCode.LookupPostCode("Bill-to City", "Bill-to Post Code", "Bill-to County", "Bill-to Country/Region Code");

         **//--> change request new "xRec" parameter
         OnAfterLookupBillToCity(Rec, xRec, PostCode);
         //<-- change request**
    end;

    trigger OnValidate()
    begin
        PostCode.ValidateCity(
          "Bill-to City", "Bill-to Post Code", "Bill-to County", "Bill-to Country/Region Code", (CurrFieldNo <> 0) and GuiAllowed);
        **//--> change request
        OnAfterValidateBillToCity(Rec, xRec);
        //<-- change request**
        ModifyBillToCustomerAddress;
    end;
}

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 46009.


Fix keras.ops.repeat cannot return an expected shape when x is a …

…KerasTensor and the axis is None
Treat an input vector of size 1 as a scalar. Make the behavior consistent with other backends.
Closes #19821

Codecov Report
Attention: Patch coverage is 88.23529% with 2 lines in your changes missing coverage. Please review.

Project coverage is 56.63%. Comparing base (2305fad) to head (3b7be3d).
Report is 3 commits behind head on master.

Files
Patch %
Lines

keras/src/ops/numpy.py
88.23%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #19826      +/-   ##
==========================================
+ Coverage   56.52%   56.63%   +0.10%
==========================================
  Files         498      498
  Lines       45801    45813      +12
  Branches     8440     8443       +3
==========================================
+ Hits        25890    25947      +57
+ Misses      18330    18282      -48
- Partials     1581     1584       +3

Flag
Coverage Δ

keras
56.63% <88.23%> (+0.10%)
:arrow_up:

keras-numpy
56.63% <88.23%> (+0.10%)
:arrow_up:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Refactor metrics

Use metrics.Event structures
Populate from existing Prometheus events

Coverage decreased (-0.8%) to 14.134% when pulling ef6d0f633208c871f9dc6fa58fb0f8b825314559 on raphink:metrics_structs into 3b66c2ac840707dc620a65dbe9d15c87ff0d2be2 on camptocamp:master.

Coverage decreased (-0.8%) to 14.134% when pulling c5ee7e0b0bff5433d7f12962bca608c0527243f7 on raphink:metrics_structs into 3b66c2ac840707dc620a65dbe9d15c87ff0d2be2 on camptocamp:master.

Please split into 2 commits : metrics refactoring and new feature (getting existing metrics)

Coverage decreased (-0.8%) to 14.134% when pulling b92ffbb4a7930a632549af08ed374f25366580f1 on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.8%) to 14.134% when pulling 015e42fb0ffb28104734ce5628c37f34d601fada on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.8%) to 14.134% when pulling 72ae63152884b8b3476a54d1465b23872392d0f1 on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.9%) to 14.068% when pulling 20baeb20d355ed796a64ddaa57e6f93d775daba9 on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.9%) to 14.068% when pulling 95c0ec5cc76cc42cb7fabd00b3c83b010059fbb2 on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.9%) to 14.068% when pulling 95c0ec5cc76cc42cb7fabd00b3c83b010059fbb2 on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.9%) to 14.068% when pulling f6969a0136df014b8471bda78b6ddb66a81041f3 on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.7%) to 14.235% when pulling e56c4952337b13031bf2576eb9ae3e4288740b1e on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.4%) to 14.581% when pulling e56c4952337b13031bf2576eb9ae3e4288740b1e on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.4%) to 14.581% when pulling df57e726f918300b0f0155f8acfb8c706efee7a9 on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.4%) to 14.581% when pulling 470316dac74eacbe1f631d657ba72c2dcb7e948f on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.4%) to 14.581% when pulling 967ec4314a67ff131f7984f35885ce985ca21191 on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.4%) to 14.545% when pulling 2f1f05e403afbb8adaa3f379bc6b34da13e13186 on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Merged

Coverage decreased (-0.4%) to 14.545% when pulling b1dfd6902b62784edcac047f1c94cb7b4bfd67f1 on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.

Coverage decreased (-0.4%) to 14.545% when pulling b1dfd6902b62784edcac047f1c94cb7b4bfd67f1 on raphink:metrics_structs into 82684ee9ba88c2247d6998dc58ff8b669ae95914 on camptocamp:master.


field-required="true" not working as expected in case of multiple controls inside a form

When there are multiple angucomplete controls inside the same form, upon validating the whole form, the directive is adding autocomplete-required to the required form.$error.
But when we select value in one of the controls, directive is removing autocomplete-required without checking the status of the other autocomplete controls. This is creating a problem while validating the controls.

Have a look at this one.
https://github.com/ghiden/angucomplete-alt/issues/192
You need to provide class name when you use more than one directive.
I'll update README about this.
Sorry for the confusion.

In your example in http://plnkr.co/edit/aeB28M the "field-required-class" is not added to the input but onle the wrappers but in your on your example page https://ghiden.github.io/angucomplete-alt/#example8 it works fine. Is this a bug?

field-required-class is an optional field to change the class name. But the example 8 looks like it should say "true" instead. It takes any truthy value for field-required so it works. I probably copied the old example and wanted to use it as field-required-class to distinguish 2 fields. I'll fix it.

@ghiden Actually its not what i mean :)
What i mean is that in my website the error classname specified in the attribute field-required-class is not added to the input. I have use several hours to solve the problem and found the source of the bug.
If you see this plunker http://plnkr.co/edit/xobmxNjbJSc7ahMAiCnz you can inspect the dom and see the error class is not added to the input. But if you remove the ngAnimate plugin from the module list in the app file the classname is added. Do you agree?

ng-invalid-country and ng-invalid-sports added. You are not seeing this?

No the classes is not added to the  tag.
See pictures:
Works fine: http://oi68.tinypic.com/2res51z.jpg
Dont work: http://oi65.tinypic.com/2dbqwwy.jpg

I see but I don't think it's about ng-animate.
Once you select something, it works.
Probably I'm not checking the validity when it is loaded.
Reopening this.
Thanks @TommySorensen

@ghiden But if you are not checking the validity when its loaded I have no chance to style the input with some kind of "unvalid"  styling.
In my case I need to know what inputs are unvalid when the user clicks submit without typing anything into the form. But the autocomplete field is the only field i cannot catch by the classname ng-unvalid or your custom invalid classname

@TommySorensen It looks like it is ng-animate as you investigated.
My code is doing what is supposed to do.
I think it is blocking class name to be written in some way.
I don't have any other way but removing it to make it work for now.

@ghiden Any progress with the bug?

@TommySorensen I labeled it as a bug but I don't think I can do anything about this.
It's ngAnimate that is blocking class name to be written.

If anyone is still struggling with this, just do interpolation on the input-class property.
Example: <angucomplete-alt input-name="firstName" input-class="my-class {{form.firstName.$error['autocomplete-required'] ? 'my-class-with-error' : ''}}"/>

field-required="true" doesn't prevent the form from getting submitted like<select required /> because it doesn't add required to the generated <input> control. Is there a way around this?

@ghiden
In my case for some reason the 'autocomplete-required' error is put only on the form but not on the input. Am I missing something?
This doesn't set the error class:
<form name="form">
  Foo
  <angucomplete input-name="type" field-required="true">
</form>

This does set it:
<form name="form">
  Foo
  <angucomplete input-name="type" field-required="true">
</form>

In addition - the required attribute doesn't propagate to the input field, which means that now there's no native error message. I really need it since the UX for error messages in all of our app is consistently native. Is there a way to overcome this? Can you consider propagating the required field to the input? IMHO that's the expected behaviour.

Hi, @krulik! I solved this issue with additional directive like this:
`directive('validForm', [ '$rootScope', function ($rootScope) {
return {
restrict: 'A',
link: function (scope, elem) {
elem.on('submit', function () {
                    var autoComplete = elem[0].querySelectorAll('[field-required="true"]');
                    autoComplete.forEach(function (val) {
                        var input = val.querySelector('input');
                        if(input.value === '') {
                            input.classList.add("ng-invalid");
                        }
                    });

                    var firstInvalid = elem[0].querySelector('.ng-invalid');

                    if (firstInvalid) {
                        $rootScope.modal.open({
                            templateUrl: '/views/partials/modals/form-error.html'
                        });
                        return firstInvalid.focus();
                    }
                });
            }
        };
    }]);`


SuperBuild hangs on cloning elastix repository (OSX)

Seems like the build hangs on cloning the elastix repository. Not sure where I have to look to fix this. Could be a server side issue.
Any pointers are appreciated (and thanks for putting this toolbox together!!!)

I have previously had problems building on hospital networks because the git protocol is blocked. You can check ELASTIX_REPOSITORY_URL CMake variable to see if it is git or https. Change to https if necessary. If this doesnt work you can download elastix yourself, compile as a library, and set USE_SYSTEM_ELASTIX CMake variable to ON.

Thanks, will try!

I added .git to the url at ELASTIX_REPOSITORY_URL, this seems to have fixed it (I think, didn't track the breakpoint but it's still running after a good while). Will keep you posted when it finishes.

bailed on a rather indescript:
make[3]: *** [all] Error 2
make[2]: *** [SimpleITK-prefix/src/SimpleITK-stamp/SimpleITK-build] Error 2
make[1]: *** [CMakeFiles/SimpleITK.dir/all] Error 2
make: *** [all] Error 2
Will try to build on linux, will probably be a bit more stable...

Same issue as @khufkens, did you solve this issue?
[ 67%] Built target SimpleITKTclsh make[3]: *** [all] Error 2 make[2]: *** [SimpleITK-prefix/src/SimpleITK-stamp/SimpleITK-build] Error 2 make[1]: *** [CMakeFiles/SimpleITK.dir/all] Error 2 make: *** [all] Error 2

Can you run it in just a single thread (i.e. no -j4 or similar)? Then it becomes easier to see exactly where it breaks

On linux (Ubuntu 14.04) I can't even get past the initial download phase.
With this error. Rather strange as Curl is up to date.
log: Protocol "https" not supported or disabled in libcurl

Thank you @kaspermarstal , then I used make -j1
The error information lists below, I worked on Mac OS 10.12.3 using Apple clang-8<IP_ADDRESS>, Python 2.7.12 :: Anaconda 4.2.0 (x86_64)
[ 34%] Built target SimpleITK_PYTHON
Scanning dependencies of target PythonVirtualEnv
[ 34%] Creating python virtual enviroment...
Already using interpreter /Users/yxcheng/Software/anaconda/bin/python
Not deleting /Users/yxcheng/GitRepos/build/SimpleITK-build/Testing/Installation/PythonVirtualenv/bin
New python executable in /Users/yxcheng/GitRepos/build/SimpleITK-build/Testing/Installation/PythonVirtualenv/bin/python
Installing setuptools, wheel...
Complete output from command /Users/yxcheng/GitRe...irtualenv/bin/python - setuptools wheel:
Traceback (most recent call last):
File "", line 4, in
File "/Users/yxcheng/Software/anaconda/lib/python2.7/tempfile.py", line 32, in
import io as _io
File "/Users/yxcheng/Software/anaconda/lib/python2.7/io.py", line 51, in
import _io
ImportError: dlopen(/Users/yxcheng/GitRepos/build/SimpleITK-build/Testing/Installation/PythonVirtualenv/lib/python2.7/lib-dynload/_io.so, 2): Symbol not found: __PyCodecInfo_GetIncrementalDecoder
Referenced from: /Users/yxcheng/GitRepos/build/SimpleITK-build/Testing/Installation/PythonVirtualenv/lib/python2.7/lib-dynload/_io.so
Expected in: flat namespace
in /Users/yxcheng/GitRepos/build/SimpleITK-build/Testing/Installation/PythonVirtualenv/lib/python2.7/lib-dynload/_io.so
...Installing setuptools, wheel...done.
CMake Error at PythonVirtualEnvInstall.cmake:40 (message):
Creation of Python virtual enviroment failed.
Traceback (most recent call last):
File "/Users/yxcheng/GitRepos/build/virtualenv/virtualenv.py", line 2332, in <module>
  main()
File "/Users/yxcheng/GitRepos/build/virtualenv/virtualenv.py", line 711, in main
  symlink=options.symlink)
File "/Users/yxcheng/GitRepos/build/virtualenv/virtualenv.py", line 944, in create_environment
  download=download,
File "/Users/yxcheng/GitRepos/build/virtualenv/virtualenv.py", line 900, in install_wheel
  call_subprocess(cmd, show_stdout=False, extra_env=env, stdin=SCRIPT)
File "/Users/yxcheng/GitRepos/build/virtualenv/virtualenv.py", line 795, in call_subprocess
  % (cmd_desc, proc.returncode))

OSError: Command /Users/yxcheng/GitRe...irtualenv/bin/python - setuptools
wheel failed with error code 1
make[5]: *** [Testing/Installation/PythonVirtualenv/bin/python] Error 1
make[5]: *** Deleting file `Testing/Installation/PythonVirtualenv/bin/python'
make[4]: *** [Wrapping/Python/CMakeFiles/PythonVirtualEnv.dir/all] Error 2
make[3]: *** [all] Error 2
make[2]: *** [SimpleITK-prefix/src/SimpleITK-stamp/SimpleITK-build] Error 2
make[1]: *** [CMakeFiles/SimpleITK.dir/all] Error 2
make: *** [all] Error 2

Try to type hash -r python as outlined in this stackoverflow thread. Otherwise try googling the error. This like an issue related to your local python configuration and it is difficult for me to debug from afar I am afraid.

Another user just reported that he had the same problem, that it was caused by anaconda, and when using the default python installation everything installed smoothly

Closing. This has been fixed.
Feel free to reopen you run into this issue again.


fix tf parsing errors

What type of PR is this?
/kind bug

Special notes for your reviewer:
fix tf parsing errors
Does this PR introduce a user-facing change?

none

Additional documentation e.g., design docs, usage docs, etc.:

none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.1%) to 72.287%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/engine/runtime/terraform/tfops/tferrors.go
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/engine/runtime/terraform/tfops/tferrors.go
1
82.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
4677

Relevant Lines:
6470

💛  - Coveralls