text:
Update silencer-lib, silencer-lib_2.13.10, ... to 1.7.13

About this PR
📦 Updates

com.github.ghik:silencer-lib
com.github.ghik:silencer-lib_2.13.10
com.github.ghik:silencer-plugin

from 1.7.12 to 1.7.13
📜 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 = "com.github.ghik" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.ghik" }
}]

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

Superseded by #239.

repo: zio/zio-profiling


text:
memory look some nervous

I browse some article and memory increase so fast

hi @HotWordland ,it looks like the article view controller is not dealloc while back to the list view controller, I will take part in it tonight

Hello @zixun,
恕我使用中文...

看了一下, root cause 應該是 CCPArticleViewController 裡面的 CCCocoaChinaWebView 一直沒有被釋放. 可能再要看一下 CCCocoaChinaWebView 為什麼在這個地方不會被釋放. 如果單純的把他放在 AppDelegate 建立的話
CCCocoaChinaWebView(frame: UIScreen.mainScreen().bounds)

倒是可以正常的調用到 deinit

@DaidoujiChen 谢谢。我找到原因了，是因为CCPArticleViewController 里的ZXCuteView循环引用导致的，已经更新ZXKit,[https://github.com/zixun/ZXKit/commit/1eec9fc3bac567dcb1466a264704f7b5dc6b3088]https://github.com/zixun/ZXKit/commit/1eec9fc3bac567dcb1466a264704f7b5dc6b3088

@HotWordland thx for you issues,it is fixed.and you can run 'pod update ' or 'pod install',it will download the newest ZXKit code

:+1:

source: gharchive/issue

authors: DaidoujiChen HotWordland zixun

repo: zixun/CocoaChinaPlus

license: mit

license_type: permissive

license_source: bigquery


text:
能不能将默认的选中样式改为圆形或者方形，椭圆有点丑

最好能支持mark自定义样式

使用customStyleGenerator可以实现。
<Calendar
        customStyleGenerator={params=>{
          if(params.selected){
            return {
                dateStyle:{
                borderRadius:"2px"
              }
            }
          }
          return {}
        }}
/>

试了下，是可以的，但是无法自定义marker组件， 我看了下代码，marker是通过一个View显示的，请问我想在marker的位置显示文本或者其他内容该怎么处理?

试了下，是可以的，但是无法自定义marker组件， 我看了下代码，marker是通过一个View显示的，请问我想在marker的位置显示文本或者其他内容该怎么处理?

如果要显示文本信息可以用extraInfo配置项。
目前不支持在marker的位置显示文本。

@zkytech
行吧，那我自己fork改下，感觉像日历这种，marker部分有文字的场景还是很多的，方便的话还是加下吧

@zkytech   有没考虑更新下默认样式，customStyleGenerator可以控制的东西太少了，而且很不好控制
我看了几个日历的app，大部分可以归为两种样式
1.圆角矩形(只用边框选中或者背景色选中)，下面是背景色选中

一般这种情况下，农历或者节日信息在选中范围的里面，mark那个点在选中范围的下面
2.圆形选中

这种农历或者节日信息 和 mark那个点 均在选中范围内
但是目前这个库，椭圆的样式，并且mark都在选中范围下面，有点不符合通用的日历样式，并且mark无法自定义
我改了一版，样式这块不是太熟，能不能一起弄一下，改成功能比较通用的日历组件

@zkytech 有没考虑更新下默认样式，customStyleGenerator可以控制的东西太少了，而且很不好控制
我看了几个日历的app，大部分可以归为两种样式
1.圆角矩形(只用边框选中或者背景色选中)，下面是背景色选中

一般这种情况下，农历或者节日信息在选中范围的里面，mark那个点在选中范围的下面
2.圆形选中

这种农历或者节日信息 和 mark那个点 均在选中范围内
但是目前这个库，椭圆的样式，并且mark都在选中范围下面，有点不符合通用的日历样式，并且mark无法自定义
我改了一版，样式这块不是太熟，能不能一起弄一下，改成功能比较通用的日历组件

可以的，但是我周末才有空。

定制效果图

repo: zkytech/taro-calendar-customizable

license: MIT

license_source: github-api


text:
testing with zips

where do I place it? I tried python test_vision_detector_search.py
and I put corr in /home/chuong/cos-pomdp/experiments/thor/
but it keeps telling me this error:
FileNotFoundError: [Errno 2] No such file or directory: '/home/john/cos-pomdp/experiments/thor/../../data/thor/corrs/distances_bedroom_AlarmClock-DeskLamp_FloorPlan321.json'

should I make 2 folders? that seems weird.

Sorry, I’ve forgotten :)
Look into how it’s used.

authors: khuechuong zkytony

repo: zkytony/cos-pomdp


text:
[Bug] Satelite bay crashes/freezes game after rocket assembly

Version of Advanced Rocketry
V1.12.2-1.5.0-126.jar
Have you verified this is an issue in the latest unstable build
N
Version of LibVulpes
1.12.2-0.4.0-49.jar
Version of Minecraft
1.12 Forge-14.23.5.2795
Crash report or log (if applicable)
No Crashreport bcause game freezes until crashes, but log from the Freeze
https://pastebin.com/raw/9sETesEh
Description of the problem
When assembling a rocket with a satelite bay, after building it and wanted to put in the satelite, you get disconnected and your game freeze
Log also mentions MEK(anism) so posting this on their github aswell
https://github.com/aidancbrady/Mekanism/issues/5271
placing in the satelite BEFORE pressing build on the rocket builder is fine

Bit of background.  When accessing chests and items in the rocket, AR temporarily switches users to a dimensionless "temp world" so that the coordinates of the tiles accessed match up with the coordinates of the tiles on the rocket.  It appears that Mekanism is sending/recieving some data while the user has been moved to the temp world.  The Temp world is not a ServerWorld nor is isRemote true.  Because the world must be able to be loaded from NBT, sometimes without access to a world object, I've not found a viable way to properly set isRemote.  I've considered using proxies, but that seems to break down in single player.
Mekanism is expecting a WorldServer on packet recieve if isRemote is false and the player in handlepacket is not null.

AdvancedRocketry-1.12.2-1.5.0-universal.jar.zip
Would you be able to try this build and see if the issue continues?

I have seen that the packdevs have pushed 1.5.0-127 to the dev-instance... Once the server gets updated I'll report back if the bug still occurs

Still crashes after using 1.5.0-127

Crash in 1.5.0-131 too

@TheonlyTazz could you provide a save file, minimal mod list and  list of instructions to trigger this bug? I'm happy to investigate why Mek requires a WorldServer instance on my fork (https://github.com/dizzyd/Mekanism) if I have enough data to reproduce reliably. :)

authors: TheonlyTazz Tntdruid dizzyd zmaster587


text:
Figure out how to ingest log files from multiple S3 buckets (CloudFormation install method)

I want to install ESF to ingest files from two S3 buckets using the sqs-s3 input.
I will use the the CloudFormation install method.

Requirements
Deploy ESF
Add an additional S3 bucket

Requirements
We need to create the following resources:

Two S3 buckets (with the data to ingest)
One SQS queue (for receiving the S3 object creation notifications)
One S3 bucket (to store the config.yaml file)

Overview

(1) S3 buckets for the data
You probably already have an S3 bucket with actual data. For this research, I will create two buckets for testing with sample data.
$ aws s3api create-bucket \
    --bucket esf-logs-bucket-001 \
    --region eu-west-1 \
    --create-bucket-configuration LocationConstraint=eu-west-1
{
    "Location": "http://esf-logs-bucket-001.s3.amazonaws.com/"
}

$ aws s3api create-bucket \
    --bucket esf-logs-bucket-002 \
    --region eu-west-1 \
    --create-bucket-configuration LocationConstraint=eu-west-1
{
    "Location": "http://esf-logs-bucket-002.s3.amazonaws.com/"
}

(2) SQS queue
We need an SQS queue where we will send the S3 object creation notifications for the esf-logs-bucket-001 bucket.
Create a new SQS queue named esf-logs-notifications-queue and set the visibility timeout to 910 seconds.
$ cat create-queue.json
{
  "VisibilityTimeout": "910"
}

$ aws sqs create-queue --queue-name esf-logs-notifications-queue --attributes file://create-queue.json
{
    "QueueUrl": "https://sqs.eu-west-1.amazonaws.com/418425532336/esf-logs-notifications-queue"
}

Enable S3 object creation from esf-logs-bucket-001 and esf-logs-bucket-002 to esf-logs-notifications-queue:
$ cat policy.json
{
  "Version": "2008-10-17",
  "Id": "__default_policy_ID",
  "Statement": [
    {
      "Sid": "__owner_statement",
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::418425532336:root"
      },
      "Action": "SQS:*",
      "Resource": "arn:aws:sqs:eu-west-1:123:esf-logs-notifications-queue"
    },
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "s3.amazonaws.com"
      },
      "Action": "SQS:SendMessage",
      "Resource": "arn:aws:sqs:eu-west-1:123:esf-logs-notifications-queue"
    }
  ]
}

# Set the SQS access policy
- Visit Amazon SQS > Queues > esf-logs-notifications-queue > Access policy > Access policy (Permissions)
- Edit, paste the content of `policy.json`, and save.

# Enable notifications
$ cat notifications.json
{
    "QueueConfigurations": [
        {
            "Id": "Creations",
            "QueueArn": "arn:aws:sqs:eu-west-1:123:zmoog-esf-howto-notifications",
            "Events": [
                "s3:ObjectCreated:*"
            ],
            "Filter": {
                "Key": {
                    "FilterRules": [
                        {
                            "Name": "Prefix",
                            "Value": ""
                        },
                        {
                            "Name": "Suffix",
                            "Value": ""
                        }
                    ]
                }
            }
        }
    ]
}

aws s3api put-bucket-notification-configuration \
    --bucket esf-logs-bucket-001 \
    --notification-configuration file://notification.json

aws s3api put-bucket-notification-configuration \
    --bucket esf-logs-bucket-002 \
    --notification-configuration file://notification.json

Create a sample.log file and upload to the zmoog-esf-howto-data bucket:
$ cat sample.log
Sample log line 1
Sample log line 2

$ aws s3 cp sample.log s3://zmoog-esf-howto-data/
upload: ./sample.log to s3://zmoog-esf-howto-data/sample.log

(3) S3 bucket for config.yml
$ aws s3api create-bucket \
    --bucket esf-logs-bucket-configs \
    --region eu-west-1 \
    --create-bucket-configuration LocationConstraint=eu-west-1
{
    "Location": "http://esf-logs-bucket-configs.s3.amazonaws.com/"
}

And upload a basic configuration file like this:
# config.yml
inputs:
  - type: "s3-sqs"
    id: "arn:aws:sqs:eu-west-1:123:esf-logs-notifications-queue"
    outputs:
      - type: "elasticsearch"
        args:
          # either elasticsearch_url or cloud_id, elasticsearch_url takes precedence
          elasticsearch_url: "<REDACTED>"
          # either api_key or username/password, api_key takes precedence
          api_key: “<REDACTED>"
          es_datastream_name: "logs-generic-default"
          batch_max_actions: 500
          batch_max_bytes: 10485760
          ssl_assert_fingerprint: ""

aws s3 cp config.yml s3://esf-logs-bucket-configs/config.yml

Deploy ESF
Using https://www.elastic.co/guide/en/esf/master/aws-deploy-elastic-serverless-forwarder.html#aws-serverless-forwarder-deploy-cloudformation
List ESF versions available for deployments:
aws serverlessrepo list-application-versions \
  --application-id arn:aws:serverlessrepo:eu-central-1:267093732750:applications/elastic-serverless-forwarder

cat sar-application.yaml

# sar-application.yaml
Transform: AWS::Serverless-2016-10-31
Resources:
  SarCloudformationDeployment:
    Type: AWS::Serverless::Application
    Properties:
      Location:
        ApplicationId: 'arn:aws:serverlessrepo:eu-central-1:267093732750:applications/elastic-serverless-forwarder'
        SemanticVersion: '1.9.0'  ## SET TO CORRECT SEMANTIC VERSION (MUST BE GREATER THAN 1.6.0)
      Parameters:
        ElasticServerlessForwarderS3ConfigFile: "s3://esf-logs-bucket-configs/config.yml"
        ElasticServerlessForwarderSSMSecrets: ""
        ElasticServerlessForwarderKMSKeys: ""
        ElasticServerlessForwarderSQSEvents: ""
        ElasticServerlessForwarderS3SQSEvents: "arn:aws:sqs:eu-west-1:123:esf-logs-notifications-queue"
        ElasticServerlessForwarderKinesisEvents: ""
        ElasticServerlessForwarderCloudWatchLogsEvents: ""
        ElasticServerlessForwarderS3Buckets: "arn:aws:s3:::esf-logs-bucket-001,esf-logs-bucket-002"
        ElasticServerlessForwarderSecurityGroups: ""
        ElasticServerlessForwarderSubnets: ""

Deploy ESF using the given configuration at sar-application.yaml:
$ aws cloudformation deploy \
    --template-file sar-application.yaml \
    --stack-name esf-logs \
    --capabilities CAPABILITY_IAM CAPABILITY_AUTO_EXPAND

Waiting for changeset to be created..
Waiting for stack create/update to complete
Successfully created/updated stack - esf-logs

Add a new S3 bucket
S3 buckets for the data
Create another S3 bucket with logs:
$ aws s3api create-bucket \
    --bucket esf-logs-bucket-003 \
    --region eu-west-1 \
    --create-bucket-configuration LocationConstraint=eu-west-1
{
    "Location": "http://esf-logs-bucket-003.s3.amazonaws.com/"
}

Enable notifications from esf-logs-bucket-003 to esf-logs-notifications-queue:
# Enable notifications
$ cat notifications.json
# same as before

aws s3api put-bucket-notification-configuration \
    --bucket esf-logs-bucket-003 \
    --notification-configuration file://notification.json

Update ESF config and parameters
We need to update ElasticServerlessForwarderS3Buckets adding the new S3 bucket ARN arn:aws:s3::esf-logs-bucket-003:
# sar-application.yaml
Transform: AWS::Serverless-2016-10-31
Resources:
  SarCloudformationDeployment:
    Type: AWS::Serverless::Application
    Properties:
      Location:
        ApplicationId: 'arn:aws:serverlessrepo:eu-central-1:267093732750:applications/elastic-serverless-forwarder'
        SemanticVersion: '1.9.0'  ## SET TO CORRECT SEMANTIC VERSION (MUST BE GREATER THAN 1.6.0)
      Parameters:
        ElasticServerlessForwarderS3ConfigFile: "s3://esf-logs-bucket-configs/config.yml"
        ElasticServerlessForwarderSSMSecrets: ""
        ElasticServerlessForwarderKMSKeys: ""
        ElasticServerlessForwarderSQSEvents: ""
        ElasticServerlessForwarderS3SQSEvents: "arn:aws:sqs:eu-west-1:123:esf-logs-notifications-queue"
        ElasticServerlessForwarderKinesisEvents: ""
        ElasticServerlessForwarderCloudWatchLogsEvents: ""
        ElasticServerlessForwarderS3Buckets: "arn:aws:s3:::esf-logs-bucket-001,arn:aws:s3::esf-logs-bucket-002,arn:aws:s3::esf-logs-bucket-003"
        ElasticServerlessForwarderSecurityGroups: ""
        ElasticServerlessForwarderSubnets: ""

Re-deploy ESF

Works as expected.
I can continue this scenario, if needed. Please let me know.

repo: zmoog/public-notes


text:
in new Sound(X, Y, callback) on android, callback might never be called.

The callback that is supposed to signify success or error of sound object creation is not called for me when loading a certain kind of mp3. Has anyone experienced something similar? What might be the cause here? The mp3 that causes these problems plays fine on iOS. It does contain some garbage bytes though. Is there any way to get more error reporting from the android sound player?

Same issue. The callback isn't called. Tried with multiple files that work fine on iOS.

Same issue here!

Same issue. The callback will  never be called, whether it is successful or not.

May i find the reason that the file path is wrong. As the doc saying, we need to put the wav into 'android/app/src/main/res/raw', and access it just like this :
const sound = new Sound('ding.wav', Sound.MAIN_BUNDLE, (error) => {
                                    if (error) {
                                        return;
                                    }
                                    sound.play(() =>
                                        sound.release()
                                    );
                                });

But this PR seems to have not been merged yet. Do you know the way to access sources in other directories? @ionTea

@YouCii For me it was a matter of making the URI correct, for example /data/user/0/<app package name>/files/<audio file>

@ionTea Could you document this somewhere in the wiki and/or README? I have had trouble playing local files using this package, and it really could use any documentation it can get. Thank you for your help!

There's a PR open #511 which addresses this.

authors: YouCii davidsalib ionTea paulmelnikow schumannd zhaccc

repo: zmxv/react-native-sound


text:
Some messages not buffered if client disconnects without /quit and then times out

If I disconnect from znc due to an issue with my internet connection, some buffer may be lost, leading to confused conversations as someone assumes you saw their reply.
It would be nice to have an option to make znc keep a buffer of what was said between now and the last successful ping, and add that to the buffer if the client disconnects due to missing a ping, or E_CONN_RESET/other similar error.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/244531-some-messages-not-buffered-if-client-disconnects-without-quit-and-then-times-out?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

Has any headway been made in relation to this issue?

This is the solution that I've been happily using for a year: http://wiki.znc.in/Playback. Yes, it needs special support from your client, but that's not difficult to implement.

Yes, it needs special support from your client, but that's not difficult to implement.

Is this currently supported by anything else than Communi-*?

Is this currently supported by anything else than Communi-*?

Textual & Mobile Colloquy

The OP's proposed solution would be a very welcomed feature.

Assuming I'm not missing any important technical detail that would lead to issues, I agree with @caktux, as this solution would (hopefully) work with all standard clients and not require special plugins.

Could this be closed based on *playbck or will this wait for it to be merged to ZNC?

I'm not entirely sure if a solution to this issue should require non-standard client implementations and/or (third-party) plugins.

Isn't this what the clearbufferonmsg module is for?

It never checks whether the actual `write(...)' call succeeded :(
I'll see if I can come up w/ sthing!

o/ o/
So, I think the issue is fixed by the commit I made in my fork (Idk if it shows here for others.)
However, only when using the clientbuffer module.  I could carry on looking for fixing w/o, but that wouldn't be solving a problem I have.
I'll send a PR for now with that, at least it is something.

Isn't this what the clearbufferonmsg module is for?

So I guess yes, it is, after educating myself.
(At first I thought write() or SSL_write() returning <= 0 meant that the message did not make it, and therefore the other way around meant that it did however as it turns out SSL_write() may still return a # of byte transmitted even though the connection is down, and for good.)
I think we could improve ZNC to only clear the buffer upon receiving  a pong, and we could emit a ping along with each messages.  But, yeah, this is virtually the same as using clearbufferonmsg (ty @AndrioCelos )
Since I am using the clientbuffer module I will take my suggestion there.

I observe this problem in my own setup, and am concerned that it happens. It suggests that there is a code path through which a message can show up and, failing delivery to the user, be dropped on the floor. TCP socket calls will provide sufficient information to detect delivery error, so it concerns me that this is a problem at all.

I was exactly same but as it turns out TCP being reliable merely means that when the connection cuts, you will now eventually about it, however not exactly at the moment it happens.
So the proper fix sounds like being folding the module clearbufferonmessage in ZNC.
Considering the wiki for it says that it addresses this very issue, a point can be made this is simply how the software is designed.
As per my previous comment an issue remains with znc-clientbuffer.  I'll open it up there

authors: AndrioCelos Mikaela PotcFdk caktux glechapelain jpnurmi nallar winny-

repo: znc/znc


text:
[Feature Request] Support sourcemaps

Everything's on the title

fixed by #24

authors: posva znck

repo: znck/rollup-plugin-vue


text:
Subnet references bug as count has changed resources from a single string to a list

Error: Incorrect attribute value type

on vpc_transit_gateway_attachment.tf line 8, in resource "aws_ec2_transit_gateway_vpc_attachment" "network_transit_gateway":
   8:   subnet_ids         = [aws_subnet.sn_private_a.*.id, aws_subnet.sn_private_b.*.id, aws_subnet.sn_private_c.*.id]

Inappropriate value for attribute "subnet_ids": element 0: string required.

Issue arrises for transit gateway and the ACLs

repo: zoitech/terraform-aws-network


text:
Make RPC docs more discoverable

From @zombiezen on August 24, 2015 23:15
Based on this thread, the overall docs for the RPC package are not easy to find.  It may be worth making a GitHub page that breaks out the "hello world" examples.
Copied from original issue: zombiezen/go-capnproto#8

Decided to do this as a wiki page.  See Getting Started and Comparison with stdlib rpc.

Also worth writing up the difference between net/rpc and this.


text:
Typo at: https://js.zonayed.me/basic/post-16

ধন্যবাদ ভাই ধরিয়ে দেবার জন্য... ফিক্স করে দিবো

My pleasure vai.

authors: TareqMonwer zonayedpca


text:
Azure Pipelines integration

Run tests on PRs and CI, and publish to PyPI when tagged.
This probably has to be done by me on my account.

Completed in #17

repo: zooba/reportabug


text:
rss.xml or sitemap 설정 관련.

안녕하세요 줌코딩님 많은 도움으로 인해 성공적으로 블로그 리빌딩 중입니다!!
다름이 아니라 줌코딩님 Gastby 테마는 advanced-sitemap 플러그인을 사용 중이신 것 같은데 RSS는 따로 등록하지 않으신 상태이신가요

@nasa1515님 안녕하세요!
RSS 설정은 따로 추가해두지 않았어서 추가 구현해서 푸쉬해두었습니다!
내용이 궁금하시다면 aa5b201 을 참고하시면 될 것 같습니다!

repo: zoomKoding/zoomkoding-gatsby-blog


text:
Projects need a FieldGuide resource

Very very similar to the Tutorial resource.
It'll contain an list of items (probably a JSON blob?), each with a title string, a content string, and an icon image source string that'll refer to a Media resource, so it needs attached_images too.

i'll get working on this tomorrow.

Do the items need to be ordered? Or would it make sense to have the project have many tutorial resources that have an order property?

Yes, some ability to define the order is required.

authors: brian-c camallen

repo: zooniverse/Panoptes


text:
🛑 AI For Students is down

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

HTTP code: 0
Response time: 0 ms

Resolved: AI For Students is back up in 4565381.

repo: zootsewt/aistatus


text:
fix(navbar): fix typo

fix #691, fix #679
Fix a typo in order to trigger a release.

No need to create a release for this fix

source: gharchive/pull-request

authors: JuliaHempel poteirard

repo: zopaUK/react-components


text:
Add f-string backport to support python 3.5 again (fixes #168)

Fixes #168

Thanks. I'll take this and rewrite it without the f-strings. I'd rather not add an extra external dependency now.

Merging into py35 branch for some edits. Thanks!

authors: ckleemann dyve


text:
Add troubleshooting ssl tls setup to apiml troubleshooting

This PR is to add a troubleshooting section for SSL/TLS setup and links to the corresponding blog post.

As the first step to get the article to the documentation, this is good.

repo: zowe/docs-site


text:
Docs site link placement

Docs site link placement requires an UX engineer review.
It is an external link and should not be placed between internal navigation links, so it should be moved to some other place, like somewhere in header or at least to be last in the row.

@samanthasusu @Phoebecdy91 Would you be able to take a look and figure out a right way to approach this question?

authors: balhar-jakub skurnevich


text:
希望能对应更新一下1.X版本

看了一下1.3版本。没有支持对error的错误。2.0以上版本有对应的支持，但是只能支持React 0.47以上的版本。希望能更新出一版1.4版本，感激不尽

已更新 v0.1.4: https://github.com/zphhhhh/react-native-speech-iflytek/tree/v0.1

repo: zphhhhh/react-native-speech-iflytek


text:
Support Chromium based Microsoft Edge

I took the liberty of creating this issue so we can track and centralize discussion around supporting the upcoming Chromium engine based Microsoft Edge.
Microsoft's official  announcement (archive.org copy) (PDF copy) (Gist markdown copy)
What

Today we’re announcing that we intend to adopt the Chromium open source project in the development of Microsoft Edge on the desktop to create better web compatibility for our customers and less fragmentation of the web for all web developers.

When

Over the next year or so, we’ll be making a technology change that happens “under the hood” for Microsoft Edge, gradually over time, and developed in the open so those of you who are interested can follow along.

My take
This is potentially great news for Lorca on Windows if future Edge provides the features that Lorca needs. Current version of Edge on Windows 10 spawns a private Edge session for me when running:
start shell:AppsFolder\Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge -private https://github.com

But my understanding is that Lorca also relies on Chrome DevTools Protocol. I hope to see that available in the new Edge.

Me too. Would make developers loves much easier

Update
Microsoft made available a preview build of Microsoft Edge based on Chromium.
Announcement: https://twitter.com/MSEdgeDev/status/1115283353731600384
Download available at: https://www.microsoftedgeinsider.com

Might also be possible to support Firefox: https://github.com/GoogleChrome/puppeteer/tree/master/experimental/puppeteer-firefox

I was able to get it working by just installing the edge dev channel and modifying the LocateChrome function
func LocateChrome() string {
	var paths []string
	switch runtime.GOOS {
        [...]
	case "windows":
		paths = []string{
			"C:/Program Files (x86)/Microsoft/Edge Dev/Application/msedge.exe",
			"C:/Users/" + os.Getenv("USERNAME") + "/AppData/Local/Google/Chrome/Application/chrome.exe",
			"C:/Program Files (x86)/Google/Chrome/Application/chrome.exe",
			"C:/Program Files/Google/Chrome/Application/chrome.exe",
		}

not passing tests, but is working when I open a locally served html5 application, so gives good indication that it shouldn't take much rework. When I have time I'll look into the tests and do a PR

PR submitted: https://github.com/zserge/lorca/pull/137, using the release path for MSEdge

PR submitted: https://github.com/zserge/lorca/pull/137, using the release path for MSEdge

Thank you very much @chenilim! Since your PR was merged I think it's sensible to close this issue.

repo: zserge/lorca


text:
Autosuggest only the commands available to the terminal

Is there any way to autosuggest only the commands available to the terminal (e.g. echo, cp, rm, etc.)? Most of the time I don't need my entire history, but when I do, the arrow keys suffice for me.
Consider: https://fishshell.com/docs/current/tutorial.html#tut_autosuggestions
Ideally you'd be able to use any combination of these features (the one I'm interested in is commands without the entire history).
As a workaround, would it be possible to tell zsh-autosuggestions to use a blank or nonexistent history file? Ignore everything after the first space in autosuggestions? A history file that lists all the commands to autosuggest and nothing more?
Thanks

You can write your own suggestion strategy. You just have to define a function with the right name and then change the strategy variable in your config. Check out https://github.com/zsh-users/zsh-autosuggestions/tree/master/src/strategies for some inspiration.

Sorry it took so long for me to reply. I changed default.zsh a bit and got it to show only the command (i.e. everything before the first space), but now it shows the same command every time I press space. What am I doing wrong?
_zsh_autosuggest_strategy_command() {
    local prefix="$1"

    typeset -g suggestion="${"${history[(r)${(b)prefix}*]}"% *}"
}

source /usr/share/zsh/plugins/zsh-autosuggestions/zsh-autosuggestions.zsh

export ZSH_AUTOSUGGEST_STRATEGY="command"

authors: GloverDonovan ericfreese

repo: zsh-users/zsh-autosuggestions


text:
Define symbols to be ignored on completion

It would be useful to provide a feature when I am not at the end of the line and to the right of cursor there are some symbols that can be ignored when suggesting a command.
For example, when I type git cm i have following suggestion

But when I press " autopair plugin inserts a send ", so the completion is gone...

Then I start to type feat(nvim):  and it would be useful to define ZSH_AUTOSUGGEST_IGNORE_SYMBOLS as following:
ZSH_AUTOSUGGEST_IGNORE_SYMBOLS="'\"})"

to make it possible to show completions even if any count of any of these symbols are now on the right of cursor.
Same issue can be with $(...):

Is it possible to implement?

It seems possible but I'm curious about how things would function when in that state of having both an ignored suffix of the command and a suggestion to show. Can you elaborate on how the suggestion would be shown in your second and fourth screenshots? And what you think should happen if you were to press enter from those states without accepting the suggestion?

Hmm, that's an interesting question :)
To be honest, I can't come up with a solution. Sorry, I didn't think of that when was opening this issue.

authors: ericfreese mitinarseny


text:
Compatibility with zsh-syntax-highlighting

I accidentally closed #260 by rebasing on the top of develop, so I'm reopening it here.
I'll be trying to fix it properly soon.

I really don't want to have code here referencing another plugin. That's a slippery slope that will lead to this plugin getting bloated with all kinds of crazy stuff to support other plugins. Lets find another way to fix this if possible.
Also, it seems like this bug could be described better as "When using vi-mode and zsh-syntax-highlighting, command is not highlighted after accepting suggestion", since the plugin is already largely compatible with z-sy-h. #6 is a very old issue, and is, in fact, already closed.

I don't want to have code referencing another plugin as well, that's why I'm trying to setup something cleaner. I definitely don't consider this hack to be mergeable as-is, I'm adding a WIP tag in the title right now, to make it clear.
I think we should be able to remove these references by replacing the manual cursor movement by a call to a widget such as end-of-line. The idea is that plugins such as zsh-syntax-highlighting wrap every existing zle widget, so by using such a call, we should be able to have the syntax highlighting updated (or any other crazy thing done by another plugin) just the way it would be if the user had typed it himself.
I'm working on it, but right now I have a recursive function call causing a stack overflow.
Anyway, I'll either push something working when I starts working, or ask for help if I can't figure it out.

Here is a cleaner version, we're getting closer to something acceptable.
I still need to figure out how the _zsh_autosuggest_bind_widget function works, especially the $bind_count variable. It's gonna be required to prevent hardcoding the autosuggest-orig-1-end-of-line widget.
We also still need to care about the _zsh_autosuggest_execute function.
I tried to check whether the tests pass or not, but I can't get them to pass even on master, so… well, if someone can give it a try, I'd be really grateful !

Oh, by the way, I couldn't install ruby 2.3.1 because of this issue, that's why I bumped the ruby version. Since the tests don't work at all for me, I can revert this change if it is the source of the problem.

@toadjaune Is this still an issue? I'm not able to reproduce with following versions:

zsh @ 5.4.2
z-asug @ b2b9bf3
z-syn-hi @ 5b53966

Yes it is, I was working on it when I ran into https://github.com/zsh-users/zsh-autosuggestions/pull/324. I'll try and have a look in the weeks to come.

I just tested, and the bug is still present for me, with the following versions :

zsh: 5.4.2
zsh-autosuggestions: current develop (ie 5549b68, newer than b2b9bf3)
zsh-syntax-highlighting: current master (ie ee26d44, newer than 5b53966)

I'd be glad to write a test showing the erroneous behaviour, but I'm not sure how to do this without loading zsh-syntax-highlighting, which would basically be an integration test (with all the version synchronization issues that arise from these).
Do you want more detailed reproduction instructions ?
In the meantime, I've merged develop into my branch, and tested again.
My fix still works fine, and does not break any test. (I do however have 3 tests that were not passing in the first place on current develop)

I've finally reproduced this! I have ^E bound to end-of-line in vi mode, and that's what I usually use to accept the suggestion. However, when I use the right arrow key to trigger vi-forward-char to accept the suggestion, I do see this behavior. I'm not sure how they have different behavior, but at least now I can reproduce. Will look into this more soon.

When squashed down and cleaned up, this diff is nothing more than this:
I've been using this branch for months now and it's been working great. I'd suggest that this is squashed and merged, assuming it doesn't cause any problems.
Thanks for the fix!
diff --git a/src/widgets.zsh b/src/widgets.zsh
index 8710c02..8efc196 100644
--- a/src/widgets.zsh
+++ b/src/widgets.zsh
@@ -124,14 +124,11 @@ _zsh_autosuggest_accept() {

        # Only accept if the cursor is at the end of the buffer
        if [ $CURSOR -eq $max_cursor_pos ]; then
-               # Add the suggestion to the buffer
-               BUFFER="$BUFFER$POSTDISPLAY"
-
-               # Remove the suggestion
-               unset POSTDISPLAY
-
-               # Move the cursor to the end of the buffer
-               CURSOR=${#BUFFER}
+               # Accepting the whole line is basically a specific case of
+               # accepting partially with "end-of-line" widget
+               # NB : we can't directly call end-of-line because since we wrap it,
+               # it would cause a recursive call to it
+               _zsh_autosuggest_partial_accept "autosuggest-orig-1-end-of-line"
        fi

        _zsh_autosuggest_invoke_original_widget $@
diff --git a/zsh-autosuggestions.zsh b/zsh-autosuggestions.zsh
index 6cbaf05..787a72d 100644
--- a/zsh-autosuggestions.zsh
+++ b/zsh-autosuggestions.zsh
@@ -389,14 +389,11 @@ _zsh_autosuggest_accept() {

        # Only accept if the cursor is at the end of the buffer
        if [ $CURSOR -eq $max_cursor_pos ]; then
-               # Add the suggestion to the buffer
-               BUFFER="$BUFFER$POSTDISPLAY"
-
-               # Remove the suggestion
-               unset POSTDISPLAY
-
-               # Move the cursor to the end of the buffer
-               CURSOR=${#BUFFER}
+               # Accepting the whole line is basically a specific case of
+               # accepting partially with "end-of-line" widget
+               # NB : we can't directly call end-of-line because since we wrap it,
+               # it would cause a recursive call to it
+               _zsh_autosuggest_partial_accept "autosuggest-orig-1-end-of-line"
        fi

        _zsh_autosuggest_invoke_original_widget $@

It seems to be caused by updating the CURSOR before calling _zsh_autosuggest_invoke_original_widget. I'm starting to think this is also partially caused by zsh-synhl too, perhaps an optimisation or oversight in that?
Here is an alternative fix that also solves the issue:
diff --git a/zsh-autosuggestions.zsh b/zsh-autosuggestions.zsh
index 1c3eab5..d94fa42 100644
--- a/zsh-autosuggestions.zsh
+++ b/zsh-autosuggestions.zsh
@@ -412,11 +412,13 @@ _zsh_autosuggest_accept() {
                # Remove the suggestion
                unset POSTDISPLAY

+               _zsh_autosuggest_invoke_original_widget $@
+
                # Move the cursor to the end of the buffer
                CURSOR=${#BUFFER}
+       else
+               _zsh_autosuggest_invoke_original_widget $@
        fi
-
-       _zsh_autosuggest_invoke_original_widget $@
 }

 # Accept the entire suggestion and execute it

This should have been closed a long time ago since #488 fixed it :)

authors: ericfreese frebib toadjaune


text:
Refactor

Pulled ScheduleFields and Field to their own file.
Pulled OrdinalIter and OrdinalRangeIter to the ordinal.rs file.

in the end I decided that it might be better to change it's implementation to keep it clean. I discussed this already in #82.  Honestly I think that the old implementation mightve been one of the problems causing the slowdown for #80

Put trait implementations in their respective files.

Closing for now, feel free to reopen.

authors: koenichiwa zslayton

repo: zslayton/cron


text:
Delete VIP failed, due to used by load balancer

If VIP is used by Load Balancer, it can't be deleted so far.
2015-08-22 10:58:58,846 DEBUG [apibinding.api] async call[url: http://10.0.101.20:8080/zstack/api/, request: {"org.zstack.network.service.vip.APIDeleteVipMsg": {"session": {"uuid": "b1cfdddf40ed4d098b57c72d7be10341"}, "uuid": "74ece6e033984d2d8b11d079a87ce3e5", "sessionUuid": "b1cfdddf40ed4d098b57c72d7be10341"}}]
2015-08-22 10:58:59,353 DEBUG [apibinding.api] async call[url: http://10.0.101.20:8080/zstack/api/, response: {"org.zstack.header.message.APIEvent":{"success":false,"error":{"code":"SYS.1006","description":"An operation failed","details":"vip[uuid:74ece6e033984d2d8b11d079a87ce3e5] is still used by the service[LoadBalancer]"}}}]

not a bug, it's design

This should be aligned with cascade framework. So reopen it.

fixed in 72cbfbaf09b692e3830214e5b68e886ba3218015

authors: youyk zstackorg zxwing

repo: zstackorg/zstack


text:
Switch from netty-all to specifying Netty JARs?

I spent a bit of time tracking down a nasty coredumping issue which turned out to be caused because Aleph bundles netty-all, and the Google Cloud SDK depends on individual netty JARs.
As best as I can tell (https://github.com/netty/netty/issues/4671, CASSANDRA-10984), netty-all is a kind of uberjar of all Netty classes, designed for people that just want to download a JAR and get running with Netty. If you're using Maven it is instead recommended to depend on specific Netty dependencies.
Now that I've figured out the problem I can just exclude the netty-all JAR to get the behaviour I want, but I thought it might save other people some anguish if Aleph moved to depending on explicit Netty JARs.
What are your thoughts on this? It looks like eventually netty-all may just become a dependency container for all of the other Netty JARs, in which case there would be no issue, however that seems like it may be a way off.

I don't have a strong opinion on this.  Back when I was first targeting Netty 4, I tried to enumerate packages Aleph depended on, couldn't get it to work in a reasonable amount of time, and so just targeted the uberjar.  If someone were to make it work for me, I'd have no problem merging the PR, but I don't see this as an immediate issue that requires fixing.

I've made a PR for this, but I agree it's not an urgent issue. I've done some testing on an actual project and everything seems fine.

authors: danielcompton ztellman

repo: ztellman/aleph


text:
Added support for IP2Location DB3 LITE

Added support for IP2Location DB3 LITE.

Thanks for your contribution.


text:
Build is broken

# github.com/zubairhamed/canopus
../../zubairhamed/canopus/dtls.go:12:26: fatal error: internal/bio.h: No such file or directory
compilation terminated.

@jvermillard is using openssl as a submodule: https://github.com/jvermillard/nativedtls. This way cgo can find correct headers.
You have probably installed on your system openssl 1.1, but it is pretty new and you can not expect it on any system.
I propose you to add correct openssl revision as a submodule (I tried adding by hand openssl dir, but it does not build)

Hey Drasko,
Yes you're right. I've commited the submodule.
Thanks!
Z

authors: drasko zubairhamed

repo: zubairhamed/canopus


text:
Request avatars of the appropriate size

With #195 fixed with PR #287, we now have a user-profile screen! 🎉
I noticed that on many profiles on CZO, the avatar is more blurry than on the corresponding screen in zulip-mobile:

zulip-flutter
zulip-mobile

This is because we don't yet have special logic for requesting a larger image when we need one. This issue is for adding such logic.
In zulip-mobile, we made an AvatarURL class with a get method that gives you a URL for an image of the specified size in physical pixels (or at least the best possible approximation). AvatarURL has three subclasses that each implement get very differently.
On CZO in #api documentation, I've summarized zulip-mobile's logic for determining a URL for any given size in physical pixels. I'm hoping the API doc can start specifying that logic, and we can use the new documentation for zulip-flutter's implementation.
To convert a logical-pixel value to a physical-pixel value, we'll want to multiply by the device pixel ratio. As in zulip-mobile:
avatarUrl.get(PixelRatio.getPixelSizeForLayoutSize(size))

I think a solution will likely have lots of interactions with #254 and #255, so the best approach might be to consider these three issues together.
Related: #254
Related: #255

An observant user noticed the blurriness and reported it in chat today: https://chat.zulip.org/#narrow/stream/48-mobile/topic/flutter.3A.20blurry.20profile.20picture/near/1735359

@gnprice I'm currently working on this feature. Finished with most of the task using gravatar's. I would like to know which formatter you are using because as I save my code most of the file gets re-formatted causing several changes in the git history. It would be really helpful if you linked the contributing guidelines as well.

@saisumith770 Cool — assigned you the issue, and I'll look at your PR in the next few days.
We don't use an auto-formatter, so you'll want to just tell your editor not to do that. Let's discuss in #mobile-team on chat.zulip.org.
For contributing guidelines, this repo's README file has information on running tests and making changes. We also follow the same basic style of clean commit history as the Zulip project in general, which is described here:
https://zulip.readthedocs.io/en/latest/contributing/commit-discipline.html

authors: chrisbobbe gnprice saisumith770

repo: zulip/zulip-flutter


text:
The new UserProfile.presence_enabled setting

See https://github.com/zulip/zulip/pull/14838 for a small new feature: a privacy setting to disable updating your presence information.
I believe the mobile apps don't need to do anything with this, since the implementation just doesn't store whatever the client sends in the presence endpoint.  So this issue is mainly an FYI about new behavior.
(Because of our POST /presence architecture where one gets other users' presence info when you send yours, it sorta has to be implemented server-side rather than not sending a ping)

I believe the mobile apps don't need to do anything with this, since the implementation just doesn't store whatever the client sends in the presence endpoint. So this issue is mainly an FYI about new behavior.

Good to know, thanks!

authors: chrisbobbe timabbott

repo: zulip/zulip-mobile


text:
Erroneous link parsing in thread titles

A thread title on a Zulip instance I'm a member of contained the string "core-js@2.6.11". A link widget pointing to the URL https://core-js@2.6.0.11/ appeared in the title. After some investigation I determined that there are a number of other erroneous cases that are parsed as URLs:

input
actual parsed link
expected

core-js@2.6.11
https://core-js@2.6.0.11
none

test@1.0
https://test@1.0.0.0/
none

bob@example.com
https://bob@example.com/
none or mailto:bob@example.com

mailto:bob@example.com
https://bob@example.com/
mailto:bob@example.com

In all of these cases, these would send the part before the @ as a HTTP basic auth username; I would be very surprised if this is ever what the user intends to do.
I also noticed that bare IP addresses are not parsed as links without the @: 1.1.1.1 does not get linkified. Some domains get linkified: google.com does, but butt.holdings does not. URLs that explicitly specify https:// always appear to be linkified, at least.

Thanks for the report!  This definitely seems wrong.

authors: rolandcrosby timabbott

repo: zulip/zulip


text:
Fix test suites that do not use sanity_check and/or assert_provisioning_status_ok

I noticed that test-documentation doesn't check that the user's development environment is setup, even though it does need our Python virtualenv to work, os it misses out on the things we do to avoid weird "missing dependency" error messages:
$ ./tools/test-documentation
/bin/sh: 1: sphinx-build: not found
Makefile:19: recipe for target 'clean' failed
make: *** [clean] Error 127

We should fix this to use , which probably involves converting that script to Python like its cousin test-help-documentation already is.
(While working on this you'll probably notice https://github.com/zulip/zulip/issues/17928; the right fix is test-documentation --skip-external-links for now)
We should also look through https://zulip.readthedocs.io/en/latest/testing/testing.html and also test-all and check that there aren't any others with this issue.

@zulipbot claim

@zulipbot claim

@zulipbot claim

I'm new here. So for this issue, my first task is to change the bash script to a python script? And is there a specific stream I can ask for help? thanks

We updated this pull request and it is ready to be reviewed.

@zulipbot claim

@zulipbot claim

@zulipbot claim

@zulipbot claim

@zulipbot claim

@zulipbot claim

https://github.com/zulip/zulip/pull/25203 seems to be decent work towards this but unfinished.

@zulipbot claim

@timabbott, I looked previous PR it has function to check environment setup . Please specify what extra things to be fixed

@zulipbot claim

@zulipbot claim

@zulipbot abandon

@zulipbot claim

@zulipbot abandon

@zulipbot claim


text:
Evaluation Error: Error while evaluating a Function Call, 'new' The string '16067.30' cannot be converted to Integer

Error: Evaluation Error: Error while evaluating a Function Call, 'new' The string '16067.30' cannot be converted to Integer (file: /home/zulip/deployments/2021-12-01-15-31-34/puppet/zulip/manifests/base.pp, line: 79, column: 22) on node

@fiber-optics can you provide more surrounding output, as well as what OS you're using Zulip on, and what you're doing when you see this?  I haven't seen this error before, but it seems like the kind of thing that could happen when running an different major release of puppet from the version that comes with the OS that Zulip expects.

i update OS from debian 9 to 10 and try update zulip 2.1.8 to 3 via
/home/zulip/deployments/current/scripts/upgrade-zulip-from-git 3.0
and this error is all i got
2021-12-01 14:25:33,441 upgrade-zulip-stage-2: Applying puppet changes...
Error: Evaluation Error: Error while evaluating a Function Call, 'new' The string '16067.30' cannot be converted to Integer (file: /home/zulip/deployments/2021-12-01-16-24-02/puppet/zulip/manifests/base.pp, line: 79, column: 22) on node mail.glyanec.net
Traceback (most recent call last):
File "/home/zulip/deployments/2021-12-01-16-24-02/scripts/lib/upgrade-zulip-stage-2", line 260, in
subprocess.check_call(["./scripts/zulip-puppet-apply", "--force"])
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['./scripts/zulip-puppet-apply', '--force']' returned non-zero exit status 1.
Traceback (most recent call last):
File "/home/zulip/deployments/current/scripts/lib/upgrade-zulip-from-git", line 69, in
deploy_path, "--from-git"] + deploy_options)
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/home/zulip/deployments/2021-12-01-16-24-02/scripts/lib/upgrade-zulip-stage-2', '/home/zulip/deployments/2021-12-01-16-24-02', '--from-git']' returned non-zero exit status 1.

It sounds like you may not have followed Zulip's instructions for upgrading from Debian Stretch to Debian Buster.  Were you working from those steps?
Note that there's no reason to stop the upgrade at 3.0; we suggest upgrading to the latest, once you're on Debian 10.  However, there are a couple steps you need to follow after upgrading the OS, before running upgrade-zulip, which are detailed in the above link.

followed, upgraded, still same error

It looks like you skipped step 6:

i cant update becouse this error

`root@mail:/usr/src# /home/zulip/deployments/current/scripts/upgrade-zulip zulip-server-latest.tar.gz
2021-12-02 18:31:18,903 upgrade-zulip: Archiving the tarball under /home/zulip/archives
2021-12-02 18:31:23,623 upgrade-zulip: Unpacking the tarball
2021-12-02 18:31:25,054 upgrade-zulip-stage-2: Upgrading system packages...
Get:1 http://deb.debian.org/debian buster-backports InRelease [46.7 kB]
Get:2 http://security.debian.org buster/updates InRelease [65.4 kB]
Hit:3 https://packages.sury.org/php buster InRelease
Hit:4 http://download.ispsystem.com/repo/debian base-buster InRelease
Hit:5 http://download.ispsystem.com/repo/debian 5.233-buster InRelease
Hit:6 http://mirror.yandex.ru/debian buster InRelease
Get:7 http://mirror.yandex.ru/debian buster-updates InRelease [51.9 kB]
Hit:8 https://packages.groonga.org/debian buster InRelease
Fetched 164 kB in 2s (103 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following package was automatically installed and is no longer required:
libzip5
Use 'apt autoremove' to remove it.
The following packages have been kept back:
facter php-apcu php-apcu-bc php-gd php-mysql php-ssh2 php-xml
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.

apt-get -y install build-essential libffi-dev libfreetype6-dev zlib1g-dev libjpeg-dev libldap2-dev python3-dev python3-pip virtualenv libxml2-dev libxslt1-dev libpq-dev libssl-dev libmagic1 libyaml-dev libxmlsec1-dev pkg-config jq libsasl2-dev
Reading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version (12.6).
libsasl2-dev is already the newest version (2.1.27+dfsg-1+deb10u1).
libmagic1 is already the newest version (1:5.35-4+deb10u2).
libfreetype6-dev is already the newest version (2.9.1-3+deb10u2).
jq is already the newest version (1.5+dfsg-2+b1).
libffi-dev is already the newest version (3.2.1-9).
libjpeg-dev is already the newest version (1:1.5.2-2+deb10u1).
libxslt1-dev is already the newest version (1.1.32-2.2~deb10u1).
libyaml-dev is already the newest version (0.2.1-1).
libldap2-dev is already the newest version (2.4.47+dfsg-3+deb10u6).
libssl-dev is already the newest version (1.1.1d-0+deb10u7).
pkg-config is already the newest version (0.29-6).
python3-pip is already the newest version (18.1-5).
virtualenv is already the newest version (15.1.0+ds-2).
python3-dev is already the newest version (3.7.3-1).
libxmlsec1-dev is already the newest version (1.2.27-2).
zlib1g-dev is already the newest version (1:1.2.11.dfsg-1).
libpq-dev is already the newest version (11.14-0+deb10u1).
libxml2-dev is already the newest version (2.9.12+dfsg-0+0~20210621.9+debian10~1.gbp43e861).
The following package was automatically installed and is no longer required:
libzip5
Use 'apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Using cached Python venv from /srv/zulip-venv-cache/168eb7839ea46fd05c260839a9d06a088ba61c90/zulip-py3-venv
ln -nsf /srv/zulip-venv-cache/168eb7839ea46fd05c260839a9d06a088ba61c90/zulip-py3-venv /home/zulip/deployments/2021-12-02-20-31-23/zulip-py3-venv
Node version 14.16.1 and yarn version 1.22.10 are already installed.
generate_secrets: No new secrets to generate.
2021-12-02 18:31:28,828 upgrade-zulip-stage-2: Installing static assets...
2021-12-02 18:31:47,259 upgrade-zulip-stage-2: Checking for needed migrations
2021-12-02 18:31:50,643 upgrade-zulip-stage-2: Stopping Zulip...
process-fts-updates: stopped
zulip-django: stopped
zulip-tornado: stopped
zulip-workers:zulip_deliver_enqueued_emails: stopped
zulip-workers:zulip_deliver_scheduled_messages: stopped
zulip-workers:zulip_events_slow_queries: stopped
zulip-workers:zulip_events_outgoing_webhooks: stopped
zulip-workers:zulip_events_invites: stopped
zulip-workers:zulip_events_signups: stopped
zulip-workers:zulip_events_user_activity_interval: stopped
zulip-workers:zulip_events_missedmessage_email_senders: stopped
zulip-workers:zulip_events_deferred_work: stopped
zulip-workers:zulip_events_missedmessage_mobile_notifications: stopped
zulip-workers:zulip_events_error_reports: stopped
zulip-workers:zulip_events_email_senders: stopped
zulip-workers:zulip_events_embedded_bots: stopped
zulip-workers:zulip_events_email_mirror: stopped
zulip-workers:zulip_events_user_activity: stopped
zulip-workers:zulip_events_embed_links: stopped
zulip-workers:zulip_events_digest_emails: stopped
zulip-workers:zulip_events_missedmessage_emails: stopped
zulip-workers:zulip_events_user_presence: stopped

Zulip stopped successfully!
2021-12-02 18:32:07,610 upgrade-zulip-stage-2: Applying Puppet changes...
Error: Evaluation Error: Error while evaluating a Function Call, 'new' The string '16067.30' cannot be converted to Integer (file: /home/zulip/deployments/2021-12-02-20-31-23/puppet/zulip/manifests/common.pp, line: 32, column: 22) on node mail.host.net
Traceback (most recent call last):
File "/home/zulip/deployments/2021-12-02-20-31-23/scripts/lib/upgrade-zulip-stage-2", line 297, in
subprocess.check_call(["./scripts/zulip-puppet-apply", "--force"])
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['./scripts/zulip-puppet-apply', '--force']' returned non-zero exit status 1.
Traceback (most recent call last):
File "/home/zulip/deployments/current/scripts/lib/upgrade-zulip", line 58, in
+ deploy_options)
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/home/zulip/deployments/2021-12-02-20-31-23/scripts/lib/upgrade-zulip-stage-2', '/home/zulip/deployments/2021-12-02-20-31-23']' returned non-zero exit status 1.
`

That still looks like a puppet version mismatch.  On Buster, we expect Puppet 5.5.10, and the error there looks like it's from version 3, maybe 4, of Puppet.  Can you show the output of:
apt-cache policy puppet
lsb_release -a

apt-cache policy puppet
puppet:
Installed: 5.5.10-4
Candidate: 5.5.10-4
Version table:
*** 5.5.10-4 500
500 http://mirror.yandex.ru/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

Hm.  I'm running short on ideas.  Do you use puppet on this host to manage the non-Zulip aspects of it -- for example, as part of a fleet-wide configuration?
Can you show:
which puppet
puppet --version
/usr/bin/puppet --version

root@mail:~# which puppet
/usr/bin/puppet
root@mail:~# puppet --version
5.5.10
root@mail:~# /usr/bin/puppet --version
5.5.10
root@mail:~#

authors: alexmv fiber-optics timabbott


text:
Deprecate and remove legacy unread endpoints

The API endpoints documented here: https://zulip.com/api/mark-all-as-read are effectively special cases of the /api/v1/messages/flags/narrow API endpoint; we should plan to replace client use of them with the more general endpoint, sharing code  web app code from #23579.
The first step for this will be starting a thread in #api design on chat.zulip.org for what our deprecation options are; if the mobile and terminal clients are not using those endpoints, then we can remove them after migrating the web app usage; whereas otherwise we'll need a longer deprecation period.

@zulipbot claim

@zulipbot abandon

@zulipbot claim

@zulipbot claim

@zulipbot abandon

@zulipbot claim

Unfortunately, current zulip-mobile (v27.211) has buttons exercising all three of the endpoints currently documented at https://zulip.com/api/mark-all-as-read:

/api/v1/mark_all_as_read
/api/v1/mark_stream_as_read
/api/v1/mark_topic_as_read

API design conversation started on CZO for this issue: https://chat.zulip.org/#narrow/stream/378-api-design/topic/deprecate.20and.20remove.20legacy.20unread.20endpoints.2C.20.2323598/near/1641196

Hi there! I'm looking forward to complete this issue as my first issue in the project.
As far as i can tell, #23579 actually resolved the issue for the frontend code by deleting the use of the old endpoint. Am I correct?
The first thing I'd do is see if the terminal client is using those APIs and, if so, undertake the work to change them, hopefully proceeding to mobile as a second step.
Please let me know if you have any suggestions or if I'm doing something incorrectly; I'm always seeking to improve myself.

@zulipbot claim

@marco-zan - Thanks for your interest in working on this issue!
If you check out the conversation that was linked above in chat.zulip.org (linked here again), you'll see there's been further discussion on how best to proceed with this issue. As you noted the mobile React Native app and terminal app both use these endpoints. And the web-app does indeed still use some of the bulk mark as read endpoints (stream and topic); see #27372.
If you're interested in working on the frontend updates for the web-app, then looking into the work on #27372 would make sense. Noting here from our contributing guide that before you claim an issue, you should be confident that you know how to address it.
The plan for mobile is to use the new endpoint in the Flutter app implementation of mark as read, which is being worked on by the core team. If you're interested in working on the terminal app's use of these endpoints, then I would start a discussion in the #zulip-terminal stream.
For now, I'm going to unassign you from this issue and remove the "help wanted" label from this issue as it's currently pending work noted above.

Sorry to have claimed without knowing how to proceed. I have missed it reading the docs.
I have read the topic on the chat, i will answer there

The next step for this project is for the mobile and terminal apps to be audited for whether they are using these endpoints, and if not, do something like https://github.com/zulip/zulip/issues/27372.
I don't see issues linked, so it might be that we should open issues for each project similar to #27372.

Marking this as blocked on the mobile apps migrating off of using the affected endpoints; see CZO thread for details. Probably this won't happen until the Flutter app transition later this year.
We also need to update the Python bindings to not recommend the removed endpoints.
Once that's done, removing this should be easy.

authors: Omar-ahmed314 chrisbobbe jcchou12 laurynmm marco-zan quinnah timabbott


text:
Fix handling of new compose box stream input in low height screens

In relatively low height streams, the new compose box's stream picker input (#23355) doesn't fit properly (the text input is off the top of the screen):

Ideally, we'd fix this in a way that also works for other dropdown list widgets with issues fitting on the page; e.g. I'm not sure how the "move topic" input works there.

My guess is the fight fix is the same one we use for user card popovers, which is to have it just appear in the center of the screen if it'd go offscreen in its default placement.

This was fixed in #25434.


text:
Add: Support for extended description box.

See previous work here https://github.com/zulip/zulip/pull/16905.
Currently, there is no way to view a long description other than the
settings panel. This adds a way via the .extended_narrow_description
box.

https://github.com/zulip/zulip/issues/14729.
Testing plan:
Tested Locally.
GIFs or screenshots:

@timabbott  This is ready for review.

@guptaprakhariitr hey, are you up for continuing work on this?  I was overwhelmed at the time you opened this PR.

authors: guptaprakhariitr timabbott


text:
documentation: organize the "Rename a topic" article

Based on @alya 's feedback, I merged the Change the topic of a message and Rename a topic articles.
I also moved parts of Rename a topic to a new article Move content to another stream under Stream management. (as those "move" features are admin-only)
Testing plan:
Generate the docs locally, and run a local web server
GIFs or screenshots:

@bucanero welcome and thanks for working on this!  I like the choice of "Move content to another stream" as the title for the extracted article, and the high-level direction.
A few thoughts on how to improve this pull request:

Can you squash the two commits and write a proper commit message for this change?  Our commit style is to have each commit individually pass tests, so fixing broken links introduced in a previous commit should always be squashed.  Check out the Zulip commit message guidelines for more details: https://zulip.readthedocs.io/en/latest/contributing/version-control.html
Since we're removing a URL that used to work, we should add a redirect so that any external links continue to function.  There's a way to do that in zproject/urls.py (search for /help/`; we'll also need a test change like b345b492db3837b3989ceab992b3f250b54d3437).  This can be squashed in as well.
Can you write a prose description of the reasoning behind some of the changes in the commit message?  Of particular note to me is this paragraph, which was removed:

By default, any user can change the topic of any message. This is useful for
keeping messages organized even if some users are still learning how to use
topics effectively.

The first part appears elsewhere (though I think it's worth highlighting, since it's important).  But I think the second sentence is important explanation for helping users understand how to use the feature, and we shouldn't drop it (unless I'm missing something). But if you did think we don't need it, that'd be a good change to either put in its own commit (with an explanatory commit message) or explain the reasoning in its own little paragraph in the main commit message. E.g. for this PR as written a good commit message in my mind would be:
help: Reorganize articles on editing topics.

* Move content on moving topics between streams to a dedicated article. We advertise it as
   "move content" to hint that one can move messages or split topics, and link to it.
* This deletes change-the-topic-of-a-message, because ....
* This commit mostly just moves content, but it also deletes a few paragraphs at the start of
  the old "change the topic" article.  Most of that content was redundant with the first few paragraphs
  of the surviving "rename a topic" article, and the "This is useful for" sentence was removed because ...

(We use the "help:" prefix for /help/, in contrast with docs: for the ReadTheDocs).
BTW, for how I noticed this: git show --color-moved (or really enabling that option by default in ~/.gitconfig) makes it easy to get this kind of output to see what content was moved vs. deleted:

For this block of added text:

+organization administrators can additionally move topics from one
+stream to another,
+or move a subset of messages to a topic from one
+stream to another.

These links have very long labels, which looks a little awkward.  Also, while you had no way of knowing this, we allow configuring who has permission to move topics between streams (as of just a couple weeks ago); so we should explain this as configurable.  I think this
I think the end result of this reorganization has one downside, which is that we now don't advertise the capability to split a topic or move some messages to another topic, which is a very common use case (e.g. when someone new posts to the wrong place); probably more common than just renaming topics is moving the last 10 messages in an existing topic to a new topic (since it was realized to be a digression from the previous conversation partway through).  Maybe we should add a /help/move-content-to-another-topic article that advertises the ability to split topics?  I'd address this in its own commit, and use your judgement on whether it works better to actually spell out how to do it vs. just link to "rename a topic" or making it the main article, with "rename a topic" being a stub linking to there (I'm not sure what will feel right).
Do you think it'd make sense to have a Related articles section at the bottom of templates/zerver/help/rename-a-topic.md and the new /help/move-content-to-another-stream?  While both articles have various links, it seems like it'd be helpful.  I'd encourage adding this in an independent commit, since it's an independent improvement from reorganizing the articles (and doing it as its own commit will make it easier to understand the changes).
I notice the "Related articles" section of templates/zerver/help/start-a-new-topic.md now has two identical links with different labels; is that intentional?
When convenient, it's nice to show before/after screenshots to help explain your changes.

Sorry this was a bit of an essay, but it's not unusual for a first contribution!   And I think this is a pretty tangly topic documentation-wise, since we the feature itself can be used for what users might think of as several very different purposes.  Let me know when you have a new version to review.

Merged, thanks @bucanero!  I made a few changes:

Added an additional link to the last commit (so that each of the 3 articles on moving topics link to the other 2) and reordered the links to present "Resolve topic" after the more similar features.
Addressed the merge commit properly. We never do merge commits in Zulip; one should always do git pull --rebase to rebase one's commits.  You can configure Git to do that by default (and our Git Guide has docs on how to do so).
Line-wrapped the commit messages.  The content was good, but prose in Git commit messages should always be line-wrapped to 70 characters or so, so that git log in a standard terminal works reasonably.

One other small bit of feedback: You should always post on the GitHub comment thread when you've resolved feedback, with notes on how you resolved it.  Otherwise, it's not clear from looking at the GitHub PR whether your work is ready for a next review, or you've just pushed some partial work towards that goal to get CI to run.
As a quick follow-up, do you think templates/zerver/help/configure-message-editing-and-deletion.md should link to the additional "Move content between streams|topics" articles directly?

Hello @timabbott, thanks for your review and the additional feedback. I'll keep those notes in mind for future PRs, so I can follow Zulip's process properly.
Regarding your question, since the article is admin-related, I think that configure-message-editing-and-deletion.md should include a "Related articles" link to move-content-to-another-stream.md. I feel that a link to "topics" is not needed in this context, since there's already a link to "rename a topic".

authors: bucanero timabbott


text:
templates: Use trans tag for translators.

It's based on "Backend Translations" policy:
https://zulip.readthedocs.io/en/latest/translating.html#backend-translations

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

Merged, thanks for fixing this @kou!

authors: kou smarx timabbott


text:
settings_users: Display status update notifications inside modal.

In settings, clicking on deactivate bot button will lead to open confirmation modal, and displaying all status update notifications inside this confirmation modal.
This PR will also lead to display status update notifications of edit user/bot inside their edit form modal.
It is a follow-up of #21490
Possible issues encountered: There is no loading spinner on buttons of edit user/bot modal. (If it is a candidate for change should I post another PR or add change to this PR)

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] 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.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@yogesh-sirsat this looks pretty good; I posted a batch of comments on various details that need attention, as well as a potential follow-up refactoring.

@timabbott PR updated.

Can you comment explicitly on how you addressed the previous round of feedback -- just saying you've updated a PR doesn't make it clear what choices you made and what the outstanding action items are.  E.g. I'm not sure what, if anything, you did in response to https://github.com/zulip/zulip/pull/21864#discussion_r855322894. (E.g. starting a #frontend thread as discussed and linking it would have been a good resolution)

Oh, I thought we are going to do this extra changes as a follow-up, so I just updated only those changes which was closely related to current PR target, including deactivate bot modal title error string, call scrollbar animate to specific target element, and fix linter of first commit inside first commit.

authors: timabbott yogesh-sirsat


text:
help_docs: Document subscribing a user to stream via @-mention.

Updates the help center documentation on subscribing users to streams to include description for doing so via mentioning a user while composing a message.
Fixes #21796.
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.

[ ] 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).

[x] Each commit is a coherent idea.
[ ] 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.

@alya - I've updated the text for those revisions.
Screenshot with revised text:

The screenshot looks good to me!

Rebased and merged, thanks @laurynmm!

authors: alya laurynmm timabbott


text:
drafts: Add a copy draft button.

[x] Add a copy draft button to the drafts panel.

Fixes: CZO Thread

Screenshots and screen captures:

Before:
After:

Demo:

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.
[x] Calls out remaining decisions and concerns.
[x] 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.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@terpimost @karlstolley Could you please review the PR, thanks :)
@zulipbot add "area: popovers"

@zulipbot adds "maintainer review"

@zulipbot add "maintainer review"

I fixed this being incorrectly labeled as a "popovers" issue, as it's about the drafts overlay.


text:
puppet: Serve /etc/zulip/well-known/ in nginx as /.well-known/.

Note this is only for zulip_ops, not for default installs.

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.

Looks great, merged, thanks @alexmv!

authors: alexmv timabbott


text:
Update user groups documentation

This makes some tweaks on top of #28096.

Merged, thanks @alya!

authors: alya timabbott


text:
left_sidebar: Remove padding from bot icon.

The padding on the bot icon is no longer necessary for vertical alignment, and by removing the 6px of padding it represents, bot DM rows will have the same 22px height as other DM rows.
CZO discussion

Screenshots and screen captures:

Before
After

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.
[x] Calls out remaining decisions and concerns.
[x] 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.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Looks great, and tagged as a backport candidate (we probably need #29004 too if we backport this, since it's nice and localized).

Cool. Sorry about the sloppiness with #29004.

authors: karlstolley timabbott


text:
help: Add example playground URL templates.

Fixes #29067. Replaces #29166.
The playgrounds were tested successfully by @laurynmm .

Merged, thanks @alya!


text:
integrations: Add OpsGenie integration.

See discussion on Zulip.

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

@timabbott updated the PR. Regarding the macro:
It is mostly redundant with {!create-stream.md!}, except for the info

The integration will automatically use the default stream
opsgenie if no stream is supplied.

I removed it, but since two other integrations are using the same text snippet, should I make a PR for removing it there as well and add the extra phrase to the macro? (FWIW, the doc on this macro is outdated as well, so I can jsut update it at the same time.

The one failing backend test seems to be a Travis flake.

There's some trailing whitespace in several of the fixtures files; easy to see with git show in color mode.  Are those intentional?  If not, it'd be great to fix them and then we can merge.

@timabbott Should be fixed now. I suppose we don't run the linter on fixtures?

Yeah; we probably should adjust the linter configuration to run at least some of the whitespace linters on the fixtures.

Merged, thanks @derAnfaenger!!

@rishig FYI; you can let the interested user know we've already added this :)

authors: derAnfaenger smarx timabbott


text:
Teamcity integration

This Fixes #683 https://github.com/zulip/zulip/issues/683
I will write the documentation soon, just wanted to get this pull request out there for feedback.

Automated message from Dropbox CLA bot
@dwrpayne, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Hmm... why are there a couple other commits in this branch? I am fairly new to github workflow - not sure what I need to do in order to fix this.

I believe that results from your having done a git pull rather than git pull --rebase at some point while developing your branch.  You should be able to fix this via:
git pull --rebase # to rebase your local branch on top of master
git push origin +HEAD:teamcity-integration # to update the branch on GitHub that this PR is based on

Ack! That seems to have made things worse. Sorry :( I think I'll close this pull request and try to fix it - maybe I'll make a new branch and cherry-pick the one commit I want into it. :)

OK -- even if you need to remake your local branch, you actually should be able to reuse this pull request if after making your new branch, you force-push using git push origin +HEAD:teamcity-integration, rather than making a new one.
You may want to play with a graphical git viewer like gitk or SourceTree to help you see what's going on if you run into a similar problem in the future.

authors: dwrpayne smarx timabbott


text:
[Off-canvas] Example Code in Documentation has FOUC problems - not usable

Searching for the solution for #8659 I am going through everything from zero.
The example linked from the off-canvas documentation comes with a FOUC problem. This is not acceptable.
You just can not publish an example with such a heavy FOUC problems and say "people, look, this is how it is done!". This is a serious problem, not an aside, somebody in your house is missing this.
You just can not publish unusable amateurish examples and keep on writing about "world class" and "enterprise" and stuff like that. You are generating a reputation problem not only for your company, but for everybody who uses zurb foundation.
Please update that example to a production grade quality or just remove it.

What browser and OS are you using? I see no FOUC. Only the small nav shows on the small breakpoint, and only the desktop nav shows from medium and up.
The only thing that doesn't load right away for me is the placeholder image below the navigation bar, but that is normal and has nothing to do with FOUC.

What an agressive bug report !!!!!
I'm pretty sure you're seing a FOUC where it's a normal behavior:
Small size -> drilldown menu
Widen the window, reaching the medium breakpoint and replace with a dropdown menu
Continue to widen, and the ZURB left toolbar will appear, toolbar wich is "off example" but which will size down the main content thus resizing it under small breakpoint -> It will fire the small breakpoint and the drilldown will replace the dropdown. It's normal, because of the left toolbar appearence resizing the content...
Continue to enlarge and the dropdown will fire after medium-breakpoint.
To polish things a bit, the solution would be force to force breakpoints of the example to lower values, so the ZURB left toolbar would not fire the small breakpoint.
Am I right ?

@gehasia that's the only thing that I can see that looks "off" with this example, but I'm not sure if that's even what @COLABORATI is referring to. I wouldn't consider that FOUC.

@COLABORATI I'm going to close this issue, assuming the FOUC you are referring to has to do with the iframe width changing between breakpoints (not to be confused with Foundation's breakpoints inside the iframe) on the building blocks site. As @gehasia mentioned, this is because the left toolbar changes widths, which makes the iframe width change.

Well, of course you should copy the code that is shown on that example page an test it in its own html file - there is a very clearly visible FOUC in all browsers I tested (Linux, Apple, Windows). This is not visible on the "Zurb University" Page where this example is presented.

@gehasia: yes, I am really frustrated with Foundation 6, since it was released I stumble from one bug or problem to another, this would have been absolutely no problem at all if it was still in alpha or beta status - but releasing this as "production ready" is the thing here that makes me feel bad. Wasted many, many hours with pre-alpha quality code. Hopefully F 6.5 will be on a good way to release quality, but until then much pain.

@COLABORATI thank you for clarifying. Not sure why this doesn't happen on the Building Blocks site, but I was able to reproduce locally. The same code that is recommended for preventing FOUC of the responsive navigation will work here:
SCSS
/* To prevent FOUC */
.no-js {
  @include breakpoint(small only) {
    .top-bar {
      display: none;
    }
  }

  @include breakpoint(medium) {
    .title-bar {
      display: none;
    }
  }
}

CSS
/* To prevent FOUC */
.no-js .top-bar {
  display: none;
}

@media screen and (min-width: 40em) {
  .no-js .top-bar {
    display: block;
  }

  .no-js .title-bar {
    display: none;
  }
}

@kball @rafibomb please add the above SCSS & CSS to building block: http://zurb.com/building-blocks/top-bar-with-off-canvas
We should add this to the docs too.

Thanks, Colin, for the professional handling of this issue.
However, the Zurb University example still has not been changed and has this problem - please fix that example or remove it, thanks!

I can not find it here

@DanielRuf the building block is probably gone now. Between the time this issue was active and now, the building blocks were revamped and off-canvas was rewritten.
@brettsmason do you know of any FOUC issues with the newer off-canvas? Is this still something we should consider adding to the off-canvas docs?

Closing as this may not be relevant anymore.

authors: COLABORATI DanielRuf colin-marshall gehasia

repo: zurb/foundation-sites


text:
don't skip 'small down' value for breakpoint

sass tests
revert to comparison with unitless 0

releated to: #7587
With this, breakpoint(small down) will transpile to media query css, but breakpoint(0 down) will be skipped. I also took liberty to modify sass tests.

+1

authors: TvrtkoM pwnall


text:
TwentyTwenty has height issues when used with Owl Carousel

This has always been a bit of an on-going issue since I started using these two items together. I know that I definitely want to use them both, and there must be a way to do it, as I've seen it used on other sites.
Anyway, I've tried using the 20/20 on it's own, and it seems to work fine when static. I've also used Owl Carousel 2 on it's own with static images, and that seems to work fine too.
But when I try to combine them, so I have multiple instances of 20/20 as 'slides' in Owl Carousel, there is an issue regarding the height of the 20/20 container, when resizing the windows.
This leads to issues when rotating mobile devices, and changing browser sizes. Usually, it sometimes gets fixed by resizing and after letting go of the mouse buttons, it may change. But sometimes it does not.
I've tried using the window.resize in the past, but that doesn't seem to make any difference.
A good example of this can be found at https://www.bellavou.co.uk/face/facelift/ - Try resizing the browser window when viewing the 20/20 slider, and after a while, you'll start to see gaps making the slide container appear huge, and not resizing with the browser.
I'm not sure what I can do, but I'm open to all suggestions and all help is appreciated! Sorry for the wordy issue...

Hey @leecollings I see the issue. Seems like both Owl and TwentyTwenty make use of the window resize event. It appears that Owl updates the width of the carousel container during the resize event AFTER TwentyTwenty has already performed its resizing calculations.
But there is hope! I found a hack to make it work for like you would expect. What it essentially does is listens for the Owl resized.owl.carousel event which indicates the Owl carousel container has finished resizing itself. At this point we can trigger another window resize event which TwentyTwenty looks for and it will base its calculations on the new container width. I tried it on your site and it appears to fix the issue:
jQuery('.owl-carousel').on('resized.owl.carousel', function(event) {
  jQuery(window).trigger("resize");
});

There are probably better solutions out there ... but I hope this helps you out. Cheers!

Hey there, thanks for your comment, that's been really helpful.
Although maybe I'm doing it wrong, but although the resize is working, it seems everytime the window is resized, I'm just adding another instance of 2020 ontop of my existing one (I can tell this from the slider line getting a thicker shadow everytime).
// load TwentyTwenty after the page has loaded
$(window).load(function(){
    $(".twentytwenty").twentytwenty();
});

// reload TwentyTwenty on page resize/orientation
$('.owl-carousel').on('resized.owl.carousel', function(event) {
    $(window).trigger("resize");
    $(".twentytwenty").twentytwenty();
});

Am I able to rather than initialise 2020 for another time, just re-initialise it?

If I'm not mistaken I don't think it's necessary to re-initialize TwentyTwenty. You could rewrite the code as follows:
// load TwentyTwenty after the page has loaded
$(window).load(function(){
    $(".twentytwenty").twentytwenty();
});

// reload TwentyTwenty on page resize/orientation
$('.owl-carousel').on('resized.owl.carousel', function(event) {
    $(window).trigger("resize");
    // Commenting this code out
    //$(".twentytwenty").twentytwenty();
});

However it's been a little while since I've looked at the code. If that doesn't work can you post a link to your site? Thanks!

Hmm it still doesn't seem to be resizing if I emulate orientation changes on iPad viewing.
It's fine when going from portrait to landscape, as the slider scales up, but when going back to portrait, the slider scales down but it's container height remains, leaving an ugly white box of space underneath.
You can view the page at: http://development.bellavou.co.uk/face/facelift/ but there's authentication applied to this subdomain. Are you able to send me a private message or email requesting this? or add me on Skype

authors: leecollings mhayes

repo: zurb/twentytwenty

license: ISC


text:
🛑 Economy API Endpoint is down

In e29e3d9, Economy API Endpoint (https://economy.roblox.com) was down:

HTTP code: 404
Response time: 189 ms

Resolved: Economy API Endpoint is back up in 73e2bf7 after 23 minutes.


text:
⚠ ZV800.com has degraded performance

In 3a1fd01, ZV800.com (https://www.zv800.com//) experienced degraded performance:

HTTP code: 200
Response time: 1110 ms

Resolved: ZV800.com performance has improved in 81b3b9e after 11 minutes.


text:
it works... but it doesn't - able to connect and send first message but then throws exceptions

Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
self.run()
File "/usr/lib/python3.5/threading.py", line 862, in run
self._target(*self._args, **self._kwargs)
File "/home/albert/whatsapp-web/chat.py", line 119, in startGetMsg
incoming_scheduler.run()
File "/usr/lib/python3.5/sched.py", line 147, in run
action(argument, **kwargs)
File "/home/albert/whatsapp-web/chat.py", line 129, in getMsg
curr_thread_name = printThreadName(driver)
File "/home/albert/whatsapp-web/chat.py", line 222, in printThreadName
curr_thread_name = driver.find_element(By.XPATH, '//[@id="main"]/header//span[contains(@dir, "auto")]').text
File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 744, in find_element
{'using': by, 'value': value})['value']
File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 231, in execute
response = self.command_executor.execute(driver_command, params)
File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/remote_connection.py", line 395, in execute
return self._request(command_info[0], url, body=data)
File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/remote_connection.py", line 425, in _request
self._conn.request(method, parsed_url.path, body, headers)
File "/usr/lib/python3.5/http/client.py", line 1107, in request
self._send_request(method, url, body, headers)
File "/usr/lib/python3.5/http/client.py", line 1142, in _send_request
self.putrequest(method, url, **skips)
File "/usr/lib/python3.5/http/client.py", line 975, in putrequest
raise CannotSendRequest(self.__state)
http.client.CannotSendRequest: Request-sent
after that whatever I type manages to go through to recipient but the script is otherwise broken, unable to receive messages.

I got a similar error but I am at least able to send messages using the send to command. Anybody else with this issue?

@cherkie The code has been updated and should work now. If you're still facing this issue please post your OS, selenium, and webdriver version. Thanks

authors: cherkie tomasi-o zvovov

repo: zvovov/whatsapp-web


text:
Aeon Labs Minimote appears as dead after network restart, despite being a battery device

Describe the bug
After I include the Minimote, it is found and the status is Asleep. When I restart zwavejs2mqtt, the node is detected as Dead, and all the device information is blank (not reloaded from cache). Once I click on a button on a remote, it completes the interview process and keeps it in the Alive status, never going Asleep, as if it were a mains-powered device. The device information is filled back in.
The device was included while on battery power.
Device information
Which device(s) is/are affected (make/model)?  Aeon Labs Minimote
What are the node IDs? Node 008
Last Known Working Configuration

[ ] New device

[ ] Previously working device (node-zwave-js)

Which library version/docker image/adapter version?
Have you made any recent configuration changes to the device? Describe.

[X] Previously working device (other platform)

Which platform? OZW
Have you made any recent configuration changes to the device? Describe. No.

Installation information
How did you install node-zwave-js?

[ ] zwavejs2mqtt (latest) docker image
[X] zwavejs2mqtt (dev) docker image
[ ] ioBroker.zwave2 adapter
[ ] Pkg
[ ] Manual Docker build

node-zwave-js branch:
zwavejs2mqtt branch:

[ ] Manually built (as described in the docs)
[ ] Other:

To Reproduce
Steps to reproduce the behavior:

Start inclusion process
Include Minimote
Notice everything looks ok
Restart zwavejs2mqtt
Notice the device details (mfg, product) are blank, and the device status is Dead
Press a button, device details appear and the device is marked incorrectly as Alive (should be asleep eventually).

Additional context
As discussed in the HA discord, this problem occurs because the device does not advertise the Wake Up CC during the interview, despite supporting it. I noticed the OZW device config file has several workarounds, including manually advertising the Wake Up CC, which is probably why I never noticed a problem there. Those are missing from the zwave-js config file.
After restarting the network, I noticed that if the very first thing I do is manually wake up the device (hold down the learn button for a few seconds), then zwave-js will decide to add the Wake Up CC to the node's list of CCs. Because of this, the attached cache file contains it. From this point on, restarting zwavejs2mqtt works fine and the device functions as expected (RestartFromCache, Asleep). If I send the wake up notification after pressing a button (thus finished the interview), the Wake Up CC will never be added.
Perhaps overriding the command classes in the config like OZW would be a good idea, to force zwave-js to think it supports the wake up CC during the inclusion. This would make a better experience. See config file.
Logfile: zwavejs_1.log
Cache files: logs.zip

First breadcrumb: zwave-js assumes this device supports WakeUp, but querying the version tells us otherwise:
17:44:13.341 DRIVER « [Node 008] [REQ] [BridgeApplicationCommand]
                      └─[VersionCCCommandClassReport]
                          CC:      Wake Up
                          version: 0
17:44:13.346 CNTRLR   [Node 008]   does NOT support CC Wake Up (0x84)

That doesn't have an effect though until the driver restarts - then the WakeUp CC is really missing from the list.

First breadcrumb: zwave-js assumes this device supports WakeUp, but querying the version tells us otherwise:
17:44:13.341 DRIVER « [Node 008] [REQ] [BridgeApplicationCommand]
                      └─[VersionCCCommandClassReport]
                          CC:      Wake Up
                          version: 0
17:44:13.346 CNTRLR   [Node 008]   does NOT support CC Wake Up (0x84)

That doesn't have an effect though until the driver restarts - then the WakeUp CC is really missing from the list.

Okay, it seems that this behavior is not spec-compliant. To get around it, we should force-add the WakeUp CC as supported with a compat flag.

Okay, it seems that this behavior is not spec-compliant. To get around it, we should force-add the WakeUp CC as supported with a compat flag.

authors: AlCalzone kpine

repo: zwave-js/node-zwave-js