email validator should return true for null, undefined and empty values

Fixes https://github.com/monterail/vuelidate/issues/65 and https://github.com/monterail/vuelidate/issues/66

Thank you! :D

Your welcome :)

Thanks! 😀 Can you fix the CI issue please?
/home/ubuntu/vuelidate/src/validators/email.js
  3:16  error  Extra semicolon  semi

✖ 1 problem (1 error, 0 warnings)

Sorry not experienced on github pull requests :(

Codecov Report

Merging #70 into master will not change coverage.

@@           Coverage Diff           @@
##           master      #70   +/-   ##
=======================================
  Coverage   97.63%   97.63%
=======================================
  Files          13       13
  Lines         211      211
=======================================
  Hits          206      206
  Misses          5        5

Impacted Files
Coverage Δ

src/validators/sameAs.js
100% <ø> (ø)
:white_check_mark:

src/validators/email.js
100% <100%> (ø)
:white_check_mark:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 22abef9...ae77bd0. Read the comment docs.

Codecov Report

Merging #70 into master will not change coverage.

@@           Coverage Diff           @@
##           master      #70   +/-   ##
=======================================
  Coverage   97.63%   97.63%
=======================================
  Files          13       13
  Lines         211      211
=======================================
  Hits          206      206
  Misses          5        5

Impacted Files
Coverage Δ

src/validators/sameAs.js
100% <ø> (ø)
:white_check_mark:

src/validators/email.js
100% <100%> (ø)
:white_check_mark:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 22abef9...ae77bd0. Read the comment docs.

I fixed the test case.
Sorry for the mess.

No problem. Just squash the commits please 😃

Done


Update Mtls details for customizing config

This PR updates docs for customizing config in case of secure endpoint.

@bwren
Can you review the proposed changes? Note that the validation warnings must be resolved before merging.
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Add contributing guide

This can be similar to https://github.com/plumerai/larq/blob/master/CONTRIBUTING.md

Hello,
I will create a CONTRIBUTING.md file for this project.
Best,
Nick

Cool, thanks! I will checkout your PR tomorrow.


My app is complete

please review. /cc @codepathreview @codepath

:+1: Congrats on completing the required stories and a few optionals as well! Nice work overall.

Your attention to UI/UX was impressive.
Good to see you were able to format the timestamp cleanly
Good to see you refreshed the timeline after composing a new tweet
Glad to see you made the compose activity into a dialog instead
Consider adding [progress bars] (http://guides.codepath.com/android/Handling-ProgressBars#actionbar-progress-bar) to your app whenever a network request goes out

We have provided a detailed Twitter Feedback Guide here which covers the most common issues with this submitted project. Read through the feedback guide point-by-point to determine how you could improve your submission.


Can we pass spark config like "spark.executor.memory" in DBT model?

We want to do fine-grained tune on each model, can we pass these spark params to Databricks through DBT?

We do not support this; you might be able to set these params as part of python models or with a pre-hook using SET, but I've not tested either method.

Hi @benc-db Thank you very much! for your reply.
Do we have plan to support this? because I think this is important for Spark task.

This is pretty far from what we are trying to accomplish with this library, and opens the door for many more hard to debug scenarios.  Honestly, I don't see us supporting it officially any time soon.  If a user submitted a request that could make this work across all of the compute types in a clean way, we may consider it.

Thanks got it! so this dbt-databricks adaptor is mainly focus on the Serverless cluster?

We're mainly focused on providing a consistent, reliable experience across SQL Warehouse (including serverless) and All-Purpose clusters.  Providing this config capability is technically feasible, but as I'm the only one providing support for this library, I'm concerned about the amount of effort (including on-call/maintenance) as compared to the demand for the feature.

Thanks @benc-db , May I ask another question in this? Do you have plan to support job cluster? because I found that job cluster is much more cheaper than All-purpose cluster.
And if we have some feature really want to use, can we develop it by ourselves than ask you for review?

Job clusters are only supported for python models as they do not have a Thrift server on them (a pre-req for the way we execute SQL).  And yes, I'm happy to review and merge user submitted code provided it is tested and doesn't break any existing workloads.  For this particular feature, I see we have existing code where we SET a property on the cursor.

Thanks! you just mentioned we can use python models on Job cluster, but I did't find any doc about this, can you introduce us more?

Yeah, it is unofficially supported, as a.) we inherited the code, and b.) it's a completely separate path that isn't tested.  However, enough people ask about it that at this point I think I'm stuck with it.  Here's an article that may help: https://www.linkedin.com/pulse/dbt-databricks-part-2-working-python-models-newmathdata-wailc/

Thank you very much!

Hi @benc-db, I have tested the method you sent me, it is worked, we can submit model to job cluster. But I found that for each model, there will be a new job cluster, Can we put all models into one job cluster?


Is there a way to assign an ID to compute nodes which is persistent across agent relaunches

The API to launch containers on a compute node requires a node id (Ih1,Ih2 and so on)  instead of names like moria, mordor etc. However, the ID is not easily available in the UI you have to click View in API for the node to lookup the ID. In addition the ids could change and hence scripts need to be changed to update for new ids if agents are relaunched.

It would be good if we could do one of the following:

Use name as ID
Allow the use of name in the API instead of ID
Allow the user to specify the id when launching compute nodes.

This way the scripts I am writing to bring up the entire cluster in one go can reliably put the same containers on the same nodes.

@usmanismail With the addition of scheduling/affinity rules a while ago you can accomplish this by putting a label on each host with city_of_middle_earth=moria and tell containers to go to a host with that label.
Also FYI the 1h42 IDs are in the UI path if you hover on a host link or are looking at a host, so you can see them without actually visiting the API.


lazy logging in event module

Description
#4189 ran into a lazy logging function we previously didn't understand. Now we understand it has a pretty significant purpose, and we need to plumb laziness through the event module to prevent rendering huge messages that will never be written to a user.
Checklist

[x] I have signed the CLA
[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change

Well I thought about it this morning, and this definitely didn't solve the problem. Because we're forcing the message construction at the call sites regardless of debug level, we kicked the can down the road and still have the issue. The bit that I just added that really does work, is the if ... and debug and ... parts of fire_event.
Because I was testing generators anyway, I figured I'd throw memoization to message construction in gen_msg, but that's just a bonus not part of the solution here.


No return type generated for rpc functions that return TABLE

Bug report
Describe the bug
No return type generated for rpc functions that return TABLE. If it's expected that this doesn't work, the documentation ought to say so.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Create a function like
CREATE OR REPLACE FUNCTION public.search_text_snapshots(IN query text,IN limit_param integer,IN offset_param integer)
    RETURNS TABLE(id bigint, url text, title text, highlight text, created_at timestamp with time zone)
    LANGUAGE 'plpgsql'

AS $BODY$
begin
  RETURN query
  -- Get the latest version of a page that contains matches.
  SELECT
    t.id,
    t.url,
    t.title,
    ts_headline(
      'english',
      t.data,
      websearch_to_tsquery('english', $1),
      'MaxWords=100, MinWords=50'),
    t.created_at
  FROM (
    SELECT *, RANK() OVER (PARTITION BY text_snapshot.url ORDER BY text_snapshot.created_at DESC) AS rk
    FROM  text_snapshot
    WHERE ts @@  websearch_to_tsquery('english', $1)
  ) t
  WHERE t.rk = 1
  ORDER BY t.created_at desc
  LIMIT $2
  OFFSET $3;
end;
$BODY$;

Generate types
supabase gen types typescript --local

types:
...
export interface Database {
  public: {
...
    Functions: {
...
      search_text_snapshots: {
        Args: { query: string; limit_param: number; offset_param: number }
        Returns: Record<string, unknown>[]
      }
    }
  }
}

Expected behavior
Returns isn't of unknown type.

Thanks for reporting this - let us know if upgrading to 1.17.1 fixes this :) (you might need to restart your local environment)

Works for me! 👏


Reorder categories by popularity according to taginfo

Basically this PR reorders category-route, category-road and category-path according to taginfo most used values.
The previous order was problematic because most important roads were the firsts in the list. But as a mapper, you do not often map motorways - it's often the inverse. That's why you have now tertiary road then secondary road then primary road and finally motorway (basically the order is inverted).
I also removed type/route/pipeline since taginfo reports it only used 34 times worldwide.

I kind of think it's helpful for new users to see these things in order of logical hierarchy, but haven't really questioned this assumption.
Is this really an issue for people?  I'm inclined to leave the order the way it is unless we get feedback from new mappers that they can't find what they are looking for.

Logical hierarchy should be maintained because it is going to be how beginners learn the hierarchy. The point about how frequently tags lower in the hierarchy are used vs those higher in the hierarchy is valid. Maybe a better change would be to simply flip the core tertiary ->  motorway sequence for roads as well as links and leave everything else as is?

Is this really an issue for people? I'm inclined to leave the order the way it is unless we get feedback from new mappers that they can't find what they are looking for.
When I started using iD, I found what I was looking for by selecting nearby routes and get their name; the route category is a bit disorganised in my opinion but it is difficult to know what majority of newcomers think of the current sort...

a better change would be to simply flip the core tertiary -> motorway sequence as well as links
Maybe this would be enough - my major issue yet is having links in the top 10 while I actually never used them nor see them... do you agree for that change @bhousel?

My other concern is also that Residential route is at first position - if logical order is kept, residential route should be at least after tertiary roads, should not it be?

No I don't agree with this change.  I think the current road category is fine, with residential listed first (as most frequently used) and the rest of the logical road hierarchy following.
current road category:
            "highway/residential",
            "highway/motorway",
            "highway/trunk",
            "highway/primary",
            "highway/secondary",
            "highway/tertiary",
            "highway/service",
            "highway/motorway_link",
            "highway/trunk_link",
            "highway/primary_link",
            "highway/secondary_link",
            "highway/tertiary_link",
            "highway/unclassified",
            "highway/track",
            "highway/road"

proposed changes in this PR:
            "highway/residential",
            "highway/service",
            "highway/track",
            "highway/unclassified",
            "highway/tertiary",
            "highway/secondary",
            "highway/primary",
            "highway/trunk",
            "highway/motorway",
            "highway/motorway_link",
            "highway/road",
            "highway/trunk_link",
            "highway/primary_link",
            "highway/secondary_link",
            "highway/tertiary_link"

If you are fine with current order, I guess this is a dead-end PR.


Remove next button from mainsite

 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.

This closes issue #113


y-coordinate bias in starting location of robot

The starting location of the robot seems to be biased to be to the left of the articulated object, across many evaluation episodes:
import gym
import mani_skill.env
import numpy as np

env = gym.make('OpenCabinetDoor-v0')
# env = gym.make('OpenCabinetDoor_1028-v0')

env.set_env_mode(obs_mode='state', reward_type='sparse')
ys = []
for level_idx in range(0, 20):
    obs = env.reset(level=level_idx)
    x, y = env.agent.get_state(by_dict=True)['base_pos']
    ys.append(y)
print(np.mean(ys), np.median(ys))
env.close()

Using this, I get 0.6809838 0.6660824 for env = gym.make('OpenCabinetDoor-v0'), and 0.77759504 0.75745267 for env = gym.make('OpenCabinetDoor_1028-v0'). Is there any reason why the y-coordinate is quite positive in both cases (indicating that the robot starts to the left of the articulated object more often than the right), and not close to 0?

Yes, in the two cabinet tasks, we put the robot on the left of the cabinet. This is because our single-arm robot only has a right arm, so it will make the gripper closer to the cabinet. In this way, we make the task less challenging.

I see, thanks!


Floating Label: position is not correctly aligned

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
I saw that the labels of Floating-Label are not perfectly aligned while first messing around with incorrect ellipsis on 5.3 (which has ben fixed according to other issues).
This is a screenshot of the website of version 5.2 (to have a correct version):

I would suggest a change to display the label with a better alignmend to the sides:

Reduced test cases
The problem, why this occurs is in the following css-attribute:
.form-floating>.form-select~label
transform: scale(.85) translateY(-.5rem) translateX(.15rem)

The scale factor reduces the size that was 100% before the transform.
Therefore the real width is 100%*0.85 instead of 100%.
In addition, the alignment is not perfect regarding the left-side because of translateX and translateY.
I would suggest the following change:
.form-floating>.form-select~label
padding-top: 0.5rem /*same adjustment as the transformY to display the label above the input */
padding-bottom: 1.5rem /* adjust for transformY as well*/
font-size: 85% /* adjusts the size of the text in the same way as scale */

Thank you for your work!
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
v5.2 (not tested on 5.3)

PS: the examples and code only show the select-input, but this issue effects ALL floating-labels.

The PR #40735 fixes the issue of alignment of floating labels as mentioned by the author of this issue. The said change is done in the _variable.scss file by creating 3 new variables for padding-top, padding-bottom, and font-size which are injected in the forms/_floating-labels.scss file.
@Alken0, you can have a look too here.
Kindly merge this PR as soon as possible.

fixed in https://github.com/twbs/bootstrap/pull/40735

The PR #40735 fixes the issue of alignment of floating labels as mentioned by the author of this issue. The said change is done in the _variable.scss file by creating 3 new variables for padding-top, padding-bottom, and font-size which are injected in the forms/_floating-labels.scss file.
@Alken0, you can have a look too here.
Kindly merge this PR as soon as possible.

thank you very much for your work

The PR #40735 fixes the issue of alignment of floating labels as mentioned by the author of this issue. The said change is done in the _variable.scss file by creating 3 new variables for padding-top, padding-bottom, and font-size which are injected in the forms/_floating-labels.scss file.
@Alken0, you can have a look too here.
Kindly merge this PR as soon as possible.

@poswalsameer thank you very much for your work

Thanks a lot!

Hi @julien-deramond, I have created a PR that solves the said issue, can you please review it and let me know if further changes are required? Thank You!


ARROW-5032: [C++] Install headers in vendored/datetime directory

I found that header files in vendored/datetime directory are not installed even though vendored/datetime.h is installed.  vendored/datetime.h depends on the files in vendored/datetime directory, so they should be installed.

Why hasn't this caused a build error?

@bkietz This would only matter for third-party project including those headers (possibly indirectly).

@kou Another commit candidate if you decide to do another RC.

It looks like @kou is OK with doing an RC4. I'll merge this and look at the other commits


Added more values to the CloudTrail schema

to: @airbnb/streamalert-maintainers
cc:
size: small|medium|large
resolves #
Background
Resolves https://github.com/airbnb/streamalert/issues/606
Testing
Deployed to our own StreamAlert deployment and no errors.

Coverage remained the same at 95.53% when pulling c1e54a4aa9579081b0084e15cbcffd83eee879a0 on 0xdabbad00:spiper-cloudtrail_schema_additions into 347c64b2e77df22b44f6caae334f9748e3060cea on airbnb:master.


A newline is added to the end of Commands

hi
I had a problem after copying and pasting  the command and Kubctl was not installed and show me error:
/usr/local/bin/kubectl: 2: Syntax error: newline unexpected
After that, i remove Kubctl and install again but removed newline from end of command
Now everything is OK.
I suggest  make a copy button for each command

@devNajjary would you be able to let us know an example of a web page where you see these symptoms, and explain what steps we can take to see the problem as you experienced it?

if you triple click on command text  and copy/paste to Linux terminal show this:

@devNajjary would you be able to let us know an example of a web page where you see these symptoms, and explain what steps we can take to see the problem as you experienced it?

I think @devNajjary is talking about this web page https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#install-kubectl-binary-with-curl-on-linux

@devNajjary It works well for me with no errors
$curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   154  100   154    0     0    389      0 --:--:-- --:--:-- --:--:--   388
100 44.2M  100 44.2M    0     0  5672k      0  0:00:07  0:00:07 --:--:-- 6684k

/kind support

@devNajjary if you can explain more about how to replicate the error (which shell, which OS, which web browser, and what error you see) that might help us to fix the page.
I suspect though that the existing web page is correct.

/remove-lifecycle rotten


Document pose + spherical coordinates combination on spawn

🎉 New feature
Summary

Accompanies the implementation change in

https://github.com/ignitionrobotics/ign-gazebo/pull/1263

Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[x] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[x] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[x] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.
🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸

This pull request has been mentioned on Gazebo Community. There might be relevant details there:
https://community.gazebosim.org/t/new-ignition-releases-2022-03-25-fortress-edifice-citadel/1343/1


fasta is part of periodictable and isn't needed in refl1d

Well that certainly solves the problem.


Make the jasmine.Spy type definition strongly typed

🚀 Feature Proposal
Make the type definition for jasmine.Spy (in https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/jest/index.d.ts) strongly typed.
Motivation
By making jasmine.Spy strongly typed the compiler can enforce mock return values are of the correct type. This is helpful when maintaining and refactoring large code bases, especially when the return type of a function is changed.
Example
Suppose some test code is trying to mock the return value of a function and passes a value that does not have the correct type for that function:
const mockDate = new Date();
spyOn(Date, 'now').and.returnValue(mockDate); // this is a mistake since Date.now returns number

The TypeScript compiler should be able to detect this inconsistency, helping developers make sure their mock values have the expected types.
This can be acomplished by strongly typing spyOn & jasmine.Spy type definition with something along these lines:
declare interface SpyAnd<T> {
    // other methods not included for brevity
    returnValue(val: T): Spy<T>;
    returnValues(...values: T[]): Spy<T>;
}

declare interface Spy<T> {
    // other methods not included for brevity
    and: SpyAnd<T>;
}

declare function spyOn<T extends {}, M extends keyof T>(object: T, method: M): Spy<T[M]>;

Although I agree with the spirit of your issue, the type definitions is not maintained in this repo. This issue (or PR!) should be opened against DefinitelyTyped.
Also note that the global spyOn will be removed in a future release, you should use jest.spyOn which uses a Jest mock function instead of a Jasmine one. https://jestjs.io/docs/en/mock-function-api

Sounds good. Thanks @SimenB

I have a solution for you @fpintos. I have a thin wrapper function that you can install via npm/yarn that converts a standard Jest spy into a type-safe Jest spy.
Could I have added this to DefinitelyTyped instead of introducing a new dependency? Maybe, but I found that the advanced generic types I had to use to infer the type made it onerous to utilize within the externally managed types. So basically, with this library you get an easy to use, type-safe, near-invisible micro-library that changes zero functionality at runtime. If you like it, I'd appreciate you clicking star on the repo :)
https://github.com/dgreene1/typeSafeJestSpy


Allow --verbose for server mode

Print a warning that --verbose is not really appropriate for multithreaded server environments at the top of quilc startup output (in server mode only).


Optional Author Bio?

Thank for making this beautiful template available.
What would be the easiest way to remove the author bio in the main page? I've tried to comment out
{% include author-bio.html %}

section in the home.html, but now article lists aligned to left (see: http://ozank.github.io/asuyatuyolar/ )

I'd like to do this too. But I can only find the right CSS in the generated CSS file. Which source file and where do I change this?

@stanstrup The source files are all in /_sass/, you'll probably find what you need in the page.scss partial.

Thanks again for your help and patience. I cannot for the life of me figure which line to change. If I simply add
#index {
    margin-left: 25%;
}

to the end of the document it works though.

The #index declarations are all around line 248. The media query mixins are probably what is tripping you up. Because the theme is responsive the column widths change depending on the screen size. Depending on where you place margin-left: 25%; will have different results.
You'll probably want to add it here so it pushes the main column over on larger screens only since on mobile the theme defaults to a single tube of content.
@media #{$x-large} {
    @include grid(12,4.5);
    margin-left: 25%;
}

The smarter thing would be to use prefix mixin to pad the left and fill the space originally occupied by the author sidebar.
@media #{$x-large} {
    @include grid(12,4.5);
    @include prefix(12,3); // adds 3 columns of blank space to the left
}

Thanks so much! It works great. And you are right. I thought I had a decent grasp of basic CSS but I am wholly unfamiliar with this syntax.

@stanstrup For the most part Sass is CSS, it just has a few tricks up its sleeve like nesting, variables, and mixins to augment things. The basics are documented here if you're interested.

Thanks for the pointer. I will read up on this as I move along with my own site.

For reference here is a version with no sidebar and more space in the middle based on @srijanshetty's fork (has categorized posts).
It has been cleaned up (stuff deleted) to be a minimal starting point for a new site.


Create LICENSE.md

This will be needed when we publish our app to the app store.

Where did you get this from/Is this exhaustive and legally safe? Can you include a link to this on the About page and remove the current text?

MIT is the standard license OpenSource projects, basically allows all users to do anything they want with the software. You can get the license via Github itself, there is a dialog to help you add the right license.
Where in the about page should I add this? (This is not the terms of service, just a license for software use)


[import-is-undefined] error for esbuild with angular version mixin in an lazy loading module

Command
build
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
I have upgrade the angular version in 17.1, and in my project I also have an angular/material dependency with  version16.
And project also has the route config about lasy loading.
when I run the build with builder: application, I can see below output with import is undefined error

Just want confirm whether this comes from the version confilict for some config error or builder bugs ?
Thanks a lot if any suggestions or guide here ~~
Minimal Reproduction
retro code repo:  https://github.com/xkx-dev/angular-custom-builder-demo/tree/master
with master branch
steps:

install (may conflict, and I'm using the --force to resolve )
npm run build

Exception or Error
Application bundle generation complete. [14.152 seconds]
▲ [WARNING] Import "ɵɵInputFlags" will always be undefined because there is no matching export in<EMAIL_ADDRESS>[import-is-undefined]

    src/app/aria-label.directive.ts:18:160:
      18 │ ...s: { ariaLabelValue: [i0.ɵɵInputFlags.None, "appAriaLabel", "...
         ╵                             ~~~~~~~~~~~~

===================================================================

Your Environment
_                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 17.1.2
Node: 18.19.0
Package Manager: npm 10.2.3
OS: win32 x64

Angular: 17.0.9
... animations, common, core, forms, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1701.2
@angular-devkit/build-angular   17.1.2
@angular-devkit/core            17.1.2
@angular-devkit/schematics      17.1.2
@angular/cli                    17.1.2
@angular/compiler               17.1.2
@angular/compiler-cli           17.1.2
@angular/material               16.2.13
@schematics/angular             17.1.2
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.3

Anything else relevant?

lazy load in routes: src\routes.ts
legacy material module import:   src\app\material.module.ts

It’s looks like the version of @angular/compiler (17.1.2) @angular/core (17.0.9) and other framework packages are mismatching.
Please make sure that the same patch version is used. In this case the NPM peer dependency warnings are correct and should not be ignored.


[Bug] Steam 下载时 CPU 占用非常高

Verify steps

[X] 我已经阅读了 文档，了解所有我编写的配置文件项的含义，而不是大量堆砌看似有用的选项或默认值。
[ ] 我未仔细看过 文档 并解决问题
[ ] 我未在 Issue Tracker 中寻找过我要提出的问题
[X] 我已经使用最新的 Alpha 分支版本测试过，问题依旧存在
[X] 我提供了可以在本地重现该问题的服务器、客户端配置文件与流程，而不是一个脱敏的复杂客户端配置文件。
[X] 我提供了可用于重现我报告的错误的最简配置，而不是依赖远程服务器、TUN、图形界面客户端或者其他闭源软件。
[X] 我提供了完整的配置文件与日志，而不是出于对自身智力的自信而仅提供了部分认为有用的部分。

操作系统
Windows
系统版本
版本	    Windows 11 家庭中文版
版本号	 23H2
操作系统版本  	22631.4317
体验	Windows Feature Experience Pack 1000.22700.1041.0
Mihomo 版本
Mihomo Meta alpha-ca3f1eb windows amd64 with go1.23.2 Sat Oct 12 00:31:56 UTC 2024
Use tags: with_gvisor
配置文件

config.yaml
mode: rule
mixed-port: 18964
allow-lan: false
log-level: debug
ipv6: true
external-controller: <IP_ADDRESS>:9099
secret: ''
geodata-mode: false
profile:
  store-selected: true
  store-fake-ip: true
geo-auto-update: true
dns:
  enable: true
  ipv6: true
  prefer-h3: true
  use-hosts: true
  use-system-hosts: false
  listen: :1053
  enhanced-mode: fake-ip
  fake-ip-range: <IP_ADDRESS>/16
  default-nameserver:
  - <IP_ADDRESS>
  - <IP_ADDRESS>
  - <IP_ADDRESS>
  - <IP_ADDRESS>
  - '[2402:4e00::]:53'
  - '[2400:3200::1]:53'
  nameserver:
  - https://<IP_ADDRESS>/dns-query#DIRECT
  - https://<IP_ADDRESS>/dns-query#DIRECT
  - <IP_ADDRESS>#DIRECT
  - <IP_ADDRESS>#DIRECT
  fallback:
  - https://<IP_ADDRESS>/dns-query#🚀 节点选择
  - https://<IP_ADDRESS>/dns-query#🚀 节点选择
  - tls://<IP_ADDRESS>:853#🚀 节点选择
  - tls://<IP_ADDRESS>:853#🚀 节点选择
  proxy-server-nameserver:
  - https://<IP_ADDRESS>/dns-query
  - https://<IP_ADDRESS>/dns-query
  - https://doh.pub/dns-query
  - https://<IP_ADDRESS>/dns-query
  - https://dns.alidns.com/dns-query
  nameserver-policy:
    geosite:private,apple,bilibili,category-games@cn:
    - https://<IP_ADDRESS>/dns-query#DIRECT
    - https://<IP_ADDRESS>/dns-query#DIRECT
    - https://<IP_ADDRESS>/dns-query#DIRECT
    geosite:gfw:
    - https://<IP_ADDRESS>/dns-query#🚀 节点选择
    - https://<IP_ADDRESS>/dns-query#🚀 节点选择
    - tls://<IP_ADDRESS>:853#🚀 节点选择
    - tls://<IP_ADDRESS>:853#🚀 节点选择
    geosite:cloudflare,google,telegram,facebook:
    - https://<IP_ADDRESS>/dns-query#🚀 节点选择
    - https://<IP_ADDRESS>/dns-query#🚀 节点选择
    - tls://<IP_ADDRESS>:853#🚀 节点选择
    - tls://<IP_ADDRESS>:853#🚀 节点选择
    geosite:geolocation-!cn:
    - https://<IP_ADDRESS>/dns-query#🚀 节点选择
    - https://<IP_ADDRESS>/dns-query#🚀 节点选择
    - tls://<IP_ADDRESS>:853#🚀 节点选择
    - tls://<IP_ADDRESS>:853#🚀 节点选择
  fallback-filter:
    geoip: true
    geoip-code: CN
    ipcidr:
    - <IP_ADDRESS>/8
    - <IP_ADDRESS>/22
    - <IP_ADDRESS>/8
    - <IP_ADDRESS>/10
    - <IP_ADDRESS>/8
    - <IP_ADDRESS>/16
    - <IP_ADDRESS>/12
    - <IP_ADDRESS>/24
    - <IP_ADDRESS>/24
    - <IP_ADDRESS>/24
    - <IP_ADDRESS>/16
    - <IP_ADDRESS>/15
    - <IP_ADDRESS>/24
    - <IP_ADDRESS>/24
    - <IP_ADDRESS>/4
    - <IP_ADDRESS>/4
    - <IP_ADDRESS>/8
    domain:
    - +.facebook.com
  fake-ip-filter:
  - localhost
  - '*.localhost'
  - lan
  - '*.lan'
tcp-concurrent: true
unified-delay: true
geox-url:
  geoip: https://ghp.ci//https://github.com/MetaCubeX/meta-rules-dat/releases/download/latest/geoip.dat
  geosite: https://ghp.ci//https://github.com/MetaCubeX/meta-rules-dat/releases/download/latest/geosite.dat
  mmdb: https://ghp.ci/https://github.com/MetaCubeX/meta-rules-dat/releases/download/latest/country.mmdb
  asn: https://ghp.ci/https://github.com/xishang0128/geoip/releases/download/latest/GeoLite2-ASN.mmdb
geo-update-interval: 24
proxies:
- name: '[SS] 🇭🇰 HKG 11'
  server: example.com
  port: 20011
  type: ss
  cipher: aes-128-gcm
  password: example
  plugin: obfs
  plugin-opts:
    mode: http
    host: example.com
  udp: true
proxy-groups:
- name: 🚀 节点选择
  type: select
  proxies:
  - '[SS] 🇭🇰 HKG 11'
rules:
- DOMAIN-SUFFIX,s.team,🚀 节点选择
- DOMAIN,fanatical.com,🚀 节点选择
- DOMAIN,humblebundle.com,🚀 节点选择
- DOMAIN,playartifact.com,🚀 节点选择
- DOMAIN-SUFFIX,steam-chat.com,🚀 节点选择
- DOMAIN-SUFFIX,steamcommunity.com,🚀 节点选择
- DOMAIN-SUFFIX,steamgames.com,🚀 节点选择
- DOMAIN-SUFFIX,steamstatic.com,🚀 节点选择
- DOMAIN-SUFFIX,steamusercontent.com,🚀 节点选择
- DOMAIN-SUFFIX,underlords.com,🚀 节点选择
- DOMAIN-SUFFIX,valvesoftware.com,🚀 节点选择
- DOMAIN-SUFFIX,steamstore-a.akamaihd.net,🚀 节点选择
- DOMAIN,api.steampowered.com,🚀 节点选择
- DOMAIN,store.steampowered.com,🚀 节点选择
- DOMAIN,steampowered.com,🚀 节点选择
- DOMAIN-SUFFIX,steamserver.net,DIRECT
- DOMAIN-SUFFIX,steamcontent.com,🚀 节点选择
- DOMAIN,cm.steampowered.com,DIRECT
- DOMAIN-SUFFIX,steamchina.com,DIRECT
- DOMAIN,csgo.wmsj.cn,DIRECT
- DOMAIN,dota2.wmsj.cn,DIRECT
- DOMAIN,wmsjsteam.com,DIRECT
- DOMAIN,dl.steam.clngaa.com,DIRECT
- DOMAIN,dl.steam.ksyna.com,DIRECT
- DOMAIN,st.dl.bscstorage.net,DIRECT
- DOMAIN,st.dl.eccdnx.com,DIRECT
- DOMAIN,st.dl.pinyuncloud.com,DIRECT
- DOMAIN,steampipe.steamcontent.tnkjmec.com,DIRECT
- DOMAIN,cdn.mileweb.cs.steampowered.com.8686c.com,DIRECT
- DOMAIN,cdn-ws.content.steamchina.com,DIRECT
- DOMAIN,cdn-qc.content.steamchina.com,DIRECT
- DOMAIN,cdn-cdn-ali.content.steamchina.com,DIRECT
- DOMAIN,xz.pphimalayanrt.com,DIRECT
- DOMAIN,steampowered.com.8686c.com,DIRECT
- DOMAIN,steamstatic.com.8686c.com,DIRECT
- DOMAIN,gstore.val.manlaxy.com,DIRECT
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/23,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/23,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/23,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/23,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/23,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/22,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/22,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/23,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/23,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/23,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/23,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/23,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/23,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/22,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/24,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/22,DIRECT,no-resolve
- IP-CIDR,<IP_ADDRESS>/23,DIRECT,no-resolve
- GEOIP,CN,DIRECT
- MATCH,🚀 节点选择

描述
Steam 下载时 mihomo CPU 占用可达 100%（ 14600KF，13700F 都会）
此时鼠标等会卡顿。

重现方式

下载 https://github.com/MetaCubeX/mihomo/releases/download/Prerelease-Alpha/mihomo-windows-amd64-alpha-ca3f1eb.zip
将配置文件放到同一文件夹
使用 .\mihomo-windows-amd64.exe -d D:\mihomo 启动 core
系统代理设置为 <IP_ADDRESS>:18964
打开 Steam 下载一个游戏
系统卡顿，CPU 100%

日志
日志一直是类似内容在快速刷屏，由于 Github 长度限制无法放上完整内容。
log.zip

Log
time="2024-10-13T15:29:59.1457805+08:00" level=debug msg="Auth success from <IP_ADDRESS>:49157 -> "
time="2024-10-13T15:29:59.1462821+08:00" level=debug msg="[Rule] use default rules"
time="2024-10-13T15:29:59.1462821+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.1462821+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.1647772+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.1647772+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.183962+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49157 --> xz.pphimalayanrt.com:80 error: dial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.1937952+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49154 --> xz.pphimalayanrt.com:80 error: dial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.1947971+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.1947971+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.2187358+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49157 --> xz.pphimalayanrt.com:80 error: dial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.2388583+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.2388583+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.2623287+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49157 --> xz.pphimalayanrt.com:80 error: dial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.2908319+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.2908319+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.3014061+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.3014061+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.3338186+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49184 --> xz.pphimalayanrt.com:80 error: dial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.3373514+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49157 --> xz.pphimalayanrt.com:80 error: dial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.3741169+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.3741169+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.396551+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49157 --> xz.pphimalayanrt.com:80 error: dial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.4368559+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.4369895+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.4601688+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.4601688+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.4752883+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49159 --> xz.pphimalayanrt.com:80 error: dial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.485377+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49161 --> xz.pphimalayanrt.com:80 error: dial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.5538498+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.5538498+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.5701611+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.5701611+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.5901081+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49157 --> xz.pphimalayanrt.com:80 error: dial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.5952855+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.5952855+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.6128947+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49184 --> xz.pphimalayanrt.com:80 error: dial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.6185905+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49173 --> xz.pphimalayanrt.com:80 error: dial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.7541461+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.7541461+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.7785883+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49153 --> xz.pphimalayanrt.com:80 error: dial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:29:59.8224073+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:29:59.8224073+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:29:59.8485251+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49157 --> xz.pphimalayanrt.com:80 error: dial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:30:00.1144539+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [240e:94c:4000:1400:0:1:b6f2:3807 240e:94c:4400:300::c 240e:94d:2:100::c 240e:94c:4c01:100::5] AAAA, expire at 2024-10-13 15:30:10"
time="2024-10-13T15:30:00.1144539+08:00" level=debug msg="[DNS] cache hit xz.pphimalayanrt.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:30:57"
time="2024-10-13T15:30:00.1367215+08:00" level=warning msg="[TCP] dial DIRECT (match Domain/xz.pphimalayanrt.com) <IP_ADDRESS>:49157 --> xz.pphimalayanrt.com:80 error: dial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4400:300::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp <IP_ADDRESS>:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94d:2:100::c]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4000:1400:0:1:b6f2:3807]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted.\ndial tcp [240e:94c:4c01:100::5]:80: connectex: Only one usage of each socket address (protocol/network address/port) is normally permitted."
time="2024-10-13T15:30:00.1589493+08:00" level=warning msg="Mihomo shutting down"

Log2
time="2024-10-13T15:34:00.2918416+08:00" level=debug msg="Auth success from <IP_ADDRESS>:50991 -> "
time="2024-10-13T15:34:00.2918416+08:00" level=debug msg="[Rule] use default rules"
time="2024-10-13T15:34:00.2918416+08:00" level=debug msg="[DNS] cache hit dl.steam.clngaa.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:34:32"
time="2024-10-13T15:34:00.2918416+08:00" level=debug msg="[DNS] cache hit dl.steam.clngaa.com --> [240e:94c:4c01:100::7 240e:94c:4400:300::e 240e:94d:2:100::e 240e:983:1201::a] AAAA, expire at 2024-10-13 15:34:31"
time="2024-10-13T15:34:00.2989926+08:00" level=info msg="[TCP] <IP_ADDRESS>:50991 --> dl.steam.clngaa.com:80 match Domain(dl.steam.clngaa.com) using DIRECT"
time="2024-10-13T15:34:00.3114356+08:00" level=debug msg="Auth success from <IP_ADDRESS>:49319 -> "
time="2024-10-13T15:34:00.3114356+08:00" level=debug msg="[Rule] use default rules"
time="2024-10-13T15:34:00.3114356+08:00" level=debug msg="[DNS] cache hit gstore.val.manlaxy.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:34:39"
time="2024-10-13T15:34:00.3114356+08:00" level=debug msg="[DNS] cache hit gstore.val.manlaxy.com --> [240e:94c:4000:1400:0:1:b6f2:382b 240e:94c:4000:1400:0:1:b6f2:3846 240e:94c:4000:1400:0:1:b6f2:382d 240e:94c:4000:1400:0:1:b6f2:3807] AAAA, expire at 2024-10-13 15:34:34"
time="2024-10-13T15:34:00.3225127+08:00" level=info msg="[TCP] <IP_ADDRESS>:49319 --> gstore.val.manlaxy.com:80 match Domain(gstore.val.manlaxy.com) using DIRECT"
time="2024-10-13T15:34:00.3326552+08:00" level=debug msg="Auth success from <IP_ADDRESS>:49337 -> "
time="2024-10-13T15:34:00.3326552+08:00" level=debug msg="Auth success from <IP_ADDRESS>:49306 -> "
time="2024-10-13T15:34:00.3326552+08:00" level=debug msg="[Rule] use default rules"
time="2024-10-13T15:34:00.3326552+08:00" level=debug msg="[Rule] use default rules"
time="2024-10-13T15:34:00.3326552+08:00" level=debug msg="[DNS] cache hit dl.steam.clngaa.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:34:32"
time="2024-10-13T15:34:00.3326552+08:00" level=debug msg="[DNS] cache hit dl.steam.clngaa.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:34:32"
time="2024-10-13T15:34:00.3326552+08:00" level=debug msg="[DNS] cache hit dl.steam.clngaa.com --> [240e:94c:4c01:100::7 240e:94c:4400:300::e 240e:94d:2:100::e 240e:983:1201::a] AAAA, expire at 2024-10-13 15:34:31"
time="2024-10-13T15:34:00.3326552+08:00" level=debug msg="[DNS] cache hit dl.steam.clngaa.com --> [240e:94c:4c01:100::7 240e:94c:4400:300::e 240e:94d:2:100::e 240e:983:1201::a] AAAA, expire at 2024-10-13 15:34:31"
time="2024-10-13T15:34:00.3488234+08:00" level=info msg="[TCP] <IP_ADDRESS>:49337 --> dl.steam.clngaa.com:80 match Domain(dl.steam.clngaa.com) using DIRECT"
time="2024-10-13T15:34:00.351379+08:00" level=info msg="[TCP] <IP_ADDRESS>:49306 --> dl.steam.clngaa.com:80 match Domain(dl.steam.clngaa.com) using DIRECT"
time="2024-10-13T15:34:00.3653026+08:00" level=debug msg="Auth success from <IP_ADDRESS>:49324 -> "
time="2024-10-13T15:34:00.3653026+08:00" level=debug msg="Auth success from <IP_ADDRESS>:49365 -> "
time="2024-10-13T15:34:00.3658113+08:00" level=debug msg="[Rule] use default rules"
time="2024-10-13T15:34:00.3658113+08:00" level=debug msg="[Rule] use default rules"
time="2024-10-13T15:34:00.3658113+08:00" level=debug msg="[DNS] cache hit dl.steam.clngaa.com --> [240e:94c:4c01:100::7 240e:94c:4400:300::e 240e:94d:2:100::e 240e:983:1201::a] AAAA, expire at 2024-10-13 15:34:31"
time="2024-10-13T15:34:00.3658113+08:00" level=debug msg="[DNS] cache hit dl.steam.clngaa.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:34:32"
time="2024-10-13T15:34:00.3658113+08:00" level=debug msg="[DNS] cache hit dl.steam.clngaa.com --> [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>] A, expire at 2024-10-13 15:34:32"
time="2024-10-13T15:34:00.3658113+08:00" level=debug msg="[DNS] cache hit dl.steam.clngaa.com --> [240e:94c:4c01:100::7 240e:94c:4400:300::e 240e:94d:2:100::e 240e:983:1201::a] AAAA, expire at 2024-10-13 15:34:31"
time="2024-10-13T15:34:00.3783636+08:00" level=info msg="[TCP] <IP_ADDRESS>:49324 --> dl.steam.clngaa.com:80 match Domain(dl.steam.clngaa.com) using DIRECT"
time="2024-10-13T15:34:00.3830072+08:00" level=warning msg="Mihomo shutting down"

额外信息
profile+heap.zip

2 台设备，本来设备 A 是不会出现此问题的，只有系统 B 会出现，结果最近 A 还是出现了。
A：13700F + 40G RAM + Windows 11 家庭中文版
B：14600KF + 48G RAM + Windows 11 专业版

也尝试过
  nameserver-policy:
    geosite:steam@cn:
    - <IP_ADDRESS>#DIRECT
    - <IP_ADDRESS>#DIRECT
    - <IP_ADDRESS>#DIRECT

以及 steam 下载域名加入 fake-ip-filter 均无效。

这是预期行为,任意代理软件处理steam连接都会高占用


We need frog release names

Bring back the frogs :frog:

You would think that with many of the devs going to Fosdem that Philip could take the time this weekend to fix this. Sad.

What's Fosdem? I heard there's a conference at Brussels called Frogdem, but that can't possibly be what you're referring to, can it?

I'm getting sporadic frame rate stutters lately. I'm fairly certain it's because the graphics pipeline needs frog names.

One note that could move this from a simple regression fix to a true enhancement would be if the release name was also appended to the version number displayed in DXVK_HUD. For example:
DXVK v1.6.0-WetToadsInYourArea
D3D11
GeForce RTX 2080
Driver: 440.48.02
Vulkan: 1.2.131
FPS: 64

still not fixed, kinda expected anyway.......
i heard dxvk is in maintanance mode right now...

still not fixed!

Wenn das der Kaiser wüsste!

we cant leave the frogs hanging, bring back froggy release names

can we make this a priority number 1 please, this is croaking painful!

Who would have guessed a side effect of merging D9VK be a frog invasion.

🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸
🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸
🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸
🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸
🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸🐸

*The Imperial March plays*

bruh


node ssl_server.js & fails

I'm following the installation instructions from the README file, and I get to the following step:
node ssl_server.js &

which fails:
$ node ssl_server.js
module.js:338
    throw err;
          ^
Error: Cannot find module '<streamium_directory>/ssl_server.js'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Function.Module.runMain (module.js:501:10)
    at startup (node.js:129:16)
    at node.js:814:3

should that instruction be:
node ssl_peerjs.js

instead?

I had the same problem.  I think the suggested change is correct.

There doesn't seem to be any activity on this repo. Closing


MInt syntax with no uses of Int2MInt crashes

Compiling this code crashes the code generator; if the commented line is un-commented then it will compile and run correctly.
module TEST
  imports INT
  imports MINT

  syntax MInt{1}

  // rule _:Int => Int2MInt(0)::MInt{1}
endmodule

If the code is ill-formed for some reason when the rule is not present, we should emit a friendlier error message either in the frontend or in the backend.

This is a known bug; there's no reason it shouldn't work but is very low priority because there's no good reason to declare and not use one of these sorts.

Though @dwightguth comments that it's a confusing error for new users trying to experiment with MInt{...}; we should try and fix this.


Happy_Hacking... label not vertically aligned in header.

Happy_Halloween label is not vertically aligned in header. I would like to work on the same.

Sure

@sudz123 I am having difficulty in syncing my forked repo with your original repo. Can you help me with the issue?

Once you have forked the repo, make sure you make any new changes on a new branch only. After forking the repo, always do a git pull to make sure your local repo is updated with the upstream master. In case there are any conflicts on the branch in which you are making changes do a git rebase master. In case you have made changes to your master by mistake do a git reset --hard. Checkout the egghead.io links I have provided in the readme. Let me know if all this helps.

@sudz123 The issue has already been fixed I guess. Please review it once and close the issue.


Recipes to be split into different JEI categories.

added initial separation, more work to be done:

allow structure to define option texture for the JEI tab


#1730 fix bug that cross-test generates data out of the target folder

PR #1730  did not fix the problem that cross-test generates data out of the target folder.

use iotdb-server:test-jar to import the EnvironmentUtils.java
put all configurations into test/resources

@mychaow

PR #1730 did not fix the problem that cross-test generates data out of the target folder.

use iotdb-server:test-jar to import the EnvironmentUtils.java
put all configurations into test/resources

@mychaow

Got it!


Do not transform layers when transforming a parent folder

Closes #482

@TrueDoctor @otdavies thoughts about this being O(n^2)? Any less expensive way to do this? It's called every mousemove which is rather a frequent.

@TrueDoctor @otdavies thoughts about this being O(n^2)? Any less expensive way to do this? It's called every mousemove which is rather a frequent.

Yes, there are functions in the graphene document that will likely make this faster / easier. Take a look at shallowest common folder and it's neighboring utility functions. I will provide an explicit example when I am able to pull the PR and take a look at it.

@TrueDoctor @otdavies thoughts about this being O(n^2)? Any less expensive way to do this? It's called every mousemove which is rather a frequent.

I believe in this scenario the function you want is called: shallowest_unique_layers, in document.rs. It only returns unique layers in the selection, aka it excludes children of folders but doesn't exclude layers that are neighbors of the folder. This is the exact situation that @0HyperCube  is solving here I think.


Background not appear appear when it save

When i test the project, try add shape or line in backgroud. After i saved it and check the images, the shape or line is appear, but the background or image that added not appear. I want to fixed that but the backgroundImage not null when added images, make me really confuse
https://user-images.githubusercontent.com/72773420/219107601-64e14815-15f8-4518-86e6-67686e190c07.mp4

Ohh wow. It seems we didn't take note of the export when we added the image import feature.
I'll look into it and try to get it fixed.

The demo link in Readme, the export is goes well.

Yes, you're right. It seems the issue only exists in debug mode. Can you tell me the Flutter version you're using?


🖌 Fix theme palette.

Fix black background on some special symbols.

Thanks @dotcypress! I pushed the update to NPM.


A couple minor changes

Added support for persisting static content using the advice from https://github.com/cdubz/babybuddy/issues/46#issuecomment-394020997. Thanks @djmwj !
Fixed a couple yamllint warning messages.
Set some values explicitly to match docker-compose config output.

Coverage remained the same at 99.611% when pulling ded6f2cf9dd64bcfd2057186747277a8c5411d42 on paulcalabro:paulcalabro-patch-1 into 74f089fcecff33a5bedd6565dc7b5c3b10b5b144 on cdubz:master.

Thanks!


Wishlist: API for domain tags

The API currently has three methods related to domain tags, but it doesn't really lend itself to navigating from a domain to its tag(s).
Could we please have the following? This is in rough order of usefulness for me.

/api/v2.0/domains/:id/tags - fetch tags for a particular domain
/api/v2.0/domains/:tag/tagged - fetch domains which have a particular tag
/api/v2.0/domains/tags - enumerate available tags

I guess a mapping between numeric tag IDs to human-readable labels could be technically doable but of limited usefulness, so I'm thinking the API might as well just use and expose the human labels only (though they might change over time). Having to go via the numeric tag IDs would be robust against renames but complicate the simple actions. (Maybe the API should have a set of well-defined error responses too, though?)

Sorry, I'm blind.

Ehm... for reference.. I meant #466.


Fixed deleteindex regex + unit test

PR for #147

Coverage remained the same at 83.216% when pulling 99a8c7198f8cb5ff72e2b42f89929ab974d98e7f on 147 into fd19599275153daaf992b038418d1c4f889b2d2c on master.

@rultor merge

@rultor merge

@amihaiemil OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@amihaiemil Done! FYI, the full log is here (took me 3min)


feat: add custom GH props

Looks alright, but I am not sure what is the use case here. Are there some edge cases where you would want to inject different props to gesture handler here?

Yes, adding simultaneous handlers


add idle timeout in meshConfig

fix envoyproxy
link istio/api PR https://github.com/istio/api/pull/799

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: devincd
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rshriram
If they are not already assigned, you can assign the PR to them by writing /assign @rshriram in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @devincd. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@devincd: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@devincd: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Blocking error in console: "Uncaught Error: Extension context invalidated"

See the proposed fix in https://github.com/decentraland/explorer/issues/1333. This could be fixed using the same approach.


How do I take 2 seperate variables and turn them into one prompt

I just want it to do 20, not 400.
20 tools
20 inventors
20 responses, not 400

To do pairwise things you need to use Tabular data. ChainForge has no way of knowing what inventor you’d want to pair with what tool.
For the example you’ve shown, note also that you’re double-using the variables “inventor” and “tool” in your last prompt node —in general all variables should be unique. Inventor here is really the list of entities extracted, so it should be named appropriately.
For referring to a variable downstream that appears in the upstream data, you can use a implicit template variable. See the docs for details, you basically do {#tool}.
Closing the issue as this seems a conceptual misunderstanding, not a problem with ChainForge itself.


Migrate chromium implementations for wolvic under org.chromium.wolvic

Chromium implementations in wolvic side are migrated under org.chromium.wolvic under org.chromium.wolvic.

This PR depends on https://github.com/Igalia/wolvic/pull/624.


New release names in polkadot-sdk

polkadot-sdk change to a different naming schema for their releases:
https://github.com/paritytech/polkadot-sdk/releases/tag/polkadot-stable2407
We should look into what this means for us. Should we also change the naming of our releases and branches?

Yes, we should definitely change our release name as well.
Suggested branch name: polkadot-stable2407-2 (exactly the same as the one Parity uses). What do you think?
As crates.io is now used by Parity and our users as well, we should probably add a crates.io release cycle as well. Are we doing something like that already?

I have to say I'm not a big fan of the naming approach of parity. I find it very unclear how stable2407, stable2407-1 and stable2407-02 are related (for example stable2407-2 was released in September). Still I think for the branches it makes sense to use the same as parity.
I wonder if for crates.io a release is always tied to a polkadot release? And how does a user know which polkadot version is supported?
Parity seems to write a version in the tagline of the crate which again does not make sense to me as this is not tied to a version: https://crates.io/crates/pallet-timestamp/

Idea from encointer: Use major version to indicate a new api-client release and minor for polkadot updates.
E.g. 1.2.0 -> version 1 from api-client and version 2 of polkdaot. If polkadot updates and we follow, it will be released as 1.3.0.
If the api-client creates a new release it will be 2.0.0. Does this sound correct @Niederb ?

Yes, that's the general idea

Then a concrete TODO to solve this issue would be:

[ ] update to newest parity release (on github master, whichever commits fits the newest release)
[ ] publish a new crates.io release with the version 1.0.0
[ ] create a new branch pointing to the respective release branch (is this still needed?)

Or should we wait with the version 1.0.0 for something specific?

If we adapt the versioning approach I would increase the major version to prevent/reduce confusion when someone is updating

See #809


Adding Docker support

Documentation needs to be updated. Closes #9.

The merge is awaiting the documentation.


compress/bzip2: add support for concatenated bzip2 files

This is not a bug, it's a feature request.

Consider you have concatenated two valid bzip2 files. The resulted file (like the
attached one) will be correctly decompressed by the /bin/bunzip2, but compress/bzip2
will only decompress the first half.
Attachments:

repro-concatenated.bz2 (201690 bytes)

Using go1.5.1
This is supported and can be closed. This was added in https://github.com/golang/go/commit/8a0779f9b91e3392d90dab9217be7fdbee08f523.
I verified that Go's version and the C bzip2 program output the same thing.


Doesn't build on osx.

Which operating system does the issue occur on?
using latest macosx, 2017 13 inch macbook pro with out the touchbar.
fish shell.
rust version
rustc 1.24.1

I compiled the repo following the instructions in the readme and the result looks like this when running the application.

using default .alacritty.yml? Any output from doing cargo run or  failing that, from RUST_LOG=alacritty=debug cargo run?

Since there has been no feedback on this issue and it does work on multiple macOS versions, I'm closing this as resolved.
If you should still run into this problem, please make sure that you have the latest Rust version installed (ideally with rustup). And if you run macOS 10.12 or lower, please try running https://github.com/jwilm/alacritty/pull/1605 instead.


Cuteolaf/feature/requested role log

Codecov Report

Merging #239 (1182d41) into main (5cd0bdb) will decrease coverage by 0.13%.
The diff coverage is 77.46%.

@@            Coverage Diff             @@
##             main     #239      +/-   ##
==========================================
- Coverage   81.51%   81.39%   -0.13%
==========================================
  Files          58       58
  Lines        5465     5493      +28
==========================================
+ Hits         4455     4471      +16
- Misses       1010     1022      +12

Impacted Files
Coverage Δ

pallets/roles/src/functions.rs
76.06% <60.97%> (-8.55%)
:arrow_down:

pallets/roles/src/lib.rs
77.86% <100.00%> (+2.86%)
:arrow_up:

pallets/roles/src/tests.rs
100.00% <100.00%> (ø)

pallets/share_distributor/src/functions.rs
91.66% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.