commerce:store:create fails with ERROR running StoreQuickstartSetup:

Creating a new store, this may take up to 10 minutes until it's available.
Store name: testStore
Org username<EMAIL_ADDRESS>Use this command to just create a community.  It will use sfdx force:community:create until a community is created or failed.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Creating Community...... Done
{
"message": "",
"status": 0,
"result": {
"message": "Your Site is being created.",
"name": "testStore",
"action": "We’re creating your site. Run sfdx force:org:open -p _ui/networks/setup/SetupNetworksPage to view a list of your sites, and to confirm when this site is ready."
},
"command": "sfdx force:community:create -u<EMAIL_ADDRESS>--name "testStore" --templatename "b2c-lite-storefront" --urlpathprefix "testStore" --description "Store testStore created by Quick Start script." --json --apiversion=57.0",
"urlpathprefix": "testStore"
}
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Creating a new store, this may take up to 10 minutes until it's available.
Store name: testStore
Org username<EMAIL_ADDRESS>Use this command to just create a community.  It will use sfdx force:community:create until a community is created or failed.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Creating Community...... Done
{
"message": "",
"status": 0,
"result": {
"message": "Your Site is being created.",
"name": "testStore",
"action": "We’re creating your site. Run sfdx force:org:open -p _ui/networks/setup/SetupNetworksPage to view a list of your sites, and to confirm when this site is ready."
},
"command": "sfdx force:community:create -u<EMAIL_ADDRESS>--name "testStore" --templatename "b2c-lite-storefront" --urlpathprefix "testStore" --description "Store testStore created by Quick Start script." --json --apiversion=57.0",
"urlpathprefix": "testStore"
}
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Creating a new store, this may take up to 10 minutes until it's available.
Store name: testStore
Org username<EMAIL_ADDRESS>Use this command to just create a community.  It will use sfdx force:community:create until a community is created or failed.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Creating Community...... Done
{
"message": "",
"status": 0,
"result": {
"message": "Your Site is being created.",
"name": "testStore",
"action": "We’re creating your site. Run sfdx force:org:open -p _ui/networks/setup/SetupNetworksPage to view a list of your sites, and to confirm when this site is ready."
},
"command": "sfdx force:community:create -u<EMAIL_ADDRESS>--name "testStore" --templatename "b2c-lite-storefront" --urlpathprefix "testStore" --description "Store testStore created by Quick Start script." --json --apiversion=57.0",
"urlpathprefix": "testStore"
}
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Creating a new store, this may take up to 10 minutes until it's available.
Store name: testStore
Org username<EMAIL_ADDRESS>Use this command to just create a community.  It will use sfdx force:community:create until a community is created or failed.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Creating Community...... Done
{
"message": "",
"status": 0,
"result": {
"message": "Your Site is being created.",
"name": "testStore",
"action": "We’re creating your site. Run sfdx force:org:open -p _ui/networks/setup/SetupNetworksPage to view a list of your sites, and to confirm when this site is ready."
},
"command": "sfdx force:community:create -u<EMAIL_ADDRESS>--name "testStore" --templatename "b2c-lite-storefront" --urlpathprefix "testStore" --description "Store testStore created by Quick Start script." --json --apiversion=57.0",
"urlpathprefix": "testStore"
}
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Waiting for community to become available... done with storeid:  0ZE01000000GqiqGAC
Completed Step 6
Community is now available
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Converting 3 metadata components... done
STATE FULL NAME                     TYPE            PROJECT PATH
───── ───────────────────────────── ─────────────── ───────────────────────────────────────────────────────────────────────────
Add   SalesforceAdapter             ApexClass       force-app/main/default/classes/SalesforceAdapter.cls-meta.xml
Add   SalesforceAdapter             ApexClass       force-app/main/default/classes/SalesforceAdapter.cls
Add   SalesforceValidationException ApexClass       force-app/main/default/classes/SalesforceValidationException.cls-meta.xml
Add   SalesforceValidationException ApexClass       force-app/main/default/classes/SalesforceValidationException.cls
Add   Salesforce                    NamedCredential force-app/main/default/namedCredentials/Salesforce.namedCredential-meta.xml
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Converting 17 metadata components... done
STATE FULL NAME                     TYPE              PROJECT PATH
───── ───────────────────────────── ───────────────── ───────────────────────────────────────────────────────────────────────────────────────────
Add   B2CCheckInventorySample       ApexClass         force-app/main/default/classes/B2CCheckInventorySample.cls-meta.xml
Add   B2CCheckInventorySample       ApexClass         force-app/main/default/classes/B2CCheckInventorySample.cls
Add   B2CCheckInventorySampleTest   ApexClass         force-app/main/default/classes/B2CCheckInventorySampleTest.cls-meta.xml
Add   B2CCheckInventorySampleTest   ApexClass         force-app/main/default/classes/B2CCheckInventorySampleTest.cls
Add   B2CDeliverySample             ApexClass         force-app/main/default/classes/B2CDeliverySample.cls-meta.xml
Add   B2CDeliverySample             ApexClass         force-app/main/default/classes/B2CDeliverySample.cls
Add   B2CDeliverySampleTest         ApexClass         force-app/main/default/classes/B2CDeliverySampleTest.cls-meta.xml
Add   B2CDeliverySampleTest         ApexClass         force-app/main/default/classes/B2CDeliverySampleTest.cls
Add   B2CPricingSample              ApexClass         force-app/main/default/classes/B2CPricingSample.cls-meta.xml
Add   B2CPricingSample              ApexClass         force-app/main/default/classes/B2CPricingSample.cls
Add   B2CPricingSampleTest          ApexClass         force-app/main/default/classes/B2CPricingSampleTest.cls-meta.xml
Add   B2CPricingSampleTest          ApexClass         force-app/main/default/classes/B2CPricingSampleTest.cls
Add   B2CTaxSample                  ApexClass         force-app/main/default/classes/B2CTaxSample.cls-meta.xml
Add   B2CTaxSample                  ApexClass         force-app/main/default/classes/B2CTaxSample.cls
Add   B2CTaxSampleTest              ApexClass         force-app/main/default/classes/B2CTaxSampleTest.cls-meta.xml
Add   B2CTaxSampleTest              ApexClass         force-app/main/default/classes/B2CTaxSampleTest.cls
Add   Heroku_test_for_B2B_lightning RemoteSiteSetting force-app/main/default/remoteSiteSettings/Heroku_test_for_B2B_lightning.remoteSite-meta.xml
Add   GetDeliveryRatesResource      StaticResource    force-app/main/default/staticresources/GetDeliveryRatesResource.resource-meta.xml
Add   GetDeliveryRatesResource      StaticResource    force-app/main/default/staticresources/GetDeliveryRatesResource.bin
Add   GetInventoryResource          StaticResource    force-app/main/default/staticresources/GetInventoryResource.resource-meta.xml
Add   GetInventoryResource          StaticResource    force-app/main/default/staticresources/GetInventoryResource.bin
Add   GetSalesPricesResource        StaticResource    force-app/main/default/staticresources/GetSalesPricesResource.resource-meta.xml
Add   GetSalesPricesResource        StaticResource    force-app/main/default/staticresources/GetSalesPricesResource.bin
Add   GetTaxesResource              StaticResource    force-app/main/default/staticresources/GetTaxesResource.resource-meta.xml
Add   GetTaxesResource              StaticResource    force-app/main/default/staticresources/GetTaxesResource.bin
Add   de                            Translations      force-app/main/default/translations/de.translation-meta.xml
Add   en_US                         Translations      force-app/main/default/translations/en_US.translation-meta.xml
Add   ja                            Translations      force-app/main/default/translations/ja.translation-meta.xml
Add   CustomLabels                  CustomLabels      force-app/main/default/labels/CustomLabels.labels-meta.xml
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Converting 4 metadata components... done
STATE FULL NAME                                        TYPE          PROJECT PATH
───── ──────────────────────────────────────────────── ───────────── ───────────────────────────────────────────────────────────────────────────────────────────
Add   unfiled$public/B2B2C_Order_Confirmation_Email    EmailTemplate force-app/main/default/email/unfiled$public/B2B2C_Order_Confirmation_Email.email-meta.xml
Add   unfiled$public/B2B2C_Order_Confirmation_Email    EmailTemplate force-app/main/default/email/unfiled$public/B2B2C_Order_Confirmation_Email.email
Add   B2B2C_Order_Confirmation_Email_Notification_Flow Flow          force-app/main/default/flows/B2B2C_Order_Confirmation_Email_Notification_Flow.flow-meta.xml
Add   OrderSummary.OCE_Account_First_Name__c           CustomField   force-app/main/default/objects/OrderSummary/fields/OCE_Account_First_Name__c.field-meta.xml
Add   OrderSummary.OCE_Account_Last_Name__c            CustomField   force-app/main/default/objects/OrderSummary/fields/OCE_Account_Last_Name__c.field-meta.xml
Add   OrderSummary.OCE_Order_Items__c                  CustomField   force-app/main/default/objects/OrderSummary/fields/OCE_Order_Items__c.field-meta.xml
Add   OrderSummary.OCE_Order_Total__c                  CustomField   force-app/main/default/objects/OrderSummary/fields/OCE_Order_Total__c.field-meta.xml
Add   OrderSummary.OCE_Payment_Method__c               CustomField   force-app/main/default/objects/OrderSummary/fields/OCE_Payment_Method__c.field-meta.xml
Add   OrderSummary.OCE_Shipping_Address__c             CustomField   force-app/main/default/objects/OrderSummary/fields/OCE_Shipping_Address__c.field-meta.xml
Add   OrderSummary.OCE_Shipping_Method__c              CustomField   force-app/main/default/objects/OrderSummary/fields/OCE_Shipping_Method__c.field-meta.xml
Add   OrderSummary                                     Workflow      force-app/main/default/workflows/OrderSummary.workflow-meta.xml
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Converting 1 metadata components... done
STATE FULL NAME                          TYPE    PROJECT PATH
───── ────────────────────────────────── ─────── ───────────────────────────────────────────────────────────────────────────────────
Add   Buyer_User_Profile_From_QuickStart Profile force-app/main/default/profiles/Buyer_User_Profile_From_QuickStart.profile-meta.xml
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Converting 3 metadata components... done
STATE FULL NAME            TYPE         PROJECT PATH
───── ──────────────────── ──────────── ────────────────────────────────────────────────────────────────────────────────────────
Add   ElectronicMediaGroup CustomObject force-app/main/default/objects/ElectronicMediaGroup/ElectronicMediaGroup.object-meta.xml
Add   ElectronicMediaGroup CustomObject force-app/main/default/objects/ElectronicMediaGroup
Add   OrderDeliveryMethod  CustomObject force-app/main/default/objects/OrderDeliveryMethod/OrderDeliveryMethod.object-meta.xml
Add   OrderDeliveryMethod  CustomObject force-app/main/default/objects/OrderDeliveryMethod
Add   ProductCatalog       CustomObject force-app/main/default/objects/ProductCatalog/ProductCatalog.object-meta.xml
Add   ProductCatalog       CustomObject force-app/main/default/objects/ProductCatalog
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Converting 5 metadata components... done
STATE FULL NAME                                                                  TYPE         PROJECT PATH
───── ────────────────────────────────────────────────────────────────────────── ──────────── ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Add   Process_CommerceDiagnosticEvents                                           Flow         force-app/main/default/flows/Process_CommerceDiagnosticEvents.flow-meta.xml
Add   CommerceDiagnosticCustomObject__c-Commerce Diagnostic Custom Object Layout Layout       force-app/main/default/layouts/CommerceDiagnosticCustomObject__c-Commerce Diagnostic Custom Object Layout.layout-meta.xml
Add   CommerceDiagnosticCustomObject__c.Context_Id_2__c                          CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Context_Id_2__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Context_Id__c                            CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Context_Id__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Context_Map__c                           CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Context_Map__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Correlation_Id__c                        CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Correlation_Id__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Count__c                                 CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Count__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Effective_Account_Id__c                  CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Effective_Account_Id__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Error_Code__c                            CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Error_Code__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Error_Message__c                         CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Error_Message__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Event_Created_By__c                      CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Event_Created_By__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Event_Created_Date__c                    CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Event_Created_Date__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Is_Retry__c                              CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Is_Retry__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Operation_Stage__c                       CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Operation_Stage__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Operation_State__c                       CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Operation_State__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Operation_Status__c                      CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Operation_Status__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Operation_Time__c                        CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Operation_Time__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Operation__c                             CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Operation__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.Service_Name__c                          CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/Service_Name__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.User__c                                  CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/User__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.WebStore_Id__c                           CustomField  force-app/main/default/objects/CommerceDiagnosticCustomObject__c/fields/WebStore_Id__c.field-meta.xml
Add   CommerceDiagnosticCustomObject__c.CommerceDiagnosticEventFields            ListView     force-app/main/default/objects/CommerceDiagnosticCustomObject__c/listViews/CommerceDiagnosticEventFields.listView-meta.xml
Add   CommerceDiagnosticCustomObject__c                                          CustomObject force-app/main/default/objects/CommerceDiagnosticCustomObject__c/CommerceDiagnosticCustomObject__c.object-meta.xml
Add   CommerceDiagnosticCustomObject__c                                          CustomObject force-app/main/default/objects/CommerceDiagnosticCustomObject__c
Add   Admin                                                                      Profile      force-app/main/default/profiles/Admin.profile-meta.xml
Add   CommerceDiagnosticCustomObject__c                                          CustomTab    force-app/main/default/tabs/CommerceDiagnosticCustomObject__c.tab-meta.xml
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Converting 1 metadata components... done
STATE FULL NAME TYPE           PROJECT PATH
───── ───────── ────────────── ────────────────────────────────────────────────────────────────────────
Add   amazonaws CspTrustedSite force-app/main/default/cspTrustedSites/amazonaws.cspTrustedSite-meta.xml
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
WARNING: This operation will modify all your local source tracking files. The operation can have unintended consequences on all the force:source commands. Are you sure you want to proceed (y/n)?:  ›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Pushing store sources...... done
Setting up the store and creating the buyer user...
Buyer username<EMAIL_ADDRESS>Buyer email<EMAIL_ADDRESS>Buyer alias: buyer
Checking if B2B or B2C.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Store Type = "B2C"
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Using this to retrieve your store info:

testStore
CustomSite

testStore1
ExperienceBundle

testStore
Network

*
NavigationMenu

57.0

Retrieving the store metadata and extracting it from the zip file.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Retrieve ID: 09S01000005H0dnEAC
Retrieving metadata from<EMAIL_ADDRESS>done
Wrote retrieve zip to /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged.zip
Archive:  /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged.zip
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/sites/testStore.site
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/addressForm.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/addressForm.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/addressList.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/addressList.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/themes/b2CCommerce.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/brandingSets/b2CCommerce.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/cart.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/cart.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/category.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/category.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/checkPassword.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/checkPassword.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/checkout.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/checkout.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/error.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/error.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/forgotPassword.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/forgotPassword.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/home.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/home.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/config/languages.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/login.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/login.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/config/mainAppPage.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/myProfile.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/myProfile.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/order.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/order.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/orderSummaryDetails.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/orderSummaryDetails.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/orderSummaryList.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/orderSummaryList.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/product.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/product.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/register.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/register.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/search.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/search.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/serviceNotAvailable.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/serviceNotAvailable.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/config/testStore.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/views/tooManyRequests.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1/routes/tooManyRequests.json
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/experiences/testStore1.site-meta.xml
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/networks/testStore.network
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/navigationMenus/Default_My_Account_Menu.navigationMenu
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/navigationMenus/Default_User_Profile_Menu.navigationMenu
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/navigationMenus/SFDC_Default_Navigation_testStore.navigationMenu
inflating: /Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/unpackaged/package.xml
Completed Quickstart Step 1
Setting up your integrations
Registering and mapping integrations
Registering Apex class B2CCheckInventorySample (CHECK_INVENTORY_B2C) for Inventory integration.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Registering Apex class B2CDeliverySample (COMPUTE_SHIPPING_B2C) for Shipment integration.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Registering Apex class B2CTaxSample (COMPUTE_TAXES_B2C) for Tax integration.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Done registering and mapping integrations
Registering and mapping pricing integrations
Registering internal pricing (Price__B2B_STOREFRONT__StandardPricing) for Price integration.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
To register an external pricing integration, delete the internal pricing mapping and then add the external pricing mapping.  See the code for details how.
Done Registering and mapping pricing integrations
Registering credit card payment integration.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Creating PaymentGatewayProvider record using ApexAdapterId=01p01000002FmGBAA0.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Creating PaymentGateway record using MerchantCredentialId=0XA01000000L06aGAC, PaymentGatewayProviderId=0cJ01000000Kyk9EAC.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Creating StoreIntegratedService using the testStore store and Integration=0b001000000KykbAAC (PaymentGatewayId)
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
You can view the results of the mapping in the Store Integrations page at /lightning/page/storeDetail?lightning__webStoreId=0ZE01000000GqiqGAC&storeDetail__selectedTab=store_integrations
Completed Quickstart Step 2
Updating members list, activating community and adding guest user.
Completed Quickstart Step 3
Importing products.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Starting import for WebStore ID: 0ZE01000000GqiqGAC to https://computing-force-7699-dev-ed.scratch.my.salesforce.com/services/data/v57.0/commerce/management/webstores/0ZE01000000GqiqGAC/product-import
Importing products.... Done importing products, got results:
{"message":"","status":0,"result":{"attributes":{"type":"ContentVersion","url":"/services/data/v57.0/sobjects/ContentVersion/06801000000ZeL0AAK"},"Id":"06801000000ZeL0AAK","ContentDocumentId":"06901000000ZeIjAAK"},"command":"sfdx shane:data:file:upload -f /Users/peter.knolle/.commerce/examples/csv/Alpine-small.csv -u<EMAIL_ADDRESS>--json --apiversion=57.0"}
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Mapping Admin User to Role.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
User role 'CEO' already exists
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
{
"status": 0,
"result": {
"id": "00501000003AdXLAA0",
"success": true,
"errors": []
}
}
Completed Quickstart Step 4
Creating Buyer User with associated Contact and Account.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Making Account a Buyer Account
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Assigning Buyer Account to Buyer Group.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Add Contact Point Addresses to the Buyer Account.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Setting up Guest Browsing.
Starting Guest Buyer Access setup!
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Converting 1 metadata components... done
STATE FULL NAME         TYPE    PROJECT PATH
───── ───────────────── ─────── ─────────────────────────────────────────────────────────────────────────────────────
Add   testStore Profile Profile testStore/sourceGuestProfile/main/default/profiles/testStore Profile.profile-meta.xml
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
*** Deploying with SOAP API v57.0 ***
Deploy ID: 0Af0100000jonf9CAA
DEPLOY PROGRESS | ████████████████████████████████████████ | 1/1 Components
=== Deployed Source
FULL NAME         TYPE    PROJECT PATH
───────────────── ─────── ─────────────────────────────────────────────────────────────────────────────────────
testStore Profile Profile testStore/sourceGuestProfile/main/default/profiles/testStore Profile.profile-meta.xml
Deploy Succeeded.
Make Site and Nav Menu Item Public
Enable Guest Browsing for WebStore and create Guest Buyer Profile.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
{
"status": 0,
"result": {
"id": "0ZE01000000GqiqGAC",
"success": true,
"errors": []
}
}
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
Done! Guest Buyer Access is set up!

›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
ERROR running StoreQuickstartSetup:  {
"status": 1,
"result": {
"checkOnly": false,
"completedDate": "2023-03-17T13:30:29.000Z",
"createdBy": "00501000003AdXL",
"createdByName": "User User",
"createdDate": "2023-03-17T13:29:59.000Z",
"details": {
"componentFailures": [
{
"changed": false,
"componentType": "Network",
"created": false,
"createdDate": "2023-03-17T13:30:29.000Z",
"deleted": false,
"fileName": "networks/testStore.network",
"fullName": "testStore",
"problem": "operation is not allowed",
"problemType": "Error",
"success": false
}
],
"componentSuccesses": [
{
"changed": true,
"componentType": "CustomSite",
"created": false,
"createdDate": "2023-03-17T13:30:29.000Z",
"deleted": false,
"fileName": "sites/testStore.site",
"fullName": "testStore",
"id": "0DM01000000KzQeGAK",
"success": true
},
{
"changed": true,
"componentType": "ExperienceBundle",
"created": false,
"createdDate": "2023-03-17T13:30:29.000Z",
"deleted": false,
"fileName": "experiences/testStore1",
"fullName": "testStore1",
"id": "0DM01000000KzQfGAK",
"success": true
},
{
"changed": true,
"componentType": "",
"created": false,
"createdDate": "2023-03-17T13:30:29.000Z",
"deleted": false,
"fileName": "package.xml",
"fullName": "package.xml",
"success": true
},
{
"changed": false,
"componentType": "NavigationMenu",
"created": false,
"createdDate": "2023-03-17T13:30:29.000Z",
"deleted": false,
"fileName": "navigationMenus/Default_User_Profile_Menu.navigationMenu",
"fullName": "Default_User_Profile_Menu",
"id": "0Lm01000000KzPVCA0",
"success": true
},
{
"changed": false,
"componentType": "NavigationMenu",
"created": false,
"createdDate": "2023-03-17T13:30:29.000Z",
"deleted": false,
"fileName": "navigationMenus/SFDC_Default_Navigation_testStore.navigationMenu",
"fullName": "SFDC_Default_Navigation_testStore",
"id": "0Lm01000000KzPUCA0",
"success": true
},
{
"changed": false,
"componentType": "NavigationMenu",
"created": false,
"createdDate": "2023-03-17T13:30:29.000Z",
"deleted": false,
"fileName": "navigationMenus/Default_My_Account_Menu.navigationMenu",
"fullName": "Default_My_Account_Menu",
"id": "0Lm01000000KzPWCA0",
"success": true
}
],
"runTestResult": {
"numFailures": 0,
"numTestsRun": 0,
"totalTime": 0,
"codeCoverage": [],
"codeCoverageWarnings": [],
"failures": [],
"flowCoverage": [],
"flowCoverageWarnings": [],
"successes": []
}
},
"done": true,
"id": "0Af0100000joptCCAQ",
"ignoreWarnings": true,
"lastModifiedDate": "2023-03-17T13:30:29.000Z",
"numberComponentErrors": 1,
"numberComponentsDeployed": 5,
"numberComponentsTotal": 6,
"numberTestErrors": 0,
"numberTestsCompleted": 0,
"numberTestsTotal": 0,
"rollbackOnError": true,
"runTestsEnabled": false,
"startDate": "2023-03-17T13:30:15.000Z",
"status": "Failed",
"success": false
},
"command": "sfdx force:mdapi:deploy -u<EMAIL_ADDRESS>-g -f "/Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/testStore/experience-bundle-package/testStore1ToDeploy.zip" --wait 60 --verbose --singlepackage --apiversion=57.0 --json"
}
ERROR running commerce:store:create:  StoreQuickstartSetup failed

Not sure what's going on here. I ran it a second time, but with --loglevel=trace and did not get the error at all and the command completed successfully. Hopefully it was just some sort of one-time hiccup.

Seems like the bug has something to do with the Network metadata: "Error: You can only select profiles that are associated with the experience.","
Deploy the new zip including the flow, ignoring warnings, then clean-up.
›   Warning: sfdx-cli update available from 7.177.1 to 7.183.1.
ERROR running StoreQuickstartSetup:  {
"status": 1,
"result": {
"checkOnly": false,
"completedDate": "2023-03-17T14:11:40.000Z",
"createdBy": "00501000003AdXL",
"createdByName": "User User",
"createdDate": "2023-03-17T14:11:23.000Z",
"details": {
"componentFailures": [
{
"changed": false,
"componentType": "Network",
"created": false,
"createdDate": "2023-03-17T14:11:40.000Z",
"deleted": false,
"fileName": "networks/Store.network",
"fullName": "Store",
"problem": "Error: You can only select profiles that are associated with the experience.",
"problemType": "Error",
"success": false
}
],
"componentSuccesses": [
{
"changed": true,
"componentType": "CustomSite",
"created": false,
"createdDate": "2023-03-17T14:11:40.000Z",
"deleted": false,
"fileName": "sites/Store.site",
"fullName": "Store",
"id": "0DM01000000KzQoGAK",
"success": true
},
{
"changed": true,
"componentType": "ExperienceBundle",
"created": false,
"createdDate": "2023-03-17T14:11:40.000Z",
"deleted": false,
"fileName": "experiences/Store1",
"fullName": "Store1",
"id": "0DM01000000KzQpGAK",
"success": true
},
{
"changed": false,
"componentType": "NavigationMenu",
"created": false,
"createdDate": "2023-03-17T14:11:40.000Z",
"deleted": false,
"fileName": "navigationMenus/Default_My_Account_Menu.navigationMenu",
"fullName": "Default_My_Account_Menu",
"id": "0Lm01000000KzPWCA0",
"success": true
},
{
"changed": true,
"componentType": "",
"created": false,
"createdDate": "2023-03-17T14:11:40.000Z",
"deleted": false,
"fileName": "package.xml",
"fullName": "package.xml",
"success": true
},
{
"changed": false,
"componentType": "NavigationMenu",
"created": false,
"createdDate": "2023-03-17T14:11:40.000Z",
"deleted": false,
"fileName": "navigationMenus/Default_User_Profile_Menu.navigationMenu",
"fullName": "Default_User_Profile_Menu",
"id": "0Lm01000000KzPVCA0",
"success": true
},
{
"changed": false,
"componentType": "NavigationMenu",
"created": false,
"createdDate": "2023-03-17T14:11:40.000Z",
"deleted": false,
"fileName": "navigationMenus/Default_User_Profile_Menu1.navigationMenu",
"fullName": "Default_User_Profile_Menu1",
"id": "0Lm01000000KzPaCAK",
"success": true
},
{
"changed": false,
"componentType": "NavigationMenu",
"created": false,
"createdDate": "2023-03-17T14:11:40.000Z",
"deleted": false,
"fileName": "navigationMenus/SFDC_Default_Navigation_Store.navigationMenu",
"fullName": "SFDC_Default_Navigation_Store",
"id": "0Lm01000000KzPZCA0",
"success": true
},
{
"changed": false,
"componentType": "NavigationMenu",
"created": false,
"createdDate": "2023-03-17T14:11:40.000Z",
"deleted": false,
"fileName": "navigationMenus/SFDC_Default_Navigation_testStore.navigationMenu",
"fullName": "SFDC_Default_Navigation_testStore",
"id": "0Lm01000000KzPUCA0",
"success": true
},
{
"changed": false,
"componentType": "NavigationMenu",
"created": false,
"createdDate": "2023-03-17T14:11:40.000Z",
"deleted": false,
"fileName": "navigationMenus/Default_My_Account_Menu1.navigationMenu",
"fullName": "Default_My_Account_Menu1",
"id": "0Lm01000000KzPbCAK",
"success": true
}
],
"runTestResult": {
"numFailures": 0,
"numTestsRun": 0,
"totalTime": 0,
"codeCoverage": [],
"codeCoverageWarnings": [],
"failures": [],
"flowCoverage": [],
"flowCoverageWarnings": [],
"successes": []
}
},
"done": true,
"id": "0Af0100000jovS5CAI",
"ignoreWarnings": true,
"lastModifiedDate": "2023-03-17T14:11:40.000Z",
"numberComponentErrors": 1,
"numberComponentsDeployed": 8,
"numberComponentsTotal": 9,
"numberTestErrors": 0,
"numberTestsCompleted": 0,
"numberTestsTotal": 0,
"rollbackOnError": true,
"runTestsEnabled": false,
"startDate": "2023-03-17T14:11:27.000Z",
"status": "Failed",
"success": false
},
"command": "sfdx force:mdapi:deploy -u<EMAIL_ADDRESS>-g -f "/Users/peter.knolle/.commerce/devhubs/peterDOTknolleATtrifecta.com/adminATcommerceDOTcom/Store/experience-bundle-package/Store1ToDeploy.zip" --wait 60 --verbose --singlepackage --apiversion=57.0 --json"
}
ERROR running commerce:store:create:  StoreQuickstartSetup failed

Hello @peterTrifecta , thank you for raising the issue! Can you please provide us more information about the environment you are working on? Specifically, the api version your salesforce instance is on, if you are working in a STEAM environment main/patch branch or from a local salesforce build, and the output of your sfdx plugins?


Clarification on Background Tasks

Hello,
Just looking at your lib for queue and upload of images/videos and have a question about what you said in #29:

The main thing is remember background tasks are limited to ~30 seconds cross platform so ensure your job can complete in that time frame (or break it up into separate tasks).

Does this mean that the upload would need to complete in this timeframe, or is it just that the job in the queue would need to be kicked off? I'm assuming the former but thought I'd check.
In this case, https://github.com/joltup/react-native-threads might be a better choice to work with your lib.. .as it doesn't seem to have the 30 second restriction?

Yes any job that is processed in a background task is limited to at most 30
seconds of execution, so the upload would need to complete during that
time. If you can't complete the upload in that time limit you will have to
get creative. For example you can do something like break the upload into
chunks and reassemble on the backend (ie if a large video file takes 2
minutes to upload then break it up into 6 jobs that each upload 1/6 video
in 20 seconds and then stitch back together on backend). Realistically you
prob want to limit the job to 25 seconds and if it times out for some
reason at least you have 5 seconds to handle that error case gracefully -
if you hit the hard OS enforced timeout I don't think your code will get a
chance to handle the timeout gracefully I suspect iOS will just kill the
process.
Note that this is an operating system limitation (specifically iOS if I
recall correctly), it's not a limitation related to react-native-queue
specific code or anything like that.
React-native-queue is agnostic and can integrate with just about anything,
so sure there's no reason to feel limited to the packages that I integrate
with in my examples, they are just there to help people wrap their heads
around how RNQ can be integrated into anything. That said I suspect
react-native-threads will run indefinitely so long as your app is in focus,
it may not run at all when your app is not in focus (which is what
the "react-native-background-task" library will do). As such I'm not sure
react-native-threads will accomplish what you need (if what you need truly
is background job processing ie when your app is running but the user isn't
actively interacting with it).
On Wed, Jan 2, 2019 at 4:58 PM Justin Lane<EMAIL_ADDRESS>wrote:

Hello,
Just looking at your lib for queue and upload of images/videos and have a
question about what you said in #29
https://github.com/billmalarky/react-native-queue/issues/29:
The main thing is remember background tasks are limited to ~30 seconds
cross platform so ensure your job can complete in that time frame (or break
it up into separate tasks).
Does this mean that the upload would need to complete in this timeframe,
or is it just that the job in the queue would need to be kicked off? I'm
assuming the former but thought I'd check.
In this case, https://github.com/joltup/react-native-threads might be a
better choice to work with your lib.. .as it doesn't seem to have the 30
second restriction?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/billmalarky/react-native-queue/issues/42, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxTU4Pj3UFoSJScxBVl5PJIoMWNLtUAks5u_StsgaJpZM4ZnSiA
.

Wow! Thanks for the speedy, detailed response. I shall close this out now as you've answered my questions and exceeded my expectations with your answer. :100: :star:

Haha thank you!
On Wed, Jan 2, 2019 at 5:32 PM Justin Lane<EMAIL_ADDRESS>wrote:

Closed #42 https://github.com/billmalarky/react-native-queue/issues/42.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/billmalarky/react-native-queue/issues/42#event-2051366063,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABxTUzIixqunXIYnCHn1BsmP-xC-UrgDks5u_TN2gaJpZM4ZnSiA
.


[Fix #6900] Rails/TimeZone cop in strict mode

Split tests for DANGEROUS_METHODS and :current, which is a special case
Use preferred #{klass}.zone.#{method} style, as opposed to "acceptable" #{klass}.#{method}.in_time_zone
Rename TIMECLASS contsant to TIMECLASSES as it represents more than one time class
Prefer Time class over DateTime in strict mode
Fix Time.current => Time.zone.now instead of Time.zone.current which raises error

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

The only issue this cop doesn't fix is if you're using "flexible" mode and already have a code like this: Time.zone.now.in_time_zone, because this cop doesn't report an issue when zone or in_time_zone methods are in method chain.
Also, I'd suggest making "strict" mode the default. "flexible" mode allows for this code:
pry(main)> Time.zone = 'GMT'
# flexible allowed
pry(main)> Time.now.beginning_of_day.in_time_zone
Sat, 13 Apr 2019 17:00:00 GMT +00:00
# strict
pry(main)> Time.zone.now.beginning_of_day
Sun, 14 Apr 2019 00:00:00 GMT +00:00

The above code will be hidden under the false assumption that rubocop detected all time zone related issues.

Also, I'd suggest making "strict" mode the default. "flexible" mode allows for this code:

Frankly, at this point I don't even remember why we have two modes. @rubocop-hq/rubocop-core Can anyone refresh my memory?

Frankly, at this point I don't even remember why we have two modes. @rubocop-hq/rubocop-core Can anyone refresh my memory?

I found in #1668 the two mode were present from the beginning, and that the idea seems to come from the referenced blog post, which talks about correct, acceptable, and wrong ways to handle time zones.

Hey @jonas054 that's a good point! It was probably introduced as a parity with that blog post. We could make the cop simpler by always suggesting using Time.zone.
I think the issue here might be that many people (me included) don't know or don't check all the cops and just run rubocop. The default here is "flexible", which in turn suggests "Acceptable" instead of "Correct" (as per blog post) option.
I guess, even for flexible mode, we should suggest "Correct" option. Autocorrect should also correct to "Correct". The only difference would be that flexible mode accepts "Acceptable" solutions, while strict mode doesn't.
...or, as said. we can remove flexible and just enforce "Correct". 🤔 At this point, where rubocop was correcting to "Acceptable", maybe it's better to keep flexible as only solution, remove strict, but when suggesting and autocorrecting, correct to "Correct". What do you think?

Bump! I just rebased this on top of master

Bump! I just rebased this on top of master (0.68)

Sorry for being slow to respond. The changes look good to me, but I'd appreciate a second opinion from  @rubocop-hq/rubocop-core.

No worries! I understand it takes time to review these changes.
I'm just selfishly trying to push my PRs while I have time to keep them in sync with master. :D

Thanks for tackling this! Probably it's worth reviewing the related sections of the Rails Style Guide as well.


How to set mimetype based on file extension

Hi -
I would like to set MIME for e.g. yaml documents to text/plain so that yaml files can be directly viewed in the web browser rather than downloaded.
I tried e.g.
idx.add_icon_rule('my_yaml_icon.png', ext='yaml', mimetype='text/plain')
but the response header returned by flask still defaults to application/octet-stream. Can you please share example how to properly set mime based on file extension?
Thank you,
TIR

Hi,
The add_icon_rule method enable to display the icon choose for extension OR mimetype. It does not set the mimetype
To do this you need to force the Content-Type header with Flask like
resp = make_response(idx.render_autoindex('.'))
resp.headers['Content-Type'] = 'text/plain'
return resp


Quarantine Prototype

An early prototype of how quarantine might work.
Questions:

quarantine / unquarantine are hard to spell, type and just don't seem right.  Please suggest alternatives
currently one can quarantine peers and containers.  To quarantine a peer/container means to temporarily remove the container from WeaveDNS.  We could extend this to also mean remove it from routing... thoughts?
quarantines are records, gossiped phone tree'd around the cluster.  I went for this over just tombstoning the DNS entry so the burden of remembering the original mapping was not placed on the caller.
I would like to extend the quarantine code to things like "all endpoints for foo.weave.local in the bar datacenter".  Weave would need to know about DCs, but this could map nicely to EC2.  Thoughts?

Example usage:
$ docker run -di --hostname foo.weave.local ubuntu /bin/bash
f18a16ce6e4c4882f38f3f44641ae2a2dc1468196b66829c5bc00b89495cb333
$ nslookup foo.weave.local <IP_ADDRESS>
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

Name:	foo.weave.local
Address: <IP_ADDRESS>

$ ./weave quarantine-container f18a16ce6e4c488 1h
3582c57bed56e2ea
$ nslookup foo.weave.local <IP_ADDRESS>
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

*** Can't find foo.weave.local: No answer

$ ./weave quarantines
ID               Container    Peer              Duration
3582c57bed56e2ea f18a16ce6e4c                   2015-07-14 13:54:38 +0000 UTC

$ ./weave unquarantine 3582c57bed56e2ea
$ nslookup foo.weave.local <IP_ADDRESS>
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

Name:	foo.weave.local
Address: <IP_ADDRESS>

TODO:

[ ] smoke tests
[ ] delete old entries
[ ] make unquarantine take a peer / container, and remove all records for that peer / container

I've just rebased this on master; the old branch is backed up as quarantine-backup.


Handle caching issues

On CFC, scratch = true: generate_peptides starts sometimes again, even though no input changed...
Could not reproduce this issue on my Mac.
Use lenient caching? And if, for which processes?

cache lenient seems to fixed this issue.
However, now ch_epitope_predictions.buffer(size: 1000, remainder: true) causes merge_predictions_buffer to rerun again always.

cache lenient seems to fixed this issue.
However, now ch_epitope_predictions.buffer(size: 1000, remainder: true) causes merge_predictions_buffer to rerun again always.


How to use Scssfmt  with lint-staged to autoformat code?

http://scssfmt.com

This is similar to stylefmt. This will be possible when #138 is done.


Feature: Top stakers of a property

Proposed Changes
A top stakers section should be added to every detail page to provide greater insights into a property
Implementation
I added a new TopStakers component to the overview which fetches the top 5 stakers and displays these in a list

@Cold-A-Muse Thanks for the best PR! 🍕🍕🍕🍕🍕🍕🍕🍕🍕🍕🍻


0.9.6 very slow during aptly publish snapshot

Hi,
During a chef run aptly publish snapshot -distribution='precise' -component 'main' ubuntu-qa-20160302 ubuntu-qa ran very slowly, and eventually timed out after an hour. I ran it manually and saw that out of ~40k packages or so it slowed down immensely around the ~27k mark. strace seemed to indicate it was spending a lot of time waiting in futex, but I no longer have the log. Since the repo is important, I downgraded to 0.9.5 which seemed to solve the issue. I realize it's not a lot to go on, but wanted to file the issue to get this on the radar in case anyone else came looking.
This was on an Ubuntu 12.04 LTS box on aptly version 0.9.6 - downgrading aptly to 0.9.5 fixed it.

@mynamewastaken see #87, you can use -skip-contents to avoid Contents indices generation.

@smira I don't have enough time to look at/update the Chef cookbook we use for aptly, so I think I will stay on 0.9.5 for now. Thanks for the quick response!


Update gems dependencies

I'm currently running Rails 4.2, and coinbase-ruby's depends on an old version of monetize/money (which in turn referenced even older versions of the i18n gems) and I was getting pretty nasty conflicts. Updated the gems and then updated the tests, all seems fine.

@aianus hi, would you mind taking a look?

Thanks, rebased on master as 6a7186288ff742a8bee56820865c4b2100d1a2bc
Also, consider using the v3 branch as it fixes a couple of small problems/annoyances in v2.

@aianus Could you please bump the gem version so this doesn't block rails 4.2.0?

@aianus Still not bumped…


Added blog List page

added blogs list page with abstracted out cards that change with dynamic array of data from backend
Description

Related Issues

Closes #436

Screenshots / videos (if applicable)

https://github.com/user-attachments/assets/9d22b8b5-f07e-479e-9f6e-7c59e7a495ac

@ShivanshPlays please update sync fork once

Done @mdazfar2


CRI-O build is broken

CRI-O build doesn't work anymore because btrfs and devicemapper packages provided by Semaphore CI environment (Ubuntu 14.04) are too old.
We should build from sources instead.

Duplicates #127


distinct marker types

I have a student currently working on an interface that will allow browsing BrAPI genotyping data and we would like to allow filtering by marker type. With the current specs, we see no other option than getting the entire (possible huge) list of markers, and building the distinct list on the client side. It would therefore be extremely more convenient to be able to grab in a single request the list of marker types in a given dataset.

Wouldn't all markers in a markerprofile mostly be the same type (GBS etc). Maybe I am not sure what you mean by marker type?

As far as I know when you launch variant calling on sequencing data you do get different kinds of variants. At least SNPs and INDELs. Sometimes CNVs or structural variants (often marked as MIXED).

May I suggest something along these lines?
GET /brapi/v1/marker-types-search{?markerDbIds}{?name}{?matchMethod}{?pageSize}{?page}

Would it be enough to define a fixed set marker types? or is it important for each system to be able to define their own marker types?
Just from this thread:
GBS
SNP
INDEL
CNV
MIXED
Any more?

From my point of view defining a fixed set of marker types is feasible but is a separate matter. The need I was trying to express was for a way of knowing which marker types are actually present in a given dataset.

Ok I think see what you are trying to do.
But how do you want to reference the data set to get marker types for?
Your previous comment suggests that you want to provide a list of markerDbIds and get back the distinct list of marker types. But for large list of markers, this seems only slightly better than doing the filtering by type on the client side right?
Someone from the GOBii team has suggested that we need the concept of a Marker Group so that we can reference a group of markers with a single ID. Would this make more sense for your use case?
Something like : GET /makertypes{?markerGroupDbId}

My ultimate goal is to make Beegmac able to query (at once) the server saying for example "I want all markers of type SNP or INDEL in chromosomes 1 and 2". But for that It needs to know which marker types are actually represented.
Sorry my suggestion on 5 Feb wasn't very accurate. In my very own case the only filtering parameter I would need to pass would be a study ID, assuming the database is able to tell which marker types are present in a given genotyping study (which I think is a pretty common situation). But I would appreciate any comments from other people working with genotyping data so we can think of a generic enough solution.
Regarding marker groups it all depends how they can be defined. If we find a way of getting a markerGroupDbId that refers to all markers used in a study then the call you suggest could solve the problem indeed, although to my eyes this creates an indirection that needs to be justified.

ok thanks for the clarification, I will talk to some other (GOBii, Germinate, etc) and see what I can come up with.
Study Id makes sense in your case, but makes me a little nervous because there is no direct link between study and marker defined in BrAPI right now. I think there should be, but it hasn't been explicitly defined yet.


Colorama dependency for helper script

The helper script has a dependency on colorama but this is not documented in the instructions. Is it worth providing a requirements.txt file for this?
Could this be automated by making the helper script a bazel target in this repo so consumers can just do bazel run //tools:add_module?

A bazel run target would be ideal, and show that the tooling we're building is sufficient to do productive work.


Rename Partner to Organisation

Missing motivation from the PR description - this would be super useful later on to know why we decided to rename this schema.

General question - are we happy with the generated docs on GraphiQL, or do we need something more.. hm, graphical?

Cool, added a description.
ooh nice idea. I'd love to be able to see entity relationship diagrams for both prismic types and our schema.


Loss of double bonds symmetry with dative bonds

There is no possibility to encode with SMILES E/Z stereochemistry of a double bond, if one of its atoms forms a dative bond:
from rdkit import Chem
print(Chem.rdBase.rdkitVersion)
> 2020.03.1
print(Chem.rdBase.rdkitBuild)
Windows|10.0.18363||MSVC|64-bit

mol = Chem.MolFromSmiles('CC=[C-]->[*])
b = mol.GetBondWithIdx(1)
b.SetStereo(Chem.BondStereo.STEREOZ)
b.SetStereoAtoms(0,3)
mol

print(Chem.MolToSmiles(mol))
> *<-[C-]=C\\C
print(Chem.MolToSmiles(mol), canonical = False)
> C/C=[C-]->*
print(Chem.MolToSmiles(Chem.MolFromSmiles(Chem.MolToSmiles(mol))))
> *<-[C-]=CC

I guess, "/>", "\>", "</", and "<\" symbols should be added for coordination bonds (and hydrogen bonds).

Confirmed. It’s not currently possible to provide info about double bond stereo in SMILES.
I will take a look at supporting /> and \>.

As a general comment: as you have discovered, it is possible to set the double bond stereo yourself. When doing that I would recommend using STEREOCIS or STEREOTRANS instead of the Z or E variants. This is more explicit and you don’t need to worry about CIP ordering

Oh, that's how it works. Thanks for the advice


Infinite loading, import not working

From a fresh install, when I open it up the spinning wheel never stops. When I go to import it will show all of the games, but clicking import doesn't work. Here's the log file contents:
[2019-11-08 07:17:03.712] [info] Started SGDB Manager 0.3.6
[2019-11-08 07:17:04.898] [info] Got Steam path: c:/program files (x86)/steam
[2019-11-08 07:17:28.357] [info] Import: Started bnet
[2019-11-08 07:17:28.363] [info] Import: Started egs
[2019-11-08 07:17:28.371] [info] Import: Started gog
[2019-11-08 07:17:28.396] [info] Import: Completed bnet
[2019-11-08 07:17:28.419] [info] Import: Completed egs
[2019-11-08 07:17:28.425] [info] Import: Completed gog
[2019-11-08 07:17:28.430] [info] Import: 2 games found for bnet
[2019-11-08 07:17:28.434] [info] s1,s2
[2019-11-08 07:17:28.441] [info] Import: 3 games found for egs
[2019-11-08 07:17:28.445] [info] Feverfew,Eagle,Turaco
[2019-11-08 07:17:28.450] [info] Import: 0 games found for gog
[2019-11-08 07:17:28.454] [info] Import: origin not installed
[2019-11-08 07:17:28.459] [info] Import: uplay not installed
[2019-11-08 07:17:31.324] [error] TypeError: Cannot read property '0' of undefined
at file:///C:/Users/chris/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:70:81718
at Array.forEach ()
at t.value (file:///C:/Users/chris/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:70:81665)
at t.value (file:///C:/Users/chris/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:70:77125)
at Object. (file:///C:/Users/chris/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:1152)
at w (file:///C:/Users/chris/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:1190)
at file:///C:/Users/chris/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:1336
at S (file:///C:/Users/chris/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:1422)
at E (file:///C:/Users/chris/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:1871)
at C (file:///C:/Users/chris/AppData/Local/Programs/SteamGridDB%20Manager/resources/app.asar/public/bundle.js:43:1683)
[2019-11-18 16:52:53.982] [info] Started SGDB Manager 0.3.6
[2019-11-18 16:52:55.533] [info] Got Steam path: c:/program files (x86)/steam
[2019-11-18 16:53:43.127] [info] Import: Started bnet
[2019-11-18 16:53:43.136] [info] Import: Started egs
[2019-11-18 16:53:43.144] [info] Import: Started gog
[2019-11-18 16:53:43.177] [info] Import: Completed bnet
[2019-11-18 16:53:43.203] [info] Import: Completed egs
[2019-11-18 16:53:43.209] [info] Import: Completed gog
[2019-11-18 16:53:43.215] [info] Import: 2 games found for bnet
[2019-11-18 16:53:43.221] [info] s1,s2
[2019-11-18 16:53:43.229] [info] Import: 3 games found for egs
[2019-11-18 16:53:43.234] [info] Feverfew,Eagle,Turaco
[2019-11-18 16:53:43.240] [info] Import: 0 games found for gog
[2019-11-18 16:53:43.245] [info] Import: origin not installed
[2019-11-18 16:53:43.251] [info] Import: uplay not installed
[2019-11-18 16:55:07.361] [info] Import: Started bnet
[2019-11-18 16:55:07.370] [info] Import: Started egs
[2019-11-18 16:55:07.379] [info] Import: Started gog
[2019-11-18 16:55:07.399] [info] Import: Completed bnet
[2019-11-18 16:55:07.409] [info] Import: Completed egs
[2019-11-18 16:55:07.437] [info] Import: Completed gog
[2019-11-18 16:55:07.443] [info] Import: 2 games found for bnet
[2019-11-18 16:55:07.448] [info] s1,s2
The import statements show up every time, but the error has only happened once.

Also, what version of node should this be built with?

Same problem here with a fresh install today :-/
Nothing happens when i click on import and the libary show me nothing and the spinning wheel nevver stops too.
[2019-11-21 09:53:50.533] [info] Started SGDB Manager 0.3.6
[2019-11-21 09:53:51.343] [info] Got Steam path: e:/steam
[2019-11-21 09:54:15.521] [info] Import: Started origin
[2019-11-21 09:54:15.765] [info] Import: Completed origin
[2019-11-21 09:54:15.774] [info] Import: bnet not installed
[2019-11-21 09:54:15.781] [info] Import: egs not installed
[2019-11-21 09:54:15.787] [info] Import: gog not installed
[2019-11-21 09:54:15.793] [info] Import: 3 games found for origin
[2019-11-21 09:54:15.798] [info] Origin.OFR.50.0002942,Origin.OFR.50.0003453,Origin.OFR.50.0003514
[2019-11-21 09:54:15.810] [info] Import: uplay not installed

Same here

Same issue here, also trying older versions results in the same problem.

It must be some update to Steam's APIs that broke this if older versions also break.

its strange because it works fine on my laptop but not my desktop with the same version of steam

Sorry for the delays, can you guys try with v0.4.0?

Sorry for the delays, can you guys try with v0.4.0?

Just tested it but same thing is happening.

Sorry for the delays, can you guys try with v0.4.0?

Just tested it but same thing is happening.

Same thing here.
I wonder if it's got to do with the size of the library on initial import...   I left it running from for about 5 hours while the system was pretty much idle and still just had the spinning load icon in the application window.  It certainly seems like it could be that the code is making too many API calls in a short amount of time and being temporarily blacklisted from hitting the API again.  This used to happen with Enhanced Steam (before it was forked into Augmented Steam) when you would navigate to the market page and it would be making API calls to Valve in order to query the buy and sell orders for cards.

Unfortunately no improvement.
Here is the log:
[2019-12-03 14: 16: 50.267] [info] Got Steam path: c: / program files (x86) / steam
[2019-12-03 14: 16: 50.278] [info] Found 2 Steam libraries
[2019-12-03 14: 16: 50.298] [info] Fetched 4 Steam games
[2019-12-03 14: 18: 16.307] [info] Import: Started origin
[2019-12-03 14: 18: 16.515] [info] Import: Completed origin
The libraries are found, but in the manager is still spinningwheel and an import does not work even though it appears in the logfile as "completed". If any data is needed ask quietly. Thank you!

Sorry for the delays, can you guys try with v0.4.0?

Just tested it but same thing is happening.

Same thing here.
I wonder if it's got to do with the size of the library on initial import...  I left it running from for about 5 hours while the system was pretty much idle and still just had the spinning load icon in the application window. It certainly seems like it could be that the code is making too many API calls in a short amount of time and being temporarily blacklisted from hitting the API again. This used to happen with Enhanced Steam (before it was forked into Augmented Steam) when you would navigate to the market page and it would be making API calls to Valve in order to query the buy and sell orders for cards.

I only have around 20 actually installed and I left it running for about 2 hours but nothing changed.

Sorry for the delays, can you guys try with v0.4.0?

Just tested it but same thing is happening.

Same thing here.
I wonder if it's got to do with the size of the library on initial import...  I left it running from for about 5 hours while the system was pretty much idle and still just had the spinning load icon in the application window. It certainly seems like it could be that the code is making too many API calls in a short amount of time and being temporarily blacklisted from hitting the API again. This used to happen with Enhanced Steam (before it was forked into Augmented Steam) when you would navigate to the market page and it would be making API calls to Valve in order to query the buy and sell orders for cards.

I only have around 20 actually installed and I left it running for about 2 hours but nothing changed.

Does it only query installed games or does it query your entire library? I'm guessing the latter (much like the GOG Galaxy 2.0 beta, which chugged on initial import of my Steam library but is much better now only looking for the delta).  If it's the former, I'm out of ideas.  How big is your Steam library overall?

Sorry for the delays, can you guys try with v0.4.0?

Just tested it but same thing is happening.

Same thing here.
I wonder if it's got to do with the size of the library on initial import...  I left it running from for about 5 hours while the system was pretty much idle and still just had the spinning load icon in the application window. It certainly seems like it could be that the code is making too many API calls in a short amount of time and being temporarily blacklisted from hitting the API again. This used to happen with Enhanced Steam (before it was forked into Augmented Steam) when you would navigate to the market page and it would be making API calls to Valve in order to query the buy and sell orders for cards.

I only have around 20 actually installed and I left it running for about 2 hours but nothing changed.

Does it only query installed games or does it query your entire library? I'm guessing the latter (much like the GOG Galaxy 2.0 beta, which chugged on initial import of my Steam library but is much better now only looking for the delta). If it's the former, I'm out of ideas. How big is your Steam library overall?

Looking at the code it only appears to query what's installed rather than the entire library. I have about 500 games but only around 20 installed.

I've just been having a look at the code and when I change

Promise.all([steamGamesPromise, nonSteamGamesPromise]).then((values) => {

to

Promise.all([steamGamesPromise]).then((values) => {

from fetchGames() in games.jsx it loads my installed Steam games instantly.
https://i.postimg.cc/Qd8ndktG/img.jpg

Should be fixed in v0.4.1

THX. Now is running 👍

it's working now, Thanks 🙏
On Thu, Dec 5, 2019 at 11:10 AM Jozen Martinez<EMAIL_ADDRESS>wrote:

Should be fixed in v0.4.1
https://github.com/steamgriddb/steamgriddb-manager/releases/tag/v0.4.1
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/steamgriddb/steamgriddb-manager/issues/56?email_source=notifications&email_token=AN4FCG6WYGTV3NL3ZEQXLULQXCZQBA5CNFSM4JPSMPJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF73WOA#issuecomment-562019128,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN4FCG37HNLVJG3KRBB2VLLQXCZQBANCNFSM4JPSMPJA
.

I am having this issue at the moment. All of the sudden, I can no longer view my library, it is loading infinitely. I have tried uninstalling and re-installing, without success.


errorwriter errors

errcontext need to be an array, otherwise the errorwriters throw an error.

@nyeholt this can be closed too :)

Thanks for fixing this @dhensby


Massa Client Not Listened TEST 16

massa-client
� command · get_status
Error: check if your node is running: error trying to connect: tcp connect error: Connection refused (os error 111)

Logs :
2022-11-01T12:24:45.940315Z  INFO massa_node: Node version : TEST.16.0
2022-11-01T12:24:46.137816Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245
2022-11-01T12:24:46.170269Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 4270.252398647s ago and you have to wait 38929.7476012s before retrying.
2022-11-01T12:24:46.170603Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T12:25:46.171770Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245
2022-11-01T12:25:46.362570Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 4040.514541526s ago and you have to wait 39159.485458428s before retrying.
2022-11-01T12:25:46.362785Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T12:26:46.364337Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245
2022-11-01T12:26:46.467851Z  WARN massa_bootstrap::client: Error while bootstrapping: io error: early eof
2022-11-01T12:26:46.468352Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T12:27:46.470408Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245
2022-11-01T12:27:46.663659Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 5058.663387752s ago and you have to wait 38141.336612164s before retrying.
2022-11-01T12:27:46.663944Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T12:28:46.665745Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245
2022-11-01T12:28:47.003563Z  WARN massa_bootstrap::client: Error while bootstrapping: io error: early eof
2022-11-01T12:28:47.004286Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T12:29:47.006050Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245
2022-11-01T12:29:47.051222Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 6454.498238812s ago and you have to wait 36745.501761098s before retrying.
2022-11-01T12:29:47.051564Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T12:30:47.053462Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245
2022-11-01T12:30:47.235108Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 4159.5918281s ago and you have to wait 39040.408171797s before retrying.
2022-11-01T12:30:47.235354Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 60s.

Are you sure you are on the last image hub release?
Can you try a docker pull rykcod/massa again? Another release pushed yesterday with same tag on the hub (Sorry ;) )? And create your container again with the last version?
This last release solve a massa-guard issue when node hang.
After if the issue persist, please give me the /massa_mount/logs/massa-guard/logs/%TODAYLOGFILE%

Ok let me check.many thanks. I will try. I will inform you if already done

Arf sorry, maybe not the good way for your issue, i think you just bootstrapped too many time on the offcial node today,
Please add this community nodes in your /massa_mount/config.toml :
http://massa.alphatux.fr/bootstrapper.toml

Just look my last message,
Please add link content into your /massa_mount/config.toml then restart your container,
Your node cant bootstrap at this time, in fact you cant use your massa-client before bootstrap

I think I did this step
 $ cat massa_mount/config.toml
[bootstrap]
bootstrap_list = [["<IP_ADDRESS>:31245", "P1hdgsVsd4zkNp8cF1rdqqG6JPRQasAmx12QgJaJHBHFU1fRHEH"],
	["<IP_ADDRESS>:31245", "P1en3tRbmgTgLCC53Rk3rvS5BPVwwN7TPMdzDG9J95bGzSCDVPR"],
	["<IP_ADDRESS>:31245", "P1cVZ8RtdnPsTAKpZsJniDyBqJ8BWevnZZ96hAzY5vhYwp8WsHj"],
	["<IP_ADDRESS>:31245", "P1Lc1GcYdhrKNuT8MCte81dCior4mGJSNgbU9ytz4bqAG9RPju6"],
	["<IP_ADDRESS>:31245", "P1sWoW9LRCJCj8VVb4j2rfbw4yWrTgPbLFFtVnRKwVpD29mouEr"],
	["<IP_ADDRESS>:31245", "P1MoKFZGuYBBeBq8nYkoRmRXuQACJU1WNJ6pp3uQC3Q36YBkrv3"],
	["<IP_ADDRESS>:31245", "P1iVgdGUM6RKLBZ7K6aYZwtjyLTnkPmcYx2d6xnUPKATC1KRrEi"],
	["<IP_ADDRESS>:31245", "P1GFcjxo2RcPg1cQYHCkEAbm5HQs13ExwPrR32SD5BpG1MpU9TB"],
	["<IP_ADDRESS>:31245", "P14HHzXa7HcynzfNXyw9yKF9GkC34oPYiiAY8chFjExGiSPoMnh"],
	["<IP_ADDRESS>:31245", "P1qxuqNnx9kyAMYxUfsYiv2gQd5viiBX126SzzexEdbbWd2vQKu"],
	["<IP_ADDRESS>:31245", "P12rPDBmpnpnbECeAKDjbmeR19dYjAUwyLzsa8wmYJnkXLCNF28E"],
	["<IP_ADDRESS>:31245", "P1SDGHkgMKbzceHMZitrAsySJiwpYnkERErXaMGW6HvLuNCfzFf"],
	["<IP_ADDRESS>:31245", "P1HEGx8JMUjTKiPNVf6KPsCa3cvrV3Bfh61CJXwqKRUeyhBDADd"],
	["<IP_ADDRESS>:31245", "P1S2VXHXxyzabGgicu6Ri1dhd17sXjMkZWbW5vvLGjDJPhREPkz"],
	["<IP_ADDRESS>:31245", "P13Ykon8Zo73PTKMruLViMMtE2rEG646JQ4sCcee2DnopmVM3P5"],
	["<IP_ADDRESS>:31245", "P1oRbuvfehdwwihCuBBPiDJfdDM6DbgPFd7ad88E9Z47qVC9kha"],
	["<IP_ADDRESS>:31245", "P12vxrYTQzS5TRzxLfFNYxn6PyEsphKWkdqx2mVfEuvJ9sPF43uq"],
	["<IP_ADDRESS>:31245", "P12UbyLJDS7zimGWf3LTHe8hYY67RdLke1iDRZqJbQQLHQSKPW8j"],
	["<IP_ADDRESS>:31245", "P1ozTcmnkX6pccZGU4X4HsXqoVYTxUedx9nwkWxA4Hjv7gCL78F"],
	["<IP_ADDRESS>:31245", "P1YdCBD14WeMjf8MiVzbi7umwdTsWdzh8rRLtufReLYpKxErBsb"],
	["<IP_ADDRESS>:31245", "P1uwVzBFQHJHEGi21mv6mXZo78d35mPe1g9pnpb7YHHzivtgAyb"],
	["<IP_ADDRESS>:31245", "P1PnLYRE7wEK7t7Kuu2v4DDMvpnRtj5h5mF5QPKEv2NPQ8sSHCJ"],
	["<IP_ADDRESS>:31245", "P1Ewsp1HYoU8gAeAYs7zP2Hm9ak2RzwPsTQXK9uAdBV7D8AYFd8"],
	["<IP_ADDRESS>:31245", "P1XxexKa3XNzvmakNmPawqFrE9Z2NFhfq1AhvV1Qx4zXq5p1Bp9"],
	["<IP_ADDRESS>:31245", "P1Nb3L8Y3AijVm6jzJXUzkoNEU1bmGJWoEszZCWNdiQLsqnSaiv"],
	["<IP_ADDRESS>:31245", "P1tK6BYtxrcRqDr693WUSHeZRuwRQzLxiuSLmZGXGGqLXVo777P"],
	["<IP_ADDRESS>:31245", "P1mpPVbrMPJgEPLhS3oKai7D72UTqQ68nyLAwbBvkK3hTwiNNvX"],
	["<IP_ADDRESS>:31245", "P1gEdBVEbRFbBxBtrjcTDDK9JPbJFDay27uiJRE3vmbFAFDKNh7"],
	["<IP_ADDRESS>:31245", "P1v6amTphHo2i4i1USM9e7XygTxV8n6Yx8cxnvSNzR2bSVBtrHR"]]

Still same,
 $ cat massa_mount/logs/massa-node/current.txt
2022-11-01T13:08:30.724219Z  INFO massa_node: Node version : TEST.16.0
2022-11-01T13:08:30.930064Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245
2022-11-01T13:08:30.934515Z  WARN massa_bootstrap::client: Error while connecting to bootstrap server: io error: Connection refused (os error 111)
2022-11-01T13:08:30.934634Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T13:09:30.936061Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245
2022-11-01T13:09:31.123176Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 6665.271450766s ago and you have to wait 36534.728549194s before retrying.
2022-11-01T13:09:31.123495Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T13:10:31.125317Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245
2022-11-01T13:10:31.169157Z  WARN massa_bootstrap::client: Error while bootstrapping: io error: early eof
2022-11-01T13:10:31.169505Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 60s.

I do restart and recreate the container, massa-client still refuesed.not listen.
� command · get_status
Error: check if your node is running: error trying to connect: tcp connect error: Connection refused (os error 111)
� command · get_status
Error: check if your node is running: error trying to connect: tcp connect error: Connection refused (os error 111)
� command · get_status
Error: check if your node is running: error trying to connect: tcp connect error: Connection refused (os error 111)

Ok,
Sorry guy, not an image issue, for me, your not unable to bootstrap,
Now, we could search whats the reason :/
Can you give me the content of your massa-guard log file?

Massa Guard only verbose this messages:
[20221101-12H44][INFO][INIT]Create your default config.toml with <IP_ADDRESS> as routable IP
[20221101-12H44][INFO][LOAD]LOAD /massa_mount/wallet.dat as ref
[20221101-12H44][INFO][LOAD]LOAD /massa_mount/node_privkey.key as ref
[20221101-12H44][INFO][LOAD]LOAD /massa_mount/staking_wallet.dat as ref
[20221101-12H48][INFO][LOAD]LOAD /massa_mount/config.toml as ref
[20221101-12H48][INFO][LOAD]LOAD /massa_mount/wallet.dat as ref
[20221101-12H48][INFO][LOAD]LOAD /massa_mount/node_privkey.key as ref
[20221101-12H48][INFO][LOAD]LOAD /massa_mount/staking_wallet.dat as ref
[20221101-13H08][INFO][LOAD]LOAD /massa_mount/config.toml as ref
[20221101-13H08][INFO][LOAD]LOAD /massa_mount/wallet.dat as ref
[20221101-13H08][INFO][LOAD]LOAD /massa_mount/node_privkey.key as ref
[20221101-13H08][INFO][LOAD]LOAD /massa_mount/staking_wallet.dat as ref
[20221101-13H13][INFO][LOAD]LOAD /massa_mount/config.toml as ref
[20221101-13H13][INFO][LOAD]LOAD /massa_mount/wallet.dat as ref
[20221101-13H13][INFO][LOAD]LOAD /massa_mount/node_privkey.key as ref
[20221101-13H13][INFO][LOAD]LOAD /massa_mount/staking_wallet.dat as ref
[20221101-13H42][INFO][LOAD]LOAD /massa_mount/config.toml as ref
[20221101-13H42][INFO][LOAD]LOAD /massa_mount/wallet.dat as ref
[20221101-13H42][INFO][LOAD]LOAD /massa_mount/node_privkey.key as ref
[20221101-13H42][INFO][LOAD]LOAD /massa_mount/staking_wallet.dat as ref
[20221101-13H45][INFO][LOAD]LOAD /massa_mount/config.toml as ref
[20221101-13H45][INFO][LOAD]LOAD /massa_mount/wallet.dat as ref
[20221101-13H45][INFO][LOAD]LOAD /massa_mount/node_privkey.key as ref
[20221101-13H45][INFO][LOAD]LOAD /massa_mount/staking_wallet.dat as ref
[20221101-13H47][INFO][LOAD]LOAD /massa_mount/config.toml as ref
[20221101-13H47][INFO][LOAD]LOAD /massa_mount/wallet.dat as ref
[20221101-13H47][INFO][LOAD]LOAD /massa_mount/node_privkey.key as ref
[20221101-13H47][INFO][LOAD]LOAD /massa_mount/staking_wallet.dat as ref

Let me know, if you need more information. please for give me suggest instruction.

Yes ok, as i said,
If we read the massa-guard log file your node dont bootstrap its normal you cant use massa-client,
We should search the reason why you are not able to bootstrap

Issue already resolved.
I removed IP node make break connection, restart container and boom running well. this my list bootstrap selection :
[bootstrap]
bootstrap_list = [["<IP_ADDRESS>:31245", "P1hdgsVsd4zkNp8cF1rdqqG6JPRQasAmx12QgJaJHBHFU1fRHEH"],
	["<IP_ADDRESS>:31245", "P1en3tRbmgTgLCC53Rk3rvS5BPVwwN7TPMdzDG9J95bGzSCDVPR"],
	["<IP_ADDRESS>:31245", "P1cVZ8RtdnPsTAKpZsJniDyBqJ8BWevnZZ96hAzY5vhYwp8WsHj"],
	["<IP_ADDRESS>:31245", "P1Lc1GcYdhrKNuT8MCte81dCior4mGJSNgbU9ytz4bqAG9RPju6"],
	["<IP_ADDRESS>:31245", "P1MoKFZGuYBBeBq8nYkoRmRXuQACJU1WNJ6pp3uQC3Q36YBkrv3"],
	["<IP_ADDRESS>:31245", "P14HHzXa7HcynzfNXyw9yKF9GkC34oPYiiAY8chFjExGiSPoMnh"],
	["<IP_ADDRESS>:31245", "P1qxuqNnx9kyAMYxUfsYiv2gQd5viiBX126SzzexEdbbWd2vQKu"],
	["<IP_ADDRESS>:31245", "P12rPDBmpnpnbECeAKDjbmeR19dYjAUwyLzsa8wmYJnkXLCNF28E"],
	["<IP_ADDRESS>:31245", "P1SDGHkgMKbzceHMZitrAsySJiwpYnkERErXaMGW6HvLuNCfzFf"],
	["<IP_ADDRESS>:31245", "P1HEGx8JMUjTKiPNVf6KPsCa3cvrV3Bfh61CJXwqKRUeyhBDADd"],
	["<IP_ADDRESS>:31245", "P1oRbuvfehdwwihCuBBPiDJfdDM6DbgPFd7ad88E9Z47qVC9kha"],
	["<IP_ADDRESS>:31245", "P1ozTcmnkX6pccZGU4X4HsXqoVYTxUedx9nwkWxA4Hjv7gCL78F"],
	["<IP_ADDRESS>:31245", "P1YdCBD14WeMjf8MiVzbi7umwdTsWdzh8rRLtufReLYpKxErBsb"],
	["<IP_ADDRESS>:31245", "P1uwVzBFQHJHEGi21mv6mXZo78d35mPe1g9pnpb7YHHzivtgAyb"],
	["<IP_ADDRESS>:31245", "P1PnLYRE7wEK7t7Kuu2v4DDMvpnRtj5h5mF5QPKEv2NPQ8sSHCJ"],
	["<IP_ADDRESS>:31245", "P1Ewsp1HYoU8gAeAYs7zP2Hm9ak2RzwPsTQXK9uAdBV7D8AYFd8"],
	["<IP_ADDRESS>:31245", "P1XxexKa3XNzvmakNmPawqFrE9Z2NFhfq1AhvV1Qx4zXq5p1Bp9"],
	["<IP_ADDRESS>:31245", "P1Nb3L8Y3AijVm6jzJXUzkoNEU1bmGJWoEszZCWNdiQLsqnSaiv"],
	["<IP_ADDRESS>:31245", "P1tK6BYtxrcRqDr693WUSHeZRuwRQzLxiuSLmZGXGGqLXVo777P"],
	["<IP_ADDRESS>:31245", "P1mpPVbrMPJgEPLhS3oKai7D72UTqQ68nyLAwbBvkK3hTwiNNvX"],
	["<IP_ADDRESS>:31245", "P1gEdBVEbRFbBxBtrjcTDDK9JPbJFDay27uiJRE3vmbFAFDKNh7"],
	["<IP_ADDRESS>:31245", "P1v6amTphHo2i4i1USM9e7XygTxV8n6Yx8cxnvSNzR2bSVBtrHR"]]

Many Thanks foryour support @rykcod
You can close this issue.

Enjoy :) have a nice day


Update to the latest version of Graphene

Hi @joaovitorsilvestre ,
First let me start off by saying this is an excellent library tying mongoengine and graphene together.  I'm surprised it does not have more stars here in Github.
I forked your repo and tried to bring everything online with the latest versions of the required packages, but the level of abstractions were too much for me to handle.
Graphene has introduced some breaking changes that are well documented, but still I could not make the required code changes.
Are you still involved with the library at all...?  It might be a little easier for you to upgrade your code.  I hope!
Here are the requirements.txt:
aniso8601==3.0.0
appdirs==1.4.3
graphene==2.1
graphql-core==2.0
graphql-relay==0.4.5
iso8601==0.1.12
mongoengine==0.15.0
promise==2.1
pymongo==3.6.1
pyparsing==2.2.0
rx==1.6.1
six==1.11.0
typing==3.6.4

and requirements-dev.txt:
attrs==17.4.0
click==6.7
coverage==4.5.1
flask-graphql==1.4.1
flask==0.12.2
graphql-core==2.0
itsdangerous==0.24
jinja2==2.10
markupsafe==1.0
mock==2.0.0
mongomock==3.9.0
more-itertools==4.1.0
pbr==4.0.2
pluggy==0.6.0
promise==2.1
py==1.5.3
pytest-cov==2.5.1
pytest==3.5.0
pytz==2018.4
rx==1.6.1
sentinels==1.0.0
six==1.11.0
typing==3.6.4
werkzeug==0.14.1

that I used (I passed your requirements*.txt through pipenv and had everything updaded to their latest version)
Without a proper update of your code I'm afraid all this nice work that you've done cannot be used in any recent projects.
Once again, here is a big proactive thanks!
Thanks!

Well,
I have good news and bad news... :smiley:
The good news is that if I change in the def resolver in graphene_mongo/models.py from:
        def auto_resolver(root, args, contex, info):
            return resolver_query(g_schema, mongo_doc, args, info, is_list=is_list, validator=validator)

to
        def auto_resolver(root, info, **kwargs):
            return resolver_query(g_schema, mongo_doc, kwargs, info, is_list=is_list, validator=validator)

implementing only the major breaking change from Graphene's 2.x upgrade, then I get the /graphiqlGUI properly resolving all my queries and mutations I tried on your test models.  And that's with all packages updated to their latest version.  I'll keep testing it...
The bad news is that the majority of the tests still fail.
Starting from the test suite apparently was too much for me.
Nonetheless, having 90% of the tests failing is not inspiring at all, so if you can still fix that I think you have a gem!!!
Thanks!

I spoke too soon.  My tests with mutation queries were done in your version of the repo not mine, so more changes are required in the mutation methods.
You can see the changes in my commit in my repo (ignore the pipfile changes)

I really apreciated the complements, thanks.
I'm at work right now, but soon as I get to home I will help you fix that.
:)

I did a small change at the setup of the tests and I belive that it fixed the most part of tests that were failing, you can see in  35_update_to_graphene2 (it has your fixes too).
The schema_builder was creating a graphene.Schema object with mutation even when it was not required (the argument mutations as None). And it breaks the assert of the function define_field_map (graphql.type.definition) because was sending a empty dict, which its not accepted anymore.
I didn't have time to fixed the other 4 tests that still failing. Soon I'll check it out.

Hey, thanks for looking it up.  I'll keep you posted on any other findings, while I start using this on my pet project.


Update dependencies, update to Swift 4.2

There's one awkward thing right now with Stencil that will prevent this from building. Basically, since it's just a git submodule, there is no Stencil module to namespace or import, so the usage of Stencil.normalize(value) breaks.
Installing it via SPM or Carthage instead of git submodules should solve this issue. I'll probably add that as an additional commit within this PR but wanted to initially submit this as a heads up.

Based on #3 it seems like the issue has already been raised.

In trying to move Stencil to Carthage, some interfaces to the Context struct become unavailable. I don't understand the project well enough yet to work around it properly.

Hi @weissazool, thanks for the PR! I'm sorry to say this project is no longer maintained, so you're probably best off forking the project and starting from there.
Regarding your issue with Stencil. If I remember correctly, I created a fork of the main Stencil repo, because there were some bugs I needed to fix, or features added, for this project to work, and it was hard to get those changes applied in the main repo in the timeframe that I wanted. It could very well be that those bugs no longer exist or those features have been added in Stencil, which would make it possible to switch back. It might require some refactoring though.

No problem - I figured this might not be maintained but thought I'd send the PR regardless. Appreciate the advice re: Stencil, cheers!


energy page top bar

If i go to the energy page (on left side bar), there is no skin on the top bar.

My ability to fix pages outside of dashboards is extremely limited, due to limitations in the mod card-mod on which this theme relies.

Oké thanks. And many thanks for this mod. I really love it. And I am using it everyday.
Lcars is the best interface ever.

Glad you like it! Thank you for the very kind words.


Can't create link to file or page from within composer form

It appears that from within a redactor content composer form you are unable to create a link to a file or page as per the 'Link' form within the Content block when editing in context. When adding a link in a composer redactor content field the url field only shows a text field and not the adjacent sitemap and page icon buttons.
Difference shown below:
Composer

In context

Fixed when updated to Redactor 10 and integrated the RedactorEditor class.


Bug with environment variables

This plugin cannot see docker container environment variables values. If I pass some variables from docker-compose.yml to container through services.environment code do not get this. In tinker all ok.

I don't use Docker, so PRs welcome! The plugin just uses Vite's loadEnv btw, which uses dotenv.

Ah! Try updating $passthroughVariables from ServeCommand.php. Environment variables for php artisan serve are filtered. See: https://github.com/laravel/framework/pull/42444


Add run untagged registration attribute in GitLab Provisoner

This adds an option to set or unset the GitLab Runner to run untagged jobs. [1]
If set to false the Runner will not pick any untagged jobs.
Will close Issue #17 🎫
Setting runUntagged to true:
[...]
provisioner:
  type: gitlab
  config:
     [..]
     runUntagged: true
     tagList: "macos-ventura-cilicon"

Setting RunUntagged to false:
[...]
provisioner:
  type: gitlab
  config:
     [...]
     runUntagged: false
     tagList: "macos-ventura-cilicon"

runUntagged is not optional inside the GitLab config block at the moment, happy to get feedback how to implement that.
[1] https://docs.gitlab.com/ee/api/runners.html#register-a-new-runner

I will close this as we have temporarily dropped support for GitLab until someone contributes an updated provisioner


Update README.md

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
13 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.02%) to 54.64%

Files with Coverage Reduction
New Missed Lines
%

btcec/signature.go
3
92.76%

database/ffldb/blockio.go
4
93.68%

peer/peer.go
6
74.28%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
26053

Relevant Lines:
47681

💛  - Coveralls


Prime and Inventory Page Rework - Fallout V&D

Submission Checklist
Required

[ ] The pull request title clearly contains the name of the sheet I am editing.
[ ] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[ ] The pull request makes changes to files in only one sub-folder.
[ ] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description
-Level information will be moved to Character Information. -Skills page was combined into Prime.
-Perks page was moved to Inventory.
-Formulas will no longer be displayed on the Character Sheet. -For SPECIAL, only Base will be calculated into every stat. -Because of this change, Total will now be used for SPECIAL checks so you can now put in your bonuses and penalties into +/- without affecting the other stats.

Character Sheet Info Roll20 Internal Use only.


"NameError: global name 'self' is not defined" in static FUSE._wrapper()

It's here https://github.com/fusepy/fusepy/blob/master/fuse.py#L756
This is the stacktrace.
Traceback (most recent call last):
  File "_ctypes/callbacks.c", line 315, in 'calling callback function'
  File "/Users/konstan/.virtualenvs/ssfs/lib/python2.7/site-packages/fuse.py", line 756, in _wrapper
    self.__critical_exception = e
NameError: global name 'self' is not defined
fuse: bad error value:<PHONE_NUMBER>

this is fixed in #125

Unfortunately, I still noticed the same issue.


Channel filter UI element for commandable vs. not commandable etc. (boolean filters)

When in the mindset to control commands manually, it's nice to be able to filter to all of an environment's commandable channels.

This should be next up. In addition to this, we want a way to spawn new windows from tabs (ideally don't even need to switch to the desired tab, should be able to just pop it out.


Add Model: GraphBEAN

Model Description
The GraphBEAN model is an unsupervised machine learning system to detect anomalies within bipartite graphs. It analyzes interactions between two distinct groups (e.g., consumers and merchants), focusing on the attributes of individual nodes and the edges (connections) between them.
Key Function: Identifies unusual or suspicious behaviors that deviate from standard patterns, allowing for the detection of potentially fraudulent activities even without prior examples of such fraud.
Details: https://engineering.grab.com/graph-anomaly-model
Interaction-Focused Anomaly Detection on Bipartite Node-and-Edge-Attributed Graphs.pdf
Tasks

[ ] Model saving/loading script
[ ] Model inference script (API or example)
[ ] Model performance evaluation script
[ ] Tutorial demonstrating usage

Additional Considerations
No response
license
yes
Submission Checklist

[ ] I have read the contribution guidelines.
[ ] I have provided a detailed model description.
[ ] All required scripts are provided, functional, and tested.
[ ] I have clarified dependencies and hardware considerations.
[ ] The tutorial is clear and demonstrates model usage.

Did a test run to trigger a release to the main pypi server, didn't work... will work on the original content of the issue.

https://pytorch-geometric.readthedocs.io/en/latest/_modules/torch_geometric/nn/dense/linear.html#HeteroDictLinear

https://pytorch-geometric.readthedocs.io/en/latest/generated/torch_geometric.data.HeteroData.html

https://medium.com/@pytorch_geometric/link-prediction-on-heterogeneous-graphs-with-pyg-6d5c29677c70

https://pytorch-geometric.readthedocs.io/en/latest/tutorial/create_gnn.html?highlight=gcn


sadly, double-quotes in app.yaml break cloudsql v2

Did this start happening recently and did our test catch it?


Extension is Broken on VS Code 1.66

I tried to use the extension on the latest version of vs code, 1.66 March 2022 update. The extension button does not show up in the lower left hand corner and trying to run teleplot: Start teleplot session gives an error saying teleplot.start is not a valid command. I reverted VS Code back to 1.64 January 2022 and the button appeared and the extension worked.

There were some issue with a VS ode update indeed, can you test the latest 1.0.7 version of the extension ?


[#177] publish does not include docs

Fixes #177

@starbelly @tsloughter Would it be possible to merge this? Or are there any changes that you think should be applied?