Does not work for a Kobo.

The translated file cannot be opened on a Kobo Glo (Find DRM) while the original untranslated book opens.
Convert en->fr

In most softwares .ePub means DRM free .ePub.
To software that deal with plain ePubs DRMd books look like gibberish.
You'll have to use software like Calibre DeDRM(free) or ePubor Ultimate(Paid) to remove the DRM and then translate it


Add call for getting all Accounts/Organizations to Api Libraries

The Accounts Api is not available in any of the Api Libraries.
This is a big oversight, as it's the first API (after auth) that many services will use.

I'm using the node version of the API which only provides the WebApi Object. I'm not sure that class exists there


The tops of some of the letters are cutoff when viewing at different zoom levels

Attach (recommended) or Link to PDF file here:
http://fundcompli.rightprospectus.com/documents/TIAACREFVA/TIAA_VA-1_soi.pdf
Configuration:

Web browser and its version: All
Operating system and its version: All
PDF.js version: latest
Is a browser extension: NA

Steps to reproduce the problem:

Open PDF file ( http://fundcompli.rightprospectus.com/documents/TIAACREFVA/TIAA_VA-1_soi.pdf) in Pdf Js Viewer.
Issue can be seen when we open PDF here - https://mozilla.github.io/pdf.js/web/viewer.html
The tops of some of the letters are cutoff when viewing at different zoom levels. Please find below screen shots at different zoom levels

What is the expected behavior? (add screenshot)

What went wrong? (add screenshot)
Zoom Level - 100%

Zoom Level - Automatic

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): NA

I can reproduce this using Firefox 57.0.1 on Arch Linux.

Attach (recommended) or Link to PDF file here:
http://fundcompli.rightprospectus.com/documents/TIAACREFVA/TIAA_VA-1_soi.pdf

It appears that the linked document has changed (which is why we advice to attach files rather than linking them), since it no longer agrees with the screen-shots posted above.
The currently available PDF file does not, as far as my testing goes, seem to reproduce the original issue; hence closing this issue as WORKSFORME.


Add info regarding plots incompatibility in the ReadMe

As the title says, please add this info in the ReadMe. I lost some time debugging why I cannot farm, only to find out that custom plots are needed from Discord ...

https://achicoin.org/faq/

The purpose of this issue was to add this info in ReadMe. Nobody checks the FAQ first.
But anyway, it is your coin do what you want with it :)

done


Sankey

related to #146 and resolves #14

@MattF-NSIDC ready for review because I believe this resolves #146 #160 an #14. There is obviously more to do in regards to the larger Sankey, but this was getting a little big and I'd like to have new branches for those specific wants/needs


Request credentials for an os-climate bucket

Requesting credentials for github user:
@piadif
@weiqing
@Red
@Corentin
Requesting credentials for the bucket: Openshift platform and the physical risk s3 bucket and add them members
Email address to send a credential download link:
@piadif |<EMAIL_ADDRESS>@weiqing |<EMAIL_ADDRESS>@Red |<EMAIL_ADDRESS>@Corentin |<EMAIL_ADDRESS>
[ ] User can establish connection with the bucket
[ ] User can read files from the bucket
[ ] User can write files to the bucket

Good morning Heather,
I hope you are doing well.
Thank you for adding all the users!
One of my colleagues does not have access. We first thought that it was IT restrictions on her laptop, but after sorting all of that out she noted that the Gitlab username she provided was different to the one on her account. Would it be possible to add her using the following username:
Github user: @weiqing.cao
Email address<EMAIL_ADDRESS>Thank you in advance.
Kind regards,
Carina
Quant Analyst - Quantitative Solutions
Mobile: +44 (0)79 7776 1196
<EMAIL_ADDRESS>Visit our Climate Risk page: Climate risk - Mazarshttps://www.mazars.co.uk/Home/Industries/Financial-Services/Banking-Capital-Markets/Climate-risk
@.***
From: Heather Ackenhusen @.>
Sent: Monday, February 5, 2024 7:51 PM
To: os-climate/OS-Climate-Community-Hub @.>
Cc: Carina Van Der Merwe @.>; Author @.>
Subject: Re: [os-climate/OS-Climate-Community-Hub] Request credentials for an os-climate bucket (Issue #141)
Alert: This email was sent by an external party

Welcome Mazars team! All users have been invited to GitHub org along with Data Commons & Phys Risk projects.
The keys are stored in openshift, you can login using your github account and should be able to see them here at this URL:
https://console-openshift-console.apps.odh-cl1.apps.os-climate.org/k8s/ns/sandbox/secrets/physrisk-s3-keyshttps://console-openshift-console.apps.odh-cl1.apps.os-climate.org/k8s/ns/sandbox/secrets/physrisk-s3-keys
Adding @sandoemahttps://github.com/sandoema @joemoorhousehttps://github.com/joemoorhouse and @ModeSevenIndustrialSolutionshttps://github.com/ModeSevenIndustrialSolutions for awareness.

Reply to this email directly, view it on GitHubhttps://github.com/os-climate/OS-Climate-Community-Hub/issues/141#issuecomment-1927964368, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDNNI5Q4IJTJLYLSPXDBCCDYSEZ3HAVCNFSM6AAAAABCWLKXDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRXHE3DIMZWHA.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>We’d love to hear your views on working with us here: https://www.mazars.co.uk/feedback
Mazars LLP is the UK firm of Mazars, an integrated international advisory and accountancy organisation. Mazars LLP is a limited liability partnership registered in England and Wales with registered number OC308299 and with its registered office at 30 Old Bailey, London, EC4M 7AU.
Details about our audit registration can be viewed on the Register of Statutory Auditors’ website, under reference number C001139861.
Mazars Financial Planning Limited and Mazars Corporate Finance Limited are both registered in England and Wales with Nos. 3172233 and 4252262 respectively. Both companies are wholly owned subsidiaries of Mazars LLP, are authorised and regulated by the Financial Conduct Authority and have their registered offices at: 30 Old Bailey, London, EC4M 7AU.
This email and any attachments are confidential and may also be subject to legal privilege. If you are not the intended recipient, please notify the sender immediately, and do not disclose the contents to another person, use it for any purpose, store or copy the information in any medium. Please also destroy and delete the message from your computer.
If you currently receive marketing communications from us and no longer wish to do so, please email @.*** confirming your choice to unsubscribe.

Hi Heather,
Thank you, she confirmed that she had received the invite via email and was able to join.
Kind regards,
Carina
From: Heather Ackenhusen @.>
Sent: Monday, February 19, 2024 4:49 PM
To: os-climate/OS-Climate-Community-Hub @.>
Cc: Carina Van Der Merwe @.>; Author @.>
Subject: Re: [os-climate/OS-Climate-Community-Hub] Request credentials for an os-climate bucket (Issue #141)
Alert: This email was sent by an external party

Hi Carina - I couldn't find a github id "weiqing.cao", so sent an invite to the email address you provided. Please let me know if she didn't receive it.

Reply to this email directly, view it on GitHubhttps://github.com/os-climate/OS-Climate-Community-Hub/issues/141#issuecomment-1952866092, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDNNI5U2BS64SKPIKKK36ULYUN7ALAVCNFSM6AAAAABCWLKXDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSHA3DMMBZGI.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>We’d love to hear your views on working with us here: https://www.mazars.co.uk/feedback
Mazars LLP is the UK firm of Mazars, an integrated international advisory and accountancy organisation. Mazars LLP is a limited liability partnership registered in England and Wales with registered number OC308299 and with its registered office at 30 Old Bailey, London, EC4M 7AU.
Details about our audit registration can be viewed on the Register of Statutory Auditors’ website, under reference number C001139861.
Mazars Financial Planning Limited and Mazars Corporate Finance Limited are both registered in England and Wales with Nos. 3172233 and 4252262 respectively. Both companies are wholly owned subsidiaries of Mazars LLP, are authorised and regulated by the Financial Conduct Authority and have their registered offices at: 30 Old Bailey, London, EC4M 7AU.
This email and any attachments are confidential and may also be subject to legal privilege. If you are not the intended recipient, please notify the sender immediately, and do not disclose the contents to another person, use it for any purpose, store or copy the information in any medium. Please also destroy and delete the message from your computer.
If you currently receive marketing communications from us and no longer wish to do so, please email @.*** confirming your choice to unsubscribe.


Fixing formatting errors in Run refdoc

Fast-track please; the run reference is broken in the docs.
https://docs.docker.com/engine/reference/builder/#arg
Signed-off-by: John Mulhausen<EMAIL_ADDRESS>

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "patch-2" git@github.com:johndmulhausen/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

LGTM

LGTM

This needs to go to master too, I'll make a PR.

Created #30334


Write end-to-end tests with Cypress

The application should have automated tests. Comprehensive end-to-end testing with Cypress should be enough.

Testing started.


Gaussian elimination chapter inconsistent

The code in the Gaussian Elimination chapter seems to be inconsistent. I am throwing this issue up to check out soon before we put out the video on the topic.

Not only the code, but also the explanation. It mentions a "current row" even though it never mentions a row iteration.

This has been addressed in #544


Feature darkmode

Redesigned the navbar and changed the color.
Fixed all darkmode color for the templates.

@abel-otegbola I merged but its not working completely working at my end . Could you figure out why

@abel-otegbola Great wokr


404 after logging in

https://www.nuget.org/Contribute/MyAccount
This link is not working

What resource are you trying to access?
The only available route of this form is https://www.nuget.org/Contribute/NewSubmission

Yes.. Its working now...
Closing this...


Quote ints in deploy template

The integers in the deploy template should be quoted to allow them to be
parsed properly by the template.
Signed-off-by: Chris Collins<EMAIL_ADDRESS>

/lgtm


[batch-llm] Check for private/gated models during HuggingFace token authentication

Some models on HuggingFace are private/gated models. Previously, the HuggingFace API returned a 400-status code in the case where the model is private/gated and no user token is provided, but the API now returns a 200 status code, with the response now including private and gated.
This PR updates the utility function used in the batch-llm template to determine if the model requires a HF token so that it works correctly for private/gated models with the new HF API response.

Closed in favor of https://github.com/anyscale/templates/pull/289


Timestamp not recognized by Excel in CSV output

I exported a table that has a timestamp without timezone column. The JSON exports the data correctly but the CSV timestamp data column is not recognized by Excel.
JSON data output =
[{"created_at":"2015-06-22T01:48:14.928Z","pk":103}]
CSV data output =
pk,created_at
103,2015-06-22 01:48:14.928 +0000 +0000

Sorry but i don't have Excel around, only Google Docs. I made a sample CSV export document that has both date and datetime columns. Try to import it and see if that works. Here's the link: https://dl.dropboxusercontent.com/u/486271/pgweb-1467084910.csv
Im not 100% sure how timestamps should be formatted in CSV files for Excel ingestion, but with a bit of googling it looks like its a standard yyyy-mm-dd hh:mm:ss. I pushed a new branch with the fix if you're interested in trying it out.

Yes that worked! Thank you!!!


Surveys for 20PI4 Planning

Some squads have asked if we will have surveys ? If yes, then we might want to get some people involved to help ?

Nick - I would turn this around - what squads have survey questions? What questions are they? are they critical for 4Q? ZLC is not against doing a survey but we need to give lead time to get it composed and get replies. Another options is Zowe is planning a quarterly "event" - first one is targeted for Oct 14 and the PROPOSAL is to offer a survey then ....... and do a quarterly cadence.

+1 from me on.... understanding which squads have questions.  I would also suggest having the squads move forward with planning and while doing so, as questions come up, consider adding them to a survey that we will MARKET and ENCOURAGE PARTICIPATING in during our Quarterly Webinar.  I realize we will be 2 weeks in to the PI but getting feedback is a fluid activity.  If we can get folks in the "groove" of expecting 1 survey per quarter, that we will announce during our webinars, it would work out for all.   Anything needed in advance can be posted via SLACK channels right?

ZLC opinion is to survey twice a year in Jan and July ....I recommended closing this item BUT placing the reminder on the development calendar to prep for Jan survey


Justify all main body text by default

First, I want to apologize if this is the wrong place for posting such a n00b question. If I should ask at another location, please just let me know :) .
My question is simple: how should I modify which file to have all the main body text justified by default? I guess I should edit some .css file or something like that?

You may ask questions related to usage (of anything related to Jekyll) at https://talk.jekyllrb.com/


[Bug]: Error: Upload failed, could not reach the server

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
After running the shopify theme dev --store=your-store-name command, it uploads your development theme, allowing you to start working on it.
Actual behavior
CLI stops and the Error appears after the success and theme preview links.

Verbose output
2024-10-18T13:48:30.071Z: Running command theme dev
2024-10-18T13:48:30.085Z: Ensuring that the user is authenticated with the Theme API with the following scopes:
[]
2024-10-18T13:48:30.085Z: Ensuring that the user is authenticated with the Admin API with the following scopes for the store xxxxxxxxxxx.myshopify.com:
[]
2024-10-18T13:48:30.085Z: Getting session store...
2024-10-18T13:48:30.087Z: 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": "xxxxxxxxxxx.myshopify.com"
}
}
2024-10-18T13:48:30.087Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2024-10-18T13:48:30.087Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:

User-Agent: Shopify CLI; v=3.68.1
Keep-Alive: timeout=30
Sec-CH-UA-PLATFORM: darwin
Content-Type: application/json

2024-10-18T13:48:30.391Z: Request to https://accounts.shopify.com/oauth/introspection completed in 303 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/"a27ae57a2d73d2dcb6f2fee835455c62"
server-timing: processing;dur=28, socket_queue;dur=1.976, edge;dur=0.021, util;dur=0.15, cfRequestDuration;dur=188.999891
x-request-id: 24d5dbf1-1285-48b7-b296-fb3c4eda4a71-1729259310

2024-10-18T13:48:30.398Z: The identity token is valid: true
2024-10-18T13:48:30.399Z:
The validation of the token for application/identity completed with the following results:

It's expired: false
It's invalid in identity: false

2024-10-18T13:48:30.399Z: The current session is valid but needs refresh. Refreshing...
2024-10-18T13:48:30.401Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_CjQI2MnJuAYQ-IHKuAZSJggBEhDd5ucRQSxA1YM18PSctY3pGhBB9s-dvhVNSJ_rC3T7W_9BEkAmcHYNCZPrKkopsZdivw3VpPKK1T1igCxnLs5rKmbDH8jRmP_cAHbtD6gH0lndY1wWVDJdFv7syujPK_y_ijAL&refresh_token=atkn_CiEI2MnJuAYQ2OPnuQaiARIKEEH2z52-FU1In-sLdPtb_0ESQBITTqQyoHiUb1jBKb21mdqACojzXPs3B_kP5CzqGMBS51qclIvoKwgzRUg8YBx4iVcegPWjVG5C3ZjujM0rDAo&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3
With request headers:

User-Agent: Shopify CLI; v=3.68.1
Keep-Alive: timeout=30
Sec-CH-UA-PLATFORM: darwin
Content-Type: application/json

2024-10-18T13:48:30.687Z: Request to https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_CjQI2MnJuAYQ-IHKuAZSJggBEhDd5ucRQSxA1YM18PSctY3pGhBB9s-dvhVNSJ_rC3T7W_9BEkAmcHYNCZPrKkopsZdivw3VpPKK1T1igCxnLs5rKmbDH8jRmP_cAHbtD6gH0lndY1wWVDJdFv7syujPK_y_ijAL&refresh_token=atkn_CiEI2MnJuAYQ2OPnuQaiARIKEEH2z52-FU1In-sLdPtb_0ESQBITTqQyoHiUb1jBKb21mdqACojzXPs3B_kP5CzqGMBS51qclIvoKwgzRUg8YBx4iVcegPWjVG5C3ZjujM0rDAo&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3 completed in 286 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/"1fd77b44c287a4cde297527e75bf47fe"
server-timing: processing;dur=78, socket_queue;dur=1.872, edge;dur=1.016, util;dur=0.1, cfRequestDuration;dur=202.999830
x-request-id: 4c6d6535-3b02-4ffb-99d8-9605aaeb0355-1729259310

2024-10-18T13:48:30.692Z: 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.68.1
Keep-Alive: timeout=30
Sec-CH-UA-PLATFORM: darwin
Content-Type: application/json

2024-10-18T13:48:30.692Z: 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.68.1
Keep-Alive: timeout=30
Sec-CH-UA-PLATFORM: darwin
Content-Type: application/json

2024-10-18T13:48:30.693Z: 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.68.1
Keep-Alive: timeout=30
Sec-CH-UA-PLATFORM: darwin
Content-Type: application/json

2024-10-18T13:48:30.693Z: 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%2Fxxxxxxxxxxx.myshopify.com%2Fadmin
With request headers:

User-Agent: Shopify CLI; v=3.68.1
Keep-Alive: timeout=30
Sec-CH-UA-PLATFORM: darwin
Content-Type: application/json

2024-10-18T13:48:30.958Z: 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 266 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/"831b9c3a71e32e677fe390e7a808c772"
server-timing: processing;dur=48, socket_queue;dur=2.174, edge;dur=1.021, util;dur=0.05, cfRequestDuration;dur=176.999807
x-request-id: aaaaf7fe-fabc-472d-a764-21590e280960-1729259310

2024-10-18T13:48:30.964Z: 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 271 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/"de17140aae130f610b78145c06d492af"
server-timing: processing;dur=46, socket_queue;dur=1.358, edge;dur=1.024, util;dur=0.35, cfRequestDuration;dur=180.999756
x-request-id: ec8e6863-53b9-423b-a8ed-97c427227725-1729259310

2024-10-18T13:48:30.967Z: 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%2Fxxxxxxxxxxx.myshopify.com%2Fadmin completed in 274 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/"a000165675020307c2e62430af9940f2"
server-timing: processing;dur=49, socket_queue;dur=1.616, edge;dur=1.02, util;dur=0.05, cfRequestDuration;dur=180.999994
x-request-id: f6889ff9-b27d-45e4-a8b2-84933a45cde5-1729259310

2024-10-18T13:48:30.971Z: 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 279 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/"fd1ad66d40e16d99289763cd0b122e54"
server-timing: processing;dur=46, socket_queue;dur=1.653, edge;dur=2.023, util;dur=0.15, cfRequestDuration;dur=184.000015
x-request-id: b2eb79fb-1040-41ff-b181-0124a4213434-1729259310

2024-10-18T13:48:30.976Z: Setting session store...
2024-10-18T13:48:30.983Z: Ensuring that the user is authenticated with the Storefront API with the following scopes:
[]
2024-10-18T13:48:30.983Z: Getting session store...
2024-10-18T13:48:30.984Z: 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": []
}
}
2024-10-18T13:48:30.984Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2024-10-18T13:48:30.984Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:

User-Agent: Shopify CLI; v=3.68.1
Keep-Alive: timeout=30
Sec-CH-UA-PLATFORM: darwin
Content-Type: application/json

2024-10-18T13:48:31.239Z: Request to https://accounts.shopify.com/oauth/introspection completed in 254 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/"ac58cfcede5311bcfbb92664964483f9"
server-timing: processing;dur=24, socket_queue;dur=1.355, edge;dur=1.03, util;dur=0.15, cfRequestDuration;dur=177.999735
x-request-id: d3a06ba7-bf42-4713-a465-6e9e7403dcd1-1729259311

2024-10-18T13:48:31.241Z: The identity token is valid: true
2024-10-18T13:48:31.241Z:
The validation of the token for application/identity completed with the following results:

It's expired: false
It's invalid in identity: false

2024-10-18T13:48:31.242Z: Getting development theme...
2024-10-18T13:48:31.649Z: Request to https://xxxxxxxxxxx.myshopify.com/admin/api/unstable/themes/141749616877.json?fields=id%2Cname%2Crole%2Cprocessing completed in 403 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=179, cfRequestDuration;dur=332.000256
x-request-id: 808cb089-c3f3-498a-b3a8-c4be75e3dd5b-1729259311

╭─ info ────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  You're using the new version of shopify theme dev.                                 │
│                                                                                │
│  Run shopify theme dev --legacy to switch back to the previous version.             │
│                                                                                │
╰───────────────────────────────────────────────────────────────────────────────────────╯
2024-10-18T13:48:31.713Z: Port 9292 is free
2024-10-18T13:48:31.722Z: Reading the content of file at .shopifyignore...
2024-10-18T13:48:31.722Z: Reading the content of file at assets/FFDINProforIIC-Black.woff2...
2024-10-18T13:48:31.722Z: Reading the content of file at assets/FFDINProforIIC-Bold.woff2...
2024-10-18T13:48:31.722Z: Reading the content of file at assets/FFDINProforIIC-Light.woff2...
2024-10-18T13:48:31.722Z: Reading the content of file at assets/FFDINProforIIC-Medium.woff2...
2024-10-18T13:48:31.722Z: Reading the content of file at assets/FFDINProforIIC.woff2...
2024-10-18T13:48:31.807Z: Request to https://xxxxxxxxxxx.myshopify.com/ completed in 110 ms
With response headers:

content-type: text/html; charset=utf-8
server-timing: processing;dur=20, db;dur=3, db_async;dur=7.135, asn;desc="50266", edge;desc="AMS", country;desc="NL", theme;desc="143001911533", pageType;desc="index", servedBy;desc="2qxc", requestID;desc="b9b1f2e7-c63f-43ff-856e-e80d465ebf4f-1729259311", cfRequestDuration;dur=66.999912
x-request-id: b9b1f2e7-c63f-43ff-856e-e80d465ebf4f-1729259311

2024-10-18T13:48:31.807Z: Getting storefront password for shop xxxxxxxxxxx.myshopify.com...
Warning: The pattern 'templates/.json' does not include subdirectories. To maintain backwards compatibility, we have modified your pattern to templates/**/.json to explicitly include subdirectories.
2024-10-18T13:48:31.979Z: Request to https://xxxxxxxxxxx.myshopify.com/password completed in 172 ms
With response headers:

content-type: text/html; charset=utf-8
server-timing: processing;dur=16;desc="gc:1", db;dur=4, db_async;dur=8.852, asn;desc="50266", edge;desc="AMS", country;desc="NL", pageType;desc="password", servedBy;desc="6hmn", requestID;desc="021395e3-387f-4f6a-8ea8-47b4de5bb29a-1729259311", cfRequestDuration;dur=151.999950
x-request-id: 021395e3-387f-4f6a-8ea8-47b4de5bb29a-1729259311

2024-10-18T13:48:31.980Z: Setting storefront password for shop xxxxxxxxxxx.myshopify.com...
2024-10-18T13:48:31.987Z: Ensuring that the user is authenticated with the Theme API with the following scopes:
[]
2024-10-18T13:48:31.987Z: Ensuring that the user is authenticated with the Admin API with the following scopes for the store xxxxxxxxxxx.myshopify.com:
[]
2024-10-18T13:48:31.987Z: Getting session store...
2024-10-18T13:48:31.987Z: 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": "xxxxxxxxxxx.myshopify.com"
}
}
2024-10-18T13:48:31.988Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2024-10-18T13:48:31.988Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:

User-Agent: Shopify CLI; v=3.68.1
Keep-Alive: timeout=30
Sec-CH-UA-PLATFORM: darwin
Content-Type: application/json

2024-10-18T13:48:32.237Z: Request to https://accounts.shopify.com/oauth/introspection completed in 249 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/"ac58cfcede5311bcfbb92664964483f9"
server-timing: processing;dur=22, socket_queue;dur=1.578, edge;dur=1.015, util;dur=0.0, cfRequestDuration;dur=173.999786
x-request-id: 24d33855-df2d-444b-9d2d-aadb3b0ccc9a-1729259312

2024-10-18T13:48:32.238Z: The identity token is valid: true
2024-10-18T13:48:32.238Z:
The validation of the token for application/identity completed with the following results:

It's expired: false
It's invalid in identity: false

2024-10-18T13:48:32.239Z: Ensuring that the user is authenticated with the Storefront API with the following scopes:
[]
2024-10-18T13:48:32.239Z: Getting session store...
2024-10-18T13:48:32.240Z: 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": []
}
}
2024-10-18T13:48:32.240Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2024-10-18T13:48:32.240Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:

User-Agent: Shopify CLI; v=3.68.1
Keep-Alive: timeout=30
Sec-CH-UA-PLATFORM: darwin
Content-Type: application/json

2024-10-18T13:48:32.460Z: Request to https://accounts.shopify.com/oauth/introspection 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/"ac58cfcede5311bcfbb92664964483f9"
server-timing: processing;dur=28, socket_queue;dur=1.389, edge;dur=1.023, util;dur=0.15, cfRequestDuration;dur=151.000023
x-request-id: f7f234aa-8992-4ef4-8bc5-88f8559bfca7-1729259312

2024-10-18T13:48:32.462Z: The identity token is valid: true
2024-10-18T13:48:32.462Z:
The validation of the token for application/identity completed with the following results:

It's expired: false
It's invalid in identity: false

2024-10-18T13:48:32.684Z: Request to https://xxxxxxxxxxx.myshopify.com/?preview_theme_id=141749616877&_fd=0&pb=0 completed in 221 ms
With response headers:

content-type: text/html; charset=utf-8
server-timing: processing;dur=52, db;dur=4, db_async;dur=5.902, asn;desc="50266", edge;desc="AMS", country;desc="NL", theme;desc="141749616877", pageType;desc="index", servedBy;desc="6n4w", requestID;desc="49612161-2417-42eb-a1ad-abe83cd88ed9-1729259312", cfRequestDuration;dur=194.000006
x-request-id: 49612161-2417-42eb-a1ad-abe83cd88ed9-1729259312

2024-10-18T13:48:32.908Z: Request to https://xxxxxxxxxxx.myshopify.com/password completed in 223 ms
With response headers:

content-type: text/html; charset=utf-8
server-timing: processing;dur=11, db;dur=3, db_async;dur=11.743, asn;desc="50266", edge;desc="AMS", country;desc="NL", pageType;desc="password", servedBy;desc="p82n", requestID;desc="9b93dffb-2a1e-4981-8582-9b695ddcc820-1729259312", cfRequestDuration;dur=149.999857
x-request-id: 9b93dffb-2a1e-4981-8582-9b695ddcc820-1729259312

2024-10-18T13:48:33.193Z: Request to https://xxxxxxxxxxx.myshopify.com/admin/api/unstable/themes/141749616877/assets.json?fields=key%2Cchecksum completed in 284 ms
With response headers:

content-type: application/json; charset=utf-8
server-timing: processing;dur=92, cfRequestDuration;dur=233.999968
x-request-id: c8216470-ad46-49df-abd7-b45d12ccff81-1729259312

Warning: The pattern 'templates/.json' does not include subdirectories. To maintain backwards compatibility, we have modified your pattern to templates/**/.json to explicitly include subdirectories.
2024-10-18T13:48:33.325Z: Ignoring theme file config/settings_data.json via .shopifyignore...
2024-10-18T13:48:33.329Z: Ignoring theme file sections/footer-group.json via .shopifyignore...
2024-10-18T13:48:33.330Z: Ignoring theme file sections/header-group.json via .shopifyignore...
2024-10-18T13:48:33.341Z: Ignoring theme file snippets/hmac-sha256-salt-key.liquid via .shopifyignore...
2024-10-18T13:48:33.360Z: Ignoring theme file templates/404.json via .shopifyignore...
2024-10-18T13:48:33.360Z: Ignoring theme file templates/cart.json via .shopifyignore...
2024-10-18T13:48:33.360Z: Ignoring theme file templates/article.json via .shopifyignore...
2024-10-18T13:48:33.360Z: Ignoring theme file templates/collection.json via .shopifyignore...
2024-10-18T13:48:33.360Z: Ignoring theme file templates/blog.json via .shopifyignore...
2024-10-18T13:48:33.360Z: Ignoring theme file templates/list-collections.json via .shopifyignore...
2024-10-18T13:48:33.360Z: Ignoring theme file templates/page.brands.json via .shopifyignore...
2024-10-18T13:48:33.360Z: Ignoring theme file templates/page.contact.json via .shopifyignore...
2024-10-18T13:48:33.360Z: Ignoring theme file templates/page.customer-service.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/page.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/page.styles.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/password.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/product.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/index.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/search.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/metaobject/store.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/customers/account.club.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/customers/account.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/customers/account.logout.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/customers/account.orders.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/customers/account.password.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/customers/account.retour.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/customers/activate_account.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/customers/addresses.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/customers/order.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/customers/register.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/customers/reset_password.json via .shopifyignore...
2024-10-18T13:48:33.361Z: Ignoring theme file templates/customers/login.json via .shopifyignore...
2024-10-18T13:48:33.362Z: Files to be uploaded:
-assets/back-to-top.js
-assets/index-DimvNaNS.js
-assets/main-utilities.css
-locales/en-dev.default.json
-snippets/format-input.liquid
-snippets/format-textarea.liquid
2024-10-18T13:48:33.362Z: Uploading the following files:
-snippets/format-input.liquid
-snippets/format-textarea.liquid
-locales/en-dev.default.json
-assets/back-to-top.js
-assets/index-DimvNaNS.js
-assets/main-utilities.css
╭─ success ─────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  Preview your theme                                                                   │
│    • http://<IP_ADDRESS>:9292                                                            │
│                                                                                │
│  Next steps                                                                           │
│    • Customize your theme at the theme editor                                         │
│    • Share your theme preview                                                         │
│      (https://xxxxxxxxxxx.myshopify.com/?preview_theme_id=141749616877)         │
│                                                                                │
╰───────────────────────────────────────────────────────────────────────────────────────╯
2024-10-18T13:48:33.388Z:
Running system process:
· Command: npm prefix
· Working directory: /Users/royvn/Projects/shopify-xxxxxxxxxxx/dist
2024-10-18T13:48:33.487Z: Obtaining the dependency manager in directory .....
2024-10-18T13:48:33.566Z:
Running system process:
· Command: ruby -v
· Working directory: /Users/royvn/Projects/shopify-xxxxxxxxxxx/dist
2024-10-18T13:48:33.766Z: Request to https://monorail-edge.shopifysvc.com/v1/produce completed in 186 ms
With response headers:

x-request-id: 557434ec-3179-46a7-b164-7594ac8e9486

2024-10-18T13:48:33.766Z: Analytics event sent: {
"command": "theme dev",
"time_start":<PHONE_NUMBER>074,
"time_end":<PHONE_NUMBER>384,
"total_time": 3310,
"success": true,
"cli_version": "3.68.1",
"ruby_version": "2.6.10",
"node_version": "20.18.0",
"is_employee": false,
"uname": "darwin arm64",
"env_ci": false,
"env_plugin_installed_any_custom": false,
"env_plugin_installed_shopify": "["@shopify/cli"]",
"env_shell": "zsh",
"env_device_id": "af656900cae58487dea1d19479244abfb1c7c074",
"env_cloud": "localhost",
"env_package_manager": "pnpm",
"env_is_global": true,
"env_auth_method": "device_auth",
"cmd_app_warning_api_key_deprecation_displayed": false,
"cmd_all_timing_network_ms": 3007,
"cmd_all_timing_prompts_ms": 0,
"cmd_all_launcher": "unknown",
"cmd_all_topic": "theme",
"cmd_all_plugin": "@shopify/theme",
"cmd_all_force": false,
"cmd_all_verbose": true,
"cmd_all_path_override": true,
"cmd_all_path_override_hash": "6f670b85bb906dc28ff596586e566cbe2883e662",
"cmd_all_timing_active_ms": 302,
"cmd_all_exit": "ok",
"user_id": "310afc4a-0260-4cb2-aa5e-301bd44071c3",
"args": "--verbose",
"env_plugin_installed_all": "["@shopify/cli"]",
"metadata": "{"extraPublic":{},"extraSensitive":{}}"
}
2024-10-18T13:48:33.766Z: Completed command theme dev
2024-10-18T13:48:34.275Z: Request to https://xxxxxxxxxxx.myshopify.com/admin/api/unstable/themes/141749616877/assets/bulk.json completed in 912 ms
With response headers:

content-type: application/json
server-timing: processing;dur=223, cfRequestDuration;dur=881.000042
x-request-id: dd89c1fa-a152-446f-8623-ac8c4cbdf855-1729259313

Error: Upload failed, could not reach the server
at bulkUploadThemeAssets (file:///Users/royvn/Library/pnpm/global/5/.pnpm/@shopify+cli@3.68.1/node_modules/@shopify/cli/dist/index.js:145204:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async handleBulkUpload (file:///Users/royvn/Library/pnpm/global/5/.pnpm/@shopify+cli@3.68.1/node_modules/@shopify/cli/dist/index.js:148757:17)
at async uploadBatch (file:///Users/royvn/Library/pnpm/global/5/.pnpm/@shopify+cli@3.68.1/node_modules/@shopify/cli/dist/index.js:148747:9)
at async Promise.all (index 0)
at async Promise.all (index 1)
Reproduction steps

Run shopify theme dev

Operating System
macOS Sonoma (14.5)
Shopify CLI version (check your project's package.json if you're not sure)
3.68.1
Shell
zsh
Node version (run node -v if you're not sure)
20.18.0
What language and version are you using in your application?
No response

I tried the new CLI version 3.69.0. The error looks different now.

I have the same issue after updating to newest shopify cli version 3.69.2
Always getting Upload failed, could not reach the server

After debugging the bulkUploadThemeAssets() function, it seemed that actually the 207 is thrown wrongly in some cases, most distinctively it seems that certain upload reponses are status 207 even though they contain a perfectly fine response single object (one object in array, not what you would expect from a 207).
I dont know the internals well enough why the 207 is thrown here and why it would constitute a "cannot reach server" if there is a 207 which says "everything ok", but just commenting out that error
// if (response.status !== 207)
  //   throw new AbortError("Upload failed, could not reach the server");

solves the issue and themes get updated fine.
So I would definitely file that as a bug (according to my limited competence here).
Would be good to hear a comment from the shopify theme, since I maybe that error is needed in other cases.

My current workaround is to use a different shop to work on with shopify theme dev. Then, I use the shopify theme push command to push the changes to the shop that’s not working.

I am getting the exact same issues, i just upgraded the CLI.. so fustrating.

Looks like this is now fixed in version 3.70.0. Connecting to the store works again 🎉.

The error has returned, it already happens to me in 2 stores


Optimize logo

Optimized logo, with https://jakearchibald.github.io/svgomg/ (svgo)

Hi @MartijnCuppens. Thank you for this optimization :) Approved :)


edk2-hikey: create bootloader/ directory prior to usage

Signed-off-by: Daniel Díaz<EMAIL_ADDRESS>

Needs propagation to Morty and Rocko.


Add option to verify checksum without requiring write access to remote objects

Add option to verify checksum without requiring write access to remote objects and without requiring to upload new data.
I wanted to check some data uploaded by another user, which I can read, but with the current mango-ingest, I can't verify the checksums as it requires write permissions to remote object by default.
Trying to run the --dry-run option with --verify-checksum does not work for just checking the checksum as it will just print dry-run: would upload /path/to/file
$ mango_ingest.py -r -p local_dir/ -d /irods --verify-checksum --verbose --no-watch --dry-run

Indeed, checksum operations require write access to the object by the user executing the code. That is not something that I/we can change as it is the way the irods backend works. Maybe a stricter checking of access rights should be added?

I don't see why it shouldn't be possible to retrieve a precalculated checksum from iRODS as a user with read only rights. If that is really not possible it is something that should be fixed in the iRODS backend.


Need CVSSv3.1 or 3.0 specification in reports

Dependency-check tool is already reporting the CVSSv3.1 or  3.0 as CvssV3 score but providing no information whether its a Cvssv3.1 or 3.0 score.
For example:
CVE-2019-10174 has v3.1 (8.8) and v3.0(7.5) CVSS scores present in NVD  but the tool reports Cvssv3score as 8.8 with no information about v3.1 or v3.0 specification.
Sample output:
"cvssv3": {
"baseScore": 8.8,
"attackVector": "NETWORK",
"attackComplexity": "LOW",
"privilegesRequired": "LOW",
"userInteraction": "NONE",
"scope": "UNCHANGED",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"availabilityImpact": "HIGH",
"baseSeverity": "HIGH"
},
It would be helpful if we could get this information in reports.

ODC will only be able to report what is included in the NVD data feed. We can improve the report to indicate which version is used - but if you look at the data feed for CVE-2019-10174 the CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H is provided by the CNA and does not appear to be included. Only the CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H is in the datafeed.

This will be included in the 6.0.0 release. See PR #2781 - the version information will not consistently be available on all CVSS entries - it will depend on if the source of the score provides the version information. Currently, this is only supplied by the NVD.


Question: Why not yarn or pnpm?

As far as i know yarn workspaces make work with lerna much more convenient

There're a lot of options, for example cycle.js uses pnpm :)

@raveclassic, description in the linked issue sounds really good

Because npm is an standard and the most stable and long term supported package manager.


Add dockerfile for auto-indexing

The docker image is published to dockerhub as sourcegraph/lsif-java

Ignoring unrelated CI failure


Animated letter

Hey Romain! Thanks for that nice contribution.
I made a lot of suggestions to improve it. Feel free to dig in and it will become amazing.

Thanks for the comments! Updated a few things. Not sure if perfect yet.
About the path vs text, actually this sample is taken from an old version of Zenika Labs' website and the letter is from Zenika's logo, not a known font exactly but close, and I find it cool to show that this can be down on any path :)

I find it cool to show that this can be down on any path :)

If the intent is to make a simple demo to highlight the effects of animating the stroke-dashoffset, I would suggest to add the pathLength attribute to the <path> element so that it allows to provide a cleaner value than "81.1px" 😉
<style>
path {
  stroke-dasharray: 1;
  stroke-dashoffset: 1;
}
</style>
<path pathLength="1" d="…"/>

It's not working (a few pixels are not drawn and the path is not closed properly). To make it work with pageLength=1, I need to have
stroke-dasharray: 1.005;
stroke-dashoffset: 1.005;

Any idea why?


Adds arguments.len() (#1135)

Adds feature request in #1135

Added is_empty()

Shouldn't this be the sum of the lengths of positional and named arguments?

I think .items() fetches all items. In to_posed() and to_named() they filter out the "undesirable" arguments.

This just made me realize that I also didn't quite understand named() and pos(). I thought both of them would just fetch all arguments and not filter out anything.

I made some more notes in the issue that the change might lead to some confusion.

I think there is no clear way forward here, right?

No, especially if the use of arguments might change in the future.


[Backport - newton-14.1] Move GROUP_VARS and HOST_VARS_PATH

These variables are now set in the bootstrap-ansible script. This is to prevent
situations where the deploy re-runs bootstrap-ansible.sh as a stand-alone script,
which would overwrite the variables causing out of scope issues.
In addition, some logic has been added so that the variables are set to their
original value before running the OSA bootstrap playbook. This is so there
are no extra settings when the bootstrap playbook runs.
(cherry picked from commit ce2b72aabc1ab95ebbc9be499973200b633c0841)

closing in favour of https://github.com/rcbops/rpc-openstack/pull/2412 as the branch name is causing problems.


Continued updates to the Cripts docs

Docs are now mostly done, but more examples will be added as well.

Cherry-picked to v10.0.x


MEX

Hello,
I am using matlab2015 and windows 10. While I tried to run the following command in command window, I am getting some errors:
mex chol2invchol.c -lgsl -lblas
Error:
Error using mex
MEX cannot find library 'gsl' specified with the -l option.
MEX looks for a file with one of the names:
libgsl.lib
gsl.lib
Please specify the path to this library with the -L option.
Can you guide me what to do?

Hi, unfortunately we weren't able to test our code on windows 10, but this problem seems to be a result of GSL not being properly installed. Could you try installing GSL


Added code for binary tree level order traversal

Fixes #1964
Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

Sir I have by mistake created the pr before being assigned the issue, please see to it. @Ayush7614 @ravikr126


jdk11 causes fe  unable to write to the fe.log log file

Steps to reproduce the behavior (Required)

docker pull starrocks/fe-ubuntu:2.5.9
docker run -it starrocks/fe-ubuntu:2.5.9 bash
export STARROCKS_HOME=/opt/starrocks/fe
cd /opt/starrocks/fe
bin/start_fe.sh --daemon
cat log/fe.log

Expected behavior (Required)

lots of lines
Real behavior (Required)

only two lines
StarRocks version (Required)

2.5.9

possibly something to do with slf42j version upgrade.

suspicious commit: dfb89fada40a8d5eeadfc5c20c6899289705acf8

I have found the reason, PR is on the way.

i had patched https://github.com/StarRocks/starrocks/pull/27671 to tag2.5.9，still have some issues

i had patched #27671 to tag2.5.9，still have some issues

using LogManager replace LoggerFactory in PluginInfo.java file，still has  some issues in jdk11 env

https://github.com/StarRocks/starrocks/pull/27852 把这个加上试试呢

#27852 把这个加上试试呢


Remove alert box

Already explained on H1 plus has now some triggers in place. Makes the website look friendlier.

:+1:


Distance minimization:SVD or LSQ

Hi,
Thanks for the amazing work.
Does this libpointmatcher use SVD approach or robust least squares for minimizing squared error ?
Regards,
Bruno

It depends of the error minimizer and outlier rejection used in your configuration. Only the point-to-point error used SVD, which can be robustified with a weighted cost function or a binary outlier rejection of your choice. Libpm is not a single registration solution, but a library of modules to build you own solution. If it can help, you can read this survey for more information:
F. Pomerleau, F. Colas and R. Siegwart (2015), "A Review of Point Cloud Registration Algorithms for Mobile Robotics", Foundations and Trends® in Robotics: Vol. 4: No. 1, pp 1-104. https://doi.org/10.1561/2300000035

Thanks for your insight .


Is there any way to print the execution time of SQL, can you give an example?

Here is part of my code, I want to print the consumption time of each SQL statement.
Currently this only prints the executed SQL statements, but not the time consumed by the corresponding statements, is there a way to get the consumption time?
drv, err := sql.Open("mysql", source)
if err != nil {
log.Fatalf("failed opening connection to mysql: %v", err)
}
drvWithContext := dialect.DebugWithContext(drv, func(ctx context.Context, i ...interface{}) {
log.WithContext(ctx).Debug(i)
})
db := drv.DB()
db.SetMaxIdleConns(50)
db.SetMaxOpenConns(5)
db.SetConnMaxLifetime(time.Hour)
client := ent.NewClient(ent.Driver(drvWithContext), ent.Log(log.Debug))

Hey @issone!
You can implement a custom driver that handles this for you. For example:
// DebugDriver is a driver that logs all driver operations.
type DebugDriver struct {
	Driver                               // underlying driver.
	log    func(context.Context, ...any) // log function. defaults to log.Println.
}

// Exec logs its params and calls the underlying driver Exec method.
func (d *DebugDriver) Exec(ctx context.Context, query string, args, v any) error {
	start := time.Now()
	err := d.Driver.Exec(ctx, query, args, v)
	d.log(ctx, fmt.Sprintf("driver.Exec: query=%v args=%v time=%v", query, args, time.Since(start)))
	return err
}

// ...

Please, see the full example here and feel free to join our Discord community in case you need more help with this 😎

Thanks, it solved my problem

Hey @issone! You can implement a custom driver that handles this for you. For example:
// DebugDriver is a driver that logs all driver operations.
type DebugDriver struct {
	Driver                               // underlying driver.
	log    func(context.Context, ...any) // log function. defaults to log.Println.
}

// Exec logs its params and calls the underlying driver Exec method.
func (d *DebugDriver) Exec(ctx context.Context, query string, args, v any) error {
	start := time.Now()
	err := d.Driver.Exec(ctx, query, args, v)
	d.log(ctx, fmt.Sprintf("driver.Exec: query=%v args=%v time=%v", query, args, time.Since(start)))
	return err
}

// ...

Please, see the full example here and feel free to join our Discord community in case you need more help with this 😎

Thanks, it solved my problem


Add Bulla Banker to Optimism Safe App store.

Hello,
I'm a dev at Bulla Network.
We recently deployed our app to Optimism
Would it be possible to add Bulla Banker to Optimism app store?
Much appreciated. Thank you!

Hi there! Sure thing 😄
I have been playing with the app on Optimism and can confirm that it is working nicely there, will ask the team to add it to the list there. We will notify you here when the app is added.
Cheers!

App should be available now


experiment(ark-zkey): Use rkyv for faster loading

Naive experiment for https://github.com/oskarth/mopro/issues/25
Doesn't currently work due to:
error[E0277]: the trait bound `ProvingKey<ark_ec::models::bn::Bn<ark_bn254::Config>>: Archive` is not satisfied
  --> ark-zkey/src/lib.rs:22:30
   |
22 | #[derive(Archive, Serialize, Deserialize, Clone, Debug, PartialEq)]
   |                              ^^^^^^^^^^^ the trait `Archive` is not implemented for `ProvingKey<ark_ec::models::bn::Bn<ark_bn254::Config>>`
   |
   = help: the following other types implement trait `Archive`:
             bool
             char
             isize
             i8
             i16
             i32
             i64
             i128
           and 139 others
   = help: see issue #48214
   = note: this error originates in the derive macro `Deserialize` (in Nightly builds, run with -Z macro-backtrace for more info)

Unclear how complex it is to fix, need to either:

Implement Archive manually for ProvingKey<ark_ec::models::bn::Bn<ark_bn254::Config>>
Use a wrapper type
Or a combination thereof

ProverKey is:
/// The prover key for for the Groth16 zkSNARK.
#[derive(Clone, Debug, PartialEq, CanonicalSerialize, CanonicalDeserialize)]
pub struct ProvingKey<E: Pairing> {
    /// The underlying verification key.
    pub vk: VerifyingKey<E>,
    /// The element `beta * G` in `E::G1`.
    pub beta_g1: E::G1Affine,
    /// The element `delta * G` in `E::G1`.
    pub delta_g1: E::G1Affine,
    /// The elements `a_i * G` in `E::G1`.
    pub a_query: Vec<E::G1Affine>,
    /// The elements `b_i * G` in `E::G1`.
    pub b_g1_query: Vec<E::G1Affine>,
    /// The elements `b_i * H` in `E::G2`.
    pub b_g2_query: Vec<E::G2Affine>,
    /// The elements `h_i * G` in `E::G1`.
    pub h_query: Vec<E::G1Affine>,
    /// The elements `l_i * G` in `E::G1`.
    pub l_query: Vec<E::G1Affine>,
}

Less relevant now, see https://github.com/zkmopro/mopro/pull/118 though


fix ci os image

Signed-off-by: huiwq1990<EMAIL_ADDRESS>
What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

What this PR does / why we need it:

This is a scheduled Ubuntu-18.04 brownout. The Ubuntu-18.04 environment is deprecated and will be removed on December 1st, 2022. For more details, see https://github.com/actions/runner-images/issues/6002Show less

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/lgtm
/approve


Mutations  - FreeCodeCamp - beginner

Can someone explain me why this code is not working?
function mutation(arr) {
for(var i=0; i<arr.length; i++) {
arr[i] = arr[i].toLowerCase();
}
for(var j=0; j<arr[1].length; j++) {
if(arr[0].indexOf(arr[1].charAt(j), 0) !== -1) {
return true;
} else {
return false;
}
}
}
mutation(["hello", "hey"]);
For some reason the letter "y" is not seen by the engine and the return is "true", although is working for all other arguments. I'm trying to understand the behavior of the method.

Please visit the HelpJavaScript Chat for assistance with writing code for the JavaScript challenges.
Issues are for reporting bugs with the challenges or website.
Happy coding!

@for3v3r4u please visit the chat room as directed by @BKinahan

I wrote the same code and am trying to understand what's going on in my loops that causes the "y" to get missed. Any new incite for3v3r4u?


[Feature] Fix submit task privilege error

What type of PR is this：

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #16904 StarRocks/StarRocksTest#1764
Problem Summary(Required) ：

PrivilegeCheckerV2 should also support unqualified table name.
Signed-off-by: Dejun Xia<EMAIL_ADDRESS>Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

[FE PR Coverage Check]
:heart_eyes: pass : 17 / 17 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeCheckerV2.java
17
17
100.00%
[]

run starrocks_admit_test


variable in class removes classes added by v-class

I have following component:

        Irrelevant component

Both currentSection (on component) and selectorGrid (in a mixin) are computed attributes.
When I step through the attribute changes, first the classes get handled and are properly attached to the Node:

Then the computed class gets handled and kicks in the method defaultHandler of ./~/vue/src/directives/attr.js:
function defaultHandler (value) {
  if (value || value === 0) {
    this.el.setAttribute(this.arg, value)
  } else {
    this.el.removeAttribute(this.arg)
  }
}

value being portal portal__filterrows-3 instead of the new classlist from step 4.
Is there a gotcha I'm not aware of (class-vars and v-class don't work together) or is it a wrong implementation of the classlist?

Hey there! I guess it's kinda hard to comment the error without a fiddle. So I finally had the time to create one so you can look at the error (or tell me that it's working as intended):
http://jsfiddle.net/frontender/gdcrobw9/4/

Hmm, the class interpolation sets the class attribute to the evaluated string, which overwrites the classes added by v-class.
I think it maybe worth it to make v-class support taking an object (which you can make as a computed property)

Angular chooses what to do depending on the type received, maybe this is a good way to go:
https://docs.angularjs.org/api/ng/directive/ngClass
I'd also welcome the possibility to using an array:
computed: {
    classes: function() {
        return [
            'icon-octopus',
            isHidden() ? 'is-hidden' : '',
            getBorderClass('home'),
            { 'is-optional': true }
        ]
    }
}

objects are now supported in v-class via https://github.com/yyx990803/vue/commit/4e83218c0cbb85f99485c51938e510a6da2453a3

Cool, thank you very much for the great work! :)
Is there a way to help you push the project forward?

At this moment the most helpful thing is probably hanging out in the Gitter channel and vuejs/Discussions and help people out. Also writing tutorials / blog posts would be great too...


Add Dutch language

Feature description
Add a Dutch translation to the Qiskit Textbook. I’m happy to take the lead.
Alternatives
No response
Additional context
No response

Hi @ianhellstrom ! Thank you for your interest in translating the Qiskit Textbook into Dutch. Per our guidelines, you will need a minimum of three members who can commit to work on the same language.
Can you please encourage members in your community to join your effort and have them leave comments here showing their support?

@ianhellstrom Hi! I noticed you closed this issue? Is everything okay? If there is anything we can do to support, please let us know. Thank you.


builder.yaml conventions

What data is required in the builder.yaml file? How should this data be organized?
Some things we will definitely have:
exec name: the tool building the code (ex: npm, maven)
exec path: path on the user/agents machine to the exec
version: version of exec to use for the build

Supply lock files for each language? node has package-lock.json and yarn.lock
python has Pipfile.lock when using pipfile's as a dependency management and I think its configurable with poetry as well for python


Fixed incorrect gravatar url

There was an issue before always showing no icons, which it shouldnt even if an email isnt registered with gravatar, will show the default icon. Turns out the old link was invalid, and the code needed to be trimmed(precaution) and lowercased as according to:
https://en.gravatar.com/site/implement/hash/

Thank you @stopspazzing!


Setup GoodProtocolUI (Goodswap.xyz)

install nvm (if don't have it yet)
> nvm install 16.17.0
> nvm use 16.17.0
clone repo https://github.com/GoodDollar/GoodProtocolUI
install packages via yarn
download .env file pinned by Lewis B in the Slack #devs channel:

place it onto project root
run project yarn start

ask me or Lewis in Slack if any issues will happen

Installed and raised locally successfully. Started, everything is ok. Packages were installed with yarn 3


Use the precompiled Docker image as the default

Yes, it would probably be good to have the precompiled image as default (i.e. latest tag).
Maybe we should keep the image without precompiled sysimage, at least for some time, with a different tag?
Btw. have you checked how large the startup / performance gain of the sysimage version is?


Create pull request and merge first release

With the template done, commit it and merge into the main branch

Develope has been merged to main


Create draft tap/target maintainer guide

@rwfeather @cjohnhanson I can't seem to remove you as reviewers on this draft but feel free to ignore for now.

Related issues:

https://github.com/meltano/internal-marketing/issues/721
https://github.com/meltano/internal-marketing/issues/620

Still need to answer: ---
## What happens if a repo gets deleted? I don’t want to risk using a variant if it could be deleted in the future? Should I be keeping a fork in my own namespace? Hard fork?
This is something that happened on npm and it ended up breaking thousands of builds. Should we mirror the ones we know about? That's a huge undertaking.

@DouweM @sbalnojan @tayloramurphy @pnadolny13 @aaronsteers Here's where I'm at with the draft of the add a tap guide as well as the tap maintainer guide. I'd love to get your feedback on it so far and can implement it when I get back from break. Thanks!
There are two TBD sections:
How can I become a maintainer in MeltanoLabs? and How do I stop being a maintainer?
Do we have a process for adding maintainers to MeltanoLabs? I know we've added folks in the past but I vaguely remember there being some permissions issue with that.
If folks want to step down I think they can just post it on Slack or open an issue somewhere. Does Singer Most Wanted make sense?

There are two TBD sections:
How can I become a maintainer in MeltanoLabs? and How do I stop being a maintainer?
Do we have a process for adding maintainers to MeltanoLabs? I know we've added folks in the past but I vaguely remember there being some permissions issue with that.
If folks want to step down I think they can just post it on Slack or open an issue somewhere. Does Singer Most Wanted make sense?

Seems like some of this content overlaps with the content in https://github.com/MeltanoLabs/Meta that @pnadolny13 created when we were starting things up. As an aside, we probably should cross-link or merge content between these two sources were applicable or overlapping. This page may also address some of the questions on 'how are folks added'. Admittedly, we may still want to update/change those processes, but there is some process documentation there we can use, recycle, or change.

Still need to answer:
## What happens if a repo gets deleted? I don’t want to risk using a variant if it could be deleted in the future? Should I be keeping a fork in my own namespace? Hard fork?
This is something that happened on npm and it ended up breaking thousands of builds. Should we mirror the ones we know about? That's a huge undertaking.

We don't have a mitigation as of now but if it is a broad concern, we should absolutely create a new issue to propose solutions. Meltano Cloud will likely cache at least the virtualenv directories at some time in the future, and we could also consider serving from our own PyPi-like server, but caching or archiving the repo itself is another matter.
Any way we want to solve this though, the scope is very large.

@aaronsteers Thanks for the meta link! I totally forgot about that repo. Good stuff.
The mirroring question came up in one of the issues related to this PR. For now I think it's enough to just mention that folks may want to create their own mirrors if they depend on a plugin in production, personally.

@pnadolny13 @tayloramurphy @sbalnojan Would you mind reviewing? Thanks!

@aaronsteers I added a new dropdown for docs as that seemed like the best place to put these sorts of things. Will that work?
@DouweM Just FYI in case the website team has already made wireframes for this. I think going forward we should make the docs more obvious on the hub.

@tayloramurphy Does the dropdown work for you? I think having a docs section is probably good here.

@afolson I've seen this weird error youre getting before https://github.com/meltano/hub/actions/runs/3998314494/jobs/6860791848, if you update your branch this usually goes away.


web: icon button error

Flutter Web:
IconButton
Error: Operator '+' cannot be called on 'double?' because it is potentially null.
Launching lib\main.dart on Chrome in debug mode...
Waiting for connection from debug service on Chrome...
../../flutter/.pub-cache/hosted/pub.dartlang.org/one_ui-0.3.1/lib/src/widgets/buttons/icon_button.dart:124:25: Error: Operator '+' cannot be called on 'double?' because it is potentially null.
              (iconSize + math.min(padding.horizontal, padding.vertical)) * 0.7,
                        ^
Failed to compile application.

[√] Flutter (Channel master, 2.6.0-12.0.pre.732, on Microsoft Windows [Version 10.0.19042.1348], locale ko-KR)
• Flutter version 2.6.0-12.0.pre.732 at C:\Dev\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 7dcdfe6304 (4 hours ago), 2021-11-17 01:08:05 +0200
• Engine revision<PHONE_NUMBER>
• Dart version 2.16.0 (build 2.16.0-14.0.dev)
• DevTools version 2.8.0
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at C:\Users\SintPatrick\AppData\Local\Android\sdk
• Platform android-30, build-tools 30.0.3
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.8.4)
• Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
• Visual Studio Community 2019 version 16.8.30907.101
• Windows 10 SDK version 10.0.18362.0
[√] Android Studio (version 2020.3)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
[√] VS Code (version 1.52.1)
• VS Code at C:\Users\SintPatrick\AppData\Local\Programs\Microsoft VS Code
• Flutter extension can be installed from:
https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[√] Connected device (3 available)
• Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19042.1348]
• Chrome (web)      • chrome  • web-javascript • Google Chrome 95.0.4638.69
• Edge (web)        • edge    • web-javascript • Microsoft Edge 94.0.992.50
• No issues found!

change it to "iconSize!"


Azure Container Instances is/are not defined on "What is Azure Container Instances?" page

This page is titled, "What is Azure Container Instances?" but nowhere on the page do you state what Azure Container Instances is or are.  It reads like sales copy, not like technical documentation.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 5c00e2ca-c968-c339-c4f2-6acebc9c4f2f
Version Independent ID: 46b156b3-b879-22ba-3194-1655137ae127
Content: Serverless containers in Azure - Azure Container Instances
Content Source: articles/container-instances/container-instances-overview.md
Service: container-instances
GitHub Login: @tomvcassidy
Microsoft Alias: tomcassidy

The closest thing to such a definition I find is, "Azure Container Instances is a great solution for any scenario that can operate in isolated containers, including simple applications, task automation, and build jobs."

@pmocek
Thanks for your feedback! We will investigate and update as appropriate.

Hi @pmocek
Azure Container Instances is a service offered by Microsoft Azure that allows you to run isolated containers in the cloud without having to manage virtual machines or adopt a higher-level orchestrator. It provides the fastest and simplest way to run containers in Azure.
https://learn.microsoft.com/en-us/azure/container-instances/container-instances-orchestrator-relationship#:~:text=Azure Container Instances enables a layered approach to orchestration%2C providing all of the scheduling and management capabilities required to run a single container%2C while allowing orchestrator platforms to manage multi-container tasks on top of it.
For reference :
https://learn.microsoft.com/en-us/azure/container-instances/container-instances-orchestrator-relationship

@pmocek
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Not working with Parallels 12 Pro on Sierra

OS version: 10.12.3
Parallels version: 12.1.3
Attempting to share the user directory fails at the Verify NFS mount message.

@mchadwickchennault would you be able to provide the fix? We are not using Parallels so it could take some time to have a fix.

Turns out this is not an issue. The problem was an anit-virus program installed by my IT department. Closing issue. Sorry for the fire drill.

@mchadwickchennault No problem. Is good to know this can cause issues too ;)


coco_eval_script script with yolov7_w6_coco.h5 leads to low AP

Hi all,
Due to some reason I get low AP (much lower than expected as far as I understand) when test with default yolov7_w6_coco.h5 model (downloaded from this repo) -
The command I run python coco_eval_script.py -m "./yolov7_w6_coco.h5"
Output:
Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.082
Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=100 ] = 0.118
Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=100 ] = 0.086
Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.032
Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.077
Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.164
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=  1 ] = 0.090
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets= 10 ] = 0.135
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.141
Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.045
Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.138
Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.269
When I look into detections by eyes during inference they look good.
Does anyone know what can be the reason? Thank you very much.

Full script output below just in case. Thank you.
`2023-12-14 22:21:45.470630: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-12-14 22:21:46.633040: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /opt/amazon/efa/lib:/opt/amazon/openmpi/lib:/usr/local/cuda/efa/lib:/usr/local/cuda/lib:/usr/local/cuda:/usr/local/cuda/lib64:/usr/local/cuda/extras/CUPTI/lib64:/usr/local/cuda/targets/x86_64-linux/lib:/usr/local/lib:/usr/lib:/opt/amazon/efa/lib:/opt/amazon/openmpi/lib:/usr/local/cuda/efa/lib:/usr/local/cuda/lib:/usr/local/cuda:/usr/local/cuda/lib64:/usr/local/cuda/extras/CUPTI/lib64:/usr/local/cuda/targets/x86_64-linux/lib:/usr/local/lib:/usr/lib
2023-12-14 22:21:46.633163: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /opt/amazon/efa/lib:/opt/amazon/openmpi/lib:/usr/local/cuda/efa/lib:/usr/local/cuda/lib:/usr/local/cuda:/usr/local/cuda/lib64:/usr/local/cuda/extras/CUPTI/lib64:/usr/local/cuda/targets/x86_64-linux/lib:/usr/local/lib:/usr/lib:/opt/amazon/efa/lib:/opt/amazon/openmpi/lib:/usr/local/cuda/efa/lib:/usr/local/cuda/lib:/usr/local/cuda:/usr/local/cuda/lib64:/usr/local/cuda/extras/CUPTI/lib64:/usr/local/cuda/targets/x86_64-linux/lib:/usr/local/lib:/usr/lib
2023-12-14 22:21:46.633183: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2023-12-14 22:21:47.605630: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-12-14 22:21:47.643166: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-12-14 22:21:47.643429: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-12-14 22:21:48.192193: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-12-14 22:21:48.192900: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-12-14 22:21:48.193151: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-12-14 22:21:48.193343: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-12-14 22:21:48.955434: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-12-14 22:21:48.955696: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-12-14 22:21:48.955901: I tensorflow/compiler/xla/stream_executor/cuda/cuda_gpu_executor.cc:981] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2023-12-14 22:21:48.956078: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1613] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 14612 MB memory:  -> device: 0, name: Tesla V100-SXM2-16GB, pci bus id: 0000:00:1e.0, compute capability: 7.0
/home/ubuntu/.pyenv/versions/yolov7/lib/python3.9/site-packages/keras/initializers/initializers_v2.py:120: UserWarning: The initializer VarianceScaling is unseeded and being called multiple times, which will return identical values  each time (even if the initializer is unseeded). Please update your code to provide a seed to the initializer, or avoid using the same initalizer instance more than once.
warnings.warn(
WARNING:tensorflow:From /home/ubuntu/.pyenv/versions/yolov7/lib/python3.9/site-packages/tensorflow/python/autograph/pyct/static_analysis/liveness.py:83: Analyzer.lamba_check (from tensorflow.python.autograph.pyct.static_analysis.liveness) is deprecated and will be removed after 2023-09-23.
Instructions for updating:
Lambda fuctions will be no more assumed to be used in the statement where they are used, or at least in the same block. https://github.com/tensorflow/tensorflow/issues/56089
WARNING:tensorflow:From /home/ubuntu/.pyenv/versions/yolov7/lib/python3.9/site-packages/tensorflow/python/autograph/pyct/static_analysis/liveness.py:83: Analyzer.lamba_check (from tensorflow.python.autograph.pyct.static_analysis.liveness) is deprecated and will be removed after 2023-09-23.
Instructions for updating:
Lambda fuctions will be no more assumed to be used in the statement where they are used, or at least in the same block. https://github.com/tensorflow/tensorflow/issues/56089

COCO evaluation: coco/2017

image: {'resize_method': 'bicubic', 'resize_antialias': True, 'rescale_mode': 'auto', 'use_bgr_input': False}
anchors: {'anchor_scale': 4, 'anchors_mode': None, 'aspect_ratios': (1, 2, 0.5), 'num_scales': 3}
nms: {'nms_score_threshold': 0.001, 'nms_iou_or_sigma': 0.5, 'nms_max_output_size': 100, 'nms_method': 'gaussian', 'nms_mode': 'per_class', 'nms_topk': 5000}

[COCOEvalCallback] input_shape: (640, 640), pyramid_levels: [3, 6], anchors_mode: yolor
loading annotations into memory...
Done (t=0.80s)
creating index...
index created!
0%|          | 0/625 [00:00<?, ?it/s]2023-12-14 22:21:56.228521: I tensorflow/compiler/xla/stream_executor/cuda/cuda_dnn.cc:428] Loaded cuDNN version 8700
100%|██████████| 625/625 [04:29<00:00,  2.32it/s]
len(image_ids) = 4928
Loading and preparing results...
Converting ndarray to lists...
(134460, 7)
0/134460
DONE (t=1.20s)
creating index...
index created!
Running per image evaluation...
Evaluate annotation type bbox
DONE (t=21.61s).
Accumulating evaluation results...
DONE (t=5.13s).
Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.082
Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets=100 ] = 0.118
Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets=100 ] = 0.086
Average Precision  (AP) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.032
Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.077
Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.164
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=  1 ] = 0.090
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets= 10 ] = 0.135
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets=100 ] = 0.141
Average Recall     (AR) @[ IoU=0.50:0.95 | area= small | maxDets=100 ] = 0.045
Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets=100 ] = 0.138
Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets=100 ] = 0.269`

Hi,
Was able to get additional context which might be helpful. My end goal is to evaluate TFLite fp32 model produced from yolov7_w6 model.

Evaluation with fp32 tflite produced from yolov7_w6 checkpoint works great during inference (judging by eyes) however during evaluation we are getting the same results as wtih yolov7_w6_coco.h5 checkpoint (reported above) - coco_eval_script.py -m "yolov7_w6_coco_fp32.tflite

Code used to generate the TFLite model -
INPUT_SHAPE = (1280, 1280, 3)
model = yolov7.YOLOV7_W6(pretrained="./model_archive/model_source/yolov7_w6_coco.h5", input_shape=shape)
Then generate TFLite based on this model```

When tried with TFLite produced with static output I am getting errors during evaluation.

2) What's interesting seems that when TFLite is used 1280x1280 shape is used. However when we evaluate with yolov7_w6_coco.h5 model 640x640 shape is used instead.

3) Both
`coco_eval_script.py -m yolov7.YOLOV7_W6 --input_shape 640` and `coco_eval_script.py -m yolov7.YOLOV7_W6 --input_shape 1280` give much better results

Thank you very much for your help.

Ya, I just finished running a basic testing usingpython3 coco_train_script.py -m yolov7.YOLOV7_W6

yield IoU=0.50:0.95 == 0.482. UsingCUDA_VISIBLE_DEVICES=1 ./coco_eval_script.py -m yolor.YOLOR_CSP --nms_method hard --nms_iou_or_sigma 0.65 \
--nms_max_output_size 300 --nms_topk -1 --letterbox_pad 64 --input_shape 704

gives IoU=0.50:0.95 == 0.496. Using --letterbox_pad 64 --input_shape 1344, we can reach IoU=0.535, still a bit lower than the reported 0.549 though.
The main reason for low IoU using loaded h5 is the rescale_mode. This value is autoset to raw01 if using -m yolov7.YOLOV7_W6, but default is torch if loaded from h5, as it's not saved to h5 file. Here raw01 indicates input images are processed to value range in [0, 1]. Trypython3 coco_train_script.py -m ./yolov7_w6_coco.h5 --rescale_model raw01

The h5 saved one is using input_shape=[640, 640, 3], but yolov7.YOLOV7_W6 default using input_shape=[1280, 1280, 3]. Additionally,  sometimes h5 file is not re-uploaded if model architecture changed but weights are reusable. Should better load and save one like:from kecam import yolov7
mm = yolov7.YOLOV7_W6()
mm.save("test.h5")

raw01 did the tirck. Thank you very much for help.


Question: Does biometryType really indicate the primary (most secure) type of biometry supported?

Hello @aparajita 👋
Thanks for creating and maintaining this plugin!
Currently I'm checking what's the best option to implement biometric auth for my Capacitor app and if for iOS everything is clear, then for Android it's not that obvious. Meaning, there could be more than one type availbale and how to handle that properly is the question...
In the doc mentioned that CheckBiometryResult biometryType returns the primary (most secure) type of biometry supported by the device, however in the code  I see that first element from the collection is taken:
biometryTypes = getDeviceBiometryTypes();
result.put("biometryType", biometryTypes.get(0).getType());

And if both FEATURE_FINGERPRINT and FEATURE_FACE are supported, then FEATURE_FINGERPRINT will be returned. @aparajita, is that intentional? 🤔

In my experience Android returns the primary biometry first, that's why I return the first one. On Android there is no way to tell the strength of a particular biometry, so I have to assume the primary biometry is returned first.
As for how to handle multiple types of biometry, take a look at the demo app, I deal with it there. You can, for example, specify that you only want the plugin to return strong biometry.

Thank you!


feat(plugin-vue): set default vue hydration mismatch flag

Summary
The flag was added in the recent Vue 3.4 release.
Related Links
https://vuejs.org/api/compile-time-flags.html#VUE_PROD_HYDRATATION_MISMATCH_DETAILS
Checklist

[x] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

Thanks! ❤


Cleanups to network service

This patch contains some minor improvements to the network service:

We now cache the connection to the network service so we don't need to spin
it up for each request.
We now manage the lifetime of NetworkServiceImpl in the same way as other
services.

Also, update the workbench sky_tools dependency to the latest version.

lgtm


result.value is undefined

This is the code I have for my swal call:
swal({
title: 'Are you sure?',
text: 'Confirm point reset for ' + currentUsers[index].first+'?',
type: 'warning',
showCancelButton: true,
confirmButtonColor: '#3085d6',
cancelButtonColor: '#d33',
confirmButtonText: 'Yes, reset points!'
}).then(function (result) {
if (result.value) {
swal(
'Successfully Reset!',
'Points reset for '+ currentUsers[index].first+'!',
'success'
)
}
else {
console.log("user clicked cancel");
}
}).catch(swal.noop)
For some reason, every time I try to print what result.value is in the console, it always says undefined. I tried changing it to 'if (result) {...} else{...}' but then nothing in the else statement ever happens. I also tried 'if (result.dismiss === 'cancel') {...}' but that doesn't work when the user presses cancel. I just tried swal two days ago and I'm pretty much a novice at this whole entire thing so I'm having trouble figuring out what the issue may be. I would appreciate any help!

make sure you're using the latest stable version
https://jsfiddle.net/ad3quksn/211/

I have version 7.0.3, but it still doesn't work...

it works https://jsfiddle.net/ad3quksn/213/


⚠ ClamAV has degraded performance

In 25df5c1, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 65 ms

Resolved: ClamAV performance has improved in 6243c6b after 16 minutes.


Issue scanning PDF417 barcodes

We are finding that scanning PDF417 barcodes is very problematic.  In most cases the scan never occurs.  In the rare cases we can get a scan to occur it takes a lot of slowly repositioning the barcode to the point the scan takes place.
Are there any known settings or things we can try to help improve scanning PDF417 barcodes?  We rely on this feature heavily.
Thanks.

Hello.
What device and OS do you use? Can you provide a sample barcode?
On my device (Oneplus 7 PRO, Android 12) i find it is best to scan on High quality. On Medium you need to put the device quite close and on Highest the barcode scanning isn't consistent for some reason.
Unfortunately I don't have much experience with iPhones but they were usually better at scanning than Android phones.

I used your sample app - the aim mode helped a lot as did setting the CaptureQuality to High.   I'm able to scan an OR DL, however, TX DL does not seem to scan.  Tried on both Android Pixel 6 and iPhone 13.  Both DLs are PDF417 format.

Aim mode doesn't really do anything to improve scanning performance. It just takes all detected barcodes and removes all of them that don't have their BoundingBox in the centre of the screen.
Sorry, I'm from Europe so I guess that you scan the code that is on US drivers licence, so I guess you can't share exact barcode that doesn't work. It would be very helpful for debugging if you can generate an example PDF417 barcode with data that would be on the drivers licence ant that doesn't work.
In my country PDF417 barcodes are popular for automatic payment of bills and I haven't had a barcode not detected. But their encoded data is less complex.
It could happen that the encoded data is crashing the app but it is really unlikely as I'm doing minimal processing on encoded data. But than again it is weird that it can't be detected on both iOS and Android...
TLDR It would be really useful to have an example of a barcode that isn't working.

@afriscic would you be interested in contacting me directly<EMAIL_ADDRESS>for more details about this?  Thx

@afriscic Attached is a sample PDF417 that scans fine with QR reader, however, it does not scan with this code.  Thoughts?
DL Barcode-Reatiler (002).pdf

Thank you for sharing.
I found a bug on iOS/MacCatalyst that would prevent scanning PDF417 barcodes if you set BarcodeSymbologies to PDF417 only. I'll publish a new release later today.
On my Android phone (Oneplus 7 Pro, Android 12) the barcode is scanned correctly on current version.

I have a Pixel 6 and am on 1.5.2 however the barcode still won't scan for me.


NullReferenceException in DefaultBitmapLoader.ctor

For example, if Markdown is created in method called via Avalonia method binding, there is a dynamically compiled method in the stack trace (the method compiled by MethodToCommandConverter.CreateExecute ). This method have no declaring type, thus we have a NullReferenceException

v0.10.9 was released to fix this issues.


Tubes don't act "round robin"

Using Minecraft 1.12.1, Teckle version git-1cc9a5d, Forge <IP_ADDRESS>2
Shouldn't the tubes evenly distribute the items?
Demonstration: https://gfycat.com/PerkyFlawedBackswimmer

Can't reproduce. Also please use CI version numbers. https://ci.elytradev.com/job/elytra/job/Teckle/job/1.12/
https://gfycat.com/JaggedRaggedGlowworm

Hmm, actually this might be because of the colour tags. Adding colours to my sorting machine and trying again...

Nope, still not happening when I add colours. Round robin ticks and counter stuff is in the network traveller class. If this only happens with your block I'd take a look in there with some breakpoints to determine if you're missing something.

Yeah you're right, whoops. I should test with your blocks too next time…

Heh.


Remove unnecessary trips to the DB

coverage: 94.326% (-0.002%) from 94.328%
when pulling d67d93f9fe29fe4ef9349694cea1028e25232675 on remove-unnecessary-db-trips
into 6d33c090688e4d68eaeb85320c1a11b0c5ff4678 on master.


how to run the saved module in depthwise_conv2d_test.py by shared library?

I am trying to save the module and use it by .so file.
It is f3 (in the depthwise_conv2d_test.py ) which I wanna to save
f3 = tvm.build(s3, [Input, Filter, Scale, Shift, Relu], "cuda")
and
save it by
dylib_path = os.path.join(base_path, "test.so")
f3.export_library(dylib_path)
syslib_path = os.path.join (base_path, "test_sys.o")
f3.save (syslib_path)
and then I change the .cpp file to assign input, filter.. for example，
int ndimx = 4;
int64_t shapex[4] = {1, 2, 2, 2};
TVMArrayAlloc(shapex, ndimx, dtype_code, dtype_bits, dtype_lanes,
device_type, device_id, &x);
for (int i = 0; i < shapex[0]; ++i) {
for (int j = 0; j < shapex[1]; ++j) {
for (int p = 0; p < shapex[2]; ++p) {
for (int q = 0; q < shapex[3]; ++q) {
static_cast<float*>(x->data)[((i*shapex[0]+j)*shapex[1]+p)*shapex[2]+q] = 1;
}
}
}
}
But, the output:
[14:45:33] cpp_deploy.cc:118: Verify dynamic loading from test_.so
[14:45:33] /home/aries/tvm2.0/tvm/dmlc-core/include/dmlc/./logging.h:308: [14:45:33] cpp_deploy.cc:16: Check failed: f != nullptr
Stack trace returned 4 entries:
[bt] (0) lib/cpp_deploy_pack() [0x406d0c]
[bt] (1) lib/cpp_deploy_pack() [0x404c0f]
[bt] (2) /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fd90993e830]
[bt] (3) lib/cpp_deploy_pack() [0x405fc9]
terminate called after throwing an instance of 'dmlc::Error'
what(): [14:45:33] cpp_deploy.cc:16: Check failed: f != nullptr
Stack trace returned 4 entries:
[bt] (0) lib/cpp_deploy_pack() [0x406d0c]
[bt] (1) lib/cpp_deploy_pack() [0x404c0f]
[bt] (2) /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fd90993e830]
[bt] (3) lib/cpp_deploy_pack() [0x405fc9]
Actually, I define the device.
ctx = tvm.context("cuda", 0)
Why Check failed: f != nullptr ?

try https://github.com/dmlc/tvm/pull/645

I tried, its my setting:
#define TVM_CUDA_RUNTIME 1
#include "../src/runtime/cuda/cuda_device_api.cc"
#include "../src/runtime/cuda/cuda_module.cc"
But it still same problem.
Build the libraries..
g++ -c -std=c++11 -O2 -fPIC -I/home/aries/tvm2.0/tvm/include -I/home/aries/tvm2.0/tvm/dmlc-core/include -I/home/aries/tvm2.0/tvm/dlpack/include -I/usr/local/cuda-8.0/include  -o lib/libtvm_runtime_pack.o  tvm_runtime_pack.cc
g++ -std=c++11 -O2 -fPIC -I/home/aries/tvm2.0/tvm/include -I/home/aries/tvm2.0/tvm/dmlc-core/include -I/home/aries/tvm2.0/tvm/dlpack/include -I/usr/local/cuda-8.0/include  -o lib/cpp_deploy_pack  cpp_deploy.cc lib/test_sys.o lib/libtvm_runtime_pack.o -L/home/aries/tvm2.0/tvm/lib -ldl -lpthread -L/usr/local/cuda-8.0/lib64 -lcudart -lnvrtc -lcuda
Run the example
Run the deployment with all in one packed library...
[13:58:34] cpp_deploy.cc:118: Verify dynamic loading from test_.so
[13:58:34] /home/aries/tvm2.0/tvm/dmlc-core/include/dmlc/./logging.h:308: [13:58:34] cpp_deploy.cc:16: Check failed: f != nullptr
Stack trace returned 4 entries:
[bt] (0) lib/cpp_deploy_pack() [0x406d0c]
[bt] (1) lib/cpp_deploy_pack() [0x404c0f]
[bt] (2) /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fbeea292830]
[bt] (3) lib/cpp_deploy_pack() [0x405fc9]
terminate called after throwing an instance of 'dmlc::Error'
what():  [13:58:34] cpp_deploy.cc:16: Check failed: f != nullptr
Stack trace returned 4 entries:
[bt] (0) lib/cpp_deploy_pack() [0x406d0c]
[bt] (1) lib/cpp_deploy_pack() [0x404c0f]
[bt] (2) /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fbeea292830]
[bt] (3) lib/cpp_deploy_pack() [0x405fc9]
./run_example.sh: line 10: 17364 Aborted                 (core dumped) lib/cpp_deploy_pack
Run the deployment with all in normal library...

That error means it failed to get the function from the module, make sure you pass in the same function name as you build the function

You can pass a name argument to the function in the build and can use it refer to the function in loaded module later

Thank you so much!!!

since this causes your confusion, would you like to open a PR to the cpp source to add more comment, and add an error message in CHECK(f!=nullptr)  to give clear error message?
Thanks


Add http landing page with info about the pub and instructions on how to join

Our pubs are running at good domain names. We should have a static web page served from each pub which has the invites, a description of the pub, and how to join.
This needs:

[ ] web design for html page
[ ] some http server added to pubs to sever the page
[ ] adding pages for all the current hosted pubs.

We're not going to do this because we're switching to primarily using rooms instead of pubs as community groups.


Component CSS don't get optimized unless AOT is enabled

Bug Report or Feature Request (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions
Angular CLI: 7.1.0
Node: 11.1.0
OS: darwin x64
Angular: 7.1.1
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.11.0
@angular-devkit/build-angular     0.11.0
@angular-devkit/build-optimizer   0.11.0
@angular-devkit/build-webpack     0.11.0
@angular-devkit/core              7.1.0
@angular-devkit/schematics        7.1.0
@angular/cli                      7.1.0
@ngtools/webpack                  7.1.0
@schematics/angular               7.1.0
@schematics/update                0.11.0
rxjs                              6.3.3
typescript                        3.1.6
webpack                           4.23.1

Repro steps

ng new css-test
p {color: white}' > src/app/app.component.css
ng build --prod --noAot --noBuildOptimizer

The log given by the failure
At the moment, when AOT is disabled components styles are not being optimised. Ie, cleancss is not running.
So for instance the above code, it should have been minified to p {color: #fff}. But this is only happening when using the AOT compiler.
Desired functionality
Component styles should be minified both when using the JIT and AOT Compiler.

Closing, since as JIT shouldn't be used if you care about bundle sizes.