text:
Please consider annotating LAPACKE_lsame with attribute((const))

LAPACKE_lsame is a case-insensitive char comparison, but is implemented in its own object file, so a compiler has no was of knowing (without LTO) that multiple calls to it with the same inputs have the same results.
GCC has __attribute__((const)) for marking functions that always return the same result on the same inputs:
https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-const-function-attribute
I'm the maintainer of the GCC static analyzer.  When building openblas-0.3.15 with my analyzer, I noticed slightly over 2000 false positives from -Wanalyzer-malloc-leak on code like this:
        if( LAPACKE_lsame( vect, 'b' ) || LAPACKE_lsame( vect, 'p' ) ) {
            pt_t = (lapack_complex_float*)
                LAPACKE_malloc( sizeof(lapack_complex_float) *
                                ldpt_t * MAX(1,n) );
            if( pt_t == NULL ) {
                info = LAPACK_TRANSPOSE_MEMORY_ERROR;
                goto exit_level_2;
            }
        }

	[...snip...]

exit_level_2:
        if( LAPACKE_lsame( vect, 'b' ) || LAPACKE_lsame( vect, 'q' ) ) {
            LAPACKE_free( q_t );
        }

e.g. in https://github.com/xianyi/OpenBLAS/blob/c5f280a7f0e875d83833d895b2b8b0e341efabf4/lapack-netlib/LAPACKE/src/lapacke_cgbbrd_work.c
where my analyzer naively assumes that LAPACKE_lsame( vect, 'b' ) || LAPACKE_lsame( vect, 'p' ) can be true at the malloc guard, and false at the free guard; other compilers/analyzers may have similar behavior.
I'm testing a fix for the GCC analyzer to take account of __attribute__((const)), and in my tests so far it fixes the OpenBLAS false positives when the attribute is added to LAPACKE_lsame.  (I'm tracking this for GCC as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104434).  Presumably some kind of configuration define would be needed to support compilers that don't have the attribute.
Hope this is constructive

Thanks - I must admit it is not entirely clear to me what the practical implications are, apart from misleading the static analyzer. The LAPACKE code in OpenBLAS is taken from https://github.com/Reference-LAPACK/lapack (also know as "netlib"), I can forward the issue if you like.

There's a chance it could affect code generation, in that with that attribute the compiler is allowed to assume that the result of e.g. LAPACKE_lsame( vect, 'b' ) doesn't change if vect doesn't change, and could thus stash the result in a synthetic local.

There are other text processing libraries out there. EN_US EBCDIC is handled well by both linux libiconv, or lighter licensed (inline-able) netbsd iconv. This function has no callers, no sign of linear projection or algebra whatsoever. Probably left there from some mainframe tests in early nineties.

@brada4 that is a bit besides the point. LSAME is used a lot internally in LAPACK, and I see no reason why third-party code that already makes use of LAPACKE for other purposes should resort to other libraries for what LSAME does. (Though this is of course trivial to do in C as well nowadays)

I think it s quite impractical to expect EBCDIC character in that place.

source: gharchive/issue

authors: brada4 davidmalcolm martin-frbg

license_type: permissive

license_source: bigquery


text:
Fix ISMIN and ISMAX kernel choices for POWER8

resolves ppc utest failures in the newly added ismin test. Note it is actually the defaults in Makefile.L1 that need to be corrected if this passes all tests.

The tests look fine but you forgot to rebase the branch on top of the current master.

Huh ? I merged isuruf's PR in the meantime but that should not conflict. What am i missing ?

Huh ? I merged isuruf's PR in the meantime but that should not conflict. What am i missing ?

I see in this pull request linked 6 commits, but it's likely irrelevant.

Should be. Besides the actual rebases there was a mistaken commit of the KERNEL file to the develop branch instead of the newly created one, and its reversal. And I tried the imin_ppc440.S as well before setting on imin.S (Guess squash&merge might have looked cleaner, but as all changes affected the same file the result should be the same)

source: gharchive/pull-request

authors: martin-frbg marxin

repo: xianyi/OpenBLAS


text:
Update uiautomator lib to v18:2.1.2.

This fixes https://github.com/xiaocong/uiautomator/issues/174, which
already works as expected in the new uiautomator.

@xiaocong, do you mind taking a look? This is still affecting our team.

@hongbinbao, are you able to merge this?

repo: xiaocong/android-uiautomator-server

license: mit


text:
The website is not very smooth

I have noticed that there are always some CPU tasks in the background. What was the cause of that?

It must be due to the dynamic gradient color. I will optimize it.

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
hug6, @killeder, @geekwho-eth, @telmag92, @vihermawan, @sdfsdfsdf145314364, @zhouzh1, @talentlessguy, @garNUE, @GoBGI, @RayMusk, @DeepEffort, @adshao, @Colorize8, @JacksonRed, @XMan-O, @RawAttack, @NissinFree, @tufo830, @zakimzf, @17737787811, @chuangjiantx123, @asyuan, @solo-tiger-man, @wgqzlj, @weixiaojian001, @emanuelb, @siuisa, @libtree, @0xd0a, @fpdb, @heisaman, @ValiAlex, @devout1337, @RogueBeef, @PHSix, @luyl, @CreaKiko, @TenviLi, @Hope-Diamond, @stackia, @gikoluo, @tuanductran, @soucat, @MoonWindow, @kakegu, @tildaw27, @i0Ek3, @Yinboan, @Askar57gianghungtien, @Rongrongku, @kai2k9, @appfromape, @less-cat, @tuananh9801, @billyma128, @innaturn, @111hunter, @upstemer-hash, @ChieKR, @kittyFishing, @kakegu, @canisminor1990, @coder-drinker, @zjxubinbin, @futanar1, @zsgzzzf, @bandyishere, @hyzhao1998, @cybernagle, @Fog3211, @orxia, @WinDB3ll, @Alejanpro, @usherasnick, @Antisunny, @1984Zenith, @Lugdunumn, @GlamRing, @HardDevel, @misc520, @Weo6, @molierflower, @Rita-Xizu, @nj-steve, @Bruce1998, @leeleoo, @mvandermeulen, @sunnala, @lhw619, @xiaojunma960, @gsZhiZunBao, @stdedit, @whatwewant, @haujoe, @src-chen, @NewHappy1024, @dashen8888, @MonchiLin

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
weboAp, @vbrekher, @pizzamanblabla, @dliuproduction, @english4coder, @phrazzld, @jueewo, @afxal, @ArnaudFavier, @siburu, @christianzoll, @mowinters, @EdgarHSalinas, @QuynhNguyen, @changjieyang01, @jzarca01, @bbrietzke, @yalcincosar, @stepcellwolf, @rockf91, @zero85258, @KeanuPang, @ndphuong, @igardiet, @Ractive89, @ohitslaurence, @erhant, @NicolasLeRoux, @dorucioclea, @lleonesouza, @beblueblue, @wgqzlj, @Koleok, @MarioJuniorPro, @forrestsatterfield, @und3fined, @wesleysmyth, @jinchun, @xox9001, @luoposhanhuige, @CodeJonesW, @kaichen, @khantzinthu2k1, @boroda413, @Demontf, @siong1987, @sptq, @zaa, @GaloisField2718, @xianz271828zoexx, @ujjwalgoyal19, @KshitijV97, @leandrogavidia, @puzzithinker, @b33l238u8, @EdsonAlcala, @strawhatboy, @ess007, @tugh, @desfero, @Lainvers, @nimatr, @alphadose, @Artikodin, @zeyuanx, @christon1, @jjyr, @itsky365, @flozender, @josojo, @RicoloveFeng, @kaiyes, @dsmagic12, @henriquecouto, @web3senior, @w1ndyz, @amohammad, @bitloo, @NexZhu, @shinyzhu, @vsboldakov, @schmijos, @sshhaatteerr, @aozkan, @iida-hayato, @izayacity, @taywils, @mdeyn, @Lifehack-crypto, @code-miller, @readygo67, @capaci, @keithadams, @tsvillain, @duanjunxiao, @jyterencekim, @Lisayg, @beaubutton, @jinsley8

authors: JE-lee byungster simonspg xiaoluoboding

repo: xiaoluoboding/vue-color-wheel

license: MIT

license_source: github-api


text:
[mac] channel-video 组件在视口内滚动时，可能导致小程序视口闪烁

笔记地址：#小程序://墨问/9Lj023FX2byfqTl
这篇笔记，mac 端打开，只要 channel-video 组件在视口中，小程序窗口就不断闪烁灰屏，滚出视口就正常了。控制台无报错。
录屏：
https://github.com/user-attachments/assets/e02c6fff-adf6-4127-a13a-e8703f083192

hack: PC 端 channel-video 组件无法跳转视频号，可以禁用掉

repo: xiaweiss/miniprogram-bug-report


text:
Inquiry about Code Release

I would like to inquire about the time of releasing the code for SVGDreamer

Dear LLSean,
Thank you for your interest in our work. We plan to open the source code in March, barring any unforeseen circumstances.
Feel free to ask any questions you may have about SVGDreamer.
Best regards,
Ximing Xing

authors: LLSean ximinng

repo: ximinng/SVGDreamer


text:
Fix build for tests non-x86_64

Test for update_cdf_4_sse2 fails since the method under test cannot be found.

Coverage remained the same at 81.708% when pulling f244ba408d04dc4728c18aefbb500d5af4004995 on barrbrain:test-non-x86_64 into e484c7ee2b0321dcc4835425d8dceab50345f737 on xiph:master.

authors: barrbrain coveralls


text:
trash_next fails

After updating from 3.0.10 to 3.0.11, my log is now filled with errors like the below.
2019-12-10 21:25:07 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.trash_next fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 270, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 450, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/afvalwijzer/sensor.py", line 143, in update
    self._state = item['value'].strip()
AttributeError: 'int' object has no attribute 'strip'

Same over here, log is flooding with errors;
Update for sensor.trash_next fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 281, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 461, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/afvalwijzer/sensor.py", line 143, in update
    self._state = item['value'].strip()
AttributeError: 'int' object has no attribute 'strip'
----
22:04 custom_components/afvalwijzer/sensor.py (ERROR) - bericht kwam voor het eerst om 17:27 en verschijnt 540 malen

Almost 100 loglines every hour.

Has been addressed in a new Pr...
You can manually delete the strip from the sensor.py until the Pr is merged

That fixed it! thanks!

authors: Mariusthvdb Veldkornet freemann


text:
Code restructuring and more pylint fixes

Purpose
More code restructuring and cleaning up pylint issues
New Features
n/a
Bug Fixes
n/a
Before/After
n/a
Additional Context
n/a

I was referring to the latter 2 lines of
from nari.types.event.status import StatusApply, StatusRemove
from nari.types.statuseffect import StatusEffect
from nari.types.status import Status

oh yah, I can merge types.statuseffect and types.status then

made those changes

authors: ayyaruq lunarrize

repo: xivlogs/nari


text:
feat: can reference any branch and have protos build correctly

Overview
Issue: https://github.com/orgs/xmtp/projects/8/views/4?pane=issue&itemId=26452558
This provides an example for being able to reference any xmtp/proto branch we want to target. Since xmtp-proto is shared, whatever branch we choose needs to be kept up to date with xmtp/proto#main.
Test Plan

Confirm that a new test field was added correctly
Ensure that cargo build passes in xmtp-proto and in xmtp-networking which consumes xmtp-proto

Open Question
What do you want to call our working branch? Should we utilize beta again?

Correction: it seems like the branch may need https://github.com/xmtp/proto/blob/main/proto/buf.yaml - so it has to be based off of recent main

FYI using xmtpv3 as the branch: https://github.com/xmtp/proto/tree/xmtpv3

repo: xmtp/libxmtp


text:
docker 创建inference ，通过网页的形式或命令行的形式都无法下载model。

System Info / 系統信息
win10  wsl2
Running Xinference with Docker? / 是否使用 Docker 运行 Xinfernece？

[X] docker / docker
[ ] pip install / 通过 pip install 安装
[ ] installation from source / 从源码安装

Version info / 版本信息
xinference, version 0.13.2
The command used to start Xinference / 用以启动 xinference 的命令
1，WebUI 不能下载，如图：

2，既然UI不能下载，我就进入容器内部，用命令下载，先确定容器可以上网，然后down，不行。如图：

3，环境cuda11.8 ，按说明直接部署运行如下，
pip install "xinference[vllm]"
报错，如图：

Reproduction / 复现过程
同上
Expected behavior / 期待表现
能下载model

最新版页面上 optional 选项里，选择 modelscope 作为下载源。

authors: qinxuye wjhmiss

repo: xorbitsai/inference


text:
🛑 Design Swan is down

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

HTTP code: 500
Response time: 114 ms

Resolved: Design Swan is back up in 28d817d after 12 minutes.

repo: xoryorz/upptime


text:
🛑 Design Swan is down

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

HTTP code: 500
Response time: 126 ms

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


text:
🛑 Design Swan is down

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

HTTP code: 500
Response time: 97 ms

Resolved: Design Swan is back up in 8923989 after 53 minutes.


text:
NC22: Replace admin user with API token

This is just a heads up that the upcoming release does not require admin privileges for monitoring anymore: https://github.com/nextcloud/serverinfo/pull/269

Thanks for the heads-up! I'll keep this open until it's implemented...

I think nextcloud 22 supports this now, would be nice to be able to drop admin permissions

I assume one of my instances will upgrade to Nextcloud 22 soon. I'll do an implementation then.

Hi @xperimental
Do you have any progress to share on the token login implementation?

@Kybeer there has been no progress on this feature yet. But I noticed last week that one of my instances is now running NC22.

Instead of a user/password the new request needs just a NC-Token header, that's easy to implement. But this also requires a new config option and maybe some logic to let the user choose between the two authentication mechanism.
https://github.com/nextcloud/serverinfo/pull/269/files#diff-b86b31801e087ecdaaf18d4d9db5f4362120f71c7173386d118e94b2f1899ac9

@J0WI Thanks! I already had a look about a week ago which led to the nc22-token branch. There are still some errors in it, that's why there's no pull-request for it yet. But I'll get there "soon" 🙂

There's a pull-request for this feature now. Also, feel free to try out the image built from that feature-branch:
xperimental/nextcloud-exporter:0.4.0-15-gbb88fb6
ghcr.io/xperimental/nextcloud-exporter:0.4.0-15-gbb88fb6

FWIW I've created a PR to allow setting up the token in https://github.com/nextcloud/docker/pull/1656

If there is no negative feedback about this change in the next days, I'll merge it and prepare a new release afterwards.

@xperimental any plans to create that release soon? :)

Sorry, the past days were busier than I expected. I'll probably do the release in the next days. The good news is that another bug was found in the meantime. :slightly_smiling_face:

authors: J0WI Kybeer mrueg xperimental

repo: xperimental/nextcloud-exporter


text:
"Sent unsupported FastCGI protocol version" error with keepalive

I was testing my ServiceStack web service with httperf tool and periodically was getting "sent unsupported FastCGI protocol version" error. Here my error log:
2016/05/04 20:27:12 [error] 23191#0: *18 upstream sent unsupported FastCGI proto
col version: 0 while reading upstream, client: 195.19.44.143, server: localhost:
8000, request: "GET /db/api/thread/list?forum=hgezdt6ufw&limit=52&order=desc&thr
ead=374 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "127.0.0.1"
2016/05/04 20:27:18 [error] 23191#0: *25 upstream sent unsupported FastCGI proto
col version: 0 while reading upstream, client: 195.19.44.143, server: localhost:
8000, request: "GET /db/api/post/list?post=976184&limit=75&order=asc&forum=qz72
HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "127.0.0.1"
2016/05/04 20:27:19 [error] 23191#0: *26 upstream sent unsupported FastCGI proto
col version: 0 while reading upstream, client: 195.19.44.143, server: localhost:
8000, request: "GET /db/api/thread/listPosts?limit=66&order=desc&thread=5651 HTT
P/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "127.0.0.1"
2016/05/04 20:27:26 [error] 23191#0: *39 upstream sent unsupported FastCGI proto
col version: 0 while reading upstream, client: 195.19.44.143, server: localhost:
8000, request: "GET /db/api/forum/listThreads?related=user&related=forum&limit=3
9&order=asc&forum=mvsf6q HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host:
"127.0.0.1"
2016/05/04 20:27:32 [error] 23191#0: *49 upstream sent unsupported FastCGI proto
col version: 0 while reading upstream, client: 195.19.44.143, server: localhost:
8000, request: "GET /db/api/thread/listPosts?limit=75&order=desc&thread=1556 HTT
P/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "127.0.0.1"

After some research I've found what appearing of the error depends on enabled or disabled keepalive.
Here my Nginx config:
upstream fastcgi_backend {
  server 127.0.0.1:9000;
  #keepalive 32;
}
server {
  listen 8000;
  server_name localhost:8000;
  error_log /var/log/nginx/Forum.Error.log;

  location / {
    root /root/forum/Forum/;
    index index.html index.htm default.aspx Default.aspx;
    fastcgi_index Default.aspx;
    #fastcgi_keep_conn on;
    fastcgi_pass fastcgi_backend;
    include /etc/nginx/fastcgi_params;
  }
}

So, if I will remove # before commented lines I will get this errors. Otherwise, running with --keepalive=false switch everything is alright.
If you need some additional information, I'll be glad provide it for you.

Can you post a reproducible test case?

All actions tested in clean Ubuntu 14.04.4.

Download a database dump:
wget https://www.dropbox.com/s/6tkw43o97ptoblk/forum.tar.gz?dl=0.

Extract the dump:
tar -xzf forum.tar.gz.

Install MySQL:
sudo apt-get install mysql-server mysql-client.

Create a database and an user:

mysql -u root -p
create database forum;
create user 'admin'@'localhost' identified by 'admin';
grant all privileges on forum.* to 'admin'@'localhost';
exit

Restore a database from the dump (long running operation, about 20-30 mins):
mysql -u root -p forum < forum.sql

Install mono, git and HyperFastCgi:

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo "deb http://download.mono-project.com/repo/debian wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list
sudo apt-get update
sudo apt-get install mono-complete
sudo apt-get install git
git clone https://github.com/xplicit/HyperFastCgi.githyperfastcgi4 `--config=server.config`
sudo apt-get install autoconf automake libtool make libglib2.0-dev libevent-dev
cd HyperFastCgi/
./autogen.sh --prefix=/usr
 make
 sudo make install

Clone my project and build:

git clone https://github.com/Ustimov/Forums.git
cd Forums/
sudo apt-get install nuget
nuget restore
xbuild /p:Configuration=Release

Install nginx:
sudo apt-get install nginx

Configure nginx and HyperFastCgi:
create file
sudo nano /etc/nginx/sites-available/forum
and past (set paths according to your environment):

upstream fastcgi_backend {
  server 127.0.0.1:9000;
  keepalive 32;
}
server {
  listen 8000;
  server_name localhost:8000;
  error_log /var/log/nginx/Forum.Error.log;

  location / {
    root /root/Forums/Forum/;
    index index.html index.htm default.aspx Default.aspx;
    fastcgi_index Default.aspx;
    fastcgi_keep_conn on;
    fastcgi_pass fastcgi_backend;
    include /etc/nginx/fastcgi_params;
  }
}

create symlink to forum file
rm /etc/nginx/sites-enabled/default
ln -s /etc/nginx/sites-available/forum /etc/nginx/sites-enabled/forum
sudo service nginx restart

create server.config with this content (set paths according to your environment):
<configuration>
        <server type="HyperFastCgi.ApplicationServers.SimpleApplicationServer">
                <!-- Host factory defines how host will be created. SystemWebHostFactory creates host in AppDomain in standard ASP.NET way -->
                <host-factory>HyperFastCgi.HostFactories.SystemWebHostFactory</host-factory>
                <!-- <threads> creates threads at startup. Value "0" means default value -->
                <threads min-worker="40" max-worker="0" min-io="4" max-io="0" />
                <!--- Sets the application host root directory -->
                <!-- <root-dir>/path/to/your/dir</root-dir> -->
        </server>
        <listener type="HyperFastCgi.Listeners.NativeListener">
                <apphost-transport type="HyperFastCgi.Transports.NativeTransport">
                        <multithreading>Single</multithreading>
                </apphost-transport>
            <protocol>InterNetwork</protocol>
            <address>127.0.0.1</address>
            <port>9000</port>
        </listener>
    <apphost type="HyperFastCgi.AppHosts.AspNet.AspNetApplicationHost">
                <log level="Debug" write-to-console="true" />
                <add-trailing-slash>false</add-trailing-slash>
    </apphost>
    <web-applications>
        <web-application>
                <name>Forum</name>
                <vhost>0.0.0.0</vhost>
                <vport>8000</vport>
                <vpath>/</vpath>
                <path>/root/Forums/Forum/</path>
        </web-application>
    </web-applications>
</configuration>

Run application:
hyperfastcgi4 --config=server.config

Clone tests:1

git clone https://github.com/s-stupnikov/technopark-db-api.git
cd technopark-db-api/tests/
nano perf_test.py
change CONFIG_PATH = '/usr/local/etc/test.conf' to CONFIG_PATH = '../conf/test.conf'

Download a test scenario:
wget https://www.dropbox.com/s/eg5o1edz8y216j7/ustimov_httperf_scenario?dl=0.

Install httperf and run tests:

sudo apt-get install httperf
httperf --hog --client=0/1 --server=127.0.0.1 --port=8000 --uri=/ --send-buffer=4096 --recv-buffer=16384 --add-header='Content-Type:application/json\n' --wsesslog=100,0.000,ustimov_httperf_scenario

P.S. With clean installation I doesn't get the same error (I use Debian before), but now I've get:
2016/06/04 14:00:25 [error] 1633#0: *77 upstream sent too big header while reading response header from upstream, client: 127.0.0.1, server: localhost:8000, request: "GET /db/api/user/listPosts?limit=29&user=amizy%40ua.ru&order=asc HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "localhost"
2016/06/04 14:00:25 [error] 1633#0: *79 upstream sent too big header while reading response header from upstream, client: 127.0.0.1, server: localhost:8000, request: "GET /db/api/forum/listPosts?related=forum&related=thread&limit=25&order=asc&forum=1lnro HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "localhost"

"too big header" error message is unrelated to the error described in header of the issue and is expected behaviour of nginx.
Nginx has limitation of size for fast_cgi response headers, so if you want to send big headers in responses from your application you should increase these limits. There are  settings fastcgi_buffer_size and fastcgi_buffers, for example.
             fastcgi_buffer_size 512k;
             fastcgi_buffers 512 4k;

The numbers in sample are pretty huge, so for real application you should tweak them to your needs. Here is an simple case how to tweak buffers: https://easyengine.io/tutorials/nginx/tweaking-fastcgi-buffers/
The second point that in your case you try to perform two mutually exclusive operations: profile the service and compute a performance. If you want to check performance of the service, you should disable MiniProfiler by commenting two lines here
https://github.com/Ustimov/Forums/blob/master/Forum/Global.asax.cs#L54
https://github.com/Ustimov/Forums/blob/master/Forum/Global.asax.cs#L59
because at every request mini profiler adds some info to the headers and after large number of requests headers become several megabytes in size. Measuring performance of few-bytes body content with megabyte headers does not make sense.
If you want to profile the service to see the bottlenecks then run limited number of requests and analyze data returned by ServiceStack.
If you meet "Sent unsupported FastCGI protocol version" again, please feel free and open new issue.

authors: Ustimov xplicit

repo: xplicit/HyperFastCgi


text:
🛑 Geräteinformationen (Apple) is down

In ca6767b, Geräteinformationen (Apple) ($DEVICE_INFO_APPLE) was down:

HTTP code: 404
Response time: 122 ms

Resolved: Geräteinformationen (Apple) is back up in af0986c.


text:
Error When get LoadGoodsGroups

Hi,
I can't get info of Goods Groups when I use function LoadGoodsGroups() in newest version.
When I debugged:
In current version
public class XsollaGroupsManager : XsollaObjectsManager<XsollaGoodsGroup>, IParseble
	{
		public IParseble Parse (JSONNode groupsNode)
		{
			//JSONNode goodsGroupsNode = groupsNode["groups"];
			IEnumerator<JSONNode> goodsGroupsEnumerator = groupsNode.Childs.GetEnumerator ();
			while(goodsGroupsEnumerator.MoveNext()){
				AddItem(new XsollaGoodsGroup().Parse(goodsGroupsEnumerator.Current) as XsollaGoodsGroup);
			}
			return this;
		}
	}

But In previous version, It run good.
public class XsollaGroupsManager : XsollaObjectsManager<XsollaGoodsGroup>, IParseble
	{
		public IParseble Parse (JSONNode groupsNode)
		{
			JSONNode goodsGroupsNode = groupsNode["groups"];//["goodsgroups"];
			IEnumerator<JSONNode> goodsGroupsEnumerator = goodsGroupsNode.Childs.GetEnumerator ();
			while(goodsGroupsEnumerator.MoveNext()){
				AddItem(new XsollaGoodsGroup().Parse(goodsGroupsEnumerator.Current) as XsollaGoodsGroup);
			}
			return this;
		}
	}

This is my mistake when I create items in dashboard or your bug?
Thanks...

Hello,
Could you please clarify do you use your own code in order to receive the groups list? If so, it means that this our error / bug and we’ll fix it with the next version. We’re currently performing the optimization process of all SDK and most of classes could be removed or changed in future. Could you please clarify as well: would it be all right for you to have separate and convenient methods for receiving specific set of shop data?

repo: xsolla/xsolla-unity-sdk


text:
Trial PR to check github actions

Bump golangci-lint to v1.36
Signed-off-by: Sameer Vohra vsameer@vmware.com
Fixes #

Proposed Changes

Release Note

Docs

Codecov Report

Merging #2 (7b5b0a6) into master (1725902) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #2   +/-   ##
=======================================
  Coverage   81.24%   81.24%
=======================================
  Files         292      292
  Lines        8297     8297
=======================================
  Hits         6741     6741
  Misses       1146     1146
  Partials      410      410

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 1725902...35eeaa6. Read the comment docs.

Codecov Report

Merging #2 (7b5b0a6) into master (1725902) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #2   +/-   ##
=======================================
  Coverage   81.24%   81.24%
=======================================
  Files         292      292
  Lines        8297     8297
=======================================
  Hits         6741     6741
  Misses       1146     1146
  Partials      410      410

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 1725902...35eeaa6. Read the comment docs.

authors: codecov-io xtreme-sameer-vohra

repo: xtreme-sameer-vohra/eventing


text:
Normalized or NOT？

Hi,
Recently I came across your paper ( a nice work), your paper explained eq. 10 with "We normalized the embeddings to unit vectors and then maximized the  dot product of the both terms". However, I can not find "normalization" operation in your codes. May I ask you about this part?
Thanks a lot

Hi Junkang,
Thanks for your question! Yes, as we wrote in the paper, the normalized embeddings seem to be more reasonable.  The results reported in the paper are based on the normalized embeddings. But we later find comparable or even better results can be achieved without normalization (as the current code shows), so we remove the normalization in the code and you can add it back to achieve similar performance.
Best

authors: junkangwu kyriemao

repo: xue-pai/UltraGCN


text:
pictureselector 设置enableCrop 闪退，没有集成UCrop这个库

提Bug前需要做的事情
1.如果是集成问题的话，请保证仔细按照如何引用的步骤，一步一步来，不要跳步骤！
2.详细阅读过使用手册，并且确保是框架的问题。
3.参考常见问题,可以解决你出现的绝大多数问题!

如果以上都不能解决你的问题,那么请按照以下说明仔细填写信息,这里需要说明的是:不符合填写要求的issue一律不予理会,希望这样能节约大家的时间!

问题描述（必填）
对问题进行清晰而简明的描述，把握问题的关键点。
使用的XUI版本（必填）
如何重现（必填）
重现的步骤:

Go to '...'
Click on '....'
Scroll down to '....'
See error

期望的效果
对你期望的效果进行清晰而简明的描述。
截图
如果方便的话，贴一下程序截图和代码片段以帮助解释您的问题。
设备信息
请填写一下你运行设备的信息，信息越全越有助于我理解问题

设备名: [e.g. 华为P20]
Android版本: [e.g. Android 7.0]
设备型号 [e.g. ]
系统版本（手机厂商定制rom）

附加信息
在此处添加任何有关该问题的任何其他说明。

麻烦看清楚点,pictureselector 和xui有什么关系?你用enableCrop不引入对应库崩溃了

你xui lib是不是有拿了这个图片库？？你自己试试你的demo,既然你能提供enableCrop这个api,为什么不引入这个库？
---原始邮件---
发件人: "薛翔"<notifications@github.com>
发送时间: 2020年8月14日(周五) 凌晨1:01
收件人: "xuexiangjys/XUI"<XUI@noreply.github.com>;
抄送: "minveYu"<874591026@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [xuexiangjys/XUI] pictureselector设置enableCrop 闪退，没有集成UCrop这个库 (#75)
麻烦看清楚点,pictureselector 和xui有什么关系?你用enableCrop不引入对应库崩溃了
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

你睁大你的眼睛瞧瞧，到底有没有引入。

你睁大你的眼睛瞧瞧，到底有没有引入。
再说那个库那么大，我为什么要引入？

authors: minveYu xuexiangjys

repo: xuexiangjys/XUI


text:
Upgrade the Excelize to the master branch code

Upgrade the Excelize to the master branch code and remove unused data types
PR Details
Upgrade the Excelize to the master branch code and remove unused data types
Description
Upgrade the Excelize to the master branch code and remove unused data types
Related Issue
N/A
Motivation and Context
Upgrade the Excelize to the master branch code and remove unused data types
How Has This Been Tested
Existing unit test are passed
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

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

Comparison is base (1a6a444) 98.44% compared to head (f8e0601) 98.44%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #19   +/-   ##
=======================================
  Coverage   98.44%   98.44%
=======================================
  Files           1        1
  Lines        2951     2958    +7
=======================================
+ Hits         2905     2912    +7
  Misses         35       35
  Partials       11       11

Flag
Coverage Δ

unittests
98.44% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

authors: codecov-commenter tianaiyouqing

repo: xuri/excelize-wasm


text:
求个好看点的 nas-tool的图标

你想要新增什么图标？

你想要新增什么图标？填写图标项目的完整名字。

该图标有可参考的项目或 LOGO 地址吗？

若有的话，请列出来。

官方的就那样

你想要新增什么图标？

你想要新增什么图标？填写图标项目的完整名字。

该图标有可参考的项目或 LOGO 地址吗？

若有的话，请列出来。

已添加文字的 https://github.com/xushier/HD-Icons/commit/2494eb38217bf02e617d1d7070b19f3a2d5395db

repo: xushier/HD-Icons


text:
Upgrade the repo to use Terraform 0.7.x release

The repo currently works with 0.6.x but not 0.7.x due to some incompatibilities.

Resolved.

repo: xuwang/aws-terraform


text:
🛑 Emby is down

In b4c1293, Emby (https://cf.embyplus.club) was down:

HTTP code: 502
Response time: 630 ms

Resolved: Emby is back up in 6c9b61f.


text:
Last match of tournament isn't recording

Describe the bug
The result of the last match of the tournament isn't being recorded. This is a known issue as mentioned on the README / code TODO, but I just wanted to make it an official issue for discussion to fix it.
Log
I added print statements that output when game_state != previous_game_state or game_mode != previous_game_mode
Currently in Tournament with 1 matches remaining.  Game state is open.
Player 1 chance to win: 54.34%
Current Balance is: $25,421
Bet placed: $11 on player1
Current Tier is: 2
game_state != previous_game_state //  game_state_lies = False  // state locked // prev state open
Currently in Tournament with 1 matches remaining.  Game state is locked.
True Streaks are: (3, 5)
game_mode != previous_game_mode // game_state_lies = True // current mode: Exhibition // prev mode: Tournament
game_state != previous_game_state // game_state_lies = False // state 1 // prev state locked
In Exhibition.  No bets are placed, and nothing is recorded.  25 matches left.

Notes
I think what might be causing this is that the game mode is being updated (From Tournament -> Exhibitions) before (or at the same time) the match result is detected (Game State: locked -> 1). The program is correctly detecting that player 1 won (game_state = 1), but because the game mode changed, the if statement  detects that Exhibitions mode is active and instead logic proceeds to this elif statement. As a result, the program will not record the match.
Unsure if it helps, but here is what the twitch chatbot WAIFU4u posts in the following order when the last match of the tournament ends:
WAIFU4u: Exhibitions will start shortly. Thanks for watching!
WAIFU4u: Chopper wins! Payouts to Team Red. 25 exhibition matches left!
WAIFU4u: Bets are OPEN for Koumakan sakuya vs Haizilyo! (S Tier) (Requested by Lookbeneathyou) (exhibitions)

Thank you for documenting this officially outside of the #TODO in the program itself.
Yes, you're correct in that the way that the JSON updates, it updates the game mode first, then the game state.  Because of this, we're in the "no last match of tournies recording" issue here.
Fix incoming probably later this week.
Keep 'em coming if you find them.

This should now be fixed!
Please let me know if it isn't, and I'll reopen.

authors: xxxFRIARxxx zappybiby

repo: xxxFRIARxxx/SaltyBot

license: Unlicense


text:
data.propertyIsEnumerable causes error when override/not-exist

use Object.prototype.propertyIsEnumerable which is the Object's original method regardless of data.

What use case is this? MDN says "Every object has a propertyIsEnumerable method." https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/propertyIsEnumerable
We don't intend to support non-standard behavior anyway.

you mis-interpreted MDN's statement, it has the method, but not the property.
Some code writes x = Object.create(null) // over x = {}, the same-ish.,
which is not an uncommon (hyper-)optimisation to avoid all the proto chain (toString,...) appear in node.js source, vue (whether it runs faster or eventually lower memory, just don't bother.)
they don't have propertyIsEnumerable,
and entirely breaks the entire render with a single error..
It is an object-inspector, it should not ignore edge cases.
I will do a code search to find each method that breaks, and resubmit the PR.

Yeah, that makes sense and they are valid use cases. Thanks for bringing this up! Would you mind adding some cases in the storybook / test cases for this case? For example: Object.create(null) and Object.assign(Object.create(null), {key: 'value'})
Object.create(null) also shows "No properties" when you expand it in DevTools, but we can take care of that later.

closed as fixed in #70

authors: alcovescape xyc

repo: xyc/react-inspector


text:
Roadmap

Что нужно сделать?

[x] создан проект gradle+kotlin
[x] добавил проверку commitLint для github actions и git hooks
[x] [amazing-github-template] добавил синхронизацию labels и их проверку в pull requests
[x] [amazing-github-template] создан репозиторий на github с лицензией и readme
[x] добавить механизм обновления зависимостей через renovate
[X] [task management][amazing-github-template] добавить шаблоны issues
[X] [task management] добавить механизм создания pull requests на основе issues
[x] добавить автоматическое создание pull request для gitflow
[x] [semantic-release] добавить механизм обновления версии в gradle.properties
[x] [semantic-release] добавить генерацию CHANGELOG.md
[x] [semantic-release] организовать процесс выкатки релиза, чтобы его можно было
частично-перезапускать(idea)
[x] [semantic-release] добавить публикацию в docker hub
[ ] [semantic-release] добавить нотификации об удачном/сломанном релизе
[x] [test] добавить unit-tests и их вызов в CI
[ ] [test] добавить линтеры(idea)
[x] [license][test] добавить проверку лицензионных заголовков
[x] [license][gradle] добавить функцию автоматического задания лицензионных заголовков
[ ] [license][semantic-release] добавить генерацию LICENSES_THIRD_PARTY.txt
[x] [gradle] вынести зависимости в toml
[ ] [gradle] добавлять покрытие тестами jacoco
[x] [gradle] добавлять аналогию maven-enforcer-plugin
[ ] [gradle] проверять конфликты зависимостей
[ ] добавить docker-compose для локальных запусков

вместо maven-enforcer-plugin:

используется gradle toolchain для контроля версии jdk(без vendor)
используется gradlew для контроля версии gradle

необходимо добавить проверку конфликтов версий зависимостей

[semantic-release] организовать процесс выкатки релиза, чтобы его можно было
частично-перезапускать(https://github.com/semantic-release/semantic-release/discussions/2331):

реализовано посредством вынесения публикации артифакта из процессов semantic-release
теперь semantic-release job выполняет только публикацию релиза
далее по хуку публикации релиза вызывается job, в котором и происходит публикации артифакта

[license][semantic-release] добавить генерацию LICENSES_THIRD_PARTY.txt:

наличие файла LICENSES_THIRD_PARTY.txt избыточно, так как с точки зрения исходников информация есть в Dependency graph github-а
а для артифактов поставка данной информации описанна в readme

repo: xzima/gradle-semantic-release-example


text:
Add libyrs.dylib built for osx arm

Add libyrs.dylib for OSX ARM

Btw: For testing I would just reference this project from the unit tests (temporarily) and then run the tests.

@SebastianStehle
I used the .dylib file on my custom project and it worked, but for some reason if I add the native ARM project as a reference to the unit tests project, it still fails
This is how the project looks like:

Added this to YDotNet.Tests.Unit

Still failing when I run. Checking the bin folder, it doesn't contain the runtimes folder.

Perhaps this is the reason why it is called "PackagePath" ;)...So I guess we have to publish it. But you have to explain me the other changes in the yml file before I can merge it.

Regarding the yml file:
Here you can find a comment that directs to the other repository that contains a workflow file that was used as inspiration:
https://github.com/y-crdt/ydotnet/blob/070adb52dc73062295482f5fec5956a008f26b6f/.github/workflows/build-binaries.yml#L18
Going to the other repository, you can find how it builds for both Mac x64 and arm64
https://github.com/crodjer/sysit/blob/b03d0d4920ab43241d8e0976a5de3962b3bce016/.github/workflows/release.yml#L62-L71
I basically copied over the yaml config to my PR and adjusted the Content's Include and PackagePath accordingly to the new directories.

changed mac to macos-x86_64, so I modified the Include path to output\macos-x86_64 and the PackagePath to osx-x64
added macos-aarch64, so Include path to output\macos-aarch64 and PackagePath to osx-arm64

I am not entirely sure where the output\ folder is configured, but from what it seems the subfolder uses the name of the build step, hence why I use macos-x86_64 and macos-aarch64 for those

Ah, I see. aarch is just an arm variation. The point is: You cannot build for arm yet because there are not arm github runners yet. Therefore we have to build it locally and this is the reason why I cannot do it myself (because I do not have a mac).
So for now, we should:

Just keep the build process as is,.
In the current MacOS project file, use runtimes\osx-x64\native and target path to avoid confusion (but use the existing source file).
Add your binary to the repo.

When ARM runners are available we can make another PR.

@SebastianStehle from what I read online it is possible to build for ARM using the Intel image, so it should technically be possible.
If you want, we can test it, otherwise I can follow your approach!

That would be great. Can you confirm that? Just run the build in your fork and download the artifacts. If it works: Great :)
I agree with your argument about Mac and Linux project. I have forgotten that. Lets do one project again

@SebastianStehle it works! Just tried on my project and it worked well.

authors: SebastianStehle vdurante

repo: y-crdt/ydotnet


text:
🛑 Acosta Automation is down

In da0da07, Acosta Automation (https://acosta-automation.herokuapp.com/webhook/f85d7cd5-bb1f-482b-9162-b038582436de) was down:

HTTP code: 404
Response time: 18448 ms

Resolved: Acosta Automation is back up in 25fb379.


text:
Error while fetching metadata with correlation id 540 : {__consumer_offsets=UNKNOWN}

Hi,
I'm running kafka manger against my Kafka cluster and i'm getting a lot of the following error in the kafka manager log files:
[warn] o.a.k.c.NetworkClient - Error while fetching metadata with correlation id 540 : {__consumer_offsets=UNKNOWN}
[warn] o.a.k.c.p.Errors - Unexpected error code: 38.

I tried googling the following error and couldn't find any reason for it.
I tested the connectivity between the kafka manager to the zookeeper and brokers and the ports are open and i'm able to connect
Any ideas what i'm doing wrong?

Broker node must config /etc/hosts, as follows:

hostname
TIKY

sudo vi /etc/hosts
192.168.3.9 TIKY

Hey, I encountered the same error. kafka-manager correctly displays info about brokers etc, but I'm not sure if JMX is working and/or showing correct data so want to eliminate all possibilities.

Hi,
I'm running kafka manger against my Kafka cluster and i'm getting a lot of the following error in the kafka manager log files:
[warn] o.a.k.c.NetworkClient - Error while fetching metadata with correlation id 540 : {__consumer_offsets=UNKNOWN}
[warn] o.a.k.c.p.Errors - Unexpected error code: 38.

I tried googling the following error and couldn't find any reason for it.
I tested the connectivity between the kafka manager to the zookeeper and brokers and the ports are open and i'm able to connect
Any ideas what i'm doing wrong?

so   how to solve the problem ?

I have the same problem  now so i want the answer  thanks

authors: jack-ju koby-meir kub1x supervery

repo: yahoo/kafka-manager


text:
Support Kafka 2.0.0

Kafka 2.0 is out now: http://kafka.apache.org/downloads#2.0.0
Support for Kafka 2.0 in Kafka Manager would be great.

Yes.  Support for 2.0 would be awesome.

Yes please !

Any news here?

yes please!

+1

+1

+1

HI, Any update on this ... support for 2.0.0

please add this support!

+1

+1 Good to have.
I have configured  apache kafka 2.0 with kafka manager from master.  did not see any issue. It is working normally as 1.0 . In drop down when adding cluster to kafka manager doesn't show 2.0.

I have tested it and it works fine with kafka 2.0.

Am using Kafka 2.11-2.1.0 with 3 Zookeeper nodes and 3 Kafka Brokers with Kafka, Zookeeper, and Kafka Manager all deployed via Ansible. So far this manager seems to be working on it. It would just be nice to have another entry in the drop down.

Which version of kafka manager, can you please share docker compose file

authors: MarcusCaepio akthodu almike baineng balvey buehlmann johnzeng2010 juvlarN maitreyavvm r2vasylenko someshkandula tdixonspin thenralmani ttobba71 yluom


text:
Add in 1.0.0 and 0.11.0.2 as valid versions

The newest versions, both which came out in November, 2017: https://kafka.apache.org/downloads
I don't know if there are other compatibility changes that need to be made, but https://github.com/yahoo/kafka-manager/issues/451 implies that probably not.

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:

I signed the CLA

This test fail looks unrelated and seems to be a bug in 0.10.0.1?

@patelh I made this and tried to keep as close to https://github.com/yahoo/kafka-manager/pull/424 as possible. I didn't add 1.0.0 to Readme in case people find regressions?

it seems everything is ok? when will it be merged into master branch?

When will this be merged into the master?

Ran this locally and all seems fine. All tests passing as well. This resolves issue of "Sum of partition offsets" always 0 in #459 due to https://github.com/yahoo/kafka-manager/blob/master/app/kafka/manager/actor/cluster/KafkaStateActor.scala#L160
[info] TestClusterConfig:
[info] - invalid name
[info] - invalid kafka version
[info] - serialize and deserialize 0.8.1.1
[info] - serialize and deserialize 0.8.2.0 +jmx credentials
[info] - serialize and deserialize 0.8.2.0
[info] - serialize and deserialize 0.8.2.1
[info] - serialize and deserialize 0.8.2.2
[info] - deserialize without version, jmxEnabled, and security protocol
[info] - deserialize from 0.8.2-beta as 0.8.2.0
[info] - deserialize from 0.9.0.1
[info] - serialize and deserialize 0.10.0.0
[info] - serialize and deserialize 0.10.1.0
[info] - serialize and deserialize 0.10.1.1
[info] - serialize and deserialize 0.10.2.0
[info] - serialize and deserialize 0.10.2.1
[info] - serialize and deserialize 0.11.0.0
[info] - serialize and deserialize 0.11.0.2
[info] - serialize and deserialize 1.0.0
[info] ScalaTest
[info] Run completed in 2 minutes, 51 seconds.
[info] Total number of tests run: 155
[info] Suites: completed 16, aborted 0
[info] Tests: succeeded 155, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.
[info] Passed: Total 155, Failed 0, Errors 0, Passed 155
[success] Total time: 178 s, completed 09-Feb-2018 20:37:53```

authors: TheMonolithX64 icco nullne yahoocla yzang


text:
SyntaxError: Unexpected string in JSON at position 946

A JavaScript error occurred in the main process
Uncaught Exception:
SyntaxError: Unexpected string in JSON at position 946
at JSON.parse ()
at loadFromFile (/opt/yakyak/resources/app/node_modules/tough-cookie-filestore/lib/filestore.js:148:32)
at new FileCookieStore (/opt/yakyak/resources/app/node_modules/tough-cookie-filestore/lib/filestore.js:14:5)
at Client.module.exports.Client.doInit (/opt/yakyak/resources/app/node_modules/hangupsjs/lib/client.js:188:68)
at new Client (/opt/yakyak/resources/app/node_modules/hangupsjs/lib/client.js:102:12)
at Object. (/opt/yakyak/resources/app/main.js:49:12)
at Object. (/opt/yakyak/resources/app/main.js:591:4)
at Object. (/opt/yakyak/resources/app/main.js:595:3)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)

I'm having the same problem here.....
ry@mintLaptop ~ $ flatpak run com.github.yakyak.YakYak
Gtk-Message: Failed to load module "atk-bridge"
A JavaScript error occurred in the main process
Uncaught Exception:
SyntaxError: Unexpected token  in JSON at position 0
at JSON.parse ()
at loadFromFile (/app/lib/com.github.yakyak.YakYak/resources/app/node_modules/tough-cookie-filestore/lib/filestore.js:148:32)
at new FileCookieStore (/app/lib/com.github.yakyak.YakYak/resources/app/node_modules/tough-cookie-filestore/lib/filestore.js:14:5)
at Client.module.exports.Client.doInit (/app/lib/com.github.yakyak.YakYak/resources/app/node_modules/hangupsjs/lib/client.js:188:68)
at new Client (/app/lib/com.github.yakyak.YakYak/resources/app/node_modules/hangupsjs/lib/client.js:102:12)
at Object. (/app/lib/com.github.yakyak.YakYak/resources/app/main.js:49:12)
at Object. (/app/lib/com.github.yakyak.YakYak/resources/app/main.js:591:4)
at Object. (/app/lib/com.github.yakyak.YakYak/resources/app/main.js:595:3)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)

Yakyak fails with this error since a week ago
> yakyak
hconnect
reconnecting 0
resolving proxy http://plus.google.com
resolving proxy https://plus.google.com
resolved proxy DIRECT
resolved proxy DIRECT
connect_failed SyntaxError: Unexpected token <
    at Object.bind.out (/home/user/bin/yakyak-1.4.3/resources/app/node_modules/hangupsjs/lib/init.js:62:23)
    at /home/user/bin/yakyak-1.4.3/resources/app/node_modules/hangupsjs/lib/init.js:63:26
    at _fulfilled (/home/user/bin/yakyak-1.4.3/resources/app/node_modules/q/q.js:854:54)
    at self.promiseDispatch.done (/home/user/bin/yakyak-1.4.3/resources/app/node_modules/q/q.js:883:30)
    at Promise.promise.promiseDispatch (/home/user/bin/yakyak-1.4.3/resources/app/node_modules/q/q.js:816:13)
    at /home/user/bin/yakyak-1.4.3/resources/app/node_modules/q/q.js:877:14
    at runSingle (/home/user/bin/yakyak-1.4.3/resources/app/node_modules/q/q.js:137:13)
    at flush (/home/user/bin/yakyak-1.4.3/resources/app/node_modules/q/q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)
error connecting SyntaxError: Unexpected token <
    at Object.bind.out (/home/user/bin/yakyak-1.4.3/resources/app/node_modules/hangupsjs/lib/init.js:62:23)
    at /home/user/bin/yakyak-1.4.3/resources/app/node_modules/hangupsjs/lib/init.js:63:26
    at _fulfilled (/home/user/bin/yakyak-1.4.3/resources/app/node_modules/q/q.js:854:54)
    at self.promiseDispatch.done (/home/user/bin/yakyak-1.4.3/resources/app/node_modules/q/q.js:883:30)
    at Promise.promise.promiseDispatch (/home/user/bin/yakyak-1.4.3/resources/app/node_modules/q/q.js:816:13)
    at /home/user/bin/yakyak-1.4.3/resources/app/node_modules/q/q.js:877:14
    at runSingle (/home/user/bin/yakyak-1.4.3/resources/app/node_modules/q/q.js:137:13)
    at flush (/home/user/bin/yakyak-1.4.3/resources/app/node_modules/q/q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

Updated to 1.5.0 now, still the same:
hconnect reconnecting 0 resolving proxy http://plus.google.com resolving proxy https://plus.google.com resolved proxy DIRECT resolved proxy DIRECT connect_failed SyntaxError: Unexpected token <     at Object.bind.out (/Applications/YakYak.app/Contents/Resources/app/node_modules/hangupsjs/lib/init.js:62:23)     at /Applications/YakYak.app/Contents/Resources/app/node_modules/hangupsjs/lib/init.js:63:26     at _fulfilled (/Applications/YakYak.app/Contents/Resources/app/node_modules/q/q.js:854:54)     at self.promiseDispatch.done (/Applications/YakYak.app/Contents/Resources/app/node_modules/q/q.js:883:30)     at Promise.promise.promiseDispatch (/Applications/YakYak.app/Contents/Resources/app/node_modules/q/q.js:816:13)     at /Applications/YakYak.app/Contents/Resources/app/node_modules/q/q.js:877:14     at runSingle (/Applications/YakYak.app/Contents/Resources/app/node_modules/q/q.js:137:13)     at flush (/Applications/YakYak.app/Contents/Resources/app/node_modules/q/q.js:125:13)     at _combinedTickCallback (internal/process/next_tick.js:73:7)     at process._tickCallback (internal/process/next_tick.js:104:9) error connecting SyntaxError: Unexpected token <     at Object.bind.out (/Applications/YakYak.app/Contents/Resources/app/node_modules/hangupsjs/lib/init.js:62:23)     at /Applications/YakYak.app/Contents/Resources/app/node_modules/hangupsjs/lib/init.js:63:26     at _fulfilled (/Applications/YakYak.app/Contents/Resources/app/node_modules/q/q.js:854:54)     at self.promiseDispatch.done (/Applications/YakYak.app/Contents/Resources/app/node_modules/q/q.js:883:30)     at Promise.promise.promiseDispatch (/Applications/YakYak.app/Contents/Resources/app/node_modules/q/q.js:816:13)     at /Applications/YakYak.app/Contents/Resources/app/node_modules/q/q.js:877:14     at runSingle (/Applications/YakYak.app/Contents/Resources/app/node_modules/q/q.js:137:13)     at flush (/Applications/YakYak.app/Contents/Resources/app/node_modules/q/q.js:125:13)     at _combinedTickCallback (internal/process/next_tick.js:73:7)     at process._tickCallback (internal/process/next_tick.js:104:9)

authors: alfredodiaz hnilsen pi-c426 ryanbrate

repo: yakyak/yakyak


text:
displayName is not set for the component of "@yamada-ui/segmented-control"

script: component-display-name
package: @yamada-ui/segmented-control
Description
The component "@yamada-ui/segmented-control" uses forwardRef, but displayName is not set, making it difficult to see the display in React Developer Tools.
Additional Information
Set displayName and __ui__ after each component definition.
For example, like this.
const Component = forwardRef((props, ref) => {
  ...
})

Component.displayName = 'Component'
Component.__ui__ = 'Component'

Replace 'component' with the name of the component. For example, for a Select component, it is 'Select'.
__ui__ is an identifier required for internal use by Yamada UI. Be sure to set it together with displayName.

@cidkumagai
I have a question. DoesSegmentedControlCursor also need displayName and __ui__?

ty

repo: yamada-ui/yamada-ui


text:
Include checksums for yc binaries on YC CLI releases page

It would be much appreciated if you could include checksums for yc binaries for every architecture it's built on the releases page (and it's russian counterpart). This would facilitate building binary packages of yc in order to deploy it conveniently in environments where curl install.sh| bash is absolutely a non-starter. Not sure though it's a right channel for such requests to make, so feel free to close and ignore if it isn't.

Hello! Thank you for your feedback.
We will include checksums for yc binaries on release page from some point in future.
If it makes situation better, now you can pre-download install.sh, read it and understand that it is safe to run it on your environment, then run your downloaded copy. It just downloads "latest" yc  and set $PATH actually. Yes, there is no checksum validation, but by downloading binary by HTTPS, you may be confident , that what your get is exactly same binary, what we had released.
To track status of feature request, it's better to add request at https://cloud.yandex.ru/features or send request to support.
This issue is not related to current repository, so we will close it.

authors: antonalekseev skipor

repo: yandex-cloud/docs


text:
Can't build ClickHouse on mac 10.14

When following instructions, after running ninja the build fails with:
...
In file included from ../dbms/src/Core/Row.h:6,
                 from ../dbms/src/DataStreams/GraphiteRollupSortedBlockInputStream.h:5,
                 from ../dbms/src/DataStreams/GraphiteRollupSortedBlockInputStream.cpp:1:
../dbms/src/Core/Field.h: In instantiation of 'decltype(auto) DB::nearestFieldType(T&&) [with T = long int&]':
../dbms/src/Core/Field.h:630:35:   required from 'DB::Field::Field(T&&, std::enable_if_t<(! is_same_v<typename std::decay<_Tp>::type, DB::Field>), void*>) [with T = long int&; std::enable_if_t<(! is_same_v<typename std::decay<_Tp>::type, DB::Field>), void*> = void*]'
../dbms/src/DataStreams/GraphiteRollupSortedBlockInputStream.cpp:254:65:   required from here
../dbms/src/Core/Field.h:613:63: error: invalid use of incomplete type 'struct DB::NearestFieldType<long int>'
     using U = typename NearestFieldType<std::decay_t<T>>::Type;
                                                               ^
../dbms/src/Core/Field.h:581:30: note: declaration of 'struct DB::NearestFieldType<long int>'
 template <typename T> struct NearestFieldType;
                              ^~~~~~~~~~~~~~~~
[769/3289] Building CXX object dbms/CMakeFiles/dbm...r/src/DataStreams/IProfilingBlockInputStream.cpp.o
ninja: build stopped: subcommand failed.

I'm building from master and according to cmake it's ClickHouse 18.14.9.

Same problem

fix : https://github.com/yandex/ClickHouse/pull/3545/files#diff-bc4722bf5d3b20b34d99c8dfb48f87f7R588

@proller
Tried to build from PR same issue in a different place ```
In file included from ../dbms/src/DataTypes/IDataType.h:6,
from ../dbms/src/Core/NamesAndTypes.h:9,
from ../dbms/src/Interpreters/Context.h:16,
from ../dbms/src/Interpreters/DDLWorker.h:2,
from ../dbms/src/Interpreters/DDLWorker.cpp:1:
../dbms/src/Core/Field.h: In instantiation of 'decltype(auto) DB::nearestFieldType(T&&) [with T = long unsigned int]':
../dbms/src/Core/Field.h:633:35:   required from 'DB::Field::Field(T&&, std::enable_if_t<(! is_same_v<typename std::decay<_Tp>::type, DB::Field>), void*>) [with T = long unsigned int; std::enable_if_t<(! is_same_v<typename std::decay<_Tp>::type, DB::Field>), void*> = void*]'
../dbms/src/Interpreters/DDLWorker.cpp:1071:77:   required from here
../dbms/src/Core/Field.h:616:63: error: invalid use of incomplete type 'struct DB::NearestFieldType'
using U = typename NearestFieldType<std::decay_t>::Type;
^
../dbms/src/Core/Field.h:581:30: note: declaration of 'struct DB::NearestFieldType'
template  struct NearestFieldType;
^~~~~~~~~~~~~~~~
[987/3289] Building CXX object dbms/CMakeFiles...bms.dir/src/Dictionaries/CacheDictionary.cpp.o
ninja: build stopped: subcommand failed.

Fixed and tested and commited:
https://github.com/yandex/ClickHouse/commit/bb1dafd2b32a3fad288f0d31c0d45d6cdea44f4a
https://github.com/yandex/ClickHouse/commit/9a98b80cf8eafba1ada1baf565d5a1d7bfb93cd5

Relates #235

authors: aleh-null filimonov proller trK54Ylmz

repo: yandex/ClickHouse


text:
Add RPM builder from Altinity

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

Postinstallation scripts should use common code with debian packages, rather than copy paste.
Spec file should be placed inside the repo rather than submodules.
debian and rpm directories should be moved inside new directory packages.
Only minimal number of libraries should be installed for build (currently it is readline and icu).

This PR is just an example (not ready for merge).

authors: alexey-milovidov sunsingerus


text:
[wip] Enable 'input_format_defaults_for_omitted_fields' by default

Category (leave one):

Backward Incompatible Change

Short description (up to few sentences):
The setting input_format_defaults_for_omitted_fields is enabled by default. It enables calculation of complex default expressions for ommitted fields in JSONEachRow format. It should be the expected behaviour but may lead to neglible performance difference or subtle incompatibilities.
Detailed description (optional):
In continuation of #5641

It needs fix for
10: 00933_ttl_with_default:                                                 [ FAIL ] - return code 62
10: Error on processing query: insert into ttl_00933_2 values (toDateTime('2000-10-10 00:00:00'), 2);
10: Code: 62, e.displayText() = DB::Exception: Syntax error (column parser): failed at position 38: AS a    TTL d + toIntervalDay(1). Expected one of: LIKE, CODEC, GLOBAL NOT IN, IS, OR, QuestionMark, BETWEEN, NOT LIKE, AND, TTL, IN, NOT, COMMENT, token, NOT IN, GLOBAL IN, Stack trace:

Perf test:
Cannot write to file /var/lib/clickhouse/data/default/table_MySQLWire/data.MySQLWire,
errno: 28, strerror: No space left on device.


text:
Nullable columns issues

While querying a table with nullable columns from Tableau using 11-07 build I have Syntax error. The query is
select platforms from gamora.params where platforms is null limit 1
Tableau wraps it and generates the following query:
SELECT `Custom_SQL_Query`.`platforms` AS `platforms`
FROM (
  select platforms from gamora.params where platforms is null limit 1
) `Custom_SQL_Query`
GROUP BY `platforms`

that leads to the error. The query is OK and according to Wireshark dump CH replues HTTP OK with data.
:) SELECTCustom_SQL_Query.platformsASplatforms    FROM (       select platforms from gamora.params where platforms is null limit 1     )Custom_SQL_Query    GROUP BYplatforms`
SELECT Custom_SQL_Query.platforms AS platforms
FROM (
select platforms
from gamora.params
where platforms is null
limit 1
) Custom_SQL_Query
GROUP BY platforms
┌─platforms─┐
│        \N │
└───────────┘
Ok. 1 row in set. Elapsed: 0.017 sec. Processed: 0.0  rows, 0.0B (0.0  rows/s, 0.0B/s)
`
`show create table gamora.params
CREATE TABLE gamora.params ( user_id Int64,  date Date,  dt DateTime,  p1 Nullable(Int32),  platforms Nullable(Int32),  max_position Nullable(Int32),  vv Nullable(Int32),  city Nullable(String),  third_party Nullable(Int8),  mobile_tablet Nullable(Int8),  mobile_phone Nullable(Int8),  desktop Nullable(Int8),  web_mobile Nullable(Int8),  tv_attach Nullable(Int8),  smart_tv Nullable(Int8),  subsite_id Nullable(Int32),  view_in_second Nullable(Int32),  view_in_second_presto Nullable(Int32)) ENGINE = MergeTree(date, user_id, 8192)
`

+1

Problem still actual? (on latest version of clickhouse and odbc driver)

It is still relevant.

Tried the following with the latest release of the ODBC driver (v1.1.1.20191108):
> clickhouse-client --query "CREATE TABLE nullable_col_issue_tbl ( nullable_col Nullable(Int32) ) ENGINE = Memory"
> clickhouse-client --query "INSERT INTO nullable_col_issue_tbl VALUES ( NULL )"
> clickhouse-client --query "SELECT nullable_col from nullable_col_issue_tbl WHERE nullable_col IS NULL LIMIT 1"
\N

then executed that same SELECT query in Tableau in Windows, and got this:

Please close this issue, if the above can be considered an indication that this issue is fixed, at least starting v1.1.1.20191108.

authors: MaximKhorev aadim alexey-milovidov proller traceon

repo: yandex/clickhouse-odbc


text:
🛑 Google is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Google is back up in fc50ed4.

repo: yangchuansheng/upptime


text:
🛑 Google is down

In 1c38c30, Google (https://google.icloudnative.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Google is back up in de71d6f.


text:
🛑 Google is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Google is back up in 8f40d8a.


text:
🛑 Google is down

In 08f0aa6, Google (https://google.icloudnative.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Google is back up in 8699228 after 13 minutes.


text:
🛑 Privatebin is down

In ebe26a2, Privatebin (https://privatebin.icloudnative.io) was down:

HTTP code: 503
Response time: 5485 ms

Resolved: Privatebin is back up in e7dff26.


text:
请教一个代码问题

请问代码下下来有哪里需要改吗？代码没有报错，但是运行会有问题

The Python AttributeError: 'str' object has no attribute 'read' error occurs when you try to utilize or access the read() method or attribute on a string object. The read() method is commonly employed for reading content or data from a file object and is not intended for use with strings.
Here are the typical causes of this error:
Direct File Content Reading: This error occurs when trying to read file content directly using the read() method on a filename string object.
Using the JSON Built-in Library: The error can also arise when attempting to load file data using json.load() without first opening the file.
官方解释，错误 AttributeError: 'str' object has no attribute 'read' 通常发生在编程中，当您试图对实际上是字符串类型的对象使用 read 方法时，该对象没有 read 方法。这个问题经常出现在文件处理情况或使用 Python 中的流时。检查下变量的类型


text:
function template(tpl, data)

function template(tpl, data)点击分页再次调用这个方法， tpl是undefined这个应该如何处理？

很抱歉，我不是太明白

页面初次加载有数据，然后我ajax请求再绑定的时候模板就是undefinde了，然后我就搞成只要是undefinde的时候就给它吧tpl赋值。
function template(tpl, data,tplval) {         if (typeof tpl !== 'string') {             if(tplval==="producttpl")             {                 tpl=producttmp();             }         }         var fn = compile(tpl);         if (!isObject(data)) {             return fn;         }         return fn(data);     }     function producttmp() {         return '<%for (var i = 0; i < list.length; i++) {%>'             +'<%var percentvalue = percent(list[i].bidTotal,list[i].available);%>'             +'
'             +'<%:=list[i].bidName%>	'            ....             +'立即	'             +'
'             +'<%}%>';     }

tplval 这个是你自己改了源代码吗？

恩

authors: sjzjams yanhaijing


text:
New Logo/Icon and Minor layout changes in README.md

#1 Created icon for the issue

If you would like any changes, let me know.

Hey @udz-codes this looks great, but I think we can tweak the color a little bit. How about we switch the colors of clock and globe and use pastel colors which are a bit dimmed.

Hey @udz-codes this looks great, but I think we can tweak the color a little bit. How about we switch the colors of clock and globe and use pastel colors which are a bit dimmed.

Okay, and what do you think about it's background. Does that need any tweaking ?

Hey @yankeexe , Here are 2 variants of with changes you suggested. Tell me which one do you like, I will make pull request wirh that one.
1. With thicker grid in background and pastel colors.

2. Without background grid.

hey @udz-codes  I think I the non-grid looks great, you can send PR with that 🙂
Thank you for your contribution. 🙏

authors: udz-codes yankeexe

repo: yankeexe/timezones-cli


text:
Support multiline configuration for jsx-equals-spacing

I think it's desirable to have different jsx-equals-spacing config for single and multiple lines, similar to key-spacing.
For example, I'd like this to treated as correct:
<PanelBody title={ __( 'Which Speakers?', 'wordcamporg' ) } initialOpen={ true }>
	<PanelRow>
		<CheckboxControl
			label    = { __( 'Show all', 'wordcamporg' ) }
			checked  = { show_all_posts }
			onChange = { ( value ) => setAttributes( { show_all_posts: value } ) }
		/>
	</PanelRow>
</PanelBody>

When the element's attributes are on a single line, there should be no spaces around the =, but when they are on multiple lines, there should be at 1 space after the =, and 1+ spaces before the = so that the = are aligned.
Currently, I don't see any way to achieve that; it's either all or nothing.

This style of alignment, while common in other languages, is wildly unidiomatic and uncommon for JS. Can you point to any popular style guides where this is common?
Separately, if the multi line example is going to force at least 1 space around the =, then I’d expect the single-line example to do the same. Alignment, obviously, would only apply when multiline.

Alright, sounds like I'll need to write a plugin. Thanks.

authors: iandunn ljharb

repo: yannickcr/eslint-plugin-react


text:
:bug: webhooks: project v2 item change may be labels

According to the webhook events we're getting sent by github, the changed field_type can be "labels" as well, but this doesn't seem to be covered by the octokit schema.
As an example, take the following snippet:
"action": "edited",
    "projects_v2_item": {
      "id": 12345,
      "node_id": "PVTI_ASDASD",
      "project_node_id": "PVT_ASDASD",
      "content_node_id": "I_ASDASD",
      "content_type": "Issue",
      "creator": {
        "login": "jecluis",
        [...]
      },
      "created_at": "2023-12-18T06:44:23Z",
      "updated_at": "2023-12-18T16:21:38Z",
      "archived_at": null
    },
    "changes": {
      "field_value": {
        "field_node_id": "PVTF_ASDASD",
        "field_type": "labels"
      }
    },

Signed-off-by: Joao Eduardo Luis <joao@1e3ms.io>

it seems this field value is not documented in the webhook types... But, the latest openapi description mark this field as simple string instead of enum. I'm working on migrate the codegen to using the openapi instead of octokit #67 . just make a fix currently 🤔 .

Fixes applied, sorry for the silly mistake. Thanks @yanyongyu !

authors: jecluis yanyongyu

repo: yanyongyu/githubkit


text:
Excellent work

Excellent work. I want to know if there is a result with an input size 256x704, backbone resnet50, and history frames 8

Hi Chuandong,
Thank you for your interest in our work. Unfortunately, we only have 3090/4090 GPUs with 24GB memory, which do not support training with 8 history frames. However, you might be able to try it if possible.

Hi Chuandong,
Thank you for your interest in our work. Unfortunately, we only have 3090/4090 GPUs with 24GB memory, which do not support training with 8 history frames. However, you might be able to try it if possible.

Thank you very much.


text:
Start with name="[1]"

Is there a way for the name & ID increment to start with [1] ?

No currently cloneya not supporting that, but if you really wants that use the cloneya events to redo the id  and names.

authors: ChaseGiunta gchokeen

repo: yapapaya/jquery-cloneya


text:
httpflv使用问题

使用httpflv进行播放的时候，通过<-request.Context().Done()方法获取到客户端在播放结束前关闭了当前链接，此时http处理方法返回会导致panic
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x1110196]
goroutine 12 [running]:
bufio.(*Writer).Flush(0xc00007ea40)
/sdk/go1.17/src/bufio/bufio.go:607 +0x56
bufio.(*Writer).Write(0xc00007ea40, {0xc00025e000, 0xc00025e000, 0xc000028d75})
/sdk/go1.17/src/bufio/bufio.go:643 +0xd8
net/http.(*response).write(0xc000152380, 0x90a, {0xc00025e000, 0x90a, 0xa80}, {0x0, 0x0})
/sdk/go1.17/src/net/http/server.go:1592 +0x21e
net/http.(*response).Write(0x0, {0xc00025e000, 0x1052306, 0x1064be0})
/sdk/go1.17/src/net/http/server.go:1550 +0x30
github.com/yapingcat/gomedia/go-flv.(*FlvWriter).writeVideo(0xc00000ec18, {0xc000233b00, 0xc000257d80, 0x10601ce}, 0x87b20a44, 0xc7c)
/Desktop/gopath/pkg/mod/github.com/yapingcat/gomedia@v0.0.0-20230222121919-c67df405bf33/go-flv/flv-file.go:373 +0x9f
github.com/yapingcat/gomedia/go-flv.(*FlvWriter).WriteH264(0x989680, {0xc000233b00, 0xc000544230, 0x0}, 0x4bfb, 0x4bfb)
/Desktop/gopath/pkg/mod/github.com/yapingcat/gomedia@v0.0.0-20230222121919-c67df405bf33/go-flv/flv-file.go:354 +0x155
是否可以在flvwriter增加一个writer是否已关闭的判断，或者手动关闭的方法？

目前gomedia不管理网络连接，连接交由调用方来管理
针对这个问题，可以把http.ResponseWriter封装一下，在封装的接口里面实现上述的逻辑判断
类似下面这个简单实现
type HttpWriterWrapper struct {
	closed    chan struct{}
	w         http.ResponseWriter
	sendChan  chan []byte
	die       chan struct{}
	lastError error
	once      sync.Once
}

func NewHttpWriterWrapper(w http.ResponseWriter, closed chan struct{}) *HttpWriterWrapper {
	return &HttpWriterWrapper{
		closed:   closed,
		w:        w,
		sendChan: make(chan []byte, 100),
		die:      make(chan struct{}),
	}
}

func (w *HttpWriterWrapper) Start() {
	go w.writeImpl()
}

func (w *HttpWriterWrapper) Stop() {
	w.once.Do(func() {
		close(w.closed)
	})
}

func (w *HttpWriterWrapper) Write(b []byte) (int, error) {
	if w.lastError != nil {
		return 0, w.lastError
	}
	w.sendChan <- b
	return len(b), nil
}

func (w *HttpWriterWrapper) writeImpl() {
	for {
		select {
		case <-w.closed:
			// reset connection by client
			// stop send
			// release some resource
			w.lastError = io.EOF
			break
		case b := <-w.sendChan:
			_, w.lastError = w.w.Write(b)
		case <-w.die:
			w.lastError = errors.New("closed by custom")
			return
		}
	}
}

repo: yapingcat/gomedia


text:
dropout_regularizer

In the paper,  entropy of a Bernoulli random variable is
H(p) := -p * log(p) - (1-p) * log(1-p)
But in the code,  dropout_regularizer was computed by
dropout_regularizer = self.p * K.log(self.p)
dropout_regularizer += (1. - self.p) * K.log(1. - self.p)
dropout_regularizer *= self.dropout_regularizer * input_dim
Could you please explain the meaning of the dropout_regularizer *= self.dropout_regularizer * input_dim. I cannot find  related equation of this code in your paper.
Thanks for your kind help in advance.

I believe this is for scaling the lambda by the output shape, before applying it.
However I think @yaringal is the only one who can properly answer this.
Whilst re-reading the code I noticed the comment above input_dim mentions ignoring the final dimension yet slices to ignore the first dim? - is the comment or code wrong?

Normal dropout upscales the feature vector by 1/(1-p) after dropping out units. We do the same, substituting W'=W/(1-p) into the model and KL calculations.
Y

authors: XinDongol joeyearsley yaringal

repo: yaringal/ConcreteDropout


text:
Alignment problem for CJK characters.

Hi,
Thanks for the great work!
However, the alignment samed to be not that good for CJK characters, even if I set { fullUnicode:true } for blessed, maybe wcwidth.js will help ?

columnify use  wcwidth.js and it works well for CJK characters:

repo: yaronn/blessed-contrib


text:
closes: #355

fix: fixed issue where null characters in the middle of a string would cut the string short on echo.

Have you tried running all tests locally? tests.sh is the script for this. There's also a -m option to toggle whether you want to run them with valgrind enabled.
I suspect you've got a memory problem somewhere, but hard to tell just by looking at your code.

Can I assume built-ins v->on_heap == false safely?

locally all tests passed the remaining errors are about msvc and c++ complaining about linking symbols

That's not a safe assumption, on_heap tells where the memory for the string was allocated (depending on creation, e.g. from the C API, dynamically at runtime, from a YASL string literal, etc). it shouldn't be relied on for this sort of stuff, even tho in this case it seems to be fine.
Also, your CL is modifying the string in place, which it should not do (strings should be immutable in YASL).
Consider the following:
const x = 'abc\0def'

echo len x

echo x

echo len x

This should print 7 for the length of x both times, but the second time it prints 6 under your CL, because the string has been modified. (Slicing the string also shows a similar problem, where the substring is from the indices based on what x was originally.)

That's not a safe assumption, on_heap tells where the memory for the string was allocated (depending on creation, e.g. from the C API, dynamically at runtime, from a YASL string literal, etc). it shouldn't be relied on for this sort of stuff, even tho in this case it seems to be fine.
Also, your CL is modifying the string in place, which it should not do (strings should be immutable in YASL).
Consider the following:
const x = 'abc\0def'

echo len x

echo x

echo len x

This should print 7 for the length of x both times, but the second time it prints 6 under your CL, because the string has been modified. (Slicing the string also shows a similar problem, where the substring is from the indices based on what x was originally.)

I have adjusted the code to allocate a buffer to keep the old string immutable, ensuring it passes the tests now

authors: CoffeeTableEspresso DarthUdp

repo: yasl-lang/yasl


text:
chore: v1.0.0-beta.16 release

fix: use unjs/pathe to resolve cross OS public path

update dependencies

fixes #105

Codecov Report
Base: 99.87% // Head: 99.87% // No change to project coverage :thumbsup:

Coverage data is based on head (aabb5dc) compared to base (aaf0583).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             beta     #112   +/-   ##
=======================================
  Coverage   99.87%   99.87%
=======================================
  Files           4        4
  Lines         788      788
  Branches      140      140
=======================================
  Hits          787      787
  Misses          1        1

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 at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: codecov-commenter yassinedoghri


text:
Remove composer.lock and add it to the gitignore

In a library the dependencies shouldn't be locked. It makes updates in projects or libraries using this library more complicated.

Thanks @chapterjason

authors: chapterjason yceruto

repo: yceruto/micro-symfony


text:
Does your PHOENIX-2014-T dataset have /1/ folder?

After download dataset, I got manual annotations in PHOENIX-2014-T.dev.corpus dataset like this:
name|video|start|end|speaker|orth|translation
11August_2010_Wednesday_tagesschau-2|11August_2010_Wednesday_tagesschau-2/1/*.png|-1|-1|Signer08|DRUCK TIEF KOMMEN|tiefer luftdruck bestimmt in den nﾃ､chsten tagen unser wetter
But in features, I cant see /1/ folder.

The released code is based on Phoenix14, you can modify the data format according to your requirements.


text:
Support duplicate column names in SDKs

For prevent customer unexpected issues after https://github.com/ydb-platform/ydb/issues/3553
If result has duplicate column names and user access to one of them by name - SK must return error.
If user access to the column by index, or access to other columns (without name duplications) - sdk must work fine.

[ ] https://github.com/ydb-platform/ydb-go-sdk/issues/1204
[ ] https://github.com/ydb-platform/ydb-python-sdk/issues/419
[ ] https://github.com/ydb-platform/ydb-java-sdk/issues/261
[ ] https://github.com/ydb-platform/ydb/issues/3886
[ ] https://github.com/ydb-platform/ydb-php-sdk/issues/138
[ ] https://github.com/ydb-platform/ydb-nodejs-sdk/issues/376
[ ] https://github.com/ydb-platform/ydb-dotnet-sdk/issues/74
[ ] https://github.com/ydb-platform/ydb-rs-sdk/issues/194

Why we must return error? It brokes some conversations like JDBC standard. From here Column names used as input to getter methods are case insensitive. When a getter method is called with a column name and several columns have the same name, the value of the first matching column will be returned.

It's worth to discus.  Since currently i.e. NodeJS SDK has no mechanism to fetch columns by index at all.  As a solution, we could think about adding an index to the column name if the name is duplicated

Why we must return error? It brokes some conversations like JDBC standard.

This behavour will be at server queries and it is safest way - we always can start to support duplicated names, but it is difficult to change behavior.
may be reaction way need more research.
Main idea was:

Now we don't support duplicated names on server side
We will support duplicated names on server side in results
Safest way - deny use unexpected column

Our API has always supported the columns with any names, including duplicated. So these is no difference - does server support it or doesn't, the SDKs have to support it already. The only think we have to decide - the behavior of various SDKs must be equal. I checked Java SDK and it returns the last matching column - but it seems very as non conversational behavior. What about others SDK?

I think about it will be better to sync not only SDK, but server too - for have same behaviour of SDK and YQL/SQL.

repo: ydb-platform/ydb


text:
我的searchBar与你的例子还是有一定的差别

我是将searBar放在了tableHeadView里，使用refreshcontrol下拉或者上拉后，searchbar位置就会被推到顶部无法显示了。实际上其他的scrollview也存在这个问题，也就是刷新后refreshcontrol计算的位置不正确。
感觉上是没有考虑nav所占的高度。
但我不会Oc，所以我在refreshdelegate中添加了一个fixRefresh以修正这个问题，使用swift来完成
在controller中实现
func fixRefresh(){
var f = view.frame
if let n = self.navigationController?.navigationBar.frame {
f.origin.y = n.height + n.origin.y
}
view.frame = f
}
在finish中调用
if ([self.delegate respondsToSelector:@selector(fixRefresh)])
{
[_delegate fixRefresh];
}

如果你oc实现上面的代码应该就更完善了

怎么现在不支持uiwebview?

let rc = RefreshControl(scrollView: webView, delegate: self) 报错，编译不通过

RefreshControl是支持tableview有tableHeaderview的情况，你可以看一下demo；
另，webview支持下拉刷新，需要传递 webview.scrollView属性，而不是webview

嗯，这个我发现了，就是关于nav高度的问题 不知能解决否

请查考，demo里面tableHeader的情况，demo中都是push到每个子页的，带有Navigation

我在xcode 6.3.2中新建 swift工程使用确定位置不正确
测试工程位置 https://github.com/miws/testRC
麻烦你看看吧

在你的tableController类里面，viewDidLoad方法添加        self.navigationController?.navigationBar.translucent=false;

谢谢，这样真的可行，但navigationbar默认好像不是透明的吧，为什么这里要显示地指定呢

这个分好多情况，默认是透明的，加上图片默认就变成不透明的了，你也可以再进行设置，这些都是布局的问题

authors: miws ydj

repo: ydj/RefreshControl


text:
Error after source code python 3 install

I get this after running the install sh and starting the env and run "python mac_apt.py -h"
Traceback (most recent call last):
File "mac_apt.py", line 23, in
import plugins.helpers.macinfo as macinfo
File "/Users/examiner/Desktop/mac_apt/mac_apt/plugins/helpers/macinfo.py", line 26, in
from plugins.helpers.hfs_alt import HFSVolume
File "/Users/examiner/Desktop/mac_apt/mac_apt/plugins/helpers/hfs_alt.py", line 29, in
from plugins.helpers.btree import AttributesTree, CatalogTree, ExtentsOverflowTree
File "/Users/examiner/Desktop/mac_apt/mac_apt/plugins/helpers/btree.py", line 18, in
from plugins.helpers.structs import *
File "/Users/examiner/Desktop/mac_apt/mac_apt/plugins/helpers/structs.py", line 185, in
"unicode" / PaddedString(lambda ctx: ctx["length"] * 2, encoding="utf-16-be") # "unicode",
NameError: name 'PaddedString' is not defined

Try upgrading to latest version of Construct

As pointed by Jack, this is due to a recent code update to update to the newer version of Construct library.
I just updated the Wiki installation page to reflect the new version of construct. Latest (2.9.45) works just fine.
pip install construct --upgrade should fix it.

Thanks guys!

Hello!!
I have updated construct with pip3 install construct --upgrade, but I still have "NameError: name 'PaddedString' is not defined"
What could I do now?

I just tested this with latest construct and did not get any problems.
Are you in the python virtual environment ? It is likely that you have installed this in the virtual env and then you are trying to use mac_apt  outside that environment, hence it is not seeing the upgrade. Or perhaps it is the other way around. Just ensure that wherever you installed construct is the same as where you are running mac_apt.

This prompt jump out when I run the installing script too.
Do you mean run pip install construct --upgrade outside the virtual env or in it?
I tried both, finnaly got the  latest version of construct is (2.10.56)outside, but a upgrade process inside.
After I run construct upgrade inside, the error about  'PaddedString' gone. However, when I run python mac_apt ..., it tell me No module named 'xxxx', i am sure i am in the mac_apt env.

This prompt jump out when I run the installing script too.
Do you mean run pip install construct --upgrade outside the virtual env or in it?
I tried both, finnaly got the latest version of construct is (2.10.56)outside, but a upgrade process inside.
After I run construct upgrade inside, the error about 'PaddedString' gone. However, when I run python mac_apt ..., it tell me No module named 'xxxx', i am sure i am in the mac_apt env.

Everything should be inside the virtual env. Instead of version 2.10, try using 2.9.45
Do this inside your virtual env:
pip uninstall construct
pip install construct==2.9.45

This is the recommended version. Follow the instructions on wiki here:
https://github.com/ydkhatri/mac_apt/wiki/Installation-for-Python3.7#macos-osx
I also updated the install script there which should do this automatically.

This prompt jump out when I run the installing script too.
Do you mean run pip install construct --upgrade outside the virtual env or in it?
I tried both, finnaly got the latest version of construct is (2.10.56)outside, but a upgrade process inside.
After I run construct upgrade inside, the error about 'PaddedString' gone. However, when I run python mac_apt ..., it tell me No module named 'xxxx', i am sure i am in the mac_apt env.

Everything should be inside the virtual env. Instead of version 2.10, try using 2.9.45
Do this inside your virtual env:
pip uninstall construct
pip install construct==2.9.45

This is the recommended version. Follow the instructions on wiki here:
https://github.com/ydkhatri/mac_apt/wiki/Installation-for-Python3.7#macos-osx
I also updated the install script there which should do this automatically.
Just ensure that you are also trying to start mac_apt inside the virtual env. This is indicated on the terminal with a  (env) in the far left of the terminal prompt (on every line).
Edit: I just tested latest version 2.10.56, and it will work too.

I thought there are some dependencies missing in v16.
Just tested the v17 script, it worked everthing correctly. Thank you.

Yes, the v16 script did not have all the dependencies as the code now requires more due to some newer plugins that were added recently. Thanks for testing v17 install script.


text:
Keep3r Jobs Migration + Ongoing Maintenance

Scope
Migration of Yearn jobs from KP3R v1 to v2 + ongoing maintenance that includes:

LP credits management
alerts for potential job errors
MEV monitoring
job performance monitoring (check if keepers are working yearn’s jobs, and if not, work them with our own keeper)

Plan
Migrating Keep3r Jobs from V1 to V2 is the main priority and will be done ASAP.
The ongoing tasks will be performed for 12 months from the starting date.
Deadline
6/6/2023
People
DeFi Wonderland
Money
The budget requested will be spent on the development of the jobs and ongoing support/monitoring for the jobs developed by us.
Amount
435000 DAI
Wallet address
0x45fEEBbd5Cf86dF61be8F81025E22Ae07a07cB23
Reporting

[X] I agree to post weekly updates

Thanks for filling out the request. Would you be open to receive this as a stream?

Thanks for filling out the request. Would you be open to receive this as a stream?

Yes, we've already reviewed and experimented with LlamaPay ourselves, so we are confident about the security of the product

Stream of 36,250 DAI/month created:

https://ethtx.info/mainnet/0x4fa67cd76454147ef697670ecfb6a1d5cc6077ab8f248ee9361d1d5f7dd19642/
https://llamapay.io/streams?chainId=1&address=0x45feebbd5cf86df61be8f81025e22ae07a07cb23

To keep this updated: The stream was modified by our request to 0x8bA72884984f669aBBc9a5a7b441AD8E3D9a4fD3
https://llamapay.io/salaries/Ethereum/0x8bA72884984f669aBBc9a5a7b441AD8E3D9a4fD3

A new stream has been agreed upon:
Start date: June 8th 2023
Duration: 6 months
Amount: 15,000 DAI per month

The new stream should be paid to 0xf58e95124d655731664c509C07E733348d7081c0

authors: 0xGorilla banteg vPEPO

repo: yearn/budget


text:
Add 0.4.3 version of smart contracts

Right now we only have 0.4.2. It'd be great to have 0.4.3

Not sure if I am running vydoc correctly, only outputs when are vault.md and registry.md files when running:
vydoc -i contracts -o docs -c vyper -f markdown
@pandadefi is this what should happen?

Yes only two files are vyper files

You must generate the solidity doc using yarn

authors: pandadefi saltyfacu

repo: yearn/yearn-devdocs


text:
Type hints for ast.py

I guess adding type hints can help using developing/debugging. For example: I was not clear to me what is tlist.
def ahf(tlist) -> int:
    """Ratio of private/protected attributes to all attributes in a class.
    :rtype: float
    """
    declaration = tlist[0][1].filter(javalang.tree.FieldDeclaration)
    fields = list(field for field in declaration)
    hidden = 0
    total = 0
    for path, node in fields:
        del path
        if 'private' in node.modifiers or 'protected' in node.modifiers:
            hidden += 1
        total += 1
    if total == 0:
        return 0
    return hidden / total

Suggestion:
def ahf(tlist: list[tuple[javalang.tree.ClassDeclaration]]) -> int:

@yegor256 can you approve this as an issue?

@ilnarkhasanov sure, let's do this

I have started working on this issue

@yegor256 I have added #176 as a solution of this issue. Can you check it please?


text:
:white_check_mark: Authentication gefixed

Ik heb de Issue van /like gefixed!

Goed bezig, lekker snel ook👀

Dat is snel haha, goed bezig!

authors: Inevdhoven ybouz2 yelizerbas

repo: yelizerbas/boekenzoeker


text:
Select is returning a stale value

Not sure if this is a misuse of generators or is this a real bug in sagas, but we have encountered some weird behaviour in code like this:
function* startSomething()  {
    yield call(updateDataForAdditional);
    const features = yield select(selectFeatures);
    const needMore = yield select(selectAdditional);

    if (needMore || features.length > 0) {
      if (needMore) {
        features.push('MORE'); // (*)
      }
      yield put(enableFeatures(features));
    }
    yield put(somethingStarted())
  }
}

function* watchStartSomething() {
  while (true) {
    yield take("START_SOMETHING_TRIGGERED");
    yield call(startSomething);
  }
}

Here selectFeatures selector cannot return 'MORE'. What we observe however is that the select does do that on the second execution of startSomething, after the first execution has executed line '*'.
Are we misusing generators somehow here?

I guess you are mutating the features with push. With const features = yield select(selectFeatures); you are grabbing the reference to some nested object in your state and then you are mutating its content so it gets updated in state too, so when you grab it again on the second run of startSomething you are geting mutated result and you will probably just push to it again so those MORE will just pile up in your state.
I would suggest to const [...features] = yield select(selectFeatures)

I'm not sure this is the case. The value returned by selectFeatures is returning a copy of ImmutableJS Seq converted to a native array with toJS. Also, selectFeatures cannot return 'MORE' in any circumstance. The behaviour is somewhat surprising, unless you consider the generated code (Babel's take below), where the reference of features is declared outside the generator body.
I haven't yet dug into how sagas step the generators here, but if there is a programming error on my part here, I cannot still determine what it is.
function startSomething() {
  var features, needMore;
  return regeneratorRuntime.wrap(function startSomething$(_context) {
    while (1) {
      switch (_context.prev = _context.next) {
        case 0:
          _context.next = 2;
          return select(selectFeatures);

        case 2:
          features = _context.sent;
          _context.next = 5;
          return select(selectAdditional);

        case 5:
          needMore = _context.sent;

          if (!(needMore || features.length > 0)) {
            _context.next = 10;
            break;
          }

          if (needMore) {
            features.push('MORE');
          }
          _context.next = 10;
          return put(enableFeatures(features));

        case 10:
        case 'end':
          return _context.stop();
      }
    }
  }, _marked[0], this);
}

Could you maybe try to post more code? Especially this selector - selectFeatures? Have you tried this const [...features] = yield select(selectFeatures)? (I know you are using Immutable so its probably not a case, but still ;))
It shouldnt matter that this features reference is outside in the closure in transpiled code, cause every call effect will call startSomething and thus create new references in 2 separate instances of this generator.

authors: Andarist tomrj

repo: yelouafi/redux-saga


text:
Android: Don't throw exception when trying to read from external app directories

App-specific directories within external storage doesn't require any permissions, so these shouldn't be blocked

@yendoplan are you merging this?


text:
Can't make a local generator

Try to follow this guide: http://yeoman.io/authoring/
I cloned the repo, renamed the package name:
"name": "generator-node-ES2017"
then ran npm link
However I get this error:
You don't seem to have a generator with the name node-es2017 installed
What am I missing!?

Did you try running yo doctor
If that doesn't work, try running DEBUG=yeoman:* yo node-ES2017

authors: SBoudrias kristianmandrup

repo: yeoman/generator-node


text:
fix: local variable 'img_ldm_i' referenced before assignment

fix: local variable 'img_ldm_i' referenced before assignment

Hi, in our code, a video with any frame in which we cannot detect face will be discarded. So the code is as expected.

authors: yerfor zhou-wjjw

repo: yerfor/GeneFacePlusPlus


text:
Spawning into different location of the world

When i spawn into the lobby
Version of Waterdog
This server is running Waterdog version git:Waterdog-Bootstrap:1.15-SNAPSHOT:1de3ca3:310 by md_5
Expected Behavior
When I join into the server, I don't spawn in the actual lobby, but in the void. Then, i need to do /spawn to warp into the actual spawn
Actual Behavior
The same as the Expected Behavior
Crashdump, Backtrace or Other Files
It looks all normal
Describe the bug
I don't know if this is a bug or not.
To Reproduce
Use a floating spawn in pocketmine, then join the server trough Waterdog
Screenshots
https://cdn.discordapp.com/attachments/706083854418575411/723123250623676526/unknown.png
Server software used:
PocketMine 3.13.0 (v.1.14.60)
Additional context

When player joins the server thought proxy, waterdog sends empty chunks to player. After that player should receive new chunk data from  server. I have heard that similar issue happened with latest release of pmmp only. Could you please test it with older version?

When player joins the server thought proxy, waterdog sends empty chunks to player. After that player should receive new chunk data from server. I have heard that similar issue happened with latest release of pmmp only. Could you please test it with older version?

Probably because they deprecated some things, added new ones and changed some things. Probably, if I switch to 3.12.5, Slappers will not work anymore, so i'll try to find another lobby. Thank you for reporting me this problem:

repo: yesdog/Waterdog


text:
Implement surface syntax for a selection of binary operators.

Not sure which binary operators to support, but I expect at a minimum it would be nice to implement:

<term1> + <term2>: addition
<term1> - <term2>: subtraction
<term1> * <term2>: multiplication
<term1> / <term2>: division

The idea is that these will be elaborated to the appropriate primitive operation. In order to do this initially we'd need to synthesize the types of the operands, which could be frustrating for users, especially when using literals. For example:
let test1 : U32 = 3 + 2;                     // error: ambiguous integer literals
let test2 = (3 : U32) + (2 : U32);     // ok
let test3 =
    let x : U32 = 3;
    let y : U32 = 2;
    x + y;                             // ok

...

Ultimately we'd want to use postponement and unification to resolve these, but that would take some more effort. This would hopefully allow for the following code to be elaborated:
let test1 = 3 + 2;
let test2 : U32 = test1;

...

A limited form of unification would require one of the operands to have a known type, at least! Then x / 2 would be okay.

Hmm, just thinking that actually we can do it bidirectionally in checking mode, based on the return type. No unification required.
But yeah you are right if there is no known return type, then you'd need to know the type of one of the operands? Does also depend on if we want to have multiple overloads for different type combinations but that makes me nerrrvous. 😬

Wasn't this resolved by https://github.com/yeslogic/fathom/pull/377?

Yep 👍

authors: Kmeakin brendanzab mikeday wezm

repo: yeslogic/fathom


text:
bug: Autocommands caused command to abort

Describe the bug
When I :wq with sidebar open, it shows this message:

To reproduce
Open sidebar, select split with file that you are editing, type :wq
Expected behavior
Closes vim
Installation method
Use lazy.nvim:
{
  "yetone/avante.nvim",
  event = "VeryLazy",
  lazy = false,
  version = false, -- set this if you want to always pull the latest change
  opts = {
    -- add any opts here
  },
  -- if you want to build from source then do `make BUILD_FROM_SOURCE=true`
  build = "make",
  -- build = "powershell -ExecutionPolicy Bypass -File Build.ps1 -BuildFromSource false" -- for windows
  dependencies = {
    "nvim-treesitter/nvim-treesitter",
    "stevearc/dressing.nvim",
    "nvim-lua/plenary.nvim",
    "MunifTanjim/nui.nvim",
  },
}

Environment
❯ nvim -v && uname -a
NVIM v0.10.2
Build type: Release
LuaJIT 2.1.1713773202
Run "nvim -V1 -v" for more info
Linux Monday 6.6.54 #1-NixOS SMP PREEMPT_DYNAMIC Fri Oct  4 14:30:05 UTC 2024 x86_64 GNU/Linux
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    -- add any other plugins here
  },
})

Any news on this? Is kind of anoying to not be able to close my editor with the avante window opened without needing to close it and then close the editor...

Can you dump your nix config here?

Sure, not sure how it is related but here you go :) https://github.com/gytis-ivaskevicius/nix2vim/blob/master/modules/ai.nix#L48-L52

authors: BubuDavid aarnphm gytis-ivaskevicius


text:
Separate out yewtil::dsl into yew-dsl

This is intended to fix #1183.
I've reimplemented the ScopeHolder type (inside yew-dsl).
I've also removed a lot of type arguments where (I think) they aren't needed.

Awesome, thanks for taking this on 😄

I think I've now successfully pulled it out of yewtil.

authors: jstarry teymour-aldridge

repo: yewstack/yew