Failed to deploy<EMAIL_ADDRESS>edge runtime - Error: Failed to publish your Function.

Failed to deploy<EMAIL_ADDRESS>edge runtime - Error: Failed to publish your Function.
23:31:16.048 |
23:31:16.102 | AAGresult: null
23:31:16.102 | Uploading... (25/26)
23:31:16.102 |
23:31:16.103 | AAG Uploading... (26/26)
23:31:16.103 |
23:31:16.105 | ✨ Success! Uploaded 3 files (23 already uploaded) (1.48 sec)
23:31:16.106 |
23:31:16.482 | ✨ Upload complete!
23:31:19.554 | Success: Assets published!
23:31:21.022 |
Error: Failed to publish your Function. Got error: Uncaught Error: Some functionality, such as asynchronous I/O, timeouts, and generating random values, can only be performed while handling a request.
  at bundledWorker-0.0805608756143057.mjs:2175:18 in o
  at bundledWorker-0.0805608756143057.mjs:2165:210 in ln
  at bundledWorker-0.0805608756143057.mjs:2176:19 in wake
  at bundledWorker-0.0805608756143057.mjs:2192:23 in Nn
  at bundledWorker-0.0805608756143057.mjs:2106:11 in Wr
  at bundledWorker-0.0805608756143057.mjs:2902:16
  at bundledWorker-0.0805608756143057.mjs:2901:9 in registerPlugin
  at bundledWorker-0.0805608756143057.mjs:1747:14 in Gm
  at bundledWorker-0.0805608756143057.mjs:21987:14 in f

This is just a simple NextJS with Contentful CMS webapp, calling getStaticProps and getStaticPaths on built time, not using any Functions. No intention to make it static export because I need to leverage on Next Image optimization and server functions in the future.
Build command: npx @cloudflare/next-on-pages --experimental-minify
Build output directory: /.vercel/output/static
Root directory: /
Repo: https://github.com/tengweiherr/jamstack-herr.my-edge
"next": "13.2.1"
"react": "18.2.0"
NODE_VERSION: 16.18.1

Same here. Using app dir and next v. 13.2.4.

Can someone try the BuildIO/Qwik plugin solution here: https://github.com/vendure-ecommerce/storefront-qwik-starter
(i) create this file /functions)/[[path]].ts
//Point to compiled output Cloudflare Pages Functions
//but need to mix all api in one, here it is idea
export { onRequest } from '../.next/server/pages/api/hello';

Can someone try the BuildIO/Qwik plugin solution here: https://github.com/vendure-ecommerce/storefront-qwik-starter (i) create this file /functions)/[[path]].ts
//Point to compiled output Cloudflare Pages Functions
//but need to mix all api in one, here it is idea
export { onRequest } from '../.next/server/pages/api/hello';

That's quite different from what we do (generate an _worker.js) but it basically produces the same type of result, I doubt it's going to help the situation 😕
Using functions/[[path]].ts also generates some limitations which we want to avoid (since for example it forces your code to get bundled by wrangler which prevents perf improvements like runtime lazy loading)

I've looked into this and is seems like the request handling fails because gsap runs this setTimeout in what I believe is its global setup: gsap wake's setTimeout.
(PS: I did try, and if you remove all gsap usages from your app then it can be successfully deployed)
I think that this is quite likely an issue with gsap SSR on Cloudflare Pages and not next-on-pages specific, for example I did try deploying the first of their sveltekit starters but it's failing deployment, so I think they are just not correctly set for doing SSR in Pages 😕
Surprisingly I did try to run a very simple Remix app using gsap and it seems to be working (repo), so maybe there are instances in which gsap does work and some where it doesn't? (I'm really not familiar with gsap so I am not really sure).
@tengweiherr what do you think? you seem quite familiar with gsap, do you when when and if they do some initial setup? and if you can have a way to delay that until the page is viewed in a browser? (I wonder if converting things to use dynamic imports could help)

Not sure if it's the same issue, but I'm using app directory, and everything works in dev and when i run my build locally, but when i deploy with npx @cloudflare/next-on-pages --experimental-minify`, all routes return 404, but the layout runs fine. there's no _worker.js file. any idea how to fix/diagnose?

Not sure if it's the same issue, but I'm using app directory, and everything works in dev and when i run my build locally, but when i deploy with npx @cloudflare/next-on-pages --experimental-minify`, all routes return 404, but the layout runs fine. there's no _worker.js file. any idea how to fix/diagnose?

Hello @justinh00k, as you have no worker file, it is not related to this issue. It sounds like one of two things is happening.
If you have any server side functionality, it might only be building functions for the nodejs runtime, and we are therefore not able to find any. This can be fixed by specifying the edge runtime for pages with server side functionality.
i.e. export const runtime = 'edge';
Your site is statically generating HTML files at build time for all your pages. In the current routing implementation, we don't handle this scenario properly, and so it won't be able to properly map routes to static HTML files, and also won't find any functions to generate the worker file from. This should be fixed with the new routing system (#129).
Getting a look at the build log will help to confirm either one of these cases.
When you say it works in dev, are you referring to next dev? If so, yeah, it will work as that uses Next.js' own dev server and routing implementation, which is completely different. To test with next-on-pages locally, you need to follow the instruction in the readme.

@james-elicx Yes, it only works in next dev and not with next-on-pages (locally or deployed.)
Build output looks like this:
⚡ @cloudflare/next-on-pages CLI v.0.9.0 ⚡ Detected Package Manager: npm ⚡ Preparing project... ⚡ Project is ready ⚡ Building project... ▲  Vercel CLI 28.20.0 ▲  WARNING: You should not upload the .nextdirectory. ▲  Installing dependencies... ▲  up to date in 2s ▲   ▲  281 packages are looking for funding ▲  runnpm fundfor details ▲  Detected Next.js version: 13.3.1 ▲  Detectedpackage-lock.jsongenerated by npm 7+... ▲  Running "npm run build" ▲  ><EMAIL_ADDRESS>build ▲  > NEXT_PUBLIC_CF_PAGES_COMMIT_SHA=$CF_PAGES_COMMIT_SHA NEXT_PUBLIC_CF_PAGES_BRANCH=$CF_PAGES_COMMIT_SHA next build ▲  info  - Loaded env from /Users/justinhook/Code/askmi/.env.local ▲  info  - Loaded env from /Users/justinhook/Code/askmi/.env.production ▲  info  - Loaded env from /Users/justinhook/Code/askmi/.env ▲  warn  - You have enabled experimental feature (appDir) in next.config.mjs. ▲  warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk. ▲  info  - Thank you for testingappDirplease leave your feedback at https://nextjs.link/app-feedback ▲  info  - Creating an optimized production build... ▲  info  - Compiled successfully ▲  info  - Linting and checking validity of types... ▲  info  - Collecting page data... ▲  info  - Generating static pages (0/22) ▲  warn  - Entire page /about deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /about ▲  warn  - Entire page /settings deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /settings ▲  warn  - Entire page /404 deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /404 ▲  info  - Generating static pages (5/22) ▲  warn  - Entire page / deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering / ▲  warn  - Entire page /surveys/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /surveys/[shortname] ▲  warn  - Entire page /notifications deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /notifications ▲  warn  - Entire page /admin deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /admin ▲  warn  - Entire page /surveys deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /surveys ▲  warn  - Entire page /profile deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /profile ▲  info  - Generating static pages (10/22) ▲  warn  - Entire page /questions deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions ▲  warn  - Entire page /surveys/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /surveys/[shortname] ▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname] ▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname] ▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname] ▲  info  - Generating static pages (16/22) ▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname] ▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname] ▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname] ▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname] ▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname] ▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname] ▲  info  - Generating static pages (22/22) ▲  info  - Finalizing page optimization... ▲   ▲  Route (app)                                Size     First Load JS ▲  ┌ ○ /                                      7.36 kB         656 kB ▲  ├ ○ /_not-found                            0 B                0 B ▲  ├ ○ /about                                 6.13 kB         314 kB ▲  ├ ○ /admin                                 187 kB          577 kB ▲  ├ ○ /notifications                         0 B                0 B ▲  ├ ○ /profile                               434 B           659 kB ▲  ├ λ /profile/[shortname]                   504 B           659 kB ▲  ├ ○ /questions                             1.18 kB         642 kB ▲  ├ ● /questions/[shortname]                 870 B           600 kB ▲  ├   ├ /questions/favorite-color ▲  ├ ○ /settings                              0 B                0 B ▲  + First Load JS shared by all              97.3 kB ▲  ├ chunks/2443530c-eb76b5fe38a88953.js    50.6 kB ▲  ├ chunks/5122-49299bab9dd798df.js        21.2 kB ▲  ├ chunks/8139-3789e2bb3281d5d5.js        23.4 kB ▲  ├ chunks/main-app-498434a275a1a6ba.js    226 B ▲  └ chunks/webpack-ef5ee84685c4d9a6.js     1.88 kB ▲   ▲  Route (pages)                              Size     First Load JS ▲  ─ ○ /404                                   182 B          87.5 kB ▲  + First Load JS shared by all              87.3 kB ▲  ├ chunks/main-90e477eaa3af9d76.js        85.2 kB ▲  ├ chunks/pages/_app-6b94368279a02b5e.js  196 B ▲  └ chunks/webpack-ef5ee84685c4d9a6.js     1.88 kB ▲  λ  (Server)  server-side renders at runtime (uses getInitialProps or getServerSideProps) ▲  ○  (Static)  automatically rendered as static HTML (uses no initial props) ▲  ●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps) ▲  Traced Next.js server files in: 5.413s ▲  Created all serverless functions in: 7.216s ▲  Collected static files (public/, static/, .next/static): 6.719ms ▲  Build Completed in .vercel/output [1m] ⚡ Completednpx vercel build. ⚡ No functions detected.
I think all of my routes use firebase which I think only works on node, so i don't have any routes that can use edge at the moment, but there are sever server components. The SSG are made with generateStaticParams. The route (app) section has everything I expect but Route (pages) is just 404 which all that loads when deploying with next-on-pages.

@james-elicx Thanks for your reply. Yes, it only works in next dev and not with next-on-pages (locally or deployed.)

Build output looks like this:
⚡ @cloudflare/next-on-pages CLI v.0.9.0
⚡ Detected Package Manager: npm
⚡ Preparing project...
⚡ Project is ready
⚡ Building project...
▲  Vercel CLI 28.20.0
▲  WARNING: You should not upload the `.next` directory.
▲  Installing dependencies...
▲  up to date in 2s
▲
▲  281 packages are looking for funding
▲  run `npm fund` for details
▲  Detected Next.js version: 13.3.1
▲  Detected `package-lock.json` generated by npm 7+...
▲  Running "npm run build"
▲  ><EMAIL_ADDRESS>build
▲  > NEXT_PUBLIC_CF_PAGES_COMMIT_SHA=$CF_PAGES_COMMIT_SHA NEXT_PUBLIC_CF_PAGES_BRANCH=$CF_PAGES_COMMIT_SHA next build
▲  info  - Loaded env from /Users/justinhook/Code/askmi/.env.local
▲  info  - Loaded env from /Users/justinhook/Code/askmi/.env.production
▲  info  - Loaded env from /Users/justinhook/Code/askmi/.env
▲  warn  - You have enabled experimental feature (appDir) in next.config.mjs.
▲  warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
▲  info  - Thank you for testing `appDir` please leave your feedback at https://nextjs.link/app-feedback
▲  info  - Creating an optimized production build...
▲  info  - Compiled successfully
▲  info  - Linting and checking validity of types...
▲  info  - Collecting page data...
▲  info  - Generating static pages (0/22)
▲  warn  - Entire page /about deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /about
▲  warn  - Entire page /settings deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /settings
▲  warn  - Entire page /404 deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /404
▲  info  - Generating static pages (5/22)
▲  warn  - Entire page / deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /
▲  warn  - Entire page /surveys/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /surveys/[shortname]
▲  warn  - Entire page /notifications deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /notifications
▲  warn  - Entire page /admin deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /admin
▲  warn  - Entire page /surveys deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /surveys
▲  warn  - Entire page /profile deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /profile
▲  info  - Generating static pages (10/22)
▲  warn  - Entire page /questions deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions
▲  warn  - Entire page /surveys/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /surveys/[shortname]
▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname]
▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname]
▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname]
▲  info  - Generating static pages (16/22)
▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname]
▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname]
▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname]
▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname]
▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname]
▲  warn  - Entire page /questions/[shortname] deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /questions/[shortname]
▲  info  - Generating static pages (22/22)
▲  info  - Finalizing page optimization...
▲
▲  Route (app)                                Size     First Load JS
▲  ┌ ○ /                                      7.36 kB         656 kB
▲  ├ ○ /_not-found                            0 B                0 B
▲  ├ ○ /about                                 6.13 kB         314 kB
▲  ├ ○ /admin                                 187 kB          577 kB
▲  ├ ○ /notifications                         0 B                0 B
▲  ├ ○ /profile                               434 B           659 kB
▲  ├ λ /profile/[shortname]                   504 B           659 kB
▲  ├ ○ /questions                             1.18 kB         642 kB
▲  ├ ● /questions/[shortname]                 870 B           600 kB
▲  ├   ├ /questions/favorite-color
▲  ├ ○ /settings                              0 B                0 B
▲  + First Load JS shared by all              97.3 kB
▲  ├ chunks/2443530c-eb76b5fe38a88953.js    50.6 kB
▲  ├ chunks/5122-49299bab9dd798df.js        21.2 kB
▲  ├ chunks/8139-3789e2bb3281d5d5.js        23.4 kB
▲  ├ chunks/main-app-498434a275a1a6ba.js    226 B
▲  └ chunks/webpack-ef5ee84685c4d9a6.js     1.88 kB
▲
▲  Route (pages)                              Size     First Load JS
▲  ─ ○ /404                                   182 B          87.5 kB
▲  + First Load JS shared by all              87.3 kB
▲  ├ chunks/main-90e477eaa3af9d76.js        85.2 kB
▲  ├ chunks/pages/_app-6b94368279a02b5e.js  196 B
▲  └ chunks/webpack-ef5ee84685c4d9a6.js     1.88 kB
▲  λ  (Server)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
▲  ○  (Static)  automatically rendered as static HTML (uses no initial props)
▲  ●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps)
▲  Traced Next.js server files in: 5.413s
▲  Created all serverless functions in: 7.216s
▲  Collected static files (public/, static/, .next/static): 6.719ms
▲  Build Completed in .vercel/output [1m]
⚡ Completed `npx vercel build`.
⚡ No functions detected.

I think all of my routes use firebase which I think only works on node, so i don't have any routes that can use edge at the moment, but there are sever server components. The SSG are made with generateStaticParams. The route (app) section has everything I expect but Route (pages) is just 404 which all that loads when deploying with next-on-pages. Does this mean it's issue #129? Would adding an edge route fix it?

Looks like everything is getting generated to static HTML as I suspected, minus /profile/[shortname] which is most likely generating a nodejs lambda function instead. Routing to static HTML pages will be resolved by #129. For your SSR pages (/profile/[shortname]), those need to use the edge runtime, i.e. export const runtime = 'edge';, and then they should work.

Unfortunately that route uses Firebase as well.
I tried adding an edge route and the build added my route (of type Streaming), but still got the following error:
 ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡
⚡      The following functions were not configured to run with the Edge Runtime:
⚡       - about.func
⚡ - about.rsc.func
⚡ - admin.rsc.func
⚡ - admin.func
⚡ - index.rsc.func
⚡ - notifications.func
⚡ - notifications.rsc.func
⚡ - index.func
⚡ - profile.rsc.func
⚡ - questions.func
⚡ - questions.rsc.func
⚡ - profile.func
⚡ - settings.func
⚡ - settings.rsc.func
⚡ - surveys.func
⚡ - surveys.rsc.func
⚡ - [shortname].func
⚡ - [shortname].rsc.func
⚡ - favorite-color.func
⚡ - favorite-color.rsc.func
⚡
⚡      If this is a Next.js project:
⚡
⚡      - you can read more about configuring Edge API Routes here: https://nextjs.org/docs/api-routes/edge-api-route
⚡
⚡      - you can try enabling the Edge Runtime for a specific page by exporting the following from your page:
⚡
⚡              export const config = { runtime: 'edge' };
⚡
⚡      - or you can try enabling the Edge Runtime for all pages in your project by adding the following to your 'next.config.js' file:
⚡
⚡              const nextConfig = { experimental: { runtime: 'edge'} };
⚡
⚡      You can read more about the Edge Runtime here: https://nextjs.org/docs/advanced-features/react-18/switchable-runtime

Does this mean any build with a static route will fail? Is there a timeline on #129? Barring that, is my only option to abandon app directory?

Unfortunately that route uses Firebase as well.

I tried adding an edge route and the build added my route (of type Streaming), but still got the following error:
 ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡
⚡      The following functions were not configured to run with the Edge Runtime:
⚡       - about.func
⚡ - about.rsc.func
⚡ - admin.rsc.func
⚡ - admin.func
⚡ - index.rsc.func
⚡ - notifications.func
⚡ - notifications.rsc.func
⚡ - index.func
⚡ - profile.rsc.func
⚡ - questions.func
⚡ - questions.rsc.func
⚡ - profile.func
⚡ - settings.func
⚡ - settings.rsc.func
⚡ - surveys.func
⚡ - surveys.rsc.func
⚡ - [shortname].func
⚡ - [shortname].rsc.func
⚡ - favorite-color.func
⚡ - favorite-color.rsc.func
⚡
⚡      If this is a Next.js project:
⚡
⚡      - you can read more about configuring Edge API Routes here: https://nextjs.org/docs/api-routes/edge-api-route
⚡
⚡      - you can try enabling the Edge Runtime for a specific page by exporting the following from your page:
⚡
⚡              export const config = { runtime: 'edge' };
⚡
⚡      - or you can try enabling the Edge Runtime for all pages in your project by adding the following to your 'next.config.js' file:
⚡
⚡              const nextConfig = { experimental: { runtime: 'edge'} };
⚡
⚡      You can read more about the Edge Runtime here: https://nextjs.org/docs/advanced-features/react-18/switchable-runtime

Does this mean any build with a static route will fail? Is there a timeline on #129? Barring that, is my only option to abandon app directory?

We've identified a solution to how Vercel generates static routes for the app directory which will receive a PR soon. Note that that solution will be intended to work with the new routing system and will most likely still face 404s in the current routing system.
Opting your app into the edge runtime will be the only way to get it to run at the moment. If your app with server functionality is unable to run on the edge runtime, it probably won't work on Cloudflare pages anyway, as we cannot deploy nodejs functions.
There is no fixed ETA for #129, but it should be coming soon.

Is this a new issue? I was able to deploy my app last week with this command, and now when I try, deployment fails, complaining about a lambda called hello.func that doesn't exist in my project.

This is should be now fixed.

thanks a lot @mountainash 🙂
Yeah I did test the application with the latest @cloudflare/next-on-pages prerelease and all seems relatively ok 🙂
see: https://f8e90dd0.next-on-pages-test-5h3.pages.dev/
not everything works perfectly, like routing seems to work in MPA mode, also for example the /techblog route returns an internal server error page.
I haven't properly checked the code so I am not sure what and how things should work.
I am closing this issue since the original "Failed to publish your function` error does seem to have been solved, but things are likely not perfect.
@tengweiherr could you please have a look and open separate issues for things you see not working as intended? 🙏 (that would be great but you don't have to, if you don't want or can't, I'll try to make some time to look into things properly later on)


Unexpected string literal ./environment/validate import call expects exactly one argument

Description
Unable to run an application, getting Unexpected string literal ./environment/validate import call expects exactly one argument.

Environment

npm ls react-native-scripts: 1.13.1
npm ls react-native: 0.55.2
npm ls expo: 26.0.0
node -v: 9.4.0
npm -v: 5.6.0

Operating system: macOS High Sierra
Phone/emulator/simulator & version: Version 10.0 (SimulatorApp-851.2 CoreSimulator-518.19)

Any updates?

I have figured that it only works with

react-native-scripts: 1.13.2
react: 16.3.1
react-native: 0.54.2

On a clean slate project I got the error saying that React Native version does not match with the one in scripts, but in this project I get this misleading error.

I have figured the real reason. It's because of the presence of .babelrc file with the following content:
{
  "presets": ["react-app"]
}

I am using one repo for both CRA and CRNA apps because they share code. It used to work but I can't figure out with which update it broke.


Handle TileOp with dynamic dimension

There are two changes:

In shape inference, remove unnecessary checks and allow dynamic dimensions.

In lowering to Krnl, avoid AffineMap if  the result is not affine. Previous code used semi-affine map. If the result of Affine.apply is not Affine, the result is used for ordinary load/store, not affine one. Such code works for check-onnx-lit. But for check-onnx-backend, it failed.

This PR is tested with the new functionality offered by PR354.
OM_FORCE_FIRST_DIM_UNKNOWN=1 make BACKEND_TEST=test_tile_cpu check-onnx-backend
This patch provides a base for us to try IndexExpr on TileOp for static and dynamic shape.

If you intend to move it to index expr, here are a couple of examples on how things are done quickly.
Once you have defined a shape helper, alloc a new array:
    // Insert an allocation and deallocation for the output of this operation.
    MemRefType outputMemRefType = convertToMemRefType(*op->result_type_begin());
    Type elementType = outputMemRefType.getElementType();
    Value alloc = insertAllocAndDeallocSimple(
        rewriter, op, outputMemRefType, loc, shapeHelper.outputDims);

create a loop using the same dimensions as in a vector of index expressions:
    outputLoops.createDefineOp();
    outputLoops.pushAllBounds(shapeHelper.outputDims);
    outputLoops.createIterateOp();

E.g. test if a dim is >1, in which case we use the index, or else we use the index zero:
        IndexExpr dim = outerContext.createSymbolIndexFromParentContext(
            shapeHelper.cDims[x]);
        cAccessFct.emplace_back(IndexExpr::select(dim > 1, resAccessFct[x], 0));

load and store values using vectors of expressions, automatically generating affine or std load depending on the index expressions being all fine:
    SmallVector<IndexExpr, 4> aAccessFct, bAccessFct;
    if (gemmOp.transA() != 0)
      aAccessFct = {k, n};
    else
      aAccessFct = {n, k};
    if (gemmOp.transB() != 0)
      bAccessFct = {m, k};
    else
      bAccessFct = {k, m};
    // Add mat mul operation.
    Value loadedA = outerContext.createLoadOp(operandAdaptor.A(), aAccessFct);
    Value loadedB = outerContext.createLoadOp(operandAdaptor.B(), bAccessFct);
    Value loadedY = outerContext.createLoadOp(alloc, resAccessFct);

@AlexandreEichenberger I will try IndexExpr for the TileOp later. Thanks for the note of new way of allocation.
I agree on reducing the use of auto: not friends for human reader.


Social cards do not support svg

While building docs with hatch run docs:build I get many warnings of the type:
WARNING: [Social card] image cannot be an SVG image, skipping...
Like scanpy, I use a svg logo. I don't see the social card being used anywhere in the RTD, so can one somehow skip the generation of it? I am unsure why card generation is attempted in the first place, given that it's not imported explicilty in docs/conf.py. I don't see it being used in sphinx_book_theme either.

I don't see the social card being used anywhere in the RTD

That’s not where it shows up. It shows up when someone links to your docs from social media (i.e. it becomes an embed picture on e.g. Discord, Reddit, or Slack).

I am unsure why card generation is attempted in the first place

It comes from sphinxext-opengraph: https://github.com/scverse/cookiecutter-scverse/blob/5d44c58df427f884585ae9772cae81f1b6638f80/{{cookiecutter.project_name}}/docs/conf.py#L61C6-L61C25
If you search in its docs, you’ll find a a broken link under the description for ogp_social_cards. That link is supposed to go to this subpage: https://sphinxext-opengraph.readthedocs.io/en/latest/socialcards.html

Thanks for the pointers, very helpful! With it I understood how to redirect the image to be a png as instructed. Cheers!

Glad I could help!


Contingency metrics from doppyo

Description
Added doppyo contingency-based metrics into a new module contingency.py.
Closes #113
Type of change

[x]  New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Writing of tests is still underway.
Checklist (while developing)

[x]  I have added docstrings to all new functions.
[x]  I have commented my code, particularly in hard-to-understand areas
[ ]  Tests added for pytest, if necessary.
[ ]  Edited CHANGELOG.rst

Pre-Merge Checklist (final steps)

[ ]  I have rebased onto master or develop (wherever I am merging) and dealt with any conflicts.
[ ]  I have squashed commits to a reasonable amount, and force-pushed the squashed commits.

References
Definitions of all metrics can be found here: https://www.cawcr.gov.au/projects/verification/#Methods_for_dichotomous_forecasts

The classes implementation and also API of Contingency.score looks quite nice. I tried it locally and this assign_coords error. see https://github.com/raybellwaves/xskillscore/pull/120 on your PR, where I also added a quick test with sklearn.metrics.confusion_matrix

you may take a testing template with sklearn.metrics.confusion_matrix from here: https://github.com/raybellwaves/xskillscore/pull/120

Also make sure to add to ci/requirements and to setup.py the xhistogram requirement.

I was a bit overexcited to try PR @dougiesquire probably we should get you finished and then review. but incase you have questions feel free to ask

Thanks @aaronspring, @bradyrx. I probably won't get back to this for a few days.

My main question is whether it makes sense to have this inconsistency in class vs. function calls in xskillscore? All other functions are called via xs.func(a, b, dim).

I'm happy to take your advice here. I do think that adding the Contingency class makes for a cleaner implementation, and it's not uncommon to have both class and function calls within a single package. To generate the contingency table itself, a user would still follow a very similar syntax:xs.Contingency(a, b, a_edges, b_edges, dim). They may wish to stop there and look at the values in the table, or they may wish to go further and compute one of the available metrics.
Regarding the histogram function in contingency.py, this is something I'll also want to use when I get to implementing the probabilistic metrics from doppyo. Is there scope for something like a utils.py module in xskillscore for housing generic code that is shared across modules? Or perhaps there is a better approach?

Thanks @dougiesquire all for your work here.

I do think that adding the Contingency class makes for a cleaner implementation, and it's not uncommon to have both class and function calls within a single package.

I'm +1 here. There are a some refactor issues (https://github.com/raybellwaves/xskillscore/issues/86) and @aaronspring noted here we should have a better way to add new metrics without copy and pasting lots of code. In the future we could refactor the old metrics with the class approach. I also think users would appreciate having this in despite an inconsistent package. https://github.com/raybellwaves/xskillscore/issues/36 will also helps users use the various modules and we can refactor later.
Makes sense to add xhistogram to the dependencies.

Is there scope for something like a utils.py module in xskillscore for housing generic code that is shared across modules?

I'm +1. I tend to look to see what's in xarray and dask and try to follow those (https://github.com/pydata/xarray/blob/master/xarray/core/utils.py
https://github.com/dask/dask/blob/master/dask/array/utils.py)

My main question is whether it makes sense to have this inconsistency in class vs. function calls in xskillscore? All other functions are called via xs.func(a, b, dim).

I'm happy to take your advice here. I do think that adding the Contingency class makes for a cleaner implementation, and it's not uncommon to have both class and function calls within a single package. To generate the contingency table itself, a user would still follow a very similar syntax:xs.Contingency(a, b, a_edges, b_edges, dim). They may wish to stop there and look at the values in the table, or they may wish to go further and compute one of the available metrics.

I like this approach.
Just how would the syntax for be?
Contingency.heidke_score(f,o,e,e,dim, yes_category=2)
# or
Contingency(f,o,e,e,dim).heidke_score(yes_category=2)

Regarding the histogram function in contingency.py, this is something I'll also want to use when I get to implementing the probabilistic metrics from doppyo. Is there scope for something like a utils.py module in xskillscore for housing generic code that is shared across modules? Or perhaps there is a better approach?

there is no utils.py yet but the other modules contain code that would also go there. please start utils.py

Just how would the syntax for be?
Contingency.heidke_score(f,o,e,e,dim, yes_category=2)
# or
Contingency(f,o,e,e,dim).heidke_score(yes_category=2)

I think I prefer the second approach because it separates the building of the contingency table (which happens when a Contingency class is instantiated, and can be accessed with the .table attribute or by printing the Contingency object) from the calculation of the contingency metrics. A user may which to calculate multiple metrics from the same table and this is intuitive and more efficient with the second approach
contingency = xs.Contingency(f,o,e,e,dim)

contingency_table = contingency.table()
Heidke_score = contingency.heidke_score()
Gerrity_score = contingency.gerrity_score()
Peirce_score = contingency.peirce_score()

It would be nice if
print(contingency.table)

produced human readable displays of the table. Currently this just prints the array objects, but it would be easy to make the display more interpretable.

Regarding my above comment, porting the xarray object to a pandas Dataframe makes human readable printing straight-forward, e.g.

but I'm not sure of the best approach for robustly dealing with multiple variables and dimensions. I think I'll leave this task for a later PR.

I think this is ready for review. The tests I added/adapted check the values in the contingency table against sklearn.metrics.confusion_matrix (1D only) and check the values of the available metrics against hand-computed values for a simple 2x2 contingency table. Unfortunately, I couldn't find a standard package containing all our metrics to reference against.

@dougiesquire, this is really awesome. I'm glad we are all collaborating and consolidating ideas over here. Just suggested a few fixes that should be pretty straight forward. I'm good to go on this once those are implemented. FYI, it looks like the CI is breaking due to some flake8 issues. Might have just forgot to activate pre-commit.
[flake8]
xskillscore/core/utils.py:18:1: W293 blank line contains whitespace
xskillscore/core/utils.py:41:49: W292 no newline at end of file
The command "./ci/run-linter.sh" exited with 1.

I just fixed the whitespace issue through the github editor here. Should be good to go after that!

Thanks @dougiesquire , this is awesome!


Added text editor software "SubEthaEdit"

Project URL
subethaedit.net
Category
Text editor
Description
added subethaedit
Why it should be included to Awesome macOS open source applications  (optional)
Checklist

[x] Only one project/change is in this pull request
[x] Addition in alphabetical order
[x] Appropriate language icon(s) added if applicable
[x] Screenshots(s) added if any
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

Hi @Brice187! Thanks for your contribution! We have new Contribution Guidelines. Please read it and resubmit or edit your PR. Thank you!


Tighten typing restriction of nbformat.ICell

By narrowing nbformat.ICell to not include the base class, type guards can effectively differentiate between the different cell types based on the cell.cell_type field.
The narrowed definition should be sufficient for all uses, as all cells should conform to one of the three cell types.

Looks good, thanks!


Fix dubbo-maven-plugin failed to run on windows

What is the purpose of the change
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 37.53%. Comparing base (392baa3) to head (58b3ba1).
Report is 40 commits behind head on 3.3.

Additional details and impacted files
@@            Coverage Diff             @@
##              3.3   #14616      +/-   ##
==========================================
- Coverage   38.05%   37.53%   -0.53%
==========================================
  Files        1804     1813       +9
  Lines       80043    80489     +446
  Branches    11898    11958      +60
==========================================
- Hits        30461    30208     -253
- Misses      45190    45888     +698
- Partials     4392     4393       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add active_support/all to all postgres HA classes

Before this change, we were not able to use activesupport methods such as Hash#symbolize_keys or Time#current in production because the required active_support files were not required in the source.
The bigger problem was that we were passing the spec tests because of the way rspec is requiring the spec files it will run.
So, to be safe, we can require active_support/all to ensure that we will have access to the methods that could be added and we can be confident that we are not getting false positives in our tests.
Replacement for #10530
@yrudman @gtanzillo @Fryguy please review
@miq-bot add_label bug, core
@miq-bot assign @gtanzillo

@miq-bot add_label darga/no


Pass alert_time to alerters via pipeline

This allows the alerters to use alert_time to display it or to calculate the timerange which the current alert covers.
It doesn't seem very 'clean' to pass alert metadata via a parameter named pipeline.
In fact, I was about to add a metadata object to the alerters when I saw that pipeline  did exactly what I wanted.
From my point of view, the pipeline object's purpose is to pass alert metadata from one alerter to the next, and we might as well use it if we want to pass more info from ElastAlerter.
With that in mind, what would you think of renaming that parameter to metadata ?

I'm open to renaming. I think metadata makes sense. I created it just for passing JIRA issue IDs to other alerters, and I would love to see it used for more stuff.

A colleague of mine wrote a templated email alerter using jinja and I wanted to put the alert time in the subject.  pipeline seemed like the way to feed that info into the alerters.
I'll see if I can rename pipeline to metadata (and keep pipeline for backward compat)


Remove or explain the side panel

When already in the middle of creating a phenopacket it is confusing to have "add phenopacket" as a visible option. I recommend removing this panel and instead prompting the user at the end of phenopacket creation if they'd like to add another. Am I missing something here @pnrobinson ?
I like the progress bar at the top to orient users within the workflow so I don't think we need the left sidebar for that. The exception would be if we build out MORE steps that no longer fit on a horizontal screen. Not sure how this renders on mobile?

@iimpulse is working on adding the ability to make the menu hidden if needed. See #135

Side panel is gone


add Kaohsiung Medical University

Institution/School Name
Kaohsiung Medical University
Instiution/School Website
https://www.kmu.edu.tw/index.php
Email Users
<EMAIL_ADDRESS>Please place an x between the square brackets if yes

[ ] Students
[ ]  Academic/Teaching Staff
[x]  Other/Support Staff
[ ]  Alumni

Education Levels
Please place an x between the square brackets if yes

[x]  Post-graduate research
[x]  Graduate School
[x]  College (University) or Undergraduate School or equivalent
[ ]  Community College or equivalent
[ ]  High School or equivalent
[ ]  Elementary School or equivalent

@sunlin1988 Pull request merged. Thank you!


md-menu with max-width

What is affected?
Component
Description
When using CSS max-width: 50% on a md-menu, the inner div.items inherits the max-width and applies it itself, which leads to wrong display.

Reproduction
https://lit.dev/playground/#gist=fa17bf6ea9bcfbef12c4fbc67f997ffe
Workaround
No workaround
Is this a regression?
Yes, worked with mwc-menu 0.27.0
Affected versions
1.0.1
Browser/OS/Node environment
Browser: Chrome 119.0.6045.123 (arm64)
Mac: Sonoma 14.1.1

https://lit.dev/playground/#gist=55d7c22148457419991a07b703dabb87 I added the mwc version to see the differences

What do you expect the max width to be for a menu styled with max-width: 50%? The menu is a popup and does not have a relative parent to base its width off of, so 50% of what relative width?

I think the problem lies in md-menu-item instead of  max-width: inherit it should be like the old list item https://github.com/material-components/material-web/blob/mwc/components/list/lib/_list-item.scss#L50 width:100%
https://github.com/material-components/material-web/blob/main/menu/internal/menuitem/_menu-item.scss#L98-L107

This works as expected for me.  As @asyncLiz says, there's no parent to define a % width from.  If you set a max-width on the menu with units it displays correctly.

@jgreffe if you move the max-width: 50%; to the .wrapper and remove it from the .menu you have the same behavior as in mwc trying to say you have to style the outer component and not md-menu as you would have done with mwc-menu

This works for a top-level menu, however, I cannot get it to work on submenus. I assume that if the menu has max-width: 50% from inheriting it from the .wrapper class, then that should propagate to the submenu max-width: inherit. However, that does not happen. Adding the .wrapper class to the submenu doesn't work either. Adding a separate wrapper to the submenu breaks the structure. How should I approach this?


Many native lsp features are not their

Many of the native lsp features are not their in rust-tools eg:
    vim.lsp.buf.declaration()
    vim.lsp.buf.definition()
    vim.lsp.buf.signature_help()
    vim.lsp.buf.type_definition()
    vim.lsp.buf.references()
    vim.diagnostic.goto_prev()
    vim.diagnostic.goto_next()
    vim.diagnostic.setloclist()
    vim.lsp.buf.implementation()

and if their are these features the please tell me how can i use them because the insctructions are not clear
Thanks for reading

This seems like a bug better filed with the nvim-lsp team.

I will try to fix it on my own by removing rust-tools and trying to do only with rust lsp
I will keep updating

I got it working
Let me know if anyone wants the config

Just remove rust tools and use native lsp instead to get more features


lowercase ids

It seems like dependencies are only working with lowercase ids, independent what is stated on the feed.
On the feed, the name of the package is for example "DotNet4.5", but if I am trying this:
<dependencies>
        <dependency id="DotNet4.5" version="4.5.20120822" />
</dependencies>

it is not working. But if I am changing it to this:
<dependencies>
        <dependency id="dotnet4.5" version="4.5.20120822" />
</dependencies>

it works fine.

Calling this closed as a duplicate, plus I think it is fixed in choco.exe.


Declare fields of sections as public

Sections are currently defined like this:
#[derive(Default)]
pub struct TypeSection(Vec<Type>);

To create a new section from scratch one needs use Default::default() and then insert the contents using the accessors. It would be a lot easier if the field of the section was declared public.
(I am currently writing a compiler with WebAssembly as the target.)

oh i think we can add From<T: IntoIterator<Type>> implementation for this

This does work but since I construct a Vec myself it involves copying the
contents.
Is it planned that the sections enforce some variants and not only the
types?
Am 03.06.2017 4:49 nachm. schrieb "Nikolay Volf"<EMAIL_ADDRESS>
oh i think we can add From<T: IntoIterator> implementation for this
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NikVolf/parity-wasm/issues/28#issuecomment-305979620,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACpvWQf55HoI_b_g636rUUWX9JoK86E8ks5sAXKJgaJpZM4NvF7N
.

yep, on the second thought, i just added with_* helper methods for now
see #29

Perfect. Thanks.


Update 144-black-hole-visualization.md

It's useful to link the demo for the people who do the merges ;) looks good though
https://github.com/JosGielen/Coding_Train_VB.net/blob/master/CC144 Black Hole Visualization/Example/RedShadow.jpg

Thank you for this contribution.


Reproducible compilation of Foundry projects

We seem to be using the older v0.8.13  version of solc, which should be updated to 0.8.21 — the latest available version at the moment.
Reproducible compilation
The problem
Different versions of solidity compiler (solc) may generate different EVM bytecode and the proof artefacts such as loop invariants may reference to the bytecode. To make reproducible compilation and proofs,  Kontrol pinpoints to a specific version of solc (0.8.13 as of now). The pinpointed version of solc is installed and linked while installing Kontrol through command kup install kontrol.
By default,  forge build command would search the latest version of solidity compiler which is compatible with the solidity source code solidity version pragmas (e.g., pragma solidity ^0.8.13;). In order to use the pinpointed solc, Kontrol pass the option —no-auto-detect to the forge build command (only happens in the nix installation) and foundry does not detect and use a compatible solc version. Instead, it uses the solc resolved through the path environment variable (in nix installation, it resolves to the pinpointed version).
However, it is highly likely that the pinpointed solc is not compatible with solc version required in customers’ solidity source code. Thus the forge build command would fail. This prevents customer to use the latest version of Kontrol.
The proposed solution
We shall allow customer to set a solc version for their repo. This can be done by adding the option solc_version="x.y.z" to foundry.toml. In order to make existing internal tests pass, we can modify the repository by setting the configuration option or make the version as an environment variable to the CI script and the CI script would install and link the specified version of solc. This solution requires that the foundry project can be compiled with only one single version of solc. We shall also have a support matrix tested to allow users to choose the latest version of solc supported by kontrol.
Some limitations

A project may require multiple versions of solc to compile, i.e., some solidity source files require a version and the other source files require another version. Without the --no-auto-detect option, forge build would compile the files with different versions and it is even possible that a single file is compiled with multiple versions of solc and thus has multiple output files.  However, forge build does not allow setting solc version for each solidity file in the same project. The possible solution is to allow users to set multiple versions of solc, and we have to install the specified versions of solc in a similar way foundry manages multiple versions of solc and specify the --offline option to forge build.  The installation of multiple solc versions through forge can be achieved by running multiple commands forge build   --use x.y.z --skip ".sol". This command will install the solc version x.y.z without building the project.

Installation of Solidity libraries. A foundry project can refer to a remote solidity library such as @openzeppelin and forge-std. However, all the external libraries are managed through forge install/update/remove and the libraries are git repositories and thus have fixed commit hashes. Thus the library build process is deterministic as long as the solc versions are fixed.

Related: https://github.com/runtimeverification/evm-semantics/issues/1980, suggests updating the version used in our tests suite to 0.8.19.

Related to this Pull Request @palinatolmach @spencerhaoxiao Has the issue of running a proof using the nix installation now been resolved such that the pragma header versions are respected and not using a pinned version of solc?

PR 105 resolves the reproducible compilation problem partially. By default without providing the specific solc_version to the flake.nix script (cd kontrol && nix build .), kontrol relies on the foundry installed by the user (not the one installed with nix). In this case, as long as the user can build their project with forge build, kontrol shall build. However, the flag --no-auto-detect is not passed to forge build and thus does not achieve reproducible compilation objective.
When kontrol is installed with a version of solc supported by kontrol (e.g., cd kontrol && nix build .#kontrol.solc_0_8_13), kontrol uses the foundry and solc installed with nix and passes the flag --no-auto-detect to forge build.

Closing issue


Error in the path when restoring the light node wallet

Celestia Node version
v0.13.4
OS
ubuntu 22.04
Install tools
No response
Others
No response
Steps to reproduce it
cd ~/celestia-node
./cel-key add my_celes_key --keyring-backend test --node.type light --recover

Expected result
The key should be restored in ~/.celestia-light-mocha-4/, but the keys are being written to a different directory, ~/.celestia-light, so the node does not detect them. Adding the home flag with the exact path specified also does not solve the problem
Actual result
cellight@reliable3:~/.celestia-light$ tree
.
└── keys
    └── keyring-test
        ├── 034d5601c0f06bb3ccecc5fab63ac2f60519196a.address
        └── my_celes_key.info
        ~~~

### Relevant log output

_No response_

### Notes

_No response_

@itrocket-team Can you please try again and add the --p2p.network mocha flag please and see if this resolves the issue?

Oh, yes. Using the --p2p.network mocha flag, everything works fine. Its my mistake, sorry


Extension XHR failed

Issue Type: Bug
i do intent install vert extension and VScode show this messae "Error while loadinf extensions, XHR failed"
VS Code version: Code 1.48.0 (db40434f562994116e5b21c24015a2e40b2504e6, 2020-08-13T07:50:42.600Z)
OS version: Windows_NT x64 10.0.18362

/duplicate - search for XHR to find some. #102714 includes a comment from someone solving it by changing DNS settings.


wk5 add local storage state widget

one major pain point was that the canvas was entirely reset each time they changed the code or the color pallet. Consider using the localstorage api to persist a save state so that they can live reload.

turns out storage won't work unless we find a way to capture the drawings as key/value pairs

Storage only supports storing and retrieving strings. If you want to save other data types, you have to convert them to strings. For plain objects and arrays, you can use JSON.stringify().

https://developer.mozilla.org/en-US/docs/Web/API/Storage/setItem

I believe there's a super janky way of serializing and deserializing an image into json format but it's 100% better practice to store the image into its own directory.
Though last I checked, most of the file loading functions I'm aware of require the use of node.js or other javascript backend runtimes to implement.
Speaking of which, we had one student completely erase everything they had, then saved, then also conveniently cleared the undo stack. I'm not really sure what to do about that other than just explicitly tell her what probably happened and how she lost all her progress when trying to save.

So, we have a solution in how I implemented the help menu in animationStudio.js, though I dunno how great it is...
The p5 function loadPixels() encodes the canvas' pixel colors into an array called pixels, which gets slapped back onto the canvas when you call updatePixels(). So, we can just JSON.stringify the array. Though, for even the default 400x400 canvas it's pretty chonky -- 400*400*4*2 Bytes = ~1.2MB. However, this is less than the 5MB cap for local storage


Update proof-of-stake.md

added links and fixed typos

this is the committee section

Just noting you saw that committees section doesn't exist.

did see that -- why was it removed?

ok asking alberto what happened
On Tue, May 24, 2022 at 11:46 AM Clay-Mysten @.***>
wrote:

did see that -- why was it removed?
Alberto replaced it with:
https://github.com/MystenLabs/sui/blob/main/doc/src/learn/architecture/validators.md#quorums
—
Reply to this email directly, view it on GitHub
https://github.com/MystenLabs/sui/pull/2168#issuecomment-1136097211, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AX5IFBUGQC2ISG4SAL4XEMLVLT2W3ANCNFSM5WXHR6IQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Send screen Update text of fee error

Please make the same text of error as here ""Сoins were automatically selected to maximize privacy and minimal transaction fee of 1,000,100 GROTH.""
https://zpl.io/aXxQl3j

checked


"dotnet publish" documentation does not tell you about how to use a saved XML profile

This is a feedback on the documentation of "dotnet publish" command found here
It was only after reading through https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/visual-studio-publish-profiles?view=aspnetcore-2.2 I got to know what you could pass the name of the XML file and have dotnet publish do the publishing without having to specify all the individual arguments.
Example:

dotnet publish  c:\Work\SomeProject.csproj /p:PublishProfile=FolderProfile.pubxml

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

ID: 211afdc7-c796-202d-239d-823f2a499dff
Version Independent ID: 9439897e-dcb3-bc2e-5cae-35c1ca2e0681
Content: dotnet publish command - .NET Core CLI
Content Source: docs/core/tools/dotnet-publish.md
Product: dotnet-core
Technology: dotnet-cli
GitHub Login: @mairaw
Microsoft Alias: mairaw

Thanks for your feedback @sdg002. We have to make updates to this article for 3.0 and we'll consider your feedback when updating the article.


Fix max_message_length

Cherry-pick #11545 onto v1.4.x

No significant performance differences

Known issues:
Basic Tests Windows: #11312
Msan C: #11529
Portability Tests Windows: #11312


The clamp in-place operation cannot modify the weight_scales tensor directly.

>>> import torch
>>> a = torch.tensor(1.5367e-08, dtype=torch.float16)
>>> a
tensor(0., dtype=torch.float16)
>>> a.to(float).clamp(min=1e-5)
tensor(1.0000e-05, dtype=torch.float64)
>>> a
tensor(0., dtype=torch.float16)
>>> a = a.to(float).clamp(min=1e-5)
>>> a
tensor(1.0000e-05, dtype=torch.float64)

As shown in the code.
This bug caused NaN values to appear in the checkpoint obtained through SmoothQuant.

Thanks @StarrickLiu , I'm integrating this fix to our internal repo.

The fix has been integrated to our internal repo. It will be available on next Github update.
Thanks again for the contribution!


mlir graph optimization is not built into tf-nightly

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): binary
TensorFlow version: tf-nightly
Python version: 3.6
Installed using virtualenv? pip? conda?: pip
Bazel version (if compiling from source): n/a
GCC/Compiler version (if compiling from source): n/a
CUDA/cuDNN version: n/a
GPU model and memory: n/a

Describe the problem
Commit 248bc00 (@ezhulenev ) enables MLIR graph optimizations. However, it looks like this is not built as part of the tf-nightly. As a result, even though the following two methods are available:
tf.config.experimental.enable_mlir_graph_optimization
tf.config.experimental.disable_mlir_graph_optimization

There is no effect by toggle on/off the above two commands with tf-nightly installed.
From the commit, if the commit is carried in tf-nightly, then with
import os
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '0'

import tensorflow as tf
...
...

we should see something like below (base on the code in commit 248bc00):
  if (!config_proto.experimental().enable_mlir_graph_optimization()) {
    VLOG(1) << "Skipping MLIR Graph Optimization Pass"
            << ", session flag not enabled";
    return Status::OK();
  }

But the logs does not show the above contents.
Is there any way (e.g., pass certain build options) so that the generated pip wheel could carry the MLIR graph optimizations?

@jpienaar @joker-eph can you please take a look and help triage?

@ezhulenev do you know why your optimization isn't available here? Can you look into this?

I don't know of any special handling of pass registration in the OSS TF.
Does this static registration invoked at start time: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/mlir/tensorflow/transforms/graph_optimization_pass_registration.cc#L25 ?
This registration forwarded to https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/mlir/mlir_graph_optimization_pass.h, and then registered with a runtime here: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/mlir/mlir_graph_optimization_pass_registration.cc#L24-L28
For now it is only registered for TF function, so if you run TF V1 graph with sessions, it will not be invoked.
For V1 you need to add MlirV1CompatOptimizationPassRegistration for this pass, but that's probably not going to work by default, because V1 graphs (graphs with sessions) contains control flow constructs that are not supported by MLIR importer.

Couple of different parts here (sessions vs graphs vs functions) that confuse things, so let's start simpler. MLIR importer does support V1 control flow constructs but majority of optimizations and focus is on V2 control flow.
But I didn't see V1 references until this point, is this a V1 model? Also I haven't tried the nightly build.
@ezhulenev is there an integration test of the feature that you added so that we could verify here with a bazel test command?

No, only mlir-unit-tests for layout optimization.
And a simple python example to test it, but the end state is not observable from python, so it can't be easily converted to end-to-end test.
from __future__ import absolute_import
from __future__ import division
from __future__ import print_function

import tensorflow as tf

from absl import app
from absl import flags

import numpy as np

FLAGS = flags.FLAGS

from google3.third_party.tensorflow.python.framework import config

def main(_):
  # Disable layout optimizer to not change input data_format.
  config.set_optimizer_experimental_options({'layout_optimizer': False})

  # Enable MLIR Graph Optimizations
  config.enable_mlir_graph_optimization()

  input_dims = [1, 9, 9, 4]
  filter_dims = [3, 3, 4, 8]
  input_t = np.random.rand(*input_dims).astype('f')
  filter_t = np.random.rand(*filter_dims).astype('f')

  @tf.function
  def fun(input, filter):
    input_tensor = np.random.rand(*input_dims) * 5
    x = tf.nn.convolution(
        input,
        filter,
        padding = "VALID",
        data_format='NHWC',
    )

    return x

  x = fun(input_t, filter_t)
  print(x)

if __name__ == '__main__':
  app.run(main)

For tf-nightly, the above example may need to make small modifications to change  from google3.third_party.tensorflow.python.framework import config.  Below is the modified one that runs on Colab:
!pip install tf-nightly

import tensorflow as tf
import numpy as np

# Disable layout optimizer to not change input data_format.
tf.config.optimizer.set_experimental_options({'layout_optimizer': False})

# Enable MLIR Graph Optimizations
tf.config.experimental.enable_mlir_graph_optimization()

input_dims = [1, 9, 9, 4]
filter_dims = [3, 3, 4, 8]
input_t = np.random.rand(*input_dims).astype('f')
filter_t = np.random.rand(*filter_dims).astype('f')

@tf.function
def fun(input, filter):
  input_tensor = np.random.rand(*input_dims) * 5
  x = tf.nn.convolution(
      input,
      filter,
      padding = "VALID",
      data_format='NHWC',
  )

  return x

x = fun(input_t, filter_t)
print(x)

I checked the bazel build file in tensorflow/BUILD, and think the issue is that
//tensorflow/compiler/mlir:mlir_graph_optimization_pass_registration

needs to be added to the target //tensorflow:tensorflow_framework, as otherwise the mlir optimization will not be included in libtensorflow_framework.so.2 that is packaged into tf-nightly.
However, if I directly add //tensorflow/compiler/mlir:mlir_graph_optimization_pass_registration to
//tensorflow:tensorflow_framework then a
Non-OK-status: RegisterAlreadyLocked(deferred_[i]) status: Already exists:

error will show up.
Think the issue is caused by inclusion of some components multiple times in bazel rules.

I have created a PR #39231 to add MLIR graph optimizations registration to be part of the libtensorflow_framework.so, so that it could be packaged to tf-nightly pip install.
It didn't make code change, though it made several changes in bazel to remove the dependency of multiple copies, and also splits import_model.[h|cc] into 3 parts (no true code change):

new import_base.[h|cc] consists of ImporterBase class and common shared functions (by import_model.[h|cc] and import_graphdef.[h|cc]
new import_graphdef.[h|cc] consists of graph only conversion to mlir
the import_model.[h|cc] has also been updated to consist model only conversion to mlir

The reason for the above change is that model imports depends on some library in core and it pulled in xla and core ops multiple times.
With the change, MLIR graph optimizations registration only need export_graphdef.cc and import_graphdef.cc, and the multiple copies of xla and core ops are avoided.
Please take a look at PR #39231  and let me know if there are any issues.


Bump to PublicApiApprover 9.0

Related to Azure Service Bus
I released today the new major version of PublicApiApprover. It uses now stable ordering that should be platform independent

The build server proofs that the linux version is now also stable

Can one of the admins verify this patch?

Isn't this pretty much a no brainer to review? :)

Bumped to 9.1 and rebased


cfep-17: Handling pin backports and dependency rebuilds

Thoughts @beckermr?

I find it confusing if the bot makes branches on feedstocks I maintain. Here's an alternative proposal,

A bot makes an issue asking to make a branch
Maintainer says yes by adding a label
A github action will create the branch
makes it less confusing

The creation of the branch is an implementation detail, mostly. It is the way by which we can have multiple versions accessible to PR at once. I would say that the maintainer consent is provided by merging the PR that breaks the current pin. Having to respond to an issue seems like a bit of a burden for something most maintainers won't need to worry about.

The creation of the branch is an implementation detail, mostly.

Right. The issue here is one of consent.
I am on the fence on this issue and am ok either way.

Whatever you decide here, please don't make it the default for feedstocks that I maintain.

Whatever you decide here, please don't make it the default for feedstocks that I maintain.

Is opt-out too much to ask, or would you prefer opt-in?

Is opt-out too much to ask

I'm on 210 teams, so yeah.

Additionally, is the choice a real one? If a maintainer turns down this option, where does that put us, back where we are now? I don't think that is tenable.

Additionally, is the choice a real one? If a maintainer turns down this option, where does that put us, back where we are now? I don't think that is tenable.

This goes back to the discussions we've been having on keybase. How much power do we exert to  get migrations to go through?

Let's say for example, you create a branch for clang 9, I won't be maintaining it because every time there's a rebuild, I have to build it on the ppc64le server and the aarch64 server. So I won't be merging any PRs unless you commit to doing the work yourself.

Clang 9 is a very hefty example that updating via the bot is honestly not possible.
A question @isuruf. Do you view people responding to an issue by adding a label as consent for the existence of the branch or as a commitment to maintain that branch too?
I think the difference here matters. We only need the branch to exist so that we can issue prs to it. We do not always need it to be maintained, though we may sometimes.

As a commitment. If there's no branch, people will not try to send patches to these older versions.

merging as deferred


RootDockingPanelAPI Internal Methods

Most of the methods in RootDockingPanelAPI are intended to be internal to the framework. Some thought will have to be given to how these can be made internal. Most likely by moving them to a private class in a package not exported from the module.
User facing:

getWindow
setEmptyPanel
isPiningSupported (renaming to isAutoHideSupported)
setPinningSupported (renaming to setAutoHideSupported)
getPinningLayer (renaming to getAutoHideLayer)
setPinningLayer (renaming to setPinningLayer)

Internal:

setWindow
getPanel
isEmpty
setPanel
removeExistingPanel
dock
undock
replaceChild
removeChild
setDockableShown
setDockableHidden
hiddenPersistentIDs
hideHiddenPanels
getWestAutoHideToolbarIDs
getEastAutoHideToolbarIDs
getSouthAutoHideToolbarIDs
isLocationSupported
updateLAF

One solution might be to wrap RootDockingPanel in an internal panel and move all the internal methods to that internal panel class.


Gradle dependencyCheckAnalyze Build failed

So after migrating the project to gradle 4.1.0 and android gradle plugin to 3.0.0, the ./gradlew app:mainModule:dependencyCheckAnalyze fails. Currently, my project runs smoothly after the migration but the dependencyCheck task doesn't work anymore. Worth mentioning that the task worked fine pre gradle 4.1.0 and android plugin gradle 3.0.0
My mainModule declares the dependency to the local library module likewise, so nothing fancy:
implementation project(':libraries_3rd_party:aLibrary')
The aLibrary's gradle has a release buildType and the only dependency is the android support v4. The mainModule has several build types: debug, release, buildType1 etc. All the buildTypes that are not release or debug have matchingFallbacks = ['debug', 'release']. The mainModule also has multiple flavours all assigned to only one dimension.

Task :app:mainModule:dependencyCheckAnalyze
Verifying dependencies for project mainModule

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:mainModule:dependencyCheckAnalyze'.

Could not resolve all dependencies for configuration ':app:mainModule:flavour1DebugCompileClasspath'.
More than one variant of project :libraries_3rd_party:aLibrary matches the consumer attributes:
- Configuration ':libraries_3rd_party:aLibrary:debugApiElements' variant android-aidl:
- Found artifactType 'android-aidl' but wasn't required.
- Required com.android.build.api.attributes.BuildTypeAttr 'debug' and found compatible value 'debug'.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Found com.android.build.gradle.internal.dependency.VariantAttr 'debug' but wasn't required.
- Required defaultDimension 'flavour' but no value provided.
- Required org.gradle.api.attributes.Usage 'java-api' and found compatible value 'java-api'.

Configuration ':libraries_3rd_party:aLibrary:debugApiElements' variant android-classes:
Configuration ':libraries_3rd_party:aLibrary:debugApiElements' variant android-manifest:
Configuration ':libraries_3rd_party:aLibrary:debugApiElements' variant android-renderscript:
Configuration ':libraries_3rd_party:aLibrary:debugApiElements' variant jar:

Thank you for the bug report - the team will try to look into this soon.

I got the same error, and was able to work around it by changing dependency references like this:
implementation project(':foo-module')
to this:
implementation project(path: ':foo-module', configuration: 'default')

have you fix this issue now? when i work around with @jebstuart's suggestion, moudle "foo-module" dependency is not transitive.

Unfortunately - not yet. The team will try to get to this soon.  PRs are welcome...

I don't know if this would help at all, but the error message looks similar to https://github.com/JFrogDev/build-info/issues/139 .

Unfortunately implementation project(path: ':foo-module', configuration: 'default') is no longer recommended for Android Gradle Plugin 3.0.0+.
https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html

As I understand there is no fix at the so far?

I believe this is also related to https://github.com/jeremylong/dependency-check-gradle/issues/71.  I will try to look at this soon - but as always PRs are welcome.  I have one fairly serious issue with the core engine that will require a number of updates before I can delve into this issue (for more info on the other issue see https://github.com/jeremylong/DependencyCheck/issues/1088).

Any solution for this?

According to this issue, there may be a problem with the Google services plugin:
https://issuetracker.google.com/issues/79235243
Downgrading the google services plugin to v3.2.1 will resolve the build error for now until Google releases a newer version of the plugin.


Always on top Option: ☐ ignore when maximized

Description of the new feature / enhancement
Option to ignore Always on top toggle behaviour if AOT toggled application is maximized.
If this option will be enabled, turned on AOT application will have this behavior:
if maximized, AOT will be disabled, other apps can be in the front, but if this application will be unmaximized again, AOT toggle will be restored (on if it was on before maximizing)
Scenario when this would be used?
I enabled AOT on the small Telegram window, so I can instantly see new messages even if I got away when they has delivered. So I can work in other application and read/write messages in the one screen without secrificing the screen space from the main application. Sometimes I want to focus on the telegram for read/write in more comfort window size. In this case there isn't sense to be AOT anymore – it's already occuping whole screen, it only interfiering switching between applications.
IMO, in most cases/scenarios AOT losing sense when application is maximized
Supporting information
No response

/dup https://github.com/microsoft/PowerToys/issues/25632


Hardcoded Values

In multiple places there are hardcoded values that make it not possible to run the server out of the box.
Examples:
__https://github.com/CanOpener/PongPlusPlus-Server/blob/master/main.go#L10__

This should be a generic directory that is on all systems and user has permissions to edit it (/tmp)

__https://github.com/CanOpener/PongPlusPlus-Server/blob/master/main.go#L12__

In this case it would be better to just specify :3000 so the server listens on all interfaces, and not just on localhost

Resolved in @654ff37f50c6356fa9681b8e81887e2b76510f92
Take a look and close the issue if you think it's ok.

Yup looks much better, but I am not sure why some flags are capitalized


closes #2017

Some docs, I think it can be merged if it passes, since it only adds some extra docs.

Thanks!  That looks good: https://www.pombase.org/status/gene-coordinate-changes-protein-coding

fab!


Patch - https://github.com/mhausenblas/burry.sh/pull/26

I did some improvement and extra information about ignored data.

Super, thanks @eye0fra!


Viewing Channel's Playlists stops at 35

I have a playlist I've been going through using another application, but it's having issues at the moment. So I went back to Old Faithful and tried to find the playlist with pipe-viewer. I searched for the channel (Hyper RPG - channel ID UCRDPlyuTAus79rPdFERMS5A if that's needed/helpful information) and used the :p=i command to view their playlists.
Unfortunately, it only shows 35 playlists (the one I'm watching not among those 35), and if I attempt to go to the "next page" of results by using :n, :next, or just hitting enter, I get an error stating [!] Invalid option: <n> or [!] Invalid option: <next>
Is there another way to find this playlist (without having to actually open YouTube in a browser and copying the URL or ID)?

Fix works great, thank you!


Notification title has html entity code at the end:

Fixed in original ticket  #4412


Add simple CLI API

:wave: This is great to see! What would be nice is if there was also a simple CLI API (using Click or something similar) for hadd that would take the form of something like
odapt hadd [OUTPUT_FILE] [INPUT_FILES]

I'm on it! Thanks for the feedback!

One extra benefit from a command line interface would be that we could use pipx to run the hadd command in an isolated environment. That's very convenient for people who still regularly work in Python environments with older awkward versions<2 (including me).


when I click the cpu input box, the default value had changed and I can't submit the form

Rancher versions:
rancher/server: stable
rancher/ui: 1.6-dev
host api: http://<IP_ADDRESS>:8000/v2-beta/projects/1a5/host
Steps to Reproduce:
1.click cpu input box
2.click create
Results:
Remind: Validation failed in API: milliCpu
post request value: milliCpu:""
expectation：
1.according to instance type, send the default values of memory and cpu to host api
2. show the default value in the input box
3.if the value is none ,remind the user the value of memory or cpu can't be none
#9575
@yasker @orangedeng

Rancher versions:
rancher/server: 1.6.9
Steps to Reproduce:

try to add a new host with machine driver from UI
click advanced options and input cpu limit field
clear the cpu limit field

Results:
User can not submit the form
Expectation：
User should be able to submit the form

Mark as duplicate of #9765


sound paused when back to home in ios

it works well in simulator, but installed in iphone 6, the sound will pause when the screen off or home button pressed, and it will recover as soon as you open the installed app.

Yes, that's by design. Check the Readme section https://github.com/zmxv/react-native-sound#setcategoryvalue-ios-only


feat: Show similar events based on event topic

Fixes #123

good work btw 👍

@iamareebjamal Please Review :+1:

@iamareebjamal Could you please review this as I want to work on #207 after this

PR Updated :+1:

@iamareebjamal Did all the changes requested :+1:

Removed EventTopicsDao for while :+1:

@dreadpool2 Squash your commits

@iamareebjamal Thanks! I will do that :+1:

@iamareebjamal Rebased my commits :+1:


docker-compose.yml fix

docker-compose.yml has wrong parameter for webpack-dev-server in the storefront container, which makes the frontend inaccessible on the host machine on linux.
"--hostname" should be "--host"

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Related to #106

Didn't see it sorry!

I had this issue too and after making the change, it works. Thank you.

Fixed in #107


test/e2e: wrap subscription e2e test logic in Eventually statement

Signed-off-by: Daniel Sover<EMAIL_ADDRESS>
Description of the change:
Fixes up the "with starting CSV" test by wrapping a flake-prone path with an Eventually()
Motivation for the change:
Flaky test
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /doc
[ ] Commit messages sensible and descriptive

/approve

/lgtm


toggle container events are reversed for basic toggle functionality

This issue does not affect off-canvas show / hide events, and only affects the normal toggle show / hide events.

Fixed.


Add isBlendMode utility.

We need to be able to validate any given blend mode. This will enable us to check the following CSS properties:

background-blend-mode
mix-blend-mode

We can do this by creating a helper function in the validators folder named isBlendMode.js. If you need an implementation reference, you can use https://github.com/ben-eb/css-values/blob/master/src/validators/isGenericFamily.js. All we need to do here is to reference the blending modes instead! You can find the list here: https://developer.mozilla.org/en-US/docs/Web/CSS/blend-mode
Don't forget to add isBlendMode to the index of validators, located at https://github.com/ben-eb/css-values/blob/master/src/validators/index.js.
Next, we need some way to tell css-values how to generate tests for these values. You can basically follow the existing format in https://github.com/ben-eb/css-values/blob/master/src/fixtures.js - import the list of blend modes and export an object named blendMode with those as valid values, and some made up invalid value.
We then need to add this to the tests. You can do this by updating https://github.com/ben-eb/css-values/blob/master/src/tests/validators.js with the isBlendMode validator that you created, named blendMode. If you run the tests now with npm test you will see that blend modes are validated properly.
Hopefully if everything worked correctly, css-values will now output a file that validates the properties listed above. You can check that it does by running npm run prepublish && npm run generate. There should be a new file in output/properties/compositingAndBlending. If this worked, then please add the properties to https://github.com/ben-eb/css-values/blob/master/src/completed.js.
If you're stuck, please post here and I'll help out in any way that I can. And with that being said, PRs welcome! 😃

I'd like to take a stab on it

Fixed in #10, many thanks to @delorge!

I want next validator task


Can't get refresh_token

Hi! Firstly, I don't speak english. So, please, be gently.
I'm trying to keep an offline access from my API with the following workflow:

I have an ionic app that makes the initial sign in. It has the offline access type so I get a serverAuthCode that I send to my API.
My API (that also have the offline access type) takes it serverAuthCode and with it, fetch an access_token, but I don't get any refresh_token, so then, when the access_token expires, I can't refresh it.

This is the code in my API:
$gClient = new \Google_Client();
$gClient->setAccessType('offline');
$gClient->setApplicationName('xxx');
$gClient->setClientId('xxx');
$gClient->setClientSecret('xxx');
$gClient->setRedirectUri('xxx');
$gClient->setDeveloperKey('xxx');
$gClient->addScope([
    'https://www.googleapis.com/auth/plus.profile.emails.read',
    'https://www.googleapis.com/auth/contacts.readonly',
]);

$accessToken = $gClient->fetchAccessTokenWithAuthCode($serverAuthCode);

$gClient->setAccessToken($accessToken);

$refreshToken = $gClient->getRefreshToken(); // It gives me null

$gOauth2 = new \Google_Service_Oauth2($gClient);

$payload = $gOauth2->userinfo_v2_me->get();

Can anyone help me, please?
Thanks!

Besides
$client->setAccessType('offline');
Need to include force prompt to Google return the refresh token:
$client->setApprovalPrompt('force');
Works for me.

I also try with $gClient->setApprovalPrompt('force'); but doesn't work too.
Can you tell me how is your client? that code is in your api?

You can see all my code: https://github.com/heukirne/geolocated-restricted-events/blob/master/generate_credentials.php
It's basically the Google Calendar Api PHP Example
https://developers.google.com/google-apps/calendar/quickstart/php

I see your code and tryied it. It works perfectly! But I'm using PHP as an API.
So, from the client (ionic 3), I get an serverAuthCode, that I send to my PHP API and exchange for an access_token. In that way, using the same code (but without generating an authUrl), I don't get any refresh_token.
Do you know any way to approach this case?

Probably the serverAuthCode from Ionic 3 doesn't allow offline access that release the refresh token. Maybe you need to set the access_type to offline in Ionic somewhere.

Yes, I already setted the access type to offline:
window['plugins'].googleplus.login(
  {
    'scopes': 'xxx',
    'webClientId': 'xxx',
    'offline': true,
  }, (gPlusResponse) => {
    // ...
  }, (errors) => {
    // ...
  }
);
}

It gives me a serverAuthCode that I exchange for a authCode, that works perfectly until it expires. That's why I want to get an refresh_token. But I can't. I don't understand why. All seems to be good.

Sorry, I can tell you.
You probably should take a look at Java Google Auth Api and look for how you can force the refresh_token.
https://github.com/EddyVerbruggen/cordova-plugin-googleplus/blob/master/src/android/GooglePlus.java

So, I suggest you to close this issue and open another in cordova-plugin-googleplus.

Thanks so much! I thought that it was a problem of my API (and this library).
Thanks again!


Possible new Goblin unit

https://www.hiveworkshop.com/threads/goblin-mercenary.240043/

https://www.hiveworkshop.com/threads/goblin-mage-variation-1.142634/


Discussion: scaffold for validation messages at question level

status quo

reactive_forms is heavily used
reactive_forms does not have a concept for questions (which survey.js uses at its core to model survey questions)
reactive_forms's validators are wired at widget level
reactive_forms's main user base seems to be those who build online forms according to requirements and usually from scratch, we, however, are expected to take whatever the survey.js creator throws at us
flutter_survey_js's most obvious use case for validators is the isRequired attribute specified at question level
flutter_survey_js's question usually consists of multiple widgets (either reactive or not)
flutter_survey_js's question sometimes map to more than one form control values (see https://github.com/goxiaoy/flutter_survey_js/issues/52#issuecomment-1534132950 and #81)
the "validation" can happen at form level (when forms are submitted)
or widgets level (when individual reactive widgets are touched)
validation errors are for the widget (or the caller) itself to parse and decide what to do (e.g. render an error message in red)

a similar concept
We already have a mechanism (or "wrap") for question titles. In the same vein, maybe we can come up with something similar? E.g. at the bottom of each question, we can choose to display an error message.
additional goodies
Once we have this "question-level validation message" in place, l10n of the required message would be a breeze: currently if one  is to provide a l10n message for required, he/she'll have to patch (at each reactive form widget's constructor) something like  validationMessages: {'required': (error) => '必填'}.

@goxiaoy @ChopinDavid thoughts?

https://github.com/joanpablo/reactive_forms#2-globalapplication-level

https://github.com/joanpablo/reactive_forms#2-globalapplication-level

@goxiaoy
Wow, I wasn't aware of this feature until you mentioned it. I guess it's safe to say I'm pleasantly surprised. This would eliminate the need to litter these tiny l10n tweaks everywhere.
That said, I still think we might have a strong case to make "isRequired" more explicit and/or pronounced at question level. If question titles warranted special treatment, maybe a "required" error message should, too. As we come up with more and more complicated implementations for various question types in terms reactive forms widgets, a concrete scaffold for validation messages at question level could potentially have a lot of appeal. It makes the intention clear and the code straight-forward.

I see, so ReactiveFormConfig would allow us to localize error messages across all widgets, which is convenient.
I am pretty concerned about

flutter_survey_js's question sometimes map to more than one form control values

This is true, as we've laid out in #81. I am not sure why SurveyJs decided to structure their response objects in this way. Our approach of having the comment specified in the response object:
{
  "question1": [
    "choice 1",
    "choice 2",
    "Some other response"
  ]
}

or
{
  "question1": {
    "values": [
      "choice 1",
      "choice 2"
    ],
    "comment": "Some other response"
  }
}

makes a whole lot more sense to me than how SurveyJS have elected to structure this same response:
{
  "question1": [
    "choice 1",
    "choice 2"
  ],
  "question1-Comment": "Some other response"
}

but we have little choice but to match how the main, web framework is structuring things. This is difficult, as we would now need to dynamically register multiple FormControls for certain survey elements depending on whether they support showOtherItem. This was experimented with a bit here.
This idea that one survey element can map to multiple FormControls is also the cause of

flutter_survey_js's question usually consists of multiple widgets (either reactive or not)

When considering lines 88-124 of lib/ui/elements/dropdown.dart, we see that we are displaying a ReactiveDropdownField when showOtherTextField == false , and a "_NonReactiveDropdownField" when showOtherTextField == true. This is because the ReactiveTextField that is rendered when showOtherTextField == true "hijacks" the FormControl previously designated for the ReactiveDropdownField. If there were two FormControls in this scenario, one for the ReactiveDropdownField and one for the ReactiveTextField, we could resolve not only the response formatting issue, but also this juggling of the single FormControl between the reactive dropdown, radio group, checkbox, etc. and their associated comment text field.

@ChopinDavid
Thanks for confirming the model mismatch between survey.js and reactive_forms. The points you listed above are real pain we have to deal with. I myself had similar (somewhat less extreme as dropdown) experience while implementing #33 .
If we can agree that a question-level scaffold is at least "useful", then the next logic step is to define what should be its responsibilities beyond merely question titles. How about:

a "shell" that behaves like a normal reactive form control
make whatever internal logic local to the question it models (insulate any possible sporadic "heavy hands" from outside)
coordination (state management) for children to properly (selectively) render themselves (e.g. the situation of ReactiveDropdownField  and _NonReactiveDropdownField you mentioned)
emits values to enclosing forms
populate values back from existing answers
triggers validation (react to touches)
parse and populate validation errors / messages for its children to consume
a common text field to display validation error messages (if any)

These seem to be a lot. Yet it could at the same time make our lives easier down the road. What do you think?


Update InternshipCard in the GUI to display {company name}[space]{role}

InternshipCard previous display the company name as the name of the internship, it has been changed to display
{company name}[space]{role} instead.
New method getDisplayName() has been added to Internship class.
All internships shown to users should have their name retrieved via getDisplayName().

Looks good to go


What goes in the config file?

What goes in the config file?

Sorry, I realize this script is still super-alpha. And a bigger apology that I didn't see this question till now, Oct 9th, holy smokes!
The session cookie you can get from your browser when you log in to humble bundle, just look at your cookies. One day I hope to automate it enough it'll take care of the logging in. This is just a side-side project right now, so any code submissions would be awesome.
cat .humbleBundle.cfg
sessionCookie: 'xxxxxxxxxxxxxxx'
saveDir: '/home/jsmith/saves'

I just made a pull request that, among other things, adds documentation about what is expected in the configuration file.

Cool, I'll look it over and get it merged in!


WIP Support calling more than one external scheduler

Chain the schedulers one after another based on a priority label and
add a context property to the even sent to them that contains all the
instances being scheduled so that the event can be generic.
We need to change the logic for prioritizing schedulers. Because the value is a string, the sorting wont behave as expected for numbers. Also, the value field is not indexed, so it is not an optimal query.
I have some work started on a jooq result handler and comparator.

@StrongMonkey i pushed an extra commit to this that was my work-in-progress for fixing the sorting. Its not finished and doesnt work, but it is how I want to do the sorting fix. Please make it work :-)

Closing in favor of https://github.com/rancher/cattle/pull/2415


Release OpenLineage java client to maven central

Already done. https://search.maven.org/artifact/io.openlineage/openlineage-java


Enforce spacing in between function definition

Problem
The scarb fmt doesn't enforce a given number of lines between two functions. This means that both
fn a() {}

fn b() {}

fn a() {}

fn b() {}

are currently valid.
Proposed Solution
Enforce either one or two lines spacing, but enforce!
Notes
No response

Hey! This is cairo-formatter issue, please report it here: https://github.com/starkware-libs/cairo

see https://github.com/starkware-libs/cairo/issues/3824


Doc: Block-derivation pseudo code for rollup node spec

Transferred from ENG-1737
EDIT(norswap): The goal is to add some pseudo-code to the rollup-node spec to give a more digestible overview of the changes.

Closed by #144


Airgapped Environment

Is your feature request related to a problem? Please describe.
I would love to use this in my environment, however it is an airgapped environment and cannot use this in its online only form.
Describe the solution you'd like
The ability to download and run the utility locally and make the icon that is generated for new installs with microwin run from a local source (be it local on that computer or locally from within the environment)
Describe alternatives you've considered
Alternative is not being able to use the tool.
Additional context
None really, i feel like this is a pretty clear description.

@aevans1987, you should be able to download the WinUtil script and run it in the air-gapped environment.


Install.Py - Collecting pyqtgraph - Not installing - Hanging

Install.Py - Collecting pyqtgraph - Not installing - Hanging for long time to install the package.
Building wheel for scipy (PEP 517) -

Can you try installing them manually:
sudo pip3 install scipy==1.4.1 pyqtgraph

Which Pi are you using?

Hi, I still face the same issue, It is not going beyond
Building wheel for scipy (PEP 517)
I m using Raspberry Pi 3

Try a few other scipy versions, you can find them here: https://pypi.org/project/scipy/#history
By default, I use version 1.4.1 because i found that to work the best. But maybe try the latest versions (1.5.0 to 1.5.2) and see if those install.
The other thing I can suggest is to just let it run, even if it takes an hour. It has to time out at some point and throw you an error. Once you get an error, it'll be easier to find a solution.

Tried leaving it for an hour and I got the below message 👍
"ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.
We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.
scipy 1.4.1 requires numpy>=1.13.3, but you'll have numpy 1.12.1 which is incompatible.
Successfully installed pyqtgraph-0.11.0 scipy-1.4.1"
Let me try executing and will reach out to you if I face issues.

Hi, I get a import module error on pyaudio, Can you please help
File "visualization.py", line 7, in
import microphone
File "/home/pi/dancyPi-audio-reactive-led/python/microphone.py", line 3, in
import pyaudio
ImportError: No module named 'pyaudio'

Numpy, Scipy, Pyqtgraph and Pyaudio are all installed at the same time - in my command above I removed pyaudio just to make sure that wasn't an issue. Just do sudo pip3 install pyaudio and that should install the module.
Also thanks for sharing the error. It's interesting and I wasn't aware of that update, I'll have to do so me testing and make sure my installer can work next month.

Thank You so much for responding very quickly, I am able to sort out the issues. Now DancyPi in action 👍  , Thank you.

Awesome! Glad you have it working :) Have fun!


Non project kotlin files crashes editor

If you have kotlin files (ktextension) which do not belong to the project itself in the project dirs, the editor crashes.
For example if you have a custom gradle plugin inside the main project dir, which is of course not built into the final  main.jar the editor crashes as it cannot find those classes in the main.jar.
I suspect the issue here is mainly that godot sees the kotlin files and tries to get script specific informations from them as it sees them as script resources.

Probably linked to #76


[will send crash log per DM!] Crash immediately when opening the app [4S, ios 8.4.1]

Hello!
I want to use riot.im for my iPhone 4S on ios 8.4.1 but it crashes immediately when opening the app, so I can't make a report or something, my phone is jailbroken though! Maybe there is a possibility somehow?
I tried deleting and reinstalling the app, and of course turning the phone off and on, but these won't work.
I haven't used riot.im before.
How could this problem be fixed, or how could I send an (anonymized!) report so you have the ability to see what's going wrong maybe?
Best regards!

Hey there! I was able to create crashlogs, and will happily provide them if asked per DM by developers (for privacy reasons).

Hi @riotimbuggggg, you can PM at @Manu:matrix.org.

The problem comes from a 3rd party library, WebRTC framework which uses iOS9 symbols:
- Dyld Error Message:
  Symbol not found: _AVCaptureSessionInterruptionReasonKey
  Referenced from: /private/var/mobile/Containers/Bundle/Application/XXXXXX/Riot.app/Frameworks/WebRTC.framework/WebRTC (which was built for iOS 9.0)
  Expected in: /System/Library/Frameworks/AVFoundation.framework/AVFoundation
 in /private/var/mobile/Containers/Bundle/Application/XXXX/Riot.app/Frameworks/WebRTC.framework/WebRTC
  Dyld Version: 353.12

I have opened an issue there: https://github.com/Anakros/WebRTC/issues/48.
I am afraid it cannot be fixed easily. The fix will probably be to move the minimal version to iOS9 - which I am going to do for Riot.