Trying to install the latest stable version of the CLI using "composer global require 'platformsh/cli:@stable' " command.

I am trying to set up local Drupal development. And I am following this document.
To succeed with Platform.sh i need the following installed on my local machine:
I have installed and configure first three things.
id_rsa public/private keypair
Git
Composer
The Platform.sh CLI
Drush
But whenever i try to install "The Platform.sh CLI" , and run run the command composer global require 'platformsh/cli:@stable' i got following error.
linux@ubuntu:~$ composer global require 'platformsh/cli:@stable'
Changed current directory to /home/linux/.composer
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- platformsh/cli 1.10.3 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.0.0 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.0.1 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.0.2 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.0.3 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.1.0 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.10.0 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.10.1 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.10.2 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.10.4 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.2.0 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.2.1 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.2.2 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.2.3 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.2.4 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.2.5 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.2.6 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.3.0 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.3.1 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.4.0 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.4.1 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.4.2 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.4.3 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.4.4 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.4.5 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.5.0 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.5.1 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.5.2 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.5.3 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.5.4 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.6.0 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.6.1 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.6.2 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.6.3 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.7.0 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.7.1 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.7.2 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.7.3 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.7.4 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.7.5 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.8.0 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.8.1 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.8.2 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.8.3 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.8.4 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.8.5 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.9.0 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.9.1 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.9.2 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- platformsh/cli v1.9.3 requires commerceguys/guzzle-oauth2-plugin ~1.0 -> satisfiable by commerceguys/guzzle-oauth2-plugin[v1.0.0].
- commerceguys/guzzle-oauth2-plugin v1.0.0 requires guzzle/guzzle >=v3.0 -> satisfiable by guzzle/guzzle[v3.0.0, v3.0.1, v3.0.2, v3.0.3, v3.0.4, v3.0.5, v3.0.6, v3.0.7, v3.1.0, v3.1.1, v3.1.2, v3.2.0, v3.3.0, v3.3.1, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.5.0, v3.6.0, v3.7.0, v3.7.1, v3.7.2, v3.7.3, v3.7.4, v3.8.0, v3.8.1, v3.9.0, v3.9.1, v3.9.2, v3.9.3].
- guzzle/guzzle v3.9.3 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.9.2 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.9.1 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.9.0 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.8.1 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.8.0 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.7.4 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.7.3 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.7.2 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.7.1 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.7.0 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.6.0 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.5.0 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.4.3 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.4.2 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.4.1 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.4.0 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.3.1 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.3.0 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.2.0 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.1.2 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.1.1 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.1.0 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.0.7 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.0.6 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.0.5 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.0.4 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.0.3 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.0.2 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.0.1 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- guzzle/guzzle v3.0.0 requires ext-curl * -> the requested PHP extension curl is missing from your system.
- Installation request for platformsh/cli @stable -> satisfiable by platformsh/cli[1.10.3, v1.0.0, v1.0.1, v1.0.2, v1.0.3, v1.1.0, v1.10.0, v1.10.1, v1.10.2, v1.10.4, v1.2.0, v1.2.1, v1.2.2, v1.2.3, v1.2.4, v1.2.5, v1.2.6, v1.3.0, v1.3.1, v1.4.0, v1.4.1, v1.4.2, v1.4.3, v1.4.4, v1.4.5, v1.5.0, v1.5.1, v1.5.2, v1.5.3, v1.5.4, v1.6.0, v1.6.1, v1.6.2, v1.6.3, v1.7.0, v1.7.1, v1.7.2, v1.7.3, v1.7.4, v1.7.5, v1.8.0, v1.8.1, v1.8.2, v1.8.3, v1.8.4, v1.8.5, v1.9.0, v1.9.1, v1.9.2, v1.9.3].
Installation failed, reverting ./composer.json to its original content.
linux@ubuntu:~$
Can you please tell me where i am going wrong. And how to resolve this issue?

The key error here is: "the requested PHP extension curl is missing from your system"
Since it looks like you're on Ubuntu, you could try:
sudo apt-get install php5-curl

@pjcdawkins
Thankyou so much...

 I assume it now works for you, so I'll close this issue.

Thank you very much.


FrameDurations is no longer available

I'm following the tutorial here and got a build error:
In file included from /home/pi/repos/libcamera-apps/libcamera_jpeg.cpp:10:
/home/pi/repos/libcamera-apps/libcamera_app.hpp: In member function ‘void LibcameraApp<OPTIONS>::StartCamera()’:
/home/pi/repos/libcamera-apps/libcamera_app.hpp:367:37: error: ‘FrameDurations’ is not a member of ‘controls’
   if (!controls_.contains(controls::FrameDurations))

This seems to be happening because FrameDurations was recently split into FrameDuration and FrameDurationLimits (commit here in a github mirror).
The problem upstream commit was only 3 days ago :-). I might skip over installing the apps at the moment, but thought I'd file the issue.

Thanks very much for this. It's a minor API change in libcamera. We've merged this now so I'll close the issue!


Pathing issues on pypi upload

BUILD FAILED - [Errno 22] invalid mode ('w') or filename: 'c:\Users\jcorson\pythonWorkspace\projectNameHere\target/reports\distutils\sdist__upload__-r__http:<IP_ADDRESS>:8080'
I am on windows working in the Git Bash. pybuilder version 0.11.8. I saw another closed issue about pathing and you made him upgrade but this is very recent
This issue didn't exist when it was the public PyPI server but I changed it to a local pypi that I need to store my project in. As a result, it seems to append the -r and the URL I provided
project.set_property("distutils_upload_repository", 'http://<IP_ADDRESS>:8080')

Traceback (most recent call last):
File "c:\python27\lib\site-packages\pybuilder\cli.py", line 403, in main
environments=options.environments, tasks=arguments)
File "c:\python27\lib\site-packages\pybuilder\reactor.py", line 124, in build
self.build_execution_plan(tasks, execution_plan)
File "c:\python27\lib\site-packages\pybuilder\reactor.py", line 166, in build_execution_plan
reactor=self)
File "c:\python27\lib\site-packages\pybuilder\execution.py", line 336, in execute_execution_plan
summaries.append(self.execute_task(task, **keyword_arguments))
File "c:\python27\lib\site-packages\pybuilder\execution.py", line 283, in execute_task
task.execute(self.logger, keyword_arguments)
File "c:\python27\lib\site-packages\pybuilder\execution.py", line 168, in execute
executable.execute(argument_dict)
File "c:\python27\lib\site-packages\pybuilder\execution.py", line 99, in execute
self.callable(*arguments)
File "c:\python27\lib\site-packages\pybuilder\plugins\python\distutils_plugin.py", line 237, in upload
execute_distutils(project, logger, upload_cmd_line, True)
File "c:\python27\lib\site-packages\pybuilder\plugins\python\distutils_plugin.py", line 261, in execute_distutils
with open(output_file_path, "w") as output_file:
i called the sdist directly without any issue

Not an issue, please see my response to #388

@nexeh The url in question is not an index URL. It's a URL of the source repository where the project to be installed is located, e.g. "git+git://github.com/pybuilder/pybuilder"

@nexeh also please upgrade to latest with "pip install --upgrade --pre pybuilder"

Duplicate of #370

@arcivanov I tried doing the upgrade which resulted in version PyBuilder==0.11.10.dev20160816052409 and it resulted in the same error message listed above

@arcivanov This is because of the ":" in the file name which windows does not allow. I tested this before be I didn't realize windows explorer automatically removed them to make it a valid name.

can't you just use Xnix? :D
kidding, I'll fix it :)

@arcivanov I WISH!
I made a tweak to see if i could move on and it does. I hit the root of your next problem now tho in the follow code in core.py...
on line 274 it makes the following call
return_code = _run_process_and_wait(commands, project.expand_path("$dir_dist"), output_file)
which results in the following error:
project.expand_path($dir_dist) c:\Users\jcorson\pythonWorkspace\projectNamehere\target/dist/projectNameHere-0.0.2
You can see the slashs are in the wrong direction for windows. This is becuase in expand path it splits on the windows path sep but its to late for that
def expand_path(self, format_string, *additional_path_elements):         elements = [self.basedir]         elements += self.expand(format_string).split(PATH_SEPARATOR)         elements += list(additional_path_elements)         return os.path.join(*elements)

@nexeh please try pip install --force-reinstall git+git://github.com/arcivanov/pybuilder@issue_387

@arcivanov Well i tried
$ pip install --force-reinstall git+git://github.com/arcivanov/pybuilder@issue_387
Collecting git+git://github.com/arcivanov/pybuilder@issue_387
  Cloning git://github.com/arcivanov/pybuilder (to issue_387) to c:\users\jcorson\appdata\local\temp\pip-xoxpop-build
    Complete output from command python setup.py egg_info:
    PyBuilder version ${dist_version}
    Build started at 2016-08-26 11:27:37
    ------------------------------------------------------------
    [INFO]  Building PyBuilder version 0.11.10.dev (0.11.10.dev20160826152737)
    [INFO]  Executing build in c:\users\jcorson\appdata\local\temp\pip-xoxpop-build
    [INFO]  Going to execute tasks: clean, install_dependencies, package
    [INFO]  Removing target directory c:\users\jcorson\appdata\local\temp\pip-xoxpop-build\target
    [INFO]  Installing all dependencies
    [INFO]  Processing batch dependency 'pip>=7.1'
    [INFO]  Installing plugin dependency pdoc
    [INFO]  Installing plugin dependency sphinx
    ------------------------------------------------------------
    BUILD FAILED - Missing prerequisite sphinx required by plugin python.sphinx
    ------------------------------------------------------------
    Build finished at 2016-08-26 11:28:05
    Build took 28 seconds (28137 ms)

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in c:\users\jcorson\appdata\local\temp\pip-xoxpop-build\

ugh :)

Anyway, the bug should be fixed, I'm going to merge and in a few minutes there's going to be a build. Please use pip install --upgrade --pre pybuilder.

@arcivanov did you see my previous comment about the next error that happens once you solve this one? On line 274? Its going to be another pathing issue?
I will install that new build tho and test regardless. Thanks so much for your help

I'll have to create a different issue for that part of the code affects a lot of places and needs to be looked at more thoroughly.

@arcivanov Man I'm sorry. I feel bad but that wasn't any good either
BUILD FAILED - [Errno 2] No such file or directory: 'c:\\Users\\jcorson\\pythonWorkspace\\halo-lambda-lib\\target\\reports\\distutils\\sdist__upload__-r__http_//<IP_ADDRESS>_8080'

the // is invalid on windows

Ok, well, at least it's an easy fix. I'll get it in the next one.

related to #392

@nexeh in a few minutes try pip install --upgrade --pre pybuilder

This fixes this issue and now exposes the second issue that i mentioned
BUILD FAILED - [Error 267] The directory name is invalid

@nexeh which one? What is the directory name?
#392 should've fixed all the path and invalid character problems you've mentioned so far.

@arcivanov OH wow. sorry i didnt see you spin up that issue and resolve it till just now. Let me go put in some print statements because it doesnt tell me now that i replaced my copy with your latest.

@arcivanov c:\users\jcorson\pythonworkspace\projectNameHere\target\dist\projectNameHere-0.0.2 Im not sure the issue now...

←[2m[DEBUG]←[0;0m project.expand_path($dir_dist) c:\users\jcorson\pythonworkspace\projectNameHere\target\dist\projectNameHere-0.0.2
Traceback (most recent call last):
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\cli.py", line 403, in main
    environments=options.environments, tasks=arguments)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\reactor.py", line 128, in build
    return self.build_execution_plan(tasks, execution_plan)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\reactor.py", line 170, in build_execution_plan
    reactor=self)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\execution.py", line 351, in execute_execution_plan
    summaries.append(self.execute_task(task, **keyword_arguments))
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\execution.py", line 298, in execute_task
    task.execute(self.logger, keyword_arguments)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\execution.py", line 169, in execute
    executable.execute(argument_dict)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\execution.py", line 100, in execute
    self.callable(*arguments)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\plugins\python\distutils_plugin.py", line 239, in upload
    execute_distutils(project, logger, upload_cmd_line, True)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\plugins\python\distutils_plugin.py", line 275, in execute_distutils
    return_code = _run_process_and_wait(commands, project.expand_path("$dir_dist"), output_file)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\plugins\python\distutils_plugin.py", line 532, in _run_process_and_wait
    shell=False)
  File "c:\python27\Lib\subprocess.py", line 710, in __init__
    errread, errwrite)
  File "c:\python27\Lib\subprocess.py", line 958, in _execute_child
    startupinfo)
WindowsError: [Error 267] The directory name is invalid
------------------------------------------------------------
←[1;31mBUILD FAILED - [Error 267] The directory name is invalid
←[0;0m------------------------------------------------------------

what about console output above the last debug message?

$ pyb -X upload
←[1mPyBuilder version 0.11.10.dev20160826161334
←[0;0mBuild started at 2016-08-26 12:50:35
------------------------------------------------------------
←[2m[DEBUG]←[0;0m Loading project module from c:\Users\jcorson\pythonWorkspace\projectNameHere\build.py
←[2m[DEBUG]←[0;0m Loading plugin 'python.core'
←[2m[DEBUG]←[0;0m Trying to load builtin plugin 'python.core'
←[2m[DEBUG]←[0;0m Loading plugin 'core'
←[2m[DEBUG]←[0;0m Trying to load builtin plugin 'core'
←[2m[DEBUG]←[0;0m Found builtin plugin 'pybuilder.plugins.core_plugin'
←[2m[DEBUG]←[0;0m Found task 'clean' with dependencies []
←[2m[DEBUG]←[0;0m Registering task 'clean'
←[2m[DEBUG]←[0;0m Found task 'compile_sources' with dependencies [prepare]
←[2m[DEBUG]←[0;0m Registering task 'compile_sources'
←[2m[DEBUG]←[0;0m Registering initializer 'init'
←[2m[DEBUG]←[0;0m Found task 'install' with dependencies [package, publish(optional)]
←[2m[DEBUG]←[0;0m Registering task 'install'
←[2m[DEBUG]←[0;0m Found task 'package' with dependencies [compile_sources, run_unit_tests(optional)]
←[2m[DEBUG]←[0;0m Registering task 'package'
←[2m[DEBUG]←[0;0m Found task 'prepare' with dependencies []
←[2m[DEBUG]←[0;0m Registering task 'prepare'
←[2m[DEBUG]←[0;0m Found task 'print_module_path' with dependencies []
←[2m[DEBUG]←[0;0m Registering task 'print_module_path'
←[2m[DEBUG]←[0;0m Found task 'print_scripts_path' with dependencies []
←[2m[DEBUG]←[0;0m Registering task 'print_scripts_path'
←[2m[DEBUG]←[0;0m Found task 'publish' with dependencies [package, verify(optional)]
←[2m[DEBUG]←[0;0m Registering task 'publish'
←[2m[DEBUG]←[0;0m Found task 'run_integration_tests' with dependencies [package]
←[2m[DEBUG]←[0;0m Registering task 'run_integration_tests'
←[2m[DEBUG]←[0;0m Found task 'run_unit_tests' with dependencies [compile_sources]
←[2m[DEBUG]←[0;0m Registering task 'run_unit_tests'
←[2m[DEBUG]←[0;0m Found task 'verify' with dependencies [run_integration_tests]
←[2m[DEBUG]←[0;0m Registering task 'verify'
←[2m[DEBUG]←[0;0m Found builtin plugin 'pybuilder.plugins.python.core_plugin'
←[2m[DEBUG]←[0;0m Registering initializer 'init_python_directories'
←[2m[DEBUG]←[0;0m Found task 'package' with dependencies []
←[2m[DEBUG]←[0;0m Registering task 'package'
←[2m[DEBUG]←[0;0m Loading plugin 'python.install_dependencies'
←[2m[DEBUG]←[0;0m Trying to load builtin plugin 'python.install_dependencies'
←[2m[DEBUG]←[0;0m Found builtin plugin 'pybuilder.plugins.python.install_dependencies_plugin'
←[2m[DEBUG]←[0;0m Found action create_install_log_directory
←[2m[DEBUG]←[0;0m Registering action 'create_install_log_directory'
←[2m[DEBUG]←[0;0m Registering initializer 'initialize_install_dependencies_plugin'
←[2m[DEBUG]←[0;0m Found task 'install_build_dependencies' with dependencies []
←[2m[DEBUG]←[0;0m Registering task 'install_build_dependencies'
←[2m[DEBUG]←[0;0m Found task 'install_dependencies' with dependencies []
←[2m[DEBUG]←[0;0m Registering task 'install_dependencies'
←[2m[DEBUG]←[0;0m Found task 'install_runtime_dependencies' with dependencies []
←[2m[DEBUG]←[0;0m Registering task 'install_runtime_dependencies'
←[2m[DEBUG]←[0;0m Found task 'list_dependencies' with dependencies []
←[2m[DEBUG]←[0;0m Registering task 'list_dependencies'
←[2m[DEBUG]←[0;0m Loading plugin 'python.distutils'
←[2m[DEBUG]←[0;0m Trying to load builtin plugin 'python.distutils'
←[2m[DEBUG]←[0;0m Found builtin plugin 'pybuilder.plugins.python.distutils_plugin'
←[2m[DEBUG]←[0;0m Found action build_binary_distribution
←[2m[DEBUG]←[0;0m Registering action 'build_binary_distribution'
←[2m[DEBUG]←[0;0m Registering initializer 'initialize_distutils_plugin'
←[2m[DEBUG]←[0;0m Found task 'install' with dependencies []
←[2m[DEBUG]←[0;0m Registering task 'install'
←[2m[DEBUG]←[0;0m Found task 'upload' with dependencies []
←[2m[DEBUG]←[0;0m Registering task 'upload'
←[2m[DEBUG]←[0;0m Found action write_manifest_file
←[2m[DEBUG]←[0;0m Registering action 'write_manifest_file'
←[2m[DEBUG]←[0;0m Found action write_setup_script
←[2m[DEBUG]←[0;0m Registering action 'write_setup_script'
←[2m[DEBUG]←[0;0m Loading plugin 'python.flake8'
←[2m[DEBUG]←[0;0m Trying to load builtin plugin 'python.flake8'
←[2m[DEBUG]←[0;0m Found builtin plugin 'pybuilder.plugins.python.flake8_plugin'
←[2m[DEBUG]←[0;0m Found task 'analyze' with dependencies [prepare]
←[2m[DEBUG]←[0;0m Registering task 'analyze'
←[2m[DEBUG]←[0;0m Found action assert_flake8_is_executable
←[2m[DEBUG]←[0;0m Registering action 'assert_flake8_is_executable'
←[2m[DEBUG]←[0;0m Registering initializer 'initialize_flake8_plugin'
←[2m[DEBUG]←[0;0m Have loaded plugins python.core, core, python.install_dependencies, python.distutils, python.flake8
←[2m[DEBUG]←[0;0m Registering initializer 'initialize'
←[2m[DEBUG]←[0;0m Found task 'run_unit_tests' with dependencies []
←[2m[DEBUG]←[0;0m Registering task 'run_unit_tests'
←[2m[DEBUG]←[0;0m Adding 'prepare' as a dependency of task 'compile_sources'
←[2m[DEBUG]←[0;0m Adding 'package' as a dependency of task 'install'
←[2m[DEBUG]←[0;0m Adding 'publish(optional)' as a dependency of task 'install'
←[2m[DEBUG]←[0;0m Adding 'compile_sources' as a dependency of task 'package'
←[2m[DEBUG]←[0;0m Adding 'run_unit_tests(optional)' as a dependency of task 'package'
←[2m[DEBUG]←[0;0m Adding 'package' as a dependency of task 'publish'
←[2m[DEBUG]←[0;0m Adding 'verify(optional)' as a dependency of task 'publish'
←[2m[DEBUG]←[0;0m Adding 'package' as a dependency of task 'run_integration_tests'
←[2m[DEBUG]←[0;0m Adding 'compile_sources' as a dependency of task 'run_unit_tests'
←[2m[DEBUG]←[0;0m Adding 'run_integration_tests' as a dependency of task 'verify'
←[2m[DEBUG]←[0;0m Adding 'prepare' as a dependency of task 'analyze'
←[2m[DEBUG]←[0;0m Adding before action 'create_install_log_directory' for task 'install_build_dependencies'
←[2m[DEBUG]←[0;0m Adding before action 'create_install_log_directory' for task 'install_runtime_dependencies'
←[2m[DEBUG]←[0;0m Adding before action 'create_install_log_directory' for task 'install_dependencies'
←[2m[DEBUG]←[0;0m Adding before action 'build_binary_distribution' for task 'publish'
←[2m[DEBUG]←[0;0m Adding after action 'write_manifest_file' for task 'package'
←[2m[DEBUG]←[0;0m Adding after action 'write_setup_script' for task 'package'
←[2m[DEBUG]←[0;0m Adding after action 'assert_flake8_is_executable' for task 'prepare'
←[2m[DEBUG]←[0;0m Verbose output enabled.

←[2m[DEBUG]←[0;0m Executing initializer 'init' from 'pybuilder.plugins.core_plugin'
←[2m[DEBUG]←[0;0m Executing initializer 'init_python_directories' from 'pybuilder.plugins.python.core_plugin'
←[2m[DEBUG]←[0;0m Executing initializer 'initialize_install_dependencies_plugin' from 'pybuilder.plugins.python.install_dependencies_plugin'
←[2m[DEBUG]←[0;0m Executing initializer 'initialize_distutils_plugin' from 'pybuilder.plugins.python.distutils_plugin'
←[2m[DEBUG]←[0;0m Executing initializer 'initialize_flake8_plugin' from 'pybuilder.plugins.python.flake8_plugin'
←[2m[DEBUG]←[0;0m Executing initializer 'initialize' from 'build'
←[2m[DEBUG]←[0;0m Project properties:
                                 basedir : c:\Users\jcorson\pythonWorkspace\projectNameHere
                                dir_dist : $dir_target/dist/projectNameHere-0.0.2
                        dir_dist_scripts : scripts
                        dir_install_logs : $dir_logs/install_dependencies
                                dir_logs : $dir_target\logs
                             dir_reports : $dir_target\reports
                  dir_source_main_python : src/main/python
                 dir_source_main_scripts : src/main/scripts
                              dir_target : target
                   distutils_classifiers : ['Development Status :: 3 - Alpha', 'Programming Language :: Python']
               distutils_command_options : None
                      distutils_commands : ['sdist', 'bdist_wheel']
  distutils_issue8876_workaround_enabled : False
             distutils_upload_repository : http://<IP_ADDRESS>:8080
                   distutils_upload_sign : False
          distutils_upload_sign_identity : None
                distutils_use_setuptools : True
                      flake8_break_build : False
                 flake8_exclude_patterns : None
                 flake8_include_patterns : None
                  flake8_include_scripts : False
             flake8_include_test_sources : False
                  flake8_max_line_length : 120
    install_dependencies_extra_index_url : None
          install_dependencies_index_url : None
install_dependencies_insecure_installation : []
      install_dependencies_local_mapping : {}
       install_dependencies_trusted_host : None
            install_dependencies_upgrade : False
                                 verbose : True
←[2m[DEBUG]←[0;0m Execution plan is upload
←[1m[INFO] ←[0;0m Building projectNameHere version 0.0.2
←[1m[INFO] ←[0;0m Executing build in c:\Users\jcorson\pythonWorkspace\projectNameHere
←[1m[INFO] ←[0;0m Going to execute task upload
←[2m[DEBUG]←[0;0m Executing task 'upload'
←[2m[DEBUG]←[0;0m Executing subtask from pybuilder.plugins.python.distutils_plugin
←[1m[INFO] ←[0;0m Uploading project projectNameHere-0.0.2 to repository 'http://<IP_ADDRESS>:8080'
←[2m[DEBUG]←[0;0m Executing distutils command ['sdist', 'upload', '-r', 'http://<IP_ADDRESS>:8080']
←[2m[DEBUG]←[0;0m project.expand_path($dir_dist) c:\users\jcorson\pythonworkspace\projectNameHere\target\dist\projectNameHere-0.0.2
Traceback (most recent call last):
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\cli.py", line 403, in main
    environments=options.environments, tasks=arguments)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\reactor.py", line 128, in build
    return self.build_execution_plan(tasks, execution_plan)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\reactor.py", line 170, in build_execution_plan
    reactor=self)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\execution.py", line 351, in execute_execution_plan
    summaries.append(self.execute_task(task, **keyword_arguments))
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\execution.py", line 298, in execute_task
    task.execute(self.logger, keyword_arguments)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\execution.py", line 169, in execute
    executable.execute(argument_dict)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\execution.py", line 100, in execute
    self.callable(*arguments)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\plugins\python\distutils_plugin.py", line 239, in upload
    execute_distutils(project, logger, upload_cmd_line, True)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\plugins\python\distutils_plugin.py", line 275, in execute_distutils
    return_code = _run_process_and_wait(commands, project.expand_path("$dir_dist"), output_file)
  File "c:\users\jcorson\pythonworkspace\projectNameHere\venv\lib\site-packages\pybuilder\plugins\python\distutils_plugin.py", line 532, in _run_process_and_wait
    shell=False)
  File "c:\python27\Lib\subprocess.py", line 710, in __init__
    errread, errwrite)
  File "c:\python27\Lib\subprocess.py", line 958, in _execute_child
    startupinfo)
WindowsError: [Error 267] The directory name is invalid
------------------------------------------------------------
←[1;31mBUILD FAILED - [Error 267] The directory name is invalid
←[0;0m------------------------------------------------------------


OneWayToSource binding causes StackOverflow

Using 0.8.999-cibuild0003713-beta I get a StackOverflowException if I use OneWayToSource binding to a control property
Here is a very simple repo using just a TextBox in the MainWindow with OneWayToSource  binding
App12.zip

You sure it is fixed? I still a StackOverflow while binding the HorizontalScrollBarMaximum using OneWaytoSource. I use the newest nightly

Is it fixed for you @aguahombre ?
Maybe it's a different issue, @HendrikMennen ? Could we get a repro?

It appears to be fixed in 0.8.999-cibuild0004187-beta.
My repo now runs without a StackOverflowException.
From: Steven Kirk<EMAIL_ADDRESS>Sent: 19 September 2019 08:10
To: AvaloniaUI/Avalonia<EMAIL_ADDRESS>Cc: David Waterman<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [AvaloniaUI/Avalonia] OneWayToSource binding causes StackOverflow (#2912)
Is it fixed for you @aguahombrehttps://github.com/aguahombre ?
Maybe it's a different issue, @HendrikMennenhttps://github.com/HendrikMennen ? Could we get a repro?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/AvaloniaUI/Avalonia/issues/2912?email_source=notifications&email_token=AEGGYRHEJPMI264GUSWKIPLQKMQV3A5CNFSM4ISOFICKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7COW4I#issuecomment-532999025, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEGGYRAKUICDOTONNMLRDY3QKMQV3ANCNFSM4ISOFICA.


Add an option to CLI to directly render templates

Awesome project!
I would like to import the rendered emails into my rust application, so I can not use the @react-email/render utility. It would be great if the CLI had a email build option that would build all the components and spit them out to a configurable location.
My current workaround in a custom script.

Any chance of updating here or syncing Discord to this? I'm interested in this but I don't want to sign up to Discord to understand what's happening

@bukinoshita use-case is that we want to pre-compile email templates in our CI pipeline.
We're running a Ruby on Rails app that uses its own mailer system, so we wanted to build our layouts in react-email and then export them into the Rails pipeline as templates, where we then interpolate context specific values.
We can't do that, of course, so someone has to manually spin up the react-email dev server and then view source in the browser to copy the output and paste it into our layout, and then manually review the result to replace the template variables.
I'd like to ask what you're investigating, because what we're looking at is just writing the email output to a file and not to an API or dev server.


Invalid Euler angles on zero scale

The way Euler angles are calculated, produces an invalid result, if the scale is set to zero. Repro:
entity.setLocalScale(0, 0, 0);
entity.setEulerAngles(10, 10, 10);

console.log(entity.getEulerAngles()); // Vec3 { x: NaN, y: NaN, z: 0 }

The use case:
We have some items spawn in the world in a little animation, which scales them from zero to normal size.

Well both rotation and scale share the 3x3 part of the Matrix4 .. and if you set scale to 0,0,0, whole 3x3 part is just zeros. So no angles are preserved.
We could do a more complicated solution perhaps that would try and keep rotation in a separate Quaternion or similar, but it's not likely worth the cost.
So the best we can do in the meantime I think is to return 0,0,0 instead of NaN, NaN, Nan.
Perhaps your animation needs to store and animate rotation / scale / translation independently if you need to handle scale of 0.

Right, so, currently I simply override the vector components to zero if one of them is of NaN value on the getEulerAngles() return.
The problem came up when one wants to add some eulers to the current eulers. After an entity gets reset, that addition breaks the math. When the scale is zero, the rotation is of no importance, but when the scale becomes larger than zero on the next frame, then it should be possible to accumulate eulers. Giving an inital value of zero would allow it. I think returning zeros and documenting it in getEulerAngles() API docs would be a good resolution to this.

NaN related issues with math, are sometimes an issue. Perhaps with DEBUG build, there could be a check.
I've caught myself many times, where after some math, I get NaN's. And due to amounts of code, the only way to find out what was a problem, is to insert dozens console.logs in between math ops. Just to nail down the source of an issue.
Perhaps a warning check in DEBUG build, which would check for NaN values could help to straight away find out that there is an issue after specific math operation due to provided inputs.


Structure Large Applications in Flask Using Blueprints and Flask Application Factory

Proposed title of article
Structure Large Applications in Flask Using Blueprints and Flask Application Factory
Introduction paragraph (2-3 paragraphs):
This article will explain and illustrate how to structure web applications on a large scale with the Python Flask backend web framework.
Key takeaways:

Work Environment Setup
Understanding and implementing Blueprints and Application Factory
Working with configuration and environment variable
Summary and Conclusion

References:
N/A

seems like a helpful topic - lets please be sure it add value beyond what is in the official docs and that it does not overlap with any existing EngEd articles or incoming topic suggestions (if you haven't already). - approved @corpsgeek
Also FYI - we encourage students to use these topic forms as a skeleton to start writing the intro paragraphs to their articles

alright @hectorkambow noted

would like to inform you that I'm currently working on this article and almost done @hectorkambow. Very active.


Update of Roles from Keycloak to Superset is not working

When we add roles to the existing user in keycloak, then the roles are not getting updated in superset.
Roles are not getting synchronized between keycloak and superset.
How to reproduce the bug

Go to Keycloak and add a superset role to an existing user
Login to superset and verify newly added roles
You will not find the roles updated/added

Expected results
Roles should be synchronized between keycloak and superset for an existing user in keycloak
Actual results
Roles are not getting synchronized between keycloak and superset.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
(please complete the following information):

browser type and version: Chrome Browser 103.0.5060.114
superset version: 1.4.0
python version: 3.8.12
node.js version: 14

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[Y] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[Y] I have reproduced the issue with at least the latest released version of superset.
[Y] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Can you try with 2.0 please? Also, make sure the feature flag AUTH_ROLES_SYNC_AT_LOGIN is set to true and the user logs out and in again.

After enabling AUTH_ROLES_SYNC_AT_LOGIN = True also still facing the same issue.
Is there any other configuartion to be made to sync keycloak user roles to superset.

@avinash-Github Please share if you found any resolution.

AUTH_ROLES_SYNC_AT_LOGIN

@MM-Lehmann - I have tried this, but still facing the issue. Not able to see keycloak roles in superset, Can you please help?

Closing this as stale since it's been silent for so long with no response to the last suggested approach, and we're trying to steer toward a more actionable Issues backlog. If people are still encountering this in current versions (currently 3.x) please re-open this issue, open a new Issue with updated context, or raise a PR to address the problem. Thanks!


(Q) Output status of node

Hi,
is there any way to get continous status output ("ready", "please visit ip:3456")?
I would like to send me a message, when the node needs the amazon site to be visited again.
Thanks!

It's been almost 5 months since this has been asked but I did something similar to this today so figured I'd share.
You can use the status node to achieve this

Configure it to listen to the status of the On Device Activity node

From there you can access the text through msg.status.text
I have an automation that listens for status updates and opens the link in a new tab so I can reauthenticate when needed.

[{"id":"c8505ea0.55aa2","type":"switch","z":"8126516b.4586e","name":"","property":"msg.status.text","propertyType":"msg","rules":[{"t":"eq","v":"open <IP_ADDRESS>:3456 in your browser","vt":"str"},{"t":"eq","v":"no JSON","vt":"str"}],"checkall":"true","repair":false,"outputs":2,"x":1370,"y":80,"wires":[["ea2cd8b1.9f4aa8"],["37432305.4756ec"]]},{"id":"ea2cd8b1.9f4aa8","type":"exec","z":"8126516b.4586e","command":"ssh mbp 'open -a \"Google Chrome\" http://<IP_ADDRESS>:3456/'","addpay":false,"append":"","useSpawn":"false","timer":"","oldrc":false,"name":"","x":1690,"y":40,"wires":[[],[],[]]},{"id":"82418c6e.87d27","type":"status","z":"8126516b.4586e","name":"","scope":["bfb8b7f0.c4eb68"],"x":1120,"y":80,"wires":[["5c47c198.3d94c"]]},{"id":"5c47c198.3d94c","type":"rbe","z":"8126516b.4586e","name":"","func":"rbe","gap":"","start":"","inout":"out","property":"status.text","x":1250,"y":80,"wires":[["c8505ea0.55aa2"]]},{"id":"37432305.4756ec","type":"api-call-service","z":"8126516b.4586e","name":"","server":"59830e87.88141","version":1,"debugenabled":false,"service_domain":"notify","service":"mobile_app_craigs_iphone","entityId":"","data":"{ \"message\": \"Failed to setup node-red-contrib-alexa-remote2\" }","dataType":"json","mergecontext":"","output_location":"","output_location_type":"none","mustacheAltTags":false,"x":1610,"y":120,"wires":[[]]},{"id":"59830e87.88141","type":"server","z":"","name":"Home Assistant","legacy":false,"addon":false,"rejectUnauthorizedCerts":true,"ha_boolean":"y|yes|true|on|home|open","connectionDelay":true,"cacheJson":true}]


Add engine mode 4

The engine mode 4 is just to replace everything with one block like stone so it appears to be absolutely nothing

You are basically describing engine mode 1. The reason you can still see blocks in engine mode 1 is that ores next to air can't be replaced with stone, otherwise legit players wont be able to see exposed ores either. To hide all ores an approach like #16 is required, which is rather complicated and computationally expensive!


Merge main into develop for 1.0.0

Codecov Report

Merging #8 (7d7405c) into develop (058a26c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           develop        #8   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           16        16
  Lines          234       234
=========================================
  Hits           234       234

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 058a26c...7d7405c. Read the comment docs.


MINOR: Add GitHub Action status badge to README

What changes were proposed in this pull request?
This PR aims to add the GitHub action status badge to README.md.

https://github.com/williamhyun/orc/blob/badge/README.md#orc-file-library

Why are the changes needed?
This will increase the visibility of the build status.
How was this patch tested?
N/A

cc: @dongjoon-hyun @pgaref

Hi, @williamhyun . Feel free to merge this as a committer. :)


Re-render with conda-smithy version 1.0.0

This is a re-rendering generated with conda-smithy version 1.0.0.
It provides a fix so that the Travis CI build will be skipped in this feedstock as this is Linux only currently. If this changes, update the skip conditions in the recipe and re-render.
Also it starts using conda-forge-build-setup to handle standard CI setup like what version of conda-build is used. This should allow us to more quickly get out in front of build issues that generally affect feedstocks.
Letting you know @pelson that I'm taking this for a spin.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge/libgsasl - I took a look at the changes and this looks good, so merging. Hope you don't mind.


refactor: adjust sorting logic

As far as the DEX transactions (swap, provide liquidity) are both OUT and IN (you send token and receive token) I would suggest that at the moment filtering logic should be:
ALL: show all transactions;
OUT: show Spend Out + DEX transactions;
IN: show all Spend In + DEX transactions;
DEX: show only the DEX transactions.
On the other hand from user's perspective it might be expected and more useful if the DEX transactions are excluded from IN and OUT filtering lists. We need to make some extra research about this one, @paolomolo.


org setings: Users: "Last active" sort doesn't work

In Chrome 83 on Mac OS X, under Settings> Organization > Users, trying to sort the list by "Last active" seems to actually sort by Name, rather than by last active:

@showell can you take point on this?

@zulipbot claim


Fix df.quantile on all missing data

[x] Closes #2792
[x] Tests added / passed
[x] Passes black dask / flake8 dask / isort dask

rerun tests

This change is pretty weird, but it's such a niche situation that it feels ok to me. What do you think @jcrist or @jrbourbeau?

The failures are probably related to github action being a little iffy this morning.


Feature/prevent double voting v2

I redid the PR to prevent merging issues and did some things differently this time:

We also check if the poll was answered in ParticipantMenu>>sendAnswer in case the menu doesn't close properly. This isn't too Squeaky, but I like to play it save. What do you think?

Other controversial things about this PR

We use global state (ParticipantMenu class>> answeredPollIds), so that the already answered IDs are kept persistently and re-opening the StartMenu doesn't allow for another vote. We feel like this is in line with "Someone shouldn't be able to cheat on a single image without tampering with the code", which is how we understood the task.
We added a test for this, which is quite close to being a UI test, which might cause people to think we want to do UI tests

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

9 of 15 (60.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+7.2%) to 46.591%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/Liquid-Core.package/LiquidStartMenu.class/instance/enterParticipantMode.st
0
6
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
7.2%

Covered Lines:
369

Relevant Lines:
792

💛  - Coveralls


Travis build failing even for valid PRs

Travis builds are failing for each PRs. Here's the issues from travis job config:
Issues :-(

> Links

  1. [L001]  https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg SSL_connect returned=1 errno=0 state=error: certificate verify failed

  2. [L011]  https://plugins.cakephp.org SSL_connect returned=1 errno=0 state=error: certificate verify failed

  3. [L448]  https://puphpet.com/ Connection timed out - connect(2) for "puphpet.com" port 443

  4. [L449]  https://puppetlabs.com/ SSL_connect returned=1 errno=0 state=error: certificate verify failed

  5. [L482] 403 http://forum.cakephp.ir/

We could remove dead links or whitelist URLs of partially valid links.

Travis build are passing now.


[Bug] Logical assignments in JS are incorrectly beautified

Description
The tool incorrectly beautifies logical AND, OR and NULL assignments.
Links:

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Logical_OR_assignment
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Logical_AND_assignment
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Logical_nullish_assignment

Input
The code looked like this before beautification:
x&&=y
x||=y
x??=y

Expected Output
The code should have looked like this after beautification:
x &&= y
x ||= y
x ??= y

Actual Output
The  code actually looked like this after beautification:
x && = y
x || = y
x ?? = y

Steps to Reproduce

Opened https://beautifier.io/
Entered the input text
Clicked "Beautify Code" button

I am new to the repo but would be happy to work on this issue

@bitwiseman What is the process for closing issues in the project? I noticed that we released some issues but they weren't closed like this one. In addition, what is the update process for the website (https://beautifier.io/) I noticed that this issue still doesn't work on the site.

@mhnaeem
Thanks for calling attention to this.  It looks like github pages publishing action is failing in beautifier/beautifier.io project: https://github.com/beautifier/beautifier.io/actions/runs/2059622873
I'll take a look at it some time this week.


Parsing file from stdin?

I try formatting via xmllint --format but to no avail. xmllint accepts input either via filename (last position on command-line) or via stdin. Then the typical "-" must be added. I tried with and without "-". I also tried setting shell to true and put all into a single string ("xmllint --format" with and without "-") but that tries to parse the whole string as the command's path/name, which, of course, breaks.
If I leave out the "-", then I get the usage message of the xmllint command in return (but nothing else). If I add the "-" then nothing happens and FitlerPipes signals: Nothing changed. So, currently I have this:
{
  "caption": "FilterPipes: Format XML (xmllint)",
  "command": "filter_pipes_process",
  "args": { "command": ["xmllint", "--format", "-"] }
}

but that does not work out as I would have expected. As a sidenote: I am on Win10 with Cygwin installed (that's the verision of xmllint I use). Thanks.

I copy-pasted your configuration exactly into my .sublime-commands file on my OSX machine, and it worked perfectly. So I think you have the right idea, but I think that something about your environment is getting in the way.
Try bringing up the console window in sublime (typically CTRL`) to see the error it produces if it fails.
If FilterPipes says "No change", then that means that the command succeeded, and the output it produced is exactly equal to the input you sent to it, such as you'd get by sending the content through /bin/cat. Otherwise, if the command returns a non-zero status code (e.g. like you get with /bin/false), then the message will say that the command failed. And if the command returns a zero status code but doesn't output any content (e.g. /bin/true), then your selection will be replaced with no content (e.g. it'll be deleted).
One other thing to try to make sure that selections aren't getting in the way is to set "use_selections": false in your args, which will send the whole file through your command even if you have part of the file selected.
Finally, I'd suggest making sure that you're not sending xmllint a properly-formatted doc to start with. Otherwise you'd expect there to be no change, which is what it sounds like is happening.

Hmmm...today I just tested it again and it worked. So I close this as one of those "close encounters with the paranormal" non-issues. Thank you for investigating. I still don't understand what happened. All I did was to put the machine into standby for a few hours...

Ah, just had to come back at it, can't keep it to myself any longer: I just wanted to express my gratitude for this super-nifty little package :^) Thanks a lot!


Unable to create _metadata

Summary
Unable to create _metadata
Can you combine those 1,2,3,... small json files into one _metadata.
or run the program just to create _metadata.
Because I made 200,000 more and it looks like the JSON.stringify serialization function seems to have a limit, so could you add a feature to combine those 1,2,3,... files into a file like _metadata.
Until now I haven't been able to solve the problem even using the @bolshoytoster fork.
And can you add a program for the _metadata file to be converted into an excel file like .csv or .xls.
Thank you @bolshoytoster
Basic example
RangeError: Invalid string length
at JSON.stringify ()
at startCreating (D:\hashlips_art_engine-main\src\main.js:552:22)
at D:\hashlips_art_engine-main\index.js:8:3
at Object. (D:\hashlips_art_engine-main\index.js:9:3)
at Module._compile (node:internal/modules/cjs/loader:1155:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
at Module.load (node:internal/modules/cjs/loader:1033:32)
at Function.Module._load (node:internal/modules/cjs/loader:868:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:22:47
Motivation
In order to be able to create more artwork and overcome the limitations that JSON.stringify has in creating _metadata.
And for excel to make it easier to collect data and edit _metadata and be able to convert it back into a .json file.

still can not and still displays it
RangeError: Invalid string length
at Array.join ()
at startCreating (D:\hashlips_art_engine-main\src\main.js:552:71)
at D:\hashlips_art_engine-main\index.js:8:3
at Object. (D:\hashlips_art_engine-main\index.js:9:3)
at Module._compile (node:internal/modules/cjs/loader:1155:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
at Module.load (node:internal/modules/cjs/loader:1033:32)
at Function.Module._load (node:internal/modules/cjs/loader:868:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:22:47
I see from the stackoverflow answer link that @boob sent there that it says you can use JSONStream stringify.
How to use the JSONStream stringify?
Can it be added in the JSONStream function or added for utils in hashlips_art_engine?
I was hoping @bolshoytoster  could make the function work around JSONStream limits on creating large _metadata on processing large numbers of objects.
Thank you @bolshoytoster for creating the function JSONStream

@mupadi

RangeError: Invalid string length

I think it's just a limitation with javascript then.

How to use the JSONStream stringify?

Run npm install JSONStream, then replace the line ~552 (the one you changed earlier) with:
  var JSONStream = require( "JSONStream" );

  var transformStream = JSONStream.stringify();
  var outputStream = fs.createWriteStream(`${buildDir}/json/_metadata.json`);
  transformStream.pipe(outputStream);
  metadataList.forEach(transformStream.write);
  transformStream.end();

I've also added this to the repo, so you could just redownload instead.


Switching delimiters to 1.234,56?

I have several numeral inputs beneath each other, with values ranging from thousands to fractions with decimals. Since I'm in the EU, I want to display numbers as 1.234,56. If I read the docs correctly, to do this requires setting numeralDecimalMark to ,, and the delimiter to ..
However, when I set the numeralDecimalMark to a comma, it completely misreads the fraction values.
0.9142857142857143 becomes 09,142,857,142,857,143 rather than 0,91.
These are my options:
{ numeral: true, numericOnly: true, numeralDecimalScale: 2, numeralDecimalMark: ',' delimiter: '.', stripLeadingZeroes: false, }
Did I miss something or is it really difficult to switch the delimiters?
FYI: I'm using React 16.3 and cleave.js 1.3.3
Thanks!

Sorry for the delayed response.
How the decimal mark works is: it has to have the correct decimal mark setup in the string so the lib can format it, that is to say, to make it show as 0,91, 0,91xxx has to be set as raw value, and when you call getRawValue, you will probably get 0,91 rather than 0.91.

@lcvbeek thank you so much, you saved my time.

Archive this, cheers.


[FR?] Uploading reports as archive

This is either a feature request, or a documentation request.
The native https://github.com/codecov/codecov-bash uploads
each report separately, which doesn't quite scale well with
large report number. I'm seeing that the upload takes
an extremely long time. It would perhaps be good to be able
to archive the reports first, and upload them in one go.
Is that something that can be done?
X-Ref https://github.com/codecov/codecov-action/issues/324

(closing out as a duplicate on the mentioned issue)

... could you please bother to actually reply to the issue?

Thank you for a very helpful reply!
The answer i was looking for: "your problem is elsewhere, we already do that: https://github.com/codecov/codecov-bash/blob/965008c97d649721850b9ff0de3f71e9b8adeb71/codecov#L1796-L1798"


Sink ref and uri cannot be used together

Knative sinks have ref and uri properties which allow making combined uri like in example below:
  sink:
    ref:
      apiVersion: v1
      kind: Service
      namespace: default
      name: mysink
    uri: /extra/path

Some TriggerMesh sources don't allow that. For example AWSSQSSource has "oneOf" set in spec:
  oneOf:
  - required: [ref]
  - required: [uri]

AWSSQSSource yaml
Setting it to "anyOf" helps and works fine.
Is it done by intention or is it a mistake?

Hi @Kaiass
That is a mistake, thanks for noticing.
We will fix that, unless you want to contribute a PR.

Hello @odacremolbap !
Created a pull request. (I did a mistake by committing this to the other PR but reverted the commit now)


Additional examples consistent with RFC-5321 Mailbox grammar.

I think these tests are consistent with the 2020-12 draft that specifically references RFC-5321 Mailbox syntax as the basis for validation.

Sounds like @awwright is happy with these -- can you add them to draft-next too? And sorry about the delay.

Sounds like @awwright is happy with these -- can you add them to draft-next too? And sorry about the delay.

Is this something I should do?  Not sure how, don't see any draft-next stuff... Happy to do whatever if somebody shows me how.

Yes! Essentially just add the same test cases to https://github.com/json-schema-org/JSON-Schema-Test-Suite/blob/master/tests/draft-next/optional/format/email.json -- let me know if you still need more guidance, apologies for the terseness!

There's a few more tests that I could suggest here, for example<EMAIL_ADDRESS>should be invalid (trailing dot, a valid domain name but illegal in an email address). But we can merge those in after this, if we have to.

let me know if you still need more guidance, apologies for the terseness!

I hope this is right, let me know if you need anything else. I'm happy about this!

Is it possible to rebase or squash PR? I'm not sure why it's pulling in 105 commits, that's a little confusing.

Is it possible to rebase or squash this PR? I'm not sure why it's pulling in 105 commits, that's a little confusing.

Yeah, sorry about that. How about all in one commit?

Is there anything more I can do to help get this merged?

Thanks, looks great! Sorry it took so long :(

The format vocabulary didn't change in draft2020-12 -- so shouldn't these tests also appear for earlier drafts as well?

I took

that specifically references RFC-5321 Mailbox syntax

to mean that what changed was whether an explicit reference was there or not -- but if that's present in earlier drafts as well then yes!

In the September 2019 draft, Email Addresses (section 7.3.2) looked like "email:  As defined by [RFC 5322, section 3.4.1]".
But the RFC-5322 spec is for the message format, not the SMTP protocol. And that document is a bit ambiguous about allowing all kinds of white space and/or comments (in parens) which can be recursively nested.
It merely says "Comments and folding white space SHOULD NOT be used around the "@" in the addr-spec." But it allows leading and trailing comments or (folding) white space. (Also "SHOULD NOT" is not "MUST NOT")
I don't think any of the newly added tests run afoul of the old standard.
For example, the grammar in RFC-5322 would accept < (comment<EMAIL_ADDRESS>(another (nested) comment) >
And if you ignore SHOULD NOT, you can mix in more comments and white space. RFC-5322 also requires support of the "Obsolete Syntax" to be compatible all the way back to RFC-822. It was kind of a nightmare.

An example email address pulled from RFC-822 (section 3.1.4 on page 7) is looks like:
<Muhammed.(I am  the greatest) Ali @(the)Vegas.WBA>
I'm pretty sure nobody wants to allow this kind of address in their web forms.

The domain part of the address as defined by RFC-5322 allows all kinds of craziness that is not acceptable by DNS as a domain, see section 3.2.3. for the definition of dot-atom. Using only the grammar from RFC-5322 a valid email address can be:
<EMAIL_ADDRESS>or <bar@----->

Ah okay, I recall the change of RFCs in the specification revision, but at the time I thought that it was a typo correction of id numbers, not an actual intended behavioural change.

An example email address pulled from RFC-822 (section 3.1.4 on page 7) looks like: <Muhammed.(I am the greatest) Ali @(the)Vegas.WBA> I'm pretty sure nobody wants to allow this kind of address in their web forms.

This section is describing how you can encode a mail message, the parenthesized expressions are comments, they're not actually a part of the email address.

The domain part of the address as defined by RFC-5322 allows all kinds of craziness that is not acceptable by DNS as a domain

This is done for forward compatibility. This isn't really a problem because it's just handled the same as a domain name that isn't registered.

@awwright The question is what should be considered a valid email address as far as JSON schema validation is concerned? A string with the spaces and (possibly nested) comments that would have to be stripped out before using in the SMTP protocol? I argued (successfully) that to be considered a valid address, the string should conform to the grammar in RFC-5321; the specification of the SMTP protocol. This way the string could be used directly, without further processing, to send email in today's Internet. So<EMAIL_ADDRESS>-- not the string <Muhammed.(I am the greatest) Ali @(the)Vegas.WBA> which will be rejected by every MTA software program I know of.
That's why the spec was changed, and why the examples I have added should work with current versions of the JSON schema validation document.

(As a general rule, things which are SHOULD NOT are accepted / marked valid in the test suite, with an optional test suite file marking them invalid, until/unless they become MUST NOT)


GetChannelVideo using too much network

The get channel video uses up a lot of network bandwidth per request. Is there a way to get only one result (the first index of the object) insted of the entire 25 video list
Thank you

Unfortunately there is now such option. Either you take all or nothing. Because the videos are always received in a batch.


Lot of AI (Internal): [Microsoft-ApplicationInsights-Extensibility-DependencyCollector] traces logged for some apps, but not others

Hi, we are seeing a large number of the following traces logged continuously on apps deployed on one of our Azure subscriptions
AI (Internal): [Microsoft-ApplicationInsights-Extensibility-DependencyCollector] Failed to handle Azure.Core.Http.Request.Stop event, error = 'System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.ApplicationInsights.DependencyCollector.Implementation.AzureSdkDiagnosticsEventHandler.OnEvent(KeyValuePair`2 evnt, DiagnosticListener diagnosticListener)'

We have the same codebase deployed in Azure Container Apps on multiple subscriptions, the configuration for those apps are practically same, but we seem to only see the above AI (Internal) traces on apps deployed in one of our subscriptions.
The AI (Internal) traces do not appear to be directly tied to other traces, we have tried looking for correlations with ParentId/OperationId
We do use Cosmos DB and other Azure things that might be utilizing the Azure.Core, so maybe the Failed to handle Azure.Core.Http.Request.Stop event error is hinting at something related to that, but again we are not seeing this on other deployments in other subscriptions that is identical to where the errors occurs.
NuGet packages we are using:

Microsoft.ApplicationInsights
Microsoft.ApplicationInsights.AspNetCore

We are using version 2.21.0 and have also tried 2.22.0-beta3 with no luck
We need a bit of help tracking down what might cause this, we are seeing no other exceptions that hint at application insights choosing to log some "internal" traces

I am also experiencing the same issue, just want to know if any version that does not have this bug?

@JiarongGu no we did not find a solution. We ended up implementing custom telemetry processor to ignore those traces being sent to log analytics. See below. We have not looked at newer versions of the nuget packages to see if the problem has been solved.
public class IgnoreApplicationInsightsSDKTelemetryProcessor : ITelemetryProcessor
{
    private readonly ITelemetryProcessor _next;

    public IgnoreApplicationInsightsSDKTelemetryProcessor(ITelemetryProcessor next)
    {
        _next = next;
    }

    public void Process(ITelemetry item)
    {
        if (item is TraceTelemetry trace)
        {
            if (trace.Context.Operation.SyntheticSource == "SDKTelemetry")
            {
                return;
            }
        }

        _next.Process(item);
    }
}

We attempted to work with Azure support to figure out the issue, but the supporter assigned needed read access to the entire subscription that contained the log analytics workspace and that compliance nightmare was not worth it so we opted for the above solution.


Can't get id in  child_changed event firebase

Version info

Angular: None
Firebase:3.5.3
AngularFire:None
Other (e.g. Node, browser, operating system) (if applicable):expressJS :4.14.0
Test case

Steps to reproduce

Expected behavior

Actual behavior

favorite
I'm kind of new to firebase. I was just trying out some example when I came across some of its event which by the way are pretty cool.
I have saved some data in firebase database which is :
 driver
      -KV_Cj7sL6sg6K9E5ifh
         status: "Incomplete"

The thing that troubling me is that when a child is updated child_changed event is triggered. When I access it's data I'm not seeing the key with it.
I have made a node(I think a row is called a node in firebase not sure) in the driver table. When I changed the status of it to complete the child_changed event it triggered. And I receive the packet which has been updated. The thing is I want to get the Id(KV_Cj7sL6sg6K9E5ifh) too. But the problem is it's only sending me status: complete.
This is the code that I have written for child_changed:
usersRef.on("child_changed", function(data) {
   var player = data.val();
   console.log(player);
   console.log("The new status is:  "+ player.status);
});

Pleas

Cross-post and answered there: http://stackoverflow.com/questions/40381478/child-changed-event-firebase

@puf  sorry for the cross post. I just read your instruction. Sorry


Add Entrepreneur value to the list of profession options

Ticket: https://github.com/Front-End-Coders-Mauritius/frontendmu-astro/issues/130
I've tested the changes:

Browser: Brave
OS: Windows 11
Responsive screens

Checklist:

[x] Added "Entrepreneur" value in the right place
[x] Tested on normal screens
[x] Tested on tablet-size screens
[x] Tested on small screens

Full screen:

Tablet:

Small screen:

I also tested with the RSVP process on a meetup page mobile and desktop. Looks good to me.
btw @abdallahYashir could you also update the types here before we merge it ?
TS doesn't throw an error because for some reason we're currently using "as" instead of enforcing the returns. I will fix that in another PR.

merging, here comes the entrepreneurs !


initialize aws-sdk with region

I was having trouble uploading to eu-west-1 region with a 12 MB file (but not with a 3 MB file). I saw the following error on the server:
I20141106-20:25:47.891(1)? Exception in callback of async function: Error: PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. [aws.createMpu]
I20141106-20:25:47.892(1)?     at packages/lepozepo:s3/server/methods.coffee:163:16
I20141106-20:25:47.892(1)?     at runWithEnvironment (packages/meteor/dynamics_nodejs.js:108)

This led me to include the region when instantiating the AWS object from the aws-sdk package, which fixes the problem.

Updated in another commit


docs .md files populated + README updated

All the pages are populated with content in what should be its final version. Will be tagging up with Drew tomorrow to try to render it locally and proof-read/check links


fasta: redirecting factories are not resolved across platform.dill border

main() {
  new Map();
}

compiles down to
  static method main() → dynamic {
    core::Map::•<dynamic, dynamic>();
  }

However it should actually compile down to an invocation of the LinkedHashMap constructor to which the Map redirects to.
This most likely happens because RedirectingFactoryBody does not actually survive serialization/deserialization when platform.dill is generated.

Good point, I'm pretty sure I know what the problem is.


WIP: avoid that processes not matched by discovery are instrumented

Do not yet merge. Still requires polishing, unit tests and documentation.

Sounds great, just mark it when it's ready for review :)!

Codecov Report
Attention: 192 lines in your changes are missing coverage. Please review.

Comparison is base (90d39e9) 81.35% compared to head (23d71db) 41.97%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #376       +/-   ##
===========================================
- Coverage   81.35%   41.97%   -39.39%
===========================================
  Files          53       53
  Lines        4120     4148       +28
===========================================
- Hits         3352     1741     -1611
- Misses        584     2297     +1713
+ Partials      184      110       -74

Flag
Coverage Δ

integration-test
?

unittests
41.97% <6.34%> (-1.33%)
:arrow_down:

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

Files
Coverage Δ

pkg/internal/ebpf/common/ringbuf.go
79.31% <100.00%> (-5.75%)
:arrow_down:

pkg/internal/ebpf/common/spanner.go
75.60% <100.00%> (-2.32%)
:arrow_down:

pkg/internal/ebpf/httpfltr/httpfltr_transform.go
100.00% <100.00%> (ø)

pkg/internal/request/span.go
100.00% <ø> (ø)

pkg/internal/discover/finder.go
0.00% <0.00%> (-91.43%)
:arrow_down:

pkg/internal/ebpf/tracer.go
0.00% <0.00%> (ø)

pkg/internal/ebpf/goruntime/goruntime.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/internal/ebpf/gosql/gosql.go
0.00% <0.00%> (-94.12%)
:arrow_down:

pkg/internal/ebpf/grpc/grpc.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/internal/ebpf/nethttp/nethttp.go
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 3 more

... and 31 files with indirect coverage changes

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

@grcevski logging the received traces at the client side, I see that neither the Host PID nor the User PID aren't recognized, so that's why the traces are filtered out.
It's strange because the reported PIDs are always 13 (on my local docker) and there isn't any process with that ID. Maybe we aren't setting them correctly or we are pointing to a wrong memory zone in the  BPF side?

@grcevski logging the received traces at the client side, I see that neither the Host PID nor the User PID aren't recognized, so that's why the traces are filtered out.

That's interesting! The eBPF side let it go now, which means we matched it correctly based on the namespaced PID on the eBPF side, produced the event, but the user space is filtering it out. Likely the pids we collect at event generation are not right.
I also noticed one more issue at the time we run the process discovery loop. We record the active port numbers, but with client programs they will grow to large arrays because it seems we are capturing the ephemeral ports too. See how the list grows in the output:
msg="new process watching events" component=discover.Watcher interval=500ms events="[{Type:0 Obj:{pid:1 openPorts:[33348 33400 33332 33318 33388 33312 33372 33356 33324 40604 40608 33338]}}]"

OK, I reproduced it with some extra debugging information. For me it seems the node client is spawning new processes to handle the outgoing request:
msg="Found event" component=httpfltr.Tracer "Host PID"=1265 "NS Pid"=1265 "NS ID"=4026531836
msg="Found event" component=httpfltr.Tracer "Host PID"=1276 "NS Pid"=1276 "NS ID"=4026531836
...

It seems our bpf code which is matching based on parent pid is what works.

Ah there's more to it, the bfp side sees it as the correct single process as it should be, it's always that host id. I think we are reading the host pid wrong in the task_pid function.
node-3418467 [008] d..31<PHONE_NUMBER>38: bpf_trace_printk: Sending client buffer GET / HTTP/1.1

@grcevski

I also noticed one more issue at the time we run the process discovery loop. We record the active port numbers, but with client programs they will grow to large arrays because it seems we are capturing the ephemeral ports too. See how the list grows in the output:
Yeah, this will be handled in the next PR, when we handle the removal of processes after they stop existing. Also the closed ports will be removed.


CIV-3627 Add Publish field to publish data in WA Queue

Before creating a pull request make sure that:

[x] commit messages are meaningful and follow good commit message guidelines
[x] README and other documentation has been updated / added (if needed)
[x] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-3627
Change description
Add publish Y to all relevant events as per DMNS
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

I see in cancellation DMN that there is an entry for MAIN_CASE_CLOSED... We currently do not have any such event. I believe we have a ticket that caters to this scenario. I would suggest to add a comment on that ticket that we need Publish Y on the CCD event definition

WA Task Cancellation event will be implemented in CIV-2801 State - Application Closed - HMCTS JIRA
Publish Y has to added


Adding empty init.py file to allow importing from a path

When I tried importing, I realized python couldn't find the module. Turns out, the solution is to add an empty __init__.py file. Just tested this out, and this allowed me to import the project as a git submodule and still import the class. You can see the solution here.
I also went ahead and added value checking to the constructor, since I realized I left that out before. It checks latitude and longitude, as well as checking the time zone. The time zone range is accurate according to wikipedia (between -12 and +14). This may change over the years if new time zones are created (which does happen on occasion). So if the fragility is a concern, I can revert it.

Good job and thanks again for the PR. I gave you push access to the repo so you can push any changes directly to the repo!

Ok, thanks!


[ENH] Allow for - (dash) (and/or +) in

I thought that we already had an issue filed for this, but may be it was just my comments in the google doc version of the BIDS specification, so filing anew.  Please close it referencing original one if one already exists.
ATM <label> is as I formalized in yet to be finished PR is allowed to contain only alpha numerics.  That makes it really difficult in some cases to place multiple entries (e.g. details for _acq- or abbreviate details of preprocessing in _desc- of BIDS derivatives). In ReproIn heuristic for heudiconv, where we do allow for - we just replace them with an ugly X as a separator to just stay compatible with BIDS.
I have been suggesting to extend the list of allowed characters in <label> to include at least - and possibly others (e.g., +) which otherwise should not introduce any backward incompatibility with BIDS 1.0 -- all BIDS 1.0 names would be compatible with new syntax allowing - in the <labels>.
The original concern (probably at least a year back) which precluded any action was a possible breakage of parsing BIDS filenames for BIDS-supporting software, and was suggested to be included in coming some time in the future BIDS 2.0.
N.B.  I have failed to file and issue outlining plans for BIDS 2.0, so I initiated a new milestone (2.0.0) to which I am adding this new issue.
IMHO (and may be we should outline it somewhere) BIDS supporting applications should be coded adhering to Postel's principle which is driving TCP implementations to "be conservative in what you do, be liberal in what you accept from others.". And most likely, in the case of added -, they already are since they are more likely to be splitting based on _ and then on - to separate key from value instead of full rigid regular expressions limiting to the allowed characters (not so obviously) mandated by the BIDS specification.  So the only catch here indeed might be splitting on - without restricting that only a single split should happen.  That is where breakage could happen if - is added.  The possibility of breakage in case of extending the list of allowed characters with + (or even : which I dislike to suggest due to messing up scp/ssh) unlikely to have negative ramifications.
Please share your thoughts/opinions

I'm personally okay with - or +, and can't really remember the arguments against them.

I'm okay with +, and not very fond of - but I understand it could be added. I would not allow - to be present in the suffix entity, though.

I would not allow - to be present in the suffix entity, though.

Great point I haven't thought to exercise @oesteban ! -- I would not allow it as well, makes parsing much more difficult etc!
The only spot I see where <label> is used not within _key-<label> is
(git)hopa:~/proj/bids/bids-specification[derivatives]git
$> git grep '_<label'
src/04-modality-specific-files/04-intracranial-electroencephalography.md:called `electrical_stimulation_<label>`, with labels chosen by the researcher and

so might need analysis/tune up (or not)

ok, after https://github.com/bids-standard/bids-specification/pull/152 is merged in one way or another we could have a PR extending the list of allowed characters non-ambiguously in a single location ;-)

Note that the request to include hypens in key-value labels is currently in the "Suggestions for BIDS 2.0" Google doc:
Allowing hyphens in filename key values
which suggests, as I had recalled, that this was a settled issue.  Including hyphens increases the complexity of parsing the filenames, was the reason I recall.

@nicholst, will '-' really increase complexity of parsing?
Each key-value parsed by '_' and everything after the first '-' is a label.

@nicholst Oh, that is where BIDS 2.0 "extensions" are discussed -- thank you for the link! I have added the link to the 2.0.0 milestone description. I think it might be worthwhile to move them all under issues over here at some point, so elderly folks like us could easily find everything relevant in the single location (here).
I would not say that parsing complexity would increase, but indeed it might require some adjustment.

@nbeliy

@nicholst, will '-' really increase complexity of parsing?
Each key-value parsed by '_' and everything after the first '-' is a label.

Just reciting the conclusion of a long thread about this issue.  Like anything, this issue can be re-raised, but I think there is the basic issue of extra clarity from having the hyphen play exactly one role in file/directory names.

my 1c: This issue by now is probably a few years old (IIRC I have suggested it possibly even during BIDS 1.x initial development/release) .  If we acted sooner, it would be no issue but even those years back I have proposed it the main argument against was "we would break the tools" of which there were much fewer.  So longer we wait to act, the harder would be to adopt this change.

I think at this point the procedure would be sending a draft PR with the suggested changes for a more focused discussion, is that correct @franklin-feingold @sappelhoff ?

I think at this point the procedure would be sending a draft PR with the suggested changes for a more focused discussion, is that correct @franklin-feingold @sappelhoff ?

Yes, and on top of that I think what this discussion needs are:

concrete use cases where the proposed changes would significantly enhance BIDS (summaries/links to such cases)
a concrete PR showing the diff of the spec prior and post the proposed changes (what @oesteban said)
more participants to voice their opinions - especially developers

Currently this change seems to me as a minor improvement with the potential for a major confusion ... but I am very happy to be convinced otherwise :-)

Use cases:
Subject or session labels come from long-established project that has
identifiers with dashes.
Related, such a project uses identifiers with underscores (but not dashes),
and the underscores need to be replaced; having dashes as an option for
replacing is helpful.

Is UTF8 allowed in BIDS file names, or if not, should it be? If so, there are many dashes to choose from which are not a minus (ASCII decimal 45). For example ‒ – and —. See https://www.w3schools.com/charsets/ref_utf_punctuation.asp

Using alternatives that look like the proposed doesn't help much with readability, makes it harder. Imagine a suffix like _inplane‒T2.json (I used your first UTF8 character). _inplane+T2.json breaks the suffix a bit, but is still readable. The limitation of the suffix is also important in this kind of proposal, IMHO.
I would be fine with the + symbol and I think the dash is not worth the pain. Adding the dash would feel to me as useful as allowing spaces (i.e., error-prone and likely confusing).

I think we should explicitly forbid UTF8 and limit to ASCII to avoid such "tricks" which could potentially cause confusion.
So let's move forward with "+"?
I doubt any tool was so strict with regexp that it listed only alpha numerics.  and sooner we change, less possible negative effect it would have.  This issue already dragged long time (I originally suggested in the times of BIDS being a google doc), and I think it is worth to be accepted to 1.x series without awaiting 2.0 which I am not quite sure would come in any foreseeable future

Agreed about limiting character sets, I also don’t look forward to multiple types of dashes or emojis in filenames. But the limit should be explicitly mentioned.
Regarding the “+” I am neutral.
Verstuurd vanaf mijn iPhone

Op 2 nov. 2019 om 00:57 heeft Yaroslav Halchenko<EMAIL_ADDRESS>het volgende geschreven:

I think we should explicitly forbid UTF8 and limit to ASCII to avoid such "tricks" which could potentially cause confusion.
So let's move forward with "+"?
I doubt any tool was so strict with regexp that it listed only alpha numerics. and sooner we change, less possible negative effect it would have. This issue already dragged long time (I originally suggested in the times of BIDS being a google doc), and I think it is worth to be accepted to 1.x series without awaiting 2.0 which I am not quite sure would come in any foreseeable future
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

ok, it seems that the path of the least resistance would be to add + as allowed character.  I will look into proposing a PR here and against bids-validator for that (unless someone would beat me to it which I would really appreciate)

oh hoh, it had been a year!  Few final remarks and then I will try to find time to compose a PR.

+ implies composition of multiple things, like _proc-mc+filt -- thing was motion corrected and filtered; whenever - is more of a pure delimiter between multiple words which need to be taken together
re _inplane‒T2. example -- "illegit" since - must not be allowed in the suffix, which it must not look like  _key-value. This issue only about <label> as used in the _key-<label>, and we never use _<label> as arbitrary suffix (git grep -e '<label>\.' -e '_<label>' comes with no relevant hits)
comparison of - to spaces is IMHO also a bit too far stretched. - does not break visual composition of the filename etc.
arguments against - because there are UTF8 characters for longer dashes are not really pertinent. Pretty much any character could have some confusingly similar symbol in UTF8, so we just must not allow utf8 in general.

Since I and others mentioned a number of use cases, and IMHO it would be easier to strip away than to add later, I will prepare a PR which would introduce allowing both - and + and then we will see how it goes.


Support Tap-to-Focus

In addition to automatic focus modes, support a tap on the screen background to trigger a manual focus. Offer an IntentBuilder method and corresponding extra to enable/disable this feature (initially enabled).

Dear @commonsguy,
I would like to ask is the Tap to Focus feature is still available in version 0.5.9? There's only 3 focus modes in the demo Playground which are:

Continuous.
Off.
Extended DOF.

Sorry if I'm missing something obvious but this is a really needed feature.
Thanks again for your time.

I would like to ask is the Tap to Focus feature is still available in version 0.5.9?

This issue is still open.

Is there any hope to see this feature any time soon?

@crackTheCode Well, it depends on what you are looking for.
This issue is for a fairly vanilla implementation, one where a tap anywhere on the preview would trigger a basic autofocus. That should be straightforward for the classic Camera engine, and I have not researched how it would be done with android.hardware.camera2, though presumably it can be done. I am not contemplating anything elaborate (e.g., focus on the point where the user tapped).
What exactly are you looking for?

I am new to the camera API so I don't know how to implement it the right way in both engines and I haven't found anything particularly helpful so I look forward to a tap to focus and exposure "calibration" feature in both engines, picture and video capture mode in a future release as the native camera app does on my OnePlus One Oxygen OS

This library is for very basic picture and video capture, nothing more. This library will never have exposure calibration. This library will never match your native camera app feature for feature.


Expose port in docker Dockerfile

To make it possible to register the service in consul when using Gliderlabs Registrator running with the -internal option:
"If you use the -internal option, Registrator will use the exposed port and Docker-assigned internal IP of the container."
Relates to: https://github.com/cloudworkz/kube-eagle-helm-chart/pull/24

I found out that we can achieve the result we wanted by using helm hooks, like the pre-install one.
Thanks


Fix include to make None mean False

Codecov Report

Merging #20 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #20   +/-   ##
=======================================
  Coverage   98.15%   98.15%
=======================================
  Files          60       60
  Lines        7516     7519    +3
=======================================
+ Hits         7377     7380    +3
  Misses        139      139

Impacted Files
Coverage Δ

iommi/traversable.py
96.63% <100.00%> (ø)

tests/test_40_forms.py
99.90% <100.00%> (+<0.01%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2ebb30c...0c8d3f7. Read the comment docs.


Read a Shlok button is not align with other button

The Read a shlok button is  dislocated . i want to work on this issue kindly assign me.

Hi! would like to take this issue can you assign this issue to me under GSSOC'23

assigning u


Protocol Buffer update for release 2.13.x at Wed Nov  3 09:26:15 UTC 2021

The PR was created by accident and can be discarded.


Error: Unable to find source_dir

I am trying to get source_dir value working, here is my code structure.
├── .github
│   └── workflows
│       └── main.yml
├── .gitignore
├── LICENSE
├── README.md
└── src
    ├── main.py
    └── requirements.txt

jobs:
  Deploy:
    runs-on: ubuntu-latest
    steps:
    - id: Deploy

      uses: google-github-actions/deploy-cloud-functions@main
      with:
        name: RvsAirtable
        runtime: python38
        source_dir: src

how does this variable work?

Hi @Rahulsharma0810
Looks like it was unable to find the src directory. I don't see a checkout step in your workflow, you will need use the checkout action to pull code into the runner.
jobs:
  Deploy:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - id: Deploy
      uses: google-github-actions/deploy-cloud-functions@main
      with:
        name: RvsAirtable
        runtime: python38
        source_dir: src

@bharathkkb Super smooth, Thanks


how to show user snippet after period

Issue Type: Feature Request
When I click "period",user snippet will not display.
VS Code version: Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:48:58.283Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

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


Flows List default roles are Flows API default roles

It's happened often enough where CLI users are confused why they get different Flow output on the Flow List command. This PR removes the default role filtering (used to default to created_by) so that if the CLI command is run without any role filters, the results returned are dependent on the API.

I kind of thought the created_by was a sane default. Perhaps this can be addressed via documentation on the option rather than a change of the default? Given the server side default change the list could be pretty large? Perhaps we need to discuss with the team before deciding on this?

For folks not versed in our various Flow roles I think this leads to confusion (at least it's the source of many questions) when they use the CLI vs the WebApp. This lowers the barrier of entry and I think letting the server decide what gets returned makes it easier to document too. In this case I feel like the server defaults (minding performance) is worth getting on the same page about. Discussion is always welcome.


KDE does not recognise the trackpad

Describe the bug
The trackpad is working, but KDE Settings says that there are no trackpads.
Expected behavior
KDE should see the trackpad.


Debugging input for .csv files

Added exception blocks to catch file reading errors
Merged the namespaces inputPrometheus & matrixPrometheusNSpace
Return type for inputPrometheus() changed to vector<matrixPrometheus>
The program is now more memory intensive.
Should contain fix for #6

The compiler warning about the conditional return of data has been fixed.
x IK


Completion should be case insensitive

Passing ignore-case to gocode but it isn't working - likely something I'm doing wrong or not doing

need to up the priority as this is a problem for the directory args completion case

I've commented to gocode issues as there is an issue regarding case insensitive search but it isn't clear if it was implemented or not.

I could make completion for non-code fields like the command directory variable case insensitive even if code completion isn't case insensitive but that might be more confusing. Thoughts?

yep I like that paradigm

ps. it is how interactive-search works already

Now implemented