Move away from Typeform

I can't find a way to include Typeform and save details properly. The only way is by having PRO+ (expensive)... Any suggestions? I found this as well: https://github.com/space10-community/conversational-form
It looks like a nice replacement for the Typeform form. What do you think?

Ho veig poc intuitiu pels usuaris. Complica coses com respondre en desordre i el canviar una resposta anterior.

pots fer toggle pero. De fet es l'approach que te HackTheNorth per aixo ho deia

@alvarogirona this is a discussion, I never intended to have it as a task yet

Tellform also seems like a good replacement. Open-source and self-hosted. https://github.com/tellform/tellform
The examples aren't working on their website, but here is a gif showing how it looks like: https://qph.ec.quoracdn.net/main-qimg-bc9cf4d0abd70a94306e6c12f88ace1d

There’s no file upload field [yet]

On Jul 5, 2017, at 16:57, alvarogirona<EMAIL_ADDRESS>wrote:
Tellform also seems like a good replacement. Open-source and self-hosted. https://github.com/tellform/tellform https://github.com/tellform/tellform
The examples aren't working on their website, but here is a gif showing how it looks like: https://qph.ec.quoracdn.net/main-qimg-bc9cf4d0abd70a94306e6c12f88ace1d https://qph.ec.quoracdn.net/main-qimg-bc9cf4d0abd70a94306e6c12f88ace1d
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/hackupc/backend/issues/107#issuecomment-313249243, or mute the thread https://github.com/notifications/unsubscribe-auth/AGl6TWGs8a5lAMfMgVZ4JGI_1rs7kp2Lks5sLBTYgaJpZM4OGEEp.

We are keeping Typeform, at least until something better appears. Long life to Typeform


Added note about SMS and MMS default rate limits being the same

For the Committer

[ ] I made sure that the site looks great and functions perfectly live
[ ] I ran splell check
[ ] I'm ready for these changes to be made live

For the Reviewer
General Review

[ ] All changes/updates requested were intentionally changed or added (no extraneous file or partial updates)
[ ] The live rendered page behaves and looks like intended.
[ ] All links work as intended. (click every link to make sure that it takes the user to the expected place).
[ ] The markdown was rendered to HTML as intended. (Tables look right, code samples are gated properly).
[ ] Any style or CSS changes are tested on multiple different pages to ensure nothing unexpected broke or changed.
[ ] I proof-read the live site (gitbook serve) and there are no oblivious splelling or grammer misteaks.

Gitbook Specific

[ ] Any new documentation pages have been added to the SUMMARY.md file so they are rendered to HTML.
[ ] Any links to other pages within this documentation use relative links ([read more about ...](guides/voice/voicemail.md)).
[ ] Gitbook can install and build the documentation (gitbook install & gitbook build)

Code Specific

[ ] All code has been tested against the live API.
[ ] All code can be run without throwing errors or new warnings.
[ ] All code is formatted correctly and consistently (spaces, tabs).
[ ] All code is legible and idiomatic to the language.
[ ] All code uses sensical method, function, and variable names.
[ ] All code samples use the appropriate syntax highlighting.
[ ] Any examples re-use same phone numbers, uuids, variable names, etc... throughout (IE don't have something like {from: '+19191231234', to: '+19191231234'} unless it's meant to show the same phone number calling/texting itself ).

TL;DR

[ ] I did these things
[ ] I'm ready for these changes to be made live

 Specify difference between SMS and MMS rate limits

Preview Changes at:
http://bw-apdocs-specify-sms-mms-default-rate-limit.s3-website-us-east-1.amazonaws.com/


Fixed missing Pull Request Stats

Thank you i've been meaning to make an issue about this :)

Awesome! Great work

Glad to help :D


Beta website transition

Phase 1

[x] Set custom domain for CF pages (changes DNS from Netlify): https://dash.cloudflare.com/950816f3f59b079880a1ae33fb0ec320/pages/view/website/domains
[x] Set-up CF deploy from production branch
[x] Move dxos-demo app to CF pages
[ ] Transition composer.space domain
[ ] Move composer-app pages + worker to new domain

Auth

[ ] Bypass gate when sending invitations (device and space members)
[ ] Automatically auth new (invited) users

Next

[ ] Signup form redirect issue client/server side rendering?
[ ] Errors: Uncaught Error: Text content does not match server-rendered HTML.

Product

[ ] Rewrite outbound email templates
[ ] Rewrite landing page after signup

Bought composer.space from Namecheap (CF doesn't support .space)
Cannot transfer for 60 days
Added CF nameservers to via Namecheap registrar:

https://dash.cloudflare.com/950816f3f59b079880a1ae33fb0ec320/composer.space

Configured DNSSEC:

https://dash.cloudflare.com/950816f3f59b079880a1ae33fb0ec320/composer.space
https://www.namecheap.com/support/knowledgebase/article.aspx/9722/2232/managing-dnssec-for-domains-pointed-to-custom-dns


Inline css-color-names, url types, declare loader globals

Last batch of miscellaneous typing issues for packages:

Inline the css-color-names package (this is basic object)
Create types for @pixi/utils.url package
Add missing defined Loader globals

Codecov Report

Merging #7059 (452fab6) into dev (0c48db9) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               dev     #7059   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           17        17
  Lines          704       704
=========================================
  Hits           704       704

Continue to review full report at Codecov.

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


Need to create a license file for this repo

This also extends to making recommendations for the licence of any linked model / weight file.
For simplicity, I would probably go for the same licence as NiftyNet for the repo / models and a cc-by or cc0 for the weights.
I't unclear however how we should keep track of the licence in each of the models  and weights.

See also https://github.com/NifTK/NiftyNet/issues/180

Also note that license for pre-trained weights might be slightly challenging as it might depend on the license of the original data use to obtain the weights (derived work?)


[Bug]: shopify theme dev - cors error Shopify Assets

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
No Cors Error?
Actual behavior
Cors Error.

Verbose output
CeriM@DESKTOP-76ILN69 MINGW64 /c/LocalWeb/Shopify/C W Sellors/Main Theme/0-main (production)
$ shopify theme dev --store=cwsellors-test.myshopify.com --verbose
2023-10-31T09:49:26.284Z: Running command theme dev
  shopify:theme:dev init version<EMAIL_ADDRESS>argv: [ '--store=cwsellors-test.myshopify.com', '--verbose' ] +0ms
2023-10-31T09:49:26.309Z: Ensuring that the user is authenticated with the Theme API with the following scopes:
[]

2023-10-31T09:49:26.311Z: Ensuring that the user is authenticated with the Admin API with the following scopes for the store cwsellors-test.myshopify.com:
[]

2023-10-31T09:49:26.312Z: Getting session store...
2023-10-31T09:49:26.316Z: Validating existing session against the scopes:
[
  "openid",
  "https://api.shopify.com/auth/shop.admin.graphql",
  "https://api.shopify.com/auth/shop.admin.themes",
  "https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
  "https://api.shopify.com/auth/shop.storefront-renderer.devtools",
  "https://api.shopify.com/auth/partners.app.cli.access",
  "https://api.shopify.com/auth/destinations.readonly"
]
For applications:
{
  "adminApi": {
    "scopes": [],
    "storeFqdn": "cwsellors-test.myshopify.com"
  }
}

2023-10-31T09:49:26.319Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2023-10-31T09:49:26.320Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.50.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: win32
 - Content-Type: application/json

2023-10-31T09:49:26.552Z: Request to https://accounts.shopify.com/oauth/introspection completed in 219 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"5e48e7b9d08aa3d69b72ae1d01ffc6ff"
 - x-request-id: 6c95b54e-0b21-4ae1-a3be-6db7e0846cfc

2023-10-31T09:49:26.558Z: The identity token is valid: true
2023-10-31T09:49:26.559Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2023-10-31T09:49:26.559Z: The current session is valid but needs refresh. Refreshing...
2023-10-31T09:49:26.561Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_CjQIiZuDqgYQqdODqgZSJggBEhBg9qEZ4alHt4WTTKK_cmpHGhBOP1r-JgFLrrYkjhlPzhB_EkAbGcOqgj8GU88vlqmDRXkxYxzq43olcEtt8OltOTHv7F4iCibLIcKkZfUP8LX0HLG1GC9AXqEEyCLIdUU_T6wP&refresh_token=atkn_CiEIiZuDqgYQibWhqwaiARIKEE4_Wv4mAUuutiSOGU_OEH8SQHGHLqwkhMmfs40pXJ8FTR5aeI3BKWSxljm1YMuVAX8QyDKJeKl1ho6Tu6EF7AbEubybaF7jkFb0WyvXcjidVQI&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3
With request headers:
 - User-Agent: Shopify CLI; v=3.50.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: win32
 - Content-Type: application/json

2023-10-31T09:49:26.822Z: Request to https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_CjQIiZuDqgYQqdODqgZSJggBEhBg9qEZ4alHt4WTTKK_cmpHGhBOP1r-JgFLrrYkjhlPzhB_EkAbGcOqgj8GU88vlqmDRXkxYxzq43olcEtt8OltOTHv7F4iCibLIcKkZfUP8LX0HLG1GC9AXqEEyCLIdUU_T6wP&refresh_token=atkn_CiEIiZuDqgYQibWhqwaiARIKEE4_Wv4mAUuutiSOGU_OEH8SQHGHLqwkhMmfs40pXJ8FTR5aeI3BKWSxljm1YMuVAX8QyDKJeKl1ho6Tu6EF7AbEubybaF7jkFb0WyvXcjidVQI&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3 completed in 257 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"2d6f4fc938084532a38bef9c592c796e"
 - x-request-id: 7534ab54-77c0-4ebf-b0bb-534b6519947d

2023-10-31T09:49:26.827Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=271e16d403dfa18082ffb3d197bd2b5f4479c3fc32736d69296829cbb28d41a6&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=****
With request headers:
 - User-Agent: Shopify CLI; v=3.50.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: win32
 - Content-Type: application/json

2023-10-31T09:49:26.829Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=ee139b3d-5861-4d45-b387-1bc3ada7811c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=****
With request headers:
 - User-Agent: Shopify CLI; v=3.50.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: win32
 - Content-Type: application/json

2023-10-31T09:49:26.830Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=32ff8ee5-82b8-4d93-9f8a-c6997cefb7dc&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fdestinations.readonly&subject_token=****
With request headers:
 - User-Agent: Shopify CLI; v=3.50.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: win32
 - Content-Type: application/json

2023-10-31T09:49:26.833Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=7ee65a63608843c577db8b23c4d7316ea0a01bd2f7594f8a9c06ea668c1b775c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.graphql+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.themes+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.collaborator-relationships.readonly&subject_token=****&destination=https%3A%2F%2Fcwsellors-test.myshopify.com%2Fadmin
With request headers:
 - User-Agent: Shopify CLI; v=3.50.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: win32
 - Content-Type: application/json

2023-10-31T09:49:27.055Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=271e16d403dfa18082ffb3d197bd2b5f4479c3fc32736d69296829cbb28d41a6&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=**** completed in 219 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"1b0fd86a7d5d5a73b8ac2d7053e33185"
 - x-request-id: d1f38c73-5562-4ad9-a001-4dce2ab52b15

2023-10-31T09:49:27.061Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=7ee65a63608843c577db8b23c4d7316ea0a01bd2f7594f8a9c06ea668c1b775c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.graphql+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.themes+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.collaborator-relationships.readonly&subject_token=****&destination=https%3A%2F%2Fcwsellors-test.myshopify.com%2Fadmin completed in 220 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"9c6401890985f84dcd9d95dfa55549b8"
 - x-request-id: 8e23da4f-98e9-4a78-bf1e-1957749513e0

2023-10-31T09:49:27.065Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=32ff8ee5-82b8-4d93-9f8a-c6997cefb7dc&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fdestinations.readonly&subject_token=**** completed in 226 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"252916bc9a15fcbb1a21b830d8a6ef68"
 - x-request-id: 8715fff4-08c7-4e4a-a78b-c8138473b909

2023-10-31T09:49:27.070Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=ee139b3d-5861-4d45-b387-1bc3ada7811c&scope=https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=**** completed in 232 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"7bfaac948d32e6a0b6f302fbbdc90b3d"
 - x-request-id: 2f18acee-cb7c-47a1-8e54-4b9dc38f51aa

2023-10-31T09:49:27.074Z: Setting session store...
2023-10-31T09:49:27.082Z: Ensuring that the user is authenticated with the Storefront API with the following scopes:
[]

2023-10-31T09:49:27.083Z: Getting session store...
2023-10-31T09:49:27.090Z: Validating existing session against the scopes:
[
  "openid",
  "https://api.shopify.com/auth/shop.admin.graphql",
  "https://api.shopify.com/auth/shop.admin.themes",
  "https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
  "https://api.shopify.com/auth/shop.storefront-renderer.devtools",
  "https://api.shopify.com/auth/partners.app.cli.access",
  "https://api.shopify.com/auth/destinations.readonly"
]
For applications:
{
  "storefrontRendererApi": {
    "scopes": []
  }
}

2023-10-31T09:49:27.093Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2023-10-31T09:49:27.094Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.50.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: win32
 - Content-Type: application/json

2023-10-31T09:49:27.295Z: Request to https://accounts.shopify.com/oauth/introspection completed in 198 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"73fba92704e63475dfa7b50a9491a12a"
 - x-request-id: ac189b4c-9613-4a80-8560-5033e31916fb

2023-10-31T09:49:27.298Z: The identity token is valid: true
2023-10-31T09:49:27.298Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2023-10-31T09:49:27.343Z:
Running system process:
  · Command: ruby -v
  · Working directory: C:/LocalWeb/Shopify/C W Sellors/Main Theme/0-main

2023-10-31T09:49:27.402Z:
Running system process:
  · Command: bundle -v
  · Working directory: C:/LocalWeb/Shopify/C W Sellors/Main Theme/0-main

2023-10-31T09:49:27.912Z: Reading the content of file at C:/Users/CeriM/AppData/Roaming/npm/node_modules/<EMAIL_ADDRESS>2023-10-31T09:49:27.945Z:
Running system process:
  · Command: bundle config set --local path C:\Users\CeriM\AppData\Local\shopify-gems-nodejs\Cache
  · Working directory: C:/Users/CeriM/AppData/Roaming/npm/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby

2023-10-31T09:49:28.504Z:
Running system process:
  · Command: bundle config set --local without development:test
  · Working directory: C:/Users/CeriM/AppData/Roaming/npm/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby

2023-10-31T09:49:29.048Z:
Running system process:
  · Command: bundle install
  · Working directory: C:/Users/CeriM/AppData/Roaming/npm/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby

2023-10-31T09:49:30.019Z:
Running system process:
  · Command: bundle exec ruby C:/Users/CeriM/AppData/Roaming/npm/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/bin/shopify theme token --admin atkn_CvsCCKabg6oGEMbTg6oGYuwCCAESEGtxj16DU0IkvT4letrgNlMaqAFodHRwczovL2FwaS5zaG9waWZ5LmNvbS9hdXRoL3BhcnRuZXJzLmNvbGxhYm9yYXRvci1yZWxhdGlvbnNoaXBzLnJlYWRvbmx5IGh0dHBzOi8vYXBpLnNob3BpZnkuY29tL2F1dGgvc2hvcC5hZG1pbi5ncmFwaHFsIGh0dHBzOi8vYXBpLnNob3BpZnkuY29tL2F1dGgvc2hvcC5hZG1pbi50aGVtZXMgDSinUzIQzOrppsu8R_W5MKjc2xHY9TokNGVjOTA3NzAtNDViYy00YzFhLWEwMDMtMzYwNjRlMWI5OTViQgdBY2NvdW50ShCuZR1c3bVP0pdS2beiwWe1UlN7InN1YiI6ImZiZGIyNjQ5LWUzMjctNDkwNy04ZjY3LTkwOGQyNGNmZDdlMyIsImlzcyI6Imh0dHBzOi8vYWNjb3VudHMuc2hvcGlmeS5jb20ifRJAlZj11D3iE7rvoh_qwaeRH05vXBuxMC6STILEKrNpIrtRquSidXR3W1nViuMMZwNi0WNNvKb2I48hoZmVMopDBQ --sfr atkn_Cv8BCKabg6oGEMbTg6oGYvABCAESELXn_ZOtJkqqtsbh4w6iASoaPmh0dHBzOi8vYXBpLnNob3BpZnkuY29tL2F1dGgvc2hvcC5zdG9yZWZyb250LXJlbmRlcmVyLmRldnRvb2xzINhSKKdTOiQ0ZWM5MDc3MC00NWJjLTRjMWEtYTAwMy0zNjA2NGUxYjk5NWJCB0FjY291bnRKEK5lHVzdtU_Sl1LZt6LBZ7VSU3sic3ViIjoiZmJkYjI2NDktZTMyNy00OTA3LThmNjctOTA4ZDI0Y2ZkN2UzIiwiaXNzIjoiaHR0cHM6Ly9hY2NvdW50cy5zaG9waWZ5LmNvbSJ9EkDD_4djFgehbtHXX19c0P0dV5w5G-GRU03b4Eho2oZ9xxalype6v2ZW_xhVRvNNctH9rHUD-QLVtg5q7pbqZxsN
  · Working directory: C:/LocalWeb/Shopify/C W Sellors/Main Theme/0-main

2023-10-31T09:49:31.780Z: Getting development theme...
2023-10-31T09:49:32.105Z: Request to https://cwsellors-test.myshopify.com/admin/api/unstable/themes/162783723831.json?fields=id%2Cprocessing completed in 322 ms
With response headers:
 - content-type: application/json; charset=utf-8
 - x-request-id: dc8bb1a2-628d-4d9d-bcab-1c29af3be654

╭─ success ────────────────────────────────────────────────────────────────────╮
│                                                                              │
│  Preview your theme                                                          │
│    • http://<IP_ADDRESS>:9292 [1]                                               │
│                                                                              │
│  Next steps                                                                  │
│    • Customize your theme at the theme editor [2]                            │
│    • Share your theme preview [3]                                            │
│      (https://cwsellors-test.myshopify.com/?preview_theme_id=162783723831)   │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯
[1] http://<IP_ADDRESS>:9292
[2] https://cwsellors-test.myshopify.com/admin/themes/162783723831/editor
[3] https://cwsellors-test.myshopify.com/?preview_theme_id=162783723831

2023-10-31T09:49:32.189Z:
Running system process:
  · Command: ruby -v
  · Working directory: C:/LocalWeb/Shopify/C W Sellors/Main Theme/0-main

2023-10-31T09:49:32.241Z:
Running system process:
  · Command: bundle -v
  · Working directory: C:/LocalWeb/Shopify/C W Sellors/Main Theme/0-main

Reproduction steps

Spin up the Shopify CLI "shopify theme dev"
Open up Firefox
Look at console

Operating System
Windows 11
Shopify CLI version (check your project's package.json if you're not sure)
3.50.0
Shell
Git Bash
Node version (run node -v if you're not sure)
v18.12.1
What language and version are you using in your application?
N/A

I'm having the same issue. When I run shopify theme dev, the preview URL (<IP_ADDRESS>:9292) will not resolve on Chrome:

I think this is related. This asset just hangs as pending

I don't see any CORS errors but it's the only asset that has Sec-Fetch-Mode set to cors. It prevents reloading of the page unless I block the Request URL in the devtools.

Is there any updates on this? I'm getting this on fonts and images

Bumping this again, still having this issue.

Bumping again

+1

Bump


Add new services to produce

Checklist

[ x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[ x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[ x] I've read the Contribution Guidelines
[ x] I've updated the documentation if necessary.

Motivation and Context
iOS 12 added Access WiFi Information entitlement. Support for this was added to spaceship.portal.app_service but the triggers were not updated. Updating them in this PR.
Description
Allow produce to enable/disable access_wifi service
Added the following options to produce enable_services
--access-wifi          Enable Access WiFi
Added the following options to produce disable_services
--access-wifi         Disable Access WiFi
As per joshdholtz comments, the previous changes failled because they are expecting Spaceship.app_service.access_wifibut it is actually Spaceship.app_service.access_wi_fi because of the capital F on the line of code I changed above. If you change AccessWiFi to AccessWifi then the code will work 😊

I've updated my email adr on my github account. the cla/google should pass now

Unfortunately not as you PR also includes a commit from @TaimurAyaz. Where did this one come from - did you both commit to the same branch?

Ah, found the original PR. I added the required change to https://github.com/fastlane/fastlane/pull/13552, we will continue there.


SolutionPackager - Unpack solution build task

There is a SolutionPackager Package Task available in the build tasks.
It would be great to have a SolutionPackager Unpack Task as well.
This would be used for extracting unmanaged solutions from a specific development environment, unpack it, and then check it into source control for change management and backup purposes.

@bo-stig-christensen would you not rather has this done by a member of the team when certain requirement is completed or milestone is reached? This way you can see conflicts (if any) and have control over the operation.

@WaelHamze Actually, I would like to automate this as much as possible.
I have build, unit testing, deployments and integration tests close to fully automated in VSTS, so basically a complete CD pipeline. During this process, I want to ensure that I catch any customization changes done, so I back up the extracted solution to a separate "CRM Backup" repo for each project. - This ensures that I always have a quite accurate customization history for the solution.
I am aware that the most interesting backups are the "milestones" or "feature completed" checkpoints, which I am thinking that I can tag in git or similar.
I have a vision of developing a solution for CRM to hook into messages related to customizations such as PublishAll and similar to kind of have Change Logging backed by Git, but that's the next step in evolution for a later point in time ;-)
I guess that the implementation of this task would be basically a copy of the SolutionPackager Pack task, but with Unpack parameters :-)

@bo-stig-christensen this task is almost ready just confirm the above so I can release

Released to Marketplace 9.0.24. Let me know if any issues.


Adding suffix breaks the mask on initial value

If you set a suffix then the input is not formatted correctly. For example <input type="text" value="20316.22">  with a suffix as say '  c' is displayed on initialization wrongly as: 203.16 c
You call mask initially as
$('input').maskMoney('mask', 20316.22);

I'm working on a new release, but this bug is fixed in master already :)

Thanks for the update. The fix partially works. It fails if the decimal point ends with zero. Let me explain:
var $input = $("#input1");
$input.maskMoney({suffix: " €"});
// the following correctly converts to 20,316.22 €
$input.maskMoney("mask", 20316.22);

// the following wrongly converts to 2,031.62 €
$input.maskMoney("mask", 20316.20);

@kartik-v yep. actually, the bug you reported is fixed. adding a zero to the end just make us hit another one(one that I'm working on ;) )


Surveillance report download feature

Dummy button implemented, which downloads local stub_download.json file. Closes #72
@anwarMZ Please change stub_download.json file contents to a surveillance report we can actually use until pipeline integrated

@ivansg44 does this allow multiple file download option or just one file? We will have > 10 files to download

This allows 1 file. Please create directory with all files and then I will change it.

Thanks @ivansg44 ! great work. I have updated surveillance reports here - #89


Upload limit, and broken build isn't handled well by deliver command.

It seems Fastlane Deliver not only does not give an appropriate message where it hits the upload limit (try again in 1 day message). Furthermore it fails, continually trying again when later trying to submit-for-review a version that was uploaded, hit the upload limit, and requires a new version number because the current version is "duplicate" when uploaded, yet never shows up in the builds activity in iTunes-connect.
Similarly, if the build is stuck at "There was an error importing this build. View all builds in Activity." in the activity/ios/builds url screen, the Deliver command just continually says:
[16:59:00]: You can tweet: "iTunes Connect #iosprocessingtime x minutes"
[16:59:32]: Waiting iTunes Connect processing for build (versionnumber)... this might take a while...
[16:59:32]:
[16:59:32]: You can tweet: "iTunes Connect #iosprocessingtime (x+1) minutes"
[17:00:04]: Waiting iTunes Connect processing for build (versionnumber)... this might take a while...
....

continually.
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?
No
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?
No

Hi @programmin1! Thanks for reaching out. Can you run deliver --verbose and send the full output. Definitely want to take a look 👍

Here are the steps -

Upload a build that happens to trigger the "Upload limit reached". Let's say it were some version "1.2.3". Now the build 1.2.3 shows nowhere on iTunes Connect yet you can't upload that version ("Redundant Binary Upload").
Run:

deliver submit_build --verbose -u username@somewhere --skip_metadata --skip_binary_upload --skip_screenshots --submit_for_review -a IDoftheapp

Instead of detecting that this isn't even showing up on iTunesConnect, and showing that you have to create a new version number, deliver would endlessly wait after login and summary:
INFO [2016-05-04 14:27:41.70]: [32mFinished the upload to iTunes Connect[0m
INFO [2016-05-04 14:27:42.42]: Selecting the latest build...
INFO [2016-05-04 14:27:43.51]: Waiting iTunes Connect processing for build 1.2.3 (1.2.3)... this might take a while...
(message repeated again and again)


feat(sqlcheck): SQL check supports affected  rows

What type of PR is this?
feat
What this PR does / why we need it:
SQL check supports affected  rows

add meta info and rule applying
affected rows check logic

Which issue(s) this PR fixes:
Special notes for your reviewer:
Additional documentation e.g., usage docs, etc.:

please add unit test cases for your code

Why is the target branch not dev/4.3.x?

Select is not included in the scope of check at present. From the explanation of affecting the number of lines, select does not affect the database in essence, but only retrieves. This is also consistent with competitors.

Why is the target branch not dev/4.3.x?

merging process: feat/yizhuo_43x_sql_infect_rows --> feat/sql_infect_rows --> dev/4.3.x

test scenarios is very important for sql check feature.
how about select into ?

Select is not included in the scope of check at present. From the explanation of affecting the number of lines, select does not affect the database in essence, but only retrieves. This is also consistent with competitors.

please add unit test cases for your code

OK, done.

lgtm, please implement select .. into affected rows check in separated PR

got it.


error on /leap/train-model { status: 520, statusText: '' }

[POST]
/leap/train-model
Time
November 01 19:36:08.56 GMT+05:30
Request Path
/leap/train-model
Host
picmaker.app
Request ID
fvct9-1698847564533-4f135877464d
Request User Agent
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Level
Error
Environment
production
Branch
main
Type
Serverless Function
Function
/leap/train-model
Location
Washington, D.C., USA (iad1)
Runtime
Node.js 18.x
{ status: 520, statusText: '' }

Managed to fix it.
Turns out that error message was that API key is not in right format, which is wierd, API is provided by Leap.
Digging their discord channels, I found out you need to click "Try Legacy Dashboard", which I assumed it just older UI version but now, there is whole section there that is missing in default UI, its about training models, and also generating API tokens for traning models. Using this this new API token, from legacy dashboard fixed 520, and 401 error.
Very poor user experience by Leap.


Showing the filtering_id in the attribution-internals UI

When a trigger is registered using the filtering_id within aggregatable_values, it can be retrieved by decoding the debug_cleartext_payload key. However, the filtering_id does not appear in the "Aggregatable reports" tab in the UI at chrome://attribution-internals/ . As a result, there is no way to easily check that the filtering_id was correctly set, which is especially important when the debugging mode will go away.

This is being addressed in https://chromium-review.googlesource.com/c/chromium/src/+/5939817.


BUG - Report generation on any email or hash iType crashes the app

BUG - Report generation on any email iType crashes the app with:
TypeError: Cannot read property 'value' of undefined
downloadFullReport
src/Util/ReportGenerator.js:25
  22 | }
  23 |
  24 | export const downloadFullReport = (result) => {
> 25 |   downloadNamedTextFile(`${result.integrations.indicatorData.value}_${currentTimeStamp()}`, generateFullReport(result))
  26 | }
  27 |

Resolved. closing


Store showID in config file

Instead of each time retrieving the showID, store it and spare HTTP requests.

The time that this enhancement saves is merely 2 seconds. Unless someone has a need for this, the issue won't be worked on.


Advanced data visualizations

Baseballsavant-style percentile plots

https://baseballsavant.mlb.com/savant-player/aaron-judge-592450?stats=statcast-r-hitting-mlb

Any others as decided later on (TBD)
Decide on library to use with compatibility with WPF

This should show for the current/most recent season
There should be a couple different versions of this:

Percentiles for the game stats like POW, CON, SPD, etc
Percentiles for the actual stats like HR, Hits, Strikeouts, etc


The Hyperdrive Daemon is Not Active

I often see this error message in my Beaker Browser:
The Hyperdrive Daemon is Not Active
The "daemon" runs Beaker's Hyperdrive networking.
Restart the Daemon
It works well for a while after start, then the daemon crashes and shows this error message. After clicking to "Restart the Daemon" button, the daemon is unable to restart, I just see the endless spinner icon.
Environment

OS: Ubuntu 20.04.1 LTS
Beaker Version: 1.0.0-prerelease.7

We had some finnicky behavior with the hyperdrive-daemon and we're replacing it with the new hyperspace daemon in the next release, hopefully that will help


Move ReconnectingChannel's async close to its own Executor.

Per the commit comments for shutdown() and awaitTerminated(), they can
sometimes hang. As a result, we should move close to its own
ExecutorService so that we don't block a Call from completing (which
could in turn complete channel shutdown).

@AngusDavis: I'm merging this.


Low Quality Artwork For Music

So I've attempted to solve this myself with no luck, but the artwork that is acquired at the time of ripping a CD is like 250x250 in size. When viewing on a 55" 4k/1080p display, it really doesn't look good. It's better right now to just disable the artwork and let the tools like Plex/Emby to download them for me.
I would prefer to have the artwork grabbed at the time of the rip, but it really needs to be a minimum of 800x800... 1000x1000 resolution would be preferable.

Are there any options in .abcde?  If not @muckngrind4 added the ability to make an API call to Emby to tell it to do a library rescan once a video rip completes, there's no reason we couldn't do something similar post audio cd rip.  Would that work?

http://www.andrews-corner.org/linux/abcde/getalbumart.html
I've tried implementing part of that guide, cause it seems possible. But I was only able to achieve resizing the small image to a desired size. Which wasn't the desired result, but maybe I wasn't reading or implementing it correctly...

I think the best we can do is #26 where Emby can be configured to scan the library post fix.  I'm going to go ahead and close this, but if you can think of a better way to do this we can re-open it.


Update Windows VMImage Version

Update all windows machines to windows2019

Can one of the admins verify this patch?

What about the other pipelines? https://github.com/Azure/azure-sdk-for-python/search?q=vs2017-win2016&unscoped_q=vs2017-win2016

What about the other pipelines? https://github.com/Azure/azure-sdk-for-python/search?q=vs2017-win2016&unscoped_q=vs2017-win2016

Thanks, I didn't realize there were more.


add texture array support to vulkan readback

add in numLayers to ReadBackVK utility class so that it properly copies texture arrays when called by bgfx::readTexture.
tested in examples-20-picking to still work
The ReadBackVK class could probably be made to be more elegant as well as to handle texturecube but I don't have a good test-case for that.

cc @pezcode

Make sure this have the same behavior on other backends too.

Make sure this have the same behavior on other backends too.

it should for opengl
looking at metal it seems to be the same behavior
more importantly since readTexture only accepts mip as an argument, the expected behavior should be to copy all of the data and not just a single slice of the array. otherwise no other way to get the data

more importantly since readTexture only accepts mip as an argument

I think maybe API should change... Intention was always to read single 2D slice, not complete chain. Something like:
	uint32_t readTexture(
		  TextureHandle _handle
		, void* _data
		, uint16_t _layer
		, uint8_t _mip
		);


Kwxm/l machine

Here's the lazy machine. There are several things that will need to be fixed eventually.

The handling of built-in functions is a bit messy: this can be sorted out when the interface has been finalised. I've been chasing Roman's changes for some time which has necessitated frequent rebasing. Some of git's behaviour has been rather confusing (conflicts reappearing many times), so I'd like to get it merged to avoid any more of that.

I've kept the structure as simple as possible to make it easy to see how it works. Some of the state could be put in a monad (the heap, and the table of dynamic built-ins, when that's stabilised), but that can be done later.

It's throwing exceptions rather than returning error results. This interacts with the built-in stuff again, so that can also be fixed later.

Some of git's behaviour has been rather confusing (conflicts reappearing many times)

A few tips to help avoid this:

If you have several commits that touch the same code this can happen. A good way to avoid this is to just squash the commits together during an interactive rebase, that way when you rebase on someone else's branch you're just applying the one commit.
You may want to enable git rerere, which remembers how you resolved commits previously.

Looks like the plutus-core-interpreter tests don't pass either.

In general I highly recommend aggressively squashing your commits down, it makes everything easier including reviewing.

The interpreter tests work ok with nix....

Are you sure? Also note that it's a property test failure, so maybe the seed is different. You can see the failed run here: https://hydra.iohk.io/build/346927/nixlog/1

Sorry about the squashing as well.  I'll try to remember that in future.  I see that it seems to have replayed many commits for some reason.  Rebasing was a bit of a nightmare (and I do have rerere enabled)

You can squash them now and force push your branch and it will all work fine, I do it all the time.

The CI fails with
            LMachineException "ConstAppFailure" (Apply () (Apply () (TyInst () (Builtin () (BuiltinName () MultiplyInteger)) (TyInt () 2)) (Constant () (BuiltinInt () 2 4748))) (Constant () (BuiltinInt () 2 2090)))

That's because the generated integers are just too big and their product does not fit into the size. I do not understand how that is possible at all and why it does not fail on master like that. I'll look into it.

Oh, wait, no, it's trivial. You simply should not throw in case of ConstAppFailure. You should return Failure in that case. That's what the CEK machines does.

Ach, you're right.  It was doing that, but I stupidly took it out when I was putting in the exceptions.

@kwxm let me know when you've done all the things you're planning to do in this PR and I'll take another look. Feel free to leave bigger improvements for later.


How do I use the definition node?

Sorry. But I searched everywhere but couldn't find any examples, demos. None of the other libraries mentions such a thing. In among the list of supported nodes, there is a 'definition' node. What is it & how does it work?

See the documentation for mdast which describes definition https://github.com/syntax-tree/mdast#definition
For a walk through try https://commonmark.org/help/tutorial/07-links.html


Use BoringSSL instead of OpenSSL

This is a prerequisite for solving #4199 (which is essentially #4121), because a dynamic framework can't be created with precompiled libraries.
It fixes #4081 and any future issue of the sort, because the BoringSSL pod works from sources.
And removes steps 6, 7, 8 and 9 from #3492, because it eliminates the 15 - 20 min of time building OpenSSL the first time one does pod install (which times out run_tests.sh). By the same token, it should speed up Travis builds considerably.

The travis build failed.

It's weird, it used XCode 6.1 for those builds, instead of 7...

Restarting them made them use the correct XCode and pass. The change took 10min off each of the 3 tests. Half of what remains is compiling protoc, and the other half is probably compiling OpenSSL for the test server.

For the record, this also fixes #4295, which happens every time OpenSSL is released and lasts O(day) until the OpenSSL podspec maintainer updates it.


Add prefix/postfix operators to the built-in operator tables

Also add lookup functions prefixOperator and postfixOperator.

@swift-ci please test


Update gdpr-dsr-Dynamics365.md

Adding link to GDPR info for Dynamics 365 Customer Service Insights

@herviicban - can you please assist to check, approve and merge the content for this PR?
Thank you.


Possible Baseline Numbering Bug

Clean fails when more than 217 ( possible actual cutoff is 256) baselines used to attempt to image data.
Could this be from i,j pair to baseline number mapping or a lower level issue?

Which package does clean fail under? CASA? or PAPER?

I have had little luck looking into CASA examples for tutorials with large amount of baselines.
I also wanted to go back and take a look at the in the uvfits files to make sure there was something there.
One of CASA's errors was the PSF is zero and to make sure your data exists.
pyuvdata version 0.0.1 can read the simulated HERA 217 and returns 408 baselines for a single time stamp ( the data array has shape (408,1,128,1)) but returns an error when trying to read the HERA 331 simulation stating the key "BASELINE" doesn't exist.
At this point I'm not sure if this is an appropriate bug for pyuvdata or PRISim.
Here is an image of my IPython workbook when trying to read the PRISim simulations.

Thank you, that's very helpful. The important piece is that BASELINE doesn't exist. Can you send me or post the header from your uvfits file?

So BASELINE is supposed to be absent for files with more than 256 antennas. For large arrays, the baseline array is meant to be replaced by the antenna1 & antenna2 arrays. I wonder if there's a quick way to find out if CASA is meant to support files with > 256 antennas.

I think CASA is not (yet) able to import from UVFITS datasets with more than 256 antennas -- see MSFITSInput.cc in the CASACORE package, function _extractAntennas

Supposedly the uvfits format specifically accounts for >256 by switching to using ant1,ant2 instead of baseline.  The problem is that CASA does not follow this spec.

@dannyjacobs Do you have a student who can look into this?  We're wondering if three years later the newer versions of CASA have resolved this.

I'm almost positive that Carilli showed that this was at least partially
not true. They've been doing SKA and maybe ngVLA sims with more than 256
antennas. I suggest we close and re-open if new evidence emerges to the
contrary.
On Wed, Jul 8, 2020 at 8:31 AM Jonathan Pober<EMAIL_ADDRESS>wrote:

@dannyjacobs https://github.com/dannyjacobs Do you have a student who
can look into this? We're wondering if three years later the newer versions
of CASA have resolved this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RadioAstronomySoftwareGroup/pyuvdata/issues/85#issuecomment-655592396,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAPNV7OY56Z3ADYIRNITALR2SGMFANCNFSM4COYXR6A
.

--
Arizona State University
School of Earth and Space Exploration
Low Frequency Cosmology
Phone:<PHONE_NUMBER>
Homepage:     danielcjacobs.com

My last info from Chris was that CASA could handle >256 antennas internally (and in their own simulations) but that it could not read in uvfits files with >256 antennas.

Bryna's understanding was correct. Casa could handle Nants > 256 but the uvfits reader could not. Maybe we should just get pyuvdata into casa builds :laughing:

Actually, with casa 6, I think one can now install via pip/conda. We could actually integrate cross-wise.

I did a brief test with the new MS writer released as part of v2.2.2, synthesizing a UVData object that contained 1024 antennas (and 524800 baselines), and it looks as though this is no longer an issue provided that you write out directly to the measurement set format vs going by way of UVFITS and importuvfits. As originally suggested by @jpober, I think with a little documentation update and an added warning to the UVFITS writer, I think this one could potentially be closed out.


b4 submission space

confirmed:B4
address:2wop9Ywhjf99zbSUyWRWz2GzyfzEV1F1oX2LKRVFh1q19PGhTp
baker:398

confirmed:B4
address:2wop9Ywhjf99zbSUyWRWz2GzyfzEV1F1oX2LKRVFh1q19PGhTp
baker:398


Remove all existing taxon tags

The education taxonomy is currently very alpha - it's not visible to the public
yet.
The finding things team has just completed a bulk tagging exercise with
publishers so we want to clear all existing tags and import the new ones.
This change removes those tags (links with type taxons).
There will be a follow up change to clear out remaining taxon content items,
that do not belong to the current taxonomy (i.e. there is no chain of
parent_taxon links linking them).

@kevindew There's no schema changes, just a delete on the links table :)

@MatMoore despite that we still hit a problem if the db/schema.rb timestamp is not up to date with the last migration.
The scenario is as follows:

We have a config that prevents you running the app in development with pending migrations
We have the end-to-end test suite that runs in development environment
This builds the db based on the timestamp in db/schema.rb and then these fail because Publishing API has a pending migration

which probably goes some way to explaining why we're hoping to separate out data migrations from schema ones 😉

Oops - sorry, I missed that rails was still updating that version number. Have added that in.

Late to the party - but great branch name 😀


jamovi: update to accomodate new manifest location

Purpose
the jamovi file format is placing the manifest in a different location (it turns out putting it at META-INF/MANIFEST.MF makes you the enemy of every email system).
Changes
trivial changes, it now reads the new path, before falling back to the old path.
Side effects
NO
QA Notes
View a .omv file
Deployment Notes
NA

Coverage increased (+0.007%) to 71.241% when pulling 3b3ca002136d75b107f50cd70fd19b7eeaa55f4d on jonathon-love:patch-2 into 9908bc8c775931b5b4360a1fa029b4883dc21fa3 on CenterForOpenScience:master.

hi guys
this is 23 days old now. could you give me some idea what timeframe to expect?
with thanks

@jonathon-love, I am following up to see if you need anything else from us? In addition, @felliott is back and he will take care of merging this PR 🐧 after unit tests are updated.

sorry, will get to this soon.
with thanks

sorry for the delay on this one guys!
it's ready now.
with thanks

Looks good!  I've added a unittest for the old manifest format.  I'm prepping a release, it should go out next week.

This is merged into develop. I will cut a release early next week (post-new-years).


Encapsulation

Description 📜
Here we will be learning about Encapsulation.

Domain of Contribution 📊

[x] C/CPP

/assign

/assign

/assign


Release Google.Cloud.GkeConnect.Gateway.V1Beta1 version 2.0.0-beta05

Changes in this release:
This release is being used to publish a new front-page of documentation, to indicate package deprecation.

Created release for Google.Cloud.GkeConnect.Gateway.V1Beta1-2.0.0-beta05


fetching nested resource

module Client
  class Base < JsonApiClient::Resource
    self.site = 'http://<IP_ADDRESS>:3000/'
  end

  class Author < Base
    has_many :posts
  end

  class Post < Base
    belongs_to :author
  end

end

p = Client::Post.where(author_id: 1, title: 'title 2')
p.params # {:filter=>{:author_id=>1, :title=>"title 2"}}
posts = p.to_a
p.params # {:filter=>{:title=>"title 2"}}

it's losing parent key somewhere

test for that bug you can put into test/unit/association_test.rb
def test_find_belongs_to_params_unchanged
  stub_request(:get, "http://example.com/foos/1/specifieds")
        .to_return(headers: {
                       content_type: "application/vnd.api+json"
                   }, body: {
                        data: [
                            {
                                id: 1,
                                name: "Jeff Ching",
                                bars: [{id: 1, attributes: {address: "123 Main St."}}]
                            }
                        ]
                    }.to_json)

  specifieds = Specified.where(foo_id: 1)
  assert_equal({filter: {foo_id: 1}}, specifieds.params)
  specifieds.all
  assert_equal({filter: {foo_id: 1}}, specifieds.params)
end

by the way, maybe we need public method like reload() in Query::Builder that will clear @to_a and fetch it again?
something like
class JsonApiClient::Query::Builder
  ...

  def clear
    @to_a = nil
  end

  def reload
    clear
    to_a
  end
end

The issue here is that i'm deleting the path params out of the params when I'm making the query. Perhaps I should be collecting the path params separately.


Update to numpy 2.0.0

Hi,
I would appreciate an update to numpy 2.0.0, or at least the option to use it. Unless it breaks something badly.
Kindest regards,
Roberto

Thanks for the suggestion! We are working on the next release; we will test this new version of numpy and add it if possible.

Checked a bit more, unfortunately onnxruntime needs numpy<2.0.0. They are planning to add support later on, but not there yet. "Support for numpy 2.0 will be added in a future release." from https://github.com/Microsoft/onnxruntime/releases/tag/v1.18.1. As soon as they add support, we'll be able to bump numpy version as well.

Update: It seems that onnxruntime 1.19 added support for numpy 2.0.0, will give it a try. https://github.com/Microsoft/onnxruntime/releases/tag/v1.19.0


Use MySQL internal CURRENT_TIMESTAMP for dates

Use SQL internal data instead of PHP generated timestamps:
`created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
`updated_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,

:exclamation: Note, the date/time may be different between the PHP and MySQL server, so there may be an offset between all new vs. existing entries.

To adjust /clean command to work with this change this could probably be used:
WHERE UNIX_TIMESTAMP(`updated_at`) + ? < UNIX_TIMESTAMP(NOW())

PS. Oh god I forgot to create this issue...

@jacklul I noticed that the insertUser and insertChat methods can be passed a $date to override the created_at and updated_at fields. I'm just wondering how useful that actually is, as these fields should be purely about "when was this row added (or updated) to the DB".
What do you think?
Also, probably makes sense to add both fields to all DB tables.

It depends how you look at it, I believe some devs like that those fields are the date when the chat was actually created (date from Update) and updated.
I fully support the change that they should contain dates of record update / creation, it makes more sense. We might simply add a field to the chat/user object that will have a date of first chat action inserted.

Message has the date, forward_date and edit_date fields anyway, so those should be safe.
So it's mainly the Chat itself that is a bit off. Update object also has no date associated to it, so there's no way of getting the exact date/time anyway.
I think we just make the change and let the users know.

Use SQL internal data instead of PHP generated timestamps:
`created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
`updated_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,

❗ Note, the date/time may be different between the PHP and MySQL server, so there may be an offset between all new vs. existing entries.

Can this problem be solved by setting the timezone of php and mysql server to be the same?


Radarr/Sonarr config breaks if Base URL does not have a preceding slash /

Describe the bug
When setting up Radarr and Sonarr settings, if the user has a base URL it is a required field. However, there is no indication whether the preceding forward-slash is required or pre-pended automatically. If the user does not provide the slash like /radarr or /sonarr, when they re-visit the settings by clicking on Edit on either Sonarr or Radarr agent the UI breaks and shows a blank page
To Reproduce
Steps to reproduce the behavior:

Go to 'Admin console'
Click on 'Settings'
In either Radarr or Sonarr tabs click on edit
See blank page with the dev console showing the following error

TypeError: this.state.profiles.map is not a function
    at s.value (radarr.js:406)
    at Va (react-dom.production.min.js:182)
    at Ba (react-dom.production.min.js:181)
    at Ou (react-dom.production.min.js:263)
    at mc (react-dom.production.min.js:246)
    at yc (react-dom.production.min.js:246)
    at uc (react-dom.production.min.js:239)
    at react-dom.production.min.js:123
    at t.unstable_runWithPriority (scheduler.production.min.js:19)
    at Go (react-dom.production.min.js:122)

Expected behavior
Either a validation message enforcing the preceding slash or auto append when the user does not provide one.
Additional context
petio version 0..4.5-alpha

Hi, could you try the dev version for us as I believe this has already been addressed in a more recent commit.

Hi @ADRFranklin, I tried on the dev image. 0.5.2-alpha. As soon as I remove the preceding / it breaks the same way. Blank screen and same JS error in console

Okay, thanks. We will try to resolve this soon.

Noted and fix planned


[SLOW TEST]: should properly generate Basic Auth Object with Bcrypt hashed password if specified in config

How to categorize this issue?

/area testing security
/kind bug
/priority normal
What happened:
This test is consistently slow in test runs:
https://github.com/gardener/gardener/blob/ca4b82674028bfe4c5dcd515cec397c234645626/pkg/utils/secrets/basic_auth_test.go#L84-L89
For example, see https://concourse.ci.gardener.cloud/teams/gardener/pipelines/gardener-master/jobs/master-head-update-job/builds/135#L5ff4d8a5:393:395
• [SLOW TEST:124.746 seconds]
Basic Auth Secrets Basic Auth Configuration #Generate should properly generate Basic Auth Object with Bcrypt hashed password if specified in config
/go/src/github.com/gardener/gardener/pkg/utils/secrets/basic_auth_test.go:84

What you expected to happen:
The test and the generation of basic auth secrets in general shouldn't take so long.
How to reproduce it (as minimally and precisely as possible):
./hack/test.sh -timeout=1m ./pkg/utils/secrets to figure out, where this is hanging:

Output
$ ./hack/test.sh -timeout=1m ./pkg/utils/secrets
Using cached envtest tools from /Users/d067603/go/src/github.com/gardener/gardener/bin/kubebuilder
setting up env vars
> Test
Running Suite: Utility Secrets Suite
====================================
Random Seed:<PHONE_NUMBER>
Will run 48 of 48 specs

•••••••••••••••••panic: test timed out after 1m0s

goroutine 44 [running]:
testing.(*M).startAlarm.func1()
  /usr/local/Cellar/go/1.15.5/libexec/src/testing/testing.go:1618 +0x11f
created by time.goFunc
  /usr/local/Cellar/go/1.15.5/libexec/src/time/sleep.go:167 +0x52

goroutine 1 [chan receive, 1 minutes]:
testing.(*T).Run(0xc0000c5200, 0x3247519, 0xb, 0x3305998, 0x0)
  /usr/local/Cellar/go/1.15.5/libexec/src/testing/testing.go:1169 +0x5f4
testing.runTests.func1(0xc0000c5200)
  /usr/local/Cellar/go/1.15.5/libexec/src/testing/testing.go:1439 +0xa7
testing.tRunner(0xc0000c5200, 0xc000951ce0)
  /usr/local/Cellar/go/1.15.5/libexec/src/testing/testing.go:1123 +0x203
testing.runTests(0xc0003a6100, 0x41702d0, 0x1, 0x1, 0xbff6270ac78acd28, 0xdfd336167, 0x41a96a0, 0x105b725)
  /usr/local/Cellar/go/1.15.5/libexec/src/testing/testing.go:1437 +0x613
testing.(*M).Run(0xc000402000, 0x0)
  /usr/local/Cellar/go/1.15.5/libexec/src/testing/testing.go:1345 +0x3b4
main.main()
  _testmain.go:45 +0x237

goroutine 19 [chan receive]:
k8s.io/klog/v2.(*loggingT).flushDaemon(0x41a99a0)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/k8s.io/klog/v2/klog.go:1131 +0xb1
created by k8s.io/klog/v2.init.0
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/k8s.io/klog/v2/klog.go:416 +0x190

goroutine 43 [syscall]:
os/signal.signal_recv(0x10b47a1)
  /usr/local/Cellar/go/1.15.5/libexec/src/runtime/sigqueue.go:144 +0x9d
os/signal.loop()
  /usr/local/Cellar/go/1.15.5/libexec/src/os/signal/signal_unix.go:23 +0x30
created by os/signal.Notify.func1.1
  /usr/local/Cellar/go/1.15.5/libexec/src/os/signal/signal.go:150 +0x7d

goroutine 16 [chan receive]:
github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).registerForInterrupts(0xc000252640, 0xc000190f60)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:223 +0xf4
created by github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).Run
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:60 +0xaf

goroutine 15 [select]:
github.com/onsi/ginkgo/internal/leafnodes.(*runner).runAsync(0xc0001d28a0, 0x3, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:93 +0x1cc
github.com/onsi/ginkgo/internal/leafnodes.(*runner).run(0xc0001d28a0, 0x3, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:62 +0xa5
github.com/onsi/ginkgo/internal/leafnodes.(*ItNode).Run(0xc0003a6ce0, 0x3491b60, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/leafnodes/it_node.go:26 +0x9a
github.com/onsi/ginkgo/internal/spec.(*Spec).runSample(0xc0004bd2c0, 0x0, 0x3491b60, 0xc000256ec0)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:215 +0x714
github.com/onsi/ginkgo/internal/spec.(*Spec).Run(0xc0004bd2c0, 0x3491b60, 0xc000256ec0)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/spec/spec.go:138 +0x188
github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpec(0xc000252640, 0xc0004bd2c0, 0x0)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:200 +0x17c
github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).runSpecs(0xc000252640, 0x1)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:170 +0x22b
github.com/onsi/ginkgo/internal/specrunner.(*SpecRunner).Run(0xc000252640, 0x8)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/specrunner/spec_runner.go:66 +0x146
github.com/onsi/ginkgo/internal/suite.(*Suite).Run(0xc0001c9730, 0x2ea068e8, 0xc0000c5380, 0x325529f, 0x15, 0xc00039e820, 0x1, 0x1, 0x34de020, 0xc000256ec0, ...)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/suite/suite.go:79 +0x89a
github.com/onsi/ginkgo.RunSpecsWithCustomReporters(0x34926e0, 0xc0000c5380, 0x325529f, 0x15, 0xc000090e70, 0x1, 0x1, 0xc000790e70)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:219 +0x35d
github.com/onsi/ginkgo.RunSpecs(0x34926e0, 0xc0000c5380, 0x325529f, 0x15, 0x0)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/ginkgo_dsl.go:200 +0x259
github.com/gardener/gardener/pkg/utils/secrets_test.TestSecrets(0xc0000c5380)
  /Users/d067603/go/src/github.com/gardener/gardener/pkg/utils/secrets/secrets_suite_test.go:26 +0x109
testing.tRunner(0xc0000c5380, 0x3305998)
  /usr/local/Cellar/go/1.15.5/libexec/src/testing/testing.go:1123 +0x203
created by testing.(*T).Run
  /usr/local/Cellar/go/1.15.5/libexec/src/testing/testing.go:1168 +0x5bc

goroutine 114 [runnable]:
golang.org/x/crypto/blowfish.encryptBlock(0x5bffc5e3f457cf09, 0xc0005aa000, 0x5bffc5e3f457cf09)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/golang.org/x/crypto/blowfish/block.go:115 +0x1145
golang.org/x/crypto/blowfish.ExpandKey(0xc000208480, 0x21, 0x40, 0xc0005aa000)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/golang.org/x/crypto/blowfish/block.go:62 +0x4b6
golang.org/x/crypto/bcrypt.expensiveBlowfishSetup(0xc0005a5938, 0x20, 0x20, 0x10, 0xc000244ae0, 0x16, 0x18, 0x1, 0x1f, 0x0)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/golang.org/x/crypto/bcrypt/bcrypt.go:227 +0x1d5
golang.org/x/crypto/bcrypt.bcrypt(0xc0005a5938, 0x20, 0x20, 0x10, 0xc000244ae0, 0x16, 0x18, 0x0, 0xc000208400, 0x0, ...)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/golang.org/x/crypto/bcrypt/bcrypt.go:191 +0x152
golang.org/x/crypto/bcrypt.CompareHashAndPassword(0xc000208400, 0x3c, 0x40, 0xc0005a5938, 0x20, 0x20, 0x2eca301, 0xc0005a5988)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/golang.org/x/crypto/bcrypt/bcrypt.go:105 +0x126
github.com/gardener/gardener/pkg/utils/secrets_test.glob..func2.1.1(0x3491080, 0xc0004db220, 0xc0004db180, 0x100)
  /Users/d067603/go/src/github.com/gardener/gardener/pkg/utils/secrets/basic_auth_test.go:46 +0xb75
github.com/gardener/gardener/pkg/utils/secrets_test.glob..func<IP_ADDRESS>(0xc0001d3d40)
  /Users/d067603/go/src/github.com/gardener/gardener/pkg/utils/secrets/basic_auth_test.go:90 +0x27b
reflect.Value.call(0x2fff820, 0xc0003a6bc0, 0x13, 0x323e263, 0x4, 0xc0006c3f18, 0x1, 0x1, 0x0, 0x0, ...)
  /usr/local/Cellar/go/1.15.5/libexec/src/reflect/value.go:476 +0x9aa
reflect.Value.Call(0x2fff820, 0xc0003a6bc0, 0x13, 0xc000797f18, 0x1, 0x1, 0x0, 0x0, 0x0)
  /usr/local/Cellar/go/1.15.5/libexec/src/reflect/value.go:337 +0xd9
github.com/onsi/ginkgo/internal/leafnodes.newRunner.func1(0xc0001d3d40)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:49 +0x16f
github.com/onsi/ginkgo/internal/leafnodes.(*runner).runAsync.func1(0xc0001d28a0, 0xc0001d3d40)
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:86 +0xc8
created by github.com/onsi/ginkgo/internal/leafnodes.(*runner).runAsync
  /Users/d067603/go/src/github.com/gardener/gardener/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:71 +0xc5
FAIL	github.com/gardener/gardener/pkg/utils/secrets	60.923s
FAIL

/assign @Kristian-ZH @plkokanov
I think, you added tests and BcryptPasswordHashRequest functionality. Can you check this, please?

/assign @Kristian-ZH @plkokanov
I think, you added tests and BcryptPasswordHashRequest functionality. Can you check this, please?

+1. I had an item in my list to check whether we can remove the Bcrypt handling as it was introduced with searchguard/elasticsearch and it should be no longer used now.

+1. I had an item in my list to check whether we can remove the Bcrypt handling as it was introduced with searchguard/elasticsearch and it should be no longer used now.

/assign @ialidzhikov

/assign @ialidzhikov

For now: https://github.com/gardener/gardener/pull/3363

For now: https://github.com/gardener/gardener/pull/3363

+1. I had an item in my list to check whether we can remove the Bcrypt handling as it was introduced with searchguard/elasticsearch and it should be no longer used now.

Yup, the bcrypt is no longer used in the logging stack

+1. I had an item in my list to check whether we can remove the Bcrypt handling as it was introduced with searchguard/elasticsearch and it should be no longer used now.

Yup, the bcrypt is no longer used in the logging stack


Order affiliated with a Party and able to shop with HQ as consultant

Have there been any reports of orders coming through with a party attached and associated with HQ as the consultant?
I searched for a consultant by zip code (55357) and 25 miles.
I selected Holly Munsterteiger
I visited Holly's page (which affiliated me with Holly)
I selected a party on her list (which affiliated me with the party)
All good so far.
Then, I decided to search for another consultant by zip code (55357), exact. There are no consultants in this zip code, and I selected the 'Shop with Tastefully Simple' from the blue bar at the bottom of the Search window.

The result was that I was affiliated with HQ as a consultant, and the Party affiliation remained. Should the party affiliation been removed? Is it possible the logic that would have removed it does not kick off when selecting the blue bar "shop with TS"

Created a ticket for this issue: TST-239

This was a problem in BigCommerceJobs.  The fix is currently in place in QA where I do a check if the partyID is not 0, and the consultant is the default for that environment.

Looks like this is fixed- I started with consultant in header,  added item to cart, selected a party under that consultant, clicked to edit my consultant, and used the zip code provided above (55357) - no results so then selected to continue with TS consultant and it updated, my cart and header and removed my party as I would expect.


Response schema validation not performed

I generated mvc code from raml file, move model code to different package and then I checked implementation against spec. All was ok, but all is ok even if I broke my model class.
I tried to debug plugin code I found that it look like ActionResponseBodySchemaChecker is newer used. Am I right ? If not, why model check not working ?

I thing the reason is described here #54

I checked again with version 0.6.1 and validation of reponse body is not perfomed.
I made pull request which probably fixes this problem #59


url: 'https://XXX/.../upnp/control/wanipconnection1' -> Error 401

Homebridge is logging permanently:
(FritzBox 7490, FritzOS 07.29<EMAIL_ADDRESS><EMAIL_ADDRESS>
[23/01/2022, 16:25:37] [FritzPlatform] FritzBox (cable): An error occured during getting state!
[23/01/2022, 16:25:37] [FritzPlatform] Error: Internal Server Error
at Object.exports.request (/usr/lib/node_modules/homebridge-fritz-platform/node_modules/@seydx/fritzbox/lib/request.js:78:21) at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at exports.requestXml (/usr/lib/node_modules/homebridge-fritz-platform/node_modules/@seydx/fritzbox/lib/request.js:230:20)
at Service.execAction (/usr/lib/node_modules/homebridge-fritz-platform/node_modules/@seydx/fritzbox/lib/service.js:133:20)
at Handler.get (/usr/lib/node_modules/homebridge-fritz-platform/src/accessories/router/router.handler.js:133:28)
at Handler.poll (/usr/lib/node_modules/homebridge-fritz-platform/src/accessories/router/router.handler.js:979:11) { title: 'Invalid Response',
code: 500,
soap: {
errorCode: '401',
errorDescription: 'Invalid Action',
action: 'urn:dslforum-org:service:WANIPConnection:1#GetInfo'
},
url: 'https://admin:XXXXX@192.168.XXX.XXX:49443/upnp/control/wanipconnection1' }

(same without SSL ->192.168.XXX.XXX:49000)
Does this matter or can it be ignored?

Same problem here - can't tell if this is new, or if this has always been the case

I am having the same issue, i do run a different fritzOS (FRITZ!OS:7.57) and running a different modem (FRITZ!Box 7530)
[04/02/2024, 12:49:34] [FritzPlatform] Error: Internal Server Error     at Object.exports.request (/var/lib/homebridge/node_modules/homebridge-fritz-platform/node_modules/@seydx/fritzbox/lib/request.js:78:21)     at processTicksAndRejections (node:internal/process/task_queues:95:5)     at exports.requestXml (/var/lib/homebridge/node_modules/homebridge-fritz-platform/node_modules/@seydx/fritzbox/lib/request.js:230:20)     at Service.execAction (/var/lib/homebridge/node_modules/homebridge-fritz-platform/node_modules/@seydx/fritzbox/lib/service.js:133:20)     at Handler.get (/var/lib/homebridge/node_modules/homebridge-fritz-platform/src/accessories/router/router.handler.js:101:28)     at Handler.poll (/var/lib/homebridge/node_modules/homebridge-fritz-platform/src/accessories/router/router.handler.js:979:11) {   title: 'Invalid Response',   code: 500,   soap: {     errorCode: '401',     errorDescription: 'Invalid Action',     action: 'urn:dslforum-org:service:WANPPPConnection:1#GetInfo'   },   url: 'https://user:pass@<IP_ADDRESS>:49443/upnp/control/wanpppconn1' }
Whats going on here?
If i try to retrieve the url stated in the logs i get a 404 (and some issues with the ssl cert not being safe).

Ok, i think i figured it out. I have fiber, and i had DSL as a connectiontype. If i change that to Cable it seems to work and the error is gone.


Create Container.hasChildren validation tests

Since container is Map, Overlay or Feature, make sure 3 different tests are made--one for each.

To Test:
Load web test
Find emp3.api.Container hasChildren
Verify  "will send message to the message handler to check if has children"

Validation tests still need to be created for this issue.


Reintroduce main navigation link for Download page

Increasing Access
Unsure
Most appropriate sub-area of p5.js?
Main navigation (on the left), all pages.
Feature request details
I greatly appreciated the old site’s readily available link to the "Download" page in the main navigation. It was convenient.
Recently, when I needed to find the download page, I had to search for it and eventually noticed it was located at the bottom in the footer. This was not immediately obvious.
To improve user-friendliness and accessibility, especially for those who may not look on GitHub or at the end of the page, it would be beneficial to add a link to the "Download" page in the main navigation. This would make it easier for all users, particularly new visitors, to quickly find the downloads they need.

Thanks @meezwhite for the suggestion.
The reason we didn't include 'Download' in the left-side navigation bar is based on research indicating that most p5.js users, especially beginners, prefer using the p5.js web editor or CDN links, which are more accessible for new users. Due to limited vertical space in the left-side navigation bar, we had to make the difficult decision to move the 'Download' link to the following two locations:

At the bottom of the homepage when you scroll down a little, as shown in the screenshot below.
In the footers on every page.

We hope these options will provide sufficient entry points to access 'Download'. We understand that the new design, especially the new navigation bar, might take some time to get used to. We can revisit this issue and the design decision if more users raise the same concern.

@Qianqianye I understand your perspective that beginners might find it easier to start with the p5.js web editor or use the CDN link, and maybe use a downloaded version at a later stage.
To me, it seems there is sufficient space for a "Download" link 😅 I don't think it would overshadow the "Start Coding" button, which is more prominently displayed. However, I understand the concern that it might prompt users to think a download is necessary.
Even if users were to visit the download page first, they are still encouraged to "Start Coding Online" first. Maybe a noticeable tip box at the start of the download page to guide beginners to start coding online with the p5.js web editor due to its low entry barrier, would encourage beginners even more to first try p5.js online and not worry about any downloads.
Ultimately, I trust your judgment on whether a link to the download page in the left navigation would be beneficial.
Thanks for considering and showing me where to find the download page. 🙏


Include game/mods version in the metadata

How about including following information in the metadata file?

version of the game
names and versions active mods

Looks good, thanks!

There, published in v0.0.21


Data colour in widget if LibreLinkup does not supply data

First of all, I would like to say how fantastic I think your app is! I use Libre 3 and a Samsung A34 as my reader, and I can now connect it to my Galaxy Watch 6 using your Gluco Data Handler.
The Libre Linkup app you use to retrieve the data is slow as hell. If it doesn't provide data, you turn the colour grey and cross out the value.
1/ Is it possible to keep the normal colour as if it were connected and just cross it out? My watch face background is black, gray is hard to read.
2/ After a while, the value is dropped completely, and it re-appears after Linkup sends new data. Can you just display the old value (crossed out)?
I am unfamiliar with how Linkup operates, but it seems to transmit data every five minutes. If the value remains unchanged, it does not transmit data at all (just a feeling).

Hi,
Libre 3 should offer a new value every minute, also over LibreLink. Sometimes the server has problems, but normally there should be a new value every minute.
Please change the interval to one minute and disable battery optimizations for my app.
If it does not work, please check the LibreLinkUp App, if there is a value every minute. If yes, it is a problem with GlucoDataHandler 😬
If not, it is a problem with the libre app. Then you should reinstall the libre app.
I just recommend to use Juggluco instead of the libre app, so you get the data direct from the app.
Regarding the color of an obsolete value. Good point, I could offer a setting to change it.
Regards, Michael

Just one more remark, there was another one using Galaxy A52s with the same issue. After re-installing the Libre 3 app, he received the value every minute.

I have tried your suggestions, reinstalling the libre app and disabling battery optimisation. There was no change in behaviour. I don't think it's a problem with your app, it's Librelinkup that's behaving strangely. When I open it I see that it doesn't receive any data for several minutes, my best guess is 5 minutes. You're not getting any data during that time either! I guess there is nothing you can do.
But my initial request was to change the colour in this situation from grey to something else. It would be easier to read on my watch. It's just a thought, no urgency.
Regards
Peter (Munich)

Hi Peter,
I will provide a setting for changing the color.
I also thought about a setting to increase the time for an obsolete value.
At the moment I have a lot to do with implement alarms. So it will take some time...
Michael

Hi Michael, as I said, no urgency, I am completely happy to have something that is working. If I can be of any help to you, just let me know. These are my usual activities: https://github.com/mvslovers/brexx370.  But I have no idea about app development.
Peter

@Peter-Jacob are you using LibreLink credentials in GlucoDataHandler or have you created a LibreLinkUp (follower) account and use those credentials with GlucoDataHandler? To my experience, these issues where some 3rd party app is not receiving Libre readings (slowly or not at all) are usually solved by either re-logging in to LibreLinkUp account (sometimes there are updated user rights agreements that need to be approved etc.) or then Libre3 app needs to be re-installed, as suggested by @pachi81, since there are some issues in sending Libre3 readings to Libre cloud, where the 3rd party app is pulling/polling them. I had similar issues than @Peter-Jacob and re-installing Libre3 helped.

Just use Juggluco instead of the nightmare of the libre app 😉🙃
No problems, you can connect the sensor direct to the Galaxy Watch, if you like, ....

Just use Juggluco instead of the nightmare of the libre app 😉🙃
No problems, you can connect the sensor direct to the Galaxy Watch, if you like, ....

I tried to set up Juggluco a while ago but it could never talk to my Libre 2 sensor IIRC

Just use Juggluco instead of the nightmare of the libre app 😉🙃
No problems, you can connect the sensor direct to the Galaxy Watch, if you like, ....

I tried to set up Juggluco a while ago but it could never talk to my Libre 2 sensor IIRC

Maybe you should try again or try using xDrip.
But in the next version I have fixed another bug with LibreLinkUp and also added a setting to change the color of obsolete values.
It is already available as beta and will released next week.

Just use Juggluco instead of the nightmare of the libre app 😉🙃
No problems, you can connect the sensor direct to the Galaxy Watch, if you like, ....

I tried to set up Juggluco a while ago but it could never talk to my Libre 2 sensor IIRC

Maybe you should try again or try using xDrip.
But in the next version I have fixed another bug with LibreLinkUp and also added a setting to change the color of obsolete values.
It is already available as beta and will released next week.

Lol. I've tried xdrip, blose, diabox, everything I could. For all it's faults, at least Libre Link was simple to get started on, it just doesn't stay like that. Eg, It took 5 months before I managed to get the sensor to last the whole 14 days 🤷 and I've managed that feat only once


Allow copying from field values table

I can select rows in the field data table for a document, even multiple rows. But today I wanted a quick way to copy two rows out into a text file, and found that the usual ⌘C shortcut didn't copy the text.
If I right-click and show the full text, then copy from the text area in there, that does work, but since I'd like to do this for a few docs, it would have saved a lot of time had it just worked on the table.
Why it doesn't work is baffling. The default look and feel on OSX supports it without having to do anything, so initially I would assume the problem is with this weird look and feel being used in the application.

It is a very old issue about Thinlet Luke, but I have just re-visited it.
I think it would be much better to add something like "copy all stored values" button to copy all stored values to clipboard to Documents tab.
Now I cannot take time for this (have other issues to resolve,) but it is a good starting point for newbies who want to learn Lucene APIs.
Could anyone take this?

Hi, I would like to take this task.

@thrusc Thanks! Please, send a PR to the master branch. (If you have questions, feel free to ask us here.)

I have some questions. What delimiter would be best for separation of values ? (new lines "\n" or some visible character like comma or semicolon) What should I do with null values ? (ignore them, use empty string or "null" value) It depends on use case, eg. using new lines and "null" - created string can be easealy pasted to excel, it will preserve number od values and it will devide each value to new cell in column.

What delimiter would be best for separation of values ? (new lines "\n" or some visible character like comma or semicolon)

First, we should decide the output file format. CSV(TSV) or JSON or XML are widely accepted, so I think it's preferable that we choose one of them. Stored values can contain arbitrary texts (may include commas, semicolons, line separators, any displayable characters.) To avoid escape character handling, I would use JSON or XML. If you have another proposal, please share this.

new lines "\n"

Just in case, when handling new lines in Java you should always use System.lineseparator() instead of "\n".
See: https://download.java.net/java/early_access/jdk11/docs/api/java.base/java/lang/System.html#lineSeparator()

What should I do with null values ? (ignore them, use empty string or "null" value)

With Lucene index, null value means "there is no stored values available for the field". So we should simply ignore the field.
See: https://lucene.apache.org/core/7_5_0/core/org/apache/lucene/index/IndexableField.html

I think best solution will be to create both.  Simple clipboard functionality for copy document values and create Export functionality with basic configuration eg. output file format, export one or multiple documents. They are both desirable and coverrige different use cases. Because if someone wants to get only values from document and he gets eg. JSON file he will be forced to process that file so it will be harder to extract values than simple paste it somewhere.

I think best solution will be to create both.
They are both desirable and coverrige different use cases.

Agree, simple clipboard functionality to just "Copy & Paste" is handy for many situation.

Is there any reason why it is not possible to select multiple rows at the same time?

Of course, multiple rows selection is possible (it is just up to the JTable configuration.) In this case, I think we will have similar problem to "Copy all fields" functionality. Users can select arbitral multiple rows, so there will be fields with different names and values (those may contain commas, line separators... etc.)
More concretely, to implement simple "Copy & Paste" use case, we should handle

field
value

f1
applebanana

f2
alice

f2
bob

Sorry, my hands slipped.

It will be shipped with the next release, 7.5.0 (or 8.0.0).


Install the project error

I'm trying to install go-astivid, get's an error, jn first step.
note: ffmpeg  installed (7:2.8.11-0ubuntu<IP_ADDRESS>).
go get -u github.com/asticode/go-astivid/...
github.com/asticode/go-astitesseract
tesseract.cpp:1:31: fatal error: tesseract/baseapi.h: No such file or directory
compilation terminated.
Any help?

@khigor777 should be fixed now, can you confirm?

Thanks, for answer.
Got another error.
go get github.com/asticode/go-astivid/poc1
package github.com/asticode/go-astivid/poc1: cannot find package "github.com/asticode/go-astivid/poc1

yeah this is normal, I've removed this package from the master branch as it's still an unstable work in progress. You shouldn't need to go get this package

ok, thanks.


Womanium Final Assignment - Abravi Emiline Tekpa

PR Description
My submission of the Womanium Final Assignment for Classiq modules
Some notes

[x] Please make sure that you placed the files in an appropriate folder

[x] And that the files have indicative names.

[x] Please note that Classiq runs automatic code linting, which may minorly alter some files.

[ ] If you're familiar with pre-commit, you may run pre-commit install, and then at each commit, your files will be altered in a similar way

Well done!
Score: 8/10


Add support for Laravel v5.3

Are we sure the installer is compatible with these versions? /cc @themsaid

@themsaid can you confirm this works?

@taylorotwell I believe it's fine yes, tested it this morning.


chore(master): release 2.1.35

:robot: I have created a release beep boop
2.1.35 (2024-03-17)
Bug Fixes

deps: update dependency wayofdev/laravel-webhook-client to v1.3.8 (9838305)
deps: update dependency wayofdev/laravel-webhook-client to v1.3.9 (53ad3da)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-stripe-webhooks/releases/tag/v2.1.35 :sunflower:


Lots of odd characters at the end of the js file

Example: https://www.thevantageproject.com/assets/js/all.js
I see lots of characters that fill 300 lines starting with sourceMappingURL=data:application/json;charset=utf8;base64,eyJ2ZXJzaW9uIjozLCJzb3VyY2VzIjpbImpxdWVyeS5qcyIsImZvdW5kYXRpb24uY29yZS5qcyIsImZvdW5kYXRpb24udXRpbC5tZWRpYVF1ZXJ5LmpzIiwiZm91bmRhdGlvbi51dGlsLnRyaWdnZXJzLmpzIiwiZm91bmRhdGlvbi5zbW9vdGhTY3JvbGwuanMiLCJmb3VuZGF0aW9uLnN0aWNreS5qcyIsImZvdW5kYXRpb24ubWFnZWxsYW4uanMiLCJhcHAuanMiXSwibmFtZXMiOlsiZ2xvYmFsIiwiZmFjdG
Any idea on what is causing this? And what this is?

Yes. Sourcemaps are for development.
For production simply run: npm run build
And your css file should be smaller and doesn’t contain sourcemaps.


Consider allowing configuring path to regal binary

I'm not sure whether it's considered a sin for a language extension to provide its own configuration, if that's even possible. But if it's cheap to try, we should. From what I can see, unknown configuration options are at least not treated as errors... but I'm not sure if they can be read by the Rust code doing the initialization.
The reason this would be useful is that sometimes you'll want to have stable Regal on $PATH, but test things out with a custom binary for development.

Ah, looks like it's currently impossible to do that, but at least there's an open issue to fix that: https://github.com/zed-industries/zed/issues/4511
I've subscribed to that now, and we can update our docs to include that when it's possible. But I'll close this for now.


Issues with test running under 1.13 using command line flags

Due to breaking changes in Go 1.13, command line test flags are not being parsed correctly.

I just noticed this myself. Adding flag.Parse() to the init func in driver_test.go fixed it.

It works with 1.13 and breaks previous versions. This is due to a known breaking change in the Go testing framework.
On Sep 27, 2019 5:03 PM, Matthew Hiles<EMAIL_ADDRESS>wrote:
I just noticed this myself. Adding flag.Parse() to the init func in driver_test.go fixed it.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/vertica/vertica-sql-go/issues/33?email_source=notifications&email_token=AK56SCNAS5PWREO52GKCK5TQLZ7JDA5CNFSM4IYAG2Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD72GL3I#issuecomment-536110573, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AK56SCJTCFQTWZ7UN63S2NLQLZ7JDANCNFSM4IYAG2QQ.


Add to awesome list for svelte

Would you consider adding this to https://github.com/TheComputerM/awesome-svelte?

Sure! 🙂 Go ahead! 👍

Added: https://github.com/TheComputerM/awesome-svelte/blob/main/README.md#webgl


NavigatorObserver and Router API

The Problem
The NavigatorObserver was original built for Navigator API. After the Router API is introduced, we started to face several issues

It can only work with one Navigator.

It is common to have nested navigators( or even no navigator) with Router API. A single navigation in Route API may trigger 0~n navigators to push/pop routes. Even if we somehow listen to all navigators, it may still be impossible to piece the notifications together.

NavigatorObserver API is too opinionated

Router can achieve things like complete replace route stack in one navigation, there isn't a corresponding API in NavigatorObserver to record the event. It may produce a bunch of didPush/didPop/didReplace that are hard to make sense.
One extreme cases is something like CupertinoTabScaffold. The navigations in between tabs are achieved by using IndexedStack to move different screens around. In this cases, none of the NavigatorObserver will fire. We encounter this issue when we implements https://github.com/flutter/packages/pull/2650
Proposal
A new observing system that based Router API. I don't have much detail yet, one initial idea is to have an observer that observe the Configuration
We can set the generic Type to Diagnotics. so that other third_party router package would need to make sure their Configuration implements the subtype in order to use the observer.
Things to consider

HeroController should be migrated away from NavigatorObserver https://github.com/flutter/flutter/issues/54200
Existing analytics tools needed to be migrated
Possible backward compatibility with NavigatorObserver

@goderbauer @Hixie I am curious if you have any thought on this.
cc @Milad-Akarie, for auto-router
cc @tomgilder, for routemaster
cc @slovnicki, for beamer

I am not a big fan of the current NavigatorObserver API, so if we can replace it with something better, I am all for it! For any proposal it would be interesting to study how the existing use cases (mainly Heroes and analytics) can be implemented with it.

cc @johnpryan

I agree with the idea of implementing a new observing system (e.g. RouterObserver) for Router API that listens to currentConfiguration. This way, we

could handle generic needs of all routing packages and solutions
will not break NavigatorObserver implementers

but the whole situation indeed is much complicated than it might seem at first. There are several things to consider furthermore
Multiple Routers
In this case, the RouterObserver could follow a similar logic as is for RootBackButtonDispatcher and ChildBackButtonDispatcher so that only the root observer gives the final notification out.
Developer Experience
Developers not using Router API should be able to just keep using NavigatorObserver, but developers who are currently using Router API with some NavigatorObserver will be confused about how and why to migrate. There is a case for using both RouteObserver and NavigatorObserver because we can use Navigator.push (without interacting with currentConfiguration) and Router API simultaneously, but having to specify both RouterObserver and NavigatorObserver in different places looks too disconnected.
From this perspective, it seems that RouterObserver could be implemented as a composite of

NavigatorObserver (which *should be passed down to Navigator) and
"CurrentConfigurationObserver" that will watch changes in currentConfiguration

This way the RouterObserver will notify of all relevant changes and it is up to developer to chose what information to use for further processing (analytic tools, etc.)
Now all developers that are currently using some NavigatorObserver can just wrap it with RouterObserver.
There is some hand-waving here, especially with "should be passed down to Navigator" which may not be trivial or obvious in general case, but should be quite straightforward for most third_party packages if RouterDelegate receives the RouterObserver containing NavigatorObserver.
Now that I've written this composite approach, I don't see any reason to prevent us from just having something like
RouterObserver with CurrentConfigurationObserver implements NavigatorObserver { ... }

with which the migration would be even easier - just some renaming and moving things around.
(I will leave the initial composite idea so we have a full train of thought)
currentConfiguration as a target for observer
We can consider adding a new property to RouterDelegate specificaly for RouterObserver to observe.
The motivation behind this is that currentConfiguration may not be the best choice for routing notification and most developers will want to see something like the output of RouteInformationParser.restoreRouteInformation.

A new or an enhanced navigator observer is definitely needed for the Router Api.
My take on this is to have an abstract NavigationEventsObserver that can be used by any navigation widget/entity ( Navigator, Router, TabsRouter ... etc ), the observer should not care about the widget dispatching the even.
Considerations I have in mind

We should be able to observer both router-configuration changes and changes per navigators and sub navigators.
Router developers can add their own navigation events by extending  NavigationEvent and have their navigation-widgets dispatch them e.g auto_route would have DidInitTabRoute and DidChangeTabRoute events.
All navigators/navigation-widgets should be able to dispatch events to the same NavigationEventsObserver instance ( navigator_state can be passed with the event )

The initial implementation idea
// something like _NavigatorObservation
abstract class NavigationEvent{}

// navigator push event
class NavigatorDidPush extends NavigationEvent{
  final Route<dynamic> route;
  final Route<dynamic> previousRoute;

  NavigatorDidPush(this.route, this.previousRoute);
}

abstract class NavigationEventsObserver{
  void onNavigationEvent(NavigationEvent event);
}

// possible  back-compatibility with current NavigationObserver
// also mapping events to method-calls for a simpler api for newer-implementations
class NavigationObserver extends NavigationEventsObserver{

  @override
  void onNavigationEvent(NavigationEvent event) {
    if(event is NavigatorDidPush){
      didPush(event.route, event.previousRoute);
    }
   // ... handle other navigator 1.0 events
  }

  void didPush(Route route, Route? previousRoute){}
}

and the NavigationEventsObserver can be passed to the Router and have it dispatch a RouterConfigrationChangeEvent(prevConfig?,config)

Not sure how to handle HeroController.

We could also consider using Notification
and NotificationListener
It is currently only used for ScrollNotification, we can add a new subclass for NavigationNotification. The possible down side of it is that this do a linear walk on the ancestor widgets to reach the listener which may potentially expansive.
I am not too worry about HeroController, I think we will decouple it from navigator anyway.


Add py.typed files

Fixes https://github.com/python-poetry/poetry/issues/5099
This PR adds a py.typed file to mark the poetry-core source code as containing type hints.
Having poetry-core typed allows Poetry plugins to be more thoroughly type checked with Mypy.

Hello @NiklasRosenstein,
thanks a lot for your contribution :+1:
We would like to wait for this until we thoroughly type checked poetry-core itself with mypy to give you the best experience with it. :smiley:
fin swimmer

Hey @finswimmer,
Don't you think that having some wrong types is better than no types to check against?
It also opens up the opportunity for consumers for poetry-core to detect typing issues; see #270

I think on the whole this would be better in than not in

we probably have made progress on the typechecking in this project since this MR was originally raised
most remaining errors are probably mostly on internal methods and won't harm users of this library
but anyway surely the only user of this library that counts is poetry itself, and if poetry would find it helpful to have typing here then that's the main thing

And if there are still mistakes then having a py.typed will encourage putting them right.
We could be still further ahead on the typechecking if the MRs that helped to progress this would be merged.  https://github.com/python-poetry/poetry/issues/5017 asks for community help, but poetry is slow to accept that help when it arrives.  I added a list of open MRs that I know about at https://github.com/python-poetry/poetry/issues/5017#issuecomment-1110052823.

I suppose this can be closed because py.typed has already sneaked in via #331. 😉

py.typed has already sneaked in via https://github.com/python-poetry/poetry-core/pull/331.

I just noticed that myself!  This was an accident, I'd been trying the effect of adding this and... well, I guess an empty file is an easy thing to miss in a diff.
Anyway, I came here to say that it had gone in accidentally but I reckon that it should stay anyway, happy to see that this was already the thought.


npm invalid "dist-tags"

need to contact npm or update implementation

https://registry.npmjs.org/angularjs-ie8-build

Worth also noting that this breaks their frontend site: https://www.npmjs.com/package/angularjs-ie8-build

Did anyone reached out yet?

I haven't

For the record, I  DMed npm support on Twitter

included in #66


Property:thematicFocus

Definition
A texual description of the collection and the characteristics and its idiosyncrasies

Dimension

Existing property

Existing class

Existing property identifier

Format
Text

Required

Repeatable

Constraints

Examples

Notes

Suggestion from a comment on the index sheet to use dcterms:abstract (https://www.dublincore.org/specifications/dublin-core/collection-description/collection-application-profile/#coldctermsabstract)

Example: (high level; from NHM) The Museum’s Lepidoptera collection contains approximately 8,712,000 specimens in 80,000 drawers. The Lepidoptera specimens are divided into two separate collections, British and international, both of which are rich in type specimens.
Would this be a suitable, high-level example?

Example: (high level; from NHM) The Museum’s orthopteroid collection contains an estimated 785,824 specimens, including 5,567 primary and 15,051 secondary type specimens. 20,618 are Type specimens.

I would not put actual numbers in an example, because they grow old quickly and we don't want people to put numbers here,

I agree with @qgroom completely.  This is probably a good rule of thumb when thinking about content in any cd field.

Also agree re the numbers.
Suggestion for updated definition: "A textual description of the collection's main foci (e.g. geographic, taxonomic or historical), strengths and idiosyncrasies."
Some potential examples:
"Worldwide, with specific strength in Madagascar, New Caledonia, Brazil"
"Belgian and DRC prehistoric sites (middle paleolithic to protohistory), Belgian historical human remains. World reference collection."
"Primarily marine Crustacea, with worldwide representation but with historical strengths in eastern Pacific Decapoda. Major historical component is from the Allan Hancock Expeditions along the west coast of the Americas in the early 20th century."
"Includes a unique collection of ferromanganese crusts and nodules from shelf sea areas; mainly from the Baltic and Barents Sea."

Maybe also add a note that numeric values should be handled by the metric classes wherever possible.


Remove PE name check from delete function

There is no reason to check PE inside of delete function.
This fixes cases where endpoint wasn't deleted on Azure side and left in the Disconnected state.

Merged as part of #128


AB#5047

Proposed changes

Related issues

Checklist

[x] I consider the submitted work as finished
[x] I tested the code for its functionality
[ ] I wrote test cases for the relevant uses case
[ ] I added/update the relevant documentation (either on github or on notion)
[ ] Where necessary I refactored code to improve the overall quality

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Code changes tested locally, @DallasP9124 @r-joyce please review and merge.