401 Unauthorized with token

I just started to use this, idk if it's an update or what, but I get this output:
[wayne]$ php DiscordBots/MMLsAdmin/Main.php
Fatal error: Uncaught exception 'Discord\Exceptions\DiscordRequestFailedException' with message 'Erorr code 401: There was an error processing the request. UNAUTHORIZED - {"code": 0, "message": "401: Unauthorized"} - users/@me' in /home/discordserver/vendor/team-reflex/discord-php/src/Discord/Helpers/Guzzle.php:212
Stack trace:
#0 /home/discordserver/vendor/team-reflex/discord-php/src/Discord/Helpers/Guzzle.php(134): Discord\Helpers\Guzzle::handleError(401, 'UNAUTHORIZED', Object(GuzzleHttp\Psr7\Stream), 'users/@me')
#1 /home/discordserver/vendor/team-reflex/discord-php/src/Discord/Helpers/Guzzle.php(66): Discord\Helpers\Guzzle::runRequest('get', 'users/@me', NULL, false, Array)
#2 /home/discordserver/vendor/team-reflex/discord-php/src/Discord/Discord.php(71): Discord\Helpers\Guzzle::__callStatic('get', Array)
#3 /home/discordserver/vendor/team-reflex/discord-php/src/Discord/Discord.php(71): Discord\Helpers\Guzzle::get('users/@me')
#4 /home/discordserver/DiscordBots/MMLsAdmin/Main.php(10): Discord\Discord->__construct(Arr in /home/discordserver/vendor/team-reflex/discord-php/src/Discord/Helpers/Guzzle.php on line 212

Here's my code:
<?PHP

include "DiscordBots/Environment.php";
include "$Root/vendor/autoload.php";

use Discord\Discord;

$Discord = new Discord(array(
    "token" => "my.coo-bot.token", // replaced with my actual app bot user token(which works on the lua discord wrapper)
));

$Discord->run();

?>

I found out it was my php CLI version was out of date.


Obnoxious naming

"JS Standard" would imply that it's actually standardised. It isn't, it's an arbitrary coding style guide with no official endorsement.

Thanks for sharing your opinion :)
Those of us who use standard find it helps hold our code to a high standard of quality and ensures that new contributors follow our module's style standards.

@feross im gonna put that in the readme :)

@TazeTSchnitzel Thanks for the feedback. You can find our clarified intent of use of the word 'standard' here: https://github.com/feross/standard/blob/master/README.md#one-style-to-rule-them-all


Merge v1.2.3 master

Description
This PR reports tag v1.2.3 into master.
Cherry picked:
40afd641a9488db6b02a09d8eaf18eaa1e935d5b
b3e6c7f598be510befab97b3b9fdc707604d89aa
fa4d2d325dbd56d68183ebe69b944f6cd529fe04
0ecfbb8279d5d3c1e3c5c1c83834f73ad8cb5698
e21feae56163217674c3406bcf7f724f48521d0f
37b44cc706ebf28e9f255fc6220418c49ec7d84e

@emilevauge AFAICS, the vendored files should not be touched.
Please double-check they do not contain changes which should have gone into the non-vendored copy. git might have been confused (-X find-renames is your friend).

@timoreimann Indeed, that's why there is still a WIP label :)
FYI, git cherry-pick -Xrename-threshold=10% was not enough, I had to remove temporarily integration/vendor, cherry pick all commits and finally rebase interactively to remove the temp commit.
We need to merge https://github.com/containous/traefik/pull/1541 before this one, to avoid merge conflicts in server.go.

Reading the git diff documentation again, it looks like you need to actually increase the threshold in order to force git to be more strict.
Good to know for the next time. :-)

I tried with 10, 30, 50 and 80 :)

Aww, damn!

@emilevauge you have my commit in your branch...

@ldez I know I know, I'm waiting for https://github.com/containous/traefik/pull/1541 to be merged :)


Move docker build stuff to own repo

More and more applications and libraries get build on top of Xenon. They also have tests and need to use the same docker images that where made for Xenon. At the moment the docker build is hidden in gradle build scripts and src/integrationTest/docker directory. Let's give the xenon docker containers more visibility by giving them their own repository called xenon-docker-images.
This repository should be responsible for keeping the images on docker hub up to date.
The repository can use Docker Hub repository links to make sure when a base image changes all it's children also get rebuild.
The images contain secrets like password and private keys which need to be available to the libraries/applications that want to interact with them, the repo contains the golden standard and the libaries/applications should make copies of the secrets into their own repositories if needed. The repo
should use automated build on Docker Hub, this will require duplication of configs and scripts to the different docker build contexts.
This will allow the gradle build script of Xenon to become simpler and will no longer require the CI build of Xenon to build the images.

I agree on

giving docker images more visibility
simpler Gradle builds
facilitating testing of external applications and libraries against our docker images

Not entirely sure what you propose as an alternative though. Do you mean to have a shared base image with the (different sets of) required data? and then use the Dockerfile's FROM to make sure 'inheritance' works?
For future reference this stackoverflow gives some alternative strategies besides tar'ing: https://stackoverflow.com/questions/39376786/docker-and-symlinks#answer-39382248.

we're in the process of moving the information relating to building docker images to its own repo at:
https://github.com/NLeSC/xenon-docker-images

All done


GCP compute machine types

We already have them in gcp-linux

GCP has a huge collection of available machine types, and including them in a module doesn't make sense.


Add prefixes to parsed derivative file names

Add prefixes to parsed derivative file names
In the SPM, the output files are usually created with a prefix to original file name. For usual names it is an easy way for ordinary files, but it will break the bidsified names, as nothing can go before sub-.
Thus, if user want to daisy-chain processing step maintaining he need rename files after each processing step.
However, if bids.layout can support prefix (SPM allow the setting of prefix, so it can be separated from sub by _), then the output of each process can be readded directly by layout. Obviously this prefix should be defined only for derivatives.
Originally posted by @nbeliy in https://github.com/bids-standard/bids-matlab/issues/60#issuecomment-779066961

In the SPM, the output files are usually created with a prefix to original file name. For usual names it is an easy way for ordinary files, but it will break the bidsified names, as nothing can go before sub-.
Thus, if user want to daisy-chain processing step maintaining he need rename files after each processing step.
However, if bids.layout can support prefix (SPM allow the setting of prefix, so it can be separated from sub by _), then the output of each process can be readded directly by layout. Obviously this prefix should be defined only for derivatives.

Ideally for SPM I would recommend using the dependency options of its batch system to link the different analysis step (also because it is an embedded way to create a log file that tracks provenance) but I will try add it to the list of options.


Fix issues on initialisation in remap phase

There are currently two issues with initialisation during the remapping phase, which happens if classes/artifacts are attempted to be remapped, but the mappings are not found/invalid (both of which are my fault, sorry).
The first issue is that after running the initialisation phase, the internal state as to whether the mappings exist was not updated, meaning that the remap would continue as if the mappings didn't exist, causing a failure.
The second issue is that if there are broken mappings (i.e., either Mojang or Spigot mappings exist, but not both), it would try to delete all mappings and re-initialise to fix this. However, since not all mapping files exist, it would try to delete non-existent files, causing a failure.
This PR addresses both of these issues.

Thanks!


[BUG]: Documentation : Multipath related instructions are missing in Powerstore prerequisites

Bug Description
Multipath related instructions are missing in Powerstore prerequisites
Logs
Multipath related instructions are missing in Powerstore prerequisites
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
prerequisites in installation
Expected Behavior
documentation should be present .
CSM Driver(s)
CSI driver for PowerStore
Installation Type
No response
Container Storage Modules Enabled
No response
Container Orchestrator
all
Operating System
RHCOS

link: 20966


[Bug]: Square brackets in page title breaks parsing

Bug Description
Page with square brackets in title will add just fine. However later loading the list will break select-read-later.js script, causing reading list to not load, and not allowing for new items to be added.
Relevant Screenshot
No response
To Reproduce
Add any page with [ ] in the title. Example:
- [ ] [Google [Example] ](https://www.google.com) 📆 2024-12-03
Debugging Log
[11:19:49.555] Read Later[Script Filter] Queuing argument '(null)'
[11:19:49.583] Read Later[Script Filter] Script with argv '(null)' finished
[11:19:49.590] ERROR: Read Later[Script Filter] Code 1: /Users/rafaud/Library/Application Support/Alfred/Alfred.alfredpreferences/workflows/user.workflow.58867FE7-E75A-48C4-B774-9CAF7C785AEC/scripts/select-read-later.js: execution error: Error: TypeError: undefined is not an object (evaluating 'str.replace') (-2700)

Workflow Configuration

Checklist

[X] I have updated to the latest version of this workflow.
[X] I am using Alfred 5. (Older versions are not supported anymore.)

Good catch. I fixed in not in the selection script, but in the script adding new items, since it looks like [] in a markdown title makes those titles invalid markdown, and the markdown tasks by the workflow should be valid markdown.

With the latest release, [] will thus be removed from any title when added.
Available in the Alfred Gallery in 1-2 days, or directly by downloading the latest release here: https://github.com/chrisgrieser/alfred-read-later/releases/download/1.4.3/alfred-read-later.alfredworkflow


Add more ext tests

Description
Changes proposed in this pull request:

Remove Certificates and Git repos examples (too many examples to support, it's not needed)
Add tests for services example
Fix crashing view, fix 'undefined' as a description

Related issue(s)

Resolves #1556

/retest

/retest

/retest


Can not run project tests using grid version 3.3.0

I can not run our unit test with Karma since ag-grid 3.3.0.
Karma produces the following error (applyToTag(styleElement, obj) method):
TypeError: 'undefined' is not an object (evaluating 'obj.css')
at http://localhost:9876/base/bower_components/ag-grid/dist/ag-grid.js?e9b234d5ba7ffe29ab52a98bb8b14b9978a97f75:13402

If I go into test debug mode in webstorm then the "obj" param gets its values. Seems as if it needs just a little bit of time to boot up properly. Is there a workaround for this? The grid is working fine in the app it self, but I can not merge my feature unless test are runnable again.

Maybe related: v.3.3 also breaks module-less typescript projects (yay for somewhat-legacy apps). The actual error I get when upgrading to 3.3.3 and changing the d.ts file to /bower_components/ag-grid/dist/lib/grid.d.ts is: Cannot compile modules unless the '--module' flag is provided. file: bower_components\ag-grid\dist\lib\entities\rowNode.d.ts

My problem still exists in version 3.3.3

@noherczeg i don't know what is happening here, nobody else has reported it. what line of code is causing the problem?
@AkosLukacs ah crap. is turning on --module flag an issue? using modules is the future, and what the other 'big projects' appear to be doing.

@ceolter It's https://github.com/ceolter/ag-grid/blob/master/dist/ag-grid.js#L13532

@ceolter Actually working on moving to full typescript and replacing the
current bundling-stuff with "proper" modul system, but that takes time.
Priority of new features is usually higher than the priority of clean up
that may break working stuff...
On 23 February 2016 at 10:57, Norbert Csaba Herczeg <
<EMAIL_ADDRESS>wrote:

@ceolter https://github.com/ceolter It's
https://github.com/ceolter/ag-grid/blob/master/dist/ag-grid.js#L13532
—
Reply to this email directly or view it on GitHub
https://github.com/ceolter/ag-grid/issues/734#issuecomment-187630475.

It's odd though, can not find a single line of matching functions in the /src folder.

@noherczeg that line of code is not ag-Grid, it's the css style loader. the function applyToTag is put in during the webpack stage, so i'm guessing it's to do with the webpack loader 'style-loader'
can you use the non-css version of ag-Grid (dist/ag-grid.noStyle.js) for your tests?
alternatively can you google this problem with regards style-loader and see if a solution is there?

@AkosLukacs
can you not just rung on --module flag?

@ceolter Will try with the non styled version right now.

right, i need to start working, will be leaving github issues for rest of the day (sorry, otherwise i get stuck here for half a day)

Problem solved by the following:

using dist/ag-grid.noStyle.js
including dist/styles/ag-grid.css

This way the grid has it's proper format, and works. Tests run as well.
Thanks @ceolter !

@AkosLukacs If your problem still exists, please open another ticket for it. I didn't wanted to keep this one open because it would be misleading.

@noherczeg Sorry for disturbing your issue in the first place. Thought these are related somehow...
@ceolter Surprisingly, looks like it's working. Just expected that everything would just blow up...

@AkosLukacs No problem! :+1:


fix: handle non-utf8 bytes in log parser

Fixes #67
Switch from_utf8 to from_utf8_lossy. Instead of throwing an error when encountering invalid characters, it will insert placeholder error characters instead, e.g.: Apple �T�E���h�E���f�B�A�n���h��.
To try this fix immediately, run this command to add the bugfix branch as a dependency:
cargo add ffmpeg-sidecar --git https://github.com/nathanbabcock/ffmpeg-sidecar.git --branch fix/non-utf8

CI failure is an unrelated Github Actions issue with DNS resolution on Mac M1, I will try it again later.
0: https://www.osxexperts.net/ffmpeg7arm.zip: Dns Failed: resolve dns name 'www.osxexperts.net:443': failed to lookup address information


High disk usage from "System" process

So i did everything in the video.. Everything is working fine except when i am trying to play COD Warzone the "System" process is the only process while im playing that has high disk usage and that results to stuttering while i am playing!
This did not occur before the changes i made..
Does anyone have any kind of solution or advice?
Thank you in advance!

hmm hopefully it is not under system interrupts if that is case then there is hardware level error

So to give more details, i do not think (and certainly hope) this is the process you are talking about. This is the 'System' Process i am talking about:

and this is its file location

The 1st solution i tried and seemed to work was a program called TimerResolution which made my computer's Current Timer Resolution from 1ms to 0.5ms.

So i do not recall having these "Parent" permissions and i am pretty sure it is from the debloater since i found out about them since i could not enter the Windows Apps Folder.

Can someone please help me remove them cause i am trying to solve this stuttering problem 3 days now..
Thanks in advance!

hmm so far i don't think it debloater at least no one else has report this issue so far and i even testing on other machine to see if something similar to this issue will happen but nothing wrong happened and that parent permission is not debloater based on script it never change it permission it use powershell Remove-AppxPackage to remove apps also windows apps folder is locked by os by default because it sandbox area for apps.
i wonder did you had any windows updates  or drivers updates happen before the issue?

Right before the issue, no... After the issue i tried to access a manual restore point i created which came to be corrupted (i left it for an hour). After that since the in-game stuttering persisted i made a clean installation of the Nvidia Drivers (removed with DDU) and after i saw that did not work either i did a windows update. Also between all these steps i have used "sfc /scannow" and the "DISM RestoreHealth". Well from some more digging i did, COD Warzone has the option to show CPU and GPU Time and while the Frame spikes, stuttering was occuring, it was when the CPU Time was going >50ms from ~10ms where it usually stands.
John thank you for testing but it seems i might have to do a clean installation of Windows and see if that fixes it. The problem might not be the debloater but maybe something else..

Ok guys, i reinstalled my Windows while keeping files and apps and everything seems to work fine.
If you want you can delete this thread since it was a personal issue that was not resolved.


in regards to cache

in regards to cache lets say company x had quarterly report or next day price change will it go get the new data or will it get it from the cache?

requests_cache ?

financials will update
prices may update, depends how you request. history(period="1d") = no. history(start=today) = yes


data is too much or too fast refresh rate of data

When the data is too much or too fast refresh rate of data occurs when the "Collection was modified; enumeration operation may not execute", this is a BUG or to limit the data and refresh rate?

How much is too fast?
Right now the updater is fired only every time animations finishes, in the next example I exmplain a bit how it works
http://lvcharts.net/App/examples/v1/wpf/Constant Changes

I have the same issue, i update my data from another thread and sometimes it got too fast, like every 50ms, in this case the lvcharts crash.

I found the problem, on ChartValues Class -> Iterate method, I changed the this, to this.ToList(), fixed the problem for me, I know that is not the best workaround, but worked. #260

Hello, any news on this, the problem is still ocurring?
Because for me it´s not a problem anymore and I´m using a lot of charts at same time with refresh rate about 300ms...

I actually was never able to reproduce this error, based on your comments it was fixed. I added the in progress label and reopened the issue because I am testing the performance in your workaround .ToList(), it does not have an important impact in performance in the next version (0.7.12) and brings more stability when working with async operations(based on your feedback)

Ok!, but If someone have the same problem again I can help to find a better way to fix it, if necessary.

This helps as feedback for #336


Html5 download tag

Hello,
I was wondering if the AdvancedWebView supports this kind of html

Because when I click on it nothing happen and it works perfectly on chrome and other browsers.
There is anything specify that I have to do to make it work?
Thanks!

Good question! Thank you :)
According to this resource, it should actually work in WebView since Android 4.4.
Someone reported an issue for Chromium (which backs the WebView since Android 4.4) but they say that it works.
Then again, when I open this page in the WebView, there's nothing happening, either. Same result as you have.

Yeah I think it doesn't work because I tired everything possible and in the end I just set the heading on my API to when access that link it download the image and works great.

Thanks for the update :)
It seems we cannot do anything here, unfortunately, so we're changing this issue to "won't fix".


Is yarn necessary?

We should aim to keep the cognitive overhead as low as possible for creating and managing extensions. Many people who create extensions will not be intimately familiar with the JS ecosystem, or care to learn several tools just to get started.
The extension template is created with yarn by default, which might be nice for power users, but requires an understanding of what npm is before you can even use it. Googling yarn issues results in a confusing collection of yarn 1 docs, yarn 2 docs, and occasionally places where you need to just read the npm docs and then guess at what yarn is doing.
I would advocate for bootstrapping npm out of the box to make things simpler for the user, unless there is a strict reason we need yarn. People who want to use yarn will know enough to infer the commands they should use.

Relevant: https://www.npmjs.com/package/yarpm

I think we should stick to yarn for now since we use it for all our own stuff. I agree the yarn v1 v2 v3 is a nightmare but not something to tackle for now. npm has its own annoyances but maybe now that it is under a company that can fund and develop it we will see it be a viable option.


Added Try catch block to API and plugin template with method name

Multiple lines are present that are not tested well.


add new arabic course

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Read our contributing guidelines
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction)

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Recreate https://github.com/EbookFoundation/free-programming-books/pull/6765

Thanks for carry on completing Arabic resources


fix(#17): handles array elements having objects

Fixes #17.
Changes

We are going back to what we were doing pre #15, except that on top of checking first.

const parentKeyToFullyRestore = setPropertiesDuringUpdate.find(
        (userSet) => key.startsWith(`${userSet}.`),
      );
      if (parentKeyToFullyRestore) {
        // ...
      }

I added && parentKeyToFullyRestore in backup as well.

Adds a test to cover this case.

@pp0rtal I'll let you update the changelog to your liking (it's an actually an excuse because I'm too tired to find one 🫣) and merge when you want. All of my tests ran successfully, so I think we should be okay.


Add CC

Attempt to activate CC on PR.

fix pep8, indent 4

Fixed CC. activated too. now CI and CC are required for PR


feat(IAM Policy Management): add service to project

PR summary
This PR adds the IAM Policy Management service to the project.
Fixes: n/a
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No## PR summary

Fixes: <! -- link to issue -->
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Other information

:tada: This PR is included in version 0.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Venue recruitment: "Invalid group id" when the invitee is an email address with uppercase

This issue happened with NeurIPS 2023 SAC recruitment, the PCs sent the invitation to an email address with uppercase, the user was invited and added to the group correctly but the url contained the email in uppercase.
I think the bug is when creating the url and the hash key we should send the email all in lowercase.

I was getting another error when trying to send the email, since the lower case email was being added to the group:

so why is it working in the live site?
https://openreview.net/forum?id=u4QodE3u4r&noteId=d2yfaVgCbY


[请求帮助] error:timeout: no recent network activity

问题详情
使用广西电信连接会出现这个，重试几千次就好了，上传速度3.70Mbps，下载速度107.45Mbps，使用江西移动不，上传下载均为199Mbps，我怀疑是延迟过高导致还未等到应答包就超时了
服务端安装信息或者一键脚本信息
hysteria version v1.2.1 2022-09-10T01:25:46.128Z 03e397b152134419d0ed4cb0565328fd81bd29f7
VPS 信息
搬瓦工美国Los Angeles, California (DC2 QNET) [USCA_2]
服务端配置
{
"listen": ":443",
"obfs": "I am your father1337",
"cert": "/etc/letsencrypt/live/testserver1.mckuhei.ml/fullchain.pem",
"key": "/etc/letsencrypt/live/testserver1.mckuhei.ml/privkey.pem"
}
服务端日志
2022-10-08T07:29:49Z [INFO] [addr::443] Server up and running
无其他日志
客户端安装信息
hysteria version v1.2.1 2022-09-10T01:25:46.128Z 03e397b152134419d0ed4cb0565328fd81bd29f7
客户端配置
{
"server": "example.com:443",
"obfs": "I am your father1337",
"up_mbps": 1000,
"down_mbps": 1000,
"Retry": 99999999,
"socks5": {
"listen": "<IP_ADDRESS>:1080"
},
"http": {
"listen": "<IP_ADDRESS>:8080"
}
}
客户端运行环境（操作系统）
Windows 10
客户端日志
2022-10-08T15:12:35+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:12:35+08:00 [INFO] [retry:1] [interval:0] Retrying...
2022-10-08T15:12:40+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:12:40+08:00 [INFO] [retry:2] [interval:0] Retrying...
2022-10-08T15:12:45+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:12:45+08:00 [INFO] [retry:3] [interval:0] Retrying...
2022-10-08T15:12:50+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:12:50+08:00 [INFO] [retry:4] [interval:0] Retrying...
2022-10-08T15:12:55+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:13:03+08:00 [INFO] [retry:5] [interval:0] Retrying...
2022-10-08T15:13:08+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:13:08+08:00 [INFO] [retry:6] [interval:0] Retrying...
2022-10-08T15:13:13+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:13:13+08:00 [INFO] [retry:7] [interval:0] Retrying...
2022-10-08T15:13:18+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:13:18+08:00 [INFO] [retry:8] [interval:0] Retrying...
2022-10-08T15:13:23+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:13:23+08:00 [INFO] [retry:9] [interval:0] Retrying...
2022-10-08T15:13:28+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:13:28+08:00 [INFO] [retry:10] [interval:0] Retrying...
2022-10-08T15:13:33+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:13:33+08:00 [INFO] [retry:11] [interval:0] Retrying...
2022-10-08T15:13:39+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:13:39+08:00 [INFO] [retry:12] [interval:0] Retrying...
2022-10-08T15:13:44+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:13:44+08:00 [INFO] [retry:13] [interval:0] Retrying...
2022-10-08T15:13:49+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:13:49+08:00 [INFO] [retry:14] [interval:0] Retrying...
2022-10-08T15:13:54+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:13:54+08:00 [INFO] [retry:15] [interval:0] Retrying...
2022-10-08T15:13:59+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:13:59+08:00 [INFO] [retry:16] [interval:0] Retrying...
2022-10-08T15:14:04+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:14:04+08:00 [INFO] [retry:17] [interval:0] Retrying...
2022-10-08T15:14:09+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:14:09+08:00 [INFO] [retry:18] [interval:0] Retrying...
2022-10-08T15:14:14+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:14:14+08:00 [INFO] [retry:19] [interval:0] Retrying...
2022-10-08T15:14:19+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:14:19+08:00 [INFO] [retry:20] [interval:0] Retrying...
2022-10-08T15:14:24+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:14:24+08:00 [INFO] [retry:21] [interval:0] Retrying...
2022-10-08T15:14:29+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:14:29+08:00 [INFO] [retry:22] [interval:0] Retrying...
2022-10-08T15:14:34+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:14:34+08:00 [INFO] [retry:23] [interval:0] Retrying...
2022-10-08T15:14:39+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:14:39+08:00 [INFO] [retry:24] [interval:0] Retrying...
2022-10-08T15:14:44+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:14:44+08:00 [INFO] [retry:25] [interval:0] Retrying...
2022-10-08T15:14:49+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:14:49+08:00 [INFO] [retry:26] [interval:0] Retrying...
2022-10-08T15:14:54+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:14:54+08:00 [INFO] [retry:27] [interval:0] Retrying...
2022-10-08T15:14:59+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:14:59+08:00 [INFO] [retry:28] [interval:0] Retrying...
2022-10-08T15:15:04+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:15:04+08:00 [INFO] [retry:29] [interval:0] Retrying...
2022-10-08T15:15:09+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:15:09+08:00 [INFO] [retry:30] [interval:0] Retrying...
2022-10-08T15:15:14+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:15:14+08:00 [INFO] [retry:31] [interval:0] Retrying...
2022-10-08T15:15:19+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:15:19+08:00 [INFO] [retry:32] [interval:0] Retrying...
2022-10-08T15:15:24+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:15:24+08:00 [INFO] [retry:33] [interval:0] Retrying...
2022-10-08T15:15:29+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:15:29+08:00 [INFO] [retry:34] [interval:0] Retrying...
2022-10-08T15:15:34+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:15:34+08:00 [INFO] [retry:35] [interval:0] Retrying...
2022-10-08T15:15:39+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:15:39+08:00 [INFO] [retry:36] [interval:0] Retrying...
2022-10-08T15:15:44+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:15:44+08:00 [INFO] [retry:37] [interval:0] Retrying...
2022-10-08T15:15:49+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:15:49+08:00 [INFO] [retry:38] [interval:0] Retrying...
2022-10-08T15:15:54+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:15:54+08:00 [INFO] [retry:39] [interval:0] Retrying...
2022-10-08T15:15:59+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:15:59+08:00 [INFO] [retry:40] [interval:0] Retrying...
2022-10-08T15:16:04+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:16:04+08:00 [INFO] [retry:41] [interval:0] Retrying...
2022-10-08T15:16:09+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:16:09+08:00 [INFO] [retry:42] [interval:0] Retrying...
2022-10-08T15:16:14+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:16:14+08:00 [INFO] [retry:43] [interval:0] Retrying...
2022-10-08T15:16:19+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:16:19+08:00 [INFO] [retry:44] [interval:0] Retrying...
2022-10-08T15:16:24+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:16:24+08:00 [INFO] [retry:45] [interval:0] Retrying...
2022-10-08T15:16:29+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:16:29+08:00 [INFO] [retry:46] [interval:0] Retrying...
2022-10-08T15:16:34+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:16:34+08:00 [INFO] [retry:47] [interval:0] Retrying...
2022-10-08T15:16:39+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:16:39+08:00 [INFO] [retry:48] [interval:0] Retrying...
2022-10-08T15:16:44+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:16:44+08:00 [INFO] [retry:49] [interval:0] Retrying...
2022-10-08T15:16:49+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:16:49+08:00 [INFO] [retry:50] [interval:0] Retrying...
2022-10-08T15:16:55+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:16:55+08:00 [INFO] [retry:51] [interval:0] Retrying...
2022-10-08T15:17:00+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:17:00+08:00 [INFO] [retry:52] [interval:0] Retrying...
2022-10-08T15:17:05+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:17:05+08:00 [INFO] [retry:53] [interval:0] Retrying...
2022-10-08T15:17:10+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:17:10+08:00 [INFO] [retry:54] [interval:0] Retrying...
2022-10-08T15:17:15+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:17:15+08:00 [INFO] [retry:55] [interval:0] Retrying...
2022-10-08T15:17:20+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:17:20+08:00 [INFO] [retry:56] [interval:0] Retrying...
2022-10-08T15:17:25+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:17:25+08:00 [INFO] [retry:57] [interval:0] Retrying...
2022-10-08T15:17:30+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:17:30+08:00 [INFO] [retry:58] [interval:0] Retrying...
2022-10-08T15:17:35+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:17:35+08:00 [INFO] [retry:59] [interval:0] Retrying...
2022-10-08T15:17:40+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:17:40+08:00 [INFO] [retry:60] [interval:0] Retrying...
2022-10-08T15:17:45+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:17:45+08:00 [INFO] [retry:61] [interval:0] Retrying...
2022-10-08T15:17:50+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:17:50+08:00 [INFO] [retry:62] [interval:0] Retrying...
2022-10-08T15:17:55+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:17:55+08:00 [INFO] [retry:63] [interval:0] Retrying...
2022-10-08T15:18:00+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:18:00+08:00 [INFO] [retry:64] [interval:0] Retrying...
2022-10-08T15:18:05+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:18:05+08:00 [INFO] [retry:65] [interval:0] Retrying...
2022-10-08T15:18:10+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:18:10+08:00 [INFO] [retry:66] [interval:0] Retrying...
2022-10-08T15:18:15+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:18:15+08:00 [INFO] [retry:67] [interval:0] Retrying...
2022-10-08T15:18:20+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:18:20+08:00 [INFO] [retry:68] [interval:0] Retrying...
2022-10-08T15:18:25+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:18:25+08:00 [INFO] [retry:69] [interval:0] Retrying...
2022-10-08T15:18:30+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:18:30+08:00 [INFO] [retry:70] [interval:0] Retrying...
2022-10-08T15:18:35+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:18:35+08:00 [INFO] [retry:71] [interval:0] Retrying...
2022-10-08T15:18:40+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:18:40+08:00 [INFO] [retry:72] [interval:0] Retrying...
2022-10-08T15:18:45+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:18:45+08:00 [INFO] [retry:73] [interval:0] Retrying...
2022-10-08T15:18:50+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:18:50+08:00 [INFO] [retry:74] [interval:0] Retrying...
2022-10-08T15:18:55+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:18:55+08:00 [INFO] [retry:75] [interval:0] Retrying...
2022-10-08T15:19:00+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:19:00+08:00 [INFO] [retry:76] [interval:0] Retrying...
2022-10-08T15:19:05+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:19:05+08:00 [INFO] [retry:77] [interval:0] Retrying...
2022-10-08T15:19:10+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:19:10+08:00 [INFO] [retry:78] [interval:0] Retrying...
2022-10-08T15:19:15+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:19:15+08:00 [INFO] [retry:79] [interval:0] Retrying...
2022-10-08T15:19:20+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:19:20+08:00 [INFO] [retry:80] [interval:0] Retrying...
2022-10-08T15:19:26+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:19:26+08:00 [INFO] [retry:81] [interval:0] Retrying...
2022-10-08T15:19:31+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:19:31+08:00 [INFO] [retry:82] [interval:0] Retrying...
2022-10-08T15:19:36+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:19:36+08:00 [INFO] [retry:83] [interval:0] Retrying...
2022-10-08T15:19:41+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:19:41+08:00 [INFO] [retry:84] [interval:0] Retrying...
2022-10-08T15:19:46+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:19:46+08:00 [INFO] [retry:85] [interval:0] Retrying...
2022-10-08T15:19:51+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:19:51+08:00 [INFO] [retry:86] [interval:0] Retrying...
2022-10-08T15:19:56+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:19:56+08:00 [INFO] [retry:87] [interval:0] Retrying...
2022-10-08T15:20:01+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:20:01+08:00 [INFO] [retry:88] [interval:0] Retrying...
2022-10-08T15:20:06+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:20:06+08:00 [INFO] [retry:89] [interval:0] Retrying...
2022-10-08T15:20:11+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:20:11+08:00 [INFO] [retry:90] [interval:0] Retrying...
2022-10-08T15:20:16+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:20:16+08:00 [INFO] [retry:91] [interval:0] Retrying...
2022-10-08T15:20:21+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:20:21+08:00 [INFO] [retry:92] [interval:0] Retrying...
2022-10-08T15:20:26+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:20:26+08:00 [INFO] [retry:93] [interval:0] Retrying...
2022-10-08T15:20:31+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:20:31+08:00 [INFO] [retry:94] [interval:0] Retrying...
2022-10-08T15:20:36+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:20:36+08:00 [INFO] [retry:95] [interval:0] Retrying...
2022-10-08T15:20:41+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:20:41+08:00 [INFO] [retry:96] [interval:0] Retrying...
2022-10-08T15:20:46+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:20:46+08:00 [INFO] [retry:97] [interval:0] Retrying...
2022-10-08T15:20:51+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:20:51+08:00 [INFO] [retry:98] [interval:0] Retrying...
2022-10-08T15:20:56+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:20:56+08:00 [INFO] [retry:99] [interval:0] Retrying...
2022-10-08T15:21:01+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:21:01+08:00 [INFO] [retry:100] [interval:0] Retrying...
2022-10-08T15:21:06+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:21:06+08:00 [INFO] [retry:101] [interval:0] Retrying...
2022-10-08T15:21:11+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:21:11+08:00 [INFO] [retry:102] [interval:0] Retrying...
2022-10-08T15:21:16+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:21:16+08:00 [INFO] [retry:103] [interval:0] Retrying...
2022-10-08T15:21:21+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:21:21+08:00 [INFO] [retry:104] [interval:0] Retrying...
2022-10-08T15:21:26+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:21:26+08:00 [INFO] [retry:105] [interval:0] Retrying...
2022-10-08T15:21:31+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:21:31+08:00 [INFO] [retry:106] [interval:0] Retrying...
2022-10-08T15:21:36+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:21:36+08:00 [INFO] [retry:107] [interval:0] Retrying...
2022-10-08T15:21:41+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:21:41+08:00 [INFO] [retry:108] [interval:0] Retrying...
2022-10-08T15:21:46+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:21:46+08:00 [INFO] [retry:109] [interval:0] Retrying...
2022-10-08T15:21:51+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:21:51+08:00 [INFO] [retry:110] [interval:0] Retrying...
2022-10-08T15:21:56+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:21:56+08:00 [INFO] [retry:111] [interval:0] Retrying...
2022-10-08T15:22:01+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:22:01+08:00 [INFO] [retry:112] [interval:0] Retrying...
2022-10-08T15:22:06+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:22:06+08:00 [INFO] [retry:113] [interval:0] Retrying...
2022-10-08T15:22:11+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:22:11+08:00 [INFO] [retry:114] [interval:0] Retrying...
2022-10-08T15:22:16+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:22:16+08:00 [INFO] [retry:115] [interval:0] Retrying...
2022-10-08T15:22:21+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:22:21+08:00 [INFO] [retry:116] [interval:0] Retrying...
2022-10-08T15:22:27+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:22:27+08:00 [INFO] [retry:117] [interval:0] Retrying...
2022-10-08T15:22:32+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:22:32+08:00 [INFO] [retry:118] [interval:0] Retrying...
2022-10-08T15:22:37+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:22:37+08:00 [INFO] [retry:119] [interval:0] Retrying...
2022-10-08T15:22:42+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:22:42+08:00 [INFO] [retry:120] [interval:0] Retrying...
2022-10-08T15:22:47+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:22:47+08:00 [INFO] [retry:121] [interval:0] Retrying...
2022-10-08T15:22:52+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:22:52+08:00 [INFO] [retry:122] [interval:0] Retrying...
2022-10-08T15:22:57+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:22:57+08:00 [INFO] [retry:123] [interval:0] Retrying...
2022-10-08T15:23:02+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:23:02+08:00 [INFO] [retry:124] [interval:0] Retrying...
2022-10-08T15:23:07+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:23:07+08:00 [INFO] [retry:125] [interval:0] Retrying...
2022-10-08T15:23:12+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:23:12+08:00 [INFO] [retry:126] [interval:0] Retrying...
2022-10-08T15:23:17+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:23:17+08:00 [INFO] [retry:127] [interval:0] Retrying...
2022-10-08T15:23:22+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:23:22+08:00 [INFO] [retry:128] [interval:0] Retrying...
2022-10-08T15:23:27+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:23:27+08:00 [INFO] [retry:129] [interval:0] Retrying...
2022-10-08T15:23:32+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:23:32+08:00 [INFO] [retry:130] [interval:0] Retrying...
2022-10-08T15:23:37+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:23:37+08:00 [INFO] [retry:131] [interval:0] Retrying...
2022-10-08T15:23:42+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:23:42+08:00 [INFO] [retry:132] [interval:0] Retrying...
2022-10-08T15:23:47+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:23:47+08:00 [INFO] [retry:133] [interval:0] Retrying...
2022-10-08T15:23:52+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:23:52+08:00 [INFO] [retry:134] [interval:0] Retrying...
2022-10-08T15:23:57+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:23:57+08:00 [INFO] [retry:135] [interval:0] Retrying...
2022-10-08T15:24:02+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:24:02+08:00 [INFO] [retry:136] [interval:0] Retrying...
2022-10-08T15:24:07+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:24:08+08:00 [INFO] [retry:137] [interval:0] Retrying...
2022-10-08T15:24:13+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:24:13+08:00 [INFO] [retry:138] [interval:0] Retrying...
2022-10-08T15:24:18+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:24:18+08:00 [INFO] [retry:139] [interval:0] Retrying...
2022-10-08T15:24:23+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:24:23+08:00 [INFO] [retry:140] [interval:0] Retrying...
2022-10-08T15:24:28+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:24:28+08:00 [INFO] [retry:141] [interval:0] Retrying...
2022-10-08T15:24:33+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:24:33+08:00 [INFO] [retry:142] [interval:0] Retrying...
2022-10-08T15:24:38+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:24:38+08:00 [INFO] [retry:143] [interval:0] Retrying...
2022-10-08T15:24:43+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:24:43+08:00 [INFO] [retry:144] [interval:0] Retrying...
2022-10-08T15:24:48+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:24:48+08:00 [INFO] [retry:145] [interval:0] Retrying...
2022-10-08T15:24:53+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:24:53+08:00 [INFO] [retry:146] [interval:0] Retrying...
2022-10-08T15:24:58+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:24:58+08:00 [INFO] [retry:147] [interval:0] Retrying...
2022-10-08T15:25:03+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:25:03+08:00 [INFO] [retry:148] [interval:0] Retrying...
2022-10-08T15:25:08+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:25:08+08:00 [INFO] [retry:149] [interval:0] Retrying...
2022-10-08T15:25:13+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:25:13+08:00 [INFO] [retry:150] [interval:0] Retrying...
2022-10-08T15:25:18+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:25:18+08:00 [INFO] [retry:151] [interval:0] Retrying...
2022-10-08T15:25:23+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:25:23+08:00 [INFO] [retry:152] [interval:0] Retrying...
2022-10-08T15:25:28+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:25:28+08:00 [INFO] [retry:153] [interval:0] Retrying...
2022-10-08T15:25:33+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:25:33+08:00 [INFO] [retry:154] [interval:0] Retrying...
2022-10-08T15:25:38+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:25:38+08:00 [INFO] [retry:155] [interval:0] Retrying...
2022-10-08T15:25:43+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:25:43+08:00 [INFO] [retry:156] [interval:0] Retrying...
2022-10-08T15:25:48+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:25:48+08:00 [INFO] [retry:157] [interval:0] Retrying...
2022-10-08T15:25:53+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:25:53+08:00 [INFO] [retry:158] [interval:0] Retrying...
2022-10-08T15:25:58+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:25:58+08:00 [INFO] [retry:159] [interval:0] Retrying...
2022-10-08T15:26:03+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:26:03+08:00 [INFO] [retry:160] [interval:0] Retrying...
2022-10-08T15:26:08+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:26:08+08:00 [INFO] [retry:161] [interval:0] Retrying...
2022-10-08T15:26:13+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:26:13+08:00 [INFO] [retry:162] [interval:0] Retrying...
2022-10-08T15:26:18+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:26:18+08:00 [INFO] [retry:163] [interval:0] Retrying...
2022-10-08T15:26:23+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:26:23+08:00 [INFO] [retry:164] [interval:0] Retrying...
2022-10-08T15:26:28+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:26:28+08:00 [INFO] [retry:165] [interval:0] Retrying...
2022-10-08T15:26:33+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:26:33+08:00 [INFO] [retry:166] [interval:0] Retrying...
2022-10-08T15:26:38+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:26:38+08:00 [INFO] [retry:167] [interval:0] Retrying...
2022-10-08T15:26:43+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:26:43+08:00 [INFO] [retry:168] [interval:0] Retrying...
2022-10-08T15:26:48+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:26:48+08:00 [INFO] [retry:169] [interval:0] Retrying...
2022-10-08T15:26:53+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:26:53+08:00 [INFO] [retry:170] [interval:0] Retrying...
2022-10-08T15:26:58+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:26:58+08:00 [INFO] [retry:171] [interval:0] Retrying...
2022-10-08T15:27:03+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:27:03+08:00 [INFO] [retry:172] [interval:0] Retrying...
2022-10-08T15:27:08+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:27:08+08:00 [INFO] [retry:173] [interval:0] Retrying...
2022-10-08T15:27:13+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:27:13+08:00 [INFO] [retry:174] [interval:0] Retrying...
2022-10-08T15:27:18+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:27:18+08:00 [INFO] [retry:175] [interval:0] Retrying...
2022-10-08T15:27:24+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:27:24+08:00 [INFO] [retry:176] [interval:0] Retrying...
2022-10-08T15:27:29+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:27:29+08:00 [INFO] [retry:177] [interval:0] Retrying...
2022-10-08T15:27:34+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:27:34+08:00 [INFO] [retry:178] [interval:0] Retrying...
2022-10-08T15:27:39+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:27:39+08:00 [INFO] [retry:179] [interval:0] Retrying...
2022-10-08T15:27:44+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:27:44+08:00 [INFO] [retry:180] [interval:0] Retrying...
2022-10-08T15:27:49+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:27:49+08:00 [INFO] [retry:181] [interval:0] Retrying...
2022-10-08T15:27:54+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:27:54+08:00 [INFO] [retry:182] [interval:0] Retrying...
2022-10-08T15:27:59+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:27:59+08:00 [INFO] [retry:183] [interval:0] Retrying...
2022-10-08T15:28:04+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:28:04+08:00 [INFO] [retry:184] [interval:0] Retrying...
2022-10-08T15:28:09+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:28:09+08:00 [INFO] [retry:185] [interval:0] Retrying...
2022-10-08T15:28:14+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:28:14+08:00 [INFO] [retry:186] [interval:0] Retrying...
2022-10-08T15:28:19+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:28:19+08:00 [INFO] [retry:187] [interval:0] Retrying...
2022-10-08T15:28:24+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:28:24+08:00 [INFO] [retry:188] [interval:0] Retrying...
2022-10-08T15:28:29+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:28:29+08:00 [INFO] [retry:189] [interval:0] Retrying...
2022-10-08T15:28:34+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:28:34+08:00 [INFO] [retry:190] [interval:0] Retrying...
2022-10-08T15:28:39+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:28:39+08:00 [INFO] [retry:191] [interval:0] Retrying...
2022-10-08T15:28:44+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:28:44+08:00 [INFO] [retry:192] [interval:0] Retrying...
2022-10-08T15:28:49+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:28:49+08:00 [INFO] [retry:193] [interval:0] Retrying...
2022-10-08T15:28:54+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:28:54+08:00 [INFO] [retry:194] [interval:0] Retrying...
2022-10-08T15:28:59+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:28:59+08:00 [INFO] [retry:195] [interval:0] Retrying...
2022-10-08T15:29:04+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:29:04+08:00 [INFO] [retry:196] [interval:0] Retrying...
2022-10-08T15:29:09+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:29:09+08:00 [INFO] [retry:197] [interval:0] Retrying...
2022-10-08T15:29:14+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:29:14+08:00 [INFO] [retry:198] [interval:0] Retrying...
2022-10-08T15:29:19+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:29:19+08:00 [INFO] [retry:199] [interval:0] Retrying...
2022-10-08T15:29:24+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:29:24+08:00 [INFO] [retry:200] [interval:0] Retrying...
2022-10-08T15:29:29+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:29:29+08:00 [INFO] [retry:201] [interval:0] Retrying...
2022-10-08T15:29:34+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:29:34+08:00 [INFO] [retry:202] [interval:0] Retrying...
2022-10-08T15:29:39+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:29:39+08:00 [INFO] [retry:203] [interval:0] Retrying...
2022-10-08T15:29:44+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:29:44+08:00 [INFO] [retry:204] [interval:0] Retrying...
2022-10-08T15:29:49+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:29:49+08:00 [INFO] [retry:205] [interval:0] Retrying...
2022-10-08T15:29:54+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:29:54+08:00 [INFO] [retry:206] [interval:0] Retrying...
2022-10-08T15:30:00+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:30:00+08:00 [INFO] [retry:207] [interval:0] Retrying...
2022-10-08T15:30:05+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:30:05+08:00 [INFO] [retry:208] [interval:0] Retrying...
2022-10-08T15:30:10+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:30:10+08:00 [INFO] [retry:209] [interval:0] Retrying...
2022-10-08T15:30:15+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:30:15+08:00 [INFO] [retry:210] [interval:0] Retrying...
2022-10-08T15:30:20+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:30:20+08:00 [INFO] [retry:211] [interval:0] Retrying...
2022-10-08T15:30:25+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:30:25+08:00 [INFO] [retry:212] [interval:0] Retrying...
2022-10-08T15:30:30+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:30:30+08:00 [INFO] [retry:213] [interval:0] Retrying...
2022-10-08T15:30:35+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:30:35+08:00 [INFO] [retry:214] [interval:0] Retrying...
2022-10-08T15:30:40+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:30:40+08:00 [INFO] [retry:215] [interval:0] Retrying...
2022-10-08T15:30:45+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:30:45+08:00 [INFO] [retry:216] [interval:0] Retrying...
2022-10-08T15:30:50+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:30:50+08:00 [INFO] [retry:217] [interval:0] Retrying...
2022-10-08T15:30:55+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:30:55+08:00 [INFO] [retry:218] [interval:0] Retrying...
2022-10-08T15:31:00+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:31:00+08:00 [INFO] [retry:219] [interval:0] Retrying...
2022-10-08T15:31:05+08:00 [ERRO] [error:timeout: no recent network activity] Failed to initialize client
2022-10-08T15:31:05+08:00 [INFO] [retry:220] [interval:0] Retrying...

今天突然也遇到这个问题，之前用着好好的

今天突然也遇到这个问题，之前用着好好的

防火长城现在会阻断UDP了

防火长城现在会阻断UDP了
意思是要打开fake TCP？这个no recent network activity我遇到有一段时间了，不定期发作。

防火长城现在会阻断UDP了

意思是要打开fake TCP？这个no recent network activity我遇到有一段时间了，不定期发作。

很奇怪，我用SagerNet有这个问题，Matsuri又正常

我这边hysteria是Windows版cli客户端会出no recent network activity，SagerNet会timeout。但在8443端口上运行的另一种quic代理没有问题，不知道是端口号的功劳还是程序的功劳。

Adding "protocol": "faketcp" to both your client and server configuration should resolve the issue. See more detail at https://github.com/HyNetwork/hysteria/wiki/Advanced-Usage

Adding "protocol": "faketcp" to both your client and server configuration should resolve the issue. See more detail at https://github.com/HyNetwork/hysteria/wiki/Advanced-Usage

你说了一个windows不支持的协议，然并卵
https://github.com/HyNetwork/hysteria/issues/456#issuecomment-1300160700

Adding "protocol": "faketcp" to both your client and server configuration should resolve the issue. See more detail at https://github.com/HyNetwork/hysteria/wiki/Advanced-Usage

你说了一个windows不支持的协议，然并卵 #456 (comment)

How about WSL

faketcp 同样出现这个问题，客户端是Android上的clash.meta

你服务端是不是centos7系统？我试过centos7系统都不行，centos8以上可以。用nc或socat测试过，centos7更新kernel后udp收包都有问题。

你服务端是不是centos7系统？我试过centos7系统都不行，centos8以上可以。用nc或socat测试过，centos7更新kernel后udp收包都有问题。

我使用的是乌班图，而且我这个是电信连不上，移动可以

你服务端是不是centos7系统？我试过centos7系统都不行，centos8以上可以。用nc或socat测试过，centos7更新kernel后udp收包都有问题。

我使用的是乌班图，而且我这个是电信连不上，移动可以

哦，那你试过更新版本的ubuntu吗

你服务端是不是centos7系统？我试过centos7系统都不行，centos8以上可以。用nc或socat测试过，centos7更新kernel后udp收包都有问题。

我使用的是乌班图，而且我这个是电信连不上，移动可以
我的情况也是如此，电信的手机卡和电信的宽带都不行，移动的手机卡和移动的宽带都可能正常使用。应该是运营商进行了UDP阻断。

使用端口跳跃可以缓解该现象

中国移动一般不QoS，但是有的时候会，比如说现在

我昨天也遇到这个问题了。不过我发现是因为的域名绑定的ip变了。
重新绑定一下ip就好了，你看看你的是不是也是这样的。

我是Mac端出现的这个问题

感觉和墙关系不大，windows系统出现这个问题，换成IOS系统小火箭连接正常

感觉和墙关系不大，windows系统出现这个问题，换成IOS系统小火箭连接正常

协议是Fake TCP吗？如果是就很正常，因为Windows的rawsocket不允许发送TCP协议，除非是Windows server，没试过用Windows server的tcpip.sys替换掉原本的tcpip.sys

On Sat, May 20, 2023 at 11:31 Minecraftku_hei @.***>
wrote:

感觉和墙关系不大，windows系统出现这个问题，换成IOS系统小火箭连接正常
协议是Fake TCP吗？如果是就很正常，因为Windows的rawsocket不允许发送TCP协议，除非是Windows
server，没试过用Windows server的tcpip.sys替换掉原本的tcpip.sys
—
Reply to this email directly, view it on GitHub
https://github.com/apernet/hysteria/issues/456#issuecomment-1555452743,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A65INDFAR3RJZDQBVKUVODDXHA3IBANCNFSM6AAAAAARAESDUA
.
You are receiving this because you commented.Message ID:
@.***>

不是，就是udp的，不过我有几个vps，只有一个出现这个问题，其他正常，怀疑和linux版本也有关系

你服务端是不是centos7系统？我试过centos7系统都不行，centos8以上可以。用nc或socat测试过，centos7更新kernel后udp收包都有问题。

太感谢了，虽然不是所有人都是这个问题，但我是，搞了一两天centos7，终于通了

你服务端是不是centos7系统？我试过centos7系统都不行，centos8以上可以。用nc或socat测试过，centos7更新kernel后udp收包都有问题。

centos7确实容易出这个问题，偶尔能连得上偶尔又连不上的，特别玄学。


[T4A1][T1-04]Dao Han

Created Printable interface and implemented getPrintableString functions in classes

@DaoHanLim Some comments added. Please close the PR after reading comments. Not a clean PR.


Default .zshrc file mistakenly calls all variables P9K_... instead of POWERLEVEL9K_...

Describe Your Issue
What is happening?
I have fixed the problem, but what was happening was that my initial .zshrc file used the environment variable prefix of P9K_ instead of POWERLEVEL9K_, as you can see in the screenshot below.

Have you tried to debug or fix it?
Yes, I eventually fixed this, but it was a big pain because it's one of those things you can stare at for hours and not notice, since subconsciously I kept seeing P9K as POWERLEVEL9K.
Environment Information
This information will help us understand your configuration.

What version of ZSH are you using? You can use zsh --version to see this.

zsh 5.4.2 (x86_64-ubuntu-linux-gnu)

Do you use a ZSH framework (e.g., Oh-My-ZSH, Antigen)?

Yes, Oh-My-ZSH.  I used the instructions found here to install it.  (This is a fresh install.)

How did you install P9k (cloning the repo, by tarball, a package from your OS, etc.,)?

I cannot remember now, but I think by cloning the repo.

What version of P9k are you using?

0.6.7, the newest as of June, 2019

Which terminal emulator do you use?

Terminator and the default Ubuntu terminal.  (I have Ubuntu 18.04.)

Final Note
It's unclear to me if I should change all of the P9K_... environment variables over to POWERLEVEL9K_....  So, while this bug report is mostly to report it - I have solved the major issues for myself - I would like to know whether I should fix all of these P9K_... variables in my .zshrc file.
Thanks!

Default .zshrc file mistakenly calls all variables P9K_... instead of POWERLEVEL9K_...
[...] my initial .zshrc file used the environment variable prefix of P9K_ instead of POWERLEVEL9K_

When you say "default" and "initial", what do you mean? Where did you get this .zshrc file?
Perhaps you've copied the config from https://github.com/bhilburn/powerlevel9k/wiki/Show-Off-Your-Config#p9kgt? This wiki page is community managed. None of the configs presented in there are officially endorsed, officially recommended or officially supported. This particular config is evidently for the next branch of p9k -- a bleeding edge branch with active development. You are free to use it but you'll need to have higher tolerance for bugs and breaking changes. Features from next eventually make it into master after rigorous testing. Most users are on master.
If you really want to use this config as is, run git checkout next in powerlevel9k directory. I don't recommend it though.
You can also try renaming all P9K variables to POWERLEVEL9K. Most of them will work. Some may not.

I would like to know whether I should fix all of these P9K_... variables in my .zshrc file.

Up to you. Right now these variables have no effect on your theme. If it looks fine to you, you can delete these parameters.


WIP config files

Fixes #616

[x] npm run test succeeds.
[x] npm run lint succeeds.
[ ] Appropriate changes to README are included in PR.

@grant I have made good progress on this PR.
As of now, .clasp.json and .claspignore can be overridden and renamed using environment variables and cli options.
I am about to do the same for .clasprc.json files… and maybe apps Script.json.
There are two failing tests on ‘clasp status’ which I have not yet investigated. And I have not designed automated tests for the new feature.
Please have a look and advise/comment.
If necessary, i’ll Produce a cleaner PR when ready.

@grant I am done committing on this PR for this week.
I couldn't fully test it yet but it looks "good enough" for some beta testing.
Potentially it addresses #12 #42 #483 #524 #554 & #616

Thanks for starting this, but we need to make PRs a lot smaller.
Try to creates PRs that are <100 lines long and only do 1 thing.
Ping me with @grant if you are blocked and need something merged.


pkgs/uwsgi: fix compiling and linking the php plugin in uwsgi

Motivation for this change
fixes #97352 - it enables the use of the php plugin of uwsgi.
Things done
I tested in a nixos docker container, on ArchLinux host:
$ docker run -ti --rm -v ~/src/nixpkgs:/nixpkgs nixos/nix:latest
# nix-build -E 'with import <nixpkgs> {}; uwsgi.override { plugins=[ "php" ]; }' # fails as specified in the bug 97352

# NIX_PATH=nixpkgs=/nixpkgs nix-build -E 'with import <nixpkgs> {}; uwsgi.override { plugins=[ "php" ]; }' # works

Explanation of the changes
The root of the problem is that uwsgi has a bit of a different build system, and it would expect to find the php-config binary in order to set it's compiler and linker flags. There was an additional problem that the uwsgi-php plugin needs to also link with the session.so php extension - which on NixOS is a separate package¹.
The first problem was solved by adding all the required buildInputs to the uwsgi package so that it can find all the needed header files, libraries and to have php-config in its PATH.
I also had to patch uwsgi to not look for php_session.h with a path like this #include "ext/session/php_session.h", since on NixOS it's just in …php-session-7.4.8-dev/include.
Third, I had to patch the uwsgi build system for the php plugin to explicitly add the session.so library and its rpath to LDFLAGS. In the nix expression that's exported as the UWSGICONFIG_PHP_LDFLAGS environment variable. It's important that these flags are not used for the main uwsgi binary, but just for the php-plugin shared object.
¹ not sure why the session extension is separated on NixOS, it's builtin in libphp.so on both Debian/Ubuntu and ArchLinux - something to be discussed by the PHP team i guess.
ps.
this is my first involvement with the NixOS project, so I'm open to any criticism and suggestions.

updated after the borked PR #97536

@rnhmjoj Do you know if this fil be merged with 20.09 as well? I find  it always difficult to understand that

The backport process to stable branches (20.09 now) is manual and the policy is to only backport security or bug fixes.
This PR is technically fixing PHP supports, but it's really adding a new feature and does non-trivial changes to uwsgi: I don't think it's a good idea to backport it.
If you need it, you could pick the uwsgi package from the unstable channel while staying on 20.09. I can't find a guide or example right know, if you're interested I can explain it to you.

> The backport process to stable branches (20.09 now) is manual and
> the policy is to only backport security or bug fixes.  This PR is
> technically fixing PHP supports, but it's really adding a new
> feature and does non-trivial changes to uwsgi: I don't think it's
> a good idea to backport it.

A new feature? It just fixes something that worked like a charm in 20.03 and
is broken in 20.09, it doesn't add any new functionality. It isn't a
new, incompatible, release of uwsgi. If you don't need the PHP module
nothing will change for you.
> If you need it, you could pick the uwsgi package from the unstable
> channel while staying on 20.09. I can't find a guide or example right
> know, if you're interested I can explain it to you.

There's no need, thanks. I just wanted me to save the hassle of using PHP
and other plugins from unstable.
--
Alberto Berti  -  Information Technology Consultant
PGP: 9377 A68C C5B5 B534 36BD  F20B E3B5 C559 99D6 7CF9
        "gutta cavat lapidem"

A new feature? It just fixes something that worked like a charm in 20.03 and
is broken in 20.09, it doesn't add any new functionality. It isn't a
new, incompatible, release of uwsgi. If you don't need the PHP module
nothing will change for you.

You're right, I wasn't aware the php was there before this PR...
It should be backported, then. I'll open a PR for this soon.

I can make a PR against release-20.09 too (I believe I already have a branch).
I personally do believe this needs to be fixed in 20.09, since it's the difference between completely not working and fixed :)

I can make a PR against release-20.09 too (I believe I already have a branch).

https://github.com/NixOS/nixpkgs/pull/107792


[8.x] Suggestion: fire a NotificationFailed event

Laravel has the following events for notifications:

NotificationSending
NotificationSent
NotificationFailed

NotificationSending and NotificationSent events are fired properly, but the other event NotificationFailed is not triggered at all. it just sits there in the code.
through this PR I'm exploring the possibility of firing this event when the driver fails to send the notification through the channel.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


[HUDI-7977] Improve bucket index partitioner algorithm

Change Logs
as https://github.com/apache/hudi/pull/11578 describe, current algorithm in some case has drawbacks, but this new algorithm also has drawbacks, so we can proceed based on practical considerations desgin the ut.
old algorithm:

new algorithm:

both of them perform bad case https://github.com/apache/hudi/pull/11578#issuecomment-2219339643 : partition values are discontinuous
parallelism = 10, bucketNumber = 5 and partition = ["2021-01-01", "2021-01-03"]
old: [1, 1, 1, 1, 1, 1, 1, 1, 1, 1]
new: [2, 2, 2, 2, 2]
parallelism = 20, bucketNumber = 5 and partition = ["2021-01-01", "2021-01-03"]
old: [2, 2, 2, 2, 2]
new: [1, 1, 1, 1, 1, 1, 1, 1, 1, 1]
Impact
none
Risk level (write none, low medium or high below)
low
Documentation Update
none
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@danny0405 @xicm cc:

Hi, @KnightChess , @danny0405  will changing the algorithm impact backward compatibility with existing data?

@stream2000 Should not, it only impacts the task rebalance of writers.

@stream2000  yes, as @danny0405 say.


Mouse button debounce

Description of the new feature / enhancement
You may be familiar with the following mouse buttons issue. Multiple clicks are registered in just a few milliseconds. Very annoying. If your mouse is afflicted with this probelm, you'd be glad to have a way to debounce the buttons. A human can click about 100ms. On good days 80ms. A problem mouse triggers clicks under that time. Just a few ms (<80ms). This is a good debouce time value.
Scenario when this would be used?
In my case, I had a mouse where the middle mouse button triggered a click multiple times. I use this button in browser to open links or close tabs. When I want to close a single tab, suddenly multiple tabs are closed. Very annoying...
Supporting information
In my opinion this should be a part in the OS like Windows. No one can click faster than around 100ms. It makes no sense, to pass clicks under that time. Alternative: Buy new mouse. But with a debouncer, that wouldn't be necessary. This is maybe nothing for PowerToys. This feature would be too deep into the system and similar as a keylogger. Feel free to close this. I just wanted to post this idea.

This sounds like a HW issue. I don’t see powertoys would build this feature out as well


Certifications display differently if page is reloaded

Describe the bug
The appearance of the donation message on the certification pages changes if you reload the page vs. navigating to it from within the site.  This is in addition to the style issues noted in https://github.com/freeCodeCamp/freeCodeCamp/issues/37378
To Reproduce
Steps to reproduce the behavior:

Go to your own profile (freecodecamp.org/your-user-name)
Click on a completed certification
See that the message only has a small gap at the top
Reload the page
See that the gap has grown

Expected behavior
It should not depend on how you navigate to the page.
Screenshots

vs

Context
At its heart, this is a routing problem, as discussed in https://github.com/freeCodeCamp/freeCodeCamp/pull/37471, but there's no ETA on that fix, so I think it's okay to use some extra css rules to solve this for now.

I was about to create a new issue, but I think I found a related problem...
Buttons when clicking on a cert have no hover effect or background color...

Buttons when reloading the cert page do...

@moT01 I have incorporated that in my PR now. Please check


Add support for ssh-ed25519 to jagged-ssh

This pull requests adds support for the ssh-ed25519 recipient type to the jagged-ssh module.
The SSH Ed25519 implementation follows the design of the agessh package,  using Ed25519 signing keys for encryption after converting to equivalent X25519 keys.
The implementation supports reading standard SSH Ed25519 public keys formatted according to RFC 8709 Section 4.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (6b9315c) to head (9886abb).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##                main        #7    +/-   ##
============================================
  Coverage     100.00%   100.00%
- Complexity       677       796   +119
============================================
  Files            106       131    +25
  Lines           2064      2477   +413
  Branches         180       194    +14
============================================
+ Hits            2064      2477   +413

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


feat: check fuel-core dependency version

Added a function that checks the fuel-core version in the published fuels crate against our current version. If they don't match, a message prompts the user to align the versions to avoid potential errors.
At the moment, I'm only comparing the major and minor, and I left out the patch.
Checklist

[x] I have linked to any relevant issues.
[ ] I have updated the documentation.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have added necessary labels.
[x] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[ ] I have requested a review from the relevant team or maintainers.

Waiting on some refactoring first before reviewing.

Waiting on some refactoring first before reviewing.

My mistake. This was supposed to be a draft through which I would exchange some ideas with you.

@FuelLabs/sdk-rust what do we do with this

@FuelLabs/sdk-rust what do we do with this

We need this
https://github.com/FuelLabs/fuels-rs/pull/1067


Stabilise rules RUF024-RUF026

Summary
Stabilise the following rules in the RUF category for Ruff v0.5:

mutable-fromkeys-value
unnecessary-dict-comprehension
default-factory-kwarg
parenthesize-chained-operators
unsorted-dunder-all
unsorted-dunder-slots

These rules have been in the preview category for several minor releases, and were released to users >90 days ago. There are no open issues about any of them, and there have not been any open issues about any of them for several months. I skimmed over the implementations for all of them, and they all look reasonable to me (except for one test fixture for RUF026 that wasn't testing what it was meant to be testing -- I fix that here as part of this PR).
Test Plan
cargo test

Generally looks reasonable (though we should review the ecosystem results when we can). ParenthesizeChainedOperators is the only one I'm unsure of because it's more opinionated but let's see what the ecosystem says.

unsorted-dunder-all, unsorted-dunder-slots

could also be considered very-opinionated, but I'm not sure if this should prevent us from stabalizing.

For now, I've struck the following rules (all authored by me 😭) off the list:

RUF021 (parenthesize-chained-operators)
RUF022 (unsorted-dunder-all)
RUF023 (unsorted-dunder-slots)

These rules are all working as designed, but they're all quite opinionated. Right now, it seems like promoting them to stable would be too disruptive for users who select the entire RUF category in their configuration file. Long-term, we'll need to figure out how to stabilise opinionated rules while minimising disruption for our users (which relates to our long-term ambition to rework our rule categorisation)

For now, I've struck the following rules (all authored by me 😭) off the list:

And I've now struck off RUF025 for similar reasons. Somewhat opinionated; has a fair few ecosystem hits; we can maybe consider it separately, but not for this PR...


Config Path Discovery

Is your feature request related to a problem? Please describe.
Hello, I'm running my setup as a headless pi4, therefore I'm want to run librespot-java as a system service with systemd. I haven't found a way to pass a config path to the program, therefore the program generates a new config.toml at `/´
Describe the solution you'd like
I suggest any combination of:

a command line parameter like --config /path/to/my/config.toml
a series of fixed paths that are checked before building a new file in local repository, e.i. /etc/librespot-java/config.toml , ~/.config/librespot-java/config.toml

I would also offer to provide AUR package for Arch Linux, therefore currently looking for the cleanest solutions possible.
Many thanks and best regards,
Paul

You can use --conf-file=/path/to/my/config.toml, I think that's undocumented.


Add required '--add-opens' to cli script

Kind of change

[ ] Bug fix
[x] New non-breaking feature
[ ] New breaking feature
[ ] Documentation update
[ ] Build improvement

Description
What is the goal of this pull request?
Remove WARN FilenoUtil : Native subprocess control requires open access to the JDK IO subsystem message at least when running the CLI.
How does it achieve that?
Simply adds required --add-open  options.
Are there any alternative ways to implement this?
No.
Are there any implications of this pull request? Anything a user must know?
This is not related to  https://github.com/asciidoctor/asciidoctorj/issues/1034, and does not fix it.
Issue
If this PR fixes an open issue, please add a line of the form:
Fixes #1155
Release notes
Please add a corresponding entry to the file CHANGELOG.adoc

If this is fine, I'll port to branch 2.5.x.

Thank you!
When porting this to v2.5.x, wouldn't the script fail when running with Java 8?

When porting this to v2.5.x, wouldn't the script fail when running with Java 8?

I'll test, in that case we can document it at least. We'd had a couple of questions about it in the maven plugin and at least that way we have an official statement and explanation.

Will you pull this into the v2.5.x or is there a schedule for v3?


Update README.md

For your consideration.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi, as discussed via email about 8 months ago here is my pull request for the projects list.
Best, Bruno.

Good to hear from you again @brunoebe, thanks for the addition. Merging it.

thanks!


git_custom_status:1: command not found: current_branch

I added git plugin to my zshrc and removed it after a while and i started getting this.

// , I keep getting this problem, too.

// , My problem comes from the "gallois" theme.
Maybe this is starting to get some cruft?

Hi,
Same problem with de "gallois" theme.

// , Is this problem actually fixed?

Yes, it was fixed in #4420.

// , Well, then!
I may actually start using this again.


unable to target k8s registry from local process

Is it possible to use a micro service client outside of a Kubernetes cluster?
Currently, the func NewService(opts ...micro.Option) micro.Service creates the registry via: r := kubernetes.NewRegistry() however this method takes in the opts ...registry.Option which I'm wishing to pass as registry.Addrs(...).
Also, I'm a little new to using micro, but does this also mean the Register method has to change since this client service doesn't exist as a pod?

The current implementation has a bit of friction. It's made to work only inside kubernetes itself. If you want to use a micro service client outside kubernetes but to access it internally then you'll need to set that up yourself.
A client doesn't necessarily have to register itself but if you're creating a new service and use the kubernetes registry then it will attempt to do that with the assumption that it's registering against a pod.
Things outside kubernetes should likely make requests through the api rather than attempting to access services directly.
Out of curiousity are you using micro at blackrock?

I see, thanks for the quick response! Although, I don't need this feature, it would simply speed development as I am now repeatedly building updated Docker images for a simple service client.
We aren't using micro at blackrock right now.. I'm currently experimenting with a possible integration with the argo-events project. I'm specifically interested in deploying a complete micro service on kubernetes (including deployment + service) from a master process possibly through the creation of a CRD.

Ah interesting.
Yea I think it would be useful to be able to connect from outside the cluster but we just need to find the right way.

I'll raise an issue in the go-plugins repo for enhancing the kubernetes registry to allow registering services remotely.

this is nice topic, maybe you can debug in local process

telepresence will work.

@ermazi expecting more information to share ,will u ?

@crazybber https://www.telepresence.io/

@ermazi thanks,


Performance of KAN in some image classification datasets

Compare the performance of  pykan, efficient-kan, and FastKAN with MLP on image classification tasks using the MNIST, CIFAR10, and CIFAR100 datasets.Additionally, include the differences in training time between FastKAN and efficient-kan.

Boreuseful: Thanks for the benchmark. I have one question: CIFAR10 KAN Case #1 and Case #2 have the network shape as (784, 10, 10) and (784, 20, 10). I am wondering if it is a typo in 784, because the image shape of CIFAR10 is 32 x 32 x 3.

Thanks for the benchmark! What does iterate mean? is it the number of parameter updates (aka optim.step())?

@Boreuseful Thanks for your benchmark! Could you share your code? I want to compare the performance between MLP and KAN. But i find that memory error happening if i do not resize the minist image from [1, 28, 28] to [1, 7, 7]. And the accuracy of KAN is about 77.89%, mlp is about 91.76 %. The results are blow:

Thanks for your benchmark. I have a question, how to statistic the model parameters? Is it by torchsummary?

Thanks for the results!


resume does not work in the neural case

resume function does not work as expected in the neural case;
when the system has to reload an existing checkpoint to continue training, it fail because it does not find the BPE model
Actually, the BPE model is not associated with the checkpoint.
I suggest to add the bpe model to the checkpoint state and loading it properly when needed.

I totally agree, bpe should be part of the checkpoint: saved and loaded just like model and metadata.

Since this issue has been solved by @nicolabertoldi, I am closing this issue now :)


fix: add nowait for asyncio disconnect

please check this.
relative pr https://github.com/redis/redis-py/pull/2356
without this, you can meet this

redis/asyncio/connection.py:767: TypeError

    async def send_packed_command(
        self, command: Union[bytes, str, Iterable[bytes]], check_health: bool = True
    ) -> None:
        if not self.is_connected:
            await self.connect()
        elif check_health:
            await self.check_health()

        try:
            if isinstance(command, str):
                command = command.encode()
            if isinstance(command, bytes):
                command = [command]
            if self.socket_timeout:
                await asyncio.wait_for(
                    self._send_packed_command(command), self.socket_timeout
                )
            else:
                self._writer.writelines(command)
                await self._writer.drain()
        except asyncio.TimeoutError:
            await self.disconnect(nowait=True)
            raise TimeoutError("Timeout writing to socket") from None
        except OSError as e:
            await self.disconnect(nowait=True)
            if len(e.args) == 1:
                err_no, errmsg = "UNKNOWN", e.args[0]
            else:
                err_no = e.args[0]
                errmsg = e.args[1]
            raise ConnectionError(
                f"Error {err_no} while writing to socket. {errmsg}."
            ) from e
        except Exception:
>           await self.disconnect(nowait=True)
E           TypeError: FakeConnection.disconnect() got an unexpected keyword argument 'nowait'

Can you add a test for it?

@cunla
you can test it with above 4.4.0rc2

Thx for writing this, but the test does not test the disconnect() method you changed..

I don't know what should I do.. should I have to test nowait of redis-py?
When you test with 4.4.0rc2 without this change and run test, you can see error.

Hi, as you can see, tests fail for redis-py below 4.4.
Please update your implementation to **kwargs and add a test for using this parameter.

@cunla , I did some commit.
I'm a newbie developer so I'm not sure if this is what you want

It passes, the failure is due to a github action bad permissions which I will fix separately.


h5py is required to save model

add h5py requirement
update scripts/ shell script filenames

@mindon Thanks! 😄 👍


Link spans do not respect sampling configuration

It'd be good to have some way to avoid sending a link span if you sample out the job span.
As it stands the link mode is unusable if you have any real volume, because it gets sent even if neither the span for the job nor the enqueuing request is being sent.

This has been fixed on https://github.com/carwow/honeykiq/commit/2a16f7d25b3ee55e942474ed29ed7e0d5b289f86
Link events now respect beeline sampling on the server middleware. However, because it is linking two traces, the probability of one of the traces being sampled out is high, making the link event not always useful.
Depending on your use case, my suggestion is to include a field in the serialized trace data with an identifiable name (e.g. parent.name: HomeController#index) of the parent trace. Usually that is enough to understand what is enqueuing jobs. (Currently not supported by honeykiq out of the box, so it would require custom code.)


Add Benjie to November WG

@benjie We had problem with Zoom here is new link:
https://meet.google.com/gop-aqar-ssv


UDP Packet size limit

Hi,
I faced the bellow warning in Xray SDK log:
W, [2019-07-01T03:04:35.414605 #22440]  WARN -- : failed to send payload due to Message too long - send(2)

My segment entry is over 65507bytes that is UDP payload size limit.
Do you have any solutions like splitting or cutting segment?

@bigplants Apologies for the late response. Yes the UDP limit is 64 kb so you are hitting that threshold. One way to get around this is by reducing the default https://github.com/aws/aws-xray-sdk-ruby/blob/135a9187a1f9b424c3179609906b2f4256eeda18/lib/aws-xray-sdk/streaming/default_streamer.rb#L13threshold to below 50 and see if that works.
Meanwhile can you describe your use case? Are you trying to add additional payload to your segment ?


Update "About Roc" section in README

Coverage: 93.844%. Remained the same when pulling f358ed6796b54a0202b9d76f3f36b7efa3db097e on gavv-patch-1 into 78625302f3d8c25724e4494c6cfecac03f2e2f05 on main.


[WIP] Mapping dynamic offset API

New mapping API and test to show intended usage.
No lowering yet.

Please rebase on top of master to get the builders working.


Failed to build on wsl2

[-Werror=unknown-pragmas] and
error: implicit declaration of function ‘__cpuid’ [-Werror=implicit-function-declaration]
I think I may be using the wrong gcc version to compile, I followed the instructions on the edk2 for linux compilations. I also tried to compile it using gcc7

iam getting the same error with vm ubuntu 16.04 and gcc 5.4. Everything builds without any problem only powermonkey getting an error

PowerMonkey Release 0.1.9 adds support for building with Linux/WSL2 + Clang (edk2 toolchain: CLANGDWARF)
I did not test with the gcc, but I suppose it shall work (unless something else is wrong) since clang also struggled with the MSVC-style __cpuid intrinsic. This has been replaced with our own implementation.


CPU-inference memory leak

Hi all,
I modified the project code to enable only-cpu inference, by replacing .cuda() with .cpu(), as well as not using .half() datatype, adding map_location=torch.device('cpu') to torch.load. However, the memory leak might be a problem. When I load the tacotron2 and waveglow models, and keep generating waveform from text, the cpu memory will increase all the time. For GPU inference, torch.cuda.empty_cache() will be useful to collect garbage. However for cpu inference, I can hardly find an alternative approach to release the memory. Is there anyone who has experience with it.

You can do it in 2 steps:

Generate mels with tacotron and save them to disk
Load the mels saved to disk and decode them with waveglow

@rafaelvalle That solves the problem. Thank you! Closing it.


Add a search box to the imported projects table

make it easier to know if a given run has been imported

Technically you can find this information by using the select run dropdown menu: