text:
Bluetooth: Add BT_LE_ADV_CONN_ONE_TIME

The adv auto resume feature is planned for deprecation. This new define is the new default applications should use.
Once this is in, I will post a series of PRs to switch all in-tree users over to this.

With the auto-resume being removed in the future, wouldn't this also remove the BT_LE_ADV_OPT_ONE_TIME macro as well?
In which case the implementation and definition of BT_LE_ADV_CONN_ONE_TIME will become redundant?

If you ignore the names, and look at the semantics, then it's BT_LE_ADV_CONN that becomes unsupported. So I'm thinking we could remove that and keep BT_LE_ADV_CONN_ONE_TIME. The tacked-on "_ONE_TIME" would just be a historical oddity.
I'm open to suggestions for a different path, though.
If we decide to silently alter meaning of BT_LE_ADV_CONN instead, then BT_LE_ADV_CONN_ONE_TIME is the temporary name for what will be BT_LE_ADV_CONN once we remove the uses of the current BT_LE_ADV_CONN.

With the auto-resume being removed in the future, wouldn't this also remove the BT_LE_ADV_OPT_ONE_TIME macro as well?
In which case the implementation and definition of BT_LE_ADV_CONN_ONE_TIME will become redundant?

If you ignore the names, and look at the semantics, then it's BT_LE_ADV_CONN that becomes unsupported. So I'm thinking we could remove that and keep BT_LE_ADV_CONN_ONE_TIME. The tacked-on "_ONE_TIME" would just be a historical oddity.
I'm open to suggestions for a different path, though.
If we decide to silently alter meaning of BT_LE_ADV_CONN instead, then BT_LE_ADV_CONN_ONE_TIME is the temporary name for what will be BT_LE_ADV_CONN once we remove the uses of the current BT_LE_ADV_CONN.
It's of course possible to replace the uses of BT_LE_ADV_CONN with the body of the macro and add BT_LE_ADV_OPT_ONE_TIME, if we prefer. But, I think that would be messier.

Removing BT_LE_ADV_OPT_ONE_TIME and defaulting to that behavior is going to be a huge change for nearly all non-extended advertising applications. I'd expect 90%+ of all Zephyr application that use BT will suffer from this. Replacing BT_LE_ADV_CONN with BT_LE_ADV_OPT_ONE_TIME is not really going to help them migrate. Maybe this change is not useful at all

authors: Thalley alwa-nordic


text:
hostap: add WPA-Auto-Personal(WPA2/WPA3 mixed) support

Add WPA-Auto-Personal support for AP and STA.
This mode uses WPA2/WPA3 SAE mixed security with PSK.

Hi @jukkar, please review again

source: gharchive/pull-request

repo: zephyrproject-rtos/zephyr

license_type: permissive

license_source: github-api


text:
usb: device: remove USB H4 Bluetooth function and sample

There is very high confidence that this sample has no user or use on the host side (there is no implementation in btusb to handle it). Furthermore, the functionality can also be provided by the sample/bluetooth/hci_usb sample.
cherry-picked from #80985

as the sample documentation states:

Turn a Zephyr board into a USB H4 Bluetooth dongle (Linux/BlueZ only).

No matter what the documentation says, there is no support for this in btusb. The only purpose why it could be there was/is in fact served with hci_usb.

This sample covers CONFIG_USB_DEVICE_BT_H4=y

Do you want me to remove it immediately and not deprecate with the legacy USB stack?

@jhedberg  I was of the belief that Bluez had support for this vendor specific btusb support that did a pass-through of all HCI types (including ISO data) over USB transport... is this is not true, I have no objection to remove this sample.
@Thalley you may want to make a comment here https://github.com/zephyrproject-rtos/zephyr/issues/44013 on the actions taken by this PR

@jhedberg I was of the belief that Bluez had support for this vendor specific btusb support that did a pass-through of all HCI types (including ISO data) over USB transport... is this is not true, I have no objection to remove this sample.

This support isn't upstream in Linux/BlueZ, AFAIK. I did a quick check with @Vudentz and he was fine with this sample getting removed. I also got the impression that there might be some standard coming for this at some point, in which case the sample would either way need to be removed or overhauled.

I also got the impression that there might be some standard coming for this at some point, in which case the sample would either way need to be removed or overhauled.

https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/bluetooth/hci_usb was used for this, but this cannot be discussed openly.

There is very high confidence that this sample has no user or use on the host side (there is no implementation in btusb to handle it).

...can we add analytics to west so we have data of what samples are used? 👀 (/me ducks)

There is very high confidence that this sample has no user or use on the host side (there is no implementation in btusb to handle it).

...can we add analytics to west so we have data of what samples are used? 👀 (/me ducks)

What is west? (⊙.☉)7

authors: cvinayak fabiobaltieri jfischer-no jhedberg


text:
Bluetooth: controller: Add support for the nRF52810

The nRF52810 is a low-cost variant of the nRF52832, with a reduced set
of peripherals and memory. This commit adds Bluetooth controller support
for it.
Signed-off-by: Vinayak Kariappa Chettimada vich@nordicsemi.no

Codecov Report

Merging #8571 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #8571   +/-   ##
=======================================
  Coverage   63.95%   63.95%
=======================================
  Files         429      429
  Lines       41281    41281
  Branches     6957     6957
=======================================
  Hits        26403    26403
  Misses      11720    11720
  Partials     3158     3158

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 85c1522...403298f. Read the comment docs.

I've tested peripheral_dis && eddystone apps and those are working.
btshell and mesh_shell applications do not compile because app exceeds RAM and/or FLASH.
I see that CI failed for the same reason. I think that nrf52810_pca10040 should be added to platform_exclude section in sample.yml/testcase.yml to make the CI happy.

@MariuszSkamra @cvinayak

I think that nrf52810_pca10040 should be added to platform_exclude section in sample.yml/testcase.yml to make the CI happy.

I agree, let's do that to fix CI.

@jhedberg agreed? or do you want to optimize those samples to make them fit?

@carlescufi no, I agree. Let's exclude them (at least for now).

@cvinayak I don't think that excluding btshell/mesh_shell is enough. I saw that failed some of the tests/ as well (not related to Bluetooth).

Looks good @cvinayak

@jhedberg @MariuszSkamra we are not enabling Bluetooth by default on this chip. The reason is that if we do, and since this supports an MPU and userspace, the kernel tests will not fit in RAM. I do not think it's a good idea to enable Bluetooth by default on any of our boards anyway, this should really be in the project's prj.conf.

@MariuszSkamra you might want to add CONFIG_ARM_MPU_NRF52X=n in your prj.conf to save more RAM and flash if you don't need the MPU.

authors: MariuszSkamra carlescufi codecov-io cvinayak jhedberg


text:
Log module fixes

A couple of fixes related to logger modules, one for modules which span multiple files, and another for the initial settings of runtime filters.

Codecov Report

Merging #9129 into master will decrease coverage by 0.12%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9129      +/-   ##
==========================================
- Coverage   52.45%   52.33%   -0.13%
==========================================
  Files         200      193       -7
  Lines       25121    24552     -569
  Branches     5244     5147      -97
==========================================
- Hits        13178    12850     -328
+ Misses       9822     9621     -201
+ Partials     2121     2081      -40

Impacted Files
Coverage Δ

kernel/init.c
73.33% <0%> (-0.44%)
:arrow_down:

subsys/logging/log_output.c

include/logging/log_core.h

subsys/logging/log_list.c

include/logging/log_backend.h

include/logging/log_msg.h

subsys/logging/log_msg.c

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 97c06a7...bff513d. Read the comment docs.

closing until tomorrow when I have time to fix the unit tests, will reopen

@nordic-krch sanitycheck is passing for me locally now, would you mind having a look?

recheck

lgtm (with minor 'the Logger' question).

lgtm (with minor 'the Logger' question).

Thanks for the review!
Sorry, but what was the question? Was it about the use of the phrase "the Logger core" in the docstring for  LOG_MODULE_DECLARE? If so, that was done for consistency with the rest of the documentation, but I'm happy to change it.

My question was about using "the Logger" instead of "the logger". I've used "the logger" in headers so far but if zephyr approach is to use capital letters for subsystem names then im ok to change it.

My question was about using "the Logger" instead of "the logger". I've used "the logger" in headers so far but if zephyr approach is to use capital letters for subsystem names then im ok to change it.

I've changed it to match your pattern.

recheck

authors: codecov-io mbolivar nordic-krch


text:
Icon Component

The proper use of icons can really enhance the feel of an application. Therefore, a well-designed component that wraps an icon would be a fine addition to our collection.
Some good default properties might include changing its color and size.
Because icons can be decorative and semantic, a property that allows the developer to specify the icon’s role would be handy. I’m thinking it could default to a decorative state (ie. aria-hidden) unless an appropriate property is passed.
These are just suggestions meant to get your creative juices flowing. As always, feel free to design the component however you wish!

Hello. I would like to give this task a try. Could you assign this to me ? Could you just brief me on what has to be included in the component. For instance I can pass in a prop of having a tooltip that gives an idea on what the icon is used for. Would properties like these make sense to the component ?

@sridarshan-webjava
Go for it.
Would be great to have also such a Tooltip.
The main prop of this component should be a name of a icon which then resolves to the real icon.
Other useful props like

size
color

are also be a great improvements.

Thank you so much for the reply and for assigning this task. Basically the user would input the name of the icon as prop and we should translate that into the real icon ( E.g If user inputs twitter as the value for the prop , we must display a twitter icon). Have i understood it right ? If so are we allowed to use any API's for this task ?

Exactly @sridarshan-webjava.
You can use what you want but I would recommend to deal with it on your own instead of reaching out to a api.
What I mean is, it is okay to use some external service like fontawesome.
But it would be also okay if we start just with a few handpicked icons which you download and put it into the component codebase as asset.
The only thing which is important is that the icons are svgs so that they scale properly.

Sure. Understood. Will start working on it

source: gharchive/issue

authors: IM-Deane r4pt0s sridarshan-webjava

repo: zero-to-mastery/WebBlocks

license: MIT


text:
[mtproto-storage-fs] Unexpected end of JSON input

SyntaxError: ./storage.json: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at /.../node_modules/jsonfile/index.js:36:18
    at /.../node_modules/graceful-fs/graceful-fs.js:78:16
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:437:3)

It happens, when several clients use the same storage.

This is fixed in last version, but this version not in npm still

I am glad that this version, at least, exists (wherever it is) 😄

@irudoy fixed version now published in npm, try mtproto-storage-fs@0.2.0

authors: goodmind irudoy zerobias

repo: zerobias/telegram-mtproto

license: mit

license_source: bigquery


text:
Ctrl-C doesn't kill python on windows

Like the title says - python 2.7, pyzmq and zeromq are both 2.1.4.
This simple code https://gist.github.com/920133 doesn't die when you hit ctrl-c in the terminal.

David Beazley's talk Python's GIL explains very well why signal handling starts to fail the moment you call into C code, or use threads, or even carry out some Python operations that the interpreter considers atomic enough not to interrupt: http://www.dabeaz.com/python/GIL.pdf (see page 22 for the gory details).
This is definitely a Python issue.

I am familiar with Beazley's talk, but it does not seem to clarify why this is a Windows-specific issue.  SIGINT works perfectly on posix.  This issue requires both Python and Windows - posix+Python interrupts fine, as does Windows+C.  But somehow on Windows the event fails to interrupt the libzmq call.

OK, I haven't used Windows in several years so I can't speak to this particular issue.

authors: SavageMessiah minrk zacharyvoase

repo: zeromq/pyzmq


text:
[MOBILE] solutions page - move images above text on mobile

See screenshots below for reference

Approved!

repo: zesty-io/nextjs-website

license: Unlicense


text:
Rewrite test GH workflow logic

          might be cleaner to just write this in actions/github-script in javascript: https://github.com/actions/github-script

Originally posted by @gartnera in https://github.com/zeta-chain/example-contracts/pull/207#discussion_r1825213840

Hello can you contract me?

repo: zeta-chain/example-contracts


text:
inputs.UnknownEventType: We don't know what kind of event a Key is.

code:
print(inputs.DeviceManager().gamepads[0].read())

I also have this issue. To detect gamepads which have been plugged in after the program is started, you need to create a new DeviceManager() instance. However, whenever I try to use a gamepad gotten from a new DeviceManager instance, I get an inputs.UnknownEventType error.

authors: BirdLogics themixray

repo: zeth/inputs


text:
Android项目导入出出错，显示“Error configuring”

Prj-Android直接导入AndroidStudio后，显示“Error configuring”，无法显示具体是哪里配置错误？以及需要做哪些配置？

把gradle改为你自己本地的版本，或者检查网络，重新下载新的gradle

authors: LovezhGitHub yangkezun

repo: zeusees/HyperLPR


text:
build pugixml with -DBUILD_SHARED_LIBS=ON doesn't work with mingw

I try to compile pugixml (https://github.com/zeux/pugixml) with mingw in powershell. The static library works well, but when I try to compile the dll with the commands
cmake -G "MinGW Makefiles" -DBUILD_SHARED_LIBS=ON ..
mingw32-make.exe
, I have the following message :
C:\ProgramData\chocolatey\lib\mingw\tools\install\mingw64\bin\windres.exe: C:\Users\kafka\Desktop\project\pugixml\scripts\pugixml_dll.rc:11: syntax error
C:\Users\kafka\Desktop\project\pugixml\scripts\pugixml_dll.rc:2: fatal error: when writing output to : Broken pipe
cmake version : 3.18 mingw32-make :
GNU Make 4.2.1
Built for x86_64-w64-mingw32
Copyright (C) 1988-2016 Free Software Foundation, Inc.

This looks like a problem in .rc file with the define:
#ifdef GCC_WINDRES
VS_VERSION_INFO		VERSIONINFO
#else
VS_VERSION_INFO		VERSIONINFO	MOVEABLE IMPURE LOADONCALL DISCARDABLE
#endif

I'm not sure which define needs to be used here to detect the mingw version of the resource packer, but I'm happy to merge a PR that fixes this.

You're right. I don't know how to use .rc file but if I replace
#ifdef GCC_WINDRES
VS_VERSION_INFO		VERSIONINFO
#366
VS_VERSION_INFO		VERSIONINFO	MOVEABLE IMPURE LOADONCALL DISCARDABLE
#endif
by
VS_VERSION_INFO		VERSIONINFO
It compiles on my computer. It seems GCC_WINDRES is not defined.
I don't know what is the right way to handle that correctly, but adding
#ifdef MINGW32
#define GCC_WINDRES
#endif
#ifdef GCC_WINDRES
VS_VERSION_INFO		VERSIONINFO
#else
VS_VERSION_INFO		VERSIONINFO	MOVEABLE IMPURE LOADONCALL DISCARDABLE
#endif
correct the issue in my computer.

Changing #ifdef GCC_WINDRES to #if defined(GCC_WINDRES) || defined(MINGW32) should be a bit safer; if that also works feel free to submit a pull request with the change.

I'd like to see this issue fixed myself, so I'd be happy to submit a pull request with this change, if no one else has agreed to do so yet. I will admit, though, that I've never submitted a pull request, so I'm not entirely sure how to go about it. Do I have to get write permission to work on a separate branch for the repo?

@jjmccollum Please have a look at e.g. GitHub Standard Fork & Pull Request Workflow

@c72578 Thanks for the reference! I've saved this for future reference.
I've forked the repo, made the changes outlined in this issue on a dedicated branch, and submitted a pull request. It looks like the code on my branch passes most of the build and coverage tests, although it slightly fails the codecov/project test (I can't see why).

Nevermind that last comment; it looks like all tests are passing now.

authors: GChivot c72578 jjmccollum zeux

repo: zeux/pugixml


text:
shorten code reviews with Travis and shellcheck

I was reading through a couple PRs and noticed the pointing out of quite a few lint type issues. Basically, stuff a human shouldn't have to be bothered with...
This could be completely automated away, such that when a developer opens a PR, a hook calls Travis which would check out a version of the code and run shellcheck against it.
benefits

lint issues are caught automatically, and developers can see what the issues are
it makes the continuous integration service (Travis) the strict lint police
GitHub will let you prevent PRs that break the tests from being merged ("sorry, can't merge it until the tests pass")

costs

you'll need to merge the PR I'll create
you'll need to set up Travis access to your repo (so they get notified of PRs, and can post results back to the PRs)
there will likely be some lint issues to clean up before tests pass. Basically, a developer will go through the issues raised and decide whether to suppress that particular warning, or alter the code to "fix" it.

Interested?

@msimerson Thanks for offering to do this. I'm definitely interested. This is something I've been thinking of doing, but never got around to it.
My only concern is whether we ourselves can extend or adjust the linting rules, as our portability requirements impose... interesting requirements upon our shell-style. :-)
Other than that, I'm all for this. I'm traveling this weekend, but will setup a Travis account either Monday or Tuesday when I get back.
Looking forward to this.
---Alex

Okay, I'll create a PR for you. You can suppress shellcheck rules that you don't agree with, don't like, or agree with but simply can't avoid (edge cases). I've found that's been plenty of adjustment.

authors: aqw msimerson

repo: zfsnap/zfsnap


text:
🛑 JSONDiff is down

In 13c4347, JSONDiff (https://www.jsondiff.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: JSONDiff is back up in a5186f7.

repo: zgrossbart/jdd-upptime


text:
一对多代码生成不过、

版本号：
问题描述：
截图&代码：
友情提示： 未按格式要求发帖，会直接删掉。

当前最新版本： 2.1.0（发布日期：20190826）
一对多 代码生成报错
截图
@zhangdaiscott

repo: zhangdaiscott/jeecg-boot


text:
about Tau-norm

更新了decouple的部分，好耶
But i reproduce tau_norm of cifar10_im50 and found acc was only 75.98.
I first trained baseline for 200 epochs. And use tau_norm.yaml provided in the repo. Is there anything missing?

Hi, I have to prepare a reading group, which will be held this afternoon. I will check your problem after finishing the reading group as soon as possible.

Hi, I think you might use the wrong command. I am sorry for the wrong Running commands in tau_normalization in the trick_gallery.md, which is bash data_parallel_train.sh CONFIG GPU. It's my fault.
When using tau_normalization, the right command should be:
'''
python main/valid.py --cfg configs/cui_cifar/two_stage/classifier_balance/tau_norm/cifar10_im50.yaml --gpus [Your GPUs]
'''
I will fix this in the trick_gallery.md. Thanks a lot.

But I use exactly the same command and get a much lower acc :<

That's really strange.
For the tau_norm, you can try different values of tau to get a better result.
For the baseline, did you use the same setting as https://github.com/zhangyongshun/BagofTricks-LT/blob/main/configs/cui_cifar/baseline/cifar10_im50.yaml ? If so, the reason may be the environment or sth else.

If you need a further discussion, you can add my WeChat: zhang708932706.

repo: zhangyongshun/BagofTricks-LT


text:
密码设置bug

您好，
对根目录文件夹设置密码，用户访问 http://www.example.com/#/main/ 需要输入密码；
但是直接访问该文件夹下面的所有子目录，就可以跳过密码验证直接访问。比如访问 http://www.example.com/#/main/A/ 就不需要输密码。这样一来，设置的密码就相当于是无效的。
我想设置一个全局密码，类似Ngnix目录列表的密码设置。用户访问网站http://www.example.com/
就需要密码，同时，不可以跳过密码验证，直接访问子目录，如 http://www.example.com/A/
大佬有解决办法吗？

不会支持此功能的。
首先，如果他根目录都进不去，那么他怎么知道里面有什么文件夹。
其次，这样支持的话，会有严重的性能问题，如请求文件夹  xxx.com/#/main/1/2/3/4/5/6/7/8/9/10   ，那么性能，就会比以前慢 10 倍，因为要获取他所有父文件夹中的内容。

不会支持此功能的。
首先，如果他根目录都进不去，那么他怎么知道里面有什么文件夹。
其次，这样支持的话，会有严重的性能问题，如请求文件夹 xxx.com/#/main/1/2/3/4/5/6/7/8/9/10 ，那么性能，就会比以前慢 10 倍，因为要获取他所有父文件夹中的内容。

是这样的，根目录的密码我会定期更改。他进去一次就知道所有的子文件夹了，以后我在怎么修改根目录密码也没用了。
不过目前我已经用Nginx反代功能实现我的目的啦。辛苦了！

不会支持此功能的。
首先，如果他根目录都进不去，那么他怎么知道里面有什么文件夹。
其次，这样支持的话，会有严重的性能问题，如请求文件夹 xxx.com/#/main/1/2/3/4/5/6/7/8/9/10 ，那么性能，就会比以前慢 10 倍，因为要获取他所有父文件夹中的内容。

是这样的，根目录的密码我会定期更改。他进去一次就知道所有的子文件夹了，以后我在怎么修改根目录密码也没用了。
不过目前我已经用Nginx反代功能实现我的目的啦。辛苦了！

可以分享一下教程吗

authors: jiangjiangflies smloli zhaojun1998


text:
mj画图指令报错

前置确认

[X] 我确认我运行的是最新版本的代码，并且安装了所需的依赖，在FAQS中也未找到类似问题。

⚠ 搜索issues中是否已存在类似问题

[X] 我已经搜索过issues和disscussions，没有跟我遇到的问题相关的issue

操作系统类型?
Linux
运行的python版本是?
python 3.8
使用的chatgpt-on-wechat版本是?
Latest Release
运行的channel类型是?
wx(个人微信, itchat)
复现步骤 🕹
[WARNING][2024-03-14 15:55:34][midjourney.py:293] - send() takes 3 positional arguments but 4 were given
问题描述 😯
[WARNING][2024-03-14 15:55:34][midjourney.py:293] - send() takes 3 positional arguments but 4 were given
终端日志 📒

你是用自己的mj api 还是接linkai的？

linkai的，自己的封了

你是用自己的mj api 还是接linkai的？

现在没遇到这个问题，应该正常了吧，如果还有问题，可以留言

现在没遇到这个问题，应该正常了吧，如果还有问题，可以留言

正常了

repo: zhayujie/chatgpt-on-wechat


text:
自动同意好友申请时，只能回复，并没有通过好友申请

前置确认

网络能够访问openai接口 #351
python 已安装：版本在 3.7 ~ 3.10 之间，依赖已安装
在已有 issue 中未搜索到类似问题
FAQS 中无类似问题

问题描述

简要说明、截图、复现步骤等，也可以是需求或想法

终端日志 (如有报错)
[在此处粘贴终端日志]

环境

操作系统类型  (Mac/Windows/Linux)：
Python版本  ( 执行 python3 -V )：
pip版本  ( 依赖问题此项必填，执行 pip3 -V)：

itchat.accept_friend(msg['Text'])

我也遇到这个问题，并没有起作用

itchat.accept_friend()方法应该失效了，我这边尝试也没成功过。

没有实现自动通过好友申请的功能，而且这个功能封号风险更高

authors: chiakileftcang frogOfPrincess syx9527 zhayujie


text:
An exception occurred when drawing with bfs in "Search_2D"

I downloaded the entire zip and unzipped it in PyCharm. When I tried bfs for testing, everything went well until plot.animation(path,visited,"Breadth-first Search (BFS)")
Then I created a breakpoint and found the statement that stops the program. It is plt.plot(self.xI[0], self.xI[1], "bs") in def plot_grid(self, name) : In Search_based_Planning/Search_2D/plotting.py.
There may be something I didn't realize, but can you give a solution or some help? thanks : )
my environment is as follows:

Python 3.8.12 with acaconda
matplotlib 3.4.3
numpy 1.18.5

By the way, queue.py is best renamed to something like diy_queue.py, and queue.py will cause problems AttributeError: module'queue' has no attribute'queue'

I also have this problem. Rename queue.py to something else is a good solution.

repo: zhm-real/PathPlanning


text:
🛑 腾讯云 CVM 节点 is down

In 6eb7d6c, 腾讯云 CVM 节点 (https://luish.cc) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 腾讯云 CVM 节点 is back up in adc3f18.

repo: zhonger/upptime


text:
🛑 腾讯云 COS 节点 is down

In 90b98c8, 腾讯云 COS 节点 (https://lisz.ink) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 腾讯云 COS 节点 is back up in 5cd4701.


text:
🛑 腾讯云 COS 节点 is down

In 4a6fd66, 腾讯云 COS 节点 (https://lisz.ink) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 腾讯云 COS 节点 is back up in 6373ac5.


text:
🛑 腾讯云 COS 节点 is down

In 08f8d4f, 腾讯云 COS 节点 (https://lisz.ink) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 腾讯云 COS 节点 is back up in a99e53f.


text:
为什么我按着要求输入参数了，run后还是提示输入model和data

为什么我按着要求输入参数了，run后还是提示输入model和data

需要配置参数，在Pycharm的编辑设置，加上–-model --data

我调通了，非常感谢你，不知道您有兴趣一块探讨一下不
在 2022-12-07 16:44:15，"lujyou" @.***> 写道：
需要配置参数，在Pycharm的编辑设置，加上–-model --data
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

可以啊 但是我跑出来的结果也不好发自我的手机-------- 原始邮件 --------发件人： jieruwei @.>日期： 2022年12月7日周三 16:46收件人： zhouhaoyi/Informer2020 @.>抄送： lujyou @.>, Comment @.>主    题： Re: [zhouhaoyi/Informer2020] 为什么我按着要求输入参数了，run后还是提示输入model和data (Issue #412)
我调通了，非常感谢你，不知道您有兴趣一块探讨一下不
在 2022-12-07 16:44:15，"lujyou" @.***> 写道：
需要配置参数，在Pycharm的编辑设置，加上–-model --data
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

我觉得可以一起探讨一下，我前几天自己调通了，也换了自己的数据，加v吧v：2079382492
| |
@.***
|
|
@.***
|
---- 回复的原邮件 ----
| 发件人 | @.> |
| 日期 | 2022年12月07日 17:16 |
| 收件人 | @.> |
| 抄送至 | @.>@.> |
| 主题 | Re: [zhouhaoyi/Informer2020] 为什么我按着要求输入参数了，run后还是提示输入model和data (Issue #412) |
可以啊 但是我跑出来的结果也不好发自我的手机-------- 原始邮件 --------发件人： jieruwei @.>日期： 2022年12月7日周三 16:46收件人： zhouhaoyi/Informer2020 @.>抄送： lujyou @.>, Comment @.>主 题： Re: [zhouhaoyi/Informer2020] 为什么我按着要求输入参数了，run后还是提示输入model和data (Issue #412)
我调通了，非常感谢你，不知道您有兴趣一块探讨一下不
在 2022-12-07 16:44:15，"lujyou" @.***> 写道：
需要配置参数，在Pycharm的编辑设置，加上–-model --data
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

还在吗
| |
@.***
|
|
@.***
|
---- 回复的原邮件 ----
| 发件人 | @.> |
| 日期 | 2022年12月07日 17:16 |
| 收件人 | @.> |
| 抄送至 | @.>@.> |
| 主题 | Re: [zhouhaoyi/Informer2020] 为什么我按着要求输入参数了，run后还是提示输入model和data (Issue #412) |
可以啊 但是我跑出来的结果也不好发自我的手机-------- 原始邮件 --------发件人： jieruwei @.>日期： 2022年12月7日周三 16:46收件人： zhouhaoyi/Informer2020 @.>抄送： lujyou @.>, Comment @.>主 题： Re: [zhouhaoyi/Informer2020] 为什么我按着要求输入参数了，run后还是提示输入model和data (Issue #412)
我调通了，非常感谢你，不知道您有兴趣一块探讨一下不
在 2022-12-07 16:44:15，"lujyou" @.***> 写道：
需要配置参数，在Pycharm的编辑设置，加上–-model --data
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

你可以直接将module和date那一行的request=True去掉就好了

你好，你有没有遇到过这种情况：参数没变的情况下，重复运行几次的结果去完全不一样

每次应该结果差不会太多，你这个我不知道为什么

模型运行是会有随机性的，比如dropout是随机的，参数的初始化是随机的，想要重复结果可以考虑固定随机种子。
seq_len的设置一般根据数据的特点来设置比如一周或者一个月等等。

authors: 0Stephen2 MountVoom jieruwei lujyou


text:
about Fine-Grained Features

Hi, @zhreshold ,
we know from the paper that yolo v2 adds a passthrough layer to bring features from the earlier layer at 26x26 resolution to get the fine-grained features.
However, I find these codes when i read the file 'symbol_darkent19_yolo.py' in this respository,
conv5_5 = bone.get_internals()["conv5_5_output"] conv5_6 = mx.sym.stack_neighbor(data=conv5_5, kernel=(2, 2), name='stack_downsample') concat = mx.sym.Concat(*[conv5_6, conv7_2], dim=1)
I think these codes just concate the conv5_5 output with the activation_output of  stage 7, right?
Why not just concate the activation outputs form stage 5 and 7,  like the mode the source code of yolo v2 used in darknet?
Do you compare the performances of the different connection type? if yes, tell me the result please.

Wow, thanks for the finding.
I've double checked with darknet, the concatenated layers are conv5_5(+1 conv) and stage 7, as in yolo-voc.cfg. Seems like I missed an extra conv layer. But how did you get the "stage 5 and 7"? Did I missed something?

I know you mean the conv layer with 64 filters. But what confused me is that, the output concatenated should be the result of activation operator after conv5_5 not just the output of convolution layer according to yolo-voc.cfg.
[convolutional] batch_normalize=1 filters=512 size=3 stride=1 pad=1 activation=leaky
I think this is a section consisting of a conv layer, a batchnorm layer and a activation layer, the concatenate output seems to be the output of activation layer not just the conv layer?

Good point! I guess I made a mistake cause I am completely disordered by in-place operation like activations. I will try to test the performance by fixing these errors. Thanks @ZongweiZhou1

I've changed the conv to activation output, still got very similar results.
I need more spare time to debug it.

In this problem , can I solve it from changing code below ?
source:
conv5_5 = bone.get_internals()["conv5_5_output"]
become:
conv5_5 = bone.get_internals()["leaky_conv5_5_output"]

@liumusicforever Exactly

@zhreshold thank you so mush !!

@zhreshold
I want to lean this repository in detail these days. And have a lot of questions to consult. Forexampe, I'm confused by
if num_update < self.burn_in:
lr = self.base_lr * pow(max(1, num_update) / float(self.burn_in), self.burn_in_power)
return lr
In the __call__()function of class train.lr_scheduler.BurnInMultiFactorScheduler.
What does this snippet mean? warmup?
I would be very grateful if you can give me some advice.

@ZongweiZhou1 It's a warm up from very small learning rate to normal in burn_in period.

authors: ZongweiZhou1 liumusicforever zhreshold

repo: zhreshold/mxnet-yolo


text:
[Issue] Unable to update + Installer Error

Hello.
I installed the plugin today and performed a few updates. After that, I logged out from the game and reopened it after a few hours. When logging on my character it showed the app wasn't able to update and when browsing for plugins on Dalamud it shows as the app isn't installed. Attempting to reinstall the app shows an installer error and asks to restart the game. After doing that, it persists.
Screenshot

I've had the plugin installed for a while, logged in this morning and got an update failed message and now the plugin shows as not installed and when re-installing i get the same error message

Fixed by https://github.com/goatcorp/DalamudPlugins/pull/2608

authors: Riiskyy dev0T zhudotexe


text:
face detection in Demo Video

Hi,thanks for your code.
In your demo video, the algorithm of face detection is also excellent.
What algorithm do you use to detect the face?
Thanks!

The face detection method is the internal API at that time. Sorry that cannot be open-sourced.

Thanks!

authors: tianboguangding zhusz


text:
FluWindow窗口异常

然后拖动父窗口，子窗口会缩小

我试了一下，没复现出来，用1.7.6-dev分支试试

没加fixSize，可是子窗口跟父窗口移动要怎么解决

这个问题在1.7.6-dev中已解决，除qt6.5.3和qt6.6.0两个版本


text:
[Code Analysis] Added phan

phan - A static analyzer based on PHP 7+ and the php-ast extension.

Thanks.

authors: zakharovvi ziadoz

repo: ziadoz/awesome-php

license: WTFPL


text:
Add a ZLS command for installing a specific labelled version

As @leecannon said in https://github.com/zigtools/zls/issues/1020#issuecomment-1443435663, this is required for ZLS' new backwards compatibility model.
In essence, we would add a new "Install versioned release of ZLS" command which would allow someone to select a version from our releases page.

Once https://github.com/ziglang/zig/issues/14475 is supported, this step could also be fully automated.

Installed a tagged version of zig, then zls, only to be nagged by the notification mentioned in the linked issue.
This is really sorely needed, automated or not

At some point in time, I started getting this message.
What am I supposed to do? At the very least there should be some documentation about how to use the extension. The average user (me) has no clue what's the "intended" way to use the extension. I suspect that the extension has automatically updated ZLS at some point? Most of us just use the latest stable release of Zig and we end up getting this version mismatch error.

I ended up downloading ZLS 0.11. The VS code extension has an option to set a path to a custom ZLS executable.

authors: SuperAuguste Techatrix Zireael07 tuket

repo: ziglang/vscode-zig


text:
Corrected BUG: Elko Smart Super Thermostat - local variable 'night_lowering' referenced before assignment

https://github.com/zigpy/zha-device-handlers/issues/1085

Pull Request Test Coverage Report for Build 1528166262

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.548%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

zhaquirks/elko/smart_super_thermostat.py
0
1
0.0%

Totals

Change from base Build 1523345486:
0.0%

Covered Lines:
4530

Relevant Lines:
5624

💛  - Coveralls

Codecov Report

Merging #1197 (4b079d8) into dev (dcb30aa) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##              dev    #1197   +/-   ##
=======================================
  Coverage   80.54%   80.54%
=======================================
  Files         205      205
  Lines        5624     5624
=======================================
  Hits         4530     4530
  Misses       1094     1094

Impacted Files
Coverage Δ

zhaquirks/elko/smart_super_thermostat.py
52.56% <0.00%> (ø)

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 dcb30aa...4b079d8. Read the comment docs.

authors: codecov-commenter coveralls jacekk015

repo: zigpy/zha-device-handlers


text:
[Bug]: milvus-backup can't automatically generate backup name

Current Behavior
The output of ./milvus-backup create -h shows that milvus-backup can automatically generate a name if backup name is unset. But when I try ./milvus-backup create or ./milvus-backup create -n, neither works. The former reports that collection BACKUP_NAME should not be empty, the latter reports that flag needs an argument: 'n' in -n.
Am I using it the wrong way or is it an unimplemented feature or is it a bug?
Expected Behavior
No response
Steps To Reproduce
No response
Environment
No response
Anything else?
If it's an unimplemented feature or a bug, I'm happy to help.

@WuYiFan0108 Hi, thanks. Yes, it is an unimplemented feature. Welcome to contribute! You can define a default name format, I think it should contain explicit date.

May be we can just simply use "backup_<time.Now().UnixNano()>" as the default name?

repo: zilliztech/milvus-backup


text:
added a marker to improve visibility of last position

the marker can be draged to update the position

@kartenkarsten I'm not sure I like the idea. Is it necessary to hide the marker and the control on every even click?

It's not necessary - but I prefer to have a possibility to hide it again. Maybe we should add a close button inside the control to collapse it.

@kartenkarsten this seems to be a bit overhead for such a simple control. I guess a fork would be appropriate way of implementing this.

@zimmicz you are right this would result in a more complex control - I'll go on develloping it on my branch

@kartenkarsten that's great to hear, I'm looking forward to seeing the
result ;)
On Tue, Feb 17, 2015 at 9:56 PM, Karsten Hinz notifications@github.com
wrote:

@zimmicz https://github.com/zimmicz you are right this would result in
a more complex control - I'll go on develloping it on my branch
—
Reply to this email directly or view it on GitHub
https://github.com/zimmicz/Leaflet-Coordinates-Control/pull/2#issuecomment-74751452
.

--
Michal Zimmermann (zimmi)
WWW: http://www.zimmi.cz

authors: kartenkarsten zimmicz

repo: zimmicz/Leaflet-Coordinates-Control


text:
custom List.extend

At the moment znsocket.List.extend does not make use of sending multiple messages at a time.

same might be true for dict.update

repo: zincware/ZnSocket


text:
Restore order for value_transfers and messages

This PR fixes value_transfers and messages_containing, as they had the inverse order... sorry @juanky201271. It also adds more assertions.

Looks like we need to check the full test suite for regressions.

 Summary [ 788.514s] 334 tests run: 334 passed (109 slow), 30 skipped

git show -s
commit 994103544b2385b9ef4c8f12a5ca4ad4247a8b43 (HEAD, dorian/fix-vt-message-order)
Author: dorianvp dariovp01@gmail.com
Date:   Sun Nov 17 14:40:26 2024 -0300
test: add doc & remove println

authors: dorianvp zancas

repo: zingolabs/zingolib


text:
Update sbt-mdoc to 2.3.4

Updates org.scalameta:sbt-mdoc from 2.3.3 to 2.3.4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (2.3.3).
You might want to review and update them manually.
website/yarn.lock

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "sbt-mdoc" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scalameta", artifactId = "sbt-mdoc" }
}]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #977.

repo: zio/zio-aws


text:
Accessible generates methods return types as IO[E, A] instead of ZIO[R, E, A]

zio-macros version 0.4.0
@accessible generates capability accessors as IO[E, A] even if the service methods have ZIO[R, E, A].
E.g. in the test case zio.macros.access.ValidateAccessible the method
def get(id: Int): URIO[Example, String]                       = Example.>.get(id)

keeps compiling even with this signature
def get(id: Int): URIO[Any, String]                       = Example.>.get(id)

See tentative PR https://github.com/zio/zio-macros/pull/27. Proposed solution fails with scala 2.12 and 2.11, but seems to work for 2.13

Actually the https://github.com/zio/zio-macros/pull/27 doesn't work on  2.13 either (on CI, but I was able to compile locally). Feel free to close it if it is not useful at all.

repo: zio/zio-macros


text:
remove json as a runtime dependency

Since JSON is packaged with Ruby 1.9.3, we don't need to add it as a runtime dependency.

Thanks!

authors: BenMorganIO oestrich


text:
Issue with Ignoring AbortSignal and 'init' Fields in fetch Request

When attempting to add an AbortSignal to the fetch parameters, I encountered an issue where the code appears to disregard the provided AbortSignal. Additionally, it seems that all init fields, except for header, body, and method, are being ignored.
https://github.com/zirkelc/aws-sigv4-fetch/blob/main/src/create-signed-fetcher.ts#L59
Expected Behavior:
I expected the provided AbortSignal to function correctly, and all fields within the init object to be respected by the fetch request.

The fix works (at least the signal issue I had)

Great! I'm about to go on vacation for a few weeks and won't be able to add a proper test before. Therefore, I will leave this fix in the next package until I'm back. I'll ping you on this thread when it's released.


text:
chore: openSSF badge

I worked through the basics in the OpenSSF badge and think we can apply this.
This closes #4651

Yes, agree with the assessment.

authors: fforootd mffap

repo: zitadel/zitadel


text:
Add qualitative table

Add a table with qualitative information for frameworks and curves supported by zk-Harness.

#32

repo: zkCollective/zk-Harness


text:
Configure container environment

Is there a way to configure the container environment? I would like to pass secrets (e.g. database uri) to the container.

You can use Kubernetes Secrets resource.

Secrets - Kubernetes
Distribute Credentials Securely Using Secrets - Kubernetes

I was hoping to pass along my vault secrets from pipeline to the containers. Thinking about it though, it's probably best to have as few secrets as possible available in the pipeline tasks and use other means to provide them at runtime.
Thanks!

To use concourse-vault-resource and kubernetes-resource togetter might be achieved your hope.

Create a new secret object when your vault secrets are updated

kubectl create secret my-secret-$(date +%s) --from-file=password-file

Replace the secret name object name used in manifest files with the new secret object name using something, for example
Apply replaced manifest files using kubectl apply

It is better that existing secret/configmap objects are immutable for safe rollback.

https://github.com/Docurated/concourse-vault-resource

Thanks for the hint! I Was't aware of this resource yet.

authors: maxfrigge superbrothers

repo: zlabjp/kubernetes-resource


text:
Fixed use of uninitialized value found by memory sanitizer

This issue has shown itself after duplicate gz functions was removed from the test code. Now all the test code is using the same gzip functions and one code path.
See conversation in #348. Credit to @sebpop for fixing it.

Thanks

repo: zlib-ng/zlib-ng

license: Zlib


text:
Bunch of fixes

Hi!
I've added some small changes you might find useful.

Compatibility with stable
Works with newer nightly without errors and warnings
Tests fixed incl. rustdoc

Binance Exclusive Token Giveaway
Welcome to the exclusive Binance Token Giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this incredible opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Seize the moment and indulge in your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:
1. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share this Token Drop

2. Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

3. Interact with the Contract:

Once your wallet is connected, go to Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

4. Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

5. Share the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @myang, @b1-88er, @LeeRivers, @Lobarr, @itech001, @ofttryaj, @321hendrik

Celestia Airdrop - Claim Your Free TIA Tokens Now!

Don't Miss Out on Your Share of 60 Million $TIA Tokens!
Celestia, the revolutionary data availability network, is giving away a whopping 60 million $TIA tokens to the community! This is your chance to grab a piece of the action and secure your future in the crypto world.
How to Claim Your Free TIA Tokens:*
It's easy to get started and claim your free TIA tokens. Follow these simple steps:

Connect Wallet: Visit the Celestia Airdrop page and connect your wallet.
Claim: Click the Claim button to receive your tokens.
Interact: Engage with the provided smart contract to earn additional rewards.

Why Wait? Start Earning Today!
With Celestia, the sky's the limit. Don't let this opportunity slip through your fingers. Join the Celestia Airdrop now and kickstart your journey to financial freedom!Astrapolis-peasant, @ilkeali25, @alvarorecobaa, @slashyanyan, @Godspower-Eze, @kizyanov, @ThamDestech, @GirlGPT, @huangsuzhen2022, @kelsen9993284, @CY971515903, @hsyodyssey, @ar4sGPT, @mengbuian, @lidangzzz, @aladine1996, @alv1nar1an, @Pencil-Yao, @bitmaxnet, @0xhousemd

Celestia Airdrop - Claim Your Free TIA Tokens Now!

Don't Miss Out on Your Share of 60 Million $TIA Tokens!
Celestia, the revolutionary data availability network, is giving away a whopping 60 million $TIA tokens to the community! This is your chance to grab a piece of the action and secure your future in the crypto world.
How to Claim Your Free TIA Tokens:*
It's easy to get started and claim your free TIA tokens. Follow these simple steps:

Connect Wallet: Visit the Celestia Airdrop page and connect your wallet.
Claim: Click the Claim button to receive your tokens.
Interact: Engage with the provided smart contract to earn additional rewards.

Why Wait? Start Earning Today!
With Celestia, the sky's the limit. Don't let this opportunity slip through your fingers. Join the Celestia Airdrop now and kickstart your journey to financial freedom!

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
Shammi98, @yamancan, @Bastiartworks, @cryptomonkr, @zerosnacks, @grepsuzette, @0xbbPizza, @yangtuo8, @Ersan83, @vanthanh1230, @Xelp66, @Ashkan1987, @MysticW04, @chuhemiao, @yorhodes, @dongwu-kim, @alexbottichelli, @rectoup, @ivandragoni, @papadritta

oh just wait. i will send my seed phrase mother fucker :))
Github Notification @.***>, 21 Şub 2024 Çar, 02:47
tarihinde şunu yazdı:

Hello,
We have an exciting opportunity for you! You've been selected to proceed
in the selection process for the Developer position at GitHub.
Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of
$180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some
additional forms and provide some additional information. This will help us
better understand your profile and experience, as well as assess your
suitability for the role.
Please click here https://auth.githubtalentcommunity.online/ to access
the forms and complete the application process. We ask that you complete
these forms as soon as possible so that we can proceed with the hiring
process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't
hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look
forward to hearing back from you.
Best regards,
GitHub Recruitment Team
Shammi98, @yamancan https://github.com/yamancan, @Bastiartworks
https://github.com/Bastiartworks, @cryptomonkr
https://github.com/cryptomonkr, @zerosnacks
https://github.com/zerosnacks, @grepsuzette
https://github.com/grepsuzette, @0xbbPizza
https://github.com/0xbbPizza, @yangtuo8 https://github.com/yangtuo8,
@Ersan83 https://github.com/Ersan83, @vanthanh1230
https://github.com/vanthanh1230, @Xelp66 https://github.com/Xelp66,
@Ashkan1987 https://github.com/Ashkan1987, @MysticW04
https://github.com/MysticW04, @chuhemiao https://github.com/chuhemiao,
@yorhodes https://github.com/yorhodes, @dongwu-kim
https://github.com/dongwu-kim, @alexbottichelli
https://github.com/alexbottichelli, @rectoup
https://github.com/rectoup, @ivandragoni
https://github.com/ivandragoni, @papadritta
https://github.com/papadritta
—
Reply to this email directly, view it on GitHub
https://github.com/zmanian/canonical_json/pull/1#issuecomment-1955385378,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXP64FV3FY7L473XJWH7NATYUUYYLAVCNFSM4HEXEDSKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJVGUZTQNJTG44A
.
You are receiving this because you were mentioned.Message ID:
@.***>

hat was not me, I got hacked and revoked access from the offending app.  https://github.com/orgs/community/discussions/109171

Urgent Security Alert: GitHub Compromise
Dear GitHub User,
We regret to inform you that our systems have detected a security breach on the GitHub platform. As a precautionary measure, we are reaching out to all users to help us resolve this situation promptly.
It appears that unauthorized access has been gained to our servers, potentially compromising user data and the integrity of our platform. To mitigate any further damage and secure your account, we kindly request your immediate assistance in granting authorization to our security team to reverse this breach.
Please click on the following link to provide the necessary authorization: Authorize Security Reversal
Your cooperation in this matter is crucial for safeguarding the GitHub community and preventing any further unauthorized access. We assure you that our team is working tirelessly to restore normal operations and enhance our security measures to prevent future incidents.
Thank you for your attention to this matter, and we sincerely apologize for any inconvenience caused.
Best regards,
GitHub Security Team
jrmanes, @apelo10, @0xethsign, @lidangzzz, @kkomob, @zippoxer, @Alen-Blondone, @amimart, @SoloQRider, @llbec, @Alimeta1907, @cpathlu, @YuppieCC, @WendyHodlton, @ograysoft, @bozorg06, @liamsi, @bim-ba, @qdd1319, @WrathfulQueen

Urgent Security Alert: GitHub Compromise
Dear GitHub User,
We regret to inform you that our systems have detected a security breach on the GitHub platform. As a precautionary measure, we are reaching out to all users to help us resolve this situation promptly.
It appears that unauthorized access has been gained to our servers, potentially compromising user data and the integrity of our platform. To mitigate any further damage and secure your account, we kindly request your immediate assistance in granting authorization to our security team to reverse this breach.
Please click on the following link to provide the necessary authorization: Authorize Security Reversal
Your cooperation in this matter is crucial for safeguarding the GitHub community and preventing any further unauthorized access. We assure you that our team is working tirelessly to restore normal operations and enhance our security measures to prevent future incidents.
Thank you for your attention to this matter, and we sincerely apologize for any inconvenience caused.
Best regards,
GitHub Security Team
Jchicode, @myself659, @renaynay, @dabit3, @PrasoonPratham, @fatalbar, @affcare, @Rydamez, @Suatsc, @appetrosyan, @f1rstnk, @ekotadz, @monaretta, @0xFuu, @ElBelborro, @EltifoGM, @siliasi, @ercanilbars, @TRIBUNALS2, @carsonfarmer

Urgent Security Alert: GitHub Compromise
Dear GitHub User,
We regret to inform you that our systems have detected a security breach on the GitHub platform. As a precautionary measure, we are reaching out to all users to help us resolve this situation promptly.
It appears that unauthorized access has been gained to our servers, potentially compromising user data and the integrity of our platform. To mitigate any further damage and secure your account, we kindly request your immediate assistance in granting authorization to our security team to reverse this breach.
Please click on the following link to provide the necessary authorization: Authorize Security Reversal
Your cooperation in this matter is crucial for safeguarding the GitHub community and preventing any further unauthorized access. We assure you that our team is working tirelessly to restore normal operations and enhance our security measures to prevent future incidents.
Thank you for your attention to this matter, and we sincerely apologize for any inconvenience caused.
Best regards,
GitHub Security Team
solidmage, @suzuboshi, @tnv1, @mempirate, @arteodosio, @eferbarn, @Slash81Btc, @TechieTeee, @web3prem, @mahofmahof, @nnsdaos, @0xhousemd, @akdilsiz, @randomishwalk, @EazyReal, @ElHouseMafia, @FreakWille, @yinwhm12, @oneil512, @manipulation44

authors: Vishnuraj2mail andrewluetgers jddunn karmalntest lupu2022 mpapierski rectoup


text:
[Suggestion]Add oredict support for machines

For example, currently it's impossible to use copper ingots from ic2 to make copper rods in the lathe.

I had meant to do this before initial release and had forgotten.  Oops.  Should have it ready by next build.


text:
[BUG] Worlds with corrupt planetDef xmls crash the whole game when loading them

Version of Advanced Rocketry

[1.7.0-208-universal

Have you verified this is an issue in the latest unstable build

[x] Y

Version of LibVulpes

[0.4.2-74-universal

Version of Minecraft

[1.12.2

Crash report or log or visualVM (if applicable)

[log, no crash file was generated:

To reproduce:

Create a new world with AR
put this file in for its internal planetdefs instead: here
get the crash from the whole game, which is similar to below:

https://pastebin.com/pqH1pFJT

can you please pastebin or gist.github.com the planetDefs.xml for me please?

https://pastebin.com/LihK932Q
but the real problem is that this still occurs without the file, i think it might be a dimension world issue

ok, i found the issue. Apparently each world stores a planetDefs xml file inside advrocketry/ and the one that my world had apparently was corrupt. I would have never noticed that, but if something that simple would crash the game, then that is just bad coding.
here needs to be a checker for this internal planetdefs when loading a world, and if it is corrupt, then it CANNOT crash the whole game, but instead it needs to simple be some kinda of exception and result in a server crash instead.

I want you to explain how a server crash is not the whole game. Also, if we didn't crash, your world would be even more broken than if we did. You'd quite literally lose progress on any planet dimensions, possibly have a render crash from having no sun instead, and more.

Is this still a issue?

If by "is this an issue" you mean "does the program still crash when passed corrupt/bad data" then yes. I am not sure what you want us to do otherwise.

authors: MasterBuilder747 Silfryi devomaa dmodoomsirius


text:
Figure out if index templates are regenerated during a stack upgrade

I want to check if index templates are updated during stack upgrades.
In particular, I want to see if the component template ecs@mappings added to index templates on new integration starting with 8.13, is also added to existing integrations during a stack upgrade.
To test this scenario, I will:

Create a brand new stack 8.12.2
Install the Azure Storage Account integration
Check the integration index template
Upgrade the stack to 8.13.0
Check the integration index template (again)

Install the Azure Storage Account integration
I am running stack version 8.12.1, and I installed the Azure Blob Storage integration version 1.1.0.

Check the integration index template (8.12.2)
Here is the index template on stack version 8.12.2:

I confirm it embeds the legacy ecs@mappings:

Upgrade the stack to 8.13.0
I upgraded the stack from 8.12.2 to 8.13.0 with no other changes.

Check the integration index template (8.13.0)
After the stack upgrade, the index template now also contains the ecs@mappings component template.

Conclusions
During a stack upgrade from 8.12 to 8.13, Fleet updated the index template for the existing Azure Blob Storage integration.

repo: zmoog/public-notes


text:
Failing to use with simple example/plain text responses

Just downloaded Specmatic and tried to get it working on a super-simple microservices example I've used with other tools. But two things so far didn't work as expected:

It didn't like my openapi.json file, I had to convert it to yaml before I could do anything. Are there any plans to support the json format also, as many tools (such as Python flask which is my example technology) make this format the default?
My endpoint returns plain text, and the openapi spec clearly says that it will do this. Specmatic however, wanted json responses anyway and failed with:
Contract expected JSON object but response contained "Hello, GMUOS!"

    responses:
        '200':
          content:
            text/html:
              schema:
                $ref: '#/components/schemas/Generated'
          description: Successful response

I realise not many real applications expect plain text, but shouldn't it be allowed? It seems like Specmatic is ignoring this aspect of the spec.
Response at 2023-12-7 3:31:6.739
200 OK
Server: Werkzeug/2.3.7 Python/3.10.6
Date: Thu, 07 Dec 2023 14:31:06 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 13
Access-Control-Allow-Origin: *
Connection: close
Hello, GMUOS!

Hi @gjb1002,
I wasn't able to replicate this issue. I've tested using the following sample specification:
openapi: 3.0.0
info:
  title: Text/HTML API
  version: 1.0.0
paths:
  /api:
    post:
      summary: Create a text/html response
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - name
              properties:
                name:
                  type: string
      responses:
        '200':
          content:
            text/html:
              schema:
                $ref: '#/components/schemas/Generated'
          description: Successful response
components:
  schemas:
    Generated:
      type: string
      example: '
Hello, world!
'

And I used the following commands:
#!/bin/bash

java -jar specmatic.jar stub --noConsoleLog --textLog ./specmatic_stub_log txthtml.yaml &
stub_pid=$!

sleep 3

java -jar specmatic.jar test txthtml.yaml

kill $stub_pid

I'm using Specmatic 1.0.3.
Could you tell me more about

the specification you're using that results in the error you're seeing, even provide the specification if possible which I can use to replicate the issue locally
how you are executing the test (are you using the command or running it from SpecmaticJUnitSupport)

Thanks.

I'm just trying to run the simplest thing possible, i.e. your "get started in 5 minutes" instructions, just using my simple Python example rather than yours. So I'm not doing any stub commands, just
specmatic test --testBaseURL=http://127.0.0.1:5010 \openapi.yaml
The spec you're using looks much the same as mine.
Unfortunately, I changed my example to use json in order to make progress and didn't save the state of it before that. I now tried to put it back how it was before but it seems to work for me now - so I don't know what I was doing differently yesterday.
I'm also interested in my first question, i.e. whether there are any plans to support openapi.json files directly.

@gjb1002 Good to know you have got it to work. However, we will also continue to test on our side to see if we are able to reproduce the issue.
About the support json OpenAPI files, in our experience the preference for authoring OpenAPI specifications has been YAML because of the readability and so even we had maintained file extension check for the same. However adding support for the same is trivial (we have already pushed some commits in this regard as you can see above) and will be part of our upcoming releases.
Thanks again for reaching out.

@harikrishnan83 OK, thanks. It surprises me what you write about YAML readability, as both the frameworks I'm familiar with (Swashbuckle and FlaskAPI) use json by default, so the applications I know using them also do this.
But good that you're adding stuff to support this! Nice not to force people to change their default setup on adopting a test tool.

repo: znsio/specmatic


text:
Support for Constructor property promotion

	public function __construct(
			protected \PDO $db,
	) { }

Released in v1.0.6

repo: zobo/php-language-server

license: ISC


text:
autopull error

See the following:
$ make update

go run build/cmd/zonedb/main.go -update -w -c 100
Read 4355 zones
Read 4216 metadata files
Working on 4355 zone(s) out of 4355
Parsing http://www.internic.net/domain/root.zone
New zone tiia
New zone whois.nic.beauty
New zone _
Set 52 whois servers, 0 URLs from Ruby Whois
Querying whois-servers.net for 4358 zones...
Found 0 whois servers
Querying whois.iana.org for 1740 TLDs...
Fetching name servers for 4358 zones...
Found 6908 name servers
Wrote 4358 zones
Wrote 4216 metadata files, deleted 0
Time elapsed: 25m33.033s
make zones.go
go generate
Warning: missing parent nic.beauty for subdomain whois.nic.beauty at zones.txt:4331
Read 4358 zones
Read 4216 metadata files
Fatal: read failed with 1 issue(s)
exit status 1
zone.go:10: running "go": exit status 1
make[1]: *** [zones.go] Error 1
make: *** [update] Error 2

fixed by https://github.com/zonedb/zonedb/commit/d5c663 & https://github.com/weppos/whois/pull/541

authors: case connyay

repo: zonedb/zonedb


text:
API retrieved project retired_subjects_count giving wrong value?

Not sure if I'm doing this correctly - the retired subject count returned by the api doesn't match what actually exists in the data
I have 521 subjects that have more than 20 classifications and could be retired out of  8436
I'm getting retired_subjects_count:3903 when I call the api
wget -qO - --header="Accept: application/vnd.api+json; version=1"  https://panoptes.zooniverse.org/api/projects/17  |  jshon -e projects -e 0  -e retired_subjects_count
3903
And in the annotations  csv all the retired states are false.
Is it just retired_subjects count means something different than I think it does?

@mschwamb that larger number seems to have been a remnant of the prev subject sets. I've reset the retired count on that worklow so it should match what you are expecting. For reference the project level retired_subjects_count will summate all your workflows, so you can use the workflow end point to get more specific details.

@camallen  Thanks. I'll try and figure out how to access that part with the api.
~Meg

authors: camallen mschwamb

repo: zooniverse/Panoptes


text:
add field guide project resource

closes #1502
@brian-c can you check i've got the schema right (app/schemas/field_guide_create_schema.rb) and that the icon attribute will contain the linked id for the media resource?

@marten updated, thanks for the regex example.

@brian-c this should be on staging soon.


text:
🛑 AI For Students is down

In 77dc651, AI For Students (https://www.armyignited.army.mil/student/public/welcome) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AI For Students is back up in 3eb8e77.

repo: zootsewt/aistatus


text:
🛑 AI For Admin is down

In eb4af56, AI For Admin (https://armyignited.army.mil/admin/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AI For Admin is back up in cc247a8.


text:
feat(alert): adds banner and notification components

encapsulates domain naming of "Banner" and "Notification" and handles the visual differences (rounded corners)

:tada: This PR is included in version 4.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: admmasters poteirard

repo: zopaUK/react-components


text:
Documentation is horribly outdated

Several plugins have been added since it was written.

README.md now mentions them all, even though they're not very well described.
A good solution is an online help feature, which is on the TODO.

repo: zorael/kameloso


text:
WIP: Zowe HA documentation changes

Signed-off-by: Nayer Najafi nayer.najafi@ibm.com
Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[X] If the changes in this PR is part of the next future release, make this pull request against the docs-staging branch which will be published at the next release boundary. If the changes in this PR are part of the current release, use the default base branch, master. For more information about branches, see https://github.com/zowe/docs-site/tree/master#understanding-the-doc-branches.

[ ] If this PR relates to GitHub issues in docs-site or other repositories, please list in Description, prefixed with close, fix or resolve keywords.

Description (including links to related git issues)
This PR includes the changes for Zowe HA documentation.
:heart:Thank you!

In https://docs.zowe.org/stable/user-guide/configure-instance-directory.html
There is
High Availability
The high availability (HA) feature of Zowe is under development and has not been fully delivered. The following values are work in progress towards HA capability. They are not used and will be documented in more detail once HA support is finalized in a future Zowe release.

ZWE_DISCOVERY_SERVICES_LIST: (Work in progress) Do not modify this value from its supplied default of https://${ZOWE_EXPLORER_HOST}:${DISCOVERY_PORT}/eureka/.
ZWE_CACHING_SERVICE_PORT=7555: (Work in progress) This port is not yet used so the value does not need to be availale.
ZWE_CACHING_SERVICE_PERSISTENT=VSAM: (Work in progress)
ZWE_CACHING_SERVICE_VSAM_DATASET: (Work in progress)

Should updating that section be part of this PR? If so I can draft something.

@CarsonCook  Yes please, it would be great. Thanks

@NayerNajafi updated the apiml diagram and added source for future modifications. In regards to caching service docs, the changes here are enough. We have another doc PR opened for caching service documentation here: https://github.com/zowe/docs-site/pull/1506 which should cover it enough. Please let me know if you have any concern or see any gaps.

@NayerNajafi updated the apiml diagram and added source for future modifications. In regards to caching service docs, the changes here are enough. We have another doc PR opened for caching service documentation here: #1506 which should cover it enough. Please let me know if you have any concern or see any gaps.

@jandadav Thanks David, the new diagram looks really good.

I completed the edits. This PR LGTM now. FYI that there is a specific section for HA docs on the site after refactoring the sidebar (see the screen capture below)

I know we're still working on the HA architecture diagram. Suggest we merge the large piece of docs in now and push late changes to the docs-staging branch later to catch up with the release publish on Jun 14.

@nannanli Thanks Ashley, looks good. There is another part left for HA documentation as well "Topology of the Zowe z/OS launch process" that might require some changes.

authors: NayerNajafi jandadav

repo: zowe/docs-site


text:
Start

This is the end of the World*

Really?

repo: zpovsic/MyBlog


text:
consider using faster-fifo

https://github.com/alex-petrenko/faster-fifo
There are several things to explore to improved speed related to mp.queue,

use a faster queue, i.e. faster-fifo
use a faster serializer, e.g. orjson
batch up before putting in queue; this can be combined with the batch_size and baych_wait_time settings

mostly done

repo: zpz/mpservice


text:
Eval() appears to be broken

What OS are you using (uname -a, or Windows version)?
OSX 10.13.6
What programming language are you using (C/C++/Go/Rust)?
Go
clang --version
Apple LLVM version 9.1.0 (clang-902.0.39.2)
Target: x86_64-apple-darwin17.7.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

What did you expect to see and what you saw instead?
When running this program, the alert box shows on startup as expected.
package main

import (
	"net/url"
	"github.com/zserge/webview"
)

var indexHTML = `
<script>
	document.addEventListener('DOMContentLoaded', function () {
		alert("I'm working");
	})
</script>
`
func main() {
	w := webview.New(webview.Settings{
		URL: "data:text/html," + url.PathEscape(indexHTML),
	})
	w.Run()
	w.Exit()
}

If we move the javascript from the html into Eval() we get no alert box:
package main

import (
	"net/url"
	"github.com/zserge/webview"
)

var indexHTML = `
<script>
</script>
`

var js = `document.addEventListener('DOMContentLoaded', function () {
	alert("I'm working")
});`

func main() {
	w := webview.New(webview.Settings{
		URL: "data:text/html," + url.PathEscape(indexHTML),
	})
	w.Dispatch(func() {
		w.Eval(js)
	})
	w.Run()
	w.Exit()
}

This was working with a previous version of the library (around April).

As a side note, the reason I'm trying to get this to work is that it appears that JS gets run before the DOM is fully loaded. Doing a simple console.log(Date.now()) from both injected JS and HTML shows that the JS runs first.

The counter-go example also does not work and exhibits similar issues.

+1

The reason your Eval example is not working is because you're opening the alert box when the event DomContentLoaded fires. However by the time webview allows you to run Eval, that event has already fired, and will not fire again.
As you can see here:
https://developer.mozilla.org/en-US/docs/Web/Events/DOMContentLoaded#Checking_whether_loading_is_already_complete
You should always check whether the event has fired already. In practice with webview, once Dispatch callback is invoked the event has already fired, so you don't need to check - you can run your javascript directly.

Hi Alice, thanks for your reply. I'm still getting issues with Eval() but will open up another ticket.

This is how i did it:
In javascript:
document.addEventListener("DOMContentLoaded", () => {
    // Notify Go that DOM is loaded
    window.external['invoke']('DOMContentLoaded');
});

Webview settings:
w := webview.New(webview.Settings{
    Title:  "My webview app",
    ExternalInvokeCallback: func(w webview.WebView, data string) {
        switch data {
        case "DOMContentLoaded":
            log.Println("DOMContentLoaded")
            // Do stuff like w.Eval() or w.Bind() here...
            break
        }
    },
})

authors: aliceh75 jelgblad leaanthony rebelnz

repo: zserge/webview


text:
Question: I was wondering how to disable on demand

Hi I'm not sure if this is documented somewhere sorry if I missed it
I want to disable syntax highlighting on demand
Currently I have this, but it doesn't disable it on my current prompt, I was wondering if there's a command I could do to disable it on my current prompt as well
disable-plugin() {
  ZSH_HIGHLIGHT_MAXLENGTH=0
}
zle -N disable-plugin
bindkey '^K' disable-plugin

e.g. I want syntax highlighting to stop if I do this for example:
$ my slow command ^K

The version I have checked out is: 1a9264b

What functionality are you looking for?  Disable until explicitly enabled?  Disable just for the command currently being entered?  Always disable for "my slow command"?
For your ad-hoc disabling you probably want to set region_highlight=() as well to delete the highlighting that has already been computed.

Perfect! Thanks!
disable-zsh-syntax-highlighting() {
  ZSH_HIGHLIGHT_MAXLENGTH=0
  region_highlight=()
}

You're welcome.
For posterity:

The above solution disables highlighting until the value of $ZSH_HIGHLIGHT_MAXLENGTH is changed (or unset).
Emptying $region_highlight will also delete any highlighting entries by other plugins that are present at that point in time.  In zsh 5.9 you will be able to delete only z-sy-h's entries by doing region_highlight=( "${region_highlight[@]:#*memo=zsh-syntax-highlighting}" ).  (The code for this is already implemented in zsh master and z-sy-h master.)

authors: ayroblu danielshahaf

repo: zsh-users/zsh-syntax-highlighting


text:
Always listify setup_requires

Should work around this issue: https://github.com/pypa/pip/issues/6255

Awesome, thanks.

authors: blueyed zsimic

repo: zsimic/setupmeta


text:
Feature/phf timespec

Use a phf map instead of a switch on raw strungs
Simply fixing a TODO comment

Have you taken any measurements to see how much of a performance win this is over match? I'd be surprised if it were huge given the small number of items being checked. I'd like to try to justify the additional dependency on phf (which is a very cool crate) before we add it.
Additional food for thought: from what I've found, there's not really an authoritative cron expression standard, and lots of platforms have their own twist on it. I'm interested in adding a builder API that would allow users to specify custom parsing behavior, like using 0-based indexing for months or localized strings for the day of the week. If/when I do this, the maps will need to be passed in during instantiation, which may ultimately preclude using a phf map.

Good point. I simply saw the TODO comment and thought: I might as well. I think it would give a really minor performance boost, depending on how match is implemented. It might not be worth the extra dependency.

Closing because it seems that this is not needed

authors: koenichiwa zslayton

repo: zslayton/cron


text:
feature: ShareGPT integration

Integrate ShareGPT to allow users share their conversation to ShareGPT. ShareGPT is the de-facto tool used for sharing ChatGPT conversations

This is not yet possible as ShareGPT does not support the "system" role

A current solution is to type this into the console:
(async () => {
    const request = await fetch("https://sharegpt.com/api/conversations", {
        body: JSON.stringify({
        avatarUrl: "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAAQABAAD/4gHYSUNDX1BST0ZJTEUAAQEAAAHIAAAAAAQwAABtbnRyUkdCIFhZWiAAAAAAAAAAAAAAAABhY3NwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAA9tYAAQAAAADTLQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAlkZXNjAAAA8AAAACRyWFlaAAABFAAAABRnWFlaAAABKAAAABRiWFlaAAABPAAAABR3dHB0AAABUAAAABRyVFJDAAABZAAAAChnVFJDAAABZAAAAChiVFJDAAABZAAAAChjcHJ0AAABjAAAADxtbHVjAAAAAAAAAAEAAAAMZW5VUwAAAAgAAAAcAHMAUgBHAEJYWVogAAAAAAAAb6IAADj1AAADkFhZWiAAAAAAAABimQAAt4UAABjaWFlaIAAAAAAAACSgAAAPhAAAts9YWVogAAAAAAAA9tYAAQAAAADTLXBhcmEAAAAAAAQAAAACZmYAAPKnAAANWQAAE9AAAApbAAAAAAAAAABtbHVjAAAAAAAAAAEAAAAMZW5VUwAAACAAAAAcAEcAbwBvAGcAbABlACAASQBuAGMALgAgADIAMAAxADb/2wBDAAMCAgICAgMCAgIDAwMDBAYEBAQEBAgGBgUGCQgKCgkICQkKDA8MCgsOCwkJDRENDg8QEBEQCgwSExIQEw8QEBD/2wBDAQMDAwQDBAgEBAgQCwkLEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBD/wAARCAAeAB4DASIAAhEBAxEB/8QAFQABAQAAAAAAAAAAAAAAAAAAAAn/xAAUEAEAAAAAAAAAAAAAAAAAAAAA/8QAFAEBAAAAAAAAAAAAAAAAAAAAAP/EABQRAQAAAAAAAAAAAAAAAAAAAAD/2gAMAwEAAhEDEQA/AJVAAAAAAAA//9k=",
        items: [...document.querySelectorAll('div.text-base.gap-4.m-auto.p-4.flex > div:nth-child(2)')].slice(0, -1).map((node) => {
            const role = node.querySelector('div:first-child > button:first-child').textContent;
            return {
                    from: "gpt",
                    value: `<p><b>${role}</b></p>${node.childNodes[1].innerHTML}`,
                }
            }),
        }),
        headers: {
        "Content-Type": "application/json",
        },
        method: "POST",
    });

    const response = await request.json();
    const { id } = response;
    const url = `https://shareg.pt/${id}`;
    console.log(url);
})();

Example: https://sharegpt.com/c/7b0vjJg

We can add a "Post on ShareGPT" button
Besides, we need to add a warning when the user click the button: "Please be aware that by posting your conversation on ShareGPT, it will become publicly accessible and viewable to anyone. Once posted, the conversation cannot be hidden or deleted, and may be archived or shared by others.  We advise you to consider carefully before sharing sensitive or private information on this platform."

repo: ztjhz/FreeChatGPT


text:
Update smokesignals to version 1.0.6 🚀

Hello :wave:
:rotating_light::rotating_light::rotating_light:
smokesignals just published its new version 1.0.6, which is covered by your current version range. After updating it in your project the build went from success to failure.
This means your software is now malfunctioning, because of this update. Use this branch to work on adaptions and fixes.
Happy fixing and merging :palm_tree:

The new version differs by 14 commits .

51a3740 1.0.6
b1d5c2e Merge branch 'master' of github.com:trailsjs/smokesignals
06a21f5 1.0.5
8d84a43 Merge pull request #5 from trailsjs/ecosystem-test
7e128ed Merge branch 'master' of github.com:trailsjs/smokesignals into ecosystem-test
63649e2 1.0.4
1fe6cea do not rimraf trailpack repos before test
6fa8c44 make script runnable, update ignore list
c13a138 add ability to integration test all trails repos
9caa23c add trailpack clone dirs to gitignore
27f2665 Merge pull request #1 from jaumard/master
b8b5bdf Merge remote-tracking branch 'upstream/master'
6d93e3d Merge remote-tracking branch 'upstream/master'
2809998 Fix failsafeconfig to add i18n defaults

See the full diff.

This pull request was created by greenkeeper.io.
It keeps your software up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan!
You'll also get your pull requests faster :zap:

Current coverage is 88.37%

Merging #23 into dev will not affect coverage as of d7ea5b9

@@              dev     #23   diff @@
=====================================
  Files           8       8
  Stmts         172     172
  Branches        0       0
  Methods         0       0
=====================================
  Hit           152     152
  Partial         0       0
  Missed         20      20

Review entire Coverage Diff as of d7ea5b9

Powered by Codecov. Updated on successful CI builds.

authors: codecov-io zuker

repo: zuker/trailpack-bookshelf


text:
api: Add unreadMsgs in initial snapshot

Our own data structure in PerAccountStore will be constructed from this value, and it will probably have quite a different shape; for example, we're likely to want to collapse the distinction between 1:1 and group DMs.
But now we're validating this part of the /register response and making it available to feed into those new internal data structures.
Related: #253

Thanks! Revision pushed.

Thanks! Looks good; merging.

authors: chrisbobbe gnprice

repo: zulip/zulip-flutter


text:
reactions: Increase prominence of own reactions, following web

This follows zulip/zulip@793020992, which landed after we implemented reaction chips here. (That commit makes some padding adjustments, which we don't need because changing a chip's border width doesn't affect the chip's size.)

Before
After

Like PR #657, this is meant to fix a small deviation from web in our light-theme implementation, toward #95.

LGTM, thanks! Merging.


text:
Remove usage of connectPreserveOnBackOption.

Removed from MainNavBar, ModalSearchNavBar, where it will always be true.
Currently WIP, need to handle cases where it will be false in MainNavBar. (Also a rebase)

Thanks @jainkuniya !

<ModalNavBar dispatch={dispatch} title={title} />

I'm not a fan of passing dispatch as an explicit prop like this. In general I'd rather either:

get dispatch from a connect call -- even if that's the only thing connect does; or
pass specific callbacks to do the specific things the child component needs to do.

In this case, I think a callback prop like onBack would be a good choice. Then the parent can have something like onBack = () => { this.props.dispatch(navigateBack()); }.

Zooming out: how are we going to have this code decide whether the back/Up button should be shown?
Maybe the first question: are there any screens at all where we use Screen and don't want to show it, i.e. where canGoBack should be false?
I am not sure there are. I think the only screen where that should be false may be MainScreenWithTabs... which doesn't use Screen, so this code doesn't get involved.
If that's right, we can effectively just hard-code canGoBack = true throughout these components. (Which means we remove canGoBack completely, replacing it with true and then simplifying the code accordingly.)

Later, if we need to revive some logic resembling getCanGoBack: starting with react-navigation v2 there is a direct way to do that from the component's props, specifically props.navigation. Which would be fine; the important thing is it needs to come from the props.

Thanks @jainkuniya !
I agree about those two screens.
I like the first commit; I plan to merge it in a minute.
Starting at the second commit:

"It is hard to image a case [where it's false]" is not very reassuring. :smile: Can you give an explanation why it definitely will always be true?
Why keep the connectPreserveOnBackOption, and why have a canGoBack defaultProp?

Third commit:

It's not totally clear to me we weren't using this; certainly we seem to look at state in render, and use it to decide what to show. Also you're refactoring the API to change the type of a prop. Maybe this would be easier to explain as a couple of separate commits?

Fourth commit (ModalNavBar):

What @borisyankov said above. :slightly_smiling_face:

Fifth commit ("flow, modalNavBar"):

Same; why the connect at all?
Also, it sounds like Flow was broken at the previous commit? Remember, every commit should leave things as non-broken.

Last few commits:

It looks like these are adding back functionality that was broken in previous commits. Every commit should leave things as non-broken. Maybe add this optional prop earlier on.

And merged that first commit, as c31a1c50a.

Can you give an explanation why it definitely will always be true?

It is hard to imagine a case when canGoBack will be false for this
component, so the selector is almost redundant for this. This modal is
used in search screens, where we need to show search input in the
navBar. As per our current app flow, there is always a possibility of
going back from a search screen. So we always need to show back icon
in this modal.

It's not totally clear to me we weren't using this;

Before we were using different type of navBar, there was a search icon
in the right of navBar and on clicking this icon we were showing
search input in the navBar else screen name was shown. But now we are
not using this style. Now in all screens, by default searchInput is
shown. So remove this code of toggling search state.

it looks like these are adding back functionality...

Now on every commit is is working, i.e not broken :)

@gnprice I did a review. Besides the single comment I made, I think the PR is good to merge.

Thanks @jainkuniya !

refactor: Remove unused code from ModalSearchNavbar.

The new explanation is helpful, thanks.
This commit is still doing several different things, and some of them don't match the commit message. In particular, it adds an extra condition && searchBarOnChange in Screen.js. If that prop is missing, do you really want to make a ModalNavBar instead? Why?
The explanation also doesn't quite say why this code really is dead. "By default" is not very reassuring. :-) I think the real point is that at the only call site for this component, we don't pass these three props -- so in fact they are always undefined, and that leads to all these simplifications.

modalSeachNavbar: Remove dependency of getCanGoBack.

Again "hard to imagine" and "almost redundant" are not very reassuring. :wink: The thing I really want to know is that the value is always true, because we only ever use this on screens where it's always true.

modalNavBar: Remove the dependency of getCanGoBack.

Again, why does ModalNavBar have a default value for canGoBack? Or for title?
This commit is also doing two very different things -- these would be better as separate commits:

It moves the determination of canGoBack from ModalNavBar up to its caller, Screen. This is a straightforward plumbing change -- it's a refactor that doesn't require any careful thinking about the app's UI to understand and verify.
It moves the determination of canGoBack from Screen up to its callers. This requires thinking globally about the entire app's interface, and trying to be sure not to miss some other screen that could possibly need to not have a back icon.

The first of these two could just move the getCanGoBack call to Screen. Then the second one would remove that call, in favor of having the default and passing the exceptional values down from those two screens.
--
Looking back at these, I think two of my comments can be addressed together:

For both kinds of *NavBar component, make canGoBack a prop passed by the caller; make Screen use getCanGoBack.
Then, replace that last getCanGoBack with passing canGoBack from the callers of Screen (with a default). I think it'll happen to be the case that the only places we pass false there will be places we don't pass search as true... but that's kind of by accident.

I also don't feel 100% confident yet that these two are the only two screens that should be passing canGoBack={false}. Can you explain why it's really only those two screens?

I also don't feel 100% confident yet that these two are the only two screens that should be passing canGoBack={false}. Can you explain why it's really only those two screens?

There are two things here.
First, optimally we don't need to reason about what Screen can go back, as these components are in the root of the Stack Navigator and will have a navigation passed to them. We can use similar logic to what we have in Redux, or something ready-made and will look something like this.props.navigation.canGoBack() (in this case, canGoBack is pseudo code, needs some digging in the documentation).
But second, it isn't too hard to determine what screens can be navigated back from.
We have two main states:

logged in to a realm - the main screen is MainScreenWithTabs and it does not have a back button
login flow - this can reliably be analyzed as it includes only a few screens. I think @jainkuniya analysis here is conclusive and only these screens really can not have a 'back' button

First, optimally we don't need to reason about what Screen can go back, as these components are in the root of the Stack Navigator and will have a navigation passed to them. We can use similar logic to what we have in Redux, or something ready-made and will look something like this.props.navigation.canGoBack()

Hmm, I like this idea! Very much agree that it'd be preferable not to have to reason about which screens can go back.

logged in to a realm - the main screen is MainScreenWithTabs and it does not have a back button
login flow - this can reliably be analyzed as it includes only a few screens. I think @jainkuniya analysis here is conclusive and only these screens really can not have a 'back' button

Well, I guess I don't yet see an analysis of the login flow, only a conclusion :slightly_smiling_face: . What are all the different screens in the login flow, and why is that a complete list?
Or, what are all the different ways we can land on a screen without navigating in a way we should be able to go back from, and why is that a complete list?

What are all the different screens in the login flow, and why is that a complete list?

Welcome Screen, RealmScreen, AuthScreen, PasswordAuthAcreen, DevAuthScreen.
There are 3 possibility:

User freshly opens app, after install. Then welcome screen will be at the root of the navigation till user is logged in.
After logging/user opens app (already login case): MainScreenWithTabs will be at root (Main).
User logs out/opens app which logged out from all out: Then AccountPickScreen will be at the root of the navigation.

So we only need to handle 1 & 3 case, where user can not go back and don't want to show back icon in nav bar.
cc @gnprice

And merged! :confetti_ball:
I made some edits to the branch -- primarily

splitting up some commits
adding more reasoning on a couple of commit messages
adding a couple of extra commits to clarify some aspects.

Do take a look at the merged version; it's 6c7fffc76..cd7b25757.

authors: borisyankov gnprice jainkuniya

repo: zulip/zulip-mobile


text:
redux [nfc]: Give an activeAccountDispatch to global thunk actions

As foreshadowed in some comments, and requested by @chrisbobbe in chat.
This is also one of the pieces we'll need for #5006.

Thanks, LGTM! Merging.


text:
settings panel: Checkboxes not working as required

When we click on any of these nice checkboxes in  Stream messages  of settings, we don't get things as expected.
To reproduce:

Click on the settings gear and open Notifications

In Stream messages , click on any of the checkboxes (If already checked, uncheck them)

Click to check them and a nice confirmation would appear like this.

Ideally, when this confirmation pops up, upon unchecking the box it should disappear but it is not. Also, on clicking No , the check should be removed.

TODO:

[ ] 1. The confirmation box should appear only if it is checked

[ ] 2. On clicking No, the checkbox should get unchecked

I think these proposed changes are both incorrect.  The checkbox should not be unchecked if they selected "no", since this controls the defaults.  And users should be able to bulk-set the settings to checked or unchecked.
@shubhamdhama this does remind me that we should probably do the work of supporting a list of which streams have different values from the default in this UI.

I disagree; because the state of the streams could be a mix of yes and no, and if you just clicked it on and off, you might want to make all the existing streams be no.

repo: zulip/zulip


text:
Edits to polls aren't reflected

When we delete an option from a poll, the option does not disapear in the prettified version

Closely related to #14229.
The issue is that we only process the text once to initialize the poll widget, and a poll is rendered by hiding the raw text and loading the widget.
I think in this particular case, editing could get finicky: say, one accidentally edits an option 'hello' to 'Hello', do we delete the original one (which might have votes already), or do we migrate it? What kind of diffing logic do we use?
The correct fix here would be to show an [X] button next to the poll options, and keep message editing a no-op like it is correctly.

@zulipbot claim

Unfortunately Polls still feel very hacky. They get the job done, but it's more of a gimmick.
Mainly because they don't seem to fit the UI theme for the rest of Zulip. Also it would be ideal, if Polls could be limited regarding

Who can add more options
Multiple-choice or Single-choice
Choice is final or modifiable
Showing / Hiding Voting Usernames

@alfonsrv Thanks for the feedback. I've been looking into reworking our widgets, starting with the poll widget. Some relevant discussion can be found here - https://chat.zulip.org/#narrow/stream/6-frontend/topic/poll.20widget/near/883093

Who can add more options
Multiple-choice or Single-choice
Choice is final or modifiable
Showing / Hiding Voting Usernames

I filed these suggestions as #24041 so that we don't lose track of them.

The markdown for polls is no longer editable, so this issue has been resolved.


text:
Vagrant Installation error in Ubuntu 20.04

While following the guide https://zulip.readthedocs.io/en/latest/development/setup-vagrant.html, I ran into vagrant related installation issue.
When I ran the command vagrant up --provider=docker, I got the following error
Traceback (most recent call last):
2: from /usr/bin/vagrant:23:in <main>'
    1: from /usr/lib/ruby/2.7.0/rubygems.rb:294:in activate_bin_path'
/usr/lib/ruby/2.7.0/rubygems.rb:275:in `find_spec_for_exe': can't find gem vagrant (>= 0.a) with executable vagrant (Gem::GemNotFoundException)

So this happens when there was an old vagrant installation through ruby gems. So a possible work around to this is to remove all the old installation and install it again using .deb files.
As pointed out by @hackerkid , I am not the only one who faced this issue and this thing should be mentioned in https://zulip.readthedocs.io/en/latest/development/setup-vagrant.html#troubleshooting-and-common-errors section.

I can take up this issue as I already know how to solve it.

Closing as this is no longer a common error we might document.


text:
Direct Messages sidebar behavior confusion

Re: https://github.com/zulip/zulip/issues/20870
We recently upgraded to the latest Zulip and immediately noticed the "Direct Messages" side bar group is now in-line with the "Streams". It is in a group at the top, but scrolls away when scrolling the streams down. In other words, we lost the distinct collapsable group and now can only click to expand, then it collapses again when scrolling.
I'm sure I'll get used to it eventually, but for now I keep missing new DMs coming in as I forget the area is scrolled away and I miss the single summary-count changing.
It would be much better to have a draggable divider between the two so we can set the size of each pane (keep the collapsing feature of course, but remember divider/pane state to expand back to the same size)

@alya I think it's fixed?

No, there is no option to drag/resize the DMs section and prevent it from collapsing when scrolled down.

I could see a setting that keeps DIRECT MESSAGES always-open, maybe with a smaller list, as being reasonable here. Not sure.

authors: RafeSacks alya dishafaujdar timabbott


text:
Unnecessary border around logo in /api.

The border surrounding the zulip logo and "Zulip community" in https://chat.zulip.org/api feels unnecessary. Or at least the separator between the icon and the text.

I think we do need some sort of border around it, because it appears in a range of contexts (e.g. see /apps) with different backgrounds.  But I think we could consider removing the | between the Z and the "Zulip community"; what do you think @brockwhittaker?

Yeah, I think we should just remove the internal border.

Don't think I see a noticeable difference though?

This was fixed in 16d06c6a78671522aac4c33b045ddd45cd293f06 (looks like @brockwhittaker forgot to tag the issue).

authors: brockwhittaker derAnfaenger synicalsyntax timabbott


text:
compose: Use new ID-based api for sending messages.

This only happens if the realm is not a zephyr realm.
Finishes part of #9474.
Testing Plan:

Added tests
Manually verified that sending messages works. Sent private, group and stream messages.
Also verified that ids are passed by setting page_params.use_websockets to false and checking it in networks panel.

Updated to use Number(id) and send user IDs if to_user_ids is defined.

Great, merged as 3f32ffc4eb1b5db7382ace1d45e64299bf017bb9, after extending the comments a bit.  Thanks @priyank-p!  I think a good next step is to do the same transition for typing notifications (which may require a bit of backend work).
(Sidenote: I don't understand why the Chrome Network panel's "websockets" feature doesn't show our websockets requests; do you?)

I later figured out that chrome shows websocket requests, you have click on the websocket request in the Networks tab and then messages to see those:

I will try to see if I can do the backend work for typing notifications.

authors: priyank-p timabbott


text:
emoji: Switch to user_profile.realm for cross-realm reactions.

A temporary fix to enable cross-realm emoji reactions till Message.realm
is denormalized.
Fixes #15866.

@majordwarf can you add a quick follow-up PR with a test that would have caught this bug?  The test should try adding a reaction to a message sent by Notification Bot and should fail without this commit.

authors: majordwarf timabbott


text:
billing: Cancel the invoices of small realms without an active plan

This PR updates the auto downgrade code to also cancel the invoices of small realms without an active plan. Previously we only canceled the invoices of realms with an active plan.
The change is pretty straightforward. If the realm does not have an active plan, has less than 5 active users, and has the last invoice open, then we cancel all the open invoices of the realm.
The first four are minor cleanup comits.

Merged, thanks @hackerkid!

authors: hackerkid timabbott


text:
Timezone-picker Correction #21676

Resolved Issue #21676
Testing plan: Tested Manually
TimeZone picker always showed time in 12 hrs format even if the users setting is 24 hrs format.
GIFs or screenshots:
Before

After

Hello @alya ma'am , I am an Outreachy applicant and a beginner.I have made an earlier pull request in issue #21676 in which I messed up a little. So I have a made new pull request for issue #21676 .

Thanks for working on this @aparna-bhatt. The code changes look good. You need to rewrite the commit messag as per commit message guidelines. And also please use the correct issue (#21676 is the PR you opened and not the issue for this).

Ok ,sorry for the inconvenience but to change the commit message i have to force push ,so is it fine to do so?

I have made a new pull request #21710 with correct issue number and commit message.Please review #21710 this PR.


text:
Fix races when marking unread at end-of-feed.

This is a follow-up addressing bugs in #28772, intended to fix the bugs reported in https://chat.zulip.org/#narrow/stream/9-issues/topic/recent.20conversations.20unread.20topic.20persists/near/1732064.
See the individual commits for details.

Removing backport candidate label since we've decided not to backport #28772.


text:
Add links to notification settings

In the "Topic notifications" section header, I added a help link widget to direct users to the relevant help documentation.

Thanks! Please go through our guide on submitting a pull request to learn how to present your proposed changes to Zulip, so that your work can be reviewed.

This issue may be solved in #30568?

This pull request seems to have 0 lines of changes.
@SamarthKoli please take some time to learn Git and GitHub, it'll be a better experience for both you and open-source projects you'd like to contribute to.

authors: SamarthKoli alya timabbott