can't install isosplit6

Hello！I got a problem when I 'pip install isosplit6'.
10 warnings and 2 errors generated.
error: command '/usr/bin/clang' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for isosplit6
Failed to build isosplit6
ERROR: Could not build wheels for isosplit6, which is required to install pyproject.toml-based projects

Hi @mengweiwei99
Is there more to the error message? In addition, could you please provide more details on your OS and environment?

OK，some details are as follows:
1、 error message
➜  ~ pip install isosplit6
Collecting isosplit6
Using cached isosplit6-0.1.2.tar.gz (25 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: isosplit6
Building wheel for isosplit6 (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for isosplit6 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [72 lines of output]
running bdist_wheel
running build
running build_py
creating build
creating build/lib.macosx-11.0-arm64-cpython-39
creating build/lib.macosx-11.0-arm64-cpython-39/isosplit6
copying isosplit6/init.py -> build/lib.macosx-11.0-arm64-cpython-39/isosplit6
running build_ext
building 'isosplit6_cpp' extension
creating build/temp.macosx-11.0-arm64-cpython-39
creating build/temp.macosx-11.0-arm64-cpython-39/src
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -fwrapv -O2 -Wall -fPIC -O2 -isystem /Users/mengweiwei/opt/anaconda3/envs/spikeinterface/include -arch arm64 -fPIC -O2 -isystem /Users/mengweiwei/opt/anaconda3/envs/spikeinterface/include -arch arm64 -I/private/var/folders/9c/_7lgrd912ns9w9n5m50xxslw0000gn/T/pip-build-env-hdasp09z/overlay/lib/python3.9/site-packages/pybind11/include -I/Users/mengweiwei/opt/anaconda3/envs/spikeinterface/include/python3.9 -c src/isocut5.cpp -o build/temp.macosx-11.0-arm64-cpython-39/src/isocut5.o -fvisibility=hidden -g0 -stdlib=libc++
In file included from src/isocut5.cpp:16:
src/isocut5.h:25:25: warning: default member initializer for non-static data member is a C++11 extension [-Wc++11-extensions]
bool already_sorted = false;
^
1 warning generated.
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -fwrapv -O2 -Wall -fPIC -O2 -isystem /Users/mengweiwei/opt/anaconda3/envs/spikeinterface/include -arch arm64 -fPIC -O2 -isystem /Users/mengweiwei/opt/anaconda3/envs/spikeinterface/include -arch arm64 -I/private/var/folders/9c/_7lgrd912ns9w9n5m50xxslw0000gn/T/pip-build-env-hdasp09z/overlay/lib/python3.9/site-packages/pybind11/include -I/Users/mengweiwei/opt/anaconda3/envs/spikeinterface/include/python3.9 -c src/isocut6.cpp -o build/temp.macosx-11.0-arm64-cpython-39/src/isocut6.o -fvisibility=hidden -g0 -stdlib=libc++
In file included from src/isocut6.cpp:16:
src/isocut5.h:25:25: warning: default member initializer for non-static data member is a C++11 extension [-Wc++11-extensions]
bool already_sorted = false;
^
In file included from src/isocut6.cpp:17:
src/isocut6.h:25:25: warning: default member initializer for non-static data member is a C++11 extension [-Wc++11-extensions]
bool already_sorted = false;
^
2 warnings generated.
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -fwrapv -O2 -Wall -fPIC -O2 -isystem /Users/mengweiwei/opt/anaconda3/envs/spikeinterface/include -arch arm64 -fPIC -O2 -isystem /Users/mengweiwei/opt/anaconda3/envs/spikeinterface/include -arch arm64 -I/private/var/folders/9c/_7lgrd912ns9w9n5m50xxslw0000gn/T/pip-build-env-hdasp09z/overlay/lib/python3.9/site-packages/pybind11/include -I/Users/mengweiwei/opt/anaconda3/envs/spikeinterface/include/python3.9 -c src/isosplit5.cpp -o build/temp.macosx-11.0-arm64-cpython-39/src/isosplit5.o -fvisibility=hidden -g0 -stdlib=libc++
In file included from src/isosplit5.cpp:16:
In file included from src/isosplit5.h:20:
src/isocut5.h:25:25: warning: default member initializer for non-static data member is a C++11 extension [-Wc++11-extensions]
bool already_sorted = false;
^
In file included from src/isosplit5.cpp:16:
src/isosplit5.h:25:29: warning: default member initializer for non-static data member is a C++11 extension [-Wc++11-extensions]
double isocut_threshold = 1.0;
^
src/isosplit5.h:26:26: warning: default member initializer for non-static data member is a C++11 extension [-Wc++11-extensions]
int min_cluster_size = 10;
^
src/isosplit5.h:27:16: warning: default member initializer for non-static data member is a C++11 extension [-Wc++11-extensions]
int K_init = 200;
^
src/isosplit5.h:28:26: warning: default member initializer for non-static data member is a C++11 extension [-Wc++11-extensions]
bool refine_clusters = false;
^
src/isosplit5.h:29:33: warning: default member initializer for non-static data member is a C++11 extension [-Wc++11-extensions]
int max_iterations_per_pass = 500;
^
src/isosplit5.h:36:27: warning: default member initializer for non-static data member is a C++11 extension [-Wc++11-extensions]
bigint num_iterations = 0;
^
src/isosplit5.h:58:25: warning: default member initializer for non-static data member is a C++11 extension [-Wc++11-extensions]
bool final_reassign = false; //not yet implemented
^
src/isosplit5.cpp:228:154: warning: format specifies type 'long' but the argument has type 'bigint' (aka 'long long') [-Wformat]
printf("Warning in isosplit5: new parcel has no points -- perhaps dataset contains duplicate points? -- original size = %ld.\n", sz);
~~~      ^~
%lld
src/isosplit5.cpp:153:14: warning: variable 'something_changed' set but not used [-Wunused-but-set-variable]
bool something_changed=false;
^
src/isosplit5.cpp:870:35: error: a space is required between consecutive right angle brackets (use '> >')
std::vector<std::vector> dists(K);
^~
> >
src/isosplit5.cpp:1163:35: error: a space is required between consecutive right angle brackets (use '> >')
std::vector<std::vector> distances(N);
^~
> >
10 warnings and 2 errors generated.
error: command '/usr/bin/clang' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
 Seems that there is a small compile error specific to your setup with ">>" needing to be changed to "> >". I made the adjustment and pushed to the main branch, but that version is not on pypi. So to test you'll need to try installing from source:
After cloning this repo:
cd isosplit6
pip install .

Would be great if you could report back on how that works. If okay, then I'll release a new version.

similar issue here in Linux, conda, python3.9:

pip install isosplit6

Collecting isosplit6
Using cached isosplit6-0.1.2.tar.gz (25 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: isosplit6
Building wheel for isosplit6 (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for isosplit6 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [23 lines of output]
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-39
creating build/lib.linux-x86_64-cpython-39/isosplit6
copying isosplit6/init.py -> build/lib.linux-x86_64-cpython-39/isosplit6
running build_ext
building 'isosplit6_cpp' extension
creating build/temp.linux-x86_64-cpython-39
creating build/temp.linux-x86_64-cpython-39/src
gcc -pthread -B /wynton/home/ganguly/hosuk88/anaconda3/envs/mtsort5/compiler_compat -Wno-unused-result -Wsign-compare -DNDEBUG -O2 -Wall -fPIC -O2 -isystem /wynton/home/ganguly/hosuk88/anaconda3/envs/mtsort5/include -I/wynton/home/ganguly/hosuk88/anaconda3/envs/mtsort5/include -fPIC -O2 -isystem /wynton/home/ganguly/hosuk88/anaconda3/envs/mtsort5/include -fPIC -I/scratch/hosuk88/pip-build-env-dknx373r/overlay/lib/python3.9/site-packages/pybind11/include -I/wynton/home/ganguly/hosuk88/anaconda3/envs/mtsort5/include/python3.9 -c src/isocut5.cpp -o build/temp.linux-x86_64-cpython-39/src/isocut5.o -fvisibility=hidden -g0
In file included from /usr/include/c++/4.8.2/cstdint:35:0,
from src/isocut5.h:20,
from src/isocut5.cpp:16:
/usr/include/c++/4.8.2/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support is currently experimental, and must be enabled with the -std=c++11 or -std=gnu++11 compiler options.
#error This file requires compiler and library support for the
^
In file included from src/isocut5.cpp:16:0:
src/isocut5.h:25:27: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
bool already_sorted = false;
^
error: command '/usr/bin/gcc' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for isosplit6
Failed to build isosplit6
ERROR: Could not build wheels for isosplit6, which is required to install pyproject.toml-based projects

@hosuk88 - from the output it doesn't seem like exactly the same problem - I don't actually see the compiler error message. But could you please try installing from source as in my last comment, in case it is the same issue?

Not sure if this will help: https://github.com/magland/isosplit6/pull/2
See also: https://github.com/flatironinstitute/mountainsort5/issues/6

Couldn't make it work, unfortunately!

Hello when I tried to install isosplit 6: and mountainsort5: I got the errors shown below.  I tried everything that is recommended from previous problem and solutions. If anyone can help I would appreciate it.
For isosplit my errors are:
Building wheels for collected packages: isosplit6
Building wheel for isosplit6 (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for isosplit6 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [15 lines of output]
and
IC -I/tmp/pip-build-env-6sht33cx/overlay/lib/python3.11/site-packages/pybind11/include -I/home/domontelab/miniconda3/include/python3.11 -c src/isocut5.cpp -o build/temp.linux-x86_64-cpython-311/src/isocut5.o -fvisibility=hidden -g0
gcc: fatal error: cannot execute ‘cc1plus’: execvp: No such file or directory
compilation terminated.
error: command '/usr/bin/gcc' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for isosplit6
Failed to build isosplit6
ERROR: Could not build wheels for isosplit6, which is required to install pyproject.toml-based projects
For mountainsort5:
Building wheels for collected packages: isosplit6
Building wheel for isosplit6 (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for isosplit6 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [15 lines of output]
and
gcc -pthread -B /home/domontelab/miniconda3/compiler_compat -DNDEBUG -fwrapv -O2 -Wall -fPIC -O2 -isystem /home/domontelab/miniconda3/include -fPIC -O2 -isystem /home/domontelab/miniconda3/include -fPIC -I/tmp/pip-build-env-af6txs06/overlay/lib/python3.11/site-packages/pybind11/include -I/home/domontelab/miniconda3/include/python3.11 -c src/isocut5.cpp -o build/temp.linux-x86_64-cpython-311/src/isocut5.o -fvisibility=hidden -g0
gcc: fatal error: cannot execute ‘cc1plus’: execvp: No such file or directory
compilation terminated.
error: command '/usr/bin/gcc' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for isosplit6
Failed to build isosplit6
ERROR: Could not build wheels for isosplit6, which is required to install pyproject.toml-based projects
Here is my whole code:
(base) domontelab@MSNBA-C000417:~/spikeinterface$ pip install mountainsort5
Collecting mountainsort5
Obtaining dependency information for mountainsort5 from https://files.pythonhosted.org/packages/35/6e/4a81230cb11213a2a038f69362b6d2a0950f8188a2f70cd19b45866343c7/mountainsort5-0.3.3-py3-none-any.whl.metadata
Using cached mountainsort5-0.3.3-py3-none-any.whl.metadata (7.6 kB)
Requirement already satisfied: spikeinterface>=0.97.1 in /home/domontelab/miniconda3/lib/python3.11/site-packages (from mountainsort5) (0.99.0.dev0)
Collecting isosplit6>=0.1.0 (from mountainsort5)
Using cached isosplit6-0.1.2.tar.gz (25 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: scikit-learn in /home/domontelab/miniconda3/lib/python3.11/site-packages (from mountainsort5) (1.3.1)
Requirement already satisfied: numpy in /home/domontelab/miniconda3/lib/python3.11/site-packages (from spikeinterface>=0.97.1->mountainsort5) (1.25.2)
Requirement already satisfied: neo>=0.12.0 in /home/domontelab/miniconda3/lib/python3.11/site-packages (from spikeinterface>=0.97.1->mountainsort5) (0.13.0.dev0)
Requirement already satisfied: joblib in /home/domontelab/miniconda3/lib/python3.11/site-packages (from spikeinterface>=0.97.1->mountainsort5) (1.3.2)
Requirement already satisfied: threadpoolctl in /home/domontelab/miniconda3/lib/python3.11/site-packages (from spikeinterface>=0.97.1->mountainsort5) (3.2.0)
Requirement already satisfied: tqdm in /home/domontelab/miniconda3/lib/python3.11/site-packages (from spikeinterface>=0.97.1->mountainsort5) (4.65.0)
Requirement already satisfied: probeinterface>=0.2.17 in /home/domontelab/miniconda3/lib/python3.11/site-packages (from spikeinterface>=0.97.1->mountainsort5) (0.2.18)
Requirement already satisfied: scipy>=1.5.0 in /home/domontelab/miniconda3/lib/python3.11/site-packages (from scikit-learn->mountainsort5) (1.11.3)
Requirement already satisfied: packaging in /home/domontelab/miniconda3/lib/python3.11/site-packages (from neo>=0.12.0->spikeinterface>=0.97.1->mountainsort5) (23.0)
Requirement already satisfied: quantities>=0.14.1 in /home/domontelab/miniconda3/lib/python3.11/site-packages (from neo>=0.12.0->spikeinterface>=0.97.1->mountainsort5) (0.14.1)
Using cached mountainsort5-0.3.3-py3-none-any.whl (29 kB)
Building wheels for collected packages: isosplit6
Building wheel for isosplit6 (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for isosplit6 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [15 lines of output]
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-311
creating build/lib.linux-x86_64-cpython-311/isosplit6
copying isosplit6/init.py -> build/lib.linux-x86_64-cpython-311/isosplit6
running build_ext
building 'isosplit6_cpp' extension
creating build/temp.linux-x86_64-cpython-311
creating build/temp.linux-x86_64-cpython-311/src
gcc -pthread -B /home/domontelab/miniconda3/compiler_compat -DNDEBUG -fwrapv -O2 -Wall -fPIC -O2 -isystem /home/domontelab/miniconda3/include -fPIC -O2 -isystem /home/domontelab/miniconda3/include -fPIC -I/tmp/pip-build-env-af6txs06/overlay/lib/python3.11/site-packages/pybind11/include -I/home/domontelab/miniconda3/include/python3.11 -c src/isocut5.cpp -o build/temp.linux-x86_64-cpython-311/src/isocut5.o -fvisibility=hidden -g0
gcc: fatal error: cannot execute ‘cc1plus’: execvp: No such file or directory
compilation terminated.
error: command '/usr/bin/gcc' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for isosplit6
Failed to build isosplit6
ERROR: Could not build wheels for isosplit6, which is required to install pyproject.toml-based projects
(base) domontelab@MSNBA-C000417:~/spikeinterface$ pip install isosplit6
Collecting isosplit6
Using cached isosplit6-0.1.2.tar.gz (25 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: isosplit6
Building wheel for isosplit6 (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for isosplit6 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [15 lines of output]
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-311
creating build/lib.linux-x86_64-cpython-311/isosplit6
copying isosplit6/init.py -> build/lib.linux-x86_64-cpython-311/isosplit6
running build_ext
building 'isosplit6_cpp' extension
creating build/temp.linux-x86_64-cpython-311
creating build/temp.linux-x86_64-cpython-311/src
gcc -pthread -B /home/domontelab/miniconda3/compiler_compat -DNDEBUG -fwrapv -O2 -Wall -fPIC -O2 -isystem /home/domontelab/miniconda3/include -fPIC -O2 -isystem /home/domontelab/miniconda3/include -fPIC -I/tmp/pip-build-env-6sht33cx/overlay/lib/python3.11/site-packages/pybind11/include -I/home/domontelab/miniconda3/include/python3.11 -c src/isocut5.cpp -o build/temp.linux-x86_64-cpython-311/src/isocut5.o -fvisibility=hidden -g0
gcc: fatal error: cannot execute ‘cc1plus’: execvp: No such file or directory
compilation terminated.
error: command '/usr/bin/gcc' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for isosplit6
Failed to build isosplit6
ERROR: Could not build wheels for isosplit6, which is required to install pyproject.toml-based projects
(base) domontelab@MSNBA-C000417:~/spikeinterface$ ^C
(base) domontelab@MSNBA-C000417:~/spikeinterface$


Kubeless function pods deleted periodically , and new pods started automatically

Is this a BUG REPORT or FEATURE REQUEST?:Not sure ( maybe some config i missed)
What happened: Kubeless function pods are getting automatically deleted periodically, and new pods are booted up. This happens while the previous pod is executing a scheduled function, which causes the ongoing function execution to stop, and get restarted on the newly created pod after it is ready and available.
What you expected to happen: I can't find any documentation where in such auto-delete-and-recreate kind of behaviour is documented. Basically , I expected the deployment to be stable and hot all the time( one pod running all the time). The previous pod should get deleted only if function update is called, upon which a new replica set starts with a new pod. So, I don't know if this is expected behaviour.
How to reproduce it (as minimally and precisely as possible): I am running a nodejs function loaded as zip file and a package.json, with nodejs8 runtime. The function is scheduled to trigger every 5 min, and takes 2-3 min to run.
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version): 1.8.1
Kubeless version (use kubeless version): 0.3.4
Cloud provider or physical cluster: Azure AKS cluster

Hi @tapanhalani ,
this is an issue with kubernetes. As far as I understood my co-workers it should be fixed with k8s version >1.8.6 (@sayanh @rakesh-garimella ). The problem is, kubernetes is republishing some events vor some reason, which is triggering kubless controller to update the deployment.

I agree with @joek, I tried it with Kubernetes 1.8.0 (Minikube 0.24.1) and the pods get restarted after a few minutes as you see but it doesn't happen in Kubernetes 1.7.12 nor v1.8.7 (both GKE) or Kubernetes 1.9.0 (Minikube 0.25.0)

@joek did you track it down to a filed issue in k8s upstream ? we should link the issue to it

@sebgoa nope, I just used some information @rakesh-garimella and @sayanh figured out. Maybe they got more information.

Let's close this issue since it no longer appears in more recent versions of Kubernetes. Please reopen it if you find it again.


ERROR in SchemaFormModule is not an NgModule

I am trying to use angular2-schema-form with the latest version of angular-cli.
When I am doing npm start then I am getting this issue : ERROR in SchemaFormModule is not an NgModule
I have checked the issue with angular-cli forums and it is happening with a lot of other modules, and according to what I understood on the forums the angular2 packages in angular2-schema-form need to be updated as well to make it usable with cli projects.
My Angular2-Cli setup:
angular-cli: 1.0.0-beta.24
node: 7.2.1
os: win32 x64
@angular/common: 2.4.1
@angular/compiler: 2.4.1
@angular/core: 2.4.1
@angular/forms: 2.4.1
@angular/http: 2.4.1
@angular/platform-browser: 2.4.1
@angular/platform-browser-dynamic: 2.4.1
@angular/router: 3.4.1
@angular/compiler-cli: 2.4.1
What are your suggestions ?

did you use the npm release or the GitHub checkout?

#50
As per https://github.com/angular/angular/issues/11262#issuecomment-244472000

All referenced libraries must include the *.metadata.json file along side any *.d.ts files they produce…

I found an article for the solution -<EMAIL_ADDRESS>

I used the npm release package.

I have just published 1.0.0-alpha.33, it should be better.

I uninstalled angular2-schema form and installed the<EMAIL_ADDRESS>again.
I still get the following error

[00:25:27]  ionic-app-scripts 0.0.47
[00:25:27]  build prod started ...
[00:25:27]  clean started ...
[00:25:27]  clean finished in 1 ms
[00:25:27]  copy started ...
[00:25:27]  ngc started ...
[00:25:29]  build prod failed: Unexpected value 'SchemaFormModule' imported by the module 'AppModule'
[00:25:29]  ionic-app-script task: "build"
[00:25:29]  Error: Unexpected value 'SchemaFormModule' imported by the module 'AppModule'
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\User\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "run" "ionic:build" "--" "--prod"
npm ERR! node v6.9.2
npm ERR! npm  v4.0.5
I still dont see the *metadata.json file in the @1.0.0-alpha.33 release

@Ragularuban try importing modules from src by import { SchemaFormModule, WidgetRegistry, DefaultWidgetRegistry } from "angular2-schema-form/src" in case metadata file is not there.
It might work.

I didn't plan the AOT compatibility at all when I submitted the new structure.
I'm currently working on it in a branch and will do a PR soon.
Sorry for the inconvenience!

@alimohammad it still didn't work. the issue was AOT compatibility
@SBats Thanks :-) Much Appreciate it.

Hey @alimohammad and @Ragularuban , could you please try with the last commit of this branch and let me know if it's any better?
https://github.com/SBats/angular2-schema-form/tree/fix-aot
If it works I'll PR it, merge and publish for a good npm version

@SBats . Extremely sorry for the delay. I will update you on it very soon

@SBats Please assist me...

git clone -g fix-aot https://github.com/SBats/angular2-schema-form.git
2)npm install
npm install threw an error

<EMAIL_ADDRESS>prepublish C:\Users\User\Desktop\test\angular2-schema-form
export NODE_ENV=production; npm run build

'export' is not recognized as an internal or external command,
operable program or batch file.

I think the error is beacause i'm running in windows. so i i continue it doing manually. I edited webpack.config.js to run in production then i continue with
3)npm run build
It threw the below errors

<EMAIL_ADDRESS>copy-template C:\Users\User\Desktop\test\angular2-schema-form
copy ./src/**/*.html ./dist/src

The syntax of the command is incorrect.

I read npm copy documentation to find out that i need to wrap files names in quote. so I changed

copy ./src/**/*.html ./dist/src

To

copy "./src/**/*.html" "./dist/src"

and then ran the build...
It threw the below error

<EMAIL_ADDRESS>copy-template C:\Users\User\Desktop\test\angular2-schema-form
copy "./src/**/*.html" "./dist/src"

./src/**/*.html
The filename, directory name, or volume label syntax is incorrect.
0 file(s) copied.

I tried various methods, but copy command is not letting me copy anything apart from the root directory(Weird)
Finally, i decided to to replace the 'copy' module with 'copyfiles' module

https://www.npmjs.com/package/copyfiles

the build then finished without any errors! :-)
I copied the files into my project files, when i tried to build the solution i got the below error

[05:41:34]  ngc started ...
[05:41:54]  typescript: ...cts/*****/node_modules/angular2-schema-form/dist/src/model/formproperty.d.ts, line: 1
Cannot find type definition file for 'core-js'.
   L1:  import { BehaviorSubject

from 'rxjs/BehaviorSubject';
[05:41:54]  ionic-app-script task: "build"        L2:  import 'rxjs/add/observable/combineLatest';
[05:41:54]  Error: Failed to transpile TypeScript

Please look into the above.

Okay, we're coming close I think.
You are right, I didn't plan windows compatibility. I've fixed scripts following what you used to resolve your windows issues, so it should be ok.
As to types of core-js missings, you should just have to install them as dev dependencies and it should work.
So to summarize:

remove angular2-schema-form from your node_modules and your package.json for now.
remove the @typings folder you add manualy. On recent build Typescript is able to automaticly fetch typings from node_modules. So if you have one missing, there's 99% chance you don't have it installed.
install schema form via the command npm i git+https://github.com/SBats/angular2-schema-form.git\#da7ac6dc990813943c717052e26d8f2a9010a644 (it install it directly in you project instead of having to copy files manualy). Add -S if you want it saved as a dependency
go in node_modules/angular2-schema-formand run npm run build
add missing types via npm i -D @types/core-js

With this, you should have a stable base to test if the new version works.
If not let me know and we'll keep searching what's wrong.
Good luck :)

I tried to do do

npm i git+https://github.com/SBats/angular2-schema-form.git#da7ac6dc990813943c717052e26d8f2a9010a64

• It threw the below error...

npm ERR! Command failed: git -c core.longpaths=true clone --template=C:\Users\User\AppData\Roaming\npm-cache_git-remotes_templates --mirror git+https://github.com/SBats/angular2-schema-f
orm.git\ C:\Users\User\AppData\Roaming\npm-cache_git-remotes\git-https-github-com-SBats-angular2-schema-form-git-da7ac6dc990813943c717052e26d8f2a9010a644-6cf526c4
npm ERR! Cloning into bare repository 'C:\Users\User\AppData\Roaming\npm-cache_git-remotes\git-https-github-com-SBats-angular2-schema-form-git-da7ac6dc990813943c717052e26d8f2a9010a644-6cf
526c4'...
npm ERR! fatal: Unable to find remote helper for 'git+https'

•  So, I downloaded the "da7ac6dc990813943c717052e26d8f2a9010a64" commit manually to node_modules/angular2-schema-form
• npm install
• npm run build
• cd to my project root
• ionic build android --prod
It threw the initial error again

[01:24:36]  ngc started ...
[01:24:40]  build prod failed: Unexpected value 'SchemaFormModule' imported by the module 'AppModule'
[01:24:40]  ionic-app-script task: "build"
[01:24:40]  Error: Unexpected value 'SchemaFormModule' imported by the module 'AppModule'

:-(

@SBats in package.json
"copy-template": "copyfiles './src/**/*.html' './dist/src'",
this command is not working properly. I tried
"copy-template": "copyfiles \"./src/**/*.html\" \"./dist\"",
this seems to do the copy action properly (Something to do with single quote and double quote)

Okay. I'll try to setup a Windows in order to test those issues in the same context as you.
You're still trying to use it on an ionic2 project, right?

Yes. Ionic 2.
Ionic Framework: 2.0.0-rc.4
Ionic Native: 2.2.11
Ionic App Scripts: 0.0.47
Angular Core: 2.2.1
Angular Compiler CLI: 2.2.1
Node: 6.9.2
OS Platform: Windows 7

At the moment, I can't make it work because of a conflict between core-js and typescript libraries loaded by Ionic 2. We might need to check if core-js is still needed for our module development.
I'm a bit busy at the moment but I will try to work on this.

@SBats It surprisingly works now without any issues :-)
All I did was updated my ionic project....

Any updates on this? I'm getting this same error after installing via npm on the angular4 release. I'm also on Windows and I've tried to work through the steps above but I'm still unable to get this working

It should be fixed with 1.0.0-beta.1

I didn't check it personally, But one of my colleagues reported that AOT compilation is successful.
Thanks a lot team :-) @ebrehault @SBats

You are welcome!
We also have to mention @fbessou who is doing great job here!


Leverage the Stripe Gems test data

Looks like a lot of the responses are already stubbed out in the official Stripe Gem. See if we can leverage those. It would probably help avoid API drift as the Stripe Gem would also need to update if the Stripe API ever changes.

Sorry to dredge this up, but I hadn't heard of stripe-ruby-mock before, and I just tried it out. It seems to include a lot more functionality than fake_stripe, so on first glance, it would seem like a better project, but I failed to notice that it doesn't stub Stripe.js like fake_stripe does.
Still, if the code here was added to stripe-ruby-mock, then we'd really have a great solution to stubbing Stripe completely.

Closing this because fake_stripe has been deprecated: https://github.com/thoughtbot/fake_stripe/pull/154


Loopback-ssl doesn't work with config.env.json

Need to make loopback-ssl recognize the correct config file based on env settings. Currently, it seems it will only recognize config.json and not config.test.json, config.staging.json, or config.production.json.

It is working in my case.
Are you using the command: NODE_ENV=production npm start ?


Amplify Frontend Build SSR Performance

I created a Next.JS app using their create-next-app tool as a starting point for my Amplify journey.  I then followed the steps to:
$ amplify init
$ amplify add hosting

I'm also using a monorepo, so I did everything around that, and the build succeeds.
However, the build consistently takes 10min+ to complete for what should be the most basic of "Hello World" apps.  I've narrowed it down to the SSR deploy part of the build.  Here is an output from my logs:
2022-06-10T22:17:02.337Z [INFO]: # Executing command: echo "PreBuild Dir:" /codebuild/output/src1234/src/my-monorepo/client-sites/my-app
...
2022-06-10T22:18:16.828Z [INFO]: Build Dir: /codebuild/output/src1234/src/my-monorepo/client-sites/my-app
2022-06-10T22:18:16.829Z [INFO]: # Executing command: npx lerna run build --scope '@client-sites/my-app'
...
2022-06-10T22:18:36.783Z [INFO]: @client-sites/my-app: Done in 11.10s.
2022-06-10T22:18:37.517Z [INFO]: Starting SSR Build...
2022-06-10T22:24:04.161Z [INFO]: SSR Build Complete.

As you can see, the time between Starting SSR Build... and SSR Build Complete is 6min+.  Can this performance be optimized at all?
I have two apps in my monorepo, one with an api folder and one without.  However, neither app has a "backend" configured in the Amplify configuration.  And both the my-app and my-app-no-api versions take 10min+.
Additionally, since this is the most basic template app from Next.JS, they don't even use SSR features.  (However, the "build" command in the package.json only contains next build so Amplify should treat them both as SSR's and not SSG's)
Below is a copy of the amplify.yml at the root of my repo.
Not sure if this is the right forum, but any assistance would be greatly appreciated!
And one more, somewhat related question... I am using yarn workspaces for my package management.  Is the caching for the node_modules/**/* correct in the build config?  (Would it actually capture the packages which are contained in the node_modules folder two levels higher?)
version: 1
applications:
  - appRoot: client-sites/my-app
    env:
      variables:
        key: value
    frontend:
      phases:
        preBuild:
          commands:
            - echo "PreBuild Dir:" $(pwd)
            - yarn install
            - npx lerna bootstrap
        build:
          commands:
            - echo "Build Dir:" $(pwd)
            - npx lerna run build --scope '@client-sites/my-app'
      artifacts:
        baseDirectory: '.next'
        files:
          - '**/*'
      cache:
        paths:
          - 'node_modules/**/*'
          - '.next/**/*'

  - appRoot: client-sites/my-app-no-api
    env:
      variables:
        key: value
    frontend:
      phases:
        preBuild:
          commands:
            - echo "PreBuild Dir:" $(pwd)
            - yarn install
            - npx lerna bootstrap
        build:
          commands:
            - echo "Build Dir:" $(pwd)
            - npx lerna run build --scope '@client-sites/my-app-no-api'
      artifacts:
        baseDirectory: '.next'
        files:
          - '**/*'
      cache:
        paths:
          - 'node_modules/**/*'
          - '.next/**/*'

We're attempting to move our Next.js app to Amplify, but experiencing many issues, and the excruciatingly slow build times have made debugging an absolute nightmare.

Hi @jd-carroll and @pjaws 👋🏽. the build times for SSR apps are currently longer than non-SSR apps because of the additional resources that need to be provisioned during the frontend build process such as the CloudFront distribution. You can see these additional resources and their IDs under the deploy tab.

Facing same issue.  I am using getServerSideProps to fetch from Appsyc API and the page performance is really poor. Looking the bundle size, the _app.js file is almost 4.8 MB

@jd-carroll Your app should be detected as SSR, you can confirm this by checking under General and you should see Next.js - SSR under "Framework".
Please re-open if you are still experiencing an issue.


docs: fix form_helper.rst

Description

fix XHTML void element tags

Checklist:

[x] Securely signed commits
[] Component(s) with PHPDoc blocks, only if necessary or adds value
[] Unit testing, with >80% coverage
[x] User guide updated
[] Conforms to style guide

Thank you @kenjis


Regular updates (late May)

remove or fix WebDAV remote info (close #1355)

@jorgeorpinel can we just merge this?

Sure, go ahead @shcheklein (needs your approval)


默认密码butongwifi 不正确，难道是我姿式不对？

admin
root
toor
butongwifi
都试了，进不了？

密码是：「password」，这个是lede的默认密码
Sent from my iPhone

On Feb 4, 2021, at 10:24 PM, 456vv<EMAIL_ADDRESS>wrote:

admin
root
toor
butongwifi
都试了，进不了？
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


TEST GH-PAGES WF: remove trivial comments

@turbomam: testing why the workflow that builds and deploys docs isn't working


Integration with Kubernetes Native Dual-Stack

Dual-stack support in kubernetes is underway (KEP). Phase-1 alpha recently merged into master and phase-2 is under active development.
Calico currently supports dual-stack independent of kubernetes; however, tighter integration with kubernetes dual-stack would be highly desirable.
Also, current dual-stack development efforts rely on simpler CNI plugins -- kubenet/bridge/host-local. Having early dual-stack support within calico would aid in testing dual-stack on: (i) more realistic/diverse deployments and (ii) e2e testing tools like KinD that use calico as their network plugin.

Are you seeing specific problems with Calico in these environments?  Does it not "just work"?

Are you seeing specific problems with Calico in these environments? Does it not "just work"?

The dual-stack work includes core API changes (e.g. PodSubnet in the Node object is now a slice), I assume these changes will require appropriate changes on the calico end. I'm not familiar with the calico code base, so I may just be wrong here.
I did manage to bring up a dual-stack cluster using a calico specific approach as documented here, but this is of course independent of the recent dual-stack changes in k8s. As more of the dual-stack PRs hit k8s master, I will attempt to integrate with calico. I'll add updates here.

Thanks for reporting this. We're looking at dual stack and IPv6, if there's information you'd like to contribute or PRs you'd like to propose we'd be very thankful.

I did manage to bring up a dual-stack cluster using a calico specific approach as documented here, but this is of course independent of the recent dual-stack changes in k8s. As more of the dual-stack PRs hit k8s master, I will attempt to integrate with calico. I'll add updates here.

Awesome, appreciate this. Someone on the Calico side should also try to review the new dual-stack KEP and add comments here with any work we identify. I think/hope it should be minimal.

@Arvinderpal I'm happy to say that the Calico integration with dual stack was done for our v3.11 release, as mentioned at https://docs.projectcalico.org/v3.11/release-notes/.
I think that means we can close this issue; please do open new issues if you notice anything missing.


Will the code be made available?

The paper/chapter (https://arxiv.org/pdf/2209.04242.pdf, https://link.springer.com/chapter/10.1007/978-3-031-16440-8_36) states that the code will be made available here. I would like to benchmark against this method. Any plans to post the code?

Hi @dhudsmith. Code is pushed. Apologies for the delay.


Crashing on firebase::app::Create

Library
Firebase C++ SDK: 4.0.2
Problem
Been adding the Firebase SDK to an Android application which has been going relatively smoothly (looks like a well-designed SDK btw) but when it hits:
Env::app = firebase::App::Create(firebase::AppOptions(), JniHelper::getEnv(), JniHelper::getActivity());

It crashes with jmethodID was NULL.
Additional Information
I've checked the output of JniHelper::getEnv() and JniHelper::getActivity() and they look valid. It also complains about the missing methods as in issue #7.
I imagine that the SDK code that calls CallObjectMethodV attempts to get a jmethodID for a method but fails (am I right in thinking their arn't any required Java methods for the Android C++ SDK to work?) and nothing picks up that failure so CallObjectMethodV is called with a null argument.
Stack Trace
07-09 22:41:59.173 5290-5343/PACKAGE_NAME W/System.err: java.lang.NoSuchMethodError: no non-static method "Lcom/google/firebase/FirebaseOptions;.getProjectId()Ljava/lang/String;"
07-09 22:41:59.173 5290-5343/PACKAGE_NAME W/System.err:     at org.cocos2dx.lib.Cocos2dxRenderer.nativeInit(Native Method)
07-09 22:41:59.173 5290-5343/PACKAGE_NAME W/System.err:     at org.cocos2dx.lib.Cocos2dxRenderer.onSurfaceCreated(Cocos2dxRenderer.java:73)
07-09 22:41:59.173 5290-5343/PACKAGE_NAME W/System.err:     at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1539)
07-09 22:41:59.173 5290-5343/PACKAGE_NAME W/System.err:     at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1270)
07-09 22:41:59.180 5290-5343/PACKAGE_NAME W/zygote: Skipping duplicate class check due to unrecognized classloader
07-09 22:41:59.181 5290-5316/PACKAGE_NAME D/FA: Connected to remote service
07-09 22:41:59.182 5290-5316/PACKAGE_NAME V/FA: Processing queued up service tasks: 2
07-09 22:41:59.201 5290-5343/PACKAGE_NAME I/firebase: Firebase App initializing app PACKAGE_NAME (default 1).
>>> CRASH >>>
07-09 22:41:59.266 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504] JNI DETECTED ERROR IN APPLICATION: jmethodID was NULL
07-09 22:41:59.266 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]     in call to CallObjectMethodV
07-09 22:41:59.266 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]     from void org.cocos2dx.lib.Cocos2dxRenderer.nativeInit(int, int)
07-09 22:41:59.266 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504] "GLThread 236" prio=5 tid=17 Runnable
07-09 22:41:59.266 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   | group="main" sCount=0 dsCount=0 flags=0 obj=0x12f695b8 self=0xa16f8c00
07-09 22:41:59.266 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   | sysTid=5343 nice=0 cgrp=default sched=0/0 handle=0x9078b970
07-09 22:41:59.266 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   | state=R schedstat=( 57357316 35185279 53 ) utm=2 stm=3 core=1 HZ=100
07-09 22:41:59.266 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   | stack=0x90689000-0x9068b000 stackSize=1038KB
07-09 22:41:59.266 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   | held mutexes= "mutator lock"(shared held)
07-09 22:41:59.267 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #00 pc 0047358b  /system/lib/libart.so (_ZN3art15DumpNativeStackERNSt3__113basic_ostreamIcNS0_11char_traitsIcEEEEiP12BacktraceMapPKcPNS_9ArtMethodEPv+203)
07-09 22:41:59.267 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #01 pc 0056ee2e  /system/lib/libart.so (_ZNK3art6Thread9DumpStackERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEEbP12BacktraceMapb+366)
07-09 22:41:59.267 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #02 pc 005696b3  /system/lib/libart.so (_ZNK3art6Thread4DumpERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEEbP12BacktraceMapb+83)
07-09 22:41:59.267 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #03 pc 00385e3e  /system/lib/libart.so (_ZN3art9JavaVMExt8JniAbortEPKcS2_+1374)
07-09 22:41:59.267 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #04 pc 003863c1  /system/lib/libart.so (_ZN3art9JavaVMExt9JniAbortVEPKcS2_Pc+113)
07-09 22:41:59.267 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #05 pc 0014ea45  /system/lib/libart.so (_ZN3art11ScopedCheck6AbortFEPKcz+69)
07-09 22:41:59.267 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #06 pc 0014e2c8  /system/lib/libart.so (_ZN3art11ScopedCheck13CheckMethodIDEP10_jmethodID+232)
07-09 22:41:59.267 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #07 pc 0014d191  /system/lib/libart.so (_ZN3art11ScopedCheck22CheckPossibleHeapValueERNS_18ScopedObjectAccessEcNS_12JniValueTypeE+289)
07-09 22:41:59.267 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #08 pc 0014c6b3  /system/lib/libart.so (_ZN3art11ScopedCheck5CheckERNS_18ScopedObjectAccessEbPKcPNS_12JniValueTypeE+1155)
07-09 22:41:59.267 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #09 pc 001524d9  /system/lib/libart.so (_ZN3art8CheckJNI13CheckCallArgsERNS_18ScopedObjectAccessERNS_11ScopedCheckEP7_JNIEnvP8_jobjectP7_jclassP10_jmethodIDNS_10InvokeTypeEPKNS_7VarArgsE+185)
07-09 22:41:59.267 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #10 pc 0015161d  /system/lib/libart.so (_ZN3art8CheckJNI11CallMethodVEPKcP7_JNIEnvP8_jobjectP7_jclassP10_jmethodIDPcNS_9Primitive4TypeENS_10InvokeTypeE+1133)
07-09 22:41:59.272 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #11 pc 0013b73b  /system/lib/libart.so (_ZN3art8CheckJNI17CallObjectMethodVEP7_JNIEnvP8_jobjectP10_jmethodIDPc+75)
07-09 22:41:59.272 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #12 pc 00494737  /data/app/PACKAGE_NAME-wnt1NlfuJlTadMzzuYlqPw==/lib/x86/libMyGame.so (???)
07-09 22:41:59.272 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #13 pc 0049e30c  /data/app/PACKAGE_NAME-wnt1NlfuJlTadMzzuYlqPw==/lib/x86/libMyGame.so (???)
07-09 22:41:59.272 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #14 pc 0049e8df  /data/app/PACKAGE_NAME-wnt1NlfuJlTadMzzuYlqPw==/lib/x86/libMyGame.so (_ZN8firebase3App6CreateERKNS_10AppOptionsEPKcP7_JNIEnvP8_jobject+501)
07-09 22:41:59.272 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #15 pc 0049eba1  /data/app/PACKAGE_NAME-wnt1NlfuJlTadMzzuYlqPw==/lib/x86/libMyGame.so (_ZN8firebase3App6CreateERKNS_10AppOptionsEP7_JNIEnvP8_jobject+55)
07-09 22:41:59.272 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #16 pc 004820dc  /data/app/PACKAGE_NAME-wnt1NlfuJlTadMzzuYlqPw==/lib/x86/libMyGame.so (_ZN11AppDelegate29applicationDidFinishLaunchingEv+824)
07-09 22:41:59.272 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #17 pc 004879ea  /data/app/PACKAGE_NAME-wnt1NlfuJlTadMzzuYlqPw==/lib/x86/libMyGame.so (_ZN7cocos2d11Application3runEv+24)
07-09 22:41:59.272 5290-5343/PACKAGE_NAME A/zygote: java_vm_ext.cc:504]   native: #18 pc 0048c5f4  /data/app/PACKAGE_NAME-wnt1NlfuJlTadMzzuYlqPw==/lib/x86/libMyGame.so (Java_org_cocos2dx_lib_Cocos2dxRenderer_nativeInit+223)

Looking for some quick clarification: I notice your callstack has cocos functions in it. Is this callstack from the firebase cocos2d-x sample app, or from a custom cocos app? If this crash was happening in the cocos sample app, I've recently updated the gradle build files to include the correct firebase library version (version 11.0.0, rather than 10.2.0). If this is a custom cocos app, can you verify for me that you're using the most up to date version of the library (11.0.0)? If everything is up to date and you're still seeing this let me know and I'll help you dig deeper.

This is a custom integration to a cocos app. I upgraded the library to 11.0.2, which is what I saw the updated documentation now says, and added the dependency to com.google.android.gms:play-services-base:11.0.2 and it no longer crashes. Thanks a lot!


Add follow/unfollow official game group option

Example: OC ask people to follow their official game group in this GA:
https://simplo.gg/index.php?giveaway=free-steam-key-athopiu

Looked into it, and this isn't a trivial thing to add.  Seeing as there's only been 1 of these, it's hard to justify the amount of work this would require.


Support version-less $schema keyword

Understanding JSON Schema:

It is recommended that all JSON Schemas have a $schema entry, which must be at the root. Therefore most of the time, you’ll want this at the root of your schema:
"$schema": "http://json-schema.org/schema#"

What do you think? We had to add a specific draft to our schemas.

It looks like http://json-schema.org/schema# redirects to the latest version (2019-09), which isn't supported yet:
% curl 'http://json-schema.org/schema#'
<!DOCTYPE html>

  <meta charset="utf-8">
  <title>Redirecting…</title>
  <link rel="canonical" href="/draft/2019-09/schema">
  <meta http-equiv="refresh" content="0; url=/draft/2019-09/schema">
  <meta name="robots" content="noindex">

Redirecting…

    Several redirections on json-schema.org are special cases:

The unversioned meta-schema URIs should no longer be used.

The vocabularies are represented by their specification text.

The "latest" specification URIs are for convenice of browser
        bookmarking only.

  Click here if you are not redirected.

It also says:

The unversioned meta-schema URIs should no longer be used.

Which draft did you intend to use? You shouldn't need to specify $schema if you're using the current default meta schema, which is 7:
https://github.com/davishmcclurg/json_schemer/blob/6bc8f60c9b48258828d51d65fc65adf0701eba0e/lib/json_schemer.rb#L36

You are right (see json-schema-org/json-schema-spec#216). In this case, what about to map it to the draft 4?

Unless there's a good reason not to, I'd rather leave the default as the latest supported version.

I don't mean to change the default, but to add a new mapping, something like this:
DRAFT_CLASS_BY_META_SCHEMA = {
    'http://json-schema.org/schema#' => Schema::Draft4,
    'http://json-schema.org/draft-04/schema#' => Schema::Draft4,
    …
  }.freeze

That doesn't seem quite right since http://json-schema.org/schema# still redirects to http://json-schema.org/draft/2019-09/schema
But I'm open to the change if it's true that http://json-schema.org/schema# was deprecated before later drafts were published.

Good point.
Well, yes, in Draft 5, there is no mention of the version-less URI whereas in Draft 4:

The "$schema" keyword
…

The following values are predefined:
http://json-schema.org/schema#  JSON Schema written against the
current version of the specification.

Sounds good to me. Feel free to open a PR with the change. Otherwise I'll get to it at some point.


Error: unexpected EOF from Bazel server

==> tensorflow : r0.9   bazel : 0.2.3  gcc:6.1.1  python: 3.5
When i try to compile tensorflow from source on my archlinux(kernel : 4.5.4-1) ,errror occured. Something like " Linking tensorflow/cc/ops/data_flow_ops_gen_cc [for host]
Error: nexpected EOF from Bazel server."

And when i tried again ,i got the same error but in compile file "tensorflow/core/common_runtime/simple_graph_execution_state.cc" . Maybe there is a bug in GCC-6.1.1 ?? How can I change the default compiler ? Thanks

This seems like a bazel issue, unfortunately.  @damienmg: Do you have any ideas?

Copy-paste of my answer on bazel-discuss to another similar issue:
"This means that something has killed Bazel during its run. I saw this behavior on some system where the memory of the OS was reaching the limit and the OOM killer was always choosing Bazel because it was the most memory consuming process."

Thanks @damienmg!  Closing since it is not a TensorFlow issue.


Optimize CI build time

This might reduce build times on CI.

Ah yeah, I included this patch... that should have gone to another PR, but I guess it doesn't matetr that much, does it?
Maybe there is more in terms of build time that can be done... don't know. I guess we can keep this open a bit until I figure some more optimizations out.

This now depends on #1297
Either way it is just an experiment by now.

Apparently, tests bind to the same address and port and thus cannot be run in parallel. Something that definitively has to be fixed.

Apparently, tests bind to the same address and port and thus cannot be run in parallel. Something that definitively has to be fixed.

So, these tests have to be run in serial manner.

Yep. Lets see what happens now, when each test has its individual broker. Would be nice if it simply worked, because this would be a huge speed improvement. Right now testing takes about 9 minutes, which is at least 7 minutes too long IMO.

Okay, now I am running into test failures that seem to not have something to do with how the tests are executed (or I am just not competent enough to see it right now).
I will carve out the patches that tinker with the test running and submit them another time in a seperate PR.
I still count this experiment a success for now:

Overall CI time is down from 21 minutes to 11 minutes
Build time is down from 8 minutes to 40 sec (although I am not 100% sure whether this is just a perfect cache hit :laughing: )
Test time is down from approx. 7 minutes to 5 minutes although most of that is probably the build time from building the test binaries in the job

So I am quite a bit concerned that the tests are failing here.
I did not touch any actual code in this PR, but only the .github folder. That means, I did not alter tests, but only how tests are run. That should have zero impact on the results of the tests (only on the speed).
That the tests are now failing shows me that there must be some issue with how the tests are implemented.
How to proceed?

So I am quite a bit concerned that the tests are failing here.

Indeed a concern. I need sometimes to understand what is going on.

Abandoned PR. Though it looked like the rust caching has already made into main.


Expert Masterlist - Experts from all category

Remove the filter to consider only Technology Experts
Map "Descriptive" Expert category to the tag version and use it in the type column
Area of Expertise (PG) Validation should be against PGs filtered by the Expert's category
Email After daily job with recap by category (and no verbose list of what was unchanged)

Are we saying that we will change the various type values from 'active', 'administrator' and 'deleted' to 'gde', 'marketing', 'productstrategy' and 'ux_ui' ?
I am not sure what is meant by Email After ...

Yes but still keeping deleted, admin and googlers are never configured but the web app uses the email to show the charts menu.
Last point is about the automated email sent after the gas function runs daily

Updated the GAS script to:

check the Expert Category is valid
check PGs by Category
Create Accounts as is without setting category on the account

TODOs:

set the Expert category on the Account object when we decided how to store this information

All the changes to the Expert Masterlist done and pushed updated Accounts


PR: Monkey patch Jedi 0.10.0 for numpydoc

This works now...but not ready for review yet.  I think I need some PEP8
It's a bit more of a mess than I would like but I have a plan to get this upstream faster.

Thanks a lot @bcolsen fir giving us a hand with this!

@ccordoba12 If it passes testing, It's ready for review.

You need to remove the pins I introduced on PR #4104 for setup.py and meta.yaml

Subscribing myself to this bug, since this would enable code completion to work on Debian with the packaged jedi version 0.10.0.

Just as a test run, I cherry-picked a squashed version of this PR on top of the current spyder-3.1.3 package on Debian, and code completion is now working with the packaged version of Jedi.
Many thanks @bcolsen.

It's true!! @bcolsen's work makes all our test suite to pass with Jedi 0.10.0. Thanks a lot @bcolsen!!
Please merge with 3.1.x to get some fixes to our tests, and then I'll merge ;-)

I also left another couple of (very simple) comments ;-)

I fixed the caching....I just changed it back to the way it was in 0.9.0 and that still works in 0.10.0
If it passes the tests it's ready to go.

@bcolsen, I added Jedi 0.10.0 to CircleCI and, as you can see, our tests are failing there (the other CIs are still using Jedi 0.9.0 because they can't be modified so easily, so please only look at the results in CircleCI).
Besides, I'd like to propose you to drop support for 0.9.0 and only focus on 0.10.0. The patches for 0.9 and 0.10 are very different, and since we won't be able to test both versions, I'd prefer to drop support for the oldest one. That'd also simplify your work ;-)

Wouldn't dropping jedi 0.10 simplify my work even more, 0.9 already works ;-)
Joking aside, I everything seems to work now. If you want, I can take out the 0.9 code but I think some users might not like that in a point release.  Maybe wait for 3.2?
The current solution:
If at first you don't succeed...Change the test.  ;-)
The problem:
jedi_plugin.py (line 61)
    def get_info(self, info):
        call_def = self.get_jedi_object('goto_definitions', info)
        for cd in call_def:
            if cd.doc and not cd.doc.rstrip().endswith(')'):
                call_def = cd
                break
        else:
            call_def = call_def[0]

This code gives an IndexError when call_def is an empty list.
Jedi 0.10 without any patching fails the two spyder tests with get_info(). As you can see in the code diff I fixed this by removing the extra characters after the function names. I'm not sure why the get_info() tests had extra characters after the function names, but It's strange that it works in 0.9 either.
Jedi 0.10.0
In [1]: import jedi
In [2]: jedi.__version__
Out[2]: '0.10.0'
In [3]: jedi.Script('import os: os.walk(').goto_definitions()
Out[3]: []
In [4]: jedi.Script('import os: os.walk').goto_definitions()
Out[4]: [<Definition def walk>]

Good, not an empty list. I changed the test and now 0.10.0 passes
Jedi 0.9.0
In [1]: import jedi
In [2]: jedi.__version__
Out[2]: '0.9.0'
In [3]: jedi.Script('import os: os.walk').goto_definitions()
Out[3]: []
In [4]: jedi.Script('import os: os.walk(').goto_definitions()
Out[4]: []

How does that work? I must be missing something here, 0.9.0 also passes.
For interest, considering that the pluging seem to be written before 0.9
Jedi 0.8.1
In [1]: import jedi
In [2]: jedi.__version__
Out[2]: '0.8.1-final0'
In [3]: jedi.Script('import os: os.walk(').goto_definitions()
Out[3]: []
In [4]: jedi.Script('import os: os.walk').goto_definitions()
Out[4]: [<Definition module os>]

Different again?

@ccordoba12 Are you satisfied with the latest changes from @bcolsen ? If so, could you ack it (even if pushed later), so I can start cherry-picking the final fix to the Debian package. Thanks.

I'll give it a final review on Wednesday.

Any news?

At least, can I have confirmation that all commits up to f9fe24d can be squashed and cherry-picked to v3.1.2 or v3.1.3 to get code completion working with Jedi 0.10? Thanks.
It is getting very unlikely v3.1.4 will be granted a freeze exception for Debian Stretch (due to the large change set since v3.1.2), but I can at least backport fixes for regressions in usability, such as broken code completion.

@ghisvail, tests are passing, so I'd say yes. However, I'd like to give this one a little bit of manual testing before merging. I'll promise you I'll do that this weekend ;-)

As far as testing is concerned, I have used a package I built locally with 3.1.3 + this patch cherry-picked on top of it and enjoyed using spyder with working code completion for the week.

Ok, merging this one then :-)
Thanks a lot @bcolsen!

@ccordoba12 Unfortunately, this PR does not apply cleanly on top of 3.1.2. It does on 3.1.3, so I will be rolling out an update of the packaging in Debian experimental with this fix, and try to make my case for an unblock request for Debian Stretch.

3.1.3 fixes a lot of segfaults introduced in 3.1.0 because of some odd focus bugs, so I'd really prefer if you use it instead of 3.1.2.

It would help me build my case if you could provide a separate listing containing only these fixed segfaults on Linux. The more comprehensive my request is, the more likely it will be accepted. Thanks.

Please take a look at our Changelog. Those segfaults affected all our supported OSes.

Please take a look at our Changelog

Since you personally reviewed most, if not all, the PR listed in this change log, you are best placed to identify the most critical issues. Even if it is just the top 3 or 5.

So you want to use only certain patches?

I mean, it's a bugfix release, so why not package the full release instead?

So you want to use only certain patches?

No.

I mean, it's a bugfix release, so why not package the full release instead?

That's the plan.
I'll provide some more context. Debian is in freeze, meaning new versions of software no longer migrate automatically to what is going to become the next stable release. Instead, updates of packages should be focusing on addressing release critical bugs affecting the frozen packages (such as failures to build, security issues, crashes...).
Updates to packages can migrate if an unblock request is granted from the release team, who will manually review the proposed changes and assess the necessity of such update (here to 3.1.3) from the current version in Stretch (here 3.1.2). Just providing a link to a big change log and writing "it is a bug fix release, do it." is not enough and is likely to upset the reviewers more than anything.
Hence myself asking whether you could make a selection of the most critical bugs fixed by 3.1.3, so I can provide a better case to the release team by pinpointing a few reproducible crashes / segfaults.

Ok, thanks for the thorough explanation. I'll provide you with the highlights of 3.1.3 this weekend.

Did you have a chance to look at it?
We now have version 3.1.3 + this fix in Debian experimental and would like to draft the unblock request quite soon.
Thanks.

The general picture: I consider 3.1.3 the first version in the 3.1 series that is stable enough to be used by the general public. All previous versions were semi-broken because of important bugs and I don't recommend to use them.
Critical bugs fixed in 3.1.3 (I don't link them with # because it makes no sense to do it in this issue):

4127 - Crash at startup, reported by Ubuntu users.
4122 - Segfault after closing the Run settings dialog
4088 - Segfault when trying to save figures in the IPython console.
4085 - Segfault when opening a file in a new Editor window.
4066 - Segfault when removing a variable in the console while it was being viewed in the Variable Explorer.

All these issues were caused by a couple of focus bugs introduced by our junior developers. It was not their fault really, we simply didn't know that changing focus policies for the main window and the application will have those terrible effects.
To avoid this in the future, we have expanded our test suite as much as we can in 3.1.3 and 3.1.4.

Thanks for providing the list of critical bugs, here is what I found:

4127 - Crash at startup, reported by Ubuntu users.

Not reproducible on Debian

4122 - Segfault after closing the Run settings dialog

Not reproducible on Debian (makes sense, we use the Qt5 backend and it only happens on Qt4)

4088 - Segfault when trying to save figures in the IPython console

Reproducible on Debian

4085 - Segfault when opening a file in a new Editor window.

Not reproducible on Debian (not sure why)

4066 - Segfault when removing a variable in the console while it was being viewed in the Variable Explorer.

Reproducible on Debian, but not your usual use case of the var explorer tbh.
To sum up, that gives me 2 bugs out of 5 which are reproducible with the current package, including one for an atypical use case. That does not give me much of a case but I'll try.

I hope my opinion counts too :-) I mean, there are other annoying bugs (like wrong auto-indentation, no new breakpoints in the IPython console while debugging and broken maximizing-the-current-pane button) and I don't want to keep telling people: please update because those things were fixed already.
I have to say that that really bothers me as a maintainer: we're doing our duty of releasing bugfix versions, but they are not being picked up by Debian. At least those versions should be easily backported to the stable Debian branch.
Sigh, unfortunately I know that's a lost battle with Debian....

I hope my opinion counts too :-)

I voiced your opinion, and referenced all your supporting material, in the following request for unblock. The rest is up to the release team at this point.

I have to say that that really bothers me as a maintainer: we're doing our duty of releasing bugfix versions, but they are not being picked up by Debian.

They are. The software is currently up-to-date in the experimental channel.

At least those versions should be easily backported to the stable Debian branch.

We will provide backports of bugfix releases in a stretch-backports channel.

Ok, thanks for the good news!

The unblock request has been accepted. Debian Stretch will have 3.1.3 + this fix + #4311 for now. If 3.1.4 gets released soon enough, I might try to request another unblock again.


python312Packages.volkszaehler: 0.4.0 -> 0.5.0

Diff: https://github.com/home-assistant-ecosystem/python-volkszaehler/compare/refs/tags/0.4.0...0.5.0
Changelog: https://github.com/home-assistant-ecosystem/python-volkszaehler/releases/tag/0.5.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 301067 run on x86_64-linux 1

4 packages built:

python311Packages.volkszaehler
python311Packages.volkszaehler.dist
python312Packages.volkszaehler
python312Packages.volkszaehler.dist


?_pretty=1 option for pretty-printing JSON output

Suggested by @frankieroberto in https://github.com/simonw/datasette/issues/782#issuecomment-782746755

This is another change which is a little bit hard to find out because I haven't solved #878 yet.


More UnicodeDecodeError issues

I am having problems trying to communicate with a R&S spectrum analyzer at GPIB address 20 attached to an ICS 9065 Ethernet to GPIB gateway. I have observed the same kinds of problems with the release versions of PyVISA and PyVISA-Py, and in tests on both Mac OS X and Debian Linux environments. The following output is from a run under Debian Linux:
$ python -m visa info
Machine Details:
   Platform ID:    Linux-3.16.0-4-amd64-x86_64-with-debian-8.4
   Processor:

Python:
   Implementation: CPython
   Executable:     /opt/anaconda-2.4.0/envs/build_spurious/bin/python
   Version:        2.7.11
   Compiler:       GCC 4.4.7 20120313 (Red Hat 4.4.7-1)
   Bits:           64bit
   Build:          Dec  6 2015 18:08:32 (#default)
   Unicode:        UCS4

PyVISA Version: 1.9.dev0

Backends:
   ni:
      Version: 1.9.dev0 (bundled with PyVISA)
      Binary library: Not found
   py:
      Version: 0.3.dev0
      ASRL INSTR:
         Please install PySerial to use this resource type.
         No module named serial
      TCPIP INSTR: Available
      USB RAW:
         Please install PyUSB to use this resource type.
         No module named usb
      USB INSTR:
         Please install PyUSB to use this resource type.
         No module named usb
      GPIB INSTR:
         Please install linux-gpib to use this resource type.
         No module named gpib
      TCPIP SOCKET: Available

Test code:
import visa

class Vxi(object):
  def __init__(self):
    visa.log_to_screen()
    rm = visa.ResourceManager('@py')
    rm.open_resource('TCPIP::<IP_ADDRESS>::gpib0,20::INSTR')

if __name__ == "__main__":
  foo = Vxi()

Output:
(build_spurious)lgadalla@fvxenrf02:~$ python test.py
2016-04-23 00:04:33,938 - pyvisa - DEBUG - SerialSession was not imported No module named serial.
2016-04-23 00:04:33,939 - pyvisa - DEBUG - USBSession and USBRawSession were not imported No module named usb.
2016-04-23 00:04:33,941 - pyvisa - DEBUG - TCPIPSession was correctly imported.
2016-04-23 00:04:33,942 - pyvisa - DEBUG - GPIBSession was not imported No module named gpib.
2016-04-23 00:04:33,942 - pyvisa - DEBUG - Created library wrapper for unset
2016-04-23 00:04:33,942 - pyvisa - DEBUG - Created ResourceManager with session 2257909
2016-04-23 00:04:33,942 - pyvisa - DEBUG - TCPIP::<IP_ADDRESS>::gpib0,20::INSTR - opening ...
2016-04-23 00:04:33,942 - pyvisa - DEBUG - RawTCPClient: connecting to socket at (<IP_ADDRESS>, 111)
2016-04-23 00:04:33,946 - pyvisa - DEBUG - Make call <PortMapperVersion.get_port: 3>, (395183, 1, 6, 0), <bound method PortMapperPacker.pack_mapping of <pyvisa-py.protocols.rpc.PortMapperPacker instance at 0x7fc06fef10e0>>, <bound method PortMapperUnpacker.unpack_uint of <pyvisa-py.protocols.rpc.PortMapperUnpacker instance at 0x7fc06fe98d88>>
Traceback (most recent call last):
  File "/opt/anaconda-2.4.0/envs/build_spurious/lib/python2.7/logging/__init__.py", line 853, in emit
    msg = self.format(record)
  File "/opt/anaconda-2.4.0/envs/build_spurious/lib/python2.7/logging/__init__.py", line 726, in format
    return fmt.format(record)
  File "/opt/anaconda-2.4.0/envs/build_spurious/lib/python2.7/logging/__init__.py", line 465, in format
    record.message = record.getMessage()
  File "/opt/anaconda-2.4.0/envs/build_spurious/lib/python2.7/logging/__init__.py", line 329, in getMessage
    msg = msg % self.args
UnicodeDecodeError: 'ascii' codec can't decode byte 0x86 in position 14: ordinal not in range(128)
Logged from file rpc.py, line 296
2016-04-23 00:04:34,201 - pyvisa - DEBUG - Received record through <socket._socketobject object at 0x7fc06fed8830>: '\x00\x00\x00\x01\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x15\xb3'
2016-04-23 00:04:34,201 - pyvisa - DEBUG - RawTCPClient: closing socket
2016-04-23 00:04:34,202 - pyvisa - DEBUG - RawTCPClient: connecting to socket at (<IP_ADDRESS>, 5555)
2016-04-23 00:04:34,202 - pyvisa - DEBUG - Make call 10,<PHONE_NUMBER>L, 0, 10000, u'gpib0,20'), <bound method Vxi11Packer.pack_create_link_parms of <pyvisa-py.protocols.vxi11.Vxi11Packer instance at 0x7fc06fee8d88>>, <bound method Vxi11Unpacker.unpack_create_link_resp of <pyvisa-py.protocols.vxi11.Vxi11Unpacker instance at 0x7fc06fee8dd0>>
Traceback (most recent call last):
  File "/opt/anaconda-2.4.0/envs/build_spurious/lib/python2.7/logging/__init__.py", line 853, in emit
    msg = self.format(record)
  File "/opt/anaconda-2.4.0/envs/build_spurious/lib/python2.7/logging/__init__.py", line 726, in format
    return fmt.format(record)
  File "/opt/anaconda-2.4.0/envs/build_spurious/lib/python2.7/logging/__init__.py", line 465, in format
    record.message = record.getMessage()
  File "/opt/anaconda-2.4.0/envs/build_spurious/lib/python2.7/logging/__init__.py", line 329, in getMessage
    msg = msg % self.args
UnicodeDecodeError: 'ascii' codec can't decode byte 0xaf in position 15: ordinal not in range(128)
Logged from file rpc.py, line 296
2016-04-23 00:04:34,458 - pyvisa - DEBUG - Received record through <socket._socketobject object at 0x7fc06fe4ec90>: '\x00\x00\x00\x01\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x00\x00\x07\xd4\x00\x00\x04\x00'
2016-04-23 00:04:34,458 - pyvisa - DEBUG - TCPIP::<IP_ADDRESS>::gpib0,20::INSTR - is open with session 1539275
2016-04-23 00:04:34,459 - pyvisa - DEBUG - TCPIP::<IP_ADDRESS>::gpib0,20::INSTR - closing
2016-04-23 00:04:34,459 - pyvisa - DEBUG - Make call 23, 512, <bound method Vxi11Packer.pack_device_link of <pyvisa-py.protocols.vxi11.Vxi11Packer instance at 0x7fc06fee8d88>>, <bound method Vxi11Unpacker.unpack_device_error of <pyvisa-py.protocols.vxi11.Vxi11Unpacker instance at 0x7fc06fee8dd0>>
Traceback (most recent call last):
  File "/opt/anaconda-2.4.0/envs/build_spurious/lib/python2.7/logging/__init__.py", line 853, in emit
    msg = self.format(record)
  File "/opt/anaconda-2.4.0/envs/build_spurious/lib/python2.7/logging/__init__.py", line 726, in format
    return fmt.format(record)
  File "/opt/anaconda-2.4.0/envs/build_spurious/lib/python2.7/logging/__init__.py", line 465, in format
    record.message = record.getMessage()
  File "/opt/anaconda-2.4.0/envs/build_spurious/lib/python2.7/logging/__init__.py", line 329, in getMessage
    msg = msg % self.args
UnicodeDecodeError: 'ascii' codec can't decode byte 0xaf in position 15: ordinal not in range(128)
Logged from file rpc.py, line 296
2016-04-23 00:04:34,462 - pyvisa - DEBUG - Received record through <socket._socketobject object at 0x7fc06fe4ec90>: '\x00\x00\x00\x02\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
2016-04-23 00:04:34,462 - pyvisa - DEBUG - RawTCPClient: closing socket
2016-04-23 00:04:34,462 - pyvisa - DEBUG - TCPIP::<IP_ADDRESS>::gpib0,20::INSTR - is closed

Please see pull request #97


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/818 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit 0d97882:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-05-18-01-41-43 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Question: Would this work with Microsoft DocumentDb IQueryable implementation?

Thanks
Chris

Hey Chris,
I haven't had a chance to play with this library and DocumentDb yet, however the goal is for it to work with any IQueryable implementation. Some queryable providers require special handling for edge case situations, which I've been adding as I discover them, but in general there's nothing super complicated going on such that I wouldn't expect it to work for some given IQueryable implementation.
I don't have a DocumentDB instance to play with right now, so if you start using it with one let me know in this issue if it does or doesn't work.

@ckimes89 Just as FYI, you can run a free DocumentDB emulator locally:
https://docs.microsoft.com/en-us/azure/documentdb/documentdb-nosql-local-emulator
It doesn't handle all scenarios, such as Partitioned Collections, but it would be a good start...
Thanks for the great project  👍

Has anyone given this ago? Will probably try doing a basic graphql-net to cosmos db (with the sql api) in the next few days to see if it plays nice.

Ran off the source and debugged some tests. Saw existing test NestedEntity which pulls back user and their linked account (foreign key). It's not quite the same as my failing query though, which uses nesting but from the same document. CosmosDb allows you to define a document (e.g. user) with nesting on the document itself. So my user looks like:
{
  id,
  profile {
    age,
    gender
  },
  settings: {
    ...
  }
},

Issue is that in GraphQL.Net.Executor::MapResults tries to source a Get property and dynamically invoke it, with type.GetProperty(field.Name).GetGetMethod().Invoke(queryObject, new object[] { }) but in my case type (of queryObject) is JProperty from Newtonsoft, so GetProperty(field.Name) is null. I can put a clause in that checks for this type and if so casts to a JProperty and returns the value straight out, but I'm not sure what happens if the nesting goes further. For instance, what if I have user's website comments in this doc too and need to dig more levels in?
I'm really just scraping the surface of how this works so forgive me. Looks like the executor is operating on some kind of dynamic types, but that only goes one level down? With my change I no longer have the exception, but the profile field comes back as an array with the the property name and value as object items, rather than just a straight object.
Will keep playing. Any help or direction would be greatly appreciated. I'm sure I'm not the only one who would love to see GraphQL on top of CosmosDB.


New release (to NuGet) to bind to Mongo C# Driver 1.10.1

I would like to see MongoRepository updated to use the latest 1.10.x version of the Mongo C# Driver and published to NuGet.

https://www.nuget.org/packages/MongoRepository/1.6.9

Awesome...thank you!


Introduce mutagen

Introduce mutagen to the codebase.

Patch 1: Introduce mutagen and mutate a bunch of already tested methods
Patch 2: Mutate U256::bits() and fix tests as required
Patch 2: Mutate U256::is_max() and fix tests as required

Going forward, the idea is to add mutation to functions/methods along with the required fixes, each in its own patch (and possibly its own PR). I'll probably batch a few patches together for a single file like I do here with patch 2 and 3.
For context on this PR see: https://github.com/rust-bitcoin/rust-bitcoin/pull/1484

Oh bother, I'm going to close this and discuss the problem on #1484 to keep the discussion in one place.


Include response body when --publish errors

A small improvement re: #1473
Simply includes the response's body in the error message.
Here's an example:
$ # before
$ CUCUMBER_PUBLISH_URL="http://localhost:4567/422 -X GET" be cucumber --publish
Traceback (most recent call last):
	2: from /home/jmks/.asdf/installs/ruby/2.7.2/lib/ruby/gems/2.7.0/gems/cucumber-5.1.3/lib/cucumber/formatter/io.rb:40:in `block (3 levels) in new'
	1: from /home/jmks/.asdf/installs/ruby/2.7.2/lib/ruby/gems/2.7.0/gems/cucumber-5.1.3/lib/cucumber/formatter/http_io.rb:75:in `close'
/home/jmks/.asdf/installs/ruby/2.7.2/lib/ruby/gems/2.7.0/gems/cucumber-5.1.3/lib/cucumber/formatter/http_io.rb:128:in `send_content': request to http://localhost:4567/422 failed with status 422 (StandardError)

$ # after
$ CUCUMBER_PUBLISH_URL="http://localhost:4567/422 -X GET" be cucumber --publish
Traceback (most recent call last):
	2: from ~/src/cucumber-ruby/lib/cucumber/formatter/io.rb:40:in `block (3 levels) in new'
	1: from ~/src/cucumber-ruby/lib/cucumber/formatter/http_io.rb:75:in `close'
~/src/cucumber-ruby/lib/cucumber/formatter/http_io.rb:128:in `send_content': request to http://localhost:4567/422 failed with status 422: you did something wrong (StandardError)

from the "server":
require "sinatra"

get "/422" do
  [422, "you did something wrong"]
end

Seems legit. Probably worth putting a little changelog entry in as well if you can. Should be easy enough to approve and merge.

Good point about the changelog. I've updated it.


java cask not updated

In my case I have java 1.8.0_60 installed, from the cask formulae I see that there is a new version java 1.8.0_66.
But when I run brew cask update, the new version won't be installed.
Am I doing something wrong ?
myhost:~ myuser$ brew cask list
java   java7
myhost:~ myuser$ /usr/libexec/java_home -V
Matching Java Virtual Machines (5):
    1.8.0_60, x86_64:	"Java SE 8"	/Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home
    1.7.0_79, x86_64:	"Java SE 7"	/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home
    1.7.0_75, x86_64:	"Java SE 7"	/Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home
    1.6.0_65-b14-466.1, x86_64:	"Java SE 6"	/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
    1.6.0_65-b14-466.1, i386:	"Java SE 6"	/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home

/Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home
myhost:~ myuser$ brew cask info java
java: 1.8.0_66-b17
Java, Java Standard Edition Development Kit
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
Not installed
https://github.com/caskroom/homebrew-cask/blob/master/Casks/java.rb
==> Contents
  JDK 8 Update 66.pkg (pkg)
==> Caveats
This Cask makes minor modifications to the JRE to prevent issues with
packaged applications, as discussed here:

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=411361

If your Java application still asks for JRE installation, you might need
to reboot or logout/login.

Installing this Cask means you have AGREED to the Oracle Binary Code
License Agreement for Java SE at

  http://www.oracle.com/technetwork/java/javase/terms/license/index.html

myhost:~ myuser$ brew cask update
Updated 2 taps (caskroom/cask, caskroom/versions).
No changes to formulae.

brew cask update is for updating the tap itself. There still isn't an actual "update" functionality yet.
You can use brew cask uninstall java && brew cask install java as a temporary workaround.

Thanks @adityadalal924 !


Create a page for planning a trip on clicking Plan a trip button.

Is your feature request related to a problem? Please describe.
On clicking plan a trip button website is not directed to any page.

Describe the solution you'd like
Create a page for planning a trip on clicking Plan a trip button

Are you contributing under any open-source program ?
JWoC 24

@pranjal12-web You are assigned. you can start working on this issue


[bug]: prompt cross attention t_start defaults to 0.1 instead of 0

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Linux
GPU
cuda
VRAM
24GB
What happened?
It appears the default value for t_start is 0.1 when it should be 0. Manually specifying 0.1 produces the same output as not specifying t_start, while looks like you'd expect when compared to manually specifying 0.
Screenshots
No response
Additional context
No response
Contact Details
No response

Ah, I see that this was changed in https://github.com/invoke-ai/InvokeAI/pull/2385 purposefully.


Error generating code. Check the Developer Console AND the backend logs for details. Feel free to open a Github issue.

Error generating code. Check the Developer Console AND the backend logs for details. Feel free to open a Github issue.
Please tell me what's going on. I keep getting this error after uploading pictures.
I didn’t see the error on the front end because I don’t know python, so it’s very strange.
Or you can try it first, and if possible, we will buy it.

Try downgrading your Python to python:3.12.3 or lower. The new version of Pydantic has some issues with the later Python versions.

OK thanks I'll try it

Hello, I lowered the version to 3.10.5
Error generating code. Please contact support.

Hi, it's probably an issue with your API keys. Your screenshot doesn't seem to have uploaded correctly.


Switch to Parcel

https://blog.daftcode.pl/hyperapp-parcel-71823bd93f1c

Closing as no longer using Hyperapp


Added empty assets/js, assets/css, assets/wasm directories to codebase

As mentioned in the comment, the build process (e.g. "from scratch") also requires the assets/js, assets/css, assets/wasm directories to exist.
Added these empty directories to codebase using .gitignore approach adviced here.
If this approach is not suitable to this project, please suggest which solution to implement, and I'll try to change this PR to alternative approach.

Nice


Ignoring silently 'null' arguments passed to 'basicAuthentication' method

Relates to this issue.

Very nice! Thank you for the tests!!!


[BUG] Improper numbering/formatting  in messages

Describe the bug
Improper numbering in the android app compared with the web app. (Please have a look at the screenshots included below)
Screenshots
Message in the web app

Same message in the android app

Note the difference in numbering in the android app(1 to 7) compared to that of the web app (1 to 2 and 1 to 5)
Devices and Versions
Your Rocket.Chat.Android version: 3.2.0

That supposed to be Problem with Markwon lib. I would like to look into this. If you are not looking in this


version 1.0.0 while require “prelude”

I use the windows Ubuntu 18.06 subsystem, which was running well yesterday, but today I have error while require "prelude"。There are no other infomation offered.
I wonder know why.
the crystal env is normal.

I reset the subsystem, it works.


Fix for WFLY-16800 and WFLY-16801, Galleon plugins and Bootable JAR upgrades

Issues:
https://issues.redhat.com/browse/WFLY-16800
https://issues.redhat.com/browse/WFLY-16801

Thanks @jfdenise


debian/control: libucode Recommends ucode-modules

When installing the ucode with apt it doesn't install the ucode-modules by default.
I added it as a Recommends: dependency. Now it will be installed by default but you still can skip it.
Declaring relationships between packages

Merged, thanks!


Transforming Images , MIT Computational Thinking Spring 2021 | Lecture 2

Transforming Images , MIT Computational Thinking Spring 2021 | Lecture 2
1:25 Announcement: Lectures will be nearly an hour
2:30 Unitful.jl package: adding units to numbers just works in Julia
5:40 Transforming images
6:15 Downsampling/Upsampling
8:55 Linear Combinations (Combining images)
12:20 element-wise multiplication (broadcast)
14:48 Convex Combinations
18:35 Fun with Photoshop
23:50 Image Filtering (convolutions)
27:17 Definition of convolutions and kernels
28:04 Computer Science: Complexity
28:51 Computer Science: Architectures, GPUs or Graphical Processing Units
30:50 Playing with a few kernels
41:17 Gaussian Filter
47:05 Computer Science: Data Structure: Offset Arrays
49:00 Discrete vs Continuous
50:55 Respect my Boundaries
Also, I was wondering if it's possible to switch this lecture's position in the playlist to the 2nd position?

Done and Done. Thank you!


test: add tests for examples

Related PRs:

https://github.com/aquasecurity/trivy/pull/7578
https://github.com/aquasecurity/trivy/pull/7407
https://github.com/aquasecurity/trivy-checks/pull/271

TODO:

use YAML examples

Close in favor of https://github.com/aquasecurity/trivy-checks/pull/297


CSL JSON/YAML names should not be parsed for particles by default

When using CSL JSON/YAML databases, pandoc-citeproc tries to parse particles from names.
This does not conform to the CSL specs and leads to incorrect results when a family name contains strings that look like, but in fact are not, particles.
pandoc-citeproc should stop trying to parse particles by default when using CSL JSON and CSL YAML databases – to conform to the CSL specs, and to ensure interoperability with other software that does.
Example:
cat > a3.json << EOT
[
	{
		"id": "id1",
		"type": "book",
		"title": "Test 1 - “van” is non-dropping-particle",
		"author": [
			{
				"family": "Author",
				"given": "Al",
				"non-dropping-particle": "van"
			}
		],
		"issued": { "date-parts": [[ "2014" ]] }
	},
	{
		"id": "id2",
		"type": "book",
		"title": "Test 2 - “van” is fixed part of family name",
		"author": [
			{
				"family": "van Author",
				"given": "Al"
			}
		],
		"issued": { "date-parts": [[ "2014" ]] }
	}
]
EOT

pandoc  -F pandoc-citeproc --biblio a3.json -t plain << EOT

---
csl: https://gist.githubusercontent.com/nickbart1980/245c0027350cfbc44b72/raw/ade2a724e125074e9e432d8b7da1c54283efb56c/chicago-author-date--demote-display-and-sort.csl
...

@id1; @id2

# References
EOT

Actual:
van Author (2014); van Author (2014)

REFERENCES

Author, Al van. 2014. _Test 1 - “van” Is Non-Dropping-Particle_.

Author, Al van. 2014. _Test 2 - “van” Is Fixed Part of Family Name_.

Expected:
van Author (2014); van Author (2014)

REFERENCES

Author, Al van. 2014. _Test 1 - “van” Is Non-Dropping-Particle_.

van Author, Al. 2014. _Test 2 - “van” Is Fixed Part of Family Name_.

Notes:
The custom csl style uses demote-non-dropping-particle="display-and-sort", so that, to make the difference clear, whatever is parsed as non-dropping particle is shown after the first name.
Again, parsing of names is not part of the official CSL specs. If pandoc-citeproc wants to continue to offer it as an option, then when using CSL JSON/YAML databases it should only be activated when pandoc-citeproc is explicitly asked to do so, i.e., when the (citeproc-js, but not official CSL) per-entry flag parse-names is set, or via a command line switch. Note that if pandoc-citeproc does parse, it needs to exclude from parsing name fields that are enclosed in double quotes (see https://github.com/jgm/pandoc-citeproc/issues/151).

I've changed the parse-names default to False.
You can try the latest by pulling from the repository and
using 'stack test'.  (I suggest installing stack
https://github.com/commercialhaskell/stack/
rather than using cabal, though cabal should still work.)
issue77 test now fails.  I think the test may need some
adjusting in light of the changed default for parse-names.
Could you look at it?
+++ nickbart1980 [Sep 09 15 03:02 ]:

When using CSL JSON/YAML databases, pandoc-citeproc tries to parse
particles from names.
This does not conform to the CSL specs and leads to incorrect results
when a family name contains strings that look like, but in fact are
not, particles.
pandoc-citeproc should stop trying to parse particles by default when
using CSL JSON and CSL YAML databases – to conform to the CSL specs,
and to ensure interoperability with other software that does.
Example:
cat > a3.json << EOT
[
{
"id": "id1",
"type": "book",
"title": "Test 1 - “van” is non-dropping-particle",
"author": [
{
"family": "Author",
"given": "Al",
"non-dropping-particle": "van"
}
],
"issued": { "date-parts": [[ "2014" ]] }
},
{
"id": "id2",
"type": "book",
"title": "Test 2 - “van” is fixed part of family name",
"author": [
{
"family": "van Author",
"given": "Al"
}
],
"issued": { "date-parts": [[ "2014" ]] }
}
]
EOT
pandoc  -F pandoc-citeproc --biblio a3.json -t plain << EOT

csl: https://gist.githubusercontent.com/nickbart1980/245c0027350cfbc44b72/raw/ad
e2a724e125074e9e432d8b7da1c54283efb56c/chicago-author-date--demote-display-and-s
ort.csl
...
@id1; @id2
References
EOT
Actual:
van Author (2014); van Author (2014)
REFERENCES
Author, Al van. 2014. Test 1 - “van” Is Non-Dropping-Particle.
Author, Al van. 2014. Test 2 - “van” Is Fixed Part of Family Name.
Expected:
van Author (2014); van Author (2014)
REFERENCES
Author, Al van. 2014. Test 1 - “van” Is Non-Dropping-Particle.
van Author, Al. 2014. Test 2 - “van” Is Fixed Part of Family Name.
Notes:
The custom csl style uses
demote-non-dropping-particle="display-and-sort", so that, to make the
difference clear, whatever is parsed as non-dropping particle is shown
after the first name.
Again, parsing of names is not part of the official CSL specs. If
pandoc-citeproc wants to continue to offer it as an option, then when
using CSL JSON/YAML databases it should only be activated when
pandoc-citeproc is explicitly asked to do so, i.e., when the
(citeproc-js, but not official CSL) per-entry flag parse-names is set,
or via a command line switch. Note that if pandoc-citeproc does parse,
it needs to exclude from parsing names that are enclosed in double
quotes (see [1]#151).
—
Reply to this email directly or [2]view it on GitHub.
References

https://github.com/jgm/pandoc-citeproc/issues/151
https://github.com/jgm/pandoc-citeproc/issues/164

Wait, this is not about parsing bibtex/biblatex databases at all, it’s only about CSL JSON and CSL YAML databases, which already contain fully parsed names. If you revert the changes to Bibtex.hs, does the issue77 test still fail?

It seemed to me that the changes to Bibtex.hs were
warranted.  The bibtex parser already has code to parse
names into prefixes and the like.  So, why should it
set parse-names to True?
+++ nickbart1980 [Sep 09 15 13:18 ]:

Wait, this is not about parsing bibtex/biblatex databases at all, it’s
only about CSL JSON and CSL YAML databases, which already contain fully
parsed names. If you revert the changes to Bibtex.hs, does the issue77
test still fail?
—
Reply to this email directly or [1]view it on GitHub.
References

https://github.com/jgm/pandoc-citeproc/issues/164#issuecomment-139034584

Ok, that was a shot in the dark, sorry. It seems the names in the data used for issue77 (see https://github.com/jgm/pandoc-citeproc/issues/77) all contain a suffix in the given field and thus now all need to have parse-names: true added.

OK, this seems to be fixed by the latest commits!

I will also note that Zotero now appears to be correctly breaking out "Jr", "III", etc. into a separate 'suffix' field, so the original problem I noted shouldn't be an issue any longer. I haven't tested it with the most recent commits, but here's an example:
{"id":"robertson:1946note","type":"article-journal","title":"A Note on the Classical Origin of \"Circumstances\" in the Medieval Confessional","container-title":"Studies in Philology","page":"6-14","volume":"43","issue":"1","source":"JSTOR","URL":"http://www.jstor.org/stable/4172741","journalAbbreviation":"Studies in Philology","author":[{"family":"Robertson","given":"D.W.","suffix":"Jr"}],"issued":{"date-parts":[["1946",1]]},"accessed":{"date-parts":[["2014",3,19]]}}


docs(MeshAccessLog): add info about targetRef MeshGateway

Can we display the info like this?

I think the idea is good. Would be nice down the road to have this table be a plugin as we're for sure growing in complexity here :)


Refactor SnapManager

What have you changed? (mandatory)
Refactor SnapManager to achieve:

[x] More simple API, especially without explicitly register/deregister.
[x] More clear internal implement.
[x] Check snapshot stale when generating, sending and applying snapshots.
[x] forbid to store too many snapshot (gen/rev) files on disk.
[x] Simplify something in PeerStorage.

Other tasks:

[x] More test cases.

What are the type of the changes? (mandatory)
Improvement.
How has this PR been tested? (mandatory)
It's WIP, not tested yet. So you can review it later.

That's a temp file. Should be deleted.

Registry is simplified. @zhangjinpeng1987 PTAL thanks.

@overvenus @BusyJay PTAL thanks.

@siddontang It's hard to split. We can review it by this:
All files in src/raftstore/store/snap is migrated from src/raftstore/store/snap.rs. So it's hard to split and we can review them begin at SnapManager, and then builder.rs and reader.rs.
Changes in peer_storage.rs and worker/region.rs are just for introducing SnapStaleNotifier, so it's very easy to review. We can just take a look after components listed above are passed.


Identify POPL(CCF A ) as  PACM PL(CCF C)

Identify Proceedings of the ACM on Programming Languages(POPL, CCF A) as Proceedings of the ACM on Programming Languages (PACM PL, CCF C)
For Example：RustBelt: Securing the foundations of the Rust programming language

The problem has been around for a long time, Thanks for noticing!
Best regards.

Yes, this issue also applied to OOPSLA (CCF-A).

Dear all,
Thank you for bringing this issue to our attention.
Thanks to @MarkLee131's pull request, the issue has been resolved.
The fix has now been merged and is currently awaiting review for release in the app store.
If you encounter any other issues, please feel free to report them.
Thank you for your attention, and wish you all the best in your academic endeavors.

@all-contributors please add @SeddonShen for bug


[17.06] backport: Avoid race when opening exec fifo

backport:

https://github.com/opencontainers/runc/pull/1698 Avoid race when opening exec fifo

with cherry-pick:
git cherry-pick -s -x 8d3e6c9 5c0af14

no conflicts

LGTM


[FEA] round and bround SQL functions

Is your feature request related to a problem? Please describe.
It would be great to support the round and bround SQL functions.
https://github.com/rapidsai/cudf/issues/3790 was filed to implement them in cudf.

It looks like the cudf side has been implemented by https://github.com/rapidsai/cudf/pull/6685

Yes, I was planning to start on cudf Java work on this once I am done with binary operations for decimal type.


Issues with jspsych-form plugin #465

Running the jspsych-form example file gives me error. When I run it in Chrome I got Uncaught TypeError: Cannot read property 'insertAdjacentHTML' of null and running it in Firefox gives me TypeError: jsPsych.plugins[trial.type].info is undefined

@GavinQ1 If you have time to look at this that would be great. I suspect this is because the info method for the plugin isn't implemented, and some of the recent changes mean that the info method is mandatory.

This plugin is not included in recent versions, so I'm closing this as out of date.


Outdated Cocoapods repository

Could you update cocoapods repository please? I think it is outdated.
Thanks.

Hello!
We can't update cocoapods, until we will release next version of Quickblox SDK.
Will try to make this release as soon as possible!

Thank you for your hard work. These services are great.