text:
[App]: Data not available for various plots

Current Behavior
Hi,
I am running a classifier model training script which generates a couple of custom plots: a barplot depicting class frequencies of the train/val set, the ROC and PRC curves of the val-set performance and a confusion matrix. For generating all these plots, I've used the basic functionality provided in the wandb documentation (Code snippets shared below).
I use both cloud and private versions of wandb. In the cloud version, when I run the attached code (shared below), the plots are successfully generated but when running in the local version, I get a "No data available" for all these plots. I'm not sure why exactly this is happening. I would greatly appreciate some help on this!
Expected Behavior
I'm supposed to get the following output (seen in cloud version):

But I get this (local wandb server):

Steps To Reproduce
Following is the code I wrote for generating these charts/plots:
Code for bar plot
# log the class frequencies in each fold
train_classes, train_outputs = np.unique(train.outputs, return_counts=True)
val_classes, val_outputs = np.unique(val.outputs, return_counts=True)
train_outputs = train_outputs / np.sum(train_outputs)
val_outputs = val_outputs / np.sum(val_outputs)

# create wandb tables
train_data = [[label, val] for (label, val) in zip(train_classes, train_outputs)]
train_table = wandb.Table(data=train_data, columns=["class", "frequency"])
val_data = [[label, val] for (label, val) in zip(val_classes, val_outputs)]
val_table = wandb.Table(data=val_data, columns=["class", "frequency"])

# log tables as barplot
wandb.log(
    {
        f"train_distribution_fold": wandb.plot.bar(
    train_table, "class", "frequency", title=f'Class Distribution for Train set'
    ),
    f"val_distribution_fold": wandb.plot.bar(
    val_table, "class", "frequency", title=f'Class Distribution for Val set'
        ),
    }
)

Code for model evaluation charts
# log model evaluation charts
wandb.log(
    {
        "pr": wandb.plot.pr_curve(ground_truths.numpy(), predictions.numpy(), labels=val_ds.class_mapping),
        "roc": wandb.plot.roc_curve(ground_truths.numpy(), predictions.numpy(), labels=val_ds.class_mapping),
        "conf_mat": wandb.plot.confusion_matrix(y_true=ground_truths.numpy(), probs=predictions.numpy(),
class_names=val_ds.class_mapping)
    }
)

Screenshots
No response
Environment
I'm running my code on a remote linux machine and visualizing the results on my desktop browser.
OS: Linux
Browsers: Chrome
Version: Chrome Version 122.0.6261.112 (Official Build) (arm64), W&B Local 0.50.3, W&B package version 0.16.3.
Additional Context
Similar to the suggestions in issue #4368, I ran a wandb verify and got the following:
Default host selected: http://localhost:8081
Find detailed logs for this test at: /tmp/tmpmj4fcxqt/wandb
Checking if logged in...................................................✅
Checking signed URL upload..............................................✅
Checking ability to send large payloads through proxy...................✅
Checking requests to base url...........................................❌
Connections are not made over https. SSL required for secure communications.
Checking requests made over signed URLs.................................❌
Signed URL requests not made over https. SSL is required for secure communications.
Checking CORs configuration of the bucket...............................❌
Your object store does not have a valid CORs configuration, you must allow GET and PUT to Origin: http://localhost:8081
Checking wandb package version is up to date............................✅
Checking logged metrics, saving and downloading a file..................✅
Checking artifact save and download workflows...........................✅

Not sure if the CORs configuration is the issue, but I didn't find any resolution for this issue in #4368
Additionally, here is the commands used to start up the local server on the remote machine:
wandb server start --port 8081
wandb login --host=http://localhost:8081

hey @Aveturi13 - this seems like a CORS issue, but to confirm, would it be possible to send over the console/network logs associated with the workspace where you're not seeing the charts populate? if you're on chrome, you can obtain this by right clicking > Inspect > console/network

hey @Aveturi13 - I wanted to follow up on this. please let me know if you're able to provide the above info


text:
【bug】标点错误

工具栏中的全部运行中，在‘运行整个测试套件’后面的标点符号为‘，’应该为‘。’

请给出截图啊！

source: gharchive/issue

repo: wangding/SeleniumIDEDoc

license: mit

license_type: permissive

license_source: bigquery


text:
单元中关于 Map 的疑问

描述
我正在 packages/core 为 DomEditor.findPath 写单元测试，一直报错，目前的现象看着和 Map 相关。
复现步骤
第一，找到 NODE_TO_PARENT 的定义，把 WeakMap 临时修改为 Map ，这样好验证。
第二，如下图，在这里可以正常打印 NODE_TO_PARENT.size （当单元测试中执行 createEditor 或者操作 editor 时）

第三，如下图，在单元测试中打印 NODE_TO_PARENT.size，结果就是 0

总结
同是在单元测试中，执行 createEditor 即可正常打印 NODE_TO_PARENT.size。但直接引用、打印 NODE_TO_PARENT.size 就是 0 。
所以，猜测 DomEditor.findPath 测试一直报错，也和 NODE_TO_PARENT.size 有关。而且，DomEditor 其他很多 API 也都用了 WeakMap ，都有这个问题。

可以试试用 setTimeout 异步获取 NODE_TO_PARENT.size，或者异步验证测试断言。
异步，案例是符合代码逻辑的，但我尚未测试成功。

找到解决方案了：packages/core 中的单元测试，不能在使用 packages/editor 的 createEditor 。使用 packages/core 的 createEditor 就没问题了。
因为从模块关系上，前者也不能依赖于后者

license: MIT

license_source: github-api


text:
粘贴到编辑区域的图片能否添加监听及处理事件

目前在工具栏上上传图片有对应的回调，并且可以禁止网络图片。能否在内容区域粘贴图片时也提供类似的回调方法，或者可以提供将粘贴到能容中的网络图片直接保存到服务器上的方法。谢谢！

https://www.kancloud.cn/wangfupeng/wangeditor3/448202  用editor.customConfig.pasteTextHandle即可做到。
分析拿到粘贴内容中的图片，做一下标记。然后将图片的 url 传递给 server ，由 server 下载图片并保存，然后 server 将保存后的图片的 url 返回给前端。前端再将之前做过标记的图片的 src 修改为获取的 url


text:
没有静态变量解决handler内存泄露的问题~

已知handler没有静态变量。
一般我们在java中解决问题是把handler写为static。或者remov，或者弱引用。
private val mHandler = object : BaseHandler(mContext) {}
这是我构建的handler内存泄露的风险吗？应该怎样做

class Outer {
private val bar: Int = 1
class Nest {
//嵌套类不能访问外部类成员,相当于java的static 静态内部类
fun foo() = 2
}
}
kotlin 默认的class 就是类似于java中的static class ，反而你需要实现java中普通内部类 需要使用inner class

authors: DaoBillTang Gongkuan


text:
feat: do not append workspaces field when no workspaces present

Description

Issues Resolved

Screenshot

Testing the changes

Check List

[ ] All tests pass

[ ] yarn test:jest
[ ] yarn test:jest_integration
[ ] yarn test:ftr

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] Update CHANGELOG.md
[ ] Commits are signed per the DCO using --signoff

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

source: gharchive/pull-request

authors: SuZhou-Joe codecov-commenter

repo: wanglam/OpenSearch-Dashboards


text:
128 VnV plan documentation (section 1 and section 3)

Description
PR for VnV plan documentation (section 1 and section 3)
Issue Link:
#128

Could you please help remove comments like this

I think you forgot to write this section:

I think there is a typo here


text:
Any thoughts around adding multi-root support?

This is an AWESOME addon!
I noticed in your readme you have
//the source dir, currently we only support single root
"js-import.root": "src"

Just wondering if you had any plans for adding multi-root support? This would be fantastic for lerna style mono-repos for example, or yarn workspaces (when they land).

@lukebatchelor actually, the extension support multiple package like lerna style if all packages are in src, just see config js-import.alias.


text:
There may be some duplication of annotation information

I run the following command to get OpenL3 embeddings of clips in FSD-MIX-CLIPS ：
python get_openl3emb_and_filelist.py
--annpath PATH-TO-FSD_MIX_CLIPS.annotations
--audiopath PATH-TO-FSD_MIX_SED.audio
--savepath PATH_TO_SAVE_OUTPUT
I have counted the number of .pkl files generated by the program and the results are as follows
Base-train: 448,123
Base-val: 65,520
Base-test: 65,422
Novel-val: 17,347
Novel-test: 16,636
The total number is 613,048, not 614,533
My guess is that some annotations in FSD_MIX_CLIPS.annotations may have overlapped and therefore overwritten the file during program execution.
Therefore, I made a small change to line 25 of file get_openl3emb_and_filelist.py：
outfile = join(savefolder, fname.replace('.wav', '' + str(start_sample) + '' + str(idx) + '.pkl'))
The number of files obtained after rerunning the code is then consistent with what is described in the paper.
Maybe you can check if the annotation information in FSD_MIX_CLIPS.annotations does overlap.
Thank you,

Thanks for pointing this out!
I confirmed that there are duplicates in FSD_MIX_CLIPS.annotations. This results from the process of chunking 1-sec windows around all sound events in each clip. When multiple sound events are closely located in time, we could chunk the same window multiple times.
Specifically, the number of duplicates in each split are:
Base-train: 1145
Base-val: 146
Base-test: 139
Novel-val: 35
Novel-test: 20
Results in a total of 1485 duplicates as observed.
Overwriting shouldn't be a problem since these are just duplicates of the same time window. We should instead update the annotation files and dataset description.

Hi, can you please upload the updated annotation files? Thank you very much!

I have written a script to solve this problem, see https://github.com/wangyu/rethink-audio-fsl/pull/19

authors: chester-w-xie wangyu

repo: wangyu/rethink-audio-fsl


text:
Ability to Start Calendar on Time Tab

Sorry for filing so many tickets, but I have another feature that would  be really handy.  Right now there's no way to open the calendar on the time-picking tab.  This is controlled by this.state.tab in input-moment, but that state isn't set from any prop.
If there was either a way to pass a tab prop, and have this used as the initial state, or have some other sort of mode="time",  "showTime={true}", etc. that would be great.  I could even file a pull request for it, if you just let me know which prop to use.
Thanks.

This is enabled by #78.

authors: aychtang machineghost

repo: wangzuo/input-moment

license: isc


text:
Add transaction support for EVM L2s - starting with Arbitrum, Optimism and Base.

Add transaction support for EVM L2s - starting with Arbitrum, Optimism and Base.

Do we need it for orders or for tx signed with sign requests?
Btw we can support them already because they are use the same mechanism as Ethereum for gas and nonces

repo: warden-protocol/wardenprotocol


text:
fix: possible deadlock in lmdb 2.7.0

prepare a MRE for https://github.com/kriszyp/lmdb-js/issues/203

@janekolszak https://github.com/kriszyp/lmdb-js/issues/203#issuecomment-1334070167 :-) can you please tomorrow the 2.7.2 version?

repo: warp-contracts/warp-contracts-lmdb


text:
カーネル解読

まだカーネルの使い方が理解できておらず解読作業中です。全く読み切ることができてませんがちょっとずつ分かってきたので確認も兼ねて質問させていただきたいです。
まず、module_idとunit_idの設定ですがpreferenceを使って不揮発メモリに保存しておくという解釈であってますか？もしあっているなら、不揮発メモリへの保存は実際に書き込むmodulename/main.cppのファイルではないもので設定するのでしょうか。TBDと書いてあったので、その設定を早いうちにしておく必要があるんですかね？

https://github.com/wasa-rockoon/WOBC/blob/aa941c142f3019fef4b720576778969fe941e1ff/src/modules/GS/main.cpp#L46
この辺りのことだと思うけど，
unit_idもmodule_idもこんな感じでコード上で指定する．
ただしmodule_idに関しては，間違ったプログラムを書き込んだときに止められるように，EEPROMに指定したmodule_idを保存しておいて今回の値と比較する機能がkernelに入ってる．module_idが一致しないときはkernel::beginがfalseを返す．
EEPROMの書き込みをユーザー側でする必要は特にない．（というか他で何らかの値を保存したいときは，EEPROMやESP32のPreferenceを直接触らず https://github.com/wasa-rockoon/WOBC/blob/aa941c142f3019fef4b720576778969fe941e1ff/src/library/process/process.h#L31 を使ってほしい）
module_idを変更したいときはkernel::begin(module_id, false)とすると，このチェックなしで上書きされる．

あと言い忘れてたけど，module_idをcomponent_idと被らないように決めてほしい

ありがとうございます。
一度モジュールIDを書き込んで置いて、それ以降はいじらないっていう認識で良いですかね？
id管理ですが一度話し合った気もするのですがそのファイルが行方不明でして、もし現時点で参照してたり決まっているものがあれば教えてもらえますか？無いようでしたら一から再度考えようと思います。

一度モジュールIDを書き込んで置いて、それ以降はいじらない

まあそうともいえるかな？別にユーザーが明示的に書き込む操作をするわけではない．kernel::beginは必ず呼ぶ

id管理

https://docs.google.com/spreadsheets/d/1Nxq4RtOsuqMcLhA3_2kKKpubHb2iXEK-Q0oDwHh2aik/edit?usp=sharing
これかな
id管理と説明はこのリポジトリのdocs/modules.md とdocs/components.md に書いていこうか

手束とテレメの話して分かったんですけど、すでに考えてくれているidがあるそうなんですけど、これをベースにするのでも良いですかね。idとかって二文字である必要はないんでしたっけ？
tornado/lib/wcpp/id_name_mapping.json

任せる
unit, module, componentのidは8bitの数値．asciiコードで1文字にするのがわかりやすいかな
unit idは同じ種類でも被らないように

私が考えたid はテレメトリのテストをするために仮で作ったものなので、自由に変えてもらってしまって大丈夫です。
私の方で勝手に必要そうなid を設定した形になります。

このjsonファイルの主な用途としては、Grafanaに表示する情報のマッピングになります。Grafanaにデータを表示する際にエントリ名やパケット名などをそのまま表示していては分かりづらいため、分かりやすい名前にマッピングするためのjsonファイルを作成しました。

@rogue1starwars なるほど、ありがとう。
パケットの使い方どころかオブジェクト指向のコードの書き方に手こずってて勉強中だから手束の方でIDの管理というか設定をお願いできないかな。
componentとmoduleはmainのhardwareの中にあるファイルを参考にしてもらいたい。orderfileは発注したやつだから無視してくれて大丈夫

@rogue1starwars ごめんpacket idについて他に決めることだったりしたら新しくissue立てて
@fujiy すみませんコーディングについて相談で、CANとか使わないシンプルなTrackerからコードを書いていまして、今LiPoPoweコンポーネントからINA226のデータを取得する関数を書いています。初歩的な質問だと思うので本当に申し訳ないんですけど、icを使うときヘッダファイルを参照して（例えばINA226.hとか）その中の関数を使うと思うのですが、ヘッダファイルのどこで宣言すればよいのかわかんないです。
すごく抽象的になってしまったので具体的な問題を共有します。
ヘッダファイルがこちらで、LiPoPwerクラス内でina1とina2とina3を定義しています。
#include <library/wobc.h>
#include <Wire.h>
#include "INA226.h"
namespace component {
class LiPoPower: public process::Component {
public:
static const uint8_t component_id = 0x22; // TBD
static const uint8_t telemetry_id = 'P'; // TBD
LiPoPower(TwoWire& wire, unsigned sample_freq_hz = 10/TODO/);
protected:
TwoWire& wire_;
INA226 ina1;
INA226 ina2;
INA226 ina3;
void setup() override;
class SampleTimer: public process::Timer {
public:
using process::Timer::Timer;
protected:
void callback() override;
} sample_timer_;
};
}
そうすると定義する方のファイルでsetupとかはできるんですけど、SampleTimerクラス内でina1の関数が使えない状況です。どうやってエラーを解消すればよろしいでしょうか？
#include "lipo_power.h"
namespace component {
LiPoPower::LiPoPower(TwoWire& wire, unsigned sample_freq_hz /TODO ピン設定/)
: process::Component("LiPoPower", component_id),
wire_(wire),
ina1(0x4F),
ina2(0x4D),
ina3(0x4E),
sample_timer_("LiPoPowerTimer", 1000 / sample_freq_hz) {
}
void LiPoPower::setup() {
start(sample_timer_);
ina1.begin();
ina2.begin();
ina3.begin();
}
void LiPoPower::SampleTimer::callback() { // Timerで定期的に実行される関数
int x1_mV = ina1.getBusVoltage() * 1000; // INA226センサー1のバス電圧（ミリボルト単位）
int x1_mA = ina1.getCurrent_mA();        // INA226センサー1の電流（ミリアンペア単位）
int x2_mV = ina2.getBusVoltage() * 1000; // INA226センサー2のバス電圧
int x2_mA = ina2.getCurrent_mA();        // INA226センサー2の電流
int x3_mV = ina3.getBusVoltage() * 1000; // INA226センサー3のバス電圧
int x3_mA = ina3.getCurrent_mA();        // INA226センサー3の電流
bool charging;
wcpp::Packet packet = newPacket(64);
packet.telemetry(telemetry_id, component_id());
packet.append("V1").setInt(x1_mV); // センサー1の電圧
packet.append("I1").setInt(x1_mA); // センサー1の電流
packet.append("V2").setInt(x2_mV); // センサー2の電圧
packet.append("I2").setInt(x2_mA); // センサー2の電流
packet.append("V3").setInt(x3_mV); // センサー3の電圧
packet.append("I3").setInt(x3_mA); // センサー3の電流
packet.append("Ch").setBool(charging);
// ... TODO
sendPacket(packet);
}
}

SampleTimerがina1...の参照をメンバで持つようにして，コンストラクタで渡すのが一番素直かな

authors: KeisukeSuganuma fujiy rogue1starwars

repo: wasa-rockoon/WOBC


text:
feat(extension) Use pre-build dynamic libraries.

By using pre-build dynamic libraries (when a new Wasmer version is
released), we simplify the build process of this project. Rust is no
longer required to build the PHP extension.

bors try

bors try

bors try

bors r+

repo: wasmerio/php-ext-wasm


text:
Web version questions

I have already used the Total Segmentator module in 3D Slicer on smaller CTs, but I am trying out the web version on a full body CT. I opened the NRRD volume with 3D Slicer and saved it as nii.gz to upload. It's been sitting all day (see image). How long should I expect to wait and does this mean there's an issue with my nii.gz? I opened it in 3D Slicer and it looks fine.

That should not happen and looks like it is stuck at the upload. Can you try with another data set? I am not at work but will look into it after the christmas holidays.Best regards,Joshy--Sent from phoneOn 23 Dec 2022, at 21:16, Terrie Simmons-Ehrhardt @.***> wrote:
I have already used the Total Segmentator module in 3D Slicer on smaller CTs, but I am trying out the web version on a full body CT. I opened the NRRD volume with 3D Slicer and saved it as nii.gz to upload. It's been sitting all day (see image). How long should I expect to wait and does this mean there's an issue with my nii.gz? I opened it in 3D Slicer and it looks fine.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Thank you for responding! I'll try other datasets.

Hi, the website is running for other datasets. Have you tried with another dataset? If it is possible for you to share the problematic dataset I can investigate what the problem is.

Yes smaller datasets have worked. This one was a full body CT. I ended up trying it in 3D Slicer and it worked--there were extra/duplicate parts but I was able to delete them. The nrrd I downloaded was from Embodi3D: https://www.embodi3d.com/files/file/29386-skull-5th-attempt/.

For very big full body images the website is not working.
For your image there are several segmentations in the background because your images contains a lot more background than the typical CT image. This problem can probably be solved by using the option --body_seg. This will first run a quick body segmentation and then only run the TotalSegmentator inside of this body segmentation. This should remove those other segmentation. This option is only available in the master branch so far. So you will have to install from this: https://github.com/wasserth/TotalSegmentator#install-latest-master-branch-contains-latest-bug-fixes

Thanks so much for taking a look at the CT! I'll try running with your suggestion.

authors: joshy terrielsimmons wasserth

repo: wasserth/TotalSegmentator


text:
HTTP/1.0 support

Below is valid HTTP request:
GET / HTTP/1.0\r\n\r\n

But the lib return undefined

This wasn't an issue with HTTP 1.0, but when there were no headers in the string. I've fixed it now in v3.0.2. Please try again 😃

authors: futurist watson

repo: watson/http-headers


text:
Fix last_seen (Compare Timestamp instead of seconds after full minute)

Tnx for finding this nice bug, @HB9HIL
Should fix it

Thx

Great that we now safe a bit more time every 60seconds. tnx for the better approach to @HB9HIL

repo: wavelog/wavelog


text:
Ctrl + S File Editor Keybinding Not Working in Ubuntu 24.04.1

Current Behavior
When opening a file in the text editor, after editing Ctrl + S cannot be used to save the file. The user has to manually click on the Save button.
Expected Behavior
Pressing Ctrl + S should save the file.
Steps To Reproduce

On an Ubuntu 24.04.1 system (64 bit)
Install amd-64 v0.8.12 (DEB) or x86_64 AppImage
Open waveterm.
If waveterm GUI opens, open the file editor in waveterm, try to edit a text file,
Try saving it by pressing Ctrl + S
Even after pressing Ctrl + S, the save button remains bright green (doesn't get disabled) and the file stays unsaved

Wave Version
v0.8.12
OS
Ubuntu 24.04.1
Architecture
x64
Anything else?
No response
Questionnaire

[X] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

Right now the keybinding for save is Alt+S on windows/linux.  We discussed internally and agree that in the preview editor on Windows/Linux Ctrl+S should also be supported.

shipped in v0.9.1

authors: sawka xbais

repo: wavetermdev/waveterm


text:
Direct float texture reading

WebGL class support methods for padded and unpadded textures
shaders: direct and deferred padding
syntactic sugar for uniform binding

Initial contribution. Hopefully dealing correctly with this github cooperative workflow. Learning as stepping through it, open to be advised on best practices or weblas conventions.

It's probably my fault for not understanding, but can you go into more detail on what this enables? I'm curious about the benefits you're seeing (or hoping to see). The last thing I want to do is waste all of the work you've put into this.

tl:dr The aim is to skip float encoding if possible and availble, saving those compute cycles.
This modifies your Tensor.transfer() function firstly, based on your webgl class "gl.hasFloat" support is available or not, if the float computation results must indeed be encoded into sets of four gl.UNSIGNED_BYTE in the output, otherwise an appropriate output texture is created instead (gl.FLOAT) and float results are output directly when read via native gl.readpixels(), or not so directly if the data shape requires padding given the texture constraints (columns as multiples of four), in which case, an alternate shader to keep individual values contiguous along the readPixels() buffer is used instead. Aside of the new method bindUniform(), this PR is all that is required to provide this functionality.
Bypassing float encode is a natural option for the unpacked format, encoding comes only as a necessity of the level of webgl support, not only or maybe as a convenience given the chosen data format ie. packed.
I gather that weblas aims to be used with smaller factor browsers, and the relevant extension(s)
OES_texture_float and WEBGL_color_buffer_float (more info on chrome) are already enabled in some browsers. Looking forward webgl 2.0 will also account for this.
My personal aim is to keep as much of any arbitrary computation an algorithm requires at the GPU level, reducing transfers, if internaly the GPU deals with floats natively, encoding comes only as a requirement for CPU reads which I'm avoiding from the begining, hence my intent on a format which is free from encoding imposed/encouraged constraints.
Feel free if you need more clarifications.

Are you available for Google Hangout or Skype some time? I want to understand this and feel like I need higher bandwidth to do so. Email me:  AT gmail

Good conversation. Going to go ahead close this.

authors: gnonio waylonflinn

repo: waylonflinn/weblas


text:
Support full file paths

The function squashfs.extract_file(..) supports grabbing files at both the root inode and beyond.
The correct functionality in my eyes would be to give the full path of the files you want, and for that path to be verified.

#5 added the ability to grab the full filepath from a given file in the fs, but I think there should still be a function that wraps extract_files(..) that requires a correct filepath before returning to the user.


text:
--index {filepath} \ in service config causes service to exit directly after writing index file

using release arm binary https://github.com/wcbonner/GoveeBTTempLogger/releases/tag/v2.20231001.1.
I would expect to be able to use --index within the service to automatically add new devices to my svg-dashboard.
Instead it restarts after writing the files. It is not listening.
Log V2 with --index in service config:
Oct 16 08:11:38 energy goveebttemplogger[13149]: [2023-10-16T06:11:38] Writing: "/var/www/html/goveebttemplogger/index.html"
Oct 16 08:11:38 energy goveebttemplogger[13149]: [2023-10-16T06:11:38] Writing: A4C1380611DD
Oct 16 08:11:38 energy goveebttemplogger[13149]: [2023-10-16T06:11:38] Done
Oct 16 08:11:41 energy systemd[1]: Stopped GoveeBTTempLogger service.
Oct 16 08:11:41 energy systemd[1]: Starting GoveeBTTempLogger service...
Oct 16 08:11:41 energy systemd[1]: Started GoveeBTTempLogger service.
Oct 16 08:11:41 energy goveebttemplogger[13181]: [2023-10-16T06:11:41] Reading: "/var/log/goveebttemplogger"
Oct 16 08:11:41 energy goveebttemplogger[13181]: [2023-10-16T06:11:41] Writing: "/var/www/html/goveebttemplogger/index.html"
Oct 16 08:11:41 energy goveebttemplogger[13181]: [2023-10-16T06:11:41] Writing: A4C1380611DD
Oct 16 08:11:41 energy goveebttemplogger[13181]: [2023-10-16T06:11:41] Done
Oct 16 08:11:46 energy systemd[1]: goveebttemplogger.service: Service hold-off time over, scheduling restart.
Oct 16 08:11:46 energy systemd[1]: Stopped GoveeBTTempLogger service.
Oct 16 08:11:46 energy systemd[1]: Starting GoveeBTTempLogger service...
Oct 16 08:11:46 energy systemd[1]: Started GoveeBTTempLogger service.
Oct 16 08:11:46 energy goveebttemplogger[13243]: [2023-10-16T06:11:46] Reading: "/var/log/goveebttemplogger"
Oct 16 08:11:46 energy goveebttemplogger[13243]: [2023-10-16T06:11:46] Writing: "/var/www/html/goveebttemplogger/index.html"
Oct 16 08:11:46 energy goveebttemplogger[13243]: [2023-10-16T06:11:46] Writing: A4C1380611DD
Oct 16 08:11:46 energy goveebttemplogger[13243]: [2023-10-16T06:11:46] Done
the index file contens is correct. After removing --index from service config, everything runs properly.
Thanks for this great tool ! - I use it on raspy 3 :-)

using release arm binary https://github.com/wcbonner/GoveeBTTempLogger/releases/tag/v2.20231001.1.
I would expect to be able to use --index within the service to automatically add new devices to my svg-dashboard.
Instead it restarts after writing the files. It is not listening.
the index file contens is correct. After removing --index from service config, everything runs properly.
Thanks for this great tool ! - I use it on raspy 3 :-)

Yes, the index option is operating as planned.
https://github.com/wcbonner/GoveeBTTempLogger#minor-update-2022-12-17 shows an example of the way I use the index option.  The program can be run this way without stopping the instance running in the background listening to Bluetooth advertisements and creating log files.
I wanted to create a starting index file when there are a lot of devices that are being monitored. I can then easily manually reorder the sections or add details to the index file in a normal editor.
I should have created the index program as a separate executable but because everything so far has been a monolithic code file, keeping all the file handling in the same place was the safer option. My alternate solution would have been to break the code into multiple header files and code files.
I've been happy the tool is useful beyond my own obsession.

Thank you for your fast Answer. Then I only would suggest to add this behaviour to the docs in Readme.md. I did not find and read the other example without advice.
My suggestion:
i (--index) Command line option. Not for usage in service: HTML index file for SVG files, must be paired with log directory. HTML file is a fully qualified name. This is meant as a one time run option just to create a simple index of all the SVG files.
Cheers.

authors: TimoGoetze wcbonner

repo: wcbonner/GoveeBTTempLogger


text:
Remove deprecated ability to set DynamoDB table name via URL

Follow-up from #357

Should we log a warning if launched with non-empty path?

Probably a good idea. Are you OK for me to merge after that or would you like another review after that? (Roundtrips are expensive)

Oh yeah for sure. LGTM.
On Mon, 27 Mar 2017 at 10:03, Jonathan Lange notifications@github.com
wrote:

Probably a good idea. Are you OK for me to merge after that or would you
like another review after that? (Roundtrips are expensive)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/cortex/pull/370#issuecomment-289381722,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbGhaXRvA7Dx9TcoumPZ5_5YgI0L5Beks5rp21WgaJpZM4MoVPy
.

authors: jml tomwilkie

repo: weaveworks/cortex


text:
Release chart 0.9.0

The release date is now yesterday 💊

authors: hiddeco stefanprodan

repo: weaveworks/flux


text:
SPIKE: Gitops & flux in any namespace

Right now, there's bits of code that assumes gitops is running in flux-system, and there's bits of code that assumes flux is running in flux-system.
I want it to work to run flux in any namespace, and gitops in any namespace, and for those namespaces not to be the same. However, I don't know what's involved in making that happen.
Make a rough outline of the kind of work required to make both of these namespaces configurable.

@ozamosi thanks for putting this together.  I didn't realize we had this restriction built in.

So you can't install and you can't log in, but other than that everything seems to work 😊

A bit off-topic, but I encountered this now:
Installed via the helm chart in a separate namespace and worked fine except for the oidc
Installed in the flux-system namespace and my ingress gives timeout for some reason I can't figure out..

authors: JamWils audunsolemdal ozamosi

repo: weaveworks/weave-gitops


text:
Fix pod not found error.

It looks like it was broken again with the following error  during the first run (if installing the dashboard right after installing Flux) or during the second run (if installing Flux during the first run and the dashboard during the second run):
macbook-pro:podinfo olga$ /Volumes/Macintosh_HD_Data/_job_ww/_src/weave-gitops-3/bin/gitops beta run ./deploy/overlays/dev --timeout=3m --port-forward namespace=dev,resource=svc/backend,port=9898:9898
► Checking for a cluster in the kube config ...
► Checking if Flux is already installed ...
► Getting Flux version ...
⚠ Flux is not found: error getting Flux labels
► Installing Flux ...
CustomResourceDefinition/alerts.notification.toolkit.fluxcd.io created
CustomResourceDefinition/buckets.source.toolkit.fluxcd.io created
CustomResourceDefinition/gitrepositories.source.toolkit.fluxcd.io created
CustomResourceDefinition/helmcharts.source.toolkit.fluxcd.io created
CustomResourceDefinition/helmreleases.helm.toolkit.fluxcd.io created
CustomResourceDefinition/helmrepositories.source.toolkit.fluxcd.io created
CustomResourceDefinition/kustomizations.kustomize.toolkit.fluxcd.io created
CustomResourceDefinition/providers.notification.toolkit.fluxcd.io created
CustomResourceDefinition/receivers.notification.toolkit.fluxcd.io created
Namespace/flux-system created
ServiceAccount/flux-system/helm-controller created
ServiceAccount/flux-system/kustomize-controller created
ServiceAccount/flux-system/notification-controller created
ServiceAccount/flux-system/source-controller created
ClusterRole/crd-controller-flux-system created
ClusterRoleBinding/cluster-reconciler-flux-system created
ClusterRoleBinding/crd-controller-flux-system created
Service/flux-system/notification-controller created
Service/flux-system/source-controller created
Service/flux-system/webhook-receiver created
Deployment/flux-system/helm-controller created
Deployment/flux-system/kustomize-controller created
Deployment/flux-system/notification-controller created
Deployment/flux-system/source-controller created
NetworkPolicy/flux-system/allow-egress created
NetworkPolicy/flux-system/allow-scraping created
NetworkPolicy/flux-system/allow-webhooks created
✔ Flux has been installed
► Waiting for flux-system/source-controller to be ready ...
✔ flux-system/source-controller is now ready ...
► Waiting for flux-system/kustomize-controller to be ready ...
✔ flux-system/kustomize-controller is now ready ...
► Waiting for flux-system/helm-controller to be ready ...
✔ flux-system/helm-controller is now ready ...
► Waiting for flux-system/notification-controller to be ready ...
✔ flux-system/notification-controller is now ready ...
► Checking if GitOps Dashboard is already installed ...
Would you like to install the GitOps Dashboard: y
► Installing the GitOps Dashboard ...
Please enter your password to generate the secret:
✔ Secret has been generated:
$2a$10$e0UvHWgR.pFl/0JJZLMNYeGIg8PIvkC/cju6wRVGxsVbSyO6jrohe
► Installing the GitOps Dashboard ...
✔ Generated GitOps Dashboard manifests
✔ GitOps Dashboard has been installed
HelmRelease/flux-system/ww-gitops created
HelmRepository/flux-system/ww-gitops created
✔ GitOps Dashboard has been installed
► Request reconciliation of dashboard (timeout 3m0s) ...
✗ Error requesting reconciliation of dashboard: helmcharts.source.toolkit.fluxcd.io "flux-system-ww-gitops" not found
► Checking namespace dev-bucket ...
✔ Created namespace dev-bucket
► Checking service dev-bucket/dev-bucket ...
✔ Created service dev-bucket/dev-bucket
► Checking deployment dev-bucket/dev-bucket ...
✔ Created deployment dev-bucket/dev-bucket
► Waiting for deployment dev-bucket to be ready ...
► Port forwarding to pod dev-bucket/dev-bucket-f649c7d6c-hgdkb ...
Forwarding from 127.0.0.1:9000 -> 9000
Forwarding from [::1]:9000 -> 9000
✔ Port forwarding for dev-bucket is ready.
✗ Error getting pod from specMap: no running pods found for deployment
Error: dashboard pod not found

For some reason, when I move waiting for Flux components to be ready out of that condition (similar to how it as before), it starts working without an error. Weird behaviour.

@ozamosi added polling for RequestReconciliation, decided to keep all three wait.Poll calls within ReconcileDashboard separate for readability and simpler exit polling conditions.


text:
[ecs] Investigate  aws ecs start-task --container-instances

It was show that
aws ecs start-task --cluster $cluster --task-definition cadvisor:1 --container-instances $instance_arn --region $region

is a thing, so it'd be possible to run kube-proxy and kubelet that way, once #18 is resolved.

Turns out that StartTask is what a custom scheduler is meant to use.

repo: weaveworks/weave-kubernetes-anywhere


text:
Add option to stop weave adding a multicast route

For users that are happy with the default routing of multicast packets, weave adding a route to 224.0.0.0/4 is unhelpful.  We could have yet another environment variable to turn off this behaviour.

For users that are happy with the default routing of multicast packets

What are those users using the default multicast route for?

There is no default multicast route actually. With this being said, my setup involves multicasting video streams through the docker bridged network because it suits my infrastructure. I'm keeping weave for multi host management only. The weave default multicast route breaks that setup.

Actually, thinking again about it, I may have found a way to actually plug my underlying setup to the weave bridge instead of the docker bridge. In that case, I have a feeling I could simply benefit from the weave default multicast route indeed. I'll try it out tomorrow and report back.

Hi all,
I have indeed managed to get my setup running over weave's network, including the multicast traffic.
With that said:

There are various tickets opened to let multicast being handled by the overlay network directly over at libnetwork: https://github.com/docker/libnetwork/issues/552. I'm wondering if that route may not eventually interfere.
unless I'm mistaken, the weave network doesn't propagare IGMP memberships outside its network. For instance, I have a video source streaming on my network somewhere. Currently, I have to enslave one physical interface to the docker bridge so that the IGMP carrier from the physical switch sees the membership. Unfortunately, I cannot enslave a physical port to the weave bridge AFAIK to keep the same behavior. I therefore still need to remove the route from ethwe when the app need to register to a multicast source outside the weave bridge.

Well thank you guys for this! :)

@Lawouach Happy holidays :)

authors: Lawouach awh bboreham rade

repo: weaveworks/weave


text:
allocator should broadcast updated ring after donating space

What you expected to happen?
When a node donates tokens to peers, it is expected to reflect the updated ring across the nodes in the cluster.
What happened?
It is noticed that other peers occasionally does not see updated tokens in the ring and continue to see the token as owned by previous donor owner. It is observed delay could be in the order of minutes.
During this window of time its possible a conflicting operation can be performed leaving the ring in inconsistent state.
When debugging #3444 I found the root cause to be this issue.
How to reproduce it?
Just keep repeating kubectl delete a node then rejoin the node to the cluster, you will see updated ring on the node which donated the range, but occasionally rest of the nodes would see updated ring after long delay.

During this window of time its possible a conflicting operation can be performed leaving the ring in inconsistent state.

Please list a sequence of steps that results in an inconsistency.

Please list a sequence of steps that results in an inconsistency.

Not a best example but the scenario seen in https://github.com/weaveworks/weave/issues/3444 is like below:

node C joins a cluster with node A and node B
node B donates a range to node C and updates ring locally
node A does not get updated view of ring (this only occasionally happens)
node C is deleted from the cluster
weave rmpeer is performed on the node A
node A performs transfer, but in its view it does not have any entries owned by node C resulting in 0 ip's getting reclaimed

Brayn shared below examples offline

A owns 10, B owns 20, C owns 30
B donates 20 to C
A owns 10, C owns 20,30
A still thinks B owns 20
B is deleted
A does rmpeer B
A owns 10,20, C owns 20,30

another example

A owns 10, B owns 20,25, C owns 30
B donates 25 to C
A owns 10, B owns 20, C owns 25,30
A still thinks B owns 20,25
B is deleted
A does rmpeer B
A owns 10,20,25, C owns 25,30

Brayn shared below examples offline

A owns 10, B owns 20, C owns 30
B donates 20 to C
A owns 10, C owns 20,30
A still thinks B owns 20
B is deleted
A does rmpeer B
A owns 10,20, C owns 20,30

another example

A owns 10, B owns 20,25, C owns 30
B donates 25 to C
A owns 10, B owns 20, C owns 25,30
A still thinks B owns 20,25
B is deleted
A does rmpeer B
A owns 10,20,25, C owns 25,30

authors: murali-reddy rade


text:
some weave status commands fail with "weave container is not present. Have you launched it?"

What you expected to happen?
Try to diagnose failures of weave-net in a kubeadm cluster. Downloaded the weave tool as per:
https://www.weave.works/docs/net/latest/install/installing-weave/
Weave net is already running:
kubectl get pods -n kube-system -lname=weave-net
NAME              READY   STATUS    RESTARTS   AGE
weave-net-kdxmc   2/2     Running   1          17m

Running weave status works
weave status

        Version: 2.6.4 (up to date; next check at 2020/07/29 14:30:28)

        Service: router
       Protocol: weave 1..2
           Name: 1e:3a:f0:9e:96:b8(giza-apps2-corp-guitar.ams.corp.google.com)
     Encryption: enabled
  PeerDiscovery: enabled
        Targets: 0
    Connections: 0
          Peers: 1
 TrustedSubnets: none

        Service: ipam
         Status: ready
          Range: 192.168.9.0/24
  DefaultSubnet: 192.168.9.0/24

Running other subcommands fails with the above error
What happened?
weave status connection
weave container is not present. Have you launched it?
Invalid 'weave status' sub-command: connection
Usage:

weave --help | help
...

It's also inconsistent - running weave status dns only print the error without the usage (although I don't find the usage helpful here).
How to reproduce it?
See above.
Anything else we need to know?
Versions:

$ weave version
weave script 2.6.5
weave 2.6.4
$ docker version
Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea838
 Built:             Wed Nov 13 07:25:58 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.5
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.12
  Git commit:       633a0ea838
  Built:            Wed Nov 13 07:24:29 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683
$ uname -a
Linux xxxxx 5.6.14-2-amd64 #1 SMP Debian 5.6.14-2 (2020-06-20 > 2018) x86_64 GNU/Linux
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-15T16:58:53Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:07:13Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}

Logs:
# $ kubectl logs -n kube-system <weave-net-pod> weave
# FYI: if you want to update the bug template to use '-lname=weave-net' people can copy'n'paste the command
$ kubectl logs -n kube-system -lname=weave-net -c weave
WARN: 2020/07/29 08:01:36.471967 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: ba:fe:f2:35:89:0b, dst: 96:92:62:52:21:b6} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}
WARN: 2020/07/29 08:01:38.423402 Vetoed installation of hairpin flow FlowSpec{keys: [InPortFlowKey{vport: 1} EthernetFlowKey{src: 1e:3a:f0:9e:96:b8, dst: d2:4d:8d:26:fd:af}], actions: [OutputAction{vport: 1}]}
WARN: 2020/07/29 08:01:38.452213 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: 1e:3a:f0:9e:96:b8, dst: 96:92:62:52:21:b6} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}
WARN: 2020/07/29 08:01:38.452271 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: b6:bf:5c:9f:95:95, dst: ba:fe:f2:35:89:0b} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}
WARN: 2020/07/29 08:01:38.643380 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: 1e:09:2e:df:98:67, dst: b6:bf:5c:9f:95:95} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}
WARN: 2020/07/29 08:01:38.643458 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: aa:cd:f7:d7:af:05, dst: b6:bf:5c:9f:95:95} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}
WARN: 2020/07/29 08:04:31.251455 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: 1e:3a:f0:9e:96:b8, dst: 8a:6d:d0:ab:66:36} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}
WARN: 2020/07/29 08:04:31.251533 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: 1e:3a:f0:9e:96:b8, dst: 62:d9:90:09:56:d9} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}
WARN: 2020/07/29 08:04:31.283265 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: 8a:02:af:38:b7:5b, dst: 26:30:06:a8:4c:2d} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}
WARN: 2020/07/29 08:04:31.571574 Vetoed installation of hairpin flow FlowSpec{keys: [EthernetFlowKey{src: ca:a6:c5:53:bb:f8, dst: a6:98:92:32:8c:53} InPortFlowKey{vport: 1}], actions: [OutputAction{vport: 1}]}

Network:
$ ip route
default via 100.109.39.254 dev ens13 proto dhcp metric 100
100.109.39.0/24 dev ens13 proto kernel scope link src 100.109.39.7 metric 100
192.168.9.0/24 dev weave proto kernel scope link src 192.168.9.1 metric 425
192.168.10.0/24 dev docker0 proto kernel scope link src 192.168.10.1 linkdown
$ ip -4 -o addr
1: lo    inet 127.0.0.1/8 scope host lo\       valid_lft forever preferred_lft forever
2: ens13    inet 100.109.39.7/24 brd 100.109.39.255 scope global dynamic noprefixroute ens13\       valid_lft 84870sec preferred_lft 84870sec
3: docker0    inet 192.168.10.1/24 brd 192.168.10.255 scope global docker0\       valid_lft forever preferred_lft forever
6: weave    inet 192.168.9.1/24 brd 192.168.9.255 scope global weave\       valid_lft forever preferred_lft forever
$ sudo iptables-save
https://gist.github.com/ensonic/e5f1b7146a20d7e8cb2424f2b32b080c

same problem with weave env.

erm it is weave status connection*s*, but that outputs an empty list

ahh, this seems to be always printed when the "docker run" fails (util_op). So its mostly a UX issue.


text:
No weaviate.configure.vectorizer.text2vecOllama

I'm following the Weaviate quickstart guide (https://weaviate.io/developers/weaviate/quickstart#step-4-define-a-data-collection) and trying to configure the Text2VecOllama vectorizer. However, I don't see any options in the TypeScript client library to set these configurations.
According to Weaviate's documentation (https://weaviate.io/developers/weaviate/modules/retriever-vectorizer-modules/text2vec-ollama#example-1), I need to manually configure the schema with specific settings. But I'm looking for a way to replicate this process using the TypeScript client library, rather than having to do it by hand.
import type { CollectionConfigCreate, WeaviateClient } from 'weaviate-client';
import weaviate, { vectorizer } from 'weaviate-client';

const client: WeaviateClient = await weaviate.connectToLocal({
  host: '127.0.0.1',
  port: 8888,
});

const schema: CollectionConfigCreate<undefined, 'Question'> = {
  name: 'Question',
  vectorizers: // weaviate.configure.vectorizer.text2vecOllama(???),
  generative: weaviate.configure.generative.ollama({
    apiEndpoint: 'http://ollama:11434',
    model: 'llama3:instruct',
  }),
};

await client.collections.create(schema);

Hi @devzeebo, thanks for the callout on this one 😁  This will be fixed and included in the v3 GA release of the TS client coming today!

Fixed in v3.0.0 that just landed!

repo: weaviate/typescript-client


text:
use strict; is not supported -  Attempted to assign to readonly property

When using "use strict"; there is an error " Attempted to assign to readonly property."
In https://github.com/web-animations/web-animations-js/blob/master/web-animations-next-lite.min.js
b["true"] = a;

Has strict mode compatibility be resolved for this library?

This is something to do with uglify's wrap option. Which produces
function(exports,global){global["true"]=exports;

authors: azogheb dstockwell

repo: web-animations/web-animations-js


text:
refactor: using object form of lightningcss feature options

Summary
Introduce LightningcssFeetureOptions, for better user experince, so user don't have to use import anything from @rspack/core

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

👍🏻

authors: JSerFeng chenjiahan

repo: web-infra-dev/rspack


text:
style: optimize inline code and link style

Summary

When hover

Related Issue

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

The underline is covered by g:

https://deploy-preview-1016--aquamarine-blini-95325f.netlify.app/guide/default-theme/home-page

repo: web-infra-dev/rspress


text:
Add Compute Pressure API

Compat features are tagged in BCD: https://github.com/mdn/browser-compat-data/pull/22687
Not sure if https://chromestatus.com/metrics/feature/timeline/popularity/3900 (PressureObserver_Observe) is the best use counter, cc @kenchris

Not sure if https://chromestatus.com/metrics/feature/timeline/popularity/3900 (PressureObserver_Observe) is the best use counter

The other alternative is https://chromestatus.com/metrics/feature/timeline/popularity/3899 (the constructor) but so far they show the same data. A call to observe() is more "real", but you can go one step further and say we should measure when the callback is actually invoked.
So I would say use the constructor until we see some difference between that and observe().

https://w3c.github.io/compute-pressure/#supported-sources has both "thermals" and "cpu", but only "cpu" is implemented in Chrome. So we should probably consider just CPU pressure the initial feature.

repo: web-platform-dx/web-features


text:
Fix gmp error

Fix gmp BigInteger error (TypeError: Argument 1 passed to Jose/Component/Core/Util/Ecc/Point::create() must be an instance of Brick/Math/BigInteger, instance of GMP given)

This won’t work.
Please see #289

This won’t work.
Please see #289

Hi,
install this lib -> https://github.com/brick/math

@MaxDomo,
This won’t resolve the issue, this library will still continue to use gmp and this will break all applications that are still using web-token/* v2.0 or v2.1

authors: MaxDomo Spomky

repo: web-push-libs/web-push-php


text:
Run & Analyze gas measurmens on Arbitrum Nitro Goerli

As a developer using BLS Wallet
I would like to understand the gas differences/savings/costs of using BLS Wallet on Arbitrum Nitro in common transactions
So that I can determine if it is the right fit for my projects needs
Notes

Produce a document which includes gas measurements & analysis of running gas measurements on Arbitrum Nitro Goerli for sharing with internal & external shareholders.

This feels a bit testnet focused. Can we include a note here that the real goal (as part of 'analyze'?) is to get an estimate of the costs on Arbitrum Nitro (for-realz)? (That is the real goal here, right?)

@voltrevo see https://github.com/web3well/bls-wallet/issues/490 (& https://github.com/web3well/bls-wallet/milestone/9)

@jacque006 Right, but I just don't see the value in running this measurement on Arbitrum Goerli except as a proxy to estimate real Arbitrum. Maybe the value is in refining/practicing the process before spending the fees on mainnet?
But then, even when running on mainnet, the L1/L2 gas ratio fluctuates all the time, so I see this measurement as quite weak.
Similar to what we touched on in our call, the (L1 gas, L2 gas) pair is the thing that we can control. If we don't have those two numbers (remembering that "gas used for L1" is not L1 gas), then the measurement we have will be subject to the constant gas variability that is outside of our project.
To put it another way, if we have the (L1 gas, L2 gas) pair, then we could put a widget on our website which constantly displays a good estimate of the current actual price of running various transactions on our stack. Any measurement which doesn't allow us to directly derive those values is, by comparison, weak information.

Maybe the value is in refining/practicing the process before spending the fees on mainnet?

This is the primary reason I started on a testnet. Also, the analysis of those testnet values & the presentation of such will likely be the same across network runs, so would like to refine that before hitting other networks/mainnets.

Similar to what we touched on in our call, the (L1 gas, L2 gas) pair is the thing that we can control. If we don't have those two numbers (remembering that "gas used for L1" is not L1 gas), then the measurement we have will be subject to the constant gas variability that is outside of our project.
To put it another way, if we have the (L1 gas, L2 gas) pair, then we could put a widget on our website which always displays an up-to-date estimate of the current actual price of running various transactions on our stack. Any measurement which doesn't allow us to directly derive those values is, by comparison, weak information.

I agree that that L1 block, gas, and price information is valuable for us & other L2 devs and I would like to include it eventually on all runs. However, I think to start most people are going to mainly care about the actual ETH/USD on that L2 and the difference if a BLS bundle vs. a normal txn, such as what is shown on https://l2fees.info/ .

@jacque006 Just acknowledging here that we did discuss adding this kind of information as followup. Can we link that here when it's created? I just can't stress enough that these measurements are an incomplete picture without that next step.

Yep, will do. It will be part of https://github.com/web3well/bls-wallet/milestone/9

eventually

I feel like we're on the same page about everything now except for the importance of this extra information.
I'm not sure what the disconnect is here. To me it is very clear that it would be grossly incomplete to not include L1 gas in the measurements. l2fees.info doesn't have the same problem because it updates in real-time. Without real-time updates, reporting the ETH cost, or for this case even reporting gas, for the same reason, is going to be frequently wrong and its usefulness therefore severely limited.
Even more important than reporting these numbers externally is our ability to measure our progress and make internal decisions. For that use case, using this fluctuating measurement is even more of a problem.


text:
clearable和popper-class这两个属性不生效耶~

clearable和popper-class这两个属性不生效耶~

这两个属性没有支持呀，不过应该支持一下，下个版本更新吧

已经支持，可更新使用

为什么我这边还是不支持，我是按照你的步骤安装这个npm包的

authors: 3125803995 qiujunyu webCoderJ

repo: webCoderJ/ele-multi-cascader


text:
Recent logins - multiple logins from the same IP address

Why will it show multiple logins from the same IP address?

Because those are different sessions.

Why will it create different sessions?
How long will the stay as Logged in? The user is not logged in 4 times. Shouldn't it detect that and change it to something else?

This could be due to multiple browsers or incognito windows on the same machine?

It seems that the user have used incognito, so that will probably explains it.

authors: Sopor iliajie jcameron

repo: webmin/authentic-theme


text:
Ramsey UUID type problem

I have data model using Ramsye UUID,
I can't query api with graphql as the type is not recognized and throws error:
"Type error: Argument 1 passed to GraphQL\\Validator\\DocumentValidator::isValidLiteralValue()
must be an instance of GraphQL\\Type\\Definition\\Type, null given,
called in /home/ubuntu/h88/api.epp.domeny.dev/vendor/webonyx/graphqlphp/src/Validator/Rules/ArgumentsOfCorrectType.php on line 27"

Did anybody had similar problem and could share how to solve it ?

Can you provide a test case to reproduce this?
Or at least your type definition, and data which causes this?

each entity has id as below
 /**
     *
     * @\Doctrine\ORM\Mapping\Column(type="uuid")
     * @\Doctrine\ORM\Mapping\GeneratedValue(strategy="CUSTOM")
     * @\Doctrine\ORM\Mapping\CustomIdGenerator(class="Ramsey\Uuid\Doctrine\UuidGenerator")
     * @\Doctrine\ORM\Mapping\Id()
     * @\Symfony\Component\Serializer\Annotation\Groups({"view", "list"})
     *
     * @var \Ramsey\Uuid\Uuid
     */
    private $id;

You must understand that ID type expects a string, not custom objects.
So you have two options:

For each id field - define a resolver which will return a string representation of the ID, e.g.:

$idField = [
    'type' => Type::id(),
    'resolve' => function ($value) {
        return (string) $value->getId();
    }
];

$myType = new ObjectType([
    'fields' => [
        'id' => $idField,
    ]
]);

Create your own custom scalar ID type and pass it in types option of the Schema instance (note that you must use v0.11.1+ for this to work).

Closing, but feel free to re-open if it's not solved for you

authors: mysiar vladar

repo: webonyx/graphql-php


text:
Lazy loading of types...

I have a large number of types (130+) in my code base, and I'm worried about the overhead of building them all for every little request. I followed the advice in your documentation, and made sure that my objects return callbacks for their field properties, and I provided a typeLoader callback when instantiating my Schema. I understand the general concept, but I must be missing a piece, because at least some types are still being constructed even though they are not referenced in any way by the query being made.
After analyzing the sample here it's not clear to me where the savings are. Imagine if MyTypeA had a list of 100 fields on it instead of 1; wouldn't 100 calls to $this->get(<fieldName>) trigger as soon as its fields callback resolves? Or is there some magic I'm missing?
I guess I was expecting something more like this:
private function MyTypeA()
    {
        return new ObjectType([
            'name' => 'MyTypeA',
            'fields' => function() {
                return [
                    'b' => ['type' => 'MyTypeB'] // use a string (or possibly a callable) here, rather than resolve the type on the spot
                ];
            }
        ]);
    }

...with the idea being that I use the name of the type in my field definition rather than a reference to the field itself, and then at runtime it would use the name to look up the type when needed.
I'm pretty sure this is just a matter of me being dumb and not getting something fundamental, so I guess my real question here is whether you think the lazy loading documentation could be improved a bit, or perhaps incorporated into the samples. If you can help me get my questions sorted out I'd be happy to help with either.
Thanks for the wonderful library!

You are right here. Types are being initiated on fields closure call. So even if you request single field of a type, all types for those fields are being instantiated.
But instance creation is not expensive. It's fields, arguments, and interfaces which add significant overhead. If you don't create them on type instantiation you should get a significant performance win (which we benchmarked).
We actually considered loading types by name, but it didn't pass a cost/benefit analysis at the moment (wins were little, costs to implement were relatively significant).
Anyways, if you do some benchmarks, illustrating the opposite we can get back to this idea.

But instance creation is not expensive. It's fields, arguments, and interfaces which add significant overhead.

Well, I make heavy use of inline schema definitions. All of my mutations, for example, are dynamically generated with custom types (with custom validation types, error codes, and so on), and many of my queries are also dynamically created. It's just a lot of busy work that I would rather not have happen if it doesn't need to. But as you say, I should do some profiling before pressing the matter. I'll see what I can come up with tomorrow.

I have some initial data.
First, I profiled my existing code with the following simple query (Faction type has no dependencies on other custom types):
{
	faction (id: 1) {
		id
  }
}

Blackfire provides the following profile for this request:

PHP spends about 124 milliseconds in Types::get. (563 milliseconds for the entire query; I have xdebug enabled for all these queries, so things are pretty slow in general overall, but we're doing apples to apples, here, so I didn't bother turning it off).
Next, I doctored my Types::get method to always return the type for faction (I verified that the query still functions as expected), and get the following profile:

The time spent in Types::get drops away to 11 milliseconds (390 milliseconds for the entire query).
I'll post my Types::get implementation here:
	public static function get($name)
	{
		$cacheName = strtolower($name);

//		$name = "faction"; // I uncomment this to simulate a perfect lazy loading simulation

		if (!isset(self::$types[strtolower($cacheName)])) {
			switch($name) {
				default:
					$method = lcfirst($name);
					if(method_exists(get_called_class(), $method)) {
						$type = self::{$method}();
					}
					else
					{
						$typeName = "\\shmax\\api\\types\\{$name}Type";
						$type = new $typeName();
					}

			}

			self::$types[$cacheName] = $type;

		}
		return self::$types[$cacheName];
	}

It's not practical for me to post my entire schema, as it's enormous, but if it would help I could prepare a sample repo that has a schema roughly equivalent in complexity. Or, I could just dive in and start trying to fix the issue, with your guidance.
Please advise, and thanks again!

In order for the typeLoader to be called with the type name, isn't the type object already loaded? I'm just trying to wrap my head around why the typeLoader needs to return a type that it should already have.

Before type loading, we had to scan the whole schema top-to-bottom to discover all possible types. This was required mostly because of the abstract types (interfaces, unions). E.g. resolveType can return type name, not the type instance itself.
Another scenario when type loading is useful is when the schema is defined via SDL. Then we have a type name from the SDL before we actually create type instance.
Technically if there were no SDL and abstract types, we could have avoided type loading at all, but then we had to couple either schema and execution (executor should've somehow registered all types loaded during execution in the schema) or couple schema and each type definition (definition should've notified schema when it has been loaded). Both approaches were adding unnecessary complexity and added restrictions to independent schema usage.
So at the moment, all that type-loading does is helping us to avoid full schema scanning. Plus, it opens ways for other optimizations (one day we may get back to the idea of defining type names as strings #62  for a fully lazy-loaded solution)

There is one more issue with the custom typeLoader. For example - we have a lot of inline type instantiations within our fields. The validation fails because of that cause for inline types you cannot get a single instance from Types.
For eg.
'name' => 'banner',
'type' => new EnumType([
...
])

The problem
When the AST tree is walked the above type creates a new instance and there is no reference for this EnumType.

I'm currently experience either some understanding issue about lazy loading or some implementation issue.
Currently, all types of all my queries and mutations on the schema are resolved, which keeps me awake since days.
From what I understand is, that basically fields' types are always fully resolved, which is already known and might be subject of future optimizations.
But I don't get why all my queries are resolve.
A Query Class looks like
<?php

declare(strict_types=1);

namespace R2\Api\GraphQL\Base\Schema\Object;

use Closure;

class QueryCashbookItems extends \R2\Api\GraphQL\Type\AbstractQueryObjectType
{
    public $attributes = [
        'name' => 'CashbookItems',
        'deprecationReason' => null,
        'description' => null,
    ];

    public function type(): \GraphQL\Type\Definition\Type
    {
        return $this->getPaginationType('CashbookItem'); // => this calls basically triggers resolution of Pagination objects as well, although the QueryCashbookItems-query is never executed
    }

    public function args(): array
    {
        return ['trainingMode' => ['type' => \GraphQL\Type\Definition\Type::nonNull(\GraphQL\Type\Definition\Type::boolean())],
            'page' => ['type' => \GraphQL\Type\Definition\Type::int()],
            'pageSize' => ['type' => \GraphQL\Type\Definition\Type::int()],
            'description' => ['type' => \GraphQL\Type\Definition\Type::string()],
            'externalDocumentId' => ['type' => \GraphQL\Type\Definition\Type::string()],
            'search' => ['type' => \GraphQL\Type\Definition\Type::string()],
        ];
    }

    public function resolve(
        $root,
        array $arguments,
        $context,
        \GraphQL\Type\Definition\ResolveInfo $resolveInfo,
        Closure $getSelectedFields
    ) {
      ....
    }
}

If a run a query, which DOES NOT involve this class, it is still resolved with all it's dependent types.
Thanks for clarification.

@shmax I am guessing this is resolved as of https://github.com/webonyx/graphql-php/pull/557, feel free to reopen if not.

@spawnia I was going to close this once all the little fix-up patches and optimizations were sorted out and released, but I suppose there's no harm in doing it now. Thanks much.

authors: at758 duxthefux justineverson shmax spawnia vladar


text:
How to stop UglifyJS from running on NODE_ENV=production?

I'm trying to use babili to do my minification instead of uglify whenever I run webpack -p.
How do I do that? I can't seem to stop it.

webpack -p is a shortform for webpack with defineplugin = NODE_ENV=production and uglifyJsPlugin.. So you should not use webpack -p and use the DefinePlugin and BabiliPlugin in your webpack config.
plugins: [
  new webpack.DefinePlugin({
    "process.env": { NODE_ENV: "'production'" }
  }),
  new BabiliPlugin()
]

Oh so whenever you run webpack with the -p option Uglify gets run? That's a downer.
Thanks for the swift response! 🙌

Oh man, couple of hours I will never get back!
Thanks -p ! 😖

Damn this hit me as well. Spent several hours trying to figure this one out.

me too :/

authors: akos-sereg boopathi joe1chen selbekk yattias


text:
Use Travis for CI

Once #3 has been implemented, we should use Travis to automatically run tests for all PRs. In addition, Travis can automatically handle npm publishing for us.

Webpack-contrib doesn't use travis for deployment. We do need to add travis integration.

@d3viant0ne seems your need here
@ChadKillingsworth we use webpack-defaults (https://github.com/webpack-contrib/webpack-defaults) for consistent code across all repos in webpack-contrib

@evilebottnawi See #19. This issue predates transferring the repo to webpack-contrib.

authors: ChadKillingsworth evilebottnawi

repo: webpack-contrib/polymer-webpack-loader


text:
docs(dev-server): add transportMode docs and examples

describe your changes...
devServer.transportMode: https://github.com/webpack/webpack.js.org/issues/3239
I think that, rather than having large custom implementation examples in here, we should link to implementation examples in webpack-dev-server/examples.

I did a bit a bit of minor reorganization for the new transportMode.client and transportMode.server sections.

@EugeneHlushko Currently the types I have are:
devServer.transportMode:
string = 'sockjs': 'sockjs' | 'ws' object
devServer.transportMode.client:
string path
devServer.transportMode.server:
string path function
Should path be there, or should we just let that fall under string? If you think these are not specific enough, could you suggest how to make it fit in with the Writer's Guide guidelines?

Could string for the client and server be changed to string = 'sockjs': 'sockjs' | 'ws' | path?
Could I do function: class? I just need something making it clear that providing a plain function like server: () => {} will not be sufficient

Yes, i think it looks very good now

Thanks!

authors: EugeneHlushko Loonride


text:
Port to webpack 3 and Upgrade Antwar

Port site to webpack 3 and a new version of antwar that fixes a variety of bugs. What's left:

[x] fix <title> tags, none of which are populated
[x] fix introduction sidebar links
[x] fix activation of current page in sidebar (i.e. displaying anchors)
[ ] fix mobile sidebar (pretty much empty for some reason, maybe due to title issue)
[ ] fix terminated build issue (not sure what's going on there 😕)

Resolves #720 (once titles are fixed, remember to double check vote title)

Ok so here’s what i’m seeing:

<title> doesn’t look like it’s populated on any page
introduction sidebar links are broken… clicking those just duplicates the section name (e.g. /concepts/concepts)
activation of current page in sidebar is broken

Aside from those I'm not seeing anything else broken but i'll keep poking around. I can look into to the two sidebar issues but I'm not sure what to do about the titles. It would be great if we could put that one to bed and close out #720.

Ok updated the lead-in description with what's left to do... I fixed two issues with the normal sidebar and will now look into the mobile sidebar.

Yeah so the issue with the SidebarMobile component is that the routing data changed and many titles are missing. Once we figure out what the solution is for title and children it should be an easy fix.

I upgraded the setup to use webpack 3 and fixed titles. Can you check the mobile sidebar bit? Also that termination issue remains most likely (some way to debug is needed).

@bebraw I'll pull, test, and try to resolve the mobile sidebar issue. I restarted the build just to see if that would help, but honestly I'm not really an expert when it comes to CI. Although I just checked the build and it seems to be moving past the initial stages now.

> webpack.js.org@0.1.2 lint:links /home/travis/build/webpack/webpack.js.org
> hyperlink -r build/index.html | ./scripts/check-links.js
Guessing --root from input files: file:///home/travis/build/webpack/webpack.js.org/build/

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received

The build has been terminated

Not really sure what's failing here, is it hyperlink? @bebraw the output directory is still called /build, right?

@bebraw I'm unable to find the necessary data within section.all(). Only some top level pages come back none of which contain any child pages:

I'm also not seeing the titles populated:

Please advise... I did wipe my node_modules and re npm install everything after checking out to this branch.

@pierreneter ok I'm a bit confused about why we're seeing all the conflicts between here and master now. I'm going to play around with this a bit locally and see what's going on.

Ok @pierreneter, so after merging #1546 into here I realized I kind of jumped the gun a bit. I realized a better approach would be to...

[ ] Rebase this branch on master first to resolve conflicts.
[ ] Then cherry pick the specific changes/fixes needed from your PR.
[ ] Then do a final test/review/merge.

I've already completed the first step of this for the most part. I'm seeing an issue with the page data that must have to do with the page-loader.js file or page data being stripped somewhere else. I'm debugging that now and looking at your specific commits from #1546. I wish I could have made that initial merge work but realized things were getting way too messy.
What I think you should do now is take a look at this branch and submit more targeted PRs against it. This way we can carefully review the changes/diff without having to dig through 200+ files. I still think we can get this finished soon.

Also note that I created two new branches on this repository mostly just so we don't lose anything:
old-feat-webpack2 (prior to rebase)
feat-webpack2-update (your branch from #1546)

Ok I resolved the page data and sorting issues (thanks for pointing out sorting). Double checked <title> tags which are not populated in development (npm start) but are populated in production (npm run build).

@pierreneter can you just make those mobile sidebar fixes in another branch and submit the PR? I think that's pretty much it, seeing the same issue we did before with hyperlink but hopefully that resolves itself as it did before.

@skipjack, I think we just need revert the merged of #1546. And I will make a new Pull Request of this again then merge it with Create a commit option to this branch, the option: Squash and merge make me as a person deprives of others contribute. My PR just like a merge of master to this branch make it is even with master.

Yeah I did revert it. This PR is now rebased and all conflicts are resolved. Just test it out and submit any other changes (e.g. the mobile sidebar) you think are needed in a separate PR (directed towards this branch instead of master as you did in #1546.

Fixed "fix mobile sidebar" with 2802732 and d3766dd
Fixed #1559 with dfe3111

Submitted webpack-contrib/polymer-webpack-loader#63 to fix the last remaining issue. @pierreneter I'm going to do another pass over all this and see if there's anything else that needs fixing or can be cleaned up. Expect it to be merged by the end of this week (this weekend at the latest).

a7f0644 related to: https://github.com/wooorm/alex/issues/175

1a67384 related to: wooorm/alex#175

4e1beb9 related to: wooorm/alex#175
alex . -q :

alex CLI searches for files with a markdown or text extension when given directories (e.g., $ alex . will find readme.md and foo/bar/baz.txt). To prevent files from being found by alex, add an .alexignore file.

and

node_modules is ignored by default.

Will do a final pass over this tonight and get it merged.

Ok @pierreneter tested this out and everything seems good to go. I did just submit webpack-contrib/npm-install-webpack-plugin#118 to fix a broken remote link but we don't necessarily have to wait on that to merge. Also seeing issues with Travis' network again but I restarted the build so we'll see what happens. Latest this goes in is tomorrow.

Ran all tests locally which only ran fine aside from the broken link from webpack-contrib/npm-install-webpack-plugin#118. Doesn't make sense to hold this merge up just for that though. If anything else comes up we can resolve in a separate PR.
@pierreneter I'll likely start working on #1519 soon, and will talk with @bebraw to try to simplify the antwar configuration even more. Will submit separate PRs for that and cc you.

@pierreneter it's in 🎉
Thanks again for all of your work on finishing this off. It should definitely make it easier to keep pushing the repo forward in terms of build process and infrustructure. I will try to set up a discussion soon, maybe in slack or something, with those interested in the infrastructure of the site so we can make a solid plan.

authors: bebraw pierreneter skipjack


text:
MinChunkSizePlugin breaks federated modules loading

Bug report

What is the current behavior?
When an application tries to load a remote module with a minimal chunk size defined via the Webpack MinChunkSizePlugin, I get this error:
Uncaught TypeError: Cannot read property 'call' of undefined
    at __webpack_require__ (bootstrap:18)
    at Function.__webpack_require__.t (create fake namespace object:7)
__webpack_require__ @ bootstrap:18
__webpack_require__.t @ create fake namespace object:7

If the current behavior is a bug, please provide the steps to reproduce.

Just add this to a Webpack config that uses remote modules via ModuleFederationPlugin:
new MinChunkSizePlugin({
  minChunkSize : 10000
})

It seems that code who is in charge of loading the remote modules is missing in the bundle that uses MinChunkSizePlugin.
To see the difference, you can just compare the two following files:

main-ok.js (without MinChunkSizePlugin)
main-not-ok.js (with MinChunkSizePlugin)

Reproducible repos:

Root application: https://github.com/gautierrollin/mf-min-chunk-size-plugin
Remote application: https://github.com/gautierrollin/mf-remote-application

What is the expected behavior?

MinChunkSizePlugin should just impact the chunk size of internal application chunk and the way of loading remotes modules should not be removed from the bundle.
Other relevant information:
webpack version:  5.4.0
Node.js version: 12.18.3
Operating System: Mac OS v10.15.6

PS: I've already encountered issues with the MinChunkSizePlugin and the first version of module federation plugin.
Well, that's an old issue but it could be related: https://github.com/ScriptedAlchemy/webpack-external-import/issues/128 CC @ScriptedAlchemy 😄

Like in my old issue, this bug appears if Webpack doesn't have to create several chunks (because of a large minChunkSize value relative to the project).

Uncaught TypeError: Cannot read property 'call' of undefined
at webpack_require (bootstrap:18)
at Function.webpack_require.t (create fake namespace object:7)
webpack_require @ bootstrap:18
webpack_require.t @ create fake namespace object:7

can't reproducible (with and without plugin), can your improve reproducible test repo

I don't think you have the same error with and without MinChunkSizePlugin.
Without the plugin, you get an error because the remote application does not exist:
Uncaught ReferenceError: app2 is not defined

I've been lazy but you can now clone this repo, start the remote application (in addition to the root application) and it'll be fixed 😉

I've been lazy but you can now clone this repo, start the remote application (in addition to the root application) and it'll be fixed wink

Please avoid this, the time it took was worth unanswered problem(s) to somebody
@sokra Limitation?

bump

@gautierrollin is this still an issue for you?

No because I don't use MinChunkSizePlugin anymore in my project. But I think the problem still exists.

Messing around with chunking is problematic. If you want to force federated modules into fewer chunks then do it through splitChunks cache groups and a regex

I got this problem when using {splitChunks : {maxSize: 300000} }. I'll give the cacheGroups a try. My UI loads several federated modules and keeping the remote entries small is very important.

authors: Gautierrr ScriptedAlchemy alexander-akait csvan evilebottnawi gautierrollin juanger

repo: webpack/webpack


text:
Output name handling with multiple entry points

Having config like:
entry: {
header_basket: './header-basket/main.jsx',
basket: './basket/main.jsx'
},
output: {
path: path.join(process.env['HOME'], 'project/js/'),
filename: '[name].js',
sourceMapFilename: '[name].map',
libraryTarget: 'var',
library: '[name]'
}
I want webpack to build bundles with names 'header_basket' and 'basket', but libraries names should be in CamelCase. Is it possible?

Nope. Sorry.

authors: WhackoJacko sokra


text:
Output.chunkFilename [name] not working?

I'm not sure whether I'm correctly understanding output.chunkFilename's [name].  My assumption was that [name] would match [name] in output.filename.
Using vue-webpack-example: https://github.com/vuejs/vue-webpack-example
module.exports = {
  entry: "./src/main.js",
  output: {
    path: "./build",
    publicPath: "/build/",
    filename: "build.js"
  },
  module: {
    loaders: [
      { test: /\.styl$/, loader: "style!css!stylus" },
      { test: /\.html$/, loader: "html" }
    ]
  }
}

Creates the following files:

build.js
1.build.js
2.build.js

If I change option.filename to: build.[name].js
module.exports = {
  entry: "./src/main.js",
  output: {
    path: "./build",
    publicPath: "/build/",
    filename: "build.[name].js"
  },
  module: {
    loaders: [
      { test: /\.styl$/, loader: "style!css!stylus" },
      { test: /\.html$/, loader: "html" }
    ]
  }
}

Creates the following files:

build.main.js
1.build.1.js
2.build.2.js

Shouldn't it create the following files?:

build.main.js
1.build.main.js
2.build.main.js

Setting [name] in output.chunkFilename always seems to become the [id]
module.exports = {
  entry: "./src/main.js",
  output: {
    path: "./build",
    publicPath: "/build/",
    chunkFilename: "[name].[id].js",
    filename: "build.[name].js"
  },
  module: {
    loaders: [
      { test: /\.styl$/, loader: "style!css!stylus" },
      { test: /\.html$/, loader: "html" }
    ]
  }
}

Creates the following files:

1.1.js
2.2.js
build.main.js

Is it working as intended?  If so, in what condition(s) do the chunks become named?

You are mistaking something.
A chunk can be named.
require(["jquery"], function($){
    // Something awesome with jQuery.
}, "jQueryStuff");

Then, it would build bundle.jQueryStuff.js or jQueryStuff.bundle.js instead.
A chunk without a name gets an incrementing ID.

When attempting to name a chunk:
require(["jquery"], function($){
    // Something awesome with jQuery.
}, "jQueryStuff");

I get the following errors:
18:6-13 require function is used in a way in which dependencies cannot be statically extracted
Module not found: Error: a dependency to an entry point is not allowed

@IngwiePhoenix Are you saying that [name] in filename and chunkFilename are different?

@tilleps The AMD 'require' does not allow you to name a chunk, so you need to use the commonjs option.  ie change your code to this and you will not get the error
require.ensure([], function(require){
var $ = require("jquery")  // you may need to add .default here
// Something awesome with jQuery. $
}, "jQueryStuff" // this will be passed webpack template under [name] and can be used with chunkFileName);

I'm trying to deal with this right now and [name].[name].bundle.js gives me 0.chunk_name.bundle.js

I am new to webpack and I had the same question. I'm trying to migrate a project from require.js to webpack. I expected that chunkFilename: '[name]-bundle.js' with my AMD's would result in named chunks but doesn't. @psimoneau22's suggestion worked but that would mean that I have to switch to CJS syntax the entire project.
Is there anyone who can explain if this is intentional and if so why?

Is chunkFilename a feature to be used only with code-splitting? Because I'm doing some tests with Webpack (not using code-splitting) and setting any value to chunkFilename doesn't make a difference in my build output.

same issue, why wouldn't chunckFilename work ?
  splitChunks: {
      automaticNameDelimiter: "-",
      cacheGroups: {
        vendor: {
          name: "1_chunk_vendors",
          chunks: "all",
          minChunks: 3,
        }
      }
    },


text:
ERROR in main Module not found: Error: Can't resolve './src' in 'project'

please help me on this issue.
ERROR in main
Module not found: Error: Can't resolve './src' in 'project'
resolve './src' in 'project'
using description file: project\package.json (relative path: .)
Field 'browser' doesn't contain a valid alias configuration
using description file: project\package.json (relative path: ./src)
no extension
Field 'browser' doesn't contain a valid alias configuration
project\src doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
project\src.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
project\src.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
project\src.wasm doesn't exist
as directory
project\src doesn't exist
webpack 5.80.0 compiled with 1 error in 71 ms

Close in favor https://github.com/webpack/webpack/discussions/17091

To anyone here from a search engine, ERROR in main Module not found: Error: Can't resolve './src' likely means that one or more of your configured entry values results in undefined & webpack is trying to use its default entry value, which doesn't exist in your codebase.

authors: Judahmeek Kranthi32 alexander-akait


text:
webpack 2: Exported ES6 config function does not get called in

When exporting an ES6 config function, webpack does not detect it as such, due to it being transpiled by babel into commonjs with a default prop on the exports object. Leaving the modules intact didn't work either, as this file is imported using node require, prior to webpack handling the file.
Could the solution be as simple as checking whether the required module has a default prop, which is a function?

Even when babel’ing your config, you can still use the module.exports object. Just use that instead of the export keyword - solves the problem.

@IngwiePhoenix Yeah I'm doing that, but I wanted to report this as it seems to be somewhat of a bug, given the fact that @sokra's examples show the use of a pure ES6 module. (https://gist.github.com/sokra/27b24881210b56bbaff7)

Could the solution be as simple as checking whether the required module has a default prop, which is a function?

I thought so: https://github.com/webpack/webpack/blob/master/bin/convert-argv.js#L115-L117

@sokra Will send a PR as soon as I can. I think it might be enough to update L97-L99 to account for the es6 exported function and call that one.

merged

authors: IngwiePhoenix johanneslumpe sokra


text:
How to config webpack 2 for React & Sass & Typescript ?

How to config webpack 2 for React & Sass & Typescript ?
Anybody can give a complete demo !

webpack.config.js

/* coming soon ...*/

Can you re-open the question at Stack Overflow please? I wrote an entire free book about the topic so that might be worth studying for specific ideas as well.

pardon ?

The current version of the book is 1.9.5.

I want to learn the version webpack 2 !

@xgqfrms-GitHub The book is for webpack 2. It's the version of the book.

authors: bebraw xgqfrms-GitHub


text:
add fetchPriority to hmr runtime's ensureChunk function

This code adds fetchPriority as an argument to the ensureChunk function.
https://github.com/webpack/webpack/blob/e381884115df2e7b8acd651d3bc2ee6fc35b188e/lib/RuntimeTemplate.js#L962-L964
We're missing that argument in the hmr runtime and this PR adds that in. Ideally this means that we are able to test webpackFetchPriority while using hmr.
Summary

copilot:summary
Details

copilot:walkthrough

Thank you

authors: alexander-akait evans


text:
drizzle plugin

Docs: https://orm.drizzle.team/kit-docs/overview
I also added playwright-ct to the schema.json file.

It should be good for a review. ✅

Thanks, Julien! 🙏

:rocket: This pull request is included in v2.28.0. See Release 2.28.0 for release notes.

authors: jgoux webpro

repo: webpro/knip

license: ISC


text:
Docker install problem

I'm having trouble with the Docker install. All appears to go OK, but accessing localhost:8089 gives me a 500 error. If I look through the docker logs the only container showing any errors is webrecorder_app, which has:
Traceback (most recent call last):   File "./webrecorder/main.py", line 4, in <module>     from webrecorder.appcontroller import AppController   File "./webrecorder/appcontroller.py", line 17, in <module>     from pywb.rewrite.templateview import JinjaEnv ImportError: No module named 'pywb.rewrite.templateview' unable to load app 0 (mountpoint='') (callable not found or import error)
docker-compose doesn't seem to have had any problem with pywb, eg:
Building app Step 1 : FROM webrecorder/pywb  ---> 0ac4e6bb4d3a
so I don't see why this would be, and I don't have the experience with Docker to know how to debug further.
This is on CentOS 7, which defaults to python 2.7; I have installed python 3.5.4 and symlinked /usr/bin/python to python3.5 (ditto with pip). There is a version of pywb installed with pip for python3.5.  I'm running the docker commands with sudo as it seems to be the only way it will work.

Having the same issue.
Here are the docker logs for the container that seem relevant.
Python version: 3.5.3 (default, Jul 24 2017, 19:52:53)  [GCC 4.9.2] Python main interpreter initialized at 0x20d3570 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 317025104 bytes (309594 KB) for 4000 cores *** Operational MODE: preforking+async *** No Archives Loaded Traceback (most recent call last):   File "./webrecorder/main.py", line 9, in <module>     application = AppController().app   File "./webrecorder/appcontroller.py", line 127, in __init__     proxy_options=self._get_proxy_options())   File "/usr/local/lib/python3.5/site-packages/wsgiprox/wsgiprox.py", line 357, in __init__     cert_not_before=-3600)   File "/usr/local/lib/python3.5/site-packages/certauth/certauth.py", line 73, in __init__     res = self.load_root_ca_cert(overwrite=overwrite)   File "/usr/local/lib/python3.5/site-packages/certauth/certauth.py", line 95, in load_root_ca_cert     self.ca_file_cache[ROOT_CA] = cert_str   File "/usr/local/lib/python3.5/site-packages/certauth/certauth.py", line 276, in __setitem__     with open(filename, 'wb') as fh: PermissionError: [Errno 13] Permission denied: './proxy-certs/webrecorder-ca.pem' unable to load app 0 (mountpoint='') (callable not found or import error) *** no app loaded. going in full dynamic mode ***
I tried replacing the webrecorder-ca.pem with a sample file since I didn't have time to generate one but it still errors out.

authors: muramasatheninja seamang

repo: webrecorder/webrecorder


text:
allow urls to be a string

Description
fixes #327 -- much as I think the spec is doing a bad thing by allowing this :-)

Nice, thank you. Why the stringify and parse? Just curious :)

deep-copy. Unrelated to the issue but i had just seen weird behaviour when modifying the config in ways the browser did not expect.

Yes modifying objects can cause unwanted behaviors especially if objects are reused. LGTM.

authors: KaptenJansson fippo ngauthier

repo: webrtc/adapter


text:
error running on colab

Hi, when I try to run the code on colab, there are issues with cuda and cuDNN:

specific error:
2024-03-11 03:23:38.648199: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:9261] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-03-11 03:23:38.648254: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:607] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-03-11 03:23:38.649936: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1515] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-03-11 03:23:39.828723: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
[03:23:40] WARNING  The following values were not passed to accelerate launch and
Are there any clue of what is happening or possible solutions? Thanks!

Not sure what raises the error exactly, since I haven't run this in the colab.
But apparently, it seems that the colab cannot find the appropriate cuda or something. Have you succeeded in running diffuers official examples (dreambooth, lora and so on) in the same colab instance?
Or you can try to run dreamstyler script without accelerate e.g. python dreamstyler/train.py ...

tried to use  python dreamstyler/train.py ... without accerlerate, although still print out same error,  but the training can work.
Thanks for suggestion!

authors: KolvacS-W nmhkahn

repo: webtoon/dreamstyler


text:
NodeJS bindings

What programming language are you using (C/C++/Go/Rust)?
Wish it was NodeJS.
What did you expect to see and what you saw instead?
NodeJS bindings would be excellent to attract users of Electron, away from it. And NodeJS is a well established JS runtime.

@matteoturini Have you tried the Deno bindings at https://github.com/webview/webview_deno ?

Yes. It's not the same thing. I still need NodeJS webviews, it's not the same thing.

We rely on the community's support to create bindings. If you have the ability to make a JavaScript binding that relies on the NodeJS runtime, we would be happy for you to get things started. We support bindings by linking to them in our README and the mature ones live in the webview organization.
This repository is for the C/C++ core library. We do not develop bindings for all other languages. If you notice a bug in our library when creating a binding, then please open an issue and let us know!

Hey, I found this today: https://github.com/suchipi/webview-node @matteoturini.

suchipi/webview-node is not a binding, it is a wrapper around exe.

Thank you, I will check it out!

authors: dandeto matteoturini runeimp zdm

repo: webview/webview


text:
获取room avatar报错

wxhook_1  | TypeError [ERR_INVALID_URL]: Invalid URL
wxhook_1  |     at new NodeError (node:internal/errors:371:5)
wxhook_1  |     at onParseError (node:internal/url:536:9)
wxhook_1  |     at new URL (node:internal/url:612:5)
wxhook_1  |     at Function.fromUrl (/node_modules/file-box/dist/src/file-box.js:88:31)
wxhook_1  |     at PuppetPadlocal.roomAvatar (/node_modules/wechaty-puppet-padlocal/dist/puppet-padlocal.js:827:41)
wxhook_1  |     at async Object.exports.create (/libs/Group.js:18:21)
wxhook_1  |     at async refreshGroupInfo (/callbackServer/router/bot.js:32:5)
wxhook_1  |     at async Wechaty.<anonymous> (/callbackServer/router/bot.js:98:3)

Fixed, will be released in wechaty-puppet-padlocal@1.11.18

authors: iyjian padlocal

repo: wechaty/puppet-padlocal


text:
Why not upgrade to a higher version of webpack？

Why not upgrade to a higher version of webpack for reduce the volume of the js bundle and speed up the compilation speed with the latest features?

@PerseveranceZ https://github.com/weexteam/weex-builder/commit/e7392063e88c6635db262f2bc85050bf1f36d82c.
The webpack have been upgraded to 3.10.0.

awesome!!! I have another question. Is UI component library able to support tree-shaking? I have tried it, but weex-ui or other libraries are not supported at present. When I import some components, I will still pack it all in.

repo: weexteam/weex-builder


text:
Custom Objects

I had to change
if (metadata.deserializedType && typeof (<any>metadata.deserializedType).Deserialize === "function") {
            instance[keyName] = (<any>metadata.deserializedType).Deserialize(source);
}

TO
if (metadata.deserializedType && typeof (<any>metadata.deserializedType).Deserialize === "function") {
            instance[keyName] = **new** (<any>metadata.deserializedType).Deserialize(source);
}

in order to maintain object type.
If you skip new here you get an anonymous object.
--- Background
I used @autoserializeAs(MyObject)
but what i got on deserialisation was a anonymous Object without the methods I expected the Object to have (MyObject).
I would appreciate an opinion to this or if i missed something.
Greetings

is object a constructable function (ie class type) or just a literal? You shouldn't need to be using new in there for sure. If autoserializeAs is not passed a class type, it will assume you are passing in a custom serializer which is  { Deserialize: (instance :  YOUR_TYPE, json:any) => any, Serialize: (instance : YOUR_TYPE) => any}

Hi weichx, thank you for your quick and sorry for my late answer!
Well, I might have special requirements.
See http://plnkr.co/edit/UXBZZN9jhU7pSUH1prGP?p=preview in app.component.ts which uses my patched version.
See http://plnkr.co/edit/5ed8ZK10CFWtHjLTIpTV?p=preview in app.component.ts which uses the original version.
I cannot see any negative side-effects of using the patched version here?

Hi weichx, thank you for your quick answer and sorry for my late answer.
I might have special requirements here.
See http://plnkr.co/edit/5ed8ZK10CFWtHjLTIpTV?p=info for the patched version (app.component.ts)
See http://plnkr.co/edit/QqrY3aPxOimtol7yfvJW?p=info for the original version (app.component.ts)
I couldn't find any negative side effects of my patched version.

authors: tkagerer weichx

repo: weichx/cerialize


text:
When I tried 'make' in surfelwarp

I have installed eigen3.3.9 pangolin cilantro in /usr/local/include, and the configuration of cmake surfelwarp has been successfully configured, but make error:
gyc@3Dre:~/Desktop/3D/surfelwarp/build$ make
[  1%] Building NVCC (Device) object common/CMakeFiles/common_lib.dir/common_lib_generated_sanity_check.cu.o
/home/gyc/Desktop/3D/surfelwarp/common/logging.h: In destructor ‘surfelwarp::LogMessageFatal::~LogMessageFatal()’:
/home/gyc/Desktop/3D/surfelwarp/common/logging.h:114:49: warning: throw will always call terminate() [-Wterminate]
throw new std::runtime_error(log_stream_.str());
^
/home/gyc/Desktop/3D/surfelwarp/common/logging.h:114:49: note: in C++11 destructors default to noexcept
[  1%] Building NVCC (Device) object common/CMakeFiles/common_lib.dir/common_lib_generated_algorithm_types.cu.o
[  2%] Building NVCC (Device) object common/CMakeFiles/common_lib.dir/common_lib_generated_common_texture_utils.cu.o
/home/gyc/Desktop/3D/surfelwarp/common/logging.h: In destructor ‘surfelwarp::LogMessageFatal::~LogMessageFatal()’:
/home/gyc/Desktop/3D/surfelwarp/common/logging.h:114:49: warning: throw will always call terminate() [-Wterminate]
throw new std::runtime_error(log_stream_.str());
^
/home/gyc/Desktop/3D/surfelwarp/common/logging.h:114:49: note: in C++11 destructors default to noexcept
[  2%] Building NVCC (Device) object common/CMakeFiles/common_lib.dir/common_lib_generated_common_utils.cu.o
[  3%] Building NVCC (Device) object common/CMakeFiles/common_lib.dir/common_lib_generated_data_transfer.cu.o
In file included from /home/gyc/Desktop/3D/surfelwarp/common/data_transfer.h:8:0,
from /home/gyc/Desktop/3D/surfelwarp/common/data_transfer.cu:1:
/home/gyc/Desktop/3D/surfelwarp/common/point_cloud_typedefs.h:13:36: fatal error: cilantro/point_cloud.hpp: 没有那个文件或目录
#include <cilantro/point_cloud.hpp>
^
compilation terminated.
CMake Error at common_lib_generated_data_transfer.cu.o.cmake:220 (message):
Error generating
/home/gyc/Desktop/3D/surfelwarp/build/common/CMakeFiles/common_lib.dir//./common_lib_generated_data_transfer.cu.o
common/CMakeFiles/common_lib.dir/build.make:101: recipe for target 'common/CMakeFiles/common_lib.dir/common_lib_generated_data_transfer.cu.o' failed
make[2]: *** [common/CMakeFiles/common_lib.dir/common_lib_generated_data_transfer.cu.o] Error 1
CMakeFiles/Makefile2:337: recipe for target 'common/CMakeFiles/common_lib.dir/all' failed
make[1]: *** [common/CMakeFiles/common_lib.dir/all] Error 2
Makefile:100: recipe for target 'all' failed
make: *** [all] Error 2

Have you solved this problem? I also meet it.

The file reference path in the code file is incorrect. Use the "locate file name" to find the file path, such as 'locate point_cloud.hpp ', and finally change the code.------------------ 原始邮件 ------------------
发件人: "wangmiaowei"<notifications@github.com>
发送时间: 2020年12月1日(星期二) 上午10:40
收件人: "weigao95/surfelwarp"<surfelwarp@noreply.github.com>;
抄送: "shugao1"<583931277@qq.com>;"State change"<state_change@noreply.github.com>;
主题: Re: [weigao95/surfelwarp] When I tried 'make' in surfelwarp (#42)


text:
BluetoothBytesParser array index out of bounds

E/AndroidRuntime: FATAL EXCEPTION: DefaultDispatcher-worker-9
Process: com.welie.blessedexample, PID: 22490
java.lang.ArrayIndexOutOfBoundsException: length=7; index=7
at com.welie.blessed.BluetoothBytesParser.setCurrentTime(BluetoothBytesParser.kt:559)
at com.welie.blessedexample.BluetoothHandler$handlePeripheral$1.invokeSuspend(BluetoothHandler.kt:54)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:39)
at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
value size is reset to 7 in call to setDateTime() after being set to 10 in setCurrentTime()
fun setCurrentTime(calendar: Calendar): Boolean {
    value = ByteArray(10)
    setDateTime(calendar)
    value[7] = ((calendar[Calendar.DAY_OF_WEEK] + 5) % 7 + 1).toByte()
    value[8] = (calendar[Calendar.MILLISECOND] * 256 / 1000).toByte()
    value[9] = 1
    return true
}

/**
 * Sets the byte array to represent the current date in CurrentTime format
 *
 * @param calendar the calendar object representing the current date
 * @return flase if the calendar object was null, otherwise true
 */
fun setDateTime(calendar: Calendar): Boolean {
    value = ByteArray(7)
    value[0] = calendar[Calendar.YEAR].toByte()
    value[1] = (calendar[Calendar.YEAR] shr 8).toByte()
    value[2] = (calendar[Calendar.MONTH] + 1).toByte()
    value[3] = calendar[Calendar.DATE].toByte()
    value[4] = calendar[Calendar.HOUR_OF_DAY].toByte()
    value[5] = calendar[Calendar.MINUTE].toByte()
    value[6] = calendar[Calendar.SECOND].toByte()
    return true
}

Good catch! Fixed in 9c3bcff4761051962ab9d4e404d69b515b3ac3ad

authors: imsunburnt weliem

repo: weliem/blessed-android-coroutines