text:
"Up and running" commands in README

Updating the readme file with "Up and running" commands and updating the link to open an issue

Just wanted to mention that the ionic sass setup command is only needed once.  That sets everything up, so then if you commit things after that, the other devs will not run that command.  So I'd recommend updating your readme accordingly.
(Fyi, I'm currently out on vacation, and will give these issues/pr's proper attention when I return.)

Cleaning things up in this repo, so I just manually applied the edits that made sense to keep.

authors: DavidFrahm jpaulobneto

repo: wakatime/wakatime-mobile


text:
String Misspelling

The following string should be fixed to use options rather than otions:
-normalmaps : Sets export otions for normal-mapped mesh export

Fixed in this commit

source: gharchive/issue

authors: t-kepic walbourn

repo: walbourn/contentexporter

license: mit

license_type: permissive

license_source: bigquery


text:
Help: Requesting Logo for Project

Requesting help from someone with graphic design experience to create a logo that matches the theme and personality of the music template.
Looking for a minimalist logo (using project key words/acronyms) with contrasting colors and accenting shapes. Open to other ideas.

Hi @waldronmatt , What about this?

Thanks for your response @waldronmatt ,, like this ? if you need to change please let me know.

Thanks @mirzazulfan these look really good! I think these will be ready to advertise.
Can you please send the png/jpeg files of the blue/purple top and bottom logos under 1 and the white themed logos (1st and 2nd screenshot)?

Hi @waldronmatt , You can download all files and editables in Gdrive .
I made it 2 versions. Thanks for accepting my proposal. PR #22
Best regard.

Fantastic! Thank you again.

authors: mirzazulfan waldronmatt

repo: waldronmatt/musicWebTemplate

license: MIT

license_source: github-api


text:
Error Invalid point encoding 0x30 when try to use secp256k1 Key Type

Hello,
In my Java application, I am using the Walt ID Credentials SDK along with the Issuer and Verifier APIs. I want to use did:key with the secp256k1 KeyType. However, it seems there is a bug with this KeyType because:

I can't sign a verifiable presentation:

  JsonPrimitive agentVcJwtPrimitive = Json.Default.decodeFromString(JsonPrimitive.Companion.serializer(), vcJwt);
            VerifiablePresentationBuilder verifiablePresentationBuilder = new VerifiablePresentationBuilder();
            verifiablePresentationBuilder.addCredential(agentVcJwtPrimitive);
            verifiablePresentationBuilder.setPresentationId();
            verifiablePresentationBuilder.setDid(subjectDid);
            verifiablePresentationBuilder.setNonce(cryptographyUtils.generateNonce());
            LocalKey localKey = new LocalKey(subjectKeyJwk);
            return verifiablePresentationBuilder.buildAndSign(localKey);

I have made the VerifiablePresentationBuilder class that wraps the kotlin  PresentationBuilder class.
Also this is the stack trace of the error I get on the walt id library:
Java.lang.IllegalArgumentException: Invalid point encoding 0x30
	at org.bouncycastle.math.ec.ECCurve.decodePoint(Unknown Source) ~[bcprov-jdk18on-1.78.jar:na]
	at id.walt.crypto.keys.JvmLocalKeyCreator.ecRawToJwk(LocalKeyGenerator.jvm.kt:50) ~[waltid-crypto-jvm-0.2.0.jar:na]
	at id.walt.crypto.keys.JvmLocalKeyCreator.importRawPublicKey(LocalKeyGenerator.jvm.kt:37) ~[waltid-crypto-jvm-0.2.0.jar:na]
	at id.walt.crypto.keys.LocalKey$Companion.importRawPublicKey(LocalKey.jvm.kt:275) ~[waltid-crypto-jvm-0.2.0.jar:na]
	at id.walt.did.utils.KeyUtils.fromPublicKeyMultiBase-gIAlu-s(KeyUtils.kt:28) ~[waltid-did-jvm-0.2.0.jar:na]
	at id.walt.did.dids.resolver.local.DidKeyResolver.resolveToKey-gIAlu-s(DidKeyResolver.kt:40) ~[waltid-did-jvm-0.2.0.jar:na]
	at id.walt.did.dids.resolver.local.DidKeyResolver.resolve-gIAlu-s(DidKeyResolver.kt:21) ~[waltid-did-jvm-0.2.0.jar:na]
	at id.walt.did.dids.resolver.LocalResolver.resolve-gIAlu-s(LocalResolver.kt:55) ~[waltid-did-jvm-0.2.0.jar:na]
	at id.walt.did.dids.DidService.resolve-gIAlu-s(DidService.kt:138) ~[waltid-did-jvm-0.2.0.jar:na]
	at id.walt.credentials.PresentationBuilder.resolveDidAuthentication(PresentationBuilder.kt:94) ~[waltid-verifiable-credentials-jvm-0.2.0.jar:na]
	at id.walt.credentials.PresentationBuilder.buildAndSign(PresentationBuilder.kt:87) ~[waltid-verifiable-credentials-jvm-0.2.0.jar:na]

I can't add credentials to my wallet (running locally).
(screenshot attached)

I have no issues when the KeyType is   Ed25519, but I need secp256k1 for compatibility with Ethereum.
I also noticed in your codebase that there is a commented-out test for this, but there is no related issue on GitHub.
@JvmStatic
        fun `given raw string, when imported then the import succeeds having the correct key type, key id and hasPrivate values`(): Stream<Arguments> =
            Stream.of(
                ........
                // secp256r1 (throwing Invalid point encoding 0x30)
//                arguments(loadResourceBytes("public-bytes/secp256k1.bin"), KeyType.secp256k1, false),
                // secp256r1 (throwing Invalid point encoding 0x30)
//                arguments(loadResourceBytes("public-bytes/secp256r1.bin"), KeyType.secp256r1, false)
                .........
            )

Is there a plan to fix this? Can we help somehow to expedite the process?
Thank you,
Myrto

Resolved by recently merged PR #630. Please update your dependencies.
Thanks again for your feedback!

The issue was solved by updating the dependencies thank you!

authors: cpatsonakis myrtp

repo: walt-id/waltid-identity


text:
[CLI] wandb: ERROR Dropped streaming file chunk

Describe the bug
I'm running a sweep. I started 6 agents in parallel with that sweep id. All going fine. Then I started another 6 agents with the same sweep id in a different parallel process. Working fine at start, but after a while, I started seeing the following error on every log step:
wandb: ERROR Dropped streaming file chunk (see wandb/debug-internal.log) ERROR:root:dropped chunk 404 Client Error: Not Found for url: https://api.wandb.ai/files/[ENTITY]/[PROJECT]/c60hxx3a/file_stream NoneType: None
The file wandb/debug-internal.log is blank.
Any ideas on what might be going wrong?
Operating System

OS: Ubuntu 18.04.4 LT
Environment: Python
Python Version: 3.9.2

Hey @sophiaas , thanks for reporting the issue. Could you please share the wandb version you're using? This was a known issue in a previous wandb version, hence, my reason for asking.
Also, can you try syncing the runs, using wandb sync and check if this resolves the issue? As it seems like wandb tried to upload a file that wasn’t there/available. To get to the root cause as to why this is happening - we would need more logs, I see you mentioned that debug-internal.log was empty. If possible, could you share other log files - for instance: debug.log, etc.

@sophiaas when you start your agent be sure to specify the fully qualified sweep name, i.e. USERNAME/PROJECT/SWEEP_ID that's my best guess as to what might be going wrong.

I met the same ERROR. When I accidentally deleted the runs on webpage, I get the same ERROR in CLI "ERROR:root:dropped chunk 404 Client Error: Not Found for url", and I can't stop it by CTRL C. My wandb version is 0.11.2.

@vanpelt I think this was my issue. I'm making sure to provide all of those details now and am no longer running into the error. Thanks!

authors: Chuyun-Shen anmolmann sophiaas vanpelt

repo: wandb/client


text:
[CLI] Unable to retrieve a run with parameter in scientific notation

Hi, wandb team!
I found it's not possible to retrieve a run with one of the parameters as a small float in scientific notation.
I have two runs with the same parameter being 0.0001 and 0.00001 (which is 1e-05).
wandb.Api.runs is used to download runs.
Step 1: Download both runs - correct

Step 2: Download only run with config.beta_f=0.0001 - correct

Step 3: Download only run with config.beta_f=0.00001 - problem

Looks like there is some problem on the server side.
Environment

Mac OS Monterey 12.0.1
Jupiter Notebook in VSCode
Python 3.8.9

For simplicity I made a simple public project with only 3 runs: https://wandb.ai/phil_s/for_testing/
It has only 2 runs with two parameters in their config files: alpha and beta.
alpha is always 1, beta can be 0.0001 or 0.00001.
The code I download these runs with is:
import wandb

api = wandb.Api(timeout=19)
betas = (0.0001, 0.00001, 1e-05)
for beta in betas:
    runs = api.runs("for_testing", filters={
        "config.alpha": 1,
        "config.beta": beta,
        })

    print(f'Beta {beta} got {len(runs)} runs.\n')

As you see in betas array, for beta=0.00001 I tried its scientific notation also.
The output of this script is:
Beta 0.0001 got 1 runs.

Beta 1e-05 got 0 runs.

Beta 1e-05 got 0 runs.

Hope this little experiment will help in finding the problem.

Hi @PhilSk!
There is probably no issue with how you are using scientific notation, but this is likely MongoDB's behavior that you are facing. Runs are filtered by the MongoDB Query Language, and due to some of the underlying logic of MongoDB, people get unintended effects - like your floating point equality check failing.
You can likely remedy this by changing:
filters = {'config.some_key' : 1e-05}

to
filters = {'config.some_key' : {"$lte" : 1e-05, "$gte" : 1e-05}}

Thank you very much!

authors: PhilSk ramit-wandb


text:
[Q] Which is the port I should expose in my docker container to use keras Wandbcallback() to log models in wandb?

I am currently logging my Keras weights in my Weights and Biases environment using Wandbcalback(). It works fine when I do it from my local machine.
When I do from a container, that is being used in the GCP cloud provider, the models are never being logged. I belevie I should expose some port in the container and in the machine to allow communication with Weights and Biases platform, but I can not find it in the documentation.

Hi @mathbr10, are you using wandb server when you use GCP? If you are can you make sure that the permissions are properly set up?

Hey @mathbr10, by default our library logs data to our hosted service at https://wandb.ai, this is the simplest way to use wandb and doesn't require any port forwarding.
If you want to run your own private wandb server you'll want to configure a load balancer and DNS then you can configure the SDK to use that server by setting the WANDB_BASE_URL environment variable.

Hello @lesliewandb, no I am only using Wandbcallback() and normal wandb run. I did not set those permission but they are related to wadb server wright?

Hi @vanpelt, yes maybe the port is not the poblem. I want to use your hosted serve in wandb.ai, but when I use keras WandbCallback  (https://docs.wandb.ai/ref/python/integrations/keras/wandbcallback) it does not logs the model in my gcp machine. It logs if I train in my local machine though.

Are you seeing any error messages in the logs?  You still need to call wandb.init before calling model.fit with the callback.  It could be that your containers have firewall rules that prevent access to the internet, but you would see errors in the logs.

Hello @vanpelt yes I am calling it. I am sending attached the output log
output.log. Below I am sending also the callback structure we are using.
earlystopping = EarlyStopping(monitor="val_loss", patience=5, restore_best_weights=True)         # TODO: add schedulers here         self.callbacks = [             earlystopping,             tf.keras.callbacks.ModelCheckpoint(                 "ckpts/weights.{epoch:02d}-{val_accuracy:.5f}.hdf5",                 monitor="val_accuracy",                 verbose=1,                 save_best_only=False,  # save all the checkpoints                 # was showing error because the model's ist parent is tfimm not tf.keras.Model                 save_weights_only=True,                 mode="max",                 save_freq="epoch",             ),             WandbCallback(                 save_model=True,                 monitor="val_accuracy",                 mode="max",                 save_graph=True,                 save_weights_only=True,                 log_weights=True,                 log_gradients=False,             ),         ]

Data is being download from wandb in my pipeline. Where is located the ./wandb/debug-internal.log I cant find it in the logs. Ok I will try this approach and get back to you soon.

@mathbr10 since we haven't heard from you, we are going to close this issue. Feel free to re-open if you still have follow up questions.

authors: kptkin lesliewandb mathbr10 vanpelt

repo: wandb/wandb


text:
🛑 网盘_alist is down

In d20605e, 网盘_alist (https://pan.wsee.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 网盘_alist is back up in bd7296a after 11 minutes.

repo: wang-task/upptime


text:
无法选中图片

bug 描述
http://106.12.198.214:8882/main/examples/default-mode.html
图片内容过多时，选不中图片。（已微信沟通，有视频）
你预期的样子是？
可选中图片
系统和浏览器及版本号
Mac OS，Chrome
wangEditor 版本
v5
demo 能否复现该 bug ？
不能
最小成本的复现步骤

使用 http://106.12.198.214:8882/main/examples/default-mode.html
第一张图片上面多插入几个空行
尝试选中第一张图片，它会自动滑动

已修复

改问题的原因如下图


text:
全屏功能怎么开启

菜单栏上面的一些参数有没有具体一点的文档解释下

引入 wangEditor-fullscreen-plugin.css 和 wangEditor-fullscreen-plugin.js 两个文件，然后在 editor.create() 之后 创建 E.fullscreen.init('#editor') 就可以了（#editor 是之前挂载编辑器实例的元素），在菜单栏最后会出现“全屏”字样，点击就会全屏

引入 wangEditor-fullscreen-plugin.css 和 wangEditor-fullscreen-plugin.js 两个文件，然后在 editor.create() 之后 创建 E.fullscreen.init('#editor') 就可以了（#editor 是之前挂载编辑器实例的元素），在菜单栏最后会出现“全屏”字样，点击就会全屏

vue版本的呢？

可以看看这个  原生js的的全屏预览+全屏编辑，官方只给了一个jq的版本 https://github.com/taosiqi/wangEditor-fullscreen-preview

V4 即将发布，已解决该问题，感谢反馈

authors: UltramanWeiLai javaWiley richardmyu taosiqi zazzlec


text:
上传图片问题

我本地运行没问题，上传阿里服务器后，上传大图片会报错，但是小图片可以运行，请问该怎么解决

这种特殊情况，还是建议用plupload重写一下上传功能http://www.kancloud.cn/wangfupeng/wangeditor2/123690 这样遇到什么问题，你可以去查找plupload的解决方案。毕竟uppload算是比较成熟的产品（七牛推荐用），绝大部分问题应该都会有相应的解决方案。

好的，谢谢


text:
这个项目残留部分跳一跳的代码

这个项目残留部分跳一跳的代码，是否需要一起删除一些没用的代码，比如截距的计算，整体精简净化？

跟跳一跳什么关系

@hanchun995    ，抖音机器人项目是直接拷贝了跳一跳那个项目，就连截图也保存为autojump.jpg，结构也非常相似，还有算跳跃时间的代码

@huobaolajiao  跳一跳项目也是楼主写的。

authors: hanchun995 huobaolajiao ronanhardiman

repo: wangshub/Douyin-Bot


text:
5.15.2编译报QSurface::Direct3DSurface未定义

我暂时屏蔽了，但是不知道会不会导致其他问题，可编译通过使用。

OK，我马上修复，不好意思了。屏蔽没问题的。

最新代码应该没问题了

请问，顶栏支持变更自定义的颜色么？


text:
udp2raw 20200818.0 带宽非对称网络速度异常

发现一个现象，使用 udp2raw + wireguard， 家用2条宽带，一条下300M,上30M  另一条下500M，上50M， 上下行不对等。
使用udp2raw后，下行速度会降低到和上行一样的速度，而且抢占上行速度会影响隧道中的下行速度。CPU占用很低， 去掉udp2raw直接使用wireguard， 速度和宽带一样，上下行不对等。
--raw-mode faketcp --cipher-mode aes128cbc --auth-mode hmac_sha1  --lower-level 模式。 不清楚是不是bug。

it's weird, I am not sure the reason.
if you would like to further debug the issue, maybe you can try some other solutions and see if they have similiar problems,  for example:

openvpn with tcp mode
phantun + wireguard.

other ideas:
when the problem 下行速度会降低到和上行一样的速度 happens,  you download a large file from VPS to your PC (without going through udp2raw/wireguard) with real TCP, see if real TCP can make use of the missing bandwith.


text:
Debian pyinstaller ModuleNotFoundError: No module named 'main.cli'; 'main' is not a package

pip3 install pyinstaller

cd ~/magic-wormhole/pyi

/home/user/.local/bin/pyinstaller --clean --distpath=dist wormhole.exe.spec

32 INFO: PyInstaller: 3.6
32 INFO: Python: 3.7.3
33 INFO: Platform: Linux-4.19.125-1.pvops.qubes.x86_64-x86_64-with-debian-10.4
34 INFO: UPX is not available.
35 INFO: Removing temporary files and cleaning cache in /home/user/.cache/pyinstaller
35 INFO: Extending PYTHONPATH with paths
['/home/user/magic-wormhole/src', '/home/user/magic-wormhole']
36 INFO: checking Analysis
36 INFO: Building Analysis because Analysis-00.toc is non existent
36 INFO: Initializing module dependency graph...
37 INFO: Caching module graph hooks...
40 INFO: Analyzing base_library.zip ...
2364 INFO: Caching module dependency graph...
2425 INFO: running Analysis Analysis-00.toc
2453 INFO: Analyzing /home/user/magic-wormhole/src/wormhole/__main__.py
2455 INFO: Processing module hooks...
2455 INFO: Loading module hook "hook-pydoc.py"...
2456 INFO: Loading module hook "hook-encodings.py"...
2499 INFO: Loading module hook "hook-xml.py"...
2702 INFO: Looking for ctypes DLLs
2702 INFO: Analyzing run-time hooks ...
2707 INFO: Looking for dynamic libraries
2885 INFO: Looking for eggs
2885 INFO: Python library not in binary dependencies. Doing additional searching...
2919 INFO: Using Python library /usr/lib/x86_64-linux-gnu/libpython3.7m.so.1.0
2921 INFO: Warnings written to /home/user/magic-wormhole/pyi/build/wormhole.exe/warn-wormhole.exe.txt
2936 INFO: Graph cross-reference written to /home/user/magic-wormhole/pyi/build/wormhole.exe/xref-wormhole.exe.html
2939 INFO: checking PYZ
2939 INFO: Building PYZ because PYZ-00.toc is non existent
2939 INFO: Building PYZ (ZlibArchive) /home/user/magic-wormhole/pyi/build/wormhole.exe/PYZ-00.pyz
3177 INFO: Building PYZ (ZlibArchive) /home/user/magic-wormhole/pyi/build/wormhole.exe/PYZ-00.pyz completed successfully.
3179 INFO: checking PKG
3179 INFO: Building PKG because PKG-00.toc is non existent
3179 INFO: Building PKG (CArchive) PKG-00.pkg
5306 INFO: Building PKG (CArchive) PKG-00.pkg completed successfully.
5307 INFO: Bootloader /home/user/.local/lib/python3.7/site-packages/PyInstaller/bootloader/Linux-64bit/run
5307 INFO: checking EXE
5308 INFO: Building EXE because EXE-00.toc is non existent
5308 INFO: Building EXE from EXE-00.toc
5308 INFO: Appending archive to ELF section in EXE dist/wormhole.exe
5361 INFO: Building EXE from EXE-00.toc completed successfully.
user@disp5326:~/magic-wormhole/pyi$ ls
build  build-exe  dist  wormhole.exe.spec
user@disp5326:~/magic-wormhole/pyi$ cd dist/
user@disp5326:~/magic-wormhole/pyi/dist$ ls
wormhole.exe
user@disp5326:~/magic-wormhole/pyi/dist$ ./wormhole.exe
Traceback (most recent call last):
  File "wormhole/__main__.py", line 3, in <module>
ModuleNotFoundError: No module named '__main__.cli'; '__main__' is not a package
[9355] Failed to execute script __main__

https://github.com/warner/magic-wormhole/pull/298
//cc @ThomasWaldmann

Hmm, does it work when removing /__main__.py and just give the package dir?

authors: ThomasWaldmann adrelanos

repo: warner/magic-wormhole


text:
Remove unused import in _version.py from file

The _version.py file generated for a from_file environment contained an unused import sys which occasionally could cause linting failures.

Looks good.. thanks! I was running into this problem myself just a few days ago.
I think that travis failure was because flake8 has stopped supporting py2.6 . I've updated the travis config to downgrade flake8 on older pythons, so I think it should pass when I merge this.

source: gharchive/pull-request

authors: akarnani warner

repo: warner/python-versioneer

license: Unlicense


text:
Version 0.5.0 release

Version 0.5.0 release. Besides bumping the version this PR also includes the following changes:

Separate the ansible-lint license.
Update changelog to include all changes for v0.5.0.
Remove duplicate documentation (code of conduct).
Add already existing documentation to the Sphinx documentation.
Add additional badges to the README.md.
Simplify and update the GitHub Workflow to release to PyPi.
Updated the version_added in all new rules.

Note: before the actual release the GitHub secretes for PyPi will need to be updated!

I've just updated to GitHub actions secrets to include the new PyPi tokens.

I've just updated to GitHub actions secrets to include the new PyPi tokens.

repo: warpnet/salt-lint


text:
update wasmbus-rpc and async-nats

Signed-off-by: stevelr steve@cosmonic.com

Closing this as we've updated since this PR

authors: brooksmtownsend stevelr

repo: wasmCloud/wash


text:
[BUG] The Fedora install fails

Affected project(s)

[ ] documentation
[ ] examples
[ ] wasmCloud host
[X] wasmCloud CLI (wash)
[ ] wasmCloud dashboard UI (washboard)
[ ] capability providers
[ ] provider bindgen
[ ] control interface client
[ ] other / not sure

Describe the bug
I have tried to install the v1 alpha on my Fedora laptop. I have followed the instructions on https://wasmcloud.com/docs/1.0/installation?os=fedora and it failed:
$ curl -s https://packagecloud.io/install/repositories/wasmcloud/core/script.rpm.sh | sudo bash
sudo dnf install wash
[sudo] password for horacio:
Detected operating system as fedora/39.
Checking for curl...
Detected curl...
Downloading repository file: https://packagecloud.io/install/repositories/wasmCloud/core/config_file.repo?os=fedora&dist=39&source=script
done.
Installing pygpgme to verify GPG signatures...
wasmCloud_core-source                                                                                205  B/s | 833  B     00:04
No match for argument: pygpgme
Error: Unable to find a match: pygpgme

WARNING:
The pygpgme package could not be installed. This means GPG verification is not possible for any RPM installed on your system.
To fix this, add a repository with pygpgme. Usualy, the EPEL repository for your system will have this.
More information: https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F

Installing yum-utils...
wasmCloud_core-source                                                                                483  B/s | 951  B     00:01
Package dnf-utils-4.5.0-1.fc39.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!

WARNING:
The yum-utils package could not be installed. This means you may not be able to install source RPMs or use other yum features.

Generating yum cache for wasmCloud_core...
Generating yum cache for wasmCloud_core-source...

The repository is setup! You can now install packages.
Last metadata expiration check: 0:00:01 ago on Wed 20 Mar 2024 02:20:55 PM CET.
No match for argument: wash
Error: Unable to find a match: wash

I am going to dig on it to try to find exactly where is the problem.
Steps to reproduce

Run the install script on a Fedora computer

curl -s https://packagecloud.io/install/repositories/wasmcloud/core/script.rpm.sh | sudo bash
sudo dnf install wash

Expected behavior
A clean install
Environment

OS: Fedora 39
Shell: bash
wasmcloud Version: 1.0 (alpha)

Screenshots / Logs / Additional context
No response

It seems that it's a similar (or even the same) problem to https://github.com/telepresenceio/telepresence/issues/1236
The pygpgme package isn't available in Fedora repositories, it haven't been there since Fedora 31 at least. And as it fails, sudo dnf install wash doesn't work, and we get a no package found error.
Going to look for a workaround...

The next problem, and the big one for me, it's that it seems to be no Fedora 39 package in the packagecloud repository.
I see Fedora 28 to 38, but not 39 (that was released last October).

Fedora 28 was released on 2018, it's nice to have such retro-compatibility, but it would be wonderful to update to last Fedora, IMHO.

I would love to send a PR for the issue, but I don't see where and how the package for the different distros are generated. Anybody could point me to the right place?

Hey @LostInBrittany ! Thank you for filing this and being willing to help, I think we can remove Fedora 28 and update to the latest. The actual release packages are generated from https://github.com/wasmCloud/wasmCloud/tree/main/crates/wash-cli/build, I seem to remember those numbers being generated from the packagecloud API and I'd have to go digging to find out how to find what number == Fedora 39... let me know if you're able to find it and if not I can help take a look

I have found the info, Fedora 39 is the id 279:
{
  "display_name": "Fedora",
  "index_name": "fedora",
  "versions": [
    {
      "id": 28,
      "display_name": "14 Laughlin",
      "index_name": "14",
      "version_number": "14.0"
    },
    {
      "id": 29,
      "display_name": "15 Lovelock",
      "index_name": "15",
      "version_number": "15.0"
    },
    {
      "id": 30,
      "display_name": "16 Verne",
      "index_name": "16",
      "version_number": "16.0"
    },
    {
      "id": 31,
      "display_name": "17 Beefy Miracle",
      "index_name": "17",
      "version_number": "17.0"
    },
    {
      "id": 32,
      "display_name": "18 Spherical Cow",
      "index_name": "18",
      "version_number": "18.0"
    },
    {
      "id": 33,
      "display_name": "19 Schrödingers Cat",
      "index_name": "19",
      "version_number": "19.0"
    },
    {
      "id": 34,
      "display_name": "20 Heisenbug",
      "index_name": "20",
      "version_number": "20.0"
    },
    {
      "id": 143,
      "display_name": "21 Fedora 21",
      "index_name": "21",
      "version_number": "21.0"
    },
    {
      "id": 147,
      "display_name": "22 Fedora 22",
      "index_name": "22",
      "version_number": "22.0"
    },
    {
      "id": 151,
      "display_name": "23 Fedora 23",
      "index_name": "23",
      "version_number": "23.0"
    },
    {
      "id": 169,
      "display_name": "24 Fedora 24",
      "index_name": "24",
      "version_number": "24.0"
    },
    {
      "id": 179,
      "display_name": "25 Fedora 25",
      "index_name": "25",
      "version_number": "25.0"
    },
    {
      "id": 184,
      "display_name": "26 Fedora 26",
      "index_name": "26",
      "version_number": "26.0"
    },
    {
      "id": 188,
      "display_name": "27 Fedora 27",
      "index_name": "27",
      "version_number": "27.0"
    },
    {
      "id": 194,
      "display_name": "28 Fedora 28",
      "index_name": "28",
      "version_number": "28.0"
    },
    {
      "id": 201,
      "display_name": "29 Fedora 29",
      "index_name": "29",
      "version_number": "29.0"
    },
    {
      "id": 204,
      "display_name": "30 Fedora 30",
      "index_name": "30",
      "version_number": "30.0"
    },
    {
      "id": 209,
      "display_name": "31 Fedora 31",
      "index_name": "31",
      "version_number": "31.0"
    },
    {
      "id": 216,
      "display_name": "32 Fedora 32",
      "index_name": "32",
      "version_number": "32.0"
    },
    {
      "id": 226,
      "display_name": "33 Fedora 33",
      "index_name": "33",
      "version_number": "33.0"
    },
    {
      "id": 231,
      "display_name": "34 Fedora 34",
      "index_name": "34",
      "version_number": "34.0"
    },
    {
      "id": 236,
      "display_name": "35 Fedora 35",
      "index_name": "35",
      "version_number": "35.0"
    },
    {
      "id": 239,
      "display_name": "36 Fedora 36",
      "index_name": "36",
      "version_number": "36.0"
    },
    {
      "id": 260,
      "display_name": "37 Fedora 37",
      "index_name": "37",
      "version_number": "37.0"
    },
    {
      "id": 273,
      "display_name": "38 Fedora 38",
      "index_name": "38",
      "version_number": "38.0"
    },
    {
      "id": 279,
      "display_name": "39 Fedora 39",
      "index_name": "39",
      "version_number": "39.0"
    },
    {
      "id": 283,
      "display_name": "40 Fedora 40",
      "index_name": "40",
      "version_number": "40.0"
    }
  ]
}

authors: LostInBrittany brooksmtownsend

repo: wasmCloud/wasmCloud


text:
chore/control interface actor rename

chore(control-interface)!: rename actor to component
chore(host)!: rename ctl actor to component
chore(wash)!: rename ctl actor to component

Feature or Problem
This PR renamed the use of actor to component in the control interface library, and propagates those changes through the host and wash. Note that this doesn't change all code occurrences as those are purely internal, and this PR focuses instead on error messages, NATS topics, and logs.
The notable remaining thing to change from actor to component is the actor_scaled and actor_scale_failed events.
Related Issues

Release Information
Next breaking alpha/rc of wasmcloud and wash
Consumer Impact
Compatibility with previous alpha versions of wasmCloud and wash will be broken, but it already was with the topic change to include v1 so there shouldn't be too much friction here.
Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

@thomastaylor312 I ended up popping the commit off and putting it as a part of https://github.com/wasmCloud/wasmCloud/tree/chore/control-interface-actor-rename-wash so I can create another PR afterwards with this change in wash, so this basically just keeps this PR clean and for the host.


text:
Instance not found; using Maven

Describe the bug
I use maven and not gradle so I built the jar as described in the readme, then I installed the jar using maven cli:
mvn install:install-file -Dfile=wasmer-jni-amd64-linux-0.2.0.jar -DgroupId=org.wasmer -DartifactId=wasmer -Dversion=0.2.0 -Dpackaging=jar

This puts it in my local maven repo. Then I added it as a dependency:
  <dependency>
      <groupId>org.wasmer</groupId>
      <artifactId>wasmer</artifactId>
      <version>0.2.0</version>
    </dependency>

But when I run my code using the example SimpleExample.java almost exactly I recieve the error:
Exception in thread "main" java.lang.NoClassDefFoundError: org/wasmer/Instance
    at com.clopen.Clopen.main(Clopen.java:15)
Caused by: java.lang.ClassNotFoundException: org.wasmer.Instance
    at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:351)

Pretty much it compiles, using the wasmer-jni-amd64-linux-0.2.0.jar as a dependency but cannot find the org.wasmer.Instance object.
Maybe a solution to this is to add the program to the maven repository. I cannot use gradle because this test example of using rust to compile to wasm to run in java will be incorporated into a much larger maven project.

Thanks for the bug report.
Did you inspect the content of the JAR? What do you have inside? I get this:
$ jar tf wasmer-jni-amd64-darwin-0.2.0.jar
META-INF/
META-INF/MANIFEST.MF
org/
org/wasmer/
org/wasmer/Native.class
org/wasmer/exports/
org/wasmer/exports/Export.class
org/wasmer/exports/Function.class
org/wasmer/Instance.class
org/wasmer/Exports.class
org/wasmer/Memory.class
org/wasmer/Module.class
org/wasmer/native/
org/wasmer/native/darwin-amd64/
org/wasmer/native/darwin-amd64/libwasmer_jni.dylib
org/wasmer/native/darwin-x86_64/
org/wasmer/native/darwin-x86_64/libwasmer_jni.dylib

The pom from bintray doesn't appear to list any dependencies.

authors: Hywan Tsangares zacharywhitley

repo: wasmerio/wasmer-java


text:
wasm-terminal: Fix multi-character font support (ligatures)

This merges these issues:
https://github.com/wasmerio/webassembly.sh/issues/62
https://github.com/wasmerio/webassembly.sh/issues/49
With the general response:

So this seems to work in Hyper. And to my understanding, they use the xterm-addon-ligatures, which fixes the way the fonts are rendered. However, I linked to the requirements, and this addon needs system access to use the native font renderer. So we are going to half to figure out how to implement this in the browser 🤔

So I went ahead and asked if we'd get browser support in: https://github.com/xtermjs/xterm.js/issues/958 , and can investigate other solutions later on 😄

The @wasmer/sdk package is mainly focused on running WASI/WASIX programs now and leaves things like stdio or presentation to the user.

repo: wasmerio/wasmer-js


text:
[Decompiler] Clean up and documentation of Expression Analysis

Opening this as a reminder that some code in the expression analysis phase could use better documentation/organization.  In particular the coloring move stuff, the dead set elimination, the use of update_from_stack, and the virtual method stuff.

Lots of clean up in https://github.com/water111/jak-project/pull/271
Still need to work on virtual methods

virtual methods have been cleaned up in https://github.com/water111/jak-project/pull/488

license: ISC


text:
fix actor compaction

Actor compaction can now be enabled! And it doesn't crash!

Pull Request Test Coverage Report for Build 1465207999

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.664%

Totals

Change from base Build 1464820096:
0.0%

Covered Lines:
40396

Relevant Lines:
72571

💛  - Coveralls


text:
Deactivate comments for PRs from bots

It is already implemented in part as it reports:
WatermelonAI Summary
AI Summary deactivated by pre-commit-ci[bot]

but it still tries to figure out Prs and tickets.
I'd prefer that for bot PRs watermelon could just not comment at all.
https://github.com/cleder/pygeoif/pull/190#issuecomment-1808519743

We should definitely do that. Thanks for your feedback @cleder

@cleder this change has been included in today's release. Please let us know how if it behaves fine!

works as expected

authors: baristaGeek cleder

repo: watermelontools/watermelon


text:
Fix undocumented code in SpeechToTextV1

{
  "warnings": [
    {
      "file": "\/Users\/vincentherrin\/Github\/ios-sdk-dev\/Source\/SpeechToTextV1\/Models\/TranscriptionSettings.swift",
      "line": 155,
      "symbol": "FLAC",
      "symbol_kind": "source.lang.swift.decl.enumelement",
      "warning": "undocumented"
    },
    {
      "file": "\/Users\/vincentherrin\/Github\/ios-sdk-dev\/Source\/SpeechToTextV1\/Models\/TranscriptionSettings.swift",
      "line": 156,
      "symbol": "L16",
      "symbol_kind": "source.lang.swift.decl.enumelement",
      "warning": "undocumented"
    },
    {
      "file": "\/Users\/vincentherrin\/Github\/ios-sdk-dev\/Source\/SpeechToTextV1\/Models\/TranscriptionSettings.swift",
      "line": 157,
      "symbol": "WAV",
      "symbol_kind": "source.lang.swift.decl.enumelement",
      "warning": "undocumented"
    },
    {
      "file": "\/Users\/vincentherrin\/Github\/ios-sdk-dev\/Source\/SpeechToTextV1\/Models\/TranscriptionSettings.swift",
      "line": 158,
      "symbol": "Opus",
      "symbol_kind": "source.lang.swift.decl.enumelement",
      "warning": "undocumented"
    }
  ],
  "source_directory": "\/Users\/vincentherrin\/Github\/ios-sdk-dev"
}

Fixed with 6472114bb897baba73fa9ee22210e18c8bc82890

repo: watson-developer-cloud/ios-sdk


text:
Failover local file

I have a working example for https://github.com/wavelog/WaveLogGate/issues/23
If error (if WLG can not push QSO with success), the QSO is written in the specified file :

Import the resulting file with multiples QSO in the WaveLog web interface works fine.
Maybe we can improve/adapt GUI error messages when the QSO is logged in the file.
Test Ok on Ubuntu 22, cannot check on Windows atm.

A few more things besides my considerations above(sorry!).
What about:

checking if location exists? Otherwise the write would fail and the OP can't see it.
a "folder-requester" modal where one can chose the path? (Should be doable with internal functions)

i learned from Wavelog itself: Everything needs to be bulletproof, because people are doing the wildest things...

repo: wavelog/WaveLogGate


text:
feat: dynamic clientId Initialization

Hi :)

Added folders for methods, constants, and states (for global ref) under src, and restructured the folder architecture considering scalability for future method development.
Introduced a new method named setGoogleClientId, which operates by changing the global ref value.
The clientId can be initialized in the following ways:

Statically during middleware installation.
Dynamically in any component.
Initially set and later updated dynamically.

Fixed an issue where the style height value was not being applied to the element before the renderButton of GoogleSignInButton is called.
Updated the documentation, including a caution block in the section about initializing nuxt-vue3-google-signin.

I am very happy to contribute to this project. Please let me know if there are any suggestions for improvements in the folder structure or functionality.

Thanks @zuhno
this is a brilliant work, and im really happy that you are really keen to be a contributor
i will review the code and let you know my thoughts

@kasvith Please let me know if there are any parts that need to be revised.

Sure, i didnt have much time lately to focus on the project

hi @zuhno made a comment

im adding this to the v3 milestone

I have checked this. I'll check the support for this feature in nuxt.
thank you for reviewing the PR :)

i have checked the related repository and will follow up on the merge status. thanks.

Now all looks great, i will check this out locally and then we are good to go

authors: kasvith zuhno


text:
[feat] set png compression/filter type through arguments

Implemented the ability to set png compression/filter type with -C and -F argument
pub enum CompressionType {
    Default,
    Fast,
    Best,
    Huffman,
    Rle,
}

pub enum FilterType {
    NoFilter,
    Sub,
    Up,
    Avg,
    Paeth,
    Adaptive,
}

Pr looks great! Is there anyway we can make this genetic enough for all the backend formats ?

Pr looks great! Is there anyway we can make this generic enough for all the backend formats ?

Compression type and filter type are options only available for png format. We can add options for other formats by using a similar smart pointer

Pr looks great! Is there anyway we can make this generic enough for all the backend formats ?

Compression type and filter type are options only available for png format. We can add options for other formats by using a similar smart pointer

Ok I see, in that case, can we offload the compression to some other crate to do it for us which can support multiple formats?
If that's too big of a task right now, then it's just best to merge this for now :D
Also while we're on the topic, I added man-page generation in build.rs with scdoc, would you mind documenting this flag in the 1 and 7 sections of wayshot?

This is a really good PR and I wish to get this to production someday. I just need to find a good way to compress all supported formats.

authors: EdenQwQ Shinyzenith

repo: waycrate/wayshot


text:
🛑 Hacker News is down

In 5fe7cc3, Hacker News (https://news.ycombinator.com) was down:

HTTP code: 502
Response time: 309 ms

Resolved: Hacker News is back up in c03f292.


text:
JSONResponse instead of PlainTextResponse

It would be great if the middleware could be configurable to return JSONResponse instead of PlainTextResponse in case of an error. My frontend application expects JSON responses, and right now I have to apply some sort of workaround to handle this.

Hi @cay89,
please check if commit 5922577ec39d859b9fc48f4d0c5faf0ebc6819a7 could satisfy your requirements. It makes more sense to return JSON responses, totally agree.

I'm ok with that, thanks.

Okay, thanks for confirming. I'll cut a new release later containing this change.

repo: waza-ari/fastapi-keycloak-middleware


text:
Smooth panning transition examples

First of all, I thank you for this lib. It is really helpful to my application.
I needed the smooth panning transition, so I was able to successfully implement it using tween.js as your team previously mentioned in another issue #791.
Then, I reckon having some examples would be helpful to others who looking for similar features because it was little bit of work for me. So after I refine my work a bit, I would like to make a PR about smooth transition example, probably for zoom-in / zoom-out / fit-view
What do you think of it?

Hey @dev-mish-mash
good idea :) We would really appreciate that!
Please open it in the website repo: https://github.com/wbkd/react-flow-docs/tree/main/src/example-flows

Hey @dev-mish-mash
good idea :) We would really appreciate that!
Please open it in the website repo: https://github.com/wbkd/react-flow-docs/tree/main/src/example-flows

authors: dev-mish-mash moklick

repo: wbkd/react-flow


text:
Abort on Default SystemD Unit on Ubuntu 20.04 and Raspberry Pi OS (Latest)

@raspberrypi:~/GoveeBTTempLogger/GoveeBTTempLogger/usr/local/bin $ sudo ./goveebttemplogger -v 1 --log /var/log/goveebttemplogger --time 60 --svg /var/www/html/goveebttemplogger/ --battery 8 --minmax 8 --titlemap /var/www/html/goveebttemplogger/gvh-titlemap.txt
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::erase: __pos (which is 47) > this->size() (which is 32)
Aborted

It seems like the trailing / on the --svg directory is what causes the crash.  I'm documenting here and will try putting my C++ hat on to submit a follow up pull request.  (It's been awhile since I've written C++, so bear with me... :grin:)

Is that the only output you got?

Yes

If you removed the trailing / on the --svg option it doesn't crash the same way?

Yes
As a side-effect of removing the /, it attempts to output SVG's to the path, /var/www/html/goveebttemploggergvh-XXXXXXXX.svg.

@sl33nyc Thanks for pointing this out. I think I introduced the problem a couple of months ago and am not positive how my system has been correctly working. I just pushed new code that should fix it.
I also included a validated parameter dump if you use --verbose 3 or higher. It was especially useful because the machine I was testing didn't have those specific paths, so my validation routine didn't use either one initially.
If this now works properly, you can close the issue. ;-)

I think it works great now!  Thanks for the quick fix!

repo: wcbonner/GoveeBTTempLogger


text:
Consider bumping dateformat.

Issue description
The dateformat version required seems to be a very old (and rather large) version https://github.com/wclr/ts-node-dev/blob/f6eb46f30f068bd3fe97cad3fb8a530d0eaaa495/package.json#L45
Apparently, the version currently in use is what node-dev used until https://github.com/fgnass/node-dev/pull/223.  Would you consider updating the version in use?  I would offer a PR, but few of the tests pass on my machine.

Also bumping this. A related problem is that dateformat in the range specified relies on meow at version 3, which requires trim-newlines at version 1 which has a high security vulnerability detected by dependabot

repo: wclr/ts-node-dev


text:
tsconfig-paths works with ts-node but not ts-node-dev

Issue description
I'm trying to use ts-node-dev in conjunction with tsconfig-paths. I have arrived at the following command:
ts-node-dev --project ./configs/tsconfig.custom.json -r tsconfig-paths/register ./src/index.ts

Unfortunately, tsconfig-paths doesn't seem to recognize the --project option, resulting in Couldn't find tsconfig.json. tsconfig-paths will be skipped and a failed compile. Normally I would open an issue with tsconfig-paths, but the command works if I use ts-node instead of ts-node-dev:
ts-node --project ./configs/tsconfig.custom.json -r tsconfig-paths/register ./src/index.ts

Is this a bug, or am I doing something wrong? Let me know if I should open this on the tsconfig-paths repo instead. Thanks!
Context
OS: Windows 10
ts-node-dev version: 1.1.8
ts-node version: 10.4.0
tsconfig-paths version: 3.11.0
I have created a git repo with a minimal repro here, where the working and broken commands can be run with yarn working and yarn broken respectively.

As a workaround, it is possible to specify the path via the TS_NODE_PROJECT environment variable, which tsconfig-paths will pick up, even when run with ts-node-dev. Still, it would be more convenient (and cross platform friendly) if the command-line argument worked like for ts-node.

Probably need to pass --project downstream then.

Probably need to pass --project downstream then.

Do you mean that this is something I need to do, or something that ts-note-dev needs to do? If it's the former, could you please let me know how?

Well, it was thoughts out loud. Though I believe, you may pass it downstream yourself (as an argument to your script), but you'll need to duplicate this flag in the cli then.

I am joining the party. My project is monorepo with yarn workspaces. Without option to pass path to tsconfig.json is for my project ts-node-dev just unusable. Hope once you fix it.

fwiw I'm also running a monorepo with yarn workspaces. Within each package's package.json I have the start script configured as:
ts-node-dev --dir ./ --files ./src/index.ts

where each package contains a tsconfig.json that extends a base tsconfig.json in the root of the monorepo

@joeyorlando for me the same compilerOptions.paths doesn't work which make ts-node-dev useless for monorepo, I prefer to use other options rather than relative imports

its a pity

I believe I hit this issue too. I have this in my tsconfig.json:
{
  // ...
  "ts-node": {
    "require": ["tsconfig-paths/register"]
  }
}

And this works: npx ts-node ./src/index.ts
But none of these work:

npx ts-node-dev ./src/index.ts
npx ts-node-dev --project ./tsconfig.json ./src/index.ts
TS_NODE_PROJECT="./tsconfig.json" npx ts-node-dev ./src/index.ts

Only this works: npx ts-node-dev -r tsconfig-paths/register ./src/index.ts
Is this really intended behavior?


text:
Submit updated enrollment table to Gregg Gilbert

after receiving data from Westat

practioner enrollment - by ethnicity, and m/f

repo: wdduncan/NDPBRN


text:
Reduce duplication when writing

We replicate writes to N (typically 3) ingesters to reduce data loss from random failures of machine or process. However this means in stable operation each metric is written to store three times, along with index entries for each label (at least in the DynamoDB back-end).  Say 10 index entries per chunk, for a total of 33 writes.  Nearly one third of these writes are pointless and, worse, they slow down queries because all those entries get re-fetched and finally deduplicated.
One alternative idea:
When an ingester is about to write a chunk, query the index to see if an overlapping chunk already exists. If so, subtract the overlapping part and merge the remainder back into the chunks being accumulated.  This would replace the 33 writes with 11 writes and 2 reads.
This idea doesn't require any particular consistency from the store - if it under-reports we'll just store some pointless chunks as before.

The details have gone hazy, but I believe there's a trade-off with how many ingesters we need to read from. The Dynamo paper section 4.5 has some discussion on this.

This proposal makes every write into a read + a write, and potentially a delete.  As Cortex tends to do many orders-of-magnitude more writes than reads, making queries cheaper by making writes more expensive seems like the wrong direction...
It might be worth considering TCO here; for systems like BigTable & Cassandra, writes are significantly cheaper than reads (in turns of IOPS and $$$), so doing read-on-write is a big no.   Its interesting that this isn't the case for DynamoDB - reads seem to be 1/5th the cost - but does at least suggest that this needs to be done on a per-backend basis.  Although the existing abstractions won't nicely support that.
Alternatives to consider:

The 3x index cost should probably be tackled by indirecting via a timeseries ID, and not having the entries point straight at chunks.  This is something we started with @aaron7 in #442, using the sha256 of the label-set of a series as its fingerprint.  This might also be necessary to do proper stream processing of queries anyway, but won't cover the 3x chunk cost.
On a query you could always get the range of chunks and then read at most 2 of the 3 chunks for every overlapping range, but this seems like it might be challenging (fun?) to compute.
We don't actually need to write to 3 ingesters in normal operation, we should only write to two.  This is discussed in #100, would get you 50% of the wins, and is probably relatively easy to implement.
We could potentially do the merge as form of "Read Repair", writing back deduped chunks after a query.  This would work for backends like Cassandra and BigTable, as you've already paid the read cost.
Moving to something like TSDB for the ingesters, and guaranteeing the last N hours are ingester, would make >80% of queries not touch the chunk store.  I think users are willing to accept slower queries for older data.

As a less rational fear, getting the write path to perform reliably was really challenging; I'd be pretty apprehensive to adding a read into that pipeline.

Thanks, I appreciate the insights.
Bit more background: the main use-case I'm targeting is when you see some data in the last hour and think "what does that look like over the last month?". Depending on the metric, the index reads for 30 days can be very expensive.
I would not change the write path lightly.

Interesting - I wouldn't have thought hour-long queries in the past would have been any more expensive than hour-long now queries, modulo caching effects.  Are the historical tables adequately provisioned in DynamoDB?  Do you know if its index lookups or chunk fetches that are dominating?
If its index, I remember an optimisation I added to make index lookups from [now-1hr, now) cheaper - the index always looks up to the end of the "row".  This is indicated by the inclusion of only a greater-than comparison here.  Given we know the maximum size of chunks, it would be possible to add a less-than comparison to the same place (and plumbing through the logic for the schemas), and terminate the scan early.  Would be a minor improvement for queries that happen in the morning...
If its chunk fetches taking the majority of time (which I guess it is by your recent PRs),   IIRC is the shear number of chunks that need fetching, more than the size of the data, that causes problems.  Do you see a lot of DynamoDB throttling? You could consider:

proactively prefetching month-ago historic chunks on queries in the background
When I get round to doing the TSDB work the average chunk size will increase significantly (and should always hit max chunk age), which should massively reduce the number of chunks fetched.
Parallelising chunk fetches across multiple parallel workers, and have them stream deduped series back to the querier.

Alternatively, instead of putting this kind of deduping and processing on the write path, you could instead do it as a separate process which reads back data and rewrites it asynchronously, taking it off the critical path.  The original design doc included a mention of this IIRC.

Index queries can be several seconds each. The data for one bucket for one index all comes from one hash key, so I'm not sure more provisioning helps - just fetching 100,000 data items takes time. Even filtering them takes 1-2 seconds.
In many cases that number can be reduced with better query formation; I have added some thoughts to #209. This was another thought that came to me.
I am working on many fronts; the PRs you see are just the parts that are ready now.

To clarify, "what does that look like over the last month" is a 30-day query not an hour-long query.
But an hour-long query in the past is also slower, because we read to the end of the bucket.

Since we're on the subject, #209 says " don't range query to end of row, but use max chunk length to query to end of query + 12hrs"; what is that "+ 12hrs" for?

Index queries can be several seconds each. The data for one bucket for one index all comes from one hash key, so I'm not sure more provisioning helps - just fetching 100,000 data items takes time. Even filtering them takes 1-2 seconds.

Indeed; indirection through a "time series" index would massively improve that, as the labels index would only contain the cardinality of the labels, not cardinality x number of chunks.

In many cases that number can be reduced with better query formation; I have added some thoughts to #209. This was another thought that came to me.

Yes! Even better, you could track and pick low cardinality indexes and only read them; you can always under read the index and over read chunks, and filter later.  Thats if the index is slower than the chunks of course.

To clarify, "what does that look like over the last month" is a 30-day query not an hour-long query.

Ah I see.  How slow?
Another idea is to pipeline index and chunk fetches, so we can start fetching chunks earlier.  Thats a fair bit of work mind you.

Since we're on the subject, #209 says " don't range query to end of row, but use max chunk length to query to end of query + 12hrs"; what is that "+ 12hrs" for?

12hrs is max chunk age

#875 now writes out (label:value) -> []seriesID and seriesID -> []chunkID indexes, which reduces the size of the index by 6-12x over the (label:value) -> []chunkID indexes of old - 3x due to replication and 4x due to average chunk size of 6hrs vs 24hrs index window.
We don't dedupe chunks yet, but this should massively reduce size of index.

Given #875 is merged, can this be closed?

The original point hasn't changed - if the chunk you're about to write is already in the store then you would benefit from not re-writing it.
Querying the disk store wasn't a good idea, but querying memcache should work better.
You have very different usage patterns if you see an "average chunk size of 6hrs".  2 hours is more like what we see as an overall average, but if you are scraping a cluster where containers start and stop a lot then the average goes down.  Chunks with just a few minutes of data are ideal candidates for de-duping, because they will have identical start and end times on all replicas.

Just noticed this:

DynamoDB - reads seem to be 1/5th the cost

From current US East pricing:
Write capacity unit (WCU)  $0.00065 per WCU
Read capacity unit (RCU)  $0.00013 per RCU
But, "DynamoDB charges one WCU for each write per second (up to 1 KB) [...] and one-half of an RCU for each eventually consistent read per second (up to 4 KB)."
So there is another factor of 2-8 in there, depending on data size.
Reads are at least 1/10th the cost of writes.

Closed by #1578 and #1475

authors: bboreham jml tomwilkie

repo: weaveworks/cortex


text:
Restore -dynamodb.*-table.start as a deprecated flag

Fixes #478

Sorry about that!  Totally my bad.  Feel free to revert #463, or merge this.  LGTM

authors: leth tomwilkie


text:
Add dynamoQueryPagesCount metric

Metric for the number of pages we see per query inside QueryPages.
Test plan: rate(cortex_dynamo_query_pages_count_sum[1m]) / rate(cortex_dynamo_query_pages_count_count[1m]) locally shows average page size of 1 which is expected.

@aaron7 whilst this is a useful bit of instrumentation, if your dev-test loop include getting something reviewed and merged into master you're gonna have a bad time.   You should experiment with a custom built query service, deploy is straight to your dev environment (as a separate service perhaps) and then fire queries at it useing the socks proxy.  Then you'll be able to iterate and get to a solution much faster.

@aaron7 whilst this is a useful bit of instrumentation, if your dev-test loop include getting something reviewed and merged into master you're gonna have a bad time. You should experiment with a custom built query service, deploy is straight to your dev environment (as a separate service perhaps) and then fire queries at it useing the socks proxy. Then you'll be able to iterate and get to a solution much faster.

Agreed. I will look into setting up a way to deploy dev environments from local branches.

Let me know if you need a hand.


text:
Fix (Flux)HelmRelease cluster lookups

Fixes #2011 (Introduced in https://github.com/weaveworks/flux/pull/1111)
The value obtained by _, value := range slice is overwritten on every iteration. Thus, saving a pointer to value is dangerous since its content will be overwritten in the next iteration.
From https://golang.org/ref/spec#For_range :

For each entry it assigns iteration values to corresponding
iteration variables if present and then executes the block.

But the iteration variables are the same on each iteration.
More explicitly, from the gccgo source code:
  // The loop we generate:
  //   len_temp := len(range)
  //   range_temp := range
  //   for index_temp = 0; index_temp < len_temp; index_temp++ {
  //           value_temp = range_temp[index_temp]
  //           index = index_temp
  //           value = value_temp
  //           original body
  //   }

Fix looks good to go to me (and looking for this must have been fun).

It didn't take that long, I had a similar problem in #1848 and went directly to the loop.

I am now wondering if we do this in other places though, guess it is a matter of time before we find out.

I checked the other resources and are ok. I wonder if go vet and friends check this kind of stuff (it's similar to  the loopclosure check).

I agree that using the address of a loopvar is often going to lead to problems. Can you explain what was the problem in this specific case? It looks to me like the makeWorkload procedures don't hold on to the pointer, they just extract what they need from it before returning -- so presumably the intent was to avoid passing a large struct by value (and the safest fix would be to pass them by value).

Can you explain what was the problem in this specific case?

Ah, the intermediate workload struct has an embedded field, and that holds on to the pointer. Ugh

Looks like this did not fix the issue described in #2011. Output from fluxctl build fresh from current master:
$ fluxctl list-workloads
WORKLOAD                               CONTAINER           IMAGE                               RELEASE  POLICY
<snip>
default:helmrelease/faulty2
default:helmrelease/faulty2
$ kubectl get helmrelease
NAME      AGE
faulty    5d21h
faulty2   5d19h

Interesting, I did test the fix and fluxctl list-worloads fixed the issue. @hiddeco can you double-check?

Ah, the intermediate workload struct has an embedded field, and that holds on to the pointer. Ugh

Exactly, I should had explained that instead of elaborating on why you should save a pointer to a loop variable.

I had a look at some git blame and this is the only change I thought might be relevant: https://github.com/2opremio/flux/commit/abe9db8febf88e926350c78099e852fe52e0c943#diff-18f3f72b1b5287be3ecab6e5884622b3R191 (but even so, I think it's actually OK).

@2opremio see below
❯ which fluxctl
/home/hidde/go/bin/fluxctl

~/go/src/github.com/weaveworks/flux master
❯ rm -rf /home/hidde/go/bin/fluxctl

~/go/src/github.com/weaveworks/flux master
❯ make clean realclean
go clean
rm -rf ./build
rm -f test/bin/kubectl test/bin/helm
rm -rf ./cache

~/go/src/github.com/weaveworks/flux master
❯ which fluxctl
fluxctl not found

~/go/src/github.com/weaveworks/flux master
❯ git pull
Already up to date.

~/go/src/github.com/weaveworks/flux master
❯ make
go install ./cmd/fluxctl
<snip>

~/go/src/github.com/weaveworks/flux master
❯ fluxctl list-workloads
WORKLOAD                               CONTAINER           IMAGE                               RELEASE  POLICY
default:helmrelease/faulty2
default:helmrelease/faulty2

~/go/src/github.com/weaveworks/flux master
❯ kubectl get hr
NAME      AGE
faulty    5d21h
faulty2   5d19h

@hiddeco can you triple-check that you are running the image from master?

@2opremio err, crap, you are right, my image was fixed on something else. Nevermind.

No worries, it happens. Thanks for checking the fox works!

@hiddeco unfortunately this bug is not fixed. I have again a list of helmReleases called helmRelease/redis when I do fluxctl list-workloads
Flux version 1.12.2
Helm operator 0.9.1

authors: 2opremio hiddeco jan-schumacher squaremo

repo: weaveworks/flux


text:
Take new screenshot that includes window chrome for readme

I think it might look nicer with some sort of border; perhaps the browser window will be enough?
Also, centre align it pls.

The current one is pulled from the official website. I added a version with window to the new website, waiting for it to be launched.

This was fixed in https://github.com/weaveworks/scope/commit/bd245384ef0db14141c79986027b0e80020eb00c

authors: davkal tomwilkie

repo: weaveworks/scope


text:
Enable eBPF tracking by default

Fixes #2441
We already had an integration test for the proc fallback (313), so I just adjusted the ebpf flag according to its default value and changed tests explicitly testing ebpf-tracking to explicitly test tracking without ebpf.

@alban PTAL (ignore the netlify error)


text:
Create a README

Short description
As a user of WeGO I want to read the README so that I can understand what weave-gitops is and get started.
Acceptance criteria

[ ] Explains what wego is
[ ] Explains why I might want to use it
[ ] How to install / get started (ideally in <5 mins using an existing cluster)
[ ] How to build
[ ] How to interact with the community
[ ] Code of Conduct
[ ] Where to find out more

@pzfreo How does this differ from the docs site?

Add contributor license agreement

authors: jpellizzari pzfreo

repo: weaveworks/weave-gitops


text:
Make collections/filters support empty lists

I would like to be able to do this:
filter = wvc.query.Filter.by_property("degree_programs").equal([])
if degrees:
    filter = filter | wvc.query.Filter.by_property("degree_programs").contains_any(val=degrees)

to query chunks with no elements in the "degree_programs" property (general documents) and, optionally, chunks about one of the specified degree programs. However, the first part of this filter causes an error:
  File "/Users/michael/PycharmProjects/TUM_MGT_Chatbot/.venv/lib/python3.12/site-packages/weaviate/collections/filters.py", line 141, in __filter_to_int_list
    if not isinstance(value, list) or not isinstance(value[0], int):
                                                     ~~~~~^^^
IndexError: list index out of range

It seems that weaviate/collections/filters.py assumes (in several places) that any filter list will be non-empty. In my opinion this is not a reasonable assumption.

Hi Michael, this should be fixed by the latest 4.5.1 release. LMK if it doesn't otherwise I will close this issue 😁

Oh I see. That's very helpful, thank you!

No problem! I think we can improve the error handling for an empty list here rather than having an index out of range error so I will open an issue to cover that

repo: weaviate/weaviate-python-client


text:
Reflect updated Web Animations API?

The spec for the Web Animations API has been updated on March 13th, 2015: https://w3c.github.io/web-animations/ - items include simplification and the moving of AnimationGroup and AnimationSequence (now GroupEffect and SequenceEffect) to Level 2.
Will you guys reflect on these API changes or still be based on the old version of the spec?

We'll be making the changes in the near future. There will be a deprecation period where both sets of names work.

This is resolved as of the 2.0.0 release.

authors: davidkpiano dstockwell samthor

repo: web-animations/web-animations-js


text:
[Feature]: update swc to 1.5.11

What problem does this feature solve?
Since SWC@1.5.8, it fix(es/minifier): Abort array property inliner if the array is used as a ref.
I think this fix the following error.
You can change the SWC version to 1.5.8 below to see the error.
What does the proposed API of configuration look like?
none

I believe we already updated, try version 0.7.0-canary-4bcc530-20240528063409

authors: JSerFeng dribble-njr

repo: web-infra-dev/rspack


text:
feat(rspack): add ignoreWarnings option

Close #2979

[x] add ignoreWarnings option in rspack options schema
[x] add  compilation.hooks.processWarnings
[x] create ignoreWarnings plugin
[x] activate the plugin when the user enter ignoreWarnings option

Known Limitations

eslint warnings get passed to the plugin as one error so with ignoreWarnings you got all eslint warnings or not

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@ahabhgk i updated the inline snapshot in defaults.unittest, am I missing anything else?

authors: CLAassistant nagy-nabil


text:
Add the <data> element

There's a discrepancy between the versions for api.HTMLDataElement and html.elements.data that probably needs to be fixed in the BCD

The Edge version will be ≤18 after https://github.com/web-platform-dx/web-features/pull/1398 and indeed we need to fix this in BCD. Just trusting the API data is probably OK for something this new, and given that the element has an attribute. (For elements without any attributes, not giving them their own interface has very little impact, and has probably happened much more often.)

I've sent https://github.com/mdn/browser-compat-data/pull/23830. If you'd like to use compute_from to get the right versions with a TODO pointing to https://github.com/mdn/browser-compat-data/pull/23830, that's OK.

I've sent mdn/browser-compat-data#23830. If you'd like to use compute_from to get the right versions with a TODO pointing to mdn/browser-compat-data#23830, that's OK.

I'm OK to leave it here and wait for that to land.

@foolip & @ddbeck - the test is failing on this one because of an invalid date, looking at the dist file, I see an odd date...
baseline_low_date: ≤2018-10-02

@petele ranges in versions and dates are a result of https://github.com/web-platform-dx/web-features/pull/1398. Can you rebase and then run npm run dist again to get it all in order?

@foolip - done.

authors: foolip petele

repo: web-platform-dx/web-features


text:
Fix initialization for H2 and introduce enum of supported DBs

fixes issue with missing username and password for H2. The H2 works even without username/password being properly set, unless there is another datasource trying to connect to the same schema. Setting it on H2 XA DataSource instance works.
introduces enum of supported DB providers. The goal is to simplify checking for particular DBs and fail fast if there is a DB we haven't ever tested with.

Gonna hook it to https://ci.modcluster.io/job/narayana-tomcat/ in a mo...

Looks good !

@rmaucher there might be additional refactoring coming - provided it's worth the effort. The idea is to split the different behaviour of various DB from the logic creating the Pooling DataSource itself. E.g. the underlying XA DataSource creation could be delegated to the DatabaseProvider enum. WDYT?
But we may do it in a separate PR to avoid blocking merging of this one.

Ok, that's not a bad idea either.

authors: Karm rmaucher rsynek

repo: web-servers/narayana-tomcat


text:
Fixes and improvements for the chain switcher component

[x]  Should show an error
[x]  The component needs clear boundaries.
[x]  Remove URLs from the list items.
[x]  Remove connectable via
[x]  Make the network name larger
[x]  Add clear boundaries between list items (like Anyswap)
[x]  Add radio buttons for "live", "test", "dev"

As a user, I can click to view all "live" chains and see only "live" production chains.
As a user, I can click "test" and see only the available testnet chains.
Should be improved for an 'all' or deselect.

[ ]  Live should be default

Default is test,

[x]  If you're on a "live"/"test"/"dev" chain already then it should show you those options
[ ]  Search bar for filtering, which also respects the radio buttons
[x]  Clicking outside of modal should close modal

Pictures of changes to the chain switcher:

repo: webb-tools/webb-dapp


text:
Page Features and Mixer inti

This PR covers those changes

Prevent showing the page if the chain is not supported, Thus underlying components shouldn't be called if the features aren't met.
Initializing the mixer, and storing, consuming an old mixer will be on another PR

Looks good but I get this when I run it!

authors: AhmedKorim drewstone


text:
Guidance on evaluating shard count/size, WebDataset length

Trying to optimize TPU pod slice solution discussed in https://github.com/webdataset/webdataset/issues/47
Assuming scenario where you need to replicate training with epochs i.e., declare length of dataset, distribute equal samples/batches to nodes...
(1) What is length actually doing to the Webdataset dataset or data loading? And how should it be calculated
(a) My original understanding was this was the total number of samples for a particular worker in an epoch, calculated like this:

length={SHARD_SAMPLES} * {SHARDS_PER_WORKER}

(b) Then in older docs I saw length=num_batches:

num_batches = dataset_size // (batch_size * world_size)

Is the difference between these two recommendations whether you use .batched(batch_size) on the WebDataset? e.g., if using .batched() then calculate with (b)?

(2) Would calculation to length change if using both:

.batched(batch_size, partial=True) on dataset
torch.utils.data.DataLoader(dataset, batch_size=None, shuffle=False, drop_last=False, num_workers=num_workers)

Recently realized I've actually been calculating length by the sample as well as batching:

num_dataset_instances = xm.xrt_world_size() * FLAGS.num_workers (256=32*8)
epoch_size = trainsize // num_dataset_instances (5000=1280000//256)
.batched(batch_size, partial=True)

(3) Any guidance or more thought around deciding optimal number of shards and size of shards (samples and/or bytes)?

e.g., for ImageNet
I suspect one constraint for shard count is that it needs to be divisible by num_workers * world_size
At some point, as the # of shards increases/approaches # of samples, advantages of sharding decrease
Lower # of shards = large files, could be impractical for large datasets
If we do lowest shard count divisible by num_workers * world_size:

we make minimum storage requests, get more Sequential, able to parallel read/process, and distribute to accelerator
But this means the shards are gong to be large (especially when working with +TBs)
Is this decision also related to memory/network constraints?

(2) For a dataset of length N, calling batch with batchsize B returns a new iterable of length equal to N/B. If your DataLoader's batch_size is non-zero, then it will return batches of batches. I believe that's why it is recommended batching in the Dataset rather than in a Dataloader.

As far as WebDataset is concerned, the length does not matter, anywhere. WebDataset just iterates through data sources until it reaches the end and then raises a StopIteration. You can set it to whatever your framework requires.
All the constraints on actual length and nominal length come from whatever framewrk you are using for training, and from the need to have the same number of batches across all nodes participating in DistributedDataParallel while at the same time training exactly by epoch.
So, if you just want an easy way of training, do this:
dataset = WebDataset(...).repeat().decode(...).to_tuple(...).batched(1024)
loader = WebLoader(dataset, ...)

for i, batch in loader:
    if i%10000 == 0:
        run_validation_step()
    ... train on batch ...

No need to ever deal with lengths, partial batches, etc.  This works regardless of the number of training nodes you use. You can also use resampling rather than iteration:
dataset = WebDataset(..., shardlist=ResampledShards).repeat().decode(...).to_tuple(...).batched(1024)

If your framework requires epochs, you can do the following:
dataset = WebDataset(...).repeat().decode(...).to_tuple(...).batched(1024)
loader = WebLoader(dataset, ...).repeat(nbatches=10000)

for epoch in range(nepochs):
    for i, batch in loader:
        ... train on batch ...
    run_validation_step()

If you really must have absolutely, perfectly exact epochs, the default will work fine for single node training:
dataset = WebDataset(...).decode(...).to_tuple(...).batched(1024)
loader = WebLoader(dataset, ...)

for epoch in range(nepochs):
    for i, batch in loader:
        ... train on batch ...
    run_validation_step()

You can't do exact epoch training for multinode training using DistributedDataParallel by only changing the I/O pipeline. The closest that any I/O pipeline can get you is via padding and truncating. This does require you to specify the number of batches after which things should get truncated.
dataset = WebDataset(...).decode(...).to_tuple(...).batched(1024)
loader = WebLoader(dataset, ...).ddp_equalize(dataset_size // batch_size)

for epoch in range(nepochs):
    for i, batch in loader:
        ... train on batch ...
    run_validation_step()

So, in short, set the length to whatever you like.
I'm going to try to document this better and clean up some of the DDP-related options.

As far as WebDataset is concerned, the length does not matter, anywhere. WebDataset just iterates through data sources until it reaches the end and then raises a StopIteration. You can set it to whatever your framework requires.
All the constraints on actual length and nominal length come from whatever framewrk you are using for training, and from the need to have the same number of batches across all nodes participating in DistributedDataParallel while at the same time training exactly by epoch.
So, if you just want an easy way of training, do this:
dataset = WebDataset(...).repeat().decode(...).to_tuple(...).batched(1024)
loader = WebLoader(dataset, ...)

for i, batch in loader:
    if i%10000 == 0:
        run_validation_step()
    ... train on batch ...

No need to ever deal with lengths, partial batches, etc. This works regardless of the number of training nodes you use. You can also use resampling rather than iteration:
dataset = WebDataset(..., shardlist=ResampledShards).repeat().decode(...).to_tuple(...).batched(1024)

If your framework requires epochs, you can do the following:
dataset = WebDataset(...).repeat().decode(...).to_tuple(...).batched(1024)
loader = WebLoader(dataset, ...).with_epoch(10000)

for epoch in range(nepochs):
    for i, batch in loader:
        ... train on batch ...
    run_validation_step()

If you really must have absolutely, perfectly exact epochs, the default will work fine for single node training:
dataset = WebDataset(...).decode(...).to_tuple(...).batched(1024)
loader = WebLoader(dataset, ...)

for epoch in range(nepochs):
    for i, batch in loader:
        ... train on batch ...
    run_validation_step()

You can't do exact epoch training for multinode training using DistributedDataParallel by only changing the I/O pipeline. The closest that any I/O pipeline can get you is via padding and truncating. This does require you to specify the number of batches after which things should get truncated.
dataset = WebDataset(...).decode(...).to_tuple(...).batched(1024)
loader = WebLoader(dataset, ...).ddp_equalize(dataset_size // batch_size)

for epoch in range(nepochs):
    for i, batch in loader:
        ... train on batch ...
    run_validation_step()

So, in short, set the length to whatever you like.
I'm going to try to document this better and clean up some of the DDP-related options.

So, suppose I have 1 node 2 gpus for distributed training in DDP mode, the following example will automatically assign the non-overlapped data slice for the corresponding GPU ?
And, I can set dataset_size as a random number, like 123456, and it will ignore this setup ?
( because we can not get the real dataset_size in webdataset, it's "iterator dataset".
dataset = WebDataset(...).decode(...).to_tuple(...).batched(1024)

# I can set dataset_size as a random number, like 123456 ?
loader = WebLoader(dataset, ...).ddp_equalize(dataset_size // batch_size)

for epoch in range(nepochs):
    for i, batch in loader:
        ... train on batch ...
    run_validation_step()

You are not repeating your training data infinitely, so this won't work.
If you want exactly one permutation of the training data per epoch and you want this distributed equally across the GPUs, you should use the wids portion of the WebDataset library; it emulates an indexed dataset perfectly and works with the multinode-related code in the PyTorch DataLoader.
https://github.com/webdataset/webdataset/blob/main/examples/train-resnet50-multiray-wds.ipynb
If you don't care about one permutation of the training data per epoch (and there is no reason you should; it does not result in better models), you just use WebDataset(..., resampled=True). In that case, just use with_epoch of whatever you find convenient, or get rid of epochs altogether, since they serve no purpose anymore.
ddp_equalize was an attempt to work around PyTorch's limited support for distributed training with IterableDataset. It kind of works, but it is never quite exact and is not recommended anymore.

You are not repeating your training data infinitely, so this won't work.
If you want exactly one permutation of the training data per epoch and you want this distributed equally across the GPUs, you should use the wids portion of the WebDataset library; it emulates an indexed dataset perfectly and works with the multinode-related code in the PyTorch DataLoader.
https://github.com/webdataset/webdataset/blob/main/examples/train-resnet50-multiray-wds.ipynb
If you don't care about one permutation of the training data per epoch (and there is no reason you should; it does not result in better models), you just use WebDataset(..., resampled=True). In that case, just use with_epoch of whatever you find convenient, or get rid of epochs altogether, since they serve no purpose anymore.
ddp_equalize was an attempt to work around PyTorch's limited support for distributed training with IterableDataset. It kind of works, but it is never quite exact and is not recommended anymore.

I think we'll take this good advice. Currently, we apply resampled=True and with_epoch. thanks for your reply.

authors: HuangChiEn mynameisvinn tmbdev tottenjordan

repo: webdataset/webdataset


text:
coffeetea

title: Issue #

Discord Username: @
What type of PR is this? (select all that apply)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 🚧 Breaking Change
[ ] 🧑💻 Code Refactor
[ ] 📝 Documentation Update

Description

Related Tickets & Documents

Related Issue #
Closes #

QA Instructions, Screenshots, Recordings

UI accessibility concerns?

Added/updated tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

[optional] Are there any post deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

export-pinetwormcmiranda-1710079871.csv.gz

repo: webdevcody/code-racer


text:
Build Errors

Running into this error when I try to build the project
 Linting and checking validity of types  ... ⨯ ESLint: Failed to load config "@repo/eslint-config/next.js" to extend from. Referenced from: C:\Users\smlsc\projects\next-drizzle-lucia-sqlite-template\.eslintrc.js
   Linting and checking validity of types  ..Failed to compile.

.next/types/app/api/login/google/callback/route.ts:8:13
Type error: Type 'OmitWithTag<typeof import("C:/Users/smlsc/projects/next-drizzle-lucia-sqlite-template/src/app/api/login/google/callback/route"), "dynamic" | "config" | "generateStaticParams" | "revalidate" | ... 11 more ... | "PATCH", "">' does not satisfy the constraint '{ [x: string]: never; }'.
  Property 'setSession' is incompatible with index signature.
    Type '(userId: number) => Promise<void>' is not assignable to type 'never'.

   6 |
   7 | // Check that the entry is a valid entry
>  8 | checkFields<Diff<{
     |             ^
   9 |   GET?: Function
  10 |   HEAD?: Function
  11 |   OPTIONS?: Function
error: script "build" exited with code 1

this should be fixed now

authors: SamuelSackey webdevcody


text:
Add unit tests

+ integration with travis/codeclimate (see wdio-sync)

done in the v5 repo

repo: webdriverio/wdio-sauce-service


text:
19 - 切换焦点指令

// 你的答案
<script setup lang="ts">
import { ref, Ref } from 'vue';

const state = ref(true);

/**
 * Implement the custom directive
 * Make sure the input element focuses/blurs when the 'state' is toggled
 *
 */

const VFocus = {
  mounted(el: any, binding: { value: any }, vnode: any, prevVnode: any) {
    const input = el;
    const res: Ref<any> = ref(binding.value);
    if (res.value) {
      input.focus();
    }
  },
  updated(el: any, binding: { value: any }, vnode: any, prevVnode: any) {
    const input: HTMLInputElement = el;
    const res: Ref<any> = ref(binding.value);
    if (res.value) {
      input.focus();
    } else {
      input.blur();
    }
  },
};

setInterval(() => {
  state.value = !state.value;
}, 2000);
</script>

<template>
  <input v-focus="state" type="text" />
</template>

为什么可以触发updated.

updated

是因为vnode里面包含了state这个状态？

repo: webfansplz/vuejs-challenges


text:
Default port

I'd recommend the default port to be set other than 8888, so it won't conflict with the default WebGME port.

I think it might be nice to maintain consistency with the webgme project. If the user is running multiple webgme instances, he/she can just uncomment the example from the default config

authors: brollb hakantunc

repo: webgme/webgme-setup-tool


text:
Add the style transfer example

https://github.com/webmachinelearning/webnn/issues/108

We're considering using newer models, @huningxin, @BruceDai, following's the comparison list of FNS Candy Style Transfer from different orgs, PTAL which is more appropriate for this example.

Fast Neural Style Transfer
Candy
Candy
Candy

Org
ONNX model zoo
ONNX model zoo
microsoft/Windows-Machine-Learning

OpSet Version
8
9
N/A

Input
float32[1,3,224,224]
float32[1,3,224,224]
float32[None,3,720,720]

Missing Ops in Spec
Upsample
Shape,   Gather, Cast, Unsqueeze, Upsample
Crop,   Affine

uploaded time
10 months ago
10 months ago
3   years ago

Size
6.6M
6.6M
1.64M

Note:   ONNX Upsample is replaced with Resize.
BTW, one more dependency is that some existing ops on Spec have not been implemented in webnn-polyfill yet. Relevant issue: https://github.com/webmachinelearning/webnn-polyfill/issues/34

After discussion, we decide to use ONNX model zoo's style transfer models with opSet version 9.

Thanks @Honry for your investigation and looking forward to your code contribution.
@anssiko , I added Wanming as collaborator so Wanming can be assignee of this issue.

@Honry thanks for looking into these new models, your contributions are much welcome.

Missing Ops in Spec	Upsample

Unsample/Resize can be mapped to resample op.

When testing the fast style transfer model of ONNX model zoo, there are couple of issues of webnn-polyfill/tf.js:

For WebGL backend, the last conv2d with input [1, 32, 904, 904] and filter [3, 32, 9, 9] would hit the WebGL maximum texture size restriction:

uncaught (in promise) Error: Requested texture size [22808x22809] greater than WebGL maximum on this browser / GPU [16384x16384].

For Wasm backend, the tf.mirrorPad and tf.image.resizeNearestNeighbor are not supported.

@huningxin, with Acer models, I still got error for WebGL backend:

uncaught (in promise) Error: Requested texture size [19467x19468] greater than WebGL maximum on this browser / GPU [16384x16384].

@huningxin, with Acer models, I still got error for WebGL backend:

uncaught (in promise) Error: Requested texture size [19467x19468] greater than WebGL maximum on this browser / GPU [16384x16384].

Sorry, it's my bad, there's a typo in my code, it works now.

authors: Honry anssiko huningxin

repo: webmachinelearning/webnn-samples


text:
ReferenceError: name is not defined

URL: https://extent.network/user-space/user-space.html
Crash when trying to run site in Exokit to emulate VR.
Running:
Ubuntu 18.04
Exokit 0.0.452
URL: https://extent.network/user-space/user-space.html
$ exokit https://extent.network/user-space/user-space.html
THREE.WebGLRenderer 95
ReferenceError: name is not defined
    at requestUsers (server-connection.js:45:52)
    at update (user-space.js:97:5)
    at onAnimationFrame (js/three.js:22685:36)
    at onAnimationFrame (js/three.js:7424:4)
    at tickAnimationFrame (/usr/local/lib/exokit/core.js:691:9)
    at Timeout._recurse [as _onTimeout] (/usr/local/lib/exokit/index.js:1359:12)
    at ontimeout (timers.js:427:11)
    at tryOnTimeout (timers.js:289:5)
    at listOnTimeout (timers.js:252:5)
    at Timer.processTimers (timers.js:212:10)
Bugsnag:  Encountered an uncaught error, terminating…
ReferenceError: name is not defined
    at requestUsers (server-connection.js:45:52)
    at update (user-space.js:97:5)
    at onAnimationFrame (js/three.js:22685:36)
    at onAnimationFrame (js/three.js:7424:4)
    at tickAnimationFrame (/usr/local/lib/exokit/core.js:691:9)
    at Timeout._recurse [as _onTimeout] (/usr/local/lib/exokit/index.js:1359:12)
    at ontimeout (timers.js:427:11)
    at tryOnTimeout (timers.js:289:5)
    at listOnTimeout (timers.js:252:5)
    at Timer.processTimers (timers.js:212:10)

thanks for bringing that up. :D
problem with the app, not exokit though.

Yeah this looks like a site issue. However, we probably shouldn't be crashing if the tick throws.
I think for cases like this we should catch from user code and default to a log but chug on, like Chrome/Firefox would.

Does not all user code already catch? What's missing?

I think the requestAnimationFrame callbacks aren't under a try-catch wrap: https://github.com/webmixedreality/exokit/blob/a2a647d686dd45c8271f942ed6ced5e17ab50d83/core.js#L679
This won't cause a server termination due to process.on('uncaughtException'), but it probably would unwind the mainloop.
I think the solution might be to wrap the raf callbacks in a try-catch-warn and keep going.

authors: chrislatorres cmdrflexo modulesio ngokevin

repo: webmixedreality/exokit


text:
Add inArray, and make oneOf an alias of it

We use the Assert library at Mollie a lot and are really happy with it. 👍
However, one thing frustrates us: the naming of oneOf is simply not intuitive.
We often write Assert:: in PhpStorm and use the automatic method completion to find the assert we are looking for. Since we don't use oneOf on a daily basis, we easily forget what it's called. Many of our engineers look for something like inArray or arrayHasValue and can't find it, and then have to dive into the assert library to remember what the method name was for the assertion that performs an in_array().
We suggest adding inArray as an alias of oneOf to restore predictability in naming, and by extension make the Assert library more intuitive to use.

Thanks for this PR, colleagues of mine have ran into the same issue before 😅 .
Currently this needs a few things, which are also indicated by the tests, namely:

a nullOrInArray in the doc comment
a allInArry in the doc comment
a section in the readme

Personally i'd be okay with even deprecating oneOf in favor of inArray, but i'd leave it like this for right now.
If you need any help feel free to leave a comment here or message me on twitter.

Happy to hear the alias is a welcome addition @BackEndTea! I made the requested changes to the PR.

authors: BackEndTea mollierobbert

repo: webmozart/assert


text:
CSS loads if not on App component

I have version 2.1.0 installed and just experienced this issue after updating.
The problem is if I do an import '../styles/App.css' on the App component. The CSS is not picked up. If I include the CSS elsewhere on ComponentX the CSS gets picked up.
It's a weird problem and an annoying one. Below is my webpack.config.js
Any ideas?
module.exports = {
  entry: {
      bundle: './src/index.js',
      vendor: VENDOR_LIBS
  },
  output: {
    path: path.join(__dirname, 'public/build'),
    filename: '[name].[chunkhash].js'
  },
  module: {
      rules: [
          {
              use: 'babel-loader',
              test: /\.js$/,
              exclude: /node_modules/
          },
          {
              test: /\.css$/i,
              use: ExtractTextPlugin.extract({
                  fallback: 'style-loader',
                  use: 'css-loader'
              })
          }
      ]
  },
  devServer: {
      contentBase: path.join(__dirname, 'public'),
      historyApiFallback: true
  },
  plugins: [
    new ExtractTextPlugin({
        filename: 'style.css',
        allChunks: true
    }),
    new webpack.optimize.CommonsChunkPlugin({
      name: ['vendor', 'manifest'],
    }),
    new HtmlWebpackPlugin({
        template: 'src/index.html'
    }),
    new webpack.DefinePlugin({
      'process.env.NODE_ENV' : JSON.stringify(process.env.NODE_ENV)
    }),
    new WebpackShellPlugin({
        onBuildExit: [
            `./postbuild.sh`
        ],
    })
  ]
};

It was a react-router v4 routing issue.

Hello. I think I'm getting the same error.
Would you mind explaining how you solved it?
Thanks

The problem was that I was using react-router v3 code on a react-router v4 dependency.
Since the App component was not even loading, the CSS import was not loading. When I migrated my react-router v3 code to react-router v4 everything worked again. So this means you might have to rewrite or merge the App component with your routes (to keep a similar structure as v3, but you can also put routes anywhere following v4 philosophy), so it can load the CSS import.
Check their docs here:
https://reacttraining.com/react-router/web/example/basic
the react-router lib changes its API a lot from one release to another, so these issues are very common as far as I know - I just didn't expect it to be a entire rewrite of react-router on v4.

authors: pbreah phlorie


text:
Unexpected: "ERROR in  doesn't export content"

When running ./node_modules/webpack/bin/webpack.js --watch, an error shows up in the terminal after changing a CSS file ("ERROR in  doesn't export content"), and the webpack compilation seems to run twice.
The high-level setup is as follows: two entry points, one (OneEntry.js) does a synchronous require of Dep.js, and the other (TwoEntry.js) does a require.ensure of Dep.js. Dep.js requires Dep.css. Changing Dep.css while running with --watch triggers the error message.
The final output doesn't seem to be affected (at least in my simple example here), but it's still a scary message. I started to step through it with node-debug, but didn't get much farther than figuring out where the error was coming from -- line 156 of extract-text-webpack-plugin/index.js. I'll probably look at it at little further tomorrow.
My webpack.config.js:
var ExtractTextPlugin = require("extract-text-webpack-plugin");

module.exports = {
    target: "web",
    debug: true,
    // devtool: "source-map",
    entry: {
        One: './OneEntry.js',
        Two: './TwoEntry.js'
    },
    output: {
        path: "./target",
        filename: "[name].bundle.js"
    },
    module: {
        loaders: [
            { test: /\.css$/, loader: ExtractTextPlugin.extract("style-loader", "css-loader") },
        ]
    },
    plugins: [
        new ExtractTextPlugin("[name].styles.css")
    ]
};

OneEntry.js
require('./Dep.js');

module.exports = function () {
    console.log("OneEntry");
}

TwoEntry.js
module.exports = function () {
    require.ensure([], function (require) {
        var One = require('./Dep.js');
    });
}

Dep.js
require('./Dep.css');

module.exports = function helloWorld() {
    console.log("Hello, World!");
}

Dep.css
body {
    font-weight: normal;
}

Console output:
[10:30:58] extract-text-plugin-bug-repro$ ./node_modules/webpack/bin/webpack.js --watch
Hash: 1af67a17d8cdba702d4f
Version: webpack 1.4.13
Time: 123ms
         Asset  Size  Chunks             Chunk Names
 Two.bundle.js  3850       0  [emitted]  Two
 1.1.bundle.js   332       1  [emitted]
 One.bundle.js  1886    2, 1  [emitted]  One
One.styles.css    32    2, 1  [emitted]  One
   [0] ./OneEntry.js 81 {2} [built]
   [0] ./TwoEntry.js 113 {0} [built]
   [1] ./Dep.js 103 {1} {2} [built]
    + 4 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Hash: 33291634f4065e501d4e
Version: webpack 1.4.13
Time: 24ms
         Asset  Size  Chunks             Chunk Names
 1.1.bundle.js   332       1  [emitted]
 One.bundle.js  1886    2, 1  [emitted]  One
One.styles.css    30    2, 1  [emitted]  One
    + 7 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Hash: 2ed4f9458139cfb59089
Version: webpack 1.4.13
Time: 8ms
         Asset  Size  Chunks             Chunk Names
 1.1.bundle.js  1253       1  [emitted]
 One.bundle.js  2807    2, 1  [emitted]  One
One.styles.css    30    2, 1  [emitted]  One
    + 7 hidden modules

ERROR in /path/extract-text-plugin-bug-repro/node_modules/extract-text-webpack-plugin/loader.js?{"omit":1,"extract":true,"remove":true}!/path/extract-text-plugin-bug-repro/node_modules/style-loader/index.js!/path/extract-text-plugin-bug-repro/node_modules/css-loader/index.js!/path/extract-text-plugin-bug-repro/Dep.css doesn't export content

Updating title to reflect that we actually see this error in non-watch mode as well. We have a little hack that seems to fix the issue, but I'm not 100% sure it's the "right" fix.

The original issue posted here said that the output wasn't affected, but it actually does seem to be affected some percentage of the time, which I think increases the severity of the bug.
After some debugging, I made a simple change that seems to fix the issue for us (the error messages go away, and it's been weeks since we had any corrupted output). I'm not entirely sure that the fix is correct -- there might be a better way to accomplish what I did, but I'm hoping someone more familiar with the code than me will take a quick look and be able to tell one way or the other.
Any help/guidance on this would be much appreciated.
Commit: https://github.com/roblg/extract-text-webpack-plugin/commit/413f55bd8c953dd0b4109b501d026add5e11a6d8

hmm ok I get the issue... If a module is in multiple chunks it is built multiple times in parallel (propably with different intents (one want to extract it, the other not)...

Got this issue, too.
It's not rare that one module being used in multiple places(pages). If it is sync-required (style supposed to be extracted out) in one page while async-required (supposed not to be extracted) in another page, error shows up. Actually error only shows up while watching. If built directly (not watching), no error shows up while the module's style will not be packaged in the async-required chunk.
Hope to know if this will be fixed soon. Thx!

Seems this is the same problem.

I had difficulty applying @roblg's patch to the current codebase. With some tinkering, I was able to kind of sort of get it to work, but it broke hot reload.
Looking a little further into it, it seems like the problem is that the loader declares that its results are cacheable, and then the plugin mutates the results from the loader. When I commented out the two lines in loader that look like this:
if (this.cacheable) this.cacheable();

everything seemed to work fine, including hot reload. I'm not sure if that will cause any other problems, but it seems relatively safe to me. I'll make a PR.

Any updates or work-around for this bug? I had to disable the extract-text plugin for the time being in development (watch) mode and add some conditionals to the application, but I'm afraid bad things might happen in production only since I use a different set-up for the development mode :(

@rosenfeld we ended up following @aickin's advice and making the plugin output non-cacheable.
He had a clever workaround to extend ExtractTextPlugin to fix the behavior -- no funky build-time step needed:
var ExtractTextLoader = require("extract-text-webpack-plugin/loader");

// we're going to patch the extract text loader at runtime, forcing it to stop caching
// the caching causes bug #49, which leads to "contains no content" bugs. This is
// risky with new version of ExtractTextPlugin, as it has to know a lot about the implementation.

module.exports = function(source) {
	this.cacheable = false;
	return ExtractTextLoader.call(this, source);
}

module.exports.pitch = function(request) {
	this.cacheable = false;
	return ExtractTextLoader.pitch.call(this, request);
}

(borrowed from: https://github.com/aickin/react-server/blob/master/packages/react-server-cli/src/NonCachingExtractTextLoader.js; no idea if that link will work forever)

I tried commenting the cacheable line before commenting in this thread and could confirm it worked, but on the other side it got much slower to update the output when the source changes, so I'm not sure whether it's better to disable caching for that plugin or to disable the plugin in watch mode... :(

@roblg, I'm curious. How do you combine this loader with other loaders? The documentation talks about using the extract method and inform the other loaders (style, css and sass in my case). I don't know how to combine this loader class with other loaders...

Nevermind, got it to work already.

https://github.com/webpack/extract-text-webpack-plugin/pull/169

I'm experiencing this issue with --watch periodically now too.

+1, require.ensure problem?

Here's a proposed fix following @aickin's suggestion that allows an isCacheable flag to be passed into the options. It worked for our implementation but we'd prefer not to fork and patch the plugin: #251

Have same issue after upgrading webpack (from v2.2.0-rc.1 to v2.2.0-rc.2).
Can it be related to https://github.com/webpack/webpack/issues/3498 ?

I was having same issue (latest webpack and extract-text-plugin), the workaround to disable cache did not work for me. Making this change in .../node_modules/extract-text-webpack-plugin/index.js did the trick
if(shouldExtract !== wasExtracted) {
to
if(shouldExtract && !wasExtracted) {
issue in my case was that it was trying to recompile when shouldextract was false and wasExtracted was true
Also it looks like in my case, aside from having a named entry including same css as an async chunk, this issue was only happening for me when my webpack config had two instances of new ExtractTextPlugin(...) in the plugins[]

I'm also having this problem, but in my case this doesn't export content error is happening in watch mode. Initially the compilation runs fine, but when I do a change to code the watch reload will fail with the error message. What is more interesting is that, when I do a second change, then everything compiles nicely again. So every second reload fails. Doing the fix, @dalimian proposed, fixed this error for me.

what's about PR merging?

Is anyone still experiencing this with 3.0.0 ? @dalimian suggestion fixes the issue for me

@kostasmanionis yes still experiencing it. Only when I run rimraf (yarn clean) though. Still looking into it.

authors: Crazymax11 JulianJorgensen aickin andreechristian dalimian hequ kostasmanionis missyjcat mnpenner nighca nktssh roblg rosenfeld sokra thebigredgeek

repo: webpack/extract-text-webpack-plugin