Breakpoints don't trigger on iPadOS when resizing a window with Stage Manager

Description
iPadOS provides some primitive window management features through Stage Manager. When resizing a React Native view using Unistyles and breakpoints one would expect that as you make the window smaller your UI will re-render with the correct styling for the given set of breakpoints. Instead the UI stays the same and overflows outside of the bounds of the application window.
I'm happy to put together an example repo if necessary, but this behavior seems trivial to reproduce in any repo that I've tried it in.
Interestingly if I console.log the Dimensions.width or Dimsensions.height from the Dimensions package in react-native the values update in realtime as I resize the window. So it seems the RN runtime is detecting the size.
Steps to reproduce

Grab an iPad or an iPad simulator
Enable Stage Manager - https://support.apple.com/en-us/105075
Install your favorite React Native app that uses Unistyles
Change the size of the screen and observe the styles don't update accordingly

Snack or a link to a repository (optional)
No response
Unistyles version
2.7.2
React Native version
0.74.1
Platforms
iOS
Engine
Hermes
Architecture
Paper (old)

Hey 👋 thanks for the report.
Should be easy to do (I guess), and I'm willing to support it as I'm also building cross platform.
Will get back to you, when I will have a plan when to release it.

I was interesting in learning more about unistyles and wanted to take a stab at this myself. It ended up being fairly simple!
https://github.com/jpudysz/react-native-unistyles/pull/209

How cool is that ?! Thank you!
I will review and test it. So most likely it will be merged in 1-2 days.

How cool is that ?! Thank you!

No problem! Happy to help!


Fix use=runtimestats heap test

resolves https://github.com/ponylang/ponyc/issues/4551

@dipinhora shall we merge this before or after #4552 ?

umm... good question.. my brain isn't working well enough for me to make a decision on this as it seems circular in nature.. 8*/

@dipinhora let's do this second.

@dipinhora let's do this second.

cokey dokey.. i'll rebase onto main once the other PR is merged..

@dipinhora can you rebase this against main? and then we can merge?

@dipinhora can you rebase this against main? once that is done and tests pass, i'll merge.

done


[SPARK-32792][SQL][FOLLOWUP] Fix Parquet filter pushdown NOT IN predicate

What changes were proposed in this pull request?
This pr fix Parquet filter pushdown NOT IN predicate if its values exceeds spark.sql.parquet.pushdown.inFilterThreshold. For example: Not(In(a, Array(2, 3, 7)). We can not push down not(and(gteq(a, 2), lteq(a, 7))).
Why are the changes needed?
Fix bug.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit test.

Test build #141073 has started for PR 33365 at commit 5472d0d.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45587/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45587/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45587/

+1, LGTM. Merging to master/3.2/3.1.
Thank you, @wangyum .

@wangyum This conflicts with branch-3.1. If you think, it should be in it, please, open a PR with backport.

Only master and branch-3.2 need this patch.

Test build #141073 has finished for PR 33365 at commit 5472d0d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141073/


LightLLM supports Multimodal llm, when will lorax?

Model description
https://github.com/ModelTC/lightllm/pull/266
Will there be vision llm support in Lorax soon?
Open source status

[X] The model implementation is available
[X] The model weights are available

Provide useful links for the implementation
https://github.com/ModelTC/lightllm/pull/266

Hey @Trickster85, yes, we definitely have support for VLMs planned (#179).
There are a few big items we want to get to first including speculative decoding, prefix caching, and embedding endpoints. Once those are done, we do plan on tackling VLMs, but definitely welcome contributions if folks want to take this on before then.


Fix issue when loading TS config with imports

Closes https://github.com/dotansimha/graphql-code-generator/issues/8437

Aborted in favor of #8441


Bluetooth "Set Up New Device..." Doesn't Work by Default

Post install, if a Bluetooth adapter is installed, the "Set Up New Device..." under the panel icon does not launch anything.  The user must install the gnome-bluetooth package manually in order to launch 'bluetooth-wizard'.  The wizard will launch by either the command line or from the panel icon when "Set Up New Device..." is selected.  This solution is not obvious to the user, so gnome-bluetooth or a similar package should be installed by default.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/11005992-bluetooth-set-up-new-device-doesn-t-work-by-default?utm_campaign=plugin&utm_content=tracker%2F10548672&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F10548672&utm_medium=issues&utm_source=github).

This project is for our website, I reported this bug on launchpad for you: https://bugs.launchpad.net/elementaryos/+bug/1443531

Thanks.  I was confused.


tuple: fix panic on i64

related: https://github.com/bluejekyll/foundationdb-rs/issues/119

This PR is WIP. I'm working to find more edge cases on integer encoding/decoding.

@bluejekyll I fixed crash on encoding/decoding edge cases:

encoding/decoding edge cases should work: i64::min_value(), i64::min_value()+1, i64::max_value(), i64::max_value()-1.
decoding non-representable values should return error: i64::max_value()+1 and larger values, i64::min_value()-1 and smaller values.

i64::min_value() is handled as a special case (Go also does it[0]), because it is an only value which abs() overflows.
[0] https://github.com/apple/foundationdb/blob/master/bindings/go/src/fdb/tuple/tuple.go#L557-L560

Ok. Let me know when you’re ready for merge.

@bluejekyll The PR is ready for merge, thanks.


Buildng project using only app router

What version of this package are you using?
2.6.2
What operating system, Node.js, and npm version?
node 20.2, npm: 9.6.6
What happened?
I have
When trying to build my application I got an error. It seems when trying to build the /404 and /505 pages next-translate tries to inject in there or sth and that causes an issue, because NextRouter was not mounted. which could be a sign, that it tries to use next/router import in an app router environment where it should use next/navigation
✓ Creating an optimized production build
 ✓ Compiled successfully
   Skipping validation of types
   Skipping linting
 ✓ Collecting page data
   Generating static pages (0/16)  [=   ]Error: NextRouter was not mounted. https://nextjs.org/docs/messages/next-router-not-mounted
    at useRouter (/Users/bjoernrave/projects/valooba-mono/node_modules/next-translate/node_modules/next/dist/client/router.js:146:15)
    at I18nProvider (/Users/bjoernrave/projects/valooba-mono/node_modules/next-translate/lib/cjs/I18nProvider.js:50:37)
    at Wc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)

Error occurred prerendering page "/404". Read more: https://nextjs.org/docs/messages/prerender-error
Error: NextRouter was not mounted. https://nextjs.org/docs/messages/next-router-not-mounted
    at useRouter (/Users/bjoernrave/projects/valooba-mono/node_modules/next-translate/node_modules/next/dist/client/router.js:146:15)
    at I18nProvider (/Users/bjoernrave/projects/valooba-mono/node_modules/next-translate/lib/cjs/I18nProvider.js:50:37)
    at Wc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
Error: NextRouter was not mounted. https://nextjs.org/docs/messages/next-router-not-mounted
    at useRouter (/Users/bjoernrave/projects/valooba-mono/node_modules/next-translate/node_modules/next/dist/client/router.js:146:15)
    at I18nProvider (/Users/bjoernrave/projects/valooba-mono/node_modules/next-translate/lib/cjs/I18nProvider.js:50:37)
    at Wc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)

Error occurred prerendering page "/500". Read more: https://nextjs.org/docs/messages/prerender-error
Error: NextRouter was not mounted. https://nextjs.org/docs/messages/next-router-not-mounted
    at useRouter (/Users/bjoernrave/projects/valooba-mono/node_modules/next-translate/node_modules/next/dist/client/router.js:146:15)
    at I18nProvider (/Users/bjoernrave/projects/valooba-mono/node_modules/next-translate/lib/cjs/I18nProvider.js:50:37)
    at Wc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
 ⚠ Entire page / deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /
 ⚠ Entire page /[lang]/dashboard/time-tracking deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /[lang]/dashboard/time-tracking
 ⚠ Entire page /[lang]/dashboard/time-tracking deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /[lang]/dashboard/time-tracking
 ⚠ Entire page /[lang]/dashboard/table-plan deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /[lang]/dashboard/table-plan
 ⚠ Entire page /[lang]/dashboard/table-plan deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /[lang]/dashboard/table-plan
 ⚠ Entire page /[lang]/dashboard/order-history deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /[lang]/dashboard/order-history
 ⚠ Entire page /[lang]/dashboard/order-history deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /[lang]/dashboard/order-history
   Generating static pages (4/16)  [==  ]
 ⚠ Entire page /[lang]/dashboard/products deopted into client-side rendering. https://nextjs.org/docs/messages/deopted
   Generating static pages (13/16) [=== ]
 ⚠ Entire page /[lang]/dashboard/service-calls deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /[lang]/dashboard/service-calls
 ⚠ Entire page /[lang]/dashboard/products deopted into client-side rendering. https://nextjs.org/docs/messages/deopted-into-client-rendering /[lang]/dashboard/products
 ⚠ Entire page /[lang]/dashboard/service-calls deopted into client-side rendering. https://nextjs.org/docs/messages/de
 ✓ Generating static pages (16/16)

> Export encountered errors on following paths:
        /_error: /404
        /_error: /500
 ELIFECYCLE  Command failed with exit code 1.

This is what my next.config.js looks like.

This is what the /[lang]/layout.tsx looks like:
import { redirect } from "next/navigation"
import ThemeRegistry from "@/components/ThemeRegistry"
import useTranslation from "next-translate/useTranslation"

import i18n from "../../i18n"

export default function RootLayout({
  children,
}: {
  children: React.ReactNode
}) {
  const { lang } = useTranslation()

  // Redirect to default locale if lang is not supported. /second-page -> /en/second-page
  if (!i18n.locales.includes(lang)) {
    redirect(`/${i18n.defaultLocale}/${lang}`)
  }

  return (
    <div className="flex min-h-screen w-full flex-col bg-primary-700 text-white">
      <ThemeRegistry lang={lang}>{children}</ThemeRegistry>
    </div>
  )
}

export function generateStaticParams() {
  return i18n.locales.map((locale) => ({
    lang: locale,
  }))
}

When I dont remove i18n from the config this is  what I get for every route:
Error occurred prerendering page "/de". Read more: https://nextjs.org/docs/messages/prerender-error
Error: The provided export path '/' doesn't match the '/[lang]' page.
Read more: https://nextjs.org/docs/messages/export-path-mismatch
    at getParams (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/export/helpers/get-params.js:27:15)
    at exportPageImpl (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/export/worker.js:86:47)
    at /Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/export/worker.js:214:22
    at Span.traceAsyncFn (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/trace/trace.js:105:26)
    at Object.exportPage (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/export/worker.js:213:41)
    at execFunction (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/compiled/jest-worker/processChild.js:1:2764)
    at execHelper (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/compiled/jest-worker/processChild.js:1:2422)
    at execMethod (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/compiled/jest-worker/processChild.js:1:2510)
    at process.messageListener (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/compiled/jest-worker/processChild.js:1:1228)
    at process.emit (node:events:511:28)

Error occurred prerendering page "/en/dashboard/table-plan". Read more: https://nextjs.org/docs/messages/prerender-error
Error: The provided export path '/dashboard/table-plan' doesn't match the '/[lang]/dashboard/table-plan' page.
Read more: https://nextjs.org/docs/messages/export-path-mismatch
    at getParams (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/export/helpers/get-params.js:27:15)
    at exportPageImpl (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/export/worker.js:86:47)
    at /Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/export/worker.js:214:22
    at Span.traceAsyncFn (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/trace/trace.js:105:26)
    at Object.exportPage (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/export/worker.js:213:41)
    at execFunction (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/compiled/jest-worker/processChild.js:1:2764)
    at execHelper (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/compiled/jest-worker/processChild.js:1:2422)
    at execMethod (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/compiled/jest-worker/processChild.js:1:2510)
    at process.messageListener (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/compiled/jest-worker/processChild.js:1:1228)
    at process.emit (node:events:511:28)

Error occurred prerendering page "/en/dashboard/time-tracking". Read more: https://nextjs.org/docs/messages/prerender-error
Error: The provided export path '/dashboard/time-tracking' doesn't match the '/[lang]/dashboard/time-tracking' page.
Read more: https://nextjs.org/docs/messages/export-path-mismatch
    at getParams (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/export/helpers/get-params.js:27:15)
    at exportPageImpl (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/export/worker.js:86:47)
    at /Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/export/worker.js:214:22
    at Span.traceAsyncFn (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/trace/trace.js:105:26)
    at Object.exportPage (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/export/worker.js:213:41)
    at execFunction (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/compiled/jest-worker/processChild.js:1:2764)
    at execHelper (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/compiled/jest-worker/processChild.js:1:2422)
    at execMethod (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/compiled/jest-worker/processChild.js:1:2510)
    at process.messageListener (/Users/bjoernrave/projects/valooba-mono/apps/pds/node_modules/next/dist/compiled/jest-worker/processChild.js:1:1228)
    at process.emit (node:events:511:28)

Probably is related to https://github.com/aralroca/next-translate/issues/1144 about generateStaticParams

Possible, but as far as I can tell in the linked issue the problem is due to the i18n object being present in the config. since I am only on app router I removed it from my next.config.js file as you can see above, but the NextRouter was not mounted error persists.  Read more: https://nextjs.org/docs/messages/prerender-error
Error: NextRouter was not mounted. https://nextjs.org/docs/messages/next-router-not-mounted
    at useRouter (/Users/bjoernrave/projects/valooba-mono/node_modules/next-translate/node_modules/next/dist/client/router.js:146:15)
    at I18nProvider (/Users/bjoernrave/projects/valooba-mono/node_modules/next-translate/lib/cjs/I18nProvider.js:50:37)
    at Wc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/Users/bjoernrave/projects/valooba-mono/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
 ✓ Generating static pages (8/8)

> Export encountered errors on following paths:
        /_error: /404
        /_error: /500
        /_error: /de/404
        /_error: /de/500
        /_error: /en/404
        /_error: /en/500

I can confirm this issue, I also get the following error:
> Export encountered errors on following paths:
        /_error: /404
        /_error: /500

I'm no expert of this project, but I doubt the example is functional, look at this redirect:
redirect(`/${i18n.defaultLocale}/${lang}`)

I guess here should be a redirect to the requested path and not to the root, also this /en/non-supported-lang redirect doesn't make any sense to me, unless lang is not a language identifier but a page subpath (which would be even stranger).

I found a solution here that works for me. It requires a few tweaks but overall, all the ingredients are here.

I found a solution here that works for me. It requires a few tweaks but overall, all the ingredients are here.

I see no solution in link you provided.
Still no idea how to avoid using next/router instead of next/navigate

In the end I switched to another package because I think this one is not ready yet. I've tried quite hard but without success. I've used next international which worked flawlessly With the new app directory (even with the latest versions of next).

Tested today<EMAIL_ADDRESS>but cannot make this package working.
Problems encountered

The official example with app dir is not working.

In layout.tsx is not possible to get the current request pathname, because a layout "wraps" more than one request. A better place to handle "HTTP redirection" (/about to /en/about) is Next.js middleware, where pathname is available. Said so:

this code should be moved in middleware https://github.com/aralroca/next-translate/blob/7b9587cd2ac3b865ee4709a1331effd953eddbef/examples/with-app-directory/src/app/layout.tsx#L12-L13
that code also is also potential wrong like @cglacet in https://github.com/aralroca/next-translate/issues/1171#issuecomment-1840503739

The middleware never runs, in order to make it "run" it had to remove nextTranslate(nextConfig) from next.config.js, but like this the entire library is disabled.


Fix sporadic timing issue with spec

@jrafanie Please review.

This is easier to review with whitespace diffs


Cannot install package on Windows An unknown git error occurred

When i'm trying to install package on Windows with command npm install "https://github.com/castlabs/electron-releases#v31.3.0+wvcus" --save-dev I'm still getting error:
0 verbose cli C:\Users\kryst\AppData\Local\fnm_multishells\13448_1722444081793\node.exe C:\Users\kryst\AppData\Local\fnm_multishells\13448_1722444081793\node_modules\npm\bin\npm-cli.js
1 info using<EMAIL_ADDRESS>2 info using<EMAIL_ADDRESS>3 silly config load:file:C:\Users\kryst\AppData\Roaming\fnm\node-versions\v20.16.0\installation\node_modules\npm\npmrc
4 silly config load:file:D:\Projects\project\.npmrc
5 silly config load:file:C:\Users\kryst\.npmrc
6 silly config load:file:C:\Users\kryst\AppData\Local\fnm_multishells\13448_1722444081793\etc\npmrc
7 verbose title npm install https://github.com/castlabs/electron-releases#v31.3.0+wvcus
8 verbose argv "install" "https://github.com/castlabs/electron-releases#v31.3.0+wvcus" "--save-dev"
9 verbose logfile logs-max:10 dir:C:\Users\kryst\AppData\Local\npm-cache\_logs\2024-07-31T16_43_33_038Z-
10 verbose logfile C:\Users\kryst\AppData\Local\npm-cache\_logs\2024-07-31T16_43_33_038Z-debug-0.log
11 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
12 silly logfile done cleaning log files
13 verbose stack Error: An unknown git error occurred
13 verbose stack     at makeError (C:\Users\kryst\AppData\Roaming\fnm\node-versions\v20.16.0\installation\node_modules\npm\node_modules\@npmcli\git\lib\make-error.js:28:13)
13 verbose stack     at C:\Users\kryst\AppData\Roaming\fnm\node-versions\v20.16.0\installation\node_modules\npm\node_modules\@npmcli\git\lib\spawn.js:37:26
13 verbose stack     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
14 error code<PHONE_NUMBER>
15 error An unknown git error occurred
16 error command git --no-replace-objects ls-remote<EMAIL_ADDRESS>17 silly unfinished npm timer reify<PHONE_NUMBER>496
18 silly unfinished npm timer reify:loadTrees<PHONE_NUMBER>500
19 silly unfinished npm timer idealTree:userRequests<PHONE_NUMBER>507
20 verbose cwd D:\Projects\project
21 verbose os Windows_NT 10.0.22631
22 verbose node v20.16.0
23 verbose npm  v10.8.1
24 verbose exit<PHONE_NUMBER>
25 verbose code<PHONE_NUMBER>

I cannot find any solution on web for this. I was trying to install using another versions of node and npm but it's not helping.

Strange, can you run the failing command line directly outside of npm? I.e execute:
git --no-replace-objects ls-remote<EMAIL_ADDRESS>

I can't repro this on my Windows box, or anywhere else, when using npm. I can however get the error if I explicitly use the above git command on a machine where the public key that matches what I have registered with GitHub is missing (since ssh transport is used).
I'm not sure why, but in your case it seems that npm opts to use ssh as the transport layer, which requires that a public key is registered on GitHub. Probably something specific to your setup since I'm not able to reproduce it. AFAICT you either need to figure out what is different with your setup, or register a public key on GitHub to allow the use of ssh.

Yes i can run this command without any problems. I have already registred ssh key on github and when i call command
ssh -T<EMAIL_ADDRESS>I see message that i'm successfully authenticated.


Update TerseTS to support various compression parameterizations

This issue is to enable TerseTS to accept different kinds of parameters to the compression algorithms. For example, PWCH does not receive an error bound, instead, it receives a minimum compression ratio (which internally is treated as the number of bins in the histogram). Likewise, other methods will require their parameterization instead of the current generic error_bound.
Originally posted by @skejserjensen in https://github.com/cmcuza/TerseTS/pull/50#discussion_r1845217883

For the full discussion, see this conversation in #50.

As specified in #46 the API of TerseTS is already inconsistent as some languages use a Configuration struct while other use multiple parameters for method and error_bound.
So the first question to answer is which API to standardize on. I propose using a Configuration struct everywhere as it can then differ per method instead of having parameters that must all be passed arguments despite each method only using a subset, e.g., error_bound is used by many but not all compression methods and number_of_buckets is only used by a few compression methods.
The next question is how this Configuration struct should look. One option could be to simply have have the total set of supported parameters in one struct, i.e., have the struct contain method, error_bound, number_of_buckets, etc. This is very simple and allows any combination of parameters to be passed to any compression method which can then just check that all the parameters it needs is present and maybe that nothing unsupported is set. To make it simpler for the user to create this struct, appropriate APIs for each language should be created, e.g., an anonymous struct could maybe be used in Zig, optional arguments in Python, and a builder pattern in Rust.
Although one issue with having one struct with all parameters is that it could become very big, making it hard for users to understand what variables should be set for each compression method. So an alternative could be to to create a Parameter struct per method and make the Configuration struct consist of the method enum and a pointer to a Parameter struct. Making Parameter a pointer ensures Configuration has the same size no matter what Parameter contains, thus making the API easier to implement. The compression method to use can then be easily selected by just reading the enum, while the compression method knows which Parameter struct it  needs and can thus cast the struct to the correct type and read the variables it contains. If needed, methods could also be added like how interfaces are sometimes implemented in Zig. Another way to think about it is as a very simple form of manually implemented inheritance from OOP since there are one known type with a fixed size and multiple specialized types with different variables and thus sizes. Alternatively maybe a tagged union could be used as the API already has method. Although it seems simpler to map structs with different variables to the various bindings.
These are my initial thoughts on how to solve this issue. Of course there are still some unknown, e.g., how to precisely implement these different solutions for each binding as the users of the bindings should not need to know how the Zig code works to use the bindings. Personally I prefer to start with the simplest solution that fulfill all requirements and then only escalate to a more complex solution when measurements show that it is needed. Thus, I think having all parameters directly in the Configuration struct is fine for now. Of course, assuming a good API for creating an instance with only the variables needed for each compression method set can be created for all bindings. What do you think @cmcuza?


Immediately interrupt worker threads when terminating

When we terminate bookwyrm, we want the worker thread to immediately join. Currently we poll inside the source scripts whether we should return. This is slow.
I'd like to keep boiler-plate a minimum in the actual scripts. We could check for interrupt in script_butler::add_item(), but we don't know how long it will take to get there, since the script needs to fetch the item in question first.
Perhaps we could spawn a nested thread that just waits until it's time to throw an interrupt exception. But that means we have two threads for each source. Ugly.
Or perhaps there is some hack we can exploit in pybind11. But if that is the case, the script butler will turn ugly if and when we decide to add support for other languages.
For now we'll just have to sprinkle checks in appropriate places in the source scripts.

https://stackoverflow.com/questions/3822674/for-pthread-how-to-kill-child-thread-from-the-main-thread

During termination, if the threads take to long to join, we could probably pthread_kill() them. This isn't safe, and probably prone to memory leaks, but shouldn't matter since it's done during termination.
An other option is to fork() the main thread and exit(). With this, bw_instance is invalidated and the worker threads would end themselves (eventually).


Custom Gradient Function Variable Naming

Hi,
When I create a custom gradient function like:
@wp.func_grad(example)
def adj_example(a: float, b: float, adj_ret: float):

	...

    if (a < 0.0):
        adj_a = adj_ret

    wp.adjoint[a] += adj_a

the generated code looks like this:
static CUDA_CALLABLE void adj_example(
    float32 var_a,
    float32 var_b,
    float32 & var_adj_ret)
{

	...

    // if (vn < 0.0):
    var_9 = (var_a < var_0);
    if (var_9) {
        // adj_a = adj_ret
        wp::copy(var_10, var_7);  <----------------------------
    }
    // wp.adjoint[a] += adj_a
	var_11 = wp::add(adj_a, adj_a);  <----------------------------
    adj_a = var_11;
}

First, adj_a is substituted with var_10 in the wp::copy call. In the next appearance of adj_a in wp::add, it is not substituted with var_10 anymore. This is very unexpected (at least to me). Am I missing something here?
Thanks in advance!

Hi Clemens,
This is definitely a bug where the variable names seem to clash with the adj_a variable. We will have this fixed in the next release, but for now you could try a different variable name and clear the cache.
@wp.func_grad(example)
def adj_example(a: float, b: float, adj_ret: float):
    # ...

    temp = 0.0  # use a variable name other than `adj_a` here and initialize with 0
    if a < 0.0:
        temp = adj_ret

    wp.adjoint[a] += temp

Hi Eric,
thanks for your suggestion, it is indeed easy to fix so not an issue for me. Just hard to identify in the first place, so thanks for looking into it!


Cannot control the Tello using keystrokes

Hello,
first, thank you for taking to the time to publish such a nice library to play with the Tello using C++.
I am not sure this is an issue or it's my improper use of the library, but I figured it may happen to other people so I decided to ask here.
I cannot get the Tello to respond to keystrokes using tello.move(), I keep getting error messages:
[Tello] Failed to send command 'rc 0.000000 0.000000 0.000000 0.000000': Timeout waiting for response
[Tello] Failed to send command 'rc 0.000000 0.000000 -5.000000 0.000000': Timeout waiting for response
[Tello] Failed to send command 'rc 0.000000 0.000000 0.000000 0.000000': Timeout waiting for response

Comms seem fine, because I do get the Tello to take off, send video stream, move around e.g. using turn_right() / turn_left() and land. The problem is with controlling it in real time with the keyboard using move().
I assume it is to do with an incorrect configuration of delays and/or not capturing properly the keystrokes.
I tried two different approaches:

first using cv::waitKey() from OpenCV  to capture the keystrokes - see code here:  https://github.com/mhered/cpp_100daysofcode/blob/main/code/Day053_18-05-23/Tello
second using onelonecoder's simple game engine to capture the keystrokes - see code here: https://github.com/mhered/cpp_100daysofcode/blob/main/code/Day096_30-06-23/Tello2 In the second case I even made a very crude tello_dummy.hpp header simulating the tello.hpp interface to test that keystrokes were sent properly

I also played with different values of delays using tello.sleep() to speed up or slow down the control loop
... but all attempts failed similarly.
Any idea of what I am doing wrong?
Thanks for your help!

Hi! Thank you for opening this issue!
Unfortunately I do not have a tello with me to test anything. I took a look at the code at https://github.com/mhered/cpp_100daysofcode/tree/main/code/Day053_18-05-23/Tello, but I can't spot a major mistake. Given the error message you are seeing, it seems like the response is not working. Are you sure everything else is working properly? Do all other commands work? What if you simply call takeoff, turn_left() and move() in a row with hardcoded values (preferrably zero), does it work in itself?
I modified the execute_command function to print the command instead of sending it and always return ok. This way, it seems like everything is working, when i press the keys in the window, the value changes. I tried it in Ubuntu/WSL because I don't have OpenCV on Windows.
You can take a look at send_request() in tello.hpp, it is responsible for actually sending and receiving the commands. Also, there is a #define TELLO_DEFAULT_COMMAND_TIMEOUT which you can alter. send_request() works in a way that it sends the command via one UDP Client and then waits for a response on another UDP Server. As soon as data arrives, this is the response, the function returns, and the response is evaluated. That means, if no data arrives, you will have the timeout you are seeing, or if it is somehow missed.
Please check yourself what the response for the rc command is or what it should be, you can also modify the function to simply print the response before returning. Maybe I just never tested the rc command and it does not actually send any response. Please check that.
I hope you can do a bit more investigation, I cannot help you directly because I have no tello for testing. PRINTF_DEBUG is your friend :)
Things you should check:

Does the move() command work at all or just not in this context?
Modify some functions in tello.hpp (especially send_request()):

What command is really being sent?
What response is sent back?
If at all, how long does it take?
There is a difference between 'commands' and 'actions'
Modify TELLO_DEFAULT_COMMAND_TIMEOUT (or action timeout) for testing only, no command should ever take longer than 1 sec

Use Wireshark to sniff what packets are actually being sent, to check if the UDP server misses it

Let me know if you know more!


Roll Flutter from 6c3a0e4d21da to 3598f20002b5 (16 revisions)

https://github.com/flutter/flutter/compare/6c3a0e4d21da...3598f20002b5
2022-06-26<EMAIL_ADDRESS>Roll Flutter Engine from d3be1c33681e to ee56813c14c8 (1 revision) (flutter/flutter#106639)
2022-06-26<EMAIL_ADDRESS>Roll Flutter Engine from b64be81fb409 to d3be1c33681e (1 revision) (flutter/flutter#106628)
2022-06-26<EMAIL_ADDRESS>Roll Flutter Engine from aea6a1c3e421 to b64be81fb409 (1 revision) (flutter/flutter#106622)
2022-06-25<EMAIL_ADDRESS>Roll Flutter Engine from 9caf2f9e0688 to aea6a1c3e421 (1 revision) (flutter/flutter#106616)
2022-06-25<EMAIL_ADDRESS>Roll Flutter Engine from 674b90f6226c to 9caf2f9e0688 (1 revision) (flutter/flutter#106600)
2022-06-25<EMAIL_ADDRESS>Roll Flutter Engine from a1dd50405992 to 674b90f6226c (1 revision) (flutter/flutter#106598)
2022-06-25<EMAIL_ADDRESS>Fix BidirectionalIterator deprecation warning and roll engine to a1dd50405992 (flutter/flutter#106595)
2022-06-25<EMAIL_ADDRESS>Roll Flutter Engine from 83b9a591a3d5 to 4446e3edda6a (5 revisions) (flutter/flutter#106591)
2022-06-25<EMAIL_ADDRESS>Fix .packages breakage and roll engine to 83b9a591a3d5 (flutter/flutter#106584)
2022-06-24<EMAIL_ADDRESS>Export public API types from foundation/scheduler/gestures/semantics (flutter/flutter#106409)
2022-06-24<EMAIL_ADDRESS>Update 2_bug.md to ask for backtrace explicitly (flutter/flutter#103001)
2022-06-24<EMAIL_ADDRESS>[flutter_tools] tool exit from flutter create when provided just a drive letter (flutter/flutter#106451)
2022-06-24<EMAIL_ADDRESS>Roll Flutter Engine from fc08bf45b0a8 to ea756c55f29a (39 revisions) (flutter/flutter#106574)
2022-06-24<EMAIL_ADDRESS>[flutter_tools] migrate project-validate to analyze --suggestions (flutter/flutter#106149)
2022-06-24<EMAIL_ADDRESS>feat(tools): Arbitrary browser flags (closes #65575)  (flutter/flutter#104935)
2022-06-24<EMAIL_ADDRESS>Roll Plugins from dfd1b6e7d83e to 8bf46f15bfe8 (9 revisions) (flutter/flutter#106564)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-plugins
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Plugins: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


The last PR

Everything looks 👌 but flak8 is not happy because he is stubborn a bit yes but let's make him happy :)


Add nuget restore CLI PackagesDirectory for package.config

Add required option when restoring via package.config
Add unit tests to ensure we include the CLI option

:sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)
Bug fix for nuget restore CLI.
:arrow_heading_down: What is the current behavior?
Nukeeper fails to restore nuget packages for older project types with package.config entries.
:new: What is the new behavior (if this is a feature change)?
Includes the missing nuget CLI option required for the restoring of packages.
:boom: Does this PR introduce a breaking change?
No
:bug: Recommendations for testing
Tested against 24 Azure DevOps private repositories with multiple private NuGet sources.
:memo: Links to relevant issues/docs
See - https://docs.microsoft.com/en-us/nuget/reference/cli-reference/cli-ref-restore.
The resent nuget versions include the required option "-PackagesDirectory" when restoring via package.config files.
:thinking: Checklist before submitting

[x] All projects build
[x] Relevant documentation was updated
[x] Unit test added

@AnthonySteele @MarcBruins @shep1987. Would you mind reviewing the following PR. I'm working through a series of legacy .net software solutions to sanity check the changes before creating the PR and working through the MAC, Linux AzDO pipeline you have configured.

Bump - Let's get this into main?


Fix SSR by not using window in UMD script

Solves #300

Thanks @danielr18! I really appreciate this. I had assumed SSR already worked but I hadn't tested it. The fix makes sense.
I'll try to get this merged and released as soon as I'm back at my computer.
By the way - are you using the cassette alpha in a project of yours? If you have any other feedback, or want to contribute tests or documentation where it's sparse, that would be awesome. :)

@danielr18 great! this looks perfect. I merged your change and it's published as version 2.0.0-alpha.5.


[Bug] Unable to load Firebase app options: missing or malformed while it's there and correct (Desktop)

[REQUIRED] Please fill in the following fields:

Unity editor version: 2020.2.1f1
Firebase Unity SDK version: 6.15.1 and 7.1.0
Source you installed the SDK: Unity Package Manager (.unitypackage or Unity Package Manager)
Problematic Firebase Component: FirebaseApp (Auth, Database, etc.)
Other Firebase Components in use: FirebaseAnalytics, FirebaseFirestore, FirebaseFunctions (Auth, Database, etc.)
Additional SDKs you are using: Steamworks but even if it's not included in the build, it still happens (Facebook, AdMob, etc.)
Platform you are using the Unity editor on: Windows (Mac, Windows, or Linux)
Platform you are targeting: Desktop (iOS, Android, and/or desktop)
Scripting Runtime: IL2CPP (Mono, and/or IL2CPP)

[REQUIRED] Please describe the issue here:
On some of my users's PC (possibly all of them are Windows users, but who knows) FirebaseApp just fails to be created.
It fails to load the FirebaseApp options, this is what it says on startup:

Unable to load Firebase app options ([Application_Data/StreamingAssets\google-services-desktop.json, Application_Data/StreamingAssets\google-services.json] are missing or malformed)

And when I first get FirebaseFirestore.DefaultInstance and it tries to create it, it throws this exception because there are no options loaded:
InitializationException:  Firebase app creation failed.
  at Firebase.FirebaseApp.CreateAndTrack (Firebase.FirebaseApp+CreateDelegate createDelegate, Firebase.FirebaseApp existingProxy) [0x000e3] in <348e5429a2d04280bc0cb46752ede7db>:0
  at Firebase.FirebaseApp.Create () [0x00027] in <348e5429a2d04280bc0cb46752ede7db>:0
  at Firebase.FirebaseApp.get_DefaultInstance () [0x00017] in <348e5429a2d04280bc0cb46752ede7db>:0
  at Firebase.Firestore.FirebaseFirestore.get_DefaultInstance () [0x00000] in <b004a94077e84d5c87ca4c668ed59347>:0
  at FirebaseSystem.AddDocument (System.String collectionName, System.Collections.Generic.Dictionary`2[TKey,TValue] documentData, System.Action`1[T] onSuccess, System.String extraInfo) [0x0002c] in <a86eca02e20e4b89aadd008b280117df>:0
  at FirebaseSystem.SendGameEnd (System.Collections.Generic.Dictionary`2[TKey,TValue] gameEndData, System.Action`1[T] onSuccess) [0x00130] in <a86eca02e20e4b89aadd008b280117df>:0
  at GameManager.SendGameEnd () [0x000c8] in <a86eca02e20e4b89aadd008b280117df>:0
...

I checked and I had the same google-services-desktop.json there as them. I even told them to replace theirs with mine, maybe there is an "invisible character" in theirs. But no, it still couldn't be loaded.
And only small part of the player base reported this issue.
Steps to reproduce:
I couldn't reproduce it, because it's only happening on their PC.
Relevant Code:
All the Firebase stuff I have at startup is just:
`FirebaseApp.CheckAndFixDependenciesAsync().ContinueWith(continuationAction: task =>
{
	FirebaseAnalytics.SetAnalyticsCollectionEnabled(true);
});`

And this is where it crashes, because it fails to create the FirebaseApp because there are no options loaded.
var db = FirebaseFirestore.DefaultInstance;

Hi @PortgateStudios,
From the error message you provided, it seems that the configuration file can't be detected. I've found a Stack Overflow post that talks about this, and some causes of it are special characters in the file path or the config file not exactly named "google-services.json". With that, please ensure that your users' configurations don't have any of these mistakes.
I'll be closing this for now. Feel free to comment if the issue persists so that this ticket can be reopened.
Thanks!

Yes, I created a special folder called Ádám (common Hungarian name), put the application inside that, and now the app options couldn't be loaded...
Great, at least now I can do a workaround this.
As I see this isn't a new issue. Why isn't thix fixed yet and is there an estimation about it?
Cheers!

Hi @PortgateStudios,
I have filed an internal request for this issue. I don't have any timelines for the fix, so I'll be leaving this open for now.
Thanks.


is-filtered sometimes returns false instead of true

Subj

for QA:
Click on Assistant button on site which should be filtered. Check if switch is on. Reload page and try again - there should be no random on/off status between reloads.


Serialization issues

Since flo 0.2.9 and introduction of forking and serialization I am running into issues testing and running flo tasks.
The current errors I get are:
java.lang.AssertionError: assertion failed: (List(import java.this.lang._),List())
scala.MatchError: None (of class scala.None$)

They seem related to:

https://groups.google.com/forum/#!msg/akka-user/jvbbilXDKdA/giruRnnSCwAJ
https://issues.scala-lang.org/browse/SI-9808
https://groups.google.com/forum/m/#!topic/scala-user/IL_RfFj_yxE
https://stackoverflow.com/questions/21687142/scala-match-on-optionobject-not-exhaustive-with-someo-and-none-in-akka-recei

My current hunch is that we might need to introduce chill and improve the kryo registrar configuration, similar to what scio does.
I created the ticket to raise awareness of the issue, ask for help and document my findings. I still need to bring the steps to reproduce the issue.

This should be resolved by #107

@labianchin is is this still an issue?

I have to update to newer version of flo and try it out. I might do this later this week.
I believe a likely scenario is that I won't find anymore issues, but still in the future it is possible some people will try to share non serializable objects between flo tasks.
So, I would suggest that we improve the documentation on how flo tasks run, how to troubleshoot serialization issues, known issues?, FAQ?,etc. before closing this task. It does need to be long and super complete documentation, maybe we can start with 4-5 sentences related to serialization, maybe pointing to this Github issue.

Now using flo 0.2.16 I have not experienced any serialization issues.


Rewrite Build Script to use NPM

The build script should not be based solely on PowerShell.

I believe this was complete in PR #73


New branch for microshift bundle creation

microshift bundles are not able to created same way as podman or openshift bundles. It have some prerequisites and by default snc.sh script not work. This issue is to discuss what would be much cleaner approach to create a microshift bundle. Either by a branch or creating another script microshift.sh in master branch which start the microshift VM and then createdisk script able to create the bundle.
As of now the steps required.

Clone the microshift repo https://github.com/openshift/microshift
Remove the customization of service and use core user

sed -i '/# customizations/,$d' scripts/image-builder/config/blueprint_v0.0.1.toml
sed -i 's/redhat/core/g' scripts/image-builder/config/kickstart.ks.template

Create the rpm for offline images

https://github.com/openshift/microshift/blob/main/docs/rhel4edge_iso.md#offline-containers

Create the rpm for microshift

make rpm

Build Installer (ISO)

https://github.com/openshift/microshift/blob/main/docs/rhel4edge_iso.md#building-installer

Create VM using generated ISO

https://github.com/openshift/microshift/blob/main/docs/rhel4edge_iso.md#install-microshift-for-edge

Create disk image which need some changes in the script side.

In my opinion, the separate branch we have for podman is something we should be getting rid of. We already had bugs because needed commits were in one branch and not the other. So I'd avoid adding a new branch for microshift.

creating another script microshift.sh

prefered

We already have now the way to create the microshift bundle using microshift.sh script.


Fix a few nullability warnings.

I'm having problems finding the warnings in my code, so now that the interface branch is merged to main in #18, I think its time to start fixing the obvious ones at least.

Number of warnings in app-lib-dotnet reduced from 419 to 227. Half of the remaining issues are cs8618, where non-nullabe properties requires a constructor to set a non-null value. They are really annoying when deserializing objects from JSON, and I typically just add  = default!; to fix them, but it needs to be done with care.

Number of warnings in app-lib-dotnet reduced from 419 to 227. Half of the remaining issues are cs8618, where non-nullabe properties requires a constructor to set a non-null value. They are really annoying when deserializing objects from JSON, and I typically just add  = default!; to fix them, but it needs to be done with care.

Great job @ivarne 👍 I see there is a conflict, but I think that's related to changes cone by @tjololo yesterday and I assume he would like a quick look on this as well to get some nit picking eyes on this:)


the vote count no longer shows when trying to vote on a proposal

the vote count no longer shows when trying to vote on a proposal

resolved by https://github.com/crypto-power/cryptopower/commit/6850bc167bfdd8a7ae5808ec23755eb6fc8db9bd


Upadate REAME.md, Add  tkniter and Fireworks

documentation add to README.md
Added my little contribution using tkniter for pawn promotion and fireworks when checkmate

thanks!
let's have the pull request fix one thing, in this case the README.md file
we can't yet update our mini-max algorithm, that will be updated with the better of the two team's code
We are looking update the pawn promotion to be completely self-contained with pygame (see video in issue #34)

thanks!
let's have the pull request fix one thing, in this case the README.md file
we can't yet update our mini-max algorithm, that will be updated with the better of the two team's code
We are looking update the pawn promotion to be completely self-contained with pygame (see video in issue #34)


timeline plugin: add offset parameter

Short description of changes:
Sometimes it's required to adjust the timeline to the audio. For example, the timeline displays musical bars with a specific time signature. However, the audio does not start at 0 seconds, but maybe at 0.3 seconds. This new parameters allows passing an offset in seconds to the timeline plugin to adjust the timeline to the audio. The value may also be negative.
Breaking in the external API:
None
Breaking changes in the internal API:
None
Todos/Notes:
What about documentation? If you can point me to a direction, I can check it. 🙂
Related Issues and other PRs:
None

Coverage decreased (-0.09%) to 69.733% when pulling bbb32899153d73b2fdd747bef642c4e558a14d86 on moritzvieli:feature/add-offset-to-timeline into faa7d660f758f493914f30341c0983222788ab35 on katspaugh:master.

@thijstriemstra done. Is it still missing somewhere?

@moritzvieli yea probably here: https://github.com/katspaugh/wavesurfer.js/blob/master/example/timeline/index.html#L96

@moritzvieli yea probably here: https://github.com/katspaugh/wavesurfer.js/blob/master/example/timeline/index.html#L96

@thijstriemstra True, thanks! I have not found any additional places to add the new param. Is it OK now?

Hi @thijstriemstra, first of all thanks for all the work you guys do! When do you expect release with this PR?

When do you expect release with this PR?

@kjakobson opened #1651 for that


Fix error if subscribed to announcement channel

telegram_client.get_participants will fail if trying to get participant from an announcement channel and the user isn't an admin of said announcement channel

@muntahailmi this is cool - could we make the except catch more specific please - what is the specific exception you actually get?

I got telethon.errors.rpcerrorlist.ChatAdminRequiredError
I've edited it a bit, though honestly, this is like, my first time touching python, so it might not be up to best practice.
So feel free to correct any mistake I made.

@ndejong I've updated it, removing the general exception catcher.
Thank you very much for checking it for me.


add 'PUT' and 'DELETE' methods for webhook action

 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.

Thanks @lmangani  for the merge !


lose not in translation text

Kubernetes will try to not schedule the pod onto the node

not is lost in Chinese translation text.

I signed it

good catch~ Thanks
/lgtm

/lgtm
/approve


204: Password reprompt for sensitive areas

Impeccable work. I love it. Just a few notes and questions. I pushed one typo fix (please confirm I was right about it being a typo).
Thanks!


Fix altitude parsing in join form logic

Altitude is reported by the city in feet, but we store it in meters, so we need to convert, and round to the nearest 0.1 meters when we do a lookup in the join form

Do you have a source you can link to about what units the city gives us the height in?

I don't have a source, I just spot checked a few addresses and they were totally off. Converting to meters made everything make sense


Changed lines show in wrong spot.

Describe the bug
The changed git lines, are not shown in proper place.
In red I highlighted where  minimap shows it, in green - where changed git lines are.
To Reproduce
Not sure, but problem is gone if I disable folding, and reload minimap.
Expected behavior
Changed lines should be shown few lines up in minimp
Screenshots

Please complete the following information:

OS: Linux.
NVIM v0.10.1
Build type: Release
LuaJIT 2.1.1720049189

Additional context
I tried to reload minimap but it would not help. Disabling code folding in my buffer helps... But it is not fix..
my setup
    init = function()
      -- The following options are recommended when layout == "float"
      vim.opt.wrap = false
      vim.opt.sidescrolloff = 36 -- Set a large value

      --- Put your configuration here
      ---@type Neominimap.UserConfig
      vim.g.neominimap = {
        auto_enable = true,

        layout = "float",
        float = { z_index = 10 },
        diagnostic = {
          enabled = false,
        },
        git = {
          enabled = true,
          mode = "line",
        },
        search = {
          enabled = true,
          mode = "sign",
        },
        win_filter = function(winid)
          return winid == vim.api.nvim_get_current_win()
        end,
      }
      -- link NeominimapGitAddLine highlight to DiffAdd
      vim.api.nvim_set_hl(0, "NeominimapGitAddLine", { link = "DiffAdd" })
      vim.api.nvim_set_hl(0, "NeominimapGitChangeLine", { link = "DiffChange" })
      vim.api.nvim_set_hl(0, "NeominimapGitDeleteLine", { link = "DiffDelete" })
    end,

This issue is related to foldings. I'm going to fix this soon.

Could you checkout #137 and see if it resolves the issue you’ve encountered? Your feedback would be greatly appreciated!

Yes it works great now. That was fast.
btw. I was thinking - if u could expose option to show  minimap  only for current buffer / Window.
I made it work with
        win_filter = function(winid)
          return winid == vim.api.nvim_get_current_win()
        end,

But imo, this would be convenient as option in   config.  Thanks for the fix.

Thank you for the suggestion! However, I’d like to keep this plugin as simple as possible. The win_filter option exists specifically to give users the flexibility to handle cases like this themselves. I believe that adding this as a built-in option might complicate the configuration unnecessarily.
That said, I think it’s a great idea to document this use case, so I’ll add it to the wiki. Thanks again for your input!


Added Pawn Sensing Component To AI Controller[EnemyAI] To Sense[Sight] The Player.

Resolves #6

Looks good!
Just one question, what's the reason for the deletion for thse 2 files?

Blueprint_CeilingLight.uasset
Floor_400x400.uasset

No, they are not necessarily so, and I don't know how that got deleted.


Unexpected event 'FlagsChanged' when using complex-modifications for vim mode

This is my config:
{
    "global": {
        "check_for_updates_on_startup": true,
        "show_in_menu_bar": false,
        "show_profile_name_in_menu_bar": false
    },
    "profiles": [
        {
            "complex_modifications": {
                "rules": [
                    {
                        "manipulators": [
                            {
                                "description": "Change left_control + hjkl to arrow key",
                                "from": {
                                    "key_code": "h",
                                    "modifiers": {
                                        "mandatory": [
                                            "left_control"
                                        ],"optional":["any"]
                                    }
                                },
                                "to": [
                                    {
                                        "key_code": "left_arrow"
                                    }
                                ],
                                "type": "basic"
                            },
                            {
                                "description": "Change left_control + hjkl to arrow key",
                                "from": {
                                    "key_code": "j",
                                    "modifiers": {
                                        "mandatory": [
                                            "left_control"
                                        ],"optional":["any"]
                                    }
                                },
                                "to": [
                                    {
                                        "key_code": "down_arrow"
                                    }
                                ],
                                "type": "basic"
                            },
                            {
                                "description": "Change left_control + hjkl to arrow key",
                                "from": {
                                    "key_code": "k",
                                    "modifiers": {
                                        "mandatory": [
                                            "left_control"
                                        ],"optional":["any"]
                                    }
                                },
                                "to": [
                                    {
                                        "key_code": "up_arrow"
                                    }
                                ],
                                "type": "basic"
                            },
                            {
                                "description": "Change left_control + hjkl to arrow key",
                                "from": {
                                    "key_code": "l",
                                    "modifiers": {
                                        "mandatory": [
                                            "left_control"
                                        ],"optional":["any"]
                                    }
                                },
                                "to": [
                                    {
                                        "key_code": "right_arrow"
                                    }
                                ],
                                "type": "basic"
                            }
                        ]
                    }
                ]
            },
            "devices": [
                {
                    "disable_built_in_keyboard_if_exists": true,
                    "identifiers": {
                        "is_keyboard": true,
                        "is_pointing_device": false,
                        "product_id": 34050,
                        "vendor_id": 2652
                    },
                    "ignore": false
                },
                {
                    "disable_built_in_keyboard_if_exists": true,
                    "identifiers": {
                        "is_keyboard": true,
                        "is_pointing_device": false,
                        "product_id": 256,
                        "vendor_id": 2131
                    },
                    "ignore": false
                }
            ],
            "fn_function_keys": {
                "f1": "display_brightness_decrement",
                "f10": "mute",
                "f11": "volume_decrement",
                "f12": "volume_increment",
                "f2": "display_brightness_increment",
                "f3": "mission_control",
                "f4": "launchpad",
                "f5": "illumination_decrement",
                "f6": "illumination_increment",
                "f7": "rewind",
                "f8": "play_or_pause",
                "f9": "fastforward"
            },
            "name": "hyper + arrow",
            "selected": true,
            "simple_modifications": {
                "caps_lock": "left_control"
            },
            "virtual_hid_keyboard": {
                "caps_lock_delay_milliseconds": 0,
                "keyboard_type": "ansi"
            }
        }
    ]
}

When I use CTRL-J/CTRL-K, things goes fine, event log:
eventType:FlagsChanged    code:0x3b       name:left_control    flags:Ctrl                               misc:
eventType:FlagsChanged    code:0x3b       name:left_control    flags:                                   misc:
eventType:KeyDown         code:0x7d       name:down_arrow      flags:NumPad Fn                          misc:
eventType:KeyDown         code:0x7d       name:down_arrow      flags:NumPad Fn                          misc:
eventType:KeyDown         code:0x7d       name:down_arrow      flags:NumPad Fn                          misc:
eventType:KeyDown         code:0x7d       name:down_arrow      flags:NumPad Fn                          misc:
eventType:KeyDown         code:0x7d       name:down_arrow      flags:NumPad Fn                          misc:
eventType:KeyDown         code:0x7d       name:down_arrow      flags:NumPad Fn                          misc:
eventType:KeyDown         code:0x7d       name:down_arrow      flags:NumPad Fn                          misc:
eventType:KeyDown         code:0x7d       name:down_arrow      flags:NumPad Fn                          misc:
eventType:KeyDown         code:0x7d       name:down_arrow      flags:NumPad Fn                          misc:
eventType:KeyUp           code:0x7d       name:down_arrow      flags:NumPad Fn                          misc:

But when I use CTRL-H/CTRL-L, things goes different:
eventType:FlagsChanged    code:0x3b       name:left_control    flags:Ctrl                               misc:
eventType:FlagsChanged    code:0x3b       name:left_control    flags:                                   misc:
eventType:KeyDown         code:0x7b       name:left_arrow      flags:NumPad Fn                          misc:
eventType:FlagsChanged    code:0x3b       name:left_control    flags:Ctrl                               misc:
eventType:KeyDown         code:0x7b       name:left_arrow      flags:Ctrl NumPad Fn                     misc:
eventType:KeyDown         code:0x7b       name:left_arrow      flags:Ctrl NumPad Fn                     misc:
eventType:KeyDown         code:0x7b       name:left_arrow      flags:Ctrl NumPad Fn                     misc:
eventType:KeyDown         code:0x7b       name:left_arrow      flags:Ctrl NumPad Fn                     misc:
eventType:KeyDown         code:0x7b       name:left_arrow      flags:Ctrl NumPad Fn                     misc:
eventType:KeyDown         code:0x7b       name:left_arrow      flags:Ctrl NumPad Fn                     misc:
eventType:KeyDown         code:0x7b       name:left_arrow      flags:Ctrl NumPad Fn                     misc:
eventType:KeyDown         code:0x7b       name:left_arrow      flags:Ctrl NumPad Fn                     misc:
eventType:KeyUp           code:0x7b       name:left_arrow      flags:Ctrl NumPad Fn                     misc:
eventType:FlagsChanged    code:0x3b       name:left_control    flags:                                   misc:

An FlagsChanged event unexpectedly happened and set the follow-up events with modifier 'Ctrl'.
I dont know whether it's a config mistake or a bug for karabiner. I need help...

Seems an unexpected 'Ctrl' flag change has taken place after 'H' key down, which makes long pressing 'H' key with unexpected 'Ctrl' modifier.

 Hope for fixing this.

Ctrl + HJKL are default macOS shortcuts. Would it help, if you use Fn + HJKL as arrow keys, and then make the letter S to be recognized as Fn if pressed alone?
This way you can use S + HJKL as arrow keys. This is actually the vi-mode on the old Karabiner.

Sweet, I was having the exact same problem and this seems to have fixed it for me.

Since version 0.91.5 is shipped, I've implemented a Vi mode for KE that can be directly imported into the app, which works fine.
http://yige.ch/vi-mode-for-karabiner-elements/


Improve Epochs docs (and more)

Based on my question in the forum, I suggest to clarify the preload parameter to make it clear that preloading does not depend on the status of raw.preload (which I assumed was the case).
I'd change the preload description as follows:

Load all epochs from disk into memory when creating the object or wait before accessing each epoch (more memory efficient but can be slower).

In addition, I'd add the following note:

Epochs are preloaded based on the value of the preload argument. Even if the raw argument has already been preloaded, the returned Epochs object will not be preloaded by default. This means that bad epochs (e.g. epochs with not enough data) will not be dropped immediately, so the number of good epochs displayed may change once the epochs are preloaded.

@hoechenberger @larsoner @agramfort @drammock since this is such a widely used object I'd be grateful if you commented and edited my suggestion if necessary.
Furthermore, I noticed that preload is used inconsistently across BaseEpochs, Epochs, EpochsArray, and EpochsFIF classes:

BaseEpochs: Doesn't have a preload parameter but preload_at_end - what's the reason to use a different parameter?
Epochs: preload=False
EpochsArray: Has neither preload nor preload_at_end parameters.
EpochsFIF: preload=True

I think it would be great to double-check these inconsistencies - there are probably good reasons, but if not we should discuss changing accordingly.
Finally, @hoechenberger suggested to discuss preload=None as a default, meaning that this would re-use its raw.preload value.

Proposed new docstring:

Whether to load the epochs into RAM when creating the object, or to access the epochs from disk when needed (more memory efficient but can be slower). Note that some operations require epochs to be loaded into RAM (e.g., epoch rejection based on peak values, setting the EEG reference, etc). Loading into RAM can also be done later with mne.Epochs.load_data. Default is False.

Thanks @drammock. I assume that this description does not need an additional note anymore.
Also, I haven't checked the implementation, but is it really true that preload=False always implies loading from disk? I assumed that if I pass a preloaded Raw object to Epochs(..., preload=False), the data used to create epochs is accessed from RAM (the preloaded Raw object) instead of going back to loading from disk. What if a Raw object isn't associated with a file?

Furthermore, the gotcha I ran into doesn't have anything to do with "some operations", which sounds as if this might happen only in some cases. Eventually, the Epochs objects has to be created, and that's where epoch rejection automatically takes place.

Also, I haven't checked the implementation, but is it really true that preload=False always implies loading from disk?

it's easy enough to test the behavior just by preloading a raw, then epoching it with preload=False and a rejection dict specified.  Indeed, the epoch rejection won't occur upon object creation; only after explicitly calling epochs.load_data().  You're probably right that strictly speaking this does not mean the epochs are "on disk"; I'd guess they store a reference to the raw object that prevents it getting GCd.  I think you'd have to read the source to be sure.

I just checked, and it seems like it really does load epochs from disk even if the Raw object is already loaded into RAM. This seems a bit inefficient, but I guess this is not what this issue is about. Let's focus on improving the docstring and maybe making the preload business a bit more consistent.

let me try to bring some clarification. The motivation was that by default
creating an Epochs object
was immediate. So even if raw.preload=True then no rejection is done and
nothing is allocated.
Also you can drop bad epochs without keeping everything is RAM. It will
read eventually drop
bad epochs and then release the memory. See calling epochs.drop_bad()  on
epochs with
preload=False.

Thanks @agramfort, I think this makes sense, but it isn't very clear. So before I open a PR, can we discuss the inconsistent usage of preload parameters in the four classes (see top comment)?

EpochsFIF has preload=True by default for historical reasons. It seems overkill to me to change-by-deprecation this to preload=False but we could do it.
Other than this, to me everything is consistent and we should just make clear that preload means "should this instance load all of its data into memory". Then Raw having preload=True (or False) means the given instance hold all of its data in memory (or not), Epochs having preload=True (or False) means its instance holds all of its data in memory (or not). From this it seems clear why doing read_raw_fif(..., preload=True) followed by Epochs(..., preload=False) would mean the Raw instance has all of its data in memory but the Epochs instance does not.

EpochsFIF has preload=True by default for historical reasons. It seems overkill to me to change-by-deprecation this to preload=False but we could do it.

I'd do it.
The way you put it makes the reasoning very clear, I'll adopt something like this somewhere in the docstring.
However, what about

BaseEpochs: Doesn't have a preload parameter but preload_at_end - what's the reason to use a different parameter?
EpochsArray: Has neither preload nor preload_at_end parameters.

BaseEpochs: Doesn't have a preload parameter but preload_at_end - what's the reason to use a different parameter?

No users should construct use this class on their own, so I'm not worried about this. (If it's not clear that users shouldn't use this, we should add a .. warning:: to the docstring at the top.) To know why you'd have to dig into the code, I don't remember offhand.

EpochsArray: Has neither preload nor preload_at_end parameters.

The data are already in an array, i.e., in memory.

Re BaseEpochs, it basically uses preload_at_end like preload (or rather, we could easily change it to preload).
Re EpochsArray, the same could be said about preloaded raw (epochs just slice out the relevant data).

we could easily change it to preload

My experience with making changes to Epochs is that anything involving data loading is never easy and has unintended consequences. If you want to try to work through it I guess we could do it, but I think there are probably many targets more worthy of our attention in our codebase.

Re EpochsArray, the same could be said about preloaded raw (epochs just slice out the relevant data).

The key part here is the "epochs just slice out the relevant data" -- in the preload=False case this happens on demand one epoch at a time as they are accessed and these data are not kept/stored in memory by the epochs instance. In the preload=True case, all these data slices are stored together (and held in a new, potentially very memory-consuming ndarray in memory separate from that of the raw instance) by the epochs instance. So for example with raw preload=True epochs preload=False your memory consumption will be whatever it takes to store your raw data; for raw preload=True epochs preload=True it will be 2x (assuming your epochs overlap perfectly with all time samples of raw for example).

My experience with making changes to Epochs is that anything involving data loading is never easy and has unintended consequences. If you want to try to work through it I guess we could do it, but I think there are probably many targets more worthy of our attention in our codebase.

OK!
Are you saying that with Epochs(preload=False) you need to keep the raw object around?

Are you saying that with Epochs(preload=False) you need to keep the raw object around?

It gets stored in Epochs._raw or so, so yes it stays around automatically at least until you epochs.load_data()

So why can't EpochsArray have a preload parameter then? Because we pass it data that is already equal to the epoched data, meaning that implicitly preload=True?

Yes

OK, final thought: would it make sense to make BaseEpochs an ABC?

What do we gain from it?

Other people won't bother us with these questions again 😄. It's just a matter of style, you don't have to do it, but this is a classic example of an abstract base class, so we could as well declare it as such.

Plus a more tangible benefit is that people can't instantiate EpochsBase, they will get an error. Now this is not enforced, it's only in the docstring.

+1 to make it an ABC if that's a painless process ;)

As long as you can still type check against it using isinstance then I don't care one way or the other.

Type checking with isinstance is exactly the point of ABCs, so yes, it works. It should be as simple as inheriting from collections.ABC and slapping @abstractmethod decorators on methods, but we'll have to see if it is really that painless. I can try and run the test suite to see if this works.

Sounds good, I'm excited to see how this works!

Closing for #8888


Performance-related question

Any plans to use newly introduced Span<T> for more efficient interop with native esent.dll?
https://channel9.msdn.com/Events/Connect/2017/T125

Did you have any specific API's to request it for?
Were you thinking of a new overload for Api.SetColumns that took Span<byte>?
(Come to think of it, there are also some APIs that could benefit from switching to IEnumerable from regular arrays.)
I'm no longer officially maintaining ManagedEsent. @michaelthorp is. :) He'd be the one to make the call on whether to increase the minimum framework version (Does Span<T> require a new framework, or just a newer compiler?).
In the past, when I made a change that required a newer framework version (was it 4.0?) that wasn't available on XP, some people complained. Now that XP is no longer getting security updates, that's not a valid reason, but there may be a similar requirement for Windows 7?
-martin

Upon further reading of the comments:
"Yes, but Span<T> is only available as a preview. I won't ship as a stable before next year."
Drat, we'll have to wait!


Joshfischer/update docs

@nwangtw This PR fixes the rest of the broken links.. 🤞 .  There are still a few more items before the page is ready to go.. You can see it here.  Let's merge this for now if you feel it is good to go.

Thanks!


Use an in use nickname

i didn't even understand the title of the PR.


[Queue] limit in data queue

Set max number in queue when sending data to other node.
Signed-off-by: Jaeyun<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #109. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @jaeyun-jung, src/libnnstreamer-edge/nnstreamer-edge-queue.c does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

Related issue: #103


Add support for Ubiquiti devices

Found some MIBs https://community.ui.com/questions/Where-to-find-UAPs-and-USWs-MIB-files/1764e3d3-0950-4072-b483-11a65e1e5e43


Option to disable the annoying popups that appear when hovering over symbols

VSCode Version: 1.13.1
OS Version: win10

Steps to Reproduce:

open a JS file
hover a param

Expect: NOTHING
Found

I REALLY want it to stop doing that! I want vs-code to be the cool minimalist tool I started with, and it gets bloated after every update

After googling - I found
  "typescript.validate.enable": false,

which is evidently not it.
Couldn't find anything else, just debates over the same setting.
Please help?

That's all the settings I could find, none of them do the trick:
  "typescript.disableAutomaticTypeAcquisition": true,
  "typescript.useCodeSnippetsOnMethodSuggest": false,
  "typescript.check.npmIsInstalled": false,
  "typescript.check.tscVersion" : false,
  "typescript.validate.enable": false,
  "typescript.format.enable": false,
  "typescript.referencesCodeLens.enabled": false,

Please help... it bothers me so much I 'll just have to stop using vscode

"editor.parameterHints": false

Doesn't work :(

// Place your settings in this file to overwrite the default settings
{ "editor.fontSize": 18,
  "editor.wordWrap": "off",
  "editor.wrappingIndent": "indent",
  "search.exclude": {
		"**/node_modules": false
  },
  "editor.parameterHints": false,
  "typescript.disableAutomaticTypeAcquisition": true,
  "typescript.useCodeSnippetsOnMethodSuggest": false,
  "typescript.check.npmIsInstalled": false,
  "typescript.check.tscVersion" : false,
  "typescript.validate.enable": false,
  "typescript.format.enable": false,
  "typescript.referencesCodeLens.enabled": false,
  "workbench.colorTheme": "Visual Studio Light"
}

@joaomoreno  - please reopen...

went over all the settings, disabled anything that might make sense, for no avail :(
even tried restarting the app
{ "editor.fontSize": 18,
  "editor.wordWrap": "off",
  "editor.wrappingIndent": "indent",
  "search.exclude": {
		"**/node_modules": false
  },
  "editor.parameterHints": false,
  "typescript.disableAutomaticTypeAcquisition": true,
  "typescript.useCodeSnippetsOnMethodSuggest": false,
  "typescript.check.npmIsInstalled": false,
  "typescript.check.tscVersion" : false,
  "typescript.validate.enable": false,
  "typescript.format.enable": false,
  "typescript.referencesCodeLens.enabled": false,
  "workbench.colorTheme": "Visual Studio Light",
  "editor.quickSuggestions": {
    "other": false,
    "comments": false,
    "strings": false
  },
  "editor.autoClosingBrackets": false,
  "editor.snippetSuggestions": "none"
}

Help?

I guess you want a setting to disable the hover widget.

ok, if that's what it's called...
I don't want the editor to popup anything unless I did something to trigger it.
Hovering does not count, because I move the mouse while I think, and the popups break my train of thoughts.
man, this actually ended up costing me money...

tl;dr:
consider a mode that this popup appears in response to a triggered user action other than hover.
something in the spirit of Ctrl+shift+space, which resembles Ctrl+space for auto-completion
or double/tripple click for mouse users
:)

There is a "hidden" setting, "editor.hover": false, which entirely disables the hover widget. It is not public, nor documented, as there are some complicated interactions of this setting with debugging. e.g. the setting will be reset to true after a debug session...

wow. it worked!   what a relief...
It did require restart of the editor though (and since the motto is working with editor instance per git repo - they all had to be restart... 😛 )
You say it resets after a debug session? I rarely debug - I usually run with prints, however - If I'll see it jumps - I'll update with my experience.

Anyway - to make a close of this issue, what I believe we should do is:

document the current status
make it stay between debug sessions (if it still jumps)
allow configure a way to invoke it by a shortcut-key stroke of the user initiative
document the end result

If you think it needs to be handled in few different issues - I'll adhere, just let me follow them too 👍

Hi there! Is there any way to disable typescript typings on hover? E.g. I'm using https://github.com/flowtype/flow-for-vscode and want to see only flow typings, so disabling hover completely is not the solution.

I like the "editor.hover": false setting (thanks tons, @alexandrudima), but not that I have to bounce the app to get it to take effect because sometimes I want them, sometimes I don't - mounds -vs- almond joy
suggestion would be to have a "hot key" to toggle it on/off - and personally I wouldn't care if it didn't survive a restart and default "enabled" if I could just hit a short-cut to disable every popup at-will without bouncing the app.  "Silent" mode as it were.

manually activate the tooltips / colorpicker:
if you have set "editor.hover" to false you can manually activate the tooltips or the colorpicker by pressing the shortcut  "CTRL+K+I". You can close the tooltip with "ESC" (if the tooltip has lost the focus, just click on the tooltip again and press "ESC")
Thank me later :)

@audiot, that's a great tip;  single-use toggle  -- many thanks!! (it's later) :)

Hi there,
I'm using VSCode 1.25.1 on OSX 10.11.6 El Capitan. This exact issue is happening to me except setting editor.hover to false does nothing. I'm at the end of my rope here, I do not need giant tooltips hovering in my face explaining what a <div> element is.
I've set
"editor.hover": false,
"editor.parameterHints": false,
"editor.quickSuggestions:" false,

and I still get the hover tooltips, everywhere.
Is there anything else I can do? Does this option no longer exist?

Yes, the option is now "editor.hover.enabled": false.

editor.hover.enabled seems to not work if you also have editor.hover defined. I had to delete the old line before it would honor the new one.

This technically resolves this issue, but what many of us really want is the option to remove TypeScript types from the hover widget. It's really confusing when using the Flow extension. https://github.com/Microsoft/vscode/issues/30114#issuecomment-368848010

Have been looking for a way to disable the hover widget for a long time now, I actually stopped using VSCode because of that, done it but sadly this disables every pop up even when you intentionally hold down the command key, you don't get the inteli-sense,  the main reason why anyone would want to remove the pop up is to avoid distractions when moving their mouse across their code, but intentionally holding down command is a different thing altogether, when a user does that then they really want to display some inteli-sense info.

Yeah this took way too much time. There's too many synonymous features that all sound like they may affect this (ie: "suggestions", "definitions", etc) and way too many settings surrounding them, that lead to a rabbit hole of Google results that frustratingly don't solve the problem.
This setting needs to be a clearly labeled checkbox in the main Text Editor settings.

@stepankuzmin Did u found a solution to disable non flow typings?

I think a smart way is to allow "turning off these notification" on the popover itself. it's crazy annoying.

I can't believe having to ask for an OPTION to turn popups off.  Nobody needs them. Remove them altogether and I'll make an "Annoying popups" extension for those wanting to distract their kittens. 18 months and this issue is still opened.

I made an extension, that switches the hover-widget on and off:
https://marketplace.visualstudio.com/items?itemName=RoyAction.toggle-hover
... read the description!

@istarkov

@stepankuzmin Did u found a solution to disable non flow typings?

I turned these off using: Extensions -> search @builtin types -> disable TypeScript and Javascript Language Features

Found editor.hover.delay was perfect for me, the problem is not that I don't want the hover widget, but that it was always blocking vision and clicks.

I still can't get rid of these very annoying popups. Every time I use my python debugger, when I hover over a variable name it pops up a huge popup showing the content of the variable, which is very distracting and hurts my eyeballs. I've tried everything in this and other threads to no avail. Here's my settings.json:

{
  "editor.hover.enabled": false,
  "editor.hover.sticky": false,
  "editor.quickSuggestions": {
      "other": false,
      "comments": false,
      "strings": false
    },
    "editor.parameterHints.enabled": false,
    "editor.suggest.snippetsPreventQuickSuggestions": false,
    "html.suggest.html5": false,
    "editor.snippetSuggestions": "none",
    "editor.codeLens": false,
    "typescript.validate.enable": false,
    "editor.hover.delay": 300000,

}

Some other info: I'm using VSCode as a remote editor, so don't know if that has an impact here. Can anyone help? I'll likely abandon VSCode if I can't resolve this.

We shouldn't HAVE to disable it, it shouldn't just be there. From a UI design point of view, unsollicited clickable and selectable and HUGE popups are a abysmally bad choice.
I don't have the editor choice in my environment... sadly.

Putting together all info here:

"editor.hover.enabled": false if you want the hover widget gone completely
Set editor.hover.delay if you want a longer delay between hovering and showing the widget
If you just want TypeScript's hover gone, type @builtin typescript into extension widget and disable it. Beware this will disable all TypeScript language features, and you may need another language server such as flow to get auto-completion etc

OP asked for an option, and there's an option now, thus closing.

Considering his issue was opened over 2 years ago, and there is an extremely excessive number of "hover" and "tooltip" settings, I really think this needs to be added to the Text Editor Settings in the UI, which is where a user would logically expect it to be.
The bulk of this thread (including OP) is centered around the terrible UX related to this setting, and the current implementation does not address that.
Issue should be re-opened.

I really think this needs to be added to the Text Editor Settings in the UI, which is where a user would logically expect it to be.

If you have concrete suggestions, feel free to open a new issue.

terrible UX

If you have concrete cases when UX is terrible (include a screenshot / screen recording if possible), open new issues.

Here's an example of terrrible UX :

Who needs to be reminded all the time, not on a click event or a keypress, but a mouseover, of the definition of the li tag? Moreover, wanting to click in the line above fires a link.
I would be glad to be part of a general discussion about the general UX of VS Code. We have the proof here, 2 years later, that opening an issue won't do anything.

If you don't like it, you can turn it off with the option "editor.hover.enabled": false. You can also increase the delay so it doesn't show unless you hover on it for 3 seconds.
While you think it is not useful to you, keep in mind that:

There are many users who are new to HTML and such hover can be useful for them.
There are new or less-used HTML elements that little people know about. Off the top of your head, can you tell me what are <rt>, <bdi> or <wbr>?
If you are working on a language you are less familiar with, you might need these hover information as well

If you don't like it, you can turn it off with the option "editor.hover.enabled": false. You can also increase the delay so it doesn't show unless you hover on it for 3 seconds.
While you think it is not useful to you, keep in mind that:

There are many users who are new to HTML and such hover can be useful for them.
There are new or less-used HTML elements that little people know about. Off the top of your head, can you tell me what are <rt>, <bdi> or <wbr>?
If you are working on a language you are less familiar with, you might need these hover information as well

As I posted above, "editor.hover.enabled": false does NOT work.

Yep, this https://github.com/microsoft/vscode/issues/30114#issuecomment-368848010 is the main issue. As a user of flowtype I want to see only flowtype hints at js files (at least with @flow annotation) I don't want to disable all hovers, I don;t want to disable ts for all files. And delay id perfect for me. So issue can't be closed as it's not solved somehow

As I posted above, "editor.hover.enabled": false does NOT work.

As explained above two years ago: https://github.com/microsoft/vscode/issues/30114#issuecomment-321490156

As a user of flowtype I want to see only flowtype hints at js files (at least with @flow annotation) I don't want to disable all hovers, I don;t want to disable ts for all files. And delay is perfect for me. So issue can't be closed as it's not solved somehow

That's all you can do now: Either use TS or Flow

You are saying you don't like TS and Flow conflicting with each other, and you want features from both. There's no way to do that, and that's not the same as the original issue.

It's ok I've completely abandoned the vscode debugger in favor of pdb. I encourage others to do the same.


English translation strings are not loaded

The file nunaliit_lang.en.js is not loaded, even if provided.

Actually, this works as expected.


Matrix transpose bug in Net::parseMatrixSpec

Thanks to Michael Whidden for reporting the following:
I noticed in Net::parseMatrixSpec that the code that is documented as doing a matrix transpose of the convolution matrix isn't actually doing so. I changed it to this to get it to work, but I did not actually test running a net with a convolution layer to make sure the "working" transpose doesn't end up causing some downstream issues.
    for (unsigned x = 0; x < mat.size(); ++x) {
        if (x == 0) {
            firstRowSize = mat[x].size(); // Remember the first row size
        } else if (mat[x].size() != firstRowSize){
            cout << "Error: in convolution matrix in topology config file, inconsistent matrix row size" << endl;
            throw("Error in topology config file: inconsistent row size in convolve matrix spec");
        }
    }
    for(unsigned y=0; y < firstRowSize; ++y){
        convMat.push_back(vector<float>());
        for (unsigned x = 0; x < mat.size(); ++x) {
            convMat.back().push_back(mat[x][y]);
        }
    }

Confirmed. Tested with convolve matrices of {1,1} and {{1},{1}}. The former, a row matrix, should sum two pixels at a time on the same horizontal row. The second form, a column matrix, should sum two pixels at a time from the same column. The proposed fix works correctly in both cases and doesn't break anything else. Thanks to Michael for this fix.


Failing upgrade test: Missing finality signatures, sync back stalled

The upgrade test fails on CI here: https://drone-auto-casper-network.casperlabs.io/casper-network/casper-node/7769/2/4
The reason is that the sync back process is stalled on trying to get finality signatures for block 119. Even though the symptoms are identical to the one from the #3747, we think the root cause is different, i.e. in the NCTL based network we expect all peers to be fully saturated with signatures, so they should never return Absent error.

It turns out that this does boil down to the same issue as for #3747.
In the test, nodes 1-5 are the genesis nodes, the network is upgraded, then nodes 6-10 are bid in but not started for a couple of eras, and finally started.
Nodes 1-5 stake way more than nodes 6-10, so the upgraded network continues to run for the period of time where 6-10 are deemed validators but are not running.
Once nodes 6-10 are started, they are joining mid way through an era in which they are validators.  They all correctly receive sync leaps and attempt to sync the initial block - a block which they would have signed if they had been validating at the time.
Node 6 does manage to completely sync this block and transition to Validate mode.  However nodes 7-10 all fail in the same way: when trying to acquire strict finality signatures, they keep requesting the same 5 signatures - the signatures of nodes 6-10.  Since these signatures were never created and will never be created, they are trapped in this state.
The fix seems to be the same as discussed for #3747, i.e. randomise the list of validators from which we choose 5 to fetch.  This would have undoubtedly allowed nodes 7-10 to complete the sync of that block and transition to Validate mode.
As such, I'm closing this ticket as a duplicate.