text:
BBQ run was not included in Figure 40

We have BBQ results on the website: https://crfm.stanford.edu/helm/v1.0/?runs=1&runSpec=bbq%3Asubject%3Dall%2Cmethod%3Dmultiple_choice_joint%2Cmodel%3Danthropic_stanford-online-all-v4-s3
but it was not included in Figure 40 of the paper https://arxiv.org/abs/2211.09110.

I'm having trouble reproducing this locally. BBQ results for all models show up:

When generating plots, I use the tables from the Results section of the website. Taking a closer look, I see that Anthropic (+others) were missing from v1.0 but are actually there for v1.1.
So I can just regenerate the plots using the v1.1 data and this should be fixed.

When generating plots, I use the tables from the Results section of the website. Taking a closer look, I see that Anthropic (+others) were missing from v1.0 but are actually there for v1.1.
So I can just regenerate the plots using the v1.1 data and this should be fixed.

I think the results are showing up because I reran with this fix: https://github.com/stanford-crfm/helm/pull/1233, but results are now missing in additional experiments: https://crfm.stanford.edu/helm/v1.1/?group=ablation_multiple_choice

Ah, I see, so the way to reproduce this is to just summarize v1.1 with main?
This gives me the following which has Anthropic but is missing BLOOM (even though we have a corresponding run from what I can tell). I can dig into this...

Ah, I see, so the way to reproduce this is to just summarize v1.1 with main?
This gives me the following which has Anthropic but is missing BLOOM (even though we have a corresponding run from what I can tell). I can dig into this...

That's correct. I debugged a bit, and I think it's because we also run these in additional experiments: https://github.com/stanford-crfm/helm/blob/main/src/helm/benchmark/presentation/run_specs_extra.conf#L265. The group is ablation_multiple_choice which changes the visibility in this table.

Updated: https://crfm.stanford.edu/helm/v1.0/?group=bbq&suite=v0.2.0

authors: dtsip teetone

repo: stanford-crfm/helm


text:
fix some tests in prep for new initialization,

which caught some problems
tagging @rjpower . Turns out we need to use approx=True for gelu in JAX to really match Gemma

(also i know the hasattr is gross, I'll clean it up)

yeah, these things are kind of finicky. It's so easy to have something that seems right but it's wrong in some tiny detail like this. It doesn't help that gelu and gelu_new are completely confusing

source: gharchive/pull-request

repo: stanford-crfm/levanter

license_type: permissive

license_source: github-api


text:
Requesting A Resume Watching Feature

Summary
Like you could press continue watching and it would resume from the exact time and episode you left it
Please confirm the following

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.

It already does this..

source: gharchive/issue

authors: jefftheev oathzed

repo: stantanasi/streamflix


text:
Transfer domain is not UX friendly

When I have no identities available I'm a bit stuck and I do not know what to do

The cool thing here would be to simply send the NFT cause people don't understand the fact that you can switch from starknet id to starknet id

**FINAL UPDATE **
Instead of an identity transfer, you'll simply need to do a Textfield that takes addresses and .stark domains + a button that will trigger three transactions in a multi-call :

Approve (if needed)
Send the NFT to the account needed
Change the resolved address to the address you're sending the NFT (Using set_address_to_domain).

The component changeAddressModal.ts could be an example of how to proceed.
This PR is pretty easy and should be an onboarding PR for a new contributor !

I'll be glad to take on this one 👍🏽

license: MIT


text:
bug: LSP formatting doesn't work for Helix

Bug Report
Cairo version:
main head at a621d15
Steps to reproduce:
First install the language server:
$ cargo install --locked --path crates/languageserver

In the Helix editor, set the language server of Cairo:
name = "cairo"
language-server = { command = "languageserver" }

Then open some unformatted Cairo file and try to format the file.
Current behavior:
The file does not change.
Expected behavior:
The file changes to the formatted text.
Related code:
Pretty sure this is causing the issue:
https://github.com/starkware-libs/cairo/blob/a621d159b7c206df59578456f4ba8351ecc5dcfa/crates/languageserver/src/lib.rs#L320-L326
Other information:
N/A

The end position of the edit here is out of bound. I guess the intend here is to indicate a "full document replacement". I'm checking the LSP spec to understand if this is allowed.

Quoting the spec v3.17:

All text edits ranges refer to positions in the document they are computed on.

I guess u32::MAX doesn't count towards "positions in the document". So I guess the bug is on the Cairo LSP side instead of Helix.

Am working on a fix now. Will submit PR :)

Thanks!

authors: spapinistarkware xJonathanLEI

repo: starkware-libs/cairo


text:
build: rename package names to include starknet_ prefix

This change is

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

Project coverage is 67.39%. Comparing base (b1c4b84) to head (f1b8efa).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #209   +/-   ##
=======================================
  Coverage   67.39%   67.39%
=======================================
  Files          25       25
  Lines         917      917
  Branches      917      917
=======================================
  Hits          618      618
  Misses        273      273
  Partials       26       26

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

repo: starkware-libs/mempool


text:
chore(monitoring): use constants

Stack:

#1864 ⬅
#1863
#1862
#1861
#1860

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

repo: starkware-libs/sequencer


text:
IKEA LED1623G12 # Model LED1623G12  Not showing up properly

Issue description
When I add the LED1623G12 it does not show up as expected. It shows up awith 2 swtiches, one with selector, and another one that shoud be the dimmer.   Unfortunatly I can not tutn of the light
Additional information
Zigbee2MQTT version:  Zigbee2MQTT version 1.18.3 (commit #f2e39af1)
Python version: 3.8.5.
Domoticz version:  Latest
Plugin version: Latest

Could you please update plugin and try one more time

Fixed, lights are dimmable now

Yes, please raise a new issue as looks like it is a different one

Will raise new issue

authors: HJKLMN stas-demydiuk


text:
my rdp conf is all green but i cannot login

I launch the remote desktop and i get to the login screen with no login bars to enter password

Please, convert your Microsoft account to a local account.

Duplicate of https://github.com/stascorp/rdpwrap/issues/1881

One termService version = one opened issue...

authors: MrDOntDIe sashaqwert

repo: stascorp/rdpwrap

license_source: bigquery


text:
10.0.22621.3447 not supported & not listening

尝试了 https://github.com/stascorp/rdpwrap/issues/2549 的方法， not supported 没有了，但是 not listening 还是没变。使用的是window 11，上周六更新了 window 自动更新后就连不上去了。

rdpwrap.ini 最后一行必须是空行，修改后就可以了。

[10.0.22621.3447]
SingleUserPatch.x64=1
SingleUserOffset.x64=C3F3
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=1C2E5
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=9D661
LocalOnlyCode.x64=jmpshort
SLInitHook.x64=1
SLInitOffset.x64=29ED0
SLInitFunc.x64=New_CSLQuery_Initialize
[10.0.22621.3447-SLInit]
bServerSku.x64=12BF50
bRemoteConnAllowed.x64=12BF64
bFUSEnabled.x64=12BF74
bAppServerAllowed.x64=12BF5C
bMultimonAllowed.x64=12BF68
lMaxUserSessions.x64=12BF54
ulMaxDebugSessions.x64=12BF70
bInitialized.x64=12BF4C

[10.0.22621.3447] SingleUserPatch.x64=1 SingleUserOffset.x64=C3F3 SingleUserCode.x64=Zero DefPolicyPatch.x64=1 DefPolicyOffset.x64=1C2E5 DefPolicyCode.x64=CDefPolicy_Query_eax_rcx LocalOnlyPatch.x64=1 LocalOnlyOffset.x64=9D661 LocalOnlyCode.x64=jmpshort SLInitHook.x64=1 SLInitOffset.x64=29ED0 SLInitFunc.x64=New_CSLQuery_Initialize
[10.0.22621.3447-SLInit] bServerSku.x64=12BF50 bRemoteConnAllowed.x64=12BF64 bFUSEnabled.x64=12BF74 bAppServerAllowed.x64=12BF5C bMultimonAllowed.x64=12BF68 lMaxUserSessions.x64=12BF54 ulMaxDebugSessions.x64=12BF70 bInitialized.x64=12BF4C

🙏

authors: JasonYadi learnselfs


text:
Add back permissions feature

It got removed from Spatie's Newsletter package, needs to be added back.
Likely do this in concert with #104

Can you flesh this one out a bit more - I'm happy to work on it but I'm not familiar enough with the project to know what this means.

Sure, hop on Discord if/when you'd like to tackle, but essentially the code here: https://github.com/statamic-rad-pack/mailchimp/blob/925e06ac8cecfb26953665d42de1c90bd10f15fc/src/Subscriber.php#L131 needs to be updated to use the mailchimp API instead of the Spatie package, because the package removed that feature.
My plans was to copy the code from the v4 version of the package, and update appropriately.

authors: edalzell ryanmitchell

repo: statamic-rad-pack/mailchimp


text:
[7.x] Add Publish State permission

Matching the canManagePublishState from core and replicating this PR: https://github.com/statamic/cms/pull/10424

@duncanmcclean let's talk about this one, as I believe we'd need a migration script otherwise it's breaking.

let's talk about this one, as I believe we'd need a migration script otherwise it's breaking.

Yes, we'd either need to ship with an upgrade script or include this PR in the next breaking changes release (which'll have the nested fields fix).

authors: duncanmcclean edalzell

repo: statamic-rad-pack/runway


text:
Publish tree migrations under their own tag

This pull request moves the migration for the trees table to its own publish tag, to allow for it to be published independently of the navigations table.
This PR also renames the migration to simply create_trees_table since the table is called trees and not navigation_trees. Feel free to rename this back if you think it'll cause issues.
Builds on the changes introduced in #249.

I wonder if we should take the chance to switch to a more conventional migrations approach and have them with fixed dates?

Yeah, I think that might be a better approach. It's the way Laravel handles it with their first-party packages. I'll close this PR and make that change in a separate PR.

repo: statamic/eloquent-driver


text:
CreateModel causes SvelteKit to fail during build

Description
Hi there. Firstly, thanks for Xstate. It's made my life considerably easier.
For context, I am encountering this issue using SvelteKit. When creating machines using "createMachine" there is (obviously) no problem and all works well.
Expecting that this may be beneficial moving forward, I have recently started refactoring these machines using the "createModel" pattern. Although everything runs smoothly in dev, what I have discovered after a few days work is that "createModel" causes an error to be thrown during a prod build.
If this is some simple config thing I have overlooked I apologise. Hopefully it's something easy to address as it would be great to continue down this refactoring path seeing as you the docs mention that it "is meant to improve the developer experience".
Expected Result
That no build error is thrown.
Actual Result
This error is thrown during the build process:
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '... /node_modules/xstate/lib/model' imported from .../.svelte-kit/output/server/chunks/index-30886392.js Did you mean to import xstate/lib/model.js?
Reproduction
I created this tiny repo that demonstrates the issue well. You can simply comment in/out the references to the machines being created in the two different ways.
https://github.com/heinschulie/carbon
Additional context
"xstate": "^4.26.1"

Your home.model.ts is being executed within node itself and since you have set "type": "module" in your package.json this gets loaded using the new node's ESM loader semantics. Therefore, to make it work you need to apply this diff:
diff --git a/src/lib/machines/home.model.ts b/src/lib/machines/home.model.ts
index 1745f74..b7c3619 100644
--- a/src/lib/machines/home.model.ts
+++ b/src/lib/machines/home.model.ts
@@ -1,5 +1,5 @@
 import type { ContextFrom, EventFrom } from 'xstate';
-import { createModel } from 'xstate/lib/model';
+import { createModel } from 'xstate/lib/model.js';

 export const homeModel = createModel(
     {

We are going to improve the story around this but XState v4 has been released before node's ESM support. We couldn't anticipate how it would work and unfortunately, it has been shipped in a way that is not compatible with the existing ecosystem. If we want to make it work - we need to adapt to it but this can only be done in the next major version of XState as changing things like this is very delicate and this could be a breaking change for the existing users.

@Andarist - thanks for the super quick response. Especially at this time of year. All works well now. Really looking forward to v5.

authors: Andarist heinschulie

repo: statelyai/xstate


text:
Explain behavior in code documentation

Problem
Some code comments may rely too much on knowledge of the protocol specs.
Developers tend to not check protocol specs unless tackling very specific scenarios.
Solution
Explain behaviour and usage of the API from a dApp dev point of view.

@jemboh: what are your thoughts on the matter as you have been playing around with the library? I believe the docs are better now and assume less knowledge of the specs from the dev.

I would suggest to park this one for now and focus on getting waku.guide up and running first.
Then it makes it easy to include guide link in the docs.

repo: status-im/js-waku


text:
Problema na execução dos métodos em ambiente de produção

Bom dia a todos!
Este problema que estou enfrentando já deve ter sido reportado aqui alguma vez, mas vamos lá.
Estou executando os métodos da maneira como indica nos exemplos em ambiente de produção com os dados que recebi dos correios, mas sempre acaba excedendo o tempo máximo de execução e não retorna os dados necessários, apenas a mensagem Maximum execution time of 60 seconds exceeded (isto apenas em ambiente de produção, em ambiente de homologação está funcionando sem problemas). Isso está acontecendo nos exemplos de:

verificaDisponibilidadeServico()
buscaCliente()
consultaCep()
getStatusCartaoPostagem()

Já os métodos restantes (principalmente o de solicitarEtiquetas()) não funcionam tanto em ambiente de produção quanto de homologação. Segui as instruções como indica nos exemplos e na documentação oficial do web service, mas não obtive sucesso.
Alguém que tenha enfrentado algum desses problemas e conseguiu solucionar, pode me ajudar?

Você percebeu se isso ocorre seguidamente, ou se esperar uns 3 minutos, depois da primeira tentativa, ele executa corretamente?

authors: islimn rodrigojob

repo: stavarengo/php-sigep

license: mit


text:
feat(workload) create catalogue item

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

We've tried to mirror the API routes as example directories, hence there is no route workload_catalogue_version. Can you please move the workload_catalogue_version files (keep the same file name) into the workload_catalogue directory?

Instead will move them all into the workloads folder to replicate the structure of the sdk

repo: stax-labs/lib-stax-python-sdk


text:
Twice Index file

ver. 1.4.4.4  When choose Filter Setup --> Vaporsynth and Source - automatic and add a file -everything is fine. - Index with ffmsindex create  ( filename.ffindex)  in temp directory
But if leave Source as default - ffms2 then Index with ffmsindex create ( filename.ffindex)  in temp directory
after that write "Writing index... done." and feel like hang, but in that time again read file and create (filename.mkv.ffindex) in source directory from which I add file

I added support for automatic source filter in filter setup profiles and made automatic default (without to force to reset the default filter setups), I think this was the reason and it also had a bug causing a crash, I'll upload a new build shortly.

Should be up in 2 minutes.

I tested new build and it`s work !  In automatic and in ffms2 as source create one index file.
Issue solved
Thanks for your work!!


text:
React 0.14

Hey, I'm using this in my project and since I'm updating to react 0.14 made some changes for this to comply, check it here: https://github.com/relax/react-colorpicker
I think it's only missing the documentation and examples, if you want make some changes there and then I can PR to merge here :)

@bruno12mota
Maybe create straight PR, so the diff, and comments are all in one place.
Did you get your version working with React 0.14 ?
I am getting:
Uncaught Error: Invariant Violation: ColorPicker.render(): A valid ReactComponent must be returned. You may have returned undefined, an array or some other invalid object.

repo: stayradiated/react-colorpicker


text:
Cannot pass negative number as a command line parameter value

I created a simple adder function:
module.exports = (params, callback) => {
    const x1 = Number(params.kwargs.x1);
    const x2 = Number(params.kwargs.x2);
    console.log(`x2 = ${x2}`);

    callback(null, x1 + x2);
};

I can't figure out how to pass negative numbers in as parameter values.  Here's what I'm trying:
c:\> lib . --x1 3 --x2 -2

The resulting output is:
x2 = 0
3

lib appears to be interpreting -2 as another parameter rather than as a parameter value for x2.  Do I need to escape the -2 value somehow?

Should be fixed as of; https://github.com/stdlib/lib/commit/ccee1fe9ef67fd67a658640fd026acd31151bce7

Works great now - thanks for your help!

authors: keithwhor thisdavej

repo: stdlib/lib


text:
Setup firebase admin SDK to manage firebase users

Currently, I was failed to setup firebase-admin due to importing error, and I'm not able to find the root cause

This is set in backend server


text:
Typescript export LocalizedStrings

Hey,
I am new to Typescript, but having problems using the code from the second comment: Issue 42
There is some error in LocalizedStrings.d.ts:
`export type LocalizedStrings = LocalizedStringsMethods & T;
interface LocalizedStringsFactory {
    new <T>(props: GlobalStrings<T>): LocalizedStrings<T>;
}

var LocalizedStrings**Factory**: LocalizedStringsFactory;
export default LocalizedStrings**Factory**;`

The LocalizedStrings should be renamed to LocalizedStringsFactory, otherwise we cannot use both (type and var) at the same time.
My own code:
`
// strings.ts
import { enStrings } from "./en";
import { deStrings } from "./de";
import LocalizedStringsFactory, {LocalizedStrings} from "react-localization";
export interface LocaleStrings {
key1: string;
key2: string;
}
export const strings: LocalizedStrings = new LocalizedStringsFactory({
en: enStrings,
de: deStrings
});
`

Hi @Larsrdev,
sorry for the delay.
You're right but it would be a breaking change.
In typescript types can be inferred by the instantiated value so there's no need to declare
export const strings: LocalizedStrings
you can just say:
export const strings = new LocalizedStrings(
Let me know if I'm missing anything.
Thanks
Stefano

Check the suggested solution to work with Typescript:
here

Yea man,
you are right. Thanks 👍
The suggested solution needs some little change:
import LocalizedStrings, { LocalizedStringsMethods } from 'react-localization';

export interface LocaleStrings extends LocalizedStringsMethods {
    key1: string;
    key2: string;
}

export const strings: LocaleStrings = new LocalizedStrings({
    en: enStrings,
    de: deStrings
});

You must post above example to main page. I wasted 2days to fix this problem

You must post above example to main page. I wasted 2days to fix this problem

authors: Larsrdev qja0707 stefalda

repo: stefalda/react-localization


text:
Add rounded edges at the ends

Hi!
Could you add in these versions these rounded edges as they are in the preview?
Thanks

The radius property could make edges to round.

Its works! Thanks :)

authors: isadoraoliv stefanJi

repo: stefanJi/IntervalProgressBar


text:
[Feature Request] Allow labels/notes to be added to maps (Karta)

Labels or notes could help identify certain places or quest locations. It would be nice to have this option in karta.
(And btw. there seems to be no way to exit the marker placement mode once an option from the left panel is selected)

Aye, seems like a good idea for me!

I will think about this, since these would be somewhat similiar to the Kirja (wiki) Notes. What would your usecase for this be compared to the wiki markers or the quest markers to mark quest locations?

I thought about this, when i wanted to tag the homes of my characters. Those don't need extra wiki page entries as they have no meaning, only as map decoration. Having to create empty pages for them would just clutter the list of more important entries.
Another use case i could see are vistas (like in Guild wars 2). They don't need explicite descriptions, a name is enough, but there can be many of them.

For marking the home of an npc I would suggest using the npc markers. Beeing able to mark an area as dangerous for example sounds like a good idea. I've planned to implement a feature for marking polygons on the map in the features and this might be useful for marking areas as dangerous (or similiar).
I will implement this feature with an upcoming release. But I will focus on exporting first, so this might take a few weeks.

Implemented with 5685305a4eef73b83ca01602e083ae18cfd6d786

It's nice that they are implemented now, but would it be possible to have them not just display "A"/their icon in the map view but their title or an abbreviation thereof (that would make them way more useful)?

You mean that the title should be in the Marker? Hmm that might be possible but still a bit more work. Could you create a new issue for this? This will help me tracking the issue a lot more. Thank you.

authors: ValooFX Wiadomy steffendx

repo: steffendx/GoNorth


text:
Overall trading volumes

I have noticed that overall trading volumes for our asset is not consistent, today could be less than the day or month before. Is this not a total trading volume since asset creation?
The attached show a minor reduction several hours later, however the overall trading always falls back down from a previous figure.

repo: stellar-expert/stellar-expert-explorer


text:
Convert Token from enum to struct with type property

Currently, Token is represented as enum which does not allow to store any properties in it, so we components property is computed, which affects performance as they can be parsed several times. We should instead convert it to struct and use a property of enum type like type.

Sounds good, I think.
Which token are we talking about though? Because if this is related to #253, it could be Token (in lexer), it could be IfToken in if-tag, and I'm sure there are some tokes somewhere in the code.

I mean enum Token in Tokenizer.swift:74

Yeah, that's a clear candidate for a struct. Every case has the same associated value 🤦♂
Is components accessed for every Token instance? Or only specific cases? I'm pretty sure we don't need the components of a .text token. Because if so, we may want to make components a lazy property.

Yes, we also don't need to parse it right away, so lazy makes total sense

Then we may want a class instead of a struct I think, if we want to use lazy var, not sure though.

authors: djbe ilyapuchka

repo: stencilproject/Stencil


text:
displayUsing not working

I have the following code, and i only see the integer insted of the currency name, the display using function not called or i dont know.
JsonRepeatable::make('Price', 'meta->price')                 ->fullWidth()                 ->rules([                     'required',                     'array',                     'min:1',                 ])                 ->fields([                     Select::make('Currency', 'currency_id')                         ->rules('required')                         ->options(Currency::all())                         ->displayUsing(function ($name) {                             return Currency::first($name)->name;                         }),          ])->hideFromIndex(),

you can use this code:
JsonRepeatable::make('Price', 'meta->price') ->fullWidth() ->rules([ 'required', 'array', 'min:1', ]) ->fields([ Select::make('Currency', 'currency_id') ->rules('required') ->options(Currency::all())])->resolveUsing(function ($fields){                     $custom_values = [];                     foreach ($fields as $field)                     {                         $field['currency_id'] = Currency::where('currency_id', $field['currency_id'])->first()->name;                         $custom_values[] = $field;                     }                     return $custom_values;                 })->onlyOnDetail(), JsonRepeatable::make('Price', 'meta->price') ->fullWidth() ->rules([ 'required', 'array', 'min:1', ]) ->fields([ Select::make('Currency', 'currency_id') ->rules('required') ->options(Currency::all())])->hideFromDetail(),

@saberhashemzadeh thanks
I think I'll analyze it later and add it to readme

authors: saberhashemzadeh stepanenko3 zsoltjanes


text:
Error: "A facade root has not been set" when calling settings helper on config files

Error when trying to use the settings helper on some config file like "config/app.php":
A facade root has not been set. {"exception":"[object] (RuntimeException(code: 0): A facade root has not been set. at
nova/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php:350)
[stacktrace]
#0 nova/vendor/stepanenko3/nova-settings/src/helpers.php(27): Illuminate\Support\Facades\Facade::__callStatic()

I'm also having the same problem. This error happens because the help settings calls the Cache::remember facade, I think it has not yet been initialized in the service container. Now I don't know if there is an alternative for this.

Hi, @metadevstudio, @leonardyrj
For Laravel, it is not normal to make queries in config files.
You can create Middleware like LoadGlobalConfig, in which you can do the following:
class LoadGlobalConfig
{
    public function handle(Request $request, Closure $next): Response
    {
        config([
            'key' => settings(...),
         ]);
    }
}

authors: leonardyrj metadevstudio stepanenko3


text:
Option to Use Intel MKL Instead of OpenBLAS

Any chance to have support for Intel MKL instead of OpenBLAS?
Intel MKL is faster and includes many useable algorithms (Accelerated LAPCAK in addition to BLAS).

Yes, you have to make sure the required Blas Intel MKL dynamic libraries are loaded via ffi.load(...) from https://luajit.org/ext_ffi_api.html.
See for instance __init.lua from https://github.com/uluadist-pkg/uluadist-pkg.github.io/blob/master/pkg/clib_libopenblas/0.2.15 (a zip file), but that relies on how things are handled in ULua so it's probably of limited help.

authors: RoyiAvital stepelu

repo: stepelu/lua-sci


text:
Raw binary support

Glaze supports BEVE for JSON like binary that can be used for storage and inspection. However, I also want to add support for raw binary without tags. This way we can implement the fastest messaging possible across compilers with matching ABI. I am all for breaking C++ ABI with new compiler versions (though this rarely happens), but for the same compiler version in performance critical applications raw binary is the fastest we can get.
Currently Glaze using the naming read_binary and write_binary for BEVE. I think this should change to read_beve and write_beve, and elsewhere the naming should change. Old naming should be deprecated and the new naming should be used for a significant amount of time before we introduce raw binary support.
Raw binary naming should use read_binary and write_binary. But, only do this after they have been deprecated for a significant amount of time.

After giving this some more thought, I've realized that really the only thing we would want different than a normal BEVE implementation is to drop tags (keys) for structs. If we use BEVE arrays for structs then we reduce memory consumption and have an excellent binary format that would match most raw implementations, and we don't need another specification. We can still be 100% BEVE conformant and just not write out the keys.
All we need is a compile time option in glz::opts such as write_structs_as_arrays. This can also be applied to JSON. But, now binary will work across compilers and operating systems, and has all the benefits of using BEVE without paying for tags.

@kalradivyanshu, thanks for offering to make a PR. In glz::opts a boolean write_structs_as_arrays needs to be added. We then need structs that satisfy the concepts of reflectable or glaze_object_t to behave similarly to how std::tuple is serialized. A minor challenge is that the concepts as not associated with glz::opts, so I'm not sure the best way of avoiding code duplication. For reflectable types we can call to_tuple and then serialize this tuple, that should be really straightforward. For glaze_object_t we'll probably need a bit more code. If you want to try to accomplish this and submit a pull request, go for it. I should also be able to work on this soon, and it should't be too much of an effort.

I'm trying to figure out what to name these functions for writing/reading untagged binary.
read_binary_untagged
read_binary_flat

I'll add the note that glaze already has a glz::array, so using this the structs_as_arrays option with glz::object is unnecessary, but I think I'll support it anyway. glz::array should compile a bit faster. But, by supporting this option with binary it allows JSON to include keys and binary to write out without keys.

I've merged in #671, which adds the option structs_as_arrays and adds the helper functions read_binary_untagged and write_binary_untagged. Unit tests have been included as well.
@kalradivyanshu, let me know if you run into any issues with this new feature.

repo: stephenberry/glaze


text:
SVO Recording very CPU intensive

When running the recording example (as it comes) on a Jetson TX2 with a ZED Mini it uses almost 3 CPU cores at 100% each. It seems that the problem is the compression, as on SVO_COMPRESSION_MODE_RAW, the CPU usage is only at about 1 CPU core at 100% usage.
To improve the situation I tried to drop the framer rate by adding  'initParameters.camera_fps  = 30;. It shows that it records only at 30fps, however there is no improvement what so ever in the CPU usage, so I assume that setting is ignored in recording mode.
Our application requires low power, and as we can not run full mapping/tracking for the entire time, we were hoping that it would be possible to store (buffer) the stream to a file (or even better keep it in RAM) and then replay it when we need it.
Is there a way to get about that which doesn't drain the resources as much? What is the situation with the RAW mode? It says it is deprecated and doesn't support IMU data. Is this true?

Bump,
Also interested in lowering the CPU usage, as I'm trying to record from a ZED camera and Realsense camera simultaneously, but getting lots of frame drops for the Realsense stream do to CPU usage by ZED. Already tested that issue is not bandwidth.

The bottle neck here seems to be the compression, so you could just dump the images in a binary file yourself after grabbing them. However, if you require playback through the SDK I think it is necessary to store images at the highest rate possible anyways. Lowering the resolution should help a bit.
I have the impression Stereolab has been working quite intensely on lowering the consumption of tracking, so you might just want to run tracking in real time and store the tracking result together with your images for further processing. At least on our system running tracking and store images as binary files is much less resource intensive than svo recording.

Hi,
On the upcoming version (2.7.0), we will introduce a new SVO compression mode, based on NVENC compression (AVCHD or HEVC) . This will allow a huge reduction of size of the SVO files and almost no CPU/GPU usage (since it' using a dedicated hardware).
You will need a NVIDIA GPU to have this mode available but I think that would help your case.
Best,
OB

Hi!
I tried SVO recording example with H264 and H265 encoding in my Jetson TX2 but the CPU usage is between 100 and 120%. I have installed ZED SDK 2.8.2. Is there any update on this issue?
Frame rate: 30fps
Resolution: HD720
Compression: SVO_COMPRESSION_MODE_HEVC / SVO_COMPRESSION_MODE_AVCHD
How can I check that I am using hardware encoding on Jetson platform?

authors: Lejboelle cosama ftheirs obraun-sl

repo: stereolabs/zed-examples


text:
React Native with Vite

I found a way:

npx react-native init demo
cd demo
Add following code in metro.config.js -> module.exports = {}
This is to compatibility with JSX files.
Maybe you need to reinstall the APP will take effect.

resolver: {
sourceExts: ['js', 'jsx', 'json', 'ts', 'tsx', 'mjs'],
  }

yarn create vite web --template react
cd web && yarn
Add following code in vite.config.js ->  export default defineConfig({})

resolve: {
    alias: {
      'react-native': 'react-native-web',
    },
  },

mkdir share && touch share/test.jsx
Add following code in share/test.jsx

import React from 'react';
import {Text} from 'react-native';

const Test = ({title}) => {
  return <Text>hello world { title}</Text>;
};

export default Test;

import Section from './web/src/share/test'; // import in RN-dir App.js and add in App component.
import Section from './share/test'; // import in Web-dir App.jsx and add in App component.
yarn dev
cd .. && yarn start

Originally posted by @hxse in necolas/react-native-web#2201 (comment)

Okay now I got it working! We need the viteCommonJS Plugin:
import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";
import { viteCommonjs, esbuildCommonjs } from "@originjs/vite-plugin-commonjs";

// https://vitejs.dev/config/
export default defineConfig({
  define: {
    global: "window",
  },
  optimizeDeps: {
    include: ["@react-navigation/native"],
    esbuildOptions: {
      mainFields: ["module", "main"],
      resolveExtensions: [".web.js", ".js", ".ts"],
      plugins: [esbuildCommonjs(["@react-navigation/elements"])],
    },
  },
  resolve: {
    extensions: [".web.tsx", ".web.jsx", ".web.js", ".tsx", ".ts", ".js"],
    alias: {
      "react-native": "react-native-web",
    },
  },
  plugins: [viteCommonjs(), react()],
  build: {
    commonjsOptions: {
      transformMixedEsModules: true,
    },
  },
});

For your convenience I will provide a live example at StackBlitz: https://stackblitz.com/github/shiftbeyond/vite-rnw-react-navigation
Edit: Also fixed a build issue when bundling for production.

Originally posted by @jgo80 in https://github.com/vitejs/vite/discussions/8195#discussioncomment-3054164

repo: stereoplegic/RRREuNITE


text:
bug: remix │ |- TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".css" node_modules/katex/dist/katex.min.css

Provide environment information
System:
OS: macOS 14.5
CPU: (11) arm64 Apple M3 Pro
Memory: 172.17 MB / 18.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.15.1 - ~/.nvm/versions/node/v20.15.1/bin/node
Yarn: 1.22.22 - /opt/homebrew/bin/yarn
npm: 10.7.0 - ~/.nvm/versions/node/v20.15.1/bin/npm
pnpm: 9.6.0 - ~/.nvm/versions/node/v20.15.1/bin/pnpm
Describe the bug
I got this error when I try to use novel in my remix project. I used the same code in my next project and everything was perfect.
13:12:39 │            remix │ 1:12:39 PM [vite] Error when evaluating SSR module
/app/routes/app.products.$productId.editor/route.tsx: failed to import "novel/extensions"
13:12:39 │            remix │ |- TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".css" for

Link to reproduction

To reproduce

Additional information
No response

i think this is caused be the css import specified here:
https://github.com/steven-tey/novel/blob/ecdb5d2ff5d3e6ab5f5af95b5a81de3ab4e8a0e9/packages/headless/src/extensions/mathematics.ts#L1
which gets bundled when it's built, and node tries to import a .css file when doing ssr

Same issue here, not sure how to resolve

It looks like the library is dead. I wouldn't recommend using it for a production level work.

Yes this library isn't active. Here I re-wrote the block-editor using Tiptap + Tailwind + Shadcn as a separate package for my project. I think it will be useful for you.

I first started using novel in August 2023. I wish I did not waste so much time on this repo. It started out as a ui component you can easily modify. They tried so hard to force it into a stand alone package.  All the complexity added on top of all the nextjs stuff.

repo: steven-tey/novel


text:
Added proof of Italy not being real

Added a simple map of Italy not being a real country, which further proves that Italians aren't real, as previously stated.

There are now merge conflicts. Could you update with the latest version from upstream?


text:
Request bdist_wheel from Travis

Ask Travis to build a wheel, as well as the source dist.
From: https://docs.travis-ci.com/user/deployment/pypi/#uploading-different-distributions

cool!  Want me to make a new version so this gets uploaded?

Yes, please. That'd be a good test that this does work correctly :)

looks good!  https://pypi.org/project/scales-rpc/#files
Ignore the build failure, I screwed up the first tag so it tried to upload the artifact twice.

authors: steveniemitz waisbrot

repo: steveniemitz/scales


text:
目前git分支的解释还没有，希望快点加上！

目前git分支的解释还没有，希望快点加上！

我提交了分支说明  #15 ，你可以看看描述的是否清晰，如果没问题的话，我将会关闭这个issue。

@stick-i 已了解，没问题！

repo: stick-i/spel-validator


text:
Rename View Helpers to Template Helpers

@frm I think we should rename View Helpers to Template Helpers. We are calling those files templates, not views. I think the only reason we called it views is because we were thing about Phonix. What do you say?

On one hand I'd prefer it to be clear and someone familiar with Phoenix would know what this is about. On the other hand, I'd prefer to not use Phoenix as a staple and to have clear terms for well defined concepts.
Let's do it.

Can I take this one? Would love to contribute.

@hgg go for it 👍

authors: frm gabrielpoca hgg

repo: still-ex/still

license: ISC


text:
use dynamic imports instead of require.context

Would you be open to a PR that would allow this API (or something similar)?:
import { startApplication } from "stimulus";

startApplication(controllerName => import(`./${controllerName}_controller`));

the implementation would look something like this:
import { Application } from "stimulus";

export const startApplication = (
  controllerImportFunction: (controllerName: string) => Promise<any>
) => {
  const application = Application.start();

  const registeredControllers = new Set();

  const registerControllers = async (element: Element | Document) => {
    element.querySelectorAll("[data-controller]").forEach(async c => {
      const controllerName = c.getAttribute("data-controller");

      if (!controllerName || registeredControllers.has(controllerName)) return;

      registeredControllers.add(controllerName);

      const { default: controller } = await controllerImportFunction(
        controllerName
      );

      application.register(controllerName, controller);
    });
  };

  new MutationObserver(function callback(mutationList) {
    mutationList.forEach(function ({ target }) {
      if (target instanceof Element) {
        registerControllers(target);
      }
    });
  }).observe(document, {
    childList: true,
    subtree: true
  });

  registerControllers(document);

  return application;
};

This method of loading controllers can reduce initial JS payloads significantly for large applications that have a lot of JS specific to certain areas/users/features. Another small benefit is that this uses the standardized import syntax instead of the webpack specific require.context.
BTW, thanks for Stimulus! I've dabbled with it in the past, but started using it heavily a couple of weeks ago and it's very nice, really brings fresh life into 'old school' server rendered HTML

I've discovered https://github.com/danieldiekmeier/stimulus-controller-resolver via https://discourse.stimulusjs.org/t/stimulus-with-dynamic-import-and-webpack/966/3.

Since this functionality is easy enough to setup using the above plugin or rolling something yourself I'm going to close this.

authors: fleck rik

repo: stimulusjs/stimulus


text:
update stm32f4 sources

See #877

cc @adamgreig This is also ready for review. mmaps needs manual run.

rebased

I think the .orig files shouldn't be in the commit?

I think the .orig files shouldn't be in the commit?

Rebasing artifacts. Fixed.

authors: adamgreig burrbull


text:
[doit] add task Documentation

Similarly to #162, this is a subset of #110.
Instead of calling make in the Documentation workflow, a task named Documentation is added to the do.py file.
For now, the following are equivalent:

./do.py Documentation
doit -f do.py Documentation
make -C docs

In upcoming PRs, we might remove docs/Makefile and replace it with more specific doit tasks.

Awesome! :+1:

In upcoming PRs, we might remove docs/Makefile and replace it with more specific doit tasks.

Let's keep that for now.

authors: stnolting umarcor


text:
🛑 Wolf Ingenieurbüro is down

In 58fe139, Wolf Ingenieurbüro (https://wolf-ingenieurbuero.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wolf Ingenieurbüro is back up in d8af9a6 after 6 minutes.

repo: stoamandl/upptime


text:
no_std feature

This pull request implements no_std features in lib/cretonne, lib/native, lib/frontend, and lib/wasm.
Important to note, they still require an environment with liballoc, so any bare-metal applications using this must have an allocator.
My main reason to port cretonne to no_std is for use in my own projects, but I can see quite a number of possible uses for it aside from that.
Since cretonne has very few dependencies, porting wasn't difficult, the main issues being std::collections and std::error. Both we resolved by using external crates (only during no_std builds) that implement apis very close to std::collections and std::error.
Comments and criticism welcome!

Ah, wish I'd seen this sooner. One thing to be aware of - negative cargo features (those which reduce API surface) are invalid, and cause Cargo's dependency logic to come to erronous conclusions which will cause spooky build failures at a distance for dependents. To quote my comment on another project:

There are two distinct concerns here:

Opt-in vs. opt-out in terms of "what the default is"
Opt-in vs. opt-out in terms of "what the polarity of each feature is"

These are orthogonal, and actually have very different behaviors:
Opt-in vs. opt-out as far as defaults is a matter of preference - generally speaking, if something has no dependencies and no conflicts or concerns, it's often nicer to downstream to enable it by default,
Opt-in vs. opt-out regarding feature polarity, however, has exactly one answer: Opt-in. Anything else breaks Cargo. The reason is that Cargo assumes that it is always safe to turn on a feature, and that doing so will never break a dependent. As a result, features with opt-out polarity will get enabled if any dependent asks for them, breaking anyone who uses the now-missing APIs.
The correct approach:
Cargo.toml:
[features]
default = ["elf", "elf64", "..."]

Anything in default is on by default
Anything not in default is off by default
Crates that don't need all of the default features can opt out of the default set and choose them á la carte
Crates that need non-default features can still enable them
Nobody's build gets broken.

But also, beware: Features that change the behavior of an API - like you seem to describe no_endian_fd - are always unsafe, because if one dependent flips them, that affects every dependent.
Those kinds of features need to be separate APIs, under different names or modules, with the feature simply enabling them.

@eternaleye That's good to know; thanks!
It turns out that we're not merging the patch into the main tree at this time. That said, I'm interested in no_std in Rust in general, so I'm experimenting a little with a fork of this PR here. I've now added a std feature which is enabled by default, along with a no_std feature which can be enabled to bring in the hashmap_core and error_core replacement libraries. With this setup, one of std or no_std must be enabled. But at least now they're both additive :-). (You can enable both, but it just acts like a std build.)

@sunfishcode Hm, I'd disagree that it's strictly additive - replacement libraries, in particular, are not additive. If one dependent explicitly uses hashmap_core (and enables no_std), and another uses the std::collections one (and leaves std enabled), then a third package depending on both cannot possibly build correctly.
This is exactly the kind of "spooky action at a distance" that is problematic.
The API surface without a feature needs to be a strict subset of the API surface with a feature; substitutions are not a strict subset (Rust has nominal typing, not structural).

@eternaleye Ah, interesting. Yes, HashMap is only used internally at the moment, but Error is indeed exposed in the API. I'm now experimenting with using the experimental failure crate to replace Error. (It's just a side experiment for now, so I'm ok depending on experimental things.)

for what its worth, one of the big changes I made when I did a (private, for now) rewrite of cton-wasm was to use failure throughout. So far I have zero regrets.

authors: eternaleye lachlansneff pchickey sunfishcode

repo: stoklund/cretonne


text:
Imagescan Rebuild: 2022-07-05

Rebuilding imagescan for stolostron/insights-client repo.

Rebuild for the issue: https://github.com/stolostron/backlog/issues/23230

/unhold

repo: stolostron/insights-client


text:
Fix e2e tests

fix the e2e issue due to the name change in prow - https://github.com/openshift/release/pull/31255
Signed-off-by: clyang82 chuyang@redhat.com

/retest

/retest

/retest

/retest

/lgtm

repo: stolostron/multicluster-globalhub


text:
check for pullsecret when installing mch in acm 2.4

Signed-off-by: Erin Murphy erinmurp@redhat.com
Issue: https://github.com/stolostron/backlog/issues/21579

2.4.5 is now open. @eemurphy is this PR ready to merge?

@JakobGray Yes this is ready to be merged!

authors: JakobGray eemurphy

repo: stolostron/multiclusterhub-operator


text:
Add deprecation message to README.md

Related issue: N/A
Changes:

Adds deprecation message to README.md

/lgtm

authors: SherinV jlpadilla

repo: stolostron/search-chart


text:
Contact?

Is there any way i can contact you?
maybe discord or telegram

https://github.com/stonedDiscord/RealAndroidBot#discord

repo: stonedDiscord/RealAndroidBot


text:
support for account with contracts in multiple currencies

I've been looking at the api-next branch, which is very well programmed and very clean code.
One issue is that an AccountSummary could have multiple currencies and the current data structure does not support that. IBKR could do margin calculations per currency and report tag/values by currency.
In api-next.ts, method: getAccountSummary the callback will overwrite the tag for whichever is the last reported currency:
const onAccountSummary = (reqId: number, account: string, tag: string, value: string, currency: string): void => {
      // get the subscription
      const subscription = this._subscriptions.get(reqId) as IBApiNextSubscription<AccountSummariesUpdate>;
      if (!subscription) {
        return;
      }

      // update cache
      const cached = subscription.value ?? new AccountSummariesUpdate();
      cached.all.getOrAdd(account).values.set(tag, { value, currency });

You may need an AccountSummaryValues map by currency.Something similar what I did here (but your code with observables is way nicer!): https://github.com/stoqey/ibkr/issues/68#issuecomment-781715475

Thanks for the feedback :)
I  will change that.
I was acutally already thinking about if also need the currency on the key as well, but coudn't imagine where this makes sense (so you can get something like [Tag:"NetLiquidation"[value:1000, current:"EUR"]] and  [Tag:"NetLiquidation"[value:900 current:"USR"]] on the same account? just trying to understand the use-case on this)

I think basically that IBKR reports everything by currency. Otherwise they would need to take into account exchange rates which is not in the API. If you trade on multiple markets you could have contracts from different currencies in your account and in that case I assume they would report multiple cash values for a single account.
Also for margin they likely have different min margin requirements by currency, or at least their API supports that, so therefore updateAccountValue has a similar signature so it would apply to that as well I think.

I see... ;) ok, so we got one more Map https://github.com/stoqey/ib/commit/9a985571e7e5f2d73b76d642d5ffcb27c91e5a97

authors: bayareacoder mfrener

repo: stoqey/ib


text:
getLoginLink does not percent-encode the redirect_uri on Linux

Attempting to use the redirect_uri parameter in getLoginLink does not percent encode the query on Linux. This is likely a corelibs-foundation issue.

Since this is not causing any major issues, we're going to leave this until Foundation fixes this.

authors: edjiang harlanhaskins

repo: stormpath/Turnstile


text:
[Bug] SV CLI with storybook not working correctly SB_CORE-SERVER_0002 (CriticalPresetLoadError): Storybook failed to load the following preset @storybook+addon-svelte-csf@5.0.0-next.21 #379

OS Name: Microsoft Windows 11 Pro                                                                                OS Version: 10.0.22631 N/A Build 22631
node -v: v23.5.0
pnpm -v: 9.15.1
CLI log:
$ npx sv@latest create sv-cli-storybook-issue
┌  Welcome to the Svelte CLI! (v0.6.10)
│
◇  Which template would you like?
│  SvelteKit minimal
│
◇  Add type checking with Typescript?
│  Yes, using Typescript syntax
│
◆  Project created
│
◇  What would you like to add to your project? (use arrow keys / space bar)
│  prettier, eslint, vitest, playwright, tailwindcss, sveltekit-adapter, drizzle, lucia, mdsvex, paraglide, storybook
│
◇  tailwindcss: Which plugins would you like to add?
│  typography, forms, container-queries
│
◇  sveltekit-adapter: Which SvelteKit adapter would you like to use?
│  node
│
◇  drizzle: Which database would you like to use?
│  PostgreSQL
│
◇  drizzle: Which PostgreSQL client would you like to use?
│  Postgres.JS
│
◇  drizzle: Do you want to run the database locally with docker-compose?
│  Yes
│
◇  lucia: Do you want to include a demo? (includes a login/register page)
│  Yes
│
◇  paraglide: Which languages would you like to support? (e.g. en,de-ch)
│  en,fr,it,de
│
◇  paraglide: Do you want to include a demo?
│  Yes
│
◇  Which package manager do you want to install dependencies with?
│  pnpm
│
◇  storybook: Running external command (pnpm dlx storybook@latest init --skip-install --no-dev)
╭──────────────────────────────────────────────────────╮
│                                                      │
│   Adding Storybook version 8.4.7 to your project..   │
│                                                      │
╰──────────────────────────────────────────────────────╯
 • Detecting project type. ✓
 • Adding Storybook support to your "SvelteKit" app
  ✔ Getting the correct version of 9 packages
    Configuring eslint-plugin-storybook in your package.json
  ✔ Installing Storybook dependencies
. ✓

attention => Storybook now collects completely anonymous telemetry regarding usage.
This information is used to shape Storybook's roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://storybook.js.org/telemetry

╭──────────────────────────────────────────────────────────────────────────────╮
│                                                                              │
│   Storybook was successfully installed in your project! 🎉                   │
│   To run Storybook manually, run pnpm run storybook. CTRL+C to stop.         │
│                                                                              │
│   Wanna know more about Storybook? Check out https://storybook.js.org/       │
│   Having trouble or want to chat? Join us at https://discord.gg/storybook/   │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯
│
◆  Successfully setup add-ons
│
◆  Successfully installed dependencies
│
◇  Successfully formatted modified files
│
◇  Project next steps ─────────────────────────────────────────────────────╮
│                                                                          │
│  1: cd sv-cli-storybook-issue                                            │
│  2: git init && git add -A && git commit -m "Initial commit" (optional)  │
│  3: pnpm run dev --open                                                  │
│                                                                          │
│  To close the dev server, hit Ctrl-C                                     │
│                                                                          │
│  Stuck? Visit us at https://svelte.dev/chat                              │
│                                                                          │
├──────────────────────────────────────────────────────────────────────────╯
│
◇  Add-on next steps ──────────────────────────────────────────────────╮
│                                                                      │
│  drizzle:                                                            │
│  - You will need to set DATABASE_URL in your production environment  │
│  - Run pnpm run db:start to start the docker container               │
│  - Run pnpm run db:push to update your database schema               │
│                                                                      │
│  lucia:                                                              │
│  - Run pnpm run db:push to update your database schema               │
│  - Visit /demo/lucia route to view the demo                          │
│                                                                      │
│  paraglide:                                                          │
│  - Edit your messages in messages/en.json                            │
│  - Consider installing the Sherlock IDE Extension                    │
│  - Visit /demo/paraglide route to view the demo                      │
│                                                                      │
├──────────────────────────────────────────────────────────────────────╯
│
└  You're all set!

pNPM dev:
> sv-cli-storybook-issue@0.0.1 dev C:\test\sv-cli-storybook-issue
> vite dev

▲ [WARNING] Cannot find base config file "./.svelte-kit/tsconfig.json" [tsconfig.json]

    tsconfig.json:2:12:
      2 │   "extends": "./.svelte-kit/tsconfig.json",
        ╵              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Using existing cloned repo
ℹ [paraglide] Compiling Messages into ./src/lib/paraglide
Forced re-optimization of dependencies

  VITE v5.4.11  ready in 4371 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
  ➜  press h + enter to show help

pNPM run storybook:
> sv-cli-storybook-issue@0.0.1 storybook C:\test\sv-cli-storybook-issue
> storybook dev -p 6006

@storybook/core v8.4.7

SB_CORE-SERVER_0002 (CriticalPresetLoadError): Storybook failed to load the following preset: .\.storybook\main.js.

Please check whether your setup is correct, the Storybook dependencies (and their peer dependencies) are installed correctly and there are no package version clashes.

If you believe this is a bug, please open an issue on Github.

SB_CORE-SERVER_0002 (CriticalPresetLoadError): Storybook failed to load the following preset: .\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\preset.js.

Please check whether your setup is correct, the Storybook dependencies (and their peer dependencies) are installed correctly and there are no package version clashes.

If you believe this is a bug, please open an issue on Github.

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '.\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\utils\identifier-utils' imported from .\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\compiler\pre-transform\codemods\legacy-story.js
    at finalizeResolution (node:internal/modules/esm/resolve:275:11)
    at moduleResolve (node:internal/modules/esm/resolve:860:10)
    at defaultResolve (node:internal/modules/esm/resolve:984:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:688:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:612:25)
    at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:647:38)
    at ModuleLoader.resolveSync (node:internal/modules/esm/loader:670:52)
    at #cachedResolveSync (node:internal/modules/esm/loader:631:25)
    at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:359:50)
    at new ModuleJobSync (node:internal/modules/esm/module_job:342:34)

More info:

    at loadPreset (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16477:13)

More info:

    at loadPreset (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16477:13)
    at async Promise.all (index 1)
    at async loadPresets (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16487:55)
    at async getPresets (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16520:11)
    at async buildDevStandalone (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\core-server\index.cjs:37145:11)
    at async withTelemetry (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\core-server\index.cjs:35757:12)
    at async dev (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\cli\bin\index.cjs:2591:3)
    at async s.<anonymous> (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\cli\bin\index.cjs:2643:74)

WARN Broken build, fix the error above.
WARN You may need to refresh the browser.

WARN   Failed to load preset: {"type":"presets","name":"C:\\test\\sv-cli-storybook-issue\\node_modules\\.pnpm\\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\\node_modules\\@storybook\\addon-svelte-csf\\dist\\preset.js"} on level 1
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '.\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\utils\identifier-utils' imported from .\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\compiler\pre-transform\codemods\legacy-story.js
    at finalizeResolution (node:internal/modules/esm/resolve:275:11)
    at moduleResolve (node:internal/modules/esm/resolve:860:10)
    at defaultResolve (node:internal/modules/esm/resolve:984:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:688:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:612:25)
    at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:647:38)
    at ModuleLoader.resolveSync (node:internal/modules/esm/loader:670:52)
    at #cachedResolveSync (node:internal/modules/esm/loader:631:25)
    at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:359:50)
    at new ModuleJobSync (node:internal/modules/esm/module_job:342:34)
√ Would you like to help improve Storybook by sending anonymous crash reports? ... yes
 ELIFECYCLE  Command failed with exit code 1.

i have tried:

Check Dependency Installation
[ OK ] pnpm install

[ OK ] rm -rf node_modules
[ OK ] rm -f package-lock.json # Or pnpm-lock.yaml for pnpm
[ OK ] npm install
2. Clean the Project
i have used after : pnpm install --force
also i have tried : pnpm update -L
 WARN  9 deprecated subdependencies found: @esbuild-kit/core-utils@3.3.2, @esbuild-kit/esm-loader@2.6.5, @humanwhocodes/config-array@0.9.5, @humanwhocodes/object-schema@1.2.1, eslint@8.4.1, glob@7.2.3, inflight@1.0.6, rimraf@2.7.1, rimraf@3.0.2
Packages: +19
+++++++++++++++++++
Progress: resolved 747, reused 625, downloaded 0, added 19, done

dependencies:
- @inlang/paraglide-sveltekit 0.11.5
+ @inlang/paraglide-sveltekit 0.15.0
- @node-rs/argon2 1.8.3
+ @node-rs/argon2 2.0.2
- drizzle-orm 0.33.0
+ drizzle-orm 0.38.3

devDependencies:
- @sveltejs/vite-plugin-svelte 4.0.4
+ @sveltejs/vite-plugin-svelte 5.0.3
- drizzle-kit 0.22.8
+ drizzle-kit 0.30.1
- mdsvex 0.11.2
+ mdsvex 0.12.3
- vite 5.4.11
+ vite 6.0.6

Done in 22.3s

same problem:
> sv-cli-storybook-issue@0.0.1 storybook C:\test\sv-cli-storybook-issue
> storybook dev -p 6006

@storybook/core v8.4.7

SB_CORE-SERVER_0002 (CriticalPresetLoadError): Storybook failed to load the following preset: .\.storybook\main.js.

Please check whether your setup is correct, the Storybook dependencies (and their peer dependencies) are installed correctly and there are no package version clashes.

If you believe this is a bug, please open an issue on Github.

SB_CORE-SERVER_0002 (CriticalPresetLoadError): Storybook failed to load the following preset: .\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._cf7nqnu6p5s3tdreqzupsb4qie\node_modules\@storybook\addon-svelte-csf\dist\preset.js.

Please check whether your setup is correct, the Storybook dependencies (and their peer dependencies) are installed correctly and there are no package version clashes.

If you believe this is a bug, please open an issue on Github.

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '.\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._cf7nqnu6p5s3tdreqzupsb4qie\node_modules\@storybook\addon-svelte-csf\dist\utils\identifier-utils' imported from .\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._cf7nqnu6p5s3tdreqzupsb4qie\node_modules\@storybook\addon-svelte-csf\dist\compiler\pre-transform\codemods\legacy-story.js
    at finalizeResolution (node:internal/modules/esm/resolve:275:11)
    at moduleResolve (node:internal/modules/esm/resolve:860:10)
    at defaultResolve (node:internal/modules/esm/resolve:984:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:688:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:612:25)
    at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:647:38)
    at ModuleLoader.resolveSync (node:internal/modules/esm/loader:670:52)
    at #cachedResolveSync (node:internal/modules/esm/loader:631:25)
    at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:359:50)
    at new ModuleJobSync (node:internal/modules/esm/module_job:342:34)

More info:

    at loadPreset (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16477:13)

More info:

    at loadPreset (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16477:13)
    at async Promise.all (index 1)
    at async loadPresets (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16487:55)
    at async getPresets (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16520:11)
    at async buildDevStandalone (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\core-server\index.cjs:37145:11)
    at async withTelemetry (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\core-server\index.cjs:35757:12)
    at async dev (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\cli\bin\index.cjs:2591:3)
    at async s.<anonymous> (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\cli\bin\index.cjs:2643:74)

WARN Broken build, fix the error above.
WARN You may need to refresh the browser.

WARN   Failed to load preset: {"type":"presets","name":"C:\\test\\sv-cli-storybook-issue\\node_modules\\.pnpm\\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._cf7nqnu6p5s3tdreqzupsb4qie\\node_modules\\@storybook\\addon-svelte-csf\\dist\\preset.js"} on level 1
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '.\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._cf7nqnu6p5s3tdreqzupsb4qie\node_modules\@storybook\addon-svelte-csf\dist\utils\identifier-utils' imported from .\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._cf7nqnu6p5s3tdreqzupsb4qie\node_modules\@storybook\addon-svelte-csf\dist\compiler\pre-transform\codemods\legacy-story.js
    at finalizeResolution (node:internal/modules/esm/resolve:275:11)
    at moduleResolve (node:internal/modules/esm/resolve:860:10)
    at defaultResolve (node:internal/modules/esm/resolve:984:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:688:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:612:25)
    at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:647:38)
    at ModuleLoader.resolveSync (node:internal/modules/esm/loader:670:52)
    at #cachedResolveSync (node:internal/modules/esm/loader:631:25)
    at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:359:50)
    at new ModuleJobSync (node:internal/modules/esm/module_job:342:34)
Assertion failed: !(handle->flags & UV_HANDLE_CLOSING), file c:\ws\deps\uv\src\win\async.c, line 76
 ELIFECYCLE  Command failed with exit code 3221226505.

Hi Mieaw, have you seen #229 issue?
Looks like you've created a duplicate.
The issue aforementioned has workaround if you still insist on using Node.js v23.
BTW, the warning you're seeing when running command: pnpm dev, can be solved with:
pnpm svelte-kit sync

using LTS :
$ nvm use lts
Now using node v22.12.0 (64-bit)

Log:
> my-app@0.0.1 storybook C:\test\my-app
> storybook dev -p 6006

@storybook/core v8.4.7

SB_CORE-SERVER_0002 (CriticalPresetLoadError): Storybook failed to load the following preset: .\.storybook\main.js.

Please check whether your setup is correct, the Storybook dependencies (and their peer dependencies) are installed correctly and there are no package version clashes.

If you believe this is a bug, please open an issue on Github.

SB_CORE-SERVER_0002 (CriticalPresetLoadError): Storybook failed to load the following preset: .\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\preset.js.

Please check whether your setup is correct, the Storybook dependencies (and their peer dependencies) are installed correctly and there are no package version clashes.

If you believe this is a bug, please open an issue on Github.

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '.\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\utils\identifier-utils' imported from .\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\compiler\pre-transform\codemods\legacy-story.js
    at finalizeResolution (node:internal/modules/esm/resolve:275:11)
    at moduleResolve (node:internal/modules/esm/resolve:932:10)
    at defaultResolve (node:internal/modules/esm/resolve:1056:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:654:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:603:25)
    at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:353:53)
    at new ModuleJobSync (node:internal/modules/esm/module_job:341:34)
    at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:413:11)
    at new ModuleJobSync (node:internal/modules/esm/module_job:341:34)
    at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:413:11)

More info:

    at loadPreset (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16477:13)

More info:

    at loadPreset (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16477:13)
    at async Promise.all (index 1)
    at async loadPresets (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16487:55)
    at async getPresets (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16520:11)
    at async buildDevStandalone (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\core-server\index.cjs:37145:11)
    at async withTelemetry (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\core-server\index.cjs:35757:12)
    at async dev (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\cli\bin\index.cjs:2591:3)
    at async s.<anonymous> (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\cli\bin\index.cjs:2643:74)

WARN Broken build, fix the error above.
WARN You may need to refresh the browser.

WARN   Failed to load preset: {"type":"presets","name":"C:\\test\\my-app\\node_modules\\.pnpm\\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\\node_modules\\@storybook\\addon-svelte-csf\\dist\\preset.js"} on level 1
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '.\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\utils\identifier-utils' imported from .\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\compiler\pre-transform\codemods\legacy-story.js
    at finalizeResolution (node:internal/modules/esm/resolve:275:11)
    at moduleResolve (node:internal/modules/esm/resolve:932:10)
    at defaultResolve (node:internal/modules/esm/resolve:1056:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:654:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:603:25)
    at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:353:53)
    at new ModuleJobSync (node:internal/modules/esm/module_job:341:34)
    at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:413:11)
    at new ModuleJobSync (node:internal/modules/esm/module_job:341:34)
    at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:413:11)

useing latest
$ nvm use latest
23.5.0
Now using node v23.5.0 (64-bit)

Log:
> my-app@0.0.1 storybook C:\test\my-app
> storybook dev -p 6006

@storybook/core v8.4.7

SB_CORE-SERVER_0002 (CriticalPresetLoadError): Storybook failed to load the following preset: .\.storybook\main.js.

Please check whether your setup is correct, the Storybook dependencies (and their peer dependencies) are installed correctly and there are no package version clashes.

If you believe this is a bug, please open an issue on Github.

SB_CORE-SERVER_0002 (CriticalPresetLoadError): Storybook failed to load the following preset: .\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\preset.js.

Please check whether your setup is correct, the Storybook dependencies (and their peer dependencies) are installed correctly and there are no package version clashes.

If you believe this is a bug, please open an issue on Github.

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '.\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\utils\identifier-utils' imported from .\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\compiler\pre-transform\codemods\legacy-story.js
    at finalizeResolution (node:internal/modules/esm/resolve:275:11)
    at moduleResolve (node:internal/modules/esm/resolve:860:10)
    at defaultResolve (node:internal/modules/esm/resolve:984:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:688:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:612:25)
    at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:647:38)
    at ModuleLoader.resolveSync (node:internal/modules/esm/loader:670:52)
    at #cachedResolveSync (node:internal/modules/esm/loader:631:25)
    at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:359:50)
    at new ModuleJobSync (node:internal/modules/esm/module_job:342:34)

More info:

    at loadPreset (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16477:13)

More info:

    at loadPreset (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16477:13)
    at async Promise.all (index 1)
    at async loadPresets (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16487:55)
    at async getPresets (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\common\index.cjs:16520:11)
    at async buildDevStandalone (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\core-server\index.cjs:37145:11)
    at async withTelemetry (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\core-server\index.cjs:35757:12)
    at async dev (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\cli\bin\index.cjs:2591:3)
    at async s.<anonymous> (.\node_modules\.pnpm\@storybook+core@8.4.7_prettier@3.4.2\node_modules\@storybook\core\dist\cli\bin\index.cjs:2643:74)

WARN Broken build, fix the error above.
WARN You may need to refresh the browser.

WARN   Failed to load preset: {"type":"presets","name":"C:\\test\\my-app\\node_modules\\.pnpm\\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\\node_modules\\@storybook\\addon-svelte-csf\\dist\\preset.js"} on level 1
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '.\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\utils\identifier-utils' imported from .\node_modules\.pnpm\@storybook+addon-svelte-csf@5.0.0-next.21_@storybook+svelte@8.4.7_storybook@8.4.7_prettier@3._invney3l7qorapowne6u3rqdru\node_modules\@storybook\addon-svelte-csf\dist\compiler\pre-transform\codemods\legacy-story.js
    at finalizeResolution (node:internal/modules/esm/resolve:275:11)
    at moduleResolve (node:internal/modules/esm/resolve:860:10)
    at defaultResolve (node:internal/modules/esm/resolve:984:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:688:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:612:25)
    at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:647:38)
    at ModuleLoader.resolveSync (node:internal/modules/esm/loader:670:52)
    at #cachedResolveSync (node:internal/modules/esm/loader:631:25)
    at ModuleLoader.getModuleJobForRequire (node:internal/modules/esm/loader:359:50)
    at new ModuleJobSync (node:internal/modules/esm/module_job:342:34)

the work around is to use what you already mentioned here: https://github.com/storybookjs/addon-svelte-csf/issues/229#issuecomment-2540390494
But i will not close the issue because the sv CLI not working as expected (normally without (NODE_OPTIONS="--no-experimental-require-module")
NODE_OPTIONS="--no-experimental-require-module" pnpm storybook

$ NODE_OPTIONS="--no-experimental-require-module" pnpm storybook

> my-app@0.0.1 storybook C:\test\my-app
> storybook dev -p 6006

@storybook/core v8.4.7

info => Starting manager..
info => Starting preview..
The following Vite config options will be overridden by SvelteKit:
  - base
Using existing cloned repo
ℹ [paraglide] Compiling Messages into ./src/lib/paraglide
Forced re-optimization of dependencies
╭──────────────────────────────────────────────────╮
│                                                  │
│   Storybook 8.4.7 for sveltekit started          │
│   1.74 s for manager and 4.1 s for preview       │
│                                                  │
│    Local:            http://localhost:6006/      │
│    On your network:  http://172.23.64.1:6006/    │
│                                                  │
╰──────────────────────────────────────────────────╯
12:19:53 PM [vite] ✨ new dependencies optimized: react/jsx-runtime, @storybook/blocks, @mdx-js/react
12:19:53 PM [vite] ✨ optimized dependencies changed. reloading
12:20:41 PM [vite] ✨ new dependencies optimized: @inlang/paraglide-sveltekit/internal
12:20:41 PM [vite] ✨ optimized dependencies changed. reloading

repo: storybookjs/addon-svelte-csf


text:
Support for SauceLabs Live

Because SauceLabs Live supports mobile devices in the browser (similar to appetize), is it possible to integrate with Storybook Native?

Hey @jgornick, I'm not familiar at all with SauceLabs Live but this is definitely possible as long as it provides you a public API key that can be used to access your mobile app somehow.
To support this, there needs to be a new SauceLabs Live controller that is similar to the Appetize one
https://github.com/storybookjs/native/blob/master/packages/controllers/src/controllers/AppetizeEmulatorController.ts
and the Controller Factory must have some logic to construct that specific controller
https://github.com/storybookjs/native/blob/master/packages/controllers/src/manager/controllerFactory.ts#L9

@jgornick Did creating the controller and controller factory work for SauceLabs?

Hey @migueln1987! Sorry, but we never got around to integrating SauceLabs.

@jgornick thanks for the reply. I didn't think I was going to get one back from a post from two or three years ago haha. Did you find a different solution? Airbnb has Showkase but it doesn't have controls to mess around with the components.

repo: storybookjs/native


text:
Updated v3 logo

Moved old files to v2 directory
Moved new files from @SachaG to v3
Updated README colors

BTW: I liked the old logs. What's the reason for the change?

@arunoda we just did a small refresh for the v3 release, heavily inspired by the v2 logo but softening the colors slightly and making it a little more playful. you can see the full discussion here:
https://github.com/storybooks/storybook/issues/1100

authors: arunoda shilman

repo: storybooks/pres


text:
Add react-docgen props to info addon

What I did
@jribeiro created #1505 to fix that and I'm making some minor changes to fix merge conflicts and redundant package.json requirements.
The original PR got automatically closed by GitHub when I tried to push to his branch so here's a new PR.
How to test
run cra example app

Hey @jribeiro, this seems to work for me without the .babelrc for react elements without flow. if you check out this branch, the DocgenButton will display info whereas the TypedButton does not.
How were you able to make the flow type work with docgen?

Removing in progress label since I don't think flow types are possible with the way our babel plugin works.

Flow type is possible and should work just fine as implemented on the initial commit... you might need the flow-bin package though. I’ve just got back from holidays and been quite busy but should be able to take a look soon if you’re actually looking for contributions to the project

@jribeiro my bad, thanks for the update and heads up! I figured I haven't heard anything for a week so I might as well merge the parts I've tested.
We can give this another try. I'd love to support flow and add some documentation for it for Storybook. I think I might need to add a dependency or two to the example app and throw some flow tests in.

I opened up a separate PR to add Flow type removal to the default Babel config.
https://github.com/storybooks/storybook/pull/1621

I added back the flowtype example and is working fine without additional modules as can be seen on  this comment:
https://github.com/storybooks/storybook/pull/1623#issuecomment-321051292
And this screenshot:

Also added some more information to https://github.com/storybooks/storybook/pull/1621 explaining why the babel-preset-flow is not needed.
Hope this helps.
Best
Joao

Ah! One last thing, with the imminent release of React Docgen version 3, you'll have problems with the hard coded dependency on react-docgen as seen on babel-plugin-react-docgen package https://github.com/storybooks/babel-plugin-react-docgen/blob/master/package.json#L31
This should be a peerDependency and not a dependency IMO but anyways version 3 brings
signature types - say () => * which this merge request already supports.

@jribeiro the babel-plugin-react-docgen needs a lot of work to make it work optimally. We basically check to see if it's a react component first, then pass it over to docgen. Docgen then checks if its a valid component again.
We still miss some edge cases in the babel plugin in terms of detecting react components and I haven't tested it with docgen 3 yet. If you want to take a shot at it, feel free to open a PR.
I think peerDep * is something we can explore, ideally with a fallback of some sort so users don't have to manually install a version.

Cool. I'll try to have a look over the next couple of days. Cheers

@danielduan
I've seen this warning in cra-kitchen-sink:
warning.js:35 Warning: DocgenButton: type specification of prop `style` is invalid; the type checker
 function must return `null` or an `Error` but returned a function. You may have forgotten to pass an
 argument to the type checker creator (arrayOf, instanceOf, objectOf, oneOf, oneOfType, and shape all
 require an argument).

Fixed the error and added a bunch more example docgen types.

authors: UsulPro danielduan jribeiro

repo: storybooks/storybook


text:
Use version from most recent update

If the major version changes, the login would not work.
Instead of manually typing it, what about requesting most recent version no. on startup?

Not planned and will not. Current API will work without error after update unless you are using ChatFeed or accessing internal network part. Also the update is still on draft and incomplete

Do you have any problems when applying the content of this issue?

authors: foliter starlesssss storycraft

repo: storycraft/node-kakao


text:
How to get the latest state in useUnmount ?

Is your feature request related to a problem? Please describe.
Imagining you implemented a counter component and would like to log the latest count when component unmount.
const Comp = () => {
  const [count, setCount] = useState(0);
  useUnmount(() => {
    console.log("comp unmount", count);
  });
  return (
    <>

Count: {count}

      <button onClick={() => setCount(count + 1)}>+</button>
    </>
  );
};

Because useUnmount use useEffect with deps====[]. The first rendered callback console.log("comp unmount", 0); was cached and won't update. So in the above example, the output will always be 0 rather than the latest count value.
Describe the solution you'd like
A clear and concise description of what you want to happen.
I create a demo at https://codesandbox.io/s/funny-dirac-z0cl9
There are two versions on useUnmount, one is from react-use and another is wroten by useRef and useEffect.
You should

Click show / hide button to mount the counter component.
Click + button to change the value
Click show /hide button again to unmount the counter
See console logs

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
useUnmount should cache callback by the second param deps as same as other hooks like useEffect, useCallback and etc.
useUnmount(callback) means callback won't be cached and the latest rendered callback will be called.
useUnmount(callback, [count] means callback cache will update if count changed.
useUnmount(callback, []) mans callback will be cached for the first time rendering and won't update anymore.
cc:  @byunicorn

It should not use the deps, but its definely a bug.
I'll take a look today.

:tada: This issue has been resolved in version 13.8.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: malash streamich xobotyi

repo: streamich/react-use

license: Unlicense


text:
IAM authorization for MSK?

Hello,
I am wondering if there is any documentation around connecting Jikkou to Amazon Managed Kafka Service (MSK) using IAM roles?
Amazon provide a module for this here: https://github.com/aws/aws-msk-iam-auth
I am using the Docker image streamthoughts/jikkou:latest@sha256:f8b4230752d276330ee071e7d4160e206fd257f4d66bc8efac1c7ed6dafe1197

I was to get this working by including the required iam jar and rebuilding.      see https://github.com/streamthoughts/jikkou/compare/main...chrisoberle:jikkou:main
Then i configured the aws cli with the appropriate creds and used a jikkou config like this:
❯ cat ~/.jikkou/config
{
  "currentContext" : "sandbox",
  "sandbox" : {
    "configFile" : null,
    "configProps" : {
      "kafka.client.security.protocol" : "SASL_SSL",
      "kafka.client.sasl.mechanism" : "AWS_MSK_IAM",
      "kafka.client.sasl.jaas.config" : "software.amazon.msk.auth.iam.IAMLoginModule required;",
      "kafka.client.sasl.client.callback.handler.class" : "software.amazon.msk.auth.iam.IAMClientCallbackHandler",
      "kafka.client.bootstrap.servers" : "SASL IAM BOOTSTRAP SERVERS"
    }
  }
}

I think this has been resolved in https://github.com/streamthoughts/jikkou/releases/tag/v0.22.0 via https://github.com/streamthoughts/jikkou/pull/212.

authors: chrisoberle joschi njlr

repo: streamthoughts/jikkou


text:
How to generate real token, use form for production?

I've adapted one of these nice examples, and have it working. However, it just generates an example token and doesn't actually show up on my Dashboard in Stripe for testing. How can I get this working and closer to production-ready?
Using other form examples, I have gotten results that show on the Dashboard, but I'm not sure what to do to get this one working.
Thanks for any help.

Okay, I was wrong, it was getting submitted, and showing up in the Dashboard Log. I expected it to show in Events, but it wasn't.
I did discover that you need to change the token from being displayed on the form after submission, to being included as a hidden field, to be transmitted to Stripe. For any other newbies working with these example forms, in index.js, under if (result.token), take out the example.querySelector('.token').innerText = result.token.id; line and insert:
        var form$ = $("#payment-form");
        var token = response['id'];
        // insert the token into the form so it gets submitted to the server
        form$.append("<input type='hidden' name='stripeToken' value='" + token + "' />");
        // and submit
        form$.get(0).submit();

At least, that seems to work. If I am wrong, please correct me. Thank you!

I'm having the same issue as well. I tried jamminjames fix and it doesn't seem to be working.
If a Stripe employee could comment on this and provide a complete example that would show up in my dashboard, that would be nice.
@asolove-stripe

Hi @jamminjames and @GeoffLedak! This is a repo for our examples of ways to style elements, so it's not the fastest or most helpful way to get answers on your Stripe integration. Please contact Stripe Support to get faster and better answers.
After calling stripe.createToken, you will need to send that token back to your server in order to use it to create charges. The method @jamminjames illustrates with adding it to a checkout form is one way to do that.
@GeoffLedak I'm not sure exactly what issue you're having. Our Quickstart guide has everything you should need to do to create a testmode card token with Elements. If you are still having trouble, I'd recommend contacting support (above), as they can see the details of your account and give you more detailed suggestions.

authors: GeoffLedak asolove-stripe jamminjames

repo: stripe/elements-examples


text:
Unable to resolve module ../../package.json

Describe the bug
Hello! I am quite new to React Native and trying to integrate Stripe using @stripe/stripe-react-native. After initializing the library following the installment guide on Stripe (https://stripe.com/docs/payments/accept-a-payment?platform=react-native&ui=custom), I get the error below and not sure how to solve this (I don't know if this is a bug or not).
Unable to resolve module ../../package.json from /Users/.../node_modules/@stripe/stripe-react-native/lib/commonjs/components/StripeProvider.js: None of these files exist: *node_modules/@stripe/stripe-react-native/lib/package.json

Versions
react: 17.0.2
react-native: 0.66.4
stripe-react-native: 0.2.3
babel: 7.12.9
running device: iOS 15 simulator

Also I am developing in React cli (not expo)
Is there anything else I need to integrate the library other than yarn add and pod install ? Any help would be much appreciated! Thanks a lot in advance!

I started to get the same issue a few minutes ago, it happened after I deleted (for reasons) the yarn lock file and installed everything again.

@fdelacruzsoto
found any solutions ... ?

this was my bad. I had wrong settings in metro.config.js. Closing!

@yanzdog what was the setting you had in metro that was causing the issue? I'm running into the same problem in my app.

@alekhinen @jukaha
I am using https://github.com/apollographql/apollo-client for api client and added some changes to metro config referring to this change log. (https://github.com/apollographql/apollo-client/blob/main/CHANGELOG.md#apollo-client-354-2021-11-19).
However, require("metro-config") was looking at wrong path and causing this stripe error. So I corrected it to the right path which is require('metro-config/src/defaults/defaults').
Hope this helps!

@jukaha @alekhinen I was able to find a workaround to this issue here hope it helps!

authors: Kinzito17 alekhinen fdelacruzsoto yanzdog

repo: stripe/stripe-react-native


text:
Replace the visitor counter on the home page

Still a relic from my old website. Counter itself can stay but at least remove the text of who interacted, since we are not tracking this at this moment

Retry styles counter added

repo: stronk-dev/LivepeerEvents


text:
Problem with guid being repeated

Not urgent, it is solved with recomputing or reloading GH-file

Not sure of the context here, but if you the Loads were modified from the FdModel you need to set Overwrite to True.

I'm not changing anything, just adding supports and loads. I put the files here:
C:\Users\JohannaRiad\StruSoft AB\StruParam - Projects\femdesign-api\Files for debugging\Guid problem
It works when you open the file, but if you try removing or adding the cables to loads for example you should be able to replicate the error

On which build are you experiencing this?

Right now I have the master build installed and get it on that. I think I got it on 20.2.0 as well yesterday

Did not clone model causing elements to be added several times on re-run.

Fixed on 20.2.0

authors: JRiad andosca

repo: strusoft/femdesign-api


text:
Add columns for sorting by last MTSS, NGE and 10GE on school overview, homeroom and section

Who is this PR for?
high school teachers, JR and other NGE teachers in particular
What problem does this PR fix?
short-term fix for not being able to find which students have recently had NGE notes.
What does this PR do?
Updates the school overview page, homeroom page and section page to add columns for last MTSS meeting, and in the high school last NGE meeting and 10GE meeting.  Per JR, they don't use MTSS at the high school but do still have SST.  This also reorders the columns to put house and counselor and homeroom on-screen.
In the process, a test bug surfaced where the students created by TestPals don't have an enrollment_status set, so this fixes that as well.
Screenshot (if adding a client-side feature)
Overview
before, HS:

after, HS:

before, K8:

after, K8:

Homeroom
before, HS:

after, HS:

before, K8:

after, K8:

Section
before, HS:

after, HS:

Checklists

[x] Author checked latest in IE - School Overview
[x] Author checked latest in IE - Homeroom Page
[x] Author checked latest in IE - Section Page
[ ] Reviewer checked latest in IE - School Overview
[ ] Reviewer checked latest in IE - Homeroom Page
[ ] Reviewer checked latest in IE - Section Page
[x] Author improved specs for code in need of better test coverage
[x] Author included specs for new code

@alexsoble Can you help review this when you get a chance?  Ideally we'd ship this Thursday ahead of the 10GE meeting Friday morning.

hmm, I'm stumped on why the authorizer_spec is failing, and pushed some debugging comments here: https://github.com/studentinsights/studentinsights/pull/1482/commits/5fe28fc925e85ec5a1300f06d41c6d996a42e347.  I'll take another look at this Thursday.

@kevinrobinson Reviewing now! 😄

@kevinrobinson I dove into the failing TestPals homeroom expectation since that seems like the biggest pain point on the PR right now.
I got the spec to go green by removing this line from the reindex! method on TestPals:
Homeroom.destroy_empty_homerooms

What's happening is that when we reindex!, many of the homerooms don't have their students_count counter cache set properly, so our Ruby code thinks they're "empty" and deletes them. Here's a SO article about this kind of rspec/counter cache issue: https://stackoverflow.com/questions/12171067/rspec-testing-of-counter-cache-columns-returning-0
I tried adding Homeroom.all.each { |homeroom| homeroom.reload } to reindex!, but it didn't fix the spec. So I think the simplest way to get the spec to go green is to remove the destroy_homerooms line. None of these homerooms are really empty so our TestPals don't benefit from us removing that line, as far as I can tell.

@alexsoble awesome, thanks for the help!  I forgot I had added that, and there's no need for that particular line here so it's gone now. 👍

@kevinrobinson 😎 😎

authors: alexsoble kevinrobinson

repo: studentinsights/studentinsights


text:
20191203 微软系统设计模式之 Cache-Aside Pattern

https://docs.microsoft.com/zh-cn/previous-versions/msp-n-p/dn589799(v=pandp.10)
标题：Cache-Aside Pattern
原文链接：https://docs.microsoft.com/zh-cn/previous-versions/msp-n-p/dn589799(v=pandp.10)
本文是微软系统设计模式的第 1 篇--缓存设计 Cache-Aside 模式，共计 24 篇，均为常见的系统设计模式，比较有意思可以先尝试翻译翻译，例子是 C# 语言的，如果能转成 Go 是最好了，可以新建一个目录单独存储这一系列。
译者自己根据原文翻译，译文保存为 markdown 格式，并附上尾部的签名。
---

https://docs.microsoft.com/zh-cn/previous-versions/msp-n-p/dn589799(v=pandp.10)

作者：[Design Patterns ](https://docs.microsoft.com/zh-cn/previous-versions/msp-n-p/dn600223(v=pandp.10))
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)

本文由 [GCTT](https://github.com/studygolang/GCTT) 原创编译，[Go 中文网](https://studygolang.com/) 荣誉推出

https://blog.csdn.net/ethanwhite/category_9267561.html
看上去已经有人翻译了

https://github.com/SapphireWriter/Cloud-Design-Patterns

https://blog.csdn.net/ethanwhite/category_9267561.html
看上去已经有人翻译了

收到～

authors: watermelo weibobo

repo: studygolang/GCTT


text:
homework_1: added logical diagram

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
What did you learn from the changes you have made?
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

Good Job!

For HW2, in Where query task you missed option2 and order by at the end, others correct.

For HW3, the more accurate type of join for Aggregate query is left join, and for date query group by month and year as well.

HW4 marked, Passed.

HW5 missing.

HW 5 , 6 Marked, Passed.

authors: SidraBushra stumac

repo: stumac/sql