[CRITICAL] [Window      ] Unable to find any valuable Window provider.

Versions

Python: 3.7.0
OS: Windows 10 64bit build 17763
Kivy: 1.10.1
Kivy installation method: pip install kivy --user

Description
I run kivy for the first time and something went wrong. I have fixed some of the errors but not all.
Code and Logs
This is the log when I run it.
[INFO   ] [Logger      ] Record log in C:\Users\werto\.kivy\logs\kivy_19-04-29_10.txt
[INFO   ] [Kivy        ] v1.10.1
[INFO   ] [Python      ] v3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)]
[INFO   ] [Factory     ] 194 symbols loaded
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_pil, img_gif (img_sdl2, img_ffpyplayer ignored)
[INFO   ] [Text        ] Provider: pil(['text_sdl2'] ignored)
[CRITICAL] [Window      ] Unable to find any valuable Window provider.
sdl2 - ImportError: DLL load failed: Uvedený modul nebyl nalezen.
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\__init__.py", line 59, in core_select_lib
    fromlist=[modulename], level=0)
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 26, in <module>
    from kivy.core.window._window_sdl2 import _WindowSDL2Storage

[CRITICAL] [App         ] Unable to get a Window, abort.

Did you install kivy.deps.sdl2?

This kind of issue is almost impossible to troubleshoot over github and often does not indicate a kivy bug but rather an installation issue. Can you try the version of kivy from https://github.com/kivy/kivy/pull/6280 and try to follow its instructions to see if that helps your issue?

I have no idea how to use it could you please help me?

can you run with python main.py -c kivy:logl_level:debug to get more information?

That PR has been merged into master. Can you install master and follow/post the log instructions? You can download a wheel of master https://kivy.org/downloads/ci/win/kivy/Kivy-1.11.0.dev0-cp37-cp37m-win_amd64.whl and install it with pip install --upgrade Kivy-1.11.0.dev0-cp37-cp37m-win_amd64.whl.

Ok used it and this came out.
`[INFO   ] [Logger      ] Record log in C:\Users\werto.kivy\logs\kivy_19-05-03_2.txt
[INFO   ] [Kivy        ] v1.11.0.dev0, git-8f375d8, 20190502
[INFO   ] [Kivy        ] Installed at "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy_init_.py"
[INFO   ] [Python      ] v3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)]
[INFO   ] [Python      ] Interpreter at "C:\Program Files\Python37\python.exe"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer"
[INFO   ] [deps        ] Successfully imported "kivy.deps.angle"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2_dev"
[INFO   ] [Factory     ] 184 symbols loaded
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_pil, img_gif (img_sdl2, img_ffpyplayer ignored)
[INFO   ] [Text        ] Provider: pil(['text_sdl2'] ignored)
[CRITICAL] [Window      ] Unable to find any valuable Window provider. Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config) and re-run your app to identify potential causes
sdl2 - ImportError: DLL load failed: Uvedený modul nebyl nalezen.
File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core_init_.py", line 63, in core_select_lib
fromlist=[modulename], level=0)
File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 27, in
from kivy.core.window._window_sdl2 import _WindowSDL2Storage
[CRITICAL] [App         ] Unable to get a Window, abort.`

Did you see the error log? Please follow the instructions given in the log.
CRITICAL] [Window ] Unable to find any valuable Window provider. Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config) and re-run your app to identify potential causes

Yes I have seen that made, that and edited the previous comment.

How did you set KIVY_SDL2_DEPENDENCY_WALKER. Can you say exactly how you set it and the value you set it to?

This PC -> Settings -> Advanced system settings ->  Environment Variables
In the bottom part New, Name: KIVY_SDL2_DEPENDENCY_WALKER Value: C:\Users\werto\Downloads\depends22_x64\depends.exe
Like this:
https://ctrlv.cz/shots/2019/05/03/I9E6.png

Did you re-start your terminal? It does not change existing terminals, you have to restart it.

Ok. I have now restarted it and I got this. Which means that I have OpenGL 1.1
[INFO   ] [Logger      ] Record log in C:\Users\werto\.kivy\logs\kivy_19-05-03_8.txt
[INFO   ] [Kivy        ] v1.11.0.dev0, git-8f375d8, 20190502
[INFO   ] [Kivy        ] Installed at "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\__init__.py"
[INFO   ] [Python      ] v3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)]
[INFO   ] [Python      ] Interpreter at "C:\Program Files\Python37\python.exe"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer"
[INFO   ] [deps        ] Successfully imported "kivy.deps.angle"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2_dev"
[INFO   ] [Factory     ] 184 symbols loaded
[DEBUG  ] [Cache       ] register <kv.lang> with limit=None, timeout=None
[DEBUG  ] [Cache       ] register <kv.image> with limit=None, timeout=60
[DEBUG  ] [Cache       ] register <kv.atlas> with limit=None, timeout=None
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_gif (img_ffpyplayer ignored)
[DEBUG  ] [Cache       ] register <kv.texture> with limit=1000, timeout=60
[DEBUG  ] [Cache       ] register <kv.shader> with limit=1000, timeout=3600
[INFO   ] [Text        ] Provider: sdl2
[DEBUG  ] [Cache       ] register <textinput.label> with limit=None, timeout=60.0
[DEBUG  ] [Cache       ] register <textinput.width> with limit=None, timeout=60.0
[DEBUG  ] [App         ] Loading kv <.\epic.kv>
[DEBUG  ] [App         ] kv <.\epic.kv> not found
[INFO   ] [Window      ] Provider: sdl2
[INFO   ] [GL          ] Using the "OpenGL" graphics system
[INFO   ] [GL          ] GLEW initialization succeeded
[DEBUG  ] [GL          ] available extensions: b'GL_WIN_swap_hint GL_EXT_bgra GL_EXT_paletted_texture'
[DEBUG  ] [GL          ] glGenFramebuffers is NULL, try to detect an extension
[INFO   ] [GL          ] No framebuffers extension is supported
[DEBUG  ] [GL          ] Any call to Fbo will crash!
[DEBUG  ] [GL          ] glActiveTexture is not available
[DEBUG  ] [GL          ] glAttachShader is not available
[DEBUG  ] [GL          ] glBindAttribLocation is not available
[DEBUG  ] [GL          ] glBindBuffer is not available
[DEBUG  ] [GL          ] glBindFramebuffer is not available
[DEBUG  ] [GL          ] glBindRenderbuffer is not available
[DEBUG  ] [GL          ] glBlendColor is not available
[DEBUG  ] [GL          ] glBlendEquation is not available
[DEBUG  ] [GL          ] glBlendEquationSeparate is not available
[DEBUG  ] [GL          ] glBlendFuncSeparate is not available
[DEBUG  ] [GL          ] glBufferData is not available
[DEBUG  ] [GL          ] glBufferSubData is not available
[DEBUG  ] [GL          ] glCheckFramebufferStatus is not available
[DEBUG  ] [GL          ] glCompileShader is not available
[DEBUG  ] [GL          ] glCompressedTexImage2D is not available
[DEBUG  ] [GL          ] glCompressedTexSubImage2D is not available
[DEBUG  ] [GL          ] glCreateProgram is not available
[DEBUG  ] [GL          ] glCreateShader is not available
[DEBUG  ] [GL          ] glDeleteBuffers is not available
[DEBUG  ] [GL          ] glDeleteFramebuffers is not available
[DEBUG  ] [GL          ] glDeleteProgram is not available
[DEBUG  ] [GL          ] glDeleteRenderbuffers is not available
[DEBUG  ] [GL          ] glDeleteShader is not available
[DEBUG  ] [GL          ] glDetachShader is not available
[DEBUG  ] [GL          ] glDisableVertexAttribArray is not available
[DEBUG  ] [GL          ] glEnableVertexAttribArray is not available
[DEBUG  ] [GL          ] glFramebufferRenderbuffer is not available
[DEBUG  ] [GL          ] glFramebufferTexture2D is not available
[DEBUG  ] [GL          ] glGenBuffers is not available
[DEBUG  ] [GL          ] glGenerateMipmap is not available
[DEBUG  ] [GL          ] glGenFramebuffers is not available
[DEBUG  ] [GL          ] glGenRenderbuffers is not available
[DEBUG  ] [GL          ] glGetActiveAttrib is not available
[DEBUG  ] [GL          ] glGetActiveUniform is not available
[DEBUG  ] [GL          ] glGetAttachedShaders is not available
[DEBUG  ] [GL          ] glGetAttribLocation is not available
[DEBUG  ] [GL          ] glGetBufferParameteriv is not available
[DEBUG  ] [GL          ] glGetFramebufferAttachmentParameteriv is not available
[DEBUG  ] [GL          ] glGetProgramInfoLog is not available
[DEBUG  ] [GL          ] glGetProgramiv is not available
[DEBUG  ] [GL          ] glGetRenderbufferParameteriv is not available
[DEBUG  ] [GL          ] glGetShaderInfoLog is not available
[DEBUG  ] [GL          ] glGetShaderiv is not available
[DEBUG  ] [GL          ] glGetShaderSource is not available
[DEBUG  ] [GL          ] glGetUniformfv is not available
[DEBUG  ] [GL          ] glGetUniformiv is not available
[DEBUG  ] [GL          ] glGetUniformLocation is not available
[DEBUG  ] [GL          ] glGetVertexAttribfv is not available
[DEBUG  ] [GL          ] glGetVertexAttribiv is not available
[DEBUG  ] [GL          ] glIsBuffer is not available
[DEBUG  ] [GL          ] glIsFramebuffer is not available
[DEBUG  ] [GL          ] glIsProgram is not available
[DEBUG  ] [GL          ] glIsRenderbuffer is not available
[DEBUG  ] [GL          ] glIsShader is not available
[DEBUG  ] [GL          ] glLinkProgram is not available
[DEBUG  ] [GL          ] glRenderbufferStorage is not available
[DEBUG  ] [GL          ] glSampleCoverage is not available
[DEBUG  ] [GL          ] glShaderBinary is not available
[DEBUG  ] [GL          ] glShaderSource is not available
[DEBUG  ] [GL          ] glStencilFuncSeparate is not available
[DEBUG  ] [GL          ] glStencilMaskSeparate is not available
[DEBUG  ] [GL          ] glStencilOpSeparate is not available
[DEBUG  ] [GL          ] glUniform1f is not available
[DEBUG  ] [GL          ] glUniform1fv is not available
[DEBUG  ] [GL          ] glUniform1i is not available
[DEBUG  ] [GL          ] glUniform1iv is not available
[DEBUG  ] [GL          ] glUniform2f is not available
[DEBUG  ] [GL          ] glUniform2fv is not available
[DEBUG  ] [GL          ] glUniform2i is not available
[DEBUG  ] [GL          ] glUniform2iv is not available
[DEBUG  ] [GL          ] glUniform3f is not available
[DEBUG  ] [GL          ] glUniform3fv is not available
[DEBUG  ] [GL          ] glUniform3i is not available
[DEBUG  ] [GL          ] glUniform3iv is not available
[DEBUG  ] [GL          ] glUniform4f is not available
[DEBUG  ] [GL          ] glUniform4fv is not available
[DEBUG  ] [GL          ] glUniform4i is not available
[DEBUG  ] [GL          ] glUniform4iv is not available
[DEBUG  ] [GL          ] glUniformMatrix4fv is not available
[DEBUG  ] [GL          ] glUseProgram is not available
[DEBUG  ] [GL          ] glValidateProgram is not available
[DEBUG  ] [GL          ] glVertexAttrib1f is not available
[DEBUG  ] [GL          ] glVertexAttrib2f is not available
[DEBUG  ] [GL          ] glVertexAttrib3f is not available
[DEBUG  ] [GL          ] glVertexAttrib4f is not available
[DEBUG  ] [GL          ] glVertexAttribPointer is not available
[INFO   ] [GL          ] Backend used <glew>
[INFO   ] [GL          ] OpenGL version <b'1.1.0'>
[INFO   ] [GL          ] OpenGL vendor <b'Microsoft Corporation'>
[INFO   ] [GL          ] OpenGL renderer <b'GDI Generic'>
[INFO   ] [GL          ] OpenGL parsed version: 1, 1
[CRITICAL] [GL          ] Minimum required OpenGL version (2.0) NOT found!

OpenGL version detected: 1.1

Version: b'1.1.0'
Vendor: b'Microsoft Corporation'
Renderer: b'GDI Generic'

Try upgrading your graphics drivers and/or your graphics hardware in case of problems.

The application will leave now.

But I when I looked if I can run kivy I got this:
https://ctrlv.cz/shots/2019/05/03/USUz.png
So now I'm confused

There's something wrong with your system. Have you restarted the terminal since installing kivy the first time? It's strange that this would happen all of a sudden.  You must have installed something that caused the gl issue.

Yes I have restarted it many times. I'll try find something that could cause the issue.

Are you using remote desktop or something similar? I had similar issues over RDC. The GL provider in your log is GDI, which implies the GPU is not being used.

I'm not using a remote desktop but I run the code from a user werto but the code is saved on user NB.
May this be the cause?

I think I'm very unlucky.
[INFO   ] [Logger      ] Record log in C:\Users\werto\.kivy\logs\kivy_19-05-04_2.txt
[INFO   ] [Kivy        ] v1.11.0.dev0, git-8f375d8, 20190502
[INFO   ] [Kivy        ] Installed at "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\__init__.py"
[INFO   ] [Python      ] v3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)]
[INFO   ] [Python      ] Interpreter at "C:\Program Files\Python37\python.exe"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer"
[INFO   ] [deps        ] Successfully imported "kivy.deps.angle"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2_dev"
[INFO   ] [Factory     ] 184 symbols loaded
[DEBUG  ] [Cache       ] register <kv.lang> with limit=None, timeout=None
[DEBUG  ] [Cache       ] register <kv.image> with limit=None, timeout=60
[DEBUG  ] [Cache       ] register <kv.atlas> with limit=None, timeout=None
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_gif (img_ffpyplayer ignored)
[DEBUG  ] [Cache       ] register <kv.texture> with limit=1000, timeout=60
[DEBUG  ] [Cache       ] register <kv.shader> with limit=1000, timeout=3600
[INFO   ] [Text        ] Provider: sdl2
[DEBUG  ] [Cache       ] register <textinput.label> with limit=None, timeout=60.0
[DEBUG  ] [Cache       ] register <textinput.width> with limit=None, timeout=60.0
[DEBUG  ] [App         ] Loading kv <.\epic.kv>
[DEBUG  ] [App         ] kv <.\epic.kv> not found
[INFO   ] [Window      ] Provider: sdl2
[INFO   ] [Window      ] Activate GLES2/ANGLE context
[CRITICAL] [Window      ] Unable to find any valuable Window provider. Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config) and re-run your app to identify potential causes
sdl2 - RuntimeError: b'Could not initialize OpenGL / GLES library'
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\__init__.py", line 71, in core_select_lib
    cls = cls()
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 146, in __init__
    super(WindowSDL, self).__init__()
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\__init__.py", line 970, in __init__
    self.create_window()
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 282, in create_window
    self.fullscreen, resizable, state)
  File "kivy\core\window\_window_sdl2.pyx", line 225, in kivy.core.window._window_sdl2._WindowSDL2Storage.setup_window
  File "kivy\core\window\_window_sdl2.pyx", line 75, in kivy.core.window._window_sdl2._WindowSDL2Storage.die

[CRITICAL] [App         ] Unable to get a Window, abort.

Maybe try to uninstall kivy.deps.angle

Hasn't worked.
[INFO   ] [Logger      ] Record log in C:\Users\werto\.kivy\logs\kivy_19-05-04_3.txt
[INFO   ] [Kivy        ] v1.11.0.dev0, git-8f375d8, 20190502
[INFO   ] [Kivy        ] Installed at "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\__init__.py"
[INFO   ] [Python      ] v3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)]
[INFO   ] [Python      ] Interpreter at "C:\Program Files\Python37\python.exe"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2_dev"
[INFO   ] [Factory     ] 184 symbols loaded
[DEBUG  ] [Cache       ] register <kv.lang> with limit=None, timeout=None
[DEBUG  ] [Cache       ] register <kv.image> with limit=None, timeout=60
[DEBUG  ] [Cache       ] register <kv.atlas> with limit=None, timeout=None
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_gif (img_ffpyplayer ignored)
[DEBUG  ] [Cache       ] register <kv.texture> with limit=1000, timeout=60
[DEBUG  ] [Cache       ] register <kv.shader> with limit=1000, timeout=3600
[INFO   ] [Text        ] Provider: sdl2
[DEBUG  ] [Cache       ] register <textinput.label> with limit=None, timeout=60.0
[DEBUG  ] [Cache       ] register <textinput.width> with limit=None, timeout=60.0
[DEBUG  ] [App         ] Loading kv <.\epic.kv>
[DEBUG  ] [App         ] kv <.\epic.kv> not found
[INFO   ] [Window      ] Provider: sdl2
[INFO   ] [Window      ] Activate GLES2/ANGLE context
[CRITICAL] [Window      ] Unable to find any valuable Window provider. Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config) and re-run your app to identify potential causes
sdl2 - RuntimeError: b'Could not initialize OpenGL / GLES library'
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\__init__.py", line 71, in core_select_lib
    cls = cls()
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 146, in __init__
    super(WindowSDL, self).__init__()
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\__init__.py", line 970, in __init__
    self.create_window()
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 282, in create_window
    self.fullscreen, resizable, state)
  File "kivy\core\window\_window_sdl2.pyx", line 225, in kivy.core.window._window_sdl2._WindowSDL2Storage.setup_window
  File "kivy\core\window\_window_sdl2.pyx", line 75, in kivy.core.window._window_sdl2._WindowSDL2Storage.die

[CRITICAL] [App         ] Unable to get a Window, abort.

Can you update your graphics drivers by downloading directly from the manufacturers site (e.g. dell).
Also, try installing it for your user rather than using it cross users. Also try a virtual env and install kivy to it.
Also, do echo %PATH% in your terminal. Then remove all folders from that list that are not system folders and then do set PATH="..." where ... is the cleaned list.
Finally, try running it with angle or sdl2 as shown here https://kivy.org/doc/stable/api-kivy.graphics.cgl.html#module-kivy.graphics.cgl

I run it and I got this
Purge log fired. Analysing...
Purge finished!
[INFO   ] [Logger      ] Record log in C:\Users\werto\.kivy\logs\kivy_19-05-06_0.txt
[INFO   ] [Kivy        ] v1.11.0.dev0, git-8f375d8, 20190502
[INFO   ] [Kivy        ] Installed at "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\__init__.py"
[INFO   ] [Python      ] v3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)]
[INFO   ] [Python      ] Interpreter at "C:\Program Files\Python37\python.exe"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2_dev"
[INFO   ] [Factory     ] 184 symbols loaded
[INFO   ] [image       ] Running dependency walker "C:\Users\werto\Downloads\depends22_x64\depends.exe" on "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\image\_img_sdl2.cp37-win_amd64.pyd" to generate troubleshooting log. Please wait for it to complete
[INFO   ] [image       ] dependency walker generated "C:\Users\werto\kivy_depends_sdl2_log_3yq0es5q.dwi" containing troubleshooting information about provider sdl2 and its failing file "kivy.core.image._img_sdl2 (C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\image\_img_sdl2.cp37-win_amd64.pyd)". You can open the file in dependency walker to view any potential issues and troubleshoot it yourself. To share the file with the Kivy developers and request support, please contact us at our support channels https://kivy.org/doc/master/contact.html (not on github, unless it's truly a bug). Make sure to provide the generated file as well as the *complete* Kivy log being printed here. Keep in mind the generated dependency walker log file contains paths to dlls on your system used by kivy or its dependencies to help troubleshoot them, and these paths may include your name in them. Please view the log file in dependency walker before sharing to ensure you are not sharing sensitive paths
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_pil, img_gif (img_sdl2, img_ffpyplayer ignored)
[INFO   ] [text        ] Running dependency walker "C:\Users\werto\Downloads\depends22_x64\depends.exe" on "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\text\_text_sdl2.cp37-win_amd64.pyd" to generate troubleshooting log. Please wait for it to complete
[INFO   ] [text        ] dependency walker generated "C:\Users\werto\kivy_depends_sdl2_log_513jht7b.dwi" containing troubleshooting information about provider sdl2 and its failing file "kivy.core.text._text_sdl2 (C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\text\_text_sdl2.cp37-win_amd64.pyd)". You can open the file in dependency walker to view any potential issues and troubleshoot it yourself. To share the file with the Kivy developers and request support, please contact us at our support channels https://kivy.org/doc/master/contact.html (not on github, unless it's truly a bug). Make sure to provide the generated file as well as the *complete* Kivy log being printed here. Keep in mind the generated dependency walker log file contains paths to dlls on your system used by kivy or its dependencies to help troubleshoot them, and these paths may include your name in them. Please view the log file in dependency walker before sharing to ensure you are not sharing sensitive paths
[INFO   ] [Text        ] Provider: pil(['text_sdl2'] ignored)
[INFO   ] [window      ] Running dependency walker "C:\Users\werto\Downloads\depends22_x64\depends.exe" on "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\_window_sdl2.cp37-win_amd64.pyd" to generate troubleshooting log. Please wait for it to complete
[INFO   ] [window      ] dependency walker generated "C:\Users\werto\kivy_depends_sdl2_log_z7qbk_v5.dwi" containing troubleshooting information about provider sdl2 and its failing file "kivy.core.window._window_sdl2 (C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\_window_sdl2.cp37-win_amd64.pyd)". You can open the file in dependency walker to view any potential issues and troubleshoot it yourself. To share the file with the Kivy developers and request support, please contact us at our support channels https://kivy.org/doc/master/contact.html (not on github, unless it's truly a bug). Make sure to provide the generated file as well as the *complete* Kivy log being printed here. Keep in mind the generated dependency walker log file contains paths to dlls on your system used by kivy or its dependencies to help troubleshoot them, and these paths may include your name in them. Please view the log file in dependency walker before sharing to ensure you are not sharing sensitive paths
[CRITICAL] [Window      ] Unable to find any valuable Window provider. Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config) and re-run your app to identify potential causes
sdl2 - ImportError: DLL load failed: Uvedený modul nebyl nalezen.
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\__init__.py", line 63, in core_select_lib
    fromlist=[modulename], level=0)
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 27, in <module>
    from kivy.core.window._window_sdl2 import _WindowSDL2Storage

[CRITICAL] [App         ] Unable to get a Window, abort.

It is the first time dependecy walker did something.
Here are the logs.
logs.zip

I don't actually see anything that is clearly fixable from the log files. Everything seems mostly ok.
But, can you install Visual C++ Redistributable for Visual Studio 2015 and see if that fixes it?
The only other thing I can think of is the user thing you mentioned. Windows could be blocking something due to user permissions? Make sure the python you use is installed for the current user.
I would highly suggest that you completely uninstall kivy (including dependencies), and then make a new virtual environment and then install kivy to it and try again.
If this doesn't fix it, I'm afraid the only next step is to try compiling kivy for yourself. See the instructions here. Make sure to uninstall kivy first though.

I made a virtual enviroment and it worked.
Thanks very much. But I don't think it is a bug it is most likely a hardware issue (my laptop is 7 years old).

Try using the following code in anaconda :
conda config --add channels conda-forge
conda install kivy
This solved my issue of kivy...
This is from the site : https://stackoverflow.com/questions/44219563/kivy-not-working-error-unable-to-find-any-valuable-window-provider

i uninstall all and then install kivy 1.11.0 following this.it works.however,i tried kivy1.10.1,it doesn't work though.

Use angle and sdl2 and remove glew
in your app:
import os
os.environ['KIVY_GL_BACKEND']='angle_sdl2'

I think I'm very unlucky.
[INFO   ] [Logger      ] Record log in C:\Users\werto\.kivy\logs\kivy_19-05-04_2.txt
[INFO   ] [Kivy        ] v1.11.0.dev0, git-8f375d8, 20190502
[INFO   ] [Kivy        ] Installed at "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\__init__.py"
[INFO   ] [Python      ] v3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)]
[INFO   ] [Python      ] Interpreter at "C:\Program Files\Python37\python.exe"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer"
[INFO   ] [deps        ] Successfully imported "kivy.deps.angle"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2_dev"
[INFO   ] [Factory     ] 184 symbols loaded
[DEBUG  ] [Cache       ] register <kv.lang> with limit=None, timeout=None
[DEBUG  ] [Cache       ] register <kv.image> with limit=None, timeout=60
[DEBUG  ] [Cache       ] register <kv.atlas> with limit=None, timeout=None
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_gif (img_ffpyplayer ignored)
[DEBUG  ] [Cache       ] register <kv.texture> with limit=1000, timeout=60
[DEBUG  ] [Cache       ] register <kv.shader> with limit=1000, timeout=3600
[INFO   ] [Text        ] Provider: sdl2
[DEBUG  ] [Cache       ] register <textinput.label> with limit=None, timeout=60.0
[DEBUG  ] [Cache       ] register <textinput.width> with limit=None, timeout=60.0
[DEBUG  ] [App         ] Loading kv <.\epic.kv>
[DEBUG  ] [App         ] kv <.\epic.kv> not found
[INFO   ] [Window      ] Provider: sdl2
[INFO   ] [Window      ] Activate GLES2/ANGLE context
[CRITICAL] [Window      ] Unable to find any valuable Window provider. Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config) and re-run your app to identify potential causes
sdl2 - RuntimeError: b'Could not initialize OpenGL / GLES library'
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\__init__.py", line 71, in core_select_lib
    cls = cls()
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 146, in __init__
    super(WindowSDL, self).__init__()
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\__init__.py", line 970, in __init__
    self.create_window()
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 282, in create_window
    self.fullscreen, resizable, state)
  File "kivy\core\window\_window_sdl2.pyx", line 225, in kivy.core.window._window_sdl2._WindowSDL2Storage.setup_window
  File "kivy\core\window\_window_sdl2.pyx", line 75, in kivy.core.window._window_sdl2._WindowSDL2Storage.die

[CRITICAL] [App         ] Unable to get a Window, abort.

Did you find the solution
I am facing the same problem

I think I'm very unlucky.
[INFO   ] [Logger      ] Record log in C:\Users\werto\.kivy\logs\kivy_19-05-04_2.txt
[INFO   ] [Kivy        ] v1.11.0.dev0, git-8f375d8, 20190502
[INFO   ] [Kivy        ] Installed at "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\__init__.py"
[INFO   ] [Python      ] v3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)]
[INFO   ] [Python      ] Interpreter at "C:\Program Files\Python37\python.exe"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer"
[INFO   ] [deps        ] Successfully imported "kivy.deps.angle"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2_dev"
[INFO   ] [Factory     ] 184 symbols loaded
[DEBUG  ] [Cache       ] register <kv.lang> with limit=None, timeout=None
[DEBUG  ] [Cache       ] register <kv.image> with limit=None, timeout=60
[DEBUG  ] [Cache       ] register <kv.atlas> with limit=None, timeout=None
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_gif (img_ffpyplayer ignored)
[DEBUG  ] [Cache       ] register <kv.texture> with limit=1000, timeout=60
[DEBUG  ] [Cache       ] register <kv.shader> with limit=1000, timeout=3600
[INFO   ] [Text        ] Provider: sdl2
[DEBUG  ] [Cache       ] register <textinput.label> with limit=None, timeout=60.0
[DEBUG  ] [Cache       ] register <textinput.width> with limit=None, timeout=60.0
[DEBUG  ] [App         ] Loading kv <.\epic.kv>
[DEBUG  ] [App         ] kv <.\epic.kv> not found
[INFO   ] [Window      ] Provider: sdl2
[INFO   ] [Window      ] Activate GLES2/ANGLE context
[CRITICAL] [Window      ] Unable to find any valuable Window provider. Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config) and re-run your app to identify potential causes
sdl2 - RuntimeError: b'Could not initialize OpenGL / GLES library'
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\__init__.py", line 71, in core_select_lib
    cls = cls()
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 146, in __init__
    super(WindowSDL, self).__init__()
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\__init__.py", line 970, in __init__
    self.create_window()
  File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 282, in create_window
    self.fullscreen, resizable, state)
  File "kivy\core\window\_window_sdl2.pyx", line 225, in kivy.core.window._window_sdl2._WindowSDL2Storage.setup_window
  File "kivy\core\window\_window_sdl2.pyx", line 75, in kivy.core.window._window_sdl2._WindowSDL2Storage.die

[CRITICAL] [App         ] Unable to get a Window, abort.

Did you find the solution
I am facing the same problem

did you try this?

Use angle and sdl2 and remove glew: pip uninstall kivy-deps.glew
in your app:
import os
os.environ['KIVY_GL_BACKEND']='angle_sdl2'

@Bertik23 I had the same issue on a windows 10 VM, it's not your machine.

It's not work!
On Mon, 17 May, 2021, 2:36 pm ShoofLLC, @.***> wrote:

I think I'm very unlucky.
[INFO   ] [Logger      ] Record log in C:\Users\werto.kivy\logs\kivy_19-05-04_2.txt
[INFO   ] [Kivy        ] v1.11.0.dev0, git-8f375d8, 20190502
[INFO   ] [Kivy        ] Installed at "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy_init_.py"
[INFO   ] [Python      ] v3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)]
[INFO   ] [Python      ] Interpreter at "C:\Program Files\Python37\python.exe"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.gstreamer"
[INFO   ] [deps        ] Successfully imported "kivy.deps.angle"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew"
[INFO   ] [deps        ] Successfully imported "kivy.deps.glew_dev"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2"
[INFO   ] [deps        ] Successfully imported "kivy.deps.sdl2_dev"
[INFO   ] [Factory     ] 184 symbols loaded
[DEBUG  ] [Cache       ] register <kv.lang> with limit=None, timeout=None
[DEBUG  ] [Cache       ] register <kv.image> with limit=None, timeout=60
[DEBUG  ] [Cache       ] register <kv.atlas> with limit=None, timeout=None
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_gif (img_ffpyplayer ignored)
[DEBUG  ] [Cache       ] register <kv.texture> with limit=1000, timeout=60
[DEBUG  ] [Cache       ] register <kv.shader> with limit=1000, timeout=3600
[INFO   ] [Text        ] Provider: sdl2
[DEBUG  ] [Cache       ] register <textinput.label> with limit=None, timeout=60.0
[DEBUG  ] [Cache       ] register <textinput.width> with limit=None, timeout=60.0
[DEBUG  ] [App         ] Loading kv <.\epic.kv>
[DEBUG  ] [App         ] kv <.\epic.kv> not found
[INFO   ] [Window      ] Provider: sdl2
[INFO   ] [Window      ] Activate GLES2/ANGLE context
[CRITICAL] [Window      ] Unable to find any valuable Window provider. Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config) and re-run your app to identify potential causes
sdl2 - RuntimeError: b'Could not initialize OpenGL / GLES library'
File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core_init_.py", line 71, in core_select_lib
cls = cls()
File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 146, in init
super(WindowSDL, self).init()
File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window_init_.py", line 970, in init
self.create_window()
File "C:\Users\werto\AppData\Roaming\Python\Python37\site-packages\kivy\core\window\window_sdl2.py", line 282, in create_window
self.fullscreen, resizable, state)
File "kivy\core\window_window_sdl2.pyx", line 225, in kivy.core.window._window_sdl2._WindowSDL2Storage.setup_window
File "kivy\core\window_window_sdl2.pyx", line 75, in kivy.core.window._window_sdl2._WindowSDL2Storage.die
[CRITICAL] [App         ] Unable to get a Window, abort.
Did you find the solution
I am facing the same problem
did you try this?
Use angle and sdl2 and remove glew: pip uninstall kivy-deps.glew
in your app:
import os
os.environ['KIVY_GL_BACKEND']='angle_sdl2'
@Bertik23 https://github.com/Bertik23 I had the same issue on a windows
10 VM, it's not your machine.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kivy/kivy/issues/6276#issuecomment-842156391, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ATX5VS2TLGP65EHEBUFN7VLTODMBFANCNFSM4HJFVXAA
.

@VinayPoul you need to add YOUR error logs not someone else's if you want anyone to help you

Ok, looks like the issue still persists. So I'm reopening the issue. We have run into the same problem at school

Installation procedures significantly changed between your original report, so please make sure to follow the exact instructions including using a virtualenv.
These issues arise when not following the instructions exactly, using an incompatible python/windows or if something is messed up with your system (something installed in the global path that clashes with Kivy). We can't really do anything about this, especially not on a github issue. I'm closing because we don't provide support on github issues so if you need further help on installation, please ask on discord.


[firebase_admob] Add support to mute video ads

Is your feature request related to a problem? Please describe.
My app is a video app, when the video ads shows while video is playing, it's annoying.
Describe the solution you'd like
If it's possible please provide setMute function to the MobleAd class

we also need it!

Would be a great improvement to the package!!

Yes, I need it too!!

I hope we will have this feature soon!

The firebase_admob plugin will be deprecated in April 2021 in favor of Google Mobile Ads SDK for Flutter.
Google Mobile Ads SDK for Flutter is a new Flutter plugin that supports more Ads formats than firebase_admob does. Google Mobile Ads SDK for Flutter currently supports loading and displaying banner, interstitial (full-screen), native ads, and rewarded video ads across AdMob and AdManager. It also supports displaying banner and native ads as Widgets as opposed to being overlayed over all app content.
We're now recommending projects currently using firebase_admob migrate to Google Mobile Ads SDK for Flutter following the instructions outlined here.
Issues with migrating or with using the new package should now be raised over on the Google Mobile Ads SDK for Flutter repository.


fix quotes in docs

Coverage remained the same at 100.0% when pulling 9553a5ec212ee55974f00e49e33390d70373f78b on tony:patch-1 into 92196509f2f8100d5fce5bb21f0372598078c83c on prymitive:master.

Thanks!


Custom Policies Azure AD B2C - No sign in requested - how hook up the Web app a'la User Flows?

Hi
I followed the steps to setup KSMI custom policies in this example and with local account. When I open the web app no sign in is required. I guess I didn't hook up the custom policies for this web app like it's done for User Flows?
How do I hook up or do I have to hook up the equivalent of the user flows (below for another tenant with non-custom policies) but for a web app with custom policies?
I use this WebApp-WebAPI example for authorization  which I registered in the tenant where I setup custom policies and I changed the Web.config policies as per those setup in Custom policies.
Thank you

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bee63035-00ee-f7fd-97a1-69dae5f808ef
Version Independent ID: a3447928-73cc-0290-6d46-b89234757e3b
Content: Get started with custom policies - Azure AD B2C
Content Source: articles/active-directory-b2c/custom-policy-get-started.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@sergiosolorzano Thank you for your query . We will investigate and update the thread further.

Hi, I hooked up the web app - web api example to custom policies and works, but it doesn't KMSI if I close the browser.

Based on your confirmation that Firefox was set to remove cookies when browser closes, which was causing the issue, I am closing this thread.


Eb/bump upstream

Bump to use the latest upstream changes for the wagmi-magic-connector
Out changes have been rebased on top of the latest upstream version.

Once approved, this I will reset our main to match the changes in this PR.


fix syntax to remove html tags

Changes
Updated syntax in formula to remove <em> tags
Closes #279
Screenshots

Thank you, @Tansito
(not sure why those always update whenever I make a change in a notebook)

It gets the environment configuration from the last run but doesn't affect anything, no problem.


External Form Upload: add ability for staff to import a CSV of user form submissions

Log in as staff and go to /staff/external_form_upload and you will see a place for organizations to upload data via a CSV from a third party form, e.g., google forms.
To do

add a note to the above description that currently we only support google form CSVs
add a route and controller action (create) that will take the submitted CSV and execute the CSV import service. Note that we currently have app/services/organizations/csvimportservice but please add a new directory importers to app/services/organizations and rename the existing csvimportservice to google_csv_import_service.rb and put it in that new directory - flexible on naming if you can think of better!
manually test things. You will need to get an example of a google form CSV
write tests that ensure the flow works as expected e.g., incude a dummy CSV and make sure you test that it creates Form Answers for users with a matching email, and skips those where there is no email match.

Questons? Ask away...

@wandergithub this issue is related to what you just worked on if you are interested?

Yes, I'm in.

I have managed to accomplish this so far:
CSV file:

FormSubmission created:

Currently, we can upload the FormSubmission with the respective FormAnswers and it seems fine under my limited understanding.
But a few doubts got my attention:
And I don't know if I'm supposed to address these now. For instance, my "email" and "timestamp" had to be manually named. This was not the default name when exported from Google Forms.
What about nil files and user feedback? I guess we are not addressing these things here??

@wandergithub i got an email notification with some questions, but I think you may have deleted the comment? Let me know what questions you have!


Test suite cleanup using LXC

Cleaned up the Travis tests here to make it simpler for me to add tests for other distros in preparations for adding support for more distributions.

Also removed cuda_packages: "traceroute" as part of the test because it's not really testing CUDA installation if CUDA doesn't get installed, but you can change that back if you want.
TODO is to re-add the test against ansible-devel.
Setting cuda_init to false skips a few tasks, but starting the actual service fails because the CI environment does not have an nvidia device. Could try to resolve this by just enabling the service in one step and then a handler to start the service (with a variable toggle to skip it that we could use during the test). Thoughts?

Nice! Haven't used LXC before, it looks a lot cleaner.
I think a handler would be good for this cuda_init.service.
How does my commit look?

There needs to be a default for cuda_init_restart_service set for this I believe.

Okay, this looks good to me.


Create animated gif to help describe what project does

@vincentmorneau I added a animated gif. Let me know what you think. I built it using Screenflow and saved the original files so can modify it and markup as well.

@martindsouza I think it's good! Closing this for now.


Could you give me some suggestions for training dataset?

Hi, I have trained a Chinese OCR model by CRNN ( 300W synth text image as train dataset). but the model has poor result for the real scene. So could you give me some suggestions for training dataset:
Does the dataset require a fixed aspect ratio?
Does the dataset need some data augment, e.g. transform , blur, different font color and diverse background and so on?

Hi, is your 300W synth text image data public? I'm working on receipt ocr now but my data hasn't been enough.


[gui error report] Error

👉 Please describe what you were doing when this error happened.
Specifications

OS: darwin
IPFS Desktop Version: 0.20.2
Electron Version: 17.1.0
Chrome Version: 98.0.4758.102

Error
Error
    at errorTemplate (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/migration-prompt.js:78:49)
    at loadWindow (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/migration-prompt.js:115:26)
    at module.exports (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/migration-prompt.js:120:3)
    at startIpfsWithLogs (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/daemon.js:158:9)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async module.exports (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/daemon.js:174:17)
    at async startIpfs (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/index.js:46:17)
    at async module.exports (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/index.js:114:3)
    at async run (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/index.js:83:5)

ps.
"Could not connect to the IPFS API" in GUI
I need to start ipfs daemon by command manually
below for the command response
Initializing daemon...
go-ipfs version: 0.11.0
Repo version: 11
System version: amd64/darwin
Golang version: go1.16.12
......
API server listening on /ip4/<IP_ADDRESS>/tcp/5001
WebUI: http://<IP_ADDRESS>:5001/webui
Gateway (readonly) server listening on /ip4/<IP_ADDRESS>/tcp/8080
Daemon is ready

Hi @leeswlwpl! Could you try updating to the newest version of IPFS Desktop? If you keep having this issue after upgrading, let me know.

I have updated IPFS Desktop and retried
but still exist problem
please check my new report #2128
Thanks so much!


Describe Build.SourceBranch[Name] value if triggered by git tag

Using https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/github-release?view=azure-devops I inferred that for tag-triggered builds, Build.SourceBranch is something like refs/tags/1.0 and (although not explicitly mentioned there) Build.SourceBranchName would then be 1.0. Is this correct? Either way, it should be described in here.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9ffebdc8-521c-44b5-cde4-4abdc1bd6f18
Version Independent ID: dc0effda-6d93-62aa-64c5-4e6f283b0826
Content: Predefined variables - Azure Pipelines
Content Source: docs/pipelines/build/variables.md
Product: devops
Technology: devops-cicd
GitHub Login: @andyjlewis
Microsoft Alias: alewis

How do you determine if there is a tag at all? Documentation needs a lot of work around git tags.

How do we get the branch name if the build was started via a git tag.


PLAT-65757: Move to a previous or next page via a channel up and down immediately

Checklist

[X] I have read and understand the contribution guide
[X] A CHANGELOG entry is included
[X] At least one test case is included for this feature or bug fix
[ ] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
The UX for page navigation via channel up and down was updated. VirtualList or Scroller jump to a previous or next page via a channel up and down immediately instead of jumping to the first or last visible item in the current page.
Resolution
There were 3 conditions to jump via channel up and down in VirtualList and Scroller with the previous UX.
Priority 1> If Spotlight was not on the first or last visible item in the current page, they jumped to it.
Priority 2> If Spotlight was on the first or last visible item in the current page and there was the spottable item in the previous or next page, it jumped to the first or last item in the page.
Priority 3> If Spotlight was on the first or last visible item in the current page and there was no the spottable item in the previous or next page, it jumped to the next spottable item.
For the update UX for page navigation, I just moved the Priority 1> to the lowest priority. So VirtualList and Scroll will jump to the previous or next page immediately via channel up and down.
Additional Considerations
Even though changing the priority, Scroller did not meet the full page navigation UX yet. So I also fixed it together.
Comments
PLAT-65757

I have two general questions. The first one: Is removing a searching logic to find the target in the current page from scrollByPage in Scrollable intended? The second one: do this PR affect any behaviors on overscroll effects? (overscroll logic depends on the result of scrollByPage method.)

@0x64

The first one: Is removing a searching logic to find the target in the current page from scrollByPage in Scrollable intended?

We need to search the spottable item in the next page first. So I remove the logic that you mentioned.

The second one: do this PR affect any behaviors on overscroll effects? (overscroll logic depends on the result of scrollByPage method.)

I didn't change the return value for scrollByPage in Scrollable. So the behaviors won't be changed.

Closing in favor of #2262


chore(main): add stale issue/pr removal automation

📑 Description
Added a GitHub actions automation to remove stale PRs and Issue after 60 days, while first issuing a warning.
✅ Checks

[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required

ℹ Additional Information

Adapted workflow in Linear, not needed currently, so closing this.


Add simple Haskell

By far the slowest implementation! Takes around 40s to run :)

Thanks for the contribution! Unfortunately I believe it goes against the constraints, as it reads the whole input into memory at once (unless I'm wrong about getContents), and I've generally not being merging solutions which are slower than the Shell version. If we can fix the "reading whole file into memory" issue I'd consider merging but excluding from the benchmarks (otherwise it just makes Haskell look slow :-). See also this Haskell version, which was similar https://github.com/benhoyt/countwords/pull/67#issuecomment-803044625

getContents reads the input lazily, meaning it gets one line at a time only when needed. I'll try to profile it and see if I can make it a little faster :)

getContents reads the input lazily, meaning it gets one line at a time only when needed

Oh, thank you for that clarification!


pysha3, which is EOL, is listed as a requirement, but doesn't appear to be used.

Hey friends.  How are y'all?
So, pysha3==1.0.2 is listed as a dependency in the requirements file.  As you can see, this project is EOL and no longer supported: https://github.com/tiran/pysha3.
I forked this repo with a mind toward using hashlib or eth_utils instead of pysha3, but it appears that... that's already the case?
A brief foray into the history hasn't illuminated where pysha3 was used - maybe somebody who is more familiar with the dependencies can chime in?
Here's a simple commit updating a couple of dependencies and  yanking pysha3, and the tests still pass: #20

You can use the drop-in replacement module that fixes that issue: https://github.com/BoboTiG/py-eip712-structs-ng

Thanks @BoboTiG :-)


[FLINK-10898][flink-yarn]Add yarn.application-attempts-failures-validity-interval in YarnConfigOptions

What is the purpose of the change
The attempt failure validity interval says that an application is only killed after the system has seen the maximum number of application attempts during one interval. This avoids that a long lasting job will deplete it’s application attempts.
Now the attempt failure validity interval is set to the Flinks’ Akka timeout value, I think we need to add a separate configuration setting of this. So add yarn.application-attempts-failures-validity-interval  to describe it in YarnConfigOptions.

@tzulitai
Please help review.

This problem has been fixed with #8400.


MKOB: Received code stops short of that sent

The received code window stops two characters short of what is sent on the wire.
For example, when receiving code on a wire where another station sends "ABCDEFG", the received code window shows "ABCDE" (missing the "FG").
Image from MKOB-2.5 (sending) and MKOB-4.0.3 (receiving):

MKOB needs to call pykob.morse.Reader.flush() after a 'suitable' length of time has passed with no new characters being received. A timer mechanism similar to that used in MorseKOB 2.5 will do the job.

Thanks. That's what I was looking at, but hadn't tried it yet. I'll try
that tonight.
Sent from my phone.
On Sun, Jun 21, 2020, 3:36 PM Les Kerr<EMAIL_ADDRESS>wrote:

MKOB needs to call pykob.morse.Reader.flush() after a 'suitable' length
of time has passed with no new characters being received. A timer mechanism
similar to that used in MorseKOB 2.5 will do the job.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MorseKOB/PyKOB/issues/74#issuecomment-647190499, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AETPXO7HX5XUJVFQOD7Z6ATRX2DODANCNFSM4ODHTHSQ
.

When MKOB-2.5 and MKOB-4.0 are run side-by-side the MKOB-2.5 window is 2 characters ahead of the MKOB-4.0 window.
Unless you have the two open together this probably isn't a big issue. Maybe flushing at a 'reasonable' time after the last character received will resolve this.

Do we understand the root cause of the delay?  Isn’t the receiving code largely similar?  Is the lagging text added to the display buffer and not shown, or not even added to the display buffer yet?
I’ll be curious to see an update when you find what it takes - I think we should make the two absolutely equal; I DON’T think a 2-character lag would be acceptable to most users.  We want this to be as “real time” as possible.

On Jun 21, 2020, at 11:25 PM, Ed Silky<EMAIL_ADDRESS>wrote:
When MKOB-2.5 and MKOB-4.0 are run side-by-side the MKOB-2.5 window is 2 characters ahead of the MKOB-4.0 window.
Unless you have the two open together this probably isn't a big issue. Maybe flushing at a 'reasonable' time after the last character received will resolve this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/MorseKOB/PyKOB/issues/74#issuecomment-647311527, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALTAYKYFLYUDKN23GW7GDWDRX32NRANCNFSM4ODHTHSQ.

There are two things going on here. The first is that the code reader needs a timer to determine when the sender has stopped sending and the reader should flush its buffer. Until this feature is added to the program, the last character or two will be pending.
The second is that there's an intentional, roughly one second delay built into the receiving client. This is the way CWCom works, and MorseKOB 2.5 works the same way. The reason for this is to smooth out the jitter that would result if a short letter (such as E) were to be decoded immediately and then followed by a long letter (such as J).
The only problem with having the receiver lag behind the sender is when an operator wants to break in between the transmissions between two other operators. To get around this, the receiving client responds immediately to the initial opening of the circuit and only starts buffering with the first character after the circuit is opened. This is not entirely realistic, but all things considered it seems to be the best compromise.

I agree with Les. The problem with the last two characters is that they are not displayed until another character is received. I started adding a timer that will flush the buffer if a character isn't received for some amount of time (probably just less than a second).
I was looking at how to correctly incorporate an async timer that can be cancelled/reset/restarted when a new character is received and flush if it expires, but then got pulled away.
I will try to get back on that. If you know OTTOYH let me know and I'll put it in my branch and test it out.


Update point colours for colour blind users (AA)

Fixed in main

the makers now seems to be on a gradient of transparency when first loaded. Also can user csv points be blue to match the toggle?!

Ah sorry I seem to have messed up. Please revert to one before. I will build this in another branch.


Incompatibility with non-integer stoichiometric coefficients

Hey!
I was trying to generate spyjac library for the detailed mechanism by Ranzi et al. http://creckmodeling.chem.polimi.it/menu-kinetics/menu-kinetics-detailed-mechanisms/menu-kinetics-complete-mechanism
However, in that particular mechanism, there are multiple reactions with non-integer stoichiometric coefficients. In spyjac code generation,  integer type (kint_type) is assumed for variables related to stoichiometric coefficients which yields an error.
Can you say whether there is some theoretical  / implementation reasons for the integer requirement? Can we simply replace the kint_type by np.float64 or would it result in problems elsewhere?
-Heikki

Hey Heikki -- there's no particular reason for the integer only requirement, other than that's the only case I've run into thus far.
I think you should be able to replace the kint_type with np.float64, and the code-gen stuff should be able to figure it out from there, but I can't guarantee something won't break in the process.
I won't have time to look at this for a little bit (working on revisions right now), but if I were going to implement it, I would have the assign_rates method check the necessary dtype for a model and set a  kint_type in the return dictionary that could then be parsed during Namestore generation.
Happy to look at any PR in the meantime!
Best,

Nick

Hey,
Good to know that there is no particular reason for it. I'll try to come up with a working solution and let you know / PR.
-HK


GUI overhaul

Could you change the GUI to be a list with options after the names? Currently the sytem you in place is great but usernames can be hard to type when long or complicated.
This could allow more options along with simplifying teleporting to others along with knowing who is permanently allowed to teleport to you.
If you wish to keep things simple then that's understandable. Idealy a tab to complete option would be greatly appreciated if that is the case.

Added basic tabcomplete functionality in #15
I hope the changes are ok and that it can be merged.


implementing and  ITaskHandlerStatus

i'm trying to schedule a com object implementing ITaskHandler interface
i've download your template project "COMTask"
Registering the task with this code everything works well
TaskService  ts = new TaskService();

TaskDefinition comTd = ts.NewTask();
comTd.RegistrationInfo.Description = "my first schedule on a COM object";

wt = new DailyTrigger();
wt.StartBoundary = new DateTime(DateTime.Today.Year, DateTime.Today.Month, DateTime.Today.Day, 14, 0, 0, 0, DateTimeKind.Local);
wt.Repetition.Interval = TimeSpan.FromMinutes(100);
comTd.Triggers.Add(wt);

ComHandlerAction cha = new ComHandlerAction(new Guid("{CE7D4428-8A77-4c5d-8A13-5CAB5D1EC734}"), "mydata");
comTd.Actions.Add(cha);

ts.RootFolder.RegisterTaskDefinition("My COM TAsk", comTd);

now i'd like to implement ITaskHandlerStatus interface in order to get the percentage of completion.
i've noticed that in your project,
into the file "TaskHandlerBase.cs" there is this interface "decorated" with a different "GUID" (different from the other one on the ITaskHandler interface)
so what does it mean? i have to register another COMtask with this guid?
is not sufficent implement this interface(ITaskHandlerStatus) into the com object i've already registered?
i've not understood well how to do
at first i thought to add the ITaskHandlerStatus interface to you COMTask class and implement its methods
your class
public class MyCOMTask : TaskHandlerBase

to
public class MyCOMTask : TaskHandlerBase, ITaskHandlerStatus

but if so, i don't understand the meaning of the second "GUID"
Originally posted: 2015-05-22T00:39:42

The ITaskHanderStatus interface is exposed through the StatusHandler property of TaskHandlerBase. Suppose you had a task that needed to write information to a log file every few seconds and terminate after 100 entries. You would create a Timer instance inside your TaskHandlerBase inherited class and then have a method like the following that would be called when that Timer's Elapsed event was called:
const int maxWrites = 100;
int writeCount = 0;

void timer_Elapsed(object sender, ElapsedEventArgs e)
{
  if (writeCount < maxWrites)
  {
    try
    {
      using (StreamWriter wri = File.AppendText(file))
        wri.WriteLine("Log entry {0}", DateTime.Now);

      this.StatusHandler.UpdateStatus((short)(++writeCount / maxWrites), string.Format("Log file started at {0}", lastWriteTime));
    }
    catch { }
  }

  if (writeCount >= maxWrites)
  {
    timer.Enabled = false;
    writeCount = 0;
    this.StatusHandler.TaskCompleted(0);
  }
}

Originally posted: 2015-05-22T08:46:58


Avoid using invalid matches

This is a replacement of #229  (I've accidentally pushed to master effectively merging it; and undoing that does not reopen the PR..)
(addressing #228)

@bochen87 please use this state of the branch for testing.
I had to do quite some changes fixing several places where invalid matches were actually used.
Could somebody please have a closer look on the changes?

@HannesSommer
Couldn't compile, compile errors:

Errors     << libpointmatcher:make /opt/enway/ws/logs/libpointmatcher/build.make.002.log
libpointmatcher/examples/compute_overlap.cpp: In function ‘int main(int, char**)’:
libpointmatcher/examples/compute_overlap.cpp:223:40: error: ‘InvalidDist’ is not a member of ‘Matches {aka PointMatcher<float>::Matches}’
       if (targetMatches.dists(k, i) != Matches::InvalidDist)
                                        ^
make[2]: *** [examples/CMakeFiles/compute_overlap.dir/compute_overlap.cpp.o] Error 1
make[1]: *** [examples/CMakeFiles/compute_overlap.dir/all] Error 2

Sorry, wrong warning - I cleaned up build and everything and built from scratch, worked now

This is probably a local issue. Are you compiling it with catkin? In any case you: you are using outdated headers that probably were installed through make install. Try to find an delete them. In case of catkin delete devel/includes/libpointmatcher. Otherwise you have to track which header is actually used OR try make uninstall in pointmatchers build folder.

👍
wow, thanks for the really fast replies! yeah, somehow figured that out as well, InvalidDist was clearly defined in the header, so i cleaned up build folder and it worked perfectly, now on to testing!

I've done some stability testing, let it run for 30+ mins - seems to work.
Will do some more test cases tomorrow, probably safe to merge after tests of tomorrow.

@HannesSommer Did some more dynamic obstacle tests and it seems to be working stable!

Nice, thanks for testing and reporting.
Does somebody have time to go over the changes before we merge?
In particular I'm not 100% sure about my decision to set the weights (OutlierFilters) to zero for all invalid matches as in https://github.com/ethz-asl/libpointmatcher/pull/230/files#diff-d26b55af8634c8550d46bdc8c70e2d91R255 .

The other outlier filters (VarTrim, Trim and Welsch) set a zero weight to matches that should be ignore by the error minimizer.  It makes sense that an invalid match should not contribute to the error minimization.

I've aksed @PhiBabin to take a look. He's working on outlier rejection on our side.

Thanks @PhiBabin  and @pomerlef  !
Then we can merge I assume?

All good for me. Thanks @HannesSommer for taking care of that.


feat(CX-2734): remove the new tag from the career highlights cards

Description

This PR resolves CX-2734
QA Testing

Acceptance Criteria

the new tag is not used on the career highlights cards

Setup Instructions

PR Checklist

[x] I tested my changes on iOS / Android.
[ ] I added screenshots or videos to illustrate my changes.
[ ] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[ ] I hid my changes behind a feature flag.
[ ] I have prefixed changes that need to be tested during a release QA with [NEEDS EXTERNAL QA] on the changelog.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

remove the new tag from the career highlights cards -daria

iOS user-facing changes

Android user-facing changes

Dev changes

removed MyCollectionCareerHighlightsModel -daria

Need help with something? Have a look at our docs, or get in touch with us.

An update migration still was needed
Since I don't think we released it, I've just removed the model from Versions. Is it the right thing to do? Or this would be better?


ResourceManagerClient.Resources.DeleteAsync throws cloudexception

Query/Question
Every time we try to delete a resource using the resource we a get a cloud exception message saying "Long running operation failed with status "Not Found"" and body saying "ParentResourceNotFound"
As a work around we catch the exception and make a get a call to verify the instance was deleted. How do I fix this?

Environment:

Name and version of the Library package used:  Microsoft.Azure.Management.ResourceManager.Fluent, Version=<IP_ADDRESS>

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

hi @xccc-msft could  you pls help on this? thanks.

@dejimarquis Could you please share which type of resource you were trying to delete? Thanks.

@xccc-msft The resource type being deleted is Microsoft.DigitaltTwins

@dejimarquis Can you please share an example of resource id? Thanks.

hi @dejimarquis could you pls share resource id for investigation? thanks

hi @dejimarquis could you pls share resource id for investigation? thanks


Type declarations

I am trying to use some attributes of the Popup method (ex. 'type', 'callback'... etc) and although they work, they give me typing errors in vscode, I have looked in the expected types and they are not declared.

Is it possible that the types in this file are missing? I don't know if more attributes are missing in other methods

Thank you for raising this! Could you please try updating your index.d.ts file with the following changes and see if it resolves the issue? I'll release an update based on this if it works for you:
declare module "react-native-popup-confirm-toast" {
    import {FC} from "react"
    import {StyleProp, TextStyle, ViewStyle} from "react-native"

    export interface Config {
        title?: string
        text?: string
        titleTextStyle?: StyleProp<TextStyle>
        descTextStyle?: StyleProp<TextStyle>
        backgroundColor?: string
        timeColor?: string
        position?: "top" | "bottom"
        icon?: FC
        timing?: number
        statusBarType?: "default" | "dark-content" | "light-content"
        statusBarTranslucent?: boolean
        statusBarHidden?: boolean
        statusBarAndroidHidden?: boolean
        statusBarAppleHidden?: boolean
        hiddenDuration?: number
        startDuration?: number
        onOpen?: () => void
        onOpenComplete?: () => void
        onClose?: () => void
        onCloseComplete?: () => void
        type?: string;
        callback?: () => void;
    }

    export interface SheetConfig {
        background?: string
        height?: number
        duration?: number
        closeDuration?: number
        closeOnDragDown?: boolean
        closeOnPressMask?: boolean
        closeOnPressBack?: boolean
        dragTopOnly?: boolean
        component?: FC
        onOpen?: () => void
        onOpenComplete?: () => void
        onClose?: () => void
        onCloseComplete?: () => void
        customStyles?: StyleProp<ViewStyle>
        timing?: number
        keyboardHeightAdjustment?: boolean
    }

    export interface Toast {
        show: (props: Config) => void
        hide: () => void
    }

    export interface Popup {
        show: (props: Config) => void
        hide: () => void
    }

    export interface SPSheet {
        show: (props: SheetConfig) => void
        setHeight: (height: number, onOpenComplete: () => void) => void
        hide: () => void
    }

    export const Toast: Toast
    export const Popup: Popup
    export const SPSheet: SPSheet
    export const Root: FC
    export const getStatusBarHeight: FC
    export const isIPhoneWithMonobrow: FC
}

Thank you for the quick response!
I can confirm that it solves the issue, but only for the examples I provided.
To give another example, 'bodyComponent' is not typed.
These are just examples, and there’s no rush. It would be worth checking the attributes in the documentation against the declared types to ensure they all match exactly.
Thanks! :)

Hi there! 🎉
We’ve expanded and improved the type definitions based on your request. You can check out the changes in this commit:
85918f9 - TypeScript type definitions updated
When you have a chance, we’d love for you to review the updates. If you encounter any errors or notice something missing in the type definitions, please let us know. Thanks in advance for your feedback! 😊

Hi, thank you so much! I’ve reviewed it, and most of the missing ones are there, but these are still missing specifically:
PopupConfig:
bodyComponentForce
onLayout
background
Could you publish these changes to npm?
Thank you! 😊


Can't click some UI elements in the Cluster Dashboard in master-head.

What kind of request is this (question/bug/enhancement/feature request):
Bug
After creating a cluster I get JS errors in the Chrome Dev Tools console and I can't click in any element of the Cluster Dashboard body section.
I tried Kubectl Config and Events but nothing happened. Clicking Launch kubectl works.
Steps to reproduce (least amount of steps as possible):

Install latest master I used latest master-head v2.3 10/07/2019
Create a cluster. I used a GKE cluster.

Result:
Can't get kubectl config file and some elements are not clickable.

Other details that may be helpful:
Uncaught (in promise) TypeError: Cannot read property 'parentNode' of undefined
    at m (percent-gauge.js:267)
    at g (percent-gauge.js:272)

Environment information

Rancher version: master-head v2.3 10/07/2019
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): GKE
Machine type (cloud/VM/metal) and specifications (CPU/memory): 3 Nodes

I wasn't able to reproduce this with rancher v2.3.0-rc12

I'm not able to reproduce in latest rancher master-head 10/21/2019. Without monitoring.
I have to test with monitoring enabled but that is blocked by: https://github.com/rancher/rancher/issues/23573

Tested with Rancher server rancher\rancher:master-head version 9930781c8
Create a cluster.
No Errors were seen in Dev Tools.

Kubectl Config can be accessed.

Events can be accessed.

Launch kubectl can be accessed.

Edit dropdown can be accessed.


Add support for binding handler 'after' logic

https://github.com/knockout/knockout/blob/45e86bf0347cf742ca359bab051ea82fdfae7a5d/src/binding/defaultBindings/checked.js#L4

The after property is souly used in the checked binding. Since the binding does not control descendant bindings, the binding context remains the same and it only affects runtime.


No justfile found

Attempting to follow the README to install shows the user needs to run just setup
just is installed and in the path, yet attempting to use it how the instructions show results in an error. No justfile found
 ls
CHANGELOG.md			LICENSE				docker-compose-prod.yml		docker-compose.yml
Dockerfile			README.md			docker-compose.override.yml	src

error: No justfile found

Are the just instructions outdated?

Are you running it from the src directory? This was an unfortunate necessity in the past based on project structure though I'm looking to see if I can move the justfile to the root where it makes more sense.

Thanks I didn't realize I needed to be in src dir.
Is php version 8.3 really required? Could it be bumped to support 8.4?
just setup
composer install
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Your lock file does not contain a compatible set of packages. Please run composer update.

  Problem 1
    - php-vcr/php-vcr is locked to version 1.8.0 and an update of this package was not requested.
    - php-vcr/php-vcr 1.8.0 requires php ^8,<8.2|>=8.2.9,<8.4 -> your php version (8.4.1) does not satisfy that requirement.
  Problem 2
    - justintime50/vcr-accessories is locked to version v0.3.0 and an update of this package was not requested.
    - justintime50/vcr-accessories v0.3.0 requires php-vcr/php-vcr ^1.7 -> satisfiable by php-vcr/php-vcr[1.8.0].
    - php-vcr/php-vcr 1.8.0 requires php ^8,<8.2|>=8.2.9,<8.4 -> your php version (8.4.1) does not satisfy that requirement.

error: Recipe `install` failed on line 19 with exit code 2
error: Recipe `setup` failed with exit code 2

This project supports php 8.4; however, a downstream testing dependency does not, I apologize. For now I would stick with 8.3 until PHP VCR loosens their PHP version pinning (unlikely to be soon, they are often very slow to react).
Alternatively you could install dependencies and skip dev deps which should get you where you need to be.


Update PatchTSModel to handle integer timestamp

🚀 Feature Request
In #178 it was found that PatchTSModel fails on data with integer timestamp. It could be fixed.
Proposal
Fix tests tests/test_models/test_inference/test_forecast/TestForecastOutSample for models:

PatchTSModel

This model fails on additional numeric feature, which breaks dimension expectations. It seems like this model can't work with additional features and this probably should be fixed.
To discuss:

Should timestamp be treated as additional numeric feature? It probably should be decided for all the models (RNNModel, MLPModel, etc)
Should this model be able to work with additional numeric features?

Test cases

Add tests on working with additional features
Move fixed tests in tests/test_models/test_inference/test_forecast/TestForecastOutSample from fail to success category
Move fixed tests tests/test_models/test_inference/test_predict/TestPredictInSampleSuffix from fail to success category

Additional context
Blocked by #178.

Let's for now fix it to work with only target column.
And add extra task to backlog for support for extra features

We should not use timestamp in integer format column for any dl models

Will be done in #191.


[CLOSED] Import replace links with tags

 Issue by elliotcm
Wednesday 19 March 2014 at 10:49 GMT
Originally opened as https://github.com/alphagov/specialist-publisher/pull/49

https://www.pivotaltracker.com/story/show/67773190

elliotcm included the following code: https://github.com/alphagov/specialist-publisher/pull/49/commits

 Comment by heathd
Wednesday 19 March 2014 at 10:50 GMT

tests?


Remove path just in case it breaks

I’ve been considering updating my docs for a while now, besides when v3 releases the url might break so yeah

I'm gonna have to make some changes to that btw

ok so this is good
Ima merge

Also. Could you please help me make a better package manager for win93 and win96? It's in my repos


Hint option in coop

Give the option to enable hints when setting up a coop room.

Included in next release.


Website Interface!

Issue will be closed if:
I make a good website interface model which contains algorithms.
I'll make the interface of all webiste and the algorithms will be further added by the contributors.

Name:
[WEBSITE]
About:
Propose of this that it list all the algorithms inside the website

Labels:
good first issue, gssoc-ext, hacktoberfest, level1

Assignees:

[x] Contributor in GSSoC-ext
[x] Want to work on it

@pankaj-bind can you please assign me the labels i requested for, also please check the level of this issue as i guess it this issue resolves a major problem.


Only persist session when icon update was user initiated

Fixes #158595

I see that we fire this on startup, so it's not the process setting it, it's us

It's us (vscode), not the user. We only want the terminal to persist if the terminal has had user interaction


Bot Feamework Composer - Luis build failed: The model name { boolean } are reserved error when using form dialog feature

Describe the bug
Unable to start bot. Getting Luis build failed: The model name { boolean } are reserved error when trying to use form dialog feature in Bot Framework Composer(v2.1.2)

Version
v2.1.2

Screenshots

Hi @PrajwalNaik2027,
What actually is your model's name? It's not boolean is it? That would be a reserved name. Additionally, is this a C# or JS bot, and are you following any specific pieces of documentation when implementing this feature? Reproduction steps would also be helpful.

Hi @anishprasad01 My model name is forms, it is a C# bot.
I am following this documentation:-
https://www.arafattehsin.com/generate-dialogs-automatically-using-form-dialogs-for-bot-framework-composer/

forms might also be a restricted name. Out of curiosity, have you tried any others?

No @anishprasad01 I haven't tried any other name, will try something else and check

@anishprasad01 I tried another name other than forms and still getting the same error

@PrajwalNaik2027
I was able to reproduce this, however the issue seems to be specific to Composer. If you open the solution file in Visual Studio or build and run it in the command line, the bot runs properly and you can trigger the form.
We will investigate the cause of this issue further. In the meantime, it's important to remember that this feature is in preview.
For the time being, developing your bot in Composer, and running it outside Composer is a viable workaround.

Thank you @anishprasad01

Since we have identified a workaround, I am going to go ahead and close this issue. If you need further help with this, feel free to comment and we can reopen the issue. If you have issues or feature requests in the future, please feel free to raise them in the appropriate repository.

Hi @anishprasad01
The Bot is running in vs code but getting ""is not a valid LUIS application ID error, even thought I have updated the LUIS details in the bot via composer, and even in the appsettings file

You might want to check that the appropriate .lu files are also present in the directory, since this is a Composer bot. Can you reproduce this issue with other bots or on other machines? I do not get this error when using a bot with LUIS.
If you can repro it, I'd advise opening a new issue, since this is a different problem.


Performance issue due to eventListeners

What happens?
When trying to serve a very huge openai spec file the page takes roughly 30  40 seconds to initially load. SwaggerUi is instantaneous.

This is related due to either attaching to many scroll listeners or some issue happening with a setTimeout.
Debugging this should be straight forward when running a non minified dev build and taking a look at the performance tab in chrome.
Maybe related to: https://github.com/scalar/scalar/issues/917
What did you expect to happen?
Page being responsive and useable after a short period of time
How can we reproduce the issue?
Try to serve an openai file with x00 routes.
Swagger/OpenAPI Example
No response

Duplicate of #330


VueForm not Working with Nuxt Layers

Environment
nuxt 3.7.0
vueforms
Reproduction

Create a nuxt app with a main app and a layer: https://nuxt.com/docs/getting-started/layers
Follow the vueforms installation instructions in the layer
Start the main app

Describe the bug
The app cannot be rendered because it is missing vueform.config.ts (since this file is sitting in the layer, and not in the main app).
The following error is shown: ERROR  [nuxt] Could not compile template vueformPlugin.mjs.
Putting vueform.config.ts in the main app solves this error.
Additional context
Other nuxt packages like @nuxtjs/tailwindcss support that their config file is taken from the layer if no file is found in the main app. Alternatively, nuxt-ui adds its config to app.config.ts.
Logs
No response

Isn't this in the Nuxt layers documentation?

Make sure any dependency imported in the layer is explicitly added to the dependencies. The nuxt dependency, and anything only used for testing the layer before publishing, should remain in the devDependencies field.

Where is vueform.config.ts file?


WIP: initial files for puya

@tannewt here is a first draft of config files for this new manufacturer and flash chip.
Lots of comments we need to clean up.  They are mostly for confirming with the datasheet found here:
https://datasheet.lcsc.com/lcsc/2006121819_-PUYA--P25Q16H-UXH-IR_C559220.pdf
This really need a review as I am not familiar with SPI flash and lots of the details are above my knowledge on the subject.
I tried to get as much information from the datasheet.  Based from the GD but updated with appropriate data.
I don't know if there are missing fields but since it's based from GD, I suspect this will be a good start...

@tannewt Thanks for the hints on the stream.  Got it compiled with this config.
It might take some time before I get the hardware.
It's your call if you want to merge this in now or want to wait...
That would allow me to update my other PR too.

How about adding a note in the flash config file saying it is untested? We can merge with that notice because it'll make it easier to test.

Good point.  I still haven't heard on getting the hardware for testing.
It's still under "Pre-Order" in their store.


Starting one client causes another to crash with latest build

https://gist.github.com/PurpleIsEverything/c22b4bb4242c887d5d796dce8500e55e

This crash occurred during replication synchronization.  Can you give me an idea of your replication setup?  Are you using Active Replication?  How many masters/replicas?

Active replication yes, we also have/had multi-master on, though the option seems to be gone from the config. 4 instances all with the same configuration essentially connecting to each other.

multi-master was updated to "yes/no"  You can enable with 'multi-master yes' in your config file.

Yes we have it enabled along with active replication, each node is configured with replicaof of the others via the command line (all dockerized)

Fixed in c8516f3dc484920de4fc52acd72f5104d643ca87
This was a regression from the fix for issue #54, sorry for the trouble it has caused.  I will rebuild docker shortly.


showLineNumbers feature does not work for code blocks inside of callouts

[x] The Plugin is up to date
[x] Obsidian is up to date

Describe the bug
When a code block is put inside of a callout with the showLineNumbers feature enabled, line numbers are not rendered.
To Reproduce
Try the following markdown:
```python showLineNumbers
print("Hello World!")
```

> [!note]
> ```python showLineNumbers
> print("Hello World!")
> ```

It renders like

Expected behavior
Line numbers should render in callouts when the feature is enabled.
Occurs on

[ ] Windows
[x] macOS
[ ] Linux
[ ] Android
[ ] iOS

Plugin version
0.2.4

This seems to be a limitation of the Obsidian API. The section info for code blocks in callouts and quotes is null in LP and the section of the callout/quote in reading mode, so there is no way for me to get the code block meta string.


Bump SDK target to 30

might be a good idea to update the samples since some of the Map features won't work when updating, specifically the Google Map App Intents (f.e. clicking the navigation button the the UI Overlay will say 'Google Maps is not installed or is disabled') without adding the <queries/> to the Manifest.

Thanks for flagging this.


factory.createApp() will initApp every time it get called and cause some middleware error

What version of Hono are you using?
4.4.8
What runtime/platform is your app running on?
node.js
What steps can reproduce the bug?
minimal repro is here: https://stackblitz.com/edit/stackblitz-starters-mj3bxo?file=index.js
after app starts, refresh the page, you'll see Hello hono!, this works fine but when you visit or refresh the /v1/feature page, you will see errors on console: Timer "total" does not exist!.
Is this unexpected bug or am I using this factory.createApp() api wrong way?
What is the expected behavior?
There should be no errors.
What do you see instead?
errors on console: Timer "total" does not exist!
Additional information
This relates to the implementation of timing middleware; the second createApp call will initialize an empty map and set it on the context, so the first map gets overwritten.
Considering this injecting variables on context behavior is very common for middlewares, the implementation of factory.createApp() might need some refine.

This relates to the implementation of timing middleware; the second createApp call will initialize an empty map and set it on the context, so the first map gets overwritten.

considering this injecting variables on context behavior is very common for middlewares, the implementation of factory.createApp() might need some refine.

Hi @zoubingwu
Thank you for creating the issue. I've investigated it. It is not factory.createApp() matter, but it may be Timing Middleware's bug. We can reproduce the bug with the following code:
import { timing } from 'hono/timing'
import { Hono } from 'hono'

const app = new Hono()
app.use(timing())

const a = new Hono()
a.use(timing())
a.get('/', (c) => c.text('a'))

app.route('/a', a)

export default app

I'll continue to fix it.

thanks, that was quick!

Created the another issue #3053. We can close this now. Thanks!


README.md link to main.go needs new target

https://github.com/hyperledger/fabric
Under 2.0 Run:
Encoded link for "main.go" text results in "page not found"
The target to the following URL is "page not found" - https://github.com/hyperledger/fabric/blob/master/main.go

it was moved into peer subfolder, I will fix it.

I just tried this link and it seems that this has already been fixed. Closing.

PR #1226


Adds IBM to the list

31 characters maximum, Spaces, ?, ../, curly braces and double byte character not allowed.

Thank you for the contribution!


Getting - cannot read property 'create' of undefined - React 16

What version of react-dates are you using? What does npm ls react-with-styles say? If you run npm update, does it fix it?

Here are my packages:

And here is what I see when I run npm ls react-with-styles

npm update  doesn't help :/

@ljharb any ideas what's wrong I've tried a few things but without luck

Same issue here!
Im getting:
Uncaught TypeError: Cannot read property 'create' of undefined     at Object.createLTR [as create] (main.js:112557)     at WithStyles.maybeCreateStyles (main.js:9133)     at WithStyles.componentWillMount (main.js:9119)     at callComponentWillMount (main.js:61652)     at mountClassInstance (main.js:61708)     at updateClassComponent (main.js:63164)     at beginWork (main.js:63548)     at performUnitOfWork (main.js:65539)     at slowWorkLoopThatChecksForFailedWork (main.js:65625)     at workLoop (main.js:65593)
``--<EMAIL_ADDRESS>--<EMAIL_ADDRESS>

was able to fix the issue by reverting to react-dates 12.2.4

That's pretty far back; and it shouldn't be needed.
The implication is that ThemedStyleSheet is undefined.
Perhaps you haven't done import 'react-dates/initialize'; at the beginning of your application, which is noted in the readme? @firaskrichi @EstebanBorai does this fix your issue?

It worked for me thanks!

It seems like this has been resolved!

I defined basepath in my environment files and used it for translations like this:
...
useFactory: (http: HttpClient) => new TranslateHttpLoader(http, environment.basepath + 'assets/i18n/', '.json'),
...

I change it to:
const BASE_PATH = environment.basepath;

...
useFactory: (http: HttpClient) => new TranslateHttpLoader(http, BASE_HREF + 'assets/i18n/', '.json'),
...

and is working fine now.

import 'react-dates/initialize';
fixed the solution for me

import 'react-dates/initialize';
fixed the problem for me too.

@firaskrichi maybe you didn't create sql side in your project.

import 'react-dates/initialize'


Xcode's git source control features don't work

Xcode's integrated git source control features don't work with XcodeProj.
Steps to reproduce

Clone XcodeProj (steps 1-3 from README.md)

Git clone the repository git@github.com:tuist/xcodeproj.git.
Generate xcodeproj with swift package generate-xcodeproj.
Open XcodeProj.xcodeproj.

In Xcode: View → Version Editor → Show Version Editor

Result:

Could not load authors for file 'Sources/XcodeProj/Project/XcodeProj.swift'
Error: fatal: no such path 'Sources/XcodeProj/Project/XcodeProj.swift' in HEAD

Alternatively:

Step 1. i-iii from above
In Xcode: make a small change to some file
Source Control → Commit...
Enter Commit Message and hit Cmd-Return

Result:

The working copy “XcodeProj” failed to commit files.
error: pathspec 'Sources/XcodeProj/Project/XcodeProj.swift' did not match any file(s) known to git

Hey @gubikmic, is XcodeProj the only Swift Package project with which you are experiencing this?

@gubikmic I'm not able to reproduce this. I was able to follow your steps with no error. Which version of Xcode & git are you using?

Hey, sorry for the late reply!
It still happens with Xcode Version 11.0 beta (11M336w) and git version 2.21.0 (Apple Git-120)
History and source control features do work with XcodeProj-Carthage.xcodeproj/ though...
It's weird, but since you can't reproduce it, feel free to close it if you want to clean up the open issues.

I also notice that the git even for local source control is not working properly with xcode 11!
I mean, I have a project with 3rd party library using pod, and after I run pod update, and try to commit the changes with the source control, it just looks like committed, but if you try to commit again, all your files from the pod still in there! I notice that I need to do a mall change manually on each file, save to be able to commit... but if you have more than 500 files to do it manually is a nightmare!

I briefly looked in to this, and can't reproduce the issue. Xcode Version 11.4.1 (11E503a)

I'll close it then. Feel free to open the issue if it still happens.

my Xcode 11.3.1 has the same issue.


Vanilla key refactor

Quotes from @duplexsystem

once biome config gets merged we should go back though the vanilla key for each biome and choose one that actually suits the biome (for spawning and structures, etc) and modify any values that need to be changed on the terra side

Referenced PR - https://github.com/PolyhedralDev/Terra/pull/330

also in line with that I think volcanoes should be not badlands because it's weird with strucure mods and mobs that are in badlands

also we should go over each biome to add new particles, ambiance, etc

defb14713a45e5e0dd72d6f422dad141ec8105e3 replaces vanilla keys with an environment which primarily determines biome colors, other behaviour such as mob spawns will still need to be done


feat(logger): add logger facility to validator core

PR summary
This commit adds logging support to the validator. The validator core itself will use a "root" logger, and each validation rule will have its own logger with a name equal to its rule name (e.g. ibm-schema-description). The user can set the logging levels with the
-l/--loglevel command-line options.
Note that this PR only includes the changes to the validator core.  Changes to individual rules to support debug logging will be done as we update each rule.
PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[x] Dependencies have been updated as needed
[x] .secrets.baseline updated as needed?

Checklist for adding a new validation rule:

[ ] Added new validation rule definition (packages/ruleset/src/rules/*.js, index.js)
[ ] If necessary, added new validation rule implementation (packages/ruleset/src/functions/*.js, updated index.js)
[ ] Added new rule to default configuration (packages/ruleset/src/ibm-oas.js)
[ ] Added tests for new rule (packages/ruleset/test/*.test.js)
[ ] Added docs for new rule (docs/ibm-cloud-rules.md)

There's a unit test failure in the travis build.  Looking at that now.  Interestingly, the failure doesn't occur in my local sandbox.  This should be fun :joy:

:tada: This PR is included in version 0.0.2-rc.1 :tada:
The release is available on npm package (@v1-rc dist-tag)
Your semantic-release bot :package::rocket:


Tweak translations.json i18n logic to use the correct algorithm for translation discovery

Basically, we should be using the algorithm described in this doc for translations.json, but are not:
def get_language_translation_data(language: str) -> Dict[str, str]:
    if language == "en":
        return {}
    locale = translation.to_locale(language)
    path = os.path.join(settings.DEPLOY_ROOT, "locale", locale, "translations.json")
    try:
        with open(path, "rb") as reader:
            return orjson.loads(reader.read())
    except FileNotFoundError:
        print(f"Translation for {language} not found at {path}")
        return {}

Specifically, following the de-at (Austrian German) example from the docs, consider what would happen if we added a de-at locale directly alongside the de one, and it only changed 10 strings:

The Django/backend translations would work correctly -- it'd detect de-at as the language, and serve strings from de-at (if present) or de (if present) or the default English (if no translation was available).
However, all of zulip's frontend translations would see that de-at is the Django locale, and serve the de-at translations.json file, that only has 10 strings in it.

We we should be doing is, if the user has selected a country-specific locale like de-at, we read both the de-at and de (there may be a fancy Django function for splitting these, but I think split("_") is correct?) files, and basically overwrite anything in the de structure that's not the empty string in de-at.
This has no effect in Zulip currently because we don't have translations.json files for country-specific variants of languages, but we might have some soon.
I think we can probably manually test our logic by just doing some fake data setup in a development environment -- use manage.py makemessages --lang=de_at or something like it to create an empty data set for de_at, and then hand-add add like 2 highly visible strings, and then do compilemessages.
@hackerkid can you take this one?

@andersk question: Do we plan to move FormatJS away from the translations.json file format?  Such a plan might adjust how good of an idea it is to invest in doing this.
(I think this is basically a blocker for our supporting the two versions of Portuguese that translators have been working on)


fix(workflow): update tag message to include commit ID and PR number

Description
This PR fixes PR Number parsing for tags

[!WARNING]
This relies on having the PR number as part of the commit message e.g. fizz buzz (#123). Changing the format of these commit messages breaks this workflow and requires adaptations to be made to accomodate the new format

Checklist
The following items should be checked before the pull request can be merged.

[x] Code follows existing style.
[x] Unit tests added (if applicable).

What if instead of parsing the values from the commit message, we just include the commit message as it is? Would it be an option?


Add note in ParallaxLayer doc about ignoring position/scale changes after entering the scene

Closes #3987.

Thanks!

Cherry-picked for 3.0.7.


Implemented the single & multi app export

Please make sure the below checklist is followed for Pull Requests.

[ ] Travis tests are green
[X] Tests are added where necessary
[X] Documentation is added/updated where necessary
[X] Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

@Shaolans this is my version of the single & multi app + entities export, can you have a look and compare with yours? if you have the time of course

The logic behind seems to be similar to me 👍. The major difference is about exporting multi apps, I am exporting on just one jdl as you are exporting a jdl on each apps. I don't know which is the better one, I was thinking that if we have subfoldes containing apps, it sould probably correponds to microservices apps used for an entire project, thus keeping all into one jdl but I might be wrong.

Nop, that's a good point! Your logic is better here.

@Shaolans it's way better, thanks for the review.