[Feature] Allow toggling of dark scheme + Display elements based on color scheme

Hi @cotes2020 , I'm about to implement this feature in my fork and figured it might be useful for others as well.
This PR allows you to switch between dark and light scheme with a body class. The implementation detail is left on developers, but this is an example of how to implement such switch:
<button
  class="color-scheme-dark-hidden"
  onclick="
    $('body')
      .removeClass('color-scheme-light')
      .addClass('color-scheme-dark')
  ">Dark scheme</button>
<button
  class="color-scheme-light-hidden"
  onclick="
    $('body')
      .removeClass('color-scheme-dark')
      .addClass('color-scheme-light')
  ">Light scheme</button>

Hi @cotes2020 , first of all - feel free to commit ;)
I wrote the persistence of the scheme settings already, but very quickly and maybe it's an overkill having a class for it. It is using cookies though, so that settings is remembered for the next visit. But it can be easily refactored to sessionStorage or localStorage for the same effect as with cookies.
Make it your decision, I'll be glad to implement whichever way.
Take a look here: https://github.com/mpavelka/miloslavpavelka-blog/blob/master/_includes/color-scheme-script.html
I guess you would want to replace setSchemeCookie and getSchemeFromCookie with storeScheme and getSchemeFromStorage and decide on the storage engine within...
And then I have

If you're OK with the implementation, I can add also to this PR.
Cheers!

Oh and this is how I have it on the blog (it's not online yet), but again, I leave the design on your decision of course ;)
Dark: https://drive.google.com/open?id=1mUKwziwKvAvJMnFFdEUM5HrJp6akImeD
Light: https://drive.google.com/open?id=15K2cMcVl1AFxBCz95AGzIYrmmaiDmE01

I wrote the persistence of the scheme settings already...

What? But sorry, I have finished the similar development in my local machine, thank you so mush~
On the other hand, please allow me to remind you that the CSS of several files in your forked edition should also be modified to comply with the mode switch:

assets/css/archives.scss
assets/css/categories.scss
assets/css/syntax.scss

They are well handled in my local, and I will publish my code later.

OK thanks, I didn't notice that, sorry for the half-done job
I'll wait for the updates and merge to my project later
Cheers!

I have released the code 89288ab7cb22cb519a930faba1527e0aaf34633c.


fixing swagger setup using localhost as host name

Introduced https://github.com/apache/pinot/pull/13122/files#diff-7c6118ecbf342922f9e9288c5fbaf9c8dd3f158895d2a7e4e5582762249ecd06R54
We shouldn't set swagger hostname as localhost, which might not be accessible from the external environment.
E.g. pinot deployed in k8s will using pinot-controller-1 as lcoalhost name, but this hostname is not exposed outside.
Current Behavior is using machine hostname:

After fix:

cc:  @abhioncbr

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

Project coverage is 0.00%. Comparing base (59551e4) to head (3a06f96).
Report is 509 commits behind head on master.

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #13254       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436     2459       +23
  Lines        133233   135354     +2121
  Branches      20636    20987      +351
=============================================
- Hits          82274        0    -82274
- Misses        44911   135354    +90443
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <ø> (-61.75%)
:arrow_down:

skip-bytebuffers-true
?

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Android Issue - Change Package name

When i changed the package name "com.freerdp.freerdpcore" to "com.myname.freerdpcore", gettting the below mentioned JNI error in logcat:
JNI DETECTED ERROR IN APPLICATION: JNI GetMethodID called with pending exception java.lang.ClassNotFoundException: Didn't find class "com.freerdp.freerdpcore.services.LibFreeRDP" on path: DexPathList
I want to change the package name, please suggest. Thank you.

@jass90 if you change the package name you will need to change it everywhere where "com.freerdp.freerdpcore"


Upmerge from v1.7

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @vosst isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf
User @chrisdunelm isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
The Linux Foundation CLA GitHub bot

sigh that'll be painful.

****************************************************************

libgrpc.so

     VM SIZE                                                 FILE SIZE
 ++++++++++++++ GROWING                                   ++++++++++++++
  +0.6% +3.14Ki [None]                                    +29.7Ki  +0.5%
      +0.6% +2.89Ki [Unmapped]                                +29.6Ki  +0.5%
      +8.3%     +92 [None]                                          0  [ = ]
      [NEW]     +56 grpc_fork_support_init()::truthy              +56  [NEW]
      [NEW]     +48 g_cv                                            0  [ = ]
       +25%     +40 g_mu                                            0  [ = ]
      +100%      +4 g_thread_count                                  0  [ = ]
      [NEW]      +4 g_awaiting_threads                              0  [ = ]
      [NEW]      +4 fork_support_enabled                            0  [ = ]
      [NEW]      +4 override_fork_support_enabled                  +4  [NEW]
  [NEW]    +550 src/core/lib/iomgr/fork_posix.cc             +550  [NEW]
      [NEW]    +279 grpc_prefork                                 +279  [NEW]
      [NEW]    +110 grpc_postfork_child() [clone .part.1]        +110  [NEW]
      [NEW]     +54 grpc_fork_handlers_auto_register              +54  [NEW]
      [NEW]     +41 [Unmapped]                                    +41  [NEW]
      [NEW]     +33 grpc_postfork_child                           +33  [NEW]
      [NEW]     +33 grpc_postfork_parent                          +33  [NEW]
   +62%    +341 src/core/lib/support/thd_posix.cc            +341   +62%
      [NEW]    +108 gpr_await_threads                            +108  [NEW]
      [NEW]     +92 dec_thd_count() [clone .part.0]               +92  [NEW]
       +11%     +55 gpr_thd_new                                   +55   +11%
      [NEW]     +53 gpr_thd_init                                  +53  [NEW]
       +73%     +19 [Unmapped]                                    +19   +73%
       +44%     +14 thread_body                                   +14   +44%
  [NEW]    +151 src/core/lib/support/fork.cc                 +151  [NEW]
      [NEW]    +128 grpc_fork_support_init                       +128  [NEW]
      [NEW]      +9 [Unmapped]                                     +9  [NEW]
      [NEW]      +7 grpc_enable_fork_support                       +7  [NEW]
      [NEW]      +7 grpc_fork_support_enabled                      +7  [NEW]
  [NEW]     +31 pthread_atfork.c                              +31  [NEW]
      [NEW]     +31 __pthread_atfork                              +31  [NEW]
  +1.4%     +16 src/core/lib/surface/init.cc                  +16  +1.4%
       +20%      +9 do_basic_init                                  +9   +20%
       +50%      +7 [Unmapped]                                     +7   +50%

  +0.4% +4.20Ki TOTAL                                     +30.7Ki  +0.5%

****************************************************************

libgrpc++.so

     VM SIZE                                    FILE SIZE
 ++++++++++++++ GROWING                      ++++++++++++++

 -------------- SHRINKING                    --------------
  -8.0%      -7 src/cpp/common/version_cc.cc      -7  -8.0%
     -17.1%      -7 grpc::Version[abi:cxx11]          -7 -17.1%

 -+-+-+-+-+-+-+ MIXED                        +-+-+-+-+-+-+-
  +0.0%      +7 [None]                           -89  -0.0%

  [ = ]       0 TOTAL                            -96  -0.0%

[trickle] No significant performance differences

Corrupt JSON data (indicates timeout or crash):
    bm_fullstack_streaming_ping_pong.BM_StreamingPingPong_InProcessCHTTP2_NoOpMutator_NoOpMutator__1_1.opt.old: 1

[microbenchmarks] No significant performance differences

@nicolasnoble
Looks like this just needs a clang format then should be all set.

Shouldn't all the upmerges from 1.7 be also included in 1.8? (if they already are, then I'm sorry, just checking).

****************************************************************

libgrpc.so

     VM SIZE                                                 FILE SIZE
 ++++++++++++++ GROWING                                   ++++++++++++++
  +0.6% +3.14Ki [None]                                    +29.7Ki  +0.5%
      +0.6% +2.89Ki [Unmapped]                                +29.6Ki  +0.5%
      +8.3%     +92 [None]                                          0  [ = ]
      [NEW]     +56 grpc_fork_support_init()::truthy              +56  [NEW]
      [NEW]     +48 g_cv                                            0  [ = ]
       +25%     +40 g_mu                                            0  [ = ]
      +100%      +4 g_thread_count                                  0  [ = ]
      [NEW]      +4 g_awaiting_threads                              0  [ = ]
      [NEW]      +4 fork_support_enabled                            0  [ = ]
      [NEW]      +4 override_fork_support_enabled                  +4  [NEW]
  [NEW]    +550 src/core/lib/iomgr/fork_posix.cc             +550  [NEW]
      [NEW]    +279 grpc_prefork                                 +279  [NEW]
      [NEW]    +110 grpc_postfork_child() [clone .part.1]        +110  [NEW]
      [NEW]     +54 grpc_fork_handlers_auto_register              +54  [NEW]
      [NEW]     +41 [Unmapped]                                    +41  [NEW]
      [NEW]     +33 grpc_postfork_child                           +33  [NEW]
      [NEW]     +33 grpc_postfork_parent                          +33  [NEW]
   +62%    +341 src/core/lib/support/thd_posix.cc            +341   +62%
      [NEW]    +108 gpr_await_threads                            +108  [NEW]
      [NEW]     +92 dec_thd_count() [clone .part.0]               +92  [NEW]
       +11%     +55 gpr_thd_new                                   +55   +11%
      [NEW]     +53 gpr_thd_init                                  +53  [NEW]
       +73%     +19 [Unmapped]                                    +19   +73%
       +44%     +14 thread_body                                   +14   +44%
  [NEW]    +151 src/core/lib/support/fork.cc                 +151  [NEW]
      [NEW]    +128 grpc_fork_support_init                       +128  [NEW]
      [NEW]      +9 [Unmapped]                                     +9  [NEW]
      [NEW]      +7 grpc_enable_fork_support                       +7  [NEW]
      [NEW]      +7 grpc_fork_support_enabled                      +7  [NEW]
  [NEW]     +31 pthread_atfork.c                              +31  [NEW]
      [NEW]     +31 __pthread_atfork                              +31  [NEW]
  +1.4%     +16 src/core/lib/surface/init.cc                  +16  +1.4%
       +20%      +9 do_basic_init                                  +9   +20%
       +50%      +7 [Unmapped]                                     +7   +50%

  +0.4% +4.20Ki TOTAL                                     +30.7Ki  +0.5%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE                                                 FILE SIZE
 ++++++++++++++ GROWING                                   ++++++++++++++
  +0.6% +3.14Ki [None]                                    +29.7Ki  +0.5%
      +0.6% +2.89Ki [Unmapped]                                +29.6Ki  +0.5%
      +8.3%     +92 [None]                                          0  [ = ]
      [NEW]     +56 grpc_fork_support_init()::truthy              +56  [NEW]
      [NEW]     +48 g_cv                                            0  [ = ]
       +25%     +40 g_mu                                            0  [ = ]
      +100%      +4 g_thread_count                                  0  [ = ]
      [NEW]      +4 g_awaiting_threads                              0  [ = ]
      [NEW]      +4 fork_support_enabled                            0  [ = ]
      [NEW]      +4 override_fork_support_enabled                  +4  [NEW]
  [NEW]    +550 src/core/lib/iomgr/fork_posix.cc             +550  [NEW]
      [NEW]    +279 grpc_prefork                                 +279  [NEW]
      [NEW]    +110 grpc_postfork_child() [clone .part.1]        +110  [NEW]
      [NEW]     +54 grpc_fork_handlers_auto_register              +54  [NEW]
      [NEW]     +41 [Unmapped]                                    +41  [NEW]
      [NEW]     +33 grpc_postfork_child                           +33  [NEW]
      [NEW]     +33 grpc_postfork_parent                          +33  [NEW]
   +62%    +341 src/core/lib/support/thd_posix.cc            +341   +62%
      [NEW]    +108 gpr_await_threads                            +108  [NEW]
      [NEW]     +92 dec_thd_count() [clone .part.0]               +92  [NEW]
       +11%     +55 gpr_thd_new                                   +55   +11%
      [NEW]     +53 gpr_thd_init                                  +53  [NEW]
       +73%     +19 [Unmapped]                                    +19   +73%
       +44%     +14 thread_body                                   +14   +44%
  [NEW]    +151 src/core/lib/support/fork.cc                 +151  [NEW]
      [NEW]    +128 grpc_fork_support_init                       +128  [NEW]
      [NEW]      +9 [Unmapped]                                     +9  [NEW]
      [NEW]      +7 grpc_enable_fork_support                       +7  [NEW]
      [NEW]      +7 grpc_fork_support_enabled                      +7  [NEW]
  [NEW]     +31 pthread_atfork.c                              +31  [NEW]
      [NEW]     +31 __pthread_atfork                              +31  [NEW]
  +1.4%     +16 src/core/lib/surface/init.cc                  +16  +1.4%
       +20%      +9 do_basic_init                                  +9   +20%
       +50%      +7 [Unmapped]                                     +7   +50%

  +0.4% +4.20Ki TOTAL                                     +30.7Ki  +0.5%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc.so

     VM SIZE                                                 FILE SIZE
 ++++++++++++++ GROWING                                   ++++++++++++++
  +0.6% +3.14Ki [None]                                    +29.7Ki  +0.5%
      +0.6% +2.89Ki [Unmapped]                                +29.6Ki  +0.5%
      +8.3%     +92 [None]                                          0  [ = ]
      [NEW]     +56 grpc_fork_support_init()::truthy              +56  [NEW]
      [NEW]     +48 g_cv                                            0  [ = ]
       +25%     +40 g_mu                                            0  [ = ]
      +100%      +4 g_thread_count                                  0  [ = ]
      [NEW]      +4 g_awaiting_threads                              0  [ = ]
      [NEW]      +4 fork_support_enabled                            0  [ = ]
      [NEW]      +4 override_fork_support_enabled                  +4  [NEW]
  [NEW]    +550 src/core/lib/iomgr/fork_posix.cc             +550  [NEW]
      [NEW]    +279 grpc_prefork                                 +279  [NEW]
      [NEW]    +110 grpc_postfork_child() [clone .part.1]        +110  [NEW]
      [NEW]     +54 grpc_fork_handlers_auto_register              +54  [NEW]
      [NEW]     +41 [Unmapped]                                    +41  [NEW]
      [NEW]     +33 grpc_postfork_child                           +33  [NEW]
      [NEW]     +33 grpc_postfork_parent                          +33  [NEW]
   +62%    +341 src/core/lib/support/thd_posix.cc            +341   +62%
      [NEW]    +108 gpr_await_threads                            +108  [NEW]
      [NEW]     +92 dec_thd_count() [clone .part.0]               +92  [NEW]
       +11%     +55 gpr_thd_new                                   +55   +11%
      [NEW]     +53 gpr_thd_init                                  +53  [NEW]
       +73%     +19 [Unmapped]                                    +19   +73%
       +44%     +14 thread_body                                   +14   +44%
  [NEW]    +151 src/core/lib/support/fork.cc                 +151  [NEW]
      [NEW]    +128 grpc_fork_support_init                       +128  [NEW]
      [NEW]      +9 [Unmapped]                                     +9  [NEW]
      [NEW]      +7 grpc_enable_fork_support                       +7  [NEW]
      [NEW]      +7 grpc_fork_support_enabled                      +7  [NEW]
  [NEW]     +31 pthread_atfork.c                              +31  [NEW]
      [NEW]     +31 __pthread_atfork                              +31  [NEW]
  +1.4%     +16 src/core/lib/surface/init.cc                  +16  +1.4%
       +20%      +9 do_basic_init                                  +9   +20%
       +50%      +7 [Unmapped]                                     +7   +50%

  +0.4% +4.20Ki TOTAL                                     +30.7Ki  +0.5%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

[microbenchmarks] Performance differences noted:
Benchmark                  cpu_time    real_time
-------------------------  ----------  -----------
BM_MetadataRefUnrefStatic  +6%         +6%

[microbenchmarks] No significant performance differences

Known failures: #12913 https://github.com/grpc/grpc/issues/13122


Vue init doesn't work on vue-cli 2.9.4

Version
2.9.3
Reproduction link
https://pastebin.com/gZfNKx7h
Steps to reproduce
vue init webpack test123
What is expected?
A directory with maded with the webpack template
What is actually happening?
An error in the terminal:
Unknown command init.
vue-cli · Failed to download repo vuejs-templates/[object Object]: Response code 404 (Not Found)

The version of vue-cli is 2.9.4

duplicate of #1413 I see just now.
Sorry


New app: LibreNMS Alerts

Description
New app: LibreNMS Alerts - See a count of active LibreNMS alerts as well as a summary of alerting devices.

Copilot

🤖 Generated by Copilot at 273fd95
Summary
🚨🌐📝

This pull request adds a new app called librenms_alerts, which shows the number of alerts from a LibreNMS server on the Tidbyt device. The app is written in Starlark and uses the Tidbyt API to fetch and display data. The app also has a manifest.yaml file with metadata for publishing and installing the app.

librenms_alerts
A new app for Tidbyt
Shows alerts in spring

Walkthrough

Create and publish a new app called librenms_alerts that displays the current count of alerts from a LibreNMS server on the Tidbyt device (link, link)

Add the code for the app in librenms_alerts.star using the Starlark language and the Tidbyt API (link)

Define a configuration schema that requires the user to enter the LibreNMS URL and API key (link)
Make HTTP requests to the LibreNMS API and parse the JSON responses (link)
Cache the data to avoid unnecessary requests and respect the API rate limit (link)
Render the alert count as text, image, or marquee depending on the device orientation and the number of alerts (link)
Handle various error scenarios and display appropriate messages (link)
Add comments to explain the logic and functionality of the app (link)

Add the metadata for the app in manifest.yaml (link)

Specify the app id, name, summary, description, author, file name, and package name (link)

I have read the CLA Document and I hereby sign the CLA

recheck


Fixed generators

Coverage remained the same at 100.0% when pulling afbe71371a75e52eb0cf9e5876e18c8e457ecde4 on feature/better_iterators into ac03a7a7c76cf551def402422563f9922a14c2e1 on develop.

Coverage remained the same at 100.0% when pulling afbe71371a75e52eb0cf9e5876e18c8e457ecde4 on feature/better_iterators into ac03a7a7c76cf551def402422563f9922a14c2e1 on develop.


Crash during vite build due to something like infinite loop eating all of the available memory

Describe the bug
First of all I've checked #2433, because of OOM error. And none of the workarounds are worked. And looks like it is completely different case. Everything points to that during build vite running into some kind of infinite loop eating all of the available memory, no matter how much you supply, and build ends up with vite node process OOM crash.
Problem is reproducible even in the simple almost empty template project using couple of cubing library submodules/functions. I wondering what in this library can cause such problem with vite.
Can't localize for now, vite build does not produce any of detailed logs during build even if --debug option is supplied. Any suggestions how to trace/debug vite build is appreciated. Already tried to make heap snapshots and V8 profiling, but at this point not all clear for me there:
$ node --heapsnapshot-near-heap-limit 2 ./node_modules/vite/bin/vite.js build
$ node --prof ./node_modules/vite/bin/vite.js build
$ node --prof-process isolate-*-v8.log > v8-profile.txt

Reproduction
https://stackblitz.com/edit/vite-oom-test
Steps to reproduce
Create simple project from template:
$ npm create vite@latest vite-oom-test -- --template vanilla-ts

Install cubing module from npm:
$ cd vite-oom-test/
$ npm install cubing
$ npm update

Replace main.ts with simple usage of that part of cubing library which causes problem:
$ cat <<EOF > src/main.ts

import {
    experimentalSolve3x3x3IgnoringCenters,
    random333Pattern
} from 'cubing/search';

var pattern = await random333Pattern();
var alg = await experimentalSolve3x3x3IgnoringCenters(pattern);
console.log(alg.toString());

EOF

Increase heap size in node as much as possible:
$ export NODE_OPTIONS="--max_old_space_size=16384"

Run vite build and expect infinite loop eating all of the available memory following with OOM crash:
$ npm run build

System Info
System:
    OS: macOS 12.7.1
    CPU: (8) x64 Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
    Memory: 4.75 GB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 20.10.0 - /usr/local/bin/node
    npm: 10.2.3 - /usr/local/bin/npm
  Browsers:
    Chrome: 120.0.6099.62
    Safari: 17.1.2
  npmPackages:
    vite: ^5.0.0 => 5.0.6

Used Package Manager
npm
Logs

Click to expand!
><EMAIL_ADDRESS>build
> tsc && vite build --debug

2023-12-07T15:40:01.562Z vite:config no config file found.
2023-12-07T15:40:01.617Z vite:config using resolved config: {
  root: '/Users/afedotov/tmp/vite-oom-test',
  base: '/',
  mode: 'production',
  configFile: undefined,
  logLevel: undefined,
  clearScreen: undefined,
  optimizeDeps: {
    disabled: 'build',
    force: undefined,
    esbuildOptions: { preserveSymlinks: false }
  },
  build: {
    target: [ 'es2020', 'edge88', 'firefox78', 'chrome87', 'safari14' ],
    cssTarget: [ 'es2020', 'edge88', 'firefox78', 'chrome87', 'safari14' ],
    outDir: 'dist',
    assetsDir: 'assets',
    assetsInlineLimit: 4096,
    cssCodeSplit: true,
    sourcemap: false,
    rollupOptions: {},
    minify: 'esbuild',
    terserOptions: {},
    write: true,
    emptyOutDir: null,
    copyPublicDir: true,
    manifest: false,
    lib: false,
    ssr: false,
    ssrManifest: false,
    ssrEmitAssets: false,
    reportCompressedSize: true,
    chunkSizeWarningLimit: 500,
    watch: null,
    commonjsOptions: { include: [Array], extensions: [Array] },
    dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] },
    modulePreload: { polyfill: true },
    cssMinify: true
  },
  configFileDependencies: [],
  inlineConfig: {
    root: undefined,
    base: undefined,
    mode: undefined,
    configFile: undefined,
    logLevel: undefined,
    clearScreen: undefined,
    optimizeDeps: { force: undefined },
    build: {}
  },
  rawBase: '/',
  resolve: {
    mainFields: [ 'browser', 'module', 'jsnext:main', 'jsnext' ],
    conditions: [],
    extensions: [
      '.mjs',  '.js',
      '.mts',  '.ts',
      '.jsx',  '.tsx',
      '.json'
    ],
    dedupe: [],
    preserveSymlinks: false,
    alias: [ [Object], [Object] ]
  },
  publicDir: '/Users/afedotov/tmp/vite-oom-test/public',
  cacheDir: '/Users/afedotov/tmp/vite-oom-test/node_modules/.vite',
  command: 'build',
  ssr: {
    target: 'node',
    optimizeDeps: { disabled: true, esbuildOptions: [Object] }
  },
  isWorker: false,
  mainConfig: null,
  isProduction: true,
  plugins: [
    'vite:build-metadata',
    'vite:watch-package-data',
    'vite:pre-alias',
    'alias',
    'vite:modulepreload-polyfill',
    'vite:resolve',
    'vite:html-inline-proxy',
    'vite:css',
    'vite:esbuild',
    'vite:json',
    'vite:wasm-helper',
    'vite:worker',
    'vite:asset',
    'vite:wasm-fallback',
    'vite:define',
    'vite:css-post',
    'vite:build-html',
    'vite:worker-import-meta-url',
    'vite:asset-import-meta-url',
    'vite:force-systemjs-wrap-complete',
    'commonjs',
    'vite:data-uri',
    'vite:dynamic-import-vars',
    'vite:import-glob',
    'vite:build-import-analysis',
    'vite:esbuild-transpile',
    'vite:terser',
    'vite:reporter',
    'vite:load-fallback'
  ],
  css: { lightningcss: undefined },
  esbuild: { jsxDev: false },
  server: {
    preTransformRequests: true,
    sourcemapIgnoreList: [Function: isInNodeModules$1],
    middlewareMode: false,
    fs: { strict: true, allow: [Array], deny: [Array] }
  },
  preview: {
    port: undefined,
    strictPort: undefined,
    host: undefined,
    https: undefined,
    open: undefined,
    proxy: undefined,
    cors: undefined,
    headers: undefined
  },
  envDir: '/Users/afedotov/tmp/vite-oom-test',
  env: { BASE_URL: '/', MODE: 'production', DEV: false, PROD: true },
  assetsInclude: [Function: assetsInclude],
  logger: {
    hasWarned: false,
    info: [Function: info],
    warn: [Function: warn],
    warnOnce: [Function: warnOnce],
    error: [Function: error],
    clearScreen: [Function: clearScreen],
    hasErrorLogged: [Function: hasErrorLogged]
  },
  packageCache: Map(1) {
    'fnpd_/Users/afedotov/tmp/vite-oom-test' => {
      dir: '/Users/afedotov/tmp/vite-oom-test',
      data: [Object],
      hasSideEffects: [Function: hasSideEffects],
      webResolvedImports: {},
      nodeResolvedImports: {},
      setResolvedCache: [Function: setResolvedCache],
      getResolvedCache: [Function: getResolvedCache]
    },
    set: [Function (anonymous)]
  },
  createResolver: [Function: createResolver],
  worker: { format: 'iife', plugins: '() => plugins', rollupOptions: {} },
  appType: 'spa',
  experimental: { importGlobRestoreExtension: false, hmrPartialAccept: false },
  getSortedPlugins: [Function: getSortedPlugins],
  getSortedPluginHooks: [Function: getSortedPluginHooks]
}
vite v5.0.6 building for production...
transforming...

<--- Last few GCs --->

[6435:0x7ff145100000]   443850 ms: Mark-Compact 16109.8 (16419.5) -> 16098.9 (16424.5) MB, 27278.40 / 0.09 ms  (average mu = 0.091, current mu = 0.007) task; scavenge might not succeed
[6435:0x7ff145100000]   471715 ms: Mark-Compact 16115.3 (16425.0) -> 16105.3 (16431.5) MB, 27674.23 / 0.06 ms  (average mu = 0.051, current mu = 0.007) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x100cec755 node::Abort() [/usr/local/bin/node]
 2: 0x100cec936 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/local/bin/node]
 3: 0x100e9c91c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/local/bin/node]
 4: 0x10108cac7 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/usr/local/bin/node]
 5: 0x101091097 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/local/bin/node]
 6: 0x10108d3e5 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/local/bin/node]
 7: 0x10108ae80 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/bin/node]
 8: 0x10107fb91 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node]
 9: 0x1010805d5 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node]
10: 0x1010626c2 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/local/bin/node]
11: 0x1014e04c0 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/local/bin/node]
12: 0x1018b2136 Builtins_CEntry_Return1_ArgvOnStack_NoBuiltinExit [/usr/local/bin/node]
13: 0x1018909b0 Builtins_ObjectEntries [/usr/local/bin/node]
14: 0x10c0cc75d
sh: line 1:  6435 Abort trap: 6           vite build --debug

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Duplicate of #14499, #7015


Feature Request: Let me know if my Angular packages are out of sync

Feature Request
ng version shows me the Angular packages currently in use, it would be nice if the CLI threw a warning if they were out of sync.
Example:

Your Angular packages are out of sync. @angular/platform-browser is version 4.2.3 but @angular/core is version 4.2.4. To fix this, run "<yarn|npm> <add|install><EMAIL_ADDRESS>

This would be useful to know, but not sure this is not exclusive to Angular (but rather npm).
You may find the following package useful:
https://www.npmjs.com/package/npm-check-updates

Thinking more about it, you @limpygnome is probably right, we should just rely on the package managers for this. That's what their job is, even if they don't do it perfectly today.


feat(kselect): add clearable prop

Summary

Porting changes of #749
@kaiarrowood
PR Checklist

[ ] Does not introduce dependencies
[ ] Functional: all changes do not break existing APIs and if so, bump major version.
[ ] Tests pass: check the output of yarn test packages/
[ ] Naming: the files and the method and prop variables use the same naming conventions as other Kongponents
[ ] Framework style: abides by the essential rules in Vue's style guide
[ ] Cleanliness: does not have formatting issues, unused code (e.g., console.logs), or leftover comments
[ ] Docs: includes a technically accurate README, uses JSDOC where appropriate

Happy to help!


ENH: Support Random Unit Vector

Is your feature request related to a problem? Please describe.
Proposed new feature or change:
Description
Often you want to randomize a "direction" that doesn't have "size". This can be useful when:

You want to randomize the direction of an NPC walk in a 2D or 3D games, where its speed is a predefined constant.
You're developing particles simulation with all particles moving in random directions
etc.

This random direction should be an nth dimensional unit vector which is randomized uniformly from the unit sphere. That means that sections of the unit sphere with equal areas should have the same chance of getting a vector from.
Implementation
If one wants to randomize nth dimensional direction uniformly, one must do the following:

Generate n components of the vector using the standard normal distribution
Find the norm the generated vector
Divide the vector by its norm

In simple Python code:
import numpy as np
from scipy import stats

def sphere_uniform(n: int):
    vec = stats.norm.rvs(size=n)
    size = np.linalg.norm(vec)
    return vec / size

This implementation suggestion is based on this blog post. I'm not sure if there's a faster way of implementing it using C++ and Cython, but I'm confident that someone here will know.
Why Implement It in Scipy?
Originally, I suggested implementing it on Numpy (numpy/numpy#21523), but they stated that they are not interested in expending the numpy.random library and suggested adding this new feature as part of scipy.stats.
I believe that random unit vectors are common enough to be a part of Numpy or Scipy, which are two of the most popular python libraries (if not the most popular ones). Scientists, gamers and engineers use random directions all the time, and I believe there is no reason why this ability shouldn't be provided out-of-the-box.

Seems a bit too specific to be on its own as a function to be honest. The following is sufficient (similar to what you have instead you want a uniform distribution):
import numpy as np

def unit_vector(n: int):
    rng = np.default_rng()
    vec = rng.random(n)
    vec /= np.linalg.norm(vec)
    return vec

It gets even shorter if you don't mind using np.random.rand(n) directly. Hence I think this is a bearable burden for any use.

I have quite some technical issues with that blogpost but regardless of the distribution which involves no additional code for changing it normal distribution, this is still a two-liner code that I would prefer burdening the user instead of maintaining within scipy or numpy.

I understand.
Thanks anyway

Uniformly-random vectors on the unit hypersphere is an important multivariate distribution. It's not hard to implement oneself, if one knows the necessary trick (and yes, the normal distribution is necessary). If one doesn't know the appropriate trick, ad hoc implementations tend to fail in ways that are hard to diagnose in higher dimensions than 2.

What could be a good API for this?
Sth like a distribution scipy.stats.UniformUnitSphere with method rvs or just a function scipy.stats.randomunitvector(size) ?

The former, I think. It would fit well as a subclass of multi_rv_generic in _multivariate.py.

Good to see that other people find this feature needed and usefull.
Do I have a go on implementing it?

I asked on the mailing list if there are any objections against this and a function for spherical mean/variance. If there are none , I think it can be taken as a yes in a few days.

I think that's true, @dschmitz89.
One thing to look out for is to not start with the shortcomings we're addressing in gh-16278. If you use another multivariate distribution as a reference, you may be tempted to add np.squeeze to the output of rvs. This is undesirable. If d is the number of dimensions and size is passed in as a shape parameter (or () if size is None), then the output shape should be size + (d,). (I think it's OK to support only scalar d for now because there is a decision to be made w.r.t. how to vectorize over array shapes.)

multi_rv_generic instances have methods that take the distribution parameters. One instance of the multi_rv_generic is made at the module level.
stats.multivariate_normal.pdf(x, mean, cov)

multi_rv_frozen instances are created by calling the multi_rv_generic instance with the distribution parameters. The frozen instance then carries those distribution parameters around so that you can call the methods without providing the distribution parameters.
my_norm = stats.multivariate_normal(mean, cov)
my_norm.pdf(x)

This scheme is relatively complicated for the multivariate distributions because each one is fairly different from the others. The univariate distributions have much more shared infrastructure and only need to implement the generic class. They all share a frozen implementation.

@saroad2 are you still interested in implementing this? If you do, I can review and merge.

Hey @mdhaber.
After many hours of trying, I could not build Scipy on my Windows environment. It was really frustrating.
Unfortunately, I don't have access to a Linux or Mac environments, so I cannot implement this ability for now.
Would love to see this ability implemented! It should be quite easy once you get to build Scipy...

@saroad2 I am using the Windows Subsystem for Linux on Windows 11. Works like a charm there with the instructions for conda given here . I admit, I have not even tried to build using windows directly. Anything related to complex compiled code on Windows has always been very painful for me too (Fortran ... :'( ).
There is a discussion about building on windows in #16769 .
In case you cannot find the time, I would be able to take this over.

Hey @dschmitz89 , thanks for the feedback!
In the following weeks I will not be able to work on this. A little bit preoccupied with other things.
I would love if you could take over so I won't block it.
Thanks!


[Bug] Dependency injection not working with inheritance

Describe the bug
The dependency injection does not work when the type of the argument is set as the protocol and not the actual implementation of the said protocol.
To Reproduce
from typing import Protocol
from sanic import Sanic, text
from sanic import Request

class ExampleServiceProtocol(Protocol):
    def some_method(self) -> int:
        ...

class ExampleServiceImplementation(ExampleServiceProtocol):
    def some_method(self) -> int:
        return 1

def protocol_route(request: Request, example_service: ExampleServiceProtocol):
    return text("ok")

def implemented_route(request: Request, example_service: ExampleServiceImplementation):
    return text("ok")

def create_app() -> Sanic:
    app = Sanic("sample-app")

    app.add_route(protocol_route, "/protocol")
    app.add_route(implemented_route, "/implemented")

    example_service = ExampleServiceImplementation()
    app.ext.dependency(example_service)

    return app

In the above example, requests to /implemented works without any issues, but requests to /protocol results in the following error:
⚠ 500 — Internal Server Error
==============================
protocol_route() missing 1 required positional argument: 'example_service'

TypeError: protocol_route() missing 1 required positional argument: 'example_service' while handling path /protocol

Expected behavior
The argument should be passed if there is an instance in the registered dependencies that is a subclass of the type specified in the route handler signature.
Environment (please complete the following information):

OS: Ubuntu 20.04.6 LTS (via WSL2 version <IP_ADDRESS>)
Sanic version: Sanic 23.3.0; Routing 22.8.0
Sanic Ext version: 23.3.0

Additional context
Of all the issues, this is the closest issue I found which might be related to it.

Not a bug. Injection requires the type to be registered.

To be more specific, when you use the higher level dependency method, the type of the object is inspected. When that type is found as an annotation, it is injected. Something like this should work:
app.ext.add_dependency(
    ExampleServiceProtocol,
    lambda: example_service)

Oh the solution you gave works perfectly! My bad for marking it as a bug. I just misunderstood how the API worked.

No worries. good luck 😎


PowerToys not responding

Environment
Windows 10 Enterprise
Windows build number: Version 10.0.17763.437
PowerToys version: v0.18.1
PowerToy module for which you are reporting the bug (if applicable): Main

Steps to reproduce
Install PowerToys
Restart Computer
Open it from show-hidden-icons section
It doesn' t respond. Tabs on the left is not clickable. Elements in the general settings is not clickable also.
Expected behavior
Elements in the general settings tab should be clickable.
Tabs should be clickable.
Solved
Close the PowerToys
Close the computer
Open it again
It works.

We migrated to a new Settings on v0.18.1 which requires a minimum of Windows 10 1903 (build 18362).
When you said "Close the computer", did you update it to a newer Windows?

No.

@jyuwono, i'm betting 'close the computer' implies either restart or close the lid.
@ogzhnndrms is there something in your event logs?  Can we maybe set up a teams call so we can see it?

Yes as i stated close and open i wrote longer but you are right i restarted.
I cannot rich event logs. Sorry.

@ogzhnndrms Merhaba, daha iyi aciklayabilecegini dusunuyorsan problemini bana Turkce yazabilirsin.
Ekran goruntusu saglayabilirsen aslinda sorunun tam olarak ne oldugundan emin olabiliriz. Ayarlar penceresi aciliyor ama ekranda elementleri goremiyor musun? Pencere tamamiyle beyaz mi? Elementler gorunmese bile uzerlerinde geldiginde imlecin degismesi gibi bir durum var mi? Boyle bir durum daha once rapor edilmisti de.

Actually if you could provide some screenshots, we could better identify the issue. Do you see the elements in the settings? Is the whole window blank? Is elements look clickable when you hover them(like cursor change), while they are invisible?

Bilgisayari kapatip actiginda problem ortadan kalkiyor degil mi?
Ve event loglara nasil erisecegini bilmiyorsun, dogru mudur?

What fixes the problem is restarting the computer and you don't know how to reach event logs right?

This may be a duplicate of https://github.com/microsoft/PowerToys/pull/4447/files

@enricogior, https://github.com/microsoft/PowerToys/issues/2439 is the root issue, lack of dll info could be the cause?

@crutkas
I doubt the lasck of DLL ifo can cause such a problem, but we are pushing the fixes for #2439, so if that is the cause now it should be fixed.
Reading again the description of this issue, it seems the same of https://github.com/microsoft/PowerToys/issues/3407 and not https://github.com/microsoft/PowerToys/issues/3384

@enricogior, ok, i linked back to the root issue you had in your comment before, glad you seem to agree. Yes i do agree #3407 and this seem to be the same issue.  Going to close this out in favor of that.


Hotfix for flow build failures

This:

Sets the correct flow version for npm
Fixes what looks like a type error in the getCommandArgs (entries in args can be set to null)

Looks good!  Go ahead and merge it


set rake default and test cleanup

@seuros thanks for your input here, but I've opted to take a different route on this.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_c76594f9-5aeb-4b47-b802-9c643cbaffc8/pull/1 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target_c76594f9-5aeb-4b47-b802-9c643cbaffc8.git

Docs Build status updates of commit 9b8fe80:
:clock10: Pending: waiting for processors (8 builds ahead of you)
:warning: Docs Build is busy, currently there are 8 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 9b8fe80:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-02-19-09-52-55 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-02-19-09-52-55

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add optional timezone parameter to date functions

We've added an (optional) timezone parameter to all XPath and OQL date/time functions:

seconds-from-dateTime (XPath)
minutes-from-dateTime (XPath)
hours-from-dateTime (XPath)
day-from-dateTime (XPath)
day-of-year-from-dateTime (XPath)
week-from-dateTime (XPath)
weekday-from-dateTime (XPath)
month-from-dateTime (XPath)
quarter-from-dateTime (XPath)
year-from-dateTime (XPath)
DATEPART (OQL)
DATEDIFF (OQL)

This change is planned for Mendix 9.22.0.

@Yiyun333 , good job reviewing the PR. I added a few minor comments.

@MariaShaposhnikova, thanks for the comments. I left one small point based on your comment. If you agree, I'll make the change accordingly throughout the PR.


[Kinesis]Fix kinesis sink can not retry to send messages

Motivation
Currently, when the kinesis sink connector fails to send a message, it will not retry. In this case, if retainOrdering is enabled, it will lead to subsequent messages can not be sent like the following:

17:09:40.923 [crm/messaging-service/messaging-service-reply-0] WARN  org.apache.pulsar.io.kinesis.KinesisSink - Skip acking message to retain ordering with previous failed message prod_extapi.reply.message-Optional[26380226003034]

Modifications

Add retry logic for the kinesis sink connector. When sending a message fails, it will retry to send.

Verify

Disconnect the network
Send a message to the input topic of the kinesis sink connector. It will output logs:

18:12:58.448 [public/default/pulsar-kinesis-sink-0] DEBUG org.apache.pulsar.io.kinesis.KinesisSink - Published message to kinesis stream test-io with size 3
18:13:16.619 [kpl-daemon-0003] ERROR com.amazonaws.services.kinesis.producer.LogInputStreamReader - [2021-04-28 18:13:16.618959] [0x00007b57][0x0000700009bf1000] [error] [AWS Log: ERROR](CurlHttpClient)Curl returned error code 28 - Timeout was reached
18:13:16.619 [kpl-daemon-0003] ERROR com.amazonaws.services.kinesis.producer.LogInputStreamReader - [2021-04-28 18:13:16.619002] [0x00007b57][0x0000700009bf1000] [error] [AWS Log: ERROR](AWSClient)HTTP response code: -1
Exception name:
Error message: Unable to connect to endpoint
0 response headers:
...

When the internal retry of KinesisProducer fails, it will go into the onFailure method of ProducerSendCallback and start retry.

18:13:28.742 [pool-2-thread-1] INFO  org.apache.pulsar.io.kinesis.KinesisSink - [test-io] Retry to publish message for replicator of Optional[persistent://public/default/test-kinesis-0]-Optional[2684354588] after 1000 ms.
...
18:14:07.141 [pool-2-thread-1] INFO  org.apache.pulsar.io.kinesis.KinesisSink - [test-io] Retry to publish message for replicator of Optional[persistent://public/default/test-kinesis-0]-Optional[2684354588] after 1914 ms.
...
18:14:39.385 [pool-2-thread-1] INFO  org.apache.pulsar.io.kinesis.KinesisSink - [test-io] Retry to publish message for replicator of Optional[persistent://public/default/test-kinesis-0]-Optional[2684354588] after 3713 ms.

Reconnect the network. It will send the message successfully.

18:14:47.102 [kpl-callback-pool-0-thread-0] DEBUG org.apache.pulsar.io.kinesis.KinesisSink - Successfully published message for test-io-shardId-000000000000 with latency 108652

It can also successfully send subsequent messages

18:14:52.166 [public/default/pulsar-kinesis-sink-0] DEBUG org.apache.pulsar.io.kinesis.KinesisSink - Published message to kinesis stream test-io with size 3
18:14:52.805 [kpl-callback-pool-0-thread-0] DEBUG org.apache.pulsar.io.kinesis.KinesisSink - Successfully published message for test-io-shardId-000000000000 with latency 640

@dlg99 PTAL

If I understood this approach correctly and to my best understanding of how the sink works, it will end up accumulating data in memory until the connection with kinesis is restored. If that takes too long, the PulsarSource will keep producing the data for the sink and eventually this will OOM. it needs a way (through the context?) to tell PulsarSource to pause.

@dlg99 @RobertIndie We can leverage the max unack message limitation to limit the memory of the connector when using retainOrdering=false, it needs users to use the Shared subscription for the connector. For retainedOrdering=true, we only retry the current message until success, so this will not introduce OOM issues.

Here I did some stress tests:

Start the sink connector with retainOrdering enabled.

Disconnect the network to let the kinesis producer fails to send messages.
Produce 1 million messages with rate 100000/s.

The sink connector will skip all the subsequent messages to retain ordering.

The memory of sink connector has not grown significantly.

When retainOrdering is disabled, there will be no retry. The changes made by this PR will not affect this case.

@dlg99 Please help take a look.

@eolivelli @codelipenghui I marked this issue for 2.7.2

Okay. Feel free to cherry pick. Otherwise I will do it tomorrow


Bugfix in version 2.x implementation

Bug fixed in the requestWithMethod:URLString:parameters:error: method.
The original code sent every request as a GET request and ignored the method parameter.

Oy! Thank you for the fix.


fix: use the correct target-platform for test

cc @0xbe7a 🤦 sorry!

Could we add cross-compile to the end-to-end tests?

For sure. Apparently we have some failing tests that I don't understand right now anyways :)


TypeError: data must be None or an array name (string), not b'NJet'

Ran into this while doing the problems for GSOC. I think the problem is that the library is not compatible with Python3 unicode strings, but I may be wrong.
Traceback
>>> import oamap.source.root, uproot, functional
>>> events = uproot.open("http://scikit-hep.org/uproot/examples/HZZ.root")["events"].oamap()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/joshua/.local/lib/python3.6/site-packages/oamap/source/root.py", line 187, in __call__
    generator = self.schema.generator()
  File "/home/joshua/.local/lib/python3.6/site-packages/oamap/source/root.py", line 184, in schema
    return oamap.schema.List(recurse(self.tree), starts="", stops="")
  File "/home/joshua/.local/lib/python3.6/site-packages/oamap/source/root.py", line 138, in recurse
    x = frominterp(name, branch, uproot.interp.auto.interpret(branch))
  File "/home/joshua/.local/lib/python3.6/site-packages/oamap/source/root.py", line 100, in frominterp
    return oamap.schema.Primitive(interpretation.todtype, data=name)
  File "/home/joshua/.local/lib/python3.6/site-packages/oamap/schema.py", line 346, in __init__
    self.data = data
  File "/home/joshua/.local/lib/python3.6/site-packages/oamap/schema.py", line 418, in data
    raise TypeError("data must be None or an array name (string), not {0}".format(repr(value)))
TypeError: data must be None or an array name (string), not b'NJet'

That's right. Another GSoC student ran into the same thing. uproot branch names are bytes (because ROOT files have no encoding) and OAMap hasn't been made aware of that.
It is a real bug, but for now just use Python 2. (Sorry!)

Tried changing basestring = str to basestring = (bytes, str), but then I got TypeError: a bytes-like object is required, not 'str'. Going to run input = input.encode() on all the relevant functions to keep python3 compat.

No longer relevant; that part of the code is gone and will be rewritten (with better Python 3 hygene in mind!).


emojis-keywords length and emoji-list length don't match

Hi, in Readme says

Complete list of emoji shortcuts. The list is a 1:1 map of emojis-list.

but
var keywords = require('emojis-keywords');
var emojis = require('emojis-list');

console.log(keywords.length) // <= 2477
console.log(emojis.length) // <= 3075

so obviously in not a 1:1 map, the others keywords not exist?

duplicate of https://github.com/Kikobeats/emojis-list/issues/10


Fix bug in str_boolean_series_stats

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

Project coverage is 100.00%. Comparing base (97a9691) to head (4fc8a71).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #391   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           58        58
  Lines         1511      1511
  Branches        59        59
=========================================
  Hits          1511      1511

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


Add dismantleBlockingWalls feature flag

This adds the first feature flag implementation. Which is "dismantleBlockingWalls" which enables creeps with WORK parts (if they end up stuck against a wall) to dismantle walls in their path (only in not owned rooms)

I think instead of making this a semi-manual optional feature we should instead just improve the remote dismantlement code, having remotes be abandoned until paths are cleared and making structures blocking paths a priority target.
I like the idea, but I think this is a misguided use of the feature flags. Do you agree?

well no, this is actually the intended behavior of feature flags -> to control (enable / disable) a specific feature which has no consequences to the rest of the code. While you are right in that this is just a temporary feature i think it's quite handy until we fix the reason for it beeing written. Once the original cause is fixed this can safely be removed again.

I'll just fix the issue now then :)


Test using 4D barycentric coordinates on tetrahedron to render vertices or edges

[x] Setup local 4D barycentric coordinates bx on the reference tetrahedron
[ ] Add vertex mode shading or discarding fragments based on distance from vertex
[ ] Add wireframe mode using distance from edge

Formula for distance in barycentric coordinates can be found here:
https://en.wikipedia.org/wiki/Barycentric_coordinate_system

Basic concept implemented in shaders and looks ok, pushed to master. Keeping this issue open until user facing parameter setup and shader generation pipeline is updated properly.

[ ] Use derivatives extension to avoid aliasing of distant edges

Can probably easily adapt the technique here to 4D barycentric coordinates:
http://codeflow.org/entries/2012/aug/02/easy-wireframe-display-with-barycentric-coordinates/

Wireframe looks good now. Dropping vertex shading using this approach as it looks weird. Remaining part here I consider part of a general refactoring of plot config so closing now.


Add support for anyio.get_cancelled_exc_class() in TRIO102, 103 and 104.

Fixes #122
rewrote critical_except a bit as I updated it, in large part because I personally failed to read the old version of the code :innocent:
Fix #106 for TRIO102 (#109 only fixed TRIO103 & TRIO104)
Thanks to #125 it was quite smooth to add a different suggestion for TRIO103 when anyio is the primary library.
As I started to write a assert_correct_message test helper I realized I had pretty bad code duplication, so checking of column, message and args are now all handled in assert_correct_attribute.
Improved how ignore_column is handled in anyio tests.
A slew of tests being moved around and modified and stuff so the necessary eval_files are handled with trio/anyio as appropriate. And some additional ones for #106+TRIO102

Added a separate error message when both are available.
But I'm unsure how to handle TRIO103 when both are imported, should bare excepts require that both have been handled in that case?

I'm unsure how to handle TRIO103 when both are imported, should bare excepts require that both have been handled in that case?

I think in this case it's safe to just catch anyio.get_cancelled_exc_class(), because if you're actually running Trio code that will return trio.Cancelled.

I'm unsure how to handle TRIO103 when both are imported, should bare excepts require that both have been handled in that case?

I think in this case it's safe to just catch anyio.get_cancelled_exc_class(), because if you're actually running Trio code that will return trio.Cancelled.

If you're running all three async libraries, and anyio's current backend is asyncio, and in the try: statement stuff is ran that could either raise trio.Cancelled or anyio.get_cancelled_exc_class(), it might bork? But that seems weird enough that I think not raising false alarms is more important.

addressed nitpicks and rebased on top of main to ensure coverage.


Some styling changes with some other odd stuff

I tried to implement pagination and search so there are probably a few things in the config files that you might want to remove.

thank you so much! Ill sort it out.


Error while installing using pip in kaggle

Instructions To Reproduce the Bug

What exact command you run:

!pip install farabio

Collecting farabio
Using cached farabio-0.0.3-py3-none-any.whl (45 kB)
Collecting albumentations==1.0.3 (from farabio)
Using cached albumentations-1.0.3-py3-none-any.whl (98 kB)
Collecting docutils==0.16 (from farabio)
Using cached docutils-0.16-py2.py3-none-any.whl (548 kB)
Collecting jupyterlab==3.1.6 (from farabio)
Using cached jupyterlab-3.1.6-py3-none-any.whl (8.6 MB)
Collecting matplotlib==3.4.3 (from farabio)
Using cached matplotlib-3.4.3.tar.gz (37.9 MB)
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [55 lines of output]
Traceback (most recent call last):
File "/opt/conda/lib/python3.10/site-packages/pkg_resources/init.py", line 3031, in _dep_map
return self.__dep_map
File "/opt/conda/lib/python3.10/site-packages/pkg_resources/init.py", line 2828, in getattr
raise AttributeError(attr)
AttributeError: _DistInfoDistribution__dep_map
  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/opt/conda/lib/python3.10/site-packages/pkg_resources/__init__.py", line 3022, in _parsed_pkg_info
      return self._pkg_info
    File "/opt/conda/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2828, in __getattr__
      raise AttributeError(attr)
  AttributeError: _pkg_info. Did you mean: 'egg_info'?

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "<string>", line 2, in <module>
    File "<pip-setuptools-caller>", line 34, in <module>
    File "/tmp/pip-install-q_o17q4m/matplotlib_92c8f5accd244278bcac3c74bd7998e1/setup.py", line 258, in <module>
      setup(  # Finally, pass this all along to distutils to do the heavy lifting.
    File "/opt/conda/lib/python3.10/site-packages/setuptools/__init__.py", line 152, in setup
      _install_setup_requires(attrs)
    File "/opt/conda/lib/python3.10/site-packages/setuptools/__init__.py", line 147, in _install_setup_requires
      dist.fetch_build_eggs(dist.setup_requires)
    File "/opt/conda/lib/python3.10/site-packages/setuptools/dist.py", line 812, in fetch_build_eggs
      resolved_dists = pkg_resources.working_set.resolve(
    File "/opt/conda/lib/python3.10/site-packages/pkg_resources/__init__.py", line 785, in resolve
      new_requirements = dist.requires(req.extras)[::-1]
    File "/opt/conda/lib/python3.10/site-packages/pkg_resources/__init__.py", line 2749, in requires
      dm = self._dep_map
    File "/opt/conda/lib/python3.10/site-packages/pkg_resources/__init__.py", line 3033, in _dep_map
      self.__dep_map = self._compute_dependencies()
    File "/opt/conda/lib/python3.10/site-packages/pkg_resources/__init__.py", line 3042, in _compute_dependencies
      for req in self._parsed_pkg_info.get_all('Requires-Dist') or []:
    File "/opt/conda/lib/python3.10/site-packages/pkg_resources/__init__.py", line 3024, in _parsed_pkg_info
      metadata = self.get_metadata(self.PKG_INFO)
    File "/opt/conda/lib/python3.10/site-packages/pkg_resources/__init__.py", line 1412, in get_metadata
      value = self._get(path)
    File "/opt/conda/lib/python3.10/site-packages/pkg_resources/__init__.py", line 1616, in _get
      with open(path, 'rb') as stream:
  FileNotFoundError: [Errno 2] No such file or directory: '/opt/conda/lib/python3.10/site-packages/numpy-1.25.0.dist-info/METADATA'

  Edit setup.cfg to change the build options; suppress output with --quiet.

  BUILDING MATPLOTLIB
    matplotlib: yes [3.4.3]
        python: yes [3.10.12 | packaged by conda-forge | (main, Jun 23 2023,
                    22:40:32) [GCC 12.3.0]]
      platform: yes [linux]
         tests: no  [skipping due to configuration]
        macosx: no  [Mac OS-X only]

  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

please simplify the steps as much as possible so they do not require additional resources to run, such as a private dataset.

To reproduce - simply run pip install farabio
Environment:
Provide your environment information using the following command:
Kaggle

No worries. Thank you for the update!


Skipping logs

While using codectrl I came across an issue where some logs would not show up in the gui. There are no errors or warnings present in either the gui or the console.
After some debugging I think It only happens when there are many requests hitting the server in very quick succession.
Trying to run the following code:
    for i in range(0, 100):
        codectrl.log(i)

In the gui I get a few missed numbers:

The same behaviour is present with both the python and the nodejs loggers, thus I think its either a codectrl problem or something with my operating system.

I will try to recreate this issue using the Rust logger and the Python one to see if it's logger-specific or CodeCtrl itself.
Also, I know this was a bit ago but can you remember whether or not you had another CodeCtrl instance open?

No. I don't, but that is a good point.
Ill try do some more tests today or tomorrow and get back to you :slightly_smiling_face:

Thank you. The reason why I ask is that I explicitly set REUSE_PORT on by default in the server portion of the code. I noticed that when one or more instances are open, the logs seem to be distributed to each instance at random. I will likely disable this, regardless of whether it is the cause of this issue or not.

That's fine. If you use reuse sockets though you should probably make sure the app is not already running when you launch. Could cause confusion :sweat_smile:

Agreed. Will have to implement some sort of check, or just disable it outright

Just tested this with the Python logger and the Rust logger, I don't seem to be getting the same issue. Possibly indicative of the multiple instances?
As I said earlier, I may either remove that ability or have a sort of check to prevent this confusion again if it's not your operating system being the cause.

Closed because I don't think this has been replicated since.


compose_tooltips: Improve tooltip logic for compose_reply_button.

Change compose_reply_button tooltip logic to show the correct tooltip. Earlier in organizations where DMs were disabled, a stale tooltip was being displayed.
Similar to #28523, When the user hovers over the compose_reply_button sometimes had stale tooltip content rendered on it. In this PR, we change the logic used to render this tooltip, to now render the tooltip content on the fly via instance.setContent() which should eliminate any such bug.
Earlier if the user hovered over the compose_reply_button when it was disabled and switched to a stream in which it was enabled before waiting for the tooltip delay, the next time the user hovers over the compose_reply_button the stale disabled tooltip is displayed instead of the enabled one.
This is fixed by checking if the compose_reply_button is enabled on the fly while rendering the tooltip.
Fixes #29238.]
Screenshots and screen captures:

- [x] [Self-reviewed](https://zulip.readthedocs.io/en/latest/contributing/code-reviewing.html#how-to-review-code) the changes for clarity and maintainability
      (variable names, code reuse, readability, etc.).
Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] Visual appearance of the changes.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

This is a lot of new code; can you explain the changes and why they're correct and the best possibly solution for this issue?
A good PR should have commit messages that explain the strategy for the change, and also just more writing about your debugging and what combination of factors creates the problem you're solving.

Updated the commit message as well as the PR description to be more descriptive.
This PR is basically an extension of #28523 for the compose_reply_button.

@sayamsamal Since this is an extension of your PR, are you up for reviewing this one?

Hey @kennethnrk, thanks for the work on this! I tested it locally, and it works as intended. I have suggested some changes; mostly just some renaming.

Thanks for the review, I have made the required changes.

I also noticed that the tooltip for the "Start new conversation" button doesn't get updated in the direct messages, when the direct messages are disabled. Are you up for adding a fix for this as well?

Sure, I'll create a new PR for that.

Can you explain precisely why the previous code didn't work? As I understand it, the get_tooltip_content function is called when showing the tooltip and would find the latest value of what template to use...

Can you explain precisely why the previous code didn't work? As I understand it, the get_tooltip_content function is called when showing the tooltip and would find the latest value of what template to use...

When the user hovers over any section and moves away before the tooltip delay, if the user hovers again on that same section get_tooltip_content is not called again. I can't figure out why, it might be something to do with the way tippy deals with delays.

https://github.com/zulip/zulip/pull/27046#issuecomment-1751446385 would possibly provide some context into this behavior. But generally speaking, instance.setContent() gives us more consistent results than changing the data-tooltip-template-id attribute in dynamic scenarios. FYI @timabbott.

OK, merged, thanks @kennethnrk and @sayamsamal, that explanation makes sense. In the future, it's worth putting that sort of explanation in the commit message/PR description -- the explanations for why something is necessary and correct are generally some of the most useful things to write down for sharing with reviewers.

I also noticed that the tooltip for the "Start new conversation" button doesn't get updated in the direct messages, when the direct messages are disabled. Are you up for adding a fix for this as well?

@sayamsamal When direct messages are disabled, the New conversation button displays the tooltip based on the last narrow visited eg New Channel Message or New Topic not the dm tooltip which is New Direct Message. Not displaying the dm tooltip makes sense as dms are disabled. Which tooltip should be displayed instead? There isn't any tooltip specifically for when dms are disable.

We don't disable the "Start new conversation" button in DMs, as you can always DM yourself or a bot.

It's possible we should make this banner more accurate, but it's probably not worth thinking about until we rework DM permissions in #24467.

We don't disable the "Start new conversation" button in DMs, as you can always DM yourself or a bot.

This, exactly. I have opened #29916 to track this; @kennethnrk FYI.


Wordnet is missing some words.

I feel like this is a bug, but Im still digging in.
wordnet.lookup('fought', function(results) {
    // no results.
}

http://wordnetweb.princeton.edu/perl/webwn?s=fought&sub=Search+WordNet&o2=&o0=1&o8=1&o1=1&o7=&o5=&o9=&o6=&o3=&o4=&h=
Related to #225  CC: @morungos

This might be the expected behaviour. Looking at @morungos (https://github.com/morungos/wordnet) I think it should be picked up in validForms, or it is, but then is being filtered out further down the stack.

I've cross commented on this on the other repo, but the comment is relevant and the resolution will be different here. "fought" is actually in Wordnet's morphological exception lists (specifically it's in verb.exc), which aren't part of the core data, and there's (as yet) no API for searching or using this in Wordnet itself. I've started to build this in the https://github.com/morungos/wordnet, but this is (currently) broken there too, in validForms handling, so I'll work to fix this asap there.

interesting, the new implementation of naturals wordnet module should make it easier to accommodate things like this. Ill try to handle it before releasing the new implementation.
tagging this for #211


Missing files in source code

Hi @uday610,
I'm currently working on supporting NPU for several networks using Vitis AI.
I noticed that I couldn’t find a docker container in the repository VAIP,
"Access the container via xdock-vitis-ai-sw ". Where I can find xdock-vitis-ai-sw repo?
Do you have plans to include it in the repo? Any guidance would be greatly appreciated.
Thanks in advance for your help!

RyzenAi includes a component called VAIP (Vitis AI partitioner). Its repository describes how to build it under Linux, and it mentions the "xdock-vitis-ai-sw" repository.
There is an unanswered question about this repository, so we decided to ask here.
To support new networks in RyzenAi, we want to deploy a development environment, and the partitioner is one of the most important components in our task.


Performance Issues Caused by Frequent Input Type Changes

I have a Wooting keyboard set up as follows:

What this means is that pressing WASD also inputs a gamepad analogue stick input.
This causes input_type_changed to be constantly emitted, which leads to  _load_icon being called repeatedly. As a result, I encounter lag spikes:

A quick and dirty fix I’ve implemented is to create a badResources cache  that remembers when a resource doesn’t exist, avoiding redundant checks. Here's the implementation:
var badResources = []

func _load_icon(path: String) -> int:

	if badResources.has(path):
		return ERR_FILE_NOT_FOUND

	if _cached_icons.has(path): return OK
	var tex = null
	if path.begins_with("res://"):
		if ResourceLoader.exists(path):
			tex = load(path)
			if not tex:
				badResources.append(path)
				return ERR_FILE_CORRUPT
		else:
			badResources.append(path)
			return ERR_FILE_NOT_FOUND
	else:
		if not FileAccess.file_exists(path):
			badResources.append(path)
			return ERR_FILE_NOT_FOUND
		var img := Image.new()
		var err = img.load(path)
		if err != OK:
			return err
		tex = ImageTexture.new()
		tex.create_from_image(img)
	_cached_icons[path] = tex
	return OK

To further improve performance, the current input type could be updated only once per physics frame or later
While the problem is currently only visible on a keyboard setup like mine I also see this issue coming up on handheld PC devices like the Steam Deck which also makes use of hybrid keyboard/controller input.

Ah, it looks like I was still using the old ControllerTextureRect because I had just copy-pasted the newer files. I'll close this issue now.


README: add two related projects

The loongson one is really fringe, so it's fine if you want to take it out.

Thanks!  I wasn't aware of the Loongson work, that's awesome. I think I'll reach out to the authors to see if they might be interested in collaborating; I'd be happy to add Loongson support to SIMDe that way everyone can benefit, not just GCC.
As for emscripten, I believe the current plan is actually to get all that code merged into SIMDe then have Emscripten just use SIMDe; they are actually already doing that for NEON.
Anyways, instead of this patch I think it would be better to just add a link in the README to the Alternatives page in the Wiki, and add these there.  If you're willing to update this PR to just point to the wiki I'd be happy to accept it, and of course feel free to add any relevant information to the wiki.

Regarding Loongson, it looks like the MMX-compatible functions were removed pretty quickly (in d65b9c), so we probably shouldn't focus on that too much.  It seems like the preferred path for Loongson is to use the functions in loongson-mmiintrin.h, which aren't x86-compatible.
Maybe @FlyGoat has some insight into where that code came from and why it disappeared so quickly? If it is still alive somewhere I'd be happy to link to them from the wiki, or maybe even merge them into SIMDe (depending on licensing).

Regarding Loongson, it looks like the MMX-compatible functions were removed pretty quickly (in d65b9c), so we probably shouldn't focus on that too much. It seems like the preferred path for Loongson is to use the functions in loongson-mmiintrin.h, which aren't x86-compatible.
Maybe @FlyGoat has some insight into where that code came from and why it disappeared so quickly? If it is still alive somewhere I'd be happy to link to them from the wiki, or maybe even merge them into SIMDe (depending on licensing).

Well because upstream suggested we shouldn't do it in GCC.

@Artoria2e5, do you want to submit a patch to tweak the README to link to the alternatives page, or would you like me to do it?
Either way, thanks again for filing this; it looks like we'll merge Loongson support into SIMDe soon thanks to this issue (and @FlyGoat's patches).

I think it would be more appropriate for you to do it.


Error: Names must match

Hi,
I have tried to convert my rest to graphql but its shows me an error and I dont know why, my swagger schema working well and is well built I think. Can you help me? I have attached my swagger.json and my types results ( renamed to txt to can be uploaded).
schema.txt
types.txt
Thanks!

Hi,
The thing is that in your schema it's pointed operationId with invalid for GraphQL { character:
 "/v{VERSION}/organizations/{ORGANIZATION_ID}/available_payment_methods" : {
            "post" : {
                "tags" : [
                    "Client"
                ],
                "operationId" : "V{VERSIONOrganizationsByORGANIZATION_IDAvailable_payment_methodsPost",

Swagger2graphql takes operationId if it exists and converts the path if not.


User interface localization

Without even talking about the data, we need to localize at least the UI.
There ton of Text constructed with variable in the middle of the string and I don't think it's a good pattern to have.
Anyway let's look into it. Never localized a SwiftUI app yet.

[x] English
[x] German
[x] French
[ ] Spanish
[x] Italian
[x] Russian
[ ] Dutch
[x] Chinese TW
[x] Chinese HK
[x] Japanese
[ ] Korean

First steps in #92
I‘m going to continue my work. You may give this issue an „in progress“ label.

Let us create a check-list in the issue (maybe someone can copy paste):

[x] English
[x] German
[ ] French
[ ] Spanish
[ ] Italien
[ ] Russian
[ ] Portuguese
[ ] Chinese
[ ] Japanese
[ ] Korean

Add / remove languages as desired.

I am able to provide ZH_TW Chinese localization but I am not good at Swift
Is that any template that I can fill in the translation?

@klin0816 here's the "template" file you use for Localization in iOS:
https://github.com/Dimillian/ACHNBrowserUI/blob/master/ACHNBrowserUI/ACHNBrowserUI/en.lproj/Localizable.strings
so for example replacing
"music" = "Music";
with
"music" = "音樂";
I'm sure if you were able to do that it'd help @TheVaan out

@klin0816 That would be awesome! As @jonnyklemmer mentioned, there are no Swift skills necessary. We changed the way translation works a little bit - the linked English localization file is not complete.
You have to choose between two ways:
First:

fork repo, navigate to /ACHNBrowserUI/ACHNBrowserUI
create a folder named zh_TW.lproj
copy and paste the files from the folder de.lproj to your new folder
to localize Localizable.strings:

the file containts hundrets of lines with "english string" = "german string"; (left: key, right: value)
just forget what I have written in German, simply translate what you finde in the key into the value
%@ (string) and %lld (number) are variables that should be inside your translation as well
there are 4 special keys, that can not be translated directly from the key: look into en.lproj/Localizable.strings to see the English value for the keys and translate them
one more "special thing": underneath // CategoryRow are the categorys with lowercased letter, I don't know how this is in Chinese but we use capital letter in the beginning because these strings are used as title in some views so the localization should also be capitalized

to localize InfoPlist.strings:

this one is simple, here you only have to write the description that is shown when the app asks for access rights to photos. So you need to tranlate the following: "Save images like furniture or generated images from the share function" and replace the German value with yours

@TheVaan Thanks for your guide anyway.
I will try to complete the translation ASAP.

Hello.
I want to Japanese Localization.
Would you tell me how to do it?

@mimikun that's great! Thank you! You can follow the tutorial I posted above. Use as name for your folder ja.lproj - you don't need Xcode, it can be done with any editor, case the strings file is plain UTF.

Or UTF-16 in case of Japanese/Chinese, and it works. Just pulled the Chinese items and now we have it in the app @klin0816 :)

@TheVaan
Thanks.
I'll try to complete the translation ASAP.

I am able to provide “Chinese Simplified” and I am familiar with swift. But there is no “Chinese Simplified” option in your comments☹

@kartbnb I can add it. The amount of Chinese language variants is not that transparent to me 😅
You are welcome to create a pull request with translated data!

@kartbnb I can add it. The amount of Chinese language variants is not that transparent to me 😅
You are welcome to create a pull request with translated data!

Just a simple question on how to add new Localizable. I just need to create a new Directory and named it and then add a "Localizable.strings" file into it?

You have two options:

simply add the folder then import the localization; file doesn’t have to be translated at this point, it only has to exists (or @Dimillian can import)
add a new localization to Localizable.Strings via menu

Hi, I can provide the Italian localization, if anybody isn't working on it just yet. 😀 The folder name for the Italian language is it_IT.lproj ?

@MrOgeid this would be awesome! There is no one translating to Italian (as far as we know). The folders name has to be it.lproj

@TheVaan Ok! Thank you for the correct folder's name! I'll try to translate all the string as soon as possible!

And for items and villagers, they should already display in Italian. You can confirm @MrOgeid ?

@Dimillian Villager's name are displaying in Italian but I see the items in the Catalog in English.

@MrOgeid On latest commit I've enable Italien so you'll find the correct folder and file. And it also enable Italien items :)

@Dimillian Sorry, probably I didn't understand.😅 I don't have access right know to Xcode as I'm not a very expert software developer, I'm more a graphic designer and copywriter.

Well if you start your translation from the last commit, you'll find the It.lproj folder with the file ready :)

Thanks @Dimillian !

Hi @Dimillian I translated in Italian all the strings from Localizable.strings in the "de.lproj" folder into the same file in the "it.lproj" folder. But I'm not quite sure if I made a correct pull request.😬

Congrats to @mimikun for adding japanese in #136 !!

Added credits in our readme :) https://github.com/Dimillian/ACHNBrowserUI#localizations-credits

I'll try to tag on this issue everything I'm adding to French localization (which should be everything we have to localize) so it give a change to anyone who wants to updated their localization file to do so :)

I figure this thread is better than opening a new issue but there are quite a few strings that are in other languages that aren't in the English file (e.g: "Friendly Reminder") Should the English strings file be expanded?

No. Swift uses the key as translation if there is no localization. So we only add a key to the English localization if it is an unreadable key.

I think I'm done with Korean one. Is there anything missing I have to do?

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @hoangpq, @mikalv, @shoman4eg, @karl0-dev, @christophwitzko, @HintikkaKimmo, @hero5512, @0x4E33, @kaito2, @maxweng, @kevink1103, @adminOfBincentive, @deckarep, @binsonze, @uzbekdev1, @zachhhhh, @baranovskis, @kuolun, @miguelmota, @Jimexist, @yepp4you, @Czechh, @andrazk, @valtab, @WhiteCrow, @ronghuazhao, @summertao, @yrxwin, @bubble501, @yangrq1018, @k-terashima, @jcoder76, @sergiotm87, @rich678s, @guayadeque, @xgdgsc, @realspal, @FlowerWrong, @HsingPeng, @kevinbg012, @youfoundron, @frandieguez, @RebornFlamme, @trunkszi, @alexrigler, @oscar3x39, @davedele, @mehmetcanyegen, @haiheipijuan, @andyidea


Header cleanup

Changed what the page headers said to remove WIP. Updated paragraph objects slightly.
Fixes #69

lgtm!


show table name in delta_scan

it will be nice to show the view/table name when scanning delta

Great idea, this is pretty straightforward. I've a PR up in duckdb that enables this. We can also look into printing other stuff like the table version and maybe even the partitioning of the table


Error Code documentation

Is there any documentation on the error codes posted by the app. e.g. scope not defined, Failed not_allowed?

Usually this app just pass errors from Slack. You should see Slack document.


Unable to Find All External Library Modules in VSCode + Yarn Berry + Yarn Workspace + @tanstack/react-query 4.x

Describe the bug
Hey there,
I hope this message finds you well. I've come across an issue that I'd like to share with you. Although I'm going for a slightly humorous tone, I still want to maintain a professional vibe. Here's the summary:
In a nutshell, we're facing a problem where external library modules cannot be found in the VSCode + Yarn Berry + Yarn Workspace + @tanstack/react-query 4.x combination.
As a frontend developer, I'm currently using @tanstack/react-query in our project. Our setup involves Yarn Berry with Yarn Plug 'n' Play (PnP), and we have multiple monorepos within our repository. Here are some key details about our environment:
Yarn version: 3.4.1
Next.js version: 13.0.6
React version: 18.2
TypeScript version: 4.9.5
VSCode version: 1.78.0
@tanstack/react-query version: 4.29.5
@tanstack/react-query-devtools version: 4.29.6
We recently migrated from react-query 3.x to @tanstack/react-query 4.x and successfully deployed the new version. Our users are happily using it as intended without any issues.
However, there's a significant problem we encounter during development. Since most of our team members prefer using VSCode, allow me to explain the situation using a humorous example:
Imagine we have two repositories, "A" and "B." Now, let's say we open the following files in VSCode:
/apps/a/index.ts from repository A
/apps/b/index.ts from repository B
In this scenario, if we start indexing the "a.ts" file, the import paths within repository A work perfectly fine. However, all external libraries located in repository B suddenly become elusive, resulting in a frustrating "cannot find module" error.
Conversely, if we restart VSCode and index the "b" repository's file first, all TypeScript files within repository A fail to locate the paths for external libraries.
We've made sure to upgrade TypeScript 5.x, Yarn 3.5.x, Yarn's SDKs (via yarn dlx @yarnpkg/sdks), and even VSCode to their latest versions, but the problem persists. Interestingly, when we downgrade to react-query 3.x, all the issues disappear. However, we are determined to stick with @tanstack/react-query 4.x and continue using the latest version.
While it could be considered a potential issue with VSCode, it's evident that the problem arises only with @tanstack/react-query 4.x. It's worth noting that we don't face any issues when using WebStorm. With that said, if you have any similar experiences or insights regarding this issue, we would be extremely grateful for your assistance. The current situation has caused significant mental stress for our team of nine.
Thank you for taking the time to read this message, and we genuinely hope you can help us out.
Best regards,
Your minimal, reproducible example
Issues in the development environment
Steps to reproduce
In other monorepos excluding the repository where indexing initially starts, installed modules cannot be found (imported), and type inference is not possible.
Expected behavior
Regardless of any monorepo, module imports and type inference should work in all repositories.
How often does this bug happen?
Every time
Screenshots or Videos

After running vscode, the first repository that is indexed works fine.

However, in all other repositories opened after that, the import paths cannot be found correctly.
It is not just a problem specific to repositories like A, B, C, but only the repository that vscode reads first works, and the rest of the repositories do not work.
Platform

OS: macOS
Yarn version: 3.4.1
Next.js version: 13.0.6
React version: 18.2
TypeScript version: 4.9.5
VSCode version: 1.78.0
@tanstack/react-query version: 4.29.5
@tanstack/react-query-devtools version: 4.29.6

Tanstack Query adapter
react-query
TanStack Query version
4.29.5
TypeScript version
4.9.5
Additional context
No response

I hope this issue gets resolved.

external library modules cannot be found in the VSCode + Yarn Berry + Yarn Workspace + @tanstack/react-query 4.x combination.

We cannot analyze this without a proper, standalone, minimal reproduction. Please provide an open source repo with this setup that clearly shows the errors you're facing. I will re-open the issue once that is provided.


Invalid Response status when attempting to run oobabot

Giving your fork of oobabot a try today and it seems to be attempting to talk to api/v1/stream which does not look like a valid endpoint when looking at localhost:5000/docs
I believe it should be using localhost:5000/v1/completions but I'm not sure where to configure that?
←[33;40m2024-02-22 21:10:18,052←[0m←[37;40m  INFO ←[0m←[37;40mStarting oobabot, core version 0.2.3←[0m
←[33;45m2024-02-22 21:10:18,054←[0m←[37;45m WARNING ←[0m←[33;45mPyNaCl is not installed, voice will NOT be supported←[0m
←[33;40m2024-02-22 21:10:18,054←[0m←[37;40m  INFO ←[0m←[37;40mOobabooga is at http://localhost:5000←[0m
←[33;40m2024-02-22 21:10:20,092←[0m←[37;40m WARNING ←[0m←[33;40mCould not connect to Oobabooga server: [http://localhost:5000]←[0m
←[33;40m2024-02-22 21:10:20,092←[0m←[37;40m WARNING ←[0m←[33;40mPlease check the URL and try again.←[0m
←[33;40m2024-02-22 21:10:20,094←[0m←[37;40m ERROR ←[0m←[31;40mReason: 403, message='Invalid response status', url=URL('http://localhost:5000/api/v1/stream')←[0m

You're right, it is located here:
https://github.com/jmoney7823956789378/oobabot/blob/ff6bbe5e29d98d4a90345452466f0b4680ee7cf7/src/oobabot/settings.py#L584
When you use --generate-config it should populate new options:
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# oobabooga
# .
oobabooga:

  # Use the OpenAI API instead of the Oobabooga API.
  #   default: True
  use_openai:

  # OpenAI API key. Required if use_openai is True.
  #   default: awesome_api_key
  api_key:

  # OpenAI API completions endpoint. Defaults to the official OpenAI API URL.
  #   default: http://localhost:5000/v1/completions
  openai_endpoint:

  # Base URL for the oobabooga instance.  This should be ws://hostname[:port] for plain
  # websocket connections, or wss://hostname[:port] for websocket connections over TLS.
  #   default: ws://localhost:5005
  base_url:

  # Base URL for the oobabooga instance.  This should be ws://hostname[:port] for plain
  # websocket connections, or wss://hostname[:port] for websocket connections over TLS.
  #   default: http://localhost:5000
  base_blocking:

I realize I was being very stupid and not pip installing your fork of oobabot but just oobabot so even though I cloned your fork and had your src in my local dir I was actually installing the upstream broken bot... >.<
It works great, now to see if I can get it running as an extension in the text-gen-ui

@Phixia that's kinda my fault too, i forgot to update the readme... either way, glad to help!


File retriever should check for valid HTTP status code

Steps to Reproduce:

Archive your soup

Expected Result:

All images are saved

Actual Result:

More than 50% of the images seem corrupted and can't be opened.

Note:
The files (in this case images) are in fact not corrupted but contain a HTML page stating that there was an error. They seem to be sent with a HTTP Status Code 5xx (502 in this case) that should prevent the retriever from persisting the response to the file system.

Fixed in d325a0b.
Thanks for the report.

It is not fixed completely, since the file is still created with 0 bytes length.


P1 Throttling in battery mode

It looks like the laptop is thermal throttling at 60 Celsius.
rdmsr -f 29:24 -d 0x1a2 gives 5, which is the default value on lenovo-throttling-fix

I see the power never exceeds 10W on battery and occasionally it says Current is Limited.
Thermal: OK - Power: OK - Current: OK - Cross-comain (e.g. GPU): OK  ||  VCore: 713 mV - Package: 9.8 W - Graphics: 0.1 W - DRAM: 1.2 W
Thermal: OK - Power: OK - Current: OK - Cross-comain (e.g. GPU): OK  ||  VCore: 713 mV - Package: 8.9 W - Graphics: 0.1 W - DRAM: 1.2 W
Thermal: OK - Power: OK - Current: OK - Cross-comain (e.g. GPU): OK  ||  VCore: 714 mV - Package: 9.4 W - Graphics: 0.1 W - DRAM: 1.2 W
Thermal: OK - Power: OK - Current: LIM - Cross-comain (e.g. GPU): OK  ||  VCore: 989 mV - Package: 9.1 W - Graphics: 0.1 W - DRAM: 1.1 W
Thermal: OK - Power: OK - Current: LIM - Cross-comain (e.g. GPU): OK  ||  VCore: 998 mV - Package: 9.1 W - Graphics: 0.1 W - DRAM: 1.2 W

I don't know why your current limit gets hit - there might be a stupid reason like: bad or weak power supply or bad regulators on the mainboard but it might also be some other process limiting you.

I agree, this is very strange at just 9W! What about on Windows?

This only happens in battery mode, not in AC mode.
On windows, it is showing the same behavior: https://imgur.com/a/KTii2Ms

On Windows, after installing Lenovo Power Management, the system can output ~30W of power.I think the same thing can be done in Linux too.

This only happens in battery mode, not in AC mode.
On windows, it is showing the same behavior: https://imgur.com/a/KTii2Ms

very strange but it could be reasonable in some conditions:
low or high battery or ambient temperatures, small battery, degraded battery, some strange power saving forced from somewhere

In BIOS you can set the power profile on battery mode. Try to set it to the same value of AC. I guess Lenovo Power Management is fiddling some values in the EC.

I already matched the power policy on battery the same as on AC before installing this service.
Now I got it running at a maximum of 20 W. Not entirely sure about what I did. But I installed dbus-python and install the whole service again.


How to upload a label config file

How to reproduce the behaviour
<!-- Before submitting an issue, make sure to check the docs and closed issues and FAQ to see if any of the solutions work for
I have a json file that contains all the labels types I want to use, and while I import it successfully through the gui is seems like there is no way to is through the client

https://github.com/doccano/doccano-client/pull/63
Depending on the project type you can use a particular group of endpoints. Look for functions with span_type for SequenceLabeling, category_type for DocumentClassification or relation_type. If you want to upload a config file use the functions post_span_type_upload, post_category_type_upload or post_relation_type_upload.