text:
fix(fungible): remove BurnCoins usage

Description
Remove balance checking and burn
Add notice for usage with temporary context
Add unit tests for the method
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.

[ ] Tested CCTX in localnet
[ ] Tested in development environment
[x] Go unit tests
[ ] Go integration tests
[ ] Tested via GitHub Actions

Checklist:

[ ] I have added unit tests that prove my fix feature works

Do we have a run down of existing callers of MinZetaToEVMAccount and they are all using tmpCtx ?

Yes, there is a single stack of calls from a tmp ctx calling this one.

repo: zeta-chain/node


text:
Add filename option.

Hi zetachang,
I add a new option 'filename' to your babel-plugin-dotenv package to allow user to customize the filename of .env file. For example, in my project, I change it to 'build.env'.
please review it.

Sorry, I add a wrong commit into this PR. So, I close it.

source: gharchive/pull-request

repo: zetachang/react-native-dotenv

license: mit

license_type: permissive

license_source: bigquery


text:
Improving performance on loading any xml data

Hi,
What i found is after using pugi::parse_full flag instead of pugi::parse_default while loading, time taken to load large xml file was little less. Please verify if it is correct ?
And also is there any way to increase the performance on reading ?
Thanks

What i found is after using pugi::parse_full flag instead of pugi::parse_default while loading, time taken to load large xml file was little less. Please verify if it is correct ?

Generally speaking parse_full performance should be the same as that of parse_default. Can you share your performance numbers?

And also is there any way to increase the performance on reading ?

Can you elaborate?

Generally speaking parse_full performance should be the same as that of parse_default. Can you share your performance numbers?

Actually we just ran a test application and loaded 350MB xml file multiple times with parser_full and parse_default options. And we found that with parser_default, it was taking ~0.810897 secs (0.80 to .82 secs) to load and parser_full was taking taking ~0.80253 seconds  (from 0.79 secs to 0.81 secs).

Can you elaborate?

yes, actually i wanted to know, whether there are any other options / ways like parser_full / parser_default which has some impact in performance while loading. As for us, even a very little different can bring up a huge impact for our application.
-Thanks

It's somewhat surprising to see the delta in this direction - I'm assuming you're measuring just the document load time? Still, the delta is small enough that maybe it's either noise or some unexpected microarchitectural effect that happens to affect your document. The only significant difference is that parse_full preserves comments as node_comment nodes, but if you don't have many comments in the file I don't see why the parse time would be different at all.
In terms of optimizing the parsing times - please note that I'm only talking about the parsing into xml_document, but you should make sure that the processing time of the document is optimal as well - there's a few things you can make sure of / try:

parse_default consists of the following flags:

const unsigned int parse_default = parse_cdata | parse_escapes | parse_wconv_attribute | parse_eol;

parse_escapes performs escape processing by replacing " with " etc.
parse_wconv_attribute performs attribute value processing by substituting newlines with spaces inside attribute values
parse_eol performs newline normalization by replacing Windows newlines (\r\n) with Unix newlines (\n) inside PCDATA (text) blocks.
You can consider removing parse_wconv_attribute & parse_eol and parsing with just parse_cdata | parse_escapes, since this is usually harmless for most documents (aka the results are the same or similar). parse_escapes is usually necessary to get a correct parse. I don't think this will help too much but worth trying.

If you are using loading from std::istream, you should consider not doing that and letting pugixml load the file by itself (via load_file) or loading using some other mechanism (not istream) into memory and loading the document from memory. istreams aren't efficient and they will eat up into your loading time.

If you are loading from a memory buffer, you should consider using load_buffer_inplace if you use load_buffer - if the document doesn't go through encoding conversion, this is generally notably faster than load_buffer.

source: gharchive/issue

repo: zeux/pugixml


text:
🛑 JSONDiff Base is down

In 3b11238, JSONDiff Base (https://jsondiff.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: JSONDiff Base is back up in 774dae4.

repo: zgrossbart/jdd-upptime

license: MIT

license_source: github-api


text:
图层影响问题

中间显示centerBtn，弹出视图。切换到其他控制器里，push进入二级界面，数据在centerBtn的地方点击会弹出CenterBtn点击视图，发现多了层ContentView，最近更新的图层显示这个一直存在，作用是什么？

你可以参考下 #32


text:
Implementation of Recurrent Neural Network

Hi,
Thank you for developing this awesome library.  Can I take up the development of RNN for this library?

Yeah totally. Please take a look at the attention branch. Some initial design is there
https://github.com/zhangxiangxiao/xjax/blob/attention/xjax/xar.py
Feel free to use the design or ignore it.

Thank you, that's very helpful

Hi, I've looking at the codebase and trying to implement a RNN layer to get started. I've come across GRUCell in flax which can be used as a building block .
Do you think the RNN layer needs to be implemented from scratch can we add a wrapper around the existing functionality in flax?

The purpose of XJAX is to avoid the complexity of other frameworks such as FLAX. The XJAX simplicity should include the readibility of internal implementations, by exposing jax numerics directly. Therefore we should not wrap on FLAX.
That said, the FLAX codebase is a great source of reference for the numerical details on how to implement a module from scratch.

That makes perfect sense! Thank you

authors: zhangxiangxiao zigzagthad

repo: zhangxiangxiao/xjax


text:
Update cropper.vue

Use of mozImageSmoothingEnabled is deprecated. Please use the unprefixed imageSmoothingEnabled property instead

Changed proposed to match Mozilla new API and prevent the following warning: "Use of mozImageSmoothingEnabled is deprecated. Please use the unprefixed imageSmoothingEnabled property instead"

repo: zhanziyang/vue-croppa

license: isc


text:
🛑 ZY is down

In 991064d, ZY (https://ziyuan.baidu.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ZY is back up in 9e776d9.

repo: zhaodylan/uptime-ziyuan


text:
fix：在docker-compose.yml文件中增加时区设置

由于 docker 容器默认时区为0时区，在时间方面就会与东8区时间不一致。比如在使用 timetask 插件配置定时任务时，时间就会慢8小时。

感谢PR~

repo: zhayujie/chatgpt-on-wechat


text:
ize mismatch for encoder.embed_tokens.weight: copying a param with shape torch.Size([10096, 128]) from checkpoint, the shape in current model is torch.Size([151000, 128]).

     你好，我训练epoch 608时，就训练结束了:

2023-07-02 01:57:38 | INFO | fairseq_cli.train | end of epoch 608 (average epoch stats below)
2023-07-02 01:57:38 | INFO | train | {"epoch": 608, "train_loss": "3.663", "train_nll_loss": "1.275", "train_diffusion": "0.424", "train_word_ins": "3.224", "train_length": "0.151", "train_ppl": "12.67", "train_bleu": "0", "train_wps": "23834.3", "train_ups": "3.3", "train_wpb": "7233.2", "train_bsz": "309.9", "train_num_updates": "300000", "train_lr": "9.12871e-05", "train_gnorm": "2.611", "train_clip": "97.3", "train_loss_scale": "16384", "train_train_wall": "25", "train_wall": "55974"}
2023-07-02 01:57:38 | INFO | fairseq_cli.train | done training in 55973.7 seconds
并且请问checkpoint_last.pt文件就是difformer.pt吗？
我下载了您提供的difformer.pt和transformer.pt文件运行却报错：
RuntimeError: Error(s) in loading state_dict for Difformer:
size mismatch for encoder.embed_tokens.weight: copying a param with shape torch.Size([10096, 128]) from checkpoint, the shape in current model is torch.Size([151000, 128]).
size mismatch for decoder.embed_tokens.weight: copying a param with shape torch.Size([10096, 128]) from checkpoint, the shape in current model is torch.Size([151000, 128]).
size mismatch for decoder.output_projection.weight: copying a param with shape torch.Size([10096, 128]) from checkpoint, the shape in current model is torch.Size([151000, 128]).
Finished evaluate_step20_beam7x3. BLEU:
2023-07-02 12:54:26 | INFO | fairseq_cli.generate | loading model(s) from models/iwslt14_de_en/difformer.pt:models/iwslt14_de_en/transformer.pt
恕我愚钝，请问您能提供一些意见吗？

Hi, thanks for your interest.
The transformer.pt should share the same vocabulary with the difformer.pt. So if you train a model using your own vocabulary, a new Transformer trained with the same vocabulary is required.

想问一下，你最终找到哪一个是difformer.pt文件了吗

想问一下，你最终找到哪一个是difformer.pt文件了吗

If you download our released checkpoints here, the difformer.pt can be find at the difformer_release/models/<dataset>/difformer.pt.
If you would like to train your own model, checkpoints are at models/<dataset>/<model name>/ckpt, among which checkpoint_last.pt is the checkpoint saved after the training finished, and checkpoint_best.pt is the best checkpoint according to evaluation bleu score.

好的，谢谢您的回复
---- 回复的原邮件 ----
| 发件人 | Zhujin @.> |
| 日期 | 2023年12月15日 20:38 |
| 收件人 | @.> |
| 抄送至 | @.>@.> |
| 主题 | Re: [zhjgao/difformer] ize mismatch for encoder.embed_tokens.weight: copying a param with shape torch.Size([10096, 128]) from checkpoint, the shape in current model is torch.Size([151000, 128]). (Issue #4) |
想问一下，你最终找到哪一个是difformer.pt文件了吗
If you download our released checkpoints here, the difformer.pt can be find at the difformer_release/models//difformer.pt.
If you would like to train your own model, checkpoints are at models///ckpt, among which checkpoint_last.pt is the checkpoint saved after the training finished, and checkpoint_best.pt is the best checkpoint according to evaluation bleu score.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

authors: Markkk111 X-fxx zhjgao

repo: zhjgao/difformer


text:
🛑 腾讯云 CVM 节点 is down

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

HTTP code: 0
Response time: 0 ms

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

repo: zhonger/upptime


text:
🛑 腾讯云 COS 节点 is down

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

HTTP code: 0
Response time: 0 ms

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


text:
🛑 腾讯云 COS 节点 is down

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

HTTP code: 0
Response time: 0 ms

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


text:
🛑 腾讯云 CVM 节点 is down

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

HTTP code: 0
Response time: 0 ms

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


text:
NO gpu can run train.py?

because of some thing...cuda 'no run.
so.i want use CPU run,But it misstated that my gpu id wasn‘t specified.

Of course you can't run train.py without GPUs...

@zouzouwei I am afraid that you have to use GPUs. I used 4 V100 for this experiments.

authors: Gregory1994 zhongyy zouzouwei

repo: zhongyy/Face-Transformer


text:
There is no register 'pretrain_encoder'?

train_dict[cfg.train.mode](loggers, loaders, model, optimizer,scheduler)
KeyError: 'pretrain_encoder'

'pretrain_encoder' is registered in line 236 of lgd/train/pretrain_encoder.py - have you organized everything as in the repo?

Thank you for your response, the issue has been resolved!


text:
Training loss keeps increasing when I removed the distribute computation code and trained with Single GPU

Hello,
Thanks for your talent work.
Currently I want to recreate the training of the network with Sentinel 2-L2C images.
As I only have one GPU, I removed the code about distribute computation in https://github.com/zhu-xlab/SSL4EO-S12/blob/main/src/benchmark/pretrain_ssl/pretrain_moco_v2_s2c.py. Also , I revised the code for shuffle batch normalization (line 156~162 in https://github.com/zhu-xlab/SSL4EO-S12/blob/main/src/benchmark/pretrain_ssl/models/moco/builder.py ) .
After revising the code, I can run the training of the model. However, I can't see any improvement of the training loss. The training loss just kept increasing when the training epochs increased.
At first, I trained the model with the 100 patches subset (epochs= 100, batch_size = 32 ) and got the following training process :

Use GPU: 0 for training
=> creating model 'resnet50'
model created.
start training...
Epoch: [0][0/3]    Time  5.731 ( 5.731)    Data  0.957 ( 0.957)    Loss 6.5629e+00 (6.5629e+00)    Acc@1 100.00 (100.00)    Acc@5 100.00 (100.00)
0
Epoch: [1][0/3]    Time  0.872 ( 0.872)    Data  0.705 ( 0.705)    Loss 6.7108e+00 (6.7108e+00)    Acc@1   0.00 (  0.00)    Acc@5   3.12 (  3.12)
1
Epoch: [2][0/3]    Time  0.833 ( 0.833)    Data  0.665 ( 0.665)    Loss 6.7479e+00 (6.7479e+00)    Acc@1   0.00 (  0.00)    Acc@5   3.12 (  3.12)
2
Epoch: [3][0/3]    Time  0.798 ( 0.798)    Data  0.630 ( 0.630)    Loss 6.8232e+00 (6.8232e+00)    Acc@1   0.00 (  0.00)    Acc@5   3.12 (  3.12)
3
Epoch: [4][0/3]    Time  0.859 ( 0.859)    Data  0.691 ( 0.691)    Loss 6.8701e+00 (6.8701e+00)    Acc@1   0.00 (  0.00)    Acc@5   3.12 (  3.12)
4
Epoch: [5][0/3]    Time  0.820 ( 0.820)    Data  0.651 ( 0.651)    Loss 6.9370e+00 (6.9370e+00)    Acc@1   3.12 (  3.12)    Acc@5   9.38 (  9.38)
5
...
Epoch: [95][0/3]    Time  0.734 ( 0.734)    Data  0.563 ( 0.563)    Loss 8.8116e+00 (8.8116e+00)    Acc@1   9.38 (  9.38)    Acc@5  28.12 ( 28.12)
95
Epoch: [96][0/3]    Time  0.724 ( 0.724)    Data  0.555 ( 0.555)    Loss 8.8189e+00 (8.8189e+00)    Acc@1   6.25 (  6.25)    Acc@5  15.62 ( 15.62)
96
Epoch: [97][0/3]    Time  0.729 ( 0.729)    Data  0.559 ( 0.559)    Loss 8.8269e+00 (8.8269e+00)    Acc@1   6.25 (  6.25)    Acc@5  25.00 ( 25.00)
97
Epoch: [98][0/3]    Time  0.781 ( 0.781)    Data  0.607 ( 0.607)    Loss 8.8340e+00 (8.8340e+00)    Acc@1   0.00 (  0.00)    Acc@5   0.00 (  0.00)
98
Epoch: [99][0/3]    Time  0.747 ( 0.747)    Data  0.577 ( 0.577)    Loss 8.8407e+00 (8.8407e+00)    Acc@1   9.38 (  9.38)    Acc@5  34.38 ( 34.38)
99
Training finished.

Then I tried to conduct the training using 12800 patches in the 25K patches (epochs= 60, batch_size = 64), the training process is still similar like above.
Could you provide some suggestions about how to solve this problem?
Thanks very much for your help.

Hi! There could be many reasons for the loss not converging. Apart from the hyper-parameter tuning, single-GPU training could also affect it. How did you modify shuffle batch normalization? MoCo officially supports only multi-GPU DistributedDataParallel to shuffle BN across GPUs. For a single GPU, it is possible to simulate that with SplitBatchNorm. This colab demo on cifar10 might be helpful for your case.

Thanks for your reply.
I tried to simulate it with SplitBatchNorm, the training process is still same.
I made changes in two files pretrain_moco_v2_s2c.py and builder.py.
I upload the files I revised here https://github.com/ftongss/SSL4EO-Test.
It is appreciated if you can have a look at the code.
The configuration to run the code is:
--data C:/Users/ftong/Desktop/lmdb/example_100_patches.lmdb
--checkpoints C:/Users/ftong/Desktop/lmdb/checkpoints_100_patches
--bands B13
--lmdb
--arch resnet50
--workers 0
--batch-size 32
--epochs 100
--lr 0.03
--mlp
--moco-t 0.2
--aug-plus
--cos
--seed 42
--gpu 0
--mode s2c
--dtype uint8
--season augment
--in_size 224

Thanks for your help.

Are you using only 100 patches? It's probably not very meaningful, as the training dataset size is too small. If you only want the loss to converge, maybe you can try:

change the negative queue size, by default it is 65536 which exceeds 100 a lot.

parser.add_argument('--moco-k', default=65536, type=int, help='queue size; number of negative keys (default: 65536)')

turn off the data augmentation
start with a small learning rate
etc..


text:
Optimize images bundle with FluentUI

Optimize images bundle with FluentUI. Mainly macOS stuff.
Reducing size without losing quality.

非常感谢！


text:
No traffic to MQTT after upgrade

Description of problem:
Version upgraded to latest. Edge version will boot, non-edge version crashes immediately.
[16:16:51] INFO: MQTT available, fetching server detail ...
[16:16:52] INFO: MQTT credentials not configured, trying to auto-discovering ...
[16:16:52] INFO: Configuring'addons' mqtt user
If I monitor MQTT, absolutely nothing is received from zigbee2mqtt
Monitoring for this: Zigbee2MQTT:info  2021-02-12 16:16:59: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
All other devices using MQTT are working fine.

Do you have default mosquitto add-on? or you have your own custom mqtt? You can try setting credentials manually.
What version of the add-on are you running? What message do you get when it's crashing?

I had exactly the same problem. After installing 1.17.1 there was no connection between Zigbee2mqtt and Hassio anymore.
In the end the probleem seems to be something with the client_id in de Zigbee2mqtt configuration. I added the following to the config.
mqtt:
  client_id: zigbee

But I've to say I tried more. I also added some ports and IP addresses to the (Debian) firewall and I introduced a username and password for mqtt. Than I also added the following to '/usr/share/hassio/share/mosquitto/accesscontrollist'.
topic readwrite #

user [username]
topic readwrite #

I don't know what exactly helped to solve this, maybe someone knows.

I had this same issue and I think it is related to running zigbee2mqtt anonymously.
I fixed it by adding a zigbee2mqtt user to my Mosquitto config as follows:
logins:
  - username: zigbee2mqtt
    password: ************

Then this user needed to be added to my accesscontrollist (/usr/share/hassio/share/mosquitto/accesscontrollist), as mentioned by @Xites. My accesscontrollist file looks like this now:
topic readwrite #

user zigbee2mqtt
topic readwrite #

Then lastly I added this user to the zigbee2mqtt config as follows:
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto'
  user: zigbee2mqtt
  password: ************

I guess I finally got punished for running things in an insecure manner 😃

@EmilFlach Thanks a lot, you save my day (night really)
Have a beer and take care!
😃

authors: DaveOke EmilFlach Xites ciotlosm deltazerorsan


text:
Fix Crash when iPathId is INVALID_MOVEPATH_ID

https://github.com/ziggi/FCNPC/issues/266

I don't think that it's actually a fix.
GetPoint calls IsPointValid function witch validates path and point.
https://github.com/ziggi/FCNPC/blob/dc39c0cea61b9afaf859f761f3856872aff3e74d/src/CMovePath.cpp#L79-L86
https://github.com/ziggi/FCNPC/blob/dc39c0cea61b9afaf859f761f3856872aff3e74d/src/CMovePath.cpp#L39-L42

authors: devblackhunter ziggi

repo: ziggi/FCNPC


text:
[Device Support Request]

**Is your feature request related to a problem? Please describe.**I
I have an issue with tuya 2 gang and 3 gang light switch's, i was running a zha quirk up untill yesterday, this morning it doesnt seem to be having any effect.
the quirk resolved the issue of when pressing one button on the switch  within HA it would turn all lights on and not treat them as seperat entiteis.
This is on a 3 gang switch , TS0013 by _TZ3000_qewo8dlz and a 2 gang switch, TS0012by _TZ3000_18ejxno0.
Describe the solution you'd like
each button to trigger its corresponding light seperatly.

Diagnostic information
{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2023.4.4",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.10.10",
"docker": true,
"arch": "x86_64",
"timezone": "Europe/London",
"os_name": "Linux",
"os_version": "5.15.90",
"supervisor": "2023.04.0",
"host_os": "Home Assistant OS 9.5",
"docker_version": "20.10.22",
"chassis": "vm",
"run_as_root": true
},
"custom_components": {
"reolink_discovery": {
"version": "1.1.1",
"requirements": []
},
"dwains_dashboard": {
"version": "3.4.3",
"requirements": []
},
"alexa_media": {
"version": "4.6.2",
"requirements": [
"alexapy==1.26.5",
"packaging>=20.3",
"wrapt>=1.12.1"
]
},
"garbage_collection": {
"version": "4.10.2",
"requirements": [
"python-dateutil>=2.8.2"
]
},
"hacs": {
"version": "1.32.1",
"requirements": [
"aiogithubapi>=22.10.1"
]
},
"tapo_control": {
"version": "4.2.1",
"requirements": [
"pytapo==3.1.7",
"onvif-zeep-async==1.2.3"
]
}
},
"integration_manifest": {
"domain": "zha",
"name": "Zigbee Home Automation",
"after_dependencies": [
"onboarding",
"usb"
],
"codeowners": [
"@dmulcahey",
"@adminiuga",
"@puddly"
],
"config_flow": true,
"dependencies": [
"file_upload"
],
"documentation": "https://www.home-assistant.io/integrations/zha",
"iot_class": "local_polling",
"loggers": [
"aiosqlite",
"bellows",
"crccheck",
"pure_pcapy3",
"zhaquirks",
"zigpy",
"zigpy_deconz",
"zigpy_xbee",
"zigpy_zigate",
"zigpy_znp"
],
"requirements": [
"bellows==0.35.1",
"pyserial==3.5",
"pyserial-asyncio==0.6",
"zha-quirks==0.0.97",
"zigpy-deconz==0.20.0",
"zigpy==0.54.1",
"zigpy-xbee==0.17.0",
"zigpy-zigate==0.10.3",
"zigpy-znp==0.10.0"
],
"usb": [
{
"vid": "10C4",
"pid": "EA60",
"description": "2652",
"known_devices": [
"slae.sh cc2652rb stick"
]
},
{
"vid": "1A86",
"pid": "55D4",
"description": "sonoffplus*",
"known_devices": [
"sonoff zigbee dongle plus v2"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "sonoffplus*",
"known_devices": [
"sonoff zigbee dongle plus"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "tubeszb",
"known_devices": [
"TubesZB Coordinator"
]
},
{
"vid": "1A86",
"pid": "7523",
"description": "tubeszb",
"known_devices": [
"TubesZB Coordinator"
]
},
{
"vid": "1A86",
"pid": "7523",
"description": "zigstar",
"known_devices": [
"ZigStar Coordinators"
]
},
{
"vid": "1CF1",
"pid": "0030",
"description": "conbee",
"known_devices": [
"Conbee II"
]
},
{
"vid": "10C4",
"pid": "8A2A",
"description": "zigbee",
"known_devices": [
"Nortek HUSBZB-1"
]
},
{
"vid": "0403",
"pid": "6015",
"description": "zigate",
"known_devices": [
"ZiGate+"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "zigate",
"known_devices": [
"ZiGate"
]
},
{
"vid": "10C4",
"pid": "8B34",
"description": "bv 2010/10",
"known_devices": [
"Bitron Video AV2010/10"
]
}
],
"zeroconf": [
{
"type": "_esphomelib._tcp.local.",
"name": "tube*"
},
{
"type": "_zigate-zigbee-gateway._tcp.local.",
"name": "zigate"
},
{
"type": "_zigstar_gw._tcp.local.",
"name": "zigstar"
},
{
"type": "_slzb-06._tcp.local.",
"name": "slzb-06*"
}
],
"is_built_in": true
},
"data": {
"ieee": "REDACTED",
"nwk": 36096,
"manufacturer": "_TZ3000_18ejxno0",
"model": "TS0012",
"name": "_TZ3000_18ejxno0 TS0012",
"quirk_applied": true,
"quirk_class": "zhaquirks.tuya.ts001x.TuyaDoubleNoNeutralSwitch_2",
"manufacturer_code": 4417,
"power_source": "Battery or Unknown",
"lqi": 127,
"rssi": null,
"last_seen": "2023-04-16T19:54:19",
"available": true,
"device_type": "EndDevice",
"signature": {
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006"
],
"out_clusters": [
"0x0019"
]
},
"2": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0004",
"0x0005",
"0x0006"
],
"out_clusters": []
}
}
},
"active_coordinator": false,
"entities": [
{
"entity_id": "button.tz3000_18ejxno0_ts0012_identify",
"name": "_TZ3000_18ejxno0 TS0012"
},
{
"entity_id": "light.tz3000_18ejxno0_ts0012_light",
"name": "_TZ3000_18ejxno0 TS0012"
},
{
"entity_id": "light.tz3000_18ejxno0_ts0012_light_2",
"name": "_TZ3000_18ejxno0 TS0012"
}
],
"neighbors": [],
"routes": [],
"endpoint_names": [
{
"name": "ON_OFF_LIGHT"
},
{
"name": "ON_OFF_LIGHT"
}
],
"user_given_name": null,
"device_reg_id": "13a3340bd81b5ec325e1f26e200fb09f",
"area_id": null,
"cluster_details": {
"1": {
"device_type": {
"name": "ON_OFF_LIGHT",
"id": 256
},
"profile_id": 260,
"in_clusters": {
"0x0000": {
"endpoint_attribute": "basic",
"attributes": {},
"unsupported_attributes": {}
},
"0x0003": {
"endpoint_attribute": "identify",
"attributes": {},
"unsupported_attributes": {}
},
"0x0004": {
"endpoint_attribute": "groups",
"attributes": {},
"unsupported_attributes": {}
},
"0x0005": {
"endpoint_attribute": "scenes",
"attributes": {},
"unsupported_attributes": {}
},
"0x0006": {
"endpoint_attribute": "on_off",
"attributes": {
"0x0000": {
"attribute_name": "on_off",
"value": 0
},
"0x4001": {
"attribute_name": "on_time",
"value": 0
},
"0x4002": {
"attribute_name": "off_wait_time",
"value": 0
},
"0x8001": {
"attribute_name": "backlight_mode",
"value": 1
},
"0x8002": {
"attribute_name": "power_on_state",
"value": 0
}
},
"unsupported_attributes": {}
}
},
"out_clusters": {
"0x0019": {
"endpoint_attribute": "ota",
"attributes": {},
"unsupported_attributes": {}
}
}
},
"2": {
"device_type": {
"name": "ON_OFF_LIGHT",
"id": 256
},
"profile_id": 260,
"in_clusters": {
"0x0004": {
"endpoint_attribute": "groups",
"attributes": {},
"unsupported_attributes": {}
},
"0x0005": {
"endpoint_attribute": "scenes",
"attributes": {},
"unsupported_attributes": {}
},
"0x0006": {
"endpoint_attribute": "on_off",
"attributes": {
"0x0000": {
"attribute_name": "on_off",
"value": 1
},
"0x4001": {
"attribute_name": "on_time",
"value": 0
},
"0x4002": {
"attribute_name": "off_wait_time",
"value": 0
}
},
"unsupported_attributes": {}
}
},
"out_clusters": {}
}
}
}
}
3 gang!
{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2023.4.4",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.10.10",
"docker": true,
"arch": "x86_64",
"timezone": "Europe/London",
"os_name": "Linux",
"os_version": "5.15.90",
"supervisor": "2023.04.0",
"host_os": "Home Assistant OS 9.5",
"docker_version": "20.10.22",
"chassis": "vm",
"run_as_root": true
},
"custom_components": {
"reolink_discovery": {
"version": "1.1.1",
"requirements": []
},
"dwains_dashboard": {
"version": "3.4.3",
"requirements": []
},
"alexa_media": {
"version": "4.6.2",
"requirements": [
"alexapy==1.26.5",
"packaging>=20.3",
"wrapt>=1.12.1"
]
},
"garbage_collection": {
"version": "4.10.2",
"requirements": [
"python-dateutil>=2.8.2"
]
},
"hacs": {
"version": "1.32.1",
"requirements": [
"aiogithubapi>=22.10.1"
]
},
"tapo_control": {
"version": "4.2.1",
"requirements": [
"pytapo==3.1.7",
"onvif-zeep-async==1.2.3"
]
}
},
"integration_manifest": {
"domain": "zha",
"name": "Zigbee Home Automation",
"after_dependencies": [
"onboarding",
"usb"
],
"codeowners": [
"@dmulcahey",
"@adminiuga",
"@puddly"
],
"config_flow": true,
"dependencies": [
"file_upload"
],
"documentation": "https://www.home-assistant.io/integrations/zha",
"iot_class": "local_polling",
"loggers": [
"aiosqlite",
"bellows",
"crccheck",
"pure_pcapy3",
"zhaquirks",
"zigpy",
"zigpy_deconz",
"zigpy_xbee",
"zigpy_zigate",
"zigpy_znp"
],
"requirements": [
"bellows==0.35.1",
"pyserial==3.5",
"pyserial-asyncio==0.6",
"zha-quirks==0.0.97",
"zigpy-deconz==0.20.0",
"zigpy==0.54.1",
"zigpy-xbee==0.17.0",
"zigpy-zigate==0.10.3",
"zigpy-znp==0.10.0"
],
"usb": [
{
"vid": "10C4",
"pid": "EA60",
"description": "2652",
"known_devices": [
"slae.sh cc2652rb stick"
]
},
{
"vid": "1A86",
"pid": "55D4",
"description": "sonoffplus*",
"known_devices": [
"sonoff zigbee dongle plus v2"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "sonoffplus*",
"known_devices": [
"sonoff zigbee dongle plus"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "tubeszb",
"known_devices": [
"TubesZB Coordinator"
]
},
{
"vid": "1A86",
"pid": "7523",
"description": "tubeszb",
"known_devices": [
"TubesZB Coordinator"
]
},
{
"vid": "1A86",
"pid": "7523",
"description": "zigstar",
"known_devices": [
"ZigStar Coordinators"
]
},
{
"vid": "1CF1",
"pid": "0030",
"description": "conbee",
"known_devices": [
"Conbee II"
]
},
{
"vid": "10C4",
"pid": "8A2A",
"description": "zigbee",
"known_devices": [
"Nortek HUSBZB-1"
]
},
{
"vid": "0403",
"pid": "6015",
"description": "zigate",
"known_devices": [
"ZiGate+"
]
},
{
"vid": "10C4",
"pid": "EA60",
"description": "zigate",
"known_devices": [
"ZiGate"
]
},
{
"vid": "10C4",
"pid": "8B34",
"description": "bv 2010/10",
"known_devices": [
"Bitron Video AV2010/10"
]
}
],
"zeroconf": [
{
"type": "_esphomelib._tcp.local.",
"name": "tube*"
},
{
"type": "_zigate-zigbee-gateway._tcp.local.",
"name": "zigate"
},
{
"type": "_zigstar_gw._tcp.local.",
"name": "zigstar"
},
{
"type": "_slzb-06._tcp.local.",
"name": "slzb-06*"
}
],
"is_built_in": true
},
"data": {
"ieee": "REDACTED",
"nwk": 16195,
"manufacturer": "_TZ3000_qewo8dlz",
"model": "TS0013",
"name": "_TZ3000_qewo8dlz TS0013",
"quirk_applied": true,
"quirk_class": "zhaquirks.tuya.ts001x.TuyaTripleNoNeutralSwitch_2",
"manufacturer_code": 4417,
"power_source": "Battery or Unknown",
"lqi": 171,
"rssi": null,
"last_seen": "2023-04-16T19:56:09",
"available": true,
"device_type": "EndDevice",
"signature": {
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006"
],
"out_clusters": [
"0x0019"
]
},
"2": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0004",
"0x0005",
"0x0006"
],
"out_clusters": []
},
"3": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0004",
"0x0005",
"0x0006"
],
"out_clusters": []
}
}
},
"active_coordinator": false,
"entities": [
{
"entity_id": "button.tz3000_qewo8dlz_ts0013_identify",
"name": "_TZ3000_qewo8dlz TS0013"
},
{
"entity_id": "light.tz3000_qewo8dlz_ts0013_light",
"name": "_TZ3000_qewo8dlz TS0013"
},
{
"entity_id": "light.tz3000_qewo8dlz_ts0013_light_2",
"name": "_TZ3000_qewo8dlz TS0013"
},
{
"entity_id": "light.tz3000_qewo8dlz_ts0013_light_3",
"name": "_TZ3000_qewo8dlz TS0013"
}
],
"neighbors": [],
"routes": [],
"endpoint_names": [
{
"name": "ON_OFF_LIGHT"
},
{
"name": "ON_OFF_LIGHT"
},
{
"name": "ON_OFF_LIGHT"
}
],
"user_given_name": null,
"device_reg_id": "2ef33d77f9539a98aa7b2039d1eb950a",
"area_id": null,
"cluster_details": {
"1": {
"device_type": {
"name": "ON_OFF_LIGHT",
"id": 256
},
"profile_id": 260,
"in_clusters": {
"0x0000": {
"endpoint_attribute": "basic",
"attributes": {
"0x0004": {
"attribute_name": "manufacturer",
"value": "_TZ3000_qewo8dlz"
},
"0x0005": {
"attribute_name": "model",
"value": "TS0013"
}
},
"unsupported_attributes": {}
},
"0x0003": {
"endpoint_attribute": "identify",
"attributes": {},
"unsupported_attributes": {}
},
"0x0004": {
"endpoint_attribute": "groups",
"attributes": {},
"unsupported_attributes": {}
},
"0x0005": {
"endpoint_attribute": "scenes",
"attributes": {},
"unsupported_attributes": {}
},
"0x0006": {
"endpoint_attribute": "on_off",
"attributes": {
"0x0000": {
"attribute_name": "on_off",
"value": 1
},
"0x4001": {
"attribute_name": "on_time",
"value": 0
},
"0x4002": {
"attribute_name": "off_wait_time",
"value": 0
},
"0x8001": {
"attribute_name": "backlight_mode",
"value": 1
},
"0x8002": {
"attribute_name": "power_on_state",
"value": 0
}
},
"unsupported_attributes": {}
}
},
"out_clusters": {
"0x0019": {
"endpoint_attribute": "ota",
"attributes": {},
"unsupported_attributes": {}
}
}
},
"2": {
"device_type": {
"name": "ON_OFF_LIGHT",
"id": 256
},
"profile_id": 260,
"in_clusters": {
"0x0004": {
"endpoint_attribute": "groups",
"attributes": {},
"unsupported_attributes": {}
},
"0x0005": {
"endpoint_attribute": "scenes",
"attributes": {},
"unsupported_attributes": {}
},
"0x0006": {
"endpoint_attribute": "on_off",
"attributes": {
"0x0000": {
"attribute_name": "on_off",
"value": 0
},
"0x4001": {
"attribute_name": "on_time",
"value": 0
},
"0x4002": {
"attribute_name": "off_wait_time",
"value": 0
}
},
"unsupported_attributes": {}
}
},
"out_clusters": {}
},
"3": {
"device_type": {
"name": "ON_OFF_LIGHT",
"id": 256
},
"profile_id": 260,
"in_clusters": {
"0x0004": {
"endpoint_attribute": "groups",
"attributes": {},
"unsupported_attributes": {}
},
"0x0005": {
"endpoint_attribute": "scenes",
"attributes": {},
"unsupported_attributes": {}
},
"0x0006": {
"endpoint_attribute": "on_off",
"attributes": {
"0x0000": {
"attribute_name": "on_off",
"value": 1
},
"0x4001": {
"attribute_name": "on_time",
"value": 0
},
"0x4002": {
"attribute_name": "off_wait_time",
"value": 0
}
},
"unsupported_attributes": {}
}
},
"out_clusters": {}
}
}
}
}

Additional logs
Paste any additional debug logs here.
Don't remove the extra line breaks outside the ``` marks.

Additional context
Add any other context or screenshots about the feature request here.

Have you checked if you have any errors in the logs, even during the HA startup?
From your report it would seem that the device needs the 'Tuya spell' but this should not happen without a device reset.
Try to remove one of your devices from HA, wait a couple of minutes and pair it again.

Hi,  this happened around the same time I was configuring a new home network.  The home assistant server was down for awhile.  I have tried repairing several times buy. With no luck,  I've even setup a clean install of home assistant and added just one of these lights,  still same issue.  I'm still very green to home assistant so will dpmy best to check logs.

So it doesn't comes from nowhere, you were making changes in ZHA and the quirk seems not being working now.

I have tried repairing several times buy

Ok, but do you have tried the way I was suggesting?

Try to remove one of your devices from HA, wait a couple of minutes and pair it again.

You can enable the debug logs during the pairing of the device and attach it here.
Also, you can check the HA logs even during the startup to see if you catch any ZHA related error:
https://www.home-assistant.io/integrations/logger/#viewing-logs

Should be fixed with HA Core 2023.9.0 and later.

authors: Horley900 TheJulianJES javicalle

repo: zigpy/zha-device-handlers


text:
Critical Crash caused AAIC

Hello,
I'm creating this issue because I noticed that AAIC caused LSPDFR to crash when I died (not during a callout)
Theses are the logs, can you please have a look ?
logs on pastebin
Thanks you in advance

Hi again, this is an other critical crash, that instantly fully crashed the game
https://pastebin.com/SqyxT7vv

I would need the full log to determin which version you are using


text:
Introduce a command line interface.

This commit introduces a command line interface (CLI) to facilitate the execution of the benchmark independently of a Streamlit application. CLI commands have been developed for the following clients: Milvus, pgvector, Redis, Weaviate Cloud, and Zilliz Cloud. The README.md file has been revised to include instructions on running the benchmark and integrating the command line option with new or existing clients.
This commit also has some general cleanups as well.
Co-authored-by: Tyler House tahouse@users.noreply.github.com

/assign @xuanyang-cn

/ #330

/assign @greenhal

/assign @XuanYang-cn

@greenhal I am absolutely thrilled and deeply grateful for your incredible contribution to our project! The new CLI support you developed is going to make a huge difference for our users, and I can't wait to get it integrated and released.
Please know that I'm committed to reviewing your pull request as soon as possible. I'll give it my full attention and care to make sure it gets merged smoothly.
Again, thank you from the bottom of my heart. I'm proud and humbled to have you as part of our community. Looking forward to many more amazing collaborations ahead!

Any questions on this PR?

repo: zilliztech/VectorDBBench


text:
lower the OS scheduling priority of knowhere threads

Set the OS scheduling priority of knowhere threads to the lowest possible value(a nice value of 19, which is the lowest possible value for a non real time scheduling policy)
/kind improvement

/hold

Good catch!!!!
/lgtm

/unhold

authors: buqian-zilliz liliu-z zhengbuqian

repo: zilliztech/knowhere


text:
zaino-test feature

Adds zaino-test feature, conditionally removes a single line of code in zingolib::testutils::regtest.rs.
This is required for zaino-testutils to be able to write its own zcashd conf files for integration tests.

This PR is work towards https://github.com/zingolabs/zaino/issues/48

it wont let me approve though

repo: zingolabs/zingolib


text:
Update aws-java-sdk-core to 1.12.608

About this PR
📦 Updates com.amazonaws:aws-java-sdk-core from 1.12.459 to 1.12.608
Usage
✅ Please merge!
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!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #676.

repo: zio/zio-flow


text:
Update scalafmt-core to 3.7.9

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.7.7 to 3.7.9
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
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!

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

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #183.

repo: zio/zio-parser


text:
Update logback-classic to 1.4.7

About this PR
📦 Updates ch.qos.logback:logback-classic from 1.2.12 to 1.4.7
Usage
✅ Please merge!
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!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.qos.logback", artifactId = "logback-classic" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "ch.qos.logback", artifactId = "logback-classic" }
}]

labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #284.

repo: zio/zio-protoquill


text:
Console doesn't translate all elements on language switch (missing translations?)

Acceptance Critiera

[ ] Console UI does only change the translations when i saved the language on my profile, not when I change it

There are some missing tanslations in console, especially the audit trail (but also in subnavigations, on dates and the 'instance' button in the header)

FYI: I added the frontend labe because of the date translations. They are probably frontend related (?)

CC @peintnermax

At the moment as soon as I change the language in my profile, the console is translated.
It should translate only if I save it.

will close this issue, had a look at the console looks fine to me

authors: fforootd hifabienne juergrinaldi

repo: zitadel/zitadel


text:
Causation and Correlation of events

In todays system architecture it is common that a request causes actions in multiple subsystems. Understanding the cause of an action can therefore get extremely difficult if systems don't allow to correlate calls to the root cause.
To allow admins of ZITADEL to deeply analyze the flow of requests ZITADEL should provide a possibility to assign requests to an identifier (id) of the cause why commands were written to the eventstore and furthermore add this as fields to the logs.
Event driven systems want to correlate events received by different systems including ZITADEL.
The goal of this issue is to

understand the use case stated above
understand current techniques
describe the solution architecture
result in user stories

Tracing
Tracing allows decoupled systems to share context information about a request lifetime. As event driven systems are split into asynchronous procedures reacting to events which happened earlier in time tracing is not a suitable solution for these scenarios. Additionally tracing allows to define a fraction of traces created meaning that not every request will be assigned a trace id.
Causation and correlation
Causation and Correlation allow event driven systems to follow a request through multiple systems. For example a system creates a user in ZITADEL based on an event which is caused in this system.
Systems like evenstoredb or rails event store allow to store correlation and causation-ids on each event.
Let's use the following cite of supply chain management for dummies as definition:

Correlation and causation are closely related. Correlation means that two variables are connected in some way. Causation means that one variable causes another to occur.

This means that each API request to the command side can result in n events stored with the given correlation id. The correlation id is passed to the API or generated by the middleware of the API.
If multiple events are created during the same call the first event should have the same correlation and causation ids, the next event should get the previous events id as causation id analog to the following picture:

Changes to ZITADEL
This concept would require the following changes to ZITADEL

Generate an event id (currently the following pattern is used as unique identifier: {instance-id}:{aggregate-type}:{aggregate-id}:{sequence})

possible solution without breaking change would be a computed column which hashes the current unique identifier

Extend events by causation and correlation id (including columns in database)
Create middleware to use passed ids or generate the ids and set it to context.Context
Change eventstore.Push to automatically set the correct causation id
Extend the log lib to always add the ids as fields to logs

Pass the context to the lib in all log calls

Maybe: add ids to trace metadata
Return the ids in the ListEvents-API call

cc @fforootd @yordis


text:
fix: use triggering origin for notification links

Closes #6587, #5844
Enables #5395
The PR changes which origins are used in notification links.
Previous behavior

Assets (Logo): The instances primary domain was used.
Verification Links: If available in the triggering event, a URL template was parsed and used without further modification. If the template was not enabled, the instances primary domain was used.

New behavior

Assets (Logo): If available in the triggering event, the property triggerOrigin is used to construct the URL. If not available, the instances primary domain is used.
Verification Links: If available in the triggering event, a URL template is still parsed and used without further modification. If the template is not available, the property triggerOrigin is used to construct the URL. If triggerOrigin isn't available neither, the instances primary domain is used to construct the URL.
The origin is extracted from the calling context when new events are created.

Deviations from the AC

Used the more precise terminology "origin" instead of "base url"
Uses the same origin for asset links like for actionable links

Other notes

Refactors the notifications package so that all side effects are mockable.
It shouldn't be breaking, as the asset URLs must already be servable from the primary domain or the origin domain.

Origin source
The origin is added to each request context.
It is constructed from the Forwarded header if available, else from the requests Host header (host and port) and TLS settings (scheme). This aligns the behavior for retrieving information from reverse proxies to the way OIDC issuer information is retrieved. I suggest using the Forwarded header also for discovering virtual instances with #5395 and cleaning up the docs.
Definition of Ready

[ ] I am happy with the code
[ ] Short description of the feature/issue is added in the pr description
[ ] PR is linked to the corresponding user story
[ ] Acceptance criteria are met
[ ] All open todos and follow ups are defined in a new ticket and justified
[ ] Deviations from the acceptance criteria and design are agreed with the PO and documented.
[ ] No debug or dead code
[ ] My code has no repetitions
[ ] Critical parts are tested automatically
[ ] Where possible E2E tests are implemented
[ ] Documentation/examples are up-to-date
[ ] All non-functional requirements are met
[ ] Functionality of the acceptance criteria is checked manually on the dev system.

One more comment:
Acceptance criteria mention:

Update docs, maybe deprecate primary domain

I didn't see a documentation update in this PR.

I changed the logic for building the origin.
It is constructed from the Forwarded header if available, else from the more widely supported X-Forwarded-* headers, else from the requests Host header (host and port) and TLS settings (scheme).
I suggest using this logic for discovering virtual instances (AC for #5395?) and also for the OIDC issuer (follow-up issue?).
@muhlemmer what do you think?

One more comment:
Acceptance criteria mention:

Update docs, maybe deprecate primary domain

I didn't see a documentation update in this PR.

The changes should be opaque to the users, so I think documenting it would introduce more confusion than clarity. I also looked through the current documentation and I didn't find any text that needs to be changed. @hifabienne is it ok to skip this AC?

authors: eliobischof muhlemmer


text:
Questions about dataset description and production

Your work is great, I have run the sample experiments, but I would like to know what the files within the onepose_datasets/sample_data represent and how they are made, like poses_ba. And how to make my own dataset for new object pose estimation.

Hi, Ginger. Have you found how to make custom training images?

sorry, I have no idea.


text:
Use Docker Compose to speed up relayer setup

Currently several steps are required to run the relayer and, depending on the host environment, different issues may arise. Moreover, the section "Running Relayer as Docker container" of the documentation seems not up to date:

During the build of Relayer.Dockerfile the process throws on this step
RUN --mount=type=cache,target=/var/cache/yarn \  bash -i -c "yarn" \   && rm -rf /var/lib/yarn/lists/*
the final CMD is commented

My suggestion is to add a docker-compose.yml file to orchestrate all the components of the relayer (prover + db + relayer core service), in order to simplify the setup process.

Thanks for the feedback, this will be useful to decentralize our relayer. The docker file is a bit out of date as well.

@guidocazzaniga Can you run the Dockerfile again and share the logs?

Sure, sorry for the late reply. When I build the Docker image, the process stops with the following error:
> [stage-0  7/12] RUN --mount=type=cache,target=/var/cache/yarn     bash -i -c "yarn"     && rm -rf /var/lib/yarn/lists/*:
0.222 bash: cannot set terminal process group (1): Inappropriate ioctl for device
0.222 bash: no job control in this shell
0.502 yarn install v1.22.22
0.601 [1/5] Validating package.json...
0.611 [2/5] Resolving packages...
1.010 [3/5] Fetching packages...
63.37 error Command failed.
63.37 Exit code: 128
63.37 Command: git
63.37 Arguments: clone https://github.com/sampritipanda/snarkjs.git /usr/local/share/.cache/yarn/v6/.tmp/474b65c5f6b3eb2df7af062f1c2abfa6
63.37 Directory: /relayer
63.37 Output:
63.37 Cloning into '/usr/local/share/.cache/yarn/v6/.tmp/474b65c5f6b3eb2df7af062f1c2abfa6'...
63.37 error: 6476 bytes of body are still expected
63.37 fetch-pack: unexpected disconnect while reading sideband packet
63.37 fatal: early EOF
63.37 fatal: fetch-pack: invalid index-pack output
63.37 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
------
Relayer.Dockerfile:29
--------------------
  28 |     # Install Yarn dependencies with caching
  29 | >>> RUN --mount=type=cache,target=/var/cache/yarn \
  30 | >>>     bash -i -c "yarn" \
  31 | >>>     && rm -rf /var/lib/yarn/lists/*
  32 |
--------------------
ERROR: failed to solve: process "/bin/bash -c bash -i -c \"yarn\"     && rm -rf /var/lib/yarn/lists/*" did not complete successfully: exit code: 128

Unfortunately I'm currently working on Windows 10 on my home network (no proxies), but my colleague noticed the same issue on macOS as well (on a different network).

Resolved on the latest version of MacOS with cb85247.

repo: zkemail/email-wallet


text:
ngx_openidc_module.so version 1016001 instead of 1021000

Hi,
I am trying to implement the ngx_openid_module into Nginx Reverse Proxy.
I've managed to install all the dependencies (jansson, libmemcache, cjose, liboauth2, etc) and installed the ngx_openid_module rpm.  However during startup, nginx is complaining about the module version
nginx: [emerg] module "/usr/lib64/nginx/modules/ngx_openidc_module.so" version 1016001 instead of 1021000 in /etc/nginx/nginx.conf:8
I've tried to recompile the module following the steps here but it seems like the git do not have the config file for recompiling.
Any idea how can I solve the version issue?
The nginx I have is
# nginx -v
nginx version: nginx/1.21.0

what distribution are you on?

I'm running the RP on RHEL7

it seems you're not running the stock NGINX version 1.16.0 then

The Nginx package were installed using Yum
So to use this module, we'll need to stick with v1.16.0?

ok, I see that the stock NGINX version has been updated in the mean time; I'll update the RPM shortly; you'll have to compile from scratch in the mean time

I'm getting 1.20.1 now... https://centos.pkgs.org/7/epel-x86_64/nginx-1.20.1-2.el7.x86_64.rpm.html

I tried recompiling following this
But the git repo is missing the config file, how else can I compile the module?

Hi @zandbelt, are you able to advise on how to compile the module from github?

use ./autogen.sh first

authors: wongkeewee zandbelt


text:
Request: ability to "backup" a project

Continued from / related to https://github.com/zooniverse/Panoptes-Front-End/issues/1273
It would be great to have a way to export / import a text representation of a project and its workflows and subject sets (ignoring the actual subjects). That way people could "save" their project to their own computers.
Alternatively -- or in addition -- it would be nice to have a project versioning system so that people could (A) try alternative approaches in creating their projects; and (B) revert to an earlier draft of the project in case something went terribly wrong (e.g. a collaborator deleted all the workflows by mistake).
Discussion warranted, as the former puts more responsibility on the end-user, but should be fairly easy to implement. The latter is more complicated and puts the responsibility for "backing-up" on Zooniverse, but is more sophisticated and perhaps more user-friendly.

I wonder if the system @aliburchard and @brian-c have cooked up for Serengeti-style projects could help here - a csv file containing Workflow data.

On 30 Jul 2015, at 20:34, Margaret Kosmala notifications@github.com wrote:
Continued from / related to zooniverse/Panoptes-Front-End#1273 (comment) https://github.com/zooniverse/Panoptes-Front-End/issues/1273#issuecomment-126315168
It would be great to have a way to export / import a text representation of a project and its workflows and subject sets (ignoring the actual subjects). That way people could "save" their project to their own computers.
Alternatively -- or in addition -- it would be nice to have a project versioning system so that people could (A) try alternative approaches in creating their projects; and (B) revert to an earlier draft of the project in case something went terribly wrong (e.g. a collaborator deleted all the workflows by mistake).
Discussion warranted, as the former puts more responsibility on the end-user, but should be fairly easy to implement. The latter is more complicated and puts the responsibility for "backing-up" on Zooniverse, but is more sophisticated and perhaps more user-friendly.
—
Reply to this email directly or view it on GitHub https://github.com/zooniverse/Panoptes/issues/1225.

It should be easy to import/export data (it's all JSON anyway), but nearly impossible to debug errors if someone changes the file manually (and they will).

What's the status of this?
We've been working on some customized aggregations using zooniverse/aggregation as a starting point, and right now that code queries Panoptes directly to get workflows. It would be much better to just read them from an exported workflow csv, but I don't think we have access to one.

@vrooje I'll add it to the future plans.
Are you actually manipulating stuff from the workflow? Or just want to save a request against Panoptes?

I just want to save it - no need to change anything.

While I think this is a good idea in principle, I can see how this might be better dealt as an API client feature, without needing special backend support for it. Closing it here, if anyone wants this feel free to work on it in the scope of panoptes-python-client or similar.

authors: brian-c chrislintott edpaget marten mkosmala vrooje

repo: zooniverse/Panoptes


text:
Puma config missing

This is broken in staging:
/usr/local/lib/ruby/gems/2.2.0/gems/puma-2.15.3/lib/puma/dsl.rb:20:in `read': No such file or directory @ rb_sysopen - config/puma (Errno::ENOENT)
        from /usr/local/lib/ruby/gems/2.2.0/gems/puma-2.15.3/lib/puma/dsl.rb:20:in `_load_from'
        from /usr/local/lib/ruby/gems/2.2.0/gems/puma-2.15.3/lib/puma/dsl.rb:9:in `block in load'
        from /usr/local/lib/ruby/gems/2.2.0/gems/puma-2.15.3/lib/puma/dsl.rb:8:in `tap'
        from /usr/local/lib/ruby/gems/2.2.0/gems/puma-2.15.3/lib/puma/dsl.rb:8:in `load'
        from /usr/local/lib/ruby/gems/2.2.0/gems/puma-2.15.3/lib/puma/configuration.rb:57:in `load'
        from /usr/local/lib/ruby/gems/2.2.0/gems/puma-2.15.3/lib/puma/cli.rb:543:in `parse_options'
        from /usr/local/lib/ruby/gems/2.2.0/gems/puma-2.15.3/lib/puma/cli.rb:189:in `run'
        from /usr/local/lib/ruby/gems/2.2.0/gems/puma-2.15.3/bin/puma:10:in `<top (required)>'
        from /usr/local/bin/puma:23:in `load'

Fixed by #1495


text:
Duplicate case value 'CNAuthorizationStatusDenied'

Before submitting a new issue

[X] I tested using the latest version of the library, as the bug might be already fixed.
[X] I tested using a supported version of react native.
[X] I checked for possible duplicate issues, with possible answers.

Bug summary
iOS build gives Duplicate case value 'CNAuthorizationStatusDenied' error in RNPermissionHandlerContacts
Library version
5.0.2
Environment info
System:
  OS: macOS 14.3.1
  CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
  Memory: 51.84 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.18.2
    path: ~/.nvm/versions/node/v18.18.2/bin/node
  Yarn:
    version: 1.22.4
    path: /usr/local/bin/yarn
  npm:
    version: 9.8.1
    path: ~/.nvm/versions/node/v18.18.2/bin/npm
  Watchman:
    version: 2023.10.30.00
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.2 AI-242.23339.11.2421.12483815
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.1
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.0.0
    wanted: ^15.0.0
  react:
    installed: 18.3.1
    wanted: ^18.3.1
  react-native:
    installed: 0.76.0
    wanted: ^0.76.0
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: false

Steps to reproduce
Try to build the package in xcode
Reproducible sample code
N/A

You need Xcode 16, it's in the release notes.

repo: zoontek/react-native-permissions


text:
🛑 AI For Admin is down

In 27f431b, 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 c620bb5.

repo: zootsewt/aistatus


text:
Feature request: gutterWidth prop

Would be great to have a gutterWidth prop that takes a number or array (left, right).

You can already set the gutterWidth (one number only though) through context types, have you tried that?

Just tried putting 0 in and it isn't working. My guess is gutterWidth || defaultGutterWidth. I hacked it together with "0".

Good point about the falsy 0, that is definitely something which should be fixed.

@gerbenmeyer would love this to be implement soon, I keep getting warning errors.

This should be fixed now in the latest version (2.0.4).

authors: gerbenmeyer volkandkaya

repo: zoover/react-grid-system


text:
ui.Eval does not return a value

Grabbing HTML value from document via Eval returns no value. Not sure if this is a bug or I have bad HTML. I do not get any runtime errors.
My code
package main

import (
	"fmt"
	"net/url"

	"github.com/zserge/lorca"
)

var (
	ui1        lorca.UI
	HTML_entry string = `
<html>
    <body>
        <input hidden type="text" name="MYVAR" value="testVal">
        <input type="submit" onclick="golangfunc()"
    </body>
</html>
`
)

func main() {
	ui1, _ = lorca.New("data:text/html,"+url.PathEscape(HTML_entry), "", 480, 320)
	ui1.Bind("golangfunc", golangfunc)
	defer ui1.Close()
	<-ui1.Done()
}

func golangfunc() {
	htmlvar := ui1.Eval(`document.getElementsByName('MYVAR').value`).String()
	fmt.Println(htmlvar)
}

I dont think its with Eval , it probably the getElementsByName() is undefined , can you do getElementById and specify and Id to the the control in the dom

@vinchauhan I do need to get elements by name, I thought HTML5 has this & I'm not getting an error when using it, but it doesn't return any value either. As for the panic though, I had accidentally created a local var ui1 using := instead of = which caused the panic. However, I still don't have the MYVAR value.

@vinchauhan I do need to get it by name rather than ID. Is there another way of getting by name? I have an arbitrary number of input fields to work with & the HTML I'm working on is being generated. I also tried changing to getElementById just to test, but still no value coming through.

@cmdpwnd - I tested it last night but I didnt have any luck with the panic - Unfortunately I am unable to go get the package from the place I am at at the moment. I will check again tonight.
I am planning to use this package myself to give GUI to my cli based api testing tool.

@vinchauhan Yes, I corrected the panic err - sorry forgot to mention - just needed to change the ui1 declaration in main() from := to = since it was already declared globally. Let me know if you get anywhere with passing that value.

@cmdpwnd - It works with getElementById.
package main
import (
"fmt"
"net/url"
"github.com/zserge/lorca"

)
var (
ui1        lorca.UI
HTML_entry = `

`
)
func main() {
ui1, _ = lorca.New("data:text/html,"+url.PathEscape(HTML_entry), "", 480, 320)
ui1.Bind("golangfunc", golangfunc)
defer ui1.Close()
<-ui1.Done()
}
func golangfunc() {
htmlvar := ui1.Eval(document.getElementById('MYVAR').value).String()
fmt.Println(htmlvar)
}

authors: cmdpwnd vinchauhan

repo: zserge/lorca


text:
Support @topic wildcard mentions

This Zulip feature (https://zulip.com/help/mention-a-user-or-group#mention-all-topic-participants).
API docs: https://zulip.com/api/update-message-flags#available-flags
Relevant discussions: https://chat.zulip.org/#narrow/stream/378-api-design/topic/highlight.20topic-wildcard.20mention/near/1621613

This has a couple of different parts, which we might split into several issues when we start working on it.

Understanding the new pair of flags for stream/channel vs. wildcard mentions.
Offering these in autocomplete, as part of #234.
Highlighting these in the message list: #646, #647.

OK, I've split this up into those more-specific issues, and edited the comment above to point to them. Closing this umbrella issue in favor of using those to track the work.

repo: zulip/zulip-flutter


text:
Fix a message loading bug and improve behavior

The behavior of 'needFetchAtFirstUnread' is quite wrong.
First, we do the minimal work to fix #3441 in the first commit.
The rest of the work implements correctly the originally intended behavior.

Thanks @borisyankov ! This indeed looks like an effective fix.
The PR summary says later commits implement the intended "do we need to fetch" behavior. I see some welcome simplifications which might make it easier to do that, but I don't see the actual new logic in the current branch. Are there more changes you intended to push?
The last commit moves the function to a selectors file. I'm not sure that's actually helpful; perhaps it'll be clearer one way or the other in the presence of the change that adds back more logic. It's true that the function is a pure function, one of whose arguments is the state... but semantically it feels to me like part of the decision-making of the "fetch messages" logic here in messages/fetchActions.
I.e., the choices we've made that are embedded in it are choices about when and what we fetch (and the other code with those choices is in this file), and not about what data structures we maintain (which is the set of choices that are embedded in selectors and reducers).

Merged, except that last commit (moving to a selectors module), and with a quick commit on top adding a comment. Thanks again!
If you already have in your head (or on your disk) a clear idea of what the more sophisticated logic ought to be, I'd be glad to see that in a further PR.

authors: borisyankov gnprice

repo: zulip/zulip-mobile


text:
Test and document support for Amazon RDS as the database

Following #13092, it should be possible to use Amazon RDS (and similar database services) as the database for Zulip.  We should test doing that (installing a zulip server off master) and document what's required in terms of installation steps (the main thing being what one should pass in  https://zulip.readthedocs.io/en/latest/production/deployment.html#running-zulip-s-service-dependencies-on-different-machines).

@zulipbot claim

@timabbott @andersk So I tested this using the DigitalOcean DB service and I am getting this error.
Operations to perform:
  Apply all migrations: analytics, auth, confirmation, contenttypes, otp_static, otp_totp, pgroonga, sessions, social_django, two_factor, zerver
Running migrations:
  Applying zerver.0001_initial...Traceback (most recent call last):
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/db/backends/utils.py", line 62, in execute
    return self.cursor.execute(sql)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zerver/lib/db.py", line 31, in execute
    return wrapper_execute(self, super().execute, query, vars)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zerver/lib/db.py", line 18, in wrapper_execute
    return action(sql, params)
psycopg2.errors.ConfigFileError: could not open dictionary file "/usr/pgsql-11/share/tsearch_data/en_us.dict": No such file or directory

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "./manage.py", line 46, in <module>
    execute_from_command_line(sys.argv)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 364, in execute_from_command_line
    utility.execute()
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 356, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/core/management/base.py", line 283, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/core/management/base.py", line 330, in execute
    output = self.handle(*args, **options)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 204, in handle
    fake_initial=fake_initial,
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 115, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 145, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 244, in apply_migration
    state = migration.apply(state, schema_editor)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/db/migrations/migration.py", line 129, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/db/migrations/operations/special.py", line 108, in database_forwards
    self._run_sql(schema_editor, self.sql)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/db/migrations/operations/special.py", line 133, in _run_sql
    schema_editor.execute(statement, params=None)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 136, in execute
    cursor.execute(sql, params)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/db/utils.py", line 94, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/utils/six.py", line 685, in reraise
    raise value.with_traceback(tb)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zulip-py3-venv/lib/python3.6/site-packages/django/db/backends/utils.py", line 62, in execute
    return self.cursor.execute(sql)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zerver/lib/db.py", line 31, in execute
    return wrapper_execute(self, super().execute, query, vars)
  File "/home/zulip/deployments/2019-09-30-10-59-50/zerver/lib/db.py", line 18, in wrapper_execute
    return action(sql, params)
django.db.utils.InternalError: could not open dictionary file "/usr/pgsql-11/share/tsearch_data/en_us.dict": No such file or directory

The issue seems to be that the postgres server doesn't have the fulltext search dictionary files that our provisioning code installs under "/usr/pgsql-11/share/tsearch_data/en_us.dict".  I googled a bit and don't think there's a way to do this; we should email Digital Ocean support to see if there's some undocumented way to upload full-text search dictionaries.
RDS seems to not have it either: https://forums.aws.amazon.com/message.jspa?messageID=626892
Can you try patching this line in 0001_initial.py to not specify the DictFile, AffFile, and StopWords arguments and see if it installs?
CREATE TEXT SEARCH DICTIONARY english_us_hunspell
  (template = ispell, DictFile = en_us, AffFile = en_us, StopWords = zulip_english);

Reading https://www.postgresql.org/docs/10/textsearch-dictionaries.html, we should figure out whether the defaults do something reasonable.

Can you try patching this line in 0001_initial.py to not specify the DictFile, AffFile, and StopWords arguments and see if it installs?

This does not work.
zulip=> CREATE TEXT SEARCH DICTIONARY english_us_hunspell (template = ispell);
ERROR:  missing AffFile parameter

Its not possible to create an ispell dictionary without specyfing DictFile and AffFile. And postgresql does not ship with any ispell files that can be used as default.

The standard PostgreSQL distribution does not include any Ispell configuration files. Dictionaries for a large number of languages are available from Ispell.
https://www.postgresql.org/docs/current/textsearch-dictionaries.html#TEXTSEARCH-ISPELL-DICTIONARY

Reading postgresql.org/docs/10/textsearch-dictionaries.html, we should figure out whether the defaults do something reasonable

By this do you mean to just use the default pg_catalog.english configuration and dont make any alterations?
CREATE TEXT SEARCH CONFIGURATION zulip.english_us_search (COPY=pg_catalog.english);

zulip=> \dF+ english_us_search
Text search configuration "zulip.english_us_search"
Parser: "pg_catalog.default"
      Token      | Dictionaries
-----------------+--------------
 asciihword      | english_stem
 asciiword       | english_stem
 email           | simple
 file            | simple
 float           | simple
 host            | simple
 hword           | english_stem
 hword_asciipart | english_stem
 hword_numpart   | simple
 hword_part      | english_stem
 int             | simple
 numhword        | simple
 numword         | simple
 sfloat          | simple
 uint            | simple
 url             | simple
 url_path        | simple
 version         | simple
 word            | english_stem

This does work and results in completion of installation using remote Posgresql DB. But not sure how good the search would be if we dont use the ispell dictionaries.
On another note I had to first create zulip schema in Posgresql using psql manually by remotely logging in as zulip user to make ./manage.py apply migrations run sucesffully. Otherwise it was throwing this error.
django.db.utils.ProgrammingError: schema "zulip" does not exist

Makes sense.  I think this is probably something we can support but should just document the issue with full-text search: That full-text search will be worse and that, and let users decide how they want to handle that tradeoff?
Can you try writing a docs section in docs/production/deployment.md covering the right setup process?
(For the full-text search thing, I assume we'll need code changes; we can potentially implement it as a special environment variable, ZULIP_POSTGRES_DICTIONARIES_UNAVAILABLE that the migration code reads?)

@zulipbot claim

@timabbott  Should I create a puppet class for installations that use remote DB or pass all the necessary puppet classes as env variables? If its second case I would need to show two example in docs, one for debian and one for redhat. If its the first case what do you suggest the class name to be?

Puppet reads the classes (and all other configuration) to use from /etc/zulip/zulip.conf; so if there's a configuration flag we need there, it should live there.  Grep for zulipconf if needed.  If you just need a flag, we can use that without making duplicate Puppet classes, which would be a lot cleaner.

(But I don't feel like I know clearly enough where you need changes to configure this; may be helpful to make a WIP PR that just makes changes unconditionally for RDS and then I can advice on how to put the options in)

@zulipbot claim

Fixed via #13472.

authors: hackerkid timabbott

repo: zulip/zulip


text:
buttons / text input invisible in mobile web view

hello,
i was testing mobile web view because i was told several times, that the native mobile apps suck.
i'm quite impressed, how nice mobile web view works, but there seem some issues.
after creating a new stream in safari or firefox on iphone X, i cannot post to the stream.
it looks like the buttons/fields are missing, but they are there but seem to be invisble.
if you type"blindly" (with guessing/remembering the right positions), you can send a message. afterwards, the gui elements magically appear.
if you want to delete a message, the delete screen is nearly invisible (no matter if normal mode or dark mode) and delete does not work, too.
if you want to reproduce, create a new stream and try to post...

@vinitS101 @Gittenburg any idea what the bug is here?

I cannot reproduce this with Firefox on Android, so this might be iPhone specific but I don't have an iPhone to reproduce.

Yeah, I can reproduce this on my iPhone. I think it also happened once a little while back and I shrugged it off as the keyboard glitching (and hence covering the compose box).
I'll try to debug this.

when creating a new stream in mobile web view on iphone, the button on the upper right is invisible, too.  looks pretty broken.

Hi I would like to contribute to solving this issue

please feel free to do so !
https://zulip.readthedocs.io/en/latest/overview/contributing.html


text:
Ensure all realm changes have RealmAuditLog entries

Perform an audit of all properties of a realm, and ensure that all of them trigger a RealmAuditLog entry.
One specific case which is known to be missing is changes to RealmDomain lists.

@zulipbot claim


text:
Make it possible to override 1-week delay for Zulip notices at the server level

In #28604 / https://github.com/zulip/zulip/pull/28720, we added a system for posting automatic updates into Zulip. There is a 1-week delay between admins being notified about this new system, and the first updated being posted.
We should make it possible for self-hosted server admins to remove that delay, so that their users can get updated for the new server version right away.

@prakhar1144 FYI; we should pick this up closer to the release date (not now).

This was completed in bc0325922e3cc52dde902ce2a52bc8fd735fe526.

authors: alya timabbott


text:
Alert not visible when scrolled down

If a user scrolls down more than the screen height, alert becomes invisible as it is positioned static.

This could be solved by making it fixed and also there is no way to hide the alert it remains there until the next action is taken.

Not much of a big issue but fixing it would be great for UX.

Thanks for the report!  This definitely should be fixed.  The idea of making it fixed at the top rather than in the scrollable section is pretty reasonable; the other approach we could take is having it appear inside the individual stream's "Administrator settings" block (which would probably be more readily visible for the user, and save a bit of work if we were to eventually move the per-stream details blocks into a modal, separate screen, or whatnot).
@wdaher for his thoughts.

Either option works for me.
On Sun, Mar 13, 2016 at 9:31 AM, Tim Abbott notifications@github.com
wrote:

Thanks for the report! This definitely should be fixed. The idea of making
it fixed at the top rather than in the scrollable section is pretty
reasonable; the other approach we could take is having it appear inside the
individual stream's "Administrator settings" block (which would probably be
more readily visible for the user, and save a bit of work if we were to
eventually move the per-stream details blocks into a modal, separate
screen, or whatnot).
@wdaher https://github.com/wdaher for his thoughts.
—
Reply to this email directly or view it on GitHub
https://github.com/zulip/zulip/issues/515#issuecomment-195838906.

Yeah, having inside the "Administrator settings" block is a good idea rather than floating it around hindering the view.Can I take this as my next project?

Go for it!

@timabbott Adding warnings inside the administrator settings block isn't a very good idea,

Sometimes even administrator settings block gets even bigger than the screen height, so having a warning inside doesn't solve the issue in the first place.
2)Non-uniformity, all the 'create new stream' warnings(and some others) will be displayed outside the administrator settings block.

I'm inclining towards the idea of making it fixed at the top. What do you think?
PS- I've implemented the code for warnings inside the "Administrator settings" block, if you want to have a look.

@disissid that reasoning makes sense to me, let's have it be fixed at the top.

authors: disissid timabbott wdaher


text:
populate_db: Increase entropy of messages generated

We have a new generate_test_data framework for generating test messages, which is great in that it includes a bunch of rich syntax now, but it definitely still needs work to increase the variability in the messages it generates.

A pretty straightforward way would be to use itertools.permutations-- in load_generators we could use a random int i from 0 to n! and then choose the i-th permutation to be the one which itertools.cycle is applied to.

I think the issue here is that we're caching a fixed set of messages to pick from, theoretically for performance reasons, but given the actual speed, I think we might want to just have the default mode not use that cache by default (I think only if we're making ~1M messages do we want the cache).

Sure, would we be substituting the cached messages for just random strings? random strings with randomized flair?

Yeah, I was thinking we just use an iterator against zerver/lib/generate_test_data.py with random flair, rather than using the cache.  Might make sense to lave the current behavior available under an option; I can imagine it being useful for certain debugging tasks.


text:
Add a notice when we save drafts (when compose is closed)

If you have compose open with some text in it, and then click somewhere to the side, we automatically hide compose (saving the text as a draft).  However, for many users, it can appear that their message was lost, because they might not know about Zulip's drafts feature.  We should probably add some sort of lightweight notice (in the compose area) to let the user know that the message was saved as a draft.
It could also make sense to have that trigger a hotspot on "Drafts" if the user hasn't been here before.
See https://github.com/zulip/zulip-electron/issues/343#issuecomment-347357992 for some context on why this is super valuable.
@sampritipanda FYI; this could significantly increase the value of "Drafts".
@rishig I'd appreciate your thoughts on this.

I think this is a great idea (both the notice and the hotspot).
Maybe we should open the hotspot issue separately, since it is more complicated than the notice.

I think we can just open a follow-up issue for the hotspot once we've completed this and know whether we actually want it.  I agree anyone working on this should just do the notice, and we can decide on the rest once that's done.
In terms of visual design, I think something that shows as a brief animation on the "closed compose" area would be a good thing to try as a start; we might find we need to do something fancier if that doesn't look great (but I'd start with doing something simple for the animation and focus on the plumbing, since that will require most of the code reading).

My opinion: Draft must save for channel and last draft autopast in "new_message_textarea", if click on "new message"

@zulipbot claim

The current version mostly works, but the preview case seems broken (albeit in a mostly harmless way).

actually, I'm having trouble repro'ing this now so closing again

authors: AasthaGupta fleytman rishig showell timabbott


text:
social_backends: If no icon is to be displayed, set display_icon to None.

Small adjustment requested in https://github.com/zulip/zulip-mobile/issues/3670#issuecomment-549541290

I addressed my comment above and pushed back to this PR; will merge once CI passes and @mateuszmandera confirms he agrees that we'll still correctly default to None.

@timabbott Sounds good to me, because the dict is constructed:
        saml_dict = dict(
            name='saml:{}'.format(idp_name),
            display_name=idp_dict.get('display_name', SAMLAuthBackend.auth_backend_name),
            display_icon=idp_dict.get('display_icon', SAMLAuthBackend.display_icon),
            login_url=reverse('login-social-extra-arg', args=('saml', idp_name)),
            signup_url=reverse('signup-social-extra-arg', args=('saml', idp_name)),
        )  # type: SocialBackendDictT

and SAMLAuthBackend.display_icon is set to None.

authors: mateuszmandera timabbott


text:
user_status inside the select tag

previously when we want to change the status we don't get option when we want to change the user-status .
so I provided options when user want to change the status with active and inactive options. here is the image

part of :#15689

Could you squash your commits, please?

I have run this locally. And there are a few things that need to be fixed:

The select box needs styling.
When you click in a status option it's not really changing the user status, as you can see buddy list in the side.
After you click in the selection box and then in the status option, the user popover should be closed.
I'm not sure about the 4th point, but:
In my opinion, if the user is "Active" then the only option that should be shown in the dropdown is the "Inactive" option. But if that is not the case, then I guess it should have an empty option tag to give a space between the dropdown options and the selection box.

I am sorry about the commit message, I forgot to delete it correctly.while sqashing.

It is unusable for me. Clicking the select status box hides the whole popover. Also, the select box needs to be properly aligned. Add some right padding. Your commit message should be as described in https://zulip.readthedocs.io/en/latest/contributing/version-control.html#commit-messages

You should reference the issue in the PR description, not in the PR title.
You should amend your commit message like @amanagr described.
You should add a GIF showcasing the new UI to the PR description.

@Gittenburg should I have to make changes in it.

I don't understand what you mean. Another thing I just noticed is that we should display "Unavailable" instead of "Inactive".

If you mean this PR by "it", yes the commit message should say "part of" instead of fixes and we should name the select option "Unavailable" instead of "Inactive"

Is this the only change that I have to do.

I still find $(".status_info option:selected").val() very weird, $(".status_info").val() should do the same.

I still find $(".status_info option:selected").val() very weird, $(".status_info").val() should do the same.

It's all done .so should I stop working on this PR

@Gittenburg ,
Is this okay.

The icon next to the user name  should also update when you change your status.

The icon next to the user name  should also update when you change your status.

hey tried and, I add the code "" in between line like this {{this.description}}
But before when we change the status the popover just hide so it changes
Now in this PR when I add this code  , the popover does not closes show it does not show when we choose option . change is shown only then when popover is once closed and opened again .
so do you have any other idea what should I do to change when option is choose

You can add an id to the <span class="{{user_circle_class}} ...> and then change the CSS class with jQuery on status change.

@Gittenburg
It's done .

Looks good! The commit messages still need to be fixed according to https://zulip.readthedocs.io/en/latest/contributing/version-control.html#commit-messages (can be done with an interactive git rebase).

Squash both commits.
Change the first line of the commit message to user_popover: Use <select> for active/unavailable setting.
Fix the typos.

Hey you should not merge master, you should rebase your branch on top of master.

Hey you should not merge master, you should rebase your branch on top of master.

first I have rebased a commit , but then I am getting the error in production so I pull the changes from master so one, extra commit is made but then I squash both the commit and push the commit back

@timabbott , can you check if this okay .

As I mentioned in PMs, the commit doesn't follow our commit guidelines.  I think you just updated the PR description rather than the commit message?

@timabbott , I have updated the commit message .

@timabbott can you review it.

@timabbott can you review.

authors: Gittenburg amanagr clarammdantas ritikchauhan-01 timabbott


text:
node_test: Add clear_search tests for clear_search_stream_button.

 Missing clear_search node tests for clear_search_stream_button.
Testing plan:
GIFs or screenshots:

@nikhilmaske-2001 it appears that the node tests fail with this commit; can you investigate?


text:
bug fix: Fix today's regression with topic counts.

The series of commits to consolidate CSS classes
for the various unread-count spans across our app
created a bug where the stream_list.js code's selector
starting capturing the unread spans in topic list items.
Suppose you had a stream with these topics:
Foo 10
    a 3
    b 3
    c 4

If another unread came in, you would briefly see:
Foo 11
    a 11
    b 11
    c 11

Now we just use subscription_block to find the
element that we want to tweak.
I remove a convoluted node test here. Part of the
reason the node test was convoluted was that the
original implementation was overly complex. I will
try to re-introduce a simpler test soon, but this
is a bit of an emergency fix.

Testing plan:
GIFs or screenshots:

This seems plausible; test-deploying on chat.zulip.org now to help verify the fix.

This fix appears to not cover all the real-time sync issues we had -- I just noticed the right sidebar showing a nonzero unread count for a user while the left sidebar had 0 (after narrowing to PMs with that user via p).  It cleared automatically with the next automatic right sidebar rerender.

Merged, thanks @showell!  I think it's better to fix forward from here since this looks like a correct tactical fix for the bug at hand.

authors: showell timabbott


text:
Simplify cross-realm validation in recipient_for_emails().

We now simply exclude all cross-realm bots from the set of emails
under consideration, and then if the remaining emails are all in
the same realm, we're good.

Automated message from Dropbox CLA bot
@showell, it looks like you've already signed the Dropbox CLA. Thanks!

This looks great; can you add some testing for the new logic (e.g. sending to welcome-bot and feedback-bot)?  Seems like the kind of thing we'll be glad we have tests for.

This looks great, merged, thanks @showell!

authors: showell smarx timabbott


text:
Missing f prefix on f-strings fix

Fixes #21905

@code-review-doctor is there a way to generate a one-commit-per-rule PR from a specific set of rules that we'd like to apply? I could easily do that if one can run your tool locally.

@timabbott we have internal tools that can do that yep :)
send me an email to hello@codereview.doctor with what you need and we will do it

Done.

Closing as this isn't useful as written and we've likely done this using ruff transformers already.

authors: code-review-doctor timabbott


text:
slack: Skip reactions for deleted users.

Fixes: #23552. Slack exports contain lists of user IDs who react to messages, including users who are not defined (deleted). Zulip requires all reactors to be defined (not deleted).

Screenshots and screen captures:
Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Looks great, merged, thanks @cognusion!

authors: cognusion timabbott


text:
Make banner about automatically following topics one-time only

Fixes: #27847

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Posted question and feedback on URLs / events in:

https://chat.zulip.org/#narrow/stream/3-backend/topic/Rename.20UserHotspot.20table/near/1692804

https://chat.zulip.org/#narrow/stream/378-api-design/topic/hotspots.20.2F.20onboarding.20steps/near/1692805

Network failure.

@alexmv can you please take a look at the migration tweaks

I repushed with an updated comment, but looks good otherwise!

Merged, thanks @prakhar1144 and @alexmv for all the work on this!

authors: alexmv prakhar1144 timabbott


text:
Modify tooltips to clarify draft saving.

Modified tooltips for both the Cancel button and the in-progress sending spinner to provide clearer guidance to users. Now, if the message fails to send successfully, the tooltip includes an additional line explicitly stating: If the message is not sent successfully, it will be saved as a draft.
Additionally, it's worth noting that in my development environment, I noticed that the loading spinner was not displayed, which may be related to the changes introduced in this commit. Despite this, I proceeded with adding tooltips for both the Cancel button and the spinner, as demonstrated in the attached screenshot.
Fixes #29100.
Screenshots and screen captures:
Cancel:

Spinner:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@alya  can you review this PR :)
Also i don't why check is not running

@alya changed the screenshot and updated the PR :)

@alya  waiting for your review

@alya  made changes can you review the PR

Sorry for the delay! @amanagr perhaps you could review this one? I haven't tested.

@sujalshah-bit thanks for working on this. Left a comment, other than that LGTM.

@amanagr made the changes.

Thanks!

Additionally, it's worth noting that in my development environment, I noticed that the loading spinner was not displayed, which may be related to the changes introduced in this commit. Despite this, I proceeded with adding tooltips for both the Cancel button and the spinner, as demonstrated in the attached screenshot.

Did you figure out why this is? I think it's important that we fix that if it's indeed a regression.
For the text, I think the text feels a bit non-specific about whether the content is already saved as a draft, or you need to do something to save it:

If the message is not sent successfully, it will be saved as a draft.

I believe the accurate story is that it is saved as a draft before we send it to the server. So maybe something like:

This message will remain safe in your drafts until it is successfully sent.

@alya thoughts?

Maybe a slight tweak on that?

This message will remain saved in your drafts until it is successfully sent.

Updated the PR:

Now, the text "This message will remain saved in your drafts until it is successfully sent." is displayed.

@timabbott,
The spinner is indeed showing, but only for a very short period of time. I think it should remain visible until the message is successfully sent. I suspect this is happening because of the following code:
{{#unless msg/show_slow_send_spinner }} hidden{{/unless}}

if the code is removed:
https://github.com/zulip/zulip/assets/73663475/2c9b7808-a1ca-4bef-ae37-728fe3f7503b
with code:
https://github.com/zulip/zulip/assets/73663475/f08cef57-b745-42c2-9cb5-0b3df1d8d28d

I think the intent of that code was to have the spinner only appear after it's been a bit of time without the message being confirmed; so I suspect the thing that's wrong is some setTimeout logic that's meant to trigger a single-message rerender to show the rerender isn't working?

This doesn't fix #29100; only one of the two bullets. Fixed the commit message to clarify that, and also line-wrap more normally.
I also made the following edited before merging, after spending a bit more time thinking about appropriate language:
diff --git a/web/templates/message_controls.hbs b/web/templates/message_controls.hbs
index 3bb39f5262..7b8c778864 100644
--- a/web/templates/message_controls.hbs
+++ b/web/templates/message_controls.hbs
@@ -22,8 +22,8 @@

-

-
+

+

diff --git a/web/templates/tooltip_templates.hbs b/web/templates/tooltip_templates.hbs
index af347815b7..7869c81c93 100644
--- a/web/templates/tooltip_templates.hbs
+++ b/web/templates/tooltip_templates.hbs
@@ -154,17 +154,17 @@
     {{t "Message actions" }}
     {{tooltip_hotkey_hints "I"}}
 </template>
-<template id="cancel-button-tooltip-template">
+<template id="dismiss-failed-send-button-tooltip-template">

-
{{t "Cancel" }}

+
{{t "Dismiss failed message" }}

-            {{t "This message will remain saved in your drafts until it is successfully sent." }}
+            {{t "This content remains saved in your drafts." }}

 </template>
 <template id="slow-send-spinner-tooltip-template">

-
{{t "Your message is taking longer than expected to be sent. Sending…" }}

+
{{t "Sending…" }}

             {{t "This message will remain saved in your drafts until it is successfully sent." }}

authors: alya amanagr sujalshah-bit timabbott


text:
kandra: Default to installing "production", not "main".

Fixes:

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Hmm, yeah, I guess a detail we missed in that naming migration.

authors: alexmv timabbott


text:
Setting Yantramanav as default site font.

This adds Yantramanav to /static/third/yantramanav/ along with making it as the primary site font.
This also changes the fonts to be anti-aliased.

Automated message from Dropbox CLA bot
@brockwhittaker, it looks like you've already signed the Dropbox CLA. Thanks!

I think we've decided not to go with this font, so closing this.  I guess you should still open a PR for anti-aliasing, though!

authors: brockwhittaker smarx timabbott