Updated byteFormat dependency to avoid dependency 404 issues

Original error:
(base) ➜  app deno run --allow-net --allow-read --allow-env mod.ts
Download https://github.com/alejandroq/mysql/raw/master/mod.ts
Download https://raw.githubusercontent.com/alejandroq/mysql/master/src/constant/capabilities.ts
Download https://raw.githubusercontent.com/alejandroq/mysql/master/src/constant/mysql_types.ts
Download https://raw.githubusercontent.com/alejandroq/mysql/master/src/auth.ts
Download https://raw.githubusercontent.com/alejandroq/mysql/master/src/constant/charset.ts
Download<EMAIL_ADDRESS>Warning std versions prefixed with 'v' were deprecated recently. Please change your import to<EMAIL_ADDRESS>(at<EMAIL_ADDRESS>error: Import<EMAIL_ADDRESS>failed: 404 Not Found
    at https://deno.land/x/bytes_formater@v1.3.0/deps.ts:1:0

After the patch it downloaded all deps with no issues.

I just created a PR of that xD you were faster

Thanks!

now we just need a new release


Cannot store other graph information in graphTuple

I thought we could store anything in graphTuple just like PyTorch geometric data or dgl, but that is not the case. I get the following error when storing node degrees:
TypeError: __new__() got an unexpected keyword argument 'in_degree'
is it the intended behavior, if so why, if not how can we store anything in there?
thanks

Sorry for the vague questions, just saw that you can use "globals" to store any extra info about the graph.


Allow dealerdirect/phpcodesniffer-composer-installer plugin

Addresses https://github.com/laminas-api-tools/api-tools-doctrine/issues/32
Signed-off-by: andyo<EMAIL_ADDRESS>

Q
A

Documentation
no

Bugfix
yes

BC Break
no

New Feature
no

RFC
no

QA
no

Description

Are you fixing a bug?

How do you reproduce it? Trigger a build into 2.5.x
What was the previous behavior? Builds were passing
What is the current behavior? Builds are failing

Updated PHPUnit to fix build error with XSD failing on lowest configuration:
Running before_script: xmllint --schema vendor/phpunit/phpunit/phpunit.xsd phpunit.xml.dist
warning: failed to load external entity "vendor/phpunit/phpunit/phpunit.xsd"

I'm going to revert changes to the lockfile and redo the update, apparently all deps were updated

Ran the following command to update:
composer update phpunit/phpunit phar-io/manifest phpunit/php-code-coverage sebastian/comparator sebastian/exporter sebastian/type nikic/php-parser --ignore-platform-req=ext-mongodb
Creating api-tools-doctrine_php_run ... done
Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
Updating dependencies
Lock file operations: 0 installs, 7 updates, 0 removals
  - Upgrading nikic/php-parser (v4.10.5 => v4.15.1)
  - Upgrading phar-io/manifest (2.0.1 => 2.0.3)
  - Upgrading phpunit/php-code-coverage (9.2.6 => 9.2.18)
  - Upgrading phpunit/phpunit (9.5.6 => 9.5.26)
  - Upgrading sebastian/comparator (4.0.6 => 4.0.8)
  - Upgrading sebastian/exporter (4.0.3 => 4.0.5)
  - Upgrading sebastian/type (2.3.4 => 3.2.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 16 installs, 105 updates, 2 removals
  - Downloading composer/package-versions-deprecated (<IP_ADDRESS>)
  - Downloading dealerdirect/phpcodesniffer-composer-installer (v0.7.1)
  - Downloading symfony/polyfill-php80 (v1.23.0)
  - Downloading jean85/pretty-package-versions (1.6.0)
  - Downloading mongodb/mongodb (1.8.0)
  - Downloading alcaeus/mongo-php-adapter (1.2.0)
  - Downloading nikic/php-parser (v4.15.1)
  - Downloading brick/varexporter (0.3.5)
  - Downloading doctrine/deprecations (v0.5.3)
  - Downloading laminas/laminas-zendframework-bridge (1.2.0)
  - Downloading laminas/laminas-stdlib (3.3.1)
  - Downloading psr/container (1.1.1)
  - Downloading container-interop/container-interop (1.2.0)
  - Downloading laminas/laminas-servicemanager (3.6.4)
  - Downloading laminas/laminas-loader (2.7.0)
  - Downloading laminas/laminas-json (3.2.0)
  - Downloading laminas/laminas-eventmanager (3.3.1)
  - Downloading laminas/laminas-view (2.12.0)
  - Downloading laminas/laminas-validator (2.14.4)
  - Downloading laminas/laminas-escaper (2.7.0)
  - Downloading laminas/laminas-uri (2.8.1)
  - Downloading laminas/laminas-http (2.14.3)
  - Downloading laminas/laminas-router (3.4.5)
  - Downloading webimpress/safe-writer (2.2.0)
  - Downloading laminas/laminas-config (3.5.0)
  - Downloading laminas/laminas-modulemanager (2.10.2)
  - Downloading laminas/laminas-mvc (3.2.0)
  - Downloading symfony/polyfill-mbstring (v1.23.0)
  - Downloading symfony/polyfill-intl-normalizer (v1.23.0)
  - Downloading symfony/polyfill-intl-grapheme (v1.23.0)
  - Downloading symfony/polyfill-ctype (v1.23.0)
  - Downloading symfony/string (v5.3.2)
  - Downloading symfony/service-contracts (v2.4.0)
  - Downloading symfony/polyfill-php73 (v1.23.0)
  - Downloading symfony/deprecation-contracts (v2.4.0)
  - Downloading symfony/console (v5.3.2)
  - Downloading psr/cache (1.0.1)
  - Downloading doctrine/lexer (1.2.1)
  - Downloading doctrine/annotations (1.13.1)
  - Downloading doctrine/reflection (1.2.2)
  - Downloading doctrine/event-manager (1.1.1)
  - Downloading doctrine/collections (1.6.7)
  - Downloading doctrine/cache (1.11.3)
  - Downloading doctrine/persistence (1.3.8)
  - Downloading doctrine/inflector (1.4.4)
  - Downloading doctrine/common (2.13.3)
  - Downloading doctrine/mongodb (1.6.4)
  - Downloading doctrine/instantiator (1.4.0)
  - Downloading doctrine/mongodb-odm (1.3.7)
  - Downloading laminas/laminas-paginator (2.10.0)
  - Downloading laminas/laminas-filter (2.11.1)
  - Downloading laminas/laminas-inputfilter (2.12.0)
  - Downloading laminas/laminas-form (2.15.1)
  - Downloading psr/simple-cache (1.0.1)
  - Downloading zendframework/zend-cache (2.9.0)
  - Downloading laminas/laminas-authentication (2.8.0)
  - Downloading doctrine/doctrine-module (2.1.10)
  - Downloading doctrine/doctrine-mongo-odm-module (1.1.1)
  - Downloading doctrine/dbal (2.13.2)
  - Downloading doctrine/orm (2.7.5)
  - Downloading doctrine/doctrine-orm-module (2.1.7)
  - Downloading laminas/laminas-code (4.4.0)
  - Downloading laminas-api-tools/api-tools-versioning (1.4.0)
  - Downloading laminas-api-tools/api-tools-api-problem (1.4.0)
  - Downloading laminas-api-tools/api-tools-content-negotiation (1.5.0)
  - Downloading laminas-api-tools/api-tools-rpc (1.5.0)
  - Downloading laminas/laminas-permissions-rbac (3.1.0)
  - Downloading laminas/laminas-permissions-acl (2.8.0)
  - Downloading webmozart/assert (1.10.0)
  - Downloading laminas/laminas-i18n (2.11.1)
  - Downloading laminas/laminas-mvc-i18n (1.2.0)
  - Downloading laminas/laminas-math (3.3.2)
  - Downloading laminas/laminas-crypt (3.4.0)
  - Downloading bshaffer/oauth2-server-php (v1.11.1)
  - Downloading laminas-api-tools/api-tools-oauth2 (1.7.2)
  - Downloading laminas-api-tools/api-tools-mvc-auth (1.6.0)
  - Downloading laminas-api-tools/api-tools-rest (1.6.1)
  - Downloading laminas-api-tools/api-tools-provider (1.4.0)
  - Downloading laminas-api-tools/api-tools-content-validation (1.9.0)
  - Downloading laminas-api-tools/api-tools-configuration (1.4.1)
  - Downloading laminas-api-tools/api-tools-admin-ui (1.4.0)
  - Downloading laminas/laminas-db (2.12.0)
  - Downloading laminas-api-tools/api-tools (1.5.0)
  - Downloading laminas-api-tools/api-tools-admin (1.9.0)
  - Downloading webimpress/coding-standard (1.2.2)
  - Downloading phpstan/phpdoc-parser (0.5.4)
  - Downloading slevomat/coding-standard (7.0.9)
  - Downloading psr/log (1.1.4)
  - Downloading laminas/laminas-log (2.13.1)
  - Downloading laminas/laminas-serializer (2.10.1)
  - Downloading sebastian/recursion-context (4.0.4)
  - Downloading sebastian/object-reflector (2.0.4)
  - Downloading sebastian/object-enumerator (4.0.4)
  - Downloading sebastian/global-state (5.0.3)
  - Downloading sebastian/diff (4.0.4)
  - Downloading sebastian/code-unit (1.0.8)
  - Downloading phpunit/php-timer (5.0.3)
  - Downloading phpunit/php-text-template (2.0.4)
  - Downloading sebastian/complexity (2.0.2)
  - Downloading sebastian/code-unit-reverse-lookup (2.0.3)
  - Downloading phpunit/php-code-coverage (9.2.18)
  - Downloading phar-io/version (3.1.0)
  - Downloading myclabs/deep-copy (1.10.2)
  - Downloading laminas/laminas-dom (2.8.0)
  - Downloading laminas/laminas-console (2.8.0)
  - Downloading laminas/laminas-test (3.5.1)
  - Downloading phpdocumentor/reflection-common (2.2.0)
  - Downloading phpdocumentor/type-resolver (1.4.0)
  - Downloading phpdocumentor/reflection-docblock (5.2.2)
  - Downloading phpro/zf-doctrine-hydration-module (v4.1.0)
  - Downloading phpspec/prophecy (1.13.0)
  - Downloading phpspec/prophecy-phpunit (v2.0.1)
  - Downloading netresearch/jsonmapper (v4.0.0)
  - Downloading felixfbecker/language-server-protocol (1.5.1)
  - Downloading felixfbecker/advanced-json-rpc (v3.2.1)
  - Downloading composer/xdebug-handler (2.0.1)
  - Downloading composer/semver (3.2.5)
  - Downloading amphp/amp (v2.5.2)
  - Downloading amphp/byte-stream (v1.8.1)
  - Downloading vimeo/psalm (4.8.1)
  - Downloading symfony/yaml (v5.3.2)
  - Removing symfony/debug (v2.8.0)
  - Removing api-skeletons/zf-doctrine-module-zend-hydrator (1.0.0)
  - Upgrading composer/package-versions-deprecated (1.10.99 => <IP_ADDRESS>): Extracting archive
  - Upgrading dealerdirect/phpcodesniffer-composer-installer (v0.7.0 => v0.7.1): Extracting archive
  - Installing symfony/polyfill-php80 (v1.23.0): Extracting archive
  - Installing jean85/pretty-package-versions (1.6.0): Extracting archive
  - Upgrading mongodb/mongodb (1.1.0 => 1.8.0): Extracting archive
  - Upgrading alcaeus/mongo-php-adapter (1.1.0 => 1.2.0): Extracting archive
  - Upgrading nikic/php-parser (v4.13.0 => v4.15.1): Extracting archive
  - Installing brick/varexporter (0.3.5): Extracting archive
  - Installing doctrine/deprecations (v0.5.3): Extracting archive
  - Upgrading laminas/laminas-zendframework-bridge (1.0.0 => 1.2.0): Extracting archive
  - Upgrading laminas/laminas-stdlib (3.3.0 => 3.3.1): Extracting archive
  - Installing psr/container (1.1.1): Extracting archive
  - Upgrading container-interop/container-interop (1.1.0 => 1.2.0): Extracting archive
  - Upgrading laminas/laminas-servicemanager (3.1.1 => 3.6.4): Extracting archive
  - Upgrading laminas/laminas-loader (2.5.1 => 2.7.0): Extracting archive
  - Upgrading laminas/laminas-json (2.6.1 => 3.2.0): Extracting archive
  - Upgrading laminas/laminas-eventmanager (3.0.1 => 3.3.1): Extracting archive
  - Upgrading laminas/laminas-view (2.11.3 => 2.12.0): Extracting archive
  - Upgrading laminas/laminas-validator (2.10.1 => 2.14.4): Extracting archive
  - Upgrading laminas/laminas-escaper (2.5.0 => 2.7.0): Extracting archive
  - Upgrading laminas/laminas-uri (2.5.2 => 2.8.1): Extracting archive
  - Upgrading laminas/laminas-http (2.8.3 => 2.14.3): Extracting archive
  - Upgrading laminas/laminas-router (3.0.1 => 3.4.5): Extracting archive
  - Installing webimpress/safe-writer (2.2.0): Extracting archive
  - Upgrading laminas/laminas-config (2.6.0 => 3.5.0): Extracting archive
  - Upgrading laminas/laminas-modulemanager (2.7.2 => 2.10.2): Extracting archive
  - Upgrading laminas/laminas-mvc (3.0.2 => 3.2.0): Extracting archive
  - Upgrading symfony/polyfill-mbstring (v1.0.0 => v1.23.0): Extracting archive
  - Installing symfony/polyfill-intl-normalizer (v1.23.0): Extracting archive
  - Installing symfony/polyfill-intl-grapheme (v1.23.0): Extracting archive
  - Installing symfony/polyfill-ctype (v1.23.0): Extracting archive
  - Installing symfony/string (v5.3.2): Extracting archive
  - Installing symfony/service-contracts (v2.4.0): Extracting archive
  - Installing symfony/polyfill-php73 (v1.23.0): Extracting archive
  - Installing symfony/deprecation-contracts (v2.4.0): Extracting archive
  - Upgrading symfony/console (v3.4.17 => v5.3.2): Extracting archive
  - Installing psr/cache (1.0.1): Extracting archive
  - Upgrading doctrine/lexer (v1.0 => 1.2.1): Extracting archive
  - Upgrading doctrine/annotations (v1.5.0 => 1.13.1): Extracting archive
  - Upgrading doctrine/reflection (v1.0.0 => 1.2.2): Extracting archive
  - Upgrading doctrine/event-manager (v1.0.0 => 1.1.1): Extracting archive
  - Upgrading doctrine/collections (v1.4.0 => 1.6.7): Extracting archive
  - Upgrading doctrine/cache (v1.6.0 => 1.11.3): Extracting archive
  - Upgrading doctrine/persistence (v1.0.0 => 1.3.8): Extracting archive
  - Upgrading doctrine/inflector (v1.0 => 1.4.4): Extracting archive
  - Upgrading doctrine/common (v2.9.0 => 2.13.3): Extracting archive
  - Upgrading doctrine/mongodb (1.3.0 => 1.6.4): Extracting archive
  - Upgrading doctrine/instantiator (1.3.1 => 1.4.0): Extracting archive
  - Upgrading doctrine/mongodb-odm (1.1.7 => 1.3.7): Extracting archive
  - Upgrading laminas/laminas-paginator (2.7.0 => 2.10.0): Extracting archive
  - Upgrading laminas/laminas-filter (2.7.1 => 2.11.1): Extracting archive
  - Upgrading laminas/laminas-inputfilter (2.7.2 => 2.12.0): Extracting archive
  - Upgrading laminas/laminas-form (2.9.2 => 2.15.1): Extracting archive
  - Installing psr/simple-cache (1.0.1): Extracting archive
  - Upgrading zendframework/zend-cache (2.7.1 => 2.9.0): Extracting archive
  - Upgrading laminas/laminas-authentication (2.5.3 => 2.8.0): Extracting archive
  - Upgrading doctrine/doctrine-module (1.2.0 => 2.1.10): Extracting archive
  - Upgrading doctrine/doctrine-mongo-odm-module (0.11.0 => 1.1.1): Extracting archive
  - Upgrading doctrine/dbal (2.12.0 => 2.13.2): Extracting archive
  - Upgrading doctrine/orm (v2.6.3 => 2.7.5): Extracting archive
  - Upgrading doctrine/doctrine-orm-module (1.1.8 => 2.1.7): Extracting archive
  - Upgrading laminas/laminas-code (2.6.3 => 4.4.0): Extracting archive
  - Upgrading laminas-api-tools/api-tools-versioning (1.2.0 => 1.4.0): Extracting archive
  - Upgrading laminas-api-tools/api-tools-api-problem (1.2.1 => 1.4.0): Extracting archive
  - Upgrading laminas-api-tools/api-tools-content-negotiation (1.2.2 => 1.5.0): Extracting archive
  - Upgrading laminas-api-tools/api-tools-rpc (1.3.0 => 1.5.0): Extracting archive
  - Upgrading laminas/laminas-permissions-rbac (2.5.1 => 3.1.0): Extracting archive
  - Upgrading laminas/laminas-permissions-acl (2.6.0 => 2.8.0): Extracting archive
  - Upgrading webmozart/assert (1.0.0 => 1.10.0): Extracting archive
  - Upgrading laminas/laminas-i18n (2.7.3 => 2.11.1): Extracting archive
  - Installing laminas/laminas-mvc-i18n (1.2.0): Extracting archive
  - Upgrading laminas/laminas-math (2.6.0 => 3.3.2): Extracting archive
  - Upgrading laminas/laminas-crypt (2.6.0 => 3.4.0): Extracting archive
  - Upgrading bshaffer/oauth2-server-php (v1.8.0 => v1.11.1): Extracting archive
  - Upgrading laminas-api-tools/api-tools-oauth2 (1.4.0 => 1.7.2): Extracting archive
  - Upgrading laminas-api-tools/api-tools-mvc-auth (1.4.2 => 1.6.0): Extracting archive
  - Upgrading laminas-api-tools/api-tools-rest (1.3.2 => 1.6.1): Extracting archive
  - Upgrading laminas-api-tools/api-tools-provider (1.2.0 => 1.4.0): Extracting archive
  - Upgrading laminas-api-tools/api-tools-content-validation (1.3.4 => 1.9.0): Extracting archive
  - Upgrading laminas-api-tools/api-tools-configuration (1.2.1 => 1.4.1): Extracting archive
  - Upgrading laminas-api-tools/api-tools-admin-ui (1.3.7 => 1.4.0): Extracting archive
  - Upgrading laminas/laminas-db (2.8.1 => 2.12.0): Extracting archive
  - Upgrading laminas-api-tools/api-tools (1.3.0 => 1.5.0): Extracting archive
  - Upgrading laminas-api-tools/api-tools-admin (1.5.7 => 1.9.0): Extracting archive
  - Upgrading webimpress/coding-standard (1.2.0 => 1.2.2): Extracting archive
  - Upgrading phpstan/phpdoc-parser (0.5.1 => 0.5.4): Extracting archive
  - Upgrading slevomat/coding-standard (7.0.0 => 7.0.9): Extracting archive
  - Upgrading psr/log (1.0.0 => 1.1.4): Extracting archive
  - Upgrading laminas/laminas-log (2.9.1 => 2.13.1): Extracting archive
  - Upgrading laminas/laminas-serializer (2.8.0 => 2.10.1): Extracting archive
  - Upgrading sebastian/recursion-context (4.0.0 => 4.0.4): Extracting archive
  - Upgrading sebastian/object-reflector (2.0.0 => 2.0.4): Extracting archive
  - Upgrading sebastian/object-enumerator (4.0.3 => 4.0.4): Extracting archive
  - Upgrading sebastian/global-state (5.0.1 => 5.0.3): Extracting archive
  - Upgrading sebastian/diff (4.0.3 => 4.0.4): Extracting archive
  - Upgrading sebastian/code-unit (1.0.6 => 1.0.8): Extracting archive
  - Upgrading phpunit/php-timer (5.0.2 => 5.0.3): Extracting archive
  - Upgrading phpunit/php-text-template (2.0.3 => 2.0.4): Extracting archive
  - Upgrading sebastian/complexity (2.0.0 => 2.0.2): Extracting archive
  - Upgrading sebastian/code-unit-reverse-lookup (2.0.2 => 2.0.3): Extracting archive
  - Upgrading phpunit/php-code-coverage (9.2.13 => 9.2.18): Extracting archive
  - Upgrading phar-io/version (3.0.2 => 3.1.0): Extracting archive
  - Upgrading myclabs/deep-copy (1.10.1 => 1.10.2): Extracting archive
  - Upgrading laminas/laminas-dom (2.6.0 => 2.8.0): Extracting archive
  - Upgrading laminas/laminas-console (2.6.0 => 2.8.0): Extracting archive
  - Upgrading laminas/laminas-test (3.4.0 => 3.5.1): Extracting archive
  - Upgrading phpdocumentor/reflection-common (1.0 => 2.2.0): Extracting archive
  - Upgrading phpdocumentor/type-resolver (0.4.0 => 1.4.0): Extracting archive
  - Upgrading phpdocumentor/reflection-docblock (4.0.0 => 5.2.2): Extracting archive
  - Upgrading phpro/zf-doctrine-hydration-module (v3.0.0 => v4.1.0): Extracting archive
  - Upgrading phpspec/prophecy (v1.10.2 => 1.13.0): Extracting archive
  - Upgrading phpspec/prophecy-phpunit (v2.0.0 => v2.0.1): Extracting archive
  - Upgrading netresearch/jsonmapper (v1.0.0 => v4.0.0): Extracting archive
  - Upgrading felixfbecker/language-server-protocol (v1.5.0 => 1.5.1): Extracting archive
  - Upgrading felixfbecker/advanced-json-rpc (v3.0.3 => v3.2.1): Extracting archive
  - Upgrading composer/xdebug-handler (1.1.0 => 2.0.1): Extracting archive
  - Upgrading composer/semver (1.4.0 => 3.2.5): Extracting archive
  - Upgrading amphp/amp (v2.4.2 => v2.5.2): Extracting archive
  - Upgrading amphp/byte-stream (v1.5.0 => v1.8.1): Extracting archive
  - Upgrading vimeo/psalm (4.8.0 => 4.8.1): Extracting archive
  - Removing symfony/yaml (v2.3.0)
 107/119 [=========================>--]  89%  - Installing symfony/yaml (v5.3.2): Extracting archive
Package container-interop/container-interop is abandoned, you should avoid using it. Use psr/container instead.
Package doctrine/reflection is abandoned, you should avoid using it. Use roave/better-reflection instead.
Package zendframework/zend-cache is abandoned, you should avoid using it. Use laminas/laminas-cache instead.
Package doctrine/mongodb is abandoned, you should avoid using it. No replacement was suggested.
Package laminas/laminas-console is abandoned, you should avoid using it. Use laminas/laminas-cli instead.
Generating autoload files
99 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

PHPCodeSniffer and Psalm checks are failing due to legitimate issues with the code. I will ignore those for now and we can address that in a separate PR. PHP8 lowest/latest builds are still failing and I"m not entirely sure why, will look into it.

In order to get PHP8 builds working we need to allow doctrine-module @ ^4.0 and replace phpro/zf-doctrine-hydration-module with something like api-skeletons/doctrine-orm-hydration-module, which has a PR pending PHP8 compatibility. Not sure how to proceed with this one.

Declining in favor of https://github.com/laminas-api-tools/api-tools-doctrine/pull/35


Energy Range Problem

Dear Users
I want to plot bandstructure and DOS in the specific range. I have changed the value code as given below,but it does not effect on plot,Secondly I also want to delete the gap between DOS and Bandstructure diagram.please suggest solution.
Thanks in Advance
emin =5.
emax =-5.
for spin in bands.bands.keys():
   for b in range(bands.nb_bands):
       emin = min(emin, min(bands.bands[spin][b]))
       emax = max(emax, max(bands.bands[spin][b]))

emin -= bands.efermi + 1
emax -= bands.efermi - 1

ax1.set_ylim(emin, emax)
ax2.set_ylim(emin, emax)

Dear Abdul
Actually, the code try to determine emin and emax as you can see in the lines you wrote in your comment.
If you want to manually define the energy range, comment or remove the line and put your own values.

got,thank you.How can we get help other modules of pymatgen .i want to
calculate polarization and thermoelectric properties using boltztrap.
ABDUL JALILLecturerDepartment of Physics00923315192550,0519057214
Allama Iqbal Open university,* Islamabad Pakistan.*
http://www.aiou.edu.pk/ http://www.aiou.edu.pk/
On Wed, May 16, 2018 at 11:13 PM, Germain Salvato Vallverdu <
<EMAIL_ADDRESS>wrote:

Dear Abdul
Actually, the code try to determine emin and emax as you can see in the
lines you wrote in your comment.
If you want to manually define the energy range, comment or remove the
line and put your own values.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gVallverdu/bandstructureplots/issues/12#issuecomment-389555543,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AScjK7bH2BaW-enN0S3a_QtOwytOXXNBks5tzEIFgaJpZM4T--kd
.

Thank excellent code!everything is looking fine but please how can we
change the position of fancy box? I want to draw at to position.Also wants
to change text style.
ABDUL JALILLecturerDepartment of Physics00923315192550,0519057214
Allama Iqbal Open university,* Islamabad Pakistan.*
http://www.aiou.edu.pk/ http://www.aiou.edu.pk/
On Thu, May 17, 2018 at 4:04 PM, Abdul Jalil<EMAIL_ADDRESS>wrote:

got,thank you.How can we get help other modules of pymatgen .i want to
calculate polarization and thermoelectric properties using boltztrap.
ABDUL JALILLecturerDepartment of Physics00923315192550,0519057214
Allama Iqbal Open university,* Islamabad Pakistan.*
http://www.aiou.edu.pk/ http://www.aiou.edu.pk/
On Wed, May 16, 2018 at 11:13 PM, Germain Salvato Vallverdu <
<EMAIL_ADDRESS>wrote:

Dear Abdul
Actually, the code try to determine emin and emax as you can see in the
lines you wrote in your comment.
If you want to manually define the energy range, comment or remove the
line and put your own values.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gVallverdu/bandstructureplots/issues/12#issuecomment-389555543,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AScjK7bH2BaW-enN0S3a_QtOwytOXXNBks5tzEIFgaJpZM4T--kd
.

Sorry forget to mention, its nanotube the calculated bandstructure is
along(GAMMA to Z) how can i remove the x and M lines?
ABDUL JALILLecturerDepartment of Physics00923315192550,0519057214
Allama Iqbal Open university,* Islamabad Pakistan.*
http://www.aiou.edu.pk/ http://www.aiou.edu.pk/
On Thu, May 17, 2018 at 5:13 PM, Abdul Jalil<EMAIL_ADDRESS>wrote:

Thank excellent code!everything is looking fine but please how can we
change the position of fancy box? I want to draw at to position.Also wants
to change text style.
ABDUL JALILLecturerDepartment of Physics00923315192550,0519057214
Allama Iqbal Open university,* Islamabad Pakistan.*
http://www.aiou.edu.pk/ http://www.aiou.edu.pk/
On Thu, May 17, 2018 at 4:04 PM, Abdul Jalil<EMAIL_ADDRESS>wrote:

got,thank you.How can we get help other modules of pymatgen .i want to
calculate polarization and thermoelectric properties using boltztrap.
ABDUL JALILLecturerDepartment of Physics00923315192550,0519057214
Allama Iqbal Open university,* Islamabad Pakistan.*
http://www.aiou.edu.pk/ http://www.aiou.edu.pk/
On Wed, May 16, 2018 at 11:13 PM, Germain Salvato Vallverdu <
<EMAIL_ADDRESS>wrote:

Dear Abdul
Actually, the code try to determine emin and emax as you can see in the
lines you wrote in your comment.
If you want to manually define the energy range, comment or remove the
line and put your own values.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gVallverdu/bandstructureplots/issues/12#issuecomment-389555543,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AScjK7bH2BaW-enN0S3a_QtOwytOXXNBks5tzEIFgaJpZM4T--kd
.


msgpack parser failed to parse null as Map key

What is the issue you have?
I'm trying to parse msgpack data like:
{
    null: 1
}

which serializes as 81 C0 01. But nlohmann::json::from_msgpack failed to parse it with
[json.exception.parse_error.113] parse error at byte 2: syntax error while parsing MessagePack string: expected length specification (0xA0-0xBF, 0xD9-0xDB); last byte: 0xC0

Please describe the steps to reproduce the issue.
↓
Can you provide a small but working code example?
#include <nlohmann/json.hpp>
int main() {
    const uint8_t src[] = {0x81, 0xC0, 0x01};
    nlohmann::json j = nlohmann::json::from_msgpack(src);
}

What is the expected behavior?
From the msgpack specs it doesn't restricts which value could be used on Map keys
And what is the actual behavior instead?
The specs above says

applications may remove Binary type, restrict keys of map objects to be String type, and put some restrictions to make the semantics compatible with JSON

So maybe it could be serialized to
{
    "null": 1
}

like other implementation does
Which compiler and operating system are you using?

Compiler: MSVC 19.30.30705
Operating system: Windows 11 22000.527
Also reproduced on gcc11

Which version of the library did you use?

[ ] latest release version 3.10.5
[x] other release - please state the version: 3.10.4
[ ] the develop branch

If you experience a compilation error: can you compile and run the unit tests?

[ ] yes
[ ] no - please copy/paste the error message below
[x] N/A

This is indeed not supported by the library as JSON requires object keys to be strings. I am hesitant to implement a workaround like treating null as a string.
In any case, we should overwork the documentation to be explicit about the restrictions.

In Python APIs there is a param bool strict_map_key=True, which does the thing.

This is indeed not supported by the library as JSON requires object keys to be strings. I am hesitant to implement a workaround like treating null as a string.

This would only need to apply to the parser, though? The user can be responsible for translating lookups to j["null"] where necessary.

Can be at least enabled on the sax parser? (all integer, unsigned integer, float ecc )
The virtual function (example json_sax::key(json_sax::number_integer_t)) can be defaulted to fail parsing while leaving the possibility to the user implementation of the parser to override it
Is this possible?
Thanks,
Luca

No. The parser expects a string for keys. This happens before the SAX interface is involved.
    bool get_msgpack_object(const std::size_t len)
    {
        if (JSON_HEDLEY_UNLIKELY(!sax->start_object(len)))
        {
            return false;
        }

        string_t key;
        for (std::size_t i = 0; i < len; ++i)
        {
            get();
            if (JSON_HEDLEY_UNLIKELY(!get_msgpack_string(key) || !sax->key(key))) // <-- string key is parsed/required here
            {
                return false;
            }

Sorry but the parse except a string because it is the only thing that know how to parse, can something like this be implemented?
bool get_msgpack_object(const std::size_t len)
{
    if (JSON_HEDLEY_UNLIKELY(!sax->start_object(len)))
    {
        return false;
    }

    for (std::size_t i = 0; i < len; ++i)
    {
        switch (get())
        {
            // EOF
            case std::char_traits<char_type>::eof():
                return false; // Or whatever

            // positive fixint
            case 0x00:
            // Various bytes omitted...
            case 0x7F:
                if( ! sax->key_number_integer(static_cast<number_unsigned_t>(current) ) ) return false;
                break;

            // fixstr
            case 0xA0:
            // Various bytes omitted...
            case 0xDB: // str 32
            {
                // NORMAL STRING CASE
                string_t s;
                if( ! ( get_msgpack_string(s) && sax->key(s) ) ) return false;
                break;
            }

            case 0xC0: // nil
                if( ! sax->key_null() ) return false;
                 break;

            case 0xC2: // false
                if( ! sax->key_bool(false) ) return false;
                 break;

            case 0xC3: // true
                if( ! sax->key_bool(true) ) return false;
                 break;

            // And so on with other meaningful types

        }

        if(JSON_HEDLEY_UNLIKELY(!parse_msgpack_internal())){
            return false;
        }
    }

Yeah I know the the default object container's key type is always basic_json::string_t and I don't want to change that, the default json_sax parser on its supposed virtual function json_sax::key_number_integer(json_sax::number_integer_t) should simply return false, this will keep same behaviour as present (fail to parse) but also let the user extend funtionality
With an extension like this @kotori2 could simply extend the sax parser with:
bool json_sax::key_null() override {
    return this->key("null");
}

Giving him his excepted result:
{
    "null": 1
}

given the input:
{
    null: 1
}

while at the same time keeping the current interface and behaviour

Sounds good. Are you interested in pursing this in form of a PR?


Initial focus date

Cloud add initial focus date ?
Like minimum date time is 2000.1.1, but i want focus on today in first time.

When you mean focus, you are saying that the today should be already selected? Or that the screen should show the month that has today's date, even it there is previous months in the calendar?
Cya

I mean tha the screen should show the month that has today's date, even it there is previous months in the calendar.
Thanks

Okay, thanks for this ideia.
I will put this on the roadmap of the package and it will problably be done soon.
Cya.

+1

+1

It is being maintained @Helzio , sorry for the delay. But I'm really busy with work and my master degree. So it's been difficult to maintain the calendar up to date in realTime.
When I got time I will check this for sure. Or If anyone wants to open a MR, it will help a lot.
Sorry again, but I will try to do my best.
Cya Folks

Any update for this issue?

@rodrigodobbin I'm push PR.

Thanks a lot @tatsuyuki25 .
@FabioFiuza and I just release the version 1.3.0 in pub.dev with your PR. I think tomorrow everebody should be able to update the package.


GEODE-5336: create integration tests to test region rest apis and con…

…current requests
Co-authored-by: Biju Kunjummen<EMAIL_ADDRESS>Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

precheckin green

precheckin green again.


Dbz 823 conditionalize incubation note as tp for downstream

DBZ-823
This change updates the description for snapshot.max.threads that was modified in DBZ-823, by conditionalizing the existing note about parallel snapshots being in an incubating state so that it renders only in the community version of the docs.
It also adds an equivalent Tech Preview statement for the product version.
At present, in the MongoDB documentation, the property description does not include any caveats. If that is ok, then this can be merged as-is. Let me know if I need to add a similar note for the MongoDB connector.

@roldanbob Applied, thanks


Removed API Key from README

Unwise to put keys in public repos, isn't it?

It would be unwise, yes. It's not an actual key.
Thanks for the concern!


c backend: implement real if and match expr

Describe the feature
Implement C code gen for if and match exprs.
E.g.
fun main() {
    var := if false { 'never' } else { 'always' }
}

fun foo(x i32) string {
	return match x {
		1 { 'one' }
		2 { 'two' }
		else { 'other' }
	}
}

Proposed Solution
The JS implementations are in #146 and #148.
Additional Information
No response

Done as side product of #160


AIML20 minor fixes

Once I resolved conflicts there are no changes, but please accept so I can re-sync my fork back to the main branch.


Office.ASP.NETCoreReactAddins uses .Net Core 2.2 Runtime which is EOL

.Net Core 2.2 was EOL 12/23/2019.  It would be great if someone can update the sample to 3.1.

Well, you are in luck ... I already did the work and created a PR #75 for this here and waiting for it to be merged. Initially only upgraded the TypeScript part as I wanted to get this pulled in before putting in more work to also update the JaveScript part. The PR has been sitting here now for a couple of weeks without any interaction so not sure what is going on. Maybe they plan to surprise us at Build 2020 next week ;-)

@aafvstam , thank you.  I am in luck; I'll use your fork until the PR gets merged.

Sorry for the delay. The PR is now merged.


Cancelled Script when flashing

Description
When flashing the dev board I accidentally canceled the bash script (flash.sh) when running. This was the output up to the point of CTRL+C
Have I bricked the dev board?
Click to expand!
Issue Type
Build/Install, Support
Operating System
Ubuntu
Coral Device
Dev Board
Other Devices
No response
Programming Language
No response
Relevant Log Output
Existing home partition detected, will not flash home (override with -H)
target reported max download size of 419430400 bytes
sending 'bootloader0' (1039 KB)...
OKAY [  0.062s]
writing 'bootloader0'...
OKAY [  0.194s]
finished. total time: 0.256s
rebooting into bootloader...
OKAY [  0.018s]
finished. total time: 0.119s
target reported max download size of 419430400 bytes
sending 'gpt' (33 KB)...
OKAY [  0.018s]
writing 'gpt'...
OKAY [  0.223s]
finished. total time: 0.241s
rebooting into bootloader...
OKAY [  0.016s]
finished. total time: 0.116s
erasing 'misc'...
OKAY [  0.043s]
finished. total time: 0.043s
target reported max download size of 419430400 bytes
sending 'boot' (131072 KB)...
OKAY [  6.093s]
writing 'boot'...
`OKAY [  6.244s]
finished. total time: 12.338s
`target reported max download size of 419430400 bytes
sending sparse 'rootfs' 1/4 (408709 KB)...

@ryan-keswick Can you try to flash the dev board with a SDCARD as instructed at https://coral.ai/docs/dev-board/get-started/#flash-the-board ?

@ryan-keswick Were you able to resolve this issue ?

Feel free to reopen if you have any issues with SDCARD flashing.


[Bug] Reports 0 tests run when specs are in third level of suite hierarchy

I have two projects generating playwright json files, one has the spec details inside the second level of suites and the summary is working correctly:

The second has the spec details inside the third level of suites and the summary is coming out as "0 tests across 4 suites":

I can see the issue is in report.ts where it is only looking at the first and second level of suites, but I have been struggling to update the code as the tests are currently not working.
It should just need updating to something like:
const specs: SpecSummary[] = report.suites.reduce((all, file) => {
	for (const spec of file.specs) {
		all.push(parseSpec(spec, [file]))
	}
	for (const suite of file.suites || []) {
		for (const spec of suite.specs) {
			all.push(parseSpec(spec, [file, suite]))
		}

		for (const suite2 of suite.suites || []) {
			for (const spec of suite2.specs) {
				all.push(parseSpec(spec, [file, suite, suite2]))
			}
		}
	}
	return all
}, [] as SpecSummary[])

Or even better a recursive function until it finds an empty array of suites.
Thanks

Makes sense. I never knew one could just recursively nest suites! If you can provide an example json report that's failing to generate the correct summary, I'm happy to take a look at it.

I think the tests are currently failing because of too strict an eslint or typescript config, not because the logic is faulty.

I can share examples but I'd rather not do it publicly. I've just followed you on Twitter/X, would you be able to follow me back and I can DM you? Unless you've got a different method (public email address etc)?

@larmitage-bjss I've sent you a dm, let me know if that works.

I've released 3.3.0 which should take care of this. Can you try it out and report back if it's working for you?

Absolute star, looks like it's working correctly now! Thank you so much!


Feature Request: Entity management "Usage Count" field type

Hi Oro Team,

Side note: Like the otherS issues we've submitted, this is something that would improve Oro and if it's not on your roadmap, i am sure the community (or our team) could contribute in the future. I hope that you dont see theses issues as an annoyance :sweat_smile:

The Tags have a Usage count colunm, I thnk that it would be very nice to be able to create read-only field when a relation ManyToOne or ManyToMany field is created.
For example :

What do you think ?

@sadortun we definitely won't object if you will contribute this feature :)

Hehehe, great! It's  on roadmap, still no ETA ....

Hello @artml I did rethink about this one and it would worth revisiting this.
This feature should also allow to filter by entities HAVING a number of related entities.
For example, to filter entities that

have  2 or more opportunities
customers that have multiple orders
...


Cross-contract Call Attack Prevention Standard

This proposal introduces a standard to protect contracts from cross-contract call attacks.

Hey Wyatt, good to see you bringing some of those ideas back over to team green 😉
From what I can understand, it seems the planned Manifest and Permission system would resolve the same problem in a more comprehensive manner. Can you verify?

Exactly, @edgedlt.
I believe it is more a requeriment than a proposal, the ABI implementation is specifing constraints.

@EdgeDLT ah hadn't seen that before. Is the manifest able to be updated after deploying? And if so, does it cost 100-1000 GAS like Contract.Migrate?
Seems like the manifest probably solves the issue more than this proposal.

Implementation is here if you'd like to take a look. Apparently, permissions will be updatable without migration.

Yeah looks good to me. Would just be curious on the cost/difficulty to update the manifest.

It looks like Contract.Update costs the same as Contract.Create. While the manifest is more comprehensive, it does look like it would be too expensive with the current fee structure: https://github.com/neo-project/neo/blob/master/neo/SmartContract/InteropService.NEO.cs#L31

Also is this included in NEO 2.x or just in 3.0?

I expect just 3.0, 2.x is LTS now it seems.
Recommend checking against the 3.0 fee structure.

@EdgeDLT Hm. Would this standard have usage for NEO 2.x, since 3.0 is still a year away? Any idea what the fee will be for Contract.Update? @erikzhang ?

Manifest and permission system are only for neo3

So then this looks like a good solution for NEO 2.x, right? @EdgeDLT what are your thoughts?
@shargon is it clear yet what the gas fee will be? Doesn't it look like Contract.Update and Contract.Create will be the same gas fee? If this is prohibitively high, like in 2.x then I think this NEP could be useful in 3.0.
If 3.0 is not prohibitively expensive to update, what would people's thoughts be? I know 2.x is not getting new features but that doesn't mean projects aren't planning on launching on NEO before 3.0.

I think we should move ahead on this.
When a NEO3 TestNet exists we can probably assume that most projects will focus on building for that. Until then, there are probably going to be others deploying or migrating contracts on NEO 2.x. There's not really a downside with providing a standard that can offer them some extra security.

I agree with @EdgeDLT on this

@erikzhang @shargon


Adjust integration turned off?

I am trying to setup this library in my app, but in the raw request in the Segment debugger is showing that the Adjust integration is disabled:
"integrations": {
  "Adjust": false
}

According to https://segment.com/docs/sources/mobile/ios/#integrations-in-debugger this means that the flag "tells the Segment servers that a request was already made directly from the device through a bundled SDK. That way we don’t send a duplicate request via our servers to those services"
Why is this disabled?

You are bundling the Ajjust SDK, so analytics-ios will cal the Adjust SDK with the event on the device. The false flag for the server to not send it via the server side integration (and end up in Adjust twice).

@f2prateek In that case, is the way I'm using now correct? Should I unbundle the Adjust SDK?


Issue22

#22

Coverage decreased (-0.5%) to 72.992% when pulling 255378e77b2c76d20dffbd0389bf71820d0a44f5 on issue22 into 15bf8b4b8b6778f9772cf376d1997760da79dca3 on master.


Latent subgoals in gl.py

I've identified a potential issue in the implementation of the get_subgoal_predictions method in gl.py, specifically regarding the call to self.nets["goal_network"].sample_prior. The method sample_prior, as defined in vae_nets.py, requires an n argument to specify the number of samples to generate from the prior. However, this argument is not provided in the current call within get_subgoal_predictions.
In get_subgoal_predictions (gl.py):
latent_subgoals = self.nets["goal_network"].sample_prior(
    conditions=obs_dict,
    goals=goal_dict,
)

Definition of sample_prior (vae_nets.py):
def sample_prior(self, n, conditions=None, goals=None):
    ...
    return self.nets["prior"].sample(n=n, obs_dict=conditions, goal_dict=goals

Please do let me know if I am missing something

I believe the number of samples is inferred from the conditions leading batch shape if not provided explicitly.


Dontmerge trigger e2e cni tests

Signed-off-by: Yuchen Dai<EMAIL_ADDRESS>

@lambdai: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


How to make up for the problem that the decompiler cannot restore the assignment and judgment

Describe the question
In one simple case, I found that the decompiler ignored assignment and judgment statements. May I ask why this problem occurs and how to avoid it.
To Reproduce
use code like below:
#include<stdio.h>

int main() {
    int a;
    scanf("%d", &a);
    if(a == 3) {
        a = 4;
    }
    printf("tet: %d\n", a);
    return 0;
}

compile it:
gcc test.c -o test2

import Ghidra and auto Analyze it.

Expected behavior
The decompiled code has if jump and assignment operation.
Not only is there no assignment operation in the above code, but also there is no assignment operation in code like the following.
#include<stdio.h>

int main() {
    int a = 3, b = 4, c = 5;
    printf("tet: %d\n", a);
    return 0;
}

The decompiled code will look like this:
undefined4 entry(void)

{
  int in_w1;

  __stubs::_printf("tet: %d\n",in_w1);
  return 0;
}

Environment (please complete the following information):

OS: [macOS 12.5]
Java Version: [openjdk 17.0.6]
Ghidra Version: [10.2.3]
Ghidra Origin: [ghthub releases]

Additional context
The computer is: [MacBook Air with M1 chip]
gcc --version
Apple clang version 13.1.6 (clang-13<IP_ADDRESS>.5)
Target: arm64-apple-darwin21.6.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

file test2
test2: Mach-O 64-bit executable arm64

Thanks.

The decompiler optimises the if-check away because it thinks the if-check has no effect. The reason it thinks this is because you specified the wrong calling convention for the scanf and printf functions. From the assembly, it appears that the first argument (a pointer to the "format" string) is passed in x0, and the remaining arguments are passed on the stack. This seems similar to the calling convention described in #3927. This is a calling convention that Ghidra doesn't support or recognise by default, so you have do some extra work to get the decompiler output to appear correctly.
You should go to the function address for printf or scanf and then right-click the function name in the decompiler window. Click Edit Function Signature. In the pop-up window, tick Use Custom Storage and manually set the correct storage (first argument goes into x0, the second argument goes into Stack[0x0]). If you do this for both printf and scanf, the decompiler output for the main function should be similar to the output in the screenshot below.

Some notes:

Unfortunately, printf and scanf are variadic functions, and combining the Varargs and Use Custom Storage does not work very well (see #4334).
It does not seem possible to set the custom storage using the "Override signature" feature.

Regarding your second example, I'd say that the decompiled code is correct. While the decompiled code does not contain the assignments to b and c, both of these variables are only assigned to and never used. This means that the compiler may have completely removed those assignments, making it impossible to reconstruct. Alternatively, it could be the decompiler that optimises the assignments out to make the decompiled code as readable as possible. While it might be nice in individual cases to still show those assignments, (in general) there are many more such assignments that the compiler might introduce. If the decompiler would also show those, the "real" operations the function performs would be needlessly obscured.

All in all, I don't think this issue should remain open in its current form. Maybe the issue could be rephrased as "It is not possible to set the custom storage using the 'Override signature' feature", although it might be cleaner to just open a new issue for that.

Thank you for your response. As a beginner, I only recently learned about function signatures and didn't initially consider that it might be the issue.
Regarding the first example, I had already deleted the program and currently do not have an m1 mac for testing (though I will test it in the future). Previously, I had tested it on my Raspberry Pi 32-bit system and the compiled code worked fine (as seen in the attached image), so at the time I thought it was an issue with m1.

As for the second example, generating temporary variables and using them in the function but then discarding the assigned value is unacceptable. I think this is a loss of detail, which means that when reading the disassembled code, I would have to go back to the assembly code to look for the current value of the variable, which could be time-consuming.
Of course, I will verify the first question and supplement the situation as soon as possible. I would love to discuss the second question with you and explore ways to alleviate the issue.


⚠ Bofrost.com has degraded performance

In 41de644, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 491 ms

Resolved: Bofrost.com performance has improved in a5c0d55 after 8 minutes.


Query Planner (Feedback Requested)

Problem Statement
Please redirect me if this is not the best place to gather feedback for an idea that is not fully formed yet. I'm looking for feedback from deeper SpiceDB  experts on this idea that I might be interested in exploring if there is interest.
The first question worth answering is "why would SpiceDB need a query planner at all?". At the end of the day, SpiceDB's queries are just trying to determine if a path exists between two points. Currently, SpiceDB performs all path finding starting from resource->subject even though there may be some queries that are more performant when traversing subject->resource. While SpiceDB tuples represent a directed graph, that does not preclude SpiceDB's query engine from traversing the graph backwards via database indexes.
Why would we ever want to traverse backwards? (subject->resource)
I think it comes down to cardinality of relationships and how much data must be loaded from the data store. Let's consider a simple scenario where there's a many-to-many relationship between entities A, B, and C:

We want to know if there's a path from A:1 to C:1 through B. We have two options for fulfilling this query:

Traverse A->B
a_to_b_tuples = """
    SELECT ... FROM tuples
    WHERE res_type = 'A' AND res_id = '1'
    AND relation = 'a_to_b_relation'
    AND subj_type = 'B';
"""

Traverse B->C
// in batches of 100
b_to_c_tuples = """
    SELECT ... FROM tuples
    WHERE res_type = 'B' AND res_id IN (a_to_b_tuples_subject_ids)
    AND relation = 'b_to_c_relation'
    AND subj_type = 'C'
    AND subj_id = '1';
"""

Access granted if b_to_c_tuples is not empty.

But what happens if A:1 has many a_to_b_relations. What if there are a million? Then step 2 will chug along making many requests (with some concurrency factor) to sift through the many A->B tuples.
What if the cardinality happens to be much better going the other way? Each A has many Bs, but each B only has 1 A.  It could potentially be much faster to:

Traverse (backwards) C->B
b_to_c_tuples = """
    SELECT ... FROM tuples
    WHERE res_type = 'B'
    AND relation = 'b_to_c_relation'
    AND subj_type = 'C'
    AND subj_id = '1';
"""

Traverse (backwards) B->A
// in batches of 100
a_to_b_tuples = """
    SELECT ... FROM tuples
    WHERE res_type = 'A' AND res_id = '1'
    AND relation = 'a_to_b_relation'
    AND subj_type = 'B' and subj_id IN (b_to_c_tuples_resource_ids);
"""

Access granted if a_to_b_tuples is not empty.

This could potentially be much faster if the relationship have lower cardinality when traversing backwards.
If a proper query planning layer existed, if could try to solve this problem and it could potentially be extended to perform other optimizations that we think of later.
Open Questions / Problems
Determining Relation Cardinality
One idea would be to use HLLs to simply count and estimate of how many unique entries we see on each side of a relation. So if two tuples are written: A:1#a_to_b_relation@B:1 and A:1#a_to_b_relation@B:2, we would end up with two HLLs:
a_to_b_relation_a_hll.Len() => 1
a_to_b_relation_b_hll.Len() => 2
At scale, these numbers could provide insight on the cardinality between the two and hint at an optimal traversal direction. Using these cardinality values between relations, we can weigh our options. Some heuristic would need to be established if there are multiple paths from A->C.
You'd want to persist this information in the datastore somehow and have nodes only leverage the information once a substantial number of data points have been gathered. All nodes need to be on the same page.
Query Planning Latency
How would a query planning step be introduced without adding significant latency to the queries? We have to be able to pay off the time we spend planning!
Fortunately, SpiceDB is purpose-built and doesn't have an infinite number of queries to serve up. A given schema only captures so many paths and clients likely only use a subset of paths that a schema is capable of. The first time SpiceDB encounters a query for some A:X#a_to_b_relation@B:Y path, the plan may be cached and reused for all queries of its shape.
Cache Hit Rate
This is likely the biggest concern. Once a query plan is chosen for a particular query type, we likely need to stick to that query plan (unless there's a REALLY good reason not to). Otherwise cache hit rate will likely be terrible. We can't be too dynamic in our execution paths. Even still, this would require some experimentation to evaluate how this idea behaves at all at scale.
Indexing & Data Size
I would need to investigate further, but my hope is that much of the indexing required may already exist since the SpiceDB already offers APIs for traversing both directions (LookupResources & LookupSubjects). If not, data increase from additional indexes could be a concern.
Query Hints?
An MVP of this could involve allowing customers to specify query hints in their schema some how (don't accept query hints at query time because of the cache hit rate problem. We don't want' people flipping back and forth.)
Other Crazy Ideas
Wouldn't it be crazy if we traversed from both sides at once and tried to meet in the middle? I have no idea how that might work right now, but the idea is an interesting future convo. 🙂 (out of scope here)
Other optimizations?...

Nice write-up, @bradengroom!
A query planner is an idea that we've thrown around a few times but has never made it into a concrete proposal. This is a great place to start jotting ideas.
Other places we've talked about query planning being potentially valuable:

Any time there is an intersection or exclusion, knowing cardinality to plan a query can short-circuit the bigger branches
Preferring branches that are known to be caveat-free when no context is provided
Preferring paths that are more likely to be cached

Once a query plan is chosen for a particular query type, we likely need to stick to that query plan (unless there's a REALLY good reason not to).

Ideally we could decompose query plans into small subproblems that would be shared between many types of queries / plans so that this is not as much of an issue.

Wouldn't it be crazy if we traversed from both sides at once and tried to meet in the middle?

Have you considered starting in the middle and going outward? 😄

Ideally we could decompose query plans into small subproblems that would be shared between many types of queries / plans so that this is not as much of an issue.

If that's true then that's much more interesting. You could potentially change your course of action halfway through a query.
"I started traversing from the source, but my estimate was off an order of magnitude. Maybe I should start traversing from the resource and try to meet myself where I've made it so far"

@ecordell @josephschorr
Thanks for the feedback!
As I think on this, I think that this might be a large change to hash out in a single thread. I'm seeing 3 distinct threads that this work can be split into:

Stats Module

What stats do we track?
How do we track them efficiently?
How do we store them in the data stores?
How does this piece fit into the rest of the code?

Physical Plan

What is the data structure used to represent the query plan?
How do we pass it through dispatch?

Cost Model

When after we've generated multiple physical plans for a given query, how do we assign them a cost?

There's also likely a thread to spin up around an optimization layer. How do we take a physical plan and transform it into something more efficient? That can likely come later though once the code base has the concept of a query plan in place at all.
Since it sounds like the idea of a query planner already has buy-in from your internal discussions, I'd like to take a piece and start designing it with more concrete details if that's alright. Do y'all have any issues with me spinning up a new, concrete proposal for the stats module? I don't want to overwhelm folks with proposal docs if this isn't the usual flow. I'm just eager to contribute 😄 I'm still exploring the code, so this will likely take some time.

There's also likely a thread to spin up around an optimization layer. How do we take a physical plan and transform it into something more efficient? That can likely come later though once the code base has the concept of a query plan in place at all.

Designs have been thrown around on an IR to do just that, but its still very much in the ideation phase

Since it sounds like the idea of a query planner already has buy-in from your internal discussions, I'd like to take a piece and start designing it with more concrete details if that's alright. Do y'all have any issues with me spinning up a new, concrete proposal for the stats module?

No issue with doing so, but it is not a priority right now either, so just be aware the response times can and likely will be lower on any such designs or PRs.
Stats is probably the best place to start with a goal of getting good stats without impacting read or write performance, which likely means a background worker updating them async.

@bradengroom Any updates on the stats side? Just curious :)

@bradengroom Any updates on the stats side? Just curious :)

I have not unfortunately.  The demands of my day job have picked up as we've gone deeper into Q4

There are two types of operations that query planners can do:

Heuristic/Rule based rewriting
Cost-based search

So far we've mostly been discussing cost-based planning, but actually I think it makes sense to first consolidate the few places where we're performing heuristic/rules rewrites already into a clean interface that can be the foundation of the planner.

@jzelinskie agreed that might be a good first step to refactor towards the larger change. Is there a good way of hunting these rewrites down? Or does someone just need to trace the code and compile a list of such rewrites? I assume it’d all be in the check dispatch path.

This would be a big win for us. Nearly all of our evaluations, especially LookupResouces, would be significantly faster with the traversal direction inverted.
We loosely followed the https://authzed.com/blog/google-cloud-iam-modeling example when creating our model. In some cases we have hundreds of thousands or millions of granted role_binding relationships, which causes things to really chug. It's compounded when the role_binding user is a group which needs to be resolved as well. We had to remove a layer from our model to make things perform "well-enough", but it would be significantly faster with a query planner inverting the traversal.


Brotli support

closes #772

I've just published async-compression 0.3.0 which switches to using brotli. It should be a non-breaking version bump since reqwest's not using the encoder at all.

@seanmonstar I upgraded async-compression, which replaced brotli2 with brotli. Due to the cargo restriction that the name of 'feature' cannot be the same as the name of 'crate', I changed the name of some features. This seems to cause the PR checks to be pending

Due to the cargo restriction that the name of 'feature' cannot be the same as the name of 'crate', I changed the name of some features.

This would be a breaking change to any users already using reqwest = { features = ["gzip"] }. What conflict exists in this PR? If need be, a crate dependency can be renamed internally (notice that we rename the cookie crate to cookie_crate = { package = "cookie" }).

This would be a breaking change to any users already using reqwest = { features = ["gzip"] }. What conflict exists in this PR? If need be, a crate dependency can be renamed internally (notice that we rename the cookie crate to cookie_crate = { package = "cookie" }).

Sorry, I did n’t know that crate can be renamed before, thank you for reviewing, let me know this.
I have made changes now


[MINOR BUG] toFlow() Kotlin cache watcher fatal crash when no internet connection

Summary
When launching the application when there is no internet connection, watchers created using the kotlin suggested toFlow() crash the application without any errors logging to the console.
I am using this style of query watching:
  apolloClient.query(BookWithAuthorName()).watcher().toFlow().collect { response ->
      // This will be called every time the book or author changes
  }

When I used the java suggested way of watching, it works no issues.
Version
ext.apolloVersion = "2.4.0"
implementation "com.apollographql.apollo:apollo-runtime:$apolloVersion"
implementation "com.apollographql.apollo:apollo-coroutines-support:$apolloVersion"
implementation "com.apollographql.apollo:apollo-normalized-cache:$apolloVersion"
implementation "com.apollographql.apollo:apollo-android-support:$apolloVersion"
Description
Git commit that fixed the issue for me:

Hi 👋 ! When using the coroutines extensions, network errors will raise an exception that you can catch to ignore:
try {
  apolloClient.query(BookWithAuthorName()).watcher().toFlow().collect { response ->
      // This will be called every time the book or author changes
  }
} catch (e: ApolloException) {
  // an error happened
}

See the android tutorial section about errors for more details


flag/option ordering matters in the new CLI

@brendandburns ➜ /workspaces/dev-wasm-go (main) $ WASMTIME_NEW_CLI=1 wasmtime main.wasm --dir=.::.
Hello Go World!
Error writing open test.txt: errno 76
@brendandburns ➜ /workspaces/dev-wasm-go (main) $ WASMTIME_NEW_CLI=0 wasmtime main.wasm --dir=.
Hello Go World!
Wrote file
Copied file

Note that with the old CLI the wasm program works, with the new CLI it doesn't. I'm not sure if this is on purpose, but if it is what is the correct new syntax?
Test Case
WASM file uploaded. If you want to rebuild see:
https://github.com/dev-wasm/dev-wasm-go?tab=readme-ov-file#simple-example
Versions and Environment
Wasmtime version or commit: 15.0.1
Operating system: Linux
Architecture: amd64
main.zip

Without the env var the original invocation prints:
$ wasmtime main.wasm --dir=.::.
warning: this CLI invocation of Wasmtime will be parsed differently in future
         Wasmtime versions -- see this online issue for more information:
         https://github.com/bytecodealliance/wasmtime/issues/7384

         Wasmtime will now execute with the old (<= Wasmtime 13) CLI parsing,
         however this behavior can also be temporarily configured with an
         environment variable:

         - WASMTIME_NEW_CLI=0 to indicate old semantics are desired and silence this warning, or
         - WASMTIME_NEW_CLI=1 to indicate new semantics are desired and use the latest behavior
Hello Go World!
Wrote file
Copied file

which indicates that this is being parsed differently with/without the new CLI. There's a more extensive writeup in the release notes but the short version is that this is behaving as expected.
The first invocation from above, WASMTIME_NEW_CLI=1 wasmtime main.wasm --dir=.::., is parsed as passing --dir=.::. to the main.wasm program itself, not Wasmtime. This behavior is explicitly opted-in to with the env var. The second invocation WASMTIME_NEW_CLI=0 wasmtime main.wasm --dir=. is forcing the usage of the old CLI (also the current default behavior) which parses --dir=. as an argument to Wasmtime itself.
I'll also note that switching the order of the arguments, wasmtime --dir=.::. main.wasm, gets this program working with/without the env var.

Ah, so if I'm reading this correctly the ordering matters in the new CLI and not in the old CLI.
fwiw, having flag ordering matter without the explicit -- violates the posix file spec, specifically:
Guideline 11:
The order of different options relative to one another should not matter, unless the options are documented as mutually-exclusive and such an option is documented to override any incompatible options preceding it. If an option that has option-arguments is repeated, the option and option-argument combinations should be interpreted in the order specified on the command line.

from https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html

The ordering of arguments with Wasmtime has always mattered, both before and after the CLI refactor. For example in the old CLI wasmtime foo.wasm arg --dir . does not work because --dir is interpreted as an argument to foo.wasm, not Wasmtime. The reason for this is that the old CLI would stop feeding options to Wasmtime after -- or after the second positional argument (in this case arg). The new CLI updates this to stop feeding options to Wasmtime after -- or after the first positional argument (in this case foo.wasm). That's why the new CLI doesn't work with the command above and why the old CLI does.
When taken literally I see how it can be concluded that Wasmtime violates the guideline that you have mentioned. Despite this though the CLI changes were done to make Wasmtime more consistent with all other tools that I at least personally know about within the space of "execute a sub-program" (e.g. docker, strace, cargo, etc). All of those commands stop feeding options to the source program after the first positional argument (e.g. strace ls -l doesn't pass -l to strace, it passes it to ls). Wasmtime is now consistently following the same semantics where it stops parsing options after the first positional argument (which for Wasmtime is always the *.wasm file to execute).
Taken a little less literally Wasmtime is not violating the guideline you highlighted. Wasmtime's option parser produces the same result no matter what order Wasmtime's own flags are passed in. For example --allow-precompiled --dir . is parsed the same way as --dir . --allow-precompiled. I say "taken less literally" here because it still requires all of Wasmtime's own options to come before the first positional argument, the *.wasm file.
Regardless though the behavior you're seeing in this issue is intended and there's not currently a bug that I'm at least personally aware of, and the issue can be fixed by passing Wasmtime's own arguments before the *.wasm for both the old and the new CLI.

fwiw, imho the docker behavior is a bad design also. Docker explicitly introduced the -- operator into it's CLI to help correct the (bad) decisions they had previously made.
If you are looking for a counter example kubectl and practically every other standard unix command line tool does not behave this way.
Clearly I'm not in a position to force any changes in the wasmtime interpretation of the command line, but I do believe (strongly) that you are violating the principal of least surprise for the majority of users who will use your tool (and be confused when it behaves differently with different CLI ordering)


Next.js + Flask example Deploy failed

I've tried to deploy this example https://vercel.com/templates/next.js/nextjs-flask-starter
but during the deployment the following error is shown:
Error: Command failed: pip3.12 install --disable-pip-version-check --target . --upgrade -r /vercel/path0/requirements.txt

And the deploy fails

numpy is definitely superfluous here, but are we sure this is the only problem deploying this example? I'm running into trouble even with Requirements.txt cleaned up, and even with package.json modernized

I had the same error and solved it by

switching to python 3.12 (cause my local repo was in 3.10)
pip install setuptools
changing the numpy version to 1.26.4 in requirements.txt.

I don't think numpy is used at all at this point, so better to clean it out. The path of:

pnpm create next-app -e python/nextjs-flask
[edit out numpy entry in requirements.txt]
commit to main
push to github
connect vercel to repo
deploy via Vercel UI

Does seem to work fine.

Thanks for that pointer @peterdresslar, removing the numpy dependency solved it for me too.

Sure! But @sup deserves the credit for their #947 that correctly fixed the issue a few weeks ago


feat: load zkey from a file path, add file downloader in swift

Research for #65
TODO

[ ] use #[cfg(feature = "use_external_zkey")] to control features
[x] download and load arkzkey in initializeMopro (See 3.)
[ ] download file in android and use it in proof
[ ] benchmark different size of arkzkeys
[ ] try on real device

load from a fixed path e.g. "mopro-core/examples/circom/keccak256/target/keccak256_256_test_final.arkzkey"
proving time in swift
Time to deserialize proving key: 9.177727583s
Time to deserialize matrices: 70.397416ms
Initializing arkzkey took: 9.25s

Generating proof 2
Witness generation took: 423.89ms
Loading arkzkey took: 26.66ms

proof generation took: 1.36s

there is no much difference between using ARKZKEY and .arkzkey
Using ARKZKEY is even slightly slower than loading from a .arkzkey file

download from a server e.g. "https://mopro.vivianjeng.xyz/keccak256_256_test_final.arkzkey"
Download ark key took: 0.021011948585510254

Time to deserialize proving key: 8.894824041s
Time to deserialize matrices: 26.038125ms
Initializing arkzkey took: 8.92s

Generating proof 2
Witness generation took: 410.84ms

// TODO: should be done in initialization
Time to deserialize proving key: 8.895085333s
Time to deserialize matrices: 24.071833ms
Loading arkzkey took: 8.94s
proof generation took: 979.47ms

Init with arkzkey initialization
Time to deserialize proving key: 8.930367541s
Time to deserialize matrices: 24.104291ms

Generating proof 2
Witness generation took: 429.28ms
Loading arkzkey took: 208.00ns
proof generation took: 963.43ms

Verification time 2: 3.227791ms

What's needed for this PR to be ready for review/merge? Can we gate this feature behind a feature flag maybe? So existing flow works but this can be toggled. Also basic docs in README or so would be great

@vivianjeng can this PR be closed with #75 merged?


Creating UDP broadcast socket with audio packets (client/server sides)

Hi, I have to create a audio streaming system which captures audio from my PC mic and sends UDP packets to WebRTC peers (I am using aiortc). What I have done so far has been creating a peer with a MediaPlayer (which relies on PyAV) to capture the audio from the microphone, but when another peer connects to the "room" the PyAV library tells me that the ALSA is busy. So I was thinking to instead or creating instances of players which capture the mic audio directly, to have a single audio capture server which broadcasts in localhost UDP packets, then several UDP clients are open to catch those packets (something like av.open("udp://localhost:6000")). My question is if there is a better approach to do this task. And if this is actually the only one solution, how to create the server and client sides:

The PyAV server captures the audio from the microphone and sends UDP packets.
The PyAV clients connects to the local port and decode the sent audio UDP packets.

I understand you're looking for someone to do the work for you, but opening a ticket both against aiortc and PyAV isn't going to help.


How to install custom software in the docker image?

I need to install custom software in the docker image. For example, for my app to run, I need imagemagick installed in the system. How can I do this?

You can build a docker image with all the stuff you want and push it to the docker registry. And then set meteor.dockerImage to your image id (ex: meteor.dockerImage: 'meteorhacks/meteord'). Take a look at the mup.js format in the readme. (BTW this feature needs testing, I'd appreciate if people can test this for me :) )

@madushan1000 Great! I just created a custom docker image with imagemagick and deployed! So far so good.. everything's working fine :-) I will test it further and let you know if there's anything wrong!

can you explain how you have installed imagemagick with docker?

create a custom docker image with meteorhacks/meteord as the base + your libraries/software, push it to the dockerhub and set meteor.dockerImage to that.


5eTreasure added

Hi @RobinKuiper, due to the fact that this contains licensed content from Wizards of the Coast (the rules and tables from the Dungeon Master's Guide), we can't accept this into the Roll20 repository; only rules covered by the OGL can be implemented.


Address ^^^ deprecation

As of Elixir 1.12, ^^^ is deprecated because its precedence will be changing in Elixir 2.0.0. This operator is currently used by Witchcraft.Arrow, and so we may need to choose another operator, or deprecate its usage here.
https://github.com/elixir-lang/elixir/issues/11590

I wonder if they'll let us define custom custom operators...
Also, where does one learn about 2.0? 🤔


Apiv2: Timebox: async smoothie

overview
Take a day to use something like pyserial-asyncio and prototype a smoothie driver that correctly runs in an event loop, for apiv2 only. Evaluate the effects it would have on the system.
Figure out whether this will:

Prevent the event loop from blocking when the robot is paused
Prevent the event loop from blocking in general during smoothie communications

┆Issue is synchronized with this Wrike Task by Unito

No longer applicable


Fixed STC Bug

Reference Issues/PRs
Fixes #321
What does this implement/fix? Explain your changes.
Checks if pd.series passed and converts to numpy for internal use.
Any other comments?
Added some additional tests for STC although may be unneccessary

Since you're on it, if you have time, it'd be great to make shapelet comply with our interface more generally see #257 :)

Okay. I'll figure out whatever that error is.  I'll have a look at #257 but I'll probably do it tomorrow :)

@mloning I will get round to this, suddenly got loads of work to juggle at the moment. Hopefully try to get a PR done for end of the week

Okay @mloning noticed another bug with random seeding which im also fixing to make sure STC is correct. Taking longer than expected.

@mloning I also noticed in base.py for the Base Classifier the predict method doesn't called check_is_fitted(). See my newest commit

@ABostrom if you're feeling brave you can remove all Shapelet related estimators from this list here, this will run all standard unit test on them.
You may have to change the test hyper-params to make it faster (e.g. contract time to 10 secs or so) in the same file in this dictionary.

oooh. scary, will see what happens.

So I think i've resolved the testing issues across all the shapelet family of algorithms. Learned alot about pytest so thanks for that @mloning :)

@mloning @jasonlines So I think the current build errors, show case the current differences between my tsml implementation and the sktime one. Between the same run of the same datasets you cannot guarantee that you will evaluate the same amount of shapelets in the same time frame. Especially on different architectures etc. Which results in idemptoency failures and inconsistent outputs on the same seeds / datasets.
Might need to re-include them in the exclusion list, and review this particular check for future contract approaches.

@ABostrom does this only apply to the contracted version? Or also the ShapeletTransformClassifier?

@mloning shapelet transform classifier uses the contracted shapelets in a pipeline with radnom forest

Let's wait if @jasonlines has any idea how to fix this, otherwise we could try to write some code to skip/ignore the idempotency test for shapelets

@mloning I agree, I will have a little look at making some changes to _config.py and test_all_estimators to have an exclusion list for certain estimators.

@ABostrom decorators may work and may be the cleanest solution, something along the following lines:
@skip_if(estimator=[ShapeletTransform])
def check_idempotency():
    ....

Pytest may even have decorators for that already

my preference and ofc feel free to overrule on this is that all config for tests should stay in config. Seems like with decorators, whilst addmittedly a clean solution could make it difficult where to track down or reconfigure tests in the future.
EXCLUDED_FROM_TESTS = {     "ShapeletTransformClassifier": [check_fit_idempotent],     "ContractedShapeletTransform": [check_fit_idempotent], }

Sounds good to me!

@mloning I'm not sure how this works. If i change the config / pytests would that run my version of the tests or the old versions through travis etc?

It'll run whatever is on the PR I think, of course you can run them locally first to see if everything is working, so feel free to change things and push to the same branch. You also need to sync with the latest changes on dev.

Yeah they have all been passing locally. Might be I'm being stupid. will debug it.

changed the config params for ST to make sure it can actually finish in a time manner suitable for the build/CI server

@mloning if you can check it over Markus. I think it's looking pretty good. Turned into a bit more than some "simple" shapelet fix. As always these things do :)

Will do these now. Was just sorting a PR for sktime-dl. but now thats done, I'll tidy this up.

@ABostrom looks all good to me now! Thanks for the clean up of shapelets! :) Ready to merge when you are.

good to go Markus. Think it looks pretty comprehensive.


Documentation for running a Cygwin shell causes build to fail

Following the instructions for setting "terminal.integrated.shellArgs.windows" given at https://code.visualstudio.com/docs/editor/integrated-terminal#_can-i-use-cygwins-shell-with-the-terminal-on-windows
causes run build task using Cygwin to fail with:
cygpath: option requires an argument -- c
Try `cygpath --help' for more information.

A task window opens and shows a bash prompt. make runs correctly at that
prompt.
run build task correctly runs Cygwin make after removing
"terminal.integrated.shellArgs.windows".
Using Cygwin Shell says:

add the following settings to your settings.json file:

"terminal.integrated.shell.windows": "C:\\Cygwin\\bin\\bash.exe",
"terminal.integrated.shellArgs.windows": ["/bin/xhere", "/bin/bash"]

xhere takes one or two arguments: a program to start and an optional
directory to make the cwd before starting the given program.
This problem occurs because, when executing run build task, VS Code
passes three arguments: the Cygwin path name of the Windows path given in
"terminal.integrated.shell.windows", a literal -c, and , as one
argument, the value of "command" and the "args" array from tasks.json. For
example, when running all from this tasks.json:
{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "all",
            "type": "shell",
            "command": "C:/cygwin64/bin/make.exe",
            "args": [
                "all"
            ],
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "problemMatcher": [
                "$gcc"
            ]
        }
    ]
}

arg 1: /bin/bash
arg 2: -c
arg 3: C:/cygwin64/bin/make.exe all
It appears that VS Code changes the current work directory before starting
"terminal.integrated.shell.windows" which would make xhere unnecessary. If
that is so, the fix would be to change the text of
https://code.visualstudio.com/docs/editor/integrated-terminal#_can-i-use-cygwins-shell-with-the-terminal-on-windows
to say that "terminal.integrated.shellArgs.windows" need not be set,
along with a warning that it must not contain -l or --login as they
reset the cwd to the user's home directory.
Version: 1.35.1 (system setup)
Commit: c7d83e57cd18f18026a8162d042843bda1bcf21f
Date: 2019-06-12T14:30:02.622Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.16299

Problem occurs with all extensions disabled.
If I clear "Dev Tools Console" before run build task, it displays nothing
new after running run build task.
VS Code version: Code 1.35.1 (c7d83e57cd18f18026a8162d042843bda1bcf21f, 2019-06-12T14:30:02.622Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (8 x 2712)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.88GB (8.22GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

spellright
ban
3.0.38

remote-containers
ms-
0.59.0

remote-ssh
ms-
0.42.2

remote-ssh-edit
ms-
0.42.2

remote-ssh-explorer
ms-
0.42.2

remote-wsl
ms-
0.38.0

vscode-remote-extensionpack
ms-
0.15.0

cpptools
ms-
0.24.0-insiders

rewrap
stk
1.9.1

You're right, it looks like cygwin just works without the args stuff now. Because of this I think we should just expose it in the default shell selector now using the standard install paths instead of having the FAQ.

It looks like there is still some additional setup needed. I can't just change the shell to cygwin:

Removing cygwin detection for now, it looks like it needs needs args which is an area the shell detector doesn't touch yet. The old instructions don't seem to work, something must have changed in cygwin https://www.fesevur.com/2017/11/cygwin-terminal-in-vscode.html
Hoping someone in the community will put together some instructions that we can update the documentation with. I'll remove the doc entry completely for the time being.


Revert "Pin Python 3.7 version in CI for macos-latest"

This reverts commit 917a1fbe33adf78fe66d7f0c8c57547d16a46f27.
Also require current sparseconverter version, which should fix #1467
Contributor Checklist:

[ ] I have added or updated my entry in the creators.json file
[ ] I have added a changelog entry for my contribution
[ ] I have added/updated documentation for all user-facing changes
[ ] I have added/updated test cases
[ ] I have included the rebuilt production build of the client (only if changes were made to the GUI)

Reviewer Checklist:

[ ] /azp run libertem.libertem-data passed
[ ] No import of GPL code from MIT code

/azp run libertem.libertem-data

/azp run libertem.libertem-data


Update README.md

Added details needed to build the project (git clone) and install the project (make install).

Thank you @ashish-billore, merged.

thanks! @sighingnow


"Compact" step needed in OSM File Loader for file geodatabase output

Hi @ThomasEmge ,
This is only a minor issue, and easily fixable: I noticed the file geodatabases created by the OSM File Loader are considerably bloated after all the steps in the loading process and the Repair Geometry. My Netherlands extract resulted in a 47GB file geodatabase. Compacting reduced this to a mere 17GB. Since this is a very fast process as well, it is well worth integrating it. Maybe there is even the possibly to not only compact at the very end, but in intermediate steps where the Compact step would be appropriate and have any effect. This could then potentially reduce (intermediate) disk space requirements for very large extracts like e.g. loading a continent.
Even if compacting is only effective or sensible for the loading process at the very end, the reduction in final output size is welcome.

I looked at this issue over the past couple of weeks and found it to be a non-event. Starting from a clean geodatabase and loading the data I checked the size, then compacted and it was the same size.
Since I am currently running tests with the Netherlands dataset I'll keep an eye on it but I would vote against it.

Starting from a clean geodatabase and loading the data I checked the size, then compacted and it was the same size.

That's weird, I created a fully new file geodatabase as well for this load session, and the size differences before and after Compact were as I reported them, although I must admit the difference was rather surprisingly big.
But this contrasts starkly with your experience... why?... is it possibly related to the issues with the loading of the multipolygon.
Yes, please do keep an eye on it, and let me know your final size for the Netherlands just after the load (without Compact), and whether its 47 or just under 17 GB.
Could you also report the timings for the loading of the relations and super-relations? I was also a bit surprised how fast these loaded (especially from the view of the "old" Load OSM File tool.
Mine were (using 3 cores):
Relations: Done loading relations (Elapsed Time: 0 hours 4 minutes 29 seconds).
Super-relations: Done loading super relations (Elapsed Time: 0 hours 1 minutes 10 seconds).

After loading the Netherlands osm file with the option to delete the supporting nodes (points), the file geodatabase is 10.1 GB. After running the compact geodatabase tool the file geodatabase is now 10.0 GB.
On my machine the relations loaded in 6 minutes and 15 seconds and the super-relations were completed in 1 minute and 30 seconds. Which in itself is not the complete time required as you should count the time it takes to append everything into a single feature class as well.

On a second country load (Poland) the file geodatabase is 7.84 GB after running the load tool and 7.8 GB after running the compact tool.


Add college

Young capital academy is a dutch company/college, which uses Novi Colleges.

Dear,
I would like to request the inclusion of the domain soulasalle.com.br in the list of Institutions of Higher Education. So that our students of Information Systems of UNILASALLE-RJ (https://www.unilasalle.edu.edu.br/rj/) have access to the tools of Jet Brains. Thank you very much.

@marciamsadok Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request, separate from a third-party request.
Please do not submit a request as a comment to someone's else request.
If you don't know how to make the request on GitHub, please email<EMAIL_ADDRESS>and we try and do it for you. Thank you for the understanding!

@rdelaater @brw I am sorry, this organization does not qualify for being added to this repository. Please see the details at #5590. There is also a solution for the matter: the academy can request free 4-months coupons for the boot camp attendees.
@marciamsadok Your comment was regarding another organization, thus please consider submitting a new request as I suggested above. Thank you.


fix(deps): update module github.com/tetsumaru/go-private-sandbox to v0.0.3

This PR contains the following updates:

Package
Type
Update
Change

github.com/tetsumaru/go-private-sandbox
require
patch
v0.0.2 -> v0.0.3

Release Notes

tetsumaru/go-private-sandbox (github.com/tetsumaru/go-private-sandbox)
v0.0.3
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: go.sum
Command failed: go get -d -t ./...
go<EMAIL_ADDRESS>reading github.com/tetsumaru/go-private-sandbox/go.mod at revision v0.0.3: git ls-remote -q origin in /go/pkg/mod/cache/vcs/86de18e818d2ff3f863245d1730caa64352667da1c19832c71c23235b2a97863: exit status 128:
	fatal: could not read Password for<EMAIL_ADDRESS>terminal prompts disabled


Connect to existing secrets in GCS from new Vault GKE cluster

Question
What are the modifications necessary to connect to existing secrets in GCS from a new Vault cluster in GKE?
Considerations
n.a
Hi guys, after trying this demo and playing around with Vault, my team is keen on implementing Vault for some of our systems.
One last concern I was tasked to investigate -- is it possible to connect to existing secrets in GCS in the event of an unintended loss of Vault cluster (e.g. human accidentally deleted Vault cluster in GKE, other problem with Vault cluster)?
If so, what are the necessary modifications required?
I tried several modifications (the KMS keys, GCS bucket name) to the terraform files to achieve this. The best I was able to achieve was a newly created Vault cluster, and terraform apply returned the same root token as the previous cluster. However, in Vault UI, I was unable to login with this same root token.
Thanks!

Hi @bryan831
When you say "connect to existing secrets in GCS" which of the following do you mean:

An existing GCS bucket that Vault was using to store data
An existing GCS bucket where you put your own data

Vault's storage backend is pluggable, if you spin up vault-cluster-1 against GCS bucket foo, tear it down, and then spin up vault-cluster-2 against the same GCS bucket, it will have the same secrets, same unseal keys, same root token, etc.
Does that answer your question? Sorry I'm not sure I completely understand the issue.

Hi @sethvargo thanks for your reply.
I am referring to 1, exactly the scenario you have mentioned.
I'm having difficulty modifying the demo terraform files to get it to spin up a new Vault cluster against existing Vault GCS secrets bucket.
Could you let me know the only fields I have to change in the terraform files to achieve this?
I think I might have modified more fields than necessary, or missed out some, that is why I cannot login to my new Vault cluster.


Remove section about the localhost port

From what I gather, the localhost HTTP port has been completely removed in Kubernetes 1.24. This PR removes the section making the distinction between the two ports, which is still currently live on the website.

/easycla

Actually, the same section exists in other languages from what I can tell. Let me know if this removal is okay in general, and I can just remove this section from the other languages as well then in an extra commit.

Hi @sftim Since this wants to remove some content could you please review this?  Thanks.
/assign @sftim

Since this wants to remove some content could you please review this?

I'll decline, thanks. I'm happy for any contributor (ideallyL a reviewer for the English localization) to take a lead reviewing this PR.

Alright, so I did not get any feedback about integrating this into the first section... After seeing #30725, I still believe it makes sense to merge the two sections together. So I gave it another shot, feedback appreciated!

/lgtm