Signal 11 crash with no debug info in backtrace

Tested versions
Reproducible in: v4.3.beta2.official [b75f0485b], v4.3.beta1.official [a4f2ea91a]
System information
Godot v4.3.beta2 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; <IP_ADDRESS>85) - 13th Gen Intel(R) Core(TM) i9-13900K (32 Threads)
Issue description
I am working on a game and I want to test overall stability (this is my first Godot project). The task involves running game logic  code continuously in a loop for ~10 seconds to see if any issues pop up. The code is "pure GDScript" (as it would run on the server app), meaning only code from custom classes; no nodes, no audio, nothing related to visuals, no physics, etc.
When testing this, the app occasionally freezes and crashes (both when running from editor, as well as exported), with CrashHandlerException: Program crashed with signal 11, and the rest of the info does not seem to help in identifying the problem:
CrashHandlerException: Program crashed with signal 11
Engine version: Godot Engine v4.3.beta2.official (b75f0485ba15951b87f1d9a2d8dd0fcd55e178e4)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] error(-1): no debug info in PE/COFF executable
[2] error(-1): no debug info in PE/COFF executable
[3] error(-1): no debug info in PE/COFF executable
[4] error(-1): no debug info in PE/COFF executable
[5] error(-1): no debug info in PE/COFF executable
[6] error(-1): no debug info in PE/COFF executable
[7] error(-1): no debug info in PE/COFF executable
[8] error(-1): no debug info in PE/COFF executable
-- END OF BACKTRACE --

What can I do to get more info about the source of the crash?
I attached the full log from running with --verbose: godot.log
I found https://github.com/Calinou/godot-debug-builds but it seems the last build is from a while back.
Steps to reproduce
I am not able to pinpoint the source of the crash.
Minimal reproduction project (MRP)
I cannot create an MRP as I do not know the source of the crash.

What can I do to get more info about the source of the crash?

Copied from here:

Currently, there are no official builds with debug symbols, so you'll have to compile from source with the debug_symbols=yes SCons option.

Maybe related: #93474

Possibly also related to the fact that the editor itself sometimes crashes while using it (~ 1-2 times/day, when not running the game).
(currently building Godot debug, will return with results)

I built Godot as debug with debug_symbols=yes, and I got the following files (no errors, all went smoothly thanks to the great docs):

After that, I launched the editor through console with --verbose, and tested until I got 4 crashes. Two of the times absolutely no errors were output in the log file, but two of the times I got this:
CrashHandlerException: Program crashed
Engine version: Godot Engine v4.3.beta.custom_build
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[0] <couldn't map PC to fn name>
[1] <couldn't map PC to fn name>
[2] <couldn't map PC to fn name>
[3] <couldn't map PC to fn name>
...
[37] <couldn't map PC to fn name>
[38] <couldn't map PC to fn name>
[39] <couldn't map PC to fn name>
[40] <couldn't map PC to fn name>
-- END OF BACKTRACE --

Here is a full log (godot debug.log)  where you can see multiple "simulations" that run and end correctly, until the last one starts before the crash.
What can I do to try and narrow down the cause of this crash?

What can I do to try and narrow down the cause of this crash?

Try running Godot using the Visual Studio debugger or WinDbg, so that you don't need to rely on Godot's crash handler to see the backtrace.

Try running Godot using the Visual Studio debugger

Question: after I run the Godot editor from Visual Studio with F5, and after that I run the game with F5 from the Godot editor, do I need to re-attach Visual Studio debugger to game process, or leave it on the editor process?

After running the Godot editor from Visual Studio and performing the test 70 times (~1 hour of it running constantly), everything worked perfectly and I was unable to reproduce the crash... Either this is related to it running from VS, or maybe this error was fixed since 4.2 beta2 released, and already corrected in the source code I downloaded today?
Tomorrow I will build the editor and Windows templates separately, and run the test outside VS.

Question: after I run the Godot editor from Visual Studio with F5, and after that I run the game with F5 from the Godot editor, do I need to re-attach Visual Studio debugger to game process, or leave it on the editor process?

I don't remember if Visual Studio automatically attaches to the child process. I recommend passing command line arguments to the debugger so that the project runs directly instead.

Thanks a lot guys for the guidance!
I managed to get some error info while testing a custom build with scons platform=windows debug_symbols=yes, and I got the following in the console/log (not launching with --verbose):
CrashHandlerException: Program crashed
Engine version: Godot Engine v4.3.beta.custom_build
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[0] Variant::reference (Z:\godot\src\core\variant\variant.cpp:1090)
[1] GDScriptInstance::get (Z:\godot\src\modules\gdscript\gdscript.cpp:1730)
[2] Object::get (Z:\godot\src\core\object\object.cpp:310)
[3] Variant::get_named (Z:\godot\src\core\variant\variant_setget.cpp:314)
[4] GDScriptFunction::call (Z:\godot\src\modules\gdscript\gdscript_vm.cpp:1167)
[5] GDScriptInstance::callp (Z:\godot\src\modules\gdscript\gdscript.cpp:2028)
[6] Object::callp (Z:\godot\src\core\object\object.cpp:786)
[7] Variant::callp (Z:\godot\src\core\variant\variant_call.cpp:1211)
[8] GDScriptFunction::call (Z:\godot\src\modules\gdscript\gdscript_vm.cpp:1768)
[9] GDScriptInstance::callp (Z:\godot\src\modules\gdscript\gdscript.cpp:2028)
[10] Object::callp (Z:\godot\src\core\object\object.cpp:786)
[11] Variant::callp (Z:\godot\src\core\variant\variant_call.cpp:1211)
[12] GDScriptFunction::call (Z:\godot\src\modules\gdscript\gdscript_vm.cpp:1768)
[13] GDScriptInstance::callp (Z:\godot\src\modules\gdscript\gdscript.cpp:2028)
[14] Object::callp (Z:\godot\src\core\object\object.cpp:786)
[15] Variant::callp (Z:\godot\src\core\variant\variant_call.cpp:1211)
[16] GDScriptFunction::call (Z:\godot\src\modules\gdscript\gdscript_vm.cpp:1768)
[17] GDScriptLambdaSelfCallable::call (Z:\godot\src\modules\gdscript\gdscript_lambda_callable.cpp:275)
[18] Callable::callp (Z:\godot\src\core\variant\callable.cpp:58)
[19] Object::emit_signalp (Z:\godot\src\core\object\object.cpp:1190)
[20] Node::emit_signalp (Z:\godot\src\scene\main\node.cpp:3890)
[21] Object::emit_signal<> (Z:\godot\src\core\object\object.h:936)
[22] BaseButton::_pressed (Z:\godot\src\scene\gui\base_button.cpp:138)
[23] BaseButton::on_action_event (Z:\godot\src\scene\gui\base_button.cpp:176)
[24] BaseButton::gui_input (Z:\godot\src\scene\gui\base_button.cpp:69)
[25] Control::_call_gui_input (Z:\godot\src\scene\gui\control.cpp:1829)
[26] Viewport::_gui_call_input (Z:\godot\src\scene\main\viewport.cpp:1570)
[27] Viewport::_gui_input_event (Z:\godot\src\scene\main\viewport.cpp:1836)
[28] Viewport::push_input (Z:\godot\src\scene\main\viewport.cpp:3259)
[29] Window::_window_input (Z:\godot\src\scene\main\window.cpp:1690)
[30] CallableCustomMethodPointer<Window,Ref<InputEvent> const &>::call (Z:\godot\src\core\object\callable_method_pointer.h:103)
[31] Callable::callp (Z:\godot\src\core\variant\callable.cpp:58)
[32] Callable::call<Ref<InputEvent> > (Z:\godot\src\core\variant\variant.h:876)
[33] DisplayServerWindows::_dispatch_input_event (Z:\godot\src\platform\windows\display_server_windows.cpp:3510)
[34] Input::_parse_input_event_impl (Z:\godot\src\core\input\input.cpp:774)
[35] Input::flush_buffered_events (Z:\godot\src\core\input\input.cpp:1053)
[36] DisplayServerWindows::process_events (Z:\godot\src\platform\windows\display_server_windows.cpp:2978)
[37] OS_Windows::run (Z:\godot\src\platform\windows\os_windows.cpp:1686)
[38] widechar_main (Z:\godot\src\platform\windows\godot_windows.cpp:181)
[39] _main (Z:\godot\src\platform\windows\godot_windows.cpp:208)
[40] main (Z:\godot\src\platform\windows\godot_windows.cpp:220)
[41] __scrt_common_main_seh (D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288)
[42] <couldn't map PC to fn name>
-- END OF BACKTRACE --

Here is the full log: godot.log
You can see in it that the test ran 33 times before it crashed on attempt 34, but this is completely random, as it sometimes crashes on the first try as well.

I mentioned in my original post that my test uses only "pure GDScript", but there is one other thing I actually use, and that is Image objects, as my game maps are stored as images so I can apply Image methods to them (get_pixel(), blend_rect(), create_from_data() and decompress_dynamic()).
Though I cannot see something related to images in the error info.
Regarding the editor crashes: does the Gogot editor itself save a log somewhere? I was unable to find one at the typical location where Godot projects keep their user files: %appdata%\Godot\

Regarding the editor crashes: does the Gogot editor itself save a log somewhere? I was unable to find one at the typical location where Godot projects keep their user files: %appdata%\Godot\

It does not, but you can start the editor from a terminal and look at the output. On Windows, make sure to use the .console.exe wrapper executable.

I have this same error so, i think I can add some extra information.

I started getting this error when I started using 4.3 beta 2 but now it also happens when I use other versions of Godot like 4.3 beta 3 or 4.2.2.
It's most likely not related to anything in the projects, I have tried with empty projects and it still happens even when just creating the project.
It also happens when running the projects and the message is the same.

My main concern with this rare/random crashing would be not as much the game client itself, but having a server app that needs to run reliably for days/weeks (assuming no errors in my own code).
I'm not sure if this is relevant, but I also rarely get some random GDScript errors, like an "invalid access of a variable" that definitely exists, or an "invalid access of an array element" that is definitely there (I got this on an array declared directly in the script file and which is never modified). In the editor, the code would pause at such an error, but if I resume, it continues working fine. To me would appear that GDScript itself sometimes "glitches".
I will get exact error messages/screenshots the next time I see one of these.

Here is an example of a random GDScript error that I previously mentioned. Hovering with the mouse over the cElement dictionary shows that the rotation property actually exists (and cSprite is a Sprite2D so it also has a rotation)

In that case, a dictionary needs to be accessed with braces:
cSprite.rotation = cElement["rotation"]

Dictionaries are not the same as objects in GDScript.

I noticed that both methods normally work, but I did not know that the braces method is better practice, thank you for this.

I noticed that both methods normally work, but I did not know that the braces method is better practice, thank you for this.

Okay I'll admit I didn't know dictionaries could be accessed by that syntax. Would it be possible to share more of the code related to that dictionary? Rename types and things as needed.

Would it be possible to share more of the code related to that dictionary?

There is no special "code" about it, it's just a simple dictionary on which I set and read values from. When I started using Godot I was using the brackets syntax to set/get values (as I was used in the old Adobe AIR/Flash), but then I saw I can get/set values directly with dot syntax, which to me looks cleaner.
I love the dynamic typing of GDScript because I can focus on building my game instead of static-typing everything, and I'm totally fine with the small performance loss caused by it.

(oh wow, adobe air that takes me back...)
What I meant is, if we can see where this dictionary is created, passed along, etc. that might be a clue to what's causing the bug.

This particular dictionary is loaded from a .json on disk, parsed with JSON.parse_string(), and stored. As it describes a generic type of object in my game ("WorldObject" as visible in my screenshot, which extends Sprite2D), whenever I create such a new object instance I duplicate the dictionary with duplicate(true) and pass it to the object class, which does its thing with it, by continuously reading/changing values in it. I use the dot syntax, and I use the .has() method before accessing any properties that may or may not exist.
If the error would be caused by how I use the dictionary, I would expect it to show up more regularly, but instead it only happens randomly about once every few days (and my game regularly uses hundreds of these objects).

I got the new 4.3 beta 3 and tested again on 3 PCs (for a few hours). To my relief, it seems that only my PC experiences this rare, random, unreproducible crashing (but somehow not when running Godot from source with VS).
On one of the crashes I did get a new error I did not see before:
USER ERROR: Reaching unreachable case
   at: reduce_expression (modules/gdscript/gdscript_analyzer.cpp:2529)

As it would seem this is just an isolated issue, like in my case, it would explain the lack of other reports on this. For now I guess I can have some peace of mind to continue working in Godot knowing that it is indeed reliable :)
If you feel this issue is not worth any further investigation, please feel free to close it.

Due to what CPU it is, i need to know if it's the CPU itself or Godot.

I got the new 4.3 beta 3 and tested again on 3 PCs (for a few hours). To my relief, it seems that only my PC experiences this rare, random, unreproducible crashing (but somehow not when running Godot from source with VS).

This message makes it more look like this is the CPU and not Godot here.

Mine is i9-13900K, and the others I tested on and worked without problems are: i7-8700K, i5-9300H, i5-4690T. Worth to note that my PC is pretty stable otherwise.

Mine is i9-13900K, and the others I tested on and worked without problems are: i7-8700K, i5-9300H, i5-4690T. Worth to note that my PC is pretty stable otherwise.

Are you underclocking currently?

I did not make any changes to voltages, but the CPU has always been limited to 175W.

I think I have the same problem. Is there a solution?
CrashHandlerException: Program crashed with signal 11
Engine version: Godot Engine v4.3.stable.official (77dcf97d82cbfe4e4615475fa52ca03da645dbd8)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] error(-1): no debug info in PE/COFF executable
[2] error(-1): no debug info in PE/COFF executable
[3] error(-1): no debug info in PE/COFF executable
[4] error(-1): no debug info in PE/COFF executable
[5] error(-1): no debug info in PE/COFF executable
[6] error(-1): no debug info in PE/COFF executable
[7] error(-1): no debug info in PE/COFF executable
[8] error(-1): no debug info in PE/COFF executable
[9] error(-1): no debug info in PE/COFF executable
[10] error(-1): no debug info in PE/COFF executable
[11] error(-1): no debug info in PE/COFF executable
[12] error(-1): no debug info in PE/COFF executable
[13] error(-1): no debug info in PE/COFF executable
[14] error(-1): no debug info in PE/COFF executable
[15] error(-1): no debug info in PE/COFF executable
[16] error(-1): no debug info in PE/COFF executable
[17] error(-1): no debug info in PE/COFF executable
[18] error(-1): no debug info in PE/COFF executable
[19] error(-1): no debug info in PE/COFF executable
-- END OF BACKTRACE --

I have concluded mostly that my problem is caused by the CPU which may be dying, since it's a 13900K and subject to the degradation issue I just recently found out about.
@404ar Do you have a high-power 13th/14th gen Intel CPU?

I have an old Intel® Celeron® Processor 2957U 2M Cache, 1.40 GHz i think that's the problem thank you @htmiel .

@htmiel  I don't think the problem is with the processor, because I tried it on Linux and it worked without crashing , i think the problem is in the Windows system?

I tested on a different CPU, and let a Godot Windows app run under high load for 2 days straight, no error. Your error could be either some isolated Windows issue, or something hardware related. But on a "healthy" Windows install and hardware, Godot worked great (at least with the Godot features I used).
If you can consistently reproduce the issue, you should try to isolate it as much as possible, to find out where it comes from, and them make a minimal reproduction project (MRP) that the contributors can investigate.

I replaced my CPU today, and with all the tests I did, I had no more errors. This confirms that the errors I mentioned here were caused by my degraded Intel CPU.


Remove errant line breaks which disrupt the table rendering.

Removes erroneous/errant line breaks which disrupt the table formatting/rendering.

issue has been fixed in another PR.


[Bug] Module not found

error message:
ERROR  Failed to compile

ERROR in ./~/haul/src/utils/polyfillEnvironment.js
Module not found: Error: Can't resolve 'InitializeCore' in 'C:\dev-projects\react-native\TestHaul\node_modules\haul\src\utils'
 @ ./~/haul/src/utils/polyfillEnvironment.js 1:487-512
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'AccessibilityInfo' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:105-133
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

details

ERROR  Failed to compile

ERROR in ./~/haul/src/utils/polyfillEnvironment.js
Module not found: Error: Can't resolve 'InitializeCore' in 'C:\dev-projects\react-native\TestHaul\node_modules\haul\src\utils'
 @ ./~/haul/src/utils/polyfillEnvironment.js 1:487-512
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'AccessibilityInfo' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:105-133
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ActivityIndicator' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:167-195
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ReactNativeART' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:215-240
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Button' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:263-280
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'DatePickerIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:310-334
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'DrawerLayoutAndroid' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:370-400
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'FlatList' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:425-444
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Image' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:466-482
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ImageEditor' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:510-532
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ImageStore' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:559-580
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'KeyboardAvoidingView' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:617-648
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ListView' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:673-692
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Modal' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:714-730
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'NavigatorIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:759-782
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Picker' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:805-822
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'PickerIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:848-868
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ProgressBarAndroid' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:903-932
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ProgressViewIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:964-990
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ScrollView' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1017-1038
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'SectionList' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1066-1088
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'SegmentedControlIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1124-1154
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Slider' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1177-1194
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'SnapshotViewIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1226-1252
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Switch' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1275-1292
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'RefreshControl' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1323-1348
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'StatusBar' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1374-1394
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'SwipeableListView' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1428-1456
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'TabBarIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1482-1502
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Text' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1523-1538
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'TextInput' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1564-1584
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ToastAndroid' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1613-1636
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ToolbarAndroid' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1667-1692
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Touchable' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1718-1738
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'TouchableHighlight' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1773-1802
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'TouchableNativeFeedback' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1842-1876
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'TouchableOpacity' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1909-1936
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'TouchableWithoutFeedback' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:1977-2012
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'View' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2033-2048
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ViewPagerAndroid' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2081-2108
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'VirtualizedList' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2140-2166
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'WebView' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2190-2208
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ActionSheetIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2239-2264
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'AdSupportIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2293-2316
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Alert' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2338-2354
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'AlertIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2379-2398
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Animated' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2423-2442
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'AppRegistry' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2470-2492
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'AppState' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2517-2536
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'AsyncStorage' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2565-2588
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'BackAndroid' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2616-2638
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'BackHandler' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2666-2688
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'CameraRoll' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2715-2736
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Clipboard' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2762-2782
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'DatePickerAndroid' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2816-2844
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'DeviceInfo' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2871-2892
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Dimensions' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2919-2940
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Easing' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:2963-2980
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ReactNative' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3011-3033
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'I18nManager' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3076-3098
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ImagePickerIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3129-3154
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'InteractionManager' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3189-3218
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Keyboard' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3243-3262
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'LayoutAnimation' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3294-3320
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Linking' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3344-3362
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'NativeEventEmitter' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3397-3426
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'NetInfo' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3450-3468
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'PanResponder' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3497-3520
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'PermissionsAndroid' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3555-3584
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'PixelRatio' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3611-3632
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'PushNotificationIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3668-3698
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Settings' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3723-3742
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Share' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3764-3780
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'StatusBarIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3809-3832
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'StyleSheet' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3859-3880
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Systrace' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3905-3924
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'TimePickerAndroid' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:3958-3986
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'TVEventHandler' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4017-4042
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'UIManager' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4068-4088
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Vibration' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4114-4134
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'VibrationIOS' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4163-4186
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'RCTDeviceEventEmitter' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4221-4253
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'NativeModules' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4356-4380
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'Platform' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4405-4424
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'RCTNativeAppEventEmitter' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4291-4326
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'requireNativeComponent' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4515-4548
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'EdgeInsetsPropType' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4689-4718
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'processColor' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4453-4476
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'PointPropType' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4748-4772
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ViewPropTypes' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4802-4826
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'ColorPropType' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4630-4654
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

ERROR in ./~/react-native/Libraries/react-native/react-native-implementation.js
Module not found: Error: Can't resolve 'takeSnapshot' in 'C:\dev-projects\react-native\TestHaul\node_modules\react-native\Libraries\react-native'
 @ ./~/react-native/Libraries/react-native/react-native-implementation.js 1:4577-4600
 @ ./index.android.js
 @ multi ./~/haul/src/utils/polyfillEnvironment.js ./index.android.js

step-by-step:
mkdir HaulBug && cd HaulBug
yarn init --yes
yarn add react-native-cli --dev
cd .. && "./HaulBug/node_modules/.bin/react-native" init HaulBug
cd HaulBug
yarn add react-native-cli --dev

yarn add haul --dev
sed -i '4 i project.ext.react = [cliPath: "node_modules/haul/bin/cli.js"]' ./android/app/build.gradle
"./node_modules/.bin/haul" init
yarn run haul start -- --platform android

Current Behavior
incorrect configuration

Expected Behavior
correct configuration

Haul Configuration (webpack.haul.js)

default
Your Environment

software
version

Haul
1.0.0-beta.1

react-native
0.45.1

node
8.1.2

npm or yarn
0.24.6 (yarn)

Fixed in #177


Create a CONTRIBUTORS.md

We don't have a list of expectations for how we want and expect people to contribute. This should be a pretty easy fix.

fixed by #2


Developer Documentation

If this is supposed to be open source project, there are some things not clear to new devs, we should clarify this somewhere not just in a Github PR comment (https://github.com/Nyumat/TalkToBeavs/pull/32#issuecomment-1530016186).
Also I'm not sure how to handle outside contributors who should not (for security reasons) access our backend and database credentials.
Either tell them to use our production API and focus on frontend issues only.
Or teach them how to set up their own backend and database (e.g. on MongoDB free plan) for testing purposes.

there are some things not clear to new devs

Can you expand more on what needs to be clarified?

Also I'm not sure how to handle outside contributors who should not (for security reasons) access our backend and database credentials.

What are you asking, exactly? Our current security measures work against this.
(JWT, rate limiting, no cors, no x-powered-by, enforcing environment variables)

Either tell them to use our production API and focus on frontend issues only.

If 'them' is the users who should not access our backend and database credentials, sharing our database credentials can pose a significant security risk and grant unnecessary access to sensitive OSU student data. Focusing on frontend issues would limit a series of developers wanting to contribute to the backend.

How will developers contribute to the backend or frontend

Three options:

Give developers our backend credentials

Will go wrong for multiple obvious reasons. Even if we do decide to go about it this way, we'll need to only provide keys to proven contributors.

Create a dev. environment for contributors looking to test the front end with their backend code changes.

This option makes the most sense. We provide an empty, dev database instance where developers who need access to the full stack of TalkToBeavs have the ability to test their changes in an isolated environment, away from our users. I see docker being a great option here.

Open Source, Closed Commit

This may not make sense at first, but this option is if we decide that we want tight control over who can access the developer environment of TalkToBeavs. We keep the repo, yet do not allow developers to make changes outside of the founders. This in my opinion defeats the purpose of GitHub, having a MIT license, and creating this in the first place.

I say we stick with option two. If you think the documentation could be better, I think that'd be better served for confluence,   jira, or similar tools. Or by just having CONTRIBUTING.md in both the /backend and /frontend directories to onboard prospective contributors.


Update French translation (#600 and #604)

Update French translation for PRs #600 and #604

@dreacot after 5 months, probably.
I will have a look when possible.

Thanks, awaiting your feedback

@dreacot it should be good now.
I merged master and added all missing translations since this PR.

@jdambron thanks a lot👌🏽, before would probably merge this last, for the last minute PRs coming up


install sklearn to debian

and fix nightly-debian-cpu

I wanted to merge this as we have no tests for it anyway. But we require all the tests now...
@tensorflow-jenkins test this please.

I can't say how much I hate the new merge policy, nobody being able to merge if it's an actual merge.


Adding contact information for large migrations

@bharathsreenivas - if you're authoring articles in the Microsoft docset, you should be using the private repos. Can you do that in the future? For this PR, can you provide a reviewer's alias? thanks.
here's some info about working in the private repos:

Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you review staging and fix all validation issues, you can tag an author for review or add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see How to get to the private repo. You can also take a look at the GitHub account setup page for additional details on making sure you're set up.

Sure - I will use the private repo the next time. @SnehaGunda can be a reviewer for this

#sign-off

... waiting on approval or sign off from @SnehaGunda

#sign-off

@SnehaGunda: I'm sorry - only the author of this article, @bharathsreenivas, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off


ConvertTo-PnPClientSidePage : Field or property "ExportMode" does not exist.

Command: ConvertTo-PnPClientSidePage -Identity "Ankita13.aspx" -PublishingPage -TargetConnection $target -Overwrite-PageLayoutMapping  "C:\QianetMig\Prod\pagelayoutmapping.xml" –AddPageAcceptBanner
Error: ConvertTo-PnPClientSidePage : Field or property "ExportMode" does not exist.

Hi @AAnkitaAswal,
This issue has been fixed in the dev release and will be part of the upcoming September release. I assume you're trying to migrate publishing pages from 2013/2016 on-premises to SPO and those pages have web parts on them?

Hi @AAnkitaAswal,
This issue has been fixed in the dev release and will be part of the upcoming September release. I assume you're trying to migrate publishing pages from 2013/2016 on-premises to SPO and those pages have web parts on them?

Hi Jasenbe,
Yes, we are trying to migrate pages from SP2013 to SPO and these pages do have custom (VS) webparts as well...
so this will be available for all in Sep release.

Correct. Alternatively you can build your own version of the modernization framework and PnP PS, but September release will be out in about 2 weeks.

closing the issue now. If you still have issues with the September release then please open a new issue.

Hi Bert,
Just to touch base, if the functionality to migrate publishing pages from on prem server to online modern pages is now available through pnp.
Regards,
Ankita Aswal
From: Bert Jansen<EMAIL_ADDRESS>Sent: Monday, August 26, 2019 4:10 PM
To: SharePoint/sp-dev-modernization<EMAIL_ADDRESS>Cc: Ankita Aswal - Contractor<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [SharePoint/sp-dev-modernization] ConvertTo-PnPClientSidePage : Field or property "ExportMode" does not exist. (#251)
Hi @AAnkitaAswalhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAAnkitaAswal&data=02|01|Ankita.Aswal%40contractor.qiagen.com|12c8bfb71d304f48c8aa08d72a11ceb2|dc81d03c239c4fd5a96f18a58773c86c|0|0|637024128293893827&sdata=8fR12e9YwwKpmr99Flhfsv4KCEtOz1C0Jas%2Fzg23iy0%3D&reserved=0,
This issue has been fixed in the dev release and will be part of the upcoming September release. I assume you're trying to migrate publishing pages from 2013/2016 on-premises to SPO and those pages have web parts on them?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-modernization%2Fissues%2F251%3Femail_source%3Dnotifications%26email_token%3DALACWUVVRAFCJEKPMMZ3N6TQGOXJTA5CNFSM4IPOJOKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5D75EI%23issuecomment-524811921&data=02|01|Ankita.Aswal%40contractor.qiagen.com|12c8bfb71d304f48c8aa08d72a11ceb2|dc81d03c239c4fd5a96f18a58773c86c|0|0|637024128293903822&sdata=zOKA8BWLnPcXk51XgmFUfo9bIA6XKsMCWroyTMEi3Wc%3D&reserved=0, or mute the threadhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALACWUWH7ELBGLWSSJVPFX3QGOXJTANCNFSM4IPOJOKA&data=02|01|Ankita.Aswal%40contractor.qiagen.com|12c8bfb71d304f48c8aa08d72a11ceb2|dc81d03c239c4fd5a96f18a58773c86c|0|0|637024128293903822&sdata=QFjDtsnGNMi4YzQxgPcbeRS0fB0obDiFJUUB2Hlt1UY%3D&reserved=0.

@AAnkitaAswal , yes it is but would recommend waiting for the October release as we've fixed one other related bug for this scenario. The October release will be available on Monday October 7th.

Hi Jarsen,
I am still facing same issue:
<EMAIL_ADDRESS>I had updated PNP powershell online.
Regards,
Ankita Aswal
From: Bert Jansen<EMAIL_ADDRESS>Sent: Friday, October 4, 2019 12:13 PM
To: SharePoint/sp-dev-modernization<EMAIL_ADDRESS>Cc: Ankita Aswal - Contractor<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [SharePoint/sp-dev-modernization] ConvertTo-PnPClientSidePage : Field or property "ExportMode" does not exist. (#251)
@AAnkitaAswalhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAAnkitaAswal&data=02|01|Ankita.Aswal%40contractor.qiagen.com|7298acc9be4a457fbc5608d748b36a25|dc81d03c239c4fd5a96f18a58773c86c|0|0|637057807736325874&sdata=qcbRroeJL3RiOQSDFIMb2hOKbeSGX9icbDc8weC%2FIXs%3D&reserved=0 , yes it is but would recommend waiting for the October release as we've fixed one other related bug for this scenario. The October release will be available on Monday October 7th.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-modernization%2Fissues%2F251%3Femail_source%3Dnotifications%26email_token%3DALACWUXTHX3FK24QMXZXNWLQM4JKDA5CNFSM4IPOJOKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEALGIKQ%23issuecomment-538338346&data=02|01|Ankita.Aswal%40contractor.qiagen.com|7298acc9be4a457fbc5608d748b36a25|dc81d03c239c4fd5a96f18a58773c86c|0|0|637057807736335873&sdata=m5qlr8cWQG20yv0Ik1hnSQyLGesBlhAMD3x1O4Bpk1M%3D&reserved=0, or mute the threadhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALACWUXGDHR43IPZEEWHVU3QM4JKDANCNFSM4IPOJOKA&data=02|01|Ankita.Aswal%40contractor.qiagen.com|7298acc9be4a457fbc5608d748b36a25|dc81d03c239c4fd5a96f18a58773c86c|0|0|637057807736345870&sdata=YiTAniZcdMIM0sXYlN%2BYaWRcSW9pL6q26RYp05IBHp0%3D&reserved=0.

Hi @AAnkitaAswal the screenshot didn’t upload, can you try again. Also if you get an error and the logs, we made some tweaks to those to get more info about the types of transforms. Thanks.

Hi Paul,
Here is the error message-
PS C:\QianetMig> Update-Module SharePointPnPPowerShell*
PS C:\QianetMig> C:\QianetMig\ConvertPage.ps1
ConvertTo-PnPClientSidePage : Field or property "ExportMode" does not exist.
At C:\QianetMig\ConvertPage.ps1:21 char:1

ConvertTo-PnPClientSidePage -Identity "AnkitaTest1.aspx" -PublishingP ...

  + CategoryInfo          : WriteError: (:) [ConvertTo-PnPClientSidePage], ServerException
  + FullyQualifiedErrorId : EXCEPTION,SharePointPnP.PowerShell.Commands.ClientSidePages.ConvertToClientSidePage

PS C:\QianetMig>
Regards,
Ankita Aswal
From: Paul Bullock<EMAIL_ADDRESS>Sent: Wednesday, October 9, 2019 9:48 AM
To: SharePoint/sp-dev-modernization<EMAIL_ADDRESS>Cc: Ankita Aswal - Contractor<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [SharePoint/sp-dev-modernization] ConvertTo-PnPClientSidePage : Field or property "ExportMode" does not exist. (#251)
Hi @AAnkitaAswalhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAAnkitaAswal&data=02|01|Ankita.Aswal%40contractor.qiagen.com|5256aef8e98b42066c7808d74c8d1064|dc81d03c239c4fd5a96f18a58773c86c|0|0|637062041066978081&sdata=YzxB0H30vwUyFyMiIB5gGFgaF2A4nYy9CfkacrSFed4%3D&reserved=0 the screenshot didn’t upload, can you try again. Also if you get an error and the logs, we made some tweaks to those to get more info about the types of transforms. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-modernization%2Fissues%2F251%3Femail_source%3Dnotifications%26email_token%3DALACWUTUG4ZNQHLCCAMREKLQNWEEPA5CNFSM4IPOJOKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAW7FVA%23issuecomment-539882196&data=02|01|Ankita.Aswal%40contractor.qiagen.com|5256aef8e98b42066c7808d74c8d1064|dc81d03c239c4fd5a96f18a58773c86c|0|0|637062041066988076&sdata=jwreG1g%2Fe4Vj1Kq7tQFhmzzR5EepOHAfp1eYpb1%2F1Pw%3D&reserved=0, or mute the threadhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALACWUQ5QPZQM4SGI77CE4LQNWEEPANCNFSM4IPOJOKA&data=02|01|Ankita.Aswal%40contractor.qiagen.com|5256aef8e98b42066c7808d74c8d1064|dc81d03c239c4fd5a96f18a58773c86c|0|0|637062041066988076&sdata=c8zg1%2Bv6RxZUuCSgp12nt5jwaoMxrs59veR5RlL3UCQ%3D&reserved=0.

Hi @AAnkitaAswal ,
Please run the transformation cmdlet with logging (add this: -LogType File -LogVerbose -LogFolder "c:\temp") and then provide us with the generated report. When you look at the page that fails, where are the custom web parts inserted? In a web part zone or in a field? Also remove the -PageAcceptBanner as that feature will not work for publishing pages.

Hi Jansen,
I have attached report,
Yes page has a content webpart added in the topmost webpart zone.
We havenot added -PageAcceptBanner in the script.
It worked, if there is not webpart in source page.
Regards,
Ankita Aswal
From: Bert Jansen<EMAIL_ADDRESS>Sent: Wednesday, October 9, 2019 11:34 PM
To: SharePoint/sp-dev-modernization<EMAIL_ADDRESS>Cc: Ankita Aswal - Contractor<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [SharePoint/sp-dev-modernization] ConvertTo-PnPClientSidePage : Field or property "ExportMode" does not exist. (#251)
Hi @AAnkitaAswalhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAAnkitaAswal&data=02|01|Ankita.Aswal%40contractor.qiagen.com|31ecc1f918bb41d1bec708d74d005c7f|dc81d03c239c4fd5a96f18a58773c86c|0|0|637062536260165067&sdata=eT9InuwB0bCLgaA8J%2Fe4cbZFywHCcDCYyEaBSO6dvi4%3D&reserved=0 ,
Please run the transformation cmdlet with logging (add this: -LogType File -LogVerbose -LogFolder "c:\temp") and then provide us with the generated report. When you look at the page that fails, where are the custom web parts inserted? In a web part zone or in a field? Also remove the -PageAcceptBanner as that feature will not work for publishing pages.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-modernization%2Fissues%2F251%3Femail_source%3Dnotifications%26email_token%3DALACWUVCSIV7RXT6KT2636TQNZE3PA5CNFSM4IPOJOKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAZPJPI%23issuecomment-540210365&data=02|01|Ankita.Aswal%40contractor.qiagen.com|31ecc1f918bb41d1bec708d74d005c7f|dc81d03c239c4fd5a96f18a58773c86c|0|0|637062536260175060&sdata=a%2FmAZ%2F89enWyn4DHhY2jYY%2BSt%2Beq%2BlF3NGdSaW9M0B4%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALACWUQCEBQSBHTMCCCNPPLQNZE3PANCNFSM4IPOJOKA&data=02|01|Ankita.Aswal%40contractor.qiagen.com|31ecc1f918bb41d1bec708d74d005c7f|dc81d03c239c4fd5a96f18a58773c86c|0|0|637062536260175060&sdata=0DM0e3ndGbCyH2skFjMZ2eCYD6iActLu%2B4kUnS1DFb8%3D&reserved=0.

Hi @AAnkitaAswal ,
Answering on this via mail will drop the attachments...can you go to the issue in git (https://github.com/SharePoint/sp-dev-modernization/issues/251) and add the attachments over there?

Page-Transformation-Report-10-10-2019-8-48-49-AM.txt

The October version log file will show the version numbers, your log does not...this means you're still using an older version. Can you try to upgrade pnp-powershell to the latest release (October version, 3.14.1910.0).
Running get-module *pnp* should show the version you've currently loaded.

So you should be all good then. Closing this issue.


How can export ONNX?

Hi,
Can you export ONNX of model?

Hi, I tried with ONNX export, but, there is some issue while exporting because,the iference speed becomes 10 Sec per image with onnx model!!!!

Hi, I tried with ONNX export, but, there is some issue while inference with ONNX model because, the inference speed becomes 10 Sec per image with onnx model!!!!

Hi MILearnerAkash,
Do you have the pre-trained pytorch model? I want this to export the onnx, but I can't find it.


MONDO:0006609

Mondo term (ID and Label):
seborrheic infantile dermatitis MONDO:0006609
Xref that should be fixed (ID and label):
C0221244 (UMLS) this is a better match for the parent concept of "seborrheic dermatitis" (SD)
Your nano-attribution (ORCID)
If you don't have an ORCID, you can sign up for one here
Other comments:
C0343047 is for "Complement component 5 deficiency" which X-refs SNOMED 7297005 'Generalized seborrheic dermatitis of infants,' 'Leiner's disease,' and 'Infantile seborrheic dermatitis' (But this UMLS CUI is problematic, since it equates OMIM 609536 https://www.omim.org/entry/609536?search=609536&highlight=609536 with the concept of infantile SD, so I will follow up with UMLS separate to split the MIM number and related concepts out, since that condition has multiple symptoms beyond just dermatitis.)
Alternatively, C0263233 is for "cradle cap"
Also, this term (MONDO:0006609) has an exact synonym of "Pityriasis capitis" but this is a separate concept in Mondo: MONDO:0024348 which I am struggling to find a good definition for (PMID: 32416039 indicates it is a more severe form of dandruff and https://www.ncbi.nlm.nih.gov/books/NBK551707/ indicates it's a mild form of SD) UMLS Maps SCTID:400201008  to Seborrheic dermatitis of scalp, CUI: C0221244) So Maybe SD (MONDO:0006608) needs a new child term, the concept for Pityriasis capitis aka Seborrheic dermatitis of scalp, CUI: C0221244, which then has a child of 'infantile SD'?

@kanems what if we just moved the UMLS:C0221244 (Pityriasis capitis) to MONDO_0024348 'pityriasis capitis' ?

note to self, here is another article: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4852869/

This article suggests these are separate diseases (as we have them currently classified: https://jamanetwork.com/journals/jamadermatology/fullarticle/479236.

https://www.aad.org/public/diseases/a-z/seborrheic-dermatitis-overview Suggests that SD is a broad term, of which cradle cap is an infantile sub-type. So I think the relationships are correct in Mondo, but this is what I think needs to be done:

[ ] Reject "Pityriasis capitis" as an exact synonym on MONDO:0006609 seborrheic infantile dermatitis
[ ] Reject UMLS:C0221244 "Seborrheic dermatitis of scalp" from X-refs on MONDO:0006609 seborrheic infantile dermatitis  (or change nature of the relationship from equivalent/exact to close? this UMLS CUI doesn't limit to an infantile onset/presentation

@kanems what if we just moved the UMLS:C0221244 (Pityriasis capitis) to MONDO_0024348 'pityriasis capitis' ?
Yes, I think this would work because SNOMED 400201008 maps to this CUI in UMLS, syns: Dandruff, Furfuracea from the SCTID.
Do we want to add MONDO_0024348 'pityriasis capitis'  to the branch under seborrheic dermatitis, as a sibling to the infantile form? If we're confident (enough) that this is synonymous with Dandruff, then it would have a syn of "Seborrheic dermatitis of scalp" (which is UMLS's preferred name for this CUI). I Don't know the differences between exanthem and dermatitis to know if being in both of those branches of "skin disease" is incorrect or not.

Pityriasis capitis commonly known as dandruff. It is a mild manifestation of seborrheic dermatitis. I do not think that a dermatologist would equate dandruff with a disease entity that is a subform of seborrheic dermatitis, and I am not sure that it is proper to regard it as a disease in its own right. Possibly it should be obsoleted and created as an HPO term. Do we have a dermatologist we can ask?

Based on this article (https://pubmed.ncbi.nlm.nih.gov/32416039/), this is considered a disease:
"Pityriasis capitis commonly known as dandruff is one of the most common and widely seen dermatological disease that affects majority of the world population."


[BUG] [nrfconnect] Chef build broken on connectedhomeip/chip-build-vscode:0.7.16

Reproduction steps

Docker pull connectedhomeip/chip-build-vscode:0.7.16
Checkout project-chip/connectedhomeip/  master
Run the run_in script below and it finally failed with the error message: nrfconnect toolchain was not found. Make sure nrfconnect.ZEPHYR_SDK_INSTALL_DIR is set on your config.yaml file...

root@9559ad961dc3:/workspace# ./scripts/run_in_build_env.sh "./examples/chef/chef.py --ci -t nrfconnect"

  WELCOME TO...

         █
         █
     ▄   █   ▄                                █     █
     ▀▀█████▀▀      ▄▀▀▀▄ ▄▀▀▀▄    ▄▀▀▀▀▄█  ▀▀█▀▀▀▀▀█▀▀   ▄▀▀▀▀▄    ▄▀▀
   ▀█▄       ▄█▀   █     █     █  █      █    █     █    █▄▄▄▄▄▄█  █
     ▀█▄   ▄█▀     █     █     █  █      █    █     █    █         █
  ▄██▀▀█   █▀▀██▄  █     █     █   ▀▄▄▄▄▀█    ▀▄▄   ▀▄▄   ▀▄▄▄▄▀   █
 ▀▀    █   █    ▀▀

  BOOTSTRAP! Bootstrap may take a few minutes; please be patient.

... (ignored) ...

Building ./chef.py -cbr -d rootnode_dimmablelight_bCwGYSDpoe -t nrfconnect
--------------------------------------------------------------------------

  ______  __    __   _______  _______
 /      ||  |  |  | |   ____||   ____|
|  ,----'|  |__|  | |  |__   |  |__
|  |     |   __   | |   __|  |   __|
|  `----.|  |  |  | |  |____ |  |
 \______||__|  |__| |_______||__|

Target is set to rootnode_dimmablelight_bCwGYSDpoe
Setting up environment...
The path for nrfconnect toolchain was not found. Make sure nrfconnect.ZEPHYR_SDK_INSTALL_DIR is set on your config.yaml file. This is typically <NCS INSTALL PATH>/ncs/toolchains/vX.X.X/opt/zephyr-sdk
Traceback (most recent call last):
  File "/workspace/./examples/chef/chef.py", line 932, in <module>
    sys.exit(main())
  File "/workspace/./examples/chef/chef.py", line 382, in main
    shell.run_cmd(command)
  File "/workspace/examples/chef/stateful_shell.py", line 139, in run_cmd
    raise RuntimeError(
RuntimeError: Error. Nonzero return code.
Returncode: 1
Cmd: ./chef.py -cbr -d rootnode_dimmablelight_bCwGYSDpoe -t nrfconnect

Bug prevalence
Everytime
GitHub hash of the SDK that was being used
12d8fecea959532396b2b89069f9df43b3d994ac
Platform
nrf
Platform Version(s)
No response
Anything else?
It is caused by the [nrfconnect] Update nRF Connect SDK version to 2.4.0 (https://github.com/project-chip/connectedhomeip/pull/27010)  where the PR is forcing to check the env ZEPHYR_SDK_INSTALL_DIR.  Unfortunately, this env doesn't exist in the docker image connectedhomeip/chip-build-vscode:0.7.16
https://github.com/project-chip/connectedhomeip/commit/4c7f38d6427436f47c603dce67a1acd63ab7106a#diff-3dca1b4a352864488fc76b756c0c50d4af075e886073bb5b02236065c2c6b713R471-R473
...
        config["nrfconnect"]["ZEPHYR_SDK_INSTALL_DIR"] = os.environ.get(
            'ZEPHYR_SDK_INSTALL_DIR')
...
        if config['nrfconnect']['ZEPHYR_SDK_INSTALL_DIR'] is None:
            flush_print(
                'The path for nrfconnect toolchain was not found. Make sure nrfconnect.ZEPHYR_SDK_INSTALL_DIR is set on your config.yaml file. This is typically <NCS INSTALL PATH>/ncs/toolchains/vX.X.X/opt/zephyr-sdk')
            exit(1)

After exporting the ENV variable, I re-run the script again successfully.
$ export ZEPHYR_SDK_INSTALL_DIR="/opt/NordicSemiconductor/nRF5_tools/zephyr-sdk-0.16.0"
$ rm examples/chef/config.yaml
$ ./scripts/run_in_build_env.sh "./examples/chef/chef.py --ci -t nrfconnect"
...
[821/821] Linking CXX executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      827620 B         1 MB     78.93%
             RAM:      233956 B       256 KB     89.25%
        IDT_LIST:          0 GB         2 KB      0.00%
Done
-------------------
Bundling nrfconnect
-------------------

Cleaning /workspace/examples/chef/staging
Checking for bundle_nrfconnect
Found bundle_nrfconnect
Copying rootnode_dimmablelight_bCwGYSDpoe.matter
Generating metadata for rootnode_dimmablelight_bCwGYSDpoe


updated changelog date

Fixes # .

Changes proposed in this Pull Request:

updated changelog date

Screenshots / Screen Recording (if applicable)

To Test:

Any specific feedback you are looking for?

Pls open #259 once this PR get merged

@raghavenc5 not sure what time this PR came in on Friday but I missed this. Can you please change date to April 17, 2023


Support for haystack v2

Are there plans to add a document store implementation for v2?
See here for Chroma and ElasticSearch integrations. Pinecone seems to be added right now:
https://github.com/deepset-ai/haystack-core-integrations

@jdb78 It's already in progress. We are hopefully going to publish the implementation next week.

Amazing. Just in time :)


Memory leaks while fetching last 10 mails

I have simple iOS app which connect to my gmail and get last 10 emails:
private lazy var oauthswift:OAuth2Swift = {
        let tempOauthswift = OAuth2Swift(
            consumerKey:    "MY_SECRET_KEY",
            consumerSecret: "",
            authorizeUrl:   "https://accounts.google.com/o/oauth2/v2/auth",
            accessTokenUrl: "https://accounts.google.com/o/oauth2/token",//!!!!!!!!!!!!!!!!!
            responseType:   "code"
        )
        tempOauthswift.allowMissingStateCheck = true
        return tempOauthswift
    }()

    @IBAction func tap(_ sender: Any) {
        oauthswift.authorize(
            withCallbackURL: URL(string: "MY_CALLBACK_URL:/oauth2Callback")!,
            scope: "https://mail.google.com/", state:"",
            success:
            {
                (credential, response, parameters) in
                let configuration = Configuration.gmail(login<EMAIL_ADDRESS>password: .accessToken(credential.oauthToken))
                print(credential.oauthToken)
                let postal = Postal(configuration: configuration)
                postal.connect { result in
                    switch result {
                    case .success:
                        print("success")
                    case .failure(let error):
                        print("error: \(error)")
                    }
                }
                postal.fetchLast("INBOX", last: 10, flags: [.body], onMessage: { (FetchResult) in
                    print(FetchResult)
                }, onComplete: { (PostalError) in
                    print(PostalError
.debugDescription)
                })
        },
            failure:
            { error in
                print("Error: \(error.localizedDescription)")
        })
    }

My app fetches emails successfully but Instruments shows leaks:

Any ideas?

Does anybody have such problem with leaks? May be I must close cfstream, but how to do it ?

I've returned to my old project and rebuild it with new version of postal. Memory leaks are still here. May be it's false positive leak or I do something wrong? Does anybody has such problem?


Template Analyzer - Template / Validation Errors Cause Failure, no output to Sarif Scan Tab

When working with the MSDO tool in our IaC Build Pipeline, we're experiencing an issue with our template : Error exit code 22: 22. Violation + Error
That is fine and understandable, but what's troubling is we're not able to view scan results in the Sarif Scan Tab, it seems the sarif files never get the chance to get loaded into the CodeAnalysisLogs artifact when this failure occurs. I'm wondering if this may be addressed in the code to allow for more meaningful error messages / remediation steps for these types of validation / error messages. to be displayed in this scans tab. Currently I'm having to sift through ~60,000 lines to find the error occurrence and it's hard to track down where in our files the failure is occurring.

I am also facing similar issue on the Build pipeline.
Error running templateanalyzer job: 1 of 1
GuardianErrorExitCodeException: templateanalyzer completed with an Error exit code: 22. Violation + Error: Scan encountered both violations in template(s) and errors trying to analyze template(s)

Same here with Binskim.
I have an exe file, licecap.exe from cockos, in my test / demo setup, and it fails binskim with error
D:\a\1\s\DFDOFiles\licecap.exe : error ERR997.ExceptionLoadingPdb : 'licecap.exe' was not evaluated because its PDB could not be loaded (E_PDB_NO_DEBUG_INFO).

## <cut for brevity>
    ------------------------------------------------------------------------------
    BinSkim completed with exit code 1
##[error]Error running binskim job: 1 of 1
##[error]GuardianErrorExitCodeException: binskim completed with an Error exit code: 1. BinSkim failed. Verify the target(s) to be scanned. BinSkim targets must be a specific filename, or a pattern with a wildcard like *.dll, dir\*.dll, or dir\*

Adding an exclusion in .gdnconfig like this
{
  "tools": [
    {
      "tool": {
        "name": "BinSkim",
        "version": "Latest"
      },
      "arguments": {
        "IgnorePdbLoadError": "true"
      }
    }
  ]
}

fixes the error and .sarif output is created
The tests do continue, and my log also has errors for other demo /test files, but the sarif output stops as soon as an error is output to the log.

Fyi; a fix for Template Analyzer was deployed to deal with that issue. Also, a fix was deployed to prevent breaking the whole flow if a tool does not execute successfully. The exception will be caught and re-thrown at the end, after post-processing has completed.


Bluetooth: host: fix deadlock when CONFIG_BT_RECV_WORKQ_BT=y

A deadlock can occur in that situation:

bt wq handles an HCI buffer that is an ATT REQ

handling it involves sending a RSP

sending a RSP involves waiting for a conn TX context

bt wq waits forever

the HCI buffer is freed after the l2cap .chan cb

in that case, that is att_recv, which is currently stuck -> buffer is held up

hci thread waits on a data buffer -> last buffer is held by bt wq

The bug doesn't manifest itself when using the syswq for bt_recv. This is infortunate as using the BT WQ is the default option.
To work around it, apply the same rule as the syswq: don't wait for a TX context or ATT metadata when sending from the workqueue that bt_recv is called from.

Deadlock might not manifest itself after #60309 .
We also have a bigger patchset coming up that might render all of this irrelevant.


Visibility control on photos

The "Visibility Control on Photos" feature allows users to specify who can view their uploaded photos and comments. When uploading a photo, users can choose to create a sharing list, restricting access to specific users. If no list is provided, the photo is public and visible to everyone. If the sharing list is empty, only the photo owner can view it. The system ensures that queries return only photos the user has permission to see, based on the visibility settings. This feature enhances privacy and control over photo sharing within the application.

The feature is well-explained and clearly highlights the privacy controls provided to users. You might consider clarifying what happens if the owner wants to edit the sharing list after the photo is uploaded or whether there is a way to change visibility settings later. Additionally, explaining how the system handles visibility for comments on a photo (e.g., whether they inherit the photo's settings) could make the functionality even clearer

The explanation is clear and detailed, but adding clarification on editing the sharing list post-upload and changing visibility settings later would enhance it further. Also, specifying how visibility settings apply to comments on a photo would provide a more comprehensive understanding.

The explanation is thorough and well-structured. Great work, team! Addressing the suggested clarifications will make it even better. Let's keep this all going well


STDOUT Output randomly doesn't work, preview takes long to open,  without any information

Godot version
v4.1.stable.flathub [970459615]
System information
Godot v4.1.stable (970459615) - Freedesktop SDK 22.08 (Flatpak runtime) - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1070 Ti (nvidia) - AMD Ryzen 5 2600X Six-Core Processor (12 Threads)
Issue description
When trying to play a scene the debug output just is randomly empty. Stopping and starting again have in the past helped as well as closing the engine and reopening the project. In the MRP i found it to reliably not output when uncommenting the last print statement at line 33 print((1000.0/(average_time_between))*60). Less reliable is uncommenting any of the other lines, but the func convert time to bpm should work too. If the function is broken, there is no debug output stating such.
https://github.com/godotengine/godot/assets/124401812/ca99fc73-db0a-46c8-b18e-aaf040f5e351
Steps to reproduce
Just open the script of the Song Editor Node in the Only tscn in the project.
Minimal reproduction project
Archive.zip

Can you reproduce this in a non-Flatpak build of the editor?

Yes, i have been able to reproduce it with the steam latest and the official download (linux x86_64, v4.1.1.stable.official [bd6af8e0e])

You might have to start and restart the scene multiple times to get it to fail. Make sure line 33 is not commented, start the scene. If it works, click the button a few times, it should produce output. Now restart the scene until the error happens. For me it was 4 times at most until change was visible.

Using the current windows x64 build and even with the most basic project, the print function does nothing.

I can't reproduce this on 4.2.dev 541674d10 (Linux).
Remember that your code doesn't print anything if beats is lower than 200. This means you need to wait some time until pressing the button will appear to do anything.

First of all i don't understand why this would be the case, could you please explain, secondly that should not impact the debug statement not showing in the console, if i understand correctly?

First of all i don't understand why this would be the case, could you please explain, secondly that should not impact the debug statement not showing in the console, if i understand correctly?

What I mean is, the code won't print anything if the block in question is never reached. Try putting a print statement in _ready() instead. If you don't see that print in the console either, then this is likely the same cause as https://github.com/godotengine/godot/issues/81102.

Same issue in other project. Looking at #81943 i have identified portmaster as the culprit. Deactivating seems to fix the issue. Will try to find out how to setup portmaster to not interfere, but closing for now.

The only way that works consistently is to change the debug port under "Editor Settings" to something like 7007 instead of 6007. Have no idea why this happens with portmaster.


Restart/reload dovecot

While docker-compose exec mail  service postfix restart or
docker-compose exec mail  /etc/init.d/postfix restart work for restarting (or reloading) the postfix daemon (after a config change), it doesn't work with the dovecot service (no service 'dovecot' found, neither using service dovecot nor using /etc/init.d/dovecot).

just had a some issues with dovecot myself. If dovecot is not running but /var/run/dovecot/master.pid exists, then dovecot will not start anymore.
For me the fix was:
rm /var/run/dovecot/master.pid
/usr/sbin/dovecot -c /etc/dovecot/dovecot.conf # or restart docker

@Zauberstuhl: Thank you for the workaround. Though in my case, postfix and dovecot run and I need to restart/reload dovecot after a config change. There seems to be no command/script available for this currently short of docker-compose restart for restarting the whole container setup (including unnecessary downtime).

restart:
/usr/sbin/dovecot stop
/usr/sbin/dovecot -c /etc/dovecot/dovecot.conf

and reload:
/usr/sbin/dovecot reload

Two convenience scripts would be nice, e.g. for cert regeneration, e.g. postfix-restart.sh, postfix-reload.sh, dovecot-restart.sh and dovecot-reload.sh.

The commands have been provided by @Zauberstuhl.
Why not just exec them? (same thing you will do without docker).
The purpose of this image is to bootstrap easily a mail server. The usage once running should be more or less the same you should have without docker.
Too much abstraction won't allow people to understand what they do, and they won't be able to do the same on a classic server.
Just my 2 cents

Then I am happy with this. Though I wonder why there is a service for postfix but not for dovecot.

When starting dovecot (after stopping it) using aforementioned command
docker exec /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf

results in docker exec hanging instead of exiting.
Also within a bash opened with docker exec, the bash won't exit as long as the dovecot process still runs.
How can I start dovecot in background the proper way?

The container name is missing in your command (a typo when pasting in Github, I suppose).
Yep, the command starts a process in foreground.
The container uses this part of code https://github.com/tomav/docker-mailserver/blob/master/target/start-mailserver.sh#L305-L317
You may have a look.


Dynamic view height

The page should set a dynamic view height that takes into account the size of the navbar and bookmark bar.

[ ] the footer position needs to be relative to this height
[x] paging options should be visible above footer
[x] no limit on title content length means the bookmark bar could be variable height
Needs to be one in:

[x] recordset w/ faceting
[x] recordset
[x] record
[x] recordedit

Creating a separate issue for the footer position.


Error: Faulty Request There was an error with the request. The "client_id" field is invalid.

This is an issue with selfauth but I'm hoping I can get some guidance here. I've also set up php-mintoken but I don't see how it even connects to selfauth. What am I missing here?
I've regenerated the config file several times and I keep getting the same error. Tried on a subdomain (http://auth.domain.tld and https://auth.domain.tld), on a subfolder (http://domain.tld/auth and https://domain.tld/auth) like in the guide, and even on the root domain (http://domain.tld and https://domain.tld). I even tried with www in the username (http://www.domain.tld and https://www.domain.tld).
<?php
define('APP_URL', 'http://auth.domain.tld/');
define('APP_KEY', ''>
define('USER_HASH', '');
define('USER_URL', 'https://domain.tld');

What client are you trying to give a token to?
Mintoken was required for older versions of the IndieAuth specification, where the authorization endpoint and token endpoint were completely separated. The client would need to do a request to the authorization endpoint (Selfauth) which would issue a “code” to the client that can then be exchanged at the token endpoint (Mintoken).
If you are getting an error about the client_id, that sounds like the very first step from your client to Selfauth is already failing. As Mintoken never throws that error. Even if you can get that part to work, it is not guaranteed that the client is able to talk to Mintoken for a code exchange though.
Your configuration might be correct already. Mintoken is not configured to use any specific Selfauth instance. A single instance of Mintoken could serve to do code exchanges for multiple Selfauth instances. Mintoken is also not configured to do (or know) anything about different clients. It simply received a “code”, checks with the given authorization endpoint (discovered from a ?me= query value) for that code, and if successful it issues a token.

I'm trying to setup IndieAuth for just one domain. Maybe I've misunderstood all of this, but I setup selfauth (and mintoken) on the same server as this domain and configured them to use this domain so I can log into IndieAuth-enabled websites using this domain. I'm not trying to setup an IndieAuth login portal on my own website.
I've tested it against every IndieAuth login portal I could find, all have been failing with the same errors (unique to each one) no matter what I do, which tells me they aren't detecting anything I've setup.
I've already opened an issue with selfauth as well but have yet to receive a response. Am I understanding you correctly in that mintoken is no longer required for an IndieAuth setup? I've looked at other IndieAuth implementations and they've all either been abandoned or are far more complex to setup than selfauth.

Sorry, I must have missed the issue on Selfauth for some reason.
Mintoken has never been a requirement. I still run Selfauth without it to authenticate with the IndieWeb wiki myself. Mintoken is only needed if you need long-lived token management for things like Micropub clients, as Selfauth does not issue tokens.
I will close this issue and continue this on the Selfauth issue tracker instead. Inklings-io/selfauth#54


User logout

When i do the logout of an user, I have this error:
"Class 'RainLab\User\Components\Event' not found" on line 90 of /home/themagi1/domains/themagicworldshop.it/public_html/plugins/rainlab/user/components/Session.php
Which is the problem? Thank you

This was fixed in v1.2.9+ make sure you are using the latest version of the plugin.


[DNA-319] Setup a build pipeline for UiPath/querybuilder (i.e. the SqlKata fork)

Should produce a package that we can use in UiPath/ProcessMining-Cloud:ProcessMining C# project.

/azp run

/azp run

/azp run