🎮 Game Request
Go is an ancient two-player strategy board game . Players take turns placing black and white stones on a 19x19 grid board, aiming to control more territory. The objective is to surround and capture opponent stones while simultaneously creating and defending one's own territories. The game is easy to learn, yet possesses immense depth and complexity, making it a favourite among enthusiasts and master players worldwide.
Point down the features
The game has straightforward rules, yet it offers deep and intricate strategic possibilities.Players aim to control more territory by surrounding and capturing their opponent's stones.Unlike many other board games, Go doesn't eliminate players; instead, they compete until the board is full or both players agree to end the game.Go's enduring popularity is attributed to its elegant design, intellectual challenge, and its ability to captivate players of all ages and skill levels.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

/assign

Hey @pxiy-a 👋!
@kunjgit here,
Hope you are doing extremely well 😇
It's confirmed 🥳, GameZone is taking part in hacktoberfest and ready to have another 💥
Ready to have some amazing contributions once again also thank you for you support in GSSoC23 you have took us on top 5 ❤🔥
if you still haven't joined us join us on Discord
See you soon 😊

Hey @pxiy-a 👋!
@kunjgit here,
Hope you are enjoying this hacktober 😀
We are excited to share that we are opening issue from our side where you will be going to add games on our website 🚀
Work on this issue 🔥
and help us building GameZone 💗
if you still haven't joined us join us on Discord
See you soon 😊

Hello @pxiy-a, Time's Uppp!⏰
Sorry for closing your issue!
But it's more than a week since we haven't received anything from your side 😢 .
Come up with new ideas, create a new issue and make sure you finish it within a week! 🔥
All the best! 🚀
Happy Hacking! 💗

Hey @pxiy-a ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


compile in (or for) ubuntu 14.04

Is it possible?
Installed clang-3.9, setted the CC and CXX env, followed hints in https://stackoverflow.com/a/7032021/250970
but I have this (in log, during configuration):
Building CXX object CMakeFiles/cmTC_affc6.dir/src.cxx.o
/usr/bin/clang++-3.9     -pthread -std=c++14 -fno-omit-frame-pointer -fno-exceptions -fno-rtti -ffunction-sections -fdata-sections -Wall -Wextra -Wpointer-arith -Wcast-qual -Wsign-compare -Wno-tautological-compare -Wpointer-arith -Wvla -Wnon-virtual-dtor -Wno-unused-parameter -Wconversion -Wno-sign-conversion -Wc++14-compat-pedantic -Qunused-arguments -Wodr -DHAVE_CXX_FLAG_FLTO_ODR_TYPE_MERGING -flto-odr-type-merging -fPIE   -flto-odr-type-merging -o CMakeFiles/cmTC_affc6.dir/src.cxx.o -c /home/redmine/TDlib/td/build/CMakeFiles/CMakeTmp/src.cxx
clang: error: unknown argument: '-flto-odr-type-merging'
clang: error: unknown argument: '-flto-odr-type-merging'
make[1]: *** [CMakeFiles/cmTC_affc6.dir/src.cxx.o] Error 1

It is definitely possible.
clang: error: unknown argument: '-flto-odr-type-merging' is not an error, it's a failed check for a compiler flag support, so the flag will not be used during the build. The problem is somewhere else.

Thank you. Yes, of course the problem is during compilation, I just tried to guess from configuration step, and I failed. Anyway this is during build:
$ cmake --build .
--
Scanning dependencies of target tdtl
[  1%] Building CXX object tdtl/CMakeFiles/tdtl.dir/td/tl/tl_config.cpp.o
In file included from /home/redmine/TDlib/td/tdtl/td/tl/tl_config.cpp:7:
In file included from /home/redmine/TDlib/td/tdtl/td/tl/tl_config.h:9:
In file included from /home/redmine/TDlib/td/tdtl/td/tl/tl_core.h:11:
In file included from /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/string:52:
In file included from /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/basic_string.h:2815:
In file included from /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/ext/string_conversions.h:43:
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/cstdio:120:11: error: no member named 'gets' in the global namespace
using ::gets;
~~^
1 error generated.
make[2]: *** [tdtl/CMakeFiles/tdtl.dir/td/tl/tl_config.cpp.o] Error 1
make[1]: *** [tdtl/CMakeFiles/tdtl.dir/all] Error 2
make: *** [all] Error 2

I have only gcc 4.8 available for ubuntu 14.04, but I specified to use clang-3.9 and clang++-3.9. I can not understand why includes came from gcc 4.8,  anyway I think this also is not really the problem, or is it?

clang fails to parse libstdc++ headers.
You need to uncomment line
#set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -stdlib=libc++")
in CMakeLists.txt to force it to use libc++ headers.
You may need also to uncomment previous line
#set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -isystem /usr/include/c++/v1")
but it has worked for me without that.

in what exactly cmake is better than autoconf/automake?

You need to find where libc++ headers was installed and specify it in that line
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -isystem <path to libc++ headers>")
For example, they can be in /usr/include/c++/v1.

I hope that the problem was resolved. Please reopen the issue if you need more help with TDLib building.

You need to find where libc++ headers was installed and specify path to them in that line
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -isystem <path to libc++ headers>")
For example, they can be in /usr/include/c++/v1.

Hi, what does 'in that line' main?


TypeError: cli.init is not a function Error

Description
In latest version new project gives this error:
TypeError: cli.init is not a function Error
Version
0.69
Output of npx react-native info
cli.init(root, projectName);
^
TypeError: cli.init is not a function
at run (C:\dev\node-v14.17.5-win-x64\node-v14.17.5-win-x64\node_modules\react-native-cli\index.js:302:7)
at createProject (C:\dev\node-v14.17.5-win-x64\node-v14.17.5-win-x64\node_modules\react-native-cli\index.js:249:3)
at init (C:\dev\node-v14.17.5-win-x64\node-v14.17.5-win-x64\node_modules\react-native-cli\index.js:200:5)
at Object. (C:\dev\node-v14.17.5-win-x64\node-v14.17.5-win-x64\node_modules\react-native-cli\index.js:153:7)
at Module._compile (internal/modules/cjs/loader.js:1072:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
at Module.load (internal/modules/cjs/loader.js:937:32)
at Function.Module._load (internal/modules/cjs/loader.js:778:12)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
at internal/main/run_main_module.js:17:47
Steps to reproduce
npx react-native init AwesomeProject
Snack, code example, screenshot, or link to a repository
No screenshot

yarn add react-native --exact
This should be able to fix your problem, dont know exactly why though

Essentially a duplicate of https://github.com/facebook/react-native/issues/34055
Please find the suggested workaround over there 👍


Add xpo.pw to file hosts + typo fixes

Fork of pomf.se with actual api.
Sorry for the shitty commit merge, tried to edit directly using github's file editor and couldn't edit multiple files in a single branch.

Thanks!


[ui][typeahead] fix nullable, onSelect props

Man, I tried something similar but there were still many errors. Must have messed up something. Thanks for fixing it in the component!!!


Unable to find any valuable Window provider

Versions

Python: 3.7 (64-bit)
OS: Windows 10, Visual Studio 2019
Kivy: 1.11.1
Kivy installation method: Using "Python Environment" dialog in Visual Studio

Description
I cannot run even the simplest program, a critical error occurs: "Unable to find any valuable Window provider". I'm sure I got all dependencies right.
Code and Logs
[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 - Exception: SDL2: Unable to load image
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\__init__.py", line 71, in core_select_lib
    cls = cls()
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\window\window_sdl2.py", line 152, in __init__
    super(WindowSDL, self).__init__()
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\window\__init__.py", line 981, in __init__
    self.create_window()
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\window\window_sdl2.py", line 312, in create_window
    super(WindowSDL, self).create_window()
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\window\__init__.py", line 1258, in create_window
    self.render_context = RenderContext()
  File "kivy\graphics\instructions.pyx", line 783, in kivy.graphics.instructions.RenderContext.__init__
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\image\__init__.py", line 561, in __init__
    self.filename = arg
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\image\__init__.py", line 756, in _set_filename
    mipmap=self._mipmap, nocache=self._nocache)
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\image\__init__.py", line 460, in load
    im = loader(filename, **kwargs)
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\image\__init__.py", line 223, in __init__
    self._data = self.load(filename)
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\image\img_sdl2.py", line 47, in load
    raise Exception('SDL2: Unable to load image')

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

And there is an exception info which has barely anything:

Have you tried researching it first?
If so, please document what you've tried so we know what not to spend time helping with. It's generally bad form to ask for people's time without showing you've invested some yourself in finding your own solution.
Did you try what the error suggested?
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
Did you follow up on the clue?
sdl2 - Exception: SDL2: Unable to load image
There's a ton of stuff out there about this exact problem, including but not limited to:

kivy-not-working-error-unable-to-find-any-valuable-window-provider

kivy-windows-unable-to-find-any-valuable-window-provider-at-all

Unable to find any valuable Window provider

Unable to find any valuable Window provider at all! (with kivy-daily build)

SDL2: Unable to load image [solved]

This usually seems to boil down to an issue related to:

Missing or otherwise incorrectly installed dependencies. Check the Windows installation guide for details on prerequisites and how to install them properly.

Missing or incorrect entries in the PATH variable. Likewise, there's a lot of info about updating your PATH, so start searching for sites discussing both PATH and your issue, then try what's suggested.

Start with this and show us what you've tried if you can't get it to work.
P.S., Some different but somewhat related issue I experienced when I first installed Kivy on a Windows 10 machine were OpenGL detection problems and the notorious "black screen". There's also lots about these out there with various solutions to try, in case you get there. What worked for me was a combined update to the Kivy config file and setting a Windows environment variable to use ANGLE instead of GLEW. This only happened in Windows 10, not in my Windows 7 or in Linux Mint PCs. I created a script I include with apps in case they run on a Windows 10 machine in order to prevent the issue outright. I should probably add logging to report this activity, but I wrote this last year and haven't revisited it until now. I'll add that to my backlog.
r"""
Fix for OpenGL detection and the "black screen" issues on Windows 10.

Check environment and Kivy configuration and make corrections as needed
based on feedback in Kivy Issue #5248:

    https://github.com/kivy/kivy/issues/5248#issuecomment-370885342
"""

import platform
import subprocess
from kivy import Config

def windows_check():
    r"""
    Check if OS is Windows 10.

    If so, set the KIVY_GL_BACKEND environment variable if it's not already
    set (to use angle_sdl2 instead of glew) to resolve issues detecting
    the OpenGL version.

    Next, set .kivy\config.ini > graphics > multisamples to '0' (for this
    instance only) in order to prevent "black screen" issue.
    """
    # If Windows 10:
    if platform.system() == 'Windows' and platform.release() == '10':
        # Check Windows 10 for appropriate environment variable
        proc = subprocess.Popen(
            'if defined KIVY_GL_BACKEND (echo True) else (echo False)',
            shell=True,
            stdout=subprocess.PIPE,
            stderr=subprocess.PIPE
        )
        out, err = proc.communicate()

        # If environment variable KIVY_GL_BACKEND does NOT exist, then
        if out is False:
            # Create environment variable to set KIVY_GL_BACKEND to angle
            subprocess.call('setx KIVY_GL_BACKEND angle_sdl2', shell=True)
        # Set .kivy\config.ini > graphics > multisamples to '0'
        Config.set('graphics', 'multisamples', 0)

if __name__ == '__main__':
    windows_check()

I don't understand this sentence:
Please enable debug logging (e.g. add -d if running from the command line, or change the log level in the config)
I am debugging in Visual Studio and where should I add this -d?

Have you tried researching it first?
If so, please document what you've tried so we know what not to spend time helping with. It's generally bad form to ask for people's time without showing you've invested some yourself in finding your own solution.
Did you try what the error suggested?
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
Did you follow up on the clue?
sdl2 - Exception: SDL2: Unable to load image
There's a ton of stuff out there about this exact problem, including but not limited to:
* [kivy-not-working-error-unable-to-find-any-valuable-window-provider](https://stackoverflow.com/questions/44219563/kivy-not-working-error-unable-to-find-any-valuable-window-provider#44220712)

* [kivy-windows-unable-to-find-any-valuable-window-provider-at-all](https://stackoverflow.com/questions/40769386/kivy-windows-unable-to-find-any-valuable-window-provider-at-all)

* [Unable to find any valuable Window provider](https://github.com/kivy/kivy/issues/5348)

* [Unable to find any valuable Window provider at all! (with kivy-daily build)](https://github.com/kivy/kivy/issues/3002)

* [SDL2: Unable to load image [solved]](https://github.com/kivy/kivy/issues/4482)

This usually seems to boil down to an issue related to:
1. Missing or otherwise incorrectly installed [dependencies](https://kivy.org/doc/stable/installation/installation-windows.html?highlight=dependencies#kivy-dependencies). Check the [Windows installation guide](https://kivy.org/doc/stable/installation/installation-windows.html?highlight=dependencies) for details on prerequisites and how to install them properly.

2. Missing or incorrect entries in the PATH variable. Likewise, there's a lot of info about updating your PATH, so start searching for sites discussing both PATH and your issue, then try what's suggested.

Start with this and show us what you've tried if you can't get it to work.
P.S., Some different but somewhat related issue I experienced when I first installed Kivy on a Windows 10 machine were OpenGL detection problems and the notorious "black screen". There's also lots about these out there with various solutions to try, in case you get there. What worked for me was a combined update to the Kivy config file and setting a Windows environment variable to use ANGLE instead of GLEW. This only happened in Windows 10, not in my Windows 7 or in Linux Mint PCs. I created a script I include with apps in case they run on a Windows 10 machine in order to prevent the issue outright. I should probably add logging to report this activity, but I wrote this last year and haven't revisited it until now. I'll add that to my backlog.
r"""
Fix for OpenGL detection and the "black screen" issues on Windows 10.

Check environment and Kivy configuration and make corrections as needed
based on feedback in Kivy Issue #5248:

    https://github.com/kivy/kivy/issues/5248#issuecomment-370885342
"""

import platform
import subprocess
from kivy import Config

def windows_check():
    r"""
    Check if OS is Windows 10.

    If so, set the KIVY_GL_BACKEND environment variable if it's not already
    set (to use angle_sdl2 instead of glew) to resolve issues detecting
    the OpenGL version.

    Next, set .kivy\config.ini > graphics > multisamples to '0' (for this
    instance only) in order to prevent "black screen" issue.
    """
    # If Windows 10:
    if platform.system() == 'Windows' and platform.release() == '10':
        # Check Windows 10 for appropriate environment variable
        proc = subprocess.Popen(
            'if defined KIVY_GL_BACKEND (echo True) else (echo False)',
            shell=True,
            stdout=subprocess.PIPE,
            stderr=subprocess.PIPE
        )
        out, err = proc.communicate()

        # If environment variable KIVY_GL_BACKEND does NOT exist, then
        if out is False:
            # Create environment variable to set KIVY_GL_BACKEND to angle
            subprocess.call('setx KIVY_GL_BACKEND angle_sdl2', shell=True)
        # Set .kivy\config.ini > graphics > multisamples to '0'
        Config.set('graphics', 'multisamples', 0)

if __name__ == '__main__':
    windows_check()

I just learned that v1.11.0 introduced another way to do this without directly adding the environment variable yourself:
`
Changing configuration with environment variables
Since 1.11.0, it is now possible to change the configuration using
environment variables. They take precedence on the loaded config.ini.
The format is::
KCFG_<section>_<key> = <value>

`
I'm going to have to try this out.

If it's not clear where/how/when to enter the -d, and research doesn't yield any results, then use the second option they provided:

(... or change the log level in the config) and re-run your app to identify potential causes

The default location is specified in the Kivy docs, as well as how to update the file for various reasons.
The logging aside, there's a lot of info out there (like the links I provided show) to give you places to start.

https://docs.python.org/3/using/cmdline.html#cmdoption-d. Also, please provide the full uncut log output. You cut the most important part at the beginning :)

@matham Full log is here:
[INFO   ] [Logger      ] Record log in C:\Users\svetz\.kivy\logs\kivy_19-11-27_0.txt
[INFO   ] [deps        ] Successfully imported "kivy_deps.gstreamer" 0.1.17
[INFO   ] [deps        ] Successfully imported "kivy_deps.angle" 0.1.9
[INFO   ] [deps        ] Successfully imported "kivy_deps.glew" 0.1.12
[INFO   ] [deps        ] Successfully imported "kivy_deps.sdl2" 0.1.22
[INFO   ] [Kivy        ] v1.11.1
[INFO   ] [Kivy        ] Installed at "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\__init__.py"
[INFO   ] [Python      ] v3.7.3 (v3.7.3:ef4ec6ed12, Mar 25 2019, 22:22:05) [MSC v.1916 64 bit (AMD64)]
[INFO   ] [Python      ] Interpreter at "C:\Users\svetz\AppData\Local\Programs\Python\Python37\python.exe"
[INFO   ] [Factory     ] 184 symbols loaded
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_gif (img_pil, img_ffpyplayer ignored)
[INFO   ] [Window      ] Provider: sdl2
[INFO   ] [GL          ] Using the "OpenGL" graphics system
[INFO   ] [GL          ] GLEW initialization succeeded
[INFO   ] [GL          ] Backend used <glew>
[INFO   ] [GL          ] OpenGL version <b'4.5.0 - Build <IP_ADDRESS>72'>
[INFO   ] [GL          ] OpenGL vendor <b'Intel'>
[INFO   ] [GL          ] OpenGL renderer <b'Intel(R) UHD Graphics 620'>
[INFO   ] [GL          ] OpenGL parsed version: 4, 5
[INFO   ] [GL          ] Shading version <b'4.50 - Build <IP_ADDRESS>72'>
[INFO   ] [GL          ] Texture max size <16384>
[INFO   ] [GL          ] Texture max units <32>
[WARNING] [Image       ] Unable to load image <C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\data\glsl\default.png>
[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 - Exception: SDL2: Unable to load image
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\__init__.py", line 71, in core_select_lib
    cls = cls()
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\window\window_sdl2.py", line 152, in __init__
    super(WindowSDL, self).__init__()
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\window\__init__.py", line 981, in __init__
    self.create_window()
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\window\window_sdl2.py", line 312, in create_window
    super(WindowSDL, self).create_window()
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\window\__init__.py", line 1258, in create_window
    self.render_context = RenderContext()
  File "kivy\graphics\instructions.pyx", line 783, in kivy.graphics.instructions.RenderContext.__init__
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\image\__init__.py", line 561, in __init__
    self.filename = arg
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\image\__init__.py", line 756, in _set_filename
    mipmap=self._mipmap, nocache=self._nocache)
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\image\__init__.py", line 460, in load
    im = loader(filename, **kwargs)
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\image\__init__.py", line 223, in __init__
    self._data = self.load(filename)
  File "C:\Users\svetz\AppData\Local\Programs\Python\Python37\lib\site-packages\kivy\core\image\img_sdl2.py", line 47, in load
    raise Exception('SDL2: Unable to load image')

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

I just learned that v1.11.0 introduced another way to do this without directly adding the environment variable yourself:
Changing configuration with environment variables
-------------------------------------------------

Since 1.11.0, it is now possible to change the configuration using
environment variables. They take precedence on the loaded config.ini.
The format is::

    KCFG_<section>_<key> = <value>

I'm going to have to try this out.

Where is this config.ini? And what is those <section>, <key>, <value>??

I guess that log doesn't illuminate the issue.
I'd guess there's something wrong with your PATH, probably it has something on it with a bad dll. Try locally clearing your path in the command line and leaving only python on it and see if it fixes it.

I just learned that v1.11.0 introduced another way to do this without directly adding the environment variable yourself:
Changing configuration with environment variables
-------------------------------------------------

Since 1.11.0, it is now possible to change the configuration using
environment variables. They take precedence on the loaded config.ini.
The format is::

    KCFG_<section>_<key> = <value>

I'm going to have to try this out.

Where is this config.ini? And what is those <section>, <key>, <value>??

I've already provided multiple resources and suggestions that would illuminate this for you. I suggest you actually review them. It seems that so far you're still not putting in the effort to solve the dilemma and expect the answer to be given to you. The Kivy team has put in a lot of effort to document their product, and many people have contributed through GitHub, StackOverflow, etc. to build a knowledge-base of support. Respect these efforts and everyone's time by trying first (and when coming for help, explaining how/what you've tried and the results).
I had to jump through these same hoops when I first started with Kivy. While I'm not expert by any means, in my opinion, if doing this kind of research is too hard or unpleasant, then perhaps working with a GUI framework, such as Kivy, isn't where you should focus your efforts at this time.

I guess that log doesn't illuminate the issue.
I'd guess there's something wrong with your PATH, probably it has something on it with a bad dll. Try locally clearing your path in the command line and leaving only python on it and see if it fixes it.

I cleared python-related paths to only Python\Python37 and Python\Python37\Scripts, but it's still not working. Am I on the right track?

I also stumbled upon this very issue. I made a simple Kivy app and packaged it with PyInstaller. The Python program executes fine if I run with python3 myprogram.py. However, when I packaged it with pysinstaller myprogram.py --onefile and I try to open the executable, I'm faced with this error log:
PS C:\Users\rafae\OneDrive\Documentos\corretor-monetario-master\dist> .\coletor_correcao.exe
[INFO   ] [Logger      ] Record log in C:\Users\rafae\.kivy\logs\kivy_20-02-13_19.txt
[INFO   ] [Kivy        ] v1.11.1
[INFO   ] [Kivy        ] Installed at "C:\Users\rafae\AppData\Local\Temp\_MEI92282\kivy\__init__.pyc"
[INFO   ] [Python      ] v3.7.6 (tags/v3.7.6:43364a7ae0, Dec 19 2019, 00:42:30) [MSC v.1916 64 bit (AMD64)]
[INFO   ] [Python      ] Interpreter at "C:\Users\rafae\OneDrive\Documentos\corretor-monetario-master\dist\coletor_correcao.exe"
[INFO   ] [Factory     ] 184 symbols loaded
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_pil, img_gif (img_ffpyplayer ignored)
[INFO   ] [Text        ] Provider: sdl2
[INFO   ] [Window      ] Provider: sdl2
[INFO   ] [GL          ] Using the "OpenGL" graphics system
[INFO   ] [GL          ] GLEW initialization succeeded
[INFO   ] [GL          ] Backend used <glew>
[INFO   ] [GL          ] OpenGL version <b'4.6.0 NVIDIA 436.48'>
[INFO   ] [GL          ] OpenGL vendor <b'NVIDIA Corporation'>
[INFO   ] [GL          ] OpenGL renderer <b'GeForce GTX 1070/PCIe/SSE2'>
[INFO   ] [GL          ] OpenGL parsed version: 4, 6
[INFO   ] [GL          ] Shading version <b'4.60 NVIDIA'>
[INFO   ] [GL          ] Texture max size <32768>
[INFO   ] [GL          ] Texture max units <32>
[WARNING] [Image       ] Unable to load image <C:\Users\rafae\AppData\Local\Temp\_MEI92282\kivy_install\data\glsl\default.png>
[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 - Exception: SDL2: Unable to load image
  File "site-packages\kivy\core\__init__.py", line 71, in core_select_lib
  File "site-packages\kivy\core\window\window_sdl2.py", line 152, in __init__
  File "site-packages\kivy\core\window\__init__.py", line 981, in __init__
  File "site-packages\kivy\core\window\window_sdl2.py", line 312, in create_window
  File "site-packages\kivy\core\window\__init__.py", line 1258, in create_window
  File "kivy\graphics\instructions.pyx", line 783, in kivy.graphics.instructions.RenderContext.__init__
  File "site-packages\kivy\core\image\__init__.py", line 561, in __init__
  File "site-packages\kivy\core\image\__init__.py", line 756, in _set_filename
  File "site-packages\kivy\core\image\__init__.py", line 460, in load
  File "site-packages\kivy\core\image\__init__.py", line 223, in __init__
  File "site-packages\kivy\core\image\img_sdl2.py", line 47, in load

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

 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 - Exception: SDL2: Unable to load image
  File "site-packages\kivy\core\__init__.py", line 71, in core_select_lib
  File "site-packages\kivy\core\window\window_sdl2.py", line 152, in __init__
  File "site-packages\kivy\core\window\__init__.py", line 981, in __init__
  File "site-packages\kivy\core\window\window_sdl2.py", line 312, in create_window
  File "site-packages\kivy\core\window\__init__.py", line 1258, in create_window
  File "kivy\graphics\instructions.pyx", line 783, in kivy.graphics.instructions.RenderContext.__init__
  File "site-packages\kivy\core\image\__init__.py", line 561, in __init__
  File "site-packages\kivy\core\image\__init__.py", line 756, in _set_filename
  File "site-packages\kivy\core\image\__init__.py", line 460, in load
  File "site-packages\kivy\core\image\__init__.py", line 223, in __init__
  File "site-packages\kivy\core\image\img_sdl2.py", line 47, in load

[CRITICAL] [App         ] Unable to get a Window, abort.
PS C:\Users\rafae\OneDrive\Documentos\corretor-monetario-master\dist>

I'm on Windows 10, using Python 3.7.6


ConnectPaymentDetails does not support visible prop

I see in your examples, and even in the documentation, you pass a visible prop, but the component doesn't accept it. Even if I try to wrap a piece of state around the component, toggle visibility using some onClick handler, then set the state to false using the onClose handler provided by the ConnectPaymentDetails component, the payment details popup doesn't disappear. ie. I don't see any way to close the component once its open.

We've since fixed this - the visible prop was removed from our beta a while ago, it is no longer needed! Simply stop rendering the component with a react conditional, like so:
{{visible ? <ConnectPaymentDetails ... /> : null }}

Or pass in a null payment.


Imagery selection has out of sync hover selected states

Description
Video:
https://github.com/facebook/Rapid/assets/111561/d2613fdb-e347-435f-9399-036841b45a6d
The blue highlighting is out sync where something has a blue background but is not selected:

Screenshots
No response
Version
canary
What browser are you seeing the problem on? What version are you running?
No response
The OS you're using
No response
Steps to reproduce
See video
The browser URL at the time you encountered the bug
https://rapideditor.org/canary#map=17.85/52.70497/13.88678&background=EsriWorldImagery&datasets=fbRoads,msBuildings&disable_features=boundaries
The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)
No response

I think what you might be seeing with the hover states is #1233 ?
This is a behavior we inherited from the iD code, and it is confusing to people.
The blue highlights will both show the current imagery and also the previous imagery - Users can toggle between these two sources by pressing the ⌘B shortcut .
I will check to see how Wayback fits in with this - I haven't tested it, so there might be a bug..

I thought about this more and decided to just remove the .switch class for the previously used imagery, since this looked weird and was causing users to think that something was broken on multiple occasions.
Now the 'last used' imagery just looks like any other inactive imagery source in the list.
Users can still use ⌘B shortcut to toggle between current and last used, which we do explain in the tooltip and on the keyboard shortcuts screen.


About Us Section Color Change

Description

Relevant GitHub Issues that will be fixed are #148
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] This change requires a documentation update
[ ] Chore (anything else)

How Has This Been Tested?

[X] Responsiveness on various devices
Desktop Browser

[ ] Apple Safari
[ ] Brave
[X] Google Chrome
[ ] Microsoft Edge
[ ]Mozilla FireFox

Mobile Browser

[X] Google Chrome
[ ] Mozilla FireFox
[ ] Microsoft Edge
[ ] Apple Safari

Other Tests:

Checklist

[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

PR Closure

Use Squash And Merge to Close Pull Request
Delete any branch after merging

https://github.com/theDS3/Website/blob/e066ed1c47edaf9f7291e59f3faae79e3704f8b4/src/components/AboutUs.tsx#L22-L26
https://github.com/theDS3/Website/blob/e066ed1c47edaf9f7291e59f3faae79e3704f8b4/src/components/AboutUs.tsx#L39-L42
In the above p tags there are to font size classes being used at the same time: text-lg, text-3xl


public var success:SuccessType? - why optional?

why is the success-Type be an optional?
let request = API.GetXY.Request(...)
currentRequest = apiClient.makeRequest(request, behaviours: [], completionQueue: DispatchQueue.main) { result in
    switch result.result {
    case let .success(value):
        let xy = value.success?.data ?? []
        completion(.success(xy))
    case let .failure(error):
        if !error.isCancelled {
            completion(.failure(error))
        }
    }
}

I don't understand when value.success can be nil - I would expect this to always be set and never be nil, so an optional can be avoided IMHO. Am I missing something?

Having a 200 range response in swagger is optional. You can edit the template if your api always has a success response though. This also lets you build a convenience function that fails on non success

Thinking about this, an improvement could be to see if all the possible responses in a spec have 200 range responses and then making this non optional in the protocol

Sorry, I actually missunderstood, the reason this is optional is that the endpoint may fail so the success property is optional. The initial result is if the endpoint returned anything at all, then you check why the response actually was. This can be abstracted in a wrapper function to just return a result with a generic failure and the success response. This will mean you won’t have typed errors though.
This issue tracks adding such a simplified handler https://github.com/yonaskolb/SwagGen/issues/91

Thanks for the quick response!
Am I getting you right that it's nil if the request is successful, the response has a successful status code but the content is not in a format the API expects? Or what has to happen that the success-property is nil?
And: do you have plans to change this? Is that what #91 is for?


image: introduce dockerclient and registry client

/lgtm
pending green https://github.com/openshift/origin/pull/23019
/hold
holding for proof

/lgtm

/hold cancel

@deads2k weird... i pruned the vendor/ dir yet still getting a diff there for distribution....

With a clean glide cache, I get the same result.  I've had trouble with verify-deps in the past.  We'll merge this.


chore: appengine sample to have GCLOUD_CONFIG explanation

Cont of https://github.com/GoogleCloudPlatform/java-docs-samples/pull/6420/files#r756243127. Using https://cloud.google.com/appengine/docs/standard/java11/quickstart, GCLOUD_CONFIG in projectID and version worked:
~/java-docs-samples/appengine-java11/springboot-helloworld $ gcloud app deploy
Services to deploy:

descriptor:                  [/Users/suztomo/java-docs-samples/appengine-java11/springboot-helloworld/pom.xml]
source:                      [/Users/suztomo/java-docs-samples/appengine-java11/springboot-helloworld]
target project:              [suztomo-cloud-function-test]
target service:              [default]
target version:              [20211201t150721]
target url:                  [https://suztomo-..(omit)..appspot.com]
target service account:      [App Engine default service account]

Do you want to continue (Y/n)?  Y

Fixes #issue

It's a good idea to open an issue first for discussion.

[x] I have followed Sample Format Guide
[ ] pom.xml parent set to latest shared-configuration
[x] Appropriate changes to README are included in PR
[ ] API's need to be enabled to test (tell us)
[ ] Environment Variables need to be set (ask us to set them)
[x] Tests pass:   mvn clean verify required
[x] Lint  passes: mvn -P lint checkstyle:check required
[x] Static Analysis:  mvn -P lint clean compile pmd:cpd-check spotbugs:check advisory only
[x] Please merge this PR for me once it is approved.

New branch name...


Run additional analysis

Runs axel-op/dart-package-analyzer@v3 to determine which points would be given to each package on pub.dev.
Also adds package discovery to the workflow so that only packages requiring build_runner will need to be added manually.

@baywet if you want to review this, let me know. Otherwise I'll merge this soon as nothing of this is really related to implementing kiota for dart; this is mainly devops stuff.


System completion nitpick

This was inspired from the conversation over at #1635

Prefer the brew/bash provided wrapper (/usr/local/etc/profile.d/bash-completion.sh) when loading bash-completion@2
Load XCode provided git completion if it exists
Remove completions that should be utilizing system and notify the user through doctor

Closes #1635

@nwinkler Okay, I've cleaned this branch up after working through git.completion, but I'm left with a question. The new logging means that the system.completion will throw a command-not-found message for brew, and I'm not sure we want to do that all the time, e.g. a linux user shouldn't care about that.
The cheap fix is just using type directly for this one case, or maybe it justifies yet another variant in helpers (_command_exists_no_log?). What do you think?

Do you know anything about this "contribution" paths?
https://github.com/Bash-it/bash-it/blob/master/completion/available/brew.completion.bash#L5-L7

Yes, it looks like these paths are there for historical reasons. One thing I've learned while maintaining this project is that if we take something like that away, there's a good chance that someone is still using that location and will complain...
So unless having these additional paths really hurts, I'd vote for leaving them in there - maybe adding a comment to note that they are there for historical purposes.

@nwinkler take another look

@nwinkler okay have another look. I included the brew cleanup because this PR got me looking at it, but I can split it out to another PR if you want.

Thanks for including the brew completion here as well - makes sense!

@nwinkler Haha no problem. To that end, I'll be sure to mark a PR as "blocking" if I ever have devs waiting on changes in the future. Sorry about that one time and thanks for always being flexible!


Low Latency HLS support

Hello, does it support Low Latency HLS?
https://en.wikipedia.org/wiki/HTTP_Live_Streaming#Low_Latency_HLS

Hi @evgenibers did you try https://github.com/Edward-Wu/srt-live-server ?
I really like nginx-rtmp-module but there is no way to get any new low latency solution I suppose :-(

@evgenibers I used OvenMediaEngine instead now

@evgenibers I used OvenMediaEngine instead now

can share how to with avideo?

@smartweekend  I wrote an article
https://habr.com/ru/post/532424/
eng version https://www.airensoft.com/post/review-ome-russia
I hope this helps. But if you don't plan to use live broadcasting  low latency engine is not important. (You will always lost in quality )

We recently open-sourced our live streaming framework - https://github.com/kaltura/media-framework/.
It uses a modified version of nginx-rtmp-module for RTMP ingestion, and it has support for LLHLS.
It also supports persistence in cloud storage (s3), DRM, subtitles etc.

We recently open-sourced our live streaming framework - https://github.com/kaltura/media-framework/. It uses a modified version of nginx-rtmp-module for RTMP ingestion, and it has support for LLHLS. It also supports persistence in cloud storage (s3), DRM, subtitles etc.

This seems like it can be a good alternative. @erankor  BTW all your sample topologies aren't visible on your page Github page.

@tolew1, the diagrams work ok for me -

Maybe you're using GitHub mobile app? I don't see the diagrams on the GitHub iPhone app...

@erankor No I always use my desktop computer. It's showing now. Before it had red boxes that said Unable to render Rich display. Apparently, it seems to happen to others. https://github.com/community/community/discussions/41020
But it's working now all of a sudden. Thanks for the response.


nothing to distinguish generators from functions

Without writing "generator" in the text somewhere it's impossible to reliably determine whether a doclet (in the --explain data or generated output) is a function or generator.
There is nothing to distinguish this function:
/**
 * a global function
 */
function globalFunction () {}

from this generator:
/**
 * a global generator
 */
function * globalGenerator () {}

:+1:

Fixed on master. The fix will be included in JSDoc 3.5.0.


1k hosts

https://mesosphere.atlassian.net/browse/DCOS-12366

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-1795. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


Facility Spoke linking option is not visible in create facility form

Describe the bug

[ ] In the create facility form, only the spoke facility field heading is visible.
[ ] We are only able to link a spoke to a facility from the update facility form

To Reproduce
Steps to reproduce the behavior:

Go to https://care.ohc.network/facility/create
See error

Expected behavior

[ ] we should be able to link a spoke to a new facility from the create facility page itself

Screenshots

@nihal467 Mind assigning this to me? Thanks!

I feel "Spoke Facilities" section can be a follow up page that can be shown after the facility is created. Similar to how bed count / doctor count / etc. is asked as follow up after facility creation.

I feel "Spoke Facilities" section can be a follow up page that can be shown after the facility is created. Similar to how bed count / doctor count / etc. is asked as follow up after facility creation.

Hmm, should we reuse the existing component or create a different one to follow the format of bed/staff capacity?

@rithviknishad @Jacobjeevan spoke assignment is not a common function. Its a rare action.
Do we even need it while creating?

We need it in Create facility form.
A user will rarely visit the update facility form. This information will just remain absent, unless we place it in the creation form.

@aparnacoronasafe add it as another action in the facility page buttons dropdown?

It's added in the create facility form now which is good.
The list of spokes is also available on the facility dashboard.
However on spoke dashboard, there is no indication of the hubs such a spoke to linked with. This needs to be added.


Fix broken link for guide to Jira and webhook integration

Hello Adnan! Firstly, thank you very much for this amazing project!
Whilst browsing through the various documentations and guides, I noticed that the ones for Jira and webhook integration had changed the resource locations. Thus, the PR to update those. There were two instances of this specific issue and i've fixed both of them.
Other than this, all the external links to other guides seem to be working well.
Signed-off-by: Prince Mendiratta<EMAIL_ADDRESS>

Thank you very much :-)


Making basic auth work with webrat and mechanize

Hi,
I have made some changes to webrat to make the basic_auth method work with the mechanize adapter.
I have also added the possibility to configure follow redirects for mechanize.
It would be awesome if you want to merge my changes and make it public.
//Best regard Andreas Knifh

Hey Andreas, I made these changes to webrat 0.7.2 and it works for basic_auth with mechanize 1.0.0, but the ability to follow redirects seems to be broken. Please let me know if I can assist with troubleshooting. I'm sort of new to all of this.

In my env.rb I have added the following. So if you can add the corresponding config with follow_redirects = true it should work
Webrat.configure do |config|
config.mode = :mechanize
config.follow_redirects = true
end

That worked great. Thanks a bunch!


Fix stack overflows

This is my attempt at fixing the infamous stack overflows (#354). They were crashing the Rust Language Server in my project and I don't like dirty workarounds. 😄
The first commit fixes the legitimate case where an import references a value (function, const, static, etc.) that has the same name as the first component in the import's path. For example:
use foo::foo;

mod foo {
    pub fn foo() {}
}

Racer will now report both the module and the function where applicable.
The second commit fixes unresolvable imports that refer to themselves, as mentioned in https://github.com/phildawes/racer/issues/354#issuecomment-134847072. For example:
use foo::foo;
// no `foo` defined anywhere

To fix this, we now keep track of the imports that are being resolved, and we ignore imports that are being resolved recursively. This has the effect that none of the names in such imports will be reported.
The third commit rolls back a workaround for glob imports causing stack overflows when they were processed recursively. I didn't figure out what caused the condition in the first place, but I suspect that the first two commits would fix it. It also removes the special case of a glob import referencing itself, because the second commit will take care of unbounded recursion.

cc @jwilm (for #479)

Oh, wow! Thank you very much for putting this together. This ought to make a lot of people (including myself) very happy.
Your implementation looks like exactly the right approach. Going to test this and follow up shortly.

This works really well. Going to merge and make a release immediately. This is fantastic work. Thanks again for putting this together!
:star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2: :star2:


Is it possible to change the amount of conflict allowed for Exclusive Feature Bundling?

The original LightGBM paper mentions using an approximation of mutual exclusivity in Exclusive Feature Bundling (EFB), like this:

we notice that there are usually quite a few features, although not 100% mutually exclusive, also rarely
take nonzero values simultaneously. If our algorithm can allow a small fraction of conflicts, we can
get an even smaller number of feature bundles and further improve the computational efficiency.

This made me think that the amount of allowed conflict could be something that is tuned, since there seems to be a trade-off: higher allowed amount of conflict should mean faster training, but possibly at the expense of some information loss.
I don't see this documented as a parameter in https://lightgbm.readthedocs.io/en/latest/Parameters.html, and it looks like it is hard-coded to #data / 10000 in https://github.com/microsoft/LightGBM/blob/0655d67cc1ee28d536a773a6c5d978d38a0e56c1/src/io/dataset.cpp#L106-L108.

Is it possible to change this level of conflict directly?
Should LightGBM support configuring this via parameters? Or is there something I'm missing that makes it a bad idea to expose this parameter?

For #1 answer is

Currently we don't provide $K$ or $\gamma$ as a hyper-parameter. Instead, $K$ is hard-coded as num_data / 10000 in the code.
https://github.com/microsoft/LightGBM/issues/4114#issuecomment-813201652

@jameslamb Would you like to turn this into a feature request?

Only if you or @shiyu1994 think it's a good idea to try tuning this parameter. I'm hesitant to add more parameters to LightGBM unless there is a compelling reason to do so.

Now we have MultiValBin class which allows a feature group to contain multiple values in the same row. With too many conflicts in a group, a better solution is to transform it into a multi-value group. A sparse multi-value group also exploits sparsity and accelerates training.
So, although we hard code the maximum allowed conflicts, those features with no proper single-value feature group can end up in the sparse multi-value feature group.
Overall, I think currently we don't need to expose this parameter.

Thanks as always for the detailed explanation @shiyu1994 ! I'll close this then and I don't think we need to add it as a feature request.

Just for the history: max_conflict_rate param was removed in #2699.
https://github.com/microsoft/LightGBM/commit/509c2e50c25eded99fc0997afe25ebee1b33285d#diff-229636b798e2650929dad136deec0c435e57b33b41c48d08eb32b2661e2c5e84L537-L542


Correctly deserialise embedded documents

Fixes the to_dict of EmbeddedDocument which was not to_dicting on it's embeded documents.
Without this it is not possible to support documents like below (which is taken from the HAL spec):
   {
     "_links": {
       "self": { "href": "/orders" },
       "next": { "href": "/orders?page=2" },
       "find": { "href": "/orders{?id}", "templated": true }
     },
     "_embedded": {
       "orders": [{
           "_links": {
             "self": { "href": "/orders/123" },
             "basket": { "href": "/baskets/98712" },
             "customer": { "href": "/customers/7809" }
           },
           "total": 30.00,
           "currency": "USD",
           "status": "shipped",
         },{
           "_links": {
             "self": { "href": "/orders/124" },
             "basket": { "href": "/baskets/97213" },
             "customer": { "href": "/customers/12369" }
           },
           "total": 20.00,
           "currency": "USD",
           "status": "processing"
       }]
     },
     "currentlyProcessing": 14,
     "shippedToday": 20
   }

Thank you very much for this @jakul - will get a release out for you 🔜

https://pypi.python.org/pypi/Flask-HAL/1.0.4 👍

Super speedy! 🚗 💨


Add helm charts for operator installation and CSI Driver creation

Describe the feature you'd like to have
Add helm charts for operator installation and CSI Driver creation
Who is the end user and what is the use case where this feature will be valuable?
Another way of installation of the operator

Looking forward to the helm chart that includes the Ceph CSI CRDs and operator, then Rook can add a helm dependency.


Replacing a node in freezer

I have a need to replace a node entirely, not merge with the existing node. I read through the issues and I see you have commented about it here, I modified the source to get this replace added to mixin.js where I publish a new event and listen to that on frozen.js with the same event name I published on mixin.js.
I got this to work. What I wanted to know is do you plan on implementing this feature yourself or is it already implemented and I just did not search enough? Will be happy to send a PR if it is not implemented already.
I don't want to go about doing node.remove for all the keys to be removed.

Hi @rrag
Yes, that method would be really handy but also dangerous. The responsibility of replacing a part of the store should belong to the parent of the store, and a component that refreshes its store should be the exception.
Keep in mind that leaf nodes won't be able to replace themsevels anyway.
Said so, I think that the replace method would be useful. I am not sure about the mothod's name, replace has sense if it is the parent who replace some of its children, but a node can't replace itself, so maybe a name like reset would be more accurate.
If you send a PR with the reset I will review and merge it.
Thanks for your feedback

Cool, I will send a PR
The problem is in react when I send a few props to a component, it does not have access to the parent, and if I need to replace/reset that node I need this feature. I was using set and did not understand that it is actually merging and not just doing a overwrite.
so I understand this right,
var store = new Freezer({
 	foo: { index: 0, bar: 'bar' }
});

var newFoo = store.get().foo.set({ index: 1, foobar: 'foobar' });
console.log(newFoo); // This prints { index: 1, foobar: 'foobar', bar:'bar' }

newFoo = store.get().foo.reset({ index: 2, lorem: 'ipsum' }); // I am adding this reset method to the mixin
console.log(newFoo); // This prints { index: 2, lorem: 'ipsum' }

Kindly confirm.
Also on a related note, I think this is better named merge, do you agree?

Yes you got it! Reset would delete the properties that are not passed as arguments.
And I agree that merge would be a better name for that method in frozen file. But be careful on update, you should also update https://github.com/arqex/freezer/blob/master/src/mixins.js#L36 to notify merge.

Thanks, will do

Added in https://github.com/arqex/freezer/commit/7ff624a4a12f4e2534e12d1af0c5873fdcc9ea51


Issue and pull-request templates

Github allows to define templates for issues and pull-requests. In this PR, the files are moved into the .github directory.

@bp-kelley : I think these make sense. Any comments/objections?

I'll have a long flight back to Boston on Sunday, I'll be able to do a proper review at that point, however I have no complaints on my quick review.

Brian Kelley

On Jun 22, 2017, at 8:33 PM, Greg Landrum<EMAIL_ADDRESS>wrote:
@bp-kelley : I think these make sense. Any comments/objections?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Perhaps we should have a code snippet at the top to indicate how to get the rdkit version?

Otherwise, I'm fine with this.

Good idea about the code snippet. I've updated the issue template. (and fixed a typo).

Thanks Peter!


Fix README.md headings

The headings aren't showing up correctly due to missing spaces.

@steven-joruk Thanks


Fork, Commit, Merge - Easy Issue 1 (HTML)

Fork, Commit, Merge - Easy Issue 1 (HTML)
Add a Simple H1-tag
Note: You don't have ask permission to start solving the issue or get assigned, since these issues are supposed to be always open for new contributors. The actions-user bot will reset the file back to previous state for the next contributor after your commit is merged. So you can just simply start working with the issue right away!
Open the tasks/html/easy directory from the root of your project.
Your task is to insert an h1 tag with the name John Doe above the h2 tag in the simple-tag.html file.
Note: Only the simple-tag.html file needs modification for this task.

If you are using VS Code and have for example Live Server extension, you can simply open simple-tag.html with the server and check how the page looks. After the task is done, you are ready to make a pull request!
If you do not have Live Server extension, you'll find information about installing and how to use it here.

Check out README.md for more instructions and how to make a pull request.
Feel free to ask any questions here if you have some problems!
Also, kindly give this project a star to enhance its visibility for new developers!

Can you assign this to me?

Can you assign this to me?

Hi! As it says on the description, we don't assign anyone to these educational issues, so you can just simply start working with the issue right away.


Enabling postproduction degrades rendering quality

Describe the bug 📝
When using the OBC.PostproductionRenderer toggling the post production on with renderer.postproduction.enabled = true; and renderer.postproduction.customEffects.outlineEnabled = true; makes the model edges fuzzy and aliased.
Before (false):

After (true):

Reproduction ▶
No response
Steps to reproduce 🔢

Follow https://top-docs.vercel.app/docs/Tutorials/FragmentIfcLoader to load an IFC file.
Previously loaded IFC file should be used with fragment highlighting following: https://top-docs.vercel.app/docs/Tutorials/FragmentHighlighter.

System Info 💻
Binaries:
    Node: 20.3.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.8.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (117.0.2045.47)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    openbim-components: ^1.1.0 => 1.1.0

Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a IFC.js components issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
[X] Check that this is a concrete bug. For Q&A join our Community.
[X] The provided reproduction is a minimal reproducible example of the bug.

I can second this, we're getting several rendering artifacts with thePostproductionRenderer:
PostproductionRenderer:
https://github.com/IFCjs/components/assets/13211347/7bca3970-0a1c-4b67-b036-6a03dd1f59ad
SimpleRenderer:
https://github.com/IFCjs/components/assets/13211347/0b31c992-32ae-4e74-a76e-c2af79645f32

We have learned, that this is tied to outlines, so we "fixed" it by disabling outlines, however that is a feat in itself.

After investigating this issue, I've found that the quality of the outlines pass degrades after being resized:
https://github.com/ThatOpen/engine_components/assets/56475338/b126f021-d824-4254-8005-2c5a30c13951
I've fixed it, and shouldn't happen again from version<EMAIL_ADDRESS>See this:
https://github.com/ThatOpen/engine_components/assets/56475338/d10707a7-0eb4-463f-a0b4-095515b74298
I suspect that this won't solve the issue described by @NiklasPor, which seem to be due to precission (surfaces being to close to each other, so the renderer is not able to determine which is in front of which).
I'm not sure how to solve this from the library, but one thing you can do is exclude a specific IFC category from being added to the outline computation by filtering them using the classifier (e.g. by IFC category) and then adding them to postproduction.customEffects.excludedMeshes, just like we do to exclude the grid in the tutorial.

I have a random shot-in-the-dark tip for the following issue - it might not
apply, but you will be able to recognise so quickly.

I suspect that this won't solve the issue described by @NiklasPor
https://github.com/NiklasPor, which seem to be due to precission
(surfaces being to close to each other, so the renderer is not able to
determine which is in front of which).

I'm not sure how to solve this from the library, but one thing you can do
is exclude a specific IFC category from being added to the outline
computation by filtering them using the classifier
https://docs.thatopen.com/Tutorials/Components/Core/Classifier (e.g. by
IFC category) and then >adding them to
postproduction.customEffects.excludedMeshes, just like we do to exclude the
grid in the tutorial.

Is the issue @NiklasPor described the issue commonly known as Z-index
fighting?
If so, there is a popular optimization for Z-buffer (which the 'good'
renderer might already use?)
A common issue for Z-buffer sorting, is that they map the perspective
projection to Z in [-1,1].
There is an optimization, where you reverse this ordering, and offset it to
0/1, so it instead maps [1, 0].
The idea with doing this, is to exploit that floating point numbers have
stronger precision around zero, and in the interval [0, 0.5].
The main reason I'm thinking about it, is that we often see lots of Z-index
fighting when viewing IFC files, because of their nature - often, the
models will contain many thin polygon layers stacked closely.
If this has nothing to do with the issue at hand, please ignore this input
:-).
On Thu, 20 Jun 2024 at 13:00, Antonio González Viegas <
@.***> wrote:

After investigating this issue, I've found that the quality of the
outlines pass degrades after being resized:
https://github.com/ThatOpen/engine_components/assets/56475338/b126f021-d824-4254-8005-2c5a30c13951
I've fixed it, and shouldn't happen again from version
@@.*** See this:
https://github.com/ThatOpen/engine_components/assets/56475338/d10707a7-0eb4-463f-a0b4-095515b74298
I suspect that this won't solve the issue described by @NiklasPor
https://github.com/NiklasPor, which seem to be due to precission
(surfaces being to close to each other, so the renderer is not able to
determine which is in front of which).
I'm not sure how to solve this from the library, but one thing you can do
is exclude a specific IFC category from being added to the outline
computation by filtering them using the classifier
https://docs.thatopen.com/Tutorials/Components/Core/Classifier (e.g. by
IFC category) and then adding them to
postproduction.customEffects.excludedMeshes, just like we do to exclude
the grid in the tutorial.
—
Reply to this email directly, view it on GitHub
https://github.com/ThatOpen/engine_components/issues/128#issuecomment-2180397197,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVBASI3B2X4T2ZB64VMTR3ZIKY5JAVCNFSM6AAAAAA5SK2VF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBQGM4TOMJZG4
.
You are receiving this because you commented.Message ID:
@.***>

I'll try to check the latest state, sadly we're still running a pre 2.0 version as many of the breaking changes were in conflict with our area-multi-select tool and we have to rewrite it to migrate 😁 I'll get back to this once we're on the latest version again.


Quick fix for #20

Should fix issue #20. I'm not sure what specifically about the map in question caused this issue, I guess there's a lot of physics props lying around in it.

im rewriting the prop code at some point, no need for a quick fix


How can i change theme when used antd design

I've tried antd on this project,It is normal and very convenient，but In my project, need to modify the default theme color，according to the official method there will be a problem in this template，https://github.com/ant-tool/atool-build/blob/a4b3e3eec4ffc09b0e2352d7f9d279c4c28fdb99/src/getWebpackCommonConfig.js#L131-L138
i don't know how can i get the theme.js and put it to rules in webpack.base.babel.js

i can change primary-color like this
{
test: /.less$/,
use: [
'style-loader',
'css-loader',
{
loader: 'less-loader',
options: {
modifyVars: {
'primary-color': '#1DA57A',
},
},
}],
},
but i want import theme.js to change it

Hi,
This is my configuration for Antd :
const fs = require('fs');
const path = require('path');
const lessToJs = require('less-vars-to-js');
const themeVariables = lessToJs(fs.readFileSync(path.join(__dirname, './../../app/less/theme.less'), 'utf8'));

{ // Transform less files from antd and replace variables
        test: /\.less$/,
        include: /node_modules/,
        use: [
          'style-loader',
          'css-loader',
          {
            loader: 'less-loader',
            options: {
              modifyVars: themeVariables,
            },
          },
        ],
      }

That's great，With your method, everything is fine。
Thanks


Add support for latest CPython and PyPy versions

Adds support for:

CPython 2.7.18, 3.5.9, 3.7.7 and 3.8.3
PyPy2.7 v7.3.1 and PyPy3.6 v7.3.1

The binaries will need generating and uploading before CI will pass.
Note: Whilst the build script for CPython 3.8.3 did already exist in the repository, it appears to have been accidentally created in #920, which predated the existence of that version of Python - so the binaries do not exist on S3.
The Heroku-18 Docker image tag has also been unpinned, since the new libssl version is now available at runtime in all environments, so we don't need to force building against the older version of the headers.
Fixes W-7582174.

Once I have review, I'll generate/upload the binaries and retrigger CI.

All binaries generated; CI now passes. I'll bump the buildpack version and release next.


Replaced most icons with vector drawables

I replaced most of the icons used in throughout the app with material design vector xml icons.

Have you tried running this on devices that don't natively support vector drawables?

Have you tried running this on devices that don't natively support vector drawables?

I've tested it using API 16 on a virtual device and it worked just fine.

Please move the vector drawables to drawable-anydpi (see https://commonsware.com/blog/2015/12/21/nodpi-anydpi-wtf.html).
Why did you rename the files? Having e.g. ic_email_open_dark instead of ic_action_mark_as_read_dark seems like a step back. Especially since "open" and "mark as read" are not really the same thing.

Please move the vector drawables to drawable-anydpi
Seems like a smart thing to do, I'll do that.
Why did you rename the files?
I renamed the files because one or two were the same icons but for different actions which means there were basically duplicate files. So my idea was to use names that describe the image instead of the action it is used for and use the assigned name from theme.xml to describe the action. I hope that makes sense.
But I'm happy to rename them again if that's how it should be done.

I renamed the files because one or two were the same icons but for different actions which means there were basically duplicate files. So my idea was to use names that describe the image instead of the action it is used for and use the assigned name from theme.xml to describe the action. I hope that makes sense.

I see. Sounds like a good idea :+1:
However, it doesn't seem to be very consistent right now. E.g. ic_delete_dark instead of ic_trash_can_dark. Also, sometimes confusing. I mistook ic_email_open_dark for an action. Maybe that one could be ic_opened_envelope_dark instead.

I moved all the files I changed to drawable-anydpi and renamed some files so they better describe the icon. I couldn't find perfectly fitting names for every icon, so some of them might still be a little confusing...

Thanks!


Estimate number of symbols & file size for design kit

Roughly speaking, a complete kit would need:
[num] of components x variations x 5 breakpoints x 4 themes
An MVP kit would need:
10 high priority components x variations x 5 breakpoints x 4 themes
Note
Some components might have states, eg. Masthead.
Some components might have more breakpoints...
Task
Estimate the number of symbols for 2 situations: a complete kit, and an MVP kit

Amazing work by @oliviaflory ! This work is done. Decision is made based on this evaluation, we will repurpose the Expressive theme sketch kits for Carbon for Dotcom kit, instead of reviving the old IBM.com kit.


How to pass custom options to Elastic Lunr?

Hey, I wonder how to enable expand option. Where can I pass expand: false ?

Expand option is used on index.search(searchTerm, {expand: false})but I think it's the default value


WMAgent v2.3.3 Validation

Impact of the new feature
WMAgent
Is your feature request related to a problem? Please describe.
By-monthly task
Describe the solution you'd like
We need to release a new WMAgent stable version in Mar/2024, so this issue is meant to keep track of the full validation activity to be carried out in the first weeks of March, once we have a final 2.3.3 tag.
In addition to the validation results, WMAgent release notes and the validation check-list twiki need to be created as well.
Describe alternatives you've considered
None
Additional context
None

WMAgent release 2.3.2.rc4 plus patches has been validated and everything seems to be working as expected. Tests and results have been tracked in this twiki.
We still have to cut the final release, but I see a few more developments already in the pipeline (from the T0 team), so we might just wait for that.
In addition, I have not validated anything regarding partial pileup - the WorkflowUpdater component - as that validation is supposed to happen with this ticket: https://github.com/dmwm/WMCore/issues/11736


Automate the creation of a semver tag and a release after push to main

Codecov Report

Merging #21 (e4d69e3) into main (0902f88) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #21   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          167       167
=========================================
  Hits           167       167

Help us with your feedback. Take ten seconds to tell us how you rate us.


Update README.md

Fix the issue where solutions generated after executing the bash script are not being saved.

The generations are saved by default in the generation_only mode https://github.com/bigcode-project/bigcode-evaluation-harness/blob/e54f33d093f342ffc0c5c057910c00aa2081515d/main.py#L389

I am also experiencing this. If you set --generation_only and --save_generations_path "./gens.json" but not --save_generations It does not write to file. Several examples and the README should be adjusted, else work might be lost.
problematic behaviour is this line: https://github.com/bigcode-project/bigcode-evaluation-harness/blame/e54f33d093f342ffc0c5c057910c00aa2081515d/bigcode_eval/evaluator.py#L117

Ah I missed that, feel free to open a PR that adds if self.args.save_generations or self.args.generation_only: @Vipitis . Thanks!

Will do, but won't be able to submit it until next week.


Metrics not found

Some metrics aren't found in this API like ga:country, ga:gender, ga:userType.

The metrics from the Google Analytics API won't show up as data types in this library, rather they are passed in as data:
  // Create the Metrics object.
  $country = new Google_Service_AnalyticsReporting_Metric();
  $country->setExpression("ga:country");
  $country->setAlias("sessions");

  $gender = new Google_Service_AnalyticsReporting_Metric();
  $gender->setExpression("ga:gender");
  $gender->setAlias("sessions");

  $usertype = new Google_Service_AnalyticsReporting_Metric();
  $usertype->setExpression("ga:userType");
  $usertype->setAlias("sessions");

  // Create the ReportRequest object.
  $request = new Google_Service_AnalyticsReporting_ReportRequest();
  $request->setViewId($VIEW_ID);
  $request->setDateRanges($dateRange);
  $request->setMetrics(array($countries, $gender, $usertype));

Thanks for filing this issue. It looks like it has been addressed, if that is not the case let us know in the comments.


Blog post Tag prediction/recommendation?

I want to recommend tags for my blog posts, I plan to have the text, and I need to receive tags.
Any recommendation about where to begin?
Any example that I can see?

I know you're not directly asking a blog or WordPress question but I can address at least the immediate issue. There are SEO plugins for WordPress that can help with keyword recommendation. This could be used for tags as well.
I'm also curious how something like this could work. Something to keep in mind here is this would also require some server knowledge to install and setup all the necessary dependencies.

Hey @elfeffe that's a great use case
The way that you'd approach the problem with machine learning would be to (either yourself or someone else) start labeling a portion of the blog posts in your database with tags by hand. Pair each sample (which may include things like the title and body of the post) with a unique tag (you will duplicate samples for posts with multiple tags). For however many samples you want to self-annotate, this will be your dataset. I would recommend settings about 20% of the data aside for cross-validation. The bigger your dataset, the better your results will be.
When inferring tags of new blog posts, you'll call the proba() method on a Probabilistic estimator to output the probabilities of every possible tag, sort them by their probability and take the top k above a threshold as the inferred tags for example.
The Sentiment example, is a good reference of natural language problems such as this one. The task is different, but many of the preprocessing steps are the same.

Great, thank you, I will check that.
This is not for a WP blog, and the main idea is to learn how to use this library.
We have 20000 posts with multiple tags (added by hand).
I will check how to begin.
Thank you guys.
Happy new year.

Great, thank you, I will check that.
This is not for a WP blog, and the main idea is to learn how to use this library.
We have 20000 posts with multiple tags (added by hand).
I will check how to begin.
Thank you guys.
Happy new year.

@andrewdalpino will be useful to remove common words (for, from, at, the) and remove accents (from Spanish words). Or it’s useless?

@andrewdalpino will be useful to remove common words (for, from, at, the) and remove accents (from Spanish words). Or it’s useless?

Ok. That’s the tdidf.

Ok. That’s the tdidf.

@andrewdalpino will be useful to remove common words (for, from, at, the) and remove accents (from Spanish words). Or it’s useless?

That's a good question, and I'm not sure there's a good answer for that except to do some experiments to see which works best for the data you have. To remove common words (a.k.a. stop words) you can try a couple of different strategies. You can use the parameter max document frequency on Word Count Vectorizer to bar stop words from entering the vocabulary, or you can filter stop words from the dataset before tokenizing the blobs using Stop Word Filter.
https://docs.rubixml.com/en/latest/transformers/word-count-vectorizer.html
https://docs.rubixml.com/en/latest/transformers/stop-word-filter.html

Ok. That’s the tdidf.

Not quite, but your intuition is good. Term Frequency - Inverse Document Frequency (TF-IDF) is a weighting scheme applied to the raw term counts created by Word Count Vectorizer such that common words are given less weight than rarer words. This is slightly different from removing the token completely from the bag of words in that some weight is still given to the occurrences.

@andrewdalpino will be useful to remove common words (for, from, at, the) and remove accents (from Spanish words). Or it’s useless?

That's a good question, and I'm not sure there's a good answer for that except to do some experiments to see which works best for the data you have. To remove common words (a.k.a. stop words) you can try a couple of different strategies. You can use the parameter max document frequency on Word Count Vectorizer to bar stop words from entering the vocabulary, or you can filter stop words from the dataset before tokenizing the blobs using Stop Word Filter.
https://docs.rubixml.com/en/latest/transformers/word-count-vectorizer.html
https://docs.rubixml.com/en/latest/transformers/stop-word-filter.html

Ok. That’s the tdidf.

Not quite, but your intuition is good. Term Frequency - Inverse Document Frequency (TF-IDF) is a weighting scheme applied to the raw term counts created by Word Count Vectorizer such that common words are given less weight than rarer words. This is slightly different from removing the token completely from the bag of words in that some weight is still given to the occurrences.


Port the DOI Service to make use of the Elide backend

refactored the code to split repository comms from xref comms

code merged into pass-core/main


[HOLD #39725] [Wave Collect] [Xero] Handle errors in the connections

We need to handle Xero connection errors. More details here.
This will be worked on by SWM engineers, see Slack discussion here.
Until the Xero authorization flow (NewDot issue)  is done (which entails NewDot, Web-E and IS changes), we won't be able to work on this yet.

On hold for https://github.com/Expensify/App/issues/39725

I can take care of that, since I'm already in context because I was doing Xero authorization flow. Could you assign me @mountiny?

@lakchote thank you for handling this. I have one question:
Is this about the error handling when connecting to Xero or error handling for invalid configuration combinations?
or is it about error handling for sync errors?

I think this is purely the connection errors

I think this is purely the connection errors

Yes @hayata-suenaga, as @mountiny said it's purely showing the connection errors and the RBR.

On hold for https://github.com/Expensify/App/issues/39725

Not on hold anymore, cc @SzymczakJ

Assigning @mananjadhav as he'll be working on this.

@lakchote Added the PR to fix the disconnect Xero.

Deployed to prod 9 hours ago.

Payout for this will be handled after all Xero issues are done. We can close this after the regression period.

Yep, agreed. Regression period is over, closing.


Client side symptom classification algorithm

This issue builds on Issue #34
Given 40% of Covid19 carriers have only mild symptoms and may not have tested, it's important to identify interactions with these individuals as well.
In order to reduce the data load on SafeTrace API, we propose to run a classification on self reported symptoms (with output high risk symptoms, medium risk symptoms and low risk symptoms) on the client side and pass user status to SafeTrace API
Next step: Determine client side algorithm based on issue #5
Requirements: The algorithm needs to be written in Javascript to run on the client-side

This issue builds on Issue #34
Given 40% of Covid19 carriers have only mild symptoms and may not have tested, it's important to identify interactions with these individuals as well.

Models based on data from Wuhan suggest that most new cases of COVID19 are likely being spread by patients showing mild symptoms or none at all. Citation.

In order to reduce the data load on SafeTrace API, we propose to run a classification on self reported symptoms (with output high risk symptoms, medium risk symptoms and low risk symptoms) on the client side and pass user status to SafeTrace API
Next step: Determine client side algorithm based on issue #5

@codeanticode this seems is similar to your research. We are trying to classify user reported symptom (fever >38 / 100, Cough, sore throat, shortness of breath) based on risk (high risk symptoms, low .. etc.)
If you have any feedback we'd be very happy to incorporate into our thinking
Cheers

@cankisagun Apologies. Other obligations prevented me from posting some content. Hopefully things will slow down this weekend and I'll be able to contribute. To be clear, you're looking for hoping to categorize a user's risk based on his/her signs/symptoms (SS), correct?

@kistn010, yes that's the idea.
@codeanticode is also working on a similar algorithm to classify the risk of symptoms.
The goal of this is to report to individuals not only diagnosed patients around them but also users who show high risk symptoms

Understood.
The majority of people who contract the virus experience only mild symptoms
(if any at all). Thus, focusing on signs/symptoms may fail to differentiate.
I think greater gain would come from stratifying users based on their
exposure (to the virus/infected person). This is a primary issue given the
amount of asymptomatic transmission that's occurring (sp., people worldwide
are transmitting the disease without even knowing they're infected). If
individuals know the level of risk associated with their exposure, it
should be easier for them to quarantine themselves more quickly/responsibly
(even if asymptomatic).
On Sat, Apr 4, 2020 at 2:55 PM cankisagun<EMAIL_ADDRESS>wrote:

@kistn010 https://github.com/kistn010, yes that's the idea.
@codeanticode https://github.com/codeanticode is also working on a
similar algorithm to classify the risk of symptoms.
The goal of this is to report to individuals not only diagnosed patients
around them but also users who show high risk symptoms
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/enigmampc/SafeTrace/issues/35#issuecomment-609081068,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKPYK7UHWI7OKLGQAAF56ETRK6GC3ANCNFSM4LXBURJQ
.

--
Brett M Kistner
Doctor of Pharmacy
University of Minnesota
P<PHONE_NUMBER>
E<EMAIL_ADDRESS><EMAIL_ADDRESS>

@cankisagun sorry for the slow reply. I have worked on some diagnosis/prognosis prediction models for Ebola with similar sign & symptom data as the input. Logistic regression models are a common choice for kind of prediction tasks.


Restructure the repo and README

This ties in with a restructuring effort for the wiki and the new, excellent banner by @fools-mate.
This is still a WIP, just wanted to get some feedback on the layout of the redesigned README. I'll unset the draft mode once I'm done so it can get merged. Take a look at a rendered preview here: https://github.com/dominiklohmann/yabai/blob/restructure/README.md
I am about to merge CODESIGN into the wiki (very soon, w/ lots of other changes and updates for 2.x) and I merged the CHANGELOG into the REAEDME already. Links in the Releases section will have to be changed by a maintainer/collaborator.
~I added the assets to the repo, and while I'd have preferred to use git-lfs to upload the .png assets, GitHub currently does not support uploading git-lfs objects to public forks for non-enterprise accounts.~
Edit: Am maintainer/collaborator now, thanks @koekeishiya—will upload via git-lfs outside of this PR.
I also have some issue templates planned, but I'm not sure if these can be added via PRs~. I think they need to be configured by a maintainer/collaborator.~
A 1280x640 (that's already 2x) banner can be used as a social media preview as well~, but that also needs to be configured by a maintainer/collaborator.~

Looks great so far. I noticed that you removed the thing about placement of the config file - I assume  this will be put in the wiki when the update happens (as it is not there as of now).
I'm also not sure if I like that the changelog is a part of the readme. I think that the changelog and the contents of the readme has a different target audience. Someone looking through the readme to get an idea of what yabai is probably doesn't care much about the latest changes; especially if the list of recent changes is large (e.g  the list of v2.0.0).

I think that the changelog and the contents of the readme has a different target audience.

That's a point of view I did not consider. I just didn't think the changelog was easily discoverable.

placement of the config file - I assume this will be put in the wiki when the update happens

That's correct. I was waiting for the 2.0 release as there were so many unreleased changes, and I'm gonna push the changes when I get back home after the weekend. They've been sitting in a private repo for a while now, and just need a short review that I've been delaying lately. The wiki is still at 1.1.2 currently.
Upon further research, a social media banner and issue templates can only be set by repository owners for account-owned (public) repositories, or by maintainers for organization-owned (public) repositories. This is apparently where the account-owned/org-owned border comes in, the collaborator privilege comes with everything except the settings tab. At least now I can upload the files, you'll just have to enable them afterwards.

Closing this in favor of #247 so that the assets can be added using git-lfs. I can't do that from a fork, sadly.

Upon further research, a social media banner

I assume this is the Social Preview thing. Is there an appropriately sized image in the assets folder that I can set it to?

I'll get you one, it needs a very high margin. There's an example file available for download just below where you can set it. It's basically what Twitter/Facebook/Reddit etc. use for previews when the repo is linked, and it defaults to your profile picture if I recall correctly.
Will be back home in the evening, which is when work on the restructuring continues. Just wanted to push this one out a bit ahead so I can use the vector graphics in the wiki later today, which is necessary because I cannot upload vector graphics to GitHub issues.

On 12. Sep 2019, at 08:53, Åsmund Vikane<EMAIL_ADDRESS>wrote:
Upon further research, a social media banner
I assume this is the Social Preview thing. Is there an appropriately sized image in the assets folder that I can set it to?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/koekeishiya/yabai/pull/237?email_source=notifications&email_token=ABCH3TZXDTARPAR2UDSKHSTQJHRNVA5CNFSM4IUIDNH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6Q3OLQ#issuecomment-530691886, or mute the thread https://github.com/notifications/unsubscribe-auth/ABCH3TYXX64IKIL5H5FCLOLQJHRNVANCNFSM4IUIDNHQ.

Aight that's fine. Just ping me whenever you have had the time and I'll see if I can get it up asap :)


[Conflict Issue] one vote call autopilot host feature are blocked by HostFixes

that's not HostFixes issues but i hope can looking for compatibility solutions, no matter Lethal_Admin or AntiCheat, all related this feature are malfunction

https://github.com/Charlese2/HostFixes/issues/11

Ah, I'll look into it as it is implemented a bit like a cheat so I'm not really surprised.

I've changed how it works and (at least for me) it works now with HostFixes. I'll probably release it this weekend (I still have some things I want to add and test)


Manual testing of UnitTestBot Family PR #1199

Initial set-up
Check that the IntelliJ Idea UTBot plugin can be successfully installed
PR - #1197

[ ] Take build from tamarinvs19/UnitTestBot_Family_PR branch
[ ] Download plugin
[ ] Check downloaded zip-file size < 100 MB
[ ] Open IntelliJ IDE
[ ] Remove previously installed UTBot plugin
[ ] Clone or reuse UTBot project (https://github.com/UnitTestBot/UTBotJava.git)
[ ] Open the project in the IDE
[ ] Install the downloaded plugin

Go through manual scenarios
Manual scenario #1

[ ] Use default plugin settings
[ ] Open the utbot-sample/src/main/java/org/utbot/examples/algorithms/ArraysQuickSort.java file
[ ] Generate tests for the class
[ ] Remove results
[ ] Generate and Run test for a method

Manual scenario #2

[ ] Use default plugin settings
[ ] Open the utbot-sample/src/main/java/org/utbot/examples/mock/CommonMocksExample.java file
[ ] Generate tests with different Mocking options combinations

Manual scenario #3

[ ] Create a new Gradle project with JDK 11
[ ] Add a simple java file to test
[ ] Generate a test in the existing test root

Manual scenario #4

[ ] Create a new Maven project with JDK 8
[ ] Set Fuzzing 100%
[ ] Add a simple java file to test
[ ] Generate a test with a new test root

Manual scenario #5

[ ] Create a new Idea project with JDK 17
[ ] Add a simple java file to test
[ ] Generate tests for several classes with Parameterization on

Current size is exceeding restriction of 100 MB:

Current plugin size is exceeding the one in main and limit of 100MB:


Suggest renaming option from name to --name

Usually when I get this error message, it's because I wrote @click.option('foo') when I meant @click.option('--foo'). So this PR updates the error message to suggest the user fix that.

Reworded the message a bit, updated test, added changelog.


Ignite 3727-2 Support local listeners async execution for IgniteMessage.send

Support local listeners async execution for IgniteMessage.send

TeamCity Test test success.

The ticket is resolved, closing PR.
Please close PRs for your resolved tickets and other non-needed PRs.
Alternatively, ask a committer

to use GitHub UI (committer can associate accounts here: https://gitbox.apache.org/setup/ )
or ./scripts/apply_pull_request.sh from Apache Ignite source.
or mention in commit message 'Fixes #(a number of PR)'.

These methods will automatically close PR.
Feel free to reopen this PR if it is anyway actual.


fix loki compactor alert dashboard

This PR fixes the dashboard link for LokiCompactorFailedCompaction alerts.
Checklist

[x] Update CHANGELOG.md
[ ] Add Unit tests
[ ] Follow Alert structure
[ ] Consider creating a dashboard (guidelines) (if it does not exist already) to help oncallers monitor the status of the issue.
[ ] Request review from oncall area, as well as team (e.g: oncall-kaas-cloud GitHub group).

Was actually


[Accelerate] [vDSP] Fill, Clear, and Generation Functions

This PR contains a suite of Swift-friendly overlays to the vDSP vector fill, clear, and generation (including window and ramp) functions. The overlays simplify the API to the existing functions and accept collections that implement _ContiguousCollection.
cc: @moiseev @airspeedswift @stephentyrone

@swift-ci Please test macOS platformn

@swift-ci Please smoke test Linux platform


k

Have you read the Contributing Guidelines?

[x] YES
[ ] NO

Project URL

What is the current behavior?

Issue Number: #...

Category

[ ] 𝑴𝒊𝒔𝒄𝒆𝒍𝒍𝒂𝒏𝒆𝒐𝒖𝒔 𝑺𝒕𝒖𝒇𝒇.
[ ] 𝑫𝑺𝑨 + CP
[ ] 𝑻𝒆𝒄𝒉𝒏𝒊𝒄𝒂𝒍 𝑺𝒖𝒃𝒋𝒆𝒄𝒕
[ ] 𝑳𝒐𝒘 𝑳𝒆𝒗𝒆𝒍 𝑫𝒆𝒔𝒊𝒈𝒏
[ ] 𝑷𝒓𝒐𝒋𝒆𝒄𝒕𝒔
[ ] 𝑰𝒎𝒑𝒐𝒓𝒕𝒂𝒏𝒕 𝑩𝒐𝒐𝒌𝒔 𝒂𝒏𝒅 𝑹𝒆𝒔𝒐𝒖𝒓𝒄𝒆𝒔
[x] 𝑩𝒆𝒉𝒂𝒗𝒊𝒐𝒖𝒓𝒂𝒍 𝑰𝒏𝒕𝒆𝒓𝒗𝒊𝒆𝒘 𝑸𝒖𝒆𝒔𝒕𝒊𝒐𝒏𝒔

Changes

Description of changes

Screenshots

(Add Runnig Work Demo Image)

Checklist ✅

[x] I've read the instructions on the README file before submitting my application.
[x] I've read the Contributing Guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've follow Tree of Index.
[x] I've add work in proper folder
[x] I've not delete/modify previous codes.

k

k


traducion instalar kanboard debian

Before to submit your pull-request:

Be sure that the unit tests pass
If you create a new feature, test your code, do not introduce new bugs
Avoid code duplication
Small pull-requests are easier to review and can be merged quickly
1 pull-request == 1 feature/improvement
Non necessary features should be implemented as plugin

Great idea!
But you should put the translated files in the sub directory "doc/es_ES".
See https://github.com/fguillot/kanboard/commit/75019b3a8e838f51bfac51bdbf9e6647faaaec1d

Your translations must be moved to the folder doc/es_ES like I said in the previous pull-requests. Here, you are overwriting the English translation. Thanks for your comprehension.

sorry , from now on the 'll add files in the docs folder doc/es_ES


Update charts and installer to latest image.

Description of changes:
Upgrade the aws provided installer and the helm chart to the latest public published image.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #165 (94082f8) into main (41dc61e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #165   +/-   ##
=======================================
  Coverage   52.88%   52.88%
=======================================
  Files           7        7
  Lines         711      711
=======================================
  Hits          376      376
  Misses        326      326
  Partials        9        9

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


Making flow check result prettier and easier to read

Currently flow check results looks like this, which is a bit hard to read and understand what the error really is:
/Users/folder/zzz.js:14:2,11:
class property initializers are not yet supported

/Users/folder/zzz.js:22:9,24: function call
Error:
/Users/folder/zzz.js:22:14,15: number
This type is incompatible with
/Users/folder/zzz.js:7:19,24: string

Found 2 errors

Wouldn't it be nicer to be like this:
Created: Tue Sep 01 2015 19:37:14 GMT+0800 (CST)
Total Errors: 2

Error:
  /Users/folder/zzz.js, line 14
  t1 = '00';
  ↑ class property initializers are not yet supported

Error:
  /Users/folder/zzz.js, line 22
  var k = foo( 33, 'a22' );
               ↑ expecting "string", got "number"

  From:
    /Users/folder/zzz.js, line 7
    function foo( bar:string, coo:number ):Array<string> {

I've built a simple parser in javascript to do just that, but thought it would be a really nice feature out of the box.
As a side note, I might go ahead and build a plugin for sublime text editor so that errors can be marked inline and a popup will show up when mouse hover over it, à la mode most IDEs out there (ie: Eclipse, Visual Studio).

@coodoo I was thinking of doing a sublime linter myself, but my python isn't great. I currently work on linter-flow-plus for atom (I will also update linter-flow as well)

Sounds good, please keep me posted if you do decide to go ahead and build that, thanks.

I went ahead and created flowery which runs as a CLI and API tool.

@coodoo This is very cool!

@coodoo I'm reading the SublimeLinter documentation trying to make sense of it all. My python is really quite rusty.
But linter-flow-plus supports error + trace, the same way that flowery does. Using the --json flag on flow helps a lot.


"utils.files is not a function" (mocha: 5.0.2)

Description
Hey, i've just upgraded to the latest mocha version 5.0.2 and I now start to see a "utils.files is not a function" error when running in watch mode with passing a glob path. Seems this commit ec8901a23c5194b6f7e6eee9c2568e5020c944ce removed the function which is still used in https://github.com/mochajs/mocha/blob/master/bin/_mocha#L532
Steps to Reproduce
NODE_ENV=test mocha './test/**/*.js'
Expected behavior:
it should execute my tests as before.
Actual behavior:
it crashes all the time
> NODE_ENV=test mocha './test/**/*.js' "--watch"

/opt/MY-PACKAGE/node_modules/mocha/bin/_mocha:532
  const watchFiles = utils.files(cwd, [ 'js' ].concat(program.watchExtensions));
                           ^

TypeError: utils.files is not a function
    at Object.<anonymous> (/opt/MY-PACKAGE/node_modules/mocha/bin/_mocha:532:28)
    at Module._compile (module.js:643:30)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Function.Module.runMain (module.js:684:10)
    at startup (bootstrap_node.js:187:16)
    at bootstrap_node.js:608:3

Versions

5.0.2
shell: zsh
The code transpiler being used: babel

Same here, looks like utils.files was removed in https://github.com/mochajs/mocha/commit/ec8901a23c5194b6f7e6eee9c2568e5020c944ce but is still in use.

This exists in 5.0.1 as well it seems.

Confirm this is still an issue.

Downgraded to 5.0.1, it works.

Error exists in 5.11, node 9.5.0 as well

Please reopen.

@sebs This has already been fixed; please check that the mocha you are executing is indeed v5.1.1; you may need to run mocha -v.  sometimes a globally-installed mocha is used by mistake

I am running the mocha via npm scripts. I can investigate that. I am running an NVM setup. I have no recollection of places where mocha is not adhering to be run via npm scripts, but my node 9.5.0 is a bit outdated.
I used the global installation to trouble shot and make sure it was really changed.

Ah I donnu, I was so sure I had pinned it down to 5.1.1 Mocha works as intended
Thanks


review CAS memory handling

The CAS of the running instance of Chainloop has been reaching the limit of 512mi and being killed by the scheduler making some release jobs fail.

We have increased the memory limit to 1GB but we should look into the memory handling of uploads to make sure there is proper handling and no leaks.

After deploying this release we've seen a memory usage climb

It's probably related to the fact that now the controlplane calls the infoz endpoint of the CAS for its readiness probe
{"level":"info","ts":1681507135.9057927,"kind":"server","component":"http","operation":"/cas.v1.StatusService/Infoz","args":"","code":0,"reason":"","stack":"","latency":0.000021218}

That endpoint seems quite simple, not sure in which part of the stack we are getting that potential memory leak


PCA Notebook

@aarmey could you take a look at the PCA. The first two plots for from our last meeting, and the both bottom two are PCA for adcc and binding. We'll include the complement activation data once we get access to it.

@aarmey I moved the PCA and R2X plots into figure6.py and ADCC cross validation stuff into figure7.py


PHP selector

Hiya,
Can you consider incorporating a php selector such as this:
https://forum.vestacp.com/viewtopic.php?f=41&t=17129
some of my scripts are wanting specific versions of php

I have something similar already in there.  Here is the doc https://github.com/niiknow/vestacp/blob/master/docs/php-fpm.md  Is it not working or what kind of problem are you having?   I have both Apache php-fcgi and nginx php-fpm with different versions (7.1 - 7.3) implemented.
php-fpm required you to add to startup script: https://github.com/niiknow/vestacp/blob/master/rootfs/sysprepz/admin/bin/my-startup.sh#L21


[FEATURE-REQUEST] Zend Server OOB knowledge

Describe the solution you'd like
It'd be cool for Service Commander to know about Zend Server and ZendPHP "out of the box".
I would need someone's help from Perforce to contribute, as I don't have any product access or knowledge.

@jbh perhaps?

Nice. Thanks for the tag @ThePrez.
I've got a busy day planning. I'll take a look this evening and tomorrow.

[ ] ZendPHP runtime (check/start/stop)
[ ] ZendServer (check)

@jbh, how's this one going? Anything I can help with?

Oops. Fell off my radar. :grimacing:
It's on my todo list again. Hopefully I can take a look this weekend.

@jbh friendly poke


Where do i find the version required for cordova-plugin-admobpro when using meteor ?

As per the documentation provided under https://github.com/floatinghotpot/cordova-admob-pro/wiki/06.-How-To-Use-with-Meteor, within the AddPlugin section, I found the below information.
Add plugin: meteor add<EMAIL_ADDRESS>Replace x.x.x with current version number, see the version here: https://www.npmjs.com/package/cordova-plugin-admobpro
But I still cannot find the exact version required for adding to meteor.
Kindly suggest.
Thanks & Regards,
Kunal Kishor Ugale

I guess you can omit the version number to always use the most recent version.
If you do wish to see the version number, see it in npm repo:
https://www.npmjs.com/package/cordova-plugin-admobpro

Thanks, Got the version number from npm repository