Issue - Calendar component app crash on vercel

NextUI Version
2.4.6
Describe the bug
I recently upgraded to nextui version 2.4.6 in order for me to use the perfect DatePicker and Calendar components. Howver once i run the app locally, it runs fine without any BUGS, but on vercel the app crashes and in the logs it displays the error below.
Tried using vercel's node version and the build was still running fine without errors.
Error: Cannot find package '/var/task/node_modules/<EMAIL_ADDRESS>imported from /var/task/node_modules/<EMAIL_ADDRESS>Did you mean to import<EMAIL_ADDRESS>    at legacyMainResolve (node:internal/modules/esm/resolve:219:26)
    at packageResolve (node:internal/modules/esm/resolve:845:14)
    at moduleResolve (node:internal/modules/esm/resolve:931:18)
    at moduleResolveWithNodePath (node:internal/modules/esm/resolve:1173:14)
    at defaultResolve (node:internal/modules/esm/resolve:1216:79)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39)
    at link (node:internal/modules/esm/module_job:86:36) {
  code: 'ERR_MODULE_NOT_FOUND',
  page: '/'
}

Local node version: 22.2.0
Vercel node version: 20.x
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
The Issue comes on vercel only
Expected behavior
Should run without the app crashing
Screenshots or Videos
No response
Operating System Version
MacOs
Browser
Chrome

Seems like this issue on NextJs
kindly follow these steps -

Try to resolve all warnings
Run npm run lint on the local environment, and check for errors
Set env variable CI = false and run npm ci --include=dev,    CI = true considers warnings as errors

See if the error stills persists.
Kindly follow the above steps and confirm again

@abhinandan-verma Thanks for the quick response,

I have cleared all errors and warnings, currentlynpm run lint shows no errors or warnings
Which environment should i run npm ci --include=dev because locally the app runs fine until i push it to vercel.

@KundwaBruno  you should run it remotely, observe the changes (if any).
Confirm if you still have the issue.

Okay, kindly guide me where to add this @abhinandan-verma

@KundwaBruno  for your help, I deployed a test app with Calendar component on Vercel, and  deployment was successful. Maybe you are having some configuration or dependency conflict issue.
here is app and repo link
repo
app
I will recommend, compare the configurations with your own app with mine one , update your  dependencies. Hopefully you should get your issue resolved.

@KundwaBruno  are you still facing the same issue?
did you compare the configuration and dependencies?
Kindly confirm

Now i just got another one after i updated my dependency version to the ones in your repo.
⨯ Error: Cannot find package '/var/task/node_modules/<EMAIL_ADDRESS>imported from /var/task/node_modules/<EMAIL_ADDRESS>Did you mean to import<EMAIL_ADDRESS>    at legacyMainResolve (node:internal/modules/esm/resolve:219:26)
    at packageResolve (node:internal/modules/esm/resolve:845:14)
    at moduleResolve (node:internal/modules/esm/resolve:931:18)
    at moduleResolveWithNodePath (node:internal/modules/esm/resolve:1173:14)
    at defaultResolve (node:internal/modules/esm/resolve:1216:79)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39)
    at link (node:internal/modules/esm/module_job:86:36) {
  code: 'ERR_MODULE_NOT_FOUND',
  page: '/'
}

I'm use the pages router tho
@abhinandan-verma

@abhinandan-verma You still there?

@KundwaBruno please share a minimal reproducible environment.

@wingkwong I reverted back to version 2.4.10 os nextui/react and it worked, not sure if it's issue within next-ui itself

Closing - not able to reproduce.

I'm having the exact same issue, also just on Vercel and while using Pages router.

Having the same issue with Vercel and Remix

I faced the same issue with the following stack :

Nextjs 14.2.14
@nextui-org/react 2.4.8

Local and remote build works correctly, no any warn or errors.
I'm using the page router.
I don't use the Calendar component in my project.
It causes my app crashes on Vercel :
⨯ Error: Cannot find package '/var/task/node_modules/@nextui-org/calendar/node_modules/<EMAIL_ADDRESS>imported from /var/task/node_modules/@nextui-org/calendar/node_modules/<EMAIL_ADDRESS>Did you mean to import<EMAIL_ADDRESS>at legacyMainResolve (node:internal/modules/esm/resolve:219:26) at packageResolve (node:internal/modules/esm/resolve:845:14) at moduleResolve (node:internal/modules/esm/resolve:931:18) at moduleResolveWithNodePath (node:internal/modules/esm/resolve:1173:14) at defaultResolve (node:internal/modules/esm/resolve:1216:79) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:540:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:509:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:239:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:96:40) at link (node:internal/modules/esm/module_job:95:36) { code: 'ERR_MODULE_NOT_FOUND', page: '/features' }
Oct 06 09:42:47.73
GET
Node.js process exited with exit status: 1. The logs above can help with debugging the issue.

I have the same behaviour for date-picker component :
⨯ Error: Cannot find package '/var/task/node_modules/@nextui-org/date-picker/node_modules/<EMAIL_ADDRESS>imported from /var/task/node_modules/@nextui-org/date-picker/node_modules/<EMAIL_ADDRESS>I downgraded @nextui-org/react to 2.3.6, and everything works as expected.

This happened to me on Vercel, not being able to import /node_modules/@nextui-org/card/node_modules/<EMAIL_ADDRESS>in my case.
I just made an upgrade from 2.2.9 to 2.4.8.

Seems like we need to dynamically import the specific NextUI component responsible for the issue ( whether calendar input or date picker input and set ssr: false ). This ensures the component is only rendered on the client side, avoiding potential server-side rendering conflicts that may cause the crash. However I think this should be a temporary work around


Save colors/Set As Wallpaper: ERR_INVALID_RESPONSE

Versions:

Google Chrome 65.0.3325.18 (Official build), dev (64 бит)
Windows 10 1709 (build 16299.64)

After selecting "Colors -> Save Colors" from the menu:

After selecting "File -> Set As Wallpaper (*)" from the menu:

Devtools:

@saber-nyan Is this still a problem?

Nope, it works now.


Update settings for targets entry, output and devServer

What does this PR do?
Paths and Output refactor
Instead of having a global setting for the output paths (paths.output), the option has been moved to the targets themselves:
 {
   paths: {
     source: 'src',
     build: 'dist',
     privateModules: 'private',
-    output: { ... }
   },
   targetsTemplates: {
     node: {
       ...,
+      output: {
+        default: '[target-name].js',
+        development: null,
+        production: null,
+      },
       ...,
     },
     browser: {
       ...,
+      output: {
+        default: {
+          js: 'statics/js/[target-name].[hash].js',
+          fonts: 'statics/fonts/[name].[hash].[ext]',
+          css: 'statics/styles/[target-name].[hash].css',
+          images: 'statics/images/[name].[hash].[ext]',
+        },
+        development: {
+          js: 'statics/js/[target-name].js',
+          fonts: 'statics/fonts/[name].[ext]',
+          css: 'statics/styles/[target-name].css',
+          images: 'statics/images/[name].[ext]',
+        },
+        production: null,
+      },
       ...,
     },
   }
 }

This allows more control when working with multiple targets.
They new options come with a default "environment key" so you don't have to repeat everything when you want to use the same settings no matter the environment.
You can use the following placeholders when building a path:

[target-name]: The name of the target.
[hash]: A random hash generated for cache busting.
[name]: The file original name (Only available on browser paths for images and fonts).
[ext]: The file original extension (Only available on browser paths for images and fonts).

Target's entry default option
Both types of targets now have a entry.default option that works as a fallback if an entry file is not defined for an environment.
Also, both targets types entry setting defaults now looks like this:
entry: {
  default: 'index.js',
  development: null,
  production: null,
}

So, for browser targets that don't have its entry modified, this is not a breaking, for Node targets it is, as they previously had start.development.js and start.production.js.
Browser targets html new default option.
Similar to the change to the targets types entry setting, the default html settings of a browser target now look like this:
{
  default: 'index.html',
  template: null,
  filename: null,
}

If you are using the same value for both and need to change it from index.html, you now can do it by modifying only one setting.
Browser targets dev server new options
host and https have been added to .devServer in case you want to specify a different host, that may or may not run on https for the target:
 devServer: {
   port: 2509,
   reload: true,
+  host: 'localhost',
+  https: false,
 }

If you are wondering about adding certificates, well, that will come soon. For now https only affects the host URI.

How should it be tested manually?
yarn test
# or
npm test

Pull Request Test Coverage Report for Build 10

18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 9:
0.0%

Covered Lines:
898

Relevant Lines:
898

💛  - Coveralls

☠


Add bitorder option to cupy.packbits

This PR addresses this issue.

pfnCI, test this please.

pfnCI, test this please.

Jenkins CI test (for commit 61ab2b20dd086650e5b1bca9cf690ec01c7414e3, target branch master) succeeded!


Touchpad broken

Hello, I installed BigSur with this repo successfully on my HP EliteBook 840 G4 but I get an issue: in recovery the touchpad worked perfectly then, after installing and several reboots, it has stopped working.
There's a solution for this?
Thanks!

Hey, I apologize for the late response.
Please check the order of all the Voodoo kexts in the config.plist file. Make sure to update the kexts to the latest version too.


Boolean protocol Commands

Hello there!
I actually don't know if this is the right way of reaching you about the development of the project, but here we go.
I know it sounds odd but, wouldn't be better if commands like EchoOffCommand HeadersOffCommand and LineFeedOffCommand had a possibility of re-enabling them?
I know that for most of the projects you just want to shut them all but what if some person (like me, but just for a tiny toy app) wanted to reactivate them?
It would be usefull if in the constructor you could send a boolean telling to go on/off.
As this is normally done in the setup it is usually just one line that would change and if you want it back again you just issue it.
What I am trying to say is that it probably wouldn't change much, but would allow the other way arround (i.e. EchoOnCommand) without creating a new class.
I would be honored to contribute with it, if agreed.
Cheers.

Hi @malvadeza. It's an interesting idea but unfortunately it would mean an API break. That said, you can open PRs for adding {Echo,Line,Headers,etc.}OnCommand. I'd be glad to review them.


Initial structure of the sponsor page

@cmaureir It's so great to see this coming together. Thank you 💯


Enable react-docgen

Build React component doc with https://github.com/reactjs/react-docgen as a part of yarn build and publish them in developer-guide.
~~Could it be integrated into storybook contents? do it together with #2896 then.
https://storybook.js.org/addons/storybook-addon-react-docgen~~
It says

React Docgen is included as part of the @storybook/addon-docs package. If you are using @storybook/addon-docs then you do not need to set up docgen

so it might be already integrated.

Docs tab is the one


chore(ci): Remove spammy logs from ts-integration

What ❔

Removes spammy logs that make ts-integration output unreadable in CI.
Enables debug reported in tests ran via zk_toolbox.

Why ❔

These logs were useful, but something was poorly ported during migration to ethers v6 and it became a spam machine.
Other debug logs are very useful however.

Checklist

[ ] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.
[ ] Code has been formatted via zk fmt and zk lint.

Closed in favor of #2848


duk cores at start with segfault on FreeBSD 11.1-RELEASE

Compiled 2.1.1 on
FreeBSD mika-ion 11.1-RELEASE-p1 FreeBSD 11.1-RELEASE-p1 #0: Wed Aug  9 11:17:49 UTC 2017     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386

with
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0)
Target: i386-unknown-freebsd11.1
Thread model: posix
InstalledDir: /usr/bin

duk core immediately at start with
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)...
Core was generated by `./duk -i'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.5
Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done.
Loaded symbols for /libexec/ld-elf.so.1
#0  0x0804c10d in duk_pop_n ()
(gdb) where
#0  0x0804c10d in duk_pop_n ()
#1  0x0805bc0e in duk__parse_stmts ()
#2  0x0805cbdc in duk__parse_stmt ()
#3  0x0805c945 in duk__parse_stmt ()
#4  0x0805bbe6 in duk__parse_stmts ()
#5  0x080582c8 in duk__parse_func_body ()
#6  0x080581bc in duk__parse_func_like_raw ()
#7  0x0805da67 in duk__parse_func_like_fnum ()
#8  0x0805f108 in duk ()
#9  0x0805f150 in duk ()
#10 0x0805ddb5 in duk__exprtop ()
#11 0x00000035 in ?? ()
#12 0x0805bdaa in duk__parse_stmt ()
#13 0x0805bbe6 in duk__parse_stmts ()
#14 0x080582c8 in duk__parse_func_body ()
#15 0x08057ea9 in duk__js_compile_raw ()
#16 0x0804a739 in duk_handle_safe_call ()
#17 0x0804a537 in duk_safe_call ()
#18 0x00000001 in ?? ()
#19 0x00000001 in ?? ()
#20 0x28629000 in ?? ()
#21 0x080578e0 in duk_js_compile ()
#22 0x0804bd9c in duk__do_compile ()
#23 0x0804bcae in duk_compile_raw ()
#24 0x0804bc0f in duk_eval_raw ()
#25 0x0807a8df in create_duktape_heap ()
#26 0x00000001 in ?? ()

Could you try what happens with -DDUK_USE_SELF_TESTS and -DDUK_USE_ASSERTIONS (given to configure.py) enabled?

There was an earlier FreeBSD m32 issue which is documented here: https://github.com/svaarala/duktape/blob/master/misc/clang_aliasing.c. The output from that test might also be useful.

One thing that pops up also is that duk_create_heap() should not call duk_eval_raw() at any stage in Duktape 2.1.1. Is it possible header/source files are somehow mixed from different versions?

Done, hopefully I did the right thing here:
[mosipov@mika-ion ~/Projekte/duktape-2.1.1]$ python2.7 tools/configure.py --output-directory /tmp/output --source-directory src-input --config-metadata config  -DDUK_USE_SELF_TESTS -DDUK_USE_ASSERTIONS
$ mv /tmp/output ~/Projekte/duktape-2.1.1/src-freebsd
$ make -f Makefile.cmdline
cc -o duk  -Os -pedantic -std=c99 -Wall -fstrict-aliasing -fomit-frame-pointer -I./src-freebsd -DDUK_CMDLINE_PRINTALERT_SUPPORT -I./extras/print-alert -DDUK_CMDLINE_CONSOLE_SUPPORT -I./extras/console -DDUK_CMDLINE_LOGGING_SUPPORT -I./extras/logging -DDUK_CMDLINE_MODULE_SUPPORT -I./extras/module-duktape src-freebsd/duktape.c examples/cmdline/duk_cmdline.c extras/print-alert/duk_print_alert.c extras/console/duk_console.c extras/logging/duk_logging.c extras/module-duktape/duk_module_duktape.c -lm
$ ./duk
*** FATAL ERROR: self test(s) failed
Causing intentional segfault...
Segmentation fault (Speicherabzug geschrieben)
[mosipov@mika-ion ~/Projekte/duktape-2.1.1]$ gdb ./duk ./duk.core
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols found)...
Core was generated by `./duk'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.5
Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done.
Loaded symbols for /libexec/ld-elf.so.1
#0  0x0808f5dd in cmdline_fatal_handler ()
(gdb) where
#0  0x0808f5dd in cmdline_fatal_handler ()
#1  0x0804e5a8 in duk_create_heap ()
#2  0x0808f2ba in create_duktape_heap ()
#3  0x00000000 in ?? ()
(gdb)

One more thing worth checking out is that the Duktape source and header files are an exact match. Sometimes if a -I... is missing for duktape.h one may accidentally use a system-installed duktape.h for a different version than the duktape.c being compiled (been there done that).
With debug symbols it would also be nice to see what duk_eval() call is causing the segfault. If there's something obviously wrong, like the packed duk_tval not working due to the aliasing issue, it's most likely the first one.
If the aliasing issue is at fault, -UDUK_USE_PACKED_TVAL (given to configure.py) would help.

Ok, that self test failure means all bets are off - it's most likely the clang aliasing issue mentioned above, so you could try -UDUK_USE_PACKED_TVAL (given to configure.py) and see what happens.

Unsetting DUK_USE_PACKED_TVAL did indeed work:
[mosipov@mika-ion ~/Projekte/duktape-2.1.1]$ ./duk
((o) Duktape 2.1.1 (external)
duk> print("hellp");
hellp
= undefined
duk> alert("toll");
toll
= undefined
duk> new Date();
= "2017-09-22T22:01:43.030Z"
duk> quit
ReferenceError: identifier 'quit' undefined
    at [anon] (src-freebsd/duktape.c:78145) internal
    at global (input:1) preventsyield
duk> = undefined
Cleaning up...

I will retry with Clang 5.0 from ports. Currently, the Duktape FreeBSD port is broken due to this which I need for Gerbera.
Does this issue imply that libduktape.so will also if I do not regenerate with configure.py?

Assuming you're trying to do a system-wide install:

You should run configure.py which generates duk_config.h, duktape.h, and duktape.c.
The libduktape.so library should be compiled from these sources.
The system headers must include the duktape.h and duk_config.h created by configure.py.

After that, the -UDUK_USE_PACKED_TVAL takes effect for any application built and linked against libduktape.so -- provided it is compiled with the correct, matching headers.

If you're not doing a system-wide install, what matters is that any application code calling into libduktape.so is compiled with the exact same headers as the library itself, i.e. the same set of duk_config.h, duktape.c, duktape.h which is written by configure.py.

I will retry with Clang 5.0 from ports. Currently, the Duktape FreeBSD port is broken due to this which I need for Gerbera.

It'll be interesting to hear if this fixes the issue. So far this issue has only happened on FreeBSD, with -m32. Linux Clang with -m32 is fine for example. The aliasing issue (see the link) is quite bizarre, to me it seems like an incorrect optimization. In short, a union with just an 8-byte array works, but if you add a double into the union, even when it is not referenced at all, union assignment copy starts failing because it compiles into a floating point store (even when the double field is not explicitly referenced at all).

I currently do not have a system-wide install because I need to make things run first. libduktape.so is passed directly to Gerbera's CMake build. I'll see how far I get with 5.0 and will also install 6.0-dev. This might be worth reporting either to LLVM or FreeBSD itself. I'll get back to you tomorrow.

I've already reported it in 2013: http://lists.llvm.org/pipermail/cfe-users/2013-December/000321.html.

Still worth reporting it to bugs.freebsd.org.

So, I have now clang from base (4.0.0) and 4.0.1 + 5.0.0 from ports:
[mosipov@mika-ion ~/Projekte/duktape/misc]$ clang -Os -m32  -std=c99 -fstrict-aliasing -fomit-frame-pointer clang_aliasing.c
[mosipov@mika-ion ~/Projekte/duktape/misc]$ ./a.out
11 22 33 44 00 00 f1 ff
11 22 33 44 00 00 f9 ff
11 22 33 44 00 00 f9 ff
11 22 33 44 00 00 f1 ff
[mosipov@mika-ion ~/Projekte/duktape/misc]$ clang -Os -m32  -std=c99 -fstrict-aliasing -fomit-frame-pointer clang_aliasing.c
[mosipov@mika-ion ~/Projekte/duktape/misc]$ ./a.out
11 22 33 44 00 00 f1 ff
11 22 33 44 00 00 f9 ff
11 22 33 44 00 00 f9 ff
11 22 33 44 00 00 f1 ff
[mosipov@mika-ion ~/Projekte/duktape/misc]$ clang40 -Os -m32  -std=c99 -fstrict-aliasing -fomit-frame-pointer clang_aliasing.c
[mosipov@mika-ion ~/Projekte/duktape/misc]$ ./a.out
11 22 33 44 00 00 f1 ff
11 22 33 44 00 00 f9 ff
11 22 33 44 00 00 f9 ff
11 22 33 44 00 00 f1 ff
[mosipov@mika-ion ~/Projekte/duktape/misc]$ clang50 -Os -m32  -std=c99 -fstrict-aliasing -fomit-frame-pointer clang_aliasing.c
[mosipov@mika-ion ~/Projekte/duktape/misc]$ ./a.out
11 22 33 44 00 00 f1 ff
11 22 33 44 00 00 f1 ff
11 22 33 44 00 00 f1 ff
11 22 33 44 00 00 f1 ff

I will report this against FreeBSD base.

Can you please update the wiki for clang 4.0.1 and 5.0.0?

Ok, I'll open a pull for it.

https://github.com/svaarala/duktape-wiki/pull/189

@svaarala  I think this is the issue and the fix for it. WDYT?

Looks very likely, I'll link to these to explain the cause a bit more.
Any suggestions if Duktape could do something to (a) reliably detect the issue or (b) work around it?
For (a), disabling packed duk_tval for Clang prior to 5.0 (or whatever the exact version is) seems quite wrong, because this issue does not appear on e.g. Linux clang prior to 5.0 (even with -m32). I'm not sure why, but maybe there's something in the way the compiler is configured/built. So one would ideally want something more precise.
Maybe "FreeBSD && clang < 5.0 && x86" would be a good check? It would mean more memory usage (because duk_tval will be larger) until clang 5.0 but it seems better than a broken build which is detected by self checks only. There's no guarantee the issue wouldn't appear elsewhere too, but this narrow case at least seems broken.
For (b), I don't have a good idea of how to work around it reliably.

According to the bug report linked above compiling with-fno-strict-aliasing works around the bug.

@fatcerberus It does, but duk_config.h has no reasonable way of detecting whether strict aliasing is used or not?

So what I'm mainly after, how to work around the issue so that the build comes our working without going through segfaults and diagnosis. I would be happy with an #error for FreeBSD + clang < 5.0 + m32 + -fstrict-aliasing, but I don't one can detect that.

#1764 is a possible automatic workaround.

-fno-strict-aliasing  does not seem to work:
[mosipov@mika-ion ~/Projekte/duktape-2.1.1]$ make -f Makefile.cmdline
cc -o duk  -fno-strict-aliasing -Os -pedantic -std=c99 -Wall -fomit-frame-pointer -I./src -DDUK_CMDLINE_PRINTALERT_SUPPORT -I./extras/print-alert -DDUK_CMDLINE_CONSOLE_SUPPORT -I./extras/console -DDUK_CMDLINE_LOGGING_SUPPORT -I./extras/logging -DDUK_CMDLINE_MODULE_SUPPORT -I./extras/module-duktape -DDUK_CMDLINE_FANCY -I./linenoise src/duktape.c examples/cmdline/duk_cmdline.c extras/print-alert/duk_print_alert.c extras/console/duk_console.c extras/logging/duk_logging.c extras/module-duktape/duk_module_duktape.c linenoise/linenoise.c -lm
linenoise/linenoise.c:568:27: warning: must specify at least one argument for '...'
      parameter of variadic macro [-Wgnu-zero-variadic-macro-arguments]
        lndebug("clear+up");
                          ^
linenoise/linenoise.c:195:9: note: macro 'lndebug' defined here
#define lndebug(fmt, ...)
        ^
linenoise/linenoise.c:574:20: warning: must specify at least one argument for '...'
      parameter of variadic macro [-Wgnu-zero-variadic-macro-arguments]
    lndebug("clear");
                   ^
linenoise/linenoise.c:195:9: note: macro 'lndebug' defined here
#define lndebug(fmt, ...)
        ^
linenoise/linenoise.c:591:28: warning: must specify at least one argument for '...'
      parameter of variadic macro [-Wgnu-zero-variadic-macro-arguments]
        lndebug("<newline>");
                           ^
linenoise/linenoise.c:195:9: note: macro 'lndebug' defined here
#define lndebug(fmt, ...)
        ^
linenoise/linenoise.c:619:17: warning: must specify at least one argument for '...'
      parameter of variadic macro [-Wgnu-zero-variadic-macro-arguments]
    lndebug("\n");
                ^
linenoise/linenoise.c:195:9: note: macro 'lndebug' defined here
#define lndebug(fmt, ...)
        ^
4 warnings generated.
[mosipov@mika-ion ~/Projekte/duktape-2.1.1]$ ./duk
Segmentation fault (Speicherabzug geschrieben)

I will try #1764.

Here is the report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222551

It might be that the root cause is not, after all, correct if the suggested workaround doesn't work.

Feel free to close this issue as it has been decently resolved. Thank you for the precious input. The FreeBSD bug report gained some traction and instruction what to do: use the port.

@michael-o Ok, thanks for taking the time to run all these tests :)


Audio play automatically when the track is loaded to the stream.

Hi,
when the WebRTC connection is active between the peer and the application in C#. I load the trace coming from the peer and insert it in the PeerConnection, the audio plays automatically from my application. Is there any way to control this playback? Stop playback and resume it whenever you want?
Thanks everyone.

When adding the trace to the app's conncectionPeer:
connection.TrackAdded += delegate (RtpReceiver rtpReceiver)
            {
                log.Info("Track Added proveniente dal PEER remoto");
                MediaStreamTrack mediaStreamTrack = rtpReceiver.Track;
                AudioTrack audioTrack = (AudioTrack)mediaStreamTrack;

The following instruction must also be performed:
audioTrack.Enabled = false;
This instruction disables application-side audio playback in C #


Merge UI Enhancements into Develop Branch

Summary

Enhanced UI components and styling across the application.
Improved responsiveness and fixed layout issues.
Updated components include Header, Footer, JobCard, and others.

This merge integrates the latest UI updates and fixes into the develop branch.

Merged UI enhancements into the develop branch.
Updated components for better functionality and routing.
Fixed image paths and adjusted styling for consistency.


Adds outline and selective bloom

I will add the example to the PR, to see it works as it should :D

I synced this branch with yarn add https://github.com/react-spring/react-postprocessing.git/#adds-select-effects to test the outline effect and found selection not updating on mouse over. My legacy effects chain from three/examples works with the same code so something might be wrong here.


Change Simplelayout.ToString - skip additional quotes

Fixes https://github.com/NLog/NLog/issues/817

interesting concequence:
[xUnit.net 00:00:28.39]     NLog.UnitTests.Config.RuleConfigurationTests.FiltersTest [FAIL]
[xUnit.net 00:00:28.39]       Assert.Equal() Failure
[xUnit.net 00:00:28.39]                                        ↓ (pos 21)
[xUnit.net 00:00:28.39]       Expected: ···tarts-with(message, 'x')
[xUnit.net 00:00:28.39]       Actual:   ···tarts-with(message, x)
[xUnit.net 00:00:28.39]                                        ↑ (pos 21)
[xUnit.net 00:00:28.39]       Stack Trace:
need to fix that.

Codecov Report

Merging #3361 into dev will increase coverage by 1%.
The diff coverage is 36%.

@@          Coverage Diff           @@
##             dev   #3361    +/-   ##
======================================
+ Coverage     80%     81%    +1%
======================================
  Files        356     344    -12
  Lines      28205   27546   -659
  Branches    3750    3700    -50
======================================
- Hits       22588   22246   -342
+ Misses      4535    4227   -308
+ Partials    1082    1073     -9


Prohibit usage of vni zero

I mean the apiserver can also do that enforcement with a block directly
https://kubernetes.io/blog/2022/09/23/crd-validation-rules-beta/
Marcel Fest @.***> schrieb am Fr., 15. März 2024, 21:12:

@.**** commented on this pull request.
In pkg/reconciler/layer3.go
https://github.com/telekom/das-schiff-network-operator/pull/105#discussion_r1526786710
:

@@ -165,6 +165,12 @@ func (r *reconcile) createVrfConfigMap(l3vnis []networkv1alpha1.VRFRouteConfigur
continue
}

if vni == 0 {

Should we not do a boundary check here?
vni <= 0 and vni >= max_vni
—
Reply to this email directly, view it on GitHub
https://github.com/telekom/das-schiff-network-operator/pull/105#pullrequestreview-1940447964,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFLAD22GOK7BSODM5QRWI3YYNIZBAVCNFSM6AAAAABEX2L2Y2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSNBQGQ2DOOJWGQ
.
You are receiving this because your review was requested.Message ID:
@.***
com>

@MaxRink only for the CRD ^^ the ConfigMap needs validation as well :)

Make the ConfigMap an CRD :P
Am Sa., 16. März 2024 um 11:25 Uhr schrieb Marcel Fest <
@.***>:

@MaxRink https://github.com/MaxRink only for the CRD ^^ the ConfigMap
needs validation as well :)
—
Reply to this email directly, view it on GitHub
https://github.com/telekom/das-schiff-network-operator/pull/105#issuecomment-2001941100,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFLADZ3X24XDPOLX3HV2GLYYQMXTAVCNFSM6AAAAABEX2L2Y2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBRHE2DCMJQGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Long dataplane apply times in route table apply

Expected Behavior

We've been investigating some high Dataplane Apply times to see what's going on.
Our environment have an average of 600 PODs per node. We've being trying to improve performance and make this possible, even it not being recommended ;)
The Dataplane apply time takes an average of 0.5s, but in some very specific times it takes more than 15s.
Making some digging and brakepointing into the code, we've faced that while applying the dataplane the routine that takes more time is this
When digging more into this function, we've faced that the following part of the code, WHEN CALLED takes that huge amount of time.
What we mean by WHEN? Because this seems an interaction. Sometimes there's no Item to interact and then this piece of code is not called.
But when it's called, the whole array of the iteration calls the r.syncRoutesForLink(ifaceName) (and all of them with success).
While each call per interface of syncRoutesForLink takes an average of 26ms and a maximum of 113ms, the sum of the times for 400 interfaces is something like 15000ms (15s!).
The question/suggestion of improvement here is:

Couldn't those syncRoutesForLink be not serial, but instead run concurrently to drop those requests from 15s to a maximum of 115ms?

I couldn't figure out why all interfaces got a syncRoutesForLink instead of only the changed interface (I may be missing something, sorry :( )

It seems, btw that this routes WG does not block IPTables (https://github.com/projectcalico/felix/blob/release-v3.6/dataplane/linux/int_dataplane.go#L936,L949) or anything like that, so it doesn't impact into the rest of dataplane update.
So may this represent a performance issue or this can be treated just as an improvement?
Your Environment

And/Or, calico/node container version (if running Felix in a container): 3.6.4
Which orchestrator are you using (e.g. Kubernetes, OpenStack, Docker, Mesos): Kubernetes
Orchestrator version (if used): 1.13.4
Etcd version (if using etcd datastore driver): 3.3
Operating System and version: CoreOS 2079.6.0

@rikatz Are you still working with Calico and nodes with many pods?  Think we might finally have a fix for this one: https://github.com/projectcalico/calico/pull/7364.  The kernel API and the netlink library now have support for kernel-side filtering, which is what we need to make our queries fast.

Hey @fasaxc I have changed company almost 2y ago and don't have access to cluster anymore :/
@gunboe  do you still have this access and the problem?

@moacirsouza

Hey there @fasaxc. We still have this Cluster running, but it is now in a "frozen" state regarding updates and patches. We've been trying to modify our Clusters infrastructure in favour of smaller, more controlled ones and the upper management don't really want to risk possible disruptive changes until the migration of the major clients end.
I guess we could still try this in our staging environment, which is considerably smaller but still able to work with 400 to 600 pods per node.
@gunboe: We could schedule some testing sessions next week, perhaps?
And thanks for the heads up @jcmoraisjr and @rikatz. Miss you guys 😞

@moacirsouza Here's the nightly build with the fix: https://2023-02-23-master-sudoku.docs.eng.tigera.net/  (Just grab a manifest with the name that you'd usually use from the manifests directory instead of from the docs.)


Add autocommit feature to let dbt users run certain db commands in macros

resolves #425
An imperfect but what I think is a necessary solution.
Description of solution
Root cause: Connection objects used in Python must have autocommit = True to run the .
But, this is a Python-level thing we need to alter. The docs I linked above have this snippet.

Yep, this is official guidance. So, we have to alter the connection in the Python post hoc instead of altering the connection instantiation function.
All together -- if we make it an opt-in config for users, we could direct them to define a separate target with autocommit=True. This isn't great but it was straightforward enough for me to get 1.5 users unblocked within the sprint!
Pros of this solution
Let users configure this behavior on their connection profiles.

no need for a massive threading rewrite which would be way out of scope of the issue (unblocking users faster)
finessed opt-in despite the code being kind of blunt ("do this on all connections")
let users configure on the profile (no env var memorization required for CLI)

The Alternatives Turned Down

Forbid users entirely from using these commands. Disservice to the user as they worked fine prior to 1.5
Stop using the Redshift connector. Goes way against our current partner/design philosophy
Enable autocommit for all connections. Not a great idea: Doing so invites performance hits, data inconsistency faults, no ACID across multiple statements, etc.
Have dbt silently flip this option on or off for these commands. My original hope unrealized; requires rewrite of connection contexts.
Okay, then fine. Let's rewrite our connection context code to alter connections based on whatever SQL they're running. There is no easy way to alter a thread based on what SQL is handed it (thanks Gerda for corroborating that 🙏 ). Neither is this the case for core nor Redshift.

Fix/feature add screenshots to illustrate impact
With this option autocommit: False in profile:

With this option autocommit: True in profile:

How to use this
1
Define all macros in a folder with the "autocommit enabled" target

2
Swap the target on the command line: --profile TEXT # Which profile to load. This method is useful for adhoc/scheduled Cloud jobs 💃
Followup
1.5 Backport
Checklist

[X] I have read the contributing guide and understand what's expected of me
[X] I have signed the CLA
[X] I have run this code in development and it appears to resolve the stated issue
[X] This PR includes tests, or tests are not required/relevant for this PR
[X] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[X] I have run changie new to create a changelog entry

Hey @dbeatty10 !

Would the default behavior in dbt-redshift 1.5 be the same as dbt-redshift 1.4 or would it be different? Different but forced by the "flags should default to false" constraint. In 1.4, you didn't need to specify this anywhere, but now we need to set it.
Do we know why things worked with psychopg2 but not redshift_connector? No 😕 The RS connector isn't exhaustively documented. Moreover
What would end users need to do to enable this? Something like this? You got it!
profile-to-my-RS-target-with-autocommit-enabled:
target: dev
outputs:
dev:
type: redshift
...
autocommit: True


Reduce some calls to re.sub

So calls to re.compile are not a problem. The main thing slowing it down is lots of calls to re.sub in abbreviation_replacer.py. I reduced some of these calls which speeds it up by a factor of ~3-3.5x on my machine, for the specific (longish) document that I tested with. I also included the script I used to test timing. Given that you are much more familiar with the codebase, see if my changes look reasonable, but all the tests do still pass. There are probably some more ways to speed up the calls in that file.

LGTM! Yes, I concur there are a lot of inefficient loops and calls happening in abbreviation_replacer.py. Since I was porting it from ruby, I thought of keeping the same loops and calls in python to get tests to pass. In a few cases, I tried to be idiomatic wherever possible, but still, there are a lot of places where we can surely improve pysbd.
It would be nice if you could list those speed up calls in the comment here so we can tackle them one by one.

I was focusing on the parts that were the majority of the time spent. Figured no need to optimize parts that weren't taking up much of the time. Here is some of the output from cProfile:
   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1    0.000    0.000    1.484    1.484 <string>:1(<module>)
      366    0.003    0.000    0.258    0.001 abbreviation_replacer.py:10(replace_pre_number_abbr)
     1492    0.004    0.000    1.145    0.001 abbreviation_replacer.py:103(scan_for_replacements)
      222    0.002    0.000    0.157    0.001 abbreviation_replacer.py:19(replace_prepositive_abbr)
      904    0.007    0.000    0.726    0.001 abbreviation_replacer.py:28(replace_period_of_abbr)
        1    0.000    0.000    0.013    0.013 abbreviation_replacer.py:43(replace_abbreviation_as_sentence_boundary)
        1    0.000    0.000    0.000    0.000 abbreviation_replacer.py:54(__init__)
        1    0.000    0.000    1.400    1.400 abbreviation_replacer.py:58(replace)
        1    0.000    0.000    0.001    0.001 abbreviation_replacer.py:70(replace_multi_period_abbreviations)
        4    0.000    0.000    0.000    0.000 abbreviation_replacer.py:71(mpa_replace)
        1    0.005    0.005    1.380    1.380 abbreviation_replacer.py:83(search_for_abbreviations_in_string)

Didn't want to cause code churn/potentially introduce bugs by over optimizing other pieces of code. I also don't actually have clear ideas at the moment for how to make those slow pieces even faster.

Any hesitation on releasing this as is?

Although, I wanted to make more optimizations in abbreviation_replacer.py but didn't find much time to do it thoroughly so releasing it for now and we can do further optimizations in the future.
Just to segregate scripts as per purpose, moving your test_timing_script.py to examples for further reference.


fix(#3800): Add proper kamel linux binary on MacOS

Try to fix Makefile syntax

@oscerd sorry, I have screwed up the Makefile. Let's see if this is better and the CI jobs are happy

This fix definitely works better on Linux.

@gansheer yes, but now it is not working on MacOS anymore 😵 I have to investigate

@gansheer yes, but now it is not working on MacOS anymore dizzy_face I have to investigate

We could also revert and find a better solution. The fix was done only for MacOS.

@gansheer yes, but now it is not working on MacOS anymore dizzy_face I have to investigate

We could also revert and find a better solution. The fix was done only for MacOS.

That seems to be a sensible approach since the main branch no longer build images on non MacOS Linux.

@oscerd @gansheer now I am sorted. I did not know that Makefile is so fuzzy about tabs vs. spaces
It should be fixed now (at least it is working on my MacOS again). Let's see what the CI jobs do report

I think it's fine if we merge. This stuff is only for building, so no need to wait for common/install and knative.

Thanks for the fast fix.


Add some stuff to X and Y

thanks for the PR, looks good! Don't forget to follow https://twitter.com/NextBigThingBot


update to 0.15

removed diagnostics since it doesnt support 0.15 yet, only got the static example to work so far (lazy)


feat(Dropdown): Enable custom DropdownItem render

Fixes #852
See the linked issue and also this comment for relevant discussion: https://github.com/Semantic-Org/Semantic-UI-React/pull/682#discussion_r84160476
In the SUI-core dropdown, you can pass both the text and name props for each option.

text - the text that gets rendered within the closed Dropdown when that option is selected
name - the text that gets rendered for a given option within the dropdown menu.

If no name is provided, text is used for both. See the second example ("Trending Repos") for an example of the distinction: http://semantic-ui.com/modules/dropdown.html#inline. Notice how within the dropdown the options are title-cased whereas when you select an option it is rendered lowercased:

This PR implements what essentially is the name prop, although I named it content to fit into the pattern established throughout the rest of the repo. It's shorthand that takes the place of children and is rendered alongside the other shorthand props (icon, flag, etc) if given.
This isn't a breaking change since the text prop is used if the content prop is missing.

Cool, this looks great.  The only thing I think we should change is the prop name content.  The DropdownItem text prop will become content before we hit v1 for consistency with all other components, it is just left over from before we standardized.
Looking at SUI core, they use data-text="" for the value rendered in the Dropdown when selected.  I think this makes perfect sense given that the Dropdown prop for the same value space is text.  It then stands to reason that the Dropdown text is set by the DropdownItem text.  Whereas, content is always the primary content of the component, in this case, the content of the DropdownItem (which only appears in the Menu).
I believe this means we ought to reverse the two props, correct?

One alternative would be to add renderText to the Dropdown and pass it the currently active DropdownItem props.  This deviates from SUI core a bit, but extends the renderLabel idea.  Depending on the majority use case, one of these (renderText vs DropdownItem text prop) will be better for users I would assume.

It then stands to reason that the Dropdown text is set by the DropdownItem text. Whereas, content is always the primary content of the component, in this case, the content of the DropdownItem (which only appears in the Menu).

I think that's right but aligns naming that's currently in the PR. Here's an example of SUI core dropdown: http://codepen.io/jeffcarbs/pen/dOXvmQ

Male-name-content

male-text === text prop === value rendered in the Dropdown when selected
Male-name-content === name|content prop === content of the DropdownItem.

I'd advocate for the content prop since it aligns with the pattern we've established throughout the app of content being shorthand for primary content of a component and it more close maps to SUI-core. If there's interest for a renderText prop I think we can consider adding it later on.

Thanks for the clarification, I was reading the DropdownExampleItemContent backwards, thinking the it was showing the Header as the rendered text (which is content).

Released in<EMAIL_ADDRESS>


Implement ConfigurableByClientsObject on AsyncBaseClient class

Mimic the behaviour of what is done for a BaseClient in the existing sync type-driven Clients class

Work in progress now


Use custom css properties on terminal font render ( webkit-font-smoothing )

[x] I am on the latest Hyper.app version

[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: macOS 10.13.3

Hyper.app version: 2.0.0

Link of a Gist with the contents of your .hyper.js: https://gist.github.com/alxtz/a103d33851cb97c501a65b567feb6cb9

Issue
In pre 2.0.0 of hyper.js, I'm able to customize the css props of the fonts in hyper.
One of my favorite, is to use -webkit-font-smoothing to make the font display more smooth.
Before

After

In 2.0.0

In 2.0.0, I believe all the x-row based css is deprecated, since the term windows is all rendering using canvas.
Is it still possible to do those customization in 2.0.0? The doc only revealed some very basic setup for it. https://hyper.is/

Maybe related to #2601 , is there still no official way to change/hook in to the rendering?

+1, would really like to get my fancy ligatures back!
x-screen x-row { font-variant-ligatures: initial; }

@Tam support for ligatures is up to xterm sadly. Since switching to canvas rendering ligatures is hard to support. see https://github.com/xtermjs/xterm.js/issues/958

That is so sad..., the only reason I use hyper.js is only for the ability to use css props 🙁

So there are actually two problems here,
@alxtz The termCSS setting is now called just css so try with that.
@Tam sadly you will have to wait for the xtermjs team to implement that.

Since hyper now renders with canvas, you are correct in that it doesn't change how fonts are rendered, some things can be changed via xterm API.


feat: constructor for custom account access rules

Add constructor for custom AccessRules in account builtin
Add access rules to create account instruction

Done in #1138


Shortcut for toggling the mouse(HID) capture while the scrcpy window is not showing

[x] I have checked that a similar feature request does not already exist.

Is your feature request related to a problem? Please describe.
Every time I want to control my tablet with mouse(HID), I have to click on the scrcpy icon on taskbar to open the window then press Alt. It is not efficient.
Describe the solution you'd like
Press shortcut to toggling the mouse(HID) capture quickly even the scrcpy window is not showing.

In the general case, the window must be focused to receive mouse events. :/

I got a dictionary program on my pc. It is hidden in tray menu normally. When I press F9, its window show up and is focused, and when I press F9 again, it is hidden into tray menu.
Is it possible to make scrcpy able to to such a thing?

For all platforms, I'm not sure (not in a generic way at least). And what happens when there are 2 scrcpy running?


Refactor IOCat into Context

Existing implementation has dependency to IO Stack. The Context pattern is a right abstraction of this type.
Make it as a context simplifies API.

fixed in v1.3.0 & v2.0.0


Ticket/stable/pdb 1721 prepared statement fix (WIP)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1702/

this was just for demonstration


crypto/rand: detect biases in rand.Int(), clarify internals

cc @FiloSottile

A more comprehensive test would be to fill up an array of size N with M samples (where M >= X^2 * N) and ensure that every element in the array has at least X samples.
So long as X isn't very small, you should always see a roughly even distribution, so if something ever violates this condition, you have a potential bias. If it's reproducible, you definitely have a bias.


append parent after CodeMirror is not working

The following code works:
var cont = document.createElement('div');
document.body.appendChild(cont);
CodeMirror(cont, {});

However, this doesn't work:
var cont = document.createElement('div');
CodeMirror(cont, {});
document.body.appendChild(cont);

It shows the UI all messed up with the elements out of place.

Yes, that's a known limitation—you have to call .refresh() on the editor when it's added to the DOM (if it's not initialized there). This is unlikely to change in version 5 (there is, at least in a bunch of the supported browsers, no way for the editor to notice it has been added to the DOM, short of polling, which is unattractive)

Thanks for the explanation.


TypeError: element.from is undefined

Hi all,
I'm trying to install your plugin on a test site, my code follows. The only difference between your demo and my code is that i created a new FB App and gor an App ID and i get the following error :
TypeError: element.from is undefined
on line 266 post.author_link = 'http://facebook.com/' + element.from.id;
element is the post from teslamotors which works fine in your example, am i stupid or is there something wrong?
$(document).ready(function(){
            $('.accAPicture').socialfeed({
                // FACEBOOK
                facebook:{
                    accounts: ['@teslamotors','!teslamotors'],
                    limit: 2,
                    access_token: '1134255683255293|eSI1YYsy6iajeWZ7N94SSP9on_Q' // APP_ID|APP_SECRET
                },
                // GENERAL SETTINGS
                length:400,
                show_media:true,
                // Moderation function - if returns false, template will have class hidden
                moderation: function(content){
                    return  (content.text) ? content.text.indexOf('fuck') == -1 : true;
                },
                //update_period: 5000,
                // When all the posts are collected and displayed - this function is evoked
                callback: function(){
                    console.log('all posts are collected');
                },
                template:'/typo3conf/ext/smeno/Resources/Public/Js/SocialFeed.html'
            });
        });

I had the same issue.
That's because your faceook app is running a newer version of the graph API.
If I get it right, we need to specify which fields we want to retrieve since version 2.4.
Simply replace the line 303 in jquery.socialfeed.js with the following:
request_url = Feed.facebook.graph + 'v2.3/' + page + '/feed?fields=id,from,name,message,created_time,story,description,link,picture,object_id&' + limit + query_extention;

Also, replace the line 296 with the following:
request_url = Feed.facebook.graph + 'v2.3/' + userdata.id + '/posts?fields=id,from,name,message,created_time,story,description,link,picture,object_id' + limit + query_extention;

Indeed my app runs API Version 2.4
Thanks for the workaround but i think a definitive solution should be handled by the official plugin. Maybe you could propose a patch?
Or maybe API Version is already handled as an option, i'll check

The API version value is hard coded, it's not handled as an option.


'NoneType' has no len()...

What is the URL of the doc?
https://github.com/Picovoice/picovoice#python-demos
What's the nature of the issue? (e.g. steps do not work, typos/grammar/spelling, etc., out of date)
When I run this code based upon the doc, I get error following...
`from picovoice import Picovoice
access_key="XkufTA/RMMGkOLmN......eQBvSRGcS9jY7Ci+hoyv9N4lWSisQpbQ=="
keyword_path="resources/porcupine/resources/keyword_files/raspberry-pi/porcupine_raspberry-pi.ppn"
def wake_word_callback():
pass
context_path="resources/rhino/resources/contexts/raspberry-pi/smart_lighting_raspberry-pi.rhn"
def inference_callback(inference):
print(inference.is_understood)
print(inference.intent)
print(inference.slots)
# take action based on intent and slot values

handle = Picovoice(
access_key=access_key,
keyword_path=keyword_path,
wake_word_callback=wake_word_callback,
context_path=context_path,
inference_callback=inference_callback)
def get_next_audio_frame():
pass
while True:
handle.process(get_next_audio_frame())
handle.delete()`
Error:
Traceback (most recent call last):
File "/home/pi/picovoice/bioloid_motions_initial_1.py", line 30, in
handle.process(get_next_audio_frame())
File "/home/pi/.local/lib/python3.9/site-packages/picovoice/picovoice.py", line 233, in process
if len(pcm) != self.frame_length:
TypeError: object of type 'NoneType' has no len()

in Python, pass essentially means this is a stub and you need to implement the function.


Unable to Create Package Repository in Local Environment using Carvel Docs

What steps did you take:
I was following the steps outlined in Adding a Package Repository, with setting up a local registry and kind cluster using this recent PR
What happened:
Getting the below error when creating the Package Repository.
Fetching image:
    Get "https://<IP_ADDRESS>:5000/v2/": dial tcp <IP_ADDRESS>:5000: connect: connection refused; Get "http://<IP_ADDRESS>:5000/v2/": dial tcp <IP_ADDRESS>:5000: connect: connection refused
)

What did you expect:
I expected the Package Repository to be set-up successfully, or further instructions in the Carvel docs in case I don't have the right set-up to do so.
Anything else you would like to add:
Environment:

kapp Controller verison:
kapp-controller.carvel.dev/version: v0.32.0
Kubernetes version (use kubectl version)
Client version: v1.23
Server version: v1.21

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

Hi @kartiklunkad26 !  - thanks for filing!
You're right - the instructions provided were for the (late) katacoda platform which is no longer available. I would expect them to still work on most linux machines but they aren't general.
On a mac, if you run ipconfig getifaddr en0 can you confirm that you get something that looks like an IP address (e.g. I get <IP_ADDRESS>).
The trick here is that <IP_ADDRESS> always refers to the most localest of localhosts so when you run that from within a pod, in a node, in a k8s cluster, in a VM,  your network request won't escape the VM's network out to your development machine.
The fundamental move is to ensure that the variable REPO_HOST has a value that can be resolved from within your k8s cluster. So in this case, we just take advantage of the VM's network being able to see our development machine's IP address.   Other options include using a fully external repo such as dockerhub or github-container-registry and then putting the corresponding url into the REPO_HOST variable.
We can update the tutorial, but that contents is actually in a separate repo.

@kartiklunkad26  how do you think we should update the docs ?  The local registry made sense when it was possible to have a fully reproducible katacoda environment, but now do you think it makes more sense to tell the docs-consumer to use a dockerhub account?

Closing this out for now as done.


Update moving-data-to-new-datacenter-geos.md

Added Teams experience in a Microsoft 365 Multi-Geo-enabled tenancy to related links

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/5206

@JohanFreelancer9 Please copy review


Lock Python version to 3.6.4 for pyenv

Simplifies the Python setup by locking the version to be used by pyenv.

Thanks. This is makes it much simpler for users of pyenv.
The tests are failing because this pull request is coming from a fork. This is a bug I just discovered, which does not have to anything to do with the changes of your pull request. So I will merge it.
I just created an issue describing the problem when pull requests are filed by forks: https://github.com/ahaselsteiner/viroconweb/issues/183


data freshness button

Introduce Freshness button on TableDetailPage.
One the endpoint is hit, it fetches the table metadata from neo4j and pass the information to data freshness client where we can adopt any kind of custom logic to determine table freshness metric
Unit test added for the new api's response.
Available in Preview Environment.
https://amundsen-pre-2f5cd284.brexhq.dev/table_detail/production/acquirer/public/acquirer_transactions
However, we are still relying on devprod team to merge this #43456 which they will do early next week. I tested it in PE by checking out a branch from #43456 and setting up the DataFreshnessClient

PTAL @adcheong @minsuo @wli-brex

@minsuo They should be, unless the open source repo changes the directory lay out.


Remove moot version property from bower.json

Per bower/bower.json-spec@a325da3
Also their maintainer says they probably won't ever use it: http://stackoverflow.com/questions/24844901/bowers-bower-json-file-version-property

Nice, thanks :+1:


Kernel death on Shapely call deep in a cartopy call stack

Background
I'm working on a geographic plotting library at the moment. The backend is based on cartopy, an extension to matplotlib which modifies matplotlib for the purposes of defining and working with cartographic projections.
cartopy, in turn, makes extensive use of shapely internally.
One particular augmentation that cartopy makes is providing a set_extent method for cartopy.GeoAxes objects (the cartopy drop-in replacement for matplotlib.Axes). I am having trouble, however, with the method: it keeps causing kernel deaths every time the statement is executed.
Trace
I spun up pdb and poked down to see what was causing it. The call stack is huge, but seems to resolve around a particular shapely.geometry.Polygon.__geom__ call deep in the sequence.
I've flattened the failure into a script execution, with the pdb session attached, here. You can reproduce the issue yourself by cloning the repo and executing the runtime-failure.ipynb Jupyter notebook.
The kernel dies as a result of a failure on the C side of Shapely's execution. The following logline is printed to the Jupyter runtime console:
Assertion failed: (0 != cs), function GEOSCoordSeq_getSize_r, file geos_ts_c.cpp, line 3797.

Since I am not a C author I cannot debug this any further than that...
Platform
At the moment I can only confirm that this error occurs on my Mac Air OSX El Capitan. brew list says I have geos: stable 3.5.0 installed, pip says I have geos 3.5.0 and Shapely 1.5.16.
To-do
I will try to simplify the minimal failing example and test this out on my Windows as well, as that platform was having similar issues.

Try pip install --no-binary shapely and see #416.

Yes, that is the best thing to do. Thanks for the help, @QuLogic!

Doing so causes import cartopy.crs as ccrs to fail with the following error:
Invalid argument (must be a Polygon)
Geometry must be a Point or LineString

The console prints the same C call failure:
Assertion failed: (0 != cs), function GEOSCoordSeq_getSize_r, file geos_ts_c.cpp, line 3797.

On Windows I am having a separate but related problem: fiona fails internally (and doesn't even seem to raise a flag while doing so) when attempting to read via import geopandas as gpd; gpd.read_file("<FILENAME>", driver='GeoJSON'). I suspect that the root cause is the same.
Unfortunately it appears I have no recourse with regards to further development until this particular dependency hell gets sorted out. Boo.

@ResidentMario I tried cloning your repo but it is incomplete, missing data, doesn't completely specify its dependencies. I can't use it to debug. I'm pretty sure that incompatible GEOS DLLs from different sources (Conda, Homebrew, others) are the root of your problem, not Shapely.

Apologies, I had not set up the repository with expectation that it would be used for debugging.
Windows
The following sequence of actions should be a minimal reproducible failure on Windows, tested using a completely clean Ananconda 3.5 install:

Get on a Windows machine (obviously).
conda create --name geoplot pandas jupyter requests
git clone the geoplot repository, navigate to the /dependencies folder and install all of the wheels---for cartopy, fiona, gdal, pyroj, and shapely, specifically. These wheels are the latest 64-bit versions taken from the unofficial directory.
pip install geopandas
Run jupyter notebook, navigate to runtime-failure-two.ipynb, and execute it.

This should result in a kernel failure.
The computer in question does not have GEOS or GDAL installed through any other source.
Mac OSX
Still working on this one.

Why are you installing wheels if you're using conda? Mixing binaries is probably rather fragile. If they're not in defaults, you should be able to get all these packages from the conda-forge channel.

When I first ran into a dependency installation issue many months ago, I Googled for a solution, and using that was the first thing that came up that worked. It's always worked for me ever since then (until now, that is), and though I was aware of conda-forge this is the first time I've heard that it's better for this. Not surprising, but still, the first time I'm hearing it.
I'm away from that machine now, but I will try the conda-forge approach tomorrow.

Well, I don't use Windows, so I can't say which is better, but it seems like using a consistent source for everything is probably less likely to be a problem.

To paraphrase from the bug report linked to above:

I believe that running brew install gdal instead gets around this specific issue, insofar as it installs a version of libproj.dylib which gets linked to cartopy correctly.
However, installing proj in that manner installs much of the rest of the C geospatial software bear, which I believe may cause dependency conflicts deeper into the stack.

...which is the issue I saw and reported here.

See also #553.


python312Packages.throttler: Remove coverage testing

Removes the unused coverage and pytest-cov dependencies, and cleans up the code to be in line with modern standards.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Closing in favor of better PRs.


networking_v2 gre.yml

under exercises/networking_v2 we need to create an exercise for creating the GRE tunnel between the two AWS VPCs.  It is not clear to me if @termlen0 and @gdykeman want to combine this with OSPF or just improve on what we have now.  We need to probably designate which rtr per VPC will be the tunnel broker.
Ideally the final playbook would be agnostic, meaning if we spun up 4x Cisco CSR OR 2x Cisco CSR & 2 x Juniper vMX we would get identical results

this is done in the provisioner now


Generate gl3w.h directly from XML

Khronos generates their GL headers (including glcorearb.h) from XML files using a Python script (https://cvs.khronos.org/svn/repos/ogl/trunk/doc/registry/public/api/genheaders.py).
Would it make sense for gl3w to parse the structured XML directly, rather than interpreting the generated headers? Less scope for error imho.

OK this is old but I'll add a comment anyway: possible but a LOT of work.
The official header generator that takes XML and creates .h files can be downloaded from opengl.org. It is about 1800 lines of Python, although it is a bit more complicated because it has to handle older versions of OpenGL plus EGL and GLES as well.
I started writing my own loader generator for just OpenGL 3/4 from XML and it's over 900 lines of code without being complete yet.
gl3w is amazingly small and simple by comparison.


az confcom katapolicygen: called Result::unwrap() on an Err value: ParseIntError { kind: InvalidDigit }

Describe the bug
When executed the command to generate a policy with a yaml input i got the error on some occasions.
It looks like some images have some kind of incompatibility, hence the error.
My biggest issue in this occasion is not just the failure but the non-helpfulness of the message which lead me to waste of time looking for any error on my configuration.
Related command
az confcom katapolicygen -y deployment.yaml
apiVersion: v1
kind: Pod
metadata:
  name: nginx
  namespace: namespace
spec:
  serviceAccountName: workload-identity-sa
  runtimeClassName: kata-cc-isolation
  volumes:
    - name: endor-loc
      hostPath:
        path: /opt/confidential-containers/share/kata-containers/reference-info-base64
  containers:
  - name: nginx
    image: nginx:latest
    command: ["/bin/sh", "-ec", "while :; do echo '.'; sleep 5 ; done"]
    resources:
      requests:
        memory: "64Mi"
        cpu: "250m"
      limits:
        memory: "128Mi"
        cpu: "500m"
    env:
    - name: SkrClientKID
      value: <redacted>
    - name: SkrClientMAAEndpoint
      value: <redacted>.weu.attest.azure.net
    - name: SkrClientAKVEndpoint
      value: <redacted>.vault.azure.net
  - name: skr
    image: mcr.microsoft.com/aci/skr:2.7
    env:
      - name: SkrSideCarArgs
        value: <redacted>
    command:
      - /bin/skr
    volumeMounts:
      - mountPath: /opt/confidential-containers/share/kata-containers/reference-info-base64
        name: endor-loc
  - name: agones-gameserver-sidecar
    image: us-docker.pkg.dev/agones-images/release/agones-sdk:1.43.0
    env:
    - name: SkrClientKID
      value: key
    - name: SkrClientMAAEndpoint
      value: <redacted>.weu.attest.azure.net
    - name: SkrClientAKVEndpoint
      value: <redacted>.vault.azure.net

Errors
thread 'main' panicked at src\registry.rs:155:56:
called Result::unwrap() on an Err value: ParseIntError { kind: InvalidDigit }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
Issue script & Debug output
cli.knack.cli: Command arguments: ['confcom', 'katapolicygen', '-y', 'deployment.yaml', '--print-policy', '--debug']
cli.knack.cli: init debug log:
Enable color in terminal.
cli.knack.cli: Event: Cli.PreExecute []
cli.knack.cli: Event: CommandParser.OnGlobalArgumentsCreate [<function CLILogging.on_global_arguments at 0x000001328A76B9C0>, <function OutputProducer.on_global_arguments at 0x000001328A8F6200>, <function CLIQuery.on_global_arguments at 0x000001328A923D80>]
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableCreate []
cli.azure.cli.core: Modules found from index for 'confcom': ['azext_confcom']
cli.azure.cli.core: Loading command modules:
cli.azure.cli.core: Name                  Load Time    Groups  Commands
cli.azure.cli.core: Total (0)                 0.000         0         0
cli.azure.cli.core: These extensions are not installed and will be skipped: ['azext_ai_examples', 'azext_next']
cli.azure.cli.core: Loading extensions:
cli.azure.cli.core: Name                  Load Time    Groups  Commands  Directory
cli.azure.cli.core: confcom                   0.012         1         2  C:\Users<redacted>.azure\cliextensions\confcom
cli.azure.cli.core: Total (1)                 0.012         1         2
cli.azure.cli.core: Loaded 1 groups, 2 commands.
cli.azure.cli.core: Found a match in the command table.
cli.azure.cli.core: Raw command  : confcom katapolicygen
cli.azure.cli.core: Command table: confcom katapolicygen
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableTruncate [<function AzCliLogging.init_command_file_logging at 0x000001328D84E520>]
cli.azure.cli.core.azlogging: metadata file logging enabled - writing logs to 'C:\Users<redacted>.azure\commands\2024-09-26.15-54-27.confcom_katapolicygen.3348.log'.
az_command_data_logger: command args: confcom katapolicygen -y {} --print-policy --debug
cli.knack.cli: Event: CommandInvoker.OnPreArgumentLoad [<function register_global_subscription_argument..add_sucli.knack.cli: Event: CommandInvoker.OnPostArgumentLoad []
cli.knack.cli: Event: CommandInvoker.OnPostCommandTableCreate [<function register_ids_argument..add_ids_arguments at 0x000001328D8B4A40>, <function register_cache_arguments..add_cache_arguments at 0x000001328D8B4B80>]
cli.knack.cli: Event: CommandInvoker.OnCommandTableLoaded []
cli.knack.cli: Event: CommandInvoker.OnPreParseArgs []
cli.knack.cli: Event: CommandInvoker.OnPostParseArgs [<function OutputProducer.handle_output_argument at 0x000001328A8F62A0>, <function CLIQuery.handle_query_parameter at 0x000001328A923E20>, <function register_ids_argument..parse_ids_arguments at 0x000001328D8B4AE0>]
az_command_data_logger: extension name: confcom
az_command_data_logger: extension version: 0.3.6
thread 'main' panicked at src\registry.rs:155:56:
called Result::unwrap() on an Err value: ParseIntError { kind: InvalidDigit }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
cli.knack.cli: Event: Cli.PostExecute [<function AzCliLogging.deinit_cmd_metadata_logging at 0x000001328D84E7A0>]
az_command_data_logger: exit code: 101
cli.main: Command ran in 53.226 seconds (init: 0.814, invoke: 52.413)
telemetry.main: Begin splitting cli events and extra events, total events: 1
telemetry.client: Accumulated 0 events. Flush the clients.
telemetry.main: Finish splitting cli events and extra events, cli events: 1
telemetry.save: Save telemetry record of length 3674 in cache
telemetry.main: Begin creating telemetry upload process.
telemetry.process: Creating upload process: "C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe C:\Program Files\Microsoft SDKs\Azure\CLI2\Lib\site-packages\azure\cli\telemetry_init_.pyc C:\Users<redacted>.azure"
telemetry.process: Return from creating process
telemetry.main: Finish creating telemetry upload process.
Expected behavior
The command should generate the policy or, at least, provide a meaningful message stating that there is a problem with the image instead of crashing.
Environment Summary
az --version
azure-cli                         2.64.0
core                              2.64.0
telemetry                          1.1.0
Extensions:
aks-preview                      9.0.0b2
attestation                        1.0.0
confcom                            1.0.0
Dependencies:
msal                              1.30.0
azure-mgmt-resource               23.1.1
Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users<redacted>.azure\cliextensions'
Python (Windows) 3.11.8 (tags/v3.11.8:db85d51, Feb  6 2024, 22:03:32) [MSC v.1937 64 bit (AMD64)]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Additional context
As i mentioned, it does not happen with all the images, so i am guessing that is related to the layers that are included on it.
In the provided example, the image causing the error is the one on the third container. If relevant, that same image but on version 1.33.0 works ¯_(ツ)_/¯

Thank you for opening this issue, we will look into it.


wsl can't access win10, setting inbound, due to windows defender intercept

ping to win10 from wsl is ok, setting inbound, but curl can't success

/template