text:
"Generate Drupal project with composer package" hanging.

`: -->
Issue Type

Bug Report / Support Request

Your Environment

Vagrant 1.9.3

Your OS

Windows 10

Full console output
TASK [geerlingguy.solr : Expand Solr.] *****************************************
skipping: [drupalvm]
TASK [geerlingguy.solr : Check if Solr is already installed.] ******************
skipping: [drupalvm]
TASK [geerlingguy.solr : Copy Solr into place.] ********************************
skipping: [drupalvm]
TASK [geerlingguy.solr : Ensure Solr install files are owned by the solr_user.]
skipping: [drupalvm]
TASK [geerlingguy.solr : Check if solr_home is already set up.] ****************
skipping: [drupalvm]
TASK [geerlingguy.solr : Ensure solr_home directory exists.] *******************
skipping: [drupalvm]
TASK [geerlingguy.solr : Copy Solr example into solr_home.] ********************
skipping: [drupalvm]
TASK [geerlingguy.solr : Fix the example solrconfig.xml file.] *****************
skipping: [drupalvm]
TASK [geerlingguy.solr : Ensure Solr home files are owned by the solr_user.] ***
skipping: [drupalvm]
TASK [geerlingguy.solr : Ensure log file is created and has proper permissions.] ***
skipping: [drupalvm]
TASK [geerlingguy.solr : Copy solr init script into place.] ********************
skipping: [drupalvm]
TASK [geerlingguy.solr : Ensure daemon is installed (Debian).] *****************
skipping: [drupalvm]
TASK [geerlingguy.solr : Copy solr systemd unit file into place (for systemd systems).] ***
skipping: [drupalvm]
TASK [geerlingguy.solr : Ensure lsof is present (RedHat).] *********************
skipping: [drupalvm]
TASK [geerlingguy.solr : Ensure setfacl support is present.] *******************
skipping: [drupalvm]
TASK [geerlingguy.solr : Run Solr installation script.] ************************
skipping: [drupalvm]
TASK [geerlingguy.solr : Ensure solr is stopped (RHEL 7 workaround).] **********
skipping: [drupalvm]
TASK [geerlingguy.solr : Run systemd daemon_reload (RHEL 7 workaround).] *******
skipping: [drupalvm]
TASK [geerlingguy.solr : Ensure solr is started and enabled on boot.] **********
skipping: [drupalvm]
TASK [geerlingguy.solr : Check current list of Solr cores.] ********************
skipping: [drupalvm]
TASK [geerlingguy.solr : Ensure Solr conf directories exist.] ******************
skipping: [drupalvm] => (item=collection1)
TASK [geerlingguy.solr : Ensure core configuration directories exist.] *********
skipping: [drupalvm] => (item=collection1)
TASK [geerlingguy.solr : Create configured cores.] *****************************
skipping: [drupalvm] => (item=collection1)
TASK [geerlingguy.solr : Remove existing SOLR_HEAP configuration.] *************
skipping: [drupalvm]
TASK [geerlingguy.solr : Apply Solr configuration changes.] ********************
skipping: [drupalvm] => (item={u'regexp': u'^.?SOLR_JAVA_MEM=', u'line': u'SOLR_JAVA_MEM="-Xms64M -Xmx128M"'})
skipping: [drupalvm] => (item={u'regexp': u'^.?SOLR_TIMEZONE=', u'line': u'SOLR_TIMEZONE="UTC"'})
skipping: [drupalvm] => (item={u'regexp': u'^SOLR_PORT=', u'line': u'SOLR_PORT="8983"'})
TASK [geerlingguy.solr : include] **********************************************
skipping: [drupalvm]
TASK [geerlingguy.java : Include OS-specific variables.] ***********************
skipping: [drupalvm]
TASK [geerlingguy.java : Include OS-specific variables for Fedora.] ************
skipping: [drupalvm]
TASK [geerlingguy.java : Include version-specific variables for Ubuntu.] *******
skipping: [drupalvm]
TASK [geerlingguy.java : Define java_packages.] ********************************
skipping: [drupalvm]
TASK [geerlingguy.java : include] **********************************************
skipping: [drupalvm]
TASK [geerlingguy.java : include] **********************************************
skipping: [drupalvm]
TASK [geerlingguy.java : include] **********************************************
skipping: [drupalvm]
TASK [geerlingguy.java : Set JAVA_HOME if configured.] *************************
skipping: [drupalvm]
TASK [geerlingguy.elasticsearch : Add Elasticsearch GPG key.] ******************
skipping: [drupalvm]
TASK [geerlingguy.elasticsearch : Add Elasticsearch repository.] ***************
skipping: [drupalvm]
TASK [geerlingguy.elasticsearch : Install Elasticsearch.] **********************
skipping: [drupalvm]
TASK [geerlingguy.elasticsearch : Add Elasticsearch apt key.] ******************
skipping: [drupalvm]
TASK [geerlingguy.elasticsearch : Add Elasticsearch repository.] ***************
skipping: [drupalvm]
TASK [geerlingguy.elasticsearch : Install Elasticsearch.] **********************
skipping: [drupalvm]
TASK [geerlingguy.elasticsearch : Configure Elasticsearch.] ********************
skipping: [drupalvm]
TASK [geerlingguy.elasticsearch : Start Elasticsearch.] ************************
skipping: [drupalvm]
TASK [geerlingguy.elasticsearch : Make sure Elasticsearch is running before proceeding.] ***
skipping: [drupalvm]
TASK [geerlingguy.varnish : Include OS-specific variables.] ********************
ok: [drupalvm]
TASK [geerlingguy.varnish : Ensure Varnish dependencies are installed.] ********
skipping: [drupalvm] => (item=[])
TASK [geerlingguy.varnish : Add Varnish repository.] ***************************
skipping: [drupalvm]
TASK [geerlingguy.varnish : Set repo fact appropriately.] **********************
skipping: [drupalvm]
TASK [geerlingguy.varnish : Install Varnish.] **********************************
skipping: [drupalvm]
TASK [geerlingguy.varnish : Ensure APT HTTPS Transport is installed.] **********
skipping: [drupalvm]
TASK [geerlingguy.varnish : Add Varnish apt key.] ******************************
skipping: [drupalvm]
TASK [geerlingguy.varnish : Add Varnish apt repository.] ***********************
skipping: [drupalvm]
TASK [geerlingguy.varnish : Install Varnish.] **********************************
changed: [drupalvm]
TASK [geerlingguy.varnish : Copy Varnish configuration (sysvinit).] ************
skipping: [drupalvm]
TASK [geerlingguy.varnish : Copy Debian Jessie/Xenial specific Varnish configs (systemd).] ***
changed: [drupalvm]
TASK [geerlingguy.varnish : Copy Varnish configuration (systemd).] *************
changed: [drupalvm]
TASK [geerlingguy.varnish : Ensure Varnish config path exists.] ****************
ok: [drupalvm]
TASK [geerlingguy.varnish : Copy Varnish default VCL.] *************************
changed: [drupalvm]
TASK [geerlingguy.varnish : Copy varnish secret.] ******************************
changed: [drupalvm]
TASK [geerlingguy.varnish : Ensure Varnish services are started enabled on startup.] ***
ok: [drupalvm] => (item=varnish)
TASK [geerlingguy.security : Include OS-specific variables.] *******************
skipping: [drupalvm]
TASK [geerlingguy.security : Install fail2ban.] ********************************
skipping: [drupalvm]
TASK [geerlingguy.security : Install fail2ban.] ********************************
skipping: [drupalvm]
TASK [geerlingguy.security : Ensure fail2ban is running and enabled on boot.] **
skipping: [drupalvm]
TASK [geerlingguy.security : Update SSH configuration to be more secure.] ******
skipping: [drupalvm] => (item={u'regexp': u'^PermitRootLogin', u'line': u'PermitRootLogin no'})
skipping: [drupalvm] => (item={u'regexp': u'^X11Forwarding', u'line': u'X11Forwarding no'})
skipping: [drupalvm] => (item={u'regexp': u'^GSSAPIAuthentication', u'line': u'GSSAPIAuthentication no'})
skipping: [drupalvm] => (item={u'regexp': u'^ChallengeResponseAuthentication', u'line': u'ChallengeResponseAuthentication no'})
skipping: [drupalvm] => (item={u'regexp': u'^PermitEmptyPasswords', u'line': u'PermitEmptyPasswords no'})
skipping: [drupalvm] => (item={u'regexp': u'^UseDNS', u'line': u'UseDNS no'})
skipping: [drupalvm] => (item={u'regexp': u'^Port', u'line': u'Port 22'})
skipping: [drupalvm] => (item={u'regexp': u'^PasswordAuthentication', u'line': u'PasswordAuthentication no'})
TASK [geerlingguy.security : Add configured user accounts to passwordless sudoers.] ***
TASK [geerlingguy.security : Add configured user accounts to passworded sudoers.] ***
TASK [geerlingguy.security : Install yum-cron.] ********************************
skipping: [drupalvm]
TASK [geerlingguy.security : Ensure yum-cron is running and enabled on boot.] **
skipping: [drupalvm]
TASK [geerlingguy.security : Configure autoupdates (RHEL 7).] ******************
skipping: [drupalvm]
TASK [geerlingguy.security : Install unattended upgrades package.] *************
skipping: [drupalvm]
TASK [geerlingguy.security : Copy unattended-upgrades configuration files in place.] ***
skipping: [drupalvm] => (item=50unattended-upgrades)
skipping: [drupalvm] => (item=10periodic)
TASK [Do not accept locale environment variables passed over SSH.] *************
changed: [drupalvm]
TASK [Check if local known_hosts file is present.] *****************************
ok: [drupalvm]
TASK [Copy known_hosts file from host into Drupal VM.] *************************
skipping: [drupalvm]
TASK [Set SSH home directory.] *************************************************
skipping: [drupalvm]
TASK [Install extra apt packages (if any are configured).] *********************
changed: [drupalvm] => (item=[u'sqlite'])
TASK [Install extra yum packages (if any are configured).] *********************
skipping: [drupalvm] => (item=[])
TASK [Define drupalvm_webserver_user (Debian).] ********************************
ok: [drupalvm]
TASK [Define drupalvm_webserver_user (RedHat).] ********************************
skipping: [drupalvm]
TASK [Register information about the /vagrant directory.] **********************
ok: [drupalvm]
TASK [Ensure a group with the same GID as used to sync directories exist (Ansible 2.3+).] ***
skipping: [drupalvm]
TASK [Ensure the webserver user is in the same group as the owner of synced directories (Ansible
2.3+).] ***
skipping: [drupalvm]
TASK [Detect if group used to sync directories already exist (Ansible 2.2).] ***
ok: [drupalvm]
TASK [Ensure a group with the same GID as used to sync directories exist (Ansible 2.2).] ***
skipping: [drupalvm]
TASK [Ensure the webserver user is in the same group as the owner of synced directories (Ansible
2.2).] ***
changed: [drupalvm]
TASK [Ensure admin group exist.] ***********************************************
changed: [drupalvm]
TASK [Ensure vagrant user is in admin group.] **********************************
changed: [drupalvm]
TASK [Set nicer permissions on Apache log directory.] **************************
changed: [drupalvm]
TASK [Copy Nginx vhosts into place.] *******************************************
skipping: [drupalvm] => (item={u'is_php': True, u'root': u'/var/www/drupalvm/drupal/web', u'server_name': u'drupalvm.dev www.drupalvm.dev'})
skipping: [drupalvm] => (item={u'is_php': True, u'root': u'/var/www/dashboard', u'server_name': u'192.168.88.88 dashboard.drupalvm.dev'})
skipping: [drupalvm] => (item={u'is_php': True, u'root': u'/usr/share/php/pimpmylog', u'server_name': u'pimpmylog.drupalvm.dev'})
skipping: [drupalvm] => (item={u'is_php': True, u'root': u'/usr/share/php/xhprof_html', u'server_name': u'xhprof.drupalvm.dev'})
skipping: [drupalvm] => (item={u'is_php': True, u'root': u'/opt/adminer', u'server_name': u'adminer.drupalvm.dev'})
TASK [Detect if AppArmor is working.] ******************************************
ok: [drupalvm]
[WARNING]: Consider using service module rather than running service
TASK [Ensure MySQL AppArmor profile is disabled (for slow query log).] *********
changed: [drupalvm]
TASK [Restart the AppArmor if necessary.] **************************************
changed: [drupalvm]
TASK [include_role] ************************************************************
TASK [geerlingguy.drupal : Add backwards-compatibility shims.] *****************
included: /vagrant/provisioning/roles/geerlingguy.drupal/tasks/backwards-compatibility.yml for drupalvm
TASK [geerlingguy.drupal : build_makefile shim] ********************************
skipping: [drupalvm]
TASK [geerlingguy.drupal : build_composer shim] ********************************
skipping: [drupalvm]
TASK [geerlingguy.drupal : build_composer_project shim] ************************
skipping: [drupalvm]
TASK [geerlingguy.drupal : install_site shim] **********************************
skipping: [drupalvm]
TASK [geerlingguy.drupal : drupalvm_database shim] *****************************
skipping: [drupalvm]
TASK [geerlingguy.drupal : Check if Drupal is already set up.] *****************
ok: [drupalvm]
TASK [geerlingguy.drupal : Define drupal_site_exists] **************************
ok: [drupalvm]
TASK [geerlingguy.drupal : include] ********************************************
skipping: [drupalvm]
TASK [geerlingguy.drupal : include] ********************************************
skipping: [drupalvm]
TASK [geerlingguy.drupal : include] ********************************************
included: /vagrant/provisioning/roles/geerlingguy.drupal/tasks/build-composer-project.yml for drupalvm
TASK [geerlingguy.drupal : Ensure drupal_composer_install_dir directory has proper permissions.]

changed: [drupalvm]
TASK [geerlingguy.drupal : Generate Drupal project with composer package.] *****
C:\Users\laurence\VirtualBox VMs\Vagrant Boxes\drupal-vm>==> drupalvm: Waiting for cleanup before exiting...
Summary
I have been trying for two days to get this working basically deleting and re-running. Tried the zip file on the site and cloning latest github Just hangs at Generate Drupal project message. No idea whats going on. any help appreciated.

@laurencefass - How long have you let this run before killing it? Sometimes it can take 20, 30, 40 minutes, depending on your Internet connection and how Composer is feeling that day.
I typically avoid using that method of building new sites if I'm just trying to get a quick Drupal 8 site put together—I instead use the example drupal.composer.json file and the composer install technique. But it usually takes less than 5 minutes on my home computer and Internet connection, and about the same in the Travis CI automated builds here on GitHub.

thanks for quick reply. im happy to do whatever to get the site running. please can you give some steps for using the composer method. do i vagrant ssh onto box or run commands on my vbox host? is it as simple as php compose install? which directory? thanks.

also: ive left it running for hours. some sort of progress or activity indicator may be useful... but ill wait for the drupal.composer.json solution and go with it...

@laurencefass see: http://docs.drupalvm.com/en/latest/deployment/composer/
You can also build from a Drush Make file (see other links in the docs linked above).

I dont really understand the context of this link. http://docs.drupalvm.com/en/latest/deployment/composer/
do i make the detailed changes and then run vagrant up? vagrant provision? do i need to make these changes on a totally clean box (so delete the one i have) or can i re-run existing box? should i see a different output?

@laurencefass - You would make those changes then if you already built the VM once, run vagrant provision. Though it might be cleanest if you do vagrant destroy to delete the VM, then vagrant up from scratch again.

ill try in the morning (its night here in the UK) and let you know how i get on. thanks so much for responding so quickly.

following instructions ive added entries into config.yml and left default.config.yml untouched. im assuming the former is parsed after the default file.
drupal_build_makefile: false
drupal_build_composer: true
drupal_build_composer_project: false
drupal_core_path: "{{ drupal_composer_install_dir }}/docroot"
OUTPUT from > vagrant provision
TASK [geerlingguy.drupal : include] ********************************************
skipping: [drupalvm]
TASK [geerlingguy.drupal : include] ********************************************
included: /vagrant/provisioning/roles/geerlingguy.drupal/tasks/build-composer.yml for drupalvm
TASK [geerlingguy.drupal : Ensure drupal_composer_install_dir directory exists.] ***
ok: [drupalvm]
TASK [geerlingguy.drupal : Copy composer.json into temporary location.] ********
changed: [drupalvm]
TASK [geerlingguy.drupal : Move composer.json into place.] *********************
changed: [drupalvm]
TASK [geerlingguy.drupal : Run composer install.] ******************************
...so its stopping here. the longest ive waited is an hour. is there a log file i can look somewhere? have you seen this before?

how do i use composer.json and drupal.composer.json? do i overwrite the former with the latter?

i ran vagrant provision a couple of times and it just worked.

@laurencefass - I'm guessing it was just a network slowdown, or it could've just been super slow if your computer has a spinning hard disk instead of SSD, something like that.

I am trying to run vagrant up in windows 10. But getting this error -
TASK [geerlingguy.drupal : Generate Drupal project with composer package in /tmp/composer-project (this may take a while).] ***
fatal: [drupalvm]: FAILED! => {"changed": true, "cmd": ["/usr/bin/composer", "create-project", "drupal/recommended-project:^9@dev", "/tmp/composer-project", "--prefer-dist", "--stability", "dev", "--no-interaction"], "delta": "0:00:30.199718", "end": "2020-09-08 07:40:38.273486", "msg": "non-zero return code", "rc": 1, "start": "2020-09-08 07:40:08.073768", "stderr": "    1/5:\thttp://repo.packagist.org/p/provider-latest$0e7e2e28ddc4fba18b0423e5c231a2f309dd7a6f86c6fb49ebd06b72eb6df0a1.json\n    2/5:\thttp://repo.packagist.org/p/provider-2020-01$9b89d58c6306aed7da9d22c30a7620db5dcd6614a56b238859073478d84e0373.json\n    3/5:\thttp://repo.packagist.org/p/provider-2020-04$b4cd377d81ef5312aba23b7dd6caaa87f3cf53064cef1a327accd76a8967b5df.json\n    4/5:\thttp://repo.packagist.org/p/provider-2019$96a23217ee6d45f8ec6f76d641fc875940ec1777cdd3161927ca1e28a95e72e3.json\n    5/5:\thttp://repo.packagist.org/p/provider-2020-07$eb7894cc88843498e08e8d9223d2f8c3316eff82add860e0f633be2df9955f9b.json\n    Finished: success: 5, skipped: 0, failure: 0, total: 5\n    1/5:\thttp://repo.packagist.org/p/provider-latest$0e7e2e28ddc4fba18b0423e5c231a2f309dd7a6f86c6fb49ebd06b72eb6df0a1.json\n    2/5:\thttp://repo.packagist.org/p/provider-2020-01$9b89d58c6306aed7da9d22c30a7620db5dcd6614a56b238859073478d84e0373.json\n    3/5:\thttp://repo.packagist.org/p/provider-2019$96a23217ee6d45f8ec6f76d641fc875940ec1777cdd3161927ca1e28a95e72e3.json\n    4/5:\thttp://repo.packagist.org/p/provider-2020-07$eb7894cc88843498e08e8d9223d2f8c3316eff82add860e0f633be2df9955f9b.json\n    5/5:\thttp://repo.packagist.org/p/provider-2020-04$b4cd377d81ef5312aba23b7dd6caaa87f3cf53064cef1a327accd76a8967b5df.json\n    Finished: success: 5, skipped: 0, failure: 0, total: 5\n    1/5:\thttp://repo.packagist.org/p/provider-2020-01$9b89d58c6306aed7da9d22c30a7620db5dcd6614a56b238859073478d84e0373.json\n    2/5:\thttp://repo.packagist.org/p/provider-latest$0e7e2e28ddc4fba18b0423e5c231a2f309dd7a6f86c6fb49ebd06b72eb6df0a1.json\n    3/5:\thttp://repo.packagist.org/p/provider-2019$96a23217ee6d45f8ec6f76d641fc875940ec1777cdd3161927ca1e28a95e72e3.json\n    4/5:\thttp://repo.packagist.org/p/provider-2020-04$b4cd377d81ef5312aba23b7dd6caaa87f3cf53064cef1a327accd76a8967b5df.json\n    5/5:\thttp://repo.packagist.org/p/provider-2020-07$eb7894cc88843498e08e8d9223d2f8c3316eff82add860e0f633be2df9955f9b.json\n
Finished: success: 5, skipped: 0, failure: 0, total: 5\nCreating a "drupal/recommended-project:^9@dev" project at "/tmp/composer-project"\nInstalling drupal/recommended-project (9.1.x-dev b19274227a2e723389bc9082b069f5afb887fe7e)\n  - Installing drupal/recommended-project (9.1.x-dev b192742): Loading from cache\nCreated project in /tmp/composer-project\n    1/2:\thttps://packages.drupal.org/8/drupal/provider-2020-2$6e1e13a519e5df061d623a7ff7a057cf1664acb0e6cc6675f92248e835bb1c06.json\n    2/2:\thttps://packages.drupal.org/8/drupal/provider-2020-3$74fce31854d7aa9febdefbb9c3b07816083c9d986fb7fb5dd33237a19fb7a803.json\n
Finished: success: 2, skipped: 0, failure: 0, total: 2\nLoading composer repositories with package information\nInstalling dependencies (including require-dev) from lock file\nPackage operations: 115 installs, 0 updates, 0 removals\n  - Installing composer/installers (v1.9.0): Loading from cache\n  - Installing drupal/core-composer-scaffold (9.1.x-dev 7b12551): Loading from cache\n  - Installing drupal/core-project-message (9.1.x-dev ae723fe): Loading from cache\n  - Installing typo3/phar-stream-wrapper (v3.1.5): Loading from cache\n  - Installing symfony/polyfill-mbstring (v1.18.1): Loading from cache\n    Failed to download symfony/polyfill-mbstring from dist: Failed to execute (2) unzip -qq -o '/tmp/composer-project/vendor/symfony/polyfill-mbstring/228d3298ea92dc5db0f55d7534bd6049' -d '/tmp/composer-project/vendor/composer/cbf2f3d5'\n\n/tmp/composer-project/vendor/composer/cbf2f3d5/symfony-polyfill-mbstring-a6977d6/Resources/unidata/lowerCase.php  bad CRC 68ab13c6  (should be 8a9fb65a)\n\n    Now trying to download from source\n  - Installing symfony/polyfill-mbstring (v1.18.1): Cloning a6977d63bf from cache\n  - Installing symfony/polyfill-ctype (v1.18.1): Loading from cache\n  - Installing twig/twig (v2.13.1): Loading from cache\n  - Installing symfony/yaml (v4.4.12): Loading from cache\n  - Installing symfony/polyfill-php80 (v1.18.1): Loading from cache\n  - Installing symfony/var-dumper (v5.1.4): Loading from cache\n  - Installing symfony/translation-contracts (v2.1.3): Loading from cache\n  - Installing symfony/validator (v4.4.12): Loading from cache\n    Failed to download symfony/validator from dist: Failed to execute (2) unzip -qq -o '/tmp/composer-project/vendor/symfony/validator/feb2d3a99c1a88725561fb3ac0a2f4fe' -d '/tmp/composer-project/vendor/composer/c5fb5657'\n\n/tmp/composer-project/vendor/composer/c5fb5657/symfony-validator-cee2f13/Constraints/RangeValidator.php  bad CRC dd5913d3  (should be 1bc28ae6)\n\n    Now trying to download from source\n  - Installing symfony/validator (v4.4.12): Cloning cee2f13ddc\n\n                                                                                \n  [RuntimeException]
\n  Failed to clone https://github.com/symfony/validator.git via https, ssh protocols, aborting.  \n
\n  - https://github.com/symfony/validator.git
\n    Cloning into '/tmp/composer-project/vendor/symfony/validator'...                            \n    error: inflate: data stream error (invalid bit length repeat)                               \n    fatal: pack has bad object at offset 408208: inflate returned -3
\n    fatal: index-pack failed                                                                    \n
\n  - git@github.com:symfony/validator.git                                                        \n    Cloning into '/tmp/composer-project/vendor/symfony/validator'...                            \n    git@github.com: Permission denied (publickey).
\n    fatal: Could not read from remote repository.                                               \n
\n    Please make sure you have the correct access rights                                         \n
and the repository exists.                                                                  \n
\n\ncreate-project [-s|--stability STABILITY] [--prefer-source] [--prefer-dist] [--repository REPOSITORY] [--repository-url REPOSITORY-URL] [--add-repository] [--dev] [--no-dev] [--no-custom-installers] [--no-scripts] [--no-progress] [--no-secure-http] [--keep-vcs] [--remove-vcs] [--no-install] [--ignore-platform-reqs] [--] [] [] []", "stderr_lines": ["    1/5:\thttp://repo.packagist.org/p/provider-latest$0e7e2e28ddc4fba18b0423e5c231a2f309dd7a6f86c6fb49ebd06b72eb6df0a1.json", "    2/5:\thttp://repo.packagist.org/p/provider-2020-01$9b89d58c6306aed7da9d22c30a7620db5dcd6614a56b238859073478d84e0373.json", "    3/5:\thttp://repo.packagist.org/p/provider-2020-04$b4cd377d81ef5312aba23b7dd6caaa87f3cf53064cef1a327accd76a8967b5df.json", "    4/5:\thttp://repo.packagist.org/p/provider-2019$96a23217ee6d45f8ec6f76d641fc875940ec1777cdd3161927ca1e28a95e72e3.json", "    5/5:\thttp://repo.packagist.org/p/provider-2020-07$eb7894cc88843498e08e8d9223d2f8c3316eff82add860e0f633be2df9955f9b.json", "    Finished: success: 5, skipped: 0, failure: 0, total: 5", "    1/5:\thttp://repo.packagist.org/p/provider-latest$0e7e2e28ddc4fba18b0423e5c231a2f309dd7a6f86c6fb49ebd06b72eb6df0a1.json", "    2/5:\thttp://repo.packagist.org/p/provider-2020-01$9b89d58c6306aed7da9d22c30a7620db5dcd6614a56b238859073478d84e0373.json", "    3/5:\thttp://repo.packagist.org/p/provider-2019$96a23217ee6d45f8ec6f76d641fc875940ec1777cdd3161927ca1e28a95e72e3.json", "    4/5:\thttp://repo.packagist.org/p/provider-2020-07$eb7894cc88843498e08e8d9223d2f8c3316eff82add860e0f633be2df9955f9b.json", "    5/5:\thttp://repo.packagist.org/p/provider-2020-04$b4cd377d81ef5312aba23b7dd6caaa87f3cf53064cef1a327accd76a8967b5df.json", "    Finished: success: 5, skipped: 0, failure: 0, total: 5", "    1/5:\thttp://repo.packagist.org/p/provider-2020-01$9b89d58c6306aed7da9d22c30a7620db5dcd6614a56b238859073478d84e0373.json", "    2/5:\thttp://repo.packagist.org/p/provider-latest$0e7e2e28ddc4fba18b0423e5c231a2f309dd7a6f86c6fb49ebd06b72eb6df0a1.json", "    3/5:\thttp://repo.packagist.org/p/provider-2019$96a23217ee6d45f8ec6f76d641fc875940ec1777cdd3161927ca1e28a95e72e3.json", "    4/5:\thttp://repo.packagist.org/p/provider-2020-04$b4cd377d81ef5312aba23b7dd6caaa87f3cf53064cef1a327accd76a8967b5df.json", "    5/5:\thttp://repo.packagist.org/p/provider-2020-07$eb7894cc88843498e08e8d9223d2f8c3316eff82add860e0f633be2df9955f9b.json", "    Finished: success: 5, skipped: 0, failure: 0, total: 5", "Creating a "drupal/recommended-project:^9@dev" project at "/tmp/composer-project"", "Installing drupal/recommended-project (9.1.x-dev b19274227a2e723389bc9082b069f5afb887fe7e)", "  - Installing drupal/recommended-project (9.1.x-dev b192742): Loading from cache", "Created project in /tmp/composer-project", "    1/2:\thttps://packages.drupal.org/8/drupal/provider-2020-2$6e1e13a519e5df061d623a7ff7a057cf1664acb0e6cc6675f92248e835bb1c06.json", "    2/2:\thttps://packages.drupal.org/8/drupal/provider-2020-3$74fce31854d7aa9febdefbb9c3b07816083c9d986fb7fb5dd33237a19fb7a803.json", "    Finished: success: 2, skipped: 0, failure: 0, total: 2", "Loading composer repositories with package information", "Installing dependencies (including require-dev) from lock file", "Package operations: 115 installs, 0 updates, 0 removals", "  - Installing composer/installers (v1.9.0): Loading from cache", "  - Installing drupal/core-composer-scaffold (9.1.x-dev 7b12551): Loading from cache", "  - Installing drupal/core-project-message (9.1.x-dev ae723fe): Loading from cache", "  - Installing typo3/phar-stream-wrapper (v3.1.5): Loading from cache", "  - Installing symfony/polyfill-mbstring (v1.18.1): Loading from cache", "    Failed to download symfony/polyfill-mbstring from dist: Failed to execute (2) unzip -qq -o '/tmp/composer-project/vendor/symfony/polyfill-mbstring/228d3298ea92dc5db0f55d7534bd6049' -d '/tmp/composer-project/vendor/composer/cbf2f3d5'", "", "/tmp/composer-project/vendor/composer/cbf2f3d5/symfony-polyfill-mbstring-a6977d6/Resources/unidata/lowerCase.php  bad CRC 68ab13c6  (should be 8a9fb65a)", "", "    Now trying to download from source", "  - Installing symfony/polyfill-mbstring (v1.18.1): Cloning a6977d63bf from cache", "  - Installing symfony/polyfill-ctype (v1.18.1): Loading from cache", "  - Installing twig/twig (v2.13.1): Loading from cache", "  - Installing symfony/yaml (v4.4.12): Loading from cache", "  - Installing symfony/polyfill-php80 (v1.18.1): Loading from cache", "  - Installing symfony/var-dumper (v5.1.4): Loading from cache", "  - Installing symfony/translation-contracts (v2.1.3): Loading from cache", "  - Installing symfony/validator (v4.4.12): Loading from cache", "    Failed to download symfony/validator from dist: Failed to execute (2) unzip -qq -o '/tmp/composer-project/vendor/symfony/validator/feb2d3a99c1a88725561fb3ac0a2f4fe' -d '/tmp/composer-project/vendor/composer/c5fb5657'", "", "/tmp/composer-project/vendor/composer/c5fb5657/symfony-validator-cee2f13/Constraints/RangeValidator.php  bad CRC dd5913d3  (should be 1bc28ae6)", "", "    Now trying to download from source", "  - Installing symfony/validator (v4.4.12): Cloning cee2f13ddc", "", "                                                                                ", "  [RuntimeException]
", "  Failed to clone https://github.com/symfony/validator.git via https, ssh protocols, aborting.  ", "
", "  - https://github.com/symfony/validator.git
", "    Cloning into '/tmp/composer-project/vendor/symfony/validator'...                            ", "    error: inflate: data stream error (invalid bit length repeat)                               ", "    fatal: pack has bad object at offset 408208: inflate returned -3
", "    fatal: index-pack failed                                                                    ", "
", "  - git@github.com:symfony/validator.git                                                        ", "    Cloning into '/tmp/composer-project/vendor/symfony/validator'...                            ", "    git@github.com: Permission denied (publickey).
", "    fatal: Could not read from remote repository.                                               ", "
", "    Please make sure you have the correct access rights
", "    and the repository exists.                                                                  ", "
", "", "create-project [-s|--stability STABILITY] [--prefer-source] [--prefer-dist] [--repository REPOSITORY] [--repository-url REPOSITORY-URL] [--add-repository] [--dev] [--no-dev] [--no-custom-installers] [--no-scripts] [--no-progress] [--no-secure-http] [--keep-vcs] [--remove-vcs] [--no-install] [--ignore-platform-reqs] [--] [] [] []"], "stdout": "", "stdout_lines": []}

authors: ananyakar2012 geerlingguy laurencefass


text:
Create Backup guide

See #7.
For backup for Pi-hole at least, in the GUI you can go to Settings > Teleporter and click 'Backup'. To automate it through the console, you can run pihole -a -t (can I integrate it with something like my geerlingguy.backup role?).
If I run docker-compose exec pihole /bin/bash pihole -a -t it exports a file inside the container. docker-compose cp is not a supported command yet (see https://github.com/docker/compose/issues/3593), so will have to figure out the best way of scripting this... maybe something like:

Create a /backup directory inside the container (mkdir -p /backup).
Run the pihole -a -t command inside the /backup directory.
Cat the contents of /backup/[latest-file-with-extension].tar.gz and pipe them to file on host.
Delete contents of /backup directory (rm -rf /backup/*).

It would be convenient for the pihole -a -t command to have an option to output the archive to shell instead of into a file, that would save the whole file-based annoying process.

I would also like to make it so you could backup the Prometheus data as well, from the configured Docker volume.

You could mount that /backup folder as a volume in your docker compose, so the host has access to the files there without needing your step 3.
Your script could docker-compose exec pihole -a -t into the /backup volume mounted and then you can rsync it off somewhere or whatever other backup method that you want.

Another simple example, is just to store all data that you want to easily backup into a volume, and then you can easily script the export of those volumes through another temporary container that you spin up just for the purposes of data-exporting.
https://docs.docker.com/storage/volumes/#backup-restore-or-migrate-data-volumes

Another way would be to map all volumes you want to backup to your host and then use a dedicated backup client container like duplicati
https://hub.docker.com/r/duplicati/duplicati/
to manage your backup.

I have been testing Duplicati and it's really good solution. I think this could be a good fit for this project as well. Could please anyone point me out which folder from "internet-monitor" I should included into the backup? Some of them seem not to be saved local.
e.g.:
prom/blackbox-exporter is saved here:
volumes:
- ./blackbox/config:/config
However,  nodeexp is here:
volumes:
- /proc:/host/proc:ro
- /sys:/host/sys:ro
- /:/rootfs:ro
Thank you!

@geerlingguy it looks like Prometheus has the ability to create snapshots for backup but you need the admin api enabled https://prometheus.io/docs/prometheus/latest/querying/api/.  How can we do that through the configuration?
Was using this to back up grafana to s3 https://github.com/ysde/grafana-backup-tool, just need the data now to complete it i think.

source: gharchive/issue

authors: Beutelwolf Jatidude asgimenez dracostheblack geerlingguy jrwagz

repo: geerlingguy/internet-pi

license: MIT

license_type: permissive

license_source: github-api


text:
fix: summary tag for safari

Change information
Fixes Summary Detail Default icon for Safari
Before:

After:

Here we should change the code of the document instead of the component.
But the documentation has been fixed in the canary branch, and I expect to release it to the main branch in the next few days.

source: gharchive/pull-request

authors: Deep-Codes unix

repo: geist-org/react


text:
"util/cpt_upgrader.py" not updating RISC-V checkpoints from v23.0.0.1 to changes in #83

To reproduce:
# Obtain the gem5 repo
git clone https://github.com/gem5/gem5.git
cd gem5

# Obtain the #83 PR
git fetch origin pull/83/head:rvv
git switch rvv

wget http://dist.gem5.org/dist/develop/checkpoints/riscv-hello-example-checkpoint-20230222.tar
mkdir checkpoint
tar xf riscv-hello-example-checkpoint-20230222.tar -C checkpoint/
./util/cpt_upgrader.py -v checkpoint

The following output is returned:
Processing file checkpoint/m5.cpt....

has tags arm-miscreg-teehbr arm-ccregs arm-gem5-gic-ext dvfs-perflevel x86-add-tlb ide-dma-abort remove-arm-cpsr-mode-miscreg etherswitch armv8 register-files ruby-block-size-bytes mempool-to-seworkload process-fdmap-rename cpu-pid globals-to-root smt-interrupts memory-per-range mempool-sections isa-is-simobject arm-sysreg-mapping-ns arm-contextidr-el2 multiple-event-queues arm-hdlcd-upgrade arm-sve arm-gicv2-banked-regs

...nothing to do

I have only proven this fault when working with #83 for updating a checkpoint from v23.0.0.1 to that necessary for the PR. The limitation of "util/cpt_upgrader.py" may exist elsewhere.

@BobbyRBruce can we close this?

authors: BobbyRBruce powerjg

license_source: bigquery


text:
Fix style in RISC-V isa file

https://github.com/gem5/gem5/blob/dceabe5fda598937b00959cc648fb7f2fbbe950a/src/arch/riscv/isa.hh#L73C19-L73C19
This should be rvType instead of rv_type.

I think pcstate.hh also need to be fix
https://github.com/gem5/gem5/blob/dceabe5fda598937b00959cc648fb7f2fbbe950a/src/arch/riscv/pcstate.hh

Pushed changes to pcstate.hh.


text:
Tiger-proxy certificate issue

Steps to Reproduce:
Start all services using the command:docker-compose -f dc-mocks.yml up
All service containers will show a healthy status, except for tiger-proxy. The health status of tiger-proxy is as follows:
"Health": {
  "Status": "unhealthy",
  "FailingStreak": 46,
  "Log": [
    {
      "Start": "2024-08-29T14:50:47.486744176+02:00",
      "End": "2024-08-29T14:50:47.530896422+02:00",
      "ExitCode": 1,
      "Output": "wget: can't connect to remote host: Connection refused\n"
    }
  ]
}

Visit https://localhost/ in a browser. The browser shows an SSL warning. Continue by selecting the "Accept Risk" option.
The connection suddenly closes, and the browser displays the message:
"localhost unexpectedly closed the connection."
Upon checking the service logs, the following messages appear:

tiger-proxy                | 2024-08-29T12:56:32.231Z  INFO 1 --- [orkerEventLoop7] o.b.jsse.provider.ProvTlsServer          : [server #10 @6de25193] accepting connection from (unknown):(unknown)
tiger-proxy                | 2024-08-29T12:56:32.235Z  INFO 1 --- [orkerEventLoop7] o.b.jsse.provider.ProvTlsServer          : [server #10 @6de25193] received fatal(2) certificate_unknown(46) alert
tiger-proxy                | 2024-08-29T12:56:32.235Z  INFO 1 --- [orkerEventLoop7] o.b.jsse.provider.ProvTlsServer          : [server #10 @6de25193] disconnected from (unknown):(unknown)
tiger-proxy                | 2024-08-29T12:56:32.236Z  WARN 1 --- [orkerEventLoop7] d.g.t.t.m.n.u.PortUnificationHandler     : TLS handshake failure:
tiger-proxy                |
tiger-proxy                |  Client does not trust MockServer Certificate Authority for:[id: 0xd9edb655, L:/172.24.0.3:443 ! R:/172.24.0.1:53694]. See http://mock-server.com/mock_server/HTTPS_TLS.html to enable the client to trust MockServer Certificate Authority.
tiger-proxy                |
tiger-proxy                | 2024-08-29T12:56:32.241Z  INFO 1 --- [orkerEventLoop3] o.b.jsse.provider.ProvTlsServer          : [server #11 @576dd0a3] accepting connection from (unknown):(unknown)
tiger-proxy                | 2024-08-29T12:56:32.247Z  INFO 1 --- [orkerEventLoop3] o.b.jsse.provider.ProvTlsServer          : [server #11 @576dd0a3] established connection with (unknown):(unknown)
tiger-proxy                | 2024-08-29T12:56:32.249Z  INFO 1 --- [orkerEventLoop3] o.b.jsse.provider.ProvTlsServer          : [server #11 @576dd0a3] disconnected from (unknown):(unknown)

Note :  We have checked the tiger-proxy certificates inside ca.p12 file  https://github.com/gematik/epa-deployment/blob/main/tiger-proxy/ca.p12. We found that the CA certificate expired on Thu, 18 Jul 2024 12:55:12 GMT.
We also tried using a self-signed certificate, but it did not work.

Hey @jisspala ,
thanks for the info. We just a released a new version including updated certificate.
Problem should be resolved now.
Regards.

Hi @sonerd ,
Thanks for your reply and the update. We have pulled the latest version and run it, but unfortunately, we are still experiencing the issue. Here is the log we are getting when we access https://localhost/ in Chrome
tiger-proxy                | 2024-09-02T16:57:09.851Z  INFO 1 --- [orkerEventLoop9] o.b.jsse.provider.ProvTlsServer          : [server #31 @39575337] accepting connection from (unknown):(unknown) tiger-proxy                | 2024-09-02T16:57:09.854Z  INFO 1 --- [orkerEventLoop9] o.b.jsse.provider.ProvTlsServer          : [server #31 @39575337] received fatal(2) certificate_unknown(46) alert tiger-proxy                | 2024-09-02T16:57:09.855Z  INFO 1 --- [orkerEventLoop9] o.b.jsse.provider.ProvTlsServer          : [server #31 @39575337] disconnected from (unknown):(unknown) tiger-proxy                | 2024-09-02T16:57:09.855Z  WARN 1 --- [orkerEventLoop9] d.g.t.t.m.n.u.PortUnificationHandler     : TLS handshake failure: tiger-proxy                |  tiger-proxy                |  Client does not trust MockServer Certificate Authority for:[id: 0x6075c6e5, L:/172.24.0.4:443 ! R:/172.24.0.1:32866]See http://mock-server.com/mock_server/HTTPS_TLS.html to enable the client to trust MocksServer Certificate Authority. tiger-proxy                |  tiger-proxy                | 2024-09-02T16:57:09.860Z  INFO 1 --- [orkerEventLoop3] o.b.jsse.provider.ProvTlsServer          : [server #32 @8236407] accepting connection from (unknown):(unknown) tiger-proxy                | 2024-09-02T16:57:09.865Z  INFO 1 --- [orkerEventLoop3] o.b.jsse.provider.ProvTlsServer          : [server #32 @8236407] established connection with (unknown):(unknown) tiger-proxy                | 2024-09-02T16:57:09.866Z  INFO 1 --- [orkerEventLoop3] o.b.jsse.provider.ProvTlsServer          : [server #32 @8236407] disconnected from (unknown):(unknown) tiger-proxy                | 2024-09-02T16:57:15.239Z  INFO 1 --- [io-8080-exec-10] o.b.jsse.provider.PropertyUtils          : Found string system property [java.home]: /opt/java/openjdk tiger-proxy                | 2024-09-02T16:57:15.245Z  INFO 1 --- [orkerEventLoop4] d.g.t.t.p.h.AbstractTigerRouteCallback   : Received HTTP GET / User-Agent: 'unirest-java/3.1.00' Request-Length: 0 bytes => http://vau-proxy-server:8080/ tiger-proxy                | 2024-09-02T16:57:15.250Z  INFO 1 --- [ver-Scheduler16] d.g.t.t.p.h.AbstractTigerRouteCallback   : Returning HTTP 404 Response-Length: 0 bytes tiger-proxy                | 2024-09-02T16:57:30.289Z  INFO 1 --- [nio-8080-exec-2] o.b.jsse.provider.PropertyUtils          : Found string system property [java.home]: /opt/java/openjdk tiger-proxy                | 2024-09-02T16:57:30.295Z  INFO 1 --- [orkerEventLoop7] d.g.t.t.p.h.AbstractTigerRouteCallback   : Received HTTP GET / User-Agent: 'unirest-java/3.1.00' Request-Length: 0 bytes => http://vau-proxy-server:8080/ tiger-proxy                | 2024-09-02T16:57:30.300Z  INFO 1 --- [rver-Scheduler8] d.g.t.t.p.h.AbstractTigerRouteCallback   : Returning HTTP 404 Response-Length: 0 bytes

Have you added the root ca to your local trust store? That is of course a prerequisite.

authors: Arkinator jisspala sonerd

repo: gematik/epa-deployment


text:
[Feature]: add a visual cue that shows tasks have been skipped

Describe your feature
Uplift will skip tasks within its internal workflow when certain preconditions are met. However, the current behaviour is that tasks will disappear from the output. It would be a better developer experience if the output showed that a task was skipped.
Your potential solution
Refactor the existing middleware so that when a task is skipped, it will be logged out.
An example output would be:
• (skipped) task

Any additional information?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

By default, skipped tasks will not be shown unless the --debug flag is used

repo: gembaadvantage/uplift


text:
protein transport from ciliary membrane to plasma membrane

Should the ciliary membrane be considered a plasma membrane region?
It is currently classified in this way (via 'cell projection membrane'):

But we also have this - which suggests

I think it makes most sense to think of it as a plasma membrane region - however specialised in may be.

(Think there's been some related discussion/tickets on this).
@paolaroncaglia

Hi David,
You're probably thinking about this other ticket https://github.com/geneontology/go-ontology/issues/11830
The relevant bits from Karen say
(some time ago) “Although I previously said I was leaning towards classifying the cilium as a cytoplasmic structure that is bounded by the ciliary membrane and which protrudes through the plasma membrane, David has reminded me that the ciliary membrane contains transmembrane receptors that we do not want to classify as "cytoplasmic" in GO. Therefore, we will make the "ciliary membrane" a specialized part of the "plasma membrane" and then the rest of the cilium will be cytoplasmic, but the entire cilium will not be classified as "cytoplasmic”.”
(more recently) "Regarding whether or not the "ciliary cytoplasm" should be considered part of the "cytoplasm". I am inclined to agree with Helen that this is not correct, despite the fact that we agreed to make it part of the cytoplasm when we discussed this with several ciliary researchers. At the FASEB Cilia and Flagella meeting I attended this summer, there were several talks about the fact that the composition of the both the plasm and the membrane of the cilium is detectably different from that in the non-ciliary cytosol and plasma membrane, e.g. calcium ion concentration, membrane lipid composition, more. By analogy with the "nucleoplasm" which is excluded from "cytoplasm", the cilium is gated by a structure that is basically the same structure as a nuclear pore, so it seems equally valid to exclude the ciliary plasm from the cytoplasm."
In ciliary research it is important to capture the process of transporting proteins from the ciliary membrane to the 'rest' of the plasma membrane - the one excluding the plasma membrane region constituting the ciliary membrane. Not sure about how to best capture this. The more recent considerations from Karen above seem to point towards severing the link between ciliary and plasma membrane but of course the ciliary membrane is still a membrane region. Can we do that? (i.e. is_a 'membrane region' rather than is_a 'plasma membrane region' but we'd have to work around the link to cell projection similarly to what we did for the cytoplasmic terms...)
Karen, could you please comment on the biology? @krchristie
Thanks,
Paola

Thanks Paola.  Looks like we decided just to change the 'plasm' term but not the membrane.  I think this means that there is no safe logical definition for  'protein transport from ciliary membrane to plasma membrane' unless we make a term for all bits of plasma membrane that are not ciliary membrane, or extend our use of OWL outside of EL so we can refer to parts of PM not part of 'ciliary membrane'.  Neither seems a good idea, so I'll just relax the Equivalent class axiom to subclassof axioms.

Paola, you copied in an accurate statement of my view of the biology.
If David is satisfied that the axioms work, that's good for me.
-Karen

Thanks Karen,
Paola

authors: dosumis krchristie paolaroncaglia

repo: geneontology/go-ontology


text:
ntr: 	tRNA ( guanine-N7)-methylation

descendant of
GO:0036265	RNA ( guanine-N7)-methylation
standard def
PMID: 17382321

Please supply def

The standard def for the other terms appears to be:
The process whereby a guanine in a RNA is methylated at the N7 position of guanine.

Thanks; but what I meant was a PMID for it, not the def.  I'm still jet lagged

PMID: 17382321 ;)

I see a problem here unrelated to the actual term:
GO:0036265 RNA ( guanine-N7)-methylation is part of 7-methyl G RNA capping. Because of this the child terms rRNA and tRNA  guanine-N7)-methylation get the same part of.
I think the part_of  to 7-methyl G RNA capping needs to be removed from RNA ( guanine-N7)-methylation

Do we have a methylation DP yet?

DP?

The capping would have_part N7 G methylation

I could make the tRNA ( guanine-N7)-methylation (NTR) a child of tRNA methylation instead.

Made new term RNA 5'cap (guanine N7) methylation  in addition and fixed parentage, in addition to adding your tRNA term.
Closed.

authors: ValWood cmungall hdrabkin


text:
NTR:  'antibacterial innate immune response'

Requested in https://github.com/geneontology/go-annotation/issues/2448#issuecomment-526647270
PMID:16177355
PMID:23006328

Definition and parents should be based on those of 'antifungal innate immune response'.
@addiehl @mgiglio99
Pascale

@hdrabkin When the terms are in MGI, you can annotate the papers above.
Thanks !


text:
cytoskeleton/nuclear membrane localization -MF (anchoring)

GO:0090286
cytoskeletal anchoring at nuclear membrane
Definition The process in which cytoskeletal filaments are directly or indirectly linked to the nuclear membrane.
has 5 experimental annotations from the same paper:
PMID:18396275
SUN1&2 and SYN1-3
These are KASH and SUN domain containing proteins and  are the same proteins that anchor the SPB (a cytoskeleton component, and other microtubule organizing  centres microtubule organising )  in the nuclear membrane
So this is the same "activity" used in very similar processes described in totally different ways:

~Part of the problem is describing
"cytoskeleton anchoring at the nuclear membrane" as "protein  and macromolecule localization. This should really be "organelle localization" with maybe "cytoskeleton localization" as a descendent.
(and removing the cytoskeleton organization" parent.?)~
I think we just dealt with this? If not we have a solution in the other membrane  anchor term (make it clearer that the anchored object can be an organelle)

solution
obsolete  GO:0071789   spindle pole body localization to nuclear envelope
This is a molecular function
term and  create new MF term
a descendant of GO:0106006   cytoskeletal protein-membrane adaptor activity
NEW1  cytoskeleton-nuclear membrane adaptor activity
NEW2  MTOC - nuclear membrane adaptor activity (anchor would be better here, more common language?)
NEW3 narrow SPB- nuclear membrane anchor activity (add parent to BP spindle pole body localization)
NEW4   centrosome-nuclear membrane anchor activity

[] Create new MF term to replace BP: cytoskeleton-nuclear membrane anchor activity

add synonym cytoskeletal protein-nuclear membrane anchor activity
cytoskeletal protein-nuclear membrane adaptor activity

Reference PMID: 16237665

+[Term]
+id: GO:0140444
+name: cytoskeleton-nuclear membrane anchor activity
+namespace: molecular_function
+def: "The binding activity of a molecule that brings together a cytoskeletal protein or protein complex and a nuclear membrane lipid or membrane-associated protein, in order to maintain the localization of the cytoskeleton at a specific location of the plasma membrane." [PMID:16237665]
+synonym: "cytoskeletal protein-nuclear membrane adaptor activity" EXACT []
+synonym: "cytoskeletal protein-nuclear membrane anchor activity" EXACT []
+is_a: GO:0043495 ! protein-membrane adaptor activity
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/18283 xsd:anyURI
+created_by: pg
+creation_date: 2020-03-24T14:57:59Z

authors: ValWood pgaudet


text:
How to setup remote device events?

I have been trying to setup receiving remote events using Harvester/genicam. But I run into some trouble when decoding the event.
I have set it up as:
        event_token = image_acquirer.remote_device.register_event(EVENT_TYPE_LIST.EVENT_REMOTE_DEVICE)
        event_manager = EventManagerRemoteDevice(event_token)
        event_adapter = EventAdapterGEV()
        event_adapter.attach_node_map(node_map.pointer)

This works and I can then use:
event_manager.num_in_queue

To check the queue for when events have come in. But to decode I was expecting to use something like:
        lm = LibraryManager()
        buffer = bytes()
        length = 0
        lm.event_get_data(event_token.h_event, buffer, length, 10000)
        event_adapter.deliver_message(buffer)
        print("LogMessageLevel: ", node_map.LogMessageLevel.value)

But here is where I run into problems, the arguments to lm.event_get_data() needs to be casted, for example buffer needs to be of the type void *,
TypeError: in method 'LibraryManager_event_get_data', argument 3 of type 'void *'

I tried using ctypes.c_void_p but this was not accepted. What should I be using to call these functions and get my log events into the node map for "easy" access?
As a workaround I found out I can read event_manager.optional_data and there parse the values I need from the raw data, but this doesn't seams like a good long term solution.

@aircleaner Hi Jonas, please excuse me for having kept your ticket waiting such long. Finally, I've finished preparing a prototype that allows you to involve the remote device event feature; there had not had been a chance to dig this further in the previous months but finally got the chance in the last weeks. I would like to check if the change does not slow the image acquisition process so I need to ask you a favor for testing. I will create a branch for this prototype so that you can give it a try anytime when you can but it is not urgent or you are not obliged at all. When you get a chance to try it out, just let me know. Thanks, Kazunari.

@kazunarikudo thank you for the effort in trying to find a fix for this, we can of course test this, I will assign it to my college Alfred when he is back at the office.

Version 1.4.1 resolves the issue.

authors: aircleaner kazunarikudo olofsjo

repo: genicam/harvesters


text:
Use certifi to set GDAL_CURL_CA_BUNDLE / PROJ_CURL_CA_BUNDLE defaults

Resolves #66
This makes certifi and installation requirement and follows approach from Fiona #1095 and rasterio #2459

The conda macos failure is also happening on main, so unrelated:
 ImportError while loading conftest '/Users/runner/work/pyogrio/pyogrio/pyogrio/tests/conftest.py'.
pyogrio/__init__.py:1: in <module>
    from pyogrio.core import (
pyogrio/core.py:6: in <module>
    from pyogrio._ogr import (
E   ImportError: dlopen(/Users/runner/work/pyogrio/pyogrio/pyogrio/_ogr.cpython-39-darwin.so, 2): Symbol not found: _ZSTD_compressBound
E     Referenced from: /Users/runner/micromamba/envs/test/lib/libgdal.30.dylib
E     Expected in: /Users/runner/micromamba/envs/test/lib/libblosc.1.dylib
E    in /Users/runner/micromamba/envs/test/lib/libgdal.30.dylib

Ah, I see you already opened https://github.com/geopandas/pyogrio/pull/99 to try to fix this

authors: brendan-ward jorisvandenbossche

repo: geopandas/pyogrio


text:
update configuration to YAML

Overview
Updates pycsw configuration from ini to YAML.
Related Issue / Discussion
Fixes #797
Additional Information
TODO

[x] migration tool/script

External updates required

[x] pycsw public demo (https://github.com/geopython/demo.pycsw.org)
[ ] GeoNode CSW plugin
[ ] CKAN CSW plugin

Contributions and Licensing
(as per https://github.com/geopython/pycsw/blob/master/CONTRIBUTING.rst#contributions-and-licensing)

[x] I'd like to contribute [feature X|bugfix Y|docs|something else] to pycsw. I confirm that my contributions to pycsw will be compatible with the pycsw license guidelines at the time of contribution.
[x] I have already previously agreed to the pycsw Contributions and Licensing Guidelines

We will also need to update the kubernetes helm charts when this is merged

k8s and helm charts first pass updated as part of this PR.

migration script added
associated demo update PR in https://github.com/geopython/demo.pycsw.org/pull/10

Nice work, just to confirm: the override mechanism with environmental variables is still supported?

@pvgenuchten yes, environment variables are interpreted as per before.

authors: kalxas pvgenuchten tomkralidis

repo: geopython/pycsw

license: mit


text:
Compilation error[E0195]: lifetime parameters or bounds on type Target do not match the trait declaration

Hello,
I'm getting an compilation error when implementing the first example as mentioned in https://crates.io/crates/geographiclib-rs
Compiling geographiclib-rs v0.2.3
error[E0195]: lifetime parameters or bounds on type `Target` do not match the trait declaration
  --> /Users/d029158/.cargo/registry/src/index.crates.io-6f17d22bba15001f/geographiclib-rs-0.2.3/src/geodesic.rs:45:1
   |
45 | / lazy_static! {
46 | |     static ref WGS84_GEOD: Geodesic = Geodesic::new(WGS84_A, WGS84_F);
47 | | }
   | |_^ lifetimes do not match type in trait
   |
   = note: this error originates in the macro `__lazy_static_internal` which comes from the expansion of the macro `lazy_static` (in Nightly builds, run with -Z macro-backtrace for more info)

I have got the same error when compiling a program which  uses surrealdb as surrealdb has a dependency to geographiclib-rs v0.2.3.
I'm using a MacBook with the following processor: 2,3 GHz 8-Core Intel Core i9.
Do you have an idea what the problem is?
Kind regards,
Stephan

I'm not immediately able to reproduce your issue. I've just added a compilable example with #55 which successfully builds.
Can you tell me the output of cargo --version?

I'm using the following cargo version:
cargo 1.75.0 (1d8b05cdd 2023-11-20)
My test program is pretty much the example that you are providing.
use geographiclib_rs::{Geodesic, DirectGeodesic};

fn main() {
    // Determine the point 10000 km NE of JFK - the "direct" geodesic calculation.
    let g = Geodesic::wgs84();
    let jfk_lat = 40.64;
    let jfk_lon = -73.78;
    let northeast_azimuth = 45.0;

    let (lat, lon, az) = g.direct(jfk_lat, jfk_lon, northeast_azimuth, 10e6);

    use approx::assert_relative_eq;
    assert_relative_eq!(lat, 32.621100463725796);
    assert_relative_eq!(lon, 49.05248709295982);
    assert_relative_eq!(az,  140.4059858768007);
}

Is it maybe a problem of lazy_static? It has not been maintained for years and there are alternatives available in the standard library now.

https://crates.io/crates/lazy_static/versions
Maybe this issue is somehow related: https://stackoverflow.com/questions/77710297/encountered-e0195-lifetime-parameters-or-bounds-on-type-target-do-not-match

Are you able to clone this repository and build the examples?
CI shows that it's possible: https://github.com/georust/geographiclib-rs/pull/55

Is it maybe a problem of lazy_static? It has not been maintained for years and there are alternatives available in the standard library now.

I think it's been stable for years, so it hasn't needed much maintenance.
But yes there are alternatives in std now. Would you be interested in opening a PR to migrate? And do the research to know which MSRV introduced the alternatives so you know what we'd need to bump our MSRV to?

Hello Michael,
I have reinstalled Rust and now it works and I can compile the example application.
I still don't understand the reason, but the issue was obviously not related to your repository.
Sorry for the inconvenience!
Kind regards,
Stephan

authors: michaelkirk stephan-j-lange

repo: georust/geographiclib-rs


text:
Error handling of bad polyline still broken

Our xix in #37 has not worked: trying to decode the polyline 'ugh_ugh' gives an out of bounds error on line 142:
index out of bounds: the len is 7 but the index is 7.

cc @mattiZed

Repro (note ommission of should_panic directive on the test: we want to ensure that error values and panics are surfaced, and we want to distinguish between them, since we can handle errors, but not panics). We expect this test to return an Err value, but we have a logic error in our loop beginning on line 141:
#[test]
fn invalid_string() {
    let s = "ugh_ugh";
    let expected: Result<_, _> = Err("Cannot decode character at index 12".to_string());
    assert_eq!(decode_polyline(s, 5), expected);
}

Well then, I guess it's time to actually understand and fix the algorithm instead of suppressing the symptoms - I might have a bit of free time for this next week as my org also relies on this crate in some sense.

authors: mattiZed urschrei

repo: georust/polyline


text:
Mapstore refactor API v2: migrate blob to new table

With the development made in the epic, now the data blob are stored in map_data instead of mapstore2_adapter_mapstoreresource.
Is required to have a migration file in order to move all the blob files into the new table and assign them to the correct resource

@giohappy for this migration we will have 2 choices:

Maintain the models in order to use the Django ORM to migrate the values from the old table to the new one and find a way to deprecated them (maybe override the save method and show in some way a warning). This migration will use RunPython
Delete the models from the MapStore library and use the SQL to run the migration (RunSQL)

I prefer the second one since we will delete the models and they will not be available anymore, but this can create some issue with the retro-compability
Any thoughts?

What about two migrations in sequence where the first one migrates the data and the second one removes the models? If they're managed they should be automatically deleted from DB too.

What about two migrations in sequence where the first one migrates the data and the second one removes the models? If they're managed they should be automatically deleted from DB too.
Yes, this is exactly what I did here:
First migration into maps  -> https://github.com/GeoNode/geonode/blob/16bc3f13a430cea16657892873d0d549426a5ba9/geonode/maps/migrations/0033_map_blob_migration.py
Second migration into mapstore -> https://github.com/GeoNode/geonode-mapstore-client/blob/1b9bb6469acbc79df5f9f1d51bd5ce33290f76d8/mapstore2_adapter/migrations/0005_remoe_mastore_models.py

by models in this comment, I mean the file models.py. If we want to approach the migration with the Django ORM, we cannot delete the file

authors: giohappy mattiagiupponi

repo: geosolutions-it/nexus-geonode


text:
support GDAL_METADATA private tag

support GDAL_METADATA private tag (same as rasterio dataset tags), parse XML into dict.
from aiocogeo import COGReader

async with COGReader("https://async-cog-reader-test-data.s3.amazonaws.com/cog_alpha_band.tif") as cog:
    print(cog.gdal_metadata)

>>> {'OVR_RESAMPLING_ALG': 'NEAREST'}

Codecov Report

Merging #78 into master will decrease coverage by 0.59%.
The diff coverage is 42.85%.

@@            Coverage Diff             @@
##           master      #78      +/-   ##
==========================================
- Coverage   91.72%   91.12%   -0.60%
==========================================
  Files          13       13
  Lines        1148     1161      +13
==========================================
+ Hits         1053     1058       +5
- Misses         95      103       +8

Impacted Files
Coverage Δ

aiocogeo/constants.py
100.00% <ø> (ø)

aiocogeo/ifd.py
90.32% <36.36%> (-5.30%)
:arrow_down:

aiocogeo/cog.py
93.90% <66.66%> (-0.30%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: codecov-commenter geospatial-jeff

repo: geospatial-jeff/aiocogeo


text:
Cleanup readme documentation

The current documentation is too focused on the implementation and not the features.
For example the post processors section is should talk about substitution and less about it being a post processor.
Add better examples early to show what is possible.
move the examples up.
Maybe include some images to better describe the architecture.

Partially addressed by https://github.com/gestalt-config/gestalt/actions/runs/4759600163

closing for now. Eventually i would like to create a static site to replace the readme docs.

repo: gestalt-config/gestalt


text:
Password removed every time you open setting->privacy

Bug description:
After successful set a password on Mac Version Bigsur M1 version 11.4 (Ferdi version5.6.0 beta6, but also on previous one)
It works at usual.
If you open setting and go to privacy and then close password it will be set as blank (no password).
So if you restart app (or simple lock it) when ferdi ask for password you can enter only using blank password.
This problem happen just opening settings->privacy (you do not need to click on password setting)
I think is very important to solve thanks!
Thanks for all this great job!

Testing Version: 5.6.0-nightly.57 on same device problem seems solved.

@mccoy88f - could you please close the ticket if the issue has been resolved in the latest nightly?

Problem solved with latest nightly build. Closed

repo: getferdi/ferdi


text:
[Feature Request] Ability to run Selenium tests on a Selenium Grid instead of locally

Gauge currently runs tests on my local machine. I'd like to ability to run tests remotely either on a separate Selenium node or hub for several reasons:

Keep resources on my machine free so that I may continue testing manually
Make more efficient use of parallel test execution
Compatibility/Version testing
Keep tests in a controlled environment that doesn't have my local test environment changes

It's possible to run Gauge tests on selenium grid. Here's an example project. https://github.com/apoorvam/gaugeGrid

authors: ghost mahendrakariya

repo: getgauge/gauge


text:
Running specs before parallel execution

New feature
There are some tests that can't run in parallel, thus, I would like to run them after a group of spec that run in parallel and get all the results in one report.

@jonathangiber Can you give us an example why you would like to run tests in serial after a parallel run?

@nehashri sure, I'm running many tests, some of them cannot be run in parallel mode (I can explain why if needed). So basically, I would like to get 1 html report with all the tests that I need to run, this is not possible since if I run two scripts one after another (for example a parallel run and after that a normal run), I will get 2 reports.
Thanks,

@jonathangiber Please do elaborate on why you are running some tests in serial while some in parallel.

Basically I would like to run all of them in parallel, but since we have some tests related to okta, those cannot run in parallel. That's why I would like to run those on serial.

@jonathangiber Now I see why you need this feature.
Unfortunately, we do not have the bandwidth to prioritize this right now. If you would really like to see one report, you may want to consider writing something custom to combine json reports.

@nehashri understood, thank you very much

Reopening this. I still feel this is a valid feature request.
Users can choose to configure different runs such as:

filter by tags
filter by env.

The report can be independantly generated, however there could also be a way to merge two reports when it makes sense to view them together.

This is certainly something that would be useful for me.
I have a few tests where the number of items are checked in two different places to see if they match. However if I have other tests running in parallel, the tests fail recurrently because between the 1st and 2nd checks a new item is created by a test running in parallel.
A possible alternative, as was mentioned, is the ability of merging reports from different runs.

Here's a thought - what do you (@jonathangiber, @j-morsum ) feel about this:

introduce a project-level new run configuration file (ex. gauge-run.yml / gauge-run.json) which can hold rules to execute.
gauge shall honour the config file to figure out how the execution has to be orchestrated.

The question is - what all could such a config dictate?

Hi,
Another possible option for your consideration is to add this settings to the spec file i.e.
settings: parallel (default) / pre:[priority] / post:[priority]
That way, not need to maintain another configuration file and duplicate spec/scenario names to this file.
The priority enable configure the order of the tests running pre/post the parallel tests.
What do you think?

@sriv
Another possibility I can think of is having a reserved tag keyword e.g. prerun/postrun that will trigger the spec to run in serial before or after the parallel run, same idea as the previous comment, to avoid another config file.

Good ideas, thank you @jonathangiber and @dudicp
My only concern with the spec file containing this - it's is a "runtime" config, and I somehow feel this is not related to how one would express the test itself.
@zabil - what do you think? There are two school of thoughts.

For me one of the problems using the specs files is losing the ability to run the tests based on the tags. So that would mean that the whole spec needs to run in serial and not only some scenarios.
I would prefer to have a flag (e.g. --pre / --post) which would receive a tag or a spec file to run the scenarios in serial before or after the parallel execution.

@j-morsum that sounds good for me too

Like @sriv points out, it's better have run time information outside the spec files.
@j-morsum suggestion looks good.
Call it --setup and --teardown which is available for both serial and parallel runs?

Here's a proposal.
Add an option to --parallel for filtering by tags.
For e.g.
$ gauge run specs  --parallel "atag"

This will first run all scenarios without the tag atag serially, and then run in parallel scenarios with the tag atag.
This can be used with other tags for example
$ gauge run --tags "auth" specs --parallel "atag"

Which will run scenarios tagged auth serially before running atag in parallel.
In case the tags are repeated for e.g.
$ gauge run --tags "atag" specs --parallel "atag"

It ignores the --parallel option for "atag" with a warning.
Open Question

Support for tag filters on --parallel option.

Looks good. Thanks!
BTW, what will be the default behavior when "--parallel" argument not specified? will all specs run serially?

Yes.
The default behaviour will be the same as now. i.e. It will run serially when unless --parallel flag is added.

though I like the approach, I think intuitively the parallel flag is harder to undestand, what the execution order is.
It is clear, that the following tags are run in parallel, but before or after everything else ?
It might be ok, if documentation is sufficient, but then still one would need to look it up, instead of understand it right away.
Also, are there cases, where the parallel tests shall run before the serial ones ?
Also, can I run multiple tags in parallel (like --parallel tag1, tag2 to execute all tests with either one of them ?)

but before or after everything else ?

It is after everything else. Because it's an option to the run tag.
gauge run specs                   // serial
gauge run specs --parallel        // will run everything in parallel
gauge run specs --parallel "tags" // only specific tags in parallel after running everything else in serial

Also, are there cases, where the parallel tests shall run before the serial ones ?

Yes there might be cases. I think it's best to come up with an optional flag for run which can also specify the default order of execution. For e.g.

Also, can I run multiple tags in parallel (like --parallel tag1, tag2 to execute all tests with either one of them ?)

Yes, you can. --parallel "tag1, tag2" will run scenarios tagged with tag1 and tag2 in parallel

There are few tech issues with  @zabil's proposal for providing options to --parallel
Issues
Since --parallel is a boolean flag it won't be possible to give string options to it. Making it a string flag will also not work the scenario when we want to execute all the specs in parallel, cause string flags can't be used without a value.
Solution
Let the --parallel flag be as it is (boolean).
Add another string flag --filter (it can be changed to a better name) which takes tag values
So this
gauge run specs                   // serial
gauge run specs --parallel        // will run everything in parallel
gauge run specs --parallel "tags" // only specific tags in parallel after running everything else in serial

can be something like
gauge run specs                   // serial
gauge run specs --parallel        // will run everything in parallel
gauge run specs --parallel --filter "tags" // only specific tags in parallel after running everything else in serial

If the filter option is used without parallel flag give an error saying
Invalid Command. flag --filter can be used only with --parallel

Just a question regarding your solution @BugDiver if I understand it well.
Lets say I have many specs tagged "in-progress". So I make a run, for example: gauge run specs --parallel --filter "!in-progress & !serial". So basically after everything runs in parallel, "in-progress" and "serial" tags will run in serial but I would like to exclude at all those who are "in-progress".
Is there anyway to exclude those with this solution proposed?
Thanks!

@jonathangiber you should still be able to use the --tags flag to exclude the specs from serial and parallel runs.

@jonathangiber @j-morsum @dudicp @fadc80 We have come up with one approach for this feature as a first cut.
We are thinking of creating a new instance of the language runner for the specs that need to be run in serial. The specs that need to be run in parallel is run is a separate instance of language runner after the serial execution finishes.
Pros :

Simpler and easier solution to implement.
Easier to separate the serial and parallel runs.

Cons :

Multi-threaded parallel execution will not work well. The specs run in serial will run in a completely different instance than that of the parallel runner. State and context will not be shared across the specs run in serial and parallel.
Performance may be affected in some language runners, as we are starting runners at two points.

Please let us know if any of these pros or cons will not work well for your usecase. We are trying to understand what works well for you as a first cut for this feature and implement that first.

The flag name --filter could be quite confusing sometime. We are thinking to change it to --only since it feels more aligned with the use case.
Examples:

gauge run specs --parallel --only "tag1 & tag2"
gauge run specs --tags "ready" --parallel --only "parallelizable"

@jonathangiber @j-morsum @dudicp @fadc80  What do you folks thinh?

@jonathangiber @j-morsum @dudicp @fadc80 This feature is available with Gauge nightly. Can you please use it and let us know if this works for your projects.
Refer this to install Gauge nightly. You may have to uninstall your current version of Gauge before installing the nightly.

Amazing, many thanks! Going to try it today

Working as expected, many thanks

Able to define the test which we want to run specifically in parallel by using "--parallel" tags and other will run in serial.
This enhancements has been verified with the below versions:
version: 1.0.5.nightly-2019-04-04.

Hi everyone,
I've a maven gauge project. My spec include 2 different scripts. First one is, Admin is creating meeting. Second one, Members vote agenda item(s) at the same time. So, I want to run first script. Then second scripts for 10 different users at the same time.
So, How can I do it with this solution. I'didn't do it.

@sriv @nehashri Hi, I am using mvn gauge:execute command and wanna run tag: dataprepation beforeSuite. How can i use this feature with mvn gauge command? I already set env  as allow_filtered_parallel_execution=true. Please help on this.

@sriv @nehashri Any help?

@Vishnu1067 - so this feature lets you choose which specs can be run in parallel, and thereby lets you choose specs that need to be run in serial.
Something like this:
mvn test-compile gauge:execute -DinParallel=true -Dflags="--only=parallel"

will execute specs without parallel tag first and then execute specs with parallel tag in parallel.
So in your usecase, I guess you need to flip your tag definition, i.e. you need to whitelist specs that need to be parallelized.
PS - gauge-maven plugin does not support the --only flag yet, so you need to use the fallback flags property.

authors: BugDiver Debashis9012 Vishnu1067 ajoecker dudicp iskoc9002 j-morsum jonathangiber nehashri sriv zabil


text:
Possibility to save data in AWS S3

Hello, I would like to know if you can implement the possibility of saving the data on a cloud server like AWS S3. This would be very useful if the tape is served by another host, but the user wants to save the attachments as images and files more safely and available.

A detailed tutorial for using Grav with AWS was posted on the blog.

Yes, however We assume that the user does not want to host the application in aws, but only the files. I'm going to make an application fork and try to implement this solution

You are welcome to try this, but I know it will be VERY slow.  Grav is file based so it makes extensive use of file methods to see if files are modified, get contents, write contents etc.  A remote file system like S3 is going to be a huge performance problem. Local SSD drives are the best option and these are a marked improvement even over standard local HDD spinning drives.

Hello,
thanks for this awesome CMS :)
I was looking for something similar.
@rhukster is fully correct about performance, however it is about updating or creating contents being slow. Assets (css/js/images) delivery will be much faster with S3 and cloudfront in the front. For the actual HTML, I as said, it does make sense due to the very nature of grav.
Would something to store assets on S3 (or other) be something grav will be interested in?

authors: OleVik lauroguedes pierrejoye rhukster

repo: getgrav/grav


text:
[change-resource] Take over Plugin/Theme

I would like to take over an existing plugin/theme. The project is marked as abandoned and I have emailed the maintainer who has stated the same.
Here are the project details:

Original project https://github.com/Perlkonig/grav-plugin-table-importer
My new project: https://github.com/jwrobb/grav-plugin-table-importer

hi @jwrobb please make sure you have a 'release' first.  Nothing will show up in GPM without a current release in your repository: https://learn.getgrav.org/17/advanced/grav-development#theme-plugin-release-process
cheers,

Apologies on the churn, I should have had the release together when I submitted the take over request. I've made the updates and put out a new release.
https://github.com/jwrobb/grav-plugin-table-importer/releases/tag/v2.3.0

authors: jwrobb rhukster


text:
Home page is looping when custom_base_url is set

When custom_base_url is set everything works except for home page. If I go to https://my.example.com/custombaseurl it would get redirected to https://my.example.com/ and then it will loop again and again. This doesn't happen if I go to https://my.example.com/custombaseurl/home
Home page configuration is default:
home:
  alias: /home
  hide_in_urls: false

UPDATE: this is somehow related or maybe the same issue as in https://github.com/getgrav/grav/issues/3822 because if I disable redirect_trailing_slash home page works without issues.


text:
need a few basic pages

Need an about page, a privacy policy page, maybe a couple of others.

Hi Kyle, would like to work on this.

I can help as well

Taking some of the wording from the README here, as well as what I said on linked-in, that would be the best starting page for text for a Privacy page and/or About page. So we just need to start drafting that text, and lay it out in basic HTML.

Shall I start building the privacy policy page?

Taking some of the wording from the README here, as well as what I said on linked-in, that would be the best starting page for text for a Privacy page and/or About page. So we just need to start drafting that text, and lay it out in basic HTML.

Sounds good as starting point.

yes! let's coordinate here in issues to minimize how much duplicative work might be done.

So maybe we should work on agreeing on the text for these pages HERE, before actually building it out in HTML. Probably easier to debate/tweak/improve wording in discussion thread rather than as PRs on top of PRs.

I agree . A contribution guideline may also be needed

Done

@kirankok and @AbednegoTM I would like to join if you need an helping hand

Hey guys @kirankok, @AbednegoTM and @getify! I would like to help as well. Please, let know if there is any page or issue I could help. Thank you!!

This is draft based on linkedIn Post and about page
About  - DRAFT
A privacy-first period tracking app.
We could almost all agree that it's never been more important for us to OWN OUR INFORMATION, not governments or "big tech" companies, so that we decide what is done with that information.
I think that especially goes for private medical/health data, of which menstrual tracking (for women / people with uteruses) might just be some of the most sensitive and important to protect.
Companies and apps can promise all they want that they're being safe and private with our information. But if they have our information, and they're a company, they're going to have to make money somehow, either by charging us for it, or worse, charging someone else to use it in some way.
We believe this kind of private and sensitive medical information belongs to you, and you alone. As such, YOU. (the app) puts you in control of all your information, and never collects or tracks anything about you, not even your name or email address. Since we don't have any of your data, we obviously CANNOT sell it or hand it over to any governmental authority.
Everything you enter into YOU. (the app) is yours, always and only yours. It stays on your device, protected and secure, and you decide what to do with that information.
This app is free to use, and will remain so forever.
Once installed, this web-app (PWA) runs entirely offline -- only locally on your device, with no need for any internet or to connect to any remote service -- and uses strong cryptography practices to keep your data secure and private on your device, ONLY.
It's built with love and respect, for you, and only about you, and only to help you keep and track your own private health information. That's it. Period.

I am not so strong in writing copy content.  @5hraddha and @gkhedekar5758 I believe this is were you come in Once we done  working on copy I will write the markup. How is that ?
@getify I think the draft above is good starting point for ABOUT page copy.

Hi Guys!
Here is the initial draft for Privacy Policy Page, based on the LinkedIn Post and Read Me.
"We believe menstrual tracking (for women/people with uteruses) data might be some of the most sensitive and important data to protect as it belongs to you, and you alone. You. (the app) is committed to putting you in control of all your information, and thus, never collects or tracks anything about you, not even your name or email address. Since we don't have any of your data, we obviously CAN NOT sell it or hand it over to any governmental authority.
Everything you enter into You. (the app) is yours, and always and only yours. It stays on your device, protected and secure, and you decide what to do with that information."
@getify @AbednegoTM We could discuss the above initial draft for Privacy Policy Page. Once finalized, I could take it up to write the initial markup for this page via a separate PR. Thank you!!

@AbednegoTM I am also not in content wrting or copy writing, I am a developer so let me know if you need any help where a programmer can help. I am in for any help regarding HTML and JS for any page

I am also present! I can contribute for Home, About pages as well.

I can also help with the about page. The draft content is already posted up there.

Hi Guys!
Here is the initial draft for Privacy Policy Page, based on the LinkedIn Post and Read Me.
"We believe menstrual tracking (for women/people with uteruses) data might be some of the most sensitive and important data to protect as it belongs to you, and you alone. You. (the app) is committed to putting you in control of all your information, and thus, never collects or tracks anything about you, not even your name or email address. Since we don't have any of your data, we obviously CAN NOT sell it or hand it over to any governmental authority.
Everything you enter into You. (the app) is yours, and always and only yours. It stays on your device, protected and secure, and you decide what to do with that information."
@getify @AbednegoTM We could discuss the above initial draft for Privacy Policy Page. Once finalized, I could take it up to write the initial markup for this page via a separate PR. Thank you!!

Looks good , you can use this format . I noticed some parts of the server may use strategies that make use of personal information to protect the same information , that means some sections I have listed below may need to be filled. some May just need a few words like  WE DO NOT COLLECT / TRACK. Just a suggestion open to discussions.
Privacy Policy
Welcome to  YOU .
This policy is effective as of [date].
Information We Collect
Log Data
When You visit the Site, Our servers may automatically log the standard data provided by Your web browser. It may include Your device’s Internet Protocol (IP) address, Your browser type and version, the pages You visit, the time and date of Your visit.
Additionally, if You encounter certain errors while using the Site, We may automatically collect data about the error and the circumstances surrounding its occurrence. This data may include technical details about Your device, what You were trying to do when the error happened, and other technical information relating to the problem. You may or may not receive notice of such errors, even in the moment they occur, that they have occurred, or what the nature of the error is.
Please be aware that while this information may not be personally identifying by itself.
Personal Information
Legitimate Reasons for Processing Your Personal Information
Collection and Use of Information
We may collect personal information from You when You do any of the following on the Site:
Sign up
Use a mobile device or web browser to access Our content
Contact Us via email, social media, or on any similar technologies
When You mention Us on social media
Security of Your Personal Information
When We collect and process personal information, and while We retain this information, We will protect it within commercially acceptable means to prevent loss and theft, as well as unauthorized access, disclosure, copying, use, or modification.
How Long We Keep Your Personal Information
To be filled
Children’s Privacy
To be filled
Disclosure of Personal Information to Third Parties
To be filled
Google Analytics
To be filled
Controlling Your Personal Information
To be filled
Use of Cookies
To be filled
Changes to This Policy
If We decide to change this privacy policy, We will post the changes here at the same link by which You are accessing this privacy policy.
To be filled
Consent From You
Where You give Us consent to collect and use Your personal information for a specific purpose.
To be filled
Our Legitimate Interests
To be filled
Compliance with Law
To be filled
Contact us
To be filled

I can work on a hamburger menu (css) and have the pages wired up
About
Privacy
Registration
Login
Dashboard (once logged in)
then we can wire up html behind this menus the actual pages and write up at least for About and Privacy page. Let me know what you all think

I can work on a hamburger menu (css) and have the pages wired up
About Privacy Registration Login Dashboard (once logged in)
then we can wire up html behind this menus the actual pages and write up at least for About and Privacy page. Let me know what you all think

How about this menu? uploading pictures . we can start with "about us"  and "privacy" page HTML and wire them up behind this. uploading some screenshot. The menu comes up from the top of the screen in transition
let me know how it looks @getify @AbednegoTM @5hraddha @kirankok . Always open to suggestion

I have two suggestions:

As someone who has lots of family in medicine, I think we need a clear indication of HIPAA policies (and similar for non-US based users, but starting with HIPAA).
Related to the educational section about menstruation: As a menstruator, I can confidently tell you that something we're never told is hour various contraceptives interact with our periods. I feel that is extremely important.

Happy to help writing the content for both!

anywhere i can jump in on this or is this issue completely covered? also is there something like a kanban/trello board?

Okk

@eireann07 thanks for the suggestions. I especially like the idea of good educational text, or at least links pointing users to good sources.
Regarding HIPPA:

I recently learned that HIPPA strangely and disturbingly does not apply to things like period trackers, personal fitbits/health trackers, etc. Since the law doesn't cover any of the kinds of data this app collects, I don't think we need to concern ourselves with either compliance or even statement of its status. Doing so might actually mislead or confuse our users.

Since this app never sends any data anywhere besides your device, I think the concept of HIPPA laws (in any jurisdiction) wouldn't even apply. Our privacy policy will state we don't ever see your data, and further that we take steps to keep the data on your device encypted and protected. While there's no legal aspect to such a statement, I think that stance (and the auditability of the code to prove it) is far stronger than the protections any law could ever give users.

BTW, I feel similarly about GDPR type laws. There's no data processors, and since you control your data, you can delete the only copy/copies of it any time you want.

@jsonjunkie (and everyone else)...
the project is still early self organizing. Not yet any official work assignments or project roadmaps or anything like that.
The issues list, and GH discussions list, is currently the source of truth for what work we're discussing, and what tasks we're tackling.
If younsee something you think needs to be done, and want to do it, please just do so. There's no official permission or authority control in place yet.
I have appointed @pselle to begin formalizing some of the organizing processes, so more will solidify in that respect in the coming days/weeks. But... this is open source, not a company. We mostly will self-organize and evolve as we go.
So expect a certain level of informality to continue, and please exercise good judgment and cooperation to communicate/coordinate with others to share the task load.

Hi all! I'm closing this issue and creating more specific issues so they can be picked up more easily. Please see issues linked to this one for contributing!


text:
Example configuration with custom template

Is your feature request related to a problem? Please describe.
I'm a Node-amateur and find the interplay of CommonJS and ES modules terribly confusing.
Describe the solution you’d like
Show me an example config that includes a custom post template, or "local" preset, using v1.0.0
Describe alternatives you’ve considered
I've tried every permutation of ES and CJS I can think of, have searched GitHub for useful examples in the wild.

👋

I'm a Node-amateur and find the interplay of CommonJS and ES modules terribly confusing.

Been there! Was far worse back in the day when there was no standard… AMD, UMD, CJS… put me off learning JavaScript for many, many years.
Nowadays it’s a little more straight forward. ES modules, as the name implies, are the standard and thus the syntax that’ll stick around. Indiekit kit uses ES modules throughout.

Show me an example config that includes a custom post template, or "local" preset, using v1.0.0

Interesting. There’s the example-config repo, but that’s for v0.x.x branch. Given the impending release of v1.x.x, and that the website documents the new configuration format, this repo is likely causing more confusion, than helping anybody.
I was considering removing/archiving it, but what you outline is a good case for keeping it around, with it showing an example of a server configured with a custom preset. I’ll look to update the example with this use case in mind.

I've tried every permutation of ES and CJS I can think of, have searched GitHub for useful examples in the wild.

Although Node.js supports ES modules, CommonJS is what it has used historically and remains its default module format. To enable ES modules, you either need to name a file with the extension .mjs, or add "type": "module" to your package.json file. Have you tried this?

Maybe this is a duplicate of #400, really

I have finally updated the example configuration, which should hopefully resolve this issue. #400 is frankly causing epic levels of procrastination at the moment, but closing this issue gets me one step closer to updating and expanding on the getting started guide!

authors: gerwitz paulrobertlloyd

repo: getindiekit/indiekit


text:
[Bug] Error rendering query when GraphQL body includes a comment

Insomnia Version: Version 5.16.0 (5.16.0.2017)
Operating System: OSX 10.13.3 (17D102)

Details
When trying to render the following query (at any or an empty target endpoint) the insomnia client fails:
# query {
#	viewer {
#		serviceConsents {
#			id
#			externalVehicleId
#			externalUserId
#			serviceId
#			vehicleId
#			scope
#			startTime
#			endTime
#		}
#	}
#}

query {
	services {
		id
		name
		scope
	}
}

The error can be seen here: https://i.imgur.com/ENDSB5u.png
But writes:
Render error
> unexpected end of comment

Caused by the following field
> Request.body.text

This is obviously not correct so there appears to be a bug in the query parsing, as the above query, including the comment is compleatly valid, and the linter picks it up perfectly? Perhaps do not try to strip comments to begin with, graphiql doesn't either?

Hmm, this might be tricky to fix. Specifically, it's because of this line: #}. All requests are rendered by Nunjucks before sending (to power environments) and #} signifies the end of a {# nunjucks comment #}.
As a temporary workaround for now, just make sure there's a space between the "#" and the "}"

Hmm fair point, perhaps it would be solved by implementing https://github.com/getinsomnia/insomnia/issues/852 prior to the nunjucks rendering?

Or perhaps not, i think i misunderstood what that issue actually ment, i.e. just on send, render it prettified, rather than an "auto format on send". None the less, i will keep the work around in mind.

authors: NinnOgTonic gschier

repo: getinsomnia/insomnia


text:
Support cap'n'proto

Cap'n'proto is a C++ binary serialization format (https://github.com/capnproto/capnproto) similar to protobuf.
It also includes a format for dynamic reflection:
https://capnproto.org/cxx.html#dynamic-reflection
We can fill this gap by implementing a reflect-cpp interface to cap'n'proto.

seconded!

repo: getml/reflect-cpp


text:
Add custom parameters to HTTPTrasport and setters

It is modify PR #222  with custom HTTPTransport
client parameters.

PR introduces options

// HTTPTransportOptions are options to configure the HTTPTransport
yet it contains 5 separate setters for all the timeouts.

Wouldn't it be better to configure it once during transport creation? It will most likely never change once configured anyway.

@kamilogorek Hi!
It is good idea.
I gonna fix soon time

repo: getsentry/raven-go


text:
Adds Node 8 to CI

Gonna go ahead and make sure this passes CI...

Err, approved once CI passes, that is.

authors: LewisJEllis benvinegar

repo: getsentry/raven-node


text:
captureUnhandledRejections - add flag for unhandled promise rejections

related https://github.com/getsentry/raven-js/pull/1278

Fixed myself and merged it to master manually

authors: kamilogorek kumavis


text:
Filtered events logged at error level

{
    "asctime": "2018-05-17 11:58:33,097",
    "created": 1526572713.097566,
    "levelname": "ERROR",
    "levelno": 40,
    "filename": "base.py",
    "funcName": "_failed_send",
    "lineno": 679,
    "module": "base",
    "message": "Sentry responded with an API error: APIError(Event dropped due to filter: web-crawlers)",
    "name": "sentry.errors",
    "pathname": "/srv/proj/local/lib/python2.7/site-packages/raven/base.py",
    "process": 11799,
    "processName": "MainProcess"
}

I have my application configured to capture all error logs and this one tends to be particularly noisy. Filtering events seems like standard operation and could be logged at INFO instead of ERROR which it doesn't appear to be.

@ashwoods any news on this? I'm still not sure whether this should be fixed in raven or sentry itself (see getsentry/sentry#8763 ) but I would really like to see this fixed.

authors: SimonPe ipmb

repo: getsentry/raven-python


text:
Fix Twisted UDP transport

Currently TwistedUDPTransport is broken.

Should raven support UDP or is it deprecated?

Sorry, the UDP support is going to be dropped. Should make it clear in the documentations.

Ok, in this case please delete TwistedUDPTransport in next release.
Because it is not work.  Actually it never was in working state.

authors: anjensan asvetlov xordoquy


text:
Revert to check & fail only approach for format & analyze

#skip-changelog
:scroll: Description

Revert to the previous approach, where we run format and analyze. If CI fails, users need to resolve the errors and push changes.
:bulb: Motivation and Context

Applying changes to a fresh PR only seems to work with a PAT, which we don't want to use.
The current approach will fix formatting and other issues (dart fix), but would fail to commit those changes.
This leads to successful CI runs with formatting & other issues.

Closes #1456
:pencil: Checklist

[x] I reviewed submitted code
[ ] I added tests to verify changes
[ ] No new PII added or SDK only sends newly added PII if sendDefaultPii is enabled
[ ] I updated the docs if needed
[ ] All tests passing
[x] No breaking changes

@denrase not sure I understand the reason to revert back.
The issue https://github.com/getsentry/sentry-dart/issues/1456 is about skipping the commit script, this has to be fixed.
The script has to run the commands and commit the changed files.
We can run rerun the CI manually if needed.

@philipphofmann Hey! I think you implemented the workflow to format code on iOS. I took your script from there, but i'm always getting an error when trying to use $GITHUB_HEAD_REF, think it's just null, even though we are on a PR. Any idea what might be the issue?

authors: denrase marandaneto

repo: getsentry/sentry-dart


text:
Feat: SentryHttpClient tracks request durations

:scroll: Description
SentryHttpClient now tracks the duration of a request. It also logs failed requests and their durations.
:bulb: Motivation and Context
https://github.com/getsentry/sentry-dart/issues/412
:green_heart: How did you test it?
:pencil: Checklist

[x] I reviewed submitted code
[x] I added tests to verify changes
[x] I updated the docs if needed
[x] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

Codecov Report

Merging #414 (f71767c) into main (c1784cd) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #414      +/-   ##
==========================================
+ Coverage   90.74%   90.78%   +0.03%
==========================================
  Files          52       52
  Lines        1654     1660       +6
==========================================
+ Hits         1501     1507       +6
  Misses        153      153

Impacted Files
Coverage Δ

dart/lib/src/http_client/sentry_http_client.dart
90.00% <100.00%> (+4.28%)
:arrow_up:

Continue to review full report at Codecov.

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

Issue with duration for reference: https://sentry.io/share/issue/2a6d6dd55b5e47c087c576bd2c538413/

authors: codecov-commenter ueman