text:
Change input/output channel

Hi Xintao,
I currently study GAN to help super-resolution task.
I do some transform of LR and HR image before feeding in the network. (modify LRHR_dataset.py)
However, I need to do the inverse transform to the SR image, so where can I modify the code to do the inverse transform to the network output?
More specifically, my input channel is now 12 not 3.

So you want the network output has 12 channels?
If so, you can modify the corresponding network strucutre, https://github.com/xinntao/BasicSR/blob/master/codes/models/modules/architecture.py

Thanks for answer, I have already modified the network structure.
However, in validation, I don't know where to conduct the transform so it is still 3-channel input.(Or if I modify LRHR_dataset.py, it will also do the transform on the validation dataset?)
And where can I modify the code to do the inverse transform to the network output? (Now the output is 12 channel and I need to do inverse transform to change the number of channel back to 3)

@BeepBump

the validation transformation can also be done in  LRHR_dataset.py. Maybe you only perform the transformation in the training phase. May need to check it.
After obtaining the 12-channel outputs, you can do the inverse transform in the xxx_model.py file,
for example, you can change it in the train and test phase by modifying the following functions.
https://github.com/xinntao/BasicSR/blob/36984e8bb1cd4269397bb15361a4221d26d4235a/codes/models/SR_model.py#L66-L80

Really appreciate about ur reply. Now, I can train SRResNet.
However, for SRGAN, it need the pretrain model for VGG net.
Does it no matter for changing the number of channel in reading pretrain SRResNet?

authors: BeepBump xinntao

repo: xinntao/BasicSR


text:
Does this network support exr file input？

Does this network support exr file input？

I am not familiar with exr files. But I think you can modify the data loader to support exr files. After reading it, the network processes them in float precision.

source: gharchive/issue

authors: qingfengmingyue xinntao

license_type: permissive

license_source: github-api


text:
【建议】希望 Markdown 的超链接语法支持新标签页打开

这个种标准格式只能当前页打开连接：
[当前页超连接](http://www.example.com)
希望增加新标签页打开链接的语法：
[新标签页超链接](tab:http://www.example.com)

参考文档：Markdown cheatsheet | ᕕ( ᐛ )ᕗ Herman's blog

已更新

太棒了！谢谢^_^

应该的

authors: SMWHff xioyito

repo: xioyito/NewBee

license: MIT


text:
Extract BD-Rate per clip using the BD-Rate

Things to do

[ ] Make as a main function and have the arg parser comments inside, so we can call bd-rate standalone
[ ] Passing clip name for computing BD-Rate

If we isolate the main function and import bdrate from the bd_rate_report.py
and run
bdrate('/home/mindfreeze/awcy/runs/av1-test-vimeo-single-acbr-s8-2021-06-17_122019-4fb45ab04/vimeo-corpus-10s-single/ffmpeg.y4m-daala.out',        '/home/mindfreeze/awcy/runs/av1-directopt-vimeo-single-acbr-s9-1.3-2021-06-19_154934-4fb45ab04/vimeo-corpus-10s-single/ffmpeg.y4m-daala.out', None, True)
We do get the metrics

repo: xiph/awcy


text:
rav1e crashes with assertion failed while encoding from ffmpeg

Describe the bug
When encoding a long video with ffmpeg using librav1e codec, rav1e will crash after a long time of encoding with this message:
thread '<unnamed>' panicked at 'assertion failed: MV_LOW <= comp && comp <= MV_UPP', src/context/mod.rs:191:5
note: run with \`RUST_BACKTRACE=1\` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
Abgebrochen

To Reproduce
On my machine, the crash is fully reproducible with this one particular video (not with others) when running the following command:
ffmpeg -i 2021-12-19\ 02-12-30.mkv -c:v librav1e -qp 130 -c:a libopus -b:a 128K -f matroska '2021-12-19 02-12-30 Starbase More Zone 3 Mining AV1 qp 130.mkv'
Unfortunately, reproducing it takes several weeks.
Expected behavior
ffmpeg and rav1e should encode the video fully until the end without crashing.
Required Information
Toolchain (if is a build problem):
$ cargo --version
cargo 1.58.0
$ rustc --version
rustc 1.58.1 (gentoo)
$ nasm --version # if on x86_64
ASM version 2.15.05 compiled on Oct  8 2020

Version:
$ rav1e --version
rav1e 0.5.1 (0.5.1) (release)

Operating system:
$ uname -a
Linux adams 5.15.23-gentoo #1 SMP Thu Feb 17 13:56:52 CET 2022 x86_64 AMD Ryzen 3 4300GE with Radeon Graphics AuthenticAMD GNU/Linux

Console Output
Please paste the console output below if it is relevant,

Full console output:
$ time ffmpeg -i 2021-12-19\ 02-12-30.mkv -c:v librav1e -qp 130 -c:a libopus -b:a 128K -f matroska '2021-12-19 02-12-30 Starbase More Zone 3 Mining AV1 qp 130.mkv'
ffmpeg version 4.4.1 Copyright (c) 2000-2021 the FFmpeg developers
  built with gcc 11.2.1 (Gentoo 11.2.1_p20220115 p4) 20220115
  configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --docdir=/usr/share/doc/ffmpeg-4.4.1-r3/html --mandir=/usr/share/man --enable-shared --cc=x86_64-pc-linux-gnu-gcc --cxx=x86_64-pc-linux-gnu-g++ --ar=x86_64-pc-linux-gnu-ar --nm=x86_64-pc-linux-gnu-nm --strip=x86_64-pc-linux-gnu-strip --ranlib=x86_64-pc-linux-gnu-ranlib --pkg-config=x86_64-pc-linux-gnu-pkg-config --optflags='-march=native -O2 -pipe' --extra-libs= --disable-static --enable-avfilter --enable-avresample --disable-stripping --disable-optimizations --disable-libcelt --enable-nonfree --disable-indev=v4l2 --disable-outdev=v4l2 --disable-indev=oss --disable-indev=jack --disable-indev=sndio --disable-outdev=oss --disable-outdev=sndio --enable-bzlib --disable-runtime-cpudetect --disable-debug --disable-gcrypt --enable-gnutls --disable-gmp --enable-gpl --disable-hardcoded-tables --enable-iconv --disable-libxml2 --disable-lzma --enable-network --disable-opencl --enable-openssl --enable-postproc --disable-libsmbclient --enable-ffplay --enable-sdl2 --enable-vaapi --disable-vdpau --disable-vulkan --enable-xlib --enable-libxcb --enable-libxcb-shm --enable-libxcb-xfixes --enable-zlib --disable-libcdio --disable-libiec61883 --disable-libdc1394 --disable-libcaca --disable-openal --enable-opengl --disable-libv4l2 --enable-libpulse --disable-libdrm --disable-libjack --disable-libopencore-amrwb --disable-libopencore-amrnb --disable-libcodec2 --enable-libdav1d --disable-libfdk-aac --disable-libopenjpeg --disable-libbluray --disable-libgme --disable-libgsm --disable-libaribb24 --disable-mmal --disable-libmodplug --enable-libopus --disable-libilbc --disable-librtmp --disable-libssh --disable-libspeex --disable-libsrt --enable-librsvg --disable-ffnvcodec --enable-libvorbis --enable-libvpx --disable-libzvbi --disable-appkit --disable-libbs2b --disable-chromaprint --disable-cuda-llvm --disable-libflite --disable-frei0r --disable-libvmaf --disable-libfribidi --disable-fontconfig --disable-ladspa --disable-libass --disable-libtesseract --disable-lv2 --enable-libfreetype --disable-libvidstab --disable-librubberband --disable-libzmq --disable-libzimg --disable-libsoxr --enable-pthreads --disable-libvo-amrwbenc --enable-libmp3lame --disable-libkvazaar --enable-libaom --disable-libopenh264 --enable-librav1e --disable-libsnappy --disable-libsvtav1 --disable-libtheora --disable-libtwolame --disable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --disable-amf --disable-gnutls --disable-armv5te --disable-armv6 --disable-armv6t2 --disable-neon --disable-vfp --disable-vfpv3 --disable-armv8 --disable-mipsdsp --disable-mipsdspr2 --disable-mipsfpu --disable-altivec --disable-vsx --disable-power8 --disable-amd3dnow --disable-amd3dnowext --disable-aesni --disable-avx --disable-avx2 --disable-fma3 --disable-fma4 --disable-sse3 --disable-ssse3 --disable-sse4 --disable-sse42 --disable-xop --cpu=host --disable-doc --disable-htmlpages --enable-manpages
  libavutil      56. 70.100 / 56. 70.100
  libavcodec     58.134.100 / 58.134.100
  libavformat    58. 76.100 / 58. 76.100
  libavdevice    58. 13.100 / 58. 13.100
  libavfilter     7.110.100 /  7.110.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  9.100 /  5.  9.100
  libswresample   3.  9.100 /  3.  9.100
  libpostproc    55.  9.100 / 55.  9.100
Input #0, matroska,webm, from '2021-12-19 02-12-30.mkv':
  Metadata:
    ENCODER         : Lavf58.29.100
  Duration: 04:15:28.75, start: 0.000000, bitrate: 6333 kb/s
  Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 2560x1440 [SAR 1:1 DAR 16:9], 60 fps, 60 tbr, 1k tbn, 120 tbc (default)
    Metadata:
      DURATION        : 04:15:28.750000000
  Stream #0:1: Audio: aac (LC), 48000 Hz, stereo, fltp (default)
    Metadata:
      title           : Track1
      DURATION        : 04:15:28.725000000
  Stream #0:2: Audio: aac (LC), 48000 Hz, stereo, fltp (default)
    Metadata:
      title           : Track2
      DURATION        : 04:15:28.725000000
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> av1 (librav1e))
  Stream #0:1 -> #0:1 (aac (native) -> opus (libopus))
Press [q] to stop, [?] for help
Output #0, matroska, to '2021-12-19 02-12-30 Starbase More Zone 3 Mining AV1 qp 130.mkv':
  Metadata:
    encoder         : Lavf58.76.100
  Stream #0:0: Video: av1 (AV01 / 0x31305641), yuv420p(tv, bt709, progressive), 2560x1440 [SAR 1:1 DAR 16:9], q=2-31, 60 fps, 1k tbn (default)
    Metadata:
      DURATION        : 04:15:28.750000000
      encoder         : Lavc58.134.100 librav1e
  Stream #0:1: Audio: opus ([255][255][255][255] / 0xFFFFFFFF), 48000 Hz, stereo, flt, 128 kb/s (default)
    Metadata:
      title           : Track1
      DURATION        : 04:15:28.725000000
      encoder         : Lavc58.134.100 libopus
thread '<unnamed>' panicked at 'assertion failed: MV_LOW <= comp && comp <= MV_UPP', src/context/mod.rs:191:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
Abgebrochen

real    24025m26,343s
user    23746m12,683s
sys     62m38,480s

Hi,
Thanks for the bug-report, will it be possible to share the sample ?

Hi, Thanks for the bug-report, will it be possible to share the sample ?

I am currently uploading a version of the video with audio removed (for privacy reasons). I don't know how I would go about sharing just a sample, mostly because I have no idea what part of the original video causes the problem to surface.

Hi, Thanks for the bug-report, will it be possible to share the sample ?

The sample (11GiB) can be downloaded from here:
https://unknownsite.de/recordings/rav1e_crashing_video_without_sound.mkv
For privacy reasons, I stripped the audio with this command:
ffmpeg -i 2021-12-19\ 02-12-30.mkv -map 0:0 -c:v copy rav1e_crashing_video_without_sound.mkv
I hope this won't make a difference for the bug, but since the video stream was copied with -c:v copy, it shouldn't.

authors: guidow vibhoothi

license_source: bigquery


text:
Make the debug printing of Plane more useful

Also make PlaneSlice derive Debug.

Coverage increased (+0.7%) to 81.835% when pulling 43e7025fb5af37562dc017ef0f21863eabea38d1 on smarter:make-debug into 27427d0cff06d95ebe3c5f376107cb366c3a9dba on xiph:master.

source: gharchive/pull-request

authors: coveralls smarter


text:
Error: Could not find kaggle.json

Hi,
I can't run backend. The command flask run -p 8000 failed with the error:
OSError: Could not find kaggle.json. Make sure it's located in /Users/XXX/.kaggle. Or use the environment method.
Do I have to create a Kaggle account to use OpenAgents?
Traceback (most recent call last):
  File "/Users/XXX/miniconda3/bin/flask", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/flask/cli.py", line 1063, in main
    cli.main()
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/click/decorators.py", line 92, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/flask/cli.py", line 911, in run_command
    raise e from None
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/flask/cli.py", line 897, in run_command
    app = info.load_app()
          ^^^^^^^^^^^^^^^
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/flask/cli.py", line 308, in load_app
    app = locate_app(import_name, name)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/flask/cli.py", line 218, in locate_app
    __import__(module_name)
  File "/Users/XXX/path/OpenAgents/backend/__init__.py", line 4, in <module>
    from backend.api import (
  File "/Users/XXX/path/OpenAgents/backend/api/chat_copilot.py", line 5, in <module>
    from backend.api.file import _get_file_path_from_node
  File "/Users/XXX/path/OpenAgents/backend/api/file.py", line 8, in <module>
    from backend.main import (
  File "/Users/XXX/path/OpenAgents/backend/main.py", line 6, in <module>
    from backend.kernel_publisher import start_kernel_publisher
  File "/Users/XXX/path/OpenAgents/backend/kernel_publisher.py", line 4, in <module>
    from backend.utils.utils import logger
  File "/Users/XXX/path/OpenAgents/backend/utils/utils.py", line 21, in <module>
    from real_agents.data_agent import (
  File "/Users/XXX/path/OpenAgents/real_agents/data_agent/__init__.py", line 10, in <module>
    from real_agents.data_agent.executors.kaggle_data_loading_executor import KaggleDataLoadingExecutor
  File "/Users/XXX/path/OpenAgents/real_agents/data_agent/executors/kaggle_data_loading_executor.py", line 10, in <module>
    from kaggle.api.kaggle_api_extended import KaggleApi
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/kaggle/__init__.py", line 23, in <module>
    api.authenticate()
  File "/Users/XXX/miniconda3/lib/python3.11/site-packages/kaggle/api/kaggle_api_extended.py", line 403, in authenticate
    raise IOError('Could not find {}. Make sure it\'s located in'
OSError: Could not find kaggle.json. Make sure it's located in /Users/XXX/.kaggle. Or use the environment method.

When you sign up to Kaggle and request an API key, you will receive a json file. Can you try putting it in the specified folder?

Agree, and we mentioned that in the guidance, we will further work on make installation easier

authors: Enogh Timothyxxx alena-m

repo: xlang-ai/OpenAgents


text:
Change font size whilst running?

Maybe a hotkey to increase and decrease the size?

Although this might be technically possible, since fzf have some kind of key binding options (I am not sure actually), but this is not a necessary feature for font preview.
My thought is, we can adjust the font size through command line arguments. Once the font size is suitable, it never needs changing during the program running, since the preview text and font size are pre-defined already.

authors: mxmilkiib xlucn

repo: xlucn/fontpreview-ueberzug


text:
Build failing

Currenty build fails due to some ngc errors:
https://travis-ci.org/xmaestro/angular2-recaptcha
When I rollback to angular 2.4.1 everything works fine. I think this is something wrong with 2.1.4 version of typescript in combination with angular 4.
This issue stopped me from making a pull request because I can't use repo without compiling files.

Build has been fixed and Angular version has been updated.

authors: mateuszkrzak xmaestro

license: isc


text:
port pkgconfig to xmake

port pkgconfig to xmake and enable on windows

Before adding new features and new modules, please go to issues to submit the relevant feature description first.
Write good commit messages and use the same coding conventions as the rest of the project.
Please commit code to dev branch and we will merge into master branch in feature
Ensure your edited codes with four spaces instead of TAB.

增加新特性和新模块之前，请先到issues提交相关特性说明，经过讨论评估确认后，再进行相应的代码提交，避免做无用工作。
编写友好可读的提交信息，并使用与工程代码相同的代码规范，代码请用4个空格字符代替tab缩进。
请提交代码到dev分支，如果通过，我们会在特定时间合并到master分支上。
为了规范化提交日志的格式，commit消息，不要用中文，请用英文描述。

这个为什么要去 port ？ 之前的不行？

这个为什么要去 port ？ 之前的不行？

适配Windows系统，有的cmake配置需要pkg-config

这个为什么要去 port ？ 之前的不行？

适配Windows系统，有的cmake配置需要pkg-config

没必要，windows 下用 pkgconf 包，toosl.meson/cmake 内部默认支持，直接 add_deps("pkgconf") 加上就行了。。
参考 https://github.com/xmake-io/xmake-repo/blob/2db2831f1d85a17b8ed22132ccddb8cfab5ba147/packages/f/freetype/xmake.lua#L49
你强行 port pkg-config ，即使编译通过，代码上也不一定很好的在 windows 上 work 。。

authors: jingkaimori waruqi

repo: xmake-io/xmake-repo


text:
xmake模块编译错误

Xmake 版本
v2.6.6
操作系统版本和架构
windows 11 22000.708
描述问题
该版本无法支持c++20模块新特性的编译，但它的上一个版本可以正常工作
期待的结果
正常生成可执行文件
工程配置
set_languages("c++20")
target("main")
set_kind("binary")
add_files(".cpp",".ixx")
附加信息和错误日志
[ 16%]: ccache compiling.release a.ixx
error: @programdir\core\main.lua:280: @programdir\actions\build\main.lua:166: ...mdir\core\sandbox\modules\import\core\base\scheduler.lua:96: ...mdir\core\sandbox\modules\import\core\base\scheduler.lua:56: @programdir\modules\private\async\runjobs.lua:256: @programdir\core\tool\compiler.lua:282: bad argument #-1 to 'args' (string expected, got nil)
stack traceback:
[C]: in function 'args'
[@programdir\core\tool\compiler.lua:282]: in function 'compcmd'
[@programdir\modules\private\action\build\object.lua:79]: in function 'script'
[@programdir\modules\private\action\build\object.lua:98]: in function 'build_object'
[@programdir\rules\c++\modules\build_modules\msvc.lua:136]: in function 'jobfunc'
[@programdir\modules\private\async\runjobs.lua:232]:
stack traceback:
[C]: in function 'error'
@programdir\core\base\os.lua:872: in function 'os.raiselevel'
(...tail calls...)
@programdir\modules\private\async\runjobs.lua:256: in field 'catch'
@programdir\core\sandbox\modules\try.lua:127: in global 'try'
@programdir\modules\private\async\runjobs.lua:218: in upvalue 'cotask'
@programdir\core\base\scheduler.lua:388: in function <@programdir\core\base\scheduler.lua:385>
stack traceback:
@programdir\core\base\utils.lua:290: in function <@programdir\core\base\utils.lua:280>
[C]: in function 'error'
@programdir\core\base\os.lua:872: in function 'os.raiselevel'
(...tail calls...)
...mdir\core\sandbox\modules\import\core\base\scheduler.lua:56: in field 'co_start_withopt'
@programdir\modules\private\async\runjobs.lua:217: in function <@programdir\modules\private\async\runjobs.lua:162>
[C]: in function 'xpcall'
@programdir\core\base\utils.lua:280: in function 'base/utils.trycall'
@programdir\core\base\scheduler.lua:504: in function 'base/scheduler.co_group_begin'
...mdir\core\sandbox\modules\import\core\base\scheduler.lua:94: in field 'co_group_begin'
@programdir\modules\private\async\runjobs.lua:162: in function <@programdir\modules\private\async\runjobs.lua:56>
(...tail calls...)
@programdir\actions\build\build.lua:252: in function <@programdir\actions\build\build.lua:240>
(...tail calls...)
@programdir\actions\build\main.lua:103: in global '_do_build'
@programdir\actions\build\main.lua:150: in function <@programdir\actions\build\main.lua:144>
[C]: in function 'xpcall'
@programdir\core\base\utils.lua:280: in function 'base/utils.trycall'
@programdir\core\sandbox\modules\try.lua:121: in global 'try'
@programdir\actions\build\main.lua:142: in function <@programdir\actions\build\main.lua:108>
(...tail calls...)
[C]: in function 'xpcall'
@programdir\core\base\utils.lua:280: in function 'base/utils.trycall'
(...tail calls...)
@programdir\core\base\task.lua:519: in function 'base/task.run'
@programdir\core\main.lua:278: in upvalue 'cotask'
@programdir\core\base\scheduler.lua:388: in function <@programdir\core\base\scheduler.lua:385>
stack traceback:
[C]: in function 'error'
@programdir\core\base\os.lua:872: in function 'os.raiselevel'
(...tail calls...)
@programdir\core\main.lua:280: in upvalue 'cotask'
@programdir\core\base\scheduler.lua:388: in function <@programdir\core\base\scheduler.lua:385>

更新到 dev 在试下。。xmake update -s dev

更新到 dev后，xmake正常工作了

repo: xmake-io/xmake


text:
xmake do not detect the llvm toolchain

Xmake Version
xmake v2.6.8+HEAD.e18471251
Operating System Version and Architecture
Windows 10 19044
Describe Bug
xmake do not find my llvm toolchain, even if installed.
$ xmake config --toolchain=llvm --sdk="C:\\Users\\gberthiaume\\scoop\\apps\\llvm\\current\\bin" -v
checking for platform ... windows
checking for architecture ... x64
error: llvm toolchain not found!

As you can see here, the llvm toolchain is correctly installed.

Expected Behavior
xmake  would find llvm
Project Configuration
target("testing-xmake-project")
    set_kind("binary")
    add_files("src/*.c")

Additional Information and Error Logs
checking for platform ... windows
checking for architecture ... x64
error: @programdir\core\main.lua:280: @programdir\core\tool\toolchain.lua:263: @programdir\toolchains\llvm\check.lua:90: llvm toolchain not found!
stack traceback:
    [C]: in function 'error'
    [@programdir\core\base\os.lua:872]:
    [@programdir\toolchains\llvm\check.lua:90]:
    [C]: in function 'xpcall'
    [@programdir\core\base\utils.lua:280]:
    [@programdir\core\tool\toolchain.lua:259]: in function 'check'
    [@programdir\core\platform\platform.lua:247]: in function 'check'
    [@programdir\actions\config\main.lua:396]:
    [C]: in function 'xpcall'
    [@programdir\core\base\utils.lua:280]:
    [@programdir\core\base\task.lua:501]: in function 'run'
    [@programdir\core\main.lua:278]: in function 'cotask'
    [@programdir\core\base\scheduler.lua:388]:

stack traceback:
        [C]: in function 'error'
        @programdir\core\base\os.lua:872: in function 'base/os.raiselevel'
        (...tail calls...)
        @programdir\core\main.lua:280: in upvalue 'cotask'
        @programdir\core\base\scheduler.lua:388: in function <@programdir\core\base\scheduler.lua:385>

try
$ xmake f --toolchain=llvm --sdk="C:\\Users\\gberthiaume\\scoop\\apps\\llvm\\current" -cvD

It seems to work.
Thanks for your support and thanks for making xmake. I'm really starting to enjoy it.

authors: g-berthiaume waruqi


text:
xmake更新之后原有工程编译不了

Xmake 版本
2.8.7
操作系统版本和架构
win10
描述问题
貌似把warning当做错误了，只要出现这个warning，后面不管编译什么都当做错误停止

期待的结果
正常编译
工程配置
仓库地址 ： https://gitee.com/openLuat/luatos-soc-air101
附加信息和错误日志
error: gcc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead
..\LuatOS\components\luatfonts\luat_lib_fonts.c:1:0: error: bad value (ck804ef) for -mtune= switch
/*
^

xmake 不会处理 warning 只会判断 gcc 的 exit code ，非 0 就退出。
即使有错，也是 Gcc 报错导致，可以对比前后 flags 的差异

xmake 不会处理 warning 只会判断 gcc 的 exit code ，非 0 就退出。
即使有错，也是 Gcc 报错导致，可以对比前后 flags 的差异

没有差异，工程不变，只更新xmake，2.8.6一切正常

再试下。。xmake update -s dev; xmake f -c

再试下。。xmake update -s dev; xmake f -c

可以了，这个影响应该比较大，下个版本是不是会提前发布

看情况。

更新了。

authors: Dozingfiretruck waruqi


text:
Is Transparent operation possible?

Would it be possible to make the operation of BeefText transparent with respect to the clipboard? i.e. leave the current clipboard contents intact, either by using some separate clipboard, or the simple option of saving the current clipboard, replacing and pasting the text and then restoring the original clipboard? That way anything the user has in the clipboard prior to expanding text isn't erased?

Oh - that's what it does do. I must have messed up my original testing! Thanks

Indeed, Beeftext is restoring the clipboard after use, but there are a few caveats:

In order to work properly there is a delay before the original clipboard content is restored after the combo substitution. Currently, the delay is 1 second.
Beeftext can only restore the clipboard if it contains text, HTML, colors, images or file paths.

repo: xmichelo/Beeftext


text:
X.P.OrgMode: Fix behaviour of getLast

Description
It's funny to notice this so late; I guess non-deterministic tests do have their drawback :)
So far, while parsing strings like "", the getLast
function immediately stopped on strings of the form "".
This may be a bit confusing given the functions name.  Strings of
the—perhaps artificial—form
"a +d f 1 +d f 2"

would be cut short and parsed as
Deadline "a" (Time { date = Next Friday, tod = Just 01:00 })

instead of the more intuitive
Deadline "a +d f 1" (Time { date = Next Friday, tod = Just 02:00 }).

This is readily fixed by applying the go parser as often as possible,
only returning the longest list, and then pruning eventual leftovers at
the end of the string.  Since we were already invoking dropWhileEnd to
trim whitespace before, the added reverses should not impact
performance at all.
Fixes: https://github.com/xmonad/xmonad-contrib/issues/584
λ ⟩ pInput "a +d f 1 +d f 2"
Just (Deadline "a +d f 1" (Time {date = Next Friday, tod = Just 02:00}))

λ ⟩ quickCheck $ prop_decodeLinearity (Deadline "+d" (Time {date = XMonad.Prompt.OrgMode.Next Friday, tod = Nothing}))
+++ OK, passed 1 test.

λ ⟩ quickCheck $ prop_decodeLinearity (Deadline "+d f 1" (Time {date = XMonad.Prompt.OrgMode.Next Friday, tod = Nothing}))
+++ OK, passed 1 test.

Checklist

[x] I've read CONTRIBUTING.md

[x] I've considered how to best test these changes (property, unit,
manually, ...) and concluded: I added some regression tests for the cases that were mentioned in #584

[n/a] I updated the CHANGES.md file
Unreleased module, I don't think this is necessary.

[n/a] I updated the XMonad.Doc.Extending file (if appropriate)

I wanted to merge this today but then life interfered and I'll be afk most of tomorrow as well so please do feel free to rebase --autosquash and merge any time.

authors: liskin slotThe

repo: xmonad/xmonad-contrib


text:
-oU urls.txt flag overwrites the contents of the file if a list of hosts are provided.

when I run waymore -lcc 3 -mode U hosts.txt -oU urls.txt the file urls.txt is overwritten with the urls of the new host that is in the file. The new URLs should be appended. Can you fix this? or am I making a mistake here?

Hi @meispi. The syntax of what you're running doesm't look quite right. You need to pass the hosts.txt with -i. I'm not sure it would actually run with what you said so maybe that isn't exactly what you're using?
So it should be python3 waymore.py -i hosts.txt -mode U -lcc 3 -oU urls.txt for example. It should not overwite the urls.txt file though unless yuou use the -ow argument. If it is still happening, can you send me the actual comman you have used? Thanks

Apologies for the confusion. I did use the flag -i, but somehow missed it while creating this issue.
Command: waymore -lcc 3 -mode U -i hosts.txt -oU urls.txt

You're right, it's overwriting the file and it shouldn't be! I'll look into it and try to get a fix sorted soon. Thanks for taking the time to raise the issue

Hey @meispi, I have just released a new verion that should hopefully fix this issue. Let me know if it resolves your problem.
Many thanks
Xnl

Awesome. Thanmks for raising it


text:
Column name USER_COMMENT causes column parsing to end

Describe the bug
There are 2 issues with parsing the enclosed create table statement in Snowflake.

The 'OR REPLACE' keywords cause the output to be blank.
The column with name 'USER_COMMENT' causes the column parsing to end so the output only includes the first column 'ASIN'.

Also a feature request: Support for constraint and table comment parsing
To Reproduce
create or replace TABLE ASIN.EXCLUSION (
	ASIN VARCHAR(10) NOT NULL,
	USER_COMMENT VARCHAR(100),
	PROCESS_SQN NUMBER(10,0) NOT NULL,
	constraint PK_EXCLUSION primary key (ASIN)
) COMMENT='ASINs to be excluded from the ASIN List File'
;

create TABLE ASIN.EXCLUSION (
	ASIN VARCHAR(10) NOT NULL,
	USER_COMMENT VARCHAR(100),
	PROCESS_SQN NUMBER(10,0) NOT NULL,
	constraint PK_EXCLUSION primary key (ASIN)
) COMMENT='ASINs to be excluded from the ASIN List File'
;

@stanorama thanks for reporting the issue, will work on it soon!

@stanorama  one more time thanks for raising the issue, you help me to find a great bug ) problem was with all strings, that started with 'USE' and 'GO'. So it was really meaning issue. I fixed in 0.26.2 release & added tests - https://github.com/xnuinside/simple-ddl-parser/blob/main/tests/test_snowflake.py#L196. Please use 0.26.2 - already released. If you will find anymore problems - feel free to open new issue, its really helpful

authors: stanorama xnuinside

repo: xnuinside/simple-ddl-parser


text:
🛑 Design Swan is down

In 63aac1a, Design Swan (https://www.designswan.com) was down:

HTTP code: 500
Response time: 111 ms

Resolved: Design Swan is back up in 65f555a.

repo: xoryorz/upptime


text:
🛑 Design Swan is down

In 4c01628, Design Swan (https://www.designswan.com) was down:

HTTP code: 500
Response time: 116 ms

Resolved: Design Swan is back up in 0f0bde0 after 12 minutes.


text:
🛑 Design Swan is down

In a4f839b, Design Swan (https://www.designswan.com) was down:

HTTP code: 500
Response time: 98 ms

Resolved: Design Swan is back up in 4f8171c.


text:
🛑 Design Swan is down

In c338195, Design Swan (https://www.designswan.com) was down:

HTTP code: 500
Response time: 146 ms

Resolved: Design Swan is back up in 1998000 after 21 minutes.


text:
🛑 Design Swan is down

In b95cdb2, Design Swan (https://www.designswan.com) was down:

HTTP code: 500
Response time: 110 ms

Resolved: Design Swan is back up in a542130.


text:
Use GtkPasswordEntry

Gtk has a widget specifically for password entries: GtkPasswordEntry
We could use that for the login screen, which would cut out a bit of custom code.

good point!

shouldn't this be closed?

authors: busterbeam jannuary xou816


text:
initializers

Implement initializers and add coverage.
int c = 4;

This change implements scalar initialisers. We will prioritise and track full implementation of intializers later.


text:
🛑 Xstatic is down

In 7d1a124, Xstatic (https://www.xstatic.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Xstatic is back up in 752d32d after 5 minutes.

repo: xstaticwebdev/upptime


text:
Using via esm leads to acorn import error

Error
In "real" esm you get this error message
import _acorn from "acorn";
       ^^^^^^
SyntaxError: The requested module 'acorn' does not provide an export named 'default'

which is true as acorn only has named exports
// node_modules/acorn/dist/acorn.mjs
export { Node, Parser, Position, SourceLocation, TokContext, Token, TokenType, defaultOptions, getLineInfo, isIdentifierChar, isIdentifierStart, isNewLine, keywords$1 as keywordTypes, lineBreak, lineBreakG, nonASCIIwhitespace, parse, parseExpressionAt, types$1 as tokContexts, types as tokTypes, tokenizer, version };

I assume it keeps working with cjs as it's always an object by default.
Reproduction
I created a reproduction here
https://github.com/daKmoR/acorn-import-assertions-esm-bug
git clone https://github.com/daKmoR/acorn-import-assertions-esm-bug.git
cd acorn-import-assertions-esm-bug
npm i
npm run build

Suggestion
it can probably be solved via
- import _acorn from "acorn";
+ import * as _acorn from "acorn";

in https://github.com/xtuc/acorn-import-assertions/blob/main/src/index.js#L1

Fixed in https://github.com/xtuc/acorn-import-assertions/commit/08ab26b9e2a5bca28f374a8a3e17f0c8c74b8ad0

thxxxx 🙇♂

authors: daKmoR xtuc

repo: xtuc/acorn-import-assertions


text:
Multi-GPU training

Hi, I want train your model on multiple gpus. But I am getting errors. Can you help me in this regard?

Hi @JigneshChowdary
What is the error your are facing?
As I am facing the following error, when running on 4 GPUs however the code work smoothly when using single GPU:
RuntimeError: Unable to find a valid cuDNN algorithm to run convolution
Your help would be much appreciated @xuekt98
Thanks in advance!

Hi @eslambakr
I encountered the same issue when running my code on 4 GPUs. Did you manage to resolve it? Could you please share how you resolved it?
RuntimeError: Unable to find a valid cuDNN algorithm to run convolution
Your help would be much appreciated @xuekt98
Thanks in advance!

maybe the hyper parameters you use is not suitable that the model is too large to run on one GPU. Just try to decrease batch size
---- Replied Message ----
| From | @.> |
| Date | 10/09/2023 10:32 |
| To | @.> |
| Cc | @.>@.> |
| Subject | Re: [xuekt98/BBDM] Multi-GPU training (Issue #14) |
Hi @eslambakr
I encountered the same issue when running my code on 4 GPUs. Did you manage to resolve it? Could you please share how you resolved it?
RuntimeError: Unable to find a valid cuDNN algorithm to run convolution
Your help would be much appreciated @xuekt98
Thanks in advance!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

I want to run on 4GPUs not 1GPU，I meet the question"RuntimeError: Unable to find a valid cuDNN algorithm to run convolution"，Could you please share how you resolved it?
---- Replied Message ----
| From | @.> |
| Date | 10/09/2023 17:54 |
| To | @.> |
| Cc | @.>@.> |
| Subject | Re: [xuekt98/BBDM] Multi-GPU training (Issue #14) |
maybe the hyper parameters you use is not suitable that the model is too large to run on one GPU. Just try to decrease batch size
---- Replied Message ----
| From | @.> |
| Date | 10/09/2023 10:32 |
| To | @.> |
| Cc | @.>@.> |
| Subject | Re: [xuekt98/BBDM] Multi-GPU training (Issue #14) |
Hi @eslambakr
I encountered the same issue when running my code on 4 GPUs. Did you manage to resolve it? Could you please share how you resolved it?
RuntimeError: Unable to find a valid cuDNN algorithm to run convolution
Your help would be much appreciated @xuekt98
Thanks in advance!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Hi @xiaoxiaoyuii
Unfortunately, I didn't solve it, as I don't have enough time to make it.
But I guess it is doable we can convert any code that run one single GPU and make it support distributed training.
Sorry for that.

Hi @xiaoxiaoyuii
i have solved the problem, sometimes, Vram is not enough to run the code. Therefore, to handle this issue you should decrease batch size

authors: JigneshChowdary arminbiglari eslambakr xiaoxiaoyuii xuekt98


text:
当列表中有轮播的时候发生崩溃

在flutter_easy_refresh的demo的NestedScrollViewPage页面加入轮播，发生崩溃。
轮播库：flutter_swiper_view: ^1.1.8
EasyRefresh(
                      header: ClassicHeader(
                        dragText: 'Pull to refresh'.tr,
                        armedText: 'Release ready'.tr,
                        readyText: 'Refreshing...'.tr,
                        processingText: 'Refreshing...'.tr,
                        processedText: 'Succeeded'.tr,
                        noMoreText: 'No more'.tr,
                        failedText: 'Failed'.tr,
                        messageText: 'Last updated at %T'.tr,
                        safeArea: false,
                      ),
                      footer: ClassicFooter(
                        position: IndicatorPosition.locator,
                        dragText: 'Pull to load'.tr,
                        armedText: 'Release ready'.tr,
                        readyText: 'Loading...'.tr,
                        processingText: 'Loading...'.tr,
                        processedText: 'Succeeded'.tr,
                        noMoreText: 'No more'.tr,
                        failedText: 'Failed'.tr,
                        messageText: 'Last updated at %T'.tr,
                      ),
                      child: CustomScrollView(
                        slivers: [
                            SliverToBoxAdapter(
                              child: Container(
                                  padding: const EdgeInsets.symmetric(horizontal: 15),
                                  height: 120,
                                  child: Swiper(
                                    itemBuilder: (context, index) {
                                      return Image.network("https://picsum.photos/200/300?random=$index", fit: BoxFit.fill);
                                    },
                                    itemCount: 3,
                                    indicatorLayout: PageIndicatorLayout.COLOR,
                                    autoplay: true,
                                    pagination: const SwiperPagination(
                                      alignment: Alignment.bottomRight,
                                      margin: EdgeInsets.all(10),
                                      builder: DotSwiperPaginationBuilder(
                                          activeColor: Colors.white38,
                                          color: Colors.transparent,
                                          size: 4.0,
                                          activeSize: 4.0,
                                          space: 3.0),
                                    ),
                                    /// control: const SwiperControl(),
                                    onIndexChanged: (index) {},
                                    onTap: (index) {},
                                  ),
                                ),
                          ),
                          SliverList(
                              delegate:
                                  SliverChildBuilderDelegate((context, index) {
                            return const SkeletonItem();
                          }, childCount: _listCount)),
                          const FooterLocator.sliver(),
                        ],
                      ),

我该怎么解决这个问题？

作用区域的问题，看readme和示例哈

authors: tianxiawoyougood xuelongqy


text:
这个库兼容你们原先提供的同名Framework么？

rt!

不兼容，这个库只处理蓝牙的搜索连接，不包含业务能力，无法独立处理iwown手表的蓝牙协议的内容。

repo: xuezou/BLEMidAutumn


text:
比较的时候  空了  #24908 java.lang.NullPointerException

#24908 java.lang.NullPointerException
Attempt to read from field 'int com.xujiaji.dmlib2.entity.BaseDmEntity.priority' on a null object reference
com.xujiaji.dmlib2.entity.BaseDmEntity.compareTo(BaseDmEntity.java:65)
1 com.xujiaji.dmlib2.entity.BaseDmEntity.compareTo(BaseDmEntity.java:65)
2 com.xujiaji.dmlib2.entity.BaseDmEntity.compareTo(BaseDmEntity.java:30)
3 java.util.PriorityQueue.siftUpComparable(PriorityQueue.java:656)
4 java.util.PriorityQueue.siftUp(PriorityQueue.java:647)
5 java.util.PriorityQueue.offer(PriorityQueue.java:344)
6 java.util.PriorityQueue.add(PriorityQueue.java:321)
7 com.xujiaji.dmlib2.widget.Controller.addToQueue(Controller.java:222)
8 com.xujiaji.dmlib2.widget.Controller$2.run(Controller.java:215)
9 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
10 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
11 java.lang.Thread.run(Thread.java:764)

下载主分支，导入项目试试呢？这个之前修复过

ok

authors: Leavds xujiaji


text:
Remove panic when method not found in the tree

Replaced panic with HandleNotFound in router.go line 257.

Pull Request Test Coverage Report for Build 190

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.7%) to 99.324%

Files with Coverage Reduction
New Missed Lines
%

router.go
2
99.05%

Totals

Change from base Build 183:
-0.7%

Covered Lines:
294

Relevant Lines:
296

💛  - Coveralls

authors: coveralls tadvi

repo: xujiajun/gorouter


text:
slot:form 的方式 proxy 方法无法关联 form 对象

（必填）请填写问题描述 Describe
slot:form 的方式 proxy 方法无法关联 form 对象
（必填）请填写能重现问题的链接，例如（jsfiddle、codesandbox、jsrun） Reproduction link
https://jsrun.net/gc2Kp/edit
请填写报错信息或截图 Error message or screenshots

点击查询后 发现form 没有关联进来 只能手动调用data中的form

此时page 对象有关联到 因为使用的是对象配置的方式 不是使用slot的方式
（必填）请填写版本号 Version

os: win10
browser: chrome
vue: 2.6.11
vxe-table: 2.9.8

没代理表单哪来关联，自定义模板你就用自定义的对象
https://jsrun.net/6c2Kp/edit

没 proxy form 哪来关联，如果自定义模板那就用自定义的对象
https://jsrun.net/6c2Kp/edit

ok 明白了

authors: huoshidehua xuliangzhan

repo: xuliangzhan/vxe-table


text:
This commit fixes 'gofmt', 'golint' and 'govet' issues.

Description of the Change
This PR runs all the Go code through gofmt to ensure recommended Go formatting.
Code has also been run through govet and golint and fixed accordingly.
e.g.

dropping 2nd argument in ranges where not required
removing else blocks where the true condition is a return
removing capitals and punctuation from error messages

Alternate Designs
We could keep things the way they are, but ideally we would write Go code the Go way.
Benefits
Promoting the adoption of standards regardless the language.
Possible Drawbacks
Getting use to lowercase error messages ;)
Verification Process
make test, govet and golint passes.
Applicable Issues
New issue.

Pull Request Test Coverage Report for Build 510

45 of 45 (100.0%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+3.2%) to 100.0%

Totals

Change from base Build 505:
3.2%

Covered Lines:
1009

Relevant Lines:
1009

💛  - Coveralls

Hold off before merge. Need to update pkg first.

This should probably be merged as soon as pkg is ready to merge (or has been merged).  glide.lock does lock in the changes from pkg that is required.

authors: coveralls rheinardkorf

repo: xwp/go-tide


text:
调用mover_curve曲线运动器会报错

【调用代码】

【报错内容】

已修复


text:
Full usage of toast config

I would like to use the Toast config features, so far only "type" is implemented

I have added ToastConfig object. After the v0.3.1 you can use all of the Toast component properties.

authors: DaveHOnCode yagizhanNY

repo: yagizhanNY/siemens-ix-blazor


text:
Process finished with exit code -536870873

Bug Report

I have read:

Usage information
Help information

I am using the latest version of the library.
Expected Behavior
Telegram bot works properly
Actual Behavior
Process finished with exit code -536870873
Steps to reproduce the Behavior
I copied code snippet from main page then made js file, pasted code, apply NTBA_FIX_319 fix and run via node v14.21.1 and process exited unexpectedly

Node 14 looks to old. Use node 18 lts or 16 (end of life now)

repo: yagop/node-telegram-bot-api


text:
Add plugins, stores and controller view doc

@jedireza @Vijar

:ship:

:+1:

authors: Vijar jedireza redonkulus


text:
support adding validation annotation to list of object in query param…

…eter

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:

authors: hankting yahoocla

repo: yahoo/parsec-rdl-gen


text:
Anyway to keep current page when sorting?

Not sure if this is a bug, but if you sort a column on any page other than 1, it resets back to the first page.  Is there anyway to sort the current page without having to go back to page 1?
By the way thank you for this contribution your hard work is much appreciated!

@pixelone , it's the default behavior of datatables. I guess you would have to override the plugin's default to achieve this. Below are some links I found that might help you with this.

https://www.datatables.net/forums/discussion/21001/how-to-keep-current-page-after-sorting
http://stackoverflow.com/questions/23607943/how-to-keep-the-current-page-after-sorting-with-jquery-datatables
https://datatables.net/examples/basic_init/state_save.html
https://www.google.com.ph/webhp?sourceid=chrome-instant&ion=1&espv=2&es_th=1&ie=UTF-8#q=datatables sort on same page&es_th=1

authors: pixelone yajra

repo: yajra/laravel-datatables

license: mit


text:
Order Columns by relational JSON data field

Summary of problem or feature request
First of all this datatables plugin is amazing. I love the service approach. But I ran into a problem with relational data and ordering. I have a JSON field in a relational table I'm trying to get the English title from. Everything works fine, but it's not possible to order the table, because the orderColumn method only searches in fields of the parent table. I'll give you a quick example.
Code snippet of problem
$query = Rating::with(['company' => function($query) {
            $query->select(['id', 'title']);
        }])->select(['ratings.id', 'ratings.company_id']);

$this->datatables
            ->eloquent($query)
            ->orderColumn('company.title', 'company.title->"$.en" $1')
            ->make(true);

This results in Unknown column 'company.title' in 'order clause' because of the select from `ratings` order by company.title->"$.de" In my option the order query should query the relational table(s), too.
@yajra Any idea how to solve this?
System details

Operating System: OSX (Laravel Valet)
PHP Version: 7.0
Laravel Version: v5.3.21
Laravel-Datatables Version: v6.21.1

FYI: I figured out how to solve this! It's pretty simple and doesn't need a orderColumn() method call. Simply adapt the column definition like this:
['data' => 'company.title', 'name' => 'company.title->en', 'title' => 'Company'],
...

And change the eager loading query like this:
$query->select(['id', 'title->en as title']);

And that's it!


text:
Notice: bei unbekannter Domain

Warning	Invalid argument supplied for foreach()
redaxo/src/addons/yrewrite/lib/yrewrite/yrewrite.php
375

Warning	Invalid argument supplied for foreach()
redaxo/src/addons/yrewrite/lib/yrewrite/yrewrite.php
362

Es passiert wenn eine URL einer nicht in yrewrite verwalteten Domain aufgerufen wird.
Lösungsmöglichkeiten / Vorschläge

Notice in REDAXO log erstellen mit aussagekräftiger Meldung
Redirect auf Hauptdomain, wenn Domain nicht in YRewrite erfasst ist
Kann beim Hoster gelöst werden durch eine 301 Umleitung.

Ich empfehle die letzte Option, sie ist am zuverlässigsten und am klarsten, was passiert und warum.

Die Warning sollte nicht kommen, und werde ich beseitigen.
Aktuell sollte es eine 404-Antwort sein, und das würde auch so bleiben.

Antwort ist ein 404 ,  + Die Notice
193.92.XXX - - [06/Dec/2020:09:21:58 +0100] “GET /wp-login.php HTTP/1.0” 404 26815 “-” “Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.1

404 und dazu noch eine leere Seite vielleicht oder eine explizite Fehlermeldung? Einen 404er alleine übersehen wieder Leute, die meinen, sie hätten die Weiterleitung/Domain gerade korrekt konfiguriert. Es sollte der Admin forciert werden zu handeln und entweder eine saubere Weiterleitung beim Hosting einrichten oder die Domain in YRewrite hinterlegen.

Es kommt für den Besucher die Seite nicht gefunden page. Das ist soweit ok @alxndr-w . Nur die Notice im Log könnte entweder eindeutiger sein oder wegfallen.

Es gibt kein denkbares Szenario, in dem man will, dass eine zusätzliche Domain auf eine REDAXO-Installation zeigt und sie nicht von YRewrite verwaltet wird.
Deswegen sollte so eine Konfiguration zu einem gut sichtbaren Feedback für den Entwickler führen. Ein 404er-Status oder eine Info im Log ist das nicht.
Im Sinne einer guten Developer-UX würde ich mir ein klareres Feedback wünschen – bis hin zur Aufforderung.
Wer fälschlicherweise auch die Startseite als Fehlerseite eingestellt hat, wird wohl ebenfalls nichts davon merken.

Die Warning hier kann theoretisch auch bei einer hinterlegten Domain kommen in einem Edge Case, es war nur wahrscheinlicher, dass es über eine nicht existente Domain ging.
Die Warning sollte also an der Stelle auf jeden Fall abgefangen werden, und hat nichts direkt mit eurer Diskussion zu "Aufruf über nicht existente Domain" zu tun.
Aktuell kennt yrewrite die "default"-Domain, die für alle Bereiche greift, die außerhalb der hinterlegten Domains liegen. Und diese default-Domain, also eine nicht hinterlegte, akzeptiert jede Domain, über die die Website aufgerufen wird.
Ich bin auch schon länger am überlegen, ob man die default-Domain abschaffen sollte. Aber das ließe sich nicht in 2.x machen, ich weiß, dass die durchaus genutzt wird. Zum Beispiel muss man aktuell theoretisch gar keine Domain in yrewrite hinterlegen.

@gharlan ja und genau "default" klappt ja nicht

Die Notice müsste seit https://github.com/yakamara/redaxo_yrewrite/commit/07c1b556bd7fa12a37e5d173198abbe9126ac66f schon weg sein. Oder bekommt ihr sie noch?

Mir ist sie seither nicht begegnet.

authors: alxndr-w gharlan skerbis


text:
how to deal with fav.movie ?

{
  "name": {"first": "Tom", "last": "Anderson"},
  "age":37,
  "children": ["Sara","Alex","Jack"],
  "fav.movie": "Deer Hunter",
  "friends": [
    {"first": "Dale", "last": "Murphy", "age": 44, "nets": ["ig", "fb", "tw"]},
    {"first": "Roger", "last": "Craig", "age": 68, "nets": ["fb", "tw"]},
    {"first": "Jane", "last": "Murphy", "age": 47, "nets": ["ig", "tw"]}
  ]
}

how to get fav.movie value ?

Maybe use the bracket syntax ($["fav.movie"]) instead of dotted syntax ?

repo: yalp/jsonpath


text:
Use  in YearPicker documentation

Closes #3730
Description
Fixed the repetition part in the YearPicker documentation to use the For component.
Is this a breaking change (Yes/No):
No

I have removed the For component in cases where using it made the code longer. Please rereview. @koralle

repo: yamada-ui/yamada-ui


text:
Update pvc-snapshot-restore.md

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=ru
Description of changes:

Update apiVersion for VolumeSnapshot (snapshot.storage.k8s.io/v1beta1 is deprecated)

Fix command for creating snapshot (wrong pod name)

Все готово!
Commit: c42017dbbb3edf149b7dd2c9a21b69ccea51e9ac
Проверьте результат: RU.
Check the result: EN.

@ulrihaa, здравствуйте. Спасибо за правки. Забираю.
Напишите, пожалуйста, идентификатор вашего платежного аккаунта, чтобы мы могли начислить вам грант в рамках контент-программы.

Все готово!
Commit: 2ec09e8212ea6716c578fc98b0424d963ba43bd8
Проверьте результат: RU.
Check the result: EN.

@ulrihaa , здравствуйте. Спасибо за правки. Забираю.
Напишите, пожалуйста, идентификатор вашего платежного аккаунта, чтобы мы могли начислить вам грант в рамках контент-программы.

Спасибо!
Я из поддержки ЯО.

authors: ulrihaa vnkiryushkin yfm-team

repo: yandex-cloud/docs


text:
Long period after clickhouse-server restart before client connections accepted

When restarting the clickhouse-server service (v18.14.15 on CentOS 7.5), some nodes in a cluster respond shortly, others can take 10s of minutes or hours beforeaccepting client connections, instead reporting
Code: 210. DB::NetException: Connection refused: (localhost:9000, 127.0.0.1)

I suspect this may be due to a number of merges queued up when service was shut down. The processes are consuming CPU and disk IO to the service does not appear to be hung. Most of the log messages are in the form of
2018.12.04 01:25:41.120131 [ 21 ] {} <Trace> testdb.customer_shard (ReplicatedMergeTreeCleanupThread): Execution took 598 ms.                                                │
2018.12.04 01:25:41.384083 [ 25 ] {} <Trace> testdb.customer_shard (StorageReplicatedMergeTree::mergeSelectingTask): Execution took 735 ms.

It there another indication in the logs that will tell us what the nodes are doing during start up, and is there a way I can diagnose what is causing the long restart cycle?

@blinkov Confirmed it was due to the number of partitions and file count resulting.

repo: yandex/ClickHouse


text:
🛑 Umami is down

In 2748ade, Umami (https://umami.icloudnative.io) was down:

HTTP code: 503
Response time: 1719 ms

Resolved: Umami is back up in 99926be.

repo: yangchuansheng/upptime


text:
🛑 Google is down

In 12e1db9, Google (https://google.icloudnative.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Google is back up in 06025aa after 6 minutes.


text:
Week 4

@yangshun 👋 sorry this was such an unproductive week.

updated 📈


text:
[app/portal][fix] Add tab redirection

Add redirection for navigation items with target: "_blank"

Thanks for fixing this for everyone :)

authors: Vielheim yangshun

repo: yangshun/tech-interview-handbook


text:
在多个页面 tab 点击切换时候，会遇到页面无响应，只能刷新

经过多次实验，是 多个 tab 之间点击时候切换到首页 tab，这时候就会出现页面无响应，我是 yarn dev 时候出现的，这时候也完全没有报错，不知道生产情况会不会这样

解决了，缓存原因。
router 的 index.js里这边noCache改为 true
{
path: '',
component: Layout,
redirect: '/index',
children: [
{
path: '/index',
component: () => import('@/views/index'),
name: 'Index',
meta: {  noCache: true,title: 'home page', icon: 'dashboard', affix: true }
}
]
},


text:
希望可以添加全站搜索和站内搜索

有些资源站侧重点不同 有点注重电影 有的注重电视剧，每次搜索还要手动切换源 ，希望可以添加

在反应一个bug，搜索后切换源，在点搜索没反应必须重新输入才可以点搜索

收到，感谢反馈，bug会近期处理，资源站由于是外部资源，不太可控，所以没有很好的处理方式

另外，不是说不考虑全站搜索，主要是目前可用（资源速度满足可观看要求的）视频源只有一个，因此，搜索出其他资源站的视频，也一直加载缓冲无法观看，所以目前只支持单一视频源也就是站内搜索，如果你有好的视频源，可以分享一下，多个满足要求的视频源是有必要做全站搜索的

authors: HankMo yanjiaxuan

repo: yanjiaxuan/TOMATOX


text:
[Fix] no-array-index-key: catch toString and String() usage

Closes https://github.com/yannickcr/eslint-plugin-react/issues/2140

This looks good, but it seems like any reference to the index should be warned on, not just .toString or String(). Can we have it do that?

This seems a bit tricky to write if I'm trying to explicitly hard code cases to look for. Is there an existing util in the codebase to do this, or something in ESLint? Do we take some sort of recursive algo approach in checking all the nodes arguments and callee.objects etc.?

I don't have a specific suggestion. I'd say that any identifier inside a jsx attribute that matches the index should be flagged?

Codecov Report

Merging #2813 (492b5f1) into master (1b307d3) will decrease coverage by 3.39%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #2813      +/-   ##
==========================================
- Coverage   97.64%   94.24%   -3.40%
==========================================
  Files         121      121
  Lines        8440     8459      +19
  Branches     3033     3048      +15
==========================================
- Hits         8241     7972     -269
- Misses        199      487     +288

Impacted Files
Coverage Δ

lib/rules/no-array-index-key.js
92.68% <100.00%> (+3.25%)
:arrow_up:

lib/util/propTypes.js
67.63% <0.00%> (-29.80%)
:arrow_down:

lib/util/ast.js
69.82% <0.00%> (-26.63%)
:arrow_down:

lib/rules/jsx-no-comment-textnodes.js
88.88% <0.00%> (-11.12%)
:arrow_down:

lib/rules/hook-use-state.js
90.76% <0.00%> (-9.24%)
:arrow_down:

lib/rules/no-unused-state.js
89.41% <0.00%> (-8.63%)
:arrow_down:

lib/rules/boolean-prop-naming.js
91.97% <0.00%> (-7.30%)
:arrow_down:

lib/rules/jsx-props-no-multi-spaces.js
94.11% <0.00%> (-5.89%)
:arrow_down:

lib/rules/jsx-no-literals.js
95.65% <0.00%> (-4.35%)
:arrow_down:

lib/rules/no-unused-prop-types.js
90.00% <0.00%> (-4.00%)
:arrow_down:

... and 8 more

Continue to review full report at Codecov.

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

Sorry forgot about this. If we open another issue I can take a look again once I have some time. But happy to let others take it if they want to

authors: RedTn codecov-commenter ljharb

repo: yannickcr/eslint-plugin-react


text:
[New] Symmetric useState hook variable names

Ensure two symmetrically-named variables are destructured from useState hook calls
Discussion
This is a re-opening of https://github.com/yannickcr/eslint-plugin-react/pull/2873
I've rebased and updated the README using npm run generate-list-of-rules to follow the new table-ish layout.

Supports both useState and React.useState
Tested with TypeScript parser and useState<> type annotation
Robust against weird useState uses like destructuring too many items, or not destructuring at all
Fixable when 2nd destructured arg does not match set<X> naming convention

i would have strongly preferred reopening #2873 instead of leaving it permanently orphaned on the repo forever :-/ please strive to avoid opening unnecessary PRs.

i would have strongly preferred reopening #2873

Same; sorry about the premature close+delete. After I restored the branch, I wasn't able to re-open the PR.
I'll tread more lightly in the future.

What about React.useState calls?

Those are covered in the documentation and in the tests;
https://github.com/yannickcr/eslint-plugin-react/pull/2921/files#diff-21ec40762f2f5ec7df5499db37c5971f0dc3f590927c1f49fddd72b0e103e057R35-R37
    {
      code: 'const [color, setColor] = React.useState()'
    },

I've added some primitive support for ensuring that React / useState is imported (though not necessarily in-scope).
React.useState calls without an imported React are not flagged.
I tried using the ScopeManager to determine at the CallExpression whether React or useState were in scope, but didn't succeed in getting any Scope information at all out of it.
I've never seen a ScopeManager usage in the wild so I may simply have been holding it wrong.

Could we add some tests for useState etc that aren't the hook, and also some tests with a pragma that isn't "React"?

Yeah, I'll take another pass at this.

No, but the ts feature runs on both the old and new TS parsers - it’s fine to add a no-ts-old feature if the old one doesn’t support what’s valid syntax.

Codecov Report

Merging #2921 (c00ac9a) into master (94826da) will decrease coverage by 0.22%.
The diff coverage is 98.30%.

@@            Coverage Diff             @@
##           master    #2921      +/-   ##
==========================================
- Coverage   97.50%   97.27%   -0.23%
==========================================
  Files         119      120       +1
  Lines        8099     8158      +59
  Branches     2888     2922      +34
==========================================
+ Hits         7897     7936      +39
- Misses        202      222      +20

Impacted Files
Coverage Δ

index.js
100.00% <ø> (ø)

lib/rules/hook-use-state.js
98.30% <98.30%> (ø)

lib/rules/no-arrow-function-lifecycle.js
87.93% <0.00%> (-10.35%)
:arrow_down:

lib/rules/no-unused-state.js
94.80% <0.00%> (-3.04%)
:arrow_down:

lib/rules/jsx-curly-spacing.js
91.17% <0.00%> (-2.95%)
:arrow_down:

lib/rules/jsx-props-no-spreading.js
95.65% <0.00%> (-2.18%)
:arrow_down:

lib/util/usedPropTypes.js
97.37% <0.00%> (-0.38%)
:arrow_down:

Continue to review full report at Codecov.

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

Could we add some tests for useState etc that aren't the hook, and also some tests with a pragma that isn't "React"?

Added valid specs where a non-React useState function is invoked.
Added invalid specs where React is imported with an alternative identifier
Added invalid specs where useState is imported with an alternative identifier

I've updated the specs to use the new parsers.all helper, annotating TS-specific tests with the ts feature.
I had to annotate a few cases with no-babel-old, all related to Babel(old)'s failure to recognize a typed, 0-argument useState<T>() expression

I wrapped most test-cases in a little more realistic code; a custom hook that acts as pass-through for the useState return value.
It highlights the problem that I'm able to rename one instance of the variable (within the destructuring assignment) but don't fix other instances of that identifier within the scope.

Are there other hooks that might want naming guidelines? useReducer, for example? If so, i'd rather a single rule to cover both instead of one for each hook.

Seems pretty good overall.

I see there are quite a few CI failures around various node versions, all related to the new shadowed-references code examples I introduced.
In my local testing I had to use the no-default feature in order to avoid the same error while running node 14.17.0, and I expected that same escape hatch would serve for all node versions.
What should my next steps be, if any, in order to address these CI failures?
For now, I'm going to link this in to my day work and see how the rule holds up in day-to-day use on a large codebase.

so like, in this example:
 import React from 'react'
      const React = {
        useState: () => {
          return null
        }
      }

      export default function useColor() {
        const result = React.useState()
      }

that's not valid javascript, because of the repeated identifier in a top-level scope. To fix that, it'd need to be shadowed inside a nested scope - like this:
 import React from 'react'
      const React = {
        useState: () => {
          return null
        }
      }

      export default function useColor() {
        {
        const React = {
          useState: () => {
            return null
          }
        }
        const result = React.useState()
      }
      }

but you basically can't shadow an import at the top level in the first place.

Thanks for the suggestion. I haven't had to deal with shadowing in the wild in a LONG time!
After the implementing the update, I was able to remove the no-default features and it looks like the tests are much happier. :smile:

I found some usages in our codebase where we use only the first member of setState as an ad-hoc memoization.
const [id] = useState(getUniqueElementId())

As it stands, this rule will flag this usage and recommend the following correction
// Now `setId` is unused
// Maybe this is good when you're first writing the code
const [id, setId] = useState(getUniqueElementId())

However, in this case I think the correct change is to directly memoize the value.
// Now id hook-use-state is happy, but useMemo may not be imported
const id = useMemo(() => getUniqueElementId(), [])

Discussion
Should this rule:

do the naive change, and add the setId member
attempt the bigger refactor
something else (ignore, warn-but-not-fix, etc…)

I think it should offer a suggestion to change it to useMemo, but no autofix at all - if someone writes that, we can’t know their intention, so the safe thing to do is force them to manually intervene.
Since you know which AST node imported useState, can the suggestion change that also so it adds useMemo? (one of the no-unused rules can clean up the useState separately, if it becomes unused)

Since you know which AST node imported useState, can the suggestion change that also so it adds useMemo? (one of the no-unused rules can clean up the useState separately, if it becomes unused)

Yep; it shouldn't even be super difficult since with the new Components react-imports tracking, I can tell whether or not useMemo has already been imported.

Are there other hooks that might want naming guidelines? useReducer, for example? If so, i'd rather a single rule to cover both instead of one for each hook.

I certainly use some naming conventions, but in my experience there's nothing as universally-used as this value+setter idiom.
Here are some conventions I use regularly, just as a concrete example of stuff I would enforce with a lint rule. These are simply personal preferences, and I don't feel they represent common practice.

const myRef = useRef() – -Ref suffix makes it easy to remember to use myRef.current when handling this value
const onMyEvent = useCallback(() => … – on- prefix (or handle- prefix, in some projects) makes it easy to spot functions, and to sort callback props together in JSX Components.

Fair - I'm more thinking that if there were ever to be anything in the future, it'd be nicer to add it as an option to a single hook naming rule than to have to make a whole new rule.

Config / Other Hooks
Yes, I tried to consider some real-world cases, and how this rule might accommodate those conventions, but I couldn't come up with anything that was both compelling, and that felt amenable to being expressed here alongside this rule.
One thing I really like about this rule as it stands is zero-configuration.
If naming (or other) conventions emerge around other hooks in the future, adding new rules for those hooks while keeping the config for this one clean seems like a reasonable approach. This code supporting this hook-use-state rule is already pretty complicated!
Use in the Wild
I hooked this rule up to a couple of work repositories; as expected I saw a few usages flagged. Somewhat unexpected was that it didn't crash on anything! (pats self on back)
The automatic variable renaming works, but falls short of a complete refactor. Here's a small example.
https://user-images.githubusercontent.com/7367/145723395-b9e3a66e-ea0b-410a-9890-c2620a602928.mov
This behavior makes me feel that all the fixes should be changed to suggestions, since I can't reliably rename later usages of the variable.
Maybe there's an easy way to do this properly, but if so I feel that rename-this-variable-throughout-the-scope should live in a helper function for other rules to use, and not be implemented as a one-off inside this rule.
Next Steps
Let me know which way you'd like to see this go. If I don't hear anything right away, I'll probably convert the fixes to suggestions, and leave the larger variable-rename-refactor work for another PR.

I agree such a thing would need to be a shared helper, and i agree that they shouldn’t be autofixes if they’re going to leave things in a broken state. Your plan seems fine.

Okay, this rule is now suggestions-only, including the useMemo suggestion (only applied when useState is only destructured into a 1-element array, and is called with 1 argument).
Specs are updated, and the internal implementation is simplified since everything is suggestions now (no more fix/suggest split)

I think the next step for this might be actually do the correct variable rename within its scope. It seems like a a chunk of work, but maybe there's something already out there in the eslint ecosystem to accomplish this.
I saw this comment about the general technique of expanding the fix range to cover the entire scope of the changed variable.

I rebased this with some tweaks, and there's a failing test - namely, the one where it should ignore hook calls outside of components (unless we agreed not to treat those differently, in which case, please point me to that thread). Thanks!

i thought we decided this should be ignored? or did we decide instead that its placement should be ignored.

I don't think there was an explicit decision made. I first switched to using Components.detect in order to leverage functionality that might make this easier, but there isn't quite enough implemented in that util to get us there.
I wrote up big-ish reply to why I thought we should leave things as-is, but it's not showing up in this view. (I could only see it in the Files view on here, not in the Conversation view, but maybe you can see the comments in your email or notifications.)
Basically, eslint-plugin-react-hooks#rules-of-hooks has the code to determine whether a hook is used in an appropriate scope; we'd have to port a significant chunk of its innards over here to get the same functionality, for what I see as very marginal benefit.

authors: codecov-commenter duncanbeevers ljharb


text:
Correct the hyperlink typo

#hashing algorithms should be #hashing-algorithms

thnks :+1:

authors: bjrmatos tngan

repo: yaronn/xml-crypto


text:
Initialize Vuepress docs for a yasa documentation

It will be easier to maintain the admin UI and let new developers explore if the project has Vuepress docs. I'd wish to merge this branch into a docs-creation branch and the plan in my opinion should be filling the MD docs, and when it'll contain enough content, merge it to master. @kezhenxu94

It will be easier to maintain the admin UI and let new developers explore if the project has Vuepress docs. I'd wish to merge this branch into a docs-creation branch and the plan in my opinion should be filling the MD docs, and when it'll contain enough content, merge it to master. @kezhenxu94

Hey @almogtavor , thank you very much for your idea, do you want me to create a branch docs-creation and you open PRs targeting that base?

Absolutely. Also, as for my understanding the project should enter the ASF. Was there any progress on this issue?

I love the documentation idea.   YASA is at that difficult point where there is a LOT of potential, but not enough community around it to make it a easy add to Solr.   @kezhenxu94 and I have talked a bit, but I haven't contributed a ton of progress.
I think where my thinking went wrong was the idea that YASA should first aim to directly replace the Solr Admin.   The more I think about it, YASA should instead attempt to build community by providing features that the current Solr Admin doesn't support, in order to gain more traction in the market.   For example, ParamSets (https://solr.apache.org/guide/8_6/request-parameters-api.html#configuring-request-parameters) can only be  configured via API.   Super powerful feature that my colleague @nathancday has used before, but kind of hidden/lost behind complex API.

@almogtavor I created a branch and change the base of this PR to it.

@epugh Agree about the community. But I don't quite understand the motive behind not moving the project to ASF right now? I think it will be much easier to gain community support that way.

@epugh Agree about the community. But I don't quite understand the motive behind not moving the project to ASF right now? I think it will be much easier to gain community support that way.

This is a dilemma, to move the project into ASF, the project should have a community (though it can be a small community) to avoid the project being orphaned, but now I am not confident there is a community behind YASA

@kezhenxu94 I think you right. The project's last feature addition happened a year ago. Another issue that the fact that the project is personal and not in ASF cause to my opinion, is that most Solr users and developers don't even know about the project. If it would be an ASF project it would be more referenced by the Solr main repo, and more developers will get to know it.

@kezhenxu94 I think you right. The project's last feature addition happened a year ago. Another issue that the fact that the project is personal and not in ASF cause to my opinion, is that most Solr users and developers don't even know about the project. If it would be an ASF project it would be more referenced by the Solr main repo, and more developers will get to know it.

Usually, from my experience in Apache SkyWalking, there must be >3 PMC members interested in this project to make it ASF project.

@kezhenxu94 I think that finding 3 contributors that are ready to become PMC members isn't a hard thing to do. I'm ready to do so it
will be needed. Anyway I think it's a necessary move.

@kezhenxu94 I think that finding 3 contributors that are ready to become PMC members isn't a hard thing to do. I'm ready to do so it will be needed. Anyway I think it's a necessary move.

I appreciate your interest very much 🙇🏻 but I’m not sure how the Solr community and their PMC members think about this, some of them reached out to me but as you see there is no progress now. I’m afraid of it being silent again

@kezhenxu94 Oh I see. I guess we'll continue to work here and contact them later to see how can we to promote this action?

authors: almogtavor epugh kezhenxu94

repo: yasa-org/yasa


text:
Update required in UI

@yashchaudhri008, the project is amazing and interesting in all the fields, but required a better UI as the button size of the CTF button is way too small and the responsiveness of the index.html page is there but again the button size was a problem. I have taken the leverage to get a confirmation alert if the user clicks the "Back to home" button in main.html.
I have integrated all the changes in my fork. I would request you to see the same and inform me of any amendments.

Similar Issues:-
#1
#2
#3

#9 Please refer to the pull request for the same.
And accept this to your beautiful model.
Please

This is actually my first open source project. Sorry for the inconvenience.
You might want to look into the interactive exit part from main.html to index.html.
Can I use bootstrap in this?

@yashchaudhari008 bootstrap will make things easy and the code easier to understand, plus adding this will make a lot of things responsive by default.

Yeah, but this is simple project. I don't want to add bootstrap to this project. Thanks for sharing your views👍🏼.


text:
Bash support

Added support for the bash scripting language, continuing #9
Also refactored code to contain only a single list of programming languages (merged with #21 )

@yaworsw Any chance this is going to get merged?

repo: yaworsw/euler-manager


text:
slack webhook URL is saved in flows json file instead of credential flows json file

Hi,
The slack webhook URL is saved in flows json file instead of the flows credentials json file.
This is problem when

trying to share your nodered flows file OR
using the latest nodered project feature where you can publish your flows on github.
as in that case you are also sharing the slack webhook URL which allows everyone to read and post messages on your slack workspace.

This URL (or at least the last part) should be stored in the flows credentials json file as specified in https://nodered.org/docs/creating-nodes/credentials
kr
Jan.

Resolved by 2.0.0

authors: janvda travisghansen

repo: yayadrian/node-red-slack


text:
🛑 GIT is down

In 4488d17, GIT (https://git.neko.red) was down:

HTTP code: 0
Response time: 0 ms

Resolved: GIT is back up in 37c34c3.


text:
feat(TenantOverview): add charts

Should fix following issues:
https://github.com/ydb-platform/ydb-embedded-ui/issues/625 - display DB charts
https://github.com/ydb-platform/ydb-embedded-ui/issues/633 - untoggle diagnostics cards behaviour
https://github.com/ydb-platform/ydb-embedded-ui/issues/638 - timeframe contorls
https://github.com/ydb-platform/ydb-embedded-ui/issues/640 - requests chart
https://github.com/ydb-platform/ydb-embedded-ui/issues/655 - format charts values
Decided to complete all issues at once, since they are deeply interconnected.
Charts normal view:

Charts error:

To turn charts on you need to toggle "Display charts in database diagnostics" experiment. Decided to do it as another experiment, since in some scenarios it shows wrong data on current version.

You can view charts in diagnostics on Database Info tab. There are 5 charts, 2 - for default view, where none of the cards is selected, CPU, Storage and Memory cards content all have 1 chart.
Link for cluster with embedded-ui version with charts: https://nda.ya.ru/t/B8a0xud774QjL7
Node with the same ui, but with disabled charts: https://nda.ya.ru/t/s85UJGEJ74QjR4

I think we'd discussed that before, I asked you to hide graphs completely if it's not supported on the database. I expect the very fast answer in that case.

I think we'd discussed that before, I asked you to hide graphs completely if it's not supported on the database. I expect the very fast answer from backend in that case.

Experiment in this case is not a big work, it easily added and easily removed if needed. I just don't want to add a feature to the UI, that is not complete. The fact, that data is present in that case doesn't guarantee its correctness, it's misleading. So, as for me, feature flag here is essential. When https://github.com/ydb-platform/ydb/issues/1065 is fixed, merged and released in some ydb tag, we could remove it
While charts are hidden by feature flag, it's not so essential to hide them if they don't work, so I'd implement this hide as a next step https://github.com/ydb-platform/ydb-embedded-ui/issues/659
As for the presented error view, I want to create some reusable chart component (I believe, the charts story will evolve event further). That's why error view is necessary. It is on the screenshot. But it doesn't mean, that disabled charts could not be hidden (but as I said, it's the next step)

I think we'd discussed that before, I asked you to hide graphs completely if it's not supported on the database. I expect the very fast answer from backend in that case.

Experiment in this case is not a big work, it easily added and easily removed if needed. I just don't want to add a feature to the UI, that is not complete. The fact, that data is present in that case doesn't guarantee its correctness, it's misleading. So, as for me, feature flag here is essential. When [Viewer] Add proxy to database node for json_render request ydb#1065 is fixed, merged and released in some ydb tag, we could remove it
While charts are hidden by feature flag, it's not so essential to hide them if they don't work, so I'd implement this hide as a next step Hide diagnostics charts if they are not enabled #659
As for the presented error view, I want to create some reusable chart component (I believe, the charts story will evolve event further). That's why error view is necessary. It is on the screenshot. But it doesn't mean, that disabled charts could not be hidden (but as I said, it's the next step)

but you could skip whole feature-flag part... it would allow us to keep interface intact until there is actuall data for the graphs.

when i switch btw day/week there is no much difference in charts, maybe because there is no data for the period
but i expect to see chosen timeframe with zero/empty line if no data available

when i switch btw day/week there is no much difference in charts, maybe because there is no data for the period but i expect to see chosen timeframe with zero/empty line if no data available

Currently GraphShard doesn't return data for such timeframe (it's a limitation of the first version). It will be improved with the next versions.
YAGR doesn't support ranges for timeline axis, so it could not be fixed easily. It could be fixed only by adding null pointes either on backend, or on frontend.
Discussed with @adameat, decided not to do anything (display only the data, that is received).
Created an issue, you could add your point there: https://github.com/ydb-platform/ydb-embedded-ui/issues/669

Further work will be with following issues:
https://github.com/ydb-platform/ydb-embedded-ui/issues/659
https://github.com/ydb-platform/ydb-embedded-ui/issues/669

authors: adameat artemmufazalov sareyu

repo: ydb-platform/ydb-embedded-ui


text:
SLO workload native

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: #568
What is the new behavior?

SLO workload for native driver
workflow for github actions

Other information

Codecov Report
Patch coverage has no change and project coverage change: -18.63 :warning:

Comparison is base (57d382e) 65.03% compared to head (c188b62) 46.41%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##           master     #671       +/-   ##
===========================================
- Coverage   65.03%   46.41%   -18.63%
===========================================
  Files         220      149       -71
  Lines       21843    15785     -6058
===========================================
- Hits        14205     7326     -6879
- Misses       6864     8124     +1260
+ Partials      774      335      -439

Flag
Coverage Δ

?

1.17.x
46.06% <ø> (-0.07%)
:arrow_down:

1.19.x
46.48% <ø> (-18.49%)
:arrow_down:

1.20.x
46.49% <ø> (-18.24%)
:arrow_down:

integration
?

macOS
46.41% <ø> (+0.01%)
:arrow_up:

secure
?

ubuntu
46.41% <ø> (ø)

unit
46.41% <ø> (-18.16%)
:arrow_down:

windows
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 169 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: ImpressionableRaccoon codecov-commenter

repo: ydb-platform/ydb-go-sdk


text:
Авторизация с помощью IAM-токена : пример не работает

Помогите пожалуйста понять почему не работает стандартный пример из SDK: Авторизация с помощью IAM-токена
Вот мой код (несколько строк):
https://github.com/gayratv/ydb-auth-token

Проблему нашел.
В примере SDK предлагается написать так:
const authService = new TokenAuthService(accessToken, databaseName);
чтобы работало надо писать так:
const authService =new TokenAuthService(process.env.YDB_ACCESS_TOKEN_CREDENTIALS, dbName, getNewSslCredentials());
Но тут сразу возникает проблема: getNewSslCredentials - это внутренняя функция.
Чтобы пример работал надо :

в env определить переменную YDB_ACCESS_TOKEN_CREDENTIALS и туда положить IAM токен.
В коде записать так:
const authService = getCredentialsFromEnv(entryPoint, databaseName, logger);

@gayratv большое спасибо за user acceptance testing наших сниппетов! Похоже, действительно, в них вкралась некоторая неточность.

@rrewll Олег, поправишь сниппеты так, чтобы их действительно можно было использовать в реальном коде?

В рамках этого коммита и версии 2.9.2 эта проблема починена.

authors: gayratv rrewll tsufiev

repo: ydb-platform/ydb-nodejs-sdk


text:
SIM-Studio renaming and exceptions

We need to:

Hide UI related to adding validators when on hosted environment
Adapt the routing to remove the simulator subpath https://studio.genlayer.com/simulator/run-debug
Gatekeep or disable sensitive endpoints
Update the plausible domains to studio.genlayer.com (both in codebase + in plausible)
Adapt copy where necessary
Update the Docs

Will we be changing the repo name? @cristiam86

Also, regarding the validators, obviously we want to hide stuff related to editing them - but do we want to display them at all?

@denishacquin if it's not too much trouble, I think read only operations on the validators would be nice to have

@denishacquin if it's not too much trouble, I think read only operations on the validators would be nice to have

You mean keeping the read endpoints open? Or also displaying the validators in the UI but just not allow to add any?

authors: AgustinRamiroDiaz denishacquin

repo: yeagerai/genlayer-simulator


text:
Budget Request: yETH Team

Scope
Following the individual requests to investigate (#107) and implement (#114) yETH, and the adoption of YIP-72, it is now time to prepare, deploy, bootstrap, and launch yETH.
This request establishes a yETH Team with the goal of supporting and facilitating the function and adoption of the independent protocol, governed by st-yETH token holders.
Plan
Deliverables include:

[ ] Completing security audits for relevant codebases.
[ ] Implementing the specification as laid out in YIP-72.
[ ] Planning and preparing for a bootstrapping phase (leading into a launch) in June, including preliminary first iterations of complimentary functionality that is independent and non-critical for the use of the protocol, such as an interface, documentation, growth hacking, and online communications.

Deadline
May 2023
People

@0xkorin
@0xpickles

With additional support from the following "team prospects", who will be considered for promotion to full team members as their contributions grow:

corn
draper
evan
marco
major
wavey

Funding
We request funding in the form of:

Contributor grants for contributors.

Paid for work to fulfill the deliverables of the above plan.
Paid in DAI and/or YFI.
Llamapay streams

Security audit of the bootstrapping contracts. Slot locked in for end of May, with a quote.

:::info
The goal is to have a plan for receiving long term sustainable funding secured by the end of the request period.
:::
Amount

Component
Breakdown
Amount

Contributor grants
0xkorin: 15k DAI + 1.5 YFI0xPickles: 5k DAI + 0 YFI Additional contributors: 3 YFI
20k DAI 4.5 YFI

Security audit
Slot locked in for end of May, with an accepted quote
25k DAI

Wallet Address

3 of 5 Gnosis Safe that will be provided to yBudget separately

Reporting
Once, at the end of the request period
Contribute
New contributors are welcome to participate through joining this Telegram group: https://t.me/+VTjZKCzPkLhmYWFkz

@0xPickles I am interested in this project and want to contribute.

repo: yearn/budget


text:
"data/raw/val_wavs/zozo_16k_deepspeech.npy" not found

Hello I'm stuck at step 4 of the quick start:
bash scripts/infer_postnet.sh
bash scripts/infer_lm3d_nerf.sh

Running scripts/infer_lm3d_nerf.sh asks for data/raw/val_wavs/zozo_16k_deepspeech.npy but that file was never generated in any previous step. Am I missing something?

Hi, the bug may locate at  line75 in inference/nerfs/lm3d_nerf_infer.py, which uses my absolute GeneFace python interpreter to generate the deepspeech feature of zozo.wav and saved it into data/raw/val_wavs/zozo_16k_deepspeech.npy.
I have changed the path in the latest commit. Hopefully, it will solve this issue.

Thanks! That was indeed the issue.

authors: yerfor zimonitrome

repo: yerfor/GeneFace


text:
Serializing into WOFF2?

It seems that the subset() function is hard-coded to output the result in OpenType format. I was wondering if you would consider adding a way to serialize into WOFF2 format as well? WOFF2 can be useful for web contexts, to embed the font into SVG files, etc.

While possible, I don't think this would be a high priority as it's fairly easy to convert a TTF to WOFF2 with something like woff2_compress from https://github.com/google/woff2. Also be aware of #27 in regards to subsetting.

authors: gendx wezm

repo: yeslogic/allsorts


text:
Make flate2/zlib feature optional to enable compiling to WASM.

Thank you for such a useful crate! As currently implemented, the use of the flate2/zlib feature in Cargo.toml prevents compiling to WASM, since zlib is not available. Would it be possible to make this dependency optional? Something like the following would do it:
[package]
name = "allsorts"
version = "0.6.0"
authors = ["YesLogic Pty. Ltd. <info@yeslogic.com>"]
edition = "2018"

homepage = "https://github.com/yeslogic/allsorts"
documentation = "https://docs.rs/crate/allsorts"
repository = "https://github.com/yeslogic/allsorts"

readme = "README.md"
license = "Apache-2.0"
include = ["/LICENSE", "src/**/*"]

description = "Font parser, shaping engine, and subsetter for OpenType, WOFF, and WOFF2"
keywords = ["font", "shaping", "opentype", "truetype", "parse"]
categories = ["text-processing"]

[dependencies]
bitflags = "1.0"
bitreader = "0.3.2"
brotli-decompressor = "2.3"
byteorder = "1.2"
encoding_rs = "0.8.16"
flate2 = { version = "1.0", default-features = false }
glyph-names = "0.1"
itertools = "0.8"
lazy_static = "1.3.0"
libc = "0.2"
log = "0.4"
num-traits = "0.2"
ouroboros = "0.9"
rustc-hash = "1.1.0"
tinyvec = { version = "1", features = ["alloc"] }
ucd-trie = "0.1.2"
unicode-canonical-combining-class = "0.1.0"
unicode-general-category = "0.3"
unicode-joining-type = "0.4.0"

# Optional dependencies
pathfinder_geometry = { version = "0.5.1", optional = true }

[dev-dependencies]
regex = "1.1.6"

# criterion = "0.3"

# [[bench]]
# name = "bench-shape"
# harness = false

# [[bench]]
# name = "bench-read"
# harness = false

[features]
default = ["outline", "zlib"]
prince = []
outline = ["pathfinder_geometry"]
zlib = ["flate2/zlib"]
miniz_oxide = ["flate2/default"]

The flate2/zlib feature is now exposed by allsorts/zlib, which is added to the default features. So by default everything remains exactly the same. But now consumers who want to compile to WASM (or other scenarios where zlib is not available) can remove that feature and use the allsorts/miniz_oxide feature instead.
No doubt there's other, possibly more elegant, ways of doing this, but this seems a simple enough solution.
Possibly related to #7.

That seems reasonable. Most of the YesLogic folks are on leave at the moment. We should be able to add this in the new year. I return 11 Jan, feel free to ping me at the end of that week if you haven't heard anything by then.

I've pushed a change to implement this. I hope to make a release this week but we've got a few other tweaks in the works that I'd like to include so will hold off for a day or so.

Many thanks, I look forward to the next release.

New release has been published.

authors: ajrcarey wezm


text:
Update to new Command/ArgumentMetadata interfaces

Update built in commands to use new Command/ArgumentMetadata interfaces

change ArgumentMetadata class to interface
change ArgumentType to enum
change Command class to an interface that enforces static and non static fields/methods

Typescript doesn't allow static fields/methods to be used in interface. In order to enforce the static properties in interface (show errors to user if a customcommand is not implemented properly), a workaround is implemented. CommandExecutable contains all the non static properties and functions. Command holds a constructor signature of type CommandExecutable and specified fields (e.g alias, args, and shortdescriptions) that will be required to be static when type checked. This approach is similar to what is used in React (Component and ComponentClass)
The syntax to follow is: const SomeCustomCommand : Command = class { ... }

Update other related files such as commandregistry, commandimporter, and yargsfactory to follow the new interface

J=SLAP-1492
TEST=compile

see that built-in commands passed when using local jambo in theme build process.

Note that custom commands failed since its command class structure does not follow the new updated infrastructure

It looks like some of the tests are failing

repo: yext/jambo


text:
'NoneType' object is not subscriptable

大部分時候翻譯正常、只會偶爾噴錯：

但有時會無限噴錯，一直--resume也沒用：

这个报错是你用了 free chatgpt-3.5 报的错。。

这个报错是你用了 free chatgpt-3.5 报的错。。

我之后完善下报错信息，抱歉最近精力没在这上

是我使用的 gpt 出問題了，我這邊再自己研究下


text:
Help improve progress bar on the book translation progress

@yihong0618 Hey, I fix the linting problem

@kj-huang

@yihong0618 This issue should be fixed, and also I update the codebase align with the newest commit

merged thanks


text:
cchardet

Something to do with this abandoned dependency? I am getting error in Python 3.11.1 (tags/v3.11.1:a7a450f, Dec  6 2022, 19:58:39) [MSC v.1934 64 bit (AMD64)] on win32

maybe will work on it these days, thanks


text:
运行xiaogpt.py 后，控制台能打印出问的问题，但没法继续就挂了

` python3 xiaogpt.py --hardware LX04  --mute_xiaoai --use_gpt3
Running xiaogpt now, 用帮我/请回答开头来提问
或用开始持续对话开始持续对话
问题：一加一等于几？
Traceback (most recent call last):
File "/Users/xiaoqiang/Market/dev/gpt/xiaogpt/xiaogpt.py", line 5, in
main()
File "/Users/xiaoqiang/Market/dev/gpt/xiaogpt/xiaogpt/cli.py", line 136, in main
loop.run_until_complete(miboy.run_forever())
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/Users/xiaoqiang/Market/dev/gpt/xiaogpt/xiaogpt/xiaogpt.py", line 466, in run_forever
await self.stop_if_xiaoai_is_playing()
File "/Users/xiaoqiang/Market/dev/gpt/xiaogpt/xiaogpt/xiaogpt.py", line 408, in stop_if_xiaoai_is_playing
is_playing = await self.get_if_xiaoai_is_playing()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/xiaoqiang/Market/dev/gpt/xiaogpt/xiaogpt/xiaogpt.py", line 399, in get_if_xiaoai_is_playing
playing_info = await self.mina_service.player_get_status(self.device_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'MiNAService' object has no attribute 'player_get_status'`

最好不用  --use_gpt3 用 chatgpt
pip uninstall miservice
pip install miservice_fork

最好不用  --use_gpt3 用 chatgpt
pip uninstall miservice
pip install miservice_fork

嗯，试过了，好像还是不行，

python3 xiaogpt.py --hardware LX04  --mute_xiaoai --use_chatgpt_api
Running xiaogpt now, 用帮我/请回答开头来提问 或用开始持续对话`开始持续对话
问题：请问明天的天气如何？
Traceback (most recent call last):
File "/Users/xiaoqiang/Market/dev/gpt/xiaogpt/xiaogpt.py", line 5, in
main()
File "/Users/xiaoqiang/Market/dev/gpt/xiaogpt/xiaogpt/cli.py", line 136, in main
loop.run_until_complete(miboy.run_forever())
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/Users/xxt/dev/gpt/xiaogpt/xiaogpt/xiaogpt.py", line 466, in run_forever
await self.stop_if_xiaoai_is_playing()
File "/Users/xxt/dev/gpt/xiaogpt/xiaogpt/xiaogpt.py", line 408, in stop_if_xiaoai_is_playing
is_playing = await self.get_if_xiaoai_is_playing()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/xx/dev/gpt/xiaogpt/xiaogpt/xiaogpt.py", line 399, in get_if_xiaoai_is_playing
playing_info = await self.mina_service.player_get_status(self.device_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'MiNAService' object has no attribute 'player_get_status'`

我们是不是可以学一下举一反三。。。
python -m pip uninstall miservice
python -m pip install miservice_fork


text:
本地编译Docker Image 构建失败

问题：
在项目根目录下执行docker构建命令，运行失败
命令：

docker build -t xiaogpt .

日志：

=> ERROR [builder 4/4] RUN python3 -m venv .venv && .venv/bin/pip install --no-cache-dir -r   43.5s
------
 > [builder 4/4] RUN python3 -m venv .venv && .venv/bin/pip install --no-cache-dir -r requirements.txt:
29.09 ERROR: Could not find a version that satisfies the requirement aiohttp==3.9.1 (from versions: none)
29.09 ERROR: No matching distribution found for aiohttp==3.9.1
43.35
43.35 [notice] A new release of pip is available: 23.0.1 -> 23.3.2
43.35 [notice] To update, run: python3 -m pip install --upgrade pip
------
Dockerfile:4
--------------------
   2 |     WORKDIR /app
   3 |     COPY requirements.txt .
   4 | >>> RUN python3 -m venv .venv && .venv/bin/pip install --no-cache-dir -r requirements.txt
   5 |
   6 |     FROM python:3.10-slim
--------------------
ERROR: failed to solve: process "/bin/sh -c python3 -m venv .venv && .venv/bin/pip install --no-cache-dir -r requirements.txt" did not complete successfully: exit code: 1

问题已解决，修改Dockerfile，给pip安装添加清华大学源
RUN python3 -m venv .venv && .venv/bin/pip install --no-cache-dir -r requirements.txt -i https://pypi.tuna.tsinghua.edu.cn/simple


text:
Feature: decorators

Would be nice allow to decorate already existing services in container.
I see at least 2 variants of usage:

Decorating already existing service that exist in another container (applied only to CompositeContainer)
// config/common.php

return [
  // ...
  LoggerInterface::class => function() use ($compositeContainer) {
    return new LoggerDecorator($compositeContainer->get(LoggerInterface::class));
  }
  // ...
];

At now it parsed as circle dependency, but we can modernize this syntax. At now it doesn't matter.
2. Decorating already existing services in current container
// config/common.php
return [
  // ...
  LoggerInterface::class => /* ... */,

  LoggerDecorator::class => [
      'decorated' => LoggerInterface::class
  ];
  // ...
];

or
// config/common.php
return [
  // ...
  LoggerInterface::class => /* ... */,
  // ...
];

// config/common.dev.php
return [
  // ...
  LoggerInterface::class => function ($container) {
      return new LoggerDecorator($container->get(LoggerInterface::class));
  }
  // ...
];

What is the expected result?
In all cases $container->get(LoggerInterface::class) should return LoggerDecorator
What do you get instead?
In the first case we have CircularReferenceException. In the second case we have LoggerInterface implementation that passed via /* ... */ or CircularReferenceException`.
Additional info
I think we need to think all future features for another cases (I'm not about decorators only).

I made syntax examples.
LoggerInterface::class => (new ContainerBuilder())
  ->callback(fn () => new Logger())
  ->decorate(fn ($container, $logger) => new LoggerDecorator($logger));

LoggerInterface::class => (new ContainerBuilder())
  ->callback(fn () => new Logger())
  ->decorate(LoggerDecorator::class),
LoggerDecorator::class => fn ($container) => new LoggerDecorator($container->get(LoggerInterface::class)),

$definitions = [
  LoggerInterface::class => fn () => new Logger(),
  LoggerDecorator::class => fn ($container) => new LoggerDecorator($container->get(LoggerInterface::class)),
];
$containerBuilder
  ->decorate(LoggerInterface::class, LoggerDecorator::class)
  ->decorate(ContainerInterface::class, ContainerDecorator::class);

#10

Why does decorators are better than nested/contextual containers?

Using decorators we can to substitude any dependencies from PSR container, not only Yii container.
It looks more cleaner and flexible.
Nested container is a part of way to use decorators.
Do you have examples with contextual container that solve this problem?

authors: viktorprogger xepozz

repo: yiisoft/di


text:
Attribute names tests

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Fixed issues
161

It's are miracle ) I will try re run test locale now

repo: yiisoft/form


text:
Locale - move Cookie to constructor?

This also will allow get rid of $cookieName, $secureCookie and $cookieDuration parameters. From the other side, cookie does not have an interface to depend on.

Cookie is not a service and isn't meant to be in DI container. How would you provide it to the constructor?

authors: arogachev samdark

repo: yiisoft/yii-middleware


text:
Test coverage 100% + MSI 100% + improvements non-code files + other...

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues
-

Test coverage 100%
MSI 100%
Refactoring tests
Replace dev dependencies yiisoft/di and yiisoft/event-dispatcher to yiisoft/psr-dummy-provider

Thanks.

authors: samdark vjik

repo: yiisoft/yii-view


text:
No check for handling SQL error in ActiveRecord updateAll()

updateAll() returns an integer with number of rows updated. Syntax below.
public static integer updateAll ( $attributes, $condition = '', $params = [] )
However there is no way to check if updateAll() was successful. In update() method, there is a provision to check for SQL failure since it returns either boolean or integer depending on success or failure of query execution as shown below.
public integer|boolean update ( $runValidation = true, $attributeNames = null )
Or may be there is a way still to check for updateAll() failure but not documented?

updateAll does not run validations, does not calls before save etc. It convient call to command::update with set model table name.
Btw update() does not return false with sql errors:

@return integer|boolean the number of rows affected, or false if validation fails or [[beforeSave()]] stops the updating process.

With sql errors exceptions will be thrown in both cases

Thanks for the clarification.