text:
Bad subtitle rendering HTML Character Entities how to fix

Have you read the Tutorials?
Yes.
Have you read the FAQ and checked for duplicate open issues?
Yes.
If the question is related to FairPlay, have you read the tutorial?
Not related.
What version of Shaka Player are you using?
4.10.2
What browser and OS are you using?
Latest Chrome. Not reproducible on Safari due to the rendering of Closed Captions being handled by the device directly.
Please ask your question
i am using XML form and embedded in MP4 and not showing correctly

document.addEventListener("DOMContentLoaded", function () {
shaka.polyfill.installAll();
    const videoElement = document.getElementById("video");
    const videoContainer = document.getElementById("video-container");
    const player = new shaka.Player(videoElement);

    window.player = player;
    const thumbnailContainer = document.getElementById(
      "thumbnail-container"
    );
    const thumbnail = document.getElementById("thumbnail");
    // UI setup
    const ui = new shaka.ui.Overlay(player, videoContainer, videoElement);
    const controls = ui.getControls();

    const defaultConfig = {
      controlPanelElements: [
        "backward",
        "play_pause",
        "forward",

        "time_and_duration",
        "spacer",
        "mute",
        "volume",
        // "language",
        // "text_settings",

        "overflow_menu", // 3 dots inside quality speed and pip
        //"playback_rate",
        // "cast",
        //"lock",
        "picture_in_picture",
        //"quality",
        "fullscreen",
      ],
      overflowMenuButtons: [
        "quality",
        "captions",
        "language",
        "playback_rate",
      ],
      seekBarColors: {
        base: "rgba(99, 99, 99, 1)",
        buffered: "rgba(255, 147, 58, 1)",
        played: "rgba(255, 147, 58, 1)",
      },

      enableTooltips: true,
      // useNativeHlsOnSafari: true,
      // textTrackVisibility: true,
      // playbackRates: [0.5, 0.75, 1, 1.25, 1.5, 1.75, 2],
      // fastForwardRates: [2, 4, 8, 1],
      // rewindRates: [-1, -2, -4, -8],
      // customContextMenu: true,
      // contextMenuElements: ["statistics"],
      // statisticsList: ["width", "height", "playTime", "bufferingTime"],
    };

    ui.configure(defaultConfig);

    ui.getControls();

    async function loadVideo() {
      try {

        const url = "myVideo.mpd";
        await player.load(url);
        await player.setTextTrackVisibility(true);

      } catch (error) {
        console.error("Error loading manifest:", error);
      }
    }

    loadVideo();
  });

  how to fix


text:
Upgrading from 3.0 to 5.0

Wanted to know the best steps to upgrade from 3.0 to 5.0.
I didn't see any guides for 3,4 or 5 in the changelog.md  (like you had for 1->2 or 2->3)
I've already done the gem update but wasn't clear on changes to get the latest react / react router or any other changes in /client
Thanks

You can find out a lot by looking at the history and latest state of the https://github.com/shakacode/react-webpack-rails-tutorial example app.  E.g. if you look at the git history of when the gem/npm module was bumped you can see what changed at the same time.

@murtali that means you didn't have to do anything. If you want to use the new features, that's up to you. There might be some deprecations.

source: gharchive/issue

authors: justin808 murtali thewoolleyman

license: MIT

license_type: permissive

license_source: github-api


text:
Clear shared redux stores when server rendering

Per https://github.com/shakacode/react_on_rails/issues/774#issuecomment-290328842, we should clear the redux stores before populating it.
The potential bug is that there are some stores with data from unrelated requests sitting around.
This can chew up memory and lead to other unexpected consequences.
Steps to fix:

Add a function in the JS library to clear all shared redux stores.
Call that function from https://github.com/shakacode/react_on_rails/blob/master/app/helpers/react_on_rails_helper.rb#L346, prepending this to the result.

See #774 for more details.

@udovenko indicated interest, so I'll flag this one as taken.

@justin808 Not sure I see the way to reset the store. Each project has its own set of reducers and its own logic for bootstrapping the data to store. So resetting the store state should be individual for each JS server bundle.

Just clear the global map.
https://github.com/shakacode/react_on_rails/blob/master/node_package/src/StoreRegistry.js#L4
hydratedStores.clear() or something like that...

You mean clear stores registration completely? Feels like we will loose some benefits form having initiated stores on the next request...

For the reasons you raised, we don't want any hydrated stores on the next call.

Ok, I'll see what I can do. Can't promise anything for sure unfortunatenly...

@justin808 I've forked them gem and tried to reproduce an issue. But it seems that ReactOnRails creates and re-registers Redux store before every component is renderd on the server. It allways calls storeGenerator(reduxProps, railsContext) on https://github.com/shakacode/react_on_rails/blob/master/app/helpers/react_on_rails_helper.rb#L345. Store generator returns new store created with combineReducers and createStore. So it seems store state cannot be shared across components render on the server.
To test it a bit more I added consoel.log('new store!') to https://github.com/shakacode/react_on_rails/blob/master/spec/dummy/client/app/stores/SharedReduxStore.jsx#L12. Here is a console replay from server for http://0.0.0.0:5000/server_side_hello_world_shared_store:
[SERVER] new store!
[SERVER] RENDERED ReduxSharedStoreApp to dom node with id: ReduxSharedStoreApp-react-component-0 with railsContext: {"inMailer":false,"i18nLocale":"en","i18nDefaultLocale":"en","href":"http://0.0.0.0:5000/server_side_hello_world_shared_store","location":"/server_side_hello_world_shared_store","scheme":"http","host":"0.0.0.0","port":5000,"pathname":"/server_side_hello_world_shared_store","search":null,"httpAcceptLanguage":"ru-RU,ru;q=0.8,en-US;q=0.6,en;q=0.4","somethingUseful":"REALLY USEFUL","serverSide":true}
[SERVER] This is a script:"
"(/script>


text:
CSS Modules SSR doesn't output anything

I can see the class being applied, but the CSS is not there. I'm using the server config only:
https://github.com/shakacode/react-webpack-rails-tutorial/blob/master/client/webpack.server.rails.build.config.js#L55-L65

If you want personalized help on this, please consider our Coaching Plan.
Your question is specific to your project rather than this project, so it's best handled privately.


text:
🛑 Shakedown Social - Uploads is down

In f95420d, Shakedown Social - Uploads (https://files.shakedown.social/accounts/avatars/109/357/389/718/265/462/original/dd80d2c95e48cfd2.jpeg) was down:

HTTP code: 403
Response time: 287 ms

Resolved: Shakedown Social - Uploads is back up in 3f33bdd.

repo: shakedown-social/upptime


text:
spread props

say I have a bunch of props to spread like in jsx, how can I achieve that? The following doesn't work
const props = `x=${x} y=${y}`
return bel`<div ${props} />`

I believe you can just do
const props = {x: 1, y: 2}
return bel`<div ${props} />`

Thank you!

authors: itajaja timwis

repo: shama/bel


text:
Update pt-br translation

Short description of what this resolves:
The current translation to Portuguese (Brazil) is all machine-translated nonsense.
I have translated all the strings from the original English file.

Nice job, Rodrigo.

source: gharchive/pull-request

repo: shanalikhan/code-settings-sync


text:
why execute time is too long than original datasource

Use the same simple sql,  original Datasource execute time is about 8ms per request
but, replace the datasource to Sharding jdbc, execute time will increase to 27ms per request, i loged the executing time what I found are SS only select from one of the ten tables,  SS router time is about 2ms, and SS execute time is about 2ms , what does the other 10ms time cause???
use id hash, 10 sub tables , test sql is SELECT id, name FROM i_test where id = "1"
sharding jdbc core 2.0.3
Thank you

could you explain why you close by issue so quickly that create by yourself without any reason?

the question were fixed by myself, It is not issue of SS, thank you for reply.

authors: baisijian terrymanu

repo: sharding-sphere/sharding-sphere


text:
循环查询分表，空指针异常

条件：
sharding-jdbc  1.5.4
mybatis   3.3.0
mybatis-spring  1.2.3
用sharding-jdbc对某张表做了分表
配置：

问题描述：
执行下面伪代码查询，第一次循环查询正常，第二次循环查询报空指针异常：
伪代码
for(String id : voucherGroup){
Map<String, Object> map = new HashMap<String, Object>();
map.put("periodId", id);
int count = accountEntryMapper.selectCountByPeriodId(map);
}
sql

异常

请在github上提供完整重现DEMO，以便跟进调试。

未提供版本号，怀疑是版本过旧导致。请用最新版本尝试。如仍有问题，请提供可重现的demo。这个isdue我先关了

由于长时间无反馈，目前的信息并不足以定位问题。只能怀疑该问题与#387是一个问题，因此先关闭了。

authors: haocao panhaicheng terrymanu

repo: shardingjdbc/sharding-jdbc

license_source: bigquery


text:
新）トランザクション

バックエンドにて、
・トランザクション実装
　CRUDが正常に機能するように

現状必要なしかも…


text:
Allow copy code snippet with cursor

Right now on the website under getting started If I want to copy a text I can do it via the copy button:

It would be nice if we could copy the text by marking it with the mouse as well, for example:

Thanks Tamir. We need to rewrite the documentation section anyway :)
But it's a very good suggestion.

repo: sharkio-dev/sharkio


text:
没有找到RFLA的实现

作者你好，代码库里没有找到RFLA相关的实现。请问文章中RFLA的结果（TABLE 6最后一行），它的base模型是什么？

here's the official implementation about RFLA : https://github.com/Chasel-Tsui/mmdet-rfla


text:
اضافه کردن درگاه پرداخت فن آوا کارت

من قصد استفاده از درگاه پرداخت فن آوا کارت رو داشتم اما توی پکیج شما این درگاه پرداخت موجود نبود

این مورد در pull request زیر رفع شد
https://github.com/shetabit/multipay/pull/131

repo: shetabit/multipay


text:
Cricitcal Error in authcheck.php

In authcheck.php the bot tries to get 'corpTicker' from the json but it should be 'ticker' this caused all my tickers to be removed. Fixed it by replacing

$corpTicker = (string)$corporationDetails['corpTicker'];

on line 335
with:

$corpTicker = (string)$corporationDetails['ticker'];

Will push something out now thanks!

authors: eifelgamedev shibdib

repo: shibdib/Dramiel

license: mit


text:
求助：2机8卡训练SFT时卡住

2机8卡训练SFT时卡住
单机4卡测试训练PT和SFT都没有任何问题，但是在2机8卡测试分布式训练时，会在SFT中卡住。
求助求助求助！请大佬帮忙看下什么原因?!
具体脚本和日志如下：
脚本（主机）：
CUDA_VISIBLE_DEVICES=0,1,2,3 \
    torchrun \
    --nproc_per_node 4 \
    --nnodes 2 \
    --master_addr 10.130.1.109 \
    --master_port 7860 \
    --node_rank 0 \
    supervised_finetuning.py \
    --model_type bloom \
    --model_name_or_path merged-pt \
    --train_file_dir ./data/finetune \
    --validation_file_dir ./data/finetune \
    --per_device_train_batch_size 4 \
    --per_device_eval_batch_size 4 \
    --do_train \
    --do_eval \
    --use_peft True \
    --fp16 \
    --max_train_samples 1000 \
    --max_eval_samples 10 \
    --num_train_epochs 1 \
    --learning_rate 2e-5 \
    --warmup_ratio 0.05 \
    --weight_decay 0.05 \
    --logging_strategy steps \
    --logging_steps 10 \
    --eval_steps 50 \
    --evaluation_strategy steps \
    --save_steps 500 \
    --save_strategy steps \
    --save_total_limit 3 \
    --gradient_accumulation_steps 1 \
    --preprocessing_num_workers 1 \
    --output_dir outputs-sft-v1 \
    --overwrite_output_dir \
    --ddp_timeout 30000 \
    --logging_first_step True \
    --target_modules all \
    --lora_rank 8 \
    --lora_alpha 16 \
    --lora_dropout 0.05 \
    --torch_dtype float16 \
    --device_map auto \
    --report_to tensorboard \
    --ddp_find_unused_parameters False \
    --gradient_checkpointing True

脚本（副机）：
CUDA_VISIBLE_DEVICES=0,1,2,3 \
    torchrun \
    --nproc_per_node 4 \
    --nnodes 2 \
    --master_addr 10.130.1.109 \
    --master_port 7860 \
    --node_rank 1 \
    supervised_finetuning.py \
    ...<同上>...

日志（主机）：
...<省略>...
labels: [tensor([ -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100,
         -100,  -100,  -100,  -100,  -100,  -100,  -100,  -100, 99464,     2],
       device='cuda:0'), tensor([  -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   6768,   7786, 130015,      2],
       device='cuda:0'), tensor([  -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,   -100,
          -100,  41381,    355,   9759,   8589,  12402,   1533,   1616,   2386,
         15388,   1570,  76353,  11111,    706,   9602,   7786,   2269,   4587,
         32622,    355,  21920,  67956,   1262,  21397,  74869,   9110,  19471,
         25011,    355,    706,   4198,   2405,   8107,  11812, 175337,    420,
          2293,   9759,   8589,  12402,   1570,  29434,   8967,    355, 100006,
         17549,   9759,   8589,  11575,   9759,   8589,   6167,    355,  90899,
         44498,   7640,  77684,    355,  67517,   5731,  17846,   5197,  11111,
        246141,    355,  11225, 168726,   6167,   4007, 117443,    420,      2],
       device='cuda:0')]
2023-11-01 10:40:24.574 | DEBUG    | __main__:main:1279 - Decode input_ids[0]: <pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad>A chat between a curious user and an artificial intelligence assistant. The assistant gives helpful, detailed, and polite answers to the user's questions.</s>USER: 原发性巨球蛋白血症的治愈率是多少？ ASSISTANT:40%</s>
2023-11-01 10:40:24.579 | DEBUG    | __main__:main:1282 - Decode labels[0]: <pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad><pad>40%</s>
trainable params: 3,145,728 || all params: 562,360,320 || trainable%: 0.5593794384354857trainable params: 3,145,728 || all params: 562,360,320 || trainable%: 0.5593794384354857

2023-11-01 10:40:24.722 | INFO     | __main__:main:1274 - *** Train ***
2023-11-01 10:40:24.722 | INFO     | __main__:main:1274 - *** Train ***

日志（副机）：
...<省略>...
The argument `trust_remote_code` is to be used with Auto classes. It has no effect here and is ignored.
2023-11-01 10:40:18.920 | DEBUG    | __main__:main:1097 - A chat between a curious user and an artificial intelligence assistant. The assistant gives helpful, detailed, and polite answers to the user's questions.</s>USER: 治疗阳痿吃什么药呢？，性生活一直很正常的，但是这段时间感觉性欲变低了，有时勃起都感觉很困难，试过许多的方法都没效果，听朋友说我这种情况可能会是早泄，想知道治疗早泄的药物？ ASSISTANT:男子早泄、早泄病症的再次发生，多由恣情纵欲，或青年误犯性交，至命门火衰，精气虚寒；或思量忧郁，伤损心脾；或因恐惧伤肾，也有因湿热下注，宗筋弛而痿的。但主要是肾阳虚衰而痿。肾阳为那身阳气之根本，有温煦形体，蒸化水液，增进围产生长发育等功能。肾阳虚衰则温煦失责，气化无权。因而再次发生畏寒肢冷，性机能减退。故见男子早泄不举或不坚，且伴发头晕目眩。</s>
The argument `trust_remote_code` is to be used with Auto classes. It has no effect here and is ignored.
2023-11-01 10:40:20.649 | INFO     | __main__:main:1213 - Fine-tuning method: LoRA(PEFT)
2023-11-01 10:40:20.649 | INFO     | __main__:main:1218 - Init new peft model
2023-11-01 10:40:20.650 | INFO     | __main__:main:1227 - Peft target_modules: ['dense', 'dense_4h_to_h', 'dense_h_to_4h', 'query_key_value']
2023-11-01 10:40:20.650 | INFO     | __main__:main:1228 - Peft lora_rank: 8
2023-11-01 10:40:20.947 | INFO     | __main__:main:1213 - Fine-tuning method: LoRA(PEFT)
2023-11-01 10:40:20.947 | INFO     | __main__:main:1218 - Init new peft model
2023-11-01 10:40:20.947 | INFO     | __main__:main:1213 - Fine-tuning method: LoRA(PEFT)
2023-11-01 10:40:20.947 | INFO     | __main__:main:1218 - Init new peft model
2023-11-01 10:40:20.947 | INFO     | __main__:main:1227 - Peft target_modules: ['dense', 'dense_4h_to_h', 'dense_h_to_4h', 'query_key_value']
2023-11-01 10:40:20.947 | INFO     | __main__:main:1228 - Peft lora_rank: 8
2023-11-01 10:40:20.947 | INFO     | __main__:main:1227 - Peft target_modules: ['dense', 'dense_4h_to_h', 'dense_h_to_4h', 'query_key_value']
2023-11-01 10:40:20.947 | INFO     | __main__:main:1228 - Peft lora_rank: 8
2023-11-01 10:40:20.948 | INFO     | __main__:main:1213 - Fine-tuning method: LoRA(PEFT)
2023-11-01 10:40:20.948 | INFO     | __main__:main:1218 - Init new peft model
2023-11-01 10:40:20.949 | INFO     | __main__:main:1227 - Peft target_modules: ['dense', 'dense_4h_to_h', 'dense_h_to_4h', 'query_key_value']
2023-11-01 10:40:20.949 | INFO     | __main__:main:1228 - Peft lora_rank: 8
trainable params: 3,145,728 || all params: 562,360,320 || trainable%: 0.5593794384354857
2023-11-01 10:40:24.389 | INFO     | __main__:main:1274 - *** Train ***
trainable params: 3,145,728 || all params: 562,360,320 || trainable%: 0.5593794384354857
trainable params: 3,145,728 || all params: 562,360,320 || trainable%: 0.5593794384354857
trainable params: 3,145,728 || all params: 562,360,320 || trainable%: 0.5593794384354857
2023-11-01 10:40:24.690 | INFO     | __main__:main:1274 - *** Train ***
2023-11-01 10:40:24.695 | INFO     | __main__:main:1274 - *** Train ***
2023-11-01 10:40:24.709 | INFO     | __main__:main:1274 - *** Train ***

nvidia-smi 查看到的显卡状态：
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 515.65.01    Driver Version: 515.65.01    CUDA Version: 11.7     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  Tesla V100S-PCI...  On   | 00000000:00:0D.0 Off |                    0 |
| N/A   41C    P0    56W / 250W |   1917MiB / 32768MiB |    100%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  Tesla V100S-PCI...  On   | 00000000:00:0E.0 Off |                    0 |
| N/A   39C    P0    51W / 250W |   1917MiB / 32768MiB |    100%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   2  Tesla V100S-PCI...  On   | 00000000:00:0F.0 Off |                    0 |
| N/A   39C    P0    53W / 250W |   1917MiB / 32768MiB |    100%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   3  Tesla V100S-PCI...  On   | 00000000:00:10.0 Off |                    0 |
| N/A   40C    P0    53W / 250W |   1917MiB / 32768MiB |    100%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A   4049068      C   ...iant/anaconda3/bin/python     1913MiB |
|    1   N/A  N/A   4049069      C   ...iant/anaconda3/bin/python     1913MiB |
|    2   N/A  N/A   4049070      C   ...iant/anaconda3/bin/python     1913MiB |
|    3   N/A  N/A   4049071      C   ...iant/anaconda3/bin/python     1913MiB |
+-----------------------------------------------------------------------------+

卡在1286行：
        train_result = trainer.train(resume_from_checkpoint=checkpoint)

通信问题？我不清楚你的环境，多机多卡可以用deepspeed，ds_report给下

我现在是全量SFT，单机6卡，在保存权重后会卡住。

authors: mymong nuoma shibing624


text:
CI: Add MacOs to runs-on, add rust fmt check

#441

ld: library not found for -lm

This means clang failed to load libm. Maybe we don't need the -lm option in runner.rs on macs?

Merged. Nice try :-)

authors: AI-Mozi yhara

repo: shiika-lang/shiika


text:
【FEAT】ISSUEのラベルを編集

概要
ISSUEのラベルを編集

close

repo: shilokuma-inc/IOSTemplateApp


text:
Getting all connected camera devices

Is there any way to get a list of all connected camera devices without using AForge?
Since OpenCV is crossplattform these kind of functions are not supported, but maybe someone here has an idea.
I can't use AForge due licence issues.

I have been using DirectShowLib, however it doesn't really show which cameras are connected rather which camera drivers are installed. In my case it doesn't really matter if the user picks the wrong camera so I didn't try to see if there is a way to check if the camera is connected. Going to check if there is a way to do it though.

There is way by using the Microsoft Expression Encoder (https://www.microsoft.com/en-us/download/details.aspx?id=27870)
var vidDevices = EncoderDevices.FindDevices(EncoderDeviceType.Video);
It's not what I am looking for, but it may help with your issue.

I created a simple device enumerator. Next step: Get friendly device names.
https://github.com/thohemp/OpenCVSharpCameraDeviceEnumerator

The following code gives you a list of connected devices and their supported configurations using MediaFoundation:
https://github.com/vvvv/VL.OpenCV/blob/master/src/VideoInInfo.cs
Hope that helps

So I got around to updating from v.3 => v.4.........now I just lost ALL my Cameras 😢

authors: XamtasticPenn ravazquez thohemp

repo: shimat/opencvsharp


text:
make '/remote/system returns 200 test' work

Hi,
just jumped in and don't know my way around yet but this seems to make the failing test work.

Coverage remained the same at 100.0% when pulling 1af1482ea544c44fb767ee4cb6afb674b43ce47e on alandyer:test-failing-0.1.7 into 35a080cf9264de5ccfcf5459b1592d2a92e6005b on shinyscorpion:master.

Coverage remained the same at 100.0% when pulling 39b1632d90ab42f77b4c97df2752c63b7554f29a on alandyer:test-failing-0.1.7 into 35a080cf9264de5ccfcf5459b1592d2a92e6005b on shinyscorpion:master.

authors: alandyer coveralls

repo: shinyscorpion/wobserver


text:
enhancement: Move player to another channel

I'm not quite sure if this is already possible, but is there a method to moving the bot / connected player to another channel?
As of now it seems, leaveVoiceChannel() and joinVoiceChannel() are the only way exposed in the library (I'm not familiar with the lavalink protocol, so manually doing this with the internal methods is out of reach for me).
It would be nice to have an easy to use function like moveVoiceChannel(). Or, any other sort of method to change channels without interrupting the player. (eg. changing "connection.channelId" and calling "updateConnection" or simply connection.update({chanelID: <id>}))

UPDATE: After a long while of toying about, I found that using connection.setStateUpdate() to update the channelId, setting the connection to State.RECONNECTING and calling connection.connect() worked! I still wish this was one function though, so I am updating the issue.

repo: shipgirlproject/Shoukaku


text:
Use tekton automation to generate operatorhub release artifacts

Follow Tekton's example to use automation to generate operatorhub release artifacts
@adambkaplan
@sbose78
https://github.com/tektoncd/operator/pull/307

Fixed by #27

authors: adambkaplan gabemontero

repo: shipwright-io/operator


text:
[1.12] filtering, warning and formatting fixes

Updated reactable to latest version to prevent console warnings
Fixed filtering on service inspect page
Fixed node column on service inspect page
Removed unnecessary console output for auth saga

Depends on #904

LGTM

authors: ehazlett tombee

repo: shipyard/shipyard


text:
Update protobuf@8.0

Build protobuf@8.0

:beers: @BrewTestBot has triggered a merge.

repo: shivammathur/homebrew-extensions


text:
Update grpc@8.2

Build grpc@8.2

:beers: @BrewTestBot has triggered a merge.


text:
Update php@8.4

Build php@8.4

:beers: @BrewTestBot has triggered a merge.

repo: shivammathur/homebrew-php


text:
Expose ParseTreeNode

Exposes ParseTreeNode to allow full matching of ParseTrees. Before, outputs of parsing couldn't be fully accessed because of the inability of construct variants of ParseTreeNode to match. Now, variants can be constructed and used for matching the ParseTreeNode enum, fully exposing ParseTree.

Coverage remained the same at 92.829% when pulling 8b7d754cfd695fae9a40a2171933cbaa172f00db on Axiomatic-Mind:main into 895aaa792c3d2dcb1f60d2db262eef3aab3970d1 on shnewto:main.

authors: Axiomatic-Mind coveralls

repo: shnewto/bnf


text:
[Bug] false resolving of home route

The resolving of the home route like it is done right now is not really safe.
https://github.com/shopware/frontends/blob/acd70e94cd252f05fb8c0f2032bac66b090d1934/packages/composables/src/useNavigationSearch.ts#L16
I see that there is a TODO-comment, but it doesn't really explain what the problem is.
For example we have multiple root-categories, one for the "normal" category tree, one for the footer-navigation and so on.
In our case, we do not get the correct root-category (as configured in the saleschannel) as the home category, but the footer category.

Hey @niklaswolf ! thanks for studying the code 💪🏻
You are right, the problem occures when there are more than one root category in the repository.
It's been changed to something more bullet-proof:
currently, for / path resolving, which means normally a "homepage", we use sessionContext.value?.salesChannel?.navigationCategoryId from the context. which is a wrapper category for main navigation:
https://github.com/shopware/frontends/commit/bf5549885516541e237c60ce1a2fda00080e1aff#diff-4cf41b529fdbc9ede59652256198b99eb400c04017588aaca4c912ce2bf3b7fbR23
Leave your feedback please, if it will work for you 🙏🏻

@mkucmus yes, that's exactly what was needed. With this change, the configuration from the saleschannel is respected. Thanks! :)
I'll therefore close this issue.

authors: mkucmus niklaswolf

repo: shopware/frontends


text:
Redirect loop when changing e-mail during guest checkout

Description
Steps to reproduce:

Put random item into cart
Start checkout
Choose guest checkout on /checkout/register page
On /checkout/confirm notice that your email address is wrong
Click browser back button
Change email in form
Submit

Expected behaviour:

A new guest account/session is created with the newly entered email and the customer is again on /checkout/confirm

Actual behaviour:

A redirect loop occurs

Possible Solution
My proposed solution to break this cycle would be to change the first check in \Shopware\Storefront\Controller\RegisterController::register as follows:
if ($context->getCustomer() && !$context->getCustomer()->getGuest()) {
    return $this->redirectToRoute('frontend.account.home.page');
}

A more detailed look into the handling of the various steps with regards to guest account handling couldn't hurt though.
Additional context
The redirect is triggered in \Shopware\Storefront\Controller\RegisterController::register, where if ($context->getCustomer()) leads to a redirect to frontend.account.home.page regardless of whether it's a guest account or not. \Shopware\Storefront\Controller\AccountProfileController::index(the target action) however starts with $this->denyAccessUnlessLoggedIn(); (default parameter $allowGuest = false), which redirects to the Login page, but \Shopware\Storefront\Controller\AuthController::loginPage again only checks for if ($context->getCustomer()) and redirects back to the account page - the endless loop begins. (The redirectTo parameter of the login page is set to the account page when the \Shopware\Core\Checkout\Cart\Exception\CustomerNotLoggedInException is handled in \Shopware\Storefront\Framework\Routing\StorefrontSubscriber::customerNotLoggedInHandler)

Added in Shopware issue tracker: https://issues.shopware.com/issues/NEXT-11790

Hey @lars-feyerabend, thank you for reporting this, and sorry for the late response.
I'm closing this issue, as this landed in our triage and we can not reproduce this on current shopware release.

This issue has since been fixed by Shopware. https://issues.shopware.com/issues/NEXT-17938

authors: lars-feyerabend lernhart mstegmeyer

repo: shopware/platform


text:
enable custom component config options to be mixed with native fields (custom sort order)

1. Why is this change necessary?
Currently if multiple config options are defined as mixed "input-field" and "component", "component"'s always have to be at the end of each card due to the constraints of <xsd:sequence>
2. What does this change do, exactly?
The change enables plugin developers to define components and input-fields in arbitrary order.
3. Describe each step to reproduce the issue or behaviour.
Define the following config options:
<card>
    <title lang="de-DE">Card Title</title>

    <input-field type="bool">
        <name>firstOption</name>
    </input-field>

    <component name="my-component">
        <name>secondOption</name>
    </component>

    <input-field type="bool">
        <name>thirdOption</name>
    </input-field>
</card>

You will get the following error:
Encountered an error while loading the configuration:Unable to parse file ".../config.xml". Message: [ERROR 1871] Element 'input-field': This element is not expected. Expected is ( component ). (in /var/www/shopware/public/ - line 93, column 0)
4. Please link to the relevant issues (if any).
5. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] I have created a changelog file with all necessary information about my changes
[] I have written or adjusted the documentation according to my changes
[] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hey @netzkollektiv, could you also please add an changelog?

@J-Rahe feel free to edit the pull request :-)

@netzkollektiv if you give me the requried data i may actually do that. if you take a look into our contribution guideline, we NEED your name(can be github name) and email(can be github mail). Without these we cant merge your PR.

Please use netzkollektiv & corporate at netzkollektiv.com.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-14211
Please use this issue to track the state of your pull request.

Hey @netzkollektiv, thanks for the PR, we have just merged it : )
(And the next time please provide the changelog from the beginning, you have an example and an template in the changelog folder and there is the bin/console changelog:create command to help you a bit).

authors: J-Rahe netzkollektiv shopwareBot


text:
Only select used fields of translation tables

1. Why is this change necessary?
Previously anytime a translated field was part of a query a full sub-select of the respective _translation table was joined to the main query. A "full sub-select" means a SELECT of all columns of the _translation table. This can result in a lot of overhead because depending on the storage engine of the database, e.g. mediumtext fields like product_translation.description require more page reads (i.e. disk access).
In complex, high cardinality queries, especially when they involve e.g. the product table, which doubles the number of joined translation tables due to requiring entity inheritance, this overhead can negatively influence the query execution plans. In fact, the same query (filtering orders based on their line items and respective products) that took a reasonable time in Shopware 6.5 ballooned to several hundred seconds with Shopware 6.6 due to a correction in filter evaluation, which leads to more joins of sub-selects in general.
2. What does this change do, exactly?

This PR reduces the selected fields of joined _translation tables to those that are actually needed for filtering or resolving TranslatedFields. It does not affect queries of _translation tables that are needed for loading translation associations.
This PR renames fallback_ join aliases in the generated queries to use override_ aliases, because their values in fact override the default translations, if available. This is just cosmetics, but IMHO makes the code (and generated queries) easier to understand.
This PR adds some more escaping to the queries that join _translation tables.
This PR currently does not add any new tests. ~I would like to get feedback first on the general approach as well as what kind of tests (unit, integration) are expected for these changes.~ All tests added in https://github.com/shopware/shopware/pull/3839 should still pass.

3. Describe each step to reproduce the issue or behaviour.
For simply seeing the difference in the generated SQL queries turn on your database's query log and send the following request to the admin API:
POST /api/search/product

{
    "filter": [
        {
            "type": "contains",
            "field": "name",
            "value": "foo"
        }
    ]
}

Generated SQL (old)
SELECT
    `product`.`id`,
    `product`.`product_number`,
    `product`.`auto_increment`
FROM `product`
LEFT JOIN `product` `product.parent`
    ON `product`.`parent_id` = `product.parent`.`id`
    AND `product`.`parent_version_id` = `product.parent`.`version_id`
LEFT JOIN (
    SELECT
        `product.translation`.product_id,
        `product.translation`.product_version_id,
        `product.translation`.meta_description AS `product.translation.metaDescription`,
        `product.translation`.name AS `product.translation.name`,
        `product.translation`.keywords AS `product.translation.keywords`,
        `product.translation`.description AS `product.translation.description`,
        `product.translation`.meta_title AS `product.translation.metaTitle`,
        `product.translation`.pack_unit AS `product.translation.packUnit`,
        `product.translation`.pack_unit_plural AS `product.translation.packUnitPlural`,
        `product.translation`.custom_search_keywords AS `product.translation.customSearchKeywords`,
        `product.translation`.slot_config AS `product.translation.slotConfig`,
        `product.translation`.custom_fields AS `product.translation.customFields`,
        `product.translation`.created_at AS `product.translation.createdAt`,
        `product.translation`.updated_at AS `product.translation.updatedAt`,
        `product.translation`.product_id AS `product.translation.productId`,
        `product.translation`.language_id AS `product.translation.languageId`,
        `product.translation`.product_version_id AS `product.translation.productVersionId`,
        `product.translation.fallback_1`.meta_description AS `product.translation.fallback_1.metaDescription`,
        `product.translation.fallback_1`.name AS `product.translation.fallback_1.name`,
        `product.translation.fallback_1`.keywords AS `product.translation.fallback_1.keywords`,
        `product.translation.fallback_1`.description AS `product.translation.fallback_1.description`,
        `product.translation.fallback_1`.meta_title AS `product.translation.fallback_1.metaTitle`,
        `product.translation.fallback_1`.pack_unit AS `product.translation.fallback_1.packUnit`,
        `product.translation.fallback_1`.pack_unit_plural AS `product.translation.fallback_1.packUnitPlural`,
        `product.translation.fallback_1`.custom_search_keywords AS `product.translation.fallback_1.customSearchKeywords`,
        `product.translation.fallback_1`.slot_config AS `product.translation.fallback_1.slotConfig`,
        `product.translation.fallback_1`.custom_fields AS `product.translation.fallback_1.customFields`,
        `product.translation.fallback_1`.created_at AS `product.translation.fallback_1.createdAt`,
        `product.translation.fallback_1`.updated_at AS `product.translation.fallback_1.updatedAt`,
        `product.translation.fallback_1`.product_id AS `product.translation.fallback_1.productId`,
        `product.translation.fallback_1`.language_id AS `product.translation.fallback_1.languageId`,
        `product.translation.fallback_1`.product_version_id AS `product.translation.fallback_1.productVersionId`
    FROM `product_translation` `product.translation`
    LEFT JOIN `product_translation` `product.translation.fallback_1`
        ON `product.translation`.`product_id` = `product.translation.fallback_1`.`product_id`
        AND `product.translation.fallback_1`.language_id = :languageId
        AND `product.translation`.product_version_id = `product.translation.fallback_1`.product_version_id
    WHERE
        `product.translation`.language_id = :languageId
) `product.product_translation`
    ON `product.product_translation`.`product_id` = `product`.`id`
    AND `product.product_translation`.product_version_id = `product`.version_id
LEFT JOIN (
    SELECT
        `product.parent.translation`.product_id,
        `product.parent.translation`.product_version_id,
        `product.parent.translation`.meta_description AS `product.parent.translation.metaDescription`,
        `product.parent.translation`.name AS `product.parent.translation.name`,
        `product.parent.translation`.keywords AS `product.parent.translation.keywords`,
        `product.parent.translation`.description AS `product.parent.translation.description`,
        `product.parent.translation`.meta_title AS `product.parent.translation.metaTitle`,
        `product.parent.translation`.pack_unit AS `product.parent.translation.packUnit`,
        `product.parent.translation`.pack_unit_plural AS `product.parent.translation.packUnitPlural`,
        `product.parent.translation`.custom_search_keywords AS `product.parent.translation.customSearchKeywords`,
        `product.parent.translation`.slot_config AS `product.parent.translation.slotConfig`,
        `product.parent.translation`.custom_fields AS `product.parent.translation.customFields`,
        `product.parent.translation`.created_at AS `product.parent.translation.createdAt`,
        `product.parent.translation`.updated_at AS `product.parent.translation.updatedAt`,
        `product.parent.translation`.product_id AS `product.parent.translation.productId`,
        `product.parent.translation`.language_id AS `product.parent.translation.languageId`,
        `product.parent.translation`.product_version_id AS `product.parent.translation.productVersionId`,
        `product.parent.translation.fallback_1`.meta_description AS `product.parent.translation.fallback_1.metaDescription`,
        `product.parent.translation.fallback_1`.name AS `product.parent.translation.fallback_1.name`,
        `product.parent.translation.fallback_1`.keywords AS `product.parent.translation.fallback_1.keywords`,
        `product.parent.translation.fallback_1`.description AS `product.parent.translation.fallback_1.description`,
        `product.parent.translation.fallback_1`.meta_title AS `product.parent.translation.fallback_1.metaTitle`,
        `product.parent.translation.fallback_1`.pack_unit AS `product.parent.translation.fallback_1.packUnit`,
        `product.parent.translation.fallback_1`.pack_unit_plural AS `product.parent.translation.fallback_1.packUnitPlural`,
        `product.parent.translation.fallback_1`.custom_search_keywords AS `product.parent.translation.fallback_1.customSearchKeywords`,
        `product.parent.translation.fallback_1`.slot_config AS `product.parent.translation.fallback_1.slotConfig`,
        `product.parent.translation.fallback_1`.custom_fields AS `product.parent.translation.fallback_1.customFields`,
        `product.parent.translation.fallback_1`.created_at AS `product.parent.translation.fallback_1.createdAt`,
        `product.parent.translation.fallback_1`.updated_at AS `product.parent.translation.fallback_1.updatedAt`,
        `product.parent.translation.fallback_1`.product_id AS `product.parent.translation.fallback_1.productId`,
        `product.parent.translation.fallback_1`.language_id AS `product.parent.translation.fallback_1.languageId`,
        `product.parent.translation.fallback_1`.product_version_id AS `product.parent.translation.fallback_1.productVersionId`
    FROM `product_translation` `product.parent.translation`
    LEFT JOIN `product_translation` `product.parent.translation.fallback_1`
        ON `product.parent.translation`.`product_id` = `product.parent.translation.fallback_1`.`product_id`
        AND `product.parent.translation.fallback_1`.language_id = :languageId
        AND `product.parent.translation`.product_version_id = `product.parent.translation.fallback_1`.product_version_id
    WHERE
        `product.parent.translation`.language_id = :languageId
) `product.product_translation.parent`
    ON `product.product_translation.parent`.`product_id` = `product.parent`.`id`
    AND `product.product_translation.parent`.product_version_id = `product.parent`.version_id
WHERE
    (`product`.`version_id` = :versionId)
    AND ((
        COALESCE(
            `product.translation.fallback_1.name`,
            `product.parent.translation.fallback_1.name`,
            `product.translation.name`,
            `product.parent.translation.name`
        ) LIKE :query
    ))
LIMIT 500

Generated SQL (new)
SELECT
    `product`.`id`,
    `product`.`product_number`,
    `product`.`auto_increment`
FROM `product`
LEFT JOIN `product` `product.parent`
    ON `product`.`parent_id` = `product.parent`.`id`
    AND `product`.`parent_version_id` = `product.parent`.`version_id`
LEFT JOIN (
    SELECT
        `product.translation`.`product_id`,
        `product.translation`.`product_version_id`,
        `product.translation`.`name` AS `product.translation.name`,
        `product.translation.override_1`.`name` AS `product.translation.override_1.name`
    FROM `product_translation` `product.translation`
    LEFT JOIN `product_translation` `product.translation.override_1`
        ON `product.translation`.`product_id` = `product.translation.override_1`.`product_id`
        AND `product.translation.override_1`.`language_id` = :languageId
        AND `product.translation`.`product_version_id` = `product.translation.override_1`.`product_version_id`
    WHERE
        `product.translation`.`language_id` = :languageId
) `product.product_translation`
    ON `product.product_translation`.`product_id` = `product`.`id`
    AND `product.product_translation`.`product_version_id` = `product`.`version_id`
LEFT JOIN (
    SELECT
        `product.parent.translation`.`product_id`,
        `product.parent.translation`.`product_version_id`,
        `product.parent.translation`.`name` AS `product.parent.translation.name`,
        `product.parent.translation.override_1`.`name` AS `product.parent.translation.override_1.name`
    FROM `product_translation` `product.parent.translation`
    LEFT JOIN `product_translation` `product.parent.translation.override_1`
        ON `product.parent.translation`.`product_id` = `product.parent.translation.override_1`.`product_id`
        AND `product.parent.translation.override_1`.`language_id` = :languageId
        AND `product.parent.translation`.`product_version_id` = `product.parent.translation.override_1`.`product_version_id`
    WHERE
        `product.parent.translation`.`language_id` = :languageId
) `product.parent.product_translation`
    ON `product.parent.product_translation`.`product_id` = `product.parent`.`id`
    AND `product.parent.product_translation`.`product_version_id` = `product.parent`.`version_id`
WHERE
    (`product`.`version_id` = :versionId)
    AND ((
        COALESCE(
            `product.translation.override_1.name`,
            `product.parent.translation.override_1.name`,
            `product.translation.name`,
            `product.parent.translation.name`
        ) LIKE :query
    ))
LIMIT 500

That simple example will usually not show a difference in performance (nor query execution plan). The following request is taken from one of our applications and will drastically improve in execution time with the fix (we noticed ~60x speed up in production environments; 215s (old) vs. 3,5s (new); 20k orders, 80k order line items, 1,5k products, MySQL v8.0.34):
POST /api/search/order

{
    "filter": [
        {
            "type": "multi",
            "operator": "and",
            "queries": [
                {
                    "type": "equals",
                    "field": "lineItems.type",
                    "value": "product"
                },
                {
                    "type": "not",
                    "operator": "and",
                    "queries": [
                        {
                            "type": "equals",
                            "field": "lineItems.product.id",
                            "value": null
                        }
                    ]
                },
                {
                    "type": "equalsAny",
                    "field": "stateMachineState.technicalName",
                    "value": [
                        "open",
                        "in_progress"
                    ]
                },
                {
                    "type": "equalsAny",
                    "field": "transactions.stateMachineState.technicalName",
                    "value": [
                        "paid",
                        "refunded_partially"
                    ]
                },
                {
                    "type": "multi",
                    "operator": "or",
                    "queries": [
                        {
                            "type": "prefix",
                            "field": "orderNumber",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "billingAddress.firstName",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "billingAddress.lastName",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "billingAddress.company",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "billingAddress.department",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "billingAddress.street",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "billingAddress.additionalAddressLine1",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "billingAddress.additionalAddressLine2",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "billingAddress.zipcode",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "value": "Foo",
                            "field": "billingAddress.city"
                        },
                        {
                            "type": "contains",
                            "field": "billingAddress.country.name",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "customerComment",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "deliveries.shippingOrderAddress.firstName",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "deliveries.shippingOrderAddress.lastName",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "deliveries.shippingOrderAddress.company",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "deliveries.shippingOrderAddress.department",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "deliveries.shippingOrderAddress.street",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "deliveries.shippingOrderAddress.additionalAddressLine1",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "deliveries.shippingOrderAddress.additionalAddressLine2",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "deliveries.shippingOrderAddress.zipcode",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "deliveries.shippingOrderAddress.city",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "deliveries.shippingOrderAddress.country.name",
                            "value": "Foo"
                        },
                        {
                            "field": "deliveries.shippingMethod.name",
                            "type": "contains",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "lineItems.product.name",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "lineItems.product.productNumber",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "lineItems.product.ean",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "lineItems.product.manufacturer.name",
                            "value": "Foo"
                        },
                        {
                            "type": "contains",
                            "field": "lineItems.product.manufacturerNumber",
                            "value": "Foo"
                        }
                    ]
                }
            ]
        }
    ]
}

4. Please link to the relevant issues (if any).
n/a
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

@svenmuennich Thanks for the PR, general approach looks fine. We are slightly worried that some breaks might occur so we would appreciate if you tackle the tests and then we can do another round of reviews, wdyt?

@svenmuennich yep integration tests would be useful here.

Hi,
LGTM  👍
It would be good when you test the following scenarios:

Filter with multiple fields in different levels of a Criteria
Filter with multiple languages and multiple fields
Full text search via term
Full text search criteria.queries
Mixed searches with filters and queries

I added the integration tests in a separate PR (https://github.com/shopware/shopware/pull/3839) to ensure that they cover the current behavior. I also rebased this PR accordingly.

@svenmuennich could you take a look at the phpstan failures please?

Linting looks good now ...

Sorry for the delay @svenmuennich - I was on holiday then battling with pipeline issues :D - Thanks for the improvements, it's merged now!

authors: AydinHassan OliverSkroblin svenmuennich

repo: shopware/shopware


text:
DRAFT: Try fix partial dataloading

The entity hydrator now only checks if criteria.fields is filled. If that's the case, all entities are loaded as partial entities.
However, entities are still being loaded and collections filled in the EntityReader. That's why there's also a one-time check here: $partial = !empty($criteria.fields).
See: https://github.com/shopware/shopware/issues/5114#issuecomment-2422344507

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Oliver Skroblin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant OliverSkroblin


text:
[BUGFIX] Use encodeURIComponent to encode semicolons

Description
encodeURI does not encode semicolons, which are not allowed in cookie values. encodeURIComponents does. Using encodeURI, the cookie will only be stored up to the first semicolon and thus cannot be completely retrieved afterwards.

Questions
Answers

BC breaks?
no

Tests pass?
yes

Related tickets?
SW-17497

How to test?
On javascript console: StorageManager.getLocalStorage().setItem("Foo", "Bar; Baz"); reload the page;  StorageManager.getLocalStorage().getItem("Foo"); // -> JSON decoding exception

Hey @m-knabe-reply,
thanks for your contribution. Your change looks good to me and makes sense.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-17509.
Please use this issue to track the state of your pull request.

Thank you for your contribution. This issue was fixed with commit 805c11e. I will close this PR now.

authors: htkassner klarstil m-knabe-reply shopwareBot


text:
Update metrics crate

The shortcut macros like counter! have been removed and the register macros like register_counter! have been renamed like counter!.
The register macros can be used in place of the shortcut macros since the shortcut macros were just registering and dropping a metric internally anyway.

I am no longer seeing the performance regression on CI or locally since https://github.com/shotover/shotover-proxy/pull/1463 was merged

repo: shotover/shotover-proxy


text:
Simplify storybook config

Why
Hey I was checking out the repo after seeing the talk at appjs conf and I came accross some storybook config that I thought could be simplified.
Congrats on launching the project, you've made something really cool here!
A lot of packages are included by default in addon-react-native-web so you don't need them listed explicitly. I've also changed the addon it to use a partial match for package names, so unless there are showtime packages you don't want to include then just @showtime is enough
How
I updated the main.js to remove packages from the module to transpile list if they are already included by default
Test Plan
I ran the storybook after making changes and it seems to run fine. If you have chromatic setup (which I think you do) then the visual tests will be a good way to validate this.

Thank you @dannyhw ❤

authors: dannyhw intergalacticspacehighway

repo: showtime-xyz/showtime-frontend


text:
feat/interoperability

This PR adds a new exercise about contract interoperability.
I had to update the compiler version to the last main for it to work.
Time spent: 3 hours

This item belongs to payment request #19A990 on OnlyDust:

from shramee to enitrat
14 items included
$500 for 1 day of work

authors: VeryDustyBot enitrat


text:
Flicker effect when skipping multiple stories

Hi Team,
First of all great work with the library. I am having a small problem in it. when i am uploading multiple picture to stories like for an example i have 4 picture to stories and out of which 3 have been seen and then i again click on the story section to view the fourth one, then there is a flicker in the rest of the 3 images which has been already read.
I don't want this  skipping effect  ,i want it to start directly from particular story number
Below is the video link You can observe the flicker effect when skipping progress bars
https://drive.google.com/file/d/1kpYIjovY3n6RLWrXHHrq0gE_ItDrFToU/view?usp=drivesdk

@Kitlabs  Hi, can you find a solution. I have same problem, can you help please. Thanks.

@Kitlabs Are you using a transparent Theme?? Thats likely the cause.

authors: Kitlabs ahmedmolawale mehmetergul

repo: shts/StoriesProgressView


text:
Border-less Markdown tables

I love how easy it is to reformat the current table, or all, in a Markdown file, but I'm not too found of the styling. I much prefer borderless tables.
Any chance you could add that?
There is another table formatter, https://marketplace.visualstudio.com/items?itemName=darkriszty.markdown-table-prettify, which detects the table style automatically. Would be really nice if you could do that too!

Thanks for using.
And sorry for my late reply.
I understood the request.
I was unexpected it, but good function!
I will consider it.
Perhaps, in May as adding config.

Thank you for waiting.
I released v1.2.1 and added borderless table configration.
Try tableformatter.markdown.tableEdgesType = "Borderless".

Awesome! I like it!
Thanks.

authors: LeviticusMB shuGH

repo: shuGH/vscode-table-formatter


text:
Problem with date year < 1900 and year = 0000

Hello there is a Problem with date's which are smaller then 1900 like '1876-01-30'
and also Problem with year "0000-00-00".
Last one I fixed it by
if ( $year === 0 || (int) $year == 0 ) {
return $excelTime;
}

fixed in 1.0.23

use raw values
$cell = "\0".'1985-01-13';
not "german time", there OS date/time/datetime format by default

yes I know it's using OS date format. But the Script is changing it automatic. So its Mixing now RAW Types and OS date. So it would be nice to tell the format for both. But this is maybe only an edge case.

if u have mixed dates <1900 and >1900, then use raw (string) values for all your dates
But the Script is changing it automatic -- setlocale temporary resets LC_NUMERIC to neгtral  for correct cast numbers to strings

authors: fapth shuchkin

repo: shuchkin/simplexlsxgen


text:
输入变量问题

请问输入变量中，groups和reduction_ratio是什么意义？

用于降低输入channel数，计算kernel时减少计算量，请参考原论文


text:
Use this project with recent GPU ?

Hello I have a 4080 (sm_89), according to the warning log CUDA is not compatible.
Is there a way to use a more recent version of CUDA/pytorch ?
I installed the project through the requirement package.

it results obviously by a :

Regards

same problem, no answers

In our case, we've opted for switching to a GPU compatible with CUDA11, specifically with version sm_75. While this approach is functional, it's not an optimal solution. Installing and configuring CUDA with a specific version can be challenging.

we switch to GTX 20xx

I would generally like to run the project somehow, even on a CPU, just to make it work even slowly. do I have a chance to do this?

I don't think you can run it on a CPU; TensorFlow requires a GPU. For now, I managed to run the project by changing the GPU, but I'm having issues generating the landmarks.

I managed to run it on an RTX4060.

It took me a couple hours, but I am happy with the results.

I managed to run it on an RTX4060.
It took me a couple hours to set up, but I am happy with the results.

Nice! Can you tell us how did you solve this problem?

authors: OchotonaPrinceps antoinersw imxtx sebaturen vladgohn


text:
Should we alway set engine_options.pool_timeout to zero？

engine_options = {
       'pool_size': 2,
       'pool_timeout': 1,
       'max_overflow': 0
 },

Once the concurrency exceed pool_size+max_overflow,  the program will deadlock.
I think the reason is the new-coming  request blocked at waiting for a connection,
Since tornado is single-thread model, this kind blocking will cause  deadlock (util timeout ).
Below is what I got from gdb, the program is waiting for a connection.
Traceback (most recent call first):
  File "/usr/lib/python3.7/threading.py", line 300, in wait
    gotit = waiter.acquire(True, timeout)
  File "/usr/lib/python3.7/site-packages/sqlalchemy/util/queue.py", line 162, in get
    self.not_empty.wait(remaining)
  File "/usr/lib/python3.7/site-packages/sqlalchemy/pool/impl.py", line 117, in _do_get
    return self._pool.get(wait, self._timeout)
  File "/usr/lib/python3.7/site-packages/sqlalchemy/pool/base.py", line 492, in checkout
    rec = pool._do_get()
  File "/usr/lib/python3.7/site-packages/sqlalchemy/pool/base.py", line 760, in _checkout
    fairy = _ConnectionRecord.checkout(pool)
  File "/usr/lib/python3.7/site-packages/sqlalchemy/pool/base.py", line 363, in connect
    return _ConnectionFairy._checkout(self)
  File "/usr/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 2276, in _wrap_pool_connect
    return fn()
  File "/usr/lib/python3.7/site-packages/sqlalchemy/engine/base.py", line 2242, in _contextual_connect
    self._wrap_pool_connect(self.pool.connect, None),
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 432, in _connection_for_bind
    conn = bind._contextual_connect()
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 420, in _connection_for_bind
    conn = self._parent._connection_for_bind(bind, execution_options)
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 313, in connection
    return self._connection_for_bind(bind, execution_options)
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/persistence.py", line 1604, in _connections_for_states
    connection = uowtransaction.transaction.connection(base_mapper)
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/persistence.py", line 374, in _organize_states_for_save
    base_mapper, uowtransaction, states
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/persistence.py", line 213, in save_obj
    ) in _organize_states_for_save(base_mapper, states, uowtransaction):
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/unitofwork.py", line 589, in execute
    uow,
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/unitofwork.py", line 422, in execute
    rec.execute(self)
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 2577, in _flush
    flush_context.execute()
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 2479, in flush
    self._flush(objects)
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 482, in _prepare_impl
    self.session.flush()
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 503, in commit
    self._prepare_impl()
  File "/usr/lib/python3.7/site-packages/sqlalchemy/orm/session.py", line 1036, in commit
    self.transaction.commit()
  File "examples/multi_databases.py", line 63, in get
    session.commit()
  File "/usr/lib/python3.7/site-packages/tornado/web.py", line 1699, in _execute
    result = await result

  <built-in method run of Context object at remote 0x7fc857aeb910>
  File "/usr/lib/python3.7/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/lib/python3.7/asyncio/base_events.py", line 1771, in _run_once
    handle._run()
  File "/usr/lib/python3.7/asyncio/base_events.py", line 534, in run_forever
    self._run_once()
  File "/usr/lib/python3.7/site-packages/tornado/platform/asyncio.py", line 148, in start
    self.asyncio_loop.run_forever()
  File "examples/multi_databases.py", line 106, in <module>
    IOLoop.current().start()

What happens if you skip pool_timeout altogether and just rely on SQLAlchemy to handle it?

The default pool_timeout is 30,   after 30s the blocking coroutine will raise Timeout Error and response 500. but the other new-coming request will continue block at waiting for connection. The deadlock will never be broken, unless there are no new-coming requests.

True, but if the timeout is disabled, then at some point the database would complain about too many connections and the responses would 500 anyway.
My proposal would be to not do anything of our own here, and just keep the SQLAlchemy defaults. Database connection bugs are tricky to debug, so I'd rather not interfere with those settings. :)

Yeah, It can't solve the 500 problem.  User should decide how to deal with it by themselves.

repo: siddhantgoel/tornado-sqlalchemy


text:
gitconfig includeIf directives does not work properly inside distrobox

[includeIf "gitdir:~/work/"]
    path = work.gitconfig

This config should load the config work.gitignore when in a repo which is a subdirectory to ~/work, and it works well on the host. However, it does not work when using git inside a distrobox for some reason.

Current solution is to map the distrobox's git to the host's

repo: sidusIO/sediment


text:
fix: tree grouping breaks if rows are assigned statically

Fixes the issue where  tree grouping breaks if rows are directly set on ngx-datatable without doing any async calls.
What kind of change does this PR introduce? (check one with "x")

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

@timowolf Could you please review this PR?
Thanks!

repo: siemens/ngx-datatable


text:
can't connect: message type: closed

Hi,
I've been using this project for a while without problems but since the last 2 days I've not been able to connect.
I get every time the following message on Chrome console while trying to connect to he API:
got message  {from: "meta", type: "closed"}
Above I get the following message:
WebSocket connection to 'ws://localhost:2019/' failed: Connection closed before receiving a handshake response
This happens every time I click on the Click to connect to API button.
Backend, API server and HTTP server seems to be running fine.

Hmm that's odd... Someone else had a similar error at #5 and #48. Which operating system do you use? Might it be a firewall issue for you?

Same here, it's been working well but it stopped. getting a
["Cmd",{"type":"update"}]

Not getting the ref like usual when trying to generate the QR code

@sigalor I am using Ubuntu 17.10
I followed the steps on #5 and everything seems fine.
Accesing http://10.135.1.5:2019/ (10.135.1.5 is the machine I am running the service on) shows a page with the following text:

Upgrade Required

@UrbanSwati Thanks for this info, now I know the cause of @nilsburg's error. Looking at the generateQRCode function of backend/whatsapp.py, you can see that the script currently wants the server to use WA Web version 0.2.9229, but apparently, the server does not support it anymore. Just exchange 9229 by 9547, because when you look at the websocket log of original WA Web using the Chrome developer console, you can see it requesting version 0.2.9547, thus this is the newest one.
A question to everyone: Is it possible to query the server for the newest WA Web version directly, i.e. without possibly receiving the ["Cmd",{"type":"update"}] message beforehand? This would allow the Python script to not rely on using a hardcoded version number.
@nilsburg, the Upgrade Required text is absolutely plausible, because a WebSocket server is listening on port 2019. Accessing it with a HTTP request does not really make sense.

Hi,
Yes! It's now working, but it seems that the JSON object with the messages has changed quite a bit so I will have to adapt my app.
Thank you very much for your help!

I now realise that the error I was getting on chrome was my fault because the client script was trying to connect to localhost:2019 while the service was launched on another machine. Sorry for the mistake.
But updating the WA Web version solved my problem... so thanks again!

authors: UrbanSwati nilsburg sigalor

repo: sigalor/whatsapp-web-reveng


text:
🛑 Höllgrotten is down

In 89bc09f, Höllgrotten (https://www.hoellgrotten.ch/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Höllgrotten is back up in 50ad311 after 9 minutes.

repo: signalwerk/uptime


text:
Fearure Request NFT:  add tokens and SIGNA flow to owner

Note:  I do not know how to format for SIPS.
Request NFT:  add tokens and SIGNA flow to owner.

During the NFT portal screen to add your graphic
a) connected XT wallet would know what existing tokens the account has
b) a drop down to show what tokens are selectable
c) a box for how many tokens to include with NFT minting
Have code for the Minted NFT that when SIGNA lands in the smart contract address of the NFT that the new SIGNA gets sent to owner of the NFT.

This would be to take an existing token and include it with a unique NFT graphic that says how many tokens are included.   And when the token sends out dividends then the NFT smart contract passes the received SIGNA to the NFT owner's SIGNA address.
Not sure about royalties or platform fees.

This should be in NFT feedback, not SIP's

I close the ticket please repon if still needed on https://github.com/signum-nft/feedback-signumart

authors: frankTheTank72 paulpoco rogerwim

repo: signum-network/SIPs

license: Unlicense


text:
Initial release plans for cosign

I reeallly want to try to sign the first release of cosign, with cosign, if we can figure out a way that makes sense.
I think we'll have to do it manually, since we won't have a signed release to use in automation yet though. Thankfully we can skip some of the issues with reproducible builds.
Here's a rough plan:
The trick is that we can use Go to build a reproducible binary.

Setup github actions to build and publish a cosign binary on each commit to main

cosign builds should be reproducible, with some care.
We'll make these build logs public, showing the sha of each binary we build.

One or more of us will generate keys specific to this initial release.

The more the merrier!
We can commit these public keys to a file here in the repo.

We can pick a commit to tag our initial release at.

We'll have several of us build our own versions of cosign from it, and check the SHAs against the ones from the GitHub action. We can publish those in an issue.

If they match, we can tag the release. We'll then sign the first binaries and git tag (v0.1.0)!

We'll publish the signatures in Rekor and in the GitHub release.

The keys to verify the release will be included in the git repo at the matching commit!

After this, we can change our automation to use it's own public/private key-pair (also stored in this repo), and the last signed cosign binary release (v0.1.0) in CI to sign continuous builds. Signatures can get published to Rekor, the build log, and wherever we host the binaries.
Actual tagged releases will also be signed by the automation, and one or more maintainers. We'll sign the git commits as well as the resulting binaries. These can get published to the GitHub release. These public keys (and their mapping to maintainers) will also be stored in the repo.
We can write a verification script to help people verify.

Setup github actions to build and publish a cosign binary on each commit to main

Won't this make the repo quite difficult for new contributors trying to clone? Since we wouldn't want to rewrite the history in the future in a project like this, I think this is something to avoid?

Won't this make the repo quite difficult for new contributors trying to clone? Since we wouldn't want to rewrite the history in the future in a project like this, I think this is something to avoid?

Sorry! I think that wasn't clear. How about: "publish a binary to  after each commit to main"?
Not things back into main :) I mean we should publish CI builds somewhere (GCS, Github artifacts) after each build.

All done here! Release 2 coming soon :)

authors: ahmetb dlorenc

repo: sigstore/cosign


text:
Handle context cancelled properly + tests.

Signed-off-by: Ville Aikas vaikas@chainguard.dev

Summary
Handle closing of the context properly and return an error for it.
Ticket Link

Fixes
Release Note

Codecov Report

Merging #1796 (a0df4f9) into main (0c4cf2e) will increase coverage by 0.01%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main    #1796      +/-   ##
==========================================
+ Coverage   32.56%   32.58%   +0.01%
==========================================
  Files         147      147
  Lines        9297     9303       +6
==========================================
+ Hits         3028     3031       +3
- Misses       5915     5917       +2
- Partials      354      355       +1

Impacted Files
Coverage Δ

pkg/cosign/kubernetes/webhook/validator.go
75.55% <66.66%> (+0.32%)
:arrow_up:

pkg/cosign/tuf/client.go
61.68% <0.00%> (-0.82%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0c4cf2e...a0df4f9. Read the comment docs.

authors: codecov-commenter vaikas


text:
Do a JavaScript release

See #3.
This would entail:

setting up an npm project for this repo
automating the procedure to generate JS bindings to the protos (Makefile), generally checking in the generated code (gen/ and .github/workflows/)
automating/documenting the procedure to do releases of the generated code (RELEASE.md plus any GH Actions) on a tag, preferably releases/js/v0.1.1 or whatever.

Then you could start consuming it in sigstore-js.
CC @bdehamer @feelepxyz @eddiezane

Can we refrain from checking in the generated code?
It makes contributions hard as it enforced everybody to install all the tools, and sometimes it causes checking in binary code like in https://github.com/sigstore/protobuf-specs/blob/16541696de137c6281d66d075a4924d9bbd181ff/gen/pb-go/bundle/v1/sigstore_bundle.pb.go#L308-L329

I argued for exactly that in https://github.com/sigstore/protobuf-specs/pull/12 but was outvoted. The main issue is that Go kinda requires it :( I'd prefer not to reopen that can of worms. CC @asraa @kommendorkapten @woodruffw for visibility though
If it's substantially more idiomatic we can skip for JS; we already skip it for Java.
That said, the only tooling really needed here seems to be Docker and make;  are you having issues with those?

The main issue is that Go kinda requires it

Can Go store the generated source into a release branch then?
Frankly speaking, it is annoying that PRs like https://github.com/sigstore/protobuf-specs/pull/64 require updating and committing generated code along with the changes themselves.

I'm willing to change my opinion, but I'm still a soft 👎 on removing checked-in codegen for Python: it's relatively idiomatic to do so, and shouldn't have any significant developer burden (since as @znewman01 mentioned everything should be Dockerized).
I haven't run into any significant issues with either Go or Python's codegen, despite having some issues with Fulcio's similar codegen (which is not Dockerized).

I think it makes sense to keep as-is, as we get to exercise the codegen frequently to avoid any hiccups during a planned release. And as already said, it's dockerized so it should be of minimal extra burden for a contributer (albeit I understand that it's easy to forget to run the code generation and so get some possible unexpected failures).

codegen for Python: it's relatively idiomatic to do so

It thought Python was using pypi or something like that rather than fetching dependencies from the source code.

I haven't run into any significant issues with either Go or Python's codegen

I wasn't able to get make to work: https://github.com/sigstore/protobuf-specs/pull/64#issuecomment-1400201925
I might need to try harder, however, previously, docker worked for me.
I see how checking in the generated code might be helpful in case the generator is complicated to set up.
For instance, suppose there's a "database engine" project, and it might have a generated SQL parser. Suppose, the parser generator is not available on all the platforms, so it might help if the generated parser was committed under source control, so everybody can work on the database without spending time on installing the generator.
On the other hand, sigstore/protobuf-specs does not fit that pattern. The only purpose of the repository is to collect .proto files, and there is no other business logic.
I am not sure I want to install toolchains (even in Docker) for all the ecosystems. It is more-or-less fine when make fetches docker images for go and python only, however, I am afraid it will go wild as the number of generators increases: go, python, javascript, rust, java, clojure, haskell, c#, elm, you name it.
I would refrain from invoking a build that downloads and installs all those dependencies, especially, when the only thing I want is to fix a typo in the proto definition and/or add an annotation.

It reduces the likelihood of codegen errors and regressions: a regression in of protoc or betterproto can't result in us silently publishing a broken package

I do not see how committing the generated code prevents regressions.
I can easily see how running tests with the newly generated code could prevent regressions, however, committing the generated code does not make it tremendously better.

It matches "publish what you know": someone who reports a bug in the Python bindings can send us a permalink to the exact line that's causing the error, without having to share their own copy of the generated code.

If you want something for documentation purposes, then it might live on a documentation branch/repository.

authors: kommendorkapten vlsi woodruffw znewman01

repo: sigstore/protobuf-specs


text:
chore: remove "Signing publications" from the logging output

Summary
The message was not adding much, and it was emitted during configuration phase, so it was not even aligned with the actual signing work.
Release Note
NONE
Documentation
NONE

gotta dco it

Frankly, DCO is useless since GitHub's terms of service include already require that any content someone posts on GitHub must comply with the target's license: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#6-contributions-under-repository-license
See https://ben.balter.com/2018/01/02/why-you-probably-shouldnt-add-a-cla-to-your-open-source-project/#if-a-license-isnt-good-enough-for-maintainers-you-shouldnt-subject-users-to-it
Can we somehow lift DCO restriction?
I'm running into this DCO validation every time, and it does take time to re-commit and re-push

Yeah, it's just applied across all sigstore repos. So I dunno :shrug:

authors: loosebazooka vlsi

repo: sigstore/sigstore-java


text:
Is it safe to share a read only PatriciaMap across multiple thread?

In another word, is it safe to add unsafe impl<V> Sync for Node<V> {} ?

I'm not 100% sure but it seems okay to implement Sync for Node<V>.

You need to implement it like,
unsafe impl<V: Sync> Sync for Node<V> {}
unsafe impl<V: Send> Send for Node<V> {}

which is something I got wrong initially

@leshow You're right. Thank you for your advice!

authors: 12101111 leshow sile


text:
Added option validator.mapping.use_annotation

Added option validator.mapping.use_annotation to change the default usage of StaticMethodLoader to AnnotationLoader.
Added option validator.mapping.cache to allow passing a CacheInterface for usage in the mapping loader.
This should simplify the creation of a validator that reads annotations instead of static methods.

@SpacePossum, Ok, I will write some tests and a documentation update. I'm not very sure how to use github to do that in this same pull request. Any idea? Or should I make a new pull request?

I'm not very sure how to use github to do that in this same pull request. Any idea? Or should I make a new pull request?

Just push to your branch and GitHub will update the according pull request automatically ;)

Any thoughts on this?

Why just add a flag and not introduce a new validator.mapping.loader
service that users could override?

This would let developers use any of the available loaders
This would also let them configure the AnnotationReader they
want to use

Something like this would be better IMHO:
$app['validator.mapping.cache'] = null;

$app['validator.mapping.loader'] = function ($app) {
    return new StaticMethodLoader();
}

$app['validator.mapping.class_metadata_factory'] = function ($app) {
    return new LazyLoadingMetadataFactory($app['validator.mapping.loader'], $app['validator.mapping.cache']);
};

If you wish, you could then add an example in the documentation to show how
to use the AnnotationLoader by overriding the new service:
$app->register(new ValidatorServiceProvider(), array(
    'validator.mapping.loader' => function ($app) {
        return new AnnotationLoader($app['annotations']);
    },
));

@jlHertel Do you think you'd be able to update this soon and resolve the conflicts? Thanks!

I guess this should be closed as well as per https://github.com/silexphp/Silex/issues/1588#issuecomment-368390861

@hkdobrev That's correct. Let's close.

authors: fabpot hkdobrev jdreesen jlHertel skalpa

repo: silexphp/Silex


text:
Androidify node-nnpack

Tested to make sure that node-nnpack compiles fine for both OSX and Android with this change. I haven't tested running this on an Android device yet. Would merge once I am done testing.

I am able to require node-nnpack on the device without any missing dependency errors. Merging this change now so I can import this module as subtree in silk-core.

repo: silklabs/node-nnpack


text:
Feature/text selection toolbar

Starter copy, bookmark, highlight, and note functionality

We merged this code in #170

authors: chrisvire saidbrandonsaid

repo: sillsdev/appbuilder-pwa


text:
Pin changes

There are a couple of problems that need to be resolved with the pins.

pins 19 and 23 on the RaspberryPiZero are switched.
Pins on the H1 and H2 connectors will have to be updated to match the EPS.

These issues are with respect to Release 1.0

Systems have chosen the replacement pins
H2-12 -> H2->22
H2-14 -> H2->24

Update:

Pins 19 and 23 from RaspberryPiZero to pins 1 and 3 on the max3100(U5) called BCM_11_SCLK and BCM_10_MOSI are switched and need to be fixed


text:
Update template styles

[ ] Change background color on all pages to white
[ ] Match fonts and link styles to mozilla.org

https://github.com/mozilla/kitsune/projects/3

repo: silverorange/kitsune


text:
AttributesHTML() not following exclude parameters

If you use something like CreditCardField, in the template it has AttributesHTML which have exclude parameters. The attributes as far as I can tell don't make it to the function in FormField.php and so all the attributes are returned which for the case of CreditCardField, breaks the form.
Creating a duplicate function and calling it from the template sends only the first attribute.
Not too sure whats going on with it but as far as I can tell it's a bug.
Tested it on two different SilverStripe installations, currently 3.4.1

Yeah there's a bug in the template. In order to pass parameters to a getter, we need to use the FULL method name. I.e. $getAttributesHTML not $AttributesHTML. You can substitute it in your code as such if you want to test it locally. :)

This has been discussed repeatedly - "getters" should not accept parameters. This "bug" can't be fixed in a patch release because the API would need to change in a breaking way (remove getHTMLAttributes) and we're not going to accept sending params to getters via the template.

Thanks @tractorcow that worked perfectly.
@dhensby While I understand what you're saying with the getters, currently the CreditCardField doesn't work as intended and you have to have your own template to get it to work (it produces invalid HTML currently). Just changing $AttributesHTML to $getAttributesHTML as @tractorcow explains fixes the issue and only changes the template rather than breaking the API.
I know my issue raised was related to the "getters" issue however ultimately I just want CreditCardField to work and was trying to be helpful with my debugging findings. I can also do the change if it helps.

Sure - if we can fix a core issue here by just amending a core template we should do it.

Fixed with https://github.com/silverstripe/silverstripe-framework/pull/6504

authors: Rudigern dhensby tractorcow

repo: silverstripe/silverstripe-framework


text:
ENHANCEMENT Allow extensions to intercept incorrect deletes on unpublish

The issue with the existing behaviour is that some queried tables are NOT a part of the hierarchy, and the subsequent delete could unintentionally delete objects outside of this object.
For instance, fluent uses a localisation table as an inner join. This existing behaviour deletes these locales, but using the ID of the record, not the ID of the localisation (which is a separate ID itself).
With the given extension points extensions are able to intercept these queries and rewrite the delete safely without violating database integrity.

For instance, this is a page that has three failover locales. When deleted it performs these deletes:
"SiteTree_Live, ID = 3"
"SiteTree_Localised_Live, ID = 3"
"SiteTree_Localised_Live, ID = 3"
"SiteTree_Localised_Live, ID = 3"

Those following three deletes should be RecordID = 3 not ID = 3.

Seems reasonable, and it doesn't change anything if there were no extensions :)

authors: flamerohr tractorcow


text:
FIX: Block Manifest of the compatibility class Object and lean on the compatibility auto loader

On PHP 7.2 initial dev/build of a SilverStripe 3.7.1 site can throw a Fatal error: Cannot use 'Object' as class name as it is reserved, I experienced this on SilverStripe Platform causing the deployment to fail and rollback.
This pull request simply adds a manifest exclude file in core/compat which causes the framework to lean on the auto loader defined in model/fieldtypes/compat/autoload.php instead.

Will this make it into the upcoming 3.7.3 release? or will it need to wait until 3.7.4? Trying to plan ahead with one of our projects that's moving to SilverStripe Platform on a stack that's currently configured for PHP 7.2, but without this pull being merged would need to be downgraded to PHP 7.1.


text:
style for Placeholder(title)

I need to css placehoder on my site (with another coler) but i cant change style because when i select an option it have same color with placeholder

See guidelines for contributing.

Bug reports
A bug is a demonstrable problem that is caused by the code in the repository.
Good bug reports are extremely helpful - thank you!
Guidelines for bug reports:

Use the GitHub issue search. Check if the issue has already been reported.

Check if the issue has been fixed. Try to reproduce it using the latest master or development branch in the repository.

Provide environment details. Provide your operating system, browser(s), jQuery version, Bootstrap version, and bootstrap-select version.

Create an isolated and reproducible test case. Create a reduced test case.

Include a live example. Make use of jsFiddle or jsBin to share your isolated test cases.

Style via the bs-placeholder class.

repo: silviomoreto/bootstrap-select


text:
replace=False preserve mask in StackView when updating frame number

useful for exploring 3D stacks

This will close issue #650

Looks good to me.

authors: PiRK alemirone t20100

repo: silx-kit/silx


text:
Easy way to determine if two rows have the same columns?

I have this method to help me determine whether old row and excluded row have same fields. I am using insert method with DoUpdate.withExcluded parameter which has where clause with (old, excluded) => isDifferent(old, excluded)
Is there any way to automatize the process? I am comparing almost all columns with same name of old with excluded. As this way is prone to logical errors that will be hard to detect, can this be done with looping through same-name columns? Maybe comparing them with something like reduce method while excluding some fields that we don't want to be compared?
More explanation is available in issue https://github.com/simolus3/drift/issues/2299#issue-1571171981.
@override
  Expression<bool> isDifferent(Users old, Users excluded) {
    return (old.dateJoined.isExp(excluded.dateJoined) &
            old.email.isExp(excluded.email) &
            old.username.isExp(excluded.username) &
            old.username.isExp(excluded.username) &
            old.syncState.isExp(excluded.syncState) &
            old.isGuest.isExp(excluded.isGuest) &
            old.isVerified.isExp(excluded.isVerified) &
            old.isDeletedLocally.isExp(excluded.isDeletedLocally))
        .not();
  }

You can always cast from a DSL table instance (Users) to the internal table object (TableInfo). This interface gives you full access to the columns defined in the table, which allows doing reflection over tables:
Expression<bool> isDifferent(Users old, Users excluded) {
  final oldTbl = old as TableInfo;
  final excludedTbl = excluded as TableInfo;

  return oldTbl.$columns
      .where((c) => true) // Skip columns you don't want to compare
      .map((column) {
        final excludedColumn = excludedTbl.columnsByName[column.name]!;

        return column.equalsExp(excludedColumn);
      })
      .reduce((a, b) => a & b)
      .not();
}


text:
Migration Error when altered same table twice.

I have table called Box .
The Scenario :

I want to add refferenceId column  and add it as uniqueKey on version 2
Then in Version 3 , I need to add another column called refferenceNumber and also add it as uniqueKey.

This Is My Migration Strategy :
onUpgrade: (Migrator m, int from, int to) async {
     await transaction(() async {
          if (from < 2) {
            await m.alterTable(
              TableMigration(
                box,
                newColumns: [box.refferenceId],
              ),
            );
          }
          if (from < 3) {
            await m.alterTable(
              TableMigration(
                box,
                newColumns: [box.refferenceNumber],
              ),
            );
          }
     });
}

The Case is :
when My App is upgrading from version 1 to 2 and then upgrade it again from version 2 to 3, The Migration Works Fine.
But, When My App is directly upgrade from version 1 to 3, i got this error :
SqliteException(1): while executing, no such column: refference_number, SQL logic error (code 1):  Causing statement: INSERT INTO tmp_for_copy_box ("id", "box_number", "type", "amount", "refference_number") SELECT "id", "box_number", "type", "amount","refference_number" FROM "box";, parameters:

So I Assumed that because when the app is upgrading directly from version 1 to 3, the box table is altered twice during onUpgrade
Please tell me, is this a bug or there is a mistake in my code.
Thank you

Indeed, the problem is that alterTable would get called twice when upgrading from 1 to 3 directly. The complicated solution is to account for this in your onUpgrade handler by always upgrading to the latest version in every branch, e.g.
          if (from < 2) {
            await m.alterTable( // 1 -> current
              TableMigration(
                box,
                newColumns: [box.refferenceId, box.refferenceNumber],
              ),
            );
          } else if (from < 3) {
            await m.alterTable( // 2 -> current
              TableMigration(
                box,
                newColumns: [box.refferenceNumber],
              ),
            );
          }

Of course, writing migrations that just do a single step and then chaining them is much easier and scales better. However, it requires you to actually migrate towards an intermediate, outdated schema (2) in your migration logic. Since box is generated for the current table though, that's not directly possible.
To do this, drift provides tools that generate step-by-step migrations based on exported database schemas. To set this up, you'd have to export your old schemas once (you can probably checkout the revision where you've updated the schema and run dart run drift_dev schema dump on that tree). Then, drift can generate all intermediate versions of your schema into a compressed format which provides enough information to write migrations like this:
    onUpgrade: stepByStep(
      from1To2: (m, schema) async {
        await m.alterTable(schema.box, newColumns: [schema.box.refferenceId]);
      },
      from2To3: (m, schema) async {
        await m.alterTable(schema.box, newColumns: [schema.box.refferenceId]);
      },
    ),