text:
频繁出现 [OpenAI] 服务器拒绝访问，请稍后再试 | Server refused to access, please try again later

我很早就开始使用本项目了 (ฅ´ω`ฅ)
昨天我看到本项目的更新，即不再需要chatgpt-proxy-server，所以我尝试了最新的方案。
我使用的go-chatgpt-api版本是：
[
    {
        "Id": "952e6c260ebd9c6c812836b93cc96308c11be589800a85ba4ce9f29f377f52be",
        "Created": "2023-04-29T23:54:32.930107483Z",
        "Path": "/app/go-chatgpt-api",
        "Args": [],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 466863,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2023-04-29T23:54:34.372380033Z",
            "FinishedAt": "0001-01-01T00:00:00Z"
        },
        "Image": "sha256:52df78ab127aafeccae0c2d8ae2d2415cf9e4e752258385f3c93888480f109fc",
        ...
    }
]

但是，我发现它会频繁出现报错： [OpenAI] 服务器拒绝访问，请稍后再试 | Server refused to access, please try again later。刷新一下可以正常输出。这和以前我们直接访问网页时非常相似。 我感觉没有之前使用chatgpt-proxy-server的时候稳定。
不知大家有没有这种情况？

我遇到同样的问题403，使用了warp也一样。机器在东京

@Beckjiang
是啊，作者昨天一波更新，以为已经稳定了，大意了！

希望大佬 @linweiyuan 可以出一个稳定的旧版本镜像，使用旧的方案，让咱们过渡一下。 旧的方案很稳 (ฅ´ω`ฅ)
现在只有latest，不知道怎么下载旧的镜像

刷新一下是重启 API 吗？

刷新一下是重启 API 吗？

我是这样做的。 之前的版本的docker-compose.yml内容是：
services:
  go-chatgpt-api:
    container_name: go-chatgpt-api
    image: linweiyuan/go-chatgpt-api
    ports:
      - 8080:8080 # 宿主机8080端口可按需改为其它端口
    environment:
      - GIN_MODE=release
      - CHATGPT_PROXY_SERVER=http://chatgpt-proxy-server:9515
      - NETWORK_PROXY_SERVER=socks5://chatgpt-proxy-server-warp:65535
    depends_on:
      - chatgpt-proxy-server
      - chatgpt-proxy-server-warp
    restart: unless-stopped

  chatgpt-proxy-server:
    container_name: chatgpt-proxy-server
    image: linweiyuan/chatgpt-proxy-server
    environment:
      - LOG_LEVEL=INFO
    restart: unless-stopped

  chatgpt-proxy-server-warp:
    container_name: chatgpt-proxy-server-warp
    image: linweiyuan/chatgpt-proxy-server-warp
    environment:
      - LOG_LEVEL=INFO
    restart: unless-stopped

昨天，我用docker-compose pull更新镜像后，用的是新的方案：
services:
  go-chatgpt-api:
    container_name: go-chatgpt-api
    image: linweiyuan/go-chatgpt-api
    ports:
      - 8080:8080
    environment:
      - GIN_MODE=release
      - GO_CHATGPT_API_PROXY=socks5://chatgpt-proxy-server-warp:65535
    depends_on:
      - chatgpt-proxy-server-warp
    restart: unless-stopped

  chatgpt-proxy-server-warp:
    container_name: chatgpt-proxy-server-warp
    image: linweiyuan/chatgpt-proxy-server-warp
    environment:
      - LOG_LEVEL=INFO
    restart: unless-stopped

这个新的方案是非常不稳定的，经常出现[OpenAI] 服务器拒绝访问，请稍后再试 | Server refused to access, please try again later。

刷新一下是重启 API 吗？

其实不太懂大佬您要问什么。 我使用的并不是API模式，而是Access Token的模式。 API模式我不需要用这个反向代理。

我的报403
[GIN] 2023/04/30 - 07:52:01 | 403 |  1.762843867s |             ::1 | GET      "/conversations?limit=5&offset=0"

我请小伙伴build了一个旧版本的go-chatgpt-api，供大家过渡使用：
docker pull ddsderek/go-chatgpt-api:latest

使用旧的方法和参数：
services:
  go-chatgpt-api:
    container_name: go-chatgpt-api
    image: ddsderek/go-chatgpt-api
    ports:
      - 8080:8080 # 宿主机8080端口可按需改为其它端口
    environment:
      - GIN_MODE=release
      - CHATGPT_PROXY_SERVER=http://chatgpt-proxy-server:9515
      - NETWORK_PROXY_SERVER=socks5://chatgpt-proxy-server-warp:65535
    depends_on:
      - chatgpt-proxy-server
      - chatgpt-proxy-server-warp
    restart: unless-stopped

  chatgpt-proxy-server:
    container_name: chatgpt-proxy-server
    image: linweiyuan/chatgpt-proxy-server
    restart: unless-stopped
    environment:
      - LOG_LEVEL=INFO

  chatgpt-proxy-server-warp:
    container_name: chatgpt-proxy-server-warp
    image: linweiyuan/chatgpt-proxy-server-warp
    restart: unless-stopped
    environment:
      - LOG_LEVEL=INFO

希望大佬们能尽快修复这个bug ヾ(≧∇≦*)ゝ 加油

是超过30分钟不用就 403，还是用着用着突然 403

是超过30分钟不用就 403，还是用着用着突然 403

不用30分钟。 可能有1-2分钟不用就会出现

~是超过30分钟不用就 403，还是用着用着突然 403~
试出来了

我没用镜像，没有成功过，都是403，不知道啥原因

我在本地挂机长时间正常，服务器上挂机2分钟403，感觉和 warp 有关
@nephen 全部接口都403吗？还是平时只用一个接口

conversations接口403，其他的不知道，获取不了会话，conversation接口也用不了

我在本地挂机长时间正常，服务器上挂机2分钟403，感觉和 warp 有关
@nephen 全部接口都403吗？还是平时只用一个接口

本地跑的裸程序也正常吗？我的环境跑原来的版本是正常的

应该是没有配 GO_CHATGPT_API_PROXY

应该是没有配 GO_CHATGPT_API_PROXY

配了的，我直接放在境外服务器跑也不行

之前的最新分支：https://github.com/linweiyuan/go-chatgpt-api/commits/legacy
整了个 linweiyuan/go-chatgpt-api:legacy，或者你自己打个先用
有点玄学，我现在服务器挂机十几分钟也没有 403 了

我这边测试了下最新版本，没出现403；环境国内服务器+代理

没用warp，没复现

有点玄学，我现在服务器挂机十几分钟也没有 403 了

大佬在使用的时候有用WARP吗？

经过测试，总结了这么几个情况：

本地镜像+魔法，正常
本地二进制+魔法，正常
服务器上镜像+魔法，正常
服务器上二进制+魔法，正常
服务器上镜像+WARP，有时 403 但重试 200，有时一直 200
服务器上二进制+WARP，一直 403

目前来看，本地跑或者服务器上加魔法是最稳的，上了 warp 就会 403 （不上也会 403，但那个是 1020）
服务器 403 的时候输出的 IP 地址也是 Cloudflare 的地址，但少了个 cookie：_cfuvid
目前来看，问题出现在 warp 上，但是我并不熟这个东西，所以可能会尝试用一些奇怪的方法来修复
有兴趣可以找那些一键 warp 脚本试下好不好使，还没试过
相同 warp 镜像，旧版为什么可以，也不清楚

经过测试，总结了这么几个情况：

本地镜像+魔法，正常
本地二进制+魔法，正常
服务器上镜像+魔法，正常
服务器上二进制+魔法，正常
服务器上镜像+WARP，有时 403 但重试 200，有时一直 200
服务器上二进制+WARP，一直 403

目前来看，本地跑或者服务器上加魔法是最稳的，上了 warp 就会 403 （不上也会 403，但那个是 1020）
服务器 403 的时候输出的 IP 地址也是 Cloudflare 的地址，但少了个 cookie：_cfuvid
目前来看，问题出现在 warp 上，但是我并不熟这个东西，所以可能会尝试用一些奇怪的方法来修复
有兴趣可以找那些一键 warp 脚本试下好不好使，还没试过
相同 warp 镜像，旧版为什么可以，也不清楚

我属于这种情况： 服务器上镜像+WARP，有时 403 但重试 200，有时一直 200

经过测试，总结了这么几个情况：

本地镜像+魔法，正常
本地二进制+魔法，正常
服务器上镜像+魔法，正常
服务器上二进制+魔法，正常
服务器上镜像+WARP，有时 403 但重试 200，有时一直 200
服务器上二进制+WARP，一直 403

目前来看，本地跑或者服务器上加魔法是最稳的，上了 warp 就会 403 （不上也会 403，但那个是 1020）
服务器 403 的时候输出的 IP 地址也是 Cloudflare 的地址，但少了个 cookie：_cfuvid
目前来看，问题出现在 warp 上，但是我并不熟这个东西，所以可能会尝试用一些奇怪的方法来修复
有兴趣可以找那些一键 warp 脚本试下好不好使，还没试过
相同 warp 镜像，旧版为什么可以，也不清楚

我没用warp，就是本地二进制加魔法403
{403 Forbidden 403 HTTP/2.0 2 0 map[Alt-Svc:[h3=":443"; ma=86400, h3-29=":443"; ma=86400] Cache-Control:[private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0] Cf-Mitigated:[challenge] Cf-Ray:[7bfe502ab9eb2ad3-LAX] Content-Encoding:[br] Content-Type:[text/html; charset=UTF-8] Cross-Origin-Embedder-Policy:[require-corp] Cross-Origin-Opener-Policy:[same-origin] Cross-Origin-Resource-Policy:[same-origin] Date:[Sun, 30 Apr 2023 08:11:17 GMT] Expires:[Thu, 01 Jan 1970 00:00:01 GMT] Permissions-Policy:[accelerometer=(),autoplay=(),camera=(),clipboard-read=(),clipboard-write=(),fullscreen=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=()] Referrer-Policy:[same-origin] Server:[cloudflare] Set-Cookie:[__cf_bm=E1BLY7p8.r8AiSwwz07rG1uoWGffED9D6MXcR63CYIk-1682842277-0-AY9jQg8ck6oe7iQmM3/4COc4YGr+RJhLeMBFcYuvKFpx84cQbst3/rOQ/9mIPcPWooT50f+JkcQ/7UujLbi1gxo=; path=/; expires=Sun, 30-Apr-23 08:41:17 GMT; domain=.chat.openai.com; HttpOnly; Secure; SameSite=None] Vary:[Accept-Encoding] X-Frame-Options:[SAMEORIGIN] X-Robots-Tag:[nofollow]] 0xc000036040 -1 [] false true map[] 0xc0004de500 0xc0003b4270}

Client, _ = tls_client.NewHttpClient(tls_client.NewNoopLogger(), []tls_client.HttpClientOption{
	tls_client.WithCookieJar(tls_client.NewCookieJar()),
	tls_client.WithDebug(),
}...)

这种 403，Access denied：

这种 403，挂机 2 分钟左右出现，重试 200：

给大哥提供连个线索 不知道有没有帮助 （和本项目无关）
https://p3terx.com/archives/cloudflare-warp-configuration-script.html
https://mailberry.com.cn/2023/02/cf-solve-it-completely-error-code-1020-by-warp/
我在仅使用xray扶墙 然后把openai.com分流到127.0.0.1:40000上
这种情况下 开无痕模式  第一次登录还是要通过一个cf真人校验

给大哥提供连个线索 不知道有没有帮助 （和本项目无关） https://p3terx.com/archives/cloudflare-warp-configuration-script.html https://mailberry.com.cn/2023/02/cf-solve-it-completely-error-code-1020-by-warp/ 我在仅使用xray扶墙 然后把openai.com分流到127.0.0.1:40000上 这种情况下 开无痕模式 第一次登录还是要通过一个cf真人校验

目前基本上就是这样做的，相同的做法，老版本（基于浏览器）正常，新版本（API 直连）有时可以有时不可

还有个建议
大哥你的容器镜像 能不能做个版本管理
现在只有latest 实在是难受
一不知道是否有更新
二没办法回退
望采纳 ：）

还有个建议 大哥你的容器镜像 能不能做个版本管理 现在只有latest 实在是难受 一不知道是否有更新 二没办法回退 望采纳 ：）

赞同。 根据我使用bitwarden镜像的经验，开发者一般会有一个test的tag，该tag会频繁更新，表明容器处于beta版本。而latest和最新版本号是同步发布的。 建议 @linweiyuan 大佬采用这种方式维护go-chatgpt-api，这样会比较规范些(ฅ´ω`ฅ)

这个汇总有例子如何让镜像自动更新到最新：https://github.com/linweiyuan/go-chatgpt-api/issues/74
更新了之后，其实旧镜像不删还是在本地的，改回来名字就可以直接用了
下回打包除了 latest，再打个当前时间戳

这个 bug 已修复

这个 bug 已修复

大佬方便大致讲一下问题发生在哪里吗？

更新了linweiyuan/go-chatgpt-api镜像，还是403，大家更新后OK吗

更新了linweiyuan/go-chatgpt-api镜像，还是403，大家更新后OK吗

比昨天要稳定很多，暂时只出现了1次网络连接问题。 如果是403，说明你的安装或使用的过程有某些问题。

这个 bug 已修复

大佬方便大致讲一下问题发生在哪里吗？

https://github.com/linweiyuan/go-chatgpt-api/commit/cb31b2e93d21010162f6ccf97992b97e212e9e61
测试的时候发现只要频繁刷新，就不会 403，旧版本因为浏览器的局限性强制每分钟后台自动刷一次，所以旧版本没有 403
那么我抄了过来，发现靠谱，但是如果问具体的原理，不清楚，我把它称为一个类似保持心跳的魔改功能

@linweiyuan
谢谢。 虽然简单粗暴但有效。点赞 (ฅ´ω`ฅ)

更新了linweiyuan/go-chatgpt-api镜像，还是403，大家更新后OK吗

测试的时候，程序启动完去调用，有机会会出现 403，但是只要 200 了，后面就没有看到了
我也感觉是哪里的配置不对

@linweiyuan
今天测试发现，刚刚开始布署的时候挺正常。 但是到后面，会持续出现 频繁出现 [OpenAI] 服务器拒绝访问，请稍后再试，完全没法使用。不能通过重启该docker stack解决。
部署方案是服务器上镜像+WARP。
问题应该还是没有实质性解决。重开issue Σ( ° △ °|||)︴

很奇怪，我的就没有成功过，裸程序+魔法跑的，现在一直是报500错误

很奇怪，我的就没有成功过，裸程序+魔法跑的，现在一直是报500错误

@nephen
你可以按我的博客教程操作一下： Docker系列 基于OpenAI API和Access Token自建ChatGPT
旧方法还是挺稳的，新方法不好说 Σ( ° △ °|||)︴

有人用旧方法 CPU 不知为何长时间占用 100%，被 VPS 商封了号，但我测试占用都比较低
我用新镜像早上到现在挂机，测试依旧正常

服务器容器+WARP：

本地裸跑+魔法：

本地容器+魔法：

@huangwb8 他非常熟悉旧版本，是本项目代码贡献者之一。。。

@nephen 不是 403 吗，怎么变 500 了，回到 403 的场景，试下加这一行代码看下会不会 200 req.Header.Set("Cookie", "cf_clearance=xxx; _cfuvid=xxx;")，值从官方网站拿，有点怀疑和这个有关，有另外的人也是一直 403

@linweiyuan
是的，我知道的，因为 @nephen  的角色是author呀 (ฅ´ω`ฅ)
我之前旧方法也出现过CPU占用很高，但后面比较少出现了。 现在占用还好吧。推测与磁盘空间大小/SWP大小有关。

有人用旧方法 CPU 不知为何长时间占用 100%，被 VPS 商封了号，但我测试占用都比较低
我用新镜像早上到现在挂机，测试依旧正常
服务器容器+WARP：

本地裸跑+魔法：

本地容器+魔法：

@huangwb8 他非常熟悉旧版本，是本项目代码贡献者之一。。。
@nephen 不是 403 吗，怎么变 500 了，回到 403 的场景，试下加这一行代码看下会不会 200 req.Header.Set("Cookie", "cf_clearance=xxx; _cfuvid=xxx;")，值从官方网站拿，有点怀疑和这个有关，有另外的人也是一直 403

更新到最新的是出现500错误了
我用最新的打标签的那个旧版本cpu是正常的，如果再老一点是有可能cpu一直高的，因为没有做异常退出处理

看，我本地裸跑无论如何都是正常的，代码也是最新的，也无未提交的改动
这个 403 目前我无法测试，因为没遇到，所以可能 403 的同学先用回旧版
或者方便的话提供一下你们目前用的网络代理供我测试一下（不确定是否有关），或者有条件的可以自行调试
https://user-images.githubusercontent.com/49076004/235468576-2e79c145-ae90-4097-ba19-8d1f5cdda6c4.mp4

遇到奇怪的问题，微软azure服务器，curl检测和实际节点都可以访问openai。使用单独新镜像，只有一个容器提供反代服务接口，az200试用账号开的机器，可以成功访问，偶尔报403或者429；使用教育账号开的az服务器和RN小鸡，报错500.完全相同的配置文件：
version: "3"
services:
go-chatgpt-api:
container_name: go-chatgpt-api
image: linweiyuan/go-chatgpt-api
ports:
- 38080:8080
environment:
- GIN_MODE=release
- GO_CHATGPT_API_PROXY=
restart: unless-stopped
此外，给不能访问openai的小鸡套上了warp后，测试可以访问，使用上述方式，报错500。使用旧版正常，CPU占用飚满

我测试的时候，500 是 EOF，就是最近亚洲节点访问直接报错，像域名不存在的效果
你那么多服务器，有没有可能给一台我测试下

我测试的时候，500 是 EOF，就是最近亚洲节点访问直接报错，像域名不存在的效果
你那么多服务器，有没有可能给一台我测试下

我提供一台新加坡的机器给你测试

发你的微信到邮箱 root@linweiyuan.com，我加你

我用新版的镜像也有这个403的问题，昨天刚配置好的时候是ok的，但是今天就不行了，一直403，重新pull和restart都没用，换回老版镜像就好了。环境是AWS服务器+WARP

可能需要拿到debug里面403和200时候的http request看看区别在哪里

最新的版本正常了，没有403了，赞

最新的版本正常了，没有403了，赞

我也正在试用该版本：
[
    {
        "Id": "sha256:6b06c75ce544e2cb32f4382c0a41c577deafc86a81bd36c4312b7814e485bbcb",
        "RepoTags": [
            "linweiyuan/go-chatgpt-api:latest"
        ],
        "RepoDigests": [
            "linweiyuan/go-chatgpt-api@sha256:2fa1981dda573913dd8b1e82819fcb0e2ca49e65a158c8a10cb44341da31c897"
        ],
        "Parent": "",
        "Comment": "buildkit.dockerfile.v0",
        "Created": "2023-05-02T14:49:22.738522389Z",
        ...
    }
]

有什么意见再来反馈吧 (ฅ´ω`ฅ)

经过测试，总结了这么几个情况：

本地镜像+魔法，正常
本地二进制+魔法，正常
服务器上镜像+魔法，正常
服务器上二进制+魔法，正常
服务器上镜像+WARP，有时 403 但重试 200，有时一直 200
服务器上二进制+WARP，一直 403

目前来看，本地跑或者服务器上加魔法是最稳的，上了 warp 就会 403 （不上也会 403，但那个是 1020）
服务器 403 的时候输出的 IP 地址也是 Cloudflare 的地址，但少了个 cookie：_cfuvid
目前来看，问题出现在 warp 上，但是我并不熟这个东西，所以可能会尝试用一些奇怪的方法来修复
有兴趣可以找那些一键 warp 脚本试下好不好使，还没试过
相同 warp 镜像，旧版为什么可以，也不清楚

在新版本的 commit 中新增使用了新的Endpoint，
並在初始化時，設置每 10 分鐘 執行一次訪問Endpoint，拿出 __cf_bm。
而後在原先的 healthCheck 中新增了 injectCookies 來設置 __cf_bm  Cookies。
想請問是因為針對使用 WARP 代理轉發的用戶做的改動嗎？
程式邏輯中似乎沒有對未使用 WARP 用戶處理，會一直訪問 Endpoint。
有點怕作者的 Endpoint 被打壞  :hushed:

@Neillife 今天我在测试调整 10 分钟时间，比如 28 29，Cloudflare 官方说 30 分钟会过期，还没测好，每次测试要等半小时有点耗时间
没有针对 warp，测试中本地跑部分节点也会有 403，似乎和出口 IP 有关，这个时候通过该节点出去打开官网会触发验证码，启动 200 的就是没有验证码
不怕被打坏，设置了 rate limit，况且从日志看，也没太多请求过来，服务器流量每个月也用不完

@Neillife 今天我在测试调整 10 分钟时间，比如 28 29，Cloudflare 官方说 30 分钟会过期，还没测好，每次测试要等半小时有点耗时间
没有针对 warp，测试中本地跑部分节点也会有 403，似乎和出口 IP 有关，这个时候通过该节点出去打开官网会触发验证码，启动 200 的就是没有验证码
不怕被打坏，设置了 rate limit，况且从日志看，也没太多请求过来，服务器流量每个月也用不完

感覺還是跟有沒有被牆有關...
因為自己本身沒有牆不牆的問題，所以關於牆不牆的問題，不太清楚有沒有關係。 😯
但是自己的 windows 不用 docker 跑代理的 server 放到現在只遇過一兩次 403 而已
不管是舊版用 chromedriver ，和新版不用 chromedriver 的版本，都很穩定。

@FastSchnell 不是，普通账户即可

Hi~ @linweiyuan
有些問題想請問一下，有點不太明白訪問端點後，拿到 __cf_bm 設定 cookie 的用意是什麼?
看了一下官方文檔，似乎是說掛上這個 cookie 後，訪問有受到 Cloudflare 機器人認證的網站不會觸發認證。 (如果我理解正確的話)
是因為用戶在使用代理訪問 openai  403 觸發認證的關係才使用 __cf_bm  cookie 的嗎?
謝謝你為 ChatGPT 社群保持活力 :upside_down_face:

差不多是这样
不设置 __cf_bm 的话，部分节点会 403，而给本来就是 200 的节点设置上，也不会有额外影响

emm...latest方案对我来说又不太有效了。 还是不得不回退到旧的版本。
顺便一提，linweiyuan/go-chatgpt-api:legacy的最新版与最初的版本是不一样的。 现在的版本会导致服务器CPU爆满。
我现在使用的是自建的旧版。 难受 Σ( ° △ °|||)︴

emm...latest方案对我来说又不太有效了。 还是不得不回退到旧的版本。
顺便一提，linweiyuan/go-chatgpt-api:legacy的最新版与最初的版本是不一样的。 现在的版本会导致服务器CPU爆满。
我现在使用的是自建的旧版。 难受 Σ( ° △ °|||)︴

自建的是基于哪个commit的？

https://github.com/linweiyuan/go-chatgpt-api/issues/108#issuecomment-1537442756

@nephen
我使用的是 https://github.com/linweiyuan/go-chatgpt-api/tree/2a7b38e39dd8635c6961a6346c56ced2e7539d63 。 不过，旧的镜像似乎也不太管用了。 我在想是不是openai的验证机制发生了变化，导致原有的项目不生效了。
我的应用场景是go-chatgpt-api + WARP，美国西部的RackNerd VPS。 403错误在重启go-chatgpt-api后偶尔可解决，但很快会重新出现。

@huangwb8

@huangwb8 我使用的https://github.com/linweiyuan/go-chatgpt-api/tree/e13ed26021f74d0c7e6779c50f78c4898e3f81d2，目前跑了很长时间了，一直正常，我的前端页面是https://dyhlyb.com/chat

@nephen
https://github.com/linweiyuan/go-chatgpt-api/tree/2a7b38e39dd8635c6961a6346c56ced2e7539d63  暂时似乎是正常的。 旧版本还是稳。 新版本一直是不稳的，哎，难受 (ฅ´ω`ฅ)

@nephen
https://github.com/linweiyuan/go-chatgpt-api/tree/2a7b38e39dd8635c6961a6346c56ced2e7539d63 暂时似乎是正常的。 旧版本还是稳。 新版本一直是不稳的，哎，难受 (ฅ´ω`ฅ)

请问下这个版本的docker image是哪个？是legacy？还是别的？

@nephen
https://github.com/linweiyuan/go-chatgpt-api/tree/2a7b38e39dd8635c6961a6346c56ced2e7539d63 暂时似乎是正常的。 旧版本还是稳。 新版本一直是不稳的，哎，难受 (ฅ´ω`ฅ)

请问下这个版本的docker image是哪个？是legacy？还是别的？

go-chatgpt-api的新版本一直不稳定，“频繁出现服务器拒绝访问，请稍后再试 ”的bug一直存在。 推荐大家使用的旧版本 （ddsderek/go-chatgpt-api）过渡，需要chatgpt-proxy-server，路由是旧的/conversation。长期保留旧版本教程。详见“（旧版本）Access Token自建ChatGPT”小节。
我请小伙伴在不久前搞的镜像。但没想到还能用上 (ฅ´ω`ฅ)

authors: AKGO47 Beckjiang Neillife aldington-david dqzboy fsyllkn huangwb8 linweiyuan nephen njukiller

repo: linweiyuan/go-chatgpt-api


text:
Multiple MarkerIcon style impossible

When adding different markers, I only have one style, that of the first marker added.
Example to reproduce :
for(final GeoPoint geoPoint in geoPoints) {
  mapController.addMarker(
    geoPoint,
    markerIcon: MarkerIcon(
      icon: Icon(
        Icons.person_pin_circle,
        color: Random().nextInt(2) == 0 ? Colors.blue : Colors.red,
        size: 56,
      ),
    ),
  );
}

=> Add blue and red markers to mapController, but render only one style (same problem with size / using AssetMarker ...).
Reproduce on Android and iOS (no idea on Web) on the last version (0.60.4).

Keyword await is missing => then it work, but there are performance issues for 50 markers => response in that discussion : use static position.
I will try, and then close if OK :).

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
在列表想要快速起播，列表页只保持一个播放器实例，切换视频的时候只是替换Url

**需求描述
在列表想要快速起播，列表页之保持一个播放器实例，切换视频的时候只是替换Url
**其他app是否实现
抖音，火山
**截图或者小视频说明
能快速起播

滑动列表的时候自动播放屏幕中间的视频，是不是这个功能

repo: lipangit/JiaoZiVideoPlayer

license: mit

license_source: bigquery


text:
支持哪些视频格式

除了MP4，能支持其他格式的吗？比如avi

https://ffmpeg.org/ffmpeg-formats.html
这里有的都支持

authors: SCNUPeiFeng lipangit

repo: lipangit/JieCaoVideoPlayer


text:
预训练模型的vocab.txt提供错误?

想要用pre-trained模型重新训练时，出现:
RuntimeError: Error(s) in loading state_dict for BIGLM:
size mismatch for tok_embed.weight: copying a param with shape torch.Size([28781, 768]) from checkpoint, the shape in current model is torch.Size([6410, 768]).
的错误，个人推测似乎是vocab.txt上传到songci的版本，想请问怎么处理?

後來發現是要替換./data中的vocab.txt

repo: lipiji/SongNet


text:
DAT-9461 local PR test

DAT-9461 local PR test

Environment
Liquibase Version:
Liquibase Integration & Version: <Pick one: CLI, maven, gradle, spring boot, servlet, etc.>
Liquibase Extension(s) & Version:
Database Vendor & Version:
Operating System Type & Version:
Pull Request Type

[ ] Bug fix (non-breaking change which fixes an issue.)
[ ] Enhancement/New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
A clear and concise description of the issue being addressed.  Additional guidance here.

Describe the actual problematic behavior.
Ensure private information is redacted.

Steps To Reproduce
List the steps to reproduce the behavior.

Please be precise and ensure private information is redacted
Include things like

Files used - sql scripts, changelog file(s), property file(s), config files, POM Files
Exact commands used - CLI, maven, gradle, spring boot, servlet, etc.

Actual Behavior
A clear and concise description of what happens in the software before this pull request.

Include console output if relevant
Include log files if available.

Expected/Desired Behavior
A clear and concise description of what happens in the software after this pull request.
Screenshots (if appropriate)
If applicable, add screenshots to help explain your problem.
Additional Context
Add any other context about the problem here.
Fast Track PR Acceptance Checklist:

[ ] Build is successful and all new and existing tests pass
[ ] Added Unit Test(s)
[ ] Added Integration Test(s)
[ ] Added Test Harness Test(s)
[ ] Documentation Updated

Need Help?
Come chat with us on our discord channel

not needed anymore. just for testing build triggers

source: gharchive/pull-request

repo: liquibase/liquibase


text:
Allow multi-line rollback statements in formatted sql changefile.

Currently, it is awkward to have a long block of rollback sql code in a formatted sql changelog file.

It appears that liquibase does support multiline rollbacks, but you have to prefix each line with --rollback.
--changeset me:1

CREATE TABLE bar (
        id INTEGER PRIMARY KEY,
        name TEXT
);

--rollback DROP TABLE
--rollback bar;

@weters : where did you find that?
That isn't working for me and I found this jira: https://liquibase.jira.com/browse/CORE-1984
So it seems it isn't supported yet, can anyone confirm if this will be added in the future?

@jcfandino  - Liquibase supports multiline rollbacks, but it doesn't support disabling splitStatements for your rollback SQL.
This is supported:
--rollback DROP TABLE
--rollback foo;

This is not supported yet (because liquibase will split the statements on every semicolon):
--rollback CREATE OR REPLACE FUNCTION foo() RETURNS bool
--rollback LANGUAGE plpgsql
--rollback AS $$
--rollback BEGIN
--rollback   RETURN true;
--rollback END;
--rollback $$;

Thanks @weters for the response.
I was getting the same error as the jira bug when using the maven plugin, but I tested it again today and it's working as expected.
It must have been another problem then.
Thanks, this is much better now!

Fun fact: I just added support splitting rollback statements for the upcoming 3.5.2 release. Just add rollbackSplitStatements:true|false and/or rollbackEndDelimiter:/ to your --changeset header

@nvoxland rollbackSplitStatements:false saved my life. I was in CREATE OR REPLACE FUNCTION hell just now.

@pmendelson Do you still plan to support multiline rollback without having lots of "--rollback"s? Brief scan of your initial commit seems to resemble something like what I'd want, curious to know why you reverted those commits after.

placing rollback sql in comment while it's multi-line or not just is ugly and no syntax highlighting from the IDE, can't we just use --rollback to mark the start of the rollback and place the rollback sql(s) on the next line like a regular migrations?
-- rollback
DROP TABLE foo;
delete from bar where 1=1;

I'm not sure why this PR has a commit that was then rolled back, but I believe I have a simpler solution to this: https://github.com/liquibase/liquibase/pull/695

Hi @nvoxland, apart from your comment, is there any documentation on multi-line rollback statements, preferably with an example?  Is #695 even being considered? Thanks!

I believe the reason to leave rollback statements as part of a comment would be for cases when we need to send the entire sql formatted changefile to an external team who has no idea what liquibase is. They won't run the .sql using liquibase, instead they are used to their green phosphor terminal where they will copy&paste the script without a clue on what it's doing. Believe me, there is still people like that, even working as DBAs. Better safe than sorry.

@holandaleo i would consider that an edge case, most don't have such a use case and we shouldn't build tools to solve 5% uses cases

I agree it would be 5% of the cases for liquibase users, but not 5% of the users who adopted the .sql format. I, personally, don't even like the .Sql format for liquibase. But, from what I've seen out there, is that teams who make the choice to adopt the .sql format, the most common reason for the choice is do that they can copy and paste fragments of the file to a sql terminal. In the other hand I'm still partially on your side that this is a bad practice and the tool design should discourage bad practices. However:

Current behavior of the .sql format is to have rollback statements within comments. Future solutions should be backward compatible and still allow rollback blocks entirely in comments despite accepting statements below the comment line making the beginning of the block
Leave 5% of the cases out of the solution is not a good argument. Liquibase is a great tool and very popular so that 5% of a lot is still a lot. The goal should be robustness and achieve 100% cases covered.

@holandaleo if you check out #695 I implemented this with backwards compatibility - you can use --rollback for single line, but --changesetrollback for multiline. So those who want .sql and copy and paste can use the existing --rollback system, and those who want .sql but multiline rollback can use --changesetrollback as well.

@holandaleo @Saravanan21 Bear with me - I'm new to liquibase and I find both of your arguments have merit.  Would it make sense to support multi-line rollbacks inside the standard delimiters for multi-line comments?
/* rollback
  DROP TABLE foo;
  delete from bar where 1=1;
*/

@jcrand it has some cons, for example it just means that for tools we write in, it will be harder to understand this syntax and provide you with feedback and check the syntax. Tools will have to add support for it. The comment delimiter works great -- rollback because it does not cause such issues the tools which don't support it will treat it as a comment while still providing autocompletion and syntax checking for the SQL that follows.
@holandaleo the 5% was just a pick from the top of my head, i don't think any of us have any numbers to support it, i just have a hunch that its a rare case. Haven't encountered any at least, so i'm not willing to bet on it.

i agree partly, major versions can introduce breaking changes to move forward
safeguard from what? that also means that tools like mentioned before, IDEs, editors for example will not provide us with assistance to write it in the first place. I hope we want better developer experience than that.
Again fictional numbers, but it's a good practice to follow 80/20 rule (Pareto principle), to reduce bloat and we can't accommodate everyone's needs, so 100% is unachievable. The only real way to measure this would be to do a survey or add anonymous usage stats to liquibase

i personally would be for #695 seems like best of both worlds

My team was just talking about needing a feature like #695 and I suspect our use case isn't uncommon. We need to add rollback scripts for stored procedures, views, and functions that may span hundreds of lines. Adding -- rollback before each line is technically possible but seems unnecessary and really ruins the developer experience. I believe syntax introduced by #695 would be a really good addition.

The problem with the style of rollback in #695 @ghunteranderson is that it breaks the ability to execute the SQL script directly without it executing the DDL/DML and ALSO the rollback. Something like /* */ style multi-line comments would be best and not break backwards compat with executing the SQL scripts directly

@Trii I agree we probably don't want to break that if people are using it. Two quick thoughts.

Often times (with MySQL at least) we cannot execute the files directly on the server anyways because of limitations around how the DELIMITER syntax is handled. (Perhaps a separate issue that needs addressing)
The --rollback syntax allows users to keep writing rollbacks as commented out sql but the new --changesetRollback would give users the option for cleaner syntax with the trade off of not being able to execute the file directly on the server any more. How do we feel about providing the option?

One last after thought. I'm not sure if I understand the use case of running change logs directly on the server especially with features like the updateSql command that is intended to generate the SQL that needs to be ran on the server. That being said, I also have a pretty narrow view of how people use Liquibase in the wild.

I'm not a maintainer of the project @ghunteranderson, just a user, but I execute the SQL files directly via psql during development on my locally running instance to make sure they are correct. I think the solution described by @jcrand https://github.com/liquibase/liquibase/pull/334#issuecomment-493499838 would be a nice compromise.

@Trii The solution here https://github.com/liquibase/liquibase/pull/334#issuecomment-493499838 isn't my first pick but I could see it being a good compromise. It offers simpler syntax (compared to prefixing every line of the rollback) and a smaller set of keywords to remember the difference between.

Hi
I am new to liquibase and we are using "sql formatted liquibase". I am trying to figure out a way to rollback stored procs.
I have got a multi line rollback working by prefixing each line of the old stored proc with the string "--rollback"
Example -

--liquibase formatted sql
--changeset authorname:ID_2 endDelimiter:/ rollbackEndDelimiter:/
Create or replace procedure test_proc is
.........new version of proc code
.........................
end;
/
--rollback Create or replace procedure test_proc is
--rollback .........old version of proc code
--rollback .........................
--rollback end;
--rollback /

But this requires developers to continually keep cutting and pasting old code and then manually adding the string --rollback to every line.
From the sparse documentation at the datical site, it seems i can use the changeSetId property to refer to an older changeset to rollback too ....That would make it really easy and readable. for example if the old change set ID is authorname:ID_1 I will have to write the new change set as below -

--liquibase formatted sql
--changeset authorname:ID_2 endDelimiter:/ rollbackEndDelimiter:/
Create or replace procedure test_proc is
.........new version of proc code
.........................
end;
/
--rollback changeSetId authorname:ID_2

Thing is - I don't know what the exact syntax is to specify a changeset to rollback to using sql formatted liquibase file. I could not find any example or any documentation. Is this even possible using sql formatted Liquibase ?
I know that in XML it is supposed to work as below -

 ......
 ....

Hi @pmendelson , thanks for the PR!  and tests!  I will pair this with #695 and let Eng decide which way to go.
Sized at Med for that effort.

While re-reading the comments on this issue a different approach occurred to me. The rollback statements for a changeset could be stored in a separate file. This would make executing the rollback statements by accident when you only wanted to run the changeset much less likely.
One way to tie them together would be to add a "rollbackFile" attribute to the change log's "include" element, perhaps paired with a --rollbackFile comment in the changeset itself.

We ended up switching to XML instead of SQL formatted changelogs.
We used inline rollback for DDL statements and an external .sql file for
rolling back stored procedures.
See examples below
DDL rollback

    <changeSet author="<YOURNAME>" id="1">
        <sql>
           create table <INITIALS>_liq_test_wrk (wrk_id number(11),

wrk_ttl varchar2(100),  title_length number(3));
create index _liq_test_wrk_ix1 on
liq_test_wrk(wrk_id);

drop table _liq_test_wrk;

Procedural code roll back
The first changeset in the example below creates the stored proc - so the
roll back is inline with
the changelog file. The second changeset alters the stored proc and the
roll back refers to an
external .sql file that contains the previous code. The .sql file is
versioned V1, V2, V3 etc

    <changeSet author="<YOURNAME>" id="1">
        <sqlFile endDelimiter="\"
                path="/code/liq_test_set_ttllen-V1.sql"
                relativeToChangelogFile="true"
                splitStatements="true"/>
        <rollback>
            drop procedure <INITIALS>_liq_test_set_ttllen
        </rollback>
    </changeSet>
    <changeSet author="<YOURNAME>" id="2">
        <sqlFile endDelimiter="\"
                path="/code/liq_test_set_ttllen-V2.sql"
                relativeToChangelogFile="true"
                splitStatements="true"/>
        <rollback changeSetAuthor="<YOURNAME>" changeSetId="1" />
    </changeSet>

Hitendra Sahay
Principal Engineer (Data Enginering)
Global Technology Solutions (GTS)
ASCAP, NY
212-621-6358 (W)
848-219-2756 (Cell)
ASCAP100.com http://ascap100.com/
[image: http://www.youtube.com/watch?v=oANP3WV4bnE]
http://www.youtube.com/watch?v=oANP3WV4bnE
Discover why our members create music: Watch the film
http://www.youtube.com/watch?v=oANP3WV4bnE
On Fri, May 15, 2020 at 3:11 PM jcrand notifications@github.com wrote:

While re-reading the comments on this issue a different approach occurred
to me. The rollback statements for a changeset could be stored in a
separate file. This would make executing the rollback statements by
accident when you only wanted to run the changeset much less likely.
One way to tie them together would be to add a "rollbackFile" attribute to
the change log's "include" element, perhaps paired with a --rollbackFile
comment in the changeset itself.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/liquibase/liquibase/pull/334#issuecomment-629429451,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALKXWZG6AW7LMZ4KSIMKPFLRRWHU7ANCNFSM4AYK2KOQ
.

--
This e-mail and any files or data transmitted with it are confidential
and intended solely for the use of the individual named above. If you have
received this email in error and are not the intended recipient, please
notify the sender by e-mail and immediately delete the message and all
materials without reading them.  If you are not the intended recipient,
copying, forwarding or otherwise disseminating or distributing this
information is prohibited.

We need to come up with a combined version of this PR at #695. I haven't gotten a chance to look at them in depth yet, but will soon.

Part of what we've been thinking about internally is how "real" sql formatted sql should be.
My original goal was that the formatted sql file should be executable outside of liquibase through normal database tools, but they would just not do liquibase-specific things. Basically you could still copy/paste the contents into any sql editor and run it and it will still make your changes correctly, even though it wouldn't track them in the databasechangelog table.
That's why the --changeSet delimiter etc. are sql comments.
But, as people actually use the formatted sql format, does that original intention make sense? Is it a useful goal to stick too? Or get in the way?
A big part of the reason why I hadn't taken this PR in earlier was trying to find a balance between "still valid sql" and something usable. It's a pain to prepend --rollback before every line of the rollback logic, but if we don't do that, then copy/pasting the file into an sql editor will run both the update and the rollback sql.
We're starting to hit the quesiton in other issues as well, like #843 .
So, question to everyone:
What are you're thoughts on how useful that ability to have formatted sql be "normally runnable" is?

It's been a long time since I've had to use liquibase, but I've been following the conversation. To me this is an important, but niche use case to support. What do you think about adding an attribute to --changeset that would allow you to specify an external file for the rollback?
Using an example from the docs:
--liquibase formatted sql

--changeset nvoxland:1  rollbackFile:nvoxland_1_rollback.sql
create  table  test1  (
    id  int  primary  key,
    name  varchar(255)
);

--changeset nvoxland:2
insert  into  test1  (id,  name)  values  (1,  ‘name  1′);
insert  into  test1  (id,  name)  values  (2,  ‘name  2′);

--changeset nvoxland:3 dbms:oracle
create  sequence  seq_test;

file: nvoxland_1_rollback.sql
--liquibase formatted sql
drop table test1;

Agree with Josh.
The below two features in XML formatted changeset, if implemented for SQL
formatted also would fix the problem for most of us

The ability to store SQL in external files. So changeset for
procedural code refers to an external file, that can be versioned V1.sql,
V2.sql etc (corresponding to changesetID1, changesetID2 respectively) and

In rollback use a reference to the prior changeset to rollback to

Hitendra Sahay
Principal Engineer (Data Enginering)
Global Technology Solutions (GTS)
ASCAP, NY
212-621-6358 (W)
848-219-2756 (Cell)
ASCAP100.com http://ascap100.com/
[image: http://www.youtube.com/watch?v=oANP3WV4bnE]
http://www.youtube.com/watch?v=oANP3WV4bnE
Discover why our members create music: Watch the film
http://www.youtube.com/watch?v=oANP3WV4bnE
On Wed, May 27, 2020 at 2:45 PM Josh Johnston notifications@github.com
wrote:

It's been a long time since I've had to use liquibase, but I've been
following the conversation. To me this is an important, but niche use case
to support. What do you think about adding an attribute to --changeset
that would allow you to specify an external file for the rollback?
Using an example from the docs:
--liquibase formatted sql
--changeset nvoxland:1  rollbackFile:nvoxland_1_rollback.sql
create  table  test1  (
id  int  primary  key,

name  varchar(255)

);
--changeset nvoxland:2
insert  into  test1  (id,  name)  values  (1,  ‘name  1′);
insert  into  test1  (id,  name)  values  (2,  ‘name  2′);
--changeset nvoxland:3 dbms:oracle
create  sequence  seq_test;
file: nvoxland_1_rollback.sql
--liquibase formatted sql
drop table test1;
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/liquibase/liquibase/pull/334#issuecomment-634866002,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALKXWZCGLZOK7CCEFKP7WZLRTVNTFANCNFSM4AYK2KOQ
.

--
This e-mail and any files or data transmitted with it are confidential
and intended solely for the use of the individual named above. If you have
received this email in error and are not the intended recipient, please
notify the sender by e-mail and immediately delete the message and all
materials without reading them.  If you are not the intended recipient,
copying, forwarding or otherwise disseminating or distributing this
information is prohibited.

We have not forgotten you!! We promise! Thankfully we have just been able to put a few more resources into the open source project and I am going back through some of the past issues - for folks on this thread, since it has been a while, please if you have time note if this is still an issue for you and if you have any new input/thoughts/etc on the topic. Thanks!!!

Is there an ETA for the rollout please?

Not sure if this thread is still active, But I found the below works fine for me (both update & rollback commands works fine)
-- liquibase formatted sql
-- changeset csidevops:20220818-005 rollbackSplitStatements:false rollbackEndDelimiter:/
BEGIN
EXECUTE IMMEDIATE 'DROP TABLE CUSTOMER_MASTER_DATA_BACKUP';
EXCEPTION
WHEN OTHERS THEN
IF SQLCODE != -942 THEN
RAISE;
END IF;
END;
--rollback BEGIN
--rollback     EXECUTE IMMEDIATE 'DROP TABLE CUSTOMER_MASTER_DATA_BACKUP';
--rollback  EXCEPTION
--rollback      WHEN OTHERS THEN
--rollback         IF SQLCODE != -942 THEN
--rollback           RAISE;
--rollback         END IF;
--rollback END;
/

Hello @pmendelson et al , thanks for the contribution Currently we have 3 PR's to handle the same problem using slightly different approaches: #334, #695 and #1399 . After reviewing the PRs, the comments and the way Liquibase works we want to go ahead with PR #1399 . So we will close this one and will centralize the discussion there.

Duplicates #1399

authors: Gamesh Saravanan21 Trii csidevops fellipecm filipelautert ghunteranderson hello-josh holandaleo hsahay1970 jcfandino jcrand jmeterNew kataggart nvoxland pmendelson pronoyroy ro-rah weters


text:
Zachmu/drop table 2

Drop and create table

Daylon, I merged this so that the dolt PR that relies on it can build. Please give this a look and suggest any changes you have in mind.

repo: liquidata-inc/go-mysql-server


text:
No updates are available for Kaggle dataset regarding the number of COVID-19 cases

What we need to document?
CovsirPhy has two data sources, but no updates are available for one dataset recommended in the documentation. We need to revise the documentation to inform users.
Details
CovsirPhy has two data sources as explained in the following documentation.
https://lisphilar.github.io/covid19-sir/INSTALLATION.html

Kaggle dataset
In the early stage, CovsirPhy was developed using this dataset. Many thanks for SRK, the author!!
However, this dataset has not been updated since 24Sep2020. This leads improper simulation USA, Greece etc.
https://www.kaggle.com/sudalairajkumar/novel-corona-virus-2019-dataset/metadata

COVID-19 Data Hub
We can download this dataset with covsirphy.DataLoader() class. We need to use this dataset for our analysis. Analysis with Italy records is shown in the following documentation.
https://lisphilar.github.io/covid19-sir/usage_quickest.html

Acknowledgement
Thank you for your suggestion, @Inglezos !

Dear @Inglezos,
The codes to download the dataset of COVID-19 Data Hub is as follows.
import covsirphy as cs
# Dataset preparation
data_loader = cs.DataLoader("input")
jhu_data = data_loader.jhu()
population_data = data_loader.population()
```

With these lines of code, the updated dataset of the "covid19datahub" team is downloaded and used, getting data from the JHU CSSE system.
The system should use directly and always as primary data source the "covid19datahub.io" source. Therefore, your kaggle notebook should be adjusted to reflect only this data source.

The kaggle notebook was updated to use COVID-19 Data Hub as the data source.
Thank you!

authors: Inglezos lisphilar


text:
[docs] Add info on automatic XSS-prevention / escaped characters

Description
In this article, it mentions that 'lit-html' includes XSS-prevention. That's what lead me to this library.
https://benfrain.com/html-templating-with-vanilla-javascript-es2015-template-literals/
Naturally, I wanted to verify that before using lit-html so I searched for 'escape' and 'XSS' in the documentation, but I wasn't able to find any mention of that functionality anywhere.
By trial and error, I found out that lit-html automatically removes  tags when using the html tagged template literal.
I also could not find info about the unsafeHTML directive in the docs although it is included in the source code.

lit-html works by building a DOM tree, so injection of whole script elements is not an issue, but there are others.
The known XSS risks are:

attacker controls value for the unsafeHTML directive; the string <img src=bogus onerror=alert(document.origin)> can inject code even though straightforward <script> injection fails.
attacker controls text in sensitive locations: html`<script>${ x }</script>`
attacker controls values for sensitive attributes like html`<iframe srcdoc=${ x }>`  or html`<script src=${ x }></script>`
attacker controls values assigned to sensitive properties like html`<div .innerHTML=${ x }>`
attacker controls string that reaches event handlers like html`<button @onclick=${ x }>`
attacker controls CSS which in other contexts has leaked information about page content.

The team is aware of those risks and is working on addressing them.

On diving deeper, it turns out html`<button @onclick=${ x }>`  is not problematic.
Will edit my summary.

Is there any official documentation on the security/threat model of lit-html? I feel this is very important information and would be very useful to include as a section on the official website: https://lit-html.polymer-project.org

What's the status of this?

@lastmjs https://github.com/Polymer/polymer-resin#readme captures my threat modelling when I wrote resin.  I don't speak for the Polymer project though.

authors: interactiveRob lastmjs leonheess mikesamuel

repo: lit/lit


text:
[ssr] Cast setAttribute values to string in SSR DOM shim

Previously, when our SSR DOM shim for setAttribute received a value, it just assumed it was a string and assigned it to its internal attribute map as-is. Later, when trying to serialize an attribute to HTML, we pass it through an escape function, which crashes if the value is not a string.
In browsers, the value passed to setAttribute is always cast to a string. So 42 becomes "42". We now mirror this behavior.
This specifically came up in https://github.com/lit/lit/issues/2633 because in ReactiveElement, when a property has {type: Number}, we do not cast the value to a string ourselves, since we assume the browser will do that automatically (in fact, we don't handle Number at all, since the default behavior is correct https://github.com/lit/lit/blob/21ff05104727d088ab577f7178cbc15eed14841a/packages/reactive-element/src/reactive-element.ts#L321).
Fixes https://github.com/lit/lit/issues/2633
cc @daKmoR

@justinfagnani @augustjk this is ready for review


text:
Is key update initiation implemented?

Hi,
I was playing with the example http3 client and server, and transferring some data between them. According to the log, interestingly I found that the key phase didn't change during the connection and hence no key update happened. Then I checked the lsquic_enc_sess_ietf.c and found that there seems to be no key update initiated there (looks like it's able to respond to a key update initiated by the peer, but just won't initiate one by itself). Just wanted to confirm, is the key update implemented in the current version? If not may I get any brief advice on how to initiate a key update?
Any advice and thoughts will be appreciated,
Thanks

It looks like the key udpate would be triggered if the packet number reaches the threshold set by IQUIC_INVALID_PACKNO (lsquic_packet_common.h:190) which seems to be consistent with the usage limit of AEAD_CHACHA20_POLY1305 defined by rfc9001. One question here is why use limit of chacha20 rather than other ciphers? (some other ciphers have smaller usage limit)
Another question I had here is, it looks like the key update won't be initiated even if the packet number reaches that secure limit, please refer to this code block taken from lsquic_enc_sess_ietf.c:2226:
  key_phase = (dst[0] & 0x04) > 0;
  pair = &enc_sess->esi_pairs[ key_phase ];
  if (key_phase == enc_sess->esi_key_phase)
  {
      crypto_ctx = &pair->ykp_ctx[ 0 ];
      /* Checked by header_prot_inited() above */
      assert(crypto_ctx->yk_flags & YK_INITED);
  }
  else if (!is_valid_packno(
                  enc_sess->esi_pairs[enc_sess->esi_key_phase].ykp_thresh)
          || packet_in->pi_packno
              > enc_sess->esi_pairs[enc_sess->esi_key_phase].ykp_thresh)
  {
      const struct ku_label kl = select_ku_label(enc_sess);
      lsquic_qhkdf_expand(enc_sess->esi_md,
          enc_sess->esi_traffic_secrets[0], enc_sess->esi_trasec_sz,
          kl.str, kl.len, new_secret, enc_sess->esi_trasec_sz);
      if (enc_sess->esi_flags & ESI_LOG_SECRETS)
          LSQ_DEBUG("key phase changed to %u, will try decrypting using "
              "new secret %s", key_phase, HEXSTR(new_secret,
              enc_sess->esi_trasec_sz, secret_str));
      else
          LSQ_DEBUG("key phase changed to %u, will try decrypting using "
              "new secret", key_phase);
      crypto_ctx = &crypto_ctx_buf;
      crypto_ctx->yk_flags = 0;
      s = init_crypto_ctx(crypto_ctx, enc_sess->esi_md,
                  enc_sess->esi_aead, new_secret, enc_sess->esi_trasec_sz,
                  evp_aead_open);
      if (s != 0)
      {
          LSQ_ERROR("could not init open crypto ctx (key phase)");
          dec_packin = DECPI_BADCRYPT;
          goto err;
      }
  }
  else
  {
      crypto_ctx = &pair->ykp_ctx[ 0 ];
      if (UNLIKELY(0 == (crypto_ctx->yk_flags & YK_INITED)))
      {
          LSQ_DEBUG("supposedly older context is not initialized (key "
              "phase: %u)", key_phase);
          dec_packin = DECPI_BADCRYPT;
          goto err;
      }
  }

It seems that, the second branch ("else if") will never be reached as long as the peer doesn't change the key phase, even if the packet number exceeds the threshold (when a key update is needed). Although the threshold is too large to be exceeded often, but is it a potential bug or is there a reason to do so? Any explanation would be appreciated.

You are right, lsquic does not implement initiating key rotation, just follow peer's key rotation.

That explains a lot - thank you very much!

authors: litespeedtech maruibin

repo: litespeedtech/lsquic


text:
Enhancement: allow CompressionMiddleware to use custom implementations of CompressionFacade

Summary
With the current implementation of compression, it's limited to whatever is supported by Litestar i.e. gzip and brotli. If others want to use a different compression, they have to create a middleware of their own for handling that, but that results in issues if they are also caching the response. The caching of the compressed responses is handled properly when using the built in CompressionMiddleware, but if users are implementing their own they'll have to handle it properly as well. For example, see here.
To work around this and allow users to use a different compression (one that is supported out of the box), I'm proposing that we allow the passing of a type that implements the CompressionFacade to the CompressionConfig. Then the middleware would use this to get the compressed body as well as the value for the Content-Encoding header. Essentially, the CompressionFacade would become a CompressionProtocol (though we might have to keep the same name in order to maintain compatibility).
Basic Example
No response
Drawbacks and Impact
No response
Unresolved questions
No response

[!NOTE]
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh Litestar dashboard

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified
This, along with engagement in the community, helps us know which features are a priority to our users.

Implemented in #2952. This will be included in the 2.6.0 release.

authors: guacs provinzkraut

repo: litestar-org/litestar


text:
fix: ensure PDM is available in the Makefile Path

Greetings to you!)
I made small changes to the Makefile by updating the PDM installation function, because without this it did not work normally and calling the Makefile ended with an error calling the newly installed PDM

@JacobCoffee

@JacobCoffee can you take a look at this one?

@ashm-tech based on what @JacobCoffee said as well, I think we're going to close this one. If you'd like to raise a PR to document that the PDM path might need to be added to PATH, that'd be much appreciated :)

authors: ashm-tech guacs provinzkraut


text:
fix: print warning if incorrect annotations for return_dto

Description
Print a warning during initialization if types do not match.
Due to the caching I think this is the only possibility where it's possible to do it.
self.app.logger is not available yet, so I used warnings.warn. For the latter, stacklevel is not the best, another option would be to use warnings.warn_explicit.
Closes
#3485

This isn't a bug, as DTOs can be defined on layers, and it would be quite restrictive to only allow routes beneath a layer that has a dto defined, to only return that DTO supported type. For example:
class MyController(Controller):
    return_dto = SomeDTO[SomeType]

    @get("/{id:int}")
    def get_handler(self) -> SomeType: ...

    @get("/")
    def list_handler(self) -> list[SomeType]: ...

    @delete("/{id:int}")
    def delete_handler(self) -> None: ...

In that example, the delete handler not returning a model instance shouldn't force the user to have to define the dto individually on all of the other handlers.
I can see some utility to raising an error if a dto is defined directly on a handler and that handler doesn't utilise it, but that implementation will look different to the one you have defined here. Also, it should consider the data parameter.

authors: peterschutt tibor-reiss


text:
Debug system instabilities

I want to use this project as a basis for running an application with Linux dependencies on Rocket.
First I tried getting https://github.com/tongchen126/Boot-Debian-On-Litex-Rocket project to run. I managed to boot to login and even successfully login a couple of times with both systemd and sysvinit but the majority of times it will just indeterministically hang at random points in or after the boot process (can be in either Kernel/systemd/sysvinit/after login).
Where the hangs after the kernel has started are far more common.
If the hang happens after the Kernel has started then the Kernel will usually still be active (it prints a message if the sdcard gets removed). In that case just the application (bash/systemd/sysvinit/other binaries) seems to become unresponsive.
Second I tried using the /bin/bash shell instead of systemd or sysvinit as they don't seem strictly necessary to run my application.
Here I encounter the same issue. Sometimes my application finishes successfully, sometimes it just randomly hangs (but kernel is still active). Especially on long program runs the probability that the application will hang is very high.
I did run into this issue last year as well when I was using an older version of the system for benchmarking purposes but I didn't have the time investigate this further (so I would just restart until I get a successfull run).
So first of all I was wondering if you @gsomlo encountered instabilities on your Rocket systems.
Second I was wondering if you have any pointers of things that I could look into.
Online I mostly found advice for deterministic hangs in Linux.
For reference I'm using the Arty board and the latest version of Litex.
I already tried different sdcards so I don't think that's an issue.
Additionally I tried using different power supplies.
I'll also try another FPGA when I get my hands on it.
Overall I'm leaning more towards that it's probably a software/gateware issue since BBL and the kernel rarely hang.

instructions on how to boot fedora with linux-on-litex-rocket have been added as part of commit b9b92a5bf79334f100ad808df7827f1f326307c1. Closing, please follow-up or re-open if any problems remain un-addressed.

authors: gsomlo troibe

repo: litex-hub/linux-on-litex-rocket


text:
true wafer

hej

Best waifu

authors: lithiumfluorine mellaninen

repo: lithiumfluorine/Lithiumbot


text:
Updated license to be a valid SPDX license

Solves npm warning "license should be a valid SPDX license expression"

thx

repo: litixsoft/karma-mocha-reporter


text:
Chore(image): update the base image to minimal scratch image for chaos-exporter

Signed-off-by: udit udit@chaosnative.com

Exporter Logs:
udit@ubuntu20 ~/g/s/g/l/chaos-exporter (scratch_dev)> kubectl logs -f chaos-exporter-74bdc88b64-z7vm4 -n litmus
W0903 08:22:05.963879       1 client_config.go:541] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2021-09-03T08:22:05Z" level=info msg="Beginning to serve on port :8080"
time="2021-09-03T08:22:05Z" level=info msg="Started creating Metrics"
time="2021-09-03T08:22:05Z" level=info msg="Registering Fixed Metrics"
time="2021-09-03T08:22:05Z" level=info msg="[Wait]: Hold on, no chaosengine found ... "
time="2021-09-03T08:23:15Z" level=info msg="The chaos metrics are as follows" AwaitedExperiments=0 StartTime=0 PassedExperiments=7 ResultNamespace=default EndTime=0 ChaosInjectTime=0 TotalDuration=0 ResultVerdict=Pass FailedExperiments=0 ProbeSuccessPercentage=100 ResultName=nginx-chaos-pod-delete

time="2021-09-03T08:23:16Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Pass ResultName=nginx-chaos-pod-delete ResultNamespace=default EndTime=0 ProbeSuccessPercentage=100 PassedExperiments=7 FailedExperiments=0 ChaosInjectTime=0 TotalDuration=0 StartTime=0 AwaitedExperiments=0

time="2021-09-03T08:23:17Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete StartTime=0 ChaosInjectTime=0 FailedExperiments=0 EndTime=0 ResultNamespace=default ProbeSuccessPercentage=100 PassedExperiments=7 ResultVerdict=Pass AwaitedExperiments=0 TotalDuration=0
time="2021-09-03T08:23:18Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete ResultNamespace=default ResultVerdict=Pass ProbeSuccessPercentage=100 AwaitedExperiments=0 TotalDuration=0 FailedExperiments=0 StartTime=0 EndTime=0 PassedExperiments=7 ChaosInjectTime=0

time="2021-09-03T08:23:19Z" level=info msg="The chaos metrics are as follows" TotalDuration=0 EndTime=0 AwaitedExperiments=0 ChaosInjectTime=0 ResultVerdict=Pass ResultName=nginx-chaos-pod-delete ResultNamespace=default ProbeSuccessPercentage=100 PassedExperiments=7 StartTime=1.630657398e+09 FailedExperiments=0

time="2021-09-03T08:23:20Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete AwaitedExperiments=0 ProbeSuccessPercentage=100 StartTime=1.630657398e+09 FailedExperiments=0 ResultNamespace=default EndTime=0 ChaosInjectTime=0 PassedExperiments=7 TotalDuration=0 ResultVerdict=Pass

time="2021-09-03T08:23:21Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default PassedExperiments=7 ChaosInjectTime=0 TotalDuration=0 ResultName=nginx-chaos-pod-delete StartTime=1.630657398e+09 ResultVerdict=Pass EndTime=0 ProbeSuccessPercentage=100 FailedExperiments=0 AwaitedExperiments=0

time="2021-09-03T08:23:22Z" level=info msg="The chaos metrics are as follows" StartTime=1.630657398e+09 PassedExperiments=7 TotalDuration=0 ResultNamespace=default FailedExperiments=0 ProbeSuccessPercentage=100 EndTime=0 AwaitedExperiments=0 ChaosInjectTime=0 ResultVerdict=Pass ResultName=nginx-chaos-pod-delete

time="2021-09-03T08:23:23Z" level=info msg="The chaos metrics are as follows" EndTime=0 FailedExperiments=0 ResultVerdict=Pass ProbeSuccessPercentage=100 StartTime=1.630657398e+09 PassedExperiments=7 ResultName=nginx-chaos-pod-delete ResultNamespace=default ChaosInjectTime=0 TotalDuration=0 AwaitedExperiments=0

time="2021-09-03T08:23:24Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=0 AwaitedExperiments=1 TotalDuration=0 EndTime=0 ChaosInjectTime=0 ResultNamespace=default ResultName=nginx-chaos-pod-delete PassedExperiments=7 FailedExperiments=0 StartTime=1.630657398e+09 ResultVerdict=Awaited

time="2021-09-03T08:23:25Z" level=info msg="The chaos metrics are as follows" ChaosInjectTime=0 ProbeSuccessPercentage=0 PassedExperiments=7 AwaitedExperiments=1 ResultNamespace=default TotalDuration=0 FailedExperiments=0 StartTime=1.630657398e+09 EndTime=0 ResultVerdict=Awaited ResultName=nginx-chaos-pod-delete
time="2021-09-03T08:23:26Z" level=info msg="The chaos metrics are as follows" TotalDuration=0 FailedExperiments=0 ResultName=nginx-chaos-pod-delete PassedExperiments=7 AwaitedExperiments=1 StartTime=1.630657398e+09 ProbeSuccessPercentage=0 ResultNamespace=default ChaosInjectTime=0 ResultVerdict=Awaited EndTime=0

time="2021-09-03T08:23:27Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete ResultNamespace=default StartTime=1.630657398e+09 AwaitedExperiments=1 PassedExperiments=7 EndTime=0 ChaosInjectTime=0 ProbeSuccessPercentage=0 TotalDuration=0 FailedExperiments=0 ResultVerdict=Awaited

time="2021-09-03T08:23:28Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Awaited ResultNamespace=default AwaitedExperiments=1 StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete PassedExperiments=7 ProbeSuccessPercentage=0 FailedExperiments=0 EndTime=0 ChaosInjectTime=0 TotalDuration=0

time="2021-09-03T08:23:29Z" level=info msg="The chaos metrics are as follows" ChaosInjectTime=0 TotalDuration=0 ProbeSuccessPercentage=0 AwaitedExperiments=1 ResultNamespace=default FailedExperiments=0 StartTime=1.630657398e+09 ResultVerdict=Awaited EndTime=0 ResultName=nginx-chaos-pod-delete PassedExperiments=7

time="2021-09-03T08:23:30Z" level=info msg="The chaos metrics are as follows" ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete FailedExperiments=0 ResultVerdict=Awaited ResultNamespace=default ProbeSuccessPercentage=0 AwaitedExperiments=1 EndTime=0 TotalDuration=0 PassedExperiments=7 StartTime=1.630657398e+09

time="2021-09-03T08:23:31Z" level=info msg="The chaos metrics are as follows" TotalDuration=0 ResultNamespace=default EndTime=0 PassedExperiments=7 AwaitedExperiments=1 ResultName=nginx-chaos-pod-delete FailedExperiments=0 ProbeSuccessPercentage=0 StartTime=1.630657398e+09 ResultVerdict=Awaited ChaosInjectTime=1630657410

time="2021-09-03T08:23:32Z" level=info msg="The chaos metrics are as follows" AwaitedExperiments=1 ResultNamespace=default ProbeSuccessPercentage=0 ResultVerdict=Awaited PassedExperiments=7 ChaosInjectTime=1630657410 FailedExperiments=0 StartTime=1.630657398e+09 TotalDuration=0 ResultName=nginx-chaos-pod-delete EndTime=0

time="2021-09-03T08:23:34Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=0 ResultNamespace=default FailedExperiments=0 AwaitedExperiments=1 StartTime=1.630657398e+09 ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete EndTime=0 TotalDuration=0 ResultVerdict=Awaited PassedExperiments=7

time="2021-09-03T08:23:35Z" level=info msg="The chaos metrics are as follows" ChaosInjectTime=1630657410 StartTime=1.630657398e+09 ResultVerdict=Awaited ResultName=nginx-chaos-pod-delete ResultNamespace=default AwaitedExperiments=1 FailedExperiments=0 TotalDuration=0 ProbeSuccessPercentage=0 EndTime=0 PassedExperiments=7

time="2021-09-03T08:23:36Z" level=info msg="The chaos metrics are as follows" FailedExperiments=0 AwaitedExperiments=1 ChaosInjectTime=1630657410 TotalDuration=0 PassedExperiments=7 ProbeSuccessPercentage=0 ResultName=nginx-chaos-pod-delete ResultVerdict=Awaited StartTime=1.630657398e+09 ResultNamespace=default EndTime=0

time="2021-09-03T08:23:37Z" level=info msg="The chaos metrics are as follows" ChaosInjectTime=1630657410 PassedExperiments=7 AwaitedExperiments=1 TotalDuration=0 FailedExperiments=0 ResultNamespace=default StartTime=1.630657398e+09 EndTime=0 ResultVerdict=Awaited ResultName=nginx-chaos-pod-delete ProbeSuccessPercentage=0
time="2021-09-03T08:23:38Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=0 TotalDuration=0 PassedExperiments=7 StartTime=1.630657398e+09 ResultVerdict=Awaited ResultNamespace=default FailedExperiments=0 AwaitedExperiments=1 EndTime=0 ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410

time="2021-09-03T08:23:39Z" level=info msg="The chaos metrics are as follows" EndTime=0 ResultVerdict=Awaited FailedExperiments=0 ResultNamespace=default PassedExperiments=7 ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410 ProbeSuccessPercentage=0 TotalDuration=0 StartTime=1.630657398e+09 AwaitedExperiments=1
time="2021-09-03T08:23:40Z" level=info msg="The chaos metrics are as follows" ChaosInjectTime=1630657410 TotalDuration=0 ResultName=nginx-chaos-pod-delete StartTime=1.630657398e+09 ResultNamespace=default PassedExperiments=7 ResultVerdict=Awaited FailedExperiments=0 ProbeSuccessPercentage=0 EndTime=0 AwaitedExperiments=1

time="2021-09-03T08:23:41Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete FailedExperiments=0 PassedExperiments=7 StartTime=1.630657398e+09 TotalDuration=0 ResultNamespace=default ProbeSuccessPercentage=0 ChaosInjectTime=1630657410 AwaitedExperiments=1 EndTime=0 ResultVerdict=Awaited

time="2021-09-03T08:23:42Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=0 FailedExperiments=0 EndTime=0 AwaitedExperiments=1 TotalDuration=0 ResultNamespace=default PassedExperiments=7 ChaosInjectTime=1630657410 ResultVerdict=Awaited ResultName=nginx-chaos-pod-delete StartTime=1.630657398e+09

time="2021-09-03T08:23:43Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default PassedExperiments=7 ProbeSuccessPercentage=0 StartTime=1.630657398e+09 FailedExperiments=0 AwaitedExperiments=1 TotalDuration=0 EndTime=0 ResultVerdict=Awaited ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410

time="2021-09-03T08:23:44Z" level=info msg="The chaos metrics are as follows" AwaitedExperiments=1 ResultNamespace=default PassedExperiments=7 TotalDuration=0 ResultName=nginx-chaos-pod-delete FailedExperiments=0 StartTime=1.630657398e+09 ResultVerdict=Awaited EndTime=0 ChaosInjectTime=1630657410 ProbeSuccessPercentage=0
time="2021-09-03T08:23:45Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=0 StartTime=1.630657398e+09 AwaitedExperiments=1 ResultName=nginx-chaos-pod-delete FailedExperiments=0 PassedExperiments=7 EndTime=0 ResultVerdict=Awaited ResultNamespace=default ChaosInjectTime=1630657410 TotalDuration=0

time="2021-09-03T08:23:46Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete AwaitedExperiments=1 ChaosInjectTime=1630657410 TotalDuration=0 ResultVerdict=Awaited FailedExperiments=0 PassedExperiments=7 EndTime=0 ResultNamespace=default ProbeSuccessPercentage=0 StartTime=1.630657398e+09

time="2021-09-03T08:23:47Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default FailedExperiments=0 StartTime=1.630657398e+09 ProbeSuccessPercentage=0 ResultVerdict=Awaited EndTime=0 ChaosInjectTime=1630657410 AwaitedExperiments=1 ResultName=nginx-chaos-pod-delete PassedExperiments=7 TotalDuration=0

time="2021-09-03T08:23:48Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default ProbeSuccessPercentage=0 TotalDuration=0 EndTime=0 ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410 StartTime=1.630657398e+09 ResultVerdict=Awaited FailedExperiments=0 AwaitedExperiments=1 PassedExperiments=7
time="2021-09-03T08:23:49Z" level=info msg="The chaos metrics are as follows" TotalDuration=0 ResultNamespace=default AwaitedExperiments=1 ProbeSuccessPercentage=0 EndTime=0 FailedExperiments=0 ResultVerdict=Awaited ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410 PassedExperiments=7 StartTime=1.630657398e+09

time="2021-09-03T08:23:51Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Awaited TotalDuration=0 ProbeSuccessPercentage=0 EndTime=0 ChaosInjectTime=1630657410 FailedExperiments=0 ResultName=nginx-chaos-pod-delete PassedExperiments=7 StartTime=1.630657398e+09 AwaitedExperiments=1 ResultNamespace=default
time="2021-09-03T08:23:52Z" level=info msg="The chaos metrics are as follows" StartTime=1.630657398e+09 TotalDuration=0 FailedExperiments=0 ResultNamespace=default EndTime=0 ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete ProbeSuccessPercentage=0 PassedExperiments=7 AwaitedExperiments=1 ResultVerdict=Awaited

time="2021-09-03T08:23:53Z" level=info msg="The chaos metrics are as follows" TotalDuration=0 ResultVerdict=Awaited ResultName=nginx-chaos-pod-delete PassedExperiments=7 FailedExperiments=0 ProbeSuccessPercentage=0 StartTime=1.630657398e+09 EndTime=0 ResultNamespace=default ChaosInjectTime=1630657410 AwaitedExperiments=1
time="2021-09-03T08:23:54Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete PassedExperiments=7 EndTime=0 ChaosInjectTime=1630657410 TotalDuration=0 StartTime=1.630657398e+09 ResultVerdict=Awaited ResultNamespace=default ProbeSuccessPercentage=0 FailedExperiments=0 AwaitedExperiments=1

time="2021-09-03T08:23:55Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Awaited FailedExperiments=0 AwaitedExperiments=1 TotalDuration=0 PassedExperiments=7 ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410 ProbeSuccessPercentage=0 ResultNamespace=default StartTime=1.630657398e+09 EndTime=0

time="2021-09-03T08:23:56Z" level=info msg="The chaos metrics are as follows" ChaosInjectTime=1630657410 StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete TotalDuration=0 AwaitedExperiments=1 ProbeSuccessPercentage=0 PassedExperiments=7 EndTime=0 ResultVerdict=Awaited ResultNamespace=default FailedExperiments=0
time="2021-09-03T08:23:57Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default FailedExperiments=0 AwaitedExperiments=1 StartTime=1.630657398e+09 TotalDuration=0 ResultName=nginx-chaos-pod-delete ResultVerdict=Awaited EndTime=0 ProbeSuccessPercentage=0 ChaosInjectTime=1630657410 PassedExperiments=7

time="2021-09-03T08:23:58Z" level=info msg="The chaos metrics are as follows" EndTime=0 PassedExperiments=7 ChaosInjectTime=1630657410 ResultNamespace=default ResultName=nginx-chaos-pod-delete ResultVerdict=Awaited FailedExperiments=0 StartTime=1.630657398e+09 TotalDuration=0 ProbeSuccessPercentage=0 AwaitedExperiments=1

time="2021-09-03T08:23:59Z" level=info msg="The chaos metrics are as follows" EndTime=0 ResultName=nginx-chaos-pod-delete AwaitedExperiments=1 ResultVerdict=Awaited ProbeSuccessPercentage=0 TotalDuration=0 PassedExperiments=7 ResultNamespace=default ChaosInjectTime=1630657410 FailedExperiments=0 StartTime=1.630657398e+09

time="2021-09-03T08:24:00Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Awaited ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410 PassedExperiments=7 TotalDuration=0 FailedExperiments=0 AwaitedExperiments=1 EndTime=0 ResultNamespace=default ProbeSuccessPercentage=0 StartTime=1.630657398e+09

time="2021-09-03T08:24:01Z" level=info msg="The chaos metrics are as follows" AwaitedExperiments=1 ProbeSuccessPercentage=0 PassedExperiments=7 TotalDuration=0 ResultVerdict=Awaited FailedExperiments=0 ChaosInjectTime=1630657410 StartTime=1.630657398e+09 EndTime=0 ResultName=nginx-chaos-pod-delete ResultNamespace=default

time="2021-09-03T08:24:02Z" level=info msg="The chaos metrics are as follows" TotalDuration=0 ResultVerdict=Awaited PassedExperiments=7 ResultNamespace=default ChaosInjectTime=1630657410 AwaitedExperiments=1 FailedExperiments=0 EndTime=0 ResultName=nginx-chaos-pod-delete ProbeSuccessPercentage=0 StartTime=1.630657398e+09

time="2021-09-03T08:24:03Z" level=info msg="The chaos metrics are as follows" TotalDuration=0 ChaosInjectTime=1630657410 PassedExperiments=7 StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete FailedExperiments=0 AwaitedExperiments=1 ResultVerdict=Awaited ResultNamespace=default ProbeSuccessPercentage=0 EndTime=0
time="2021-09-03T08:24:04Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default ProbeSuccessPercentage=0 ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete ResultVerdict=Awaited StartTime=1.630657398e+09 FailedExperiments=0 EndTime=0 AwaitedExperiments=1 PassedExperiments=7 TotalDuration=0

time="2021-09-03T08:24:05Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete TotalDuration=0 StartTime=1.630657398e+09 PassedExperiments=7 ChaosInjectTime=1630657410 ResultNamespace=default FailedExperiments=0 ProbeSuccessPercentage=0 AwaitedExperiments=1 EndTime=0 ResultVerdict=Awaited

time="2021-09-03T08:24:06Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default AwaitedExperiments=1 ResultName=nginx-chaos-pod-delete ProbeSuccessPercentage=0 ChaosInjectTime=1630657410 TotalDuration=0 StartTime=1.630657398e+09 ResultVerdict=Awaited PassedExperiments=7 FailedExperiments=0 EndTime=0

time="2021-09-03T08:24:07Z" level=info msg="The chaos metrics are as follows" EndTime=0 FailedExperiments=0 ResultName=nginx-chaos-pod-delete ProbeSuccessPercentage=0 AwaitedExperiments=1 TotalDuration=0 PassedExperiments=7 ResultVerdict=Awaited ResultNamespace=default StartTime=1.630657398e+09 ChaosInjectTime=1630657410
time="2021-09-03T08:24:09Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Awaited ResultNamespace=default PassedExperiments=7 ResultName=nginx-chaos-pod-delete EndTime=0 ChaosInjectTime=1630657410 AwaitedExperiments=1 StartTime=1.630657398e+09 TotalDuration=0 FailedExperiments=0 ProbeSuccessPercentage=0

time="2021-09-03T08:24:10Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=0 ResultNamespace=default TotalDuration=0 EndTime=0 PassedExperiments=7 ChaosInjectTime=1630657410 ResultVerdict=Awaited StartTime=1.630657398e+09 FailedExperiments=0 AwaitedExperiments=1 ResultName=nginx-chaos-pod-delete

time="2021-09-03T08:24:11Z" level=info msg="The chaos metrics are as follows" StartTime=1.630657398e+09 ResultNamespace=default AwaitedExperiments=1 ResultVerdict=Awaited ResultName=nginx-chaos-pod-delete PassedExperiments=7 FailedExperiments=0 EndTime=0 TotalDuration=0 ProbeSuccessPercentage=0 ChaosInjectTime=1630657410

time="2021-09-03T08:24:12Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=0 ResultVerdict=Awaited EndTime=0 ChaosInjectTime=1630657410 StartTime=1.630657398e+09 FailedExperiments=0 ResultName=nginx-chaos-pod-delete PassedExperiments=7 TotalDuration=0 ResultNamespace=default AwaitedExperiments=1

time="2021-09-03T08:24:13Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default TotalDuration=0 StartTime=1.630657398e+09 EndTime=0 ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete FailedExperiments=0 ProbeSuccessPercentage=100 PassedExperiments=8 AwaitedExperiments=0 ResultVerdict=Pass
time="2021-09-03T08:24:14Z" level=info msg="The chaos metrics are as follows" FailedExperiments=0 TotalDuration=0 EndTime=0 PassedExperiments=8 ResultNamespace=default ProbeSuccessPercentage=100 StartTime=1.630657398e+09 AwaitedExperiments=0 ResultVerdict=Pass ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410

time="2021-09-03T08:24:15Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=100 ChaosInjectTime=1630657410 FailedExperiments=0 TotalDuration=56 ResultVerdict=Pass AwaitedExperiments=0 PassedExperiments=8 StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete EndTime=1.630657454e+09 ResultNamespace=default

time="2021-09-03T08:24:16Z" level=info msg="The chaos metrics are as follows" AwaitedExperiments=0 FailedExperiments=0 ResultNamespace=default PassedExperiments=8 ChaosInjectTime=1630657410 StartTime=1.630657398e+09 ProbeSuccessPercentage=100 EndTime=1.630657454e+09 TotalDuration=56 ResultName=nginx-chaos-pod-delete ResultVerdict=Pass

time="2021-09-03T08:24:17Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete ResultNamespace=default TotalDuration=56 FailedExperiments=0 AwaitedExperiments=0 StartTime=1.630657398e+09 ChaosInjectTime=1630657410 ResultVerdict=Pass ProbeSuccessPercentage=100 PassedExperiments=8 EndTime=1.630657454e+09

time="2021-09-03T08:24:18Z" level=info msg="The chaos metrics are as follows" TotalDuration=56 ResultNamespace=default AwaitedExperiments=0 ProbeSuccessPercentage=100 ChaosInjectTime=1630657410 PassedExperiments=8 ResultVerdict=Pass EndTime=1.630657454e+09 StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete FailedExperiments=0
time="2021-09-03T08:24:19Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default ResultVerdict=Pass PassedExperiments=8 ProbeSuccessPercentage=100 EndTime=1.630657454e+09 ChaosInjectTime=1630657410 FailedExperiments=0 AwaitedExperiments=0 StartTime=1.630657398e+09 TotalDuration=56 ResultName=nginx-chaos-pod-delete

time="2021-09-03T08:24:20Z" level=info msg="The chaos metrics are as follows" StartTime=1.630657398e+09 AwaitedExperiments=0 ResultNamespace=default ChaosInjectTime=1630657410 TotalDuration=56 ResultVerdict=Pass PassedExperiments=8 FailedExperiments=0 ResultName=nginx-chaos-pod-delete ProbeSuccessPercentage=100 EndTime=1.630657454e+09

time="2021-09-03T08:24:21Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Pass PassedExperiments=8 TotalDuration=56 StartTime=1.630657398e+09 FailedExperiments=0 AwaitedExperiments=0 ResultName=nginx-chaos-pod-delete ProbeSuccessPercentage=100 ChaosInjectTime=1630657410 ResultNamespace=default EndTime=1.630657454e+09
time="2021-09-03T08:24:22Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete FailedExperiments=0 AwaitedExperiments=0 ProbeSuccessPercentage=100 ResultNamespace=default EndTime=1.630657454e+09 StartTime=1.630657398e+09 ChaosInjectTime=1630657410 ResultVerdict=Pass TotalDuration=56 PassedExperiments=8

time="2021-09-03T08:24:23Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=100 AwaitedExperiments=0 PassedExperiments=8 ResultName=nginx-chaos-pod-delete FailedExperiments=0 TotalDuration=56 EndTime=1.630657454e+09 ChaosInjectTime=1630657410 StartTime=1.630657398e+09 ResultVerdict=Pass ResultNamespace=default

time="2021-09-03T08:24:25Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=100 FailedExperiments=0 AwaitedExperiments=0 PassedExperiments=8 StartTime=1.630657398e+09 TotalDuration=56 ResultVerdict=Pass EndTime=1.630657454e+09 ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete ResultNamespace=default

time="2021-09-03T08:24:26Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=100 EndTime=1.630657454e+09 PassedExperiments=8 ResultName=nginx-chaos-pod-delete StartTime=1.630657398e+09 ChaosInjectTime=1630657410 ResultNamespace=default ResultVerdict=Pass TotalDuration=56 AwaitedExperiments=0 FailedExperiments=0

time="2021-09-03T08:24:27Z" level=info msg="The chaos metrics are as follows" TotalDuration=56 ResultName=nginx-chaos-pod-delete ResultNamespace=default FailedExperiments=0 ChaosInjectTime=1630657410 StartTime=1.630657398e+09 EndTime=1.630657454e+09 ProbeSuccessPercentage=100 ResultVerdict=Pass AwaitedExperiments=0 PassedExperiments=8

time="2021-09-03T08:24:28Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Pass PassedExperiments=8 ChaosInjectTime=1630657410 ResultNamespace=default ResultName=nginx-chaos-pod-delete AwaitedExperiments=0 ProbeSuccessPercentage=100 EndTime=1.630657454e+09 FailedExperiments=0 StartTime=1.630657398e+09 TotalDuration=56
time="2021-09-03T08:24:29Z" level=info msg="The chaos metrics are as follows" PassedExperiments=8 AwaitedExperiments=0 ChaosInjectTime=1630657410 FailedExperiments=0 ProbeSuccessPercentage=100 ResultVerdict=Pass TotalDuration=56 ResultName=nginx-chaos-pod-delete StartTime=1.630657398e+09 EndTime=1.630657454e+09 ResultNamespace=default

time="2021-09-03T08:24:30Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Pass ProbeSuccessPercentage=100 ResultName=nginx-chaos-pod-delete AwaitedExperiments=0 EndTime=1.630657454e+09 FailedExperiments=0 ResultNamespace=default PassedExperiments=8 ChaosInjectTime=1630657410 StartTime=1.630657398e+09 TotalDuration=56
time="2021-09-03T08:24:31Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=100 ResultVerdict=Pass ResultName=nginx-chaos-pod-delete FailedExperiments=0 ResultNamespace=default AwaitedExperiments=0 PassedExperiments=8 EndTime=1.630657454e+09 TotalDuration=56 StartTime=1.630657398e+09 ChaosInjectTime=1630657410

time="2021-09-03T08:24:32Z" level=info msg="The chaos metrics are as follows" EndTime=1.630657454e+09 ProbeSuccessPercentage=100 PassedExperiments=8 TotalDuration=56 ResultNamespace=default AwaitedExperiments=0 ResultVerdict=Pass FailedExperiments=0 ChaosInjectTime=1630657410 StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete

time="2021-09-03T08:24:33Z" level=info msg="The chaos metrics are as follows" AwaitedExperiments=0 ProbeSuccessPercentage=100 PassedExperiments=8 ResultVerdict=Pass EndTime=1.630657454e+09 ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410 TotalDuration=56 ResultNamespace=default StartTime=1.630657398e+09 FailedExperiments=0
time="2021-09-03T08:24:34Z" level=info msg="The chaos metrics are as follows" ChaosInjectTime=1630657410 ProbeSuccessPercentage=100 EndTime=1.630657454e+09 StartTime=1.630657398e+09 ResultVerdict=Pass PassedExperiments=8 ResultName=nginx-chaos-pod-delete ResultNamespace=default AwaitedExperiments=0 TotalDuration=56 FailedExperiments=0

time="2021-09-03T08:24:35Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default FailedExperiments=0 EndTime=1.630657454e+09 ProbeSuccessPercentage=100 AwaitedExperiments=0 StartTime=1.630657398e+09 ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete TotalDuration=56 ResultVerdict=Pass PassedExperiments=8

time="2021-09-03T08:24:36Z" level=info msg="The chaos metrics are as follows" ChaosInjectTime=1630657410 TotalDuration=56 ResultNamespace=default StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete AwaitedExperiments=0 EndTime=1.630657454e+09 FailedExperiments=0 ProbeSuccessPercentage=100 ResultVerdict=Pass PassedExperiments=8

time="2021-09-03T08:24:37Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default FailedExperiments=0 AwaitedExperiments=0 StartTime=1.630657398e+09 ProbeSuccessPercentage=100 ChaosInjectTime=1630657410 TotalDuration=56 EndTime=1.630657454e+09 ResultVerdict=Pass ResultName=nginx-chaos-pod-delete PassedExperiments=8

time="2021-09-03T08:24:38Z" level=info msg="The chaos metrics are as follows" PassedExperiments=8 ChaosInjectTime=1630657410 StartTime=1.630657398e+09 EndTime=1.630657454e+09 ProbeSuccessPercentage=100 TotalDuration=56 ResultName=nginx-chaos-pod-delete AwaitedExperiments=0 ResultVerdict=Pass FailedExperiments=0 ResultNamespace=default
time="2021-09-03T08:24:39Z" level=info msg="The chaos metrics are as follows" ChaosInjectTime=1630657410 EndTime=1.630657454e+09 TotalDuration=56 ResultVerdict=Pass PassedExperiments=8 AwaitedExperiments=0 ResultNamespace=default FailedExperiments=0 ResultName=nginx-chaos-pod-delete ProbeSuccessPercentage=100 StartTime=1.630657398e+09

time="2021-09-03T08:24:40Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=100 FailedExperiments=0 EndTime=1.630657454e+09 ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete ResultVerdict=Pass AwaitedExperiments=0 PassedExperiments=8 StartTime=1.630657398e+09 TotalDuration=56 ResultNamespace=default

time="2021-09-03T08:24:41Z" level=info msg="The chaos metrics are as follows" TotalDuration=56 ProbeSuccessPercentage=100 ChaosInjectTime=1630657410 ResultVerdict=Pass AwaitedExperiments=0 EndTime=1.630657454e+09 StartTime=1.630657398e+09 ResultNamespace=default PassedExperiments=8 FailedExperiments=0 ResultName=nginx-chaos-pod-delete
time="2021-09-03T08:24:42Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete FailedExperiments=0 ChaosInjectTime=1630657410 PassedExperiments=8 AwaitedExperiments=0 ResultNamespace=default ResultVerdict=Pass EndTime=1.630657454e+09 ProbeSuccessPercentage=100 StartTime=1.630657398e+09 TotalDuration=56

time="2021-09-03T08:24:43Z" level=info msg="The chaos metrics are as follows" PassedExperiments=8 FailedExperiments=0 AwaitedExperiments=0 ProbeSuccessPercentage=100 TotalDuration=56 ResultVerdict=Pass ResultName=nginx-chaos-pod-delete ResultNamespace=default EndTime=1.630657454e+09 ChaosInjectTime=1630657410 StartTime=1.630657398e+09

time="2021-09-03T08:24:45Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete PassedExperiments=8 TotalDuration=56 AwaitedExperiments=0 EndTime=1.630657454e+09 ResultVerdict=Pass ResultNamespace=default FailedExperiments=0 ChaosInjectTime=1630657410 ProbeSuccessPercentage=100 StartTime=1.630657398e+09

time="2021-09-03T08:24:46Z" level=info msg="The chaos metrics are as follows" AwaitedExperiments=0 StartTime=1.630657398e+09 PassedExperiments=8 ResultVerdict=Pass ProbeSuccessPercentage=100 ResultName=nginx-chaos-pod-delete EndTime=1.630657454e+09 TotalDuration=56 FailedExperiments=0 ResultNamespace=default ChaosInjectTime=1630657410

time="2021-09-03T08:24:47Z" level=info msg="The chaos metrics are as follows" ChaosInjectTime=1630657410 StartTime=1.630657398e+09 EndTime=1.630657454e+09 PassedExperiments=8 AwaitedExperiments=0 ProbeSuccessPercentage=100 ResultNamespace=default ResultName=nginx-chaos-pod-delete FailedExperiments=0 ResultVerdict=Pass TotalDuration=56

time="2021-09-03T08:24:48Z" level=info msg="The chaos metrics are as follows" FailedExperiments=0 PassedExperiments=8 EndTime=1.630657454e+09 ResultNamespace=default ResultName=nginx-chaos-pod-delete StartTime=1.630657398e+09 TotalDuration=56 ProbeSuccessPercentage=100 AwaitedExperiments=0 ChaosInjectTime=1630657410 ResultVerdict=Pass

time="2021-09-03T08:24:49Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Pass ProbeSuccessPercentage=100 AwaitedExperiments=0 EndTime=1.630657454e+09 ChaosInjectTime=1630657410 TotalDuration=56 FailedExperiments=0 ResultName=nginx-chaos-pod-delete ResultNamespace=default PassedExperiments=8 StartTime=1.630657398e+09

time="2021-09-03T08:24:50Z" level=info msg="The chaos metrics are as follows" EndTime=1.630657454e+09 AwaitedExperiments=0 ProbeSuccessPercentage=100 ResultVerdict=Pass ResultNamespace=default FailedExperiments=0 StartTime=1.630657398e+09 ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete PassedExperiments=8 TotalDuration=56

time="2021-09-03T08:24:51Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default ChaosInjectTime=1630657410 TotalDuration=56 AwaitedExperiments=0 StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete PassedExperiments=8 FailedExperiments=0 ResultVerdict=Pass ProbeSuccessPercentage=100 EndTime=1.630657454e+09
time="2021-09-03T08:24:52Z" level=info msg="The chaos metrics are as follows" EndTime=1.630657454e+09 ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete AwaitedExperiments=0 TotalDuration=56 StartTime=1.630657398e+09 PassedExperiments=8 ResultNamespace=default FailedExperiments=0 ResultVerdict=Pass ProbeSuccessPercentage=100

time="2021-09-03T08:24:53Z" level=info msg="The chaos metrics are as follows" PassedExperiments=8 EndTime=1.630657454e+09 TotalDuration=56 ResultName=nginx-chaos-pod-delete StartTime=1.630657398e+09 ResultVerdict=Pass FailedExperiments=0 AwaitedExperiments=0 ResultNamespace=default ChaosInjectTime=1630657410 ProbeSuccessPercentage=100
time="2021-09-03T08:24:54Z" level=info msg="The chaos metrics are as follows" EndTime=1.630657454e+09 FailedExperiments=0 AwaitedExperiments=0 PassedExperiments=8 StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete ProbeSuccessPercentage=100 ResultVerdict=Pass ResultNamespace=default ChaosInjectTime=1630657410 TotalDuration=56

time="2021-09-03T08:24:55Z" level=info msg="The chaos metrics are as follows" PassedExperiments=8 AwaitedExperiments=0 EndTime=1.630657454e+09 ResultNamespace=default ResultName=nginx-chaos-pod-delete ResultVerdict=Pass ChaosInjectTime=1630657410 StartTime=1.630657398e+09 TotalDuration=56 FailedExperiments=0 ProbeSuccessPercentage=100

time="2021-09-03T08:24:56Z" level=info msg="The chaos metrics are as follows" TotalDuration=56 StartTime=1.630657398e+09 EndTime=1.630657454e+09 ResultNamespace=default PassedExperiments=8 FailedExperiments=0 AwaitedExperiments=0 ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete ProbeSuccessPercentage=100 ResultVerdict=Pass

time="2021-09-03T08:24:58Z" level=info msg="The chaos metrics are as follows" TotalDuration=56 ResultVerdict=Pass ResultNamespace=default ProbeSuccessPercentage=100 StartTime=1.630657398e+09 PassedExperiments=8 ChaosInjectTime=1630657410 AwaitedExperiments=0 FailedExperiments=0 EndTime=1.630657454e+09 ResultName=nginx-chaos-pod-delete

time="2021-09-03T08:24:59Z" level=info msg="The chaos metrics are as follows" FailedExperiments=0 StartTime=1.630657398e+09 TotalDuration=56 EndTime=1.630657454e+09 ResultName=nginx-chaos-pod-delete ProbeSuccessPercentage=100 ResultVerdict=Pass ChaosInjectTime=1630657410 ResultNamespace=default PassedExperiments=8 AwaitedExperiments=0

time="2021-09-03T08:25:00Z" level=info msg="The chaos metrics are as follows" StartTime=1.630657398e+09 PassedExperiments=8 FailedExperiments=0 ProbeSuccessPercentage=100 ChaosInjectTime=1630657410 ResultVerdict=Pass EndTime=1.630657454e+09 ResultNamespace=default AwaitedExperiments=0 ResultName=nginx-chaos-pod-delete TotalDuration=56
time="2021-09-03T08:25:01Z" level=info msg="The chaos metrics are as follows" FailedExperiments=0 ChaosInjectTime=1630657410 ProbeSuccessPercentage=100 TotalDuration=56 ResultNamespace=default ResultVerdict=Pass EndTime=1.630657454e+09 ResultName=nginx-chaos-pod-delete StartTime=1.630657398e+09 PassedExperiments=8 AwaitedExperiments=0

time="2021-09-03T08:25:02Z" level=info msg="The chaos metrics are as follows" PassedExperiments=8 FailedExperiments=0 ProbeSuccessPercentage=100 ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete StartTime=1.630657398e+09 TotalDuration=56 ResultNamespace=default EndTime=1.630657454e+09 AwaitedExperiments=0 ResultVerdict=Pass

time="2021-09-03T08:25:03Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Pass ResultNamespace=default AwaitedExperiments=0 StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete EndTime=1.630657454e+09 PassedExperiments=8 ProbeSuccessPercentage=100 TotalDuration=56 FailedExperiments=0 ChaosInjectTime=1630657410

time="2021-09-03T08:25:04Z" level=info msg="The chaos metrics are as follows" PassedExperiments=8 ProbeSuccessPercentage=100 FailedExperiments=0 TotalDuration=56 ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410 ResultNamespace=default AwaitedExperiments=0 StartTime=1.630657398e+09 ResultVerdict=Pass EndTime=1.630657454e+09
time="2021-09-03T08:25:05Z" level=info msg="The chaos metrics are as follows" PassedExperiments=8 ProbeSuccessPercentage=100 EndTime=1.630657454e+09 ChaosInjectTime=1630657410 TotalDuration=56 FailedExperiments=0 ResultVerdict=Pass AwaitedExperiments=0 StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete ResultNamespace=default

time="2021-09-03T08:25:06Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Pass ProbeSuccessPercentage=100 ChaosInjectTime=1630657410 ResultNamespace=default EndTime=1.630657454e+09 StartTime=1.630657398e+09 TotalDuration=56 PassedExperiments=8 FailedExperiments=0 ResultName=nginx-chaos-pod-delete AwaitedExperiments=0

time="2021-09-03T08:25:07Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=100 TotalDuration=56 StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete AwaitedExperiments=0 ChaosInjectTime=1630657410 ResultVerdict=Pass FailedExperiments=0 EndTime=1.630657454e+09 ResultNamespace=default PassedExperiments=8

time="2021-09-03T08:25:08Z" level=info msg="The chaos metrics are as follows" StartTime=1.630657398e+09 FailedExperiments=0 ResultName=nginx-chaos-pod-delete PassedExperiments=8 TotalDuration=56 ResultVerdict=Pass ProbeSuccessPercentage=100 ResultNamespace=default ChaosInjectTime=1630657410 EndTime=1.630657454e+09 AwaitedExperiments=0

time="2021-09-03T08:25:09Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default EndTime=1.630657454e+09 ResultName=nginx-chaos-pod-delete FailedExperiments=0 AwaitedExperiments=0 ChaosInjectTime=1630657410 ProbeSuccessPercentage=100 StartTime=1.630657398e+09 TotalDuration=56 ResultVerdict=Pass PassedExperiments=8

time="2021-09-03T08:25:10Z" level=info msg="The chaos metrics are as follows" StartTime=1.630657398e+09 ChaosInjectTime=1630657410 ResultNamespace=default AwaitedExperiments=0 TotalDuration=56 PassedExperiments=8 FailedExperiments=0 ResultName=nginx-chaos-pod-delete ProbeSuccessPercentage=100 ResultVerdict=Pass EndTime=1.630657454e+09

time="2021-09-03T08:25:11Z" level=info msg="The chaos metrics are as follows" ProbeSuccessPercentage=100 StartTime=1.630657398e+09 FailedExperiments=0 EndTime=1.630657454e+09 ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410 TotalDuration=56 ResultNamespace=default AwaitedExperiments=0 ResultVerdict=Pass PassedExperiments=8
time="2021-09-03T08:25:12Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete ResultNamespace=default EndTime=1.630657454e+09 TotalDuration=56 ChaosInjectTime=1630657410 FailedExperiments=0 StartTime=1.630657398e+09 PassedExperiments=8 AwaitedExperiments=0 ProbeSuccessPercentage=100 ResultVerdict=Pass

time="2021-09-03T08:25:13Z" level=info msg="The chaos metrics are as follows" TotalDuration=56 ProbeSuccessPercentage=100 StartTime=1.630657398e+09 ResultNamespace=default ChaosInjectTime=1630657410 PassedExperiments=8 EndTime=1.630657454e+09 AwaitedExperiments=0 ResultName=nginx-chaos-pod-delete FailedExperiments=0 ResultVerdict=Pass
time="2021-09-03T08:25:15Z" level=info msg="The chaos metrics are as follows" ResultNamespace=default EndTime=1.630657454e+09 ResultVerdict=Pass StartTime=1.630657398e+09 ChaosInjectTime=1630657410 PassedExperiments=8 ProbeSuccessPercentage=100 TotalDuration=56 ResultName=nginx-chaos-pod-delete FailedExperiments=0 AwaitedExperiments=0

time="2021-09-03T08:25:16Z" level=info msg="The chaos metrics are as follows" EndTime=1.630657454e+09 ResultNamespace=default PassedExperiments=8 AwaitedExperiments=0 ProbeSuccessPercentage=100 ResultVerdict=Pass StartTime=1.630657398e+09 ChaosInjectTime=1630657410 FailedExperiments=0 ResultName=nginx-chaos-pod-delete TotalDuration=56

time="2021-09-03T08:25:17Z" level=info msg="The chaos metrics are as follows" StartTime=1.630657398e+09 ResultName=nginx-chaos-pod-delete FailedExperiments=0 ResultNamespace=default ProbeSuccessPercentage=100 EndTime=1.630657454e+09 TotalDuration=56 ChaosInjectTime=1630657410 ResultVerdict=Pass PassedExperiments=8 AwaitedExperiments=0

time="2021-09-03T08:25:18Z" level=info msg="The chaos metrics are as follows" AwaitedExperiments=0 ResultName=nginx-chaos-pod-delete PassedExperiments=8 ChaosInjectTime=1630657410 TotalDuration=56 StartTime=1.630657398e+09 ResultVerdict=Pass FailedExperiments=0 ResultNamespace=default ProbeSuccessPercentage=100 EndTime=1.630657454e+09

time="2021-09-03T08:25:19Z" level=info msg="The chaos metrics are as follows" TotalDuration=56 ResultNamespace=default ProbeSuccessPercentage=100 StartTime=1.630657398e+09 EndTime=1.630657454e+09 FailedExperiments=0 ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410 ResultVerdict=Pass AwaitedExperiments=0 PassedExperiments=8

time="2021-09-03T08:25:20Z" level=info msg="The chaos metrics are as follows" FailedExperiments=0 ResultVerdict=Pass ResultNamespace=default TotalDuration=56 ProbeSuccessPercentage=100 PassedExperiments=8 AwaitedExperiments=0 StartTime=1.630657398e+09 ChaosInjectTime=1630657410 EndTime=1.630657454e+09 ResultName=nginx-chaos-pod-delete
time="2021-09-03T08:25:21Z" level=info msg="The chaos metrics are as follows" ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410 ResultNamespace=default EndTime=1.630657454e+09 ResultVerdict=Pass ProbeSuccessPercentage=100 TotalDuration=56 FailedExperiments=0 StartTime=1.630657398e+09 PassedExperiments=8 AwaitedExperiments=0

time="2021-09-03T08:25:22Z" level=info msg="The chaos metrics are as follows" TotalDuration=56 AwaitedExperiments=0 ProbeSuccessPercentage=100 EndTime=1.630657454e+09 ResultVerdict=Pass ResultNamespace=default ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete StartTime=1.630657398e+09 FailedExperiments=0 PassedExperiments=8

time="2021-09-03T08:25:23Z" level=info msg="The chaos metrics are as follows" AwaitedExperiments=0 ProbeSuccessPercentage=100 EndTime=1.630657454e+09 ChaosInjectTime=1630657410 ResultVerdict=Pass PassedExperiments=8 TotalDuration=56 ResultName=nginx-chaos-pod-delete ResultNamespace=default StartTime=1.630657398e+09 FailedExperiments=0

time="2021-09-03T08:25:24Z" level=info msg="The chaos metrics are as follows" StartTime=1.630657398e+09 ChaosInjectTime=1630657410 ProbeSuccessPercentage=100 PassedExperiments=8 TotalDuration=56 EndTime=1.630657454e+09 FailedExperiments=0 ResultVerdict=Pass ResultNamespace=default ResultName=nginx-chaos-pod-delete AwaitedExperiments=0
time="2021-09-03T08:25:25Z" level=info msg="The chaos metrics are as follows" FailedExperiments=0 AwaitedExperiments=0 ResultVerdict=Pass EndTime=1.630657454e+09 TotalDuration=56 PassedExperiments=8 ProbeSuccessPercentage=100 StartTime=1.630657398e+09 ResultNamespace=default ChaosInjectTime=1630657410 ResultName=nginx-chaos-pod-delete

time="2021-09-03T08:25:26Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Pass ChaosInjectTime=1630657410 ResultNamespace=default StartTime=1.630657398e+09 PassedExperiments=8 FailedExperiments=0 ProbeSuccessPercentage=100 TotalDuration=56 AwaitedExperiments=0 EndTime=1.630657454e+09 ResultName=nginx-chaos-pod-delete

time="2021-09-03T08:25:27Z" level=info msg="The chaos metrics are as follows" ResultVerdict=Pass ChaosInjectTime=1630657410 PassedExperiments=8 AwaitedExperiments=0 StartTime=1.630657398e+09 EndTime=1.630657454e+09 ResultName=nginx-chaos-pod-delete ResultNamespace=default FailedExperiments=0 ProbeSuccessPercentage=100 TotalDuration=56

time="2021-09-03T08:25:28Z" level=info msg="The chaos metrics are as follows" PassedExperiments=8 StartTime=1.630657398e+09 TotalDuration=56 FailedExperiments=0 ResultName=nginx-chaos-pod-delete ChaosInjectTime=1630657410 ResultNamespace=default ProbeSuccessPercentage=100 EndTime=1.630657454e+09 ResultVerdict=Pass AwaitedExperiments=0

repo: litmuschaos/chaos-exporter


text:
Updated pod logs to fetch argo and experiment logs independently

Signed-off-by: Soumya Ghosh Dastidar gdsoumya@gmail.com
Proposed changes
This PR updates the pod logs feature to query argo and experiment pods dependently.
fixes #2813
Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[ ] New feature (non-breaking change which adds functionality)
[x] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the commit for DCO to be passed.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)

Logs after argo pods are deleted but experiment pods are still live:
Failed to get argo pod logs

W0517 10:23:22.488627       1 client_config.go:541] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time='2021-05-17T10:23:22Z' level=info msg='Experiment Name: pod-delete'
time='2021-05-17T10:23:22Z' level=info msg='[PreReq]: Getting the ENV for the  experiment'
time='2021-05-17T10:23:22Z' level=info msg='[PreReq]: Updating the chaos result of pod-delete experiment (SOT)'
time='2021-05-17T10:23:22Z' level=info msg='The application information is as follows' Namespace=default Label='app=nginx' Ramp Time=0
time='2021-05-17T10:23:22Z' level=info msg='[Status]: Verify that the AUT (Application Under Test) is running (pre-chaos)'
time='2021-05-17T10:23:22Z' level=info msg='[Status]: Checking whether application containers are in ready state'
time='2021-05-17T10:23:22Z' level=info msg='[Status]: The Container status are as follows' container=nginx Pod=nginx-6799fc88d8-9h4td Readiness=true
....

repo: litmuschaos/litmus


text:
Change init.lua to init.luau in package.json

I'm using npmluau and it wasn't working due to the file name being wrong

This is a requirement for Roblox-TS ☹
I might have to wait on a fix for Roblox-TS to support this change.

repo: littensy/ripple


text:
🛑 USTC is down

In 4e7fe26, USTC (https://www.ustc.edu.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: USTC is back up in a51cd7c.

repo: littlekud/sites-status


text:
🛑 USTC is down

In ecd948a, USTC (https://www.ustc.edu.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: USTC is back up in b34e6ff.


text:
New object types in next release - ideas, suggestions, reviews

In the next release (v4.3.0) I'm planning to add new smart phone like object types.
I thought about the following types:

lv_split a hor. or ver. line for decoration purpose
lv_valset a label with "+" and "-" buttons
lv_tabview organise content with tabs (support swipe left/right)
lv_btngrp display more buttons to choose an option from them
lv_switch turn on/off by tap (a little slider)
lv_roller roller to select a value (like on smartphones)

If you have any new idea or suggestion don't hesitate to write a comment!

Tabview, roller,switch and btngrp (from lv_btnm)  is added in v5.0.0

repo: littlevgl/lvgl


text:
Add createdevdata management command

On other Django projects we typically have a manage.py command that creates useful fake data for development. It would be nice to have one here.

Closing in favour of using a SQL dump.

repo: littleweaver/django-brambling


text:
After focusout, the window will show the 6px white frame if you don't resize

@akascape do you have any idea about this?

yessssssssssssssssssssssssssssssssssss

repo: littlewhitecloud/CustomTkinterTitlebar


text:
页面自发失去焦点

当其他的input(type=text)和该编辑器在同一表单中，编辑其他的input会自发失去焦点，umeditor会自动获取焦点

v0.5.19 已解决该问题。


text:
库名带-会报错

[2022/07/11 17:35:24] [fatal] sqlgen.go:324 Fail to generate update sql for bi-report.QRTZ_SCHEDULER_STATE mysql-bin.001840 1610282-1610529
error: Invalid database name specified
ORIGINAL STACK TRACE:
my2sql/sqlbuilder.(*updateStatementImpl).String
/root/go/src/my2sql/sqlbuilder/statement.go:702 +0x66c062
my2sql/base.GenUpdateSqlsForOneRowsEvent
/root/go/src/my2sql/base/sqlgen.go:322 +0x69fdf0
my2sql/base.GenForwardRollbackSqlFromBinEvent
/root/go/src/my2sql/base/events.go:151 +0x69083e
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1371 +0x46c1c0
rows data:[RuoyiScheduler bi-report-client_sit1648115311244 1657529390600 15000]

[RuoyiScheduler bi-report-client_sit1648115311244 1657529405601 15000]

这个错误是引用的外部开源库sqlbuilder报出的异常，数据库名应该包含了特殊字符，这个bug暂时修不了。