Generate-Android: fatal error: stdlib.h: No such file or directory

Following the C/Java procedure in the Contributing page I have the following error in my mac:

Executing task: Generate-Android
Executing: mono --debug build/lib/Release/Embeddinator-4000.exe  -verbose -gen=Java -out=build/lib/Release/android -platform=Android -compile tests/managed/android/bin/Release/managed.dll
Executing: mono --debug build/lib/Release/Embeddinator-4000.exe  -verbose -gen=Java -out=build/lib/Release/android -platform=Android -compile tests/managed/android/bin/Release/managed.dll
Parsing assemblies...
Parsed 'managed.dll'
Processing assemblies...
Pass 'Embeddinator.Passes.CheckReservedKeywords'
Pass 'Embeddinator.Passes.GenerateObjectTypesPass'
Pass 'Embeddinator.Passes.GenerateArrayTypes'
Pass 'CppSharp.Passes.CheckIgnoredDeclsPass'
Property 'Null' was ignored due to ignored decl
Function 'new' was ignored due to ignored param
Function 'GetBaseException' was ignored due to ignored return decl
Function 'GetObjectData' was ignored due to ignored param
Function 'GetType' was ignored due to ignored return decl
Function 'GetObjectData' was ignored due to ignored param
Function 'GetBaseException' was ignored due to ignored return decl
Function 'GetObjectData' was ignored due to ignored param
    ### removed other similar warnings ###

    Function 'remove_SystemUiVisibilityChange' was ignored due to ignored param
    Function 'add_Touch' was ignored due to ignored param
    Function 'remove_Touch' was ignored due to ignored param
    Function 'add_FocusChange' was ignored due to ignored param
    Function 'remove_FocusChange' was ignored due to ignored param
    Function 'new' was ignored due to ignored return decl
    Function 'ToLocalJniHandle' was ignored due to ignored return decl
    Function 'SetJniIdentityHashCode' was ignored due to ignored param
    Function 'SetJniManagedPeerState' was ignored due to ignored param
    Function 'SetPeerReference' was ignored due to ignored param
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Implicit' was ignored due to ignored return decl
    Function 'op_Explicit' was ignored due to ignored return decl
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'op_Explicit' was ignored due to ignored param
    Function 'Equals' was ignored due to ignored param
    Function 'Wait' was ignored due to ignored param
    Function 'Wait' was ignored due to ignored param
    Property 'Handle' was ignored due to ignored decl
    Function 'ToLocalJniHandle' was ignored due to ignored return decl
    Property 'KeyHandle' was ignored due to ignored decl
    Property 'IsProxy' was ignored due to ignored decl
    Property 'NeedsActivation' was ignored due to ignored decl
    Function 'SetJniIdentityHashCode' was ignored due to ignored param
    Function 'SetPeerReference' was ignored due to ignored param
    Function 'SetJniManagedPeerState' was ignored due to ignored param
    Property 'JniIdentityHashCode' was ignored due to ignored decl
    Property 'PeerReference' was ignored due to ignored decl
    Property 'JniPeerMembers' was ignored due to ignored decl
    Property 'JniManagedPeerState' was ignored due to ignored decl
    Property 'KeyHandle' was ignored due to ignored decl
    Property 'IsProxy' was ignored due to ignored decl
    Property 'NeedsActivation' was ignored due to ignored decl
    Property 'JniIdentityHashCode' was ignored due to ignored decl
    Property 'PeerReference' was ignored due to ignored decl
    Property 'JniPeerMembers' was ignored due to ignored decl
    Property 'Handle' was ignored due to ignored decl
    Property 'ThresholdClass' was ignored due to ignored decl
    Property 'ThresholdType' was ignored due to ignored decl
    Property 'JniManagedPeerState' was ignored due to ignored decl
    Property 'class_ref' was ignored due to ignored decl
    Property 'Class' was ignored due to ignored decl
    Function 'InvalidateDrawable' was ignored due to ignored param
    Function 'ScheduleDrawable' was ignored due to ignored param
    Function 'UnscheduleDrawable' was ignored due to ignored param
    Function 'SendAccessibilityEvent' was ignored due to ignored param
    Function 'SendAccessibilityEventUnchecked' was ignored due to ignored param
    Function 'OnKeyDown' was ignored due to ignored param
    Function 'OnKeyLongPress' was ignored due to ignored param
    Function 'OnKeyMultiple' was ignored due to ignored param
    Function 'OnKeyUp' was ignored due to ignored param
    Field 'View::AccessibilityLiveRegionAssertive' was ignored due to ignored type '::Android_Views_AccessibilityLiveRegion'
    Field 'View::AccessibilityLiveRegionNone' was ignored due to ignored type '::Android_Views_AccessibilityLiveRegion'
    Field 'View::AccessibilityLiveRegionPolite' was ignored due to ignored type '::Android_Views_AccessibilityLiveRegion'
    Field 'View::DragFlagGlobal' was ignored due to ignored type '::Android_Views_DragFlags'
    Field 'View::DragFlagGlobalPersistableUriPermission' was ignored due to ignored type '::Android_Views_DragFlags'
    Field 'View::DragFlagGlobalPrefixUriPermission' was ignored due to ignored type '::Android_Views_DragFlags'
    Field 'View::DragFlagGlobalUriRead' was ignored due to ignored type '::Android_Views_DragFlags'
    Field 'View::DragFlagGlobalUriWrite' was ignored due to ignored type '::Android_Views_DragFlags'
    Field 'View::DragFlagOpaque' was ignored due to ignored type '::Android_Views_DragFlags'
    Field 'View::FindViewsWithContentDescription' was ignored due to ignored type '::Android_Views_FindViewsWith'
    Field 'View::ImportantForAccessibilityAuto' was ignored due to ignored type '::Android_Views_ImportantForAccessibility'

    ### removed other similar warnings ###

    Function 'new' was ignored due to ignored return decl
    Function 'StartActivity' was ignored due to ignored param
    Function 'new' was ignored due to ignored return decl
    Function 'FindApplicationName' was ignored due to ignored return decl
    Function 'FindThisIsCaps' was ignored due to ignored return decl
    Property 'Hello' was ignored due to ignored decl
    Property 'LibraryName' was ignored due to ignored decl
    Property 'ApplicationName' was ignored due to ignored decl
    Property 'ThisIsCaps' was ignored due to ignored decl
    Function 'new' was ignored due to ignored return decl
    Function 'CreateClient' was ignored due to ignored return decl
Pass 'Embeddinator.Passes.FieldToGetterSetterPropertyPass'
    Property created from field: 'Interfaces_Conflicted_TestField'
    Property created from field: 'Arrays_ValueType_IntValue'
    Property created from field: 'NestedClasses_NestedClass_X'
    Property created from field: 'NestedClasses_NestedClass_Y'
    Property created from field: 'NestedClasses_NestedClass_Sum'
    Property created from field: 'Structs_Point_Zero'
    Property created from field: 'Fields_Class_MaxLong'
    Property created from field: 'Fields_Class_Scratch'
    Property created from field: 'Fields_Class_Integer'
    Property created from field: 'Fields_Class_Boolean'
    Property created from field: 'Fields_Class_Structure'
    Property created from field: 'Fields_Struct_Empty'
    Property created from field: 'Fields_Struct_Scratch'
    Property created from field: 'Fields_Struct_Integer'

    ### removed other similar warnings ###

    Property created from field: 'managedandroid_String_library_name'
    Property created from field: 'managedandroid_Styleable_LoadingImageView'
    Property created from field: 'managedandroid_Styleable_LoadingImageView_circleCrop'
    Property created from field: 'managedandroid_Styleable_LoadingImageView_imageAspectRatio'
    Property created from field: 'managedandroid_Styleable_LoadingImageView_imageAspectRatioAdjust'
    Property created from field: 'managedandroid_Styleable_SignInButton'
    Property created from field: 'managedandroid_Styleable_SignInButton_buttonSize'
    Property created from field: 'managedandroid_Styleable_SignInButton_colorScheme'
    Property created from field: 'managedandroid_Styleable_SignInButton_scopeUris'
    Property created from field: 'managedandroid_Styleable_THIS_IS_CAPS'
    Property created from field: 'managedandroid_Styleable_THIS_IS_CAPS_THIS_IS_CAPS'
    Property created from field: 'managedandroid_Styleable_THIS_IS_CAPS_camelCase'
    Property created from field: 'managedandroid_Styleable_Theme'
    Property created from field: 'managedandroid_Styleable_Theme_hello'
Pass 'Embeddinator.Passes.CheckDeclarations'
    Found duplicate method: System_Exception_new
    Found duplicate method: Interfaces_IMakeItUp_Convert
    Found duplicate method: Abstracts_AbstractClass_Convert
    Found duplicate method: Interfaces_Conflicted_Hello
    Found duplicate property: Interfaces_Conflicted_TestProperty
    Found duplicate property: Interfaces_Conflicted_TestField
    Found duplicate method: Arrays_Arr_StringArrMethod
    Found duplicate method: Arrays_Arr_ValueHolderArrMethod
    Found duplicate method: Arrays_Arr_ValueTypeArrMethod
    Found duplicate method: Arrays_Arr_BoolArrMethod
    Found duplicate method: Arrays_Arr_CharArrMethod
    Found duplicate method: Arrays_Arr_DoubleArrMethod
    Found duplicate method: Arrays_Arr_FloatArrMethod
    Found duplicate method: Arrays_Arr_SbyteArrMethod
    Found duplicate method: Arrays_Arr_ShortArrMethod
    Found duplicate method: Arrays_Arr_IntArrMethod
    Found duplicate method: Arrays_Arr_LongArrMethod
    Found duplicate method: Arrays_Arr_UshortArrMethod
    Found duplicate method: Arrays_Arr_UintArrMethod
    Found duplicate method: Arrays_Arr_UlongArrMethod
    Found duplicate method: Arrays_Arr_ByteArrMethod
    Found duplicate method: Arrays_Arr_InterfaceArrMethod
    Found duplicate method: Overloads_AllOperators_op_Division
    Found duplicate method: Overloads_AllOperators_op_Division
    Found duplicate method: Overloads_AllOperators_op_Division
    Found duplicate method: Overloads_AllOperators_op_BitwiseAnd
    Found duplicate method: Overloads_ConflictingNamingOverload_Format
    Found duplicate property: Properties_DuplicateIndexedProperties_Item
    Found duplicate method: Methods_DuplicateMethods_DoIt
    Found duplicate method: Methods_DuplicateMethods_DoIt
    Found duplicate method: Methods_DuplicateMethods_DoIt
    Found duplicate method: Methods_DuplicateMethods_Find
    Found duplicate method: Comparable_Different_CompareTo
    Found duplicate method: Constructors_Unique_new
    Found duplicate method: Constructors_AllTypeCode_new
    Found duplicate method: Constructors_AllTypeCode_new
    Found duplicate method: Constructors_AllTypeCode_new
    Found duplicate method: Constructors_DefaultValues_new
    Found duplicate method: Constructors_Duplicates_new
    Found duplicate method: Constructors_Duplicates_new
Pass 'Embeddinator.Passes.FixMethodParametersPass'
Pass 'Embeddinator.Passes.CheckReservedKeywords'

Generating binding code...
Generated: managed.h
Generated: managed.c
Generated: mscorlib.h
Generated: mscorlib.c
Generated: Mono.Android.h
Generated: Mono.Android.c
Generated: Java.Interop.h
Generated: Java.Interop.c
Generated: c-support.c
Generated: c-support.h
Generated: embeddinator.h
Generated: glib.c
Generated: glib.h
Generated: mono-support.c
Generated: mono-support.h
Generated: mono_embeddinator.c
Generated: mono_embeddinator.h
Compiling binding code...
Invoking: /Users/castaldig/userapp/android/sdk/ndk-bundle/toolchains/arm-linux-androideabi-4.9/prebuilt/darwin-x86_64/bin/arm-linux-androideabi-gcc --sysroot="/Users/castaldig/userapp/android/sdk/ndk-bundle/platforms> /android-24/arch-arm" -fdiagnostics-color -DMONO_EMBEDDINATOR_DLL_EXPORT -I"/Library/Frameworks/Mono.framework/Versions/Current/include/mono-2.0" -L"/Users/castaldig/userapp/mobile/temp/Embeddinator-4000/external/> Xamarin.Android/lib/xbuild/Xamarin/Android/lib/armeabi" -lmonosgen-2.0 -lmono-android.release build/lib/Release/android/managed.c build/lib/Release/android/mscorlib.c build/lib/Release/android/Mono.Android.c build/> lib/Release/android/Java.Interop.c build/lib/Release/android/c-support.c build/lib/Release/android/glib.c build/lib/Release/android/mono-support.c build/lib/Release/android/mono_embeddinator.c --std=c99 -shared -o > build/lib/Release/android/android/jni/armeabi/libmanaged.so
In file included from build/lib/Release/android/managed.h:9:0,
from build/lib/Release/android/managed.c:7:
build/lib/Release/android/glib.h:4:20: fatal error: stdlib.h: No such file or directory
#include <stdlib.h>
^
compilation terminated.
In file included from build/lib/Release/android/mscorlib.h:9:0,
from build/lib/Release/android/mscorlib.c:7:
build/lib/Release/android/glib.h:4:20: fatal error: stdlib.h: No such file or directory
#include <stdlib.h>
^
compilation terminated.
In file included from build/lib/Release/android/Mono.Android.h:9:0,
from build/lib/Release/android/Mono.Android.c:7:
build/lib/Release/android/glib.h:4:20: fatal error: stdlib.h: No such file or directory
#include <stdlib.h>
^
compilation terminated.
In file included from build/lib/Release/android/Java.Interop.h:9:0,
from build/lib/Release/android/Java.Interop.c:7:
build/lib/Release/android/glib.h:4:20: fatal error: stdlib.h: No such file or directory
#include <stdlib.h>
^
compilation terminated.
In file included from build/lib/Release/android/embeddinator.h:33:0,
from build/lib/Release/android/c-support.h:28,
from build/lib/Release/android/c-support.c:26:
/Users/castaldig/userapp/android/sdk/ndk-bundle/toolchains/arm-linux-androideabi-4.9/prebuilt/darwin-x86_64/lib/gcc/arm-linux-androideabi/4.9.x/include/stdint.h:9:26: fatal error: stdint.h: No such file or directory
include_next <stdint.h>
                      ^

compilation terminated.
build/lib/Release/android/glib.c:29:19: fatal error: stdio.h: No such file or directory
#include <stdio.h>
^
compilation terminated.
In file included from build/lib/Release/android/mono-support.h:28:0,
from build/lib/Release/android/mono-support.c:26:
/Users/castaldig/userapp/android/sdk/ndk-bundle/toolchains/arm-linux-androideabi-4.9/prebuilt/darwin-x86_64/lib/gcc/arm-linux-androideabi/4.9.x/include/stdint.h:9:26: fatal error: stdint.h: No such file or directory
include_next <stdint.h>
                      ^

compilation terminated.
In file included from build/lib/Release/android/embeddinator.h:33:0,
from build/lib/Release/android/mono_embeddinator.h:31,
from build/lib/Release/android/mono_embeddinator.c:29:
/Users/castaldig/userapp/android/sdk/ndk-bundle/toolchains/arm-linux-androideabi-4.9/prebuilt/darwin-x86_64/lib/gcc/arm-linux-androideabi/4.9.x/include/stdint.h:9:26: fatal error: stdint.h: No such file or directory
include_next <stdint.h>
                      ^

compilation terminated.
Failed to compile generated code.
An error occurred when executing task 'Generate-Android'.
Error: System.AggregateException: One or more errors occurred. ---> System.Exception: mono failed!
at Submission#0.Exec (System.String path, Cake.Core.IO.ProcessSettings settings) [0x00081] in :0
at Submission#0.Exec (System.String path, System.String args, System.String workingDir) [0x00021] in :0
at Submission#0.Embeddinator (System.String args) [0x0002a] in :0
at Submission#0.<>b__0_1 () [0x0002a] in :0
at Cake.Core.CakeTaskBuilderExtensions+<>c__DisplayClass6_0.b__0 (Cake.Core.ICakeContext context) [0x00000] in <13e3bbc8a42c4a419c501956a53939ca>:0
at Cake.Core.CakeTaskBuilderExtensions+<>c__DisplayClass8_0.b__0 (Cake.Core.ICakeContext x) [0x00000] in <13e3bbc8a42c4a419c501956a53939ca>:0
at Cake.Core.ActionTask+d__14.MoveNext () [0x00066] in <13e3bbc8a42c4a419c501956a53939ca>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at Cake.Core.DefaultExecutionStrategy+d__4.MoveNext () [0x000ee] in <13e3bbc8a42c4a419c501956a53939ca>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at Cake.Core.CakeEngine+d__29.MoveNext () [0x00144] in <13e3bbc8a42c4a419c501956a53939ca>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at Cake.Core.CakeEngine+d__18.MoveNext () [0x00231] in <13e3bbc8a42c4a419c501956a53939ca>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at Cake.Scripting.BuildScriptHost+<RunTargetAsync>d__3.MoveNext () [0x0008d] in <cc457eb20afd4019b40c6c7d68eabf46>:0  --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter1[TResult].GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at Cake.Core.Scripting.ScriptHost.RunTarget (System.String target) [0x0000d] in <13e3bbc8a42c4a419c501956a53939ca>:0
at Submission#0+<>d__0.MoveNext () [0x00bee] in :0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at Microsoft.CodeAnalysis.Scripting.ScriptExecutionState+<RunSubmissionsAsync>d__91[TResult].MoveNext () [0x00186] in <9edb99c3aaa5489db8bb992099d2db96>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at Microsoft.CodeAnalysis.Scripting.Script1+d__21[T].MoveNext () [0x000a8] in <9edb99c3aaa5489db8bb992099d2db96>:0
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional (System.Boolean includeTaskCanceledExceptions) [0x00011] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Threading.Tasks.Task.Wait (System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00043] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Threading.Tasks.Task.Wait () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at Cake.Scripting.Roslyn.RoslynScriptSession.Execute (Cake.Core.Scripting.Script script) [0x00129] in :0
at Cake.Core.Scripting.ScriptRunner.Run (Cake.Core.Scripting.IScriptHost host, Cake.Core.IO.FilePath scriptPath, System.Collections.Generic.IDictionary2[TKey,TValue] arguments) [0x00358] in > <13e3bbc8a42c4a419c501956a53939ca>:0    at Cake.Commands.BuildCommand.Execute (Cake.CakeOptions options) [0x00026] in <cc457eb20afd4019b40c6c7d68eabf46>:0    at Cake.CakeApplication.Run (Cake.CakeOptions options) [0x00015] in <cc457eb20afd4019b40c6c7d68eabf46>:0    at Cake.Program.Main () [0x000d1] in <cc457eb20afd4019b40c6c7d68eabf46>:0  ---> (Inner Exception #0) System.Exception: mono failed!   at Submission#0.Exec (System.String path, Cake.Core.IO.ProcessSettings settings) [0x00081] in <c80b354d947346faaf5c03f548b26962>:0    at Submission#0.Exec (System.String path, System.String args, System.String workingDir) [0x00021] in <c80b354d947346faaf5c03f548b26962>:0    at Submission#0.Embeddinator (System.String args) [0x0002a] in <c80b354d947346faaf5c03f548b26962>:0    at Submission#0.<<Initialize>>b__0_1 () [0x0002a] in <c80b354d947346faaf5c03f548b26962>:0    at Cake.Core.CakeTaskBuilderExtensions+<>c__DisplayClass6_0.<Does>b__0 (Cake.Core.ICakeContext context) [0x00000] in <13e3bbc8a42c4a419c501956a53939ca>:0    at Cake.Core.CakeTaskBuilderExtensions+<>c__DisplayClass8_0.<Does>b__0 (Cake.Core.ICakeContext x) [0x00000] in <13e3bbc8a42c4a419c501956a53939ca>:0    at Cake.Core.ActionTask+<Execute>d__14.MoveNext () [0x00066] in <13e3bbc8a42c4a419c501956a53939ca>:0  --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at Cake.Core.DefaultExecutionStrategy+<ExecuteAsync>d__4.MoveNext () [0x000ee] in <13e3bbc8a42c4a419c501956a53939ca>:0  --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at Cake.Core.CakeEngine+<ExecuteTaskAsync>d__29.MoveNext () [0x00144] in <13e3bbc8a42c4a419c501956a53939ca>:0  --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at Cake.Core.CakeEngine+<RunTargetAsync>d__18.MoveNext () [0x00231] in <13e3bbc8a42c4a419c501956a53939ca>:0  --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at Cake.Scripting.BuildScriptHost+d__3.MoveNext () [0x0008d] in :0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at System.Runtime.CompilerServices.TaskAwaiter1[TResult].GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at Cake.Core.Scripting.ScriptHost.RunTarget (System.String target) [0x0000d] in <13e3bbc8a42c4a419c501956a53939ca>:0    at Submission#0+<<Initialize>>d__0.MoveNext () [0x00bee] in <c80b354d947346faaf5c03f548b26962>:0  --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at Microsoft.CodeAnalysis.Scripting.ScriptExecutionState+d__91[TResult].MoveNext () [0x00186] in <9edb99c3aaa5489db8bb992099d2db96>:0  --- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <4fdc5ed61a074cafb49fa42deb20d521>:0    at System.Runtime.CompilerServices.ConfiguredTaskAwaitable1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <4fdc5ed61a074cafb49fa42deb20d521>:0
at Microsoft.CodeAnalysis.Scripting.Script`1+d__21[T].MoveNext () [0x000a8] in <9edb99c3aaa5489db8bb992099d2db96>:0 <---

I have run into this issue before and it occurs because of missing include folders in the android-ndk. For example in my android-ndk-r16b download from the ndk site, I don't have an include folder under platforms/android-24/arch-arm/usr. I solved the issue by downloading android-ndk-r15c and pointing the NDK path to it which does appear to have the include folder and has the headers required.

Downgrading my NDK to r15c resolved this issue for me

Just hit this issue myself. Seems all NDK versions above 15c. Looks like the NDK bits that are used are being deprecated too.

Just hit this issue also. Trying the NDK down grade now.
Seems its been around for over a year now. Are there any plans to fix it?

Hit this issue today.
Downgrading now, but its a real huge pain with Mac OS Catalina since the NDK Bundle is a bunch of un-notorized scripts which mac requires you to mack verification exceptions for.


Simple usage without a build?

Hi David,
I have an API key "SECRET" and channel ID, UCFzGyNKXPAglNq28qWYTDFA and I want to use your cli to list all my videos. Hoping it will do that without me having to worry about that bothersome nextPageToken stuff.
However I'm struggling to find a client_secret.json example?
Would it be more natural to go install the cli and have a default like ~/.ytapi/credentials?
My use case is build a list of my videos so I can back them up. Thank you!

Hi Kai! You should create a developer account for yourself on https://console.developers.google.com and then create a project for the tool. You can then create "Credentials" and download the client_secrets.json file.
Also remember to enable the YouTube API's within your project - the link for that is
https://console.developers.google.com/apis/library
Let me know if you need any more help.

Little confused about the roles: https://s.natalian.org/2017-09-11/ytapi.mp4

My apologies Kai. Thanks for your video. In fact if you only want the client_secrets.json file, then you don't need the service account flow. I've created a counterpart video here:
https://github.com/djthorpe/ytapi/blob/master/doc/Creating a client secrets file.mov?raw=true

Will close this issue now, please let me know if you need any more help!


How are you?
jan-casas I guess is necessary more information.
However, some step suggestions that you can look up:

Check your theme settings: Sometimes, theme settings can interfere with the custom colors you've set. Make sure the theme you're using isn't overriding your custom settings.

Disable extensions: Some extensions can interfere with color settings. Try disabling your extensions one by one to see if any of them are causing the issue.

Check your workspace settings: If you have a .vscode/settings.json file in your workspace, it could be overriding your user settings. Check if there are any settings that might be causing the issue.

Reinstall VS Code: As a last resort, you might try uninstalling and reinstalling VS Code. This should reset all settings to their default values.

I hope that you can fix it.
Regards.

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Push back to copier-python after merging a Pull Request from Dependabot

See blakeNaccarato/copier-python#1

This will be needlessly complex. We would need to modify the *.yml.jinja version of the workflow file in copier-python with the same bumps performed on the *.yml version here. Let's just manually do this for now, and revisit it if that becomes burdensome.
Since workflow version bumps are more likely to break something than linter and dev tooling bumps, it may be desirable to let PRs build up here and to a bunch at once. This could be tied to a minor version bump of copier-python, while tooling updates are bundled into a patch version bump of copier-python.
Small architectural changes will be dedicated to minor version bumps, while major versions will be reserved for major overhauls of copier-python.


Docs not scrollable (v4 alpha)

The docs linked in the v4 alpha README are not scrollable:
https://react-router-website-xvufzcovng.now.sh/
Removing height:100% fixes it

A dupe of https://github.com/ReactTraining/react-router/issues/3859?

react-router.now.sh
On Thu, Sep 22, 2016 at 1:26 AM Adrian Lynch<EMAIL_ADDRESS>wrote:

A dupe of #3859
https://github.com/ReactTraining/react-router/issues/3859?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ReactTraining/react-router/issues/3927#issuecomment-248841421,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGHaFIDC_hRA6Ybn0lAjDShMXT6veonks5qsjvCgaJpZM4KDf0a
.


After Deleting a note and returning to Home page the website breaks

Steps to produce error:
Delete a already created note
Shift back or directly go to home page
BUG
The Redux is unable to fetch the data for all notes

i'd like to take a peek into this in my free time. Don't assign me yet. If anybody want to work on it, you can assign to them,

Sure, Let me know if u need any help I will be gald to do so


Add "Relevant Programs" section to "Application confirmation" page

The section has been added. Styling the cards is tracked in #8156 (mocks) and #8157 (implementation)

Closing since the functionality is complete. Styling will be QA'd in #8157


Release v0.2.3

cc @wikimedia/services

Coverage remained the same at 94.424% when pulling 31982416f549d58a0eb0a0e8f0d704c9652df021 on d00rman:rel-023 into 39f883ef433b5a6d0f43777ee9f959b8b94c1842 on wikimedia:master.

Published as v0.2.3


Resolve entity framework warnings

Resolves aspnet/entity framework generated warnings:

comma separated list input values conversion configurations lacked a comparator: Certification.EscoUri, WorkPreferences.PreferredMunicipalityCode, WorkPreferences.PreferredRegionCode and WorkPreferences.WorkingLanguageEnum:

warning example: The property 'Certification.EscoUri' is a collection or enumeration type with a value converter but with no value comparer. Set a value comparer to ensure the collection/enumeration elements are compared correctly.

the field PersonAdditionalInformation.Address marked as a required value: it's an ef-shared model that is "merged/combined " with the parent one and when the field was defined as optional the entity framework flagged it as odd behaviour

warning example:  The entity type 'Address' is an optional dependent using table sharing without any required non shared property that could be used to identify whether the entity exists. If all nullable properties contain a null value in database then an object instance won't be created in the query. Add a required property to create instances with null values for other properties or mark the incoming navigation as required to always create an instance.

database queries that included relations (a JOIN-clause) needed a specification which query strategy to use: https://learn.microsoft.com/en-us/ef/core/querying/single-split-queries

warning example: Compiling a query which loads related collections for more than one collection navigation, either via 'Include' or through projection, but no 'QuerySplittingBehavior' has been configured. By default, Entity Framework will use 'QuerySplittingBehavior.SingleQuery', which can potentially result in slow query performance. See https://go.microsoft.com/fwlink/?linkid=2134277 for more information. To identify the query that's triggering this warning call 'ConfigureWarnings(w => w.Throw(RelationalEventId.MultipleCollectionIncludeWarning))'
note: in this case the QuerySplittingBehavior.SingleQuery is what we want as the data relation structure is all related and wanted to be attached to single entities (of a Person-model) so there's no performance penalty as described by the frameworks warning

configured the aspnet core data protection mechanism to use key persistence using the database as in lambda/container-scheme the filesystem based persistence would not work: https://learn.microsoft.com/en-us/aspnet/core/security/data-protection/configuration/overview?view=aspnetcore-6.0

warning examples:

Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
No XML encryptor configured. Key {52c377ea-769a-4d0c-a84f-eca479935816} may be persisted to storage in unencrypted form.

Tähän on muuten hankala testausohjetta kirjoitella, kuin että logeista pitäisi hävitä ym. waroitukset myös lokaalissa ja appiksen käytön pitäisi toimia normaalisti.

.AsSingleQuery()
Erikoista, että tuota pitää spämmätä kaikkialla, jos se on kuitenkin default mitä käytellään. Toisaalta, ei sitten osanne antaa varoitusta asiasta..
Voisko tuosta asetella jotenniin globaalin asetuksen, minkä sit vois case-kohtaisesti ylikirjoitella tarvittaessa, https://learn.microsoft.com/en-us/ef/core/querying/single-split-queries#enabling-split-queries-globally

In cases where the built-in comparison behavior isn't appropriate, users may provide a value comparer, which contains logic for snapshotting, comparing and calculating a hash code.
Jos built-in toimii (ilmeisesti toiminut kuitenkin tähän asti), niin eikö tuota voi hiljentää mitenkään vaikka case-kohtaisesti, vs. määritellä tuollanen hc valueComparer?


github: Avoid duplicating version annotation step

The original files are still accessible from the Build step, use them during the Update SSP Operator step and avoid annotating twice.

What this PR does / why we need it:
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 #
Special notes for your reviewer:
Release note:

https://github.com/kubevirt/common-instancetypes/pull/72 is a better approach


Script to add image watermark

A common script that people need in daily life is one that adds watermark to images

Thank you


KAFKA-9734: Fix IllegalState in Streams transit to standby

Consolidate ChangelogReader state management inside of StreamThread to avoid having to reason about all execution paths in both StreamThread and TaskManager.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

This time, there were two different, unrelated failures.
kafka.api.PlaintextConsumerTest.testLowMaxFetchSizeForRequestAndPartition
kafka.api.ConsumerBounceTest.testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup


migrated old qpn branch-specific code to new qpn fork

@nikhil153 looks like this PR's target is neurodatascience/mr_proc:main, not neurodatascience/mr_proc-qpn:main. Is this a mistake? I think GitHub automatically chooses the original repo for PRs, so we need to choose the right fork when creating the PR.


Add Moonwalk, and where?

I want to create a PR to add moonwalk, but I'm not sure where it belongs. It's also worth noting that it hasn't been updated in a while. It's still working well for me, though, and is very useful!

@Computer2340 neat plugin! maybe the Neovim Lua Development section?


ResourcePathRepr

Atm ResourcePathRepr are stored in the database parallel to the resource. This is a source for errors as there is no single origin of truth. Change implementation so that only resources are stored and PathRepr is generated when neccessary.

Working on branch PathRep


fix(aws): Change ListStoppedInstances to ListNonRunningInstances

osd-11731
ListStoppedInstances updated to ListNonRunningInstances to reflect that it is not only stopped instances.

/lgtm
/approve
this look great!
and it makes the fmt clearer for the user :)
/hold
as I want to allow others to look aswell

/lgtm
/approve
/unhold


fix(retail-react-app): recent searches

Description
Closes #968
Types of Changes

[x] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

Add missing return to recent searches filter method

How to Test-Drive This PR

See steps in #968

Checklists

General

[x] Changes are covered by test cases
[ ] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[x] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

@breadadams thank you for fixing it and writing the tests too 🙏


Stretch Goal - Auto-populate search queries

Requirements

When the user types their destination into the search bar, potential search options are dynamically displayed as auto-populate options

Design of site changed to dropdowns instead of text fields, no longer required/already achieved.


Test fc_blas fails

I doubt it ever properly worked on Travis.
Previously it passed trivially until 4d0784d.

Could you please have a look at this @miroi ? The test works
locally but fails on Travis.

https://github.com/scisoft/autocmake/commit/4d0784dbd9e975991b9ab2bad659e926b741b363

Please see my comments in 4d0784d.
With this I doubt the test ever worked for the right reason on Travis.

This is strange:
https://travis-ci.org/miroi/autocmake/builds/71224638
For some reasons travis does not detect string in stdout....
>           assert 'dgemm test ok' in stdout
E           assert 'dgemm test ok' in ''

Maybe I find a solution.

I think there is simply no stdout.

Whiel playing with
https://github.com/miroi/autocmake/blob/fix_travis/test/fc_blas/src/example.f90
The problem seems to appear  around commands "allocate - dgemm - deallocate", see https://travis-ci.org/miroi/autocmake/builds/71227409
Maybe dynamical allocation not permitted on travis-ci ?

Well, I have to instert stderr catchers, both from setup.py and example.f90.
Stderr catching is urgently needed for cases as this one.

Travis certainly allows dynamic allocation. But here we launch the code via a subprocess.
It could be that Travis blocks dynamic allocation for subprocesses to prevent fork-bombing the system.
We don't need dynamic allocation for this test - let's go with static arrays.

Static arrays are not working either. Plus missing stderr printout from example.f90/setup.py in the test.py script is making difficult to determine the exact cause of travis-ci test failure.

Static arrays are not the problem - https://travis-ci.org/miroi/autocmake/builds/71233486 .
Problem is own DGEMM calling, https://travis-ci.org/miroi/autocmake/builds/71234385 .
I don't see the stderr from the fortran executable. How to implement stderr catching into test.py ? I need it urgently. Without seeing all stderrs the development is pain.

Well, here: https://pytest.org/latest/capture.html
Please give me, @bast, green light to implement it into test.py.

Hi Miro, you don't need my permission. "Just Do It". That's the beauty of open source
and distributed version control: you can do anything you like and all improvements
will be incorporated.

Could we please close this issue ? The test is working now.

Sure! Closing.


When switching scenes from within pannellum, the writable should also update.

When in developer mode, there should be an onclick function on the hotspots that handles this

clickHandlerFunc (function) and clickHandlerArgs (object)
If clickHandlerFunc is specified, this function is added as an event handler for the hot spot’s click event. The event object and the contents of clickHandlerArgs are passed to the function as arguments.

It for now only works when clicking on the viewer when the scene is loaded. So clicking on a hotspot wont switch the scenes, the user will first need to click somewhere else in the viewer.


Neovide.Neovide version 0.10.4

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

This package is expecting arguments. Using -help gives:
Neovide: No Nonsense Neovim Gui

Usage: neovide.exe [OPTIONS] [FILES_TO_OPEN]... [-- [NEOVIM_ARGS]...]

Arguments:
  [FILES_TO_OPEN]...  Files to open (plainly appended to NeoVim args)
  [NEOVIM_ARGS]...    Arguments to pass down to NeoVim without interpreting them

Options:
      --geometry <GEOMETRY>
          The geometry of the window [default: 100x50]
...


[RFC] fix hive.fetch_logs

what's in this PR:

adopted https://github.com/airbnb/superset/issues/2954#issuecomment-308023559
change return type to string instead of a list of strings.
fix one of the assert statements inside the except clause

this closes https://github.com/airbnb/superset/issues/2954
@mistercrunch

codeclimate complains about line length, but in this case, breaking lines up actually hurts readability, if this is absolutely required, I'll fix.

Sorry that I've notified you when the PR isn't ready, but I think I've got it working correctly now, request for comment @mistercrunch

request for comment @bkyryliuk

I've adjust the line breaks just to satisfy codeclimate. all green lights now, care to comment? @mistercrunch
again, sorry to mention you so many times, but I was suspecting if github had some kind of mechanics that prevent maintainers from receiving notifications from inadequate pull requests, because I didn't think the codeclimate's suggestions are useful and just let its tests stay unsuccessful.
now that travis and codeclimate tests is passing, I really wish somebody can take a look at this and tell me if I was doing things the way it should be.
I've also added some explanations in the PR descriptions, looking forward to your response.

Sorry it took me a while to get to this, I was out on vacation for a while and busy in general. Reviewing now.


removed the key for tolerations in flannel daemonset

We noticed when adding a custom taint to a node that this meant that the flannel daemonset was no longer scheduled on it, which is a problem as our cluster relies on flannel.
This change is to make the tolerations on the flannel daemonset the same as the other network_plugns (weave, canal etc) so that the ds still gets scheduled on all nodes.

wrong email address


"unable to invoke agent installation" on Raspberry Pi B+

I get the following error when attempting to create a synchronization session between a CentOS 7 computer and a Raspberry Pi B+ running Raspbian:
$ mutagen create data-dir user@hostname:~/data-dir
Installing agent...
Error: create failed: unable to connect to beta: unable to connect to SSH remote: unable to install agent: unable to invoke agent installation: exit status 255

When I try to run the mutagen-agent binary on the Raspberry Pi B+, it fails:
user@hostname:~ $ file .mutagen-agent44a72715-c57b-4c0b-8da1-50059dcc81b9
.mutagen-agent44a72715-c57b-4c0b-8da1-50059dcc81b9: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped
user@hostname:~ $ ./.mutagen-agent44a72715-c57b-4c0b-8da1-50059dcc81b9
Illegal instruction

Processor info for the Raspberry Pi B+
user@hostname:~ $ cat /proc/cpuinfo
processor	: 0
model name	: ARMv6-compatible processor rev 7 (v6l)
BogoMIPS	: 697.95
Features	: half thumb fastmult vfp edsp java tls
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xb76
CPU revision	: 7

Hardware	: BCM2835
Revision	: 0010

Is it possible to compile and manually install the mutagen-agent on the B+?

I had something similar when I was using docker. Turns out it was a permissions error.
Check the user you are using has a home directory and write access.
I initially went mad with chmodding 777 places until it worked then worked backwards.
Hope it helps!

Sorry for the slow reply - I'm hoping to get to the backlog of comments this evening.
This looks like an issue with Go generating incorrect instructions in the ARM binaries rather than a permissions issue.  The Mutagen build process sets GOARM=5, so ARMv5 and above should be supported, but I think that there have been cases in the past where the Go compiler has generated unsupported ARM instructions in binaries for older ARM architectures.  Additionally, in Go 1.11, they switched to a new software floating point implementation for ARMv5 binaries, so that could be doing something weird.
Since no Rapsberry Pi uses anything below ARMv6, and that was the primary target for the Mutagen ARM port anyway, I will most likely issue v0.7.0-beta2 with support for only ARMv6 and above.  Hopefully that will solve the issue.
I have a Raspberry Pi 3B that I'll play with tonight and see if I can reproduce.  It's ARMv7, but the issue may also manifest there.

@matthew-gill, I suspected a permissions issue after reading #46 so I changed the uid/gid for the user account on the remote system to be the same as the local system.  I could see that the mutagen-agent binary was being successfully copied to the remote home dir at which point I started looking elsewhere for the problem.
@havoc-io, If I copy the 32-bit ARM mutagen agent to a Raspberry Pi 3, the agent runs without error:
 $ ./linux_arm
The Mutagen agent should not be invoked by human beings.

Usage:
  mutagen-agent [flags]
  mutagen-agent [command]

Available Commands:
  install     Perform agent installation
  endpoint    Run the agent in endpoint mode
  version     Show version information
  legal       Show legal information
  help        Help about any command

Flags:
  -h, --help   Show help information

Use "mutagen-agent [command] --help" for more information about a command.

Here is the cpu info:
$ cat /proc/cpuinfo
processor	: 0
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

<snip>

Hardware	: BCM2835
Revision	: a22082

The Pi on which the agent binary is failing is a v1 Raspberry Pi B+ (revision 0010).  Here is its uname output:
$ uname -sm
Linux armv6l

The Pi on which I copied the agent binary for testing is a v3 Raspberry Pi B (revision a22082.  Here is its uname output:
$ uname -sm
Linux armv7l

Ah, okay, so there are two Pis involved.  My guess would be a bad instruction being generated by the Go compiler for ARMv5 binaries in Go 1.11.  If you try with Mutagen v0.6.1, does it work with the v1 Pi?  That was the last release compiled with Go 1.10.  It would help narrow down the issue.  I'll have a look at the Go issue tracker tonight and see if I can't track down what's going on.

Ah, okay, so there are two Pis involved.

Yes.  The testing on the v3 Pi was an attempt to save you troubleshooting
time.

If you try with Mutagen v0.6.1, does it work with the v1 Pi?

All of my testing so far has been with v0.6.1.  The download link from
mutagen.io goes to a github page that doesn't show the v0.7.0-beta1
release, so I didn't realize I wasn't using the latest version.  I
downloaded a tested with v0.7.0-beta1 and found that the agent binary fails
in the same way on the v1 Pi B+.

@frankdeath Thanks for the clarification and the debugging help.  I think I'm going to have to spin this up in QEMU to debug exactly which "illegal instruction" is being embedded in the binaries.  Or perhaps just generate a beta build using GOARM=6 and see if it's this software floating point implementation that's causing problems.  I probably won't get to that until Friday unfortunately, but I'd be happy to give you a ping and even happier if you could test it on the real hardware.

I'm happy to test any new builds on the Pi B+.
I'm not very familiar with go.  If I do a skinny build of mutagen on the Pi B+, would that generate the agent binary?

I followed the procedure described in the second-best answer from this stack overflow page: https://stackoverflow.com/questions/10354147/find-which-assembly-instruction-caused-an-illegal-instruction-error-without-debu
The core file generated by the v0.7.0-beta1 agent crashes on this instruction:
  >│0x48f94 vmov.f32       s0, #112        ; 0x3f800000  1.0                   │
   │0x48f98 vsub.f32       s0, s0, s0                                          │
   │0x48f9c vstr   s0, [sp, #32]                                               │
   │0x48fa0 vmov.f64       d0, #112        ; 0x3f800000  1.0                   │
   │0x48fa4 vsub.f64       d0, d0, d0

The core file generated by the v0.6.1 agent crashes on this instruction:
  >│0x496b0 vmov.f32       s0, #112        ; 0x3f800000  1.0                   │
   │0x496b4 vsub.f32       s0, s0, s0                                          │
   │0x496b8 vstr   s0, [sp, #32]                                               │
   │0x496bc vmov.f64       d0, #112        ; 0x3f800000  1.0                   │
   │0x496c0 vsub.f64       d0, d0, d0

@frankdeath Thanks for the excellent debugging.  It was definitely an incorrect instruction being generated.
I found the bug that was causing this problem.  It was in the build script:
if t.GOOS == "arm" {
    result = append(result, fmt.Sprintf("GOARM=%s", minimumARMSupport))
}

This should have read:
if t.GOARCH == "arm" {
    result = append(result, fmt.Sprintf("GOARM=%s", minimumARMSupport))
}

I was checking the OS setting instead of the architecture setting.
The fix another 100 KB to the linux_arm agent binary, but that should be fine.  Mutagen doesn't have any floating point code, so hopefully this shouldn't impact performance at all.  Most of Mutagen is syscall-limited.
I'm building v0.7.0-beta2 at the moment that should have an ARM binary that'll work on the ARMv6 system (and, hopefully, ARMv5).  I'll ping you once that's ready.
Right now I have #19 on the docket to enable QEMU-based testing of ARM et al. on the Travis Linux builders, at least to some level.  Hopefully I'll catch stuff like this sooner in the future.

@frankdeath v0.7.0-beta2 is available.  Could I ask you to give it a shot on the Pi v1?

@frankdeath https://github.com/frankdeath v0.7.0-beta2
https://github.com/havoc-io/mutagen/releases/tag/v0.7.0-beta2 is
available. Could I ask you to give it a shot on the Pi v1?

The agent gets installed on the v1 Pi B+ and doesn't crash with the
"Illegal instruction" message:
$ ~/.mutagen/agents/0.7.0-beta2/mutagen-agent
The Mutagen agent should not be invoked by human beings.

Usage:
  mutagen-agent [flags]
  mutagen-agent [command]

Available Commands:
  install     Perform agent installation
  endpoint    Run the agent in endpoint mode
  version     Show version information
  legal       Show legal information
  help        Help about any command

Flags:
  -h, --help   Show help information

Use "mutagen-agent [command] --help" for more information about a command.

The create fails to connect to the agent that was just installed on the Pi,
but I'm fairly confident that is a different issue:
$ mutagen create data-dir user@hostname:~/data-dir
Connecting to agent (POSIX)...

Error: create failed: unable to connect to beta: unable to connect to SSH
remote: unable to connect to agent: command not found

Well that's a step forward I guess...
If you remove ~/.mutagen on the Pi, does running the mutagen create ... command successfully copy the agent to ~/.mutagen/agents/0.7.0-beta2/mutagen-agent on the Pi?

If you remove ~/.mutagen on the Pi, does running the mutagen create ... command
successfully copy the agent to ~/.mutagen/agents/0.7.0-beta2/mutagen-agent on
the Pi?

Yes.  The agent is successfully copied to that location.
Is there a system command that is run when attempting to connect to the
agent that might be missing from my system?

Is there a system command that is run when attempting to connect to the agent that might be missing from my system?

Not that I can think of... Maybe there's something in a .bashrc file (or similar) that's causing execution problems when Mutagen tries to invoke the agent via SSH?  Can you try to invoke the agent on the Pi over SSH and see what happens?  E.g.
ssh user@hostname .mutagen/agents/0.7.0-beta2/mutagen-agent version

or
ssh user@hostname .mutagen/agents/0.7.0-beta2/mutagen-agent endpoint

That should be a faithful reproduction of what Mutagen's doing.  The latter command will hang and need to be terminated with Ctrl+C.
The "command not found" error (exit code 127 on POSIX shells) can (confusingly) also be returned by the system linker when certain libraries aren't found, but the executable is completely statically linked, so I doubt that could be the issue.  Just for a sanity check, you could try to run
ldd ~/.mutagen/agents/0.7.0-beta2/mutagen-agent

When I invoke the agent on the Pi over SSH, the calls are successful:
$ ssh user@hostname .mutagen/agents/0.7.0-beta2/mutagen-agent version
0.7.0-beta2
$ ssh user@hostname .mutagen/agents/0.7.0-beta2/mutagen-agent endpoint
'�^CKilled by signal 2.

This is the ldd output on the Pi:
$ ldd ~/.mutagen/agents/0.7.0-beta2/mutagen-agent
not a dynamic executable

If the error was coming from mutagen and not mutagen-agent I could use delve to debug.  Is it possible to create a session manually so that I can run mutagen-agent in delve?

I've successfully connected to the v1 Pi B+ now.  This issue can be closed again.
This error was occurring because I failed to restart the daemon after switching to the latest version of mutagen:
$ mutagen create data-dir user@hostname:~/data-dir
Connecting to agent (POSIX)...

Error: create failed: unable to connect to beta: unable to connect to SSH remote: unable to connect to agent: command not found

I don't know if the daemon that was running was v0.6.1 or v0.7.0-beta1.  I stopped it before realizing that would have been a good thing to know.
The session I created is in the staging phase and the mutagen-agent's CPU usage on the v1 Pi B+ is in the 35-60% range.

@havoc-io Thanks for all the help!

@frankdeath That explains it.  I didn't even think of that, but yes, the daemon always looks for the agent executable corresponding to its own version.  I need to expand the documentation on the daemon's behavior.  Or, eventually, hopefully hide it from the user complete.

The session I created is in the staging phase and the mutagen-agent's CPU usage on the v1 Pi B+ is in the 35-60% range.

That sounds about right.  It should drop down to idle (with occasional polling) after staging is complete.
Thanks again for your debugging help!  Please don't hesitate to let me know if any other issues crop up.


:bug: Clusterclass e2e test fix

This PR is a followup to #1405
It fixes issues with redundant test env related vars and configs that couses the test to fail at start. Those were removed in #1624 and should be also removed for clusterclass.
Also, it tries to fix issue with {{ ds.meta_data.hostname }}' reference reported in the comment here.
It seems that, according to the cluster-api repository, NodeRegistration.Name defaults to hostname, so I believe referencing hostname explicitly here is redundant and minght be deleted.

/ok-to-test

/metal3-centos-e2e-integration-test-main
/lgtm

/test metal3-centos-e2e-integration-test-main
/test metal3-ubuntu-e2e-integration-test-main

/approve
Thanks a lot for the fix @p-strusiewiczsurmacki-mobica

The link to the centos e2e points to completely different PR.
Anyways, ubuntu passed,
/override metal3-centos-e2e-integration-test-main


Add ability to create namespace certificates, routing certificates and control certificates.

Done in https://github.com/knative-extensions/control-protocol/commit/3531529a36e80238feee4466c3d5f3239c5e0a66
/close


Load Markdig in an assembly load context

Summary of the new feature / enhancement
As a developer working on a PowerShell module that interacts with Markdown, I want to be able to use newer versions of the Markdig library without conflict errors. Because Markdig isn't loaded in an ALC, using a newer version of Markdig in my module isn't feasible.
One reason to desire a newer version of the library is to gain access to the round-tripping support and more walkable AST.
Proposed technical implementation details (optional)
Update the module to load Markdig in an ALC. No change is required to the version of Markdig used.

I'm willing to attempt a PR if there is interest @adityapatwardhan @xtqqczze?

Please do. Would love a PR.

@adityapatwardhan sounds good, can you add the up for grabs label?

Hugely appreciated, @JustinGrote - I've been bouncing off this problem for the Documentarian module(s) for a bit and this would be radically helpful!


HTTP 429: Too Many Requests

🐛 Summary
The load_certs.py script crashes after receiving multiple HTTP 429 errors.
To reproduce
Steps to reproduce the behavior:

Execute ./load_certs.py. The script will crash after processing approximately 70 domains.

Any helpful log output or screenshots

I will refactor the cert_by_id task in tasks.py to use a custom retry delay with the Retry-After header value returned from the HTTP 429 error.

crt.sh does not send a Retry-After header with the response. Back to square one.
Since crt.sh doesn't like that we send multiple requests at once, I switched the group signature in group_update_domain() to a chain. That seems to be working, but it's probably too slow a solution to be useful.
Next, I want to try using chunks. My thinking is we can break the tasks into pieces, gradually increasing the number of certificates done in a batch, until we reach the maximum crt.sh can manage.

Testing the script with a default rate limit of no more than 60 certificate grabs per minute, according to https://groups.google.com/g/crtsh/c/NZJntKrBdmg.


2D motion prediction and keypoint format

Has anybody tried predicting 2D instead of 3D motion? I can see that there's an option to choose depth=2 in the model but I can't find any example of using it.
Also, does the model accept only SMPL keypoint format?

Hi,
depth=2 represents the depth of the 1D convolutional network in the VQVAE, which does not refer to 2D or 3D.
We have not tried formats other than SMPL, but I think it may be adaptable to other models


feat: Add coverage action

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@5dbd7cc). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 4b88699 differs from pull request most recent head d9335be. Consider uploading reports for the commit d9335be to get more accurate results

@@           Coverage Diff           @@
##             main       #7   +/-   ##
=======================================
  Coverage        ?   87.80%
=======================================
  Files           ?        2
  Lines           ?       41
  Branches        ?        5
=======================================
  Hits            ?       36
  Misses          ?        0
  Partials        ?        5

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


Update Composer dependencies (2023-11-16-00-10)

Visual regression test passed!
View the visual regression test report


Map, Set, WeakMap, WeakSet can't be wrapped successfully

If this PR gets merged -> https://github.com/justin-schroeder/arrow-js/pull/87, the reactivity will not wrap Map, Set, WeakMap, WeakSet (which means they'll be returned without any interception)
Without it being merged I don't think they work properly inside of reactive(), the following throws:
const data = reactive({
  map: new Map()
})
data.map.size

Error in the browser (Firefox): Uncaught TypeError: get size method called on incompatible Proxy
Output in a test with the above code:
TypeError: Method get Map.prototype.size called on incompatible receiver #<Map>
 ❯ Object.get src/reactive.ts:208:29
    206|       if (Reflect.has(depProps, p)) return Reflect.get(depProps, p)
    207|
    208|       const value = Reflect.get(...args)
       |                             ^
    209|       // For any existing dependency collectors that are active, add this
    210|       // property to their observed properties.

Can confirm, Set doesn't work as a reactive property 😢

They dont work inside reactive() — and honestly I’m leaning towards not implementing them either. Getting a reactive framework to work well in the ~2kb range is pretty tough and the smaller the api surface area the better. Proxying maps and sets would add some precious bytes to the pile — not ruling it out though. After the refactors ship if there is any room in the byte budget this would be something to look at doing.

That's actually ok with me so long as the documentation makes this very clear. I would prefer that it throws a sensible exception as well, but I don't know how much spare room you have for error checking.

ditto for TypedArray.
My current use case is fine with an immutable TypedArray—no need to react to changes to its individual elements—but it was an unpleasant surprise to discover the thing I retrieved from the state store was not usable.¹
I could work around it if I could unwrap the object from the proxy, but it doesn't look like it exposes its proxySource. Hmm… Reflect.getPrototypeOf(proxy) appears to do that, but that feels more like a lucky implementation detail than a well-defined API.
1: despite the fact that it went in to the store just fine.


chore: lerna update

Новый мажорный релиз - https://github.com/lerna/lerna/releases

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.007%) to 79.027%

Totals

Change from base Build<PHONE_NUMBER>:
0.007%

Covered Lines:
6842

Relevant Lines:
7880

💛  - Coveralls


move java libs into their own dirs in third_party

Create gson/, guava/, and weberknecht/ dirs in third_party/ and move the java jars and licenses into the respective dirs.
@danrubel

LGTM


[Draft] Support for mixed language targets

@paulb777, there are still some outstanding comments but I refactored the approach since it seems to be in a more stable place. PTAL and let me know your thoughts!


Task doesn't fail when status code is incorrect

Hi,
I am using GooseRequest builder and the task aren't recorded as "failed" even if an error is returned (status code 400+). The code for my task is below, in this case the JSON is invalid a 400 error is returned. Not sure if there is something wrong in how I am using it:
async fn table_data_entry(user: &mut GooseUser) -> GooseTaskResult {

    let value : u64 = rand::thread_rng().gen_range(245..255);
    let data = TableUpdate::new(&vec!["2000-01","LAX","JFK","AA", "N126AA", "Flight Time"], value as f64);

    let req = user.get_request_builder(&GooseMethod::Patch, "api/end-pont")?
        .basic_auth("admin", Option::<&str>::None)
        .json(&data);

    let req = GooseRequest::builder()
        .set_request_builder(req)
        .build();

    user.request(req).await?;

    Ok(())
}

I have put together a fix to return the error and also return the body as part of the error message (goose.rs 1631-1638):
       if !request_metric.success {
            if let Ok(r) = response {
                warn!("{:?} {}: {}", &path, &request_metric.error, r.text().await.unwrap_or("".to_string()));
            } else {
                warn!("{:?} {}", &path, &request_metric.error);
            }
            return Err(GooseTaskError::RequestFailed{raw_request: request_metric});
        }

I can create a pull request if this solves the issue I have.

The error is in the request log see below. The error does appear in the per request numbers and in the "ERRORS" section in the end. This issue that the error doesn't show up in the per task details and an error isn't logged to the console when the error occurs. Logging to the console seems important to me because as I can see that something is failing, maybe because on an incorrect task. See details below.
{"coordinated_omission_elapsed":0,"elapsed":57000,"error":"400 Bad Request: ","final_url":"http://localhost:5050/api/end-point","name":"","raw":{"body":"","headers":["(\"authorization\", Sensitive)","(\"content-type\", \"application/json\")"],"method":"Get","url":"http://localhost:5050/api/end-point"},"redirected":false,"response_time":1,"status_code":400,"success":false,"update":false,"user":21,"user_cadence":0}

 === PER TASK METRICS ===
 ------------------------------------------------------------------------------
 Name                     |   # times run |        # fails |   task/s |  fail/s
 ------------------------------------------------------------------------------
 9: table_data_entry      |
   1:                     |             2 |         0 (0%) |     0.04 |    0.00
 -------------------------+---------------+----------------+----------+--------
 Aggregated               |            12 |         0 (0%) |     0.21 |    0.00
 ------------------------------------------------------------------------------
 Name                     |    Avg (ms) |        Min |         Max |     Median
 ------------------------------------------------------------------------------

 9: table_data_entry      |
   1:                     |        4.50 |          1 |           8 |          1
 -------------------------+-------------+------------+-------------+-----------
 Aggregated               |        1009 |          1 |       4,046 |         40

 === PER REQUEST METRICS ===
 ------------------------------------------------------------------------------
 Name                     |        # reqs |        # fails |    req/s |  fail/s
 ------------------------------------------------------------------------------
 GET                      |            12 |      2 (16.7%) |     0.21 |    0.04
 ------------------------------------------------------------------------------
 Name                     |    Avg (ms) |        Min |         Max |     Median
 ------------------------------------------------------------------------------
 GET                      |        1009 |          1 |       4,046 |        280
 ------------------------------------------------------------------------------
 Slowest page load within specified percentile of requests (in ms):
 ------------------------------------------------------------------------------
 Name                     |    50% |    75% |    98% |    99% |  99.9% | 99.99%
 ------------------------------------------------------------------------------
 GET                      |    280 |  2,000 |  4,000 |  4,000 |  4,000 |  4,000

 === ERRORS ===
 ------------------------------------------------------------------------------
 Count       | Error
 ------------------------------------------------------------------------------
 3             GET : 400 Bad Request:
 ------------------------------------------------------------------------------
 ------------------------------------------------------------------------------

In the current release you must include -v to see errors etc on the console. A PR was already merged so this will not be required in the next release. When you enable -v do you see the error?

It is hard to tell as the -v logs everything to the console including debug statements so it is very hard to find errors. Should the per task metrics include the failure count?

Which version of Goose are you using? If a single -v is logging everything then you must be using the latest development version? With the current stable release a single -v should only show INFO level logs and higher. It would take two -vv to log debug messages too. (A PR was recently committed as not showing INFO level messages by default was proving confusing to new users.)
In any case, I reviewed the code in question and we don't seem to be emitting an info!() level message when detecting an invalid HTTP response code as I thought. I agree we should, a PR is welcome. Perhaps we'd check if request_metric.error is not empty, and if so print the error as an INFO level message, around here:
https://github.com/tag1consulting/goose/blob/main/src/goose.rs#L1630

Should the per task metrics include the failure count?

In order for a task to show as an error, you must return Err() from your task. Per-request errors will only show up in the per-request section of the metrics.

I was using 0.15.2 but are on the current main branch. info, warn or error? I also find it helpful to include the request body as in this case and others the issue is often caused by invalid payload. Example code in the location use suggested:
if !request_metric.success {
	if let Ok(r) = response {
		warn!("{:?} {}: {}", &path, &request_metric.error, r.text().await.unwrap_or("".to_string()));
	} else {
		warn!("{:?} {}", &path, &request_metric.error);
	}
	return Err(GooseTaskError::RequestFailed{raw_request: request_metric});
}

In order for a task to show as an error, you must return Err() from your task. Per-request errors will only show up in the per-request section of the metrics.

So I should be doing user.request(req).await?.response?; in the task?

It sounds like you're looking for the debug log. Try adding the following options:
--debug-log debug.log
Now review the debug.log to find complete details about all request errors, including the request made, the response headers, and the response body. (Unfortunately due to this reqwest limitation we are frequently unable to log all request headers.)
You can also store the body of the request made in the request log if you enable --request-body.

So I should be doing user.request(req).await?.response?; in the task?

Take a look at the provided Goose examples.   For example, see the drupal_memcache example and how it calls set_failure when various expectations aren't met.
For much simpler error handling, see the simple which simply passes errors up.

I think the session sample needs to be updated, that is what I started with. It doesn't check the response so the task will always succeed even if it fails.
/// A very simple task that simply loads the front page.
async fn authenticated_index(user: &mut GooseUser) -> GooseTaskResult {
    // This will panic if the session is missing or if the session is not of the right type.
    // Use `get_session_data` to handle a missing session.
    let session = user.get_session_data_unchecked::<Session>();

    // Create a Reqwest RequestBuilder object and configure bearer authentication when making
    // a GET request for the index.
    let reqwest_request_builder = user
        .get_request_builder(&GooseMethod::Get, "/")?
        .bearer_auth(&session.jwt_token);

    // Add the manually created RequestBuilder and build a GooseRequest object.
    let goose_request = GooseRequest::builder()
        .set_request_builder(reqwest_request_builder)
        .build();

    // Make the actual request.
    user.request(goose_request).await?;

    Ok(())
}

The simple example also doesn't check for the response error so the task will always succeed.

Mostly correct. It will fail if request() returns an Err().
There's a number of lines where this function many return an Error:

https://github.com/tag1consulting/goose/blob/main/src/goose.rs#L1497
https://github.com/tag1consulting/goose/blob/main/src/goose.rs#L1508
https://github.com/tag1consulting/goose/blob/main/src/goose.rs#L1520
https://github.com/tag1consulting/goose/blob/main/src/goose.rs#L1623
https://github.com/tag1consulting/goose/blob/main/src/goose.rs#L1628

As explained in the documentation, the simple example is by-design as simple as possible (and clones a similar example from Locust), just showing basic interactions with the Goose library. It is very much not intended to demonstrate all possible Goose functionality or best practices.
For a more fleshed-out example, see the 'umami`](https://github.com/tag1consulting/goose/tree/main/examples/umami) example. See the 'umami documentation', the [`related blog`](https://www.tag1consulting.com/blog/goose-clouds-load-testing-scale), and the [`goose-eggs version`.

The issue with the examples (simple and session) is that the request could fail because of a typo or invalid payload and the task will be marked as successful.
From the task how do you actually check for an error? I just checked user.request(req).await?.response? and it doesn't work because the response is actually Ok when the status is 400+ or different to expect_status_code. I would have though the request will return an error if the status code is different to the what is expected.
In my case I am trying to get the simplest example working. I did that by copying the sample and going from there. When I provided the wrong JSON for the payload of the task it wasn't obvious that it failed because it was saying it succeeded. I only knew it failed because I wasn't getting an incorrect log statement in my back-end.
This isn't criticism, I just want to understand how to use it better because it works great, I am able to send 100s of request with very little overhead which is awesome.

Tasks and Requests are different things. (It may be helpful to see this PR which is working to clarify this https://github.com/tag1consulting/goose/pull/435.
In Goose, there are Requests of which one or more are contained in a Task of which one or more are contained in a TaskSet. It is up to you when writing your load test to determine if a single failed Request results in the entire Task failing or not.
For example: if you have a Task called "load front page" it may 1) load index.html, 2) validate the HTML title and returned Headers, 3) scrape locally hosted assets from the returned html, and 4) load each of those scraped assets (ie images, JS and CSS). It's common for one or more of these assets to be missing (resulting in a 404) or otherwise to generate an error: but even though that Request failed I would consider the Task to have failed.
When writing load tests with Goose, I always enable the error log and the debug log to collect as much information as possible about errors. This will capture all 400+ responses (unless you override this, ie if you WANT to load test a 404 page) and allow you to quickly track down things like typos.
Of course, if you Really want a 1:1 mapping between a single Request and a single Task, you can do this easily enough by parsing the GooseResponse that's returned by, for example, a get Request and returning an Err() from your Task if the Status Code isn't what you expect.
I referred you to the Umami example as it is the most complete load test example included with Goose and demonstrates how to do things like this and much more. I personally tend to leverage the Goose Eggs validate functions to avoid writing boilerplate.

It's a little outdated now, but we tried to capture some real-world examples of using Goose in this blog:
https://www.tag1consulting.com/blog/real-life-goose-load-testing

Please also see this similar discussion: https://github.com/tag1consulting/goose/issues/437

It would be good to be able to easily return an error from a request if the status is invalid. In my case I am testing an API not a web page.  Something like:
let req = user.get_request_builder(&GooseMethod::Post, "api/view/Flight/execute")?
        .basic_auth("admin", Option::<&str>::None)
        .json(&view);

let req = GooseRequest::builder()
        .set_request_builder(req)
        .error_on_fail()
        .build();

Is that something you would consider?

Yes, adding flexibility is always welcome, so long as it doesn't negatively impact performance. This would be a welcome addition.

Fixed in https://github.com/tag1consulting/goose/pull/438


Missing action icons

Action icons (left panel) are missing on my current build of EasyPaint.

See issue #2

Werent there icons in the previous EasyPaint build?

Do you think that old icons good?

They're better than no icon at all for now :) And I don't really remember what they looked like.

Ok, I'll add them to project later.


NameError: name 'text_processing' is not defined

When running !python ../build_vqa_inputs.py --input_dir='../datasets' --output_dir='../datasets'
I see
Traceback (most recent call last):   File "../build_vqa_inputs.py", line 96, in <module>     main(args)   File "../build_vqa_inputs.py", line 69, in main     answer_dict = text_processing.VocabDict(vocab_answer_file) NameError: name 'text_processing' is not defined

try this import text_helper as text_processing in your build_vqa_inputs.py file
this is work for me.


Skip policy evaluation if the repo is not enabled

The allstar run takes a very long time on a github org which has many repos that are excluded by virtue of being archived/forked etc, with these repos being excluded via "optOut" config. Instead this PR skips policy evaluation when the repositories are not enabled.
@jeffmendoza If you feel the old behaviour should be preserved, let me know and I'll make it configurable. I can't imagine most use-cases would want policy evaluation on repos you are opting out.

Hi @coheigea, this operator-level option is supposed to do this: https://github.com/ossf/allstar/blob/main/pkg/config/operator/operator.go#L58-L65
However, due to historical reasons, each policy is implementing it separately (ex: https://github.com/ossf/allstar/blob/main/pkg/policies/security/security.go#L120), and it is a bit messy and inconsistant.
I'd like to refactor that to be checked in the enforce loop as you have here. and remove the checks from each policy.

@jeffmendoza Thanks for the feedback, I made the changes along the lines you suggested - please take another look.

Yeah, I'm seeing that the logic is now changed - the doNothingOnOptOut option is hinged on the whole repo enable/disable and not individual policies.
I think this is better and more desirable behavior. At the allstar.yaml level you would have optOutprivate/fork/archive and then each individual policy would just have all enabled. That said, we should have this documented in the operator.go comment and in the changelog.
Yes, adding an IsEnabled() function to the policy definition makes sense, so the enforce loop can call that and then decide there before calling Check.

@jeffmendoza I added IsEnabled to the policies, please review again.

Awesome!


New check: hhea.caretSlopeRun/Rise

What needs to be checked?
if not is_italic(ttFont):
-> hhea.caretSlopeRun == 0
-> hhea.caretSlopeRise == 1
Detailed description of the problem
@koeberlin Mentioned issues with Adobe InDesign, when this is not set correcly.
Optional fix
if not is_italic(ttFont):
-> hhea.caretSlopeRun == 0
-> hhea.caretSlopeRise == 1
Resources and exact process needed to replicate
https://learn.microsoft.com/en-us/typography/opentype/spec/hhea#:~:text=int16,0 for vertical.
Expected Profile
Please suggest in which profile should it be included. (You could inspect the Profiles's list at https://font-bakery.readthedocs.io/en/stable/fontbakery/profiles/index.html). Most common are:

[ ] Vendor-specific: Google Fonts
[ ] Vendor-specific: Adobe Fonts
[x] OpenType (requirements imposed by the OpenType specification)
[ ] Universal (broadly accepted best practices on the type design community)
[ ] Other:

Expected Result
Which log result level should it have:

[x] 🔥 FAIL (Something that must be addressed for the propper functioning of the font)
[] ⚠ WARN (Highlights potential issues that are suggested to address)

Severity assessment
(On a 1 to 5 level, how "buggy" would the font be considered if not including the aspect checked? Where 1 is something ideal to include but that would not affect the behavior of the font, and 5 is something that could lead to bad performance.)
3

Check is linked to #3670

@koeberlin then this check is a duplicate of #3670


(doc) Add optimization GH issue

Description Of Changes
Replaced the GitHub issue for optimization with the one that was recently reaised and that community and customers can subscribe to.
Motivation and Context
Gives community and customers something they can subscribe to.
Testing

[ ] I have previewed these changes using the Docker Container or another method before submitting this pull request.

Change Types Made

[x] Minor documentation fix (typos etc.).
[ ] Major documentation change (refactoring, reformatting or adding documentation to existing page).
[ ] New documentation page added.
[ ] The change I have made should have a video added, and I have raised an issue for this.

Issue #

Change Checklist

[ ] Requires a change to menu structure (top or left hand side)/
[ ] Menu structure has been updated

Related Issue
N/A

@pauby thanks for getting this updated!


I am facing problem accessing dotnet on macOS terminal

I installed the sdk from this link https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-6.0.101-macos-x64-installer
Operating System: macos
After finishing dotnet 6.0 sdk installation when I try to check dotnet on the terminal it returns "command not found: dotnet".
I am new to macOS. I am not sure what is going wrong.

Hi,
Did you uncheck any options related to PATH while installing dotnet ?
if yes then you can either uninstall and reinstall with the option enabled.
Or
you can follow this here https://stackoverflow.com/questions/53030531/dotnet-command-not-found-in-mac

Did you try closing the terminal window and opening a new one?  The installation process may install to a place that isn't already in your ${PATH} environment variable, but potentially registers it at the end.

Also, are you on a M1 machine? Just trying to confirm whether you should have installed the arm64 version instead.

Thank you all for you quick response. It was path issue. After placing dotnet in \usr\local\bin folder it solved the issue.


New Minecraft Dungeons Version

Minecraft Dungeons got a new update please make it compatible

yes

yes make it compaitable to <IP_ADDRESS>

someone close this they updated it


"Create another" button's suffix malfunctions after 10th file

Describe the bug
After converting a file, and using the "Create another" button in the conversion progress window, the suffix breaks after the 10th file, it should go from "filename.webm-10" to "filename.webm-11", but instead it becomes "filename.webm-10-2". This happens every time the latter number hits 10, so the 20th file is "filename.webm-10-10-2".
To keep a constant numbering of output files, the only option after 10th file is to always use the "close" button, and change the number manually.
To Reproduce
Steps to reproduce the behavior:

Convert 11 files and always use "create another" button in the conversion progress window after conversion is complete.
The suffix of the 11th file becomes "-10-2" instead of "-11".

Expected behavior
The suffix of 11th file should keep the constant numbering, and become "-11".
Screenshots
Output filename for the 22th file as an example. The suffix should be "-22" instead of "-10-10-4"
Don't think settings make a difference here, so no screenshots of them.

Software version(please complete the following information):

Avisynth: 3.7.2
WebM for Lazys: v3.40.3

Test File
Works with any file.

Fixed in v3.40.4.


[stable/prometheus-mongodb-exporter] Add MongoDB Exporter chart

What this PR does / why we need it:
Adds a Prometheus MongoDB Exporter chart. There was a previous PR to add one but it was abandoned.
Which issue this PR fixes
Special notes for your reviewer:
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @cpanato

/lgtm


Remove gh-extension topic from this repository

Hi, thanks for maintaining a list of awesome CLI extensions.
GitHub CLI searches repositories with the gh-extension topic to programmatically discover installable extensions. Your repository has that topic, but it isn't an extension one can install. It would be helpful if you removed the misleading topic, since that would make gh extension search command more efficient. Thank you!

@mislav removed, thanks.


Add JupySQL tutorial

Link to suggestion
https://jupysql.ploomber.io/en/latest/integrations/polars.html?utm_content=buffer13c9f&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer
Targeted section
Tutorials & workshops
Describe your suggestion

Converting SQL Queries to Polars DataFrames with JupySQL - A tutorial that explains how to convert SQL queries to Polars DataFrames using JupySQL by @ploomber.

Checklist

[X] checked if your suggestion is not already listed in Awesome Polars list.
[X] checked if it can fit in an existed section or suggest a new section and explain why your item does not fit into one and what would be the interest of your new section.
[X] checked when it's a repository if it's maintained (archived repository will be rejected).

@ploomber your new page about Polars will be added to the Awesome Polars List !


Stringly-typed HeaderValue?

Hi!
Hyper made the design decision to having properly-typed header values, and cites good reasons for it: https://docs.rs/hyper/0.11.6/hyper/header/index.html
I was wondering if it was an explicit design decision in http to not do this, and if so, could someone go into the reasons?
I'm genuinely curious if this could be a nice addition to http, especially since it seems hyper is planning to move to http-provided types in a future version, or whether there are strong reasons against it.

For a quick answer: https://www.reddit.com/r/rust/comments/6qr9mf/announcing_the_http_crate/dkzqcmq/

Cool, thanks @steveklabnik! @seanmonstar, what does this mean for hyper specifically? Will hyper continue to provide the typed header abstraction on top of http?

hyper will eventually replace its usage of Request and Response for those in http (and thus, the associated types like method, status, headers, etc). It needs to do this to in order to allow hyper to be used with frameworks who don't specifically use hyper, but just http.
The typed headers will be moved a separate crate, I imagine. Related hyper issue.

I have some thoughts re: typed headers (for outside the http crate), but I haven't explored them fully.

@seanmonstar from reddit, linked above

While I still feel that typed headers are a fantastic thing that Rust can provide, they don't fit in http.  And, the typed headers do have an overhead to them (it's very minimal, but it's not free).

Can you explain the overhead, and is there a longer explanation why it was decided that typed headers don't fit into the http crate? I feel that since http is supposed to be the standard HTTP crate that the community uses, it is important that a decision like this be explained in detail.

Just to chime in pseudo-randomly, I personally prefer the "stringly-typed" header values how they are in this crate. Maybe I just have a bad "get off my lawn" attitude, but I know the HTTP headers and generally how they should be written. This crate should worry about the basic HTTP types needed for interoperability,  and not whether I'm reading or writing the right content in my HTTP messages. Moreover, I think a big use case is to translate headers from "raw" sources (HTTP parsers, (Fast)CGI, etc.) where typed header values are of little use anyway.
It's also a lot easier to put a typed abstraction on a string-based approach than the other way around.

Typed headers got lost in transition to 0.12 after all. What a shame!

@vorot93 https://crates.io/crates/hyperx is one option for typed headers.

Is there an easy way to rebuild the typed headers from the HeaderValue ? Because from what I understood, now, the HeaderMap::get(key) will return a HeaderValue.
For example, I used to write something like this :
req.headers().get::()
But now, the get is defined like this :
pub fn get(&self, key: K) -> Option<&T>
The key, if I understand correctly is http::header::IF_MATCH. So I should do something like this :
headers().get(::http::header::IF_MATCH) and this will return a HeaderValue. How can I build the IfMatch type from that ?
Thanks

Hi @fdubois1! I've just run into the same issue myself, and I think I can provide at least a partial solution. Assuming you know which header you want, you can use HeaderMap::get to obtain the HeaderValue that you want, using either a static string or the constant provided by the library (e.g. for the Link header, you can either pass the actual string "link" or this constant). HeaderValue has a to_str method, which lets you get the raw string value of the header, which you can then use to construct the header by using its FromStr implementation. All together, it would look something like this (with the caveat that I haven't compiled or run this snippet):
let header_value = headers.get(::http::header::LINK);
let raw_string = header_value.to_str()?;
let link_header = ::hyperx::header::Link::from_str(raw_string)?;

Converting the entire HeaderMap into a list of hyperx::Header values would be a bit more work, but hopefully this is sufficient for what you need!

There is ongoing work to provide a crate that includes typed headers.

As stated, work has been happening around this. See #264 for thoughts on where the API should "live".


Remove Python 3.7 from tests actions

Given we are dropping Python 3.7 support, we could remove Python 3.7 from our tests actions: https://github.com/microsoft/vscode-pylint/blob/main/.github/workflows/pr-check.yml

Hi, can i work on this